Develop Bugs

SuperSU for broadband' sm-t805k/t805l/t805l

Hi, I am curious if anyone can answer this question.
I am a deliberation from obtaining the Tab S version SM-T805K/SM-T805S/SM-T805L launched in Korea with the Exynos 5433 processor. The article here explain this product: phonearena . com/news/Speedier-Samsung-Galaxy-Tab-S-with-Exynos-5433-processor-and-LTE-A-to-be-launched-soon_id61316.; this aricle has an inacccuracy probably from translation, but it supports 'broadband LTE-A', which combines three LTE bands, instead of two like the regular LTE-A for 1.5x increased throughput. Anyway, the release is similar to the Galaxy S5 'broadband LTE-A' with model number SM-G906(S/K/L)
Obviously chainfire's autoroot package for the SM-T805 doesn't work due to different processor.s However, it shares the same processor as the Note 4, so I am curious if there is a method to botain root suing existing downloads and by using TWRP. This amounts to a general question. Is root processor-specific? Does one of the root packages for Note 4 work? Or if a new root package needs to be written for the model altogether.
Please let me know your thoughts.

No the root method is not cpu specific, but it is device specific. However the TWRP method is not as long as there is a twrp version for your device that can be installed. This requires an unlocked boot loader, it's not common for Samsung to lock bootloaders. It's usually only US models that have locked bootloaders.
There is a firmware update for the SM-T805S at Samsung Updates, if you download it, extract the recovery image from it, send it to me and I'll build TWRP for your device.

ashyx said:
No the root method is not cpu specific, but it is device specific. However the TWRP method is not as long as there is a twrp version for your device that can be installed. This requires an unlocked boot loader, it's not common for Samsung to lock bootloaders. It's usually only US models that have locked bootloaders.
There is a firmware update for the SM-T805S at Samsung Updates, if you download it, extract the recovery image from it, send it to me and I'll build TWRP for your device.
Click to expand...
Click to collapse
Wow thank you so much! I have linked it here.
https: // drive.google. com/file/d/0B2CszRKCbxDSM0RuVHI4SHlfWTg/view?usp=sharing
Just for my own clarity, the TWRP version is not CPU or device -specific, but requires a version that can be installed; would you please care to elaborate?

Ah, there is some ambiguity in the thread.
So, the TWRP recovery itself is device specific? and then rooting can be done by sdcard method in TWRP with current version of chainfire's SuperSU zip?
Thank you.

To boot twrp or any recovery it has to be built for a device using files specific to that device such as the kernel. It has to built and configured so that the kernel can boot and then boot recovery. It needs to know the partition layout of that device and such things as the display resolution.

Ashyx is an awesome recovery builder. He built many recoveries such as a twrp mod and also twrp for snapdragon tab s. Without him, some devices may never gotten an custom recovery

I notice that the partition structure seems to be slightly different in the new version.
When you get your tablet I will need you to run a command on the device to get some info.
Hopefully then I can build it.

ashyx said:
I notice that the partition structure seems to be slightly different in the new version.
When you get your tablet I will need you to run a command on the device to get some info.
Hopefully then I can build it.
Click to expand...
Click to collapse
Just wondering, can it be done from the device itself (no ADB)? If so I can try to get someone to do this on a display model, but availability is questionable. Plus, for some reason, the SM-T805S model has mysteriously disappeared from the Samsung Korea website in the past couple weeks (http:// www.samsung. com/sec/consumer/mobile-tablet/tablet/filter/). The SM-T805K seems to be the most available.
This is the model I am most likely to get. If I got the SM-T805K is there a way to get a hand on the firmware through Kies or other means?
Could you post your commands here? Someone with the device is bound to read this forum and run the commands, but it may take a while. But who knows
Thank you for working on this! :good:

The s,k,l variable is probably just carrier variants. The actual part of the firmware I need is likely the same.

ashyx said:
The s,k,l variable is probably just carrier variants. The actual part of the firmware I need is likely the same.
Click to expand...
Click to collapse
Yes, they are are carrier variants (SK Telecom, KT Olleh, LG U+).
So, does it require ADB to do? what were the commands? :fingers-crossed:
(I spose PM if needed. Thanks!)

You can run the commands on the device itself. It would be best if you have the device because the output would be quite long so a screenshot would be best.

Sorry I havent gotten back sooner. I will report back here when I get the device. :silly:

No worries

Sorry to jump in. Just one question. If the tab is designed/locked for a specific carrier, is there a way to unlock it to any carrier without changing the original ROM?
Thinking of buying this model also, however, im not from Korea!
TQ

itman2000my said:
Sorry to jump in. Just one question. If the tab is designed/locked for a specific carrier, is there a way to unlock it to any carrier without changing the original ROM?
Thinking of buying this model also, however, im not from Korea!
TQ
Click to expand...
Click to collapse
I've read on other forums that people have used their korean-carrier device abroad with foreign sims without issue.
This si just a conjecture, but I wonder if we load a custom rom if the device would even be carrier locked anymore. If we delete the hidden.img and cache.img from the rom, if this would solve it? Also, I have seen rooted apps that claim to unlock your device. For me, I consider calling the carrier to have the device unlcoked an option as well.
Using this deivce in the United sttates it is more relevant to note the LTE bands. AT&T would be the only compatible arrier on band 17, and the network would not support LTE-A or broadband LTE-A, but LTE-A is only available in three cities as far as I know.
I am viewing this forum from the SM-T807 version, and the lag is ridiculous. I don't believe it is the bloatware...

eeekw0 said:
I am viewing this forum from the SM-T807 version, and the lag is ridiculous. I don't believe it is the bloatware...
Click to expand...
Click to collapse
This forum is terrible for lag, due to all the java crap and ads running on it. The stock browser deals with it the best imo.
However I use the XDA app which provides a smoother experience.

CF-autoroot test build
I have compiled a test build of CF-autoroot for this device. Feedback if it works or not please.
http://forum.xda-developers.com/galaxy-tab-s/development/root-t3087315/post60221952#post60221952
Custom recovery will come next.

eeekw0 said:
Hi, I am curious if anyone can answer this question.
I am a deliberation from obtaining the Tab S version SM-T805K/SM-T805S/SM-T805L launched in Korea with the Exynos 5433 processor.
Click to expand...
Click to collapse
Hv you bought the unit? Just wondering how you bought it?
TQ

itman2000my said:
Hv you bought the unit? Just wondering how you bought it?
TQ
Click to expand...
Click to collapse
I'm sorry to disappoint. No, I haven't. I was just thinking of getting one the next time I go. depending on the circumtances and this would give me time to do something with the 6 tablets that I currently have.
Ebay acquired a site called gmarket.co.kr a few years back where retailers in south korea sell crap online; shipping is only in-country, but the other obstacle is making payment; you owuld have to wire your funds internationally, but there are fees on top of fees depending on how many banks it has to cross separate from daily forex changes. The cost for a single unit would probably end up to be a thousand dollars. For the shipping, I know people who are among the 27,000 american military deployed over regions in south korea, and through them shipping can amount to a APO or FPO address with USPS Priority Mail.

ashyx said:
I have compiled a test build of CF-autoroot for this device. Feedback if it works or not please.
http://forum.xda-developers.com/galaxy-tab-s/development/root-t3087315/post60221952#post60221952
Custom recovery will come next.
Click to expand...
Click to collapse
oh wow. i didn't even realise this post until now. just curious, how long did it take?
i don't have the device but i will try to find someone who has it and is interested in rooting

Is there any way to upgrade the LRA model of the One M9 to Marshmallow?

It seems Bluegrass Cellular, (a regional carrier in my area) never approved the update to Marshmallow, and will probably never approve of the Nougat update. So, I'm stuck on Lollipop, but I'd like newer features and the security patches. If my only option is to do something like S-Off, are there any known RUUs that wouldn't break my functionality?
Thanks in advance, the work you guys do is awesome.

purplekid97 said:
It seems Bluegrass Cellular, (a regional carrier in my area) never approved the update to Marshmallow, and will probably never approve of the Nougat update. So, I'm stuck on Lollipop, but I'd like newer features and the security patches. If my only option is to do something like S-Off, are there any known RUUs that wouldn't break my functionality?
Thanks in advance, the work you guys do is awesome.
Click to expand...
Click to collapse
If it is a GSM variant, then converting your phone to the developer SKU would allow you to apply the Nougat RUU that is available. If it is a CDMA variant, you are almost certainly out of luck. Software for CDMA is pretty particular to the carrier and generally not applicable between device variants - to the point that attempting it will probably brick your phone.
Please post your OS version (Settings, About, Software Version) and we'll be able to get a better handle on what options are out there for your phone.

computerslayer said:
If it is a GSM variant, then converting your phone to the developer SKU would allow you to apply the Nougat RUU that is available. If it is a CDMA variant, you are almost certainly out of luck. Software for CDMA is pretty particular to the carrier and generally not applicable between device variants - to the point that attempting it will probably brick your phone.
Please post your OS version (Settings, About, Software Version) and we'll be able to get a better handle on what options are out there for your phone.
Click to expand...
Click to collapse
Android: 5.1
Software:2.6.512.17

purplekid97 said:
Android: 5.1
Software:2.6.512.17
Click to expand...
Click to collapse
Unfortunately, that SKU (512) confirms that your phone is a CDMA variant of the M9. I don't know of any upgrade path available to your device, apart from the carrier actually choosing to produce the software update. I'm sorry to be the bearer of bad news.

computerslayer said:
Unfortunately, that SKU (512) confirms that your phone is a CDMA variant of the M9. I don't know of any upgrade path available to your device, apart from the carrier actually choosing to produce the software update. I'm sorry to be the bearer of bad news.
Click to expand...
Click to collapse
That's unfortunate. Thank you for your input. Hopefully they'll make it happen eventually. I'll be sure the next phone I purchase will be fully supported by my carrier, or unlocked. I love my One M9 nonetheless.

Lg G7 firmware questions

well, thing is my device has a firmware from a carrier form mexico and i wanted to change it to get rid of those MANY apps it comes with. however, i ended up with some questions, i want a version that can give me OTA updates as they come out (this carrier takes a lot of time to realease updates) so as far as i could find the lm-g710em10b was a good option, but my model is a lm-g710awm, so...
1._ can i flash the g710em10b kdz on my g710awm model without having to worry about something in specific?
2._ Is that kdz version a good one or do you recomend another one for me?
3._ as far i know i do not need to unlock my bootloader to change my firmware, am i wrong?
hope you can help me, and thanks in advance hehe

Flashing generic Samsung firmware to carrier branded Tab S4 (SM-T837T -> SM-T835)

I think this has been asked before in a different way in this section but no real response yet. I did some research in the other Samsung device forums and see that often it is possible to remove branding or switch carriers adjusting device ID and bootloader etc. But no idea how to do it for the Tab S4.
I'm sick of waiting for slow updates through T-Mobile (or any carrier) and would like to fully unlock it's potential with Android 10 rather sooner than later. I bought this device second hand network unlocked.
Any short or long answer to these questions? Can it be done? If so where to start?

Am looking to do so, with the t835 you will have full calling functionality,,,
Cidious said:
I think this has been asked before in a different way in this section but no real response yet. I did some research in the other Samsung device forums and see that often it is possible to remove branding or switch carriers adjusting device ID and bootloader etc. But no idea how to do it for the Tab S4.
I'm sick of waiting for slow updates through T-Mobile (or any carrier) and would like to fully unlock it's potential with Android 10 rather sooner than later. I bought this device second hand network unlocked.
Any short or long answer to these questions? Can it be done? If so where to start?
Click to expand...
Click to collapse

Ramiyounan said:
Am looking to do so, with the t835 you will have full calling functionality,,,
Click to expand...
Click to collapse
not needing the calling function on a tablet. but steady updates are welcome... tired of waiting twice.. first for Samsung with slow update policies then another time for carriers that already got their money and cant care much a anymore...
i'd be looking for T835C since I'm in China now.

Cidious said:
Any short or long answer to these questions?
Click to expand...
Click to collapse
The short answer is no.
I've tried that after I found my T837V can be successfully loaded with T837R4/T837T/... firmware. I thought maybe I could flash stock firmware of other versions. But if you do that with any firmware other than T837*, you will get "secure check fail pit" error. So sadly no.

ivesun said:
The short answer is no.
I've tried that after I found my T837V can be successfully loaded with T837R4/T837T/... firmware. I thought maybe I could flash stock firmware of other versions. But if you do that with any firmware other than T837*, you will get "secure check fail pit" error. So sadly no.
Click to expand...
Click to collapse
Thanks for the response! So it does mean you can freely flash T837 versions which could mean I can just wait for the first version that comes out with android 10. Any first release should work. Right?
Turkey version has it:
https://www.sammobile.com/samsung/galaxy-tab-s4/firmware/#SM-T837

Cidious said:
freely flash T837 versions [/url]
Click to expand...
Click to collapse
T837 is Turkey version and I've tried it. It can't be loaded, maybe it need to be T837x which are all US variants.
As for Android 10 update, I think this will work. I'm waiting for the first one who gives the OneUI 2.1 update. So far the Verizon version(T837V) seems to have the most active firmware updates.

In the USA, SM-T837 ARE carrier tablets.
There are the SM-T837A, V, and T; ATT, Verizon, T-Mobile. TheSe are locked to the Carrier. If you have them unlock it, OTA upgrades are over. If you know how to hack the firmware, you can write over the carrier version. The best way to go is probably custom ROM AND ROOTING. But in other nations, it will probably work to write a different Samsung ROM. The SM-T835 HAS no US version, so you can probably write any tab s4 Factory ROM to it.
The USA HAS so many cellular devices, the rules are strict. And, the carriers sell the devices pretty cheap. So, they want them to stay with their service.

T-mobile update for android 10 finally out just got it

Question Missing features/failed software installation/corrupted software?

Copied from the OnePlus forums - no response yet so far
I recently got my new OnePlus 9rt, however I've ran into a few perplexing issues with the handset.
The first issue is that it is just outright missing the manual update option. No cog, no nothing.
The second issue which compounds to the first, is that every time I try to update the software to MT2111_11.A.07_2022031423170148, it fails. My current version is 11.3 according to the phone. Manually updating through the oxygen OS installer also fails. Which brings me to the next point..
The third issue is that under the model section of the phone, instead of saying the model of the handset, it says the model is Lahaina for arm64, which I'm quite sure it's not meant to be there. Everything else, build number, baseband version, kernel version (provided below) match the other handsets. However a cursory examination on this forum says that there were/are people on this forum with a similar issue to the second point.
So I'm wondering, is this ROM official? Or did I get a corrupted pre-install of the software on the phone? Or am I overthinking this?
Also messages don't delete completely in messenger app. You delete them, and then a second later they return.
For reference, here is the information..
Build number: MT2111_11_A.03
Baseband version: Q_V1_P14,Q_V1_P14
Kernel version: 5.4.96-qgki-g449ba87830ff
Thanks in advance

Where did you buy the phone from and what country are you in? Currently the handset is only officially sold in China and India.
Was the package completely sealed, or has it been opened? It sounds to me like you have been sold a handset from the Chinese market and it's had the unofficial Indian ROM flashed on it.
ie. this one https://forum.xda-developers.com/t/...xygenos-a-04-a-07-for-mt2110-devices.4404719/

I bought the phone from Kogan, and I'm from Australia. This isn't the first time I bought a OnePlus from there, but this is my first time with these issues specifically.
As for the package, it was sealed yes. And yes, those issues are practically identical with a few asides - such as the cog button missing. Such as that one..
Device name in settings displayed incorrectly "Lahaina for amd64" instead of expected "MT2111".
Yeah, that's 100% what it is.

Issue resolved, thanks!

Skywrath0135 said:
Issue resolved, thanks!
Click to expand...
Click to collapse
how to fix this? i have same problem