So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )
You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium
linux minimal screen shot, and unbuntu hang up
DanRyan85 said:
You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
Well, not to be insulting, but it was my understanding that moto chopper would only work if temp rooted or had gained root acess previously? I may be wrong. Anyways, the prob. with unbuntu is thing i guess froze (but still ran) after patiently running it like six hours. Last screen at was installing-reinstalling previous "somethings" but I figured need a system clean and would try again. gotta be easier way. so here is my linux minimal screenshot attempt. running root bionic jb ovf file. noticed where it starting going wrong is
chmod: pwn: operation not permitted.
rooting phone...
phone may appear to.......
/system/bin/sh: /storage/rfs0/pwn: not found <-------Right here i noticed the file path on the phone and it's ---> storage/rfs1 Would that have something to do w/ it?
nothing ever vibrates and reboots in flash. got bad flash or something?
MotoChopper works on non TI (OMAP) CPus that are in Motoroal devices.
Coincidentally, it also works on ASUS Tranformer Infinity (and the Prime as well, IIRC).
It does not work on the BIONIC.
The method that works on rooting the JB build on the BIONIC is one that is based upon the older RAZR method - see http://www.droidrzr.com/index.php/topic/16518-root-motoshare-2-old-bug-new-exploit/
Bionic and JB OVA flash superuser binary outdated
Naughtybutbritt said:
So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )
Click to expand...
Click to collapse
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T
To Naughty: Sorry about the mix up that was what I meant to say Moto share 2 NOT Motochopper. I had all the same problems as you after some number of tries with motoshare2 I was in business.
To martin: have you already tried the motoshare 2 on Ubuntu?
Sent from my XT875 using xda premium
toddmartin- you're gonna love me...i gotcha
toddmartin said:
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T
Click to expand...
Click to collapse
Ok so using virtual box the ova Root_Bionic_JB_20130501-4 the fourth ubdate of the orginal release. Now i suggest erasing all superuser apps installed your self and anything to do with them. When it's done right, it will appear on it's own and work flawlessly. No uncertianties about it. Then i've posted a screen shot of the commands with notes to help understand easiest. The instant the command to press hardware key or power/or each volume itself is the instant you want to press it. Now the reboot is instantious kinda itself and gotta be noticing phone unless have ungodly long boot up let me know if the screen shot helped what you were asking.
Related
Okay everybody, first off let me apologize, as I am sure that this is asked quite a bit. However, I am not very savvy with using terminal and such to enable sideloading on my Captivate, and I cannot get any of the methods to work properly.
I started off with the Unleash the Beast root on my phone, then for some reason I thought that froyo was out as an official update, because when I went to check for an update, it would download a package, reboot my phone, then tell me that the update could not be applied. So, thinking that it was due to the root, I had to use Odin to get Unleash the Beast off the phone; however, whatever "update" the phone was attempting to apply still would not work. So I reverted back to root the phone. I have used the One Click Root to program, I have installed BusyBox, and allowed SuperUser access. I am trying to enable sideloading so that I can download the Market Access app, but I am having troubles getting it to work. I have a Mac, and I have used many methods to try and enable it, but no matter what I do it will not work.
Again, I apologize for my ignorance. I have searched all over, and I still can't get this stuff to work. If anybody could provide any assistance, it would be greatly appreciated.
Thanks
goosefraba91 said:
Okay everybody, first off let me apologize, as I am sure that this is asked quite a bit. However, I am not very savvy with using terminal and such to enable sideloading on my Captivate, and I cannot get any of the methods to work properly.
I started off with the Unleash the Beast root on my phone, then for some reason I thought that froyo was out as an official update, because when I went to check for an update, it would download a package, reboot my phone, then tell me that the update could not be applied. So, thinking that it was due to the root, I had to use Odin to get Unleash the Beast off the phone; however, whatever "update" the phone was attempting to apply still would not work. So I reverted back to root the phone. I have used the One Click Root to program, I have installed BusyBox, and allowed SuperUser access. I am trying to enable sideloading so that I can download the Market Access app, but I am having troubles getting it to work. I have a Mac, and I have used many methods to try and enable it, but no matter what I do it will not work.
Again, I apologize for my ignorance. I have searched all over, and I still can't get this stuff to work. If anybody could provide any assistance, it would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
Could you provide a little more information about your phone? Is it stock JF6 with just root? If not provide firmware information and anything else that might be useful
P.S. Questions belong in the Q&A section
I'm not really sure what JF6 is haha...After I used Odin and set it back to stock conditions, the only thing I did was use the One Click Root.
As far as sideloading goes, the One Click De-Cripple method on page 2 of the general forum worked for me. If you want to know what version your phone is, go to the about phone section under your settings menu. If you need or want to upgrade to JH7, which was the last OTA update from ATT, do a search and there are a few options out there for that.
Well unfortunately I cannot use OCD on Mac..I tried to do the command prompts, but the su is asking for a password, which is odd because the way I understand it, it shouldn't be doing that
goosefraba91 said:
Well unfortunately I cannot use OCD on Mac..I tried to do the command prompts, but the su is asking for a password, which is odd because the way I understand it, it shouldn't be doing that
Click to expand...
Click to collapse
You did type adb shell first right? Then you should get a "$" where you then type su. It then echoes back su and you should see a "#".
From what you just said, it sounds like you're attempting to get root access on your mac through terminal, which in that case should be your password.
miztaken1312 said:
You did type adb shell first right? Then you should get a "$" where you then type su. It then echoes back su and you should see a "#".
From what you just said, it sounds like you're attempting to get root access on your mac through terminal, which in that case should be your password.
Click to expand...
Click to collapse
Ok, I got that to work. Now I'm just having trouble entering the code for mac. Like I said, I'm not very savvy with this stuff, so pardon my ignorance, haha.
I'm using the method in the "How to: Remove (Almost) Every Trace of AT&T" thread. (I would post a link, but since I'm a new user, it won't let me)
Is there anything different that I need to put into terminal other than the "./adb"?
I tried to paste the link to this thread but being a new member I am not allowed to post a link because of spam issues. Do a google search for "how to enable non market apps on captivate consolidated" and this will be the first xda thread that comes up.
This thread gives several methods for permanent enabling of sideloading. Being a noob, all of them were a little intimidating to me except for METHOD 3. You don't need a computer and you can do it all on your phone with Root Explorer, SQ Lite, and Terminal Emulator which are all available on the market. The step by step is pretty good and I have done it twice with no issues.
Roof King said:
I tried to paste the link to this thread but being a new member I am not allowed to post a link because of spam issues. Do a google search for "how to enable non market apps on captivate consolidated" and this will be the first xda thread that comes up.
This thread gives several methods for permanent enabling of sideloading. Being a noob, all of them were a little intimidating to me except for METHOD 3. You don't need a computer and you can do it all on your phone with Root Explorer, SQ Lite, and Terminal Emulator which are all available on the market. The step by step is pretty good and I have done it twice with no issues.
Click to expand...
Click to collapse
That method worked great. Thank you!
No prob!
Happy Modding!
Glad you got it working. For the record, the next time you guys wanna post links, just replace the http in the front with hxxp. Most people will fix it when they copy/paste it
Sent from my Captivate
We've heard that you can root the LG Optimus 2X with Z4Root. Is it permanent or temporary?
No supporting evidence just yet, but rooting this phone should be a piece of cake.
I used Z4root on two samples of the 2X, no issues what so ever. These were however pre-release roms, but I couldn't imagine any differences from the final release.
And yes, it's permanent. I had some app testing to do and tried Z4root just for fun and it worked like a charm.
//Dave
Cool. I have already ordered one. Is the root reversible? E.g. can one root an unroot as if nothing happened?
I'm holding the 2x in my hand right now and unrooted it. (didn't try adb on it for confirmation but tried clocksync, which refused access (superuser has disappeared as well). Rerooting at the moment.
Once again this is a pre relase rom so I can't guarantee that the final ROM will have the same functionality.
//Dave
dave79 said:
I'm holding the 2x in my hand right now and unrooted it. (didn't try adb on it for confirmation but tried clocksync, which refused access (superuser has disappeared as well). Rerooting at the moment.
Once again this is a pre relase rom so I can't guarantee that the final ROM will have the same functionality.
//Dave
Click to expand...
Click to collapse
Thanks. Can't wait to get my hands on one.
Good news dave. My understanding is that the main issues with the Optimus 2x so far have been regarding the massive amount of bloat apps as well as some instability in day to day operations (browser and messaging seems to crash from time to time).
Are you experiencing these? Would you be able to remove some of the bloat apps and see if it breaks anything in the LG rom?
UHOH!
Bantu85 said:
Good news dave. My understanding is that the main issues with the Optimus 2x so far have been regarding the massive amount of bloat apps as well as some instability in day to day operations (browser and messaging seems to crash from time to time).
Are you experiencing these? Would you be able to remove some of the bloat apps and see if it breaks anything in the LG rom?
Click to expand...
Click to collapse
I'll take a look at it, I've got an early version of the 2x which I'll try to push the new system dump to. I've rooted it and while using adb shell it looks like I've bricked it! uhoh!
Bricking a pre-production version of the best phone on the planet isn't quite what I wanted to do! I'm stuck in a boot loop and I manage to get a limited connection when booting it into the bootloader. However, probably because of pre-production status, the bootloader will let me go up and down using the volume keys, but it won't let me select any of the options!
When in the bootloader, I do have some type of recognized connection via the PC. DDMS recognizes the phone, ADB doesn't let me access it.
I'll chill on doing anything to the "good" phone for now (hope you understand)... but if I get the bricked one started, I'm back in the game .
Feel free giving me tips or trix to get it up and running.
from a somewhat uneasy Dave
dave79 said:
Feel free giving me tips or trix to get it up and running.
from a somewhat uneasy Dave
Click to expand...
Click to collapse
Have you tried using the power button or one of the other buttons to select an option in the bootmenu?
GIR said:
Have you tried using the power button or one of the other buttons to select an option in the bootmenu?
Click to expand...
Click to collapse
I sure did, thanx anyways. I've used every button available incl, the touch screen corners, tapping on the selection itself.
//Dave
Z4root doesn't work with my sample
No way to root
pocketAM said:
Z4root doesn't work with my sample
No way to root
Click to expand...
Click to collapse
Do you have a preproduction model like Dave or a sales sample?
On mine Z4root simply quits...after saying "Aquiring root shell" ... will try an other version, hope that will work...
Do you have a temporary root? After z4root locks? I tried with a later rom and got the same issue. However after accessing it with ADB shell it clearly has root "#" is showing and I have permissions I otherwise wouldn't have. However it seems like the root is temporary. Weird thing... I'll continue hunting for alternative solutions.
BTW, my other X2 may rest in peace. After a friend helping me out we managed to get the phone into fastboot, the kernel must have been intact, the system was completely wiped. Pushed the system through ADB and rebooted. Now we can't get it into fastboot at all... RIP ;(
//Dave
dave79 said:
Do you have a temporary root? After z4root locks? I tried with a later rom and got the same issue. However after accessing it with ADB shell it clearly has root "#" is showing and I have permissions I otherwise wouldn't have. However it seems like the root is temporary. Weird thing... I'll continue hunting for alternative solutions.
BTW, my other X2 may rest in peace. After a friend helping me out we managed to get the phone into fastboot, the kernel must have been intact, the system was completely wiped. Pushed the system through ADB and rebooted. Now we can't get it into fastboot at all... RIP ;(
//Dave
Click to expand...
Click to collapse
Wow, sorry to hear your loss...sad story.
Anyway, I heard that it is possible to root 2.2.1 devices with Super One Click, but I can't get my Optimus 2x connected to adb, somehow Windows 7 doesn't wanna install the downloaded Google USB Drivers...
The reason Z4root doesn't work on firmwares 2.2< is that the exploit it uses to gain root rights has been fixed in those newer versions
GIR said:
Do you have a preproduction model like Dave or a sales sample?
Click to expand...
Click to collapse
sales sample x press
After update OTA to version LS670ZVC, machine is unable to be rooted at this time. I am sure someone is working on it.
I returned this previously rooted phone Saturday feb 12 for replacement due to HW fault. Got new phone home and saw the phone was auto-updating to the LS670ZVC version. Which kept me from using Zroot as I did in the past. Drat! Tried many tricks found on other android forums to try and root.
The skinny of it is, if this update was applied OTA, we are SOL for now. If you updated using LG software via computer, you can root it still. If you haven't updated from version 9, don't do it until an exploit is released.
I have another thread going on this same issue. I have tried using superoneclick. Even though everything looked ok it didn't make a difference. Did a root checker it said busybox was ok and I know that SU is ok. Just looks like they "fixed" the exploit for now...
Sent from my LS670 using XDA App
domi007 said:
Wow, sorry to hear your loss...sad story.
Anyway, I heard that it is possible to root 2.2.1 devices with Super One Click, but I can't get my Optimus 2x connected to adb, somehow Windows 7 doesn't wanna install the downloaded Google USB Drivers...
The reason Z4root doesn't work on firmwares 2.2< is that the exploit it uses to gain root rights has been fixed in those newer versions
Click to expand...
Click to collapse
Mmmm, sad about the old one, however I got my second device so I'll unroot my it and then try the SuperOneClick option.. I'll let you know. Once again this is a sample but the rom is dated from 2010-12-14 so it must be quite close to production ROMs.
//Dave
Post removed by User.
I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.
SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.
SuperOneClick 2.2.2 Will Work With FRK76 if...
I took the rageagainstthecage exploit file from SuperOneClick 1.7 and placed it in the "Exploits" sub-directory of SuperOneClick 2.2.2 and it worked as well after a reboot. Note: You'll get a warning message about it's incompatibility with Android 2.3 + (not an issue as FRK76 is 2.2.3)
Don't know what the above means
Does 2.3.1 work without modification?
While I still have my 2 year old droid, I don't have my windows computer any more. Is there any way to do this with a Mac?
Noob needing help
sir_lunatic said:
I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.
Click to expand...
Click to collapse
Good day, I've scoured the xda dev & android forums, and haven't been able to come up with a resolution to this: I let the OTA [FRK76 - 2.2.3] update slip through, and now i'm having issues rooting.
Besides the fact i'm running linux, i refuse to use any of the one click methods.. Would rather root manually so i know what's happening.
I'm running Ubuntu & doing this all through ADB / terminal, following the instructions listed in android forums [Rooting the Droid without rsd lite up to and including FRG83D], i get to step 13 and i still see the $ & not #.
As there anyone out there who can assist?
Thanks much in advance!
sir_lunatic said:
SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.
Click to expand...
Click to collapse
how does one get an older version of SuperOneClick 1.7?
envoy510 said:
Does 2.3.1 work without modification?
Click to expand...
Click to collapse
As per i know it does not.
Pete has a stock rooted FRK76 Rom on his website, fyi
My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.
flukehawkins said:
My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.
Click to expand...
Click to collapse
The rageagainstthecage exploit works for the FRK76 build, but I couldn't get SuperOneClick to run without crashing, so I just did it manually.
Download SuperOneClick 1.7
Extract, and use the rageagainstthecage, busybox, su, Superuser.apk with this guide: http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
The only difference is the block device /system is mounted from (the guide says mtdblock3, and I think on the droid it is mtdblock4). Just type `mount` on the command line and look for the line that has /system and check the mount path.
I used superoneclick 1.7 to root a stock frk76.
On a note to new users...if you are on windows 7, I could not get it to work. I had an old xp machine that I downloaded soc1.7 to, when I first tried to run it, my PC posted an error about .net 2.0 framework. I Google, found, and downloaded the net 2 0 framework and it worked instantly.
It did not give me recovery. I used rsdlite and only rsd recovery after I rooted it to install cwm. Once you install cwm go directly to it and flash your new rom.
For me, after I rooted and had a stock rom, my recovery would not survive a reboot. But after moving cm7 and gapps to my SD card, re-rsd recovery. Booted directly to recovery. Flashed. Once booted I went to rom manager and had it reflash cwm recovery again and it never had another issue.
My steps may sound confusing but this is what I did.
I do not have sdk setup completely on my laptop and found this to be extremely easy. It works 100% and supplied no errors. I hope this helps someone else.
Is there a RUU i can run to unroot my phone?
YoungCorruptionV2.0 said:
Is there a RUU i can run to unroot my phone?
Click to expand...
Click to collapse
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.
stkiswr said:
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.
Click to expand...
Click to collapse
Ah okay thanks for the tip. I'll look in the development section for one
YoungCorruptionV2.0 said:
Ah okay thanks for the tip. I'll look in the development section for one
Click to expand...
Click to collapse
You may be able to find it on rom manager but def can find it on peter Alfonso site
How to root VZW Galaxy Tab 2 7.0 LTE
RECOMMENDED METHOD
07/09/2014
Working root method by geohot. This is now the recommended method!
http://forum.xda-developers.com/showthread.php?t=2783157
CAN ALSO WORK ON VRBMI1
It has been said the following root method: saferoot
Has been able to root VRBMI1. Give this a try before using the system image below.
****
!!!!WARNING!!!!
Many of you have been complaining about broken wifi and other issues.
I do not own this tablet anymore, which means I can no longer support it.
Verizon/Samusung released a new update: VRBMI1
Check your firmware version
THE LAST VERSION SUPPORTED BY THIS GUIDE IS VRBLL2.
IF VERIZON/SAMSUNG CHANGED THE KEYS THEY SIGN THEIR FIRMWARE WITH, THAN ANY ATTEMPT TO DOWNGRADE/UNLOCK MAY POTENTIALLY BRICK YOUR DEVICE.
This has been seen on the VZW Galaxy S4 and just recently the VZW Galaxy S3 (The VZW Tab 2 is a clone of the S3!)
If you are on the latest build (VRBMI1), then it is entirely possible things will not work. It is also possible the bootloader unlock may brick your device.
If the root method doesn't work, flash a stock odin tar for VRBLL2.
AGAIN... IF VERIZON/SAMSUNG CHANGED THEIR KEYS, YOU MAY BRICK!
If you are on VRBMI1 and have semi-bricked using this method, flash this stock ODIN image using ODIN 3.04.
DO NOT CHECK RE-PARTITION, FLASH LOCK, OR LED CONTROL
VRBMI1
http://-/android/SCH-I705/ROMs/4.1.2/HOME_I705VRBMI1_1415457_REV02_user_low_ship.tar.md5
The above information is unknown to me. Do all at your own risk!
YOU HAVE BEEN WARNED****
READ FIRST
*** *** *** *** Disclaimer *** *** *** ***
I am not responsible if you break your stuff. READ READ READ
If you DO NOT own a VERIZON Galaxy Tab 2 7.0 SCH-I705 then DO NOT flash this! If you have not verified and flash this on a p3xxx tab, something will break and I will not help you!
Table of Contents
Step 1: Root
Step 2: Bootloader
Step 3: Recovery
OPTIONAL: Return to Stock
YOU MUST DO ALL STEPS IN ORDER 1-3
This will probably trip your flash counter!
Step 1 - root Make sure to READ! Select the correct method below.
Root ICS 4.0.4 - Use if you are on STOCK Ice Cream Sandwich ONLY
This is a pre-rooted J1 base system image. It has all the latest updates from Verizon.
*Pre-requisites*
A. Reboot into stock recovery and data wipe / factory reset.
B. Reboot directly into Download Mode.
*Flash Pre-Rooted System Image*
1. Install Samsung drivers for SCH-I705 - Download Here
2. Download stock rooted 7zip archive and extract ODIN image sch-i705_4.0.4_VRLJ1_prerooted_ODIN.7z
3. Open ODIN ODIN 3.04
4. Select the system.ext4.tar.md5 file in the PDA section, uncheck f. Reset time
5. Press START. This process can up to 10 minutes. DO NOT UNPLUG YOUR TAB!!! Reboot.
6. Press the Thanks button
7. Go to Step 2
Root JB 4.1.2 - Use if you are on STOCK Jellybean ONLY
This is a pre-rooted VRBLL2 base Jellybean system image. It has all the latest updates from Verizon.
*Pre-requisites*
A. Reboot into stock recovery and data wipe / factory reset.
B. Reboot directly into Download Mode.
*Flash Pre-Rooted System Image*
1. Install Samsung drivers for SCH-I705 - Download Here
2. Download stock rooted 7zip archive and extract ODIN image jellybean-4.1.2-rooted_sch-i705.tar.md5-COMPRESSED.7z Just extract it
3. Open ODIN ODIN 3.04
4. Select the jellybean-4.1.2-rooted_sch-i705.tar.md5 file in the PDA section, uncheck f. Reset time
5. Press START. This process can up to 10 minutes. DO NOT UNPLUG YOUR TAB!!! Reboot.
6. Press the Thanks button!!
7. Go to Step 2Step 2 - Bootloader
Unlock Bootloader
Unlock your bootloader
How to UNLOCK VZW Galaxy Tab 2 7.0 bootloader
Go to Step 3
Step 3 - Recovery
Custom Recovery
Flash CWM recovery OR TWRP recovery
How to flash unofficial ClockworkMod
How to flash unofficial TWRP
Once you got custom, NEVER accept an OTA!
Return to Stock
Download stock firmware, ODIN flashable. Extract .md5 from the .zip file. DO NOT EXTRACT ANYTHING OUT FROM THE .md5!
I705VRBLL2_I705VZWBLL2_VZW.zip
Reboot into DOWNLOAD mode.
Connect Device.
Open ODIN, select the .md5 in the PDA section. The ONLY checkboxes that should be checked are Reset Time and Auto Reboot.
Press START and WAIT! DO NOT UNPLUG DEVICE. IT WILL REBOOT ON IT'S OWN!
You are now stock.
Original root method for VRALG3 (original factory firmware) was achieved using RootDebugFS.bat
Thanks to
miloj
Noxious Ninja
sparkym3
joYstick61
Ezgoing2406
Scrosler
Good job man. I hope the vtab gets its own development subforum here. Xda has a request thread for new threads for new devices. All of you with these new tabs should go post in it.
Edit: this is the thread. http://forum.xda-developers.com/showthread.php?t=1660354
I posted in it in hopes of getting it done. Good luck vtabbers
THIS WORKED!
Just wanted to post in this thread too... so ppl know that this method works...
Thanks again MrHyde
Nexttonomy
Thanks for the tip Scottx. Posted there as well and you're welcome nextonomy!
Root Fail SCH-i705 Galaxy 2 Vzn LTE 7.0
cant figure out why this isnt working... could someone give a little more detail about why? followed every step to the letter.
Thanks in Advance
leakim13 said:
cant figure out why this isnt working... could someone give a little more detail about why? followed every step to the letter.
Thanks in Advance
Click to expand...
Click to collapse
Are other apps such as TB, Terminal, or AdFree Android able to gain root privileges? If so, then Busybox Installer may have been denied. Check Superuser and remove it from the Denied list if it's there. After removing it, try again and make sure to tap "Allow" when it asks.
EDIT: Downloaded that app to test. SU asked if I wanted to grant SU permissions, tapped 'Grant'. All is fine. If it's NOT in the SU denied list, Force Close the app. Reopen it and it should ask.
This is awesome. Thanks! One thing - is there a way to stop the OTA update nag?
Xer0daze said:
This is awesome. Thanks! One thing - is there a way to stop the OTA update nag?
Click to expand...
Click to collapse
Do this
MrHyde03 said:
Yes, using titanium you can freeze SDM.
Green icon with a phone and up arrow. Freeze or uninstall with titanium and verizon won't know what hit em.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yes, using titanium backup freeze or remove SDM
Sent from my SCH-I535 using xda app-developers app
Thanks, I did that. I also noticed in system/app there were SDM.apk and SDM.odix. I went ahead an renamed them SDM.apk.bak and SDM.odix.bak. I'm hoping this will get rid of the nag notification. One last thing - the update tried to run overnight once but CWM stopped it. When I woke up the tab was sitting on the CWM screen. Since then every time I reboot the tab it acts as if dalvik cache was cleared (I get the "android is upgrading - optimizing applications" screen before the tab loads). I think OTA set a reboot/clear cache flag somewhere I need to clear, but I don't know where that is set. Any ideas? Thanks again.
That will get rid of it. As for the reboot issue, have you tried clearing cache? Or even a factory reset? Factory reset won't hurt your root any nor restore the update app.
Thanks for the reply - Yep. I factory reset a couple days ago and made the update changes mentioned earlier. I no longer get the OTA notifications (YAY), but every time I restart the device it still rebuilds cache. I've formatted the cache partition, cleared dalvik cache, and as I mentioned, I tried a factory reset as well. This is the only hurdle I have left to clear. Out of curiosity, why are there no custom roms for the VZW version of this device? The VZW version doesn't carry the same model numbers as the retail models (GT-Pxxxx). The verizon device is simply SCH-I705 - there don't seem to be any roms for that. Isn't the only real difference the radio? I've asked around the forums, but not gotten a reply from anyone on this. I'd love to try some custom roms on this tab, and I'm sure that would fix the majority of my issues, but I have yet to find one.
There is actually a big difference between the wifi and lte devices. The i705 is closer related to the i535 (gs3) than it is the wifi tab 2's. And there are no custom ROMs yet becuase there are so few of us that own it, and even fewer (two of us actually..) who are trying to get anything done on it. I'm a novice developer so I'm still learning the process of ROM development. On top of that, I'm very busy working two jobs, saving up for a wedding. Unless someone else is capable of getting more development done we may only have 1 or two custom stock roms floating around, which is what I'm working on ever so slowly. CM10 and the others a bit out of my league right now.
If anyone wants to try to bring more attention to this device, feel free to do so. It'd be helpful to have people who know what they're doing more than me.
MrHyde03 -
Thank you so much for the detailed information. That is exactly what I've been looking for... exactly THAT. Congrats on the upcoming wedding by the way. That's awesome.
I might be willing to donate or lend a device to the right person if potential exists for that to result in a working Rom.I wouldn't know where to begin on that. I am in the Seattle area but can ship if necessary. I like CM10 and have Paranoid Rom (based on CM10) running on my GS3 and I'd absolutely LOVE to have the same features on my SCH-I705. I have the tab mounted in my car and It's a really great device, but the stock rom is HORRIBLE. For one, this 'loud volume warning' (whenever playing music over headphones or line output, it decreases the volume because, according to Samsung, I'm not a big enough boy to make my own decisions with regards to my own hearing) is driving me absolutely crazy. My GS3 did the same thing, but since I've rooted and loaded custom roms on it, I've loved it.
Thank you again for being one of the few to reply to my questions and for providing these details, you are appreciated.
I'm getting this:
Step 1 - Pushing files...
failed to copy 'debugfs' to '/data/local//debugfs': Permission denied
failed to copy 'su' to '/data/local//su': Permission denied
failed to copy 'debugfsinput' to '/data/local//debugfsinput': Permission denied
failed on '/data/local/tmp' - Permission denied
link failed File exists
Rebooting...
Once your devices has finished restarting,
Press any key to continue . . .
Step 2 - Rooting...
For this step, ignore any error messages that say "File not found"
Unable to chmod /data/local/debugfs: No such file or directory
/system/bin/sh: can't open /data/local/debugfsinput: No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/debugfs, No such file or directory
rm failed for /data/local/debugfsinput, No such file or directory
Rooting FAILED! You may want to try running this tool again.
Your device region may not be supported if you see this message again.
Press any key to continue . . .
Could this have anything to do with me not yet having a sim card for the device (region??)?
I get permission denied errors when trying to push su and other files. Cannot obtain root. Any help?
What version android do you have? This is only confirmed on 4.0.4.
Sent from my SCH-I535 using xda app-developers app
MrHyde03 said:
What version android do you have? This is only confirmed on 4.0.4.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
4.0.4
I'm gonna try again today now that I have a sim, but I doubt that's the issue.
---------- Post added at 03:09 PM ---------- Previous post was at 03:02 PM ----------
JelloB said:
4.0.4
I'm gonna try again today now that I have a sim, but I doubt that's the issue.
Click to expand...
Click to collapse
Same thing. No luck.
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
RevosFTS said:
I get permission denied errors when trying to push su and other files. Cannot obtain root. Any help?
Click to expand...
Click to collapse
Looks like we're having the same problem.
Yeah we have the same exact error. I am tempted to try manually pushing the root files through adb. I may have to call the banners though. Perhaps Liquid would be willimg to help.
Damn, if I had only seen this before I went TO the Verizon store, lol.
Oh well. I was just going to root and get a ROM out for everyone.
If anyone finds root let me know and I can start ROMS!
OP: You should put "not working" in title so people dont fill the thread with.. OMG it doesnt work!
I took the JB OTA update. Which works great except the phone wont allow me to access my dialpad mid-call sometimes...weird. Anyway, I used Voodoo OTA Root keeper and took the update and restored...all check marks there, but no root. So i decided to wait for an exploit for a lil while and then i got my wish! Which using ubuntu and the terminal and not windows seemed easier to me so i set it up.
Did all the steps and it worked! or so i thought...phone vibrated and came back on with the superuser apk etc. Check with root checker...no root. Not sure where my conflict is coming from now? Not sure if I should Fxz JB 4.1.2 or what, I've been reading some things on that thread, different problems people have had seemingly with the firmware. I didn't think it should matter as far as rooting the phone goes, but one person was saying that using it would stop the exploit from working? Never thought that would be the case, am i missing something?
Also, my phone after i tried both of these keeps asking me to update my superuser binary. First with one superuser app and now with the one that was with the exploit package and i can't seem to do it. Feel like i'm missing something simple here but i'm not sure what it is?
Did you wait for the vibrations and then press a hardware button, like vol up or dn? Others have reported having to go through the exploit more than once to get it rooted. Give it another try. I was able to get root on the second try, but I royally messed up the process the first time.
Embarrassing, but no I forgot the hardware button. Worked like a champ second time lol my advice don't do this late when your not awake, follow all the steps!
Sent from my XT875 using xda premium