Hi guys,
I got real damn headache since my GNex updated to 4.2, the Wifi tethering wipe out.
My PS Vita Couldn't connect it again over a year and no one could help me.
Now I wanna update to 4.3, but I need face this problem to let my Nexus work with correct WiFi.
I got 4.1.1 WiFi binaries from official, but what is the next step to overwrite it to 4.3 WiFi component?
I have try Google it, but I'm NOOB so much and no idea how to deal it...
Anyone could help me?
Thanks
There used to be a couple flashable zips floating around here (in kernel threads I believe...maybe tiny kernel) that will do what you seek.
Or just find those files in the system and overwrite them(take note of their permissions first so you can set them after overwriting the files)
Related
Hello Folks
Until few weeks back my bluetooth was working fine. Since OTA update from google, my bluetooth does not work
The issue is that I cannot even slide the Bluetooth radio button to the right to turn it on. It keeps popping back to off.
Please advice
Regards
Replying to this to bring it on top. I have same issue with my phone.
Thanks Appreciate it. Still havent been able to fig it out
Regards
I had the same issue. I'm not sure if it happened with 4.2 or 4.2.1, but i know bluetooth worked fine on 4.1.2. My solution was this: First backup anything you might hate to lose, then download the stock factory image from google developers, unzip twice i believe until you can find the system.img. Move it to where fastboot is in your path, and reflash the system image : in my case, "./fastboot flash system system.img". YOU WILL LOSE ROOT, EVEN IF YOU HAVE OTA ROOTKEEPER! All in all, with an unlocked bootloader, it was easy enough to re-gain root and re-apply system mods. Worth it to be able to play with / learn some bluetooth capabilities. I just couldnt believe my ota broke bluetooth, and again this should work for you if you can compromise and weigh your options.
I have the same problem with my Nexus 7 and GNex. The 4.2 update sucks. Breaks more that it adds to JB.
Sent from my Nexus 7 using Tapatalk 2
bodh said:
I had the same issue. I'm not sure if it happened with 4.2 or 4.2.1, but i know bluetooth worked fine on 4.1.2. My solution was this: First backup anything you might hate to lose, then download the stock factory image from google developers, unzip twice i believe until you can find the system.img. Move it to where fastboot is in your path, and reflash the system image : in my case, "./fastboot flash system system.img". YOU WILL LOSE ROOT, EVEN IF YOU HAVE OTA ROOTKEEPER! All in all, with an unlocked bootloader, it was easy enough to re-gain root and re-apply system mods. Worth it to be able to play with / learn some bluetooth capabilities. I just couldnt believe my ota broke bluetooth, and again this should work for you if you can compromise and weigh your options.
Click to expand...
Click to collapse
Thanks for the feedback. Wondering if you would be willing to share step by step instructions since I am new bee and the information would also be helpful to others.
Regards
I can confirm the same problem with stock after accepting the latest OTA update, only a reboot fixes it. Going back to Xylon.
New Bluetooth Stack
I've had nothing but problems since updating to OTA 4.2.1 Android....Actually it started with OTA 4.2 update. I see that Android changed the Bluetooth stack starting with 4.2....
New Bluetooth stack: Android 4.2 introduces a new Bluetooth stack optimized for use with Android devices. The new Bluetooth stack developed in collaboration between Google and Broadcom replaces the stack based on BlueZ and provides improved compatibility and reliability.
Click to expand...
Click to collapse
from the developers description of JB 4.2.
I decided to downgrade back to 4.1.2 until this gets straightened out.....
==
Michael
Step by Step
Roism said:
Thanks for the feedback. Wondering if you would be willing to share step by step instructions since I am new bee and the information would also be helpful to others.
Regards
Click to expand...
Click to collapse
Efrant did all the work: http://forum.xda-developers.com/showthread.php?t=1812959
then http://forum.xda-developers.com/showthread.php?t=1626895
In the second thread, what you're looking for are steps B,C,D STEP 9...
This will all depend on what you're running on, and how willing you are to get involved.
I highly suggest that if you do not know what you are doing, KEEP READING! There are troves of excellent information on xda to help you, you just have to do the work.
Thanks All for the help. I reverted it back to stock and got the blue tooth working.
Mod's issue resolved, please close thread
Regards
I have been using PDAnet for a couple of years now and never had a problem with the USB tether until I got an update a week or so ago and now it just gets stuck on "connecting to your phone....". I have been emailing the website for PDAnet and they seem to think the update screwed up a driver or something so I reinstalled everything on the phone and PC including the phone drivers. I preferr stock since I am too lazy and too old to keep up with the speed at which changes come so has anyone else had this problem? If so is there a fix? If theres no fix how hard is it to roll back this last update?
Tethering is important to me so all options are on the table even if I have to get back into rooting (though I preferr not to since you guys would get sick of my dumb questions).
Now this has me bothered. Ive never posted a question in here that didn't get some kind of assistance. That would ordinarily make me think my problem was unique except for I have found others with the same issue posting in the PDAnet and PDAnet plus feedback on the Play store.
I'll take any attempt at something I haven't tried from one of you smarter folks. I did a factory reset and it did nothing to help the problem.
Then complain to PDAnet as they probably need to update their app to work with 4.2.2
I have and they are being quite useless. I've just always had good luck here on XDA. Oh well maybe it isnt meant to be.
On another note does anyone have any suggestions on another app to try for tethering without root?
It's not hard to roll back, except that you'll have to unlock the device's bootloader, which wipes its data. Also, you'll have to find a factory image of 4.2.1 for your device, unless you roll back to 4.1.2, then get an update to 4.2.1 and figure out how to disable it for the 4.2.2 update. http://forum.xda-developers.com/showthread.php?t=1626895
When new versions of Android are released its normal for apps to require an update to work properly.
Koush has that no root usb tethering app. Can't remember the name, search the play store fore more apps from the Rom Manager dev and you will see it. Never used it but that's the one I know of.
Just about any custom firmware will have any tethering block or tracker disabled so you can just tether natively with a ROM.
Solved with jTether (root needed).
(This was the most related section to my phone, if I'm wrong please move it and don't delete it. I really need help! lol.)
K I rooted last night, flashed CM7.2
Phone: LG Thrill 4G AT&T flashed to CyanogenMod 7.2
Before you guys tell me to use the search, I have! I've been working on this for 11 hours straight now cause I can't use my phone!
1st Problem: After flashing I had no service. (Yes I used search.) Tried adding APN manually, no luck with many different methods. All the other methods possible required file transfers, which leads me to my 2nd problem.
2nd Problem: My computer will not recognize my phone to transfer files. It will charge however. I tried uninstalling drivers and reinstalling them, etc.
BUT right now I have it open! Yes! Now I just want to know the best files and things to do right now before it won't let me transfer files again. I do not know why it is suddenly reading it so I'm counting on it not being able to after I try fixing everything.
If I flash to a new ROM will I get service back? Should I just go back to stock/unroot? I'd prefer to keep it rooted if I can get my service and everything working.
Thank you guys! I know a lot of these question have been answered and I tried finding them, I really did. But I'm so close now that I can actually transfer files and I just need help! Thank you. I appreciate it.
And by the way I can't just backup because when I flashed to CM7 my original backup got deleted, or just hidden deep away somewhere??
v3 Steezyy said:
(This was the most related section to my phone, if I'm wrong please move it and don't delete it. I really need help! lol.)
K I rooted last night, flashed CM7.2
Phone: LG Thrill 4G AT&T flashed to CyanogenMod 7.2
Before you guys tell me to use the search, I have! I've been working on this for 11 hours straight now cause I can't use my phone!
1st Problem: After flashing I had no service. (Yes I used search.) Tried adding APN manually, no luck with many different methods. All the other methods possible required file transfers, which leads me to my 2nd problem.
2nd Problem: My computer will not recognize my phone to transfer files. It will charge however. I tried uninstalling drivers and reinstalling them, etc.
BUT right now I have it open! Yes! Now I just want to know the best files and things to do right now before it won't let me transfer files again. I do not know why it is suddenly reading it so I'm counting on it not being able to after I try fixing everything.
If I flash to a new ROM will I get service back? Should I just go back to stock/unroot? I'd prefer to keep it rooted if I can get my service and everything working.
Thank you guys! I know a lot of these question have been answered and I tried finding them, I really did. But I'm so close now that I can actually transfer files and I just need help! Thank you. I appreciate it.
And by the way I can't just backup because when I flashed to CM7 my original backup got deleted, or just hidden deep away somewhere??
Click to expand...
Click to collapse
This forum is for the LG Optimus G. You'll probably get some help if you post it in the LG thrill forum.
Hey guys, I know I'm a little late in getting into the whole world of tweaking this guy and development has promptly stopped awhile ago. But here's what's up... I've gone into the general s6 edge plus thread on XDA and downloaded the pixel ROM, and this ROM is absolutely amazing (but data doesn't work, 4glte or call) I've figured if I can extract the modem from any nougat built for the T-Mobile version I can just install it and have data working for this ROM. Oh and btw this ROM was apparently for the g928c so that probably explains a few things. Okay so I've actually had a chance to extract the modem.bin from a nougat build for T-Mobile but I'm having the up most difficulty in implementation. I can't seem to Odin install as Odin stays checking the file and never installs. Right now I'm out of ideas and it doesn't help windows botched the ease of using ADB in favour of windows powershell. Everything doesn't seem to work any more like it used to... Sideloading... Flashing doesn't seem to work... I'm getting off topic but if you guys have any input feel free to reply to this thread or hmu on my Instagram Anthony_vibez
- Thanks
Hi guys n Gals How you all doing? Staying safe i hope!! Im posting this incase it is of any use to anyone who happens to stumble upon an old tablet as i did, But is absolutely bamboozled with what to do next.
Well then i had been looking for help on this issue with regard to Kindle Jem and done my fair share of reading before signing up here.
I am right out of the wrapper and wet behind the ears with Kindles and the like(1st time rooting anything at all) however i managed to install TWRP 2.8.6.0 on su rooted kindle using the bin4ry method.
I followed step by step a tutorial on Youtube named " KindleFireHD89 to pure android"
1. At first i was getting read/load errors:
when attempting to flash cm10.1 cm11/12 through adb sideload i was getting the error message "unable to read cm 11/12" or "unable to load cm11/12" each time i try to flash the rom.
So I done some research on XDA and found a thread to do with the \LARGEADDRESS issue , so downloaded the program to use more than 2GB ram for the flash process, all to no avail. (THIS WAS ABSOLUTELY NO USE AT ALL)
I soon figured i was copying and pasting the commands for flash/fastboot wrong ( i was forgetting to add .img to the name of the image files i was pasting into the command prompt to flash lol)
2. I done a bit of reading around and saw that most , if not all the files were severely obsolete (like the Jem) so i searched around and first upgraded to TWRP 3.0.0.2 from 2.8.6.0 which i feel made a big difference if not just for a smoother gui alone.
3. As my determination and curiosity got the better of me i began replacing the roms also , flashing newer ones each time in this order:
cm 10.1 (success)
cm 11(success)
cm 12.1 (success)
And finally onto Lineage OS 14.1 along with GApps 7.1 Pico where i remain , however i am unable to fix the bluetooth issue as i dont know the commands/ paths or method to alter the LTE file replacement. (any help with this would be great guys or girls (i know Ladye made a fix i think) i just dont know how to go about editing these files.
I got into the menu brand new , though weirdly it wasnt by the volume up button, it was by turning on/off about 5 times and then holding the POWER button in and finally the TWRP Recovery screen would popup.
### edited### i know this is an old kiindle hence why there is no replies .....
####23rd May 2020 EDITED YET AGAIN ##### So i wondered whether there was a recent newish kinda Rom for the JEM after managing to flash (with great difficulty and beginners syndrome) custom rom in TWRP 3.0.0.2.
As i said earlier this was a kindle that was found and when i got it in out the rain and dried off with the hairdrier treatment , was amazed it still worked. So i figured it was a tough mofo and deserved to live outwith the bin since he made it this far.
Anyway when i checked it out the firehd 8.9 was blacklisted ((((Which i am assuming will mean i at least dont need to worry about disabling OTA updates??????))))
So bottom line and after all the fuss above trying to root etc i got 14.1 lineage os without the bluetooth but ill figure that out soon.
For anyone out there this post may help if you can be bothered to read through it haha.
###Last but not least I would like to thank all the guys n gals who make these mods possible and xda themselves for not binning these old posts for noobs like myself . Respect people . thanks again man ###