Related
This is the stock US KitKat ROM for The Galaxy Tab 3 7" Tablet. Finally found it after a bunch of hassle online, and figured I'd post it here to make things easier for everyone.
When I Odin'd this ROM, it actually upgraded my tablet, and left all my items installed (not guaranteeing this will work the same for everyone else).
Afterwards, I just Odin'd TWRP to reroot using Chainfire's SuperSU (no other Superuser would work) and called it good.
Caution: if you are using a custom ROM, this may not work without reflashing stock 4.1.2 since the 4.4.2 ROM appears to be an update, rather than a full ROM.
Rooted devices and custom kernels that are otherwise stock should be fine.
The cache, and if possible dalvik-cache should be cleared before flashing. Some of those files can sometimes interfere with upgrades.
It might be necessary to pinpoint apps that are force closing, uninstall and reinstall them. Some apps, particularly paid apps, store their data differently on KitKat, and will automatically fail as a result.
If that fails, it might be necessary to factory reset the device.
The Stock 4.1.2 ROM for the T210R is available here: http://forum.xda-developers.com/gal...-stock-sm-t210r-4-1-2-jellybean-odin-t2958676
The T210R...XAR file is for the 210R:
https://drive.google.com/open?id=0B2iEgzRTFjrQTmI0ZjRBbWtOajQ&authuser=0
The ITV file is for the T210 (no R)
To download these ROMs, a torrent client is required (such as utorrent).
Anyone who wishes to contribute, please seed if you can after downloading ("Force Starting" the torrent will seed it indefinitely.)
Can I flash this on the SM-T210?
john410 said:
Can I flash this on the SM-T210?
Click to expand...
Click to collapse
I've seen both devices referenced together quite regularly, implying that they use the same ROM.
http://www.boeboer.com/samsung-galaxy-tab-3-7-sm-t210r-manual-guide-wifi/
And even use the same kernel from what I've read:
http://forum.xda-developers.com/showthread.php?t=2439564
I would take standard precautions, such as having a odin image of your original software available and performing a backup of your current system (if able).
Perhaps someone else has some insight to this question?
edit: Looks like I had my information wrong. Found where I obtained the ROM from, it is for the T210R model, and was not intended for the T210.
There are custom ROMs that have been patched for use on both devices, which is where my confusion came from, but this is an official ROM.
I have gotten my hands on the T210(no R) ROM file, and have update the Links above.
I am not responsible for any failed attempts at flashing to either device.
Greaper88 said:
I've seen both devices referenced together quite regularly, implying that they use the same ROM.
http://www.boeboer.com/samsung-galaxy-tab-3-7-sm-t210r-manual-guide-wifi/
And even use the same kernel from what I've read:
http://forum.xda-developers.com/showthread.php?t=2439564
I would take standard precautions, such as having a odin image of your original software available and performing a backup of your current system (if able).
Perhaps someone else has some insight to this question?
edit: Looks like I had my information wrong. Found where I obtained the ROM from, it is for the T210R model, and was not intended for the T210.
There are custom ROMs that have been patched for use on both devices, which is where my confusion came from, but this is an official ROM.
I have gotten my hands on the T210(no R) ROM file, and have update the Links above.
I am not responsible for any failed attempts at flashing to either device.
Click to expand...
Click to collapse
First, thanks for this. I have the T210R. I tried using this and had the same result, it updated the tablet instead of loading a completely new version. I did however run into a problem...the tablet had many for closes and reboots to a point it was unusable and so I reverted back to my backup. Did you see this? Maybe I had a bad download?
[email protected] said:
First, thanks for this. I have the T210R. I tried using this and had the same result, it updated the tablet instead of loading a completely new version. I did however run into a problem...the tablet had many for closes and reboots to a point it was unusable and so I reverted back to my backup. Did you see this? Maybe I had a bad download?
Click to expand...
Click to collapse
I did not have this problem, but I didn't have much on my Tab either. (Some apps don't play well with KitKat upgrades.)
Torrents have multiple segmented hashchecks to make sure you get an uncorrupted download, but it might still be possible. I'm reasonably sure my file is OK since I've used it (can't speak for the non R file though).
Did you clear your cache, and if possible your dalvik cache? I've read that some of those files interfere with upgrades.
If you can pinpoint the apps that are force closing, uninstall and reinstall them. Some apps, particularly paid apps, store their data differently on KitKat, and will automatically fail as a result.
Other option would be to try a factory reset and see if that fixes it. (I understand not wanting to do that though.)
One more thing, if your ROM isn't stock, or stock rooted (custom kernel should be ok too), you may have to flash 4.2 before the 4.4 ROM will work on the device.
Right guys, here i go, just joined and first question!!!
i have not ever rooted a sm-t210 but it was rooted when i bought it second hand!
i have linux installed on my p.c. and was wondering if there is a way to upgrade to and official KITKAT!
as stated i am having problems because my SM-T210 wifi only! and want to update to kitkat official release!
but was hoping also that there is a way/method to root via LINX and not via windows!!
if that is not possible how do i go about it on windows!! as i can use a friends WINDOWS-P.C. if i must!
ah also my SM-T210 does not have the options to change the function of the USB-function,,,
i.e.
it used to have an option to,, use as a mass storege, media transfer or use with samsung keis,,, or some thing of the sort
but this option has dissapeared! may have been my fault!!!! as i uninstalled some system apps,
now it crashes and reboots whenever i try to turn of USB-DEBUGGING options in DEVELOPER-OPTIONS !!!!
many thanks in advance,
Void.Naught
void.naught said:
Right guys, here i go, just joined and first question!!!
i have not ever rooted a sm-t210 but it was rooted when i bought it second hand!
i have linux installed on my p.c. and was wondering if there is a way to upgrade to and official KITKAT!
as stated i am having problems because my SM-T210 wifi only! and want to update to kitkat official release!
but was hoping also that there is a way/method to root via LINX and not via windows!!
if that is not possible how do i go about it on windows!! as i can use a friends WINDOWS-P.C. if i must!
ah also my SM-T210 does not have the options to change the function of the USB-function,,,
i.e.
it used to have an option to,, use as a mass storege, media transfer or use with samsung keis,,, or some thing of the sort
but this option has dissapeared! may have been my fault!!!! as i uninstalled some system apps,
now it crashes and reboots whenever i try to turn of USB-DEBUGGING options in DEVELOPER-OPTIONS !!!!
many thanks in advance,
Void.Naught
Click to expand...
Click to collapse
I do know that Heimdall is a multiplatform flashing tool substitute for Odin. Check out
http://forum.xda-developers.com/galaxy-tab-3/general/root-sm-t210-r-using-heimdall-t2936061
for more info. Hope it helps.
thank you for finding and posting the correct files for this tab
hi i have a galaxy tab kid t2105 rooted, is it possible to install any other rom after 4.1.2?
Greaper88 said:
Rooted devices and custom kernels that are otherwise stock should be fine.
Click to expand...
Click to collapse
Just to triple check, by the above quote you mean that if my tablet is currently rooted, I should still be fine to flash this update correct? [obviously it would become non-rooted once flashed and I'd have to re-root it as you mentioned you rooted after installing]
Also, how much space does this take up?
thanks
~J
ubuntujason said:
Just to triple check, by the above quote you mean that if my tablet is currently rooted, I should still be fine to flash this update correct? [obviously it would become non-rooted once flashed and I'd have to re-root it as you mentioned you rooted after installing]
Also, how much space does this take up?
thanks
~J
Click to expand...
Click to collapse
That is correct. I was rooted running the Werewolf custom OC kernel. I still had my tablet upgrade without wiping, and one other user has reported back saying the same. But I can not promise upgrade as opposed to overwrite.
The flash file once extracted, is about 1.4 GB, I don't know sizes beyond that. It does not repartition the tablet however.
Greaper88 said:
That is correct. I was rooted running the Werewolf custom OC kernel. I still had my tablet upgrade without wiping, and one other user has reported back saying the same. But I can not promise upgrade as opposed to overwrite.
The flash file once extracted, is about 1.4 GB, I don't know sizes beyond that. It does not repartition the tablet however.
Click to expand...
Click to collapse
Awesome, thanks!
~J
Could you upload the T210 ITV file? This torrent is going to take 10 hours
No system file
Well this is awesome, system won't mount and I don't have a backup. Samsung website does NOT have the stock firmware, and attempting to get it for another country just to get this to load so I can flash a ROM leaves me with having to download at 15kbs. I am in the process of selling this to someone for their kid... And there are ZERO seeders for these files. Lovely.
Sorry, m'y post an error
ragnaroksangel said:
Well this is awesome, system won't mount and I don't have a backup. Samsung website does NOT have the stock firmware, and attempting to get it for another country just to get this to load so I can flash a ROM leaves me with having to download at 15kbs. I am in the process of selling this to someone for their kid... And there are ZERO seeders for these files. Lovely.
Click to expand...
Click to collapse
Are you looking for the Stock Rom?
Darthlord064 said:
Are you looking for the Stock Rom?
Click to expand...
Click to collapse
I am, can you help?
Greaper88 said:
I do know that Heimdall is a multiplatform flashing tool substitute for Odin. Check out
http://forum.xda-developers.com/galaxy-tab-3/general/root-sm-t210-r-using-heimdall-t2936061
for more info. Hope it helps.
Click to expand...
Click to collapse
For some (unknown) reason, Odin3 nor JOdin3 doesn't seem to work for flashing my Samsung Galaxy Tab3 device. For that reason I tried Heimdall-Frontend, but to make that work you need to extract the content of a stock ROM first.
Anyways, it still didn't lead to get my device into factory reset yet.
But that's another story on which I still have not yet found the answers needed to get the device successfully back into factory reset.
My guess is that the 'system.img' file, of Android 4.4.2, successfully has been loaded from Heimdall-Frontend, yet by going into reboot right away after Heimdall-Frontend releases the connected device, the download may be deleted.
I read that the cause of that may lie in the fact that Android 4.4.2 is only an update and no full ROM.
Hi friends, well basically the problem is I got a friends y GT-I9500 and it bootloops over and over with any ROM other than South Africa Rom 4.2.2 and has invalid baseband. It's a cell from a friend of mine I never new which rom was installed on this phone and as soon as I got it I installed the official stock rom from my country which was KIT KAT rom 4.4.2 tried unbranded ARO version first through ODIN, everything went fine, but it got stuck on bootloop.
These were the things I tried.
- stock recovery (I9500UBUGNG1_I9500UUBGNG1_ARO) --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
Installed another Stock rom KIT KAT from corresponding Carrier (I9500UBUFNC1_I9500TFGFNC1_UFN) , did :
- stock recovery --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
Downloaded previous builds of stock rom going back to 4.2.2 , installed stock version of 4.2.2 ARO unbranded (I9500UBUBMG1_I9500TFGBMG1_UFN)
- stock recovery --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
I also tried installed some custom roms , having flashed Philz recovery and installed from there onwards, no luck as well.
So I came across some threads which said the only possible way of downgrading if I had installed 4.4.2 kit kat , was using a South African ROM 4.2.2. So I tried it and to my surprise the phone booted fine without any problems. Honestly I don't remember if I did flash it with the PIT file and re-partition. But I did work . The only problem once inside the OS itself it showed invalid baseband. I suppose this was due to the EFS partition being changed intially by KIT KAT.
So I'm hoping someone might help me out as to know what else to try, because honestly I'm out of all ideas.
Thanks !
When you went into download mode, what was the product name the phone reported?
Strephon Alkhalikoi said:
When you went into download mode, what was the product name the phone reported?
Click to expand...
Click to collapse
mmm I have to check, what do yo uwant me to see what string? I can put it on downlaod mode again.. and get you a screenshot
Screenshot is fine as it will give me what I need to know.
Strephon Alkhalikoi said:
When you went into download mode, what was the product name the phone reported?
Click to expand...
Click to collapse
screenshot attached , please check
Thanks. I just wanted to be sure you didn't get a Frankenstein phone, as there have been a run of these phones appearing in the last few months. Resellers will take SGH-I337 phones (US AT&T Galaxy S4), slap an I9500 or I9505 IMEI on them, and proceed to add firmware for the I9500/I9505 onto them. When the purchaser gets the device and attempts to update it or customize it, they find they can't, as the AT&T S4 bootloader is locked.
Now that I've gotten the explanation out of the way, you need to do the following. 1) Install Wanam's EFS Backup tool to the S4, run it, and backup the hidden partitions on the device. 2) You're going to again install the latest ROM for your region through Odin, but this time you're also going to add an I9500 PIT file to it. The PIT file should be available for download in the S4 forums here and will tell Odin the correct partition layout of the device. Odin will then install the ROM using that partition layout. With luck, it should correct the issues you've been having.
Should you have an issue with no IMEI or no signal after flashing, flash the modem file, which should also be available on the forums, and don't use the PIT file. If that doesn't work, install EFS Backup again and restore the partitions.
Strephon Alkhalikoi said:
Thanks. I just wanted to be sure you didn't get a Frankenstein phone, as there have been a run of these phones appearing in the last few months. Resellers will take SGH-I337 phones (US AT&T Galaxy S4), slap an I9500 or I9505 IMEI on them, and proceed to add firmware for the I9500/I9505 onto them. When the purchaser gets the device and attempts to update it or customize it, they find they can't, as the AT&T S4 bootloader is locked.
Now that I've gotten the explanation out of the way, you need to do the following. 1) Install Wanam's EFS Backup tool to the S4, run it, and backup the hidden partitions on the device. 2) You're going to again install the latest ROM for your region through Odin, but this time you're also going to add an I9500 PIT file to it. The PIT file should be available for download in the S4 forums here and will tell Odin the correct partition layout of the device. Odin will then install the ROM using that partition layout. With luck, it should correct the issues you've been having.
Should you have an issue with no IMEI or no signal after flashing, flash the modem file, which should also be available on the forums, and don't use the PIT file. If that doesn't work, install EFS Backup again and restore the partitions.
Click to expand...
Click to collapse
Ok , thanks for such a complete explanation. It's always nice when someone with knowledge takes the time to go detail by detail explaining everything. This is the way things have to be done, and explained. Ok so let me get things straight
- Wanams Efs backup , I need to install within a working ROM right? It's not through Philz recovery, What should I backup with EFS backup only EFS?. Something I forgot to tell you was I did change some permissions to see if the invalid baseband got fixed, I changed some owner permissions on the EFS folder, you should know about this.
-Then you want me to install latest ROM should that be KIT KAT right?. Unbranded for my region. Yes I know about the PIT file to repartition, I've already done this and still bootlooped with all the rom variants I tried. The only possible way the phone boots and succeeds is with South African ROM 4.2.2 I've tried all previous roms even choosin the apropiate PIT and still bootlooped.
-The only thing I'm left thinking is all these bootloops have something to do with the modem file, which the South African rom 4.2.2 might have a different modem. Which modem should I install I've read the G versions onwards modified the EFS partition.
- Last, how would EFS backup fix the EFS partition if it's only backing it up, Cause i'm thinking as I've initially when I received the phone installed KIT KAT. IT changed the whole partition scheme of efs.
So now that I've gone through every point, can you clear again the steps sorry if I'm so tedious on reviewing again but I needed to clarify bit by bit.
I must have misunderstood you regarding the IMEI. If it's invalid EFS Backup won't help. Also, if you've already ran the PIT file and still get bootloops, you may have to take the device in for servicing. A service center should be able to fix this without too much trouble. Unfortunately, I can't fathom why only one ROM installs, unless the carrier locked down the device so much that upgrades are impossible.
Perhaps one of the other advanced users or developers have a clue?
Strephon Alkhalikoi said:
I must have misunderstood you regarding the IMEI. If it's invalid EFS Backup won't help. Also, if you've already ran the PIT file and still get bootloops, you may have to take the device in for servicing. A service center should be able to fix this without too much trouble. Unfortunately, I can't fathom why only one ROM installs, unless the carrier locked down the device so much that upgrades are impossible.
Perhaps one of the other advanced users or developers have a clue?
Click to expand...
Click to collapse
Hey so many thanks, honestly I don't know what have been wrong with the device. I'm suspeting this has to do with the modem. Could the modem version on the South africa rom be causing the ROM to install fine. But think of this me first installing KIT KAT and have screwed up the efs and as a consequence the IMEI. My only way would be to install kit kat succesfully as the EFS might have changed. Any advices on this?
The modem isn't likely to cause a bootloop. At worst, it's likely to render the cellular and WiFi services unusable until it's flashed again. Screwing the EFS up is where I believe your problems lie. The EFS partition may well be corrupted, which could cause your bootloop. I really think the only way you'll resolve this is by having someone at Samsung take a look at it. You've repeatedly installed ROMs and have had no luck, so installing a ROM again isn't going to help you here.
hi,
I have a nexus 5 with lollipop 5.0.1, xposed (gravity box, amplify and greenify activated) and franco kernel.
My problem is that in the wifi settings i dont see any wifi available, my phone just connects to the few wify that i had already saved.
I donwload a third party app (wifi manager) and from the app i can see every connection available near me, so the problem must be rom related, not hardware related.
I tried flashing system and boot from 5.0 image, but that didnt solve the problem (i tought that going back to stock kernel and deactivating xposed would have helped). So i tried to flash 5.1 (i'm actually still with 5.0.1 because i want to use xposed), i flashed boot system radio and bootloader and that solved the problem, without wiping any data or app.
Since that solved the problem i thought that maybe bootloader or radio had something to do with it, ann i flashed again 5.0.1 with the new bootloader and the new radio but the bug was still there, nothing changed.
Is this a common bug?i searched in the forum and trough google but i couldnt find anyone with my exact problem, do you think you can help me?
If you need any log i'll post it here, just tell me what you need!
Thanks in advamce
AtField said:
hi,
I have a nexus 5 with lollipop 5.0.1, xposed (gravity box, amplify and greenify activated) and franco kernel.
My problem is that in the wifi settings i dont see any wifi available, my phone just connects to the few wify that i had already saved.
I donwload a third party app (wifi manager) and from the app i can see every connection available near me, so the problem must be rom related, not hardware related.
I tried flashing system and boot from 5.0 image, but that didnt solve the problem (i tought that going back to stock kernel and deactivating xposed would have helped). So i tried to flash 5.1 (i'm actually still with 5.0.1 because i want to use xposed), i flashed boot system radio and bootloader and that solved the problem, without wiping any data or app.
Since that solved the problem i thought that maybe bootloader or radio had something to do with it, ann i flashed again 5.0.1 with the new bootloader and the new radio but the bug was still there, nothing changed.
Is this a common bug?i searched in the forum and trough google but i couldnt find anyone with my exact problem, do you think you can help me?
If you need any log i'll post it here, just tell me what you need!
Thanks in advamce
Click to expand...
Click to collapse
http://forum.xda-developers.com/google-nexus-5/help/wifi-stuck-t2721643
beekay201 said:
http://forum.xda-developers.com/google-nexus-5/help/wifi-stuck-t2721643
Click to expand...
Click to collapse
Thanks for the answer but my WiFi actually turns on without any problem, and also connect to the few WiFi that I already had saved! And with a third party app i actually have no problem, It works as it should
Anyone?
Bump! I still have this problem
suddenly i bought this phone second hand. then when I tested Turning on my bluetooth it won't turn on.
Is there anyone experiencing the same problem?
I already did troubleshoot and performed this steps:
1. Wipe cache of Bluetooth Applications on System apps in settings
2. Force stop Bluetooth Applications on System apps in settings
3. Restart my phone
4. Wipe Cache on stock Recovery & restart my phone
5. Restore Factory Settings on Recovery
but suddenly bluetooth still won't open when touching it on notification panel nothing happens even directly on the settings toggling the bluetooth won't work. :crying:
my phone is untouch on rooting world.
So my questions is;
1. Will rooting and flashing rom can solve my bluetooth problem?
2. Is this a hardware problem?
3. Is there a separate chip or module for bluetooth on the motherboard of S7 edge?
to all XDA members I'm asking if you have an idea on this matter please feel free to reply to this post.
thanks you so much!
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Beanvee7 said:
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Click to expand...
Click to collapse
if it is a hardware problem? is there a separate module or chip on the s7 edge motherboard? or it is integrated on the processor ?
I don't know the answer to that
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
dhawal4u said:
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
Click to expand...
Click to collapse
what custom rom have you tested?
i already tried Batman-Rom
lervzz said:
what custom rom have you tested?
i already tried Batman-Rom
Click to expand...
Click to collapse
batman / superman / tgp and many others
none working
dhawal4u said:
batman / superman / tgp and many others
none working
Click to expand...
Click to collapse
I tried flashing newest stock nougat firnware XTC csc.
Tried it using ODIN
But still bluetooth won't turn on.
Can you say that our problem is hardware failure? But I think if it's a hardware issue then wifi should not work too. Because wifi and bluetooth is on the same chip module. ???
Update: I've talk to numerous technician and they think its not a hardware issue since my wifi is working. They said that wifi and bluetooth is on the same micro chip module. So if it is hardware issue on the bluetooth wifi should not work too. ???????? @dhawal4u
Same Problem here. Since 2 months after trying Badman Rom my Bluetooth doenst work. Now I load Stock Rom, Bootloader, Modem but no solve for the Problem
I've spent months now trying to find a modem update for my Samsung SM-G920F 8.1 oreo without any luck. I get none stop wifi disconnections and in tired of this. I have searched every place I can even think of. Can anyone help?
I'm in the UK and can only find any info on US modems.
Any time any questions are asked about this, people seem to avoid the question or just point to dead posts.
Modzmarvin said:
I've spent months now trying to find a modem update for my Samsung SM-G920F 8.1 oreo without any luck. I get none stop wifi disconnections and in tired of this. I have searched every place I can even think of. Can anyone help?
I'm in the UK and can only find any info on US modems.
Any time any questions are asked about this, people seem to avoid the question or just point to dead posts.
Click to expand...
Click to collapse
Maybe the issue is not with the modem?
From the time that the issue started, what did you initially try and what have you tried since then up to now?
Sent from my LGL84VL using Tapatalk
Droidriven said:
Maybe the issue is not with the modem?
From the time that the issue started, what did you initially try and what have you tried since then up to now?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I have come to this conclusion from a bug report i made to lineage. There solution they have been giving everyone was "update modem/baseband", although i must admit, i haven't had any issues on another Samsung i have (SM-G910N) which i found strange as that's never had a modem update since like 5.1)
I've tried a few customers kernels (AldeXus kernel, fk r5+r7 anytime kernel, quantum oreo g920x v2, stormguard oc mido 6.2, + few more), that have all failed to install due to "unsupported device" but claim to support sm-g920f, but in all honesty i really don't know what else to try.
I get this issue on 8.1 lineage and 8.1 resurrection and the highest stock ROM available for this phone is 7.1 (don't get this issue on 7.1).
I've searched everything direction i can and so far the only solutions i could see that make sense is baseband as of course it controls communication with WiFi and network.
Lineage refuse to help as that is there only solution and point me to a thread that is for a nexus who have a 8.1 stock ROM to take the modem from (decompiling a stock ROM and flashing the modem)
Regards
Modzmarvin said:
I have come to this conclusion from a bug report i made to lineage. There solution they have been giving everyone was "update modem/baseband", although i must admit, i haven't had any issues on another Samsung i have (SM-G910N) which i found strange as that's never had a modem update since like 5.1)
I've tried a few customers kernels (AldeXus kernel, fk r5+r7 anytime kernel, quantum oreo g920x v2, stormguard oc mido 6.2, + few more), that have all failed to install due to "unsupported device" but claim to support sm-g920f, but in all honesty i really don't know what else to try.
I get this issue on 8.1 lineage and 8.1 resurrection and the highest stock ROM available for this phone is 7.1 (don't get this issue on 7.1).
I've searched everything direction i can and so far the only solutions i could see that make sense is baseband as of course it controls communication with WiFi and network.
Lineage refuse to help as that is there only solution and point me to a thread that is for a nexus who have a 8.1 stock ROM to take the modem from (decompiling a stock ROM and flashing the modem)
Regards
Click to expand...
Click to collapse
Have you tried extracting the modem from the 7.1 stock firmware then flashing the modem?
Here are guides for extracting the firmware to get a copy of the modem.img.
https://forum.xda-developers.com/showthread.php?t=2138885
https://www.rwilco12.com/forum/showthread.php?tid=74
Here is a guide to take the extracted modem.img and convert it to an Odin flashable .tar.md5, flash it via Odin in the AP slot in Odin.
https://forum.xda-developers.com/showthread.php?t=2154762
Here is a tool that might make it easier to create the Odin flashable file.
https://forum.xda-developers.com/showthread.php?t=2446269
Sent from my LGL84VL using Tapatalk
Droidriven said:
Have you tried extracting the modem from the 7.1 stock firmware then flashing the modem?
Here are guides for extracting the firmware to get a copy of the modem.img.
https://forum.xda-developers.com/showthread.php?t=2138885
https://www.rwilco12.com/forum/showthread.php?tid=74
Here is a guide to take the extracted modem.img and convert it to an Odin flashable .tar.md5, flash it via Odin in the AP slot in Odin.
https://forum.xda-developers.com/showthread.php?t=2154762
Here is a tool that might make it easier to create the Odin flashable file.
https://forum.xda-developers.com/showthread.php?t=2446269
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
The modem i currently have installed is from the 7.1 stock ROM but i think what ill do is download the latest 7.1 and try and see what if it has any improvements as it has been a few months since i flashed the 7.1 modem so there could possibly be an improvement in one of the latest updates.
Truly hope so because although lineage it disconnected often, it would reconnect rather easy but resurrection its become a right pain cause its making me turn the wifi off and back on again before it can find any wifi around me!
Thanks for the links pal, I'll give it a shot once i finally manage to download the ROM lol
Droidriven said:
Have you tried extracting the modem from the 7.1 stock firmware then flashing the modem?
Here are guides for extracting the firmware to get a copy of the modem.img.
https://forum.xda-developers.com/showthread.php?t=2138885
https://www.rwilco12.com/forum/showthread.php?tid=74
Here is a guide to take the extracted modem.img and convert it to an Odin flashable .tar.md5, flash it via Odin in the AP slot in Odin.
https://forum.xda-developers.com/showthread.php?t=2154762
Here is a tool that might make it easier to create the Odin flashable file.
https://forum.xda-developers.com/showthread.php?t=2446269
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Updated the modem. Now to wait and see if it any better haha. THanks for the links!
Found it was super simple to do.
Pulled the tar.md5 apart with 7zip and then zipped it back up with 7zip and it flashed with odin nice and simple . Links are useful for the img files tho! also good to learn from!
Droidriven said:
Have you tried extracting the modem from the 7.1 stock firmware then flashing the modem?
Here are guides for extracting the firmware to get a copy of the modem.img.
https://forum.xda-developers.com/showthread.php?t=2138885
https://www.rwilco12.com/forum/showthread.php?tid=74
Here is a guide to take the extracted modem.img and convert it to an Odin flashable .tar.md5, flash it via Odin in the AP slot in Odin.
https://forum.xda-developers.com/showthread.php?t=2154762
Here is a tool that might make it easier to create the Odin flashable file.
https://forum.xda-developers.com/showthread.php?t=2446269
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Modem updated and still getting random wifi drops
Modzmarvin said:
Modem updated and still getting random wifi drops
Click to expand...
Click to collapse
Have you at any point, tried booting to recovery and wipe the cache partition?
Sent from my LGL84VL using Tapatalk
Droidriven said:
Have you at any point, tried booting to recovery and wipe the cache partition?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Yep done it a fair few times. Also gone through like 5 lineage updates and 2 resurrection updates. Wipe dalvik/cache each time. Plus wipes cache when rooting, getting any laggy points so on.
Can the kernel help improve the wifi? Its so far the only thing that not been updated (although i can't seem to find a single kernel that works but curious if that may be the issue).
I assume it is an issue I'm having unlike most on 8.1 with a sm-g920f as I'm not seeing many saying they are having the same issue
Modzmarvin said:
Yep done it a fair few times. Also gone through like 5 lineage updates and 2 resurrection updates. Wipe dalvik/cache each time. Plus wipes cache when rooting, getting any laggy points so on.
Can the kernel help improve the wifi? Its so far the only thing that not been updated (although i can't seem to find a single kernel that works but curious if that may be the issue).
I assume it is an issue I'm having unlike most on 8.1 with a sm-g920f as I'm not seeing many saying they are having the same issue
Click to expand...
Click to collapse
I'm doubting whether the kernel is related with the issue.
When you flashed Lineage, did you perform a system wipe and then clean install the ROM?
Sent from my LGL84VL using Tapatalk
Droidriven said:
I'm doubting whether the kernel is related with the issue.
When you flashed Lineage, did you perform a system wipe and then clean install the ROM?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Damn, there's hoping haha.
Yep every time i install a new room i wipe everything (other then internal storage). This issue has only come about when i wiped everything on 7.0 then installed 8.0. Then wiped it again and put 8.1 cause i didn't notice there was a 8.1 update.
Modzmarvin said:
Damn, there's hoping haha.
Yep every time i install a new room i wipe everything (other then internal storage). This issue has only come about when i wiped everything on 7.0 then installed 8.0. Then wiped it again and put 8.1 cause i didn't notice there was a 8.1 update.
Click to expand...
Click to collapse
Do any of the updated that you've taken, have locked bootloader that prevents downgrading the stock firmware? If you can flash back to what you originally had when you first rooted the device, then root and install TWRP again, it might clear things up and return to its original working state before whatever update started the issue.
In other words, if you can get back to what you originally had, then work your way back through all the way up to just before the update except don't do that update this time, maybe you can figure something out from there to update the device without causing the same issue this time.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Do any of the updated that you've taken, have locked bootloader that prevents downgrading the stock firmware? If you can flash back to what you originally had when you first rooted the device, then root and install TWRP again, it might clear things up and return to its original working state before whatever update started the issue.
In other words, if you can get back to what you originally had, then work your way back through all the way up to just before the update except don't do that update this time, maybe you can figure something out from there to update the device without causing the same issue this time.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I don't believe I've ever had any bootloader locks. Been unlocked from the first day i unlocked it and never re enabled.
I just realised this started on 15.1 as just checked my lineage but report and it was for 15.1.
When i made the bug report, this was the link they gave me then closed the ticket: https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-1890
even typing this out the wifi dropped out ?. when it was on 15.1, it used to need the wifi to be turned off, the phone would freeze then after a few minutes the wifi would turn off. I'd then turn it back on and all wifi would pick back up. the closest i could find to the wifi issue is:
https://www.google.co.uk/amp/s/foru...xy-s6/524916-s6-wifi-drop-out-issues.html?amp
That some one said "I also have this issue I would know wifi disconnects and reconnects becoz the phone will stop responding. It not that I get ANR notif but the phone is jsut froze and only responsive when wifi reconnects. "
Which is as close to my issue i have.
I think i may just go back to stock and see if it works, then as you say slowly move up bit by bit till i start getting the issue and see what happens.
Modzmarvin said:
I don't believe I've ever had any bootloader locks. Been unlocked from the first day i unlocked it and never re enabled.
I just realised this started on 15.1 as just checked my lineage but report and it was for 15.1.
When i made the bug report, this was the link they gave me then closed the ticket: https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-1890
even typing this out the wifi dropped out [emoji58]. when it was on 15.1, it used to need the wifi to be turned off, the phone would freeze then after a few minutes the wifi would turn off. I'd then turn it back on and all wifi would pick back up. the closest i could find to the wifi issue is:
https://www.google.co.uk/amp/s/foru...xy-s6/524916-s6-wifi-drop-out-issues.html?amp
That some one said "I also have this issue I would know wifi disconnects and reconnects becoz the phone will stop responding. It not that I get ANR notif but the phone is jsut froze and only responsive when wifi reconnects. "
Which is as close to my issue i have.
I think i may just go back to stock and see if it works, then as you say slowly move up bit by bit till i start getting the issue and see what happens.
Click to expand...
Click to collapse
Once you get flashed back to stock and then get TWRP installed, make sure you make a nandroid backup before performing the next step, if the issue starts, you can restore the backup and be back to what you had before performing that step. Each time you successfully step up without issues, make a new backup and remove the backup from before that, then perform your next step, always keeping a backup from just before that step.
Sent from my LGL84VL using Tapatalk