• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM RELEASE] 2.2-based Byron Bare

Okay, then it's definitely it not being able to set it up, *not* that it's missing something required for it to work. I have one somewhat far-fetched idea that I'll try tonight.

I agree. I would say it must be something with my headset, but it works on every other rom stock or custom. When it doesn't pair after FCing, it gives a "couldn't pair with this device" something about wrong pin or passcode. Let me know if there is something else I can do to test.
 
I agree. I would say it must be something with my headset, but it works on every other rom stock or custom. When it doesn't pair after FCing, it gives a "couldn't pair with this device" something about wrong pin or passcode. Let me know if there is something else I can do to test.

Do you have another device you can attempt to pair with your phone?
 
Regarding wifi tether: It seems that I had a false positive. If you install (in normal /data space), then flash a /system version overtop of it, it will continue to work. However, it's still not working if you flash from the beginning. I have no idea why.
 
Experimental bluetooth fixer. Backup before trying, please.

EDIT: updated: byron_bluefix.zip

Mediafire is not liking me this morning, can you post it here?

Edit - Mediafire is working with you other links, so it must be something to do with this one.

Edit2 - My car BT doesn't like Byron either, did the same thing as my earpiece. Obviously, haven't tried the 'fix' yet.
 
Mediafire is not liking me this morning, can you post it here?

Edit - Mediafire is working with you other links, so it must be something to do with this one.

Edit2 - My car BT doesn't like Byron either, did the same thing as my earpiece. Obviously, haven't tried the 'fix' yet.

The file is fine, working for me at work. Are you using the updated one or one you got via email subscription to this thread? The latter would no longer work.

I'm attempting to attach the file here.
 

Attachments

The file is fine, working for me at work. Are you using the updated one or one you got via email subscription to this thread? The latter would no longer work.

I'm attempting to attach the file here.

When I click on the download link within media fire, it goes to a 403 forbidden page. Maybe because I don't have an account with them. Like I said all your other MF links work fine, just that one.

Anyhow, since I don't subcribe to this thread, I downloaded the latest one that you attached to your last post.

It nows says that pairing was refused by my earpiece. When I try it again it FCs. Definetly different then what it did before. It did the same thing via my nandroid backup or fresh Bryon lite install.

Edit - BTW, do you not have a BT device or are you just not having problems with it?
 
I have a similar problem. I can pair with my bluetooth headset fine, but when I attempt to pair with my laptop, it will FC. When I initiate pairing from my phone, it phone finds my laptop, but can't pair with it. I get "unable to pair HP rejected..." When I initiate pairing on my laptop, it displays the choose your pin, etc. but as soon as I select "enter pin" and hit next, it FC on my phone. I downloaded the bluetooth fix, but have no idea what to do with the file. I'm new to all this. I'm running Bryon Full, BTW. It worked before I rooted and flashed.
 
@icon123 - bt works as expected for me in every imaginable test
@corki2 - flash it like a rom, using recovery, over byron
 
Thanks darkxsun. I flashed the BT update but it had no effect. I finally figured out it was an issue with my laptop, not the ROM. I had to reinstall my BT drivers. It's working fine now. I love this ROM. :)
 
icon, do you have the Voice Dial addon installed? Try installing that, then connect again.
 
icon, do you have the Voice Dial addon installed? Try installing that, then connect again.

Reinstalled rom and addon, just to make sure. Although it didn't seem to FC as much, it did say that it was rejected by my headset more. I tried it with your voice dial add-on and with and without the BT fix you posted a couple of days ago.

In never gets to the confirmation point where it asks if you want to connect with BT device. These error messages happen right when I click the BT device to pair.

I appreciate your dilegence, but since no one else seems to be having this same problem, you can let it go. Thanks for trying.
 
Thread is old, but problem I'm having isn't listed so I thought I'd add.

After flashing with Byron Bare on my LG Ally 2.2, it boots fine, except I get to the "Welcome to Ally" screen and my touch screen no longer works.

Do you have any idea of how to fix this? I've tried other roms, I've tried a nandroid restore, I've tried stock rom, I've tried taking battery out, push power 5 times to reset, I can get into my recovery mode to launch the roms from my SD, but that's the extent of anything I can do otherwise.

ANY ideas, would be wonderful. It sounds to me like something within' one of the roms (not specifically yours) changed some radio setting or otherwise that I'm unable to change back without the knowledge of how. If not that, I'm not sure what to do.. I know it's not permanently bricked as all the hardware keys work and nothing happened that would have damaged the touch screen, it just isn't being loaded during boot (my assumption).
 
Thread is old, but problem I'm having isn't listed so I thought I'd add.

After flashing with Byron Bare on my LG Ally 2.2, it boots fine, except I get to the "Welcome to Ally" screen and my touch screen no longer works.

Do you have any idea of how to fix this? I've tried other roms, I've tried a nandroid restore, I've tried stock rom, I've tried taking battery out, push power 5 times to reset, I can get into my recovery mode to launch the roms from my SD, but that's the extent of anything I can do otherwise.

ANY ideas, would be wonderful. It sounds to me like something within' one of the roms (not specifically yours) changed some radio setting or otherwise that I'm unable to change back without the knowledge of how. If not that, I'm not sure what to do.. I know it's not permanently bricked as all the hardware keys work and nothing happened that would have damaged the touch screen, it just isn't being loaded during boot (my assumption).

Does this happen with other ROMs? There's no really good reason I can think of that the touch screen wouldn't be loaded during boot. This sounds like a hardware issue.

If this happens in all ROMs, then the best thing to do, I think, is to use the LG-sanctioned tools to go back to stock, and if things work, work your way back up to rooted 2.2. If not, you've got busted hardware.
 
It does happen with all ROM's, but was working FINE before I flashed it. It does it with Velocity, byron, etc. I've even tried the "I need a volunteer who wants to go back to completely stock" instructions, it goes through to the same screen "Welcome to Ally" but I can't touch the screen, it doesn't respond.

I've tried everything I can think of, but I don't have a clue what steps to take next.
 
It does happen with all ROM's, but was working FINE before I flashed it. It does it with Velocity, byron, etc. I've even tried the "I need a volunteer who wants to go back to completely stock" instructions, it goes through to the same screen "Welcome to Ally" but I can't touch the screen, it doesn't respond.

I've tried everything I can think of, but I don't have a clue what steps to take next.

Sounds like hardware.

I definitely think you should try the LG way rather than that flashed-stock way though.
 
I know I've heard of simple hardware failure before, being in IT this happens frequently, but it happened subsequently after flashing the rom, so I still believe it's fixable.

How do you suggest I go about doing that? I can't get into USB Debugging mode for the computer to see the phone. The only way I can access things is in aloha recovery usb-ms.
 
I know I've heard of simple hardware failure before, being in IT this happens frequently, but it happened subsequently after flashing the rom, so I still believe it's fixable.

How do you suggest I go about doing that? I can't get into USB Debugging mode for the computer to see the phone. The only way I can access things is in aloha recovery usb-ms.

Use the instructions here: http://androidforums.com/ally-all-t...-3-2011-3-40-pm-est-now-easier-than-ever.html to get back to v6 (don't go farther than using KP500-Utils, at first, until you find out of your screen will work in v6).

If it's software, that's essentially the biggest gun you have. If that doesn't work, I have very little hope.
 
But it asks to enable usb debugging as the 3rd step, I cannot do that. I cannot access that menu.

Isn't Byron set to be in that mode automatically? I can't remember now. If not, I feel like one of the other ROMs around here is set that way...

Regardless, give it a shot anyway. If that doesn't work, try starting it from recovery. If that still doesn't work, try flashing different ROMs to find one pre-set that way.
 
Velocity is supposed to be, but it isn't. I've tried all the roms available for Ally and none of them do it. They all flash fine and boot fine, and get to that screen and I'm done I can't go any further.

I'll keep that link on hand.

Would I be better off if I could flash the STOCK recovery? Would I have more options? or is the aloha recovery going to do better off for me right now. That's about the only thing I haven't tried, currently I'm restoring a v6 stock nandroid, in hopes that'll work. Likely won't. Nope. Goes through a boot loop, hits the Verizon logo, flashes a blue light and reboots and repeats til I pluck battery.

Damn it, this is getting frustrating. As easy as everyone else made flashing sound, I feel like a complete imbecile.
 
Velocity is supposed to be, but it isn't. I've tried all the roms available for Ally and none of them do it. They all flash fine and boot fine, and get to that screen and I'm done I can't go any further.

I'll keep that link on hand.

Would I be better off if I could flash the STOCK recovery? Would I have more options? or is the aloha recovery going to do better off for me right now. That's about the only thing I haven't tried, currently I'm restoring a v6 stock nandroid, in hopes that'll work. Likely won't. Nope. Goes through a boot loop, hits the Verizon logo, flashes a blue light and reboots and repeats til I pluck battery.

Damn it, this is getting frustrating. As easy as everyone else made flashing sound, I feel like a complete imbecile.

The stock recovery has *no* options. You can't do anything other than flash a signed ROM from LG if it's in the predefined place with the predefined name. No menus, no nothing.
 
Alright.

Well, I think I'm out of options, I decided to use the stock recovery flash before I read your reply, now it won't even boot to anything but boot loop. When I try to boot to recovery it brings up the Android and the Package installing icon, then reboots. So that failed as well.

Off to Verizon to get a replacement.

Sorry to bother you.
 
Back
Top Bottom