[Q] LG Optimus vs410pp Rooting - Android Q&A, Help & Troubleshooting

I mulled over the suggested threads from 2012 (because I live under a rock), and am desperately trying to root this phone.
So, this is the about in the phone section.
Optimus Zone vs410pp
Model #: LG-VS410P
And Version: 2.3.6
Baseband version: MSM7625-0-AA
Build #: GRK39F
Software Version: VS410PP2
I feel like I've tried everything for this phone to Root. Currently going to try SuperOneClick again, but if anyone knows of a sure fire way to do this, please explain in the most simple words you can. I don't care if you drag it out to 39 steps... Pretend you are teaching a potato to use a phone... I know... I need help, but that will come later.. Right now... I need a rooted phone....
Thanks for helping this poor vegetation understand human stuff....
.:Edit:.
So, I just so wonderfully found out that I can't post links as of yet, and was told so via the forum eating all of my extra content I just added. Isn't that nice? You guys should change that to a default "Return to edit" instead of just removing the 2k words I just wrote to help communicate my issue. Thanks XDA-Forum CSS coder. You're a real pal.
Now, moving on to the issue at hand. I'm following a guide, Thread A, that led me to another step by step instructional thread. This is the thread we will call "Thread B".
This is a quote from Thread B.
5. If you have to manually update the driver, you may have to go about it the long way. I had to click "Browse my computer..." then "Let me pick from a list..." then "Have disk..." before browsing all the way to the Universal ADB folder, plus I had to click "OK" through several warnings.
Click to expand...
Click to collapse
So, my issue is that I've only had to update drivers manual three times in my life, and they were point and click issues. There was zero decision making. Now, with ADB, which I'm assuming I need as SOC is working, but not rooting the phone correctly. How do I update drivers for this? When I plug in the phone I have a few options in the device manager, and I'm unawares of which I should choose being a potato, and all. Past that, I've around 9 different doo-hickies (yes.. doo-hickies... They are not the standard .dll that I normally run into, and all have very different unknown extensions) to choose from. Do I install them all individually, or is there something I can do to expedite this process, like naving through my sys files, and d&d all these doo-hickies at once so my computer knows LGE Optimus Zone phonespeak?
Thanks to anyone whom may shed light on my plight.
.:Edit:.
To add additional content to my trails, I am currently repeating poot to see what happens here as a user suggested to repeat it after removing the battery roughly ten times to see if poot will slip past the demon. Thus far, I have generated tree-fiddy demons. I'm unsure as to where the demons are materializing, but Poot continuously suggests they are doing such. Potatoes aren't particularly afraid of demons, but this is very inconvenient for them to get in the way of my electronics.
If you've information on any method of adding the access of the phones origins I would be most generous in my thanks.

Related

A newbies guide to Rooting the MyTouch Slide 3G

How to Root the MyTouch Slide
v1.0 Brandt DeLorenzo 7/19/2010
(I tried to add links, but I couldn't because I was still a newbie on the forum...oh well)
Required Hardware
Windows, Linux, or Mac Computer
USB Cable
T-Mobile MyTouch Slide with SD card
Required Computer Software
ADB Drivers for your computer
The Android SDK
Command Line editor
Required Files
Root.zip
MyTouch Slide Rom(s)
Optional Apps
Rom Manager (by ClockWorkMod)
Any backup app from the market (like MyBackUp Pro)
Step 1: Install Required Software on the Computer
I. In order for your device to communicate with the computer, you will need the proper ADB drivers. ADB Drivers should install automatically when you attach your MyTouch Slide to your computer when using a PC. If you need to manually install the drivers for a PC, locate and install the HTC Sync Update program on your computer.
II. On the device, go to Settings > Application > Development and turn on USB Debugging.
III. Download the Android SDK and unzip the directory in your C: drive somewhere where you can easily find it. I’d also suggest renaming the SDK folder from android-sdk-windows to something shorter, like “asdk”. You do not need to install anything inside that SDK folder after you unzip it. Just move it to the C: directory and rename the folder to something short and easy to type, like “asdk”.
IV. You need to add the Android SDK Tool folder to your system path if you’re using a Windows PC. Go to Control Panel > System > Advanced > Environment Variables > In System Variables, highlight "Path" and click Edit. Add C:\asdk\tools to the end of the string. Be sure there is a semi-colon between the last entry and C:\androidsdk\tools. For example, it might look like this:
C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\asdk\tools
Then click OK on all of the windows and you're done with this step
V. Be sure that you have a working command line editor for your computer. For example, Windows users can go to Start > Run > (type CMD) > OK.
Step 2: Download and Move Some Files
I. Download the Root.zip file from Eugene's thread about rooting the Slide, unzip the contents (update.zip, ota.zip, and loop) and place them all in the C:/asdk/tools folder. This zip file contains all of the files that will unlock your MyTouch Slide and install the Recovery software to make everything easier in the future.
II. Find the MyTouch Slide Rom that you want to install. You may download as many as you want if you plan on switching between different versions of Android. You can find many of those Roms here or on AndroidSPIN. Download them to your computer and then move them to your SD card. They should be anywhere from 50MB to 150MB each.
Step 3: Preparing for Root
I. Before we begin the process, we need to test ADB to make sure your device can be seen by the computer. Connect your MyTouch Slide (it should be on right now) to your computer via the USB cable. Open up your command line editor and get to the Android SDK tools folder. If you named your SDK folder ‘asdk’, then you would type CD C:/asdk/tools and hit enter. You should see the prompt change from C:/ to C:/asdk/tools>. Type loop and hit enter.
II. If ADB is working, you will see a continuous loop of commands running up the screen. Hold down Ctrl+C to temporarily stop the loop and look for something that says:
List of Devices Attached
HT05RPS02484 Online
If you see something like this, type Y and hit enter. (Your device number may be different than display above)
If ADB is not working, go here to troubleshoot ADB and make sure that you can get the loop to detect your device before you go any further.
III. Perform a backup of any applications or data that you would like to restore. I’d suggest backing up applications, contacts, or any data that may not sync back to your device. You can find an application in the Android Market to complete these tasks. I prefer MyBackUp Pro.
*Mac and Linux users may need to put a ./ in front of anything that is typed in the command line. Like ./loop instead of loop.
Step 4: Beginning the Root Process
I. Power off your device. Hold the Volume Down Key and Press the Power button at the same time. Hold both buttons until the screen comes up in Bootloader mode.
II. In your command line editor, be sure that you are in the C:/asdk/tools> prompt. Type loop and then hit enter. You should see:
List of Devices Attached
HT05RPS02484 Offline
III. Select Recovery from the menu. Use the volume buttons to move up and down. Use the Power button to select the option. You should now see a dark screen with a black device and a red triangle with an exclamation point inside. Hold the Volume Up button and press the Power button. You should now see the Android system recovery (2e) screen.
If you kept the loop running, it should change to say:
List of Devices Attached
HT05RPS02484 Recovery
If it doesn’t change, unplug the USB cable from the device and plug it back in.
If your device number and “Recovery” appears, you can now stop the loop with Ctrl+C. If you do not see your device number and “Recovery”, you need to power off your device and try again. This may take a few tries.
IV. On the device, scroll down to Update.zip and select it using the Power button. It will display an error message that it failed. This should be expected and is part of the process.
V. In the command line editor, you should still be in the C:/asdk/tools> prompt. Type adb push ota.zip /sdcard/update.zip and hit enter.
VI. This is the most difficult part of the process. Type adb push update.zip /sdcard into the command line editor, but do not click enter yet.
VII. On the device, scroll down to Apply sdcard:update.zip and as soon as you select it with the Power button, click enter in the command line editor on your computer. The process should be all done within a second. If you did this properly, a new window in green text should appear with the title “Clockword Mod Recovery v2.5.0.1” or another version number.
VIII. Now you are in Clockwork Mod Recovery. First, scroll down to the partitions menu and make sure it does not say ‘mount system’. If it does say ‘mount system’, highlight it and hit the Power button to mount it.
IX. Scroll down to apply sdcard:update.zip and click the Power button to select it.
X. Power down the device. Follow the steps to get back into ClockWorkMod Recovery, but you won’t need to complete step VII. Simply select Apply sdcard:update.zip and hit the Power button to get back into ClockWorkMod Recovery in the future. (If a blank screen appears when you hit the Power button, press the Trackpad as the enter button.)
XI. On the computer, you should run the loop command to determine if the device is connected again. If it is, type adb install superuser.apk and hit enter. You have full root access.
Step 5: Installing a Rom
I. If you have already performed a backup of your files, you can now wipe the device from the ClockWorkMod screen. Scroll down to wipe data/factory reset and hit the Power button. You will be prompted with another screen with a Yes – delete all user data prompt. Select Yes – delete all user data and hit the Power button.
II. After the wipe has completed, scroll to install zip from sdcard and hit the Power button. Then scroll to choose zip from sdcard and hit the Power button. Now locate the Rom you want to install. Press the Power button to select the Rom and install it.
Managing your Roms
To make your life easy, download and install the Rom Manager application by ClockWorkMod. From this application, you can backup & restore your Roms, reboot into recovery with one click, partition your drives, and find new supported Roms for your device.
we already have a root and a simple root if a noob cant get root with either one they dont need root this thread is unnecessary and ,imo, more confusing especially w/o links
i agree, we've already got this pretty much in 2 different threads, in 2 different ways, one fully automated and the other manual. and i created a video and a tut that has more detail as far as how to install roms and such.. this is an unneccessary thread
Sorry man :/
where is my blow torch...prepare to flame
There is also ....
There is also a questionable step.
I cant get into Clockwork mod using the start update from the phone then push update.zip.
But if I adb push first, wait for the server to start, then updat from the power button on the phone, it works.
good luck.
nice guide! thanks
HighRidas said:
we already have a root and a simple root if a noob cant get root with either one they dont need root this thread is unnecessary and ,imo, more confusing especially w/o links
Click to expand...
Click to collapse
No offense, but I've tried many of the guides and they were difficult to follow when ADB was acting dumb on my laptop. The actual steps are easy, troubleshooting ADB on a Windows PC is a pain for most. Now that I have root and I'm using different roms, it's all easy and painless.
If there wasn't a no-linking rule on new user threads, it would have been much better...I agree.
between the fact that it doesn't need to be any easier, and the ROM bibke holds most of this, there is no need for this thread, i understand that you were probably trying tobe helpful but you are an idiot and made a perfectly useless thread with no links for no reason
tubaking182 said:
between the fact that it doesn't need to be any easier, and the ROM bibke holds most of this, there is no need for this thread, i understand that you were probably trying tobe helpful but you are an idiot and made a perfectly useless thread with no links for no reason
Click to expand...
Click to collapse
calm down bro !!! since i came to the slide side all i see is u going hard on people .. that ****'s not cool at all !!! it makes me wonder about u !!!
everybody got their pitch forks and torches out !!! just closed the thread that simple !!!!
i am helpful when stuff i posted in the correct forum, and when it is a new thread that has not been posted in th past. when people continuously post new threads to state stuff that has already been said, especially since without links this thread is pointless, then we xda devs are going to get upset, devs do not like to see pointless threads in the dev section, and certainly don't like it when people try to belittle the work that went into root by "making it easy" first requirement for having root is to know how to use a computer, after that you can learn to do some really cool stuff
Well I thought this guide WAS Helpful to be honest! Not to mention lesstalk was just trying to help. Tubaking is always busting peoples chops everytime he says something it ends up being rude! If you dont have anything nice to say then go to a diff thread dude cause your sorry azz attitude just makes it so people dont want to post cause their scared of getting verbally bashed by folks like you! Being rude is NOT doing anyone any good and Im sure im not the only one who feels this way about you!
in my opinion they should be afraid to post, if they aren't then they make crap like this. i stated that he was trying to be helpful but without links this thread just takes up space and makes people ave to search harder to root thier phone. i am a nice person IRL, but i do not like wasted space. if someone has come up with a "easier" way to root then fine, but there is already a thread for preparing to root your slide, two threads on rooting your slide, and the slide rom bible which includes all of those threads, a stickie should be more than enough for most people and if not then they need to think before hitting that new thread button. there is no need for repetitive threads in the developement section. if there had been links in this thread(which i know he can't do as he is a new member) then it would have been fine and i would have shut up and left it alone, but right now there are two ways to root, one for computer people and one for script kiddies, either way if you can't get it to work with either method then you probably don't need root. if you can't read the simple walkthroughs then you don't need root, if you don't know what you are doing then you don't need root
EDIT: Here is the link to the thread that already covers all of this, and guess where i found it
http://forum.xda-developers.com/showthread.php?t=708522
I did find this thread helpful, especially since i'm new to android. I want to know what i'm doing and the only way i can learn what i'm doing is from reading many posts and lots of trial and error.
I have read both of the rooting guides from the rom bible, and there is still some stuff left out. I actually like this guide better than the others because there is more help in the whole ADB part of the root process.
Now, i know what i'm doing with computers, it still freaks me out how much i can do with computers. But in new areas where i want to learn, it helps to have more info than needed because people have different viewpoints on the same process.
@tubaking182 - for most of the threads you come in bashing in the dev section, i agree with you. But on this thread, i think you're way out of line. Yes there are 2 threads already and yes this thread needs links. But it's not a waste of space. I've lurked on xda since i bought and returned my HD2 (~late april). And when the slide was released, i headed to this subsection. And i've only seen it go down hill with more people posting threads that needn't be posted, but also with "wanna-be" mods flaming the person who didn't think and posted the needless thread.
But now that animosity has taken a turn for the worst and i only seen bashing in this section of the slide section of xda. And it's really making me want to leave xda.
The whole rooting process can be easy to learn if you've come from a previous android phone and have previously used ADB commands. But when you're really lost about even the whole linux folder structure (i'm not totally lost with this, but i'm more used to the desktop linux folder structure), then some of the guides out there to do certain tasks seem like another language.
3 guides for the rooting process can't hurt, especially when someone who doesn't know what's going on in the process wants to figure it out step by step and is too afraid of members like tubaking182 are always going on about searching for previous posts and flaming for simple questions (not that people shouldn't search for previous posts and threads).
EDIT: i do commend all the devs for their hard work making anything like rooting the phone remotely possible.
tething is, when you want to post an issue about something you saw in another thread, the issue should be posted there, it will be answered when people see it or when the OP has time to get on and answer. i am not trying to be a "wanna-be" MOD as i don't ned to be on XDA any more than i already am regulating posts and mergng threads when they should be merged, this thread holds ZERO new info and therefore should not be posted. if this member found a simple one-click root(which i hope to god never happens with this phone) and he wanted to tell us about it and tell us what he searched to find it and whatever else then great i ould not care, but some things do not need a new thread, if users all searched the Q&A section, the General section, and the Dev section BEFORE clicking the new thread link at the top then we would probably have half as many pages in the dev section, we have 8 pages now that i have gone through in the dev section and i have seen way too many repeat threads and questions. if you wanna see who i am take a look through my posts, i am a very helpful person when people want HELP, but when people want ANSWERS and they want stuff easier and they post in the wrong section then i get irritated and my messages are less helpful.
the number one reason n00bs post in here is because more people will see it, unfortunately this means the devs have to deal with the BS threads that push their stuff to page 3-4 and most people don't read past page two to look for a thread
yes, but you have to remember this is a very publicized and a public forum. In another forum i belong to, this happens all the time even though we have clearly marked stickies in every section.
I bet you most of the pointless threads have the OP posting only once and never even commenting on the posts made after they got the answer. That is what happens when you have a forum that's known for phone customization (or any public forum for that matter).
EDIT: and i'm not saying you're mean, i'm just saying it's going a little too far.
EDIT 2: if someone makes a thread only looking for answers that have been previously posted, just don't respond to it as that person won't ever be back. it's as simple as that.
@lesstalk - Thanks for the guide, outside of the lack of links(out of your control) this is a wonderful guide that I have started pointing new MTS users to.
@tubaking182 - Fact is, the guide on this actual covers steps that were skipped over in the other root guides because they were assumed to be common knowledge. Its that assumption which will kill future android users desire to learn about the device, especially when its accompanied by such a poor attitude from the "regulars" of the forum.
Outside of the links being missing due to being a new user account on the forum, the guide was more complete and comprehensive than any of the other guides so far. It managed to cover step(s) that are easily overlooked by someone who has rooted other android phones before, but CRITICAL to function and not mentioned in the other guides. I cant count the number of people I pointed to the pre-existing threads on rooting for MTS, who completely missed the superuser.apk setup because there were not any steps written for it.
A well educated userbase is a happy and quieter userbase, and while there are alot of useless threads in this section, this one actually served a purpose.
^^^
Here here!!
This is the first guide that has explained it all, and now I feel like I can do it too. I've done my g1, and tons of wm phones, but this one is completely different. All depends on your background.
You should be trying to expand and diversify the user base, not alienate it. or would you rather lock up the keys and argue with your self all day?
Sent from my T-Mobile myTouch 3G Slide using XDA App
I agree that this guide might Hold your Hand & even ( Might have missed steps ).
It's not my Job, nor any others person job to make sure you have your driver's setup & adb working correctly. There is plenty of other threads that already cover this, easy to find by using Google..
regardless, Thank you to the OP for try to help make things a bit clearer
~Eugene
tubaking182 said:
i am helpful when stuff i posted in the correct forum, and when it is a new thread that has not been posted in th past. when people continuously post new threads to state stuff that has already been said, especially since without links this thread is pointless, then we xda devs are going to get upset, devs do not like to see pointless threads in the dev section, and certainly don't like it when people try to belittle the work that went into root by "making it easy" first requirement for having root is to know how to use a computer, after that you can learn to do some really cool stuff
Click to expand...
Click to collapse
i feel u on that u do have a point !!! some people just that "dumb" and can't help it. they should post in the right thread but at the same time just putting them down isn't always the best way !!
dcowboys2184 said:
i feel u on that u do have a point !!! some people just that "dumb" and can't help it. they should post in the right thread but at the same time just putting them down isn't always the best way !!
Click to expand...
Click to collapse
Ditto. This is a redundant and unnecessary post. There are more than four different guides and several other posts on preparation. Yes, they aren't written for a kindergartner, but rooting your phone isn't supposed to be easy. Do some research, read a post or several, and only post after your eyes start to bleed. Cluttering the forum makes it even harder for new members to the community.

Searched and NOTHING!

Hey guys, so I searched and search, using the search function as described in the forum rules, and couldn't come across anything with this nature, so if anyone has an urge to help out a noob I would really appreciate it!
So I downloaded the new Android Desire V4 rom, someone told me there were instructions in the download, which there were...they read as follows...
set mtype 2524
set ramaddr 0x20000000
set ramsize 0x0fc00000
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline ""
boot
So my question is, again, um how do I do any of that! LOL Those look like a list of things I am supposed to do as opposed to actual instructions on how to do them LOL
If I run HaRet, it boots, but from my understanding I need to do the above list to make it functioning to it's (current) fullest potential?
Thanks for any assists!
i haven't tried android, not interested in kids play things, but that to me lookslike a list of setup commands, , sure they aren't supposed to go in an initialization file of some kind?
thats the startup txt details, and all you hav to do is copy it all to ur sd root and thats it its honestly not worth it at the min unless u just gonna play about for a bit
hmm
samsamuel said:
i haven't tried android, not interested in kids play things, but that to me lookslike a list of setup commands, , sure they aren't supposed to go in an initialization file of some kind?
Click to expand...
Click to collapse
Probably, but I don't even know what that means! LOL
I am like a super noob..haha.
I guess I am asking specifically what you would do, every step, to do the list of setup commands.
1. How do I change to those values, like which part of the phone I go into.
2. If they need to be installed, how exactly, specifically do I install them.
I am basically looking for full instructions. For example if I were teaching someone to watch a DVD who has never used a DVD/movie playing device before, I wouldn't just say "put it in and watch it." I would say. "This is the power button. Click that to turn the device on. This is the open tray button, click this, and place the DVD shiny/mirror side down flat. Click the open tray button again to close the tray. Once closed it should automatically play, if not click the button with the sideways triangle on it to start the movie."
Like that is how nooby I am with this stuff LOL..but not stupid enough to change something I shouldn't, screw something up. If the instructions are there, I got it.
Demon_man said:
thats the startup txt details, and all you hav to do is copy it all to ur sd root and thats it its honestly not worth it at the min unless u just gonna play about for a bit
Click to expand...
Click to collapse
So I don't have to do anything? I have booted Android Desire V4 rom about 22 times so far, and every single time it is stuck in fast forward mode, does not give me the sim option like in the instructions on the website to download the file, and is generally the exact opposite of what everyone is claiming it is/doing.
So I would assume I am missing some key crucial steps no? Also My radio rom is fine, I reformatted my SD Card, it's fresh and all files are on the root of the card. From the sounds of it, you have to do something with the zImage (from what I have read), and something else... this is why I am confused.
as far as i'm aware there are still a few issues where certain models cant run it properly? and isn't there something about there being a few different digitizers, and it only works on some? (that might not be an issue anymore, i've not been keeping up)
i tried android quite a few times on my previous device (htc kaiser). i believe nearly the same concepts apply to the HD2 at the current stage of android development for the HD2.
facts:
1. you should know that android's files are to be kept on the sd card according to the instructions (more details here: http://forum.xda-developers.com/showthread.php?t=719646)
2. you should know that your windows and any settings made under windows will remain INTACT. this is because android, being in the storage card, is like an independent operating system.
3. point 2 above implies that any settings specific to windows or specifically made in the windows system settings (etc) have NO IMPACT on android. so no need to ask:
1. How do I change to those values, like which part of the phone I go into.
Click to expand...
Click to collapse
4. the only things important to android are the radio ROM version and MAYBE the (Hard)SPL version.
5. android is spun into action using "haret". haret is a little program that is started from windows but it essentially kicks out windows (temporarily) and tricks the phone into booting android from the sd card.
so from all of the above points, we can conclude that any and all configurations for android must be made in some text files. this text file must be placed according to the instructions somewhere along side haret and the rest of the android files on the sd card. this should answer:
2. If they need to be installed, how exactly, specifically do I install them.
Click to expand...
Click to collapse
this text file, as suggested by demon_man in post 3 in this thread is the "startup.txt". another name for startup.txt is "default.txt". these files are the same, except that haret pre-selects "default.txt" as your startup script when you launch haret. this saves you the step of manually selecting a particular startup file (you can have a bunch of startup files with different settings in each to experiment and you can name them ANYTHING). so after experimenting, you should arrive at a startup file containing configurations that work well for you. you can then name this file as "default.txt" and you can also optionally delete all the other startup files you created while you were experimenting.
i hope the above gives you some idea of what to do. if i had tried android on the HD2 for myself and if i had personally done more research of android on the HD2, i would have certainly given you some links of material that i am CERTAIN already exists, if you fancy searching just a little bit. being a noob is no excuse, because "search" is the FIRST forum rule. and just saying that you searched without posting some example keywords of what you searched for sounds "fishy", so not sure you searched well
i have written the above to help you build your concept, but we would all applaud for you (yay!) if you post in the appropriate threads for android and android tutorials from now on. i doubt you will need to post more because what i have tried to detail for you above should be a very solid foundation for you to understand how the wonderful people here at xda have gotten android to work on devices it was never released for.

[Q] Rooting T-01D/ F-05D

Greeting,
It was heard that rooting T-01D are similar as F-05D.
I found a website regarding rooting F-05D, but I dont read Japanese, just want to know if anyone have tried the enclosed method to root T-01D?
or could anybody do the translation, since the terms become quite strange after using the online translators
The following link is ref. of rooting F-05D:
ttp://ayati.cocolog-nifty.com/blog/2012/01/f-05droot-1d0b.html
(should be "http" rather than "ttp")
The source code of T-01D have been provided also, but I have no idea how to use it and root the machine:
ttp://spf.fmworld.net/oss/t-01d/data/download.html
(should be "http" rather than "ttp")
Thank you very much in advance?
Update of 4/4
the following t-01d rooting procedures is provided by Magimaster
Hello.
I am sending this pm regarding the translation for flashing the Fujitsu f-05d sold by Docomo in Japan. I cannot reply in the development section due to my low post count.
My phone is an f-05d. I do not have a t-01d but, according to the original rooting guide for the f-05d, the users are reporting success in rooting the t-01d as well.
I will not really translate for you. Rather, I will explain what I did to root my f-05d.
Here is a rough summary of the steps I followed:
For starters, you need to make sure that adb recognizes your phone when connected to the PC via USB. This means that you need to install the Android SDK and the USB driver for your t-01d by Fujitsu.
I had trouble getting adb to recognize my phone, as Window$ insisted in recognizing it as an USB drive. What I did, among other things, was:
In the phone settings, go to Applications > Development and check USB Debigging and Stay awake.
Install the Google USB Driver package, in the extras section of the Android SDK Manager.
With the phone connected to the PC, go to Window$ device manager > Universal Serial Bus Controllers and uninstall (use the delete key from your the keyboard) every mass storage device that appeared when my phone was connected. Disconnect and reconnect the usb cable.
Only until I did this final step was my phone recognized and listed as Android Phone > Android Composite ADB Interface in the device manager. If your device is not recognized, you just cannot continue. Look for help about this, or else you cannot move on with this method of rooting.
Confirm that your phone is recognized as Android Phone > Android Composite ADB Interface in the Window$ device manager. Do not continue until it is.
From the Android SDK manager, install the package android sdk platform-tools.
You need download F05Droot.zip from the original blog page your linked before. I will not link to the file directly, but you should have no problem finding it. Extract the files within into the program directory \Android\android-sdk\platform-tools (this is my path).
You need to download a replacement for the file lsm_disabler.ko that is inside the F05Droot.zip. Get it from here and extract it an replace the one inside the platform-tools directory.
By the way, this platform-tools directory is the one that has the adb executable file. Just a heads up.
You need to download su. I cannot tell you where to get it. I just do not know where I got mine from, but was easy so go for it When you have it, extract it and put it in the platform-tools directory.
Confirm that the platform-tools directory includes these files:
Code:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
su
lsm_disabler.ko
f05dsu.bat
There will be more, but these are the ones needed for this to work.
Now, get ready to root. Connect your phone to the PC.
Go to your phone settings > setting my body > step/activity counter app > pedometer use and confirm it is checked on.
In the platform-tools directory, look for f05dsu.bat and run it. A DOS window will open. This is the funny part. Unless you are doing this from a Japanese version of Window$, or from a Window$ with Japanese locale active, you will see a lot of strange symbols instead of Japanese characters... which would be the same for almost anyone anyway Regardless, you will see a prompt to Press any key to continue . . .. At this point, you do not need to do anything on your phone, other than visually checking that the check mark on the pedometer is set.
On the DOS window press any key, your will see more garbage and another prompt to press any key. This is the important part. See if you can find among all those symbols this pattern: OFF/ON. If you do see it, it means we are on track.
Now that you were able to see the OFF/ON, go to your phone and uncheck the pedometer (OFF) and check it again (ON).
In the DOS window, press any key. Your phone will reboot. The message in the DOS window says that you must wait for the phone to boot up and for Window$ to recognize your usb connection to the phone.
When/if your phone is recognized by Window$, go to the DOS window and press any key.
Again, press any key and your phone will reboot.
The DOS window has a message indicating that you must now install superuser and busybox. When your phone reboots, go to the android market and install from there when you have the time.
You can now close the DOS window because, unless there was any error, you are now rooted, my friend
From the market, install a terminal, or an app that includes a terminal. I use Rom Toolbox because it has a terminal and scripts to mount the /system as rw.
Open whatever terminal you chose and, at the $ prompt type su
If new prompt is #, type soff
You will need to run these commands every time before trying to mount /system as rw.
That is all. I hope you can root your phone.
Just a petition, post this message in the forums, as it may help others who have similar difficulties. It sure could have helped me if someone had done before me.
Have a nice one and please forgive my English.
Click to expand...
Click to collapse
update 15/4
On 13/4 finally i got my phone rooted
I have to run f05droot.bat instead of f05dsu.bat
After I have run the f05dsu.bat, for the steps, no error popout.
then I open the terminal type su, it reply me "permission denied".
I know it is not successful, after several run, the situation still the same.
after that have checked the contents of f05droot.bat and f05dsu.bat.
They are very similar but the f05droot.bat will push the superuser and busybox into the device at the same time.
(so I added those files in the directory \Android\android-sdk\platform-tools )
Therefore, i tried that and its works finally.
I feel really exciting at that moment.
I hope this post can help they T-01d user to root the phone.
personally I really like this phone ^~^
the su file is also important
Anyone try it? Does it work?
I have got the source code from its web
But I dont know how to use that and lead me to root the machine
ttp://spf.fmworld.net/oss/t-01d/data/download.html
Can you post a review of this device?
redcarrot said:
Greeting,
It was heard that rooting T-01D are similar as F-05D.
I found a website regarding rooting F-05D, but I dont read Japanese, just want to know if anyone have tried the enclosed method to root T-01D?
or could anybody do the translation, since the terms become quite strange after using the online translators
The following link is ref. of rooting F-05D:
ttp://ayati.cocolog-nifty.com/blog/2012/01/f-05droot-1d0b.html
(should be "http" rather than "ttp")
The source code of T-01D have been provided also, but I have no idea how to use it and root the machine:
ttp://spf.fmworld.net/oss/t-01d/data/download.html
(should be "http" rather than "ttp")
Thank you very much in advance?
Click to expand...
Click to collapse
If you have time, can you please post a mini review of the device? I wanted to buy one too and I'm quite excited reading your review!
Thanks and more power!
Here is the mini review
Screen color is perfect except black and accurate. Speed is good in comparing with SGS2. Battery life is similar to SGS2. Form factor is better than SGS2. Camera is outstanding, thanks to the 1.3MP camera. Waterproofing design is what I like. The bad is upgrading is only possible in Japan. Digital TV is useless. Sound level is a bit low.
personally i like this phone very much especially the outlook.
my personal review is the following:
1. same as above the screen is perfect
2. the camera is also excellent
3. while you have a phone call, it change mode automatically depends on the environment
4. if i switch off all the data things, this phone can stand more than one day
(so i wont blame the battery, because I think we use too many network related stuffs)
5. i have to admit that the firmware is not quite stable (fortunately the phone can be upgrade to 4.0 after july)
for the rooting process, it seems like someone has success:
(i think that is temp root)
search "T-01D 軟解, tofu-keitai" in google (that is chinese unfortunately)
redcarrot said:
Greeting,
It was heard that rooting T-01D are similar as F-05D.
I found a website regarding rooting F-05D, but I dont read Japanese, just want to know if anyone have tried the enclosed method to root T-01D?
or could anybody do the translation, since the terms become quite strange after using the online translators
The following link is ref. of rooting F-05D:
ttp://ayati.cocolog-nifty.com/blog/2012/01/f-05droot-1d0b.html
(should be "http" rather than "ttp")
The source code of T-01D have been provided also, but I have no idea how to use it and root the machine:
ttp://spf.fmworld.net/oss/t-01d/data/download.html
(should be "http" rather than "ttp")
Thank you very much in advance?
Update of 4/4
the following t-01d rooting procedures is provided by Magimaster
Click to expand...
Click to collapse
It really work!~
I rooted my T-01D with this method!
And it's permanent root!!
Many thanks!~
hi HaoyuWen,
i have followed the steps, when i type su in the terminal simulator, it comes out segmentation fault su, do you have any idea.
I use titanium backup to check and it said my t-01d is not rooted.
for the pedometer on/off things, do i need to press the home key and go back to the pedometer to do the switch?
Thank you very much in advance
HaoyuWen said:
It really work!~
I rooted my T-01D with this method!
And it's permanent root!!
Many thanks!~
Click to expand...
Click to collapse
So both F-05D and T-01D can use this ?
yes, but i havnt got that work yet.
just want to know when I get the device rooted, will the device screen shows the device is rooted?
finally i got my phone rooted
you have to run f05droot.bat instead of f05dsu.bat
the su file is also important
redcarrot said:
yes, but i havnt got that work yet.
just want to know when I get the device rooted, will the device screen shows the device is rooted?
Click to expand...
Click to collapse
You can install a root checker to see
^ Please update it on the front page
Gonna get mine soon, so excited to hear this
wth_is_life said:
You can install a root checker to see
^ Please update it on the front page
Gonna get mine soon, so excited to hear this
Click to expand...
Click to collapse
I think I brick my T-01D. Don' know why, I do exactly the same what I have been told here... Now It ends up infinite boot loop
Anybody help me please?
Hey there everyone, sadly this guide isn't working for me. Everything in the guide goes smoothly and I do exactly what is listed but after my phone reboots the final time I still have no root access. I run f05droot.bat instead of f05dsu.bat like the user said but to no avail, I even ran f05dsu.bat and still nothing.
Anyone else have trouble? Maybe it is because I am on a certain FW? I am on 2.3.5
Baseband Version C_L1_M23
Kernel version: 2.6.35.7 [email protected] #1
and Build number is V43R41C
Just wondering as I really want root to disable all of these RAM-hogging default applications.
Bump? Anyone?
As far as I know, this rooting method cannot be done on FW V43R41C.
Sent from my SC-01D using Tapatalk 2
kinchung said:
As far as I know, this rooting method cannot be done on FW V43R41C.
Sent from my SC-01D using Tapatalk 2
Click to expand...
Click to collapse
Aw Thanks for the notice, of course it's my firmware. Any idea about ICS? It was supposed to come out in July but yeah..
I don't know about ICS for t-01d. My sc-01d has been already upgraded to ICS, the performance is improved a lot. sh-01d also gets ICS today.
Sent from my SC-01D using Tapatalk 2
kinchung said:
I don't know about ICS for t-01d. My sc-01d has been already upgraded to ICS, the performance is improved a lot. sh-01d also gets ICS today.
Sent from my SC-01D using Tapatalk 2
Click to expand...
Click to collapse
I see, I read about the T-01D (among many others) getting updated from articles like this: http://forums.hardwarezone.com.sg/e.../docomo-update-ics-4-0-18-models-3662812.html
I'm sure the T-01D would perform pretty awesome and maybe pre-installed software would not be as big a deal as it is now. Maybe since your SH-01D is getting updated, T-01D isn't far behind. The only thing I have to see is if I can update out of Japan.
I don't have sh-01d but galaxy tab 10.1 sc-01d instead. My t-01d also upgraded to V43R41C last month during visiting Japan. Upgrade of t-01d may not be possible outside Japan as Software Update cannot be executed without docomo sim and network.
Sent from my SC-01D using Tapatalk 2

[Q] REVERT TO 4.0.3 (pre R5)

Can anyone help me get my TABLET S (non-XPERIA) back to the pre-Revision 5 release of 4.0.3?
I HATE, HATE, HATE R5. Took away so many things that I was using, and I want to go back.
I already called SONY and was told I can't go back. I told the guy...I will find a way - and hung up.
I am sure it can be done....just need to find the software and the steps to do it.
bearhntr
bearhntr said:
Can anyone help me get my TABLET S (non-XPERIA) back to the pre-Revision 5 release of 4.0.3?
I HATE, HATE, HATE R5. Took away so many things that I was using, and I want to go back.
I already called SONY and was told I can't go back. I told the guy...I will find a way - and hung up.
I am sure it can be done....just need to find the software and the steps to do it.
bearhntr
Click to expand...
Click to collapse
Simple as. Change vendor/vendor.prop incremental to a lower number and flash an older update.zip
Or use AIO and install rescue back door, boot loop protection.
Manually flash either 120803002 or 120410004.zip
Done
stifilz said:
Simple as. Change vendor/vendor.prop incremental to a lower number and flash an older update.zip
Or use AIO and install rescue back door, boot loop protection.
Manually flash either 120803002 or 120410004.zip
Done
Click to expand...
Click to collapse
While I appreciate the reply, which gives you credit for a post (yes - I know how these forums work), I asked for the steps and software. I know it can be done, as I did it to my DroidX phone and had someone give me step by step instructions (rather directed me to a post he had done a year before with had everything I needed in one place).
I am talking real steps 1)...2)...3)... and links to the files. Not just some partial filenname which sends me on a goose chase.
Someone in another forum directed me to download signed-nbx03_001-ota-120410004.zip but then gave me nothing more - like do I put it on an SD CARD and do something with it. How do I get into BootLoader mode so that I can apply it, etc. I have already paid for a couple of apps that I used when I did my phone - I am sure that they might work for my tablet as well.
I am no idiot, do not need Crayola drawings, but at least 6th grade steps and locations on how to do this.
I cannot believe that for $350.00 that I just paid for the table SONY would tell me you can't do it - nor do they offer a manner to go back to the previous level (1 step) if you do not like the ROM that got installed.
4.0.3 (r5) is for the birds....takes away some of the best features of the reason I bought the SONY Tablet S over something else.
While I do appreciate, and do thank/reward those that help me - I think I need a little more than a simple 3 line response.
Curtis
bearhntr said:
While I appreciate the reply, which gives you credit for a post (yes - I know how these forums work), I asked for the steps and software. I know it can be done, as I did it to my DroidX phone and had someone give me step by step instructions (rather directed me to a post he had done a year before with had everything I needed in one place).
I am talking real steps 1)...2)...3)... and links to the files. Not just some partial filenname which sends me on a goose chase.
Someone in another forum directed me to download signed-nbx03_001-ota-120410004.zip but then gave me nothing more - like do I put it on an SD CARD and do something with it. How do I get into BootLoader mode so that I can apply it, etc. I have already paid for a couple of apps that I used when I did my phone - I am sure that they might work for my tablet as well.
I am no idiot, do not need Crayola drawings, but at least 6th grade steps and locations on how to do this.
I cannot believe that for $350.00 that I just paid for the table SONY would tell me you can't do it - nor do they offer a manner to go back to the previous level (1 step) if you do not like the ROM that got installed.
4.0.3 (r5) is for the birds....takes away some of the best features of the reason I bought the SONY Tablet S over something else.
While I do appreciate, and do thank/reward those that help me - I think I need a little more than a simple 3 line response.
Curtis
Click to expand...
Click to collapse
If you KNEW these forums you would know that we do not take kindly to those who do not use the SEARCH function. It is there so we don't have to repeat ourselves over and over again.
None the less.
If you can't manage this then take it in to Sony saying that you are having issues with the camera (they will restore it to original 3.2 software)
Step One
Root your device.
See my FAQ LINKS IS ALSO IN MY SIGNATURE!!
Step Two
Use AIO to 'Install "rescue-backdoor" [anti-bootloop protection].'
First you want to download, then extract to a folder, then double-click on S.onyTablet.S.bat, this will open a menu, enter '4' then press enter then enter '1' and press enter again. MAGIC, you have now decreased your incremental, well done.
Step 3
See my Update Links NOTE: ALSO IN MY SIGNATURE AND HAS BEEN FOR A LONG TIME, others had no problem with it
Find the update you require to flash, you want signed-nbx03_001-ota-120803002.zip or for you highness LINK
Step 4
Copy signed-nbx03_001-ota-120803002.zip to your SD card. Google how to if you don't know
Step 5
Put SD card back into tablet and boot into recovery. See my FAQ LINKS IS ALSO IN MY SIGNATURE!!
Step 6
Leave tablet to boot into R1A
Step 7
Be happy and click the fricken Thanks button.
P.S this is not hard stuff
Stifilz,
Thank you so very much for the long post. I was going cross-eyed looking for something like that...surprised that no-one has STICKY'd that one.
So I checked out #1 - followed the directions in FAQ to put the ADB path into the my DOS PATH statement (ahhhhh. the good old days - DOS). I can go to the DOS prompt and type 'adb' from any directory and it will bring up the ADB menu - hence it is working.
So I went to the task manager and verified that ADB.EXE was not listed. I typed ADB DEVICES (lower case) and it gave me the following:
C:\Windows\system32>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Windows\system32>:
I made sure that the SONY TABLET is seen - I unplugged from the computer and re-plugged, Windows bonks and wants to know if I want to browse the device. I have made sure the USB DEBUGGING is enabled on the device (before I connect it - had that problem with my DROIDX). Still the ADB 0.29 is not seeing the SONY TABLET S.
Any Ideas why?
When I try running the RUNME.BAT file I get the following:
D:\ROOT_W_RESTORE>runme
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (02.10.2012) v13 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 2
Special mode:
1) Root
2) Rollback
Make a choice: 1
Tablet S mode enabled!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
and it just sits there...left it for 20 minutes while I was making dinner. Should I have the power plugged in at the same time? Do I need to enable the STAY AWAKE setting?
Your guidance is again requested.
Please ignore my previous response. I really am not an ass - I was getting frustrated during my 2+ hours search not finding a message such as yours with the steps laid out like that - without making you bounce from one post to another - to another, it was like a scavenger hunt.
Again accept my thanks and my apologies.
Have you installed the drivers http://forum.xda-developers.com/showthread.php?t=1488822
Sent from my Desire S using xda app-developers app
gordo79 said:
Have you installed the drivers http://forum.xda-developers.com/showthread.php?t=1488822
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
Hey...THANKS. not sure why I did not catch that the tablet did not show as adb device, as I had to do the same thing when I rooted my DroidX...I guess I assumed that it would do it from that install.
Again thanks...now lets see if I can get the 4.0.3 (pre-R5) back on the tablet.
SO FAR SO GOOD. Weird that the SD card does not show from the tablet with it in the SD slot on the tablet like it does on my DROIDX. You can copy files to and from the SD Card in the phone without taking it out.
See...you can teach an old bear new tricks.
Stifilz,
On last step of your instructions...have one question.
What is the difference between this signed-nbx03_001-ota-120803002.zip that you mention and the signed-nbx03_001-ota-120410004.zip that I also downloaded from another forum message I was reading?
Thanks
bearhntr said:
Stifilz,
On last step of your instructions...have one question.
What is the difference between this signed-nbx03_001-ota-120803002.zip that you mention and the signed-nbx03_001-ota-120410004.zip that I also downloaded from another forum message I was reading?
Thanks
Click to expand...
Click to collapse
120803 is 2012-Aug-03 which is ICS R1A
120410 is 2012-Apr-10 which is ICS original. R1A is suposedly better
Stifilz
stifilz said:
120803 is 2012-Aug-03 which is ICS R1A
120410 is 2012-Apr-10 which is ICS original. R1A is suposedly better
Stifilz
Click to expand...
Click to collapse
stifilz,
Well I was successful...but it killed my ROOT. I got to playing with the new load, and it looks to have kept a bunch of my apps and some settings, but some of the apps do not work well.
I take it that if I go though the process again and choose to NOT RESTORE, it will put it back to OUT OF BOX configuration?
I do not have a lot of customizations that I will have a problem re-doing to get it back to O-O-B configuration. All of my apps can be pulled back off GOOGLE PLAY. Learning that is advantageous to have a GOOGLE PLAY account for each device (he he).
There are a lot of apps that I have noticed on GOOGLE PLAY that say not compatible with my device. Any known reason why? I figured that open source was open source.
I saw in the AIO that you can change the device type of your tablet to something else. Have you ever tried that? Does it seem to work?
I have also read that the UK models have a slot for a SIM card. Do you know if the US models have it to - just maybe inside and inaccessible?
I am loving the tablet....but find that now that I am back on the 4.0.3 my media files on my HTPC will not play. I find this wierd. The 4.0.3 update - according to the SONY site, says it improves the H.264 file playing...and nothing is mentioned about any changes in the R5 update.
Also one thing I noticed about the R5 load was it would sometimes just turn OFF the tablet. No reason or rhyme to it. Ever hear of that?
I may wind up going back up - if I cannot get them to play...have yet to try copying one to the SD card and playing it. But all of them used to play before I went back down.
Been looking into codecs too - but most of the processing of streamed DLNA stuff is done on the host machine [ putting on the Sherlock Holmes outfit again ]
Thank again for all your insight.
bearhntr said:
stifilz,
Well I was successful...but it killed my ROOT. I got to playing with the new load, and it looks to have kept a bunch of my apps and some settings, but some of the apps do not work well.
I take it that if I go though the process again and choose to NOT RESTORE, it will put it back to OUT OF BOX configuration?
I do not have a lot of customizations that I will have a problem re-doing to get it back to O-O-B configuration. All of my apps can be pulled back off GOOGLE PLAY. Learning that is advantageous to have a GOOGLE PLAY account for each device (he he).
There are a lot of apps that I have noticed on GOOGLE PLAY that say not compatible with my device. Any known reason why? I figured that open source was open source.
I saw in the AIO that you can change the device type of your tablet to something else. Have you ever tried that? Does it seem to work?
I have also read that the UK models have a slot for a SIM card. Do you know if the US models have it to - just maybe inside and inaccessible?
I am loving the tablet....but find that now that I am back on the 4.0.3 my media files on my HTPC will not play. I find this wierd. The 4.0.3 update - according to the SONY site, says it improves the H.264 file playing...and nothing is mentioned about any changes in the R5 update.
Also one thing I noticed about the R5 load was it would sometimes just turn OFF the tablet. No reason or rhyme to it. Ever hear of that?
I may wind up going back up - if I cannot get them to play...have yet to try copying one to the SD card and playing it. But all of them used to play before I went back down.
Been looking into codecs too - but most of the processing of streamed DLNA stuff is done on the host machine [ putting on the Sherlock Holmes outfit again ]
Thank again for all your insight.
Click to expand...
Click to collapse
If you use MX player it will play most files. Regarding the apps have you checked the unknown sources in the settings?
Sent from my Desire S using xda app-developers app
bearhntr said:
Hey...THANKS. not sure why I did not catch that the tablet did not show as adb device, as I had to do the same thing when I rooted my DroidX...I guess I assumed that it would do it from that install.
Again thanks...now lets see if I can get the 4.0.3 (pre-R5) back on the tablet.
Click to expand...
Click to collapse
bearhntr, I have been struggling trying to get my tablet to show up when I type in adb devices. I was having the same problem you had before you wrote this post. I followed the directions in Bluechips post for the ADB installer (very huge thanks for all those who develop these things to make it easier) and even did step by step with the video. I have also tried other methods to get ADB to work.
Long story short, did you do anything different than listed in Bluechips post to achieve success in getting your computer to see your tablet as an ADB device?
Thanks!
esonnen said:
bearhntr, I have been struggling trying to get my tablet to show up when I type in adb devices. I was having the same problem you had before you wrote this post. I followed the directions in Bluechips post for the ADB installer (very huge thanks for all those who develop these things to make it easier) and even did step by step with the video. I have also tried other methods to get ADB to work.
Long story short, did you do anything different than listed in Bluechips post to achieve success in getting your computer to see your tablet as an ADB device?
Thanks!
Click to expand...
Click to collapse
Esonnen,
I followed the steps from BLUECHIPS direction step by step. Are you seeing the tablet at all in the Windows Device manager? Mine was showing up in the device manager - but not correctly until I installed the drivers.
I right mouse button clicked on the SONY TABLET S entry in the device manager in Windows and chose UPDATE DRIVER...then pointed it to the extracted AdbWinUsbApi.dll file. Followed the prompts and after that the SONY TABLET was listed in an new CATEGORY called ANDROID PHONE, as ANDROID COMPOSITE ADB INTERFACE.
I found that if I did not get it to show as this in the DEVICE MANAGER, nothing I tried with ADB or other tools that used that software would work. This was the same problem I had when I was working with my DROIDX. I had thought that by getting the DROIDX to work properly in the rooting process - that the tablet would as well. It was the simple act of changing the driver to the AdbWinUsbApi.dll that fixed it.
gordo79 said:
If you use MX player it will play most files. Regarding the apps have you checked the unknown sources in the settings?
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
I had already tried that player and it also downloaded the ARMv7 CODEC set to the tablet.
This player may work fine...but it wants the files to be LOCAL to the device or streamed from a WEBPAGE type arena.
I want something that will stream DLNA (the tablet sees all three of my Windows DLNA device and my Sony STR-DN1020 receiver) using the DLNA services that are in 4.0.3. It even shows me the folders on my HTPC. I can also list the movies on it. Where the 4.0.3(r5) showed an actual thumbnail of the first frame of the .M4V files - the 4.0.3 shows what appears to be a set of hotair balloons.
Touching one of the files yields the following error: "INVALID MEDIA - PLAYBACK NOT SUPPORTED" These files play fine on the HTPC and my D-LINK DSM-750 Media Center Extender (and in 5.1 audio). Generally with DLNA the decoding is handled at the source PC, not the playback device. I find this weird too.
Maybe I will try copying one of these files to the device and try playing it from there....try and narrow it down.
GORDO79,
Not sure what has happened, but my Tablet S is now playing the videos from my HTPC. The details of all the videos hows VIDEO CODEC: UNKNOWN and AUDIO CODEC: UNKNOWN, but all of them seem to be playing.
I searched the GOOGLE PLAY STORE, but do not find any codecs listed there other than the ones for various players.
I am so happy now that I can play my videos and I think I will be able to THROW them to my DSM-750 (Media Center Extended) until I can get a BRAVIA TV (hint hint Santa).
Much thanks for everyone's help.
stifilz said:
If you KNEW these forums you would know that we do not take kindly to those who do not use the SEARCH function. It is there so we don't have to repeat ourselves over and over again.
None the less.
If you can't manage this then take it in to Sony saying that you are having issues with the camera (they will restore it to original 3.2 software)
Step One
Root your device.
See my FAQ LINKS IS ALSO IN MY SIGNATURE!!
Step Two
Use AIO to 'Install "rescue-backdoor" [anti-bootloop protection].'
First you want to download, then extract to a folder, then double-click on S.onyTablet.S.bat, this will open a menu, enter '4' then press enter then enter '1' and press enter again. MAGIC, you have now decreased your incremental, well done.
Step 3
See my Update Links NOTE: ALSO IN MY SIGNATURE AND HAS BEEN FOR A LONG TIME, others had no problem with it
Find the update you require to flash, you want signed-nbx03_001-ota-120803002.zip or for you highness LINK
Step 4
Copy signed-nbx03_001-ota-120803002.zip to your SD card. Google how to if you don't know
Step 5
Put SD card back into tablet and boot into recovery. See my FAQ LINKS IS ALSO IN MY SIGNATURE!!
Step 6
Leave tablet to boot into R1A
Step 7
Be happy and click the fricken Thanks button.
P.S this is not hard stuff
Click to expand...
Click to collapse
stifilz,
Again many thanks for your help with this. Not sure why the ROOT broke when I did the deed (and I was successful), but I tried to get my root back following your steps again (other than flashing with the .ZIP from the SD card), and I cannot seem to get my ROOT back. Neither the AIO or the ROOT W/RESTORE works.
I wanted to use the AIO to turn off the OTA prompt and run a few of the tweaks, but each time I run it - the screen goes red and tells me I have to ROOT.
Any ideas where I am going wrong?
Much Thanks
can anyone tell me the main differences between the first ics release and the r1a?
sony tablet s 4.0.3 r5?
Personally I know that many people come to know about looking for it and I've spent hours and hours looking for a way to rooted my tablet and still nothing ...
Really there is still no way to update the sony tablet s 4.0.3 r5?
Nor has the downgrade to another rom?
I've looked almost everywhere but to no avail. help me.

[HOW TO] beaups Moonshine S-OFF exploit for linux/android noobs

How to for n00bs:
Beaups Moonshine S-OFF for the Droid DNA
(Note: This guide will assume that you are complete noob with android and linux, BUT that you are not too dense to google basic things and infer basic differences between PC setups)
YOU WILL NEED:
1 Laptop or Desktop with internet access
1 32bit Linux (Ubuntu or Mint preferred, Mint to be used in this guide) liveUSB or liveCD (liveCD preferred, and what will be covered in this guide)
1 Stock Droid DNA with the 2.06 firmware update (2.04 is reported to work, but more success seems to be had with the updated firmware) WITH AT LEAST 80% BATTERY LIFE
1 Factory HTC/Droid micro-usb (Or any cable you know will work with ADB)
{
"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"
}
Prepping your computer:
1: Burn a liveCD of your linux distro of choice. Mint is my choice due to having great out of the box compatibility with hardware.
2: Insert liveCD into your PC, turn it on (or reboot), and enter boot menu (typically esc, f8, or f12 pressed during start up) and select “Boot from CD Drive”.
3: Allow liveCD to boot, it may take some time depending on the speed of your hardware. This is good time to prepare your phone for shining.
Prepping your phone:
1: Update to the 2.06 firmware update, if you have not already. If you cannot OTA, you can find guides to flash said firmware update elsewhere on XDA
a: If you are unsure what firmware you are on, go to “Settings”, “About”, and “Software Information” and it will have your firmware listed.
2: Disable any sort of screen lock. Image lock, facelock, pin lock, doesn't matter, it MUST BE DISABLED FOR THIS TO WORK
3: Disable “Fastboot”. “Settings”, “Battery”, UNCHECK “Fastboot”
4: Enable USB Debugging. “Settings”, “Developer Options”, “USB Debugging”
5: Boot into fastboot (turn off phone, reboot holding down POWER button and VOLUME DOWN button simultaneously). Select “Factory reset”. Allow phone to reset and reboot. Go back into settings, repeat sets 2 and 3 if necessary.
Downloading, unpacking, and excecuting moonshine.
1: On your live linux session, that is connected to the internet, go to www.moonshine.io
2: READ EVERYTHING
3: READ EVERYTHING AGAIN
4: Download the .tgz file relevant to your device (for most of us this will be the Verizon DNA file “moonshine_dlx_2.06.605.1.tgz”
5: Go to the folder your .tgz was just downloaded to. This should be your “downloads directory”
6: Right click anywhere in your download directory and select “Open in Terminal”
7: Extract the moonshine .tgz by typing out the following command into terminal “tar -zxf moonshine_<device>_<version>.tgz” For the Verizon DNA this will be “tar -zxf moonshine_dlx_2.06.605.1.tgz”
Your download directory should look like this when done
(Unfortunately, after this, the iPhone I was using to take pictures died, so there are no more pictures after this, but everything is very straightforward)
At this time plug your phone (which has been factory reset, rebooted, and all things listed in the “phone prep section” have been double checked) into your PC via your HTC/Android USB cable.
8: Execute the “Distiller” by typing the following command into terminal “sudo ./distiller”
9: Agree to the onscreen prompts, sit back, relax, DO NOT F**K WITH YOUR PHONE, and let the shine do its magic. This should take five to fifteen minutes and your phone will reboot several times.
10: Enjoy S-OFF and root.
ALL CREDIT GOES TO BEAUPS AND THE MOONSHINE DEV TEAM, this is simply a shoddy step by step guide by a n00b for n00bs to (hopefully) get more comfortable with the idea. This may be reproduced, altered, or edited in anyway as long as credit is given to me (DWC2134) for the original text and pictures and to the DEVS who brought us this awesome utility. In fact, PLEASE edit, improve, and revise this as you see fit for use by new android and linux users. Any changes suggested in this thread will be taken into account and incorporated into the OP.
Toubleshooting:
1: If you are experiencing the "temproot failed" problem, first try a hard reboot, then a factory reset + hard reboot if the reboot alone does not solve the problem.
2: There is some chatter of questionable validity that VZW is trying to push an update to stop SOFF. If you are having trouble, turn off your radios and/or put your phone in airplane mode while attempting moonshine. While most, myself included, doubt the validity of this claim it is better safe then sorry.
Beaups original moonshine thread
Moderators, if this is in the wrong section, or out of line, etc etc, please move, edit, delete, or do as needed.
Does it have to be the 32 bit version? If so I just have to redo my live usb.
sent from my droid DNA with xda premium
DaPitt84 said:
Does it have to be the 32 bit version? If so I just have to redo my live usb.
sent from my droid DNA with xda premium
Click to expand...
Click to collapse
Yes or the exploit will give an error saying there aren't enough 32 bit libraries. I tried on a 64 bit and got that error. I re did my live cd to use 32 bit ran the exploit and it worked flawlessly.
Sent from my HTC6435LVW using xda premium
Nice howto I did the s-off yesterday worked great. I'm on windows 7 64 bit and installed 32 bit mint.
For people doing this like op said install and use 32 bit just easier and if you're on a 64 bit system doesn't matter 32 bit installs fine.
Sent from my HTC6435LVW using xda premium
Very nice "How To' for us Windows PC peeps dwc2134...thank you.
I have a couple of questions if anyone can answer:
1) I haven't seen any other procedure where "Factory Reset" is called upon. Is there a specific reason?
2) I have a burned image of "Ubuntu-13.04-desktop-i386.iso" on USB Stick that runs v/smoothly on my laptop w/Vista Ultimate, but I can't seem to get to terminal screen. I do however see all of the Moonshine flies in download folder when in Ubuntu and "moonshine_dlx_2.06.605.1.tgz"
Please forgive the noobish Q's
Thx in advance
First of all, thank you dwc2134 for providing this guide! I am very new to this scene (Android rooting) and this guide helps out TREMENDOUSLY since I have no knowledge about terminal/command prompts.
However, after re-reading this guide and the instructions at moonshine.io, I have some questions in my head that are preventing me from going further (If anyone here can answer any of my questions, it would be most appreciated!)
1. At the Instructions page on moonshine.io, Step 8 says "Use the matchingStockRUU..", I have no idea what this, is this something I should worry about? I have not modified my Droid DNA in anyway whatsoever ever since I got the device. I only did the 2 OTA updates (2.04 and 2.06) and that's it.
2. In this guide (dwc2134's) on Step 8 where it says to execute the "Distiller", do I type it into the same terminal window I extracted the Moonshine.tgz file?
3. Once the whole process finishes, and I go back to the fastboot screen to see the glorious text that reads: "S-Off", does this mean my phone is rooted and I can install apps like SetCPU off the bat? Or do I have to flash a custom ROM and if so, can anyone recommend a "tried-and-true" ROM?
Once again, if anyone can answer my queries, it would be very helpful. Thank you in advance!
dfa7 said:
Very nice "How To' for us Windows PC peeps dwc2134...thank you.
I have a couple of questions if anyone can answer:
1) I haven't seen any other procedure where "Factory Reset" is called upon. Is there a specific reason?
2) I have a burned image of "Ubuntu-13.04-desktop-i386.iso" on USB Stick that runs v/smoothly on my laptop w/Vista Ultimate, but I can't seem to get to terminal screen. I do however see all of the Moonshine flies in download folder when in Ubuntu and "moonshine_dlx_2.06.605.1.tgz"
Please forgive the noobish Q's
Thx in advance
Click to expand...
Click to collapse
OK, fingered it out. This may just be of some help to others here. ubuntu-13.04-desktop-i386.iso wouldn't get into "terminal" BUT, linuxmint-15-cinnamon-dvd-32bit.iso does.
Does anyone know if it absolutely necessary to "Factory Reset" DNA with this Mooshine S-OFF method?
dfa7 said:
Very nice "How To' for us Windows PC peeps dwc2134...thank you.
I have a couple of questions if anyone can answer:
1) I haven't seen any other procedure where "Factory Reset" is called upon. Is there a specific reason?
2) I have a burned image of "Ubuntu-13.04-desktop-i386.iso" on USB Stick that runs v/smoothly on my laptop w/Vista Ultimate, but I can't seem to get to terminal screen. I do however see all of the Moonshine flies in download folder when in Ubuntu and "moonshine_dlx_2.06.605.1.tgz"
Please forgive the noobish Q's
Thx in advance
Click to expand...
Click to collapse
1: While not ENTIRELY necessary for a successful moonshining, performing the factory reset and hard reboot seems to solve the "temproot failed" problem several users (myself included) have expierenced.
2: Mint is my go to, so it may be slightly different in ubuntu. You can also open terminal by pressing ctrl-alt-T or by going to your applications menu (or the search in the dash) and searching for "Terminal" and then inputting "cd ~/downloads". This will, for lack of better words, open your download directory in terminal so that the commands you input specifically look for, and effect, the files there. You may have to alter the "~/downloads" portion slightly to get you to the correct directory, but looking at the filepath on your computer it should be pretty obvious.
AndroM31 said:
First of all, thank you dwc2134 for providing this guide! I am very new to this scene (Android rooting) and this guide helps out TREMENDOUSLY since I have no knowledge about terminal/command prompts.
However, after re-reading this guide and the instructions at moonshine.io, I have some questions in my head that are preventing me from going further (If anyone here can answer any of my questions, it would be most appreciated!)
1. At the Instructions page on moonshine.io, Step 8 says "Use the matchingStockRUU..", I have no idea what this, is this something I should worry about? I have not modified my Droid DNA in anyway whatsoever ever since I got the device. I only did the 2 OTA updates (2.04 and 2.06) and that's it.
2. In this guide (dwc2134's) on Step 8 where it says to execute the "Distiller", do I type it into the same terminal window I extracted the Moonshine.tgz file?
3. Once the whole process finishes, and I go back to the fastboot screen to see the glorious text that reads: "S-Off", does this mean my phone is rooted and I can install apps like SetCPU off the bat? Or do I have to flash a custom ROM and if so, can anyone recommend a "tried-and-true" ROM?
Once again, if anyone can answer my queries, it would be very helpful. Thank you in advance!
Click to expand...
Click to collapse
1: If you have not modified your phone in anyway, and have received the OTAs, then that is irrelevant to you.
2: Yes. Or in another terminal window opened in your "downloads" directory, though opening a second window seems kind of pointless.
3: Moonshine installs superuser to your device, so YES YOU CAN install custom apps like SetCPU right off the bat. I would recommend first installing a custom recovery (I am using CWMs new touch version) and making a nandroid backup before doing anything else, personally. I would also highly recommend installing a custom rom instead of putting in too much time with the stock sense rom. There are so many fantastic roms out for this phone, it would almost be a waste not to. A lot of folks swear by the ViperROM. I'm currently using it and love it.
dwc2134 said:
1: While not ENTIRELY necessary for a successful moonshining, performing the factory reset and hard reboot seems to solve the "temproot failed" problem several users (myself included) have expierenced.
2: Mint is my go to, so it may be slightly different in ubuntu. You can also open terminal by pressing ctrl-alt-T or by going to your applications menu (or the search in the dash) and searching for "Terminal" and then inputting "cd ~/downloads". This will, for lack of better words, open your download directory in terminal so that the commands you input specifically look for, and effect, the files there. You may have to alter the "~/downloads" portion slightly to get you to the correct directory, but looking at the filepath on your computer it should be pretty obvious
Click to expand...
Click to collapse
Thanks for clarrification. I decided to Mint and all is perfect! Ubuntu was a challenge considering I'm not an Apple guy and Linux is greek to me. As for the "Factory Reset", I'll gamble only 'cause I'm configured to my liking and not in mood yet to spend a day getting everything back. Thx again!
All's well that ends well. If you end up having the temp root problem, try a hard reboot first and then a factory reset.
Sent from my HTC6435LVW using xda app-developers app
dwc2134 said:
1: If you have not modified your phone in anyway, and have received the OTAs, then that is irrelevant to you.
2: Yes. Or in another terminal window opened in your "downloads" directory, though opening a second window seems kind of pointless.
3: Moonshine installs superuser to your device, so YES YOU CAN install custom apps like SetCPU right off the bat. I would recommend first installing a custom recovery (I am using CWMs new touch version) and making a nandroid backup before doing anything else, personally. I would also highly recommend installing a custom rom instead of putting in too much time with the stock sense rom. There are so many fantastic roms out for this phone, it would almost be a waste not to. A lot of folks swear by the ViperROM. I'm currently using it and love it.
Click to expand...
Click to collapse
Thank you so much for clearing away my doubts! Once I get the "S-Off" message, I'll look into your suggestions mentioned here.
dwc2134 said:
All's well that ends well. If you end up having the temp root problem, try a hard reboot first and then a factory reset.
Click to expand...
Click to collapse
dwc2134 - thanks for your help, patience and interset with some of us and this project! It does seem easier than revone.
Where do I find the Linux file to put on usb? I don't have any blank cd's either...will it work from usb stick?
HellRayzer said:
Where do I find the Linux file to put on usb? I don't have any blank cd's either...will it work from usb stick?
Click to expand...
Click to collapse
You can find the .iso image for any distro you want online. I prefer Linux Mint, though Ubuntu is another crowd favorite. You can make a bootable USB, but I find it easier to make and use liveCD/DVDs. A pack of burnable DVDs is $2.89 at CVS. Google is your friend for the rest of this, it is all VERY self explanatory and most distro sites put step by step instructions right on their website.
http://www.linuxmint.com/download.php
http://www.linuxmint.com/documentation/user-guide/english_15.0.pdf
Error When Trying To Download - 'This file reached max downloads limit"
Followed the guide...booted from USB Ubuntu. No problems. Connected to moonshine.io, clicked next, next, but when I selected the DNA version, I get the error:
"This file reached max downloads limit"
...and no download.
Any ideas? I see another person has posted this in the developers section. Is there a link problem?
Thanks.
dwc2134 said:
You can find the .iso image for any distro you want online. I prefer Linux Mint, though Ubuntu is another crowd favorite. You can make a bootable USB, but I find it easier to make and use liveCD/DVDs. A pack of burnable DVDs is $2.89 at CVS. Google is your friend for the rest of this, it is all VERY self explanatory and most distro sites put step by step instructions right on their website.
http://www.linuxmint.com/download.php
http://www.linuxmint.com/documentation/user-guide/english_15.0.pdf
Click to expand...
Click to collapse
This is spot on. I did my first live cd related to rescuing crucial data on a government computer with a corrupt OS a few weeks ago. I googled "How to make a bootable live cd USB drive" and literally in five minutes I was booted into my Ubuntu distro.
One thing I did learn is with Ubuntu there's a lot of alternative distros on their main site with all the links. After not having the option to boot without making any changes I went to my google-found guide again and realized only ubuntu distros with "desktop" in the filename would give me the live boot option I needed for the task at hand.
One of those small details I overlooked, that was solved by a quick recheck with google.
EXCELLENT GUIDE, I'm really impressed.
Max download limit reached.
I am having the same issue it says that the maxium download limit has been reached.:crying:
I can't donate if I can't download!
FUBAR'd
UntamedDarkness said:
I am having the same issue it says that the maxium download limit has been reached.:crying:
I can't donate if I can't download!
Click to expand...
Click to collapse
Link looks to be FUBAR'd. Maybe Verizon got pizzzed and did a bit of hacking themselves...
Several people now reporting the issues in multiple threads. I just rechecked...same error.
Out of curiosity, are you using Verizon Mobile Hotspot on your phone to connect to the internet via computer? I am.
CharliesTheMan said:
This is spot on. I did my first live cd related to rescuing crucial data on a government computer with a corrupt OS a few weeks ago. I googled "How to make a bootable live cd USB drive" and literally in five minutes I was booted into my Ubuntu distro.
One thing I did learn is with Ubuntu there's a lot of alternative distros on their main site with all the links. After not having the option to boot without making any changes I went to my google-found guide again and realized only ubuntu distros with "desktop" in the filename would give me the live boot option I needed for the task at hand.
One of those small details I overlooked, that was solved by a quick recheck with google.
EXCELLENT GUIDE, I'm really impressed.
Click to expand...
Click to collapse
Yep, google has most any answer you could ever need if you search enough. The only reason I promote liveCDs over liveUSBs is that I think they are a touch easier to make and use. For some reason I have always had a hard time getting liveUSBs to work.
Thank you! I'm really glad it seems to have helped some folks out!
UntamedDarkness said:
I am having the same issue it says that the maxium download limit has been reached.:crying:
I can't donate if I can't download!
Click to expand...
Click to collapse
ejohanss said:
Link looks to be FUBAR'd. Maybe Verizon got pizzzed and did a bit of hacking themselves...
Several people now reporting the issues in multiple threads. I just rechecked...same error.
Out of curiosity, are you using Verizon Mobile Hotspot on your phone to connect to the internet via computer? I am.
Click to expand...
Click to collapse
I doubt it is Verizon, most likely a bandwidth issue or hosting service issue. Seems to be common with everyone trying to download moonshine right now. Sounds like there is trouble with the download limit counter. I knew I should have kept a backup copy of the .tgz
No, when I tether I use one of the free solutions. I got bumped off of unlimited, so I tend to use more wifi then phone data. You NEED an internet connection that is not reliant on your phone for this to work. Moonshine actively connects to the internet during the ./distiller program.
dwc2134 said:
Yep, google has most any answer you could ever need if you search enough. The only reason I promote liveCDs over liveUSBs is that I think they are a touch easier to make and use. For some reason I have always had a hard time getting liveUSBs to work.
Thank you! I'm really glad it seems to have helped some folks out!
I doubt it is Verizon, most likely a bandwidth issue or hosting service issue. Seems to be common with everyone trying to download moonshine right now. Hopefully beaups will be able to set up some new downloads or someone else will be willing to host the files for him. I knew I should have kept a backup copy of the .tgz
No, when I tether I use one of the free solutions. I got bumped off of unlimited, so I tend to use more wifi then phone data. You NEED an internet connection that is not reliant on your phone for this to work. Moonshine actively connects to the internet during the ./distiller program.
Click to expand...
Click to collapse
I just checked it's a host download limit it's ABSOLUTELY not related to verizon.

Categories

Resources