I just tweaked the recent ota to just patch the radio since I don't want to change the rom I'm on, but I did want the radio. Since we don't have the full rom to get the radio.img from this is the next best thing.
*****THIS IS FOR THE 9020T*****
Flash with CWR
KD1 -> KF1 Patch
http://www.mediafire.com/?k0gdlbf423540m3
KF1 pulled from the full OTA update.zip
http://www.mediafire.com/?phxp9xnerhdr0ob
So do I just flash this zip file on CWM for i9020T?
What do you think about KF1? I have bad signal in my area so I was wondering if KF1 would improve my situation. Thanks!
droidance said:
So do I just flash this zip file on CWM for i9020T?
What do you think about KF1? I have bad signal in my area so I was wondering if KF1 would improve my situation. Thanks!
Click to expand...
Click to collapse
just flash in clockwork. can't judge the signal quality just yet. just flashed 30 minutes ago
would it work on 9023?
Thanks for providing the zip. Tried flashing this in clockwork and it came back bad and aborted. Anything I'm doing wrong?
Sent from my Nexus S using XDA App
rob77 said:
Thanks for providing the zip. Tried flashing this in clockwork and it came back bad and aborted. Anything I'm doing wrong?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Redownloading will probably do it. It's likely that the file is not completely downloaded. I was able to flash via CWM successfully.
jungbum said:
Redownloading will probably do it. It's likely that the file is not completely downloaded. I was able to flash via CWM successfully.
Click to expand...
Click to collapse
Thanks ill try on my computer when I get home. My phone isn't allowing me to download it again for some reason
Sent from my Nexus S using XDA App
rob77 said:
Thanks for providing the zip. Tried flashing this in clockwork and it came back bad and aborted. Anything I'm doing wrong?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I was lazy and didn't sign the zip. Make sure to toggle signature verification to off.
Sent from my Google Nexus S using Tapatalk
I am on kd3 (Tweaked and getting HSPA) with nightly 206 + voodoo patch. No problem with this combinations yet, any improvement with this radio? Thanks
Sent from my Nexus S using XDA Premium App
It updated mine just fine. thanks!
what does this do exactly? Possibly improve your connection? Will it work on CM7.1?
So far nothing amazing but nothing bad as well. Really nothing really happened to where I live (Canada) signal wise. I can't comment on speeds yet. I'll try it later tormorrow
lvnatic said:
would it work on 9023?
Click to expand...
Click to collapse
s works well on i9023
Two things here:
One, let's hope this increases stability!
Two, I'm creating a full radio image file, I will be uploading it to my website, and posting it in a new thread. Keep your eyes open for it!
unforgiven512 said:
Two things here:
One, let's hope this increases stability!
Two, I'm creating a full radio image file, I will be uploading it to my website, and posting it in a new thread. Keep your eyes open for it!
Click to expand...
Click to collapse
Look here.
I've noticed it seems to hold on to a HSPA signal better than KD1. With KD1 mine would always revert back to 3g but now it is showing a H most of the time.
you right, much more better signal stability with new radio...
I will say it did break wifi tether on mine with miui 1.99.23. I am sure I can just push the updated ril files and fix if I wasn't so lazy
Sent from my Google Nexus S using Tapatalk
Thanks
Thanks
Its switching from 3G to WIFI faster than KD1
I just tried to use the update pulled from the OTA and it aborted both times. The patch seemed to work.
Related
Hey guys, I see some of you are bricking or not being able to update.
You can use this to flash to I897UCJH7 OTA.
Use Clockwork recovery to flash it...
Cognition is currently being rebuilt on top of this, deodexed and all that fun stuff.
This flashes the system folder, kernel, and modem.
Download:
http://www.ponack.net/designgears/JH7_OTA.zip
Let me know how the GPS works for you guys!! I have gotten it to lock in my basement!!
Could you tell us what differences are in this and the JH7 we've had for a while? I assume the GPS is supposed to work better but anything aside from that?
Sent from my Samsung Captivate using Tapatalk Pro (No FC on posts like the official XDA app!)
Cheers! Thanks DG!
bts0uth said:
Could you tell us what differences are in this and the JH7 we've had for a while? I assume the GPS is supposed to work better but anything aside from that?
Sent from my Samsung Captivate using Tapatalk Pro (No FC on posts like the official XDA app!)
Click to expand...
Click to collapse
not sure of all the changes, but lots of files had different checksums..
Thanks for this dg.
Sent from my Samsung Captivate w/Voodoo using Tapatalk
Damn looks like I'm flashing for like the billionth time today.
designgears said:
not sure of all the changes, but lots of files had different checksums..
Click to expand...
Click to collapse
Awesome. Hopefully it will make Cog even better than it already is. Can't wait to try out the gps
Sent from my Samsung Captivate using Tapatalk Pro (No FC on posts like the official XDA app!)
Test.
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks DG! I've been looking for this.
Thanks so much for this!
Quick question though... if my phone already says it is at JH7 even after a 100% OTA update and had the Update Failed message, could I still flash this with Clockwork and have it function properly?
UberGoat said:
Thanks so much for this!
Quick question though... if my phone already says it is at JH7 even after a 100% OTA update and had the Update Failed message, could I still flash this with Clockwork and have it function properly?
Click to expand...
Click to collapse
sure can!!!
Tested and it works! thanks!
If I do encounter problem, I'll let you know.
Should I wipe data and clear cache prior to doing this? What are the implications of wiping my previous rom.
I am getting installation aborted from Recovery Mode. Any suggesstions?
WTF!!!!!!
do i need to uninstall lag fix first?
i forgot to uninstall lag fix. and flash this file.
now after the startup ATT and samsung logo, i just got a black/blank screen!
what do i do now?? how do i uninstall lag fix when i only getting a black/blank screen???
netnerd said:
WTF!!!!!!
do i need to uninstall lag fix first?
i forgot to uninstall lag fix. and flash this file.
now after the startup ATT and samsung logo, i just got a black/blank screen!
what do i do now?? how do i uninstall lag fix when i only getting a black/blank screen???
Click to expand...
Click to collapse
Mmm I'm not sure but... mine was stock ( did odin ) before I flashed this.
if a battery pull doesnt get it to work, then I would reflash JF6 with Odin, flash this JH7 OTA with Rom manager.
Im about to try to disable lag fix first, then flash and if it bricks it then ill flash to stock JF6 first.
Thank you DG. I needed the update because for some reason the one click installer thing wouldn't allow OTA updates. But your one click installer is still a huge help when needed.
First, breath, you are not bricked yet. Search in here for odin one click. Follow the instructions. You will most likely need to do method 3 for your download mode. (remove battery, sim, sdcard /replace battery /hil vol+ and vol- while simultaniouslyplugging in the usb cable) Once you get flashed back to stock you can try again.
Sigh after so many tries to update I went back to cognition with leaked jh7. Guess I'll be flashing again once I get off work tomorrow.
Sent from my SAMSUNG-SGH-I897 using XDA App
Stephenv1971 said:
First, breath, you are not bricked yet. Search in here for odin one click. Follow the instructions. You will most likely need to do method 3 for your download mode. (remove battery, sim, sdcard /replace battery /hil vol+ and vol- while simultaniouslyplugging in the usb cable) Once you get flashed back to stock you can try again.
Click to expand...
Click to collapse
thanks Stephenv1971 !
i almost have a heart attack! haha
just flashed back to stock rom using Odin 1 click!
I think Samsung / Verizon are definitely going to have the OTA ICS update released sometime before the end of the year I hope.
Maybe
Anyone out there with real info? ¿
Sent from my SCH-I815 using xda app-developers app
A question mark in the title would be have prevented you from cruelly getting my hopes up!
good point
tr2ride said:
I think.. definitely.. I hope.. Maybe
Click to expand...
Click to collapse
You seem confident. I'll say it's here by Q3 end; JB we shouldn't hold our breath for (officially).
I would actually be content with a custom rom based on the 3g Ics upgrade with no working 4g for the time being as I could just tether anyways
Sent from my SCH-I815 using xda premium
Any news on Verizon devices update on ICS?
A comment a few days ago from Verizon customer service stated they didn't even have a timeframe yet...
https://community.verizonwireless.com/thread/776946
Never again, Verizon!
Gilbot said:
I would actually be content with a custom rom based on the 3g Ics upgrade with no working 4g for the time being as I could just tether anyways
Sent from my SCH-I815 using xda premium
Click to expand...
Click to collapse
There's a CM9 for the i815 in the Android development thread that has everything working but 4G and auto brightness, according to the developer. I'm going to install this weekend, but it seems to be the real deal at this point.
It's also currently missing HDMI, which is unfortunate...but I agree that it could easily be a daily driver in another month or so.
Rodney
esoh said:
There's a CM9 for the i815 in the Android development thread that has everything working but 4G and auto brightness, according to the developer. I'm going to install this weekend, but it seems to be the real deal at this point.
Click to expand...
Click to collapse
I have installed the CM9 today and it works great!
:good:
esoh said:
There's a CM9 for the i815 in the Android development thread that has everything working but 4G and auto brightness, according to the developer. I'm going to install this weekend, but it seems to be the real deal at this point.
Click to expand...
Click to collapse
Yup. I'm rocking CM9 as my daily driver. Love it !
Sent from my SCH-I815 using xda premium
Gilbot said:
Yup. I'm rocking CM9 as my daily driver. Love it !
Sent from my SCH-I815 using xda premium
Click to expand...
Click to collapse
This is great news, sure I'd love 4g to be working too but I typically have at least 2 networks I can tether on in addition to Verizon so ready to take the plunge.
Which version of CWM are you running and how did you install it? Odin or heimdall? I downloaded what I thought was the proper CWM but have had trouble installing.
tr2ride said:
This is great news, sure I'd love 4g to be working too but I typically have at least 2 networks I can tether on in addition to Verizon so ready to take the plunge.
Which version of CWM are you running and how did you install it? Odin or heimdall? I downloaded what I thought was the proper CWM but have had trouble installing.
Click to expand...
Click to collapse
CWM 5.5.0.4 recovery from locerra, flashed via Odin.
Do yourself a favor before flashing the recovery via odin if you're rooted and follow these instructions, or else the stock recovery will override your CWM recovery every boot:
ODIN flashable CWM 5.5.0.4 TAR file: http://goo.im/devs/ohanar/clockworkmod/i815/CWM-20120710-i815.tar
Installation Instructions for stock FD01 users with stock 3e recovery:
Gain root access if you don't already have it.
Disable any lockscreen security you have.
While in the Stock ROM after enabling root access, navigate to the /system folder with a root-enabled file explorer app and mount R/W.
Locate the file "recovery-from.boot.p" and rename it to "recovery-from.boot.p.bak" then power down your tab, Do Not reboot or let the tab boot into your stock rom!
Boot into download mode by pressing and holding power + volume down
Press Volume up to continue into download mode and connect your tab to your pc
Load up ODIN and flash the 5.5.4.0 tar file via PDA
Reboot, you should now have persistent CWM 5.5.0.4
Did my nandroid fail?
What is the size of your nandroid backups?
I'm concerned mine is too small to be correct.
When I backed up there were no errors but still seems small.
The entire backup directory in clockworkmod/backups/<backupname> is only 21.5 MB
tr2ride said:
What is the size of your nandroid backups?
I'm concerned mine is too small to be correct.
When I backed up there were no errors but still seems small.
The entire backup directory in clockworkmod/backups/<backupname> is only 21.5 MB
Click to expand...
Click to collapse
Here's a pic of my backup directory, it looks like data and system are jacked
Are there any other mechanisms for backup other than nandroid? since its impossible to revert the i815 without a backup I'm being extra paranoid
thanks
tr2ride said:
Here's a pic of my backup directory, it looks like data and system are jacked
Are there any other mechanisms for backup other than nandroid? since its impossible to revert the i815 without a backup I'm being extra paranoid
thanks
Click to expand...
Click to collapse
That's wayy too small of a nandroid. I have two over 1gb and one thats over 350m. Which version of CWM did you install?
Is this ever going to happen? Anyone hear anything from VZ?
tr2ride said:
Is this ever going to happen? Anyone hear anything from VZ?
Click to expand...
Click to collapse
The silence from Verizon is deafening. If CM10 had 4G support I'd be running it but since I use my 4G a lot I'm stuck running honeycomb.
mgleed said:
The silence from Verizon is deafening. If CM10 had 4G support I'd be running it but since I use my 4G a lot I'm stuck running honeycomb.
Click to expand...
Click to collapse
Same here.....sadly
Sent from the Delta Quadrant using XDA Premium
I'm running CM10 and it is very smooth and a huge step up from stock HC. I use mine solely on Wi-Fi so it having 4G issues is not a problem for me. VZW's attitude toward customers and their painfully slow updating process is what drove me away from them. I will never go back to VZW until these attitudes change. I am now a very happy T-Mobile customer with unlimited 4G data. Suck it VZW.
Does anyone know of a stock flashable ROM without Root and Busybox?
I'm aware of the thread guiding people on going back to factory but I don't want to do that. I want to be able to just flash a Rooted ROM if I want one and flash back to standard unrooted if I want using TWRP.
My reason behind this that I spend a lot of time on the train at the minute so decided to get Sky Go. Unfortunately it detects that the device is rooted and won't run.
There are a few threads around the net with scripts and suggestions but nothing seems to work for me.
I don't think there are any..... Hmmm.
Sent from my Nexus 4 using Tapatalk 2
You can flash the stock ROM with fastboot but not from within recovery. Get it here: https://developers.google.com/android/nexus/images
I could make one I suppose, wouldn't take long at all...
EddyOS said:
I could make one I suppose, wouldn't take long at all...
Click to expand...
Click to collapse
If you could do that it would be great.
I was just looking at the tutorial to bake it myself but having issues with Cygwin. Much quicker and easier if you did it.
Owe you one.
I use Linux so it won't take long. You literally want a flashable stock ROM, no changes whatsoever?
EddyOS said:
I use Linux so it won't take long. You literally want a flashable stock ROM, no changes whatsoever?
Click to expand...
Click to collapse
Exactly. I use a standard stock rooted ROM usually.
Just realised I don't actually use root for anything at the minute but likely will do in the future.
Thanks again.
I'll try and do it this afternoon but if not this evening once back at home
Uploading at the mo, it's literally the stock ROM dumped into the kitchen and cooked out with no change whatsoever
EddyOS said:
Uploading at the mo, it's literally the stock ROM dumped into the kitchen and cooked out with no change whatsoever
Click to expand...
Click to collapse
Excellent. Thanks buddy.
I think I'll play with it too and keep the zip stored just so I have it.
Thanks
Sent from my Nexus 4 using Tapatalk 2
Here you go. I've not tested but it should be fine (let me know if it's not)
https://www.yousendit.com/download/UVJnSU5IQVNiV3dPd3NUQw
Working perfectly so far mate! Sky Go is working and no wipe was required.
Owe you one mate. Top work. Thank you.
Good to hear! You're welcome
EddyOS said:
I could make one I suppose, wouldn't take long at all...
Click to expand...
Click to collapse
Very cool that you've done this, but I should give a word of caution: there are some problems that wiping via fastboot will fix, but installing a flashable stock .zip won't fix. For example, when a 16GB phone thinks it's only 8GB. (I have reason to believe that there are other problems that can only be fixed in this way, but I can't prove it. :silly
That's not something the OP cared about, he just needed to 'unroot' to use a TV app that checks for root access
He should give this app a try
http://forum.xda-developers.com/showthread.php?t=1241517.
Sent from my Nexus 4 using XDA Premium HD app
trapdogg said:
He should give this app a try
http://forum.xda-developers.com/showthread.php?t=1241517.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
It doesn't work - none of the 'root hiding' apps work with Sky Go
trapdogg said:
He should give this app a try
http://forum.xda-developers.com/showthread.php?t=1241517.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
I tried that.
I tried a script that was published on the net to remove root and busybox.
I tried removing root and busybox manually.
I tried flashing stock kernal
I tried several other apps.
A flashable stock rom was my last resort as I was under the impression that I'd need to wipe and I didn't want to do that. I just tried it without wiping on the off chance that it worked and it did, so problem solved.
None of my Apps were using Root so I thought I'd get rid of it completely but wanted the option to flash CM10.1 once Bluetooth MAP profile is fixed and working without having to go through putting TWRP on again.
It's all in the OP and posts following that.
EddyOS saw what I was after and offered to help. He's a great dude.
Just for learning purposes, how come no one has made a flashable stock zip until now? Wouldn't it just be like any custom rom but instead its just stock?
Hi,
This is an odd one.
I get 12mb download speeds on my home wifi if i do a test from my laptop or girlfriends iphone. If I do the test on my Nexus i only get about 1.5mb.
If I reboot the router (Draytek) I get the full 12mb again for a few hours then it drops right back down to 1.5mb.
Now I know you are all thinking straight away its the router but I have recently changed this from a Linksy router to the draytek and had the same problem with that one, so it would appear it is my Nexus.
I am running PA with the latest Kernal for it.
Any ideas or help?
foxguard said:
Hi,
This is an odd one.
I get 12mb download speeds on my home wifi if i do a test from my laptop or girlfriends iphone. If I do the test on my Nexus i only get about 1.5mb.
If I reboot the router (Draytek) I get the full 12mb again for a few hours then it drops right back down to 1.5mb.
Now I know you are all thinking straight away its the router but I have recently changed this from a Linksy router to the draytek and had the same problem with that one, so it would appear it is my Nexus.
I am running PA with the latest Kernal for it.
Any ideas or help?
Click to expand...
Click to collapse
Try changing your Radio. Which Radio you are on? Latest is .98
sidnoit22 said:
Try changing your Radio. Which Radio you are on? Latest is .98
Click to expand...
Click to collapse
Thanks for the reply mate. Im new to this, how do I tell which Radio is installed and how do I update it if needs be?
foxguard said:
Thanks for the reply mate. Im new to this, how do I tell which Radio is installed and how do I update it if needs be?
Click to expand...
Click to collapse
In "About Phone" look for baseband (a.k.a. radio) version. But be careful, if you are using Jelly Bean ROM, your radio should be 0.84. If KitKat ROM, then the radio should be .97 or .98. Don't flash 97 or 98 on Jelly Bean ROM !!!
taodan said:
In "About Phone" look for baseband (a.k.a. radio) version. But be careful, if you are using Jelly Bean ROM, your radio should be 0.84. If KitKat ROM, then the radio should be .97 or .98. Don't flash 97 or 98 on Jelly Bean ROM !!!
Click to expand...
Click to collapse
Thanks for that,
im on PA which is still Jelly Bean isn't it?
But the radio is 0/84, is that what it should be?
foxguard said:
Thanks for that,
im on PA which is still Jelly Bean isn't it?
But the radio is 0/84, is that what it should be?
Click to expand...
Click to collapse
In "About Phone" look for "Android Version" if it's below 4.4 then you are on Jelly Bean (e.g., 4.3 or 4.2). I don't use PA ROM so I don't know which version currently for PA.
taodan said:
In "About Phone" look for "Android Version" if it's below 4.4 then you are on Jelly Bean (e.g., 4.3 or 4.2). I don't use PA ROM so I don't know which version currently for PA.
Click to expand...
Click to collapse
4.3 is the one im on. Cheers
So any ideas on how to fix it?
foxguard said:
4.3 is the one im on. Cheers
So any ideas on how to fix it?
Click to expand...
Click to collapse
Have you tried to wipe cache and dalvik cache in recovery? Also did you test your phone in different area because it depends on where you are compared to the cell signal tower.
taodan said:
Have you tried to wipe cache and dalvik cache in recovery? Also did you test your phone in different area because it depends on where you are compared to the cell signal tower.
Click to expand...
Click to collapse
Have now done this and will see what happens )
Not sure I understand the second part though as im talking about my home wifi and not my 3g coverage.
foxguard said:
Have now done this and will see what happens )
Not sure I understand the second part though as im talking about my home wifi and not my 3g coverage.
Click to expand...
Click to collapse
I found this information on Google's support forum:
I can hereby confirm that flashing back the radio from M9615A-CEFWMAZM-2.0.1700.84 (default for 4.3) to M9615A-CEFWMAZM-2.0.1700.48 (default for 4.2.2), whilst keeping the rest of 4.3, did NOT fix the wifi speed and connectivity problems on my phone.
I then proceeded to downgrade completely to 4.2.2 using the Google-supplied factory images, and I'm now getting 44 Mbit/s down and 5 Mbit/s up via 802.11n, where on 4.3 with either of the two radios, I couldn't even reliably finish the test (it would stop halfway, with the download speed estimated at 7 Mbit/s). Besides that, I've now been able to update tons of apps from Play, where with 4.3 this was not possible with either of the radios.
Just in case someone finds this, the version of Android on this Nexus 4 causing endless wifi problems is:
* Android 4.3
* baseband M9615A-CEFWMAZM-2.0.1700.84
* kernel 3.4.0-perf-gf43c3d9, 2013-06-17
* build number JWR66V
The version working well is:
* Android 4.2.2
* baseband M9615A-CEFWMAZM-2.0.1700.48
* kernel 3.4.0-perf-g7ce11cd, 2013-01-29
* build number JDQ39
You should use a different radio. I'd recommend the hybrid radios 33/84. Uses .33 radio for connections such as WiFi and data, whereas .84 radio is used for calls.
Sent from my Nexus 4 using xda app-developers app
foxguard said:
Hi,
This is an odd one.
I get 12mb download speeds on my home wifi if i do a test from my laptop or girlfriends iphone. If I do the test on my Nexus i only get about 1.5mb.
If I reboot the router (Draytek) I get the full 12mb again for a few hours then it drops right back down to 1.5mb.
Now I know you are all thinking straight away its the router but I have recently changed this from a Linksy router to the draytek and had the same problem with that one, so it would appear it is my Nexus.
I am running PA with the latest Kernal for it.
Any ideas or help?
Click to expand...
Click to collapse
i had the same issue, its not the radio , there is a zip file that you can flash which was ported from an LG phone, and you Wifi will be fine for sure.
Check this link out, i know you will hit thanks after this for sure , lol
http://forum.xda-developers.com/showthread.php?t=2300873
Ajaykumar21066 said:
i had the same issue, its not the radio , there is a zip file that you can flash which was ported from an LG phone, and you Wifi will be fine for sure.
Check this link out, i know you will hit thanks after this for sure , lol
http://forum.xda-developers.com/showthread.php?t=2300873
Click to expand...
Click to collapse
Ok, have done this..... will it work!
Ajaykumar21066 said:
i had the same issue, its not the radio , there is a zip file that you can flash which was ported from an LG phone, and you Wifi will be fine for sure.
Check this link out, i know you will hit thanks after this for sure , lol
http://forum.xda-developers.com/showthread.php?t=2300873
Click to expand...
Click to collapse
Nope didn't work.
CellPhish said:
You should use a different radio. I'd recommend the hybrid radios 33/84. Uses .33 radio for connections such as WiFi and data, whereas .84 radio is used for calls.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Where do I get these from and do I just flash I'm recovery please?
foxguard said:
Where do I get these from and do I just flash I'm recovery please?
Click to expand...
Click to collapse
I am going to give you the best info you're likely going to get as I suffer the same problem.
Don't reset you're rooter switch wifi on and off on the phone as it achieves the same results.
After a while of doing this it will improve the duration it locks on to fast wifi.
Also I think relocking the bootloader helps WHY I haven't a clue.
All I know is I have the same problem with the newest and fastest wifi available in my area and after trying everything flashable, settings in wifi and even patching my wifi from roms with my wifi working the results are.
1 go back to a stock 4.3 rom.
2 try what I suggested.
Sent from my Nexus 4 using XDA Premium 4 mobile app
---------- Post added at 01:21 AM ---------- Previous post was at 01:13 AM ----------
bladebuddy said:
I am going to give you the best info you're likely going to get as I suffer the same problem.
Don't reset you're rooter switch wifi on and off on the phone as it achieves the same results.
After a while of doing this it will improve the duration it locks on to fast wifi.
Also I think relocking the bootloader helps WHY I haven't a clue.
All I know is I have the same problem with the newest and fastest wifi available in my area and after trying everything flashable, settings in wifi and even patching my wifi from roms with my wifi working the results are.
1 go back to a stock 4.3 rom.
2 try what I suggested.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
To add to the above I don't know if its 4g capabilities being added to roms as I have tried everything but thats what I am looking at now even though I have flashed multiple radios.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Just asking, but are you sure you didn't confuse MByte/s with Mbit/s? (Notice the lower and upper case B )
It would make sense as 12Mbit/s are 1.5MByte/s.
Ok guys, just so you know, Radio/Baseband has nothing to do with your WiFi connectivity or the transfers speeds you are getting on WiFi. All WiFi modules, drivers are present in the Kernel and NOT the modem/baseband. Hope this gives you clarity and prevent waste of your time fiddling with the modem to solve WiFi issues!!
prembox said:
Ok guys, just so you know, Radio/Baseband has nothing to do with your WiFi connectivity or the transfers speeds you are getting on WiFi. All WiFi modules, drivers are present in the Kernel and NOT the modem/baseband. Hope this gives you clarity and prevent waste of your time fiddling with the modem to solve WiFi issues!!
Click to expand...
Click to collapse
Flashed enough radio basebands and pulled enough files from the system to know where both live. I am talking about interference something causing the wifi to drop suddenly as if the network is strangled (but its not) there's a few phones that suffer the same problems as I have read all there posts.
It's something causing it to drop turning it on and off helps for a short time in my case about 3mins tops.
It could be anything I just find it a little strange that on a custom rom any soap ,cm and custom stocks this happens but not on a Google image. So something strange is happening who knows. Just wish I did.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Is Nexus 4 getting wireless speed over 2.4mb/s?
This is the maximum that I can see at transferring of files to PC on same network.
I can't have it locked over 54mbps at settings of wireless.
Sent from my NookColor using Tapatalk 4
The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Edit:
To get the OTA to work properly and flash the correct kernal, your CID must be changed to GOOGL001. If you have the GPE device, you don't need to do anything, but if you have a converted GPE then you must change your CID if you want OTA's. This was not made clear in the RUU thread, it was mentioned that changing your CID was optional if you had one of the listed CID's, but it is not optional, but a requirement if you want the OTA's to work.
Everyone that has changed there CID's reflashed the OTA and everything flashed fine, whereas anybody that had not modified there CID had the problem with the kernal.
Psosmith82 said:
The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Click to expand...
Click to collapse
maybe you had a bad download?
HRodMusic said:
maybe you had a bad download?
Click to expand...
Click to collapse
I used the download linked from the discussion thread. Put on phone storage, rebooted into recovery and applied the update from phone storage.
Same results with OTA.
Sent from space.
Psosmith82 said:
I used the download linked from the discussion thread. Put on phone storage, rebooted into recovery and applied the update from phone storage.
Click to expand...
Click to collapse
Checked the MD5 before?
Extremer2903 said:
Checked the MD5 before?
Click to expand...
Click to collapse
Used the OTA provided by graffixnyc
Extremer2903 said:
Checked the MD5 before?
Click to expand...
Click to collapse
The signature verification wouldn't apply the update if it saw mismatches.
Archon810 said:
The signature verification wouldn't apply the update if it saw mismatches.
Click to expand...
Click to collapse
Odd.. I had no problems using the OTA zip.. Did you guys try wiping data?
graffixnyc said:
Odd.. I had no problems using the OTA zip.. Did you guys try wiping data?
Click to expand...
Click to collapse
I tried wiping data, still had the same problem. I am reflashing the RUU and will try the ota again. If it doesn't work after the 2nd try, i will just wait for google to send the OTA to me. Wiping data sucks, have to redo everything
Psosmith82 said:
The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Click to expand...
Click to collapse
I wonder if this is also being experienced by any other users or if this is specific to your software config and/or some glitch while writing the firmware. I assume you haven't yet tried wiping your /data partition, right?
willverduzco said:
I wonder if this is also being experienced by any other users or if this is specific to your software config and/or some glitch while writing the firmware. I assume you haven't yet tried wiping your /data partition, right?
Click to expand...
Click to collapse
I wiped data and still had problems. I'm working on starting over right now
Then problem should be wiped/not wiped, I think. Anyway, trying with this error stuff is always an excited challenge with me, try to deal with it like that to reduce percentage of throwing your devices away .
Also you need to be FULLY stock.. that includes the stock kernel. If you are running a custom kernel some kernels flash libs and modules. EVERYTHING NEEDS TO BE STOCK
graffixnyc said:
Also you need to be FULLY stock.. that includes the stock kernel. If you are running a custom kernel some kernels flash libs and modules. EVERYTHING NEEDS TO BE STOCK
Click to expand...
Click to collapse
Mine is fully stock. I have an unlocked HTC one, and i flashed the GPE conversion RUU. Does the CID need to be changed to the Google CID
Psosmith82 said:
Mine is fully stock. I have an unlocked HTC one, and i flashed the GPE conversion RUU. Does the CID need to be changed to the Google CID
Click to expand...
Click to collapse
that's a really good question Psosmith
Only thing I can think of on my example is I had 'CF.lumen' installed... Other than that, I had (your) completely stock GPE conversion.
Troubleshooting...
Sent from space.
Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Android The Greek said:
Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I figured out the problem. I flashed the new RUU that graffix posted with 4.4.3. The Kernal in the OTA is not updating like it should, it stays on the kernal that was made in March. The new Kernal has a date of Thursday May 22nd. So for whatever reason, the OTA is not flashing the new Kernal, which is why all those things were broken. If you use the RUU update, it will flash the new kernal, and everything works as it should.
You'll know right off the bat at first boot. With the OTA, the boot animation hangs and it hangs on the home screen. With the RUU flash, everything is buttery smooth.
Something tells me this problem is occurring for people who actually have a retail M8 that they dirty-flashed using a GPE RUU.
Does anyone with an honest-to-God GPE that was purchased from Google have this problem? If so, this is huge.
Android The Greek said:
Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The update worked fine on my device and I used it for the conversion RUU. odd.. I used that very same OTA file. very odd...