Develop Bugs

[Q] Unsure if my LG G3 is fixable, please say it is

Ok, so lets start with hello you wonderful smart people
I did something very stupid and I'm really hoping there is a solution to my foolishness.
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.

xSandmanx59 said:
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
Click to expand...
Click to collapse
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.

epidenimus said:
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
Click to expand...
Click to collapse
Thank you for the response. It's a surprisingly easy error indeed. Since I posted this, I figured out the key press you mentioned and have been trying ROM after ROM intended for my phone specifically, yet all of them will end one of 3 ways.
I get a black screen with itty bitty little text saying fastboot mode and restart.
I get everything ready and I boot up, it loads until about the wifi set up and then it will either freeze for a couple seconds and go to a black screen which requires a battery pull.
Or, I get a bsod with the options of volume up = dload and volume down = reboot.
So far I've tried candy5, CM 12.1/11, blisspop, paranoid android, cloudy, and dirty unicorn.
Not sure what I'm doing wrong with these. I use TWRP to wipe everything except external sd, install from there, reboot, and repeat.

I fixed it!! thanks to http://forum.xda-developers.com/sprint-lg-g3/development/rom-stock-zv6-base-odex-deodex-t2949087
this ROM is the only one I could find that worked. I'd still love to be able to upgrade to L but it seems like all of the 5.x roms crash during setup. Not sure what this is due to, but I have a working phone, so I'm not too upset by it.
If anyone has any info on why all the lollipop ROMs are having trouble on here I would appreciate it much.

Well it WAS fixed.... All was fine and well until there was a software update, I clicked install, it tried to reboot, and now I'm stuck in a custom recovery boot loop. I still can't connect to either of my PCs by USB and using my SD card to flash ROMs isn't doing anything now, just boots straight into TWRP every time, after full wiping and re-flashing several times now I'm really not sure how to fix this one.

Update:
Got past the bootloop from another thread on here which had a flashable fix. Now that I did that I'm actually able to use 5.x ROMs it seems. Currently working on Blisspop 3.5, once I get GAPPS to flash correctly, I think I aughta have a working Lollipop phone

Make sure you are using the correct TWRP for your device, having Bumped, as needed. Also, make sure you use the correct version of Gapps; it matters based on the version of Android your ROM is based upon.
Good luck and enjoy!

Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.

xSandmanx59 said:
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Click to expand...
Click to collapse
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
xSandmanx59 said:
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
Click to expand...
Click to collapse
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?

epidenimus said:
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
Click to expand...
Click to collapse
Thank you for the response. I have noticed that a few small things are not so frequently updated in the copy/paste updates of the ROM threads. But that's to be expected =P Anyways, to answer your questions:
What are the driver's requirements? These are more variables associated with Windows...
I'm not entirely sure about this one. I know I found the drivers on the LG website for my LS990 model and I also installed a few others including older/latest/various models to test if any of them would work. I'm running windows 8.1 currently and the ls990 seems to have a little less support as the PC suite for LG doesn't include this model in their driver list.
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
Yes, it's been a long running issue on stock, stock rooted, and blisspop all with debugging on. I was able to connect to both of my computers for a long while until one day it just stopped. It was much worse than it is now. For a few days, then it decided to charge up to about 4% when I plugged it in with no battery and then put the battery back and waited for about 3-4 hours. Then I could turn it on long enough to selectively power down and it would then charge while powered off. Over the past couple days I've been able to plug it in and reboot to get it charging again... So bothersome. As for USB debugging, not sure when it stopped exactly but I assume it was around the same time (2 months ago)
What version of the Android SDK/Studio are you running?
I have the latest version of android studio from their website.
Have you added the platform-tools to the SDK, as required?
Yes, I believe so. I'm not 100% on the SDK stuff.
Can you get ADB to recognize the device when you connected and are in TWRP?
No. There is no response from my computer at all during any of the stages of driver and twrp and studio installations. Nothing is listed in my device menu either.
Beyond this, today my phone ran out of battery while I was out and about and then has refused to charge by any method. Then I finally got it to turn on to power down etc so it would charge about 3 hours later. Once I was able to boot back up I went out to smoke and came back to my phone somehow automatically flashing a different version of blisspop that had something about user_modified in the file name which then unloaded all of my saved layouts and whatnot. After about 20 minutes of reorganizing it went black, and has since been locked in a bootloop which has survived full wipes and re-installations of the previous version of blisspop I had been using. I just downloaded the latest version for ls990 once more, and I'll report back with whether or not that fixed the issue at hand.

[Q] SM-T805 - Unleash the tab ?

Hello,
I bought a second hand SM-T805 tab, mainly as a multimedia reader. The device itself is great, but the software turns out to be a real downer. So much uneeded stuff just sucking up battery time. Thus, I'm wondering what can be done to alleviate that. I'm fairly experienced with linux, recently hacked a zyxel nas to boot a custom debian, but a complete android noob. I mean come on: where is my console ?
So good advices are very welcome
For an instance, would it be possible to run a clean and fast kernel on that device, offering all drivers (cam, sound, touchscreen and so on), with a speedy interface, console command and nfs/samba support ? How about a stock android only patched with samsung drivers ? What would be the drawbacks compared to stock samsung software.
Than comes the question how it's done. Are there any complete guides on this forum about flashing an sm-t805 ? Any reasons why I should think twice about doing so ? Would it be possible to return to stock samsung afterwards ?
So many questions! Thank you for your help,
qwerkus

qwerkus said:
Hello,
I bought a second hand SM-T805 tab, mainly as a multimedia reader. The device itself is great, but the software turns out to be a real downer. So much uneeded stuff just sucking up battery time. Thus, I'm wondering what can be done to alleviate that. I'm fairly experienced with linux, recently hacked a zyxel nas to boot a custom debian, but a complete android noob. I mean come on: where is my console ?
So good advices are very welcome
For an instance, would it be possible to run a clean and fast kernel on that device, offering all drivers (cam, sound, touchscreen and so on), with a speedy interface, console command and nfs/samba support ? How about a stock android only patched with samsung drivers ? What would be the drawbacks compared to stock samsung software.
Than comes the question how it's done. Are there any complete guides on this forum about flashing an sm-t805 ? Any reasons why I should think twice about doing so ? Would it be possible to return to stock samsung afterwards ?
So many questions! Thank you for your help,
qwerkus
Click to expand...
Click to collapse
Install stock lollipop from odin and after that install TWRP with odin. I recommand this rom: IronRom. There is also a description about how to do this thing here, take a look

qwerkus said:
Hello,
I bought a second hand SM-T805 tab, mainly as a multimedia reader. The device itself is great, but the software turns out to be a real downer. So much uneeded stuff just sucking up battery time. Thus, I'm wondering what can be done to alleviate that. I'm fairly experienced with linux, recently hacked a zyxel nas to boot a custom debian, but a complete android noob. I mean come on: where is my console ?
So good advices are very welcome
For an instance, would it be possible to run a clean and fast kernel on that device, offering all drivers (cam, sound, touchscreen and so on), with a speedy interface, console command and nfs/samba support ? How about a stock android only patched with samsung drivers ? What would be the drawbacks compared to stock samsung software.
Than comes the question how it's done. Are there any complete guides on this forum about flashing an sm-t805 ? Any reasons why I should think twice about doing so ? Would it be possible to return to stock samsung afterwards ?
So many questions! Thank you for your help,
qwerkus
Click to expand...
Click to collapse
- console command: you can use Terminal Emulator app.
- you can always return to stock by flashing stock firmware via Odin.

Thank you for your replies. I found this page: http://forum.xda-developers.com/galaxy-tab-s/general/index-galaxy-tab-s-t3149566 It seems to sum up the possibilites offered on xda-devs for the sm-t805. Yet still miss documentation: why would I do what, how does the samsung stock software work and so on. For an instance, I got a cheap sd card - can't I boot to it and install a custom OS there, why leaving the stock rom untouched ? Flashing is always a tricky operation, which I would not recommend unless really necessary, especially when other storage medium is present.

Mi A2 Lite Stuck on Android 8.1 - What am i doing wrong?

Hi everybody,
i have a new Mi A2 Lite. I purchased it from a private person, not a shop, but it was still in foil and opened by me. It works nicely, is fast, the phone feels fine, i like it. It has AndroidONE, Oreo, on it. If i search for updates, it tells me that it is up to date and there are no updates. The same for the security patches - they are from nov. 2018, which is nearly a year ago, but there are no updates either.
I wanted to install android 9, so i did lots of tricks and things like using a VPN to poland and resetting the phone and so on, but to no avail - there are no updates.
so...
(1) is there something that can be done wrong? why wouldnt the phone find updates?
(2) is there a way to flash the official OTA zip without unlocking? I do not want a special kernel or rom, i dont want to modyfy anything on the os, i just want the official, latest os on the phone
(3) Any other ideas?
Thanks in advance

damaltor said:
It has AndroidONE, Oreo, on it. If i search for updates, it tells me that it is up to date and there are no updates.
Click to expand...
Click to collapse
Hi!
Could you please share a screenshot showing your actual Android build number and kernel version? You might have a fake A2 lite (Redmi 6 Pro).
Edit: Don't flash anything before you're sure that your device is a geniue A2 lite, otherwise you will brick your device.

yep, i heard about that. unfortunately, i did flash it by now, but the flash worked perfectly. i unlocked the bootloader with fastboot, flashed the last fastboot package, and re-locked the bootloader. the device is now on android pie and it still works nicely. is there any way to find out if it is genuine after flashing?

So, now i can say the following:
- the deveice works still well with the flashed software.
- the device did just find and download the google security patches of sep 2019
- the imei of the device passes the xiaomi authentication test
so, i am somewhat sure that the device is an original.
still, i am interested why the device was stuck on the old version. maybe it could only handle incremental updates and the old incremental update was not available anymore?

Hi!
I have simmiliar issue. New, 100% original Mi A2 Lite. It downloaded 1GB update 8.0 to 8.1 (?), but no update for Android 9, and now it is stuck.
My screens:
ibb.co/SKjNJ6D
ibb.co/YR4793D
Regards!

Facing The same in my Mi A1
The same thing is happening with my Mi A1, I have Android 8.1 an I hadn't update to Android 9. Every day the notification for Android 9 would appear in my phone, saying that is available.
Today that update didn't show and when I checked for updates, it said I was already up to date.
Sorry for my English, I barely know it

Well i could probably Help you to flash your device but you should be sure that the device is not a fake, too. I cannot help you with that though. I will look in here tomorrow and give you a few hints to the flashing process.

So, the screenshots of the A2 Lite look pretty mich exactly like mine did. for me the only way was to reflash the device. if you are interested, i can tell you how, but there is a risk of bricking your device if it is a fake a2 lite. i cannot tell by your screenshots, maybe @thorin0815 can?
Otherwise, do you want to try it and risk ist?
edit: you can put in your imei here to check your phone, though i would not entirely trust it.
https://www.mi.com/global/shield#imei_en

*Deleted* *replay *

chriss7777 said:
Hi!
I have simmiliar issue. New, 100% original Mi A2 Lite. It downloaded 1GB update 8.0 to 8.1 (?), but no update for Android 9, and now it is stuck.
Click to expand...
Click to collapse
You're right, your device looks like a geniue A2 lite. We never had an update from 8.0 to 8.1, it was shipped with 8.1.
Maybe Xiaomi pulled the incremental (8.1->9.0) OTA updates from their servers.
The "safest" way to update would be to flash the latest available full firmware via Miflash tool.

well, thats what i did. fortunately there is no longer the need to wait for hours or days to unlock the bootloader, it works in an instant now even without registration.

thorin0815 said:
You're right, your device looks like a geniue A2 lite. We never had an update from 8.0 to 8.1, it was shipped with 8.1.
Maybe Xiaomi pulled the incremental (8.1->9.0) OTA updates from their servers.
The "safest" way to update would be to flash the latest available full firmware via Miflash tool.
Click to expand...
Click to collapse
I did not notice what update it was downloading. I unboxed it, then I connect to WiFi and it started downloading. Anyway it downloaded aprox. 1GB of data, then restart and update. And now it is stuck with 8.1. I thought it will be Android 9 after update with latest patches.
I validate IMEI's on site and it is valid, also it has all google logos, and so on.
Is there any comprehensive update manual for MiFlash for this model?

Well, Not that I know of one that is really complete and up to date. But here you are (own phone, own risk!). Back up your phone first!
Switch on your phone.
Go to settings, about phone.
Tap the build number multiple times until "you are a developer".
Open the developer options.
Switch on USB debugging.
Switch on "allow unlocking bootloader".
Leave settings.
Download this, and install it, answering yes to all three questions:
https://forum.xda-developers.com/showthread.php?t=2588979
Connect the phone and when asked, accept the adb debug question on your phone. Your computer is now allowed to debug your phone.
Also download your new os from here:
https://xiaomifirmwareupdater.com/miui/ (put your phone model in there and download the latest fastboot image)
Unpack it. Depending on your packing program you might have to unpack twice - you should have a few folders and files.
Download the mi flash tool here:
https://www.xiaomiflash.com/
Now you are ready. Take a deep breath. Make sure your phone is charged, 50% should be enough.
Disconnect and Switch off the phone. Hold volume down and power until a rabbit working on an Android robot is seen on the screen. Now reconnect the cable.
Open a command window on the computer by pressing windows+R and entering "cmd".
In that window, type "fastboot oem unlock" and press enter. You should get the answer "OKAY".
If your phone reboots now, hold volume down and power again until the rabbit is there again.
Start miflash. Show miflash the folder in which you unpacked the os files.
In the lower right select "clean and lock" and then press update, select your phone, and press flash.
Flashing now takes roundabout 5 minutes.
Afterwards your phone should reboot into Android 9. Your data will be gone (though my phone managed to keep a few of it's settings for some reason).
Good luck!

damaltor said:
Well, Not that I know of one that is really complete and up to date. But here you are (own phone, own risk!). Back up your phone first!
Afterwards your phone should reboot into Android 9. Your data will be gone (though my phone managed to keep a few of it's settings for some reason).
Good luck!
Click to expand...
Click to collapse
It works like a charm. Also now it is updating with new security patch. Thanks damaltor!

No problem, good to hear that it worked!

[GSI][UNOFFICIAL] Descendant 4.0.1 Modified [Stable][XT1952-2]

MODIFIED EXCLUSIVELY FOR MOTO G7 PLAY
WARNING
Do not try to install this via fastboot, remove the magisk, to remove just reinstall the Stock Rom
MAIN FEATURES
Added apps
Battery usage statistics working
BusyBox already installed
Gapps already installed
More speed
More battery
Notch fix
Root modified by Spaceminer
Several useless apps removed
Tweaks
And more
DOES NOT WORK
Fingerprint
Automatic brightness
NAVIGATION BAR
If the navigation bar disappears, activate it in the configuration
INSTALLATION INSTRUCTION
1. Download and extract
2. Put the GSI on your memory card
3. Restart your phone in Bootloader / Fastboot mode
4. Open fastboot on your computer
use the command: fastboot -w
use the command: fastboot boot twrp.img
5. TWRP: Install> Install image> Choose image file> Flash on the system
DOWNLOADS
TWRP by Spaceminer: https://mega.nz/file/roRzBCTK#THHq0VMWqgtowJNkY-Id3b9S9H9dhzsJhE83k0Kvt2k
GSI: https://drive.google.com/file/d/1-2L4Hl8iUgHqb-ER0TVggjHsVZQEz8G-/view

Wow, incredible!! Please continue with the work, the system is perfect, thank you very much !!

Thank you for this! Is there a way to remove root on this? I want to see if I can use Magisk instead.

Is there going to be an android 10 build?

Not work lockscreen for me.

wanderleiAlfa said:
Not work lockscreen for me.
Click to expand...
Click to collapse
You need an encrypted data partition, but sadly this means TWRP can't read data, and it wont boot when installed, only through fastboot boot twrp.img

Thanks, i will try.

Adb shell
su 0
/system/bin/phh-securize.sh

Working well on the xt1952-4. Got Magisk installed as well, and disabled the phh-supersu app and a couple other apps I've never heard of. The auto brightness and fingerprints, is that something fixable in the near future? I will l likely keep for a daily driver ROM, especially with those fixes.. Either way, thanks for the ROM here. Worked when other GSIs failed. ?

Anybody has tested this gsi with xt1952-6 variant?

Anybody got this working on boost mobile when the rom setups it says sprint I tried to input the boost apn settings I always use with android 10 GSIs that always works and it’s not working here I can’t get data working on any android 9 GSI at least this one shows a Provider in mobile data other pie GSIs just show 31000 in mobile data I just need this to work I can’t install gps joystick as a system app in Q GSI roms to use system mode but it works in pie ROMS I use it together with smali patcher to avoid rubberbandin

theburrus1 said:
Working well on the xt1952-4. Got Magisk installed as well, and disabled the phh-supersu app and a couple other apps I've never heard of. The auto brightness and fingerprints, is that something fixable in the near future? I will l likely keep for a daily driver ROM, especially with those fixes.. Either way, thanks for the ROM here. Worked when other GSIs failed. [emoji854]
Click to expand...
Click to collapse
Was you able to get smali patcher to work everytime I run the tool I get this error with this rom but with other roms I can run smali patcher with no issue....
([emoji88]Descendent GSI[emoji88])

@PoochyX, in fastboot mode, try configuring the /carrier partition and /fsg to Boost Mobile.
fastboot oem config carrier boost
fastboot oem config fsg-id boost
I have not yet tried this ROM on my Boost device. But those config commands have worked on my other Moto devices when using custom ROMs. Just an idea. These commands prompt the /utags partition to configure the device to specific mobile providers, such as Boost Mobile, Virgin Mobile, etc.

I got it i had to upgrade modem back to android 10 and then data configured properly

PoochyX said:
I got it i had to upgrade modem back to android 10 and then data configured properly
Click to expand...
Click to collapse
That's good to know @PoochyX. Thanks for confirmation on that. By upgrading the modem back to Android 10, I'm assuming you mean the stock Android 10 Retail firmware. Are you referring to NON-HLOS.bin only or NON-HLOS.bin and fsg.mbn? Thanks again.

Viva La Android said:
That's good to know @PoochyX. Thanks for confirmation on that. By upgrading the modem back to Android 10, I'm assuming you mean the stock Android 10 Retail firmware. Are you referring to NON-HLOS.bin only or NON-HLOS.bin and fsg.mbn? Thanks again.
Click to expand...
Click to collapse
Yeah the issue is if you have upgraded to android 10 then you have to use the android 10 modem & fsg with android 9 and Android 10 GSIs (and also u would get signal issues with a android 9 modem on android 10 (even if u didn't upgrade to stock 10 to have to revert to a android 10 modem) also the android 10 DSP bin (adspso) or you won't hear anything when you call somebody but the android 9 dtbo cause android 9 GSIs won't boot with android 10 dtbo but android 10 GSIs can boot with android 9 dtbo...
([emoji88]Descendent GSI[emoji88])

PoochyX said:
Yeah the issue is if you have upgraded to android 10 then you have to use the android 10 modem & fsg with android 9 and Android 10 GSIs (and also u would get signal issues with a android 9 modem on android 10 (even if u didn't upgrade to stock 10 to have to revert to a android 10 modem) also the android 10 DSP bin (adspso) or you won't hear anything when you call somebody but the android 9 dtbo cause android 9 GSIs won't boot with android 10 dtbo but android 10 GSIs can boot with android 9 dtbo...
([emoji88]Descendent GSI[emoji88])
Click to expand...
Click to collapse
That's really good info to know. Thanks as always, @PoochyX.

Can't flash TWRP attempt #3983532, SM-T830

FYI I'm definitely a newbie to android and had 0 knowledge of any of this when starting so this very well could be something stupid and easy I'm missing..
Device: Samsung galaxy tab S4 wifi version SM-T830 (Now on android 10)
Cliff notes:
I was on android 8.1.0 (oreo), tried rooting via a patched root(?) i think it's called, without twrp using magisk. magisk showed it was not rooted
Tried flashing TWRP still on oreo, odin showed a failure to flash with no other information, just the standard (<OSM> All threads completed. (succeed 0 / failed 1))
I tried different odin and twrp version combinations with the steps above, i couldn't find which version of odin to use on oreo as their docs seem to list every android version but oreo and had other people suggest maybe not using the latest TWRP since I wasn't on the latest version of android. None of the combos worked
Finally got updated to android 10 today, using one of the latest odin versions (3.14.1) and a couple different TWRP files found either on twrp.me or on here (twrp-3.5.0_9-0-gts4lwifi.img.tar / TWRP_T83x_3.4.0-6.tar) but still nothing, same message in odin.
One last thing that might be helpful is that I only just updated today to android 10 because by some magic my device finally showed updates in the settings of the tablet itself. Previously I had tried samsung's smart switch which found updates but got stuck on 0% for the install the 50 times i tried it. I'm also still unclear as to how I'd flash a custom recovery(?) to get myself to a good version of android. I know how to in odin but I don't know where I can find trustworthy files that will work for my device. I've downloaded some with Frija but have been nervous about trying it as I'm just too new to this to know if that's always safe to do or if I'd cause more issues..
So yeah sorry that was still long, shortest version: Can't flash TWRP no matter what I do. Does anyone have ideas on what else I can try or does anything stick out as blatantly wrong? I'm at such a loss with all of this.

I find it hilarious that after like a week and a half 5+ hour days trying to figure this out, i finally give in and post my question. Within 30 min I find the answer and flashing works lol... I saw user Mentalmuso mention in one post, if Odin errors to restart the device and PC. Go figure, that worked. How stupid that you have to completely shutdown your workspace on error lol! Anyway hope someone facing the same issue sees this. Good luck!