DISCONTINUED [Firmware & ROM] SCH-I705 VRBMI1 - October 2013 - 4.1.2 - Galaxy Tab 2 7" Android Development

VRBMI1 Firmware and ROM
***NOTICE***​Questions belong in the Q&A section. I am not providing support for this ROM. This is a stock release from Samsung/Verizon.
***Disclaimer***​I am not responsible if you break your stuff. READ READ READ
Click to expand...
Click to collapse
Features
VRBMI1 update from Verizon
Partitions updated:
RPM
TZ
BOOT
SYSTEM
Requirements
A SCH-I705, Verizon Galaxy Tab 2 7.0
Unlocked bootloader
Installation
Flash in ODIN 3.04
Download link removed
As it appears the firmware has been signed with different keys, this will likely brick most tabs.
Don't forget to hit the thanks button!

Wow! thanks a lot!!
screen shot pls

Its a stock ROM with no changes other than root. No need for a screenshot.
Sent from my SCH-I535 using XDA Premium 4 mobile app

So is it worth it to update or would we better off.. And if so is there anyway to stop getting the notification to update
Sent from my SCH-I500 using xda premium

Honestly, the only difference I noticed is the notification drop down takes up the whole screen now.
Remove notification by removing SDM.apk (if its still called that)
Sent from my SCH-I535 using XDA Premium 4 mobile app

MrHyde03 said:
Honestly, the only difference I noticed is the notification drop down takes up the whole screen now.
Remove notification by removing SDM.apk (if its still called that)
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Does removed SDM.apk remove the ability to pull down the notification panel? That's actually what I'm looking for, so that would be cool.
---------- Post added at 05:29 PM ---------- Previous post was at 05:14 PM ----------
MrHyde03 said:
VRBMI1 Firmware and ROM
Requirements
A SCH-I705, Verizon Galaxy Tab 2 7.0
Unlocked bootloader​
Click to expand...
Click to collapse
Hi, quick question - why would I need an unlocked bootloader to flash via ODIN?​

Because this is a repackaged, unsigned ODIN package. It probably won't let you flash, and if it does, will probably brick you.
Unlock your bootloader or stay away from it.

MrHyde03 said:
Because this is a repackaged, unsigned ODIN package. It probably won't let you flash, and if it does, will probably brick you.
Unlock your bootloader or stay away from it.
Click to expand...
Click to collapse
+MrHyde03 .... I just bought the Verizon Samsung Galaxy Tab 2.0 7" yesterday from my local Verizon store and I've not found much about rooting THIS particular firmware model (VRBMI1) until now. I'm excited as hell to find this from you because I've almost given up on getting root ..... =/ The only thing I'm wondering about is that you said in the OP that this requires an unlocked bootloader.... since I bought this thing from verizon with vrbmi1, I obviously can't go backwards a firmware model in order to unlock the bootloader, so would you care to point me in the right direction , in terms of maybe a link to a good thread with instructions to unlock this thing and get this stock rooted vrbmi1 ROM on here?
Thank you soooo much!! =)

As far as I know, there is no known root method. I no longer have the tab myself so I will no longer be doing any work for it. As for unlocking, the previous method has been known to brick tabs. Basically, any version from VRBMI1 and forward will no longer be unlockable unless you get your hands on an insecure VRBMI1 bootloader.

Related

[Q] Samsung Galaxy S3 Mini SM-G730A downgrade to older android firmware? 2.2

i have a s3 mini phone that has a very new model (g730a) that looks like nobody else on the internet has. there are no threads on this entire forum about this model number, and i am trying to downgrade the stock firmware, 4.2.2, to a very old firmware, 2.2 (froyo), is there any way of doing this? (this phone was bought from an at&t store) how do people even downgrade? where do they get their downloads from?
if there is "no way" of me doing this easily by downloading something, how can i do it myself?
really need some help with this, thanks!
theodoeshutup said:
i have a s3 mini phone that has a very new model (g730a) that looks like nobody else on the internet has. there are no threads on this entire forum about this model number, and i am trying to downgrade the stock firmware, 4.2.2, to a very old firmware, 2.2 (froyo), is there any way of doing this? (this phone was bought from an at&t store) how do people even downgrade? where do they get their downloads from?
if there is "no way" of me doing this easily by downloading something, how can i do it myself?
really need some help with this, thanks!
Click to expand...
Click to collapse
why would you want to downgrade?
i just think froyo looks cool, and i see it still functions with the play store and that. i've heard of cyanogen mod or whatever it's called yet don't know what it is nor how to use it. i am brand new to this android world. was told that this site had everything
Device was not here when froyo was so you will never be able to downgrade. It came with jb, so that's what you will have.
Sent through time and space from my s3mini/CM10.1
do you know if it is root able and if cwm install works
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I guess you have the latest S3 Mini from AT&T with a different SOC so dont use anything for i8190s
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
lgkahn said:
do you know if it is root able and if cwm install works
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
At least not yet
AssToast said:
I guess you have the latest S3 Mini from AT&T with a different SOC so dont use anything for i8190s
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
At least not yet
Click to expand...
Click to collapse
do you have one.. so 8901 root doesnt work.. do you know if bootloader is locked?
lgkahn said:
do you know if it is root able and if cwm install works
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Try the "one-click-root" that someone posted in general. It might work. Then you can take a look on what's inside, and maybe have a recovery built.
Sent through time and space from my s3mini/CM10.1
haven't got one.. waiting ..don't want yo get one for wife unless rooteable and non locked boot loader
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
lgkahn said:
haven't got one.. waiting ..don't want yo get one for wife unless rooteable and non locked boot loader
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
It's rootable.
tys0n said:
Device was not here when froyo was so you will never be able to downgrade. It came with jb, so that's what you will have.
Sent through time and space from my s3mini/CM10.1
Click to expand...
Click to collapse
wow, that's disappointing. you can install windows 2000 on any computer yet can't do the same for a phone.
theodoeshutup said:
wow, that's disappointing. you can install windows 2000 on any computer yet can't do the same for a phone.
Click to expand...
Click to collapse
You CAN install any android version that is older that you want, but it isn't created for the device. So somebody would need to develop drivers for it to work on the particular version of android.
Short answer: No you can't do it
Long answer: It can be done but a skilled person would need to develop drivers to make it work.
In this day and age creating drivers to downgrade from 4.1 to 2.2 it's not worth the time it takes.
Factory Unlocking
Has anyone successfully factory unlocked the S3 mini SM-G730 att. Or even paid for an unlock code?

Need Testers For 4.4.2 Stock Rom

Title says it all. I am one of a few who flashed the current broken stock rom in the development section. The dev stated he can't get it to work right now. (Not sure if it's difficult or he's short on free time...) Anyways, I got my own running on my phone. I'm zipping up the rom right now if anybody wants to flash away.
Includes:
SU (SuperSU)
Busybox 1.22.1
PM me if interested. No noobs for now please...
Rydah805 said:
Title says it all. I am one of a few who flashed the current broken stock rom in the development section. The dev stated he can't get it to work right now. (Not sure if it's difficult or he's short on free time...) Anyways, I got my own running on my phone. I'm zipping up the rom right now if anybody wants to flash away.
Includes:
SU (SuperSU)
Busybox 1.22.1
PM me if interested. No noobs for now please...
Click to expand...
Click to collapse
guess that rules me out. lol:cyclops:
PM Sent.
loader2142 said:
guess that rules me out. lol:cyclops:
Click to expand...
Click to collapse
Lol...
fgr said:
PM Sent.
Click to expand...
Click to collapse
Thanks.
Sent From My Samsung Galaxy S4! ?
I'll report later tonight. Got a Valentine's Day sushi dinner & movie first. Hope all goes well~
Sent from my Nexus 5 using Tapatalk
Why do you need to have a ROM? Just flash the update and re root using my thread. Just wondering. Not trying to bash a Dev.
Sent from my SPH-L720 using xda app-developers app
Zachisimo said:
Why do you need to have a ROM? Just flash the update and re root using my thread. Just wondering. Not trying to bash a Dev.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
People don't want the Knox bootlaoder that comes with the update. Some people are still on MF9 boot loader.
Sent from my SPH-L720 using Tapatalk
I'm no dev, just trying to help.
Sent From My HTC One! ?
Reporting in...it didn't work. Stuck in Samsung logo screen.
Sent from my Nexus 5 using Tapatalk
Dafuq. Lol, what's going on with this base... I just realized I didn't include an updater-script...
Also, no further testers needed...
Sent From My HTC One! ?
Zachisimo said:
Why do you need to have a ROM? Just flash the update and re root using my thread. Just wondering. Not trying to bash a Dev.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
What the ... are you serious? Knox Bootloader is the devil. Everyone should use ONLY a deknoxed rom. ONLY. And never ever ever use your thread.
Some people . like myself could care less about Knox. I was worried for a while but once it was tripped I really don't care.
Sent from my SPH-L720 using Tapatalk
You may not care but the rest of us do.
eskomo said:
You may not care but the rest of us do.
Click to expand...
Click to collapse
There's a lot that don't. I used to really care. But it doesn't mean much. Its only Samsung warranty. Sprint still has their 1 year.
Sent from my SPH-L720 using Tapatalk
I don't care about it at all lol tripped it early on and hasn't caused me a single problem
Sent from my SPH-L720 using Tapatalk
I still care about tripping Knox. But I'll feel okay about it once my warranty expires in a couple months.
daniel4653 said:
Some people . like myself could care less about Knox. I was worried for a while but once it was tripped I really don't care.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I for one don't care either. it doesn't stop me.
Sent From My HTC One! ?
IIRC there are two KNOX issues on this phone and people tend to get them confused.
First off there is the KNOX Bootloader that has the warranty flag thingy. Once this bootloader is installed it cannot be removed or downgraded AFAIK. Also if you root and/or change roms it trips the counter which some people fear will void their warranty even though I haven't seen this actually be the case with anyone so far.
The second KNOX is the KNOX files included in the OS. This can (somewhat) easily be removed from a rooted S4 even if it has the KNOX bootloader. This is what I did with my GF's S4 as she blindly installed the 4.3 update right when she got it.
Now people have made their own 4.3 update (minus the KNOX stuff) that can be installed on the side to update the OS without installing KNOX. This is the route I would have taken if I had the chance.
I think the biggest fear with the 4.4 KitKat update is that it will once again force KNOX back onto the system - even if it had already been removed. Because of this many people are hesitant to install the OTA update until they are sure that KNOX can be removed from it - or until a version is made that can be manually installed that already has KNOX removed.
MasterTec said:
IIRC there are two KNOX issues on this phone and people tend to get them confused.
First off there is the KNOX Bootloader that has the warranty flag thingy. Once this bootloader is installed it cannot be removed or downgraded AFAIK. Also if you root and/or change roms it trips the counter which some people fear will void their warranty even though I haven't seen this actually be the case with anyone so far.
The second KNOX is the KNOX files included in the OS. This can (somewhat) easily be removed from a rooted S4 even if it has the KNOX bootloader. This is what I did with my GF's S4 as she blindly installed the 4.3 update right when she got it.
Now people have made their own 4.3 update (minus the KNOX stuff) that can be installed on the side to update the OS without installing KNOX. This is the route I would have taken if I had the chance.
I think the biggest fear with the 4.4 KitKat update is that it will once again force KNOX back onto the system - even if it had already been removed. Because of this many people are hesitant to install the OTA update until they are sure that KNOX can be removed from it - or until a version is made that can be manually installed that already has KNOX removed.
Click to expand...
Click to collapse
Any thoughts on what people will be doing once the S5 rolls out? It is probably a safe bet that they will come with Knox or a Knox like system factory installed.
Sent via mobile
Maybe by then there'll be a way to remove/disable KNOX (bootloader KNOX, to clarify)
I remember once HTC did their bootloaders, people either did an engineering bootloader or a custom unlocked bootloader. (let's not speak of the Evo 3D) Here's hoping we don't have to go that route with Samsung devices.

How to root tab s

Use cf root method from note 10.1 2014 edition. Download the files for odin, flash using odin, and profit!
Is it the smt600 file from chain fires site. Or the 2 files from the note 10.1 2014 edition forum. I soft bricked when I did chain fire smt600 file. How to root.
Sent from my SM-T700 using XDA Premium 4 mobile app
will6316 said:
Is it the smt600 file from chain fires site. Or the 2 files from the note 10.1 2014 edition forum. I soft bricked when I did chain fire smt600 file. How to root.
Sent from my SM-T700 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's the files from the note 10.1 2014. I don't know what a sm-t600 is????
http://forum.xda-developers.com/showthread.php?t=2490805
mingkee said:
http://forum.xda-developers.com/showthread.php?t=2490805
Click to expand...
Click to collapse
Did it work for you. Cant seem to get it to work stuck on boot logo. Need to reodin stock rom.
Be mindful of the Knox counter. Knox might be an issue, if resale or return is a possbility.
Don't really care about knox I sold my tab pro for this. Problem is I can't root. I tried at least 5 times with the above method even tried the tab pro 10.1 cf root. Odin is success. But cant get pass boot logo. Is there something I'm doing wrong.
I haven't received my tablet yet. But has anyone tried towelroot?
will6316 said:
Did it work for you. Cant seem to get it to work stuck on boot logo. Need to reodin stock rom.
Click to expand...
Click to collapse
Same here, stuck on logo screen. Any known tricks/tips to get past the logo screen? Anybody ??
suzook said:
It's the files from the note 10.1 2014. I don't know what a sm-t600 is????
Click to expand...
Click to collapse
I meant the smp600 with is the note 10.1 2014. Do you have root suzook?
Play it safe and wait for the Devs to come up with a safe root for the Tab S. No roms yet anyway so why bother?
Don't make a $500 paperweight because you were impatient.
mitchellvii said:
Play it safe and wait for the Devs to come up with a safe root for the Tab S. No roms yet anyway so why bother?
Don't make a $500 paperweight because you were impatient.
Click to expand...
Click to collapse
+1, Exactly. I just experienced this. I tried the root method listed in this thread and it bricked the device. (It just remained stuck on the Samsung logo screen), Luckily I just picked it up yesterday and was still well within the return policy at BestBuy. I just got it replaced.
So YES, Please just wait until the DEVS post a root process which is tested functional for this specific device.
Just a warning/heads-up based on my very recent experience
ewells38 said:
+1, Exactly. I just experienced this. I tried the root method listed in this thread and it bricked the device. (It just remained stuck on the Samsung logo screen), Luckily I just picked it up yesterday and was still well within the return policy at BestBuy. I just got it replaced.
So YES, Please just wait until the DEVS post a root process which is tested functional for this specific device.
Just a warning/heads-up based on my very recent experience
Click to expand...
Click to collapse
I'd take it even a step further. Don't trust anything from anyone unless they have the xda dev symbol by their name. They are the only ones who have a long track record of putting out quality safe code. If some guy says "hey this is my first rom!", proceed with extreme caution. Might be fine and then again it might not.
These expensive toys break easily. Take this seriously.
I think mod should lock this thread because:
No pic of evidence
No link to the file
OP didn't state which Tab S model who uses.
mingkee said:
I think mod should lock this thread because:
No pic of evidence
No link to the file
OP didn't state which Tab S model who uses.
Click to expand...
Click to collapse
Agreed. I'm like a cop-show me the evidence!
Had a Surface Pro 2, returned it as a POS and got both Tab S slates in exchange-so I'm anxious for root, but not this anxious! !
Rich
ewells38 said:
+1, Exactly. I just experienced this. I tried the root method listed in this thread and it bricked the device. (It just remained stuck on the Samsung logo screen), Luckily I just picked it up yesterday and was still well within the return policy at BestBuy. I just got it replaced.
So YES, Please just wait until the DEVS post a root process which is tested functional for this specific device.
Just a warning/heads-up based on my very recent experience
Click to expand...
Click to collapse
All you have to do is put back in download mode and Odin stock file and you good.
will6316 said:
All you have to do is put back in download mode and Odin stock file and you good.
Click to expand...
Click to collapse
How is that even possible with no stock firmware released?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
FYI, I tried towelroot on an earlier firmware and it appears to be patched. Simplest method here we will have to wait till the teams at TWRP or CWM create a recovery for our device and then we can just flash the SuperSU zip once that's out.
Nothing too hard since our devices aren't locked, just need some attention here is all.
FYI, I flashed the TWRP recovery from the Tab Pro and unsurprisingly it didn't boot into it.
I'm uploading latest stock firmware for the 8.4 model and hopefully should have it up tonight.
jdellingson7 said:
How is that even possible with no stock firmware released?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
www.sammobile.com/firmwares firmware section. sm-t700
Thread closed as this method didn't work for anyone.
Thanks.

[Links] Root AT&T S6 5.0.2 (w/o KNOX trip) OCE / OE2 / OF3 / OF4 (May - August 2015)

[Links] Root AT&T S6 5.0.2 (w/o KNOX trip) OCE / OE2 / OF3 / OF4 (May - August 2015)
Ping Pong root method for 5.0.2
(Thanks to the Keen Team)
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
If your looking to keep root from OE2 and wanting to upgrade to OF3.
(Thanks to Designgears)
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-flashfire-update-t3156221
And for OF3 to OF4.
(Thanks to Wesgarner & Designgears OF3 method)
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-to-of4-flashfire-update-t3181135
As far as October 5th I have yet to see a way to root the 5.1.1 update.
Does it root the S6 Edge?
ENvisiNKeD said:
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
Ping-pong one click app!
No Knox trip but custom status on about phone
Special Thanks to the Keen Team
Click to expand...
Click to collapse
wp4jot said:
Does it root the S6 Edge?
Click to expand...
Click to collapse
Not yet
I made a tutorial video for this root method if anyone needs it! Hope it helps:
https://www.youtube.com/watch?v=eAQ4WBg9xj0
Great job! Thanks!
qbking77 said:
I made a tutorial video for this root method if anyone needs it! Hope it helps:
https://www.youtube.com/watch?v=eAQ4WBg9xj0
Click to expand...
Click to collapse
---------- Post added at 11:32 AM ---------- Previous post was at 11:01 AM ----------
Beta 4 has been posted and it works for the SM-G925A, AT&T's S6 Edge. Thanks!
notobsessivejustcurious said:
Not yet
Click to expand...
Click to collapse
Amazing! Now to find out if it's safe to uninstall all the AT&T crap on our phones! And then lets see if we get tethering, memory manager and download booster!
ENvisiNKeD said:
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
Ping-pong one click app!
No Knox trip but custom status on about phone
Special Thanks to the Keen Team
Click to expand...
Click to collapse
Looks promising. I like that it doesn't trip KNOX but will the "custom status" be a problem?
I'm 7 days into this phone, still have a week to return/exchange it if something is defective. So far it's running fine, dont foresee need to take it back.
But .............. If I did need to return it, is there an "unroot" and/or a way to remove the custom status ?
*** EDIT *** I haven't read all the way thru the root thread, so if my question has already been answered I apologize.
No Custom Status
I have now rooted twice, flashing the firmware posted in this forum in the middle. My phone has not shown custom on the bootscreen once. I also encrypt before I root, so maybe thats it. Who knew you could be encrypted with root?
Have you uninstall all the att bloatware without problems? Or used greenify to improve battery life?
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
SlimJ87D said:
Have you uninstall all the att bloatware without problems? Or used greenify to improve battery life?
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
Click to expand...
Click to collapse
Yes, all the typical rooting items work as they should. You can even flash zips with fireflash, and not trip Knox.
It's NOT in the bootscreen where you can see the custom status. It's in settings / about device / status. In the last line it crearly says "Custom" under Device status.
dave812 said:
I have now rooted twice, flashing the firmware posted in this forum in the middle. My phone has not shown custom on the bootscreen once. I also encrypt before I root, so maybe thats it. Who knew you could be encrypted with root?
Click to expand...
Click to collapse
dave812 said:
Yes, all the typical rooting items work as they should. You can even flash zips with fireflash, and not trip Knox.
Click to expand...
Click to collapse
Awesome! I want to root but I'm wondering how OTA will work now with Android 5.0. I heard it's a little more complicated to get OTA if you're rooted.
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
SlimJ87D said:
Awesome! I want to root but I'm wondering how OTA will work now with Android 5.0. I heard it's a little more complicated to get OTA if you're rooted.
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
Click to expand...
Click to collapse
You'll generally have to manually flash updates once you've rooted, the OTA process will usually refuse to update a device running a modified system image. Not that big a problem, but sometimes it confuses people.
superhyper said:
You'll generally have to manually flash updates once you've rooted, the OTA process will usually refuse to update a device running a modified system image. Not that big a problem, but sometimes it confuses people.
Click to expand...
Click to collapse
Or, install Samsung drivers, then Odin, and flash a stock image that way to return to stock, then OTA works fine. There is another thread around here with a stock image, I'd suggest anyone looking to return to stock in order to complete an OTA, to review that thread.
superhyper said:
You'll generally have to manually flash updates once you've rooted, the OTA process will usually refuse to update a device running a modified system image. Not that big a problem, but sometimes it confuses people.
Click to expand...
Click to collapse
knigitz said:
Or, install Samsung drivers, then Odin, and flash a stock image that way to return to stock, then OTA works fine. There is another thread around here with a stock image, I'd suggest anyone looking to return to stock in order to complete an OTA, to review that thread.
Click to expand...
Click to collapse
Would we be able to use fireflash and keep root if somebody were to get the OTA and customize it for our needs to keep root, etc? I know it's a hard question to answer, but maybe you guys have experience with other locked bootloader devices.
I'm coming from a M7 and M8. Thanks in advance.
SlimJ87D said:
Would we be able to use fireflash and keep root if somebody were to get the OTA and customize it for our needs to keep root, etc? I know it's a hard question to answer, but maybe you guys have experience with other locked bootloader devices.
I'm coming from a M7 and M8. Thanks in advance.
Click to expand...
Click to collapse
This is similar to how we did it on the AT&T S4 using safestrap to flash touchwiz based roms that were pre-rooted. Unfortunately, we wouldn't be able to flash non-touchwiz based roms without an unlocked bootloader.
knigitz said:
This is similar to how we did it on the AT&T S4 using safestrap to flash touchwiz based roms that were pre-rooted. Unfortunately, we wouldn't be able to flash non-touchwiz based roms without an unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the response. I've always stuck with oem based roms anyways.
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
Anyone have any idea on if root for the Edge is coming? I just bought one a few days ago.
darien87 said:
Anyone have any idea on if root for the Edge is coming? I just bought one a few days ago.
Click to expand...
Click to collapse
Pingpong root already supports the edge.
Did you search? Did you click on the link in post #1 of this thread?
darien87 said:
Anyone have any idea on if root for the Edge is coming? I just bought one a few days ago.
Click to expand...
Click to collapse

[ROM][ROOT] Tab S 8.4 - SM-T707V(Verizon) Stock Pre-rooted ROM - Tester required.

I built this ROM as a test for those who have locked bootloaders on the Tab S and can't get root.
In my experience Samsung bootloader locked devices will not allow a custom kernel or recovery to be installed. However it is possible that the bootloader will allow a modified rom to be installed.
The rom is bone stock Lollipop 5.0.2 except it is pre-rooted with SuperSU 2.49. It needs to be installed via ODIN. If ODIN allows it to flash then its highly likely it will boot just fine.
If there are any issues that arise then all that is required is to flash the stock firmware, available here: http://www.sammobile.com/firmwares/database/SM-T707V/
T707VVRS1BOK1_preroot_system.img.tar
If anyone gives this a shot, please report with details.
.
i dont have this device but you are awesome for trying this!
Sent from my SM-T700 using Tapatalk
lev777 said:
i dont have this device but you are awesome for trying this!
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
If it works for the T707v then I'll do the same for the other Bootloader locked devices. It all depends on whether ODIN will flash it or not.
The reason I have used the T707v is because this device at least has the stock firmware available, so it should be relatively safe to try this.
Not many wanting a rooted t707v then.
ashyx said:
Not many wanting a rooted t707v then.
Click to expand...
Click to collapse
It seems the US LTE variants were not very popular, T807T does not have a lot of use either.
deadman96385 said:
It seems the US LTE variants were not very popular, T807T does not have a lot of use either.
Click to expand...
Click to collapse
Seems so, would have done it for the att and other Verizon model if it worked. Wouldn't want to test it out on an att model first with no stock firmware available.
@deadman96385
Anyway I could do to pick your brains about something.
Am I right in thinking you have a Tab A?
ashyx said:
Seems so, would have done it for the att and other Verizon model if it worked. Wouldn't want to test it out on an att model first with no stock firmware available.
@deadman96385
Anyway I could do to pick your brains about something.
Am I right in thinking you have a Tab A?
Click to expand...
Click to collapse
I do have one, what's up?
I don't believe Odin allows modified system images to flash on bootloader-locked devices.
I tried on my Verizon S5, it shouldn't work, but let's see anyways
I have one and I'll try it but I'm out of town for work right now won't be home to try it until the 24th. Would be awesome if it works.
Sent from my HTC6525LVW using XDA-Developers mobile app
Nandr0idC0nsumer said:
I don't believe Odin allows modified system images to flash on bootloader-locked devices.
I tried on my Verizon S5, it shouldn't work, but let's see anyways
Click to expand...
Click to collapse
It does, it depends on the device's bootloader.
Plenty have been rooted or modified this way.
ashyx said:
It does, it depends on the device's bootloader.
Plenty have been rooted or modified this way.
Click to expand...
Click to collapse
Exactly why I said let's see anyways
It's just that the S5 and Tab S are so similar in so many ways and were release at the same time on VZW, that I thought they'd have the same locks.
Nandr0idC0nsumer said:
Exactly why I said let's see anyways
It's just that the S5 and Tab S are so similar in so many ways and were release at the same time on VZW, that I thought they'd have the same locks.
Click to expand...
Click to collapse
You may be right, but nothing ventured nothing gained.
deadman96385 said:
I do have one, what's up?
Click to expand...
Click to collapse
Pm sent
Does anybody with a T707V even use XDA?
Nandr0idC0nsumer said:
Does anybody with a T707V even use XDA?
Click to expand...
Click to collapse
I do and I'll try this next week. Right now I'm out of town for work.
Sent from my SM-T707V using XDA Premium HD app
i ran it it did noithing at all for my t707v did not unlock bootloader or root at all its just the same as factory os
---------- Post added at 07:06 AM ---------- Previous post was at 06:55 AM ----------
Nandr0idC0nsumer said:
Exactly why I said let's see anyways
It's just that the S5 and Tab S are so similar in so many ways and were release at the same time on VZW, that I thought they'd have the same locks.
Click to expand...
Click to collapse
i ran it it did noithing at all for my t707v did not unlock bootloader or root at all its just the same as factory os
tsorensen2931 said:
i ran it it did noithing at all for my t707v did not unlock bootloader or root at all its just the same as factory os
---------- Post added at 07:06 AM ---------- Previous post was at 06:55 AM ----------
i ran it it did nothing at all for my t707v did not unlock bootloader or root at all its just the same as factory os
Click to expand...
Click to collapse
What do you mean you ran it and did nothing at all? It doesn't unlock the bootloader.
Its the stock OS already rooted.
Did it install successfully with ODIN?
What is the state of root when checked with Root validator?
We need screenshots if possible please.
tsorensen2931 said:
i ran it it did noithing at all for my t707v did not unlock bootloader or root at all its just the same as factory os
Click to expand...
Click to collapse
One hit wonder, very helpful...
I have the 807V and am watching this thread very closely. Too bad that other guy didn't provide any info.
Lonestar614 said:
I have the 807V and am watching this thread very closely. Too bad that other guy didn't provide any info.
Click to expand...
Click to collapse
Exactly, if he'd have only took the time to at least let us know if it installed OK with odin. It seems like it did which means that he should also have had root.
Not sure what he was expecting to see?

Categories

Resources