Root [ROM][BETA][4.1.2]"L" Awe V2.5 Final[Works with stock device]

tb2017 · Nov 6, 2014

I am using TWRP 2.8.0 and 2.7.1 tried both of those and I got the same error..

JHell · Nov 6, 2014

tb2017 said:
Now the error i keep getting is Error updating binary scripts /sdcard/L_Awe...

did u download over ur network or wifi? its best to download over wifi

DsyMnapTic · Nov 6, 2014

tb2017 said:
Now the error i keep getting is Error updating binary scripts /sdcard/L_Awe...

I'm trying to remember what produced that.... Umm, what Rom were you coming from prior to trying to flash "L" awe? The first thing I can recommend is restoring a backup if you have one. Then boot back into recovery and manually(advance) wipe cache, dalvik, data and system. (obviously don't touch internal and external storage). Try to flash again, then tell me what it says.

tb2017 · Nov 6, 2014

DsyMnapTic said:
I'm trying to remember what produced that.... Umm, what Rom were you coming from prior to trying to flash "L" awe? The first thing I can recommend is restoring a backup if you have one. Then boot back into recovery and manually(advance) wipe cache, dalvik, data and system. (obviously don't touch internal and external storage). Try to flash again, then tell me what it says.

I was coming from the PacMan Rom. I dont have a backup. I tried formatting cache,dalvik, data, system, and i even tried internal. nothing changed

tb2017 · Nov 6, 2014

JHell said:
did u download over ur network or wifi? its best to download over wifi

I downloaded it on a PC and dragged and dropped onto my phone

roadkill42 · Nov 6, 2014

tb2017 said:
I downloaded it on a PC and dragged and dropped onto my phone

flash cwm then rebot recovery then reflash twrp that's what I did when this happened to me then format data several times also pull bat and power cord in plunged then put bat back and try that

tb2017 · Nov 6, 2014

roadkill42 said:
flash cwm then rebot recovery then reflash twrp that's what I did when this happened to me then format data several times

I don't have a cwm recovery but i have Phil'z.. Would that work?

roadkill42 · Nov 6, 2014

try it nothing to loose. make sure to format data when u get twarp re flashed

tb2017 · Nov 6, 2014

roadkill42 said:
try it nothing to loose. make sure to format data when u get twarp re flashed

Thanks!! IT WORKED! You're a life saver man

DsyMnapTic · Nov 6, 2014

tb2017 said:
Thanks!! IT WORKED! You're a life saver man

Awww damn, he got to you first... That would've been my next recommendation. Anyhow glad someone could help you and that you figured it out

roadkill42 · Nov 7, 2014

tb2017 said:
Thanks!! IT WORKED! You're a life saver man

ur welcome

horseflesh · Nov 13, 2014

hoosierbunny said:
I'm loving this rom so far, but I accidentally launched the tether before configuring the settings on my Awe. I've got them configured as in the op, but VM yanks control of the connection and the hotspot shuts down.

Should I just reflash the Wifi Tether-Treve Mod app, config the settings and try again?

Thoughts?

I've been wrestling with tethering for a bit now and came by today to post my findings, which I think may help you.

I used Wifi Tether on my AWE for a year on the stock ROM so I thought I knew all the ins and outs, but I still learned some things when trying to get tethering working on the Awe "L" ROM.

First, you should not have to re-install the wifi tether app. Simply changing the settings will be enough--though you may need to reboot the phone too, the app doesn't always seem to cleanly shut down between tethering sessions.

I found that my AWE also yanked wifi control back, especially when the screen went to sleep. To fix this I had to check the first "restart wifi driver" box in tethering setup.

Now things get a little weird. Right after I installed "L" I set up Wifi Tether and used it successfully for a day. The next day, things weren't working right. My devices would connect to the hot spot, but had no Internet access. (In Windows terms, the connection was "Limited." I was unable to even ping an IP address.)

I had made no changes besides installing some apps on my phone, stuff that should have been totally benign.

In the end what worked for me was turning on Access Control. Here's one mistake I made along the way, though... If Access Control is turned on, you need to go into the device list and hit the checkbox for an device to authorize it.

This seems pretty common sense, but on the stock AWE ROM with the most recent Wifi Tether beta, Access Control didn't work that way. I had it on for a year, never explicitly authorized any device, and it worked fine! I just ignored Access Control. So, I overlooked the darn check boxes on the TrevE version in this L ROM. Once I authorized the devices, rebooted the phone, and restarted the hot spot, things started to work.

I do not think that Access Control was my only problem because in the course of my experiments, I tried running with it turned off--many times. I think the app is still just kind of flaky. But at the end of the day, on "L," properly using Access Control fixed my connection problems... At least for today!

JHell · Nov 16, 2014

horseflesh said:
I've been wrestling with tethering for a bit now and came by today to post my findings, which I think may help you.

I used Wifi Tether on my AWE for a year on the stock ROM so I thought I knew all the ins and outs, but I still learned some things when trying to get tethering working on the Awe "L" ROM.

First, you should not have to re-install the wifi tether app. Simply changing the settings will be enough--though you may need to reboot the phone too, the app doesn't always seem to cleanly shut down between tethering sessions.

I found that my AWE also yanked wifi control back, especially when the screen went to sleep. To fix this I had to check the first "restart wifi driver" box in tethering setup.

Now things get a little weird. Right after I installed "L" I set up Wifi Tether and used it successfully for a day. The next day, things weren't working right. My devices would connect to the hot spot, but had no Internet access. (In Windows terms, the connection was "Limited." I was unable to even ping an IP address.)

I had made no changes besides installing some apps on my phone, stuff that should have been totally benign.

In the end what worked for me was turning on Access Control. Here's one mistake I made along the way, though... If Access Control is turned on, you need to go into the device list and hit the checkbox for an device to authorize it.

This seems pretty common sense, but on the stock AWE ROM with the most recent Wifi Tether beta, Access Control didn't work that way. I had it on for a year, never explicitly authorized any device, and it worked fine! I just ignored Access Control. So, I overlooked the darn check boxes on the TrevE version in this L ROM. Once I authorized the devices, rebooted the phone, and restarted the hot spot, things started to work.

I do not think that Access Control was my only problem because in the course of my experiments, I tried running with it turned off--many times. I think the app is still just kind of flaky. But at the end of the day, on "L," properly using Access Control fixed my connection problems... At least for today!

ive had a similar problem with the wifi tether too. access control is one thing ive never used. i just set up a password. my problem was with the wifi driver reload. i always use wifi driver reload not the second one. whenever u turn of the tethering just make sure u restart ur phone before u use it again

JHell · Nov 16, 2014

Just want to give a BIG THANKS to brittnearl and starkraving for this ROM. this has been my daily driver since u guys built it. between the wifi driver and the fact that i can use the FM radio and the UI im pretty well set

DaRkSkYxP · Nov 16, 2014

I don't tether because I don't have my phone activated with anyone but at my work I have 3 routers properly configured for WiFi roaming that works on other devices here but seem to have a problem with this phone a lot so I have solved the problem by using WiFi fixer from the app store. It properly reconnects to the closest access point on it's own when it's signal is stronger. I know it's irrelevant to tethering but just thought I would point it out in case someone else has similar problems.

starkraving · Nov 18, 2014

Anybody wanting to use Inbox but haven't gotten an invite? I have one golden ticket left first pm with your gmail gets it.

JHell · Nov 18, 2014

starkraving said:
Anybody wanting to use Inbox but haven't gotten an invite? I have one golden ticket left first pm with your gmail gets it.

whats inbox?

starkraving · Nov 18, 2014

JHell said:
whats inbox?

Inbox is a new gmail extension with groupings, snooze notifications, attachment previews and a lot more.

JHell · Nov 18, 2014

starkraving said:
Inbox is a new gmail extension with groupings, snooze notifications, attachment previews and a lot more.

ohhhh..... ok

horseflesh · Nov 18, 2014

I just noticed that with this ROM I am getting poor GPS performance. Can't get a lock at all, in fact. Any ideas?

JHell · Nov 18, 2014

horseflesh said:
I just noticed that with this ROM I am getting poor GPS performance. Can't get a lock at all, in fact. Any ideas?

can u get a log cat?

horseflesh · Nov 18, 2014

I just installed catlog, what should I save? There are a load of GPS entries.

Something is definitely screwy. I have a Nexus 7 beside my AWE and it locks on as expected. The AWE has been rebooted a half dozen times with no change.

GPS Status app shows no locks at all... Well now it just got one.

EDIT: I eventually got it to work. I uninstalled GPS Status and tried GPS Test, a similar app that had been recommended in another thread. In both apps I tried downloading fresh AGPS data. Both apps showed that the phone saw satellites but it was having a hell of a time syncing with them. Under GPS Test, I did get a fix within a few minutes. Thereafter, I got a fix very quickly, as expected.

Maybe the problem was that I did not wait long enough... A cold start takes a while, and I had just updated the ROM. But that doesn't make sense because the day before this post, I used the GPS w/ the L ROM. It took a couple of minutes to lock, but it did work... so I wasn't really running from a cold start at all when I had this problem.

Bottom line, it is working fine now and I don't understand why.

If this happens again, I will grab GPS logs.

horseflesh · Nov 26, 2014

Today's dumb question--how can I customize the apps on the unlock screen? For example, I want to change Hangouts to something else.

horseflesh · Nov 26, 2014

Oops, dupe post.

DaRkSkYxP · Nov 26, 2014

horseflesh said:
Today's dumb question--how can I customize the apps on the unlock screen? For example, I want to change Hangouts to something else.

I believe brittnearl said that they are hard coded so you can't. I remember uninstalling hangouts and when I would accidentally slide to it from the lock screen it would put me into a soft reboot. Really sucked lol. There may be another lock screen program in the play store that has that feature and will let you set them up. I know some of the kitkat ROMs have that feature built in.

Root [ROM][BETA][4.1.2]"L" Awe V2.5 Final[Works with stock device]

Member

Android Enthusiast

Android Expert

Member

Member

Android Expert

Member

Android Expert

Member

Android Expert

Android Expert

Newbie

Android Enthusiast

Android Enthusiast

Android Enthusiast

Android Expert

Android Enthusiast

Android Expert

Android Enthusiast

Newbie

Android Enthusiast

Newbie

Newbie

Newbie

Android Enthusiast

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads