[Ask Any Question][Newbie Friendly]

[plegdroid]

I don't understand the question, but device was definetly upgraded to 7.1.1.

Would suggest, that when Samsung originally released this tab, it came from the factory with android 5 installed. To recover it back to the factory state, you may have to downgrade to upgrade.

 

[bojan.1995]

Wow thats awesome

Could I just flash stock Firmware 5?
Not the one you linked?


I just found out it was on Austria css but they don't know which Telekom. (like 5min ago)
They gave me some email.


Edit:
I tried flashing with Pit British FW 7.1.1 and it failed 20min ago.

Edit 2:
I must admit I didn't chat with such a kind member for a while on the forum.

Edit 3:
the original plan was to root it... and look what happened

 

[plegdroid]

Wow thats awesome

Could I just flash stock Firmware 5?
Not the one you linked?


I just found out it was on Austria css but they don't know which Telekom. (like 5min ago)


Edit:
I tried flashing with Pit British FW 7.1.1 and it failed 20min ago.

Edit 2:
I must admit I didn't chat with such a kind member for a while on the forum.

Think stock ota updates only went up android 6. The issue could be the 7.1.1 pit, which could be a custom pit to repartition the tab to make room for a 7.1.1 rom. If you want to get back to stock, you would need also the stock pit to re partion system back to it's original size too

 

[bojan.1995]

Think stock ota updates only went up android 6. The issue could be the 7.1.1 pit, which could be a custom pit to repartition the tab to make room for a 7.1.1 rom. If you want to get back to stock, you would need also the stock pit to re partion system back to it's original size too

I extracted PIT myself from 7.1.1 stock rom - British.

I downloaded rom from galaxy firmwares site.

First time I tried flashing this rom or German... I don't remember anymore, it went up to 90% and failed. It was only 1 file for AP


Edit:
If stock ota went to 6.0 how did I have 7.1.1 stock today
(I tried to root and bricked today)

Maybe if I flash your 5.0 or try to flash Austrian 5.0 with extracted PIT from that rom.
And then root it (I read it's easier to root this device lower then 7.0)
and then flash 6.0 + root again.
Since it's so hard to root it on 7.1.1 (idk why).

Many people had this problem on 7.1.1

 

[prsco424298]

it's almost July and my unlocked s21 ultra on Verizon has received jack sh*t updates and my phone still says im on may security update. can I take another carrier firmware and flash just the rom and leaving the csc u touched

 

[bojan.1995]

it's almost July and my unlocked s21 ultra on Verizon has received jack sh*t updates and my phone still says im on may security update. can I take another carrier firmware and flash just the rom and leaving the csc u touched

Instant brick.
Like the moment you think about that idea it would be bricked 100%

You could root and delete bloatware

 

[plegdroid]

I extracted PIT myself from 7.1.1 stock rom - British.

I downloaded rom from galaxy firmwares site.

First time I tried flashing this rom or German... I don't remember anymore, it went up to 90% and failed. It was only 1 file for AP


Edit:
If stock ota went to 6.0 how did I have 7.1.1 stock today
(I tried to root and bricked today)

Maybe if I flash your 5.0 or try to flash Austrian 5.0 with extracted PIT from that rom.
And then root it (I read it's easier to root this device lower then 7.0)
and then flash 6.0 + root again.
Since it's so hard to root it on 7.1.1 (idk why).

Many people had this problem on 7.1.1

Yes try the android 5,pit. Think of it as, if the tab was up and working, and for what ever reason, you decided to do a factory reset, it would reset back to android 5. Then it would sequentially update to 6 via ota, then again to 7.1.1 (genuinely throught it only went upto 6) as its currently broken, its worth trying

 

[bojan.1995]

Yes try the android 5,pit. Think of it as, if the tab was up and working, and for what ever reason, you decided to do a factory reset, it would reset back to android 5. Then it would sequentially update to 6 via ota, then again to 7.1.1 (genuinely throught it only went upto 6) as its currently broken, its worth trying

Could you help with a link for Rooting 7.1.1 version?

 

[plegdroid]

Could you help with a link for Rooting 7.1.1 version?

Why not root it at 5, and then install a custom 7.1.1 rom with custom recovery (if there are custom roms available)

 

[bojan.1995]

Why not root it at 5, and then install a custom 7.1.1 rom with custom recovery (if there are custom roms available)

Exactly, no custom rom with working sim
Thats why I thought staying at 6.0 is best option for rooted device.

 

[plegdroid]

Exactly, no custom rom with working sim
Thats why I thought staying at 6.0 is best option for rooted device.

Stay with 6, but it will be resorected, dare say, once its up and running, you'll have choices again

 

[prsco424298]

Instant brick.
Like the moment you think about that idea it would be bricked 100%

You could root and delete bloatware

can't root it it's a Qualcomm unlocked I bought directly from Samsung to use on Verizon. the bloat ware isn't the problem I just want the June update

 

[DiamondJohn]

I don't understand the question, but device was definetly upgraded to 7.1.1.

Would suggest, that when Samsung originally released this tab, it came from the factory with android 5 installed. To recover it back to the factory state, you may have to downgrade to upgrade.

I'd be careful about downgrading, do some checks. I know it was only one device, but I personally had a Moto X 1052 that became known for hard briking if you downgraded. Once bitten...

 

[prsco424298]

the device is only on the may 2022 security update and its almost July and haven't gotten the June 2022 security update in looking to flash a different carrier that HAS gotten the June 2022 security update

 

[SubwayChamp]

it's almost July and my unlocked s21 ultra on Verizon has received jack sh*t updates and my phone still says im on may security update. can I take another carrier firmware and flash just the rom and leaving the csc u touched

can't root it it's a Qualcomm unlocked I bought directly from Samsung to use on Verizon. the bloat ware isn't the problem I just want the June update

the device is only on the may 2022 security update and its almost July and haven't gotten the June 2022 security update in looking to flash a different carrier that HAS gotten the June 2022 security update

I think CSC have much to do with updates, without changing CSC, the firmware switch is useless?, so, yet to determine, if the culprit is the carrier or the CSC, then you may opt for the non-carrier XAA firmware or other from the few compatibles for Verizon, as I don't live in US, not sure if the XAA or the others CSCs, suite perfectly well with the Verizon services, anyway, this deserves more research, from what I heard, in newer devices (S21/U, N10+, N20) Samsung blocked real changes to the CSC, either by stripping binary panic, or when detected the SIM card, all related to that carrier remains there.

If all of that is nearly true, you may try with, flashing a different firmware, matching the same or newer binary version, pulling out your SIM card, and checking for updates.

 

[bojan.1995]

Why not root it at 5, and then install a custom 7.1.1 rom with custom recovery (if there are custom roms available)

It worked with stock 5.0 in odin.
I didnt used pit.

But I can't find root now

 

[Artuditto]

TWRP KEEP BRIKING MY PHONE

Hi! I got a problem with my Xiaomi Redmi 3s and TWRP, i already read all the Redmi 3 XDA forum and look tons of tutorial but no luck so far.

I use this phone exclusively to play pokemon go (no root) but this week a new update ask for android 7 or better to run the game, since the only official ROM is up to android 6 i try to install a custom ROM, everything was ok, i install TWRP but then i was unable to find the install archive of Magisk (i try to root first), i can see every folder but not a single file using TWRP install, but if i use the TWRP Advanced/File Manager i find the file without problems but of course, i can't install from there. Anyway, as soon as i reboot and try to enter my phone the phone brick and stay in the "mi" logo screen. I can unbrick the phone easily with MIFLASH and reinstalling a official ROM so no problem for that, i already try with 2 versions of TWRP and 2 official ROM (MIUI 7.5.8.0 and 10.2.2.0) but the same problem keep happening. Also, i create backups but even after the backup is restored the phone brick again as soon as i leave TWRP. By the way, not sure if it's relevant but the phone was probably rooted in the past, i buy the phone used and without root but i can tell because the SuperSU folder still exist.

TIA and sorry if i made some mistakes, my english is not the best.

 

[SubwayChamp]

It worked with stock 5.0 in odin.
I didnt used pit.

But I can't find root now

Probably you can flash Magisk directly through TWRP https://androidfilehost.com/?w=search&s=t555 or patch the firmware, and flash it through Odin.

 

[SubwayChamp]

TWRP KEEP BRIKING MY PHONE

Hi! I got a problem with my Xiaomi Redmi 3s and TWRP, i already read all the Redmi 3 XDA forum and look tons of tutorial but no luck so far.

I use this phone exclusively to play pokemon go (no root) but this week a new update ask for android 7 or better to run the game, since the only official ROM is up to android 6 i try to install a custom ROM, everything was ok, i install TWRP but then i was unable to find the install archive of Magisk (i try to root first), i can see every folder but not a single file using TWRP install, but if i use the TWRP Advanced/File Manager i find the file without problems but of course, i can't install from there. Anyway, as soon as i reboot and try to enter my phone the phone brick and stay in the "mi" logo screen. I can unbrick the phone easily with MIFLASH and reinstalling a official ROM so no problem for that, i already try with 2 versions of TWRP and 2 official ROM (MIUI 7.5.8.0 and 10.2.2.0) but the same problem keep happening. Also, i create backups but even after the backup is restored the phone brick again as soon as i leave TWRP. By the way, not sure if it's relevant but the phone was probably rooted in the past, i buy the phone used and without root but i can tell because the SuperSU folder still exist.

TIA and sorry if i made some mistakes, my english is not the best.

Not sure what root solution you are asking for, if it is for SuperSu, better forget it, if it is for Magisk, then you just have to change the file .zip extension for .apk, although some custom recoveries can detect perfectly the Magisk.apk to flash it through it.
Flashing the Magisk file through TWRP will work perfectly, in this model, after that, reboot device and install the Magisk file as a normal apk, open it, and let it doing its thing.

 

[Artuditto]

Not sure what root solution you are asking for, if it is for SuperSu, better forget it, if it is for Magisk, then you just have to change the file .zip extension for .apk, although some custom recoveries can detect perfectly the Magisk.apk to flash it through it.
Flashing the Magisk file through TWRP will work perfectly, in this model, after that, reboot device and install the Magisk file as a normal apk, open it, and let it doing its thing.

Thank you but i'm not asking about root, my problem is TWRP briking my phone, when i install TWRP on my phone i'm unable to find any file with the install option of TWRP, any file like pictures, temp or other apk, not only magisk (if i use the option TWRP advanced/file manager the file is show tho, but i can't install from file manager), and then, when i exit TWRP, my phone stay in the "mi"logo screen every time, i'm able to un-brick the phone installing a official ROM with MiFlash, but if i try to install/use again TWRP the same problem repeat and brick my phone again, i already try 2 different versions of TWRP and 2 ROM.