Database Info

SM-T235 / SM-T235Y Tab 4 7" - ROOTED - TWRP Recovery 2.8.7 for SM-T235/235Y (LTE)

SM-T235 / SM-T235Y Tab 4 7" - ROOTED - TWRP Recovery 2.8.7 for SM-T235/235Y (LTE)
UPDATED 7/30/2015 with OFFICIAL TWRP 2.8.7 for Galaxy Tab 4.7.0 SM-T235(Y) DEVICES​As with other TWRP's for newer Samsung devices, you need to uncheck auto-reboot and F.Reset time in Odin so you can manually shut down the device and boot into recovery the first time after flashing the custom recovery. If you don't boot into the custom recovery immediately after flashing it to the device, then the OS will overwrite it with the factory recovery and you'll need to start over.
DISCLAIMER :
While we all love to flash new things, You and You alone can choose or choose not to flash this custom recovery.
I am not liable for any of the following : Bricks, Soft Bricks, Meltdowns, loss of data, or damage to your device.
DISCLAIMER #2:
THIS RECOVERY WILL TRIP YOUR KNOX COUNTER - YOUR WARRANTY WILL BE VOID.
THIS RECOVERY IS ONLY FOR SM-T235 and SM-T235Y Tab 4 7" LTE Devices
INSTRUCTIONS​1). Download Odin3v1.85.zip, recovery.tar.md5.zip, and UPDATE-SuperSU-v2.46.zip - all attached
2). Unzip Odin3v1.85.zip placing the extracted folder somewhere on your PC you can find and execute Odin3 from later.
3). Store UPDATE-SuperSU-v2.46.zip somewhere on your SM-T235's external SD storage where you can find it from TWRP later.
4). Unzip recovery.tar.md5.zip placing the extracted file recovery.tar.md5 somewhere on your PC you can find it from Odin3 later.
5). Put SM-T235 tablet in Download Mode (Power Button+Volume Down+Home Button)
6). Flash recovery.tar.md5 using Odin3 v1.85 - use PDA/AP button in Odin - UNCHECK Auto-Reboot and F.Reset Time
7). When flashing is completed you will see RESET displayed in Odin3.
8). Unplug your SM-T235/SM-T235Y from the PC and press (Power Button+Volume Down+Home Button) to initiate a restart/reboot - Don't release your fingers from the buttons.
9). IMPORTANT: AS SOON AS THE DEVICE POWERS DOWN (screen goes blank) MOVE YOUR FINGER FROM THE VOLUME DOWN BUTTON TO THE VOLUME UP BUTTON WHILE STILL PRESSING THE POWER BUTTON+HOME BUTTON.
10). IMPORTANT: AS SOON AS THE SAMSUNG SM-T235 LOGO APPEARS (White Letters) RELEASE YOUR FINGER FROM THE POWER BUTTON WHILE CONTINUING TO PRESS VOLUME UP+HOME BUTTON (If the animated Samsung Logo appears, then you missed Recovery mode and will need to start the entire process over from the beginning.
11). IMPORTANT: If you timed your finger pressing and releasing properly, you should now SEE the blue TEAMWIN splash screen which means you are entering TWRP recovery.
12). Once in TWRP Recovery, you will see a button that says Install. Tap on it.
13). Find UPDATE-SuperSU-v2.46.zip where you previously stored it on your external SD card and install/flash it to your SM-T235/235Y using TWRP.
14). Once installation of UPDATE-SuperSU-v2.46.zip is completed, you can proceed to reboot your SM-T235/T235Y from the TWRP main menu.
15). After the device finishes booting up, your Galaxy Tab 4 7.0" SM-T235/T235Y will be rooted.
16.) Download and run RootChecker to verify root.
CREDITS:
hennymcc - [T235][ROM][5.1.1][LMY48G] CyanogenMod 12.1 for T235(Y) [Alpha 12/07/2015]
RVR - TWRP 2.8.1 for the Galaxy S5 Mini (G800F)
Chainfire - UPDATE-SuperSU-v2.46
A.S._id - Odin3 ROM Editor
A.S._Dev - android_img_repack_tools​

My friends,
I still could use some radio help. ...
TTB
SM-T235 Tab 4 7" LTE ROOTED - TWRP 2.8.1 for the SM-T235/T235Y Tab 4 7" LTE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Reserved

TopTongueBarry said:
Also reserved
IT IS SO NEARLY IMPOSSIBLE TO WORK ON ANY THREAD OR POSTING ON THIS SITE. I LOST EVERYTHING I I WAS TRYINGTO UPDATE THIS THREAD WITH D/L LINKS, BUT THE VIDEO ADVERTISEMENTS JUST KILL IE. REPEATEDLY. WHY SO MANY VIDEO ADS, IMPOSSIBLE TO ENJOY AN XDA EXPERIENCE BECAUSE THE HUGE VIDEO ADS JUST CRAWL MY SYSTEM.
THERE WOULD HAVE BEEN A T235 RECOVERY ROOT HERE TODAY BUT THE ADS KILLED MY SESSIONS. I WROTE INSTRUCTIONS AND HAD EVERYTHING READY. THE LONGER IT TAKES TO POST A TOPIC AND INSTRUCTIONS THE MORE BEFUDDLED UP IE GETS UNTIL IT CRASHES.
OH WELL I CANNOT SPEND ANY MORE TIME TODAY HERE. HAVE TO GET BACK TO WORK. SO MUCH FOR GIVING YOU THE D/L's DURING LUNCH BREAK, BUT MAYBE TONIGHT, MAYBE NOT. IM TOO FRUSTRATED AND UPSET THAT I LOST ALL THAT WRITING AND WORK HERE TODAY. WE'LL SEE HOW QUICKLY I GET OVER IT , THEN YOU'LL GET YOUR RECOVERY ROOT.
Click to expand...
Click to collapse
That really blows, I feel your pain. I use chrome on my desktop with the adblock extension (I think it's even available for IE now) and I find the -- XDA 2013 theme for the website is much more aesthetically appealing and easier to navigate

It works! Changing of buttons is kinda tricky though, but its all good.. Thanks alot! :good:

thisisapoorusernamechoice said:
That really blows, I feel your pain. I use chrome on my desktop with the adblock extension (I think it's even available for IE now) and I find the -- XDA 2013 theme for the website is much more aesthetically appealing and easier to navigate
Click to expand...
Click to collapse
Thanks for the tip. I added the adblock plug in. My XDA experience is much improved. Thanks!
TTB

Jay018 said:
It works! Changing of buttons is kinda tricky though, but its all good.. Thanks alot! :good:
Click to expand...
Click to collapse
Confirming what you posted in the old thread, that your device is a SM-T235Y ?
Glad it works.
The T235Y has different factory ROMS on sammobile than the T235. Differences include CSC groupings, and configured radio bands, but the kernel and the partitions are the same as the T235. I suspect that's why this recovery works for the T235Y too.
- Speaking of which, can anybody point me in the direction of a way to get past the hurdles Samsung has added to block the ability to reconfigure LTE radio bands
- If we need to change the CSC's or CSC group to be able to enable LTE Bands 4 and 17, well, Sammy's making that tough to do too.
- Wondering if I can flash the modem firmware from the S5 Mini on the Tab 4 7" LTE using TWRP?
- Then wondering if bands 4 and 17 would be available after flashing since the CSC's play such a role in which radio band's get configured on each device.
Any help with the radio would be greatly appreciated.
TTB

TopTongueBarry said:
Confirming what you posted in the old thread, that your device is a SM-T235Y ?
Glad it works.
The T235Y has different factory ROMS on sammobile than the T235. Differences include CSC groupings, and configured radio bands, but the kernel and the partitions are the same as the T235. I suspect that's why this recovery works for the T235Y too.
Click to expand...
Click to collapse
Yes it's T235Y.. You can add T235Y in your title so other users will know.. Yes it has different ROM so I hesitated at first. Just need a couple of beer to do it, lol. Thanks a lot for this recovery. :good:

My friend....Congratulations...I have tried any method known to Google to root this tablet. Yours was the only one that worked. I have been waiting for this moment from November so thank you for making my day.

Success!!
I played fingers just like over my guitar fingerboard, haha! Then, suddenly, I was in face of TWRP face!:laugh:
First of all: install SD fix!
Infinity thanks to TopTongueBarry and his brilliant idea!:good:

aftnoon2 said:
Success!!
I played fingers just like over my guitar fingerboard, haha! Then, suddenly, I was in face of TWRP face!:laugh:
First of all: install SD fix!
Infinity thanks to TopTongueBarry and his brilliant idea!:good:
Click to expand...
Click to collapse
SD gets fixed if you flash a newer factory ROM than the 5/22 NE8 version. You will need to reinstall TWRP and re root.
TWRP installation and root tested and found to be working no matter which ROM you are running, including the latest version, NJ3
TTB
P.S. After rooting, KNOX can be disabled using ES Task Manager and it doesn't respawn, remains disabled. I'm toying with this in an attempt to get service mode changes to the available LTE bands to stick.
P.S.S ... I'll be releasing either ALPHA 2 or BETA 1 with the Slide to install SuperSU fixed and the missing advanced menu items added later this week.

TopTongueBarry said:
SD gets fixed if you flash a newer factory ROM than the 5/22 NE8 version. You will need to reinstall TWRP and re root.
TWRP installation and root tested and found to be working no matter which ROM you are running, including the latest version, NJ3
TTB
P.S. After rooting, KNOX can be disabled using ES Task Manager and it doesn't respawn, remains disabled. I'm toying with this in an attempt to get service mode changes to the available LTE bands to stick.
P.S.S ... I'll be releasing either ALPHA 2 or BETA 1 with the Slide to install SuperSU fixed and the missing advanced menu items added later this week.
Click to expand...
Click to collapse
Just don't care, TTB! I was ALREADY on NJ3!
Thanks for the Es explorer Knox idea, but, do you mean freezing Knox? I don't understand, sorry ...
And many thanks for keep the job over TWRP :good:

this is awesome i bought a couple 235y of my step dads friend for 100 bucks a pop thinking i got a great deal and and I was gonna put vanilla on it and blah blah came to xda to see there was no support..... decided to come on today see if there was anything and see this...
so amped..
---------- Post added at 10:51 PM ---------- Previous post was at 10:11 PM ----------
any custom rome we can flash or am i assuming no because deltas, I'm gonna try a couple things.

David111jr said:
this is awesome i bought a couple 235y of my step dads friend for 100 bucks a pop thinking i got a great deal and and I was gonna put vanilla on it and blah blah came to xda to see there was no support..... decided to come on today see if there was anything and see this...
so amped..
---------- Post added at 10:51 PM ---------- Previous post was at 10:11 PM ----------
any custom rome we can flash or am i assuming no because deltas, I'm gonna try a couple things.
Click to expand...
Click to collapse
No Custom ROMS yet, but since we now have a working recovery and root, there will hopefully be some soon..
I'm beating my head against the wall trying to get LTE bands 4 and 17 added. The factory firmware is quite unforgiving. A custom ROM would sure make the effort easier. Someone PLEEZE ......
Regarding freezing Knox, yes that's what I meant, and it works, but I've managed to wipe the CSC during my efforts to add LTE bands. Don't know if that's a good or bad thing at this point.
Apparently the Samsung USB drivers do have a diagnostic mode driver for Marvel chipsets. After much effort, I have it installed on my Win 8 machine, and the driver switches dynamically when switching from PDA to MODEM in the Service Mode menus. Problem is, its not a serial driver it is a USB/QC driver and QPST version 2.7.411 still doesn't recognize it. Need to find a way to get QPST to recognize it.
Can't do the NV ram edit needed to add LTE bands without diagnostics mode.
TTB

It works. SM-T235 LTE
Thanks!

I think my t235y will never be rooted, you are awesome bro

Thanks for your efforts, TTB!
Now a question : can we make a Nandroid bckp on the External SD?
I would to make one, but, apparently, the bckp goes to Internal, where I have no place ...
Is this intrinsic of TWRP or a later version can change this?

aftnoon2 said:
Thanks for your efforts, TTB!
Now a question : can we make a Nandroid bckp on the External SD?
I would to make one, but, apparently, the bckp goes to Internal, where I have no place ...
Is this intrinsic of TWRP or a later version can change this?
Click to expand...
Click to collapse
Check the T230 recovery/root threads. I believe (not 100% certain though) I saw that someone has created a fix/work-around to allow switching internal SD and external SD for this.

thienlong0193 said:
I think my t235y will never be rooted, you are awesome bro
Click to expand...
Click to collapse
What do you mean you think it will never be rooted? This works on the T235 and the T235Y.

TopTongueBarry said:
What do you mean you think it will never be rooted? This works on the T235 and the T235Y.
Click to expand...
Click to collapse
sorry my bad english, i mean i've been waiting for so long to root my tab :laugh: thank you a lot :x

[TOOL] WinDroid Toolkit | Unlock | Root | Flash | Install | Shield Tablet

Link To Main Thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.

Reserved
Reserved.

Sorry for the question... but how is the process to root a Nvidia Shield Tablet? It supports update 2.2.1?
Thanks!!

tux_topo said:
Sorry for the question... but how is the process to root a Nvidia Shield Tablet? It supports update 2.2.1?
Thanks!!
Click to expand...
Click to collapse
I'm working on a step-by-step written guide, but the toolkit will guide you through the steps to root as well. The toolkit does support the 2.2.1 update. :good:

Noob question: The proccess reset the tablet? Will gone a loose any data?
Thanks!!

tux_topo said:
Noob question: The proccess reset the tablet? Will gone a loose any data?
Thanks!!
Click to expand...
Click to collapse
+1.
not looking to install custom recovery, just root. Looking forward to the progress of this toolkit. Thanks @WindyCityRockr
Sent from my 1+1

tux_topo said:
Noob question: The proccess reset the tablet? Will gone a loose any data?
Thanks!!
Click to expand...
Click to collapse
Mojar7070 said:
+1.
not looking to install custom recovery, just root. Looking forward to the progress of this toolkit. Thanks @WindyCityRockr
Sent from my 1+1
Click to expand...
Click to collapse
Unlocking the bootloader WILL erase all data. I don't know if you could achieve root without a custom recovery but if you plan to flash a custom recovery you will need to unlock the bootloader.

While this tool worked for me, it didn't work well with step 2. It did flash the recovery but I had to manually reboot to recovery for it to work. Selecting yes/next to reboot to recovery after flashing it through the tool only took me to fastboot. That was the only thing I noticed but other than that, everything else worked perfectly. For clarification as well, I did it on newest firmware available right now (2.2.1).

gqukyo said:
While this tool worked for me, it didn't work well with step 2. It did flash the recovery but I had to manually reboot to recovery for it to work. Selecting yes/next to reboot to recovery after flashing it through the tool only took me to fastboot. That was the only thing I noticed but other than that, everything else worked perfectly. For clarification as well, I did it on newest firmware available right now (2.2.1).
Click to expand...
Click to collapse
The reboot option after the recovery flash is supposed to reboot you back to Android because the next step in the toolkit is to push SuperSU, which requires ADB.

WindyCityRockr said:
The reboot option after the recovery flash is supposed to reboot you back to Android because the next step in the toolkit is to push SuperSU, which requires ADB.
Click to expand...
Click to collapse
Well in my case, it didn't do that either, mine ended up in fastboot. In any case it everything works as it should. thanks!

Worked flawless.
After flashing TWRP where it asks to reboot, it does reboot the tablet but the program seems to get stuck on "Rebooting......" even after the tablet have booted.
I tried waiting a min to see if it changed but I had to remove and attach the USB again before it realized it was connected and said "Move to step 3".
I'm happy though because anything that can be done smoother than ADB (even though it is really easy) is appreciated.

Wow, this looks super useful and easy. I was just thinking of rooting my shield again cause I'm sick of adds and just dropped in to see how things were progressing on the development side.
Glad I did now, might give this a whirl today

Edit: This is awesome! I was contemplating rooting my 2nd shield (after my first one blew up after 5 days) and have been putting it off for a while.
I'm used to rooting n'stuff so I don't find it to difficult but this just made things so much easier! I had it unlocked and rooted in a couple of minutes.
Big thank you for your effort and hard work.

I can't seem to get adb working. What do I need to do to get the program to recognize my shield tablet?
Sent from my Nexus 6 using Xparent Cyan Tapatalk 2

Ensure you have installed the drivers.

And don't forget to use an USB 2.0 port! USB 3.0 ports generally do not work.

Is there any way to do this with Ubuntu?

Thank you for this! It looks like an amazing tool, just what I was looking for. I had a Kindle Fire HD and it was a hell lot of trouble to install TWRP and flash roms, and when I saw my brand new shield had a hell of a process to get rooted in Lollipop the Kindle nightmare just flashed before my eyes (I had bricked it once so my heart practically stops every time an android device of mine reboots, in fear it won't turn on again). It's such a relief to see everything automated.
If you read what I had written there before (some questions about how to use the toolkit) never mind me, I found the instructions

i can't get this to work, it keeps saying OFFLINE. i installed everything it requested when I opened the .exe

Unlocked bootloader.
Installed Twrp.
But when i go to recovery mode on my lg watch r it STILL boots to the stock recovery???
Am i doing something wrong?

New Update - QC2

According to the Verizon Galaxy S5 Update Page:
This software update provides the latest Android™ security patches, fixes an email issue and updates the Amazon Shopping app.
Email update:
Fixes an issue that prevented Outlook® 2007 and 2003 users from accessing and downloading email attachments.
Click to expand...
Click to collapse
Please note that if you happen to play Pokemon GO or any game which "GPS Spoofers" take advantage of, the March Security Patch, and this update will prevent GPS Spoofing.
Also, I'm not entirely sure yet as to whether the Samsung Patch for Qualcomm Galaxy S5 bootloaders included in the March Security Patch will affect the ability to have a Developer bootloader anymore:
SVE-2016-7930: Multiple Buffer Overflow in Qualcomm Bootloader
Severity: Critical
Affected versions: Galaxy S5 with Qualcomm AP chipset
Reported on: December 20, 2016
Disclosure status: Privately disclosed.
A buffer overflow vulnerability exist in Qualcomm bootloader.
The patch prevents buffer overflow by removing the problematic source code.
Click to expand...
Click to collapse
I, personally, am not willing to test this, but if anyone does, please post your results. I'll upload an aboot free (Dev Friendly) firmware as soon as possible in case anyone wants to test it.
I'm currently in the process of downloading/uploading the Odin firmwares right now. I'll update this post when they are uploaded.
EDIT:
Stock No-Wipe FW. Will remove Developer Status Bootloader: G900VVRU2DQC2_G900VVZW2DQC2_G900VVRU2DQC2_HOME.tar.md5.zip
Developer Bootloader Friendly:
G900VVRU2DQC2_G900VVZW2DQC2_G900VVRU2DQC2_HOME_No_Aboot.tar.md5.zip

If it breaks something that I warned about, please reply.
If it breaks something that I didn't warn or know about, please share with everyone else.

I'm guessing no replies and no ROMs based on QC2 means noone has tested it yet.
I'm going to flash the aboot free version to one of my CID 15 S5's later tonight so I'll reply with results.

I'm gonna try it out when I get a chance this week. Thanks!

Has anybody tried this?

robbyoconnor said:
Has anybody tried this?
Click to expand...
Click to collapse
Not yet I'm gonna download this once I get to a pc definitely
Sent from my SM-G900V using Tapatalk

Kastro1784 said:
Not yet I'm gonna download this once I get to a pc definitely
Click to expand...
Click to collapse
You can use Flaahfire by the way.

Download /installed last night.Havent had time to dig around. Precursor look has only shown latest Android security updates.

Dudash said:
I'm going to flash the aboot free version to one of my CID 15 S5's later tonight so I'll reply with results.
Click to expand...
Click to collapse
How we looking, captain?

I recently was pushed the QC2 update with the March 2017 security package. I have noticed a significant decline in performance and battery life. Anyone in the same boat?
It seems like they have pushed a security updated every other month or so for the last 6 months. It is very irritating. I want to go back to root but it is too much of a hassle to figure it out at this point. I feel like they are deliberately doing these updates to make the S5 run worse and feel more outdated so you are more inclined to go buy a new one. Really sick of the whole game that is the telecom industry.
I am going to try doing a factory reset (very annoying) and see if that helps. Hopefully I can hold out long enough for the Pixel 2.

@Dudash QD1 is up, can you upload it to AFH. thanks in advance.

Noooooo! I flashed the Dev friendly QC2 modem and it seems to have killed my dev bootloader and wiped my phone!
I'll keep messing around and see if it can't be remedied. I could just punch myself for being so ambitious, though.
Edit 1: It was taking forever on the Verizon logo, so I pulled the battery and rebooted to recovery. It wiped TWRP and put in stock. I booted to Download Mode, and it still reads MODE: Developer (which I hope to God means my Dev bootloader is retained).
Edit 2: TWRP sucessfully re-flashed. The "Custom" with unlocked lock icon has reappeared on the boot screen, along with the yellow text at the top (so clearly, I was wrong about losing Dev status. Whew! I just freaked out when I saw a plain boot screen and the dreaded Verizon logo :silly. My installation of Lineage OS is clearly gone, but, peeking through TWRP's file manager appears to indicate my media data (photos, downloads, etc.) may yet have survived. I'll flash Lineage and GApps and see what happens.
Edit 3: Lineage OS booted successfully (made easier with the help of an SD card-- hooray for those things, amirite?), with QC2 baseband intact! Hooray! And my downloads and pictures and everything survived too.
Lesson: Always make a nandroid backup when doing this sort of thing! It takes a while, and it's morbidly annoying, but had I done it, I probably wouldn't've had to start from scratch. But hey, got the new baseband, and still running Lineage, so I call this a win. Cheers, everyone! And thanks to OP for posting updates!
Follow-up: Since it doesn't seem like we can flash only the new basebands by themselves, I've found a tactic that does the trick for those of us on not-stock ROMs. Boot into TWRP and make a backup of Boot, System, and Data (notice there's a Modem option-- leave it unchecked). I imagine it's best to put the backup image on an SD card. Then Odin the dev-friendly firmware update (I used the no-wipe option). Let the phone restart, then Odin the most recent TWRP back on there. Boot into TWRP, do a Factory Reset Wipe, and restore the backup you made. Takes a little while, but it does leave you with your phone as it was, but with the new baseband. :victory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mohammad.afaneh said:
@Dudash QD1 is up, can you upload it to AFH. thanks in advance.
Click to expand...
Click to collapse
In the process of uploading right now.

Dudash said:
In the process of uploading right now.
Click to expand...
Click to collapse
??? thanks

J-Lindo said:
How we looking, captain?
Click to expand...
Click to collapse
I totally missed this reply. I flashed QC2 onto one of my S5's and it remained a Dev Edition. Then earlier today I flashed QD1 onto my other S5 and it remained a Dev Edition as well. Faking GPS doesnt work on either anymore but they keep Dev status.

Dudash said:
I totally missed this reply. I flashed QC2 onto one of my S5's and it remained a Dev Edition. Then earlier today I flashed QD1 onto my other S5 and it remained a Dev Edition as well. Faking GPS doesnt work on either anymore but they keep Dev status.
Click to expand...
Click to collapse
No problem! I'm sure you've already seen the results of my first (embarrassingly n00bish) independent baseband flash :laugh:
I appreciate the response, though. Fortunately, I'm not into GPS spoofing, so this isn't an issue for me. When you say you flashed QC2 and QD1, do you mean strictly the basebands without the bootloaders, or did you flash the entire updates and still retain Dev status?

J-Lindo said:
No problem! I'm sure you've already seen the results of my first (embarrassingly n00bish) independent baseband flash :laugh:
I appreciate the response, though. Fortunately, I'm not into GPS spoofing, so this isn't an issue for me. When you say you flashed QC2 and QD1, do you mean strictly the basebands without the bootloaders, or did you flash the entire updates and still retain Dev status?
Click to expand...
Click to collapse
I flashed the entire firmware minus the aboot.

Please help, Samsung A11 - TRWP problem

Hi everyone,
Recently I purchased and Samsung A11. I wanted to root it and unlocked the bootloader first. Than I used Odin to install TRWP recovery. Odin showed "PASS" and I was supposed to press certain buttons which didn't work. Phone kept coming back to "Download Mode" although I pressed those buttons. So I was stuck. The only option was to cancel the download mode, so I pressed volume down + power button for more than 7 seconds. That was the end Now the phone turns on until I see the Samsung logo, there's a small vibration but it can't go forward. It resets back and now stuck in a loop. None of the buttons work including Volume Down+Power combination. Don't know what I am supposed to do now. Can anybody help?
Thanks...

1. Add Samsung A11 to this thread's title thus mainly owners of such a phone get addressed
2. My recommendation: Re-flash STOCK ROM to get rid off of all mods you applied.

jwoegerbauer said:
Re-flash STOCK ROM to get rid off of all mods you applied.
Click to expand...
Click to collapse
Thanks but how can I do that? Phone doesn't turn on, so PC cannot recognise...

gokund said:
Thanks but how can I do that? Phone doesn't turn on, so PC cannot recognise...
Click to expand...
Click to collapse
As I can see you are proud owner of a softbricked phone.
Take it to authorized service center and let them fix it.

jwoegerbauer said:
As I can see you are proud owner of a softbricked phone.
Take it to authorized service center and let them fix it.
Click to expand...
Click to collapse
Yeah, veeeery proud
I plan to let it die on battery and will try to see if I can turn on "Download Mode" after recharging. Do you think it may work?

gokund said:
Yeah, veeeery proud
I plan to let it die on battery and will try to see if I can turn on "Download Mode" after recharging. Do you think it may work?
Click to expand...
Click to collapse
it wouldn't ... usually the cause of bootloop is certain corrupted partition and as long as that partition is corrupted it would keep bootlooping.
if you doesn't know what your doing your best bet is Take it to authorized service center and let them fix it. like what @jwoubeir said

I don't have the A11 model but have used this on other A models that were in the same loop.
Press the volume up and down at the sametime and plug in the usb cable.
This has to be done within a second or two after it vibrates and before it reboots and will likely take a few tries. Good Luck

sammiev said:
I don't have the A11 model but have used this on other A models that were in the same loop.
Press the volume up and down at the sametime and plug in the usb cable.
This has to be done within a second or two after it vibrates and before it reboots and will likely take a few tries. Good Luck
Click to expand...
Click to collapse
great tip work on ADB too anyway OP is provably using sp flashtool since his phone is samsung so this method would be rather tricky

Yayy, I managed to get into the "Download mode" doing exactly how @sammiev told and I tried flashing another TRWP file thinking that might have caused the problem but nothing has changed. Same loop again ! So I flashed the original ROM back using Odin and it's back live again Thanks for the help guys. But to be honest, I am still curious. What might be the problem in not getting TRWP flashing going right?

gokund said:
Yayy, I managed to get into the "Download mode" doing exactly how @sammiev told
Click to expand...
Click to collapse
Used that method of a few peoples Samsung phones. Worked for me every time. It's just to get the timing right.
Sure you have the correct TWRP?

sammiev said:
Used that method of a few peoples Samsung phones. Worked for me every time. It's just to get the timing right.
Sure you have the correct TWRP?
Click to expand...
Click to collapse
I tried again from scratch with a new TRWP file and the result is the same. Odin shows "PASS" but the "Download Mode" screen gives the error as in the photo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone model is A115F and I downloaded the TRWP file from this link:
Downloads for : Samsung Galaxy A11 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
The version I used is "twrp-3.5.0_10-3_afaneh92-a11q.tar"
I also tried rooting with Magisk without the need of TRWP installation. That was also unsuccesfull. Odin was PASS but I got bootloader screen saying Secure Check Fail : vbmeta
Here's the screenshot of Magisk fail in "Download Mode"
Can't figure out what's wrong ...

Have you flashed the latest stock rom to this device?
Was there other TWRP files for this model?
Is other people having trouble with this model?
I never worked on A11 Samsung yet
I would hate to give you bad info and have you brick your phone.

Deleted

sammiev said:
Have you flashed the latest stock rom to this device?
Was there other TWRP files for this model?
Is other people having trouble with this model?
I never worked on A11 Samsung yet
I would hate to give you bad info and have you brick your phone.
Click to expand...
Click to collapse
Following your advice, I managed to get into the Download Mode and I flashed the original rom. So phone is up and running now but not rooted. So I've been trying to root again first with Magisk to bypass the need of TRWP installation and with others which need TRWP installation first. There seems to be something blocking the flashing of anything other than the original rom !! On the link I shared above, there are other (older version) TRWP files. Shall I try them?

gokund said:
Following your advice, I managed to get into the Download Mode and I flashed the original rom. So phone is up and running now but not rooted. So I've been trying to root again first with Magisk to bypass the need of TRWP installation and with others which need TRWP installation first. There seems to be something blocking the flashing of anything other than the original rom !! On the link I shared above, there are other (older version) TRWP files. Shall I try them?
Click to expand...
Click to collapse
Usually the latest TWRP with the latest firmware.

Check my profile, your KG stated is ****ed. There is nothing you can do about it, there is abosulutly no way to fix this without unsoldering the eMMC and resetting it entirely. Some people on 4PDA had the same problem and found no fix. I was hopping to develop a custom rom but I cant as my kg state is prenormal. This mexican dude on youtube fixes devices with KG and FRP issues, but yeah this aint something that you can do at home. At least I learned not to buy any samsung devices in the future https://www.youtube.com/c/TeamOcmineMMCBootRepair
edit: nvm your oem is unlocked, you can just flash the vbmeta reset script via odia and everything should flash fine.

[Solved!] [SM-G955F] RMM state still locked after 7 days (RMM State Prenormal)

I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution

FlooferLand said:
I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution
Click to expand...
Click to collapse
Can you send a screenshot of the bootloader screen?

Kenora_I said:
Can you send a screenshot of the bootloader screen?
Click to expand...
Click to collapse
I'm guessing you mean the Download screen..?
Here's the Download screen if so:
https://imgur.com/pxu0hsS

FlooferLand said:
I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution
Click to expand...
Click to collapse
You did run fastboot OEM unlock?
or
fastboot flashing unlock

Kenora_I said:
You did run fastboot OEM unlock?
or
fastboot flashing unlock
Click to expand...
Click to collapse
I don't think my phone even has fastboot
I tried booting it into recovery and selecting to apply an update with ADB, I've also tried it at the "Waiting for update" screen.
Fastboot just gets stuck saying < waiting for any device >
The OEM unlock checkbox is already checked in Developer Options.
I don't think the S8+ needs another way to enable OEM unlock other than the checkbox in Developer Options.
EDIT: Here's the output of adb logcat --regex rmm after booting into Android if that's helpful(?) (I have no idea how to use Logcat):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

you did install fastboot drivers? Sometimes if you connect with a usb 3.0 port it dosent work properly

Kenora_I said:
you did install fastboot drivers? Sometimes if you connect with a usb 3.0 port it dosent work properly
Click to expand...
Click to collapse
I've seen a lot of people say the S8+ doesn't have fastboot, there's also no "Reboot to fastboot" option in the recovery menu

Apparently Samsung's RMM server (https://rmm.samsung.com/) appears to be dead (SSL certificate expired and the entire server seems to not work)
So i'm wondering if there's a way to actually spoof the data the server sends, basically blocking Samsung's server and making my own DNS that resolves to my own server sending it's own data.
My problem then is, how would i even know what data my server is supposed to send? And would that even be possible?
I'm very much out of ideas XD
I also found this post (and i have a continuation file for my own phone so in theory it should work?) but it requires the use of iRoot and some proprietary sketchy Windows program. And iRoot and all of these one-click root apps have been known for injecting malware system-level into devices.

FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!

Nice work! tbh I'd never think of that lol,
FlooferLand said:
FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!
Click to expand...
Click to collapse

FlooferLand said:
FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!
Click to expand...
Click to collapse
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !

JuanMat97 said:
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !
Click to expand...
Click to collapse
The same goes. I have tried everything, and it seems that the post here suggests that we now entirely depend on Samsung to get the site certificate sorted out
Link pasted here for those who don't trust shortened links: https://forum.xda-developers.com/t/...d-expired-certificate-whats-next-lol.4403393/

JuanMat97 said:
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !
Click to expand...
Click to collapse
I very much have no clue how it worked for me XD
It's very much possible, you just have to continously try.
I've heard rumors that if you have a Snapdragon chip instead of an Exynos, the RMM is doomed to lock until Samsung resolves their issue. But idk anything about that so i can't really confirm it XD.
I would recommend upgrading to Android 9 and doing the thing i said tho, that worked for me.
Also make sure that your ROM is from the country your SIM card is from, very important.
My phone was originally from Spain, and having a ROM that was made in Spain seemed to caused the RMM to continuously trip out since my SIM wasn't from Spain, so it essentially detected my phone as stolen or smth. You can find official ROMs on something like SamFW.
If this still doesn't work, try waiting 7 days again, then doing the thing i said.

FlooferLand said:
I very much have no clue how it worked for me XD
It's very much possible, you just have to continously try.
I've heard rumors that if you have a Snapdragon chip instead of an Exynos, the RMM is doomed to lock until Samsung resolves their issue. But idk anything about that so i can't really confirm it XD.
I would recommend upgrading to Android 9 and doing the thing i said tho, that worked for me.
Also make sure that your ROM is from the country your SIM card is from, very important.
My phone was originally from Spain, and having a ROM that was made in Spain seemed to caused the RMM to continuously trip out since my SIM wasn't from Spain, so it essentially detected my phone as stolen or smth. You can find official ROMs on something like SamFW.
If this still doesn't work, try waiting 7 days again, then doing the thing i said.
Click to expand...
Click to collapse
friend please, could you say, step by step and in an orderly manner what you did? for example when you said "The time trick actually worked.
All i had to do was turn back the time by like a year" 1-¿have you done that after a flash, a hard reset, or just rebooted without deleting anything?, and also when you said "reboot, enter recovery mode" 2-¿what you did was restart directly to recovery, or restart the system and then restart it again to recovery? and lastly in the part where you said "re-enable OEM unlock, spam the update phone button" 3-¿"re-enable", if you said "re" it means that before reactivating it you already had it activated, right? 4-¿"spam button" by that you mean pressing many times, but, did you have the automatic updates box enabled or not, and... how many times did you touch the update button? thanks in advance, I would appreciate if you answer the 4 questions

which ROM were you using when you did theses steps to unlock? I've tried the 168hs+ method almost now and it didn't worked, then I found your post and tried doing this method changing the date and rebooting cleaning the partition but until now I couldn't achieve it, can you help me pleass

which ROM were you using when you did theses steps to unlock? I've tried the 168hs+ method almost now and it didn't worked, then I found your post and tried doing this method changing the date and rebooting cleaning the partition but until now I couldn't achieve it, can you help me pleass