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.
Alright guys, so this happened 100% ON ACCIDENT but it actually worked! I wanted to let you guys know because maybe it will help some of the devs figure out how to eliminate the static boot for good.
I have the H910 ATT V20. I initially rooted it using Dirty Santa but, at the time, nobody had made a custom ROM for the ATT variant yet. I flashed the Konverged Kernel and from then on, I had the dreaded static screen on boot. @Tilde88 was extremely generous in offering to make a custom ROM if I provided some files for him and he made the first excellent NotSoStock ROM for the ATT V20. However, I had some issues installing it on the first try. When I tried to flash his ROM, TWRP gave me an error telling me I had a US996. I patched the zip with a file from Tilde88 and it worked like magic!
Since then, there has been a lot of progress in ROMs and kernels for all the variants. For the sake of experimentation, I have tried different ROMs and kernels to see how they affect the phone. Since my phone is registering as a US996, I flashed that variant of the NotSoStock ROM. The Werewolf Kernel from @USA-RedDragon is the only one I know of so far that does not have the static on boot. I have been flashing Werewolf and Konverged along with different ROMs to see the difference in performance and battery.
The ROM I am on right now is Extreme Syndicate from @elliwigy. Since it is based off of the stock deodexed US996 firmware, I thought it sounded great to try since it has NONE of the bloat from any of the various carriers. I read in a post by @AlkaliV2 here about flashing the stock kernel located on my computer from the original Dirty Santa root method:
https://forum.xda-developers.com/v2...-nrd90m-modded-notsostock-rom-t3525344/page21
That gave me an idea to download and flash the stock unlocked US996 kernel since Extreme Syndicate is based off of that. I had Konverged Kernel at the time. I flashed the US996 kernel, but forgot to flash SuperSU before boot... Woops lol. So I went back to TWRP and formatted my phone to start from a fresh flash, but realized I also deleted my ROM backup when I formatted my phone. So I decided to install a ROM and kernel fresh.
HERE IS HOW I FIXED THE STATIC BOOT
After formatting my phone, I flashed the Extreme Syndicate ROM with the Werewolf Kernel. I chose this kernel so there would not be any static on boot.
Then
I booted back to TWRP, made a backup just in case, and flashed my stock H910 ATT kernel from the file named bootbackup.img. After that, I flashed SuperSU, wiped Cache and Dalvik, rebooted... and BAM, just like that, no static! It says under software information that I am on kernel version 3.18.31. 3C Toolbox shows the kernel as Linux 3.18.31g12e8957
It is still fresh so I have to see how it goes with battery and performance. Initially, it was noticeably slower. I completely fixed this by:
1. Implementing all options under "One Click -> Performance Optimizations" in the app 3C Toolbox
2. Selecting "Performance" under Profiles in the app L Speed
I just wanted to share this with everyone to put this info out there. I have not seen a fix for the static boot yet and though that this might be useful info for someone out there! I hope this helps!
Yes, there is an updated driver branch using CAF sources that fixes static boot. I'm far too busy in life to get anything done, and before anything else, I have to get v6.0 for the H918 going. Once that is up (using the latest build and soruces from LG), I can move forward for 6.0 for the other devices.
nikktrikk said:
I just wanted to share this with everyone to put this info out there. I have not seen a fix for the static boot yet and though that this might be useful info for someone out there! I hope this helps!
Click to expand...
Click to collapse
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb
AlkaliV2 said:
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb
Click to expand...
Click to collapse
Hmmm interesting. Mine returned with:
Code:
3.18.31-g12e8957
[/QUOTE]
Do you have any idea why that might have happened? I used the file directly from the Dirty Santa folder, but maybe there is an issue since I flashed it over the previous kernel.
AlkaliV2 said:
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb
Click to expand...
Click to collapse
Also, I think it is an issue with my phone registering as a LG-US996. None of the ATT ROMs will flash onto it and I don't know how to convert it back to register as an H910. It seems like that is one of the primary reasons that the kernel I used from my computer may be having issues. Do you know how I can revert my phone? Nemisisg4 mentioned that when he tried to reflash the NotSoStockRom, it said no OS was installed. I also got that error numerous times when messing with different setups and it caused me to have to flash things all over again. I could not restore my saved backups of the 5.5 either after wiping the ROM I think because, since the ROM needed to go from the 5.1 to the 5.5, when I backed-up the 5.5, there was a conflict during the restore process.
nikktrikk said:
Also, I think it is an issue with my phone registering as a LG-US996. None of the ATT ROMs will flash onto it and I don't know how to convert it back to register as an H910. It seems like that is one of the primary reasons that the kernel I used from my computer may be having issues. Do you know how I can revert my phone? Nemisisg4 mentioned that when he tried to reflash the NotSoStockRom, it said no OS was installed. I also got that error numerous times when messing with different setups and it caused me to have to flash things all over again. I could not restore my saved backups of the 5.5 either after wiping the ROM I think because, since the ROM needed to go from the 5.1 to the 5.5, when I backed-up the 5.5, there was a conflict during the restore process.
Click to expand...
Click to collapse
Alright, I was out for a little but I'm back now and I have a suggestion. I'm going to write up a short how-to but go here: https://forum.xda-developers.com/v20/how-to/stock-att-h910-stock-recovery-boot-image-t3528060
You are not going to follow that guide directly as I need to update it to include the actual stock kernel bootbackup.img but the backup files need to be placed in TWRP for the Restore function to work.
So to modify the steps a bit for your usage:
!) You need SuperSU 2.79 stable and your bootbackup.img file saved to your microSD card
1.) Put the files in the TWRP > Backups folder (preferably on your microSD card because we are formatting your entire data and internal storage) *
2.) You are going to go to advanced wipe and wipe everything except microSD and USB-OTG
3.) Go back and choose Format Data from the wipe screen and swipe to wipe data again just to be sure
4.) Reboot to recovery
5.) Now we want to restore the system image you have saved to your MicroSD card. Hit the restore menu, make sure the system checkbox is checked only, and slide to start
6.) Once finished head back to the main menu and choose Install > Install image and choose your bootbackup.img file
7.) Once done immediately flash SuperSU 2.79 stable
8.) Power off the device from the menu leave it be for about 30 seconds then turn it back on and let it boot.
It SHOULD work. Let me know if it doesn't and I wish you luck. Also, avoid US996 ROMs for the time being. I am getting the H910 image out to devs as quickly as I can and it has files that are pretty important to the hardware in our phone. If you get this to boot just use TiBu to remove things you don't want and always keep a copy of this backup ROM on your drive.
*If you do not have a microSD card to put these files on you can do a full wipe like I mention above, but you'll have to fully wipe it as I have instructed, reboot recovery to TWRP, hook the phone up to the PC at that point and copy the files you need over to it at that point.
AlkaliV2 said:
Alright, I was out for a little but I'm back now and I have a suggestion. I'm going to write up a short how-to but go here: https://forum.xda-developers.com/v20/how-to/stock-att-h910-stock-recovery-boot-image-t3528060
You are not going to follow that guide directly as I need to update it to include the actual stock kernel bootbackup.img but the backup files need to be placed in TWRP for the Restore function to work.
So to modify the steps a bit for your usage:
!) You need SuperSU 2.79 stable and your bootbackup.img file saved to your microSD card
1.) Put the files in the TWRP > Backups folder (preferably on your microSD card because we are formatting your entire data and internal storage) *
2.) You are going to go to advanced wipe and wipe everything except microSD and USB-OTG
3.) Go back and choose Format Data from the wipe screen and swipe to wipe data again just to be sure
4.) Reboot to recovery
5.) Now we want to restore the system image you have saved to your MicroSD card. Hit the restore menu, make sure the system checkbox is checked only, and slide to start
6.) Once finished head back to the main menu and choose Install > Install image and choose your bootbackup.img file
7.) Once done immediately flash SuperSU 2.79 stable
8.) Power off the device from the menu leave it be for about 30 seconds then turn it back on and let it boot.
It SHOULD work. Let me know if it doesn't and I wish you luck. Also, avoid US996 ROMs for the time being. I am getting the H910 image out to devs as quickly as I can and it has files that are pretty important to the hardware in our phone. If you get this to boot just use TiBu to remove things you don't want and always keep a copy of this backup ROM on your drive.
*If you do not have a microSD card to put these files on you can do a full wipe like I mention above, but you'll have to fully wipe it as I have instructed, reboot recovery to TWRP, hook the phone up to the PC at that point and copy the files you need over to it at that point.
Click to expand...
Click to collapse
Wow, thank you for such a detailed post! So just to clarify, after flashing the bootbackup.img that includes the stock kernel AND the stock ROM? And this is basically unrooting my phone and putting it back to stock, so I would need to go through this process, then re-root?
Before you responded, I managed to flash the stock US996 kernel to my phone with the extreme syndicate ROM. So far it is lightning fast, the battery seems good. Usage so far is about 7 hours with an estimated time remaining of 35h 27 min. I know you said to avoid the US996 ROMs, do you think it is worth it to go back to stock if I am getting those stats as of right now, will the battery life and speed be comparable? Isn't the hardware the same, just each phone has it's own OS, hence why my phone functions on the US996 after the conversion happened? I have no idea about this so I am just throwing that out there to ask!
Thanks again for your help!
nikktrikk said:
Wow, thank you for such a detailed post! So just to clarify, after flashing the bootbackup.img that includes the stock kernel AND the stock ROM? And this is basically unrooting my phone and putting it back to stock, so I would need to go through this process, then re-root?
Before you responded, I managed to flash the stock US996 kernel to my phone with the extreme syndicate ROM. So far it is lightning fast, the battery seems good. Usage so far is about 7 hours with an estimated time remaining of 35h 27 min. I know you said to avoid the US996 ROMs, do you think it is worth it to go back to stock if I am getting those stats as of right now, will the battery life and speed be comparable? Isn't the hardware the same, just each phone has it's own OS, hence why my phone functions on the US996 after the conversion happened? I have no idea about this so I am just throwing that out there to ask!
Thanks again for your help!
Click to expand...
Click to collapse
I can't even begin to tell you what the right thing to do here is. I can only say what my experience was having my device run as a US996. Broken comfort view, no wifi-calling, FM radio not working (variant kernel related), and issues with battery drain. But that was my experience. If you are having good results running 996 then don't feel obligated to change. My post was just to get your phone back to being recognized as a H910. Now to answer your original question:
The files I linked to above in the guide are for the H910 system, recovery, and boot image made immediately after I got dirty cow working. The kernel in that backup set is the US996 kernel, not the one you need to go back to full rooted stock. The restore method I mention does not remove root or break TWRP it just puts back the stock ROM in full and then you flash bootbackup.img along with SuperSu to keep root and boot the stock kernel. It is the config I am running right now because it gets me all the features working aside from the static boot. So you only need to follow my guide if you can't get back to stock H910 rooted.
Edit: let me be clear in case it wasn't before. If you decide to use my backup files: do NOT use the boot or recovery image from those restore files. Use just the system restore image and your own personal bootbackup.img kernel along with SuperSu 2.79 stable.
AlkaliV2 said:
I can't even begin to tell you what the right thing to do here is. I can only say what my experience was having my device run as a US996. Broken comfort view, no wifi-calling, FM radio not working (variant kernel related), and issues with battery drain. But that was my experience. If you are having good results running 996 then don't feel obligated to change. My post was just to get your phone back to being recognized as a H910. Now to answer your original question:
The files I linked to above in the guide are for the H910 system, recovery, and boot image made immediately after I got dirty cow working. The kernel in that backup set is the US996 kernel, not the one you need to go back to full rooted stock. The restore method I mention does not remove root or break TWRP it just puts back the stock ROM in full and then you flash bootbackup.img along with SuperSu to keep root and boot the stock kernel. It is the config I am running right now because it gets me all the features working aside from the static boot. So you only need to follow my guide if you can't get back to stock H910 rooted.
Edit: let me be clear in case it wasn't before. If you decide to use my backup files: do NOT use the boot or recovery image from those restore files. Use just the system restore image and your own personal bootbackup.img kernel along with SuperSu 2.79 stable.
Click to expand...
Click to collapse
Definitely makes sense. Yeah I have been having issues with battery drain and all that, as well. This is the very first time since I have been having issues with the US996/H910 conversion and incompatibility that I have actually got it to be stable. I also didn't like not having comfort view, and this actually fixed it! Comfort view now works on my phone, it didn't work earlier today before this most recent flash. I think that I will just give it some time before I make a decision and see how the battery fares. You have been a HUGE help, I really appreciate you taking the time to explain the process to restore my phone. I do want to do it, but being that it currently seems to be doing a lot better than before, I'll wait before making the leap back to stock just for comparison.
Help me
I also have h910 model but when i tried to boot after dirtysanta 3 rd step it didnt boot into twrp..even though i tried to flash recovery with fastboot flash recovery command.
I m stuck and static screen is a mess..plz help me
Hi, I'm a bit of a novice at this, can you please explain this line:
"flashed my stock H910 ATT kernel from the file named bootbackup.img"
Where do I get this file, and how do I flash it?
titmus said:
Hi, I'm a bit of a novice at this, can you please explain this line:
"flashed my stock H910 ATT kernel from the file named bootbackup.img"
Where do I get this file, and how do I flash it?
Click to expand...
Click to collapse
you where supposed to back up your original filesystem you would have gotten it from there.
Hello everyone, looking for advice in how to return to factory firmware. First, a few bullets to condense the information, then an expanded explanation below. Any assistance would be appreciated.
TL : DR
-Xfinity Mobile GS8+, SM-G955U
-Phone boots and works fine
-When device was still on Nougat, the Oreo beta firmware update.zips were floating around
-Downloaded and installed via factory recovery said update.zips in succession
-Stuck on pre-release build, want to get back to official Verizon Firmware and receiving OTAs
-Current Build: R16NW.G955USQU2CRAD
-Desired Build: G955USQS5CRI4 (Verizon, 09.11.18)
-Tried flashing CRI4 package manually via Odin, Odin said no
-A few hours of Googling and reading through forums as etiquette demands I try first has led me to post this, never not been able to find a fix in the forums
-Plz help, will PayPal/GooglePay/whatever you a 12-pack of beer or whatever to whoever gets me back to factory
Things I've Tried:
-Factory reset
-Odin
-Smart Switch
-OTA
So I have a Galaxy S8+ purchased through Xfinity Mobile. I wasn't able to get into the Oreo beta officially offered through the Samsung Program, but there were update.zips floating around that allowed you to migrate to the pre-release builds. The samsung.firmware.science link above was relatively straightforward - pick your model, it had the latest official build, download an update.zip, and profit.
As the beta program progressed and various more final builds were released, these builds provided additional successive update.zips, until ultimately resting on what was the final version, build number R16NW.G955USQU2CRAD, which I am on currently. I use various forms of Package Disabler and had until recently kept a lot of Samsung's bloat disabled, including the OTA services. Note this only disables them and keeps them from running, not actually remove them from the phone.
Anyway, being an old ROM crackhead from back in the day when aftermarket ROMs actually provided significant software improvements over the garbage that OEMs ship on their phones, I don't like OTA updates that often because I prefer to factory reset after each update - the updates usually make the phone feel sluggish, which may be placebo, but here we are. In light of all the recent Android security vulnerabilities, despite not doing dumb stuff on my phone I figured it was time to go ahead and OTA to get the newest security patch. The issue is that my phone does not recognize any new OTAs despite being on a firmware build from January 2018.
I'm familiar with Odin, figure no big deal, grab the newest build for Verizon (Xfinity Mobile runs on Verizon towers, there's currently a Verizon sim in the device, and Xfinity Mobile builds seem to be entirely absent) and try to flash G955USQS5CRI4 dated 09.11.18. Verified through redundant sources this is, in fact, the latest Verizon build for the S8+.
Lo and behold, it doesn't work. Contacted Samsung regarding possible solutions, their chat agent wasn't very helpful, directed me to a local authorized repair store, who said they may or may not be able to flash it back with Samsung's software, and it requires what may be a two hour diagnostic that checks every possible thing it can on the device, and if it's not an official build, they will tell me to **** off, not withstanding the fact that the guy mentioned that the software from time to time glitches and crashes. My experience with flashing firmware makes me wary of what would happen during a system flash if the software crashes.
Anyway, for those of you who bothered to read past the TLR and embrace my dissertation, I've been out of the flashing game for a while, and because flashing factory firmware via Odin was my go to in the past, I'm not up to date on fixes for obscure issues. A few hours of Googling and reading through forums and I'm not anywhere closer than where I started, and I'd rather fix this myself rather than go to a store and potentially pay them for something that is "out of warranty."
Any ideas would be much appreciated, would gladly PayPal/Google Pay/Whatever someone a 12-pack of beer/$ to someone who can help me get this thing back to factory firmware.
Thanks in advance for any help.
From looking at your odin log almost looks like nothing was flashed, usually you will see abl.elf, modem, system.img, etc.... in the log while it's being flashed; After it checked the MD5 and started flashing it almost immediately closed it looks like but see no errors.
*After looking again I notice it says (success 0/fail 1) so it did not flash anything. Also make sure you are using the newest odin to flash
My suggestion, try flashing without USERDATA; When I flash I flash:
BL/AP/CP/CSC_OYM and not the HOME_CSC and never UserData
If that doesn't work try odin to G955USQU2CRC5 (Verizon 4/18) and then from there update to the latest update.
bmxmike said:
From looking at your odin log almost looks like nothing was flashed, usually you will see abl.elf, modem, system.img, etc.... in the log while it's being flashed; After it checked the MD5 and started flashing it almost immediately closed it looks like but see no errors.
*After looking again I notice it says (success 0/fail 1) so it did not flash anything. Also make sure you are using the newest odin to flash
My suggestion, try flashing without USERDATA; When I flash I flash:
BL/AP/CP/CSC_OYM and not the HOME_CSC and never UserData
If that doesn't work try odin to G955USQU2CRC5 (Verizon 4/18) and then from there update to the latest update.
Click to expand...
Click to collapse
Thanks for the response. I'm downloading the CRC5 file from Updato, and while the download speed is fluctuating, it's averaging around 50 KB/s with an ETA around 22~ hours. Is there a faster method to download this? I have a 300 Mb/s connection, so there's no bottleneck.
I'll try those steps in Odin, but can you expand on the reasoning so I understand the underlying mechanics? I was using the CSC_OYM and not the HOME_CSC, but why does this make a difference? Why never use USERDATA?
zerofighter1 said:
Thanks for the response. I'm downloading the CRC5 file from Updato, and while the download speed is fluctuating, it's averaging around 50 KB/s with an ETA around 22~ hours. Is there a faster method to download this? I have a 300 Mb/s connection, so there's no bottleneck.
I'll try those steps in Odin, but can you expand on the reasoning so I understand the underlying mechanics? I was using the CSC_OYM and not the HOME_CSC, but why does this make a difference? Why never use USERDATA?
Click to expand...
Click to collapse
I'm saying I have never flashed USERDATA as I've never seen it packed in most the roms I download, only other thing they have included is MAYBE a pit file for repartitioning. As for CSC:
Home_CSC: Flash the firmware without wiping the data (if you just want to update the ROM)
CSC: Flash the firmware along with a complete wipe including data (mostly used in cases like bricked phones or Go-Back-To-Stock situations)
I would try reflashing in download mode doing what I suggested and make sure that only reboot, nand erase, and f. reset are the only things checked.
As for downloads my suggestion is google try this:
site:androidfilehost.com G955USQU2CRC5
or
G955USQU2CRC5 filetype:zip (basing on the fact the roms I've downloaded all are zip format)
I think you can search from within the site, not sure. If you can find it always try download off filehost atleast I do because better speeds.
bmxmike said:
As for downloads my suggestion is google try this:
site:androidfilehost.com G955USQU2CRC5
or
G955USQU2CRC5 filetype:zip (basing on the fact the roms I've downloaded all are zip format)
I think you can search from within the site, not sure. If you can find it always try download off filehost atleast I do because better speeds.
Click to expand...
Click to collapse
https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-stock-g955usqu2crc5-odin-files-t3773033
I managed to find this under AT&T SM-G955U thread, is this of any significance? Okay to flash?
zerofighter1 said:
https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-stock-g955usqu2crc5-odin-files-t3773033
I managed to find this under AT&T SM-G955U thread, is this of any significance? Okay to flash?
Click to expand...
Click to collapse
Should have mentioned, the reason I'm asking is there is a discrepancy between the file size from Updato and this file - Updato file is 3.6~ GB and the one in this thread is 3.12~ GB.
No telling could be way it was compressed or files inside, like I said the rims I usually download don't include a USERDATA tar so maybe one has one and the other doesn't.
Have you tried again with what you have now?
There's been plenty of times I've tried to flash something to where I sometimes have to do it 3-5 times cause I over look something like under options (especially with resetting Odin cause when I do that it automatically enables partitioning for some reason). Also try a different USB cable, cause there should be something in Odin logs to lead you to problem; ex:
1 > 2 = This error usually means lower version Bootloader
Couldn't open file on XXXX: = Usually means partitioning was selected but no partition table given
Also if nothing else try flash in cosmey, I have yet to flash a v5 BL so I can't give you a this is what you need to do because my USB port is not working, but I've flashed from v1 to v3 in cosmey and have never had a issue with software only User Error (I'm trying to find a way to update from partycyborg to the same as you without Odin but cant because of my BL)
bmxmike said:
No telling could be way it was compressed or files inside, like I said the rims I usually download don't include a USERDATA tar so maybe one has one and the other doesn't.
Have you tried again with what you have now?
There's been plenty of times I've tried to flash something to where I sometimes have to do it 3-5 times cause I over look something like under options (especially with resetting Odin cause when I do that it automatically enables partitioning for some reason). Also try a different USB cable, cause there should be something in Odin logs to lead you to problem; ex:
1 > 2 = This error usually means lower version Bootloader
Couldn't open file on XXXX: = Usually means partitioning was selected but no partition table given
Also if nothing else try flash in cosmey, I have yet to flash a v5 BL so I can't give you a this is what you need to do because my USB port is not working, but I've flashed from v1 to v3 in cosmey and have never had a issue with software only User Error (I'm trying to find a way to update from partycyborg to the same as you without Odin but cant because of my BL)
Click to expand...
Click to collapse
Hey sorry, I've been busy working and haven't had the time to get back to this. I'm going to try this today and I'll get back to this post with an update.
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