I've been working on this for days and I'm on the verge of giving up and send my android tablet back to the retailer but, on the off chance that someone can help, I thought I'd post a plea for help.
I have been playing with my mother's birthday gift, an android tablet, in an attempt to put a bird watching app on it. I'm not used to this OS, so it took me a few days to get the hang of it, and then the wifi stopped working.
From a user perspective, you turn on the wifi and, after 20 seconds, it turns itself off and the tick disappears.
I decided to look a little further into the problem, as I didn't believe it was the hardware so soon, and used LauncherPro and SuperOneClick to root the tablet and ddms to see what was going on.
Anyway, I think I have tracked the issue to the wpa_supplicant file. I can load up the wifi interface from the command line:
insmod /system/lib/modules/8192cu.ko
busybox ifconfig wlan0 up
But when I ran the original wpa_supplicant in /system/bin/ it simply said "not found"
The file was there - I could copy it onto a usb stick and open it in a hex editor on my PC, but whatever I did, it would say "not found" if I tried to use it (chmod 777 as well).
When I got no joy from that, I started to look for alternative wpa_supplicants (there was no sign of a direct replacement for my disgo8100 2.3.3 version) and found the ad-hoc enabled ones.
I have tried a selection, but the one that comes closest to working (I mounted the system rw and replaced the original before mounting it ro again) insists on running as "wifi" (or 1010) when the original ran as "system" (or 1000).
This seems to mean that, although the supplicant runs happily, it doesn't create the /data/system/wpa_supplicant/wlan0 file in a form that other programs can access (wrong group/permissions, I think).
So, this has become very frustrating (but I've learned a lot about android, and how it differs from linux).
Can anyone provide an explanation for why the original file says "not found"? Could it be corrupt? If so, could someone provide a replacement from the disgo 8100? Could it be relying on a library that's not there?
What about the ad-hoc version I have? Can I force it to run as system.system instead of wifi? Am I wasting my time and should try to get disgo to provide a whole replacement rom (they have an update apk, but I believe you need to connect to the Internet to do an OTA update, which I can't).
As I said, I'm ready to send this tablet back, but I hate to admit defeat!! Any help would be gratefully received.
Cheers.
Never mind. Made some progress with the ad-hoc supplicant in this thread:
http://www.freaktab.com/showthread....pa_supplicant-file&p=3600&viewfull=1#post3600
Disgo 8100 Rooting
On the basis that there doesn't seem to be much information about the Disgo 8100, I thought I would post my findings.
I initially tried z4root, universalandroot and gingerbreak, but none of these worked. However, I didn't understand that I needed (or how) to enable USB debugging.
Once I did, I installed LauncherPro-0.8.6.apk and configured a shortcut to the development tab, which let me enable the USB debugging option.
I then downloaded android-sdk_r18-windows and modified the android_winusb.inf file by inserting the following at the end of the [Google.NTx86] and [Google.NTamd64] sections:
;Disgo8100
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_1F00
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_1F00&MI_00
When I plugged in the Disgo 8100, windows XP asked for drivers and I pointed it to the edited .inf file so that they could be installed and the disgo was recognised.
I then used SuperOneClickv2.3.3-ShortFuse on the PC to root the tablet - it all worked perfectly and reported success.
Installing term.apk got me a terminal emulator and I could su into root. Hopefully you can get yours rooted, too.
Disgo 8100 Android Market/Vending/Google Play
Whilst I managed to root the tablet, I couldn't get any form of the vending system to work.
I got the play dot google dot com site to recognise my tablet as a T-Mobile Samsung Nexus S using the information in this thread:
http://www.techknow.t0xic.nl/forum/index.php?topic=770.0
But market 2.3.6, 3.4.4 and the latest Google Play all fail with various errors (although I noticed that play only [email protected] out when the wireless is enabled - the others may do the same).
I have taken a log capture of google play failing using ddms and will look through it.
By the way, grabbing the hwver for this tablet gives:
console=ttySAC3,115200 androidboot.mode=normal mem=512M hwver=81.1.0.0 mtdparts=imapx200:[email protected](ramdisk),[email protected](kernel),[email protected](resv),[email protected](system),[email protected](userdata),[email protected](cache),[email protected](Local-disk),[email protected](panic) androidboot.mode=normal
Google Play working on Disgo 8100
Drawing this one to a close, in case anyone is interested:
I have Google Play installed and working. I downloaded com.android.vending-3.5.15.apk from the link in this thread:
http://www.theandroidsoul.com/download-google-play-store-apk-3-5-15/
I renamed it "Vending.apk" (the capitalisation may be important, not sure), mounted /system as rw (mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system) and copied it into /system/app. I changed permissions to "666".
I cleared the data/cache from the YouTube application and deleted YouTube.apk from /system/app (because it kept locking up) and replaced it with signedy244.apk (renamed as YouTube.apk) from http://forum.xda-developers.com/showthread.php?t=1529715 (the WifiHD version).
Rebooting the tablet, I connected to the WiFi and ran YouTube (in order to confirm my gmail account), which worked fine, and then Google Play, which (to my amazement) worked fine too.
Hope yours does too
Excellent thread! Wish I could thank you but I don't seem to have a Thanks button. Anyway, do you mind if I ask a couple of questions re. rooting the 8100:
1) Was your tablet running Android 2.3.3, kernel 2.6.35.7, build number GRI40?
2) Could you explain in a bit more detail what you did when you "configured a shortcut to the development tab"?
a3d35232 said:
Excellent thread! Wish I could thank you but I don't seem to have a Thanks button. Anyway, do you mind if I ask a couple of questions re. rooting the 8100:
Click to expand...
Click to collapse
Glad you like it.
a3d35232 said:
1) Was your tablet running Android 2.3.3, kernel 2.6.35.7, build number GRI40?
Click to expand...
Click to collapse
Yes.
a3d35232 said:
2) Could you explain in a bit more detail what you did when you "configured a shortcut to the development tab"?
Click to expand...
Click to collapse
a. Install launcherpro
b. Press home in the top left corner
c. Choose launcherpro
d. Press and hold a blank part of the screen
e. Choose shortcuts
f. Choose activities
g. Choose settings (scroll down to it)
h. Choose development (scroll down - not in alphabetical order)
i. Press ok
You should now have a desktop icon that lets you turn on USB debugging.
Enjoy
Thanks. Everything worked as you describe except the signedy244 version of YouTube. Whenever I launch it I get an error message "There was a problem with the network [400]". Searching on the net, it seems a lot of people are seeing this error and there may have been an update to the app which isn't in the signedy version. Are you still able to run it?
a3d35232 said:
Thanks.
Click to expand...
Click to collapse
No problem.
a3d35232 said:
Everything worked as you describe except the signedy244 version of YouTube. Are you still able to run it?
Click to expand...
Click to collapse
Yep, didn't have an issue - dropped it into the app folder, chmod and rebooted; worked first time and tested it a few times. The file I downloaded was 2,554,313 bytes, in case you want to check.
FYI, the issue I was having with the YouTube app was that it was making requests to the server with "restriction=ZH" in the uri. The server was replying with a HTML 400 error (bad request) because ZH is a language code, not a country code. Anyway, I've patched the app further to remove the restriction parameter from the request. I've posted details in the YouTubeHD thread (about half-way down page 36) if you're interested.
Any chance of telling a idiot how to get google play on the Disgo 8100?
My dad got given one at work but the app store sucks and I'm a little confused by the above
Many thanks
Related
This is an automated nooter file to streamline the rooting process for the NookColor. This has been tested by myself and others.
Thanks To: pokey9000 for nooter, Mistar Muffin for Market and GTalk Fix, clockworx for the hacked framework.jar used to get androidID, mastapsi for testing and coding, lewellyn for coding, [mbm] for ABI Fix, Suteru for the new custom Boot Animation,Hotaru for the Gingerbread keyboard, rpollard00 for DroidX keyboard with bigger font, bpk for Soft Keys, Ben74 for NookColor Tools which enables Non Market Installs, Freenode's #nookcolor chat for dealing with my crap and checking my code.
Please Note: If I'm using your app within AutoNooter and you'd like it removed please send me a PM stating so and I will do so for future versions.
DO NOT USE THIS IF YOU ARE 1.0.0
There are a few bugs before I can release 3.x.x that need to be worked out.
This is the only officially supported AutoNooter by those working on AN
Changes:
Added: Gingerbread Keyboard.
Deleted: YouTube.apk from /system/app
Update: Busybox has whoami
Update: Installs Soft Keys 3.0.0
What it does:
Installs su and Superuser.apk
Installs Busybox
Installs Softkeys 3.0.0
Installs NookColor Tools (To Enable Non-Market Installs)
Installs Calendar and Calculator.
Installs Android Market, Gmail, Youtube
Enable Multi-touch for Android Apps
Enables Live Wallpapers
Enables Android Market and Gmail.
App Auto Install (Open up NooterFiles from sdcard drop in /data/app)
Still Needs:
Custom Kernel to display something while working.
How to Use:
Before you begin:
* To update to 1.0.1 you must do a complete wipe.
* You must update to 1.0.1 to use AutoNooter 2.12.25 Instructions Here.
1 You must already have a registered NOOKcolor
2 You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
3 You must either have dd (Linux) or WinImage (Windows) software.
4 You must have an external microSDCard reader or this will not work. Do NOT use the NC.
5 You must have enough intelligence to follow instructions.
Let's get started:
1 Download Auto-Nooter from here: auto-nooter-2-12-25.img.zip
2 Linux: Unzip and use dd if=auto-nooter-2-12-25.img of=/dev/sdcard
2 Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
2 Windows Alternative: https://launchpad.net/win32-image-writer/+download
3 Unplug your NOOKcolor from computer. (If Plugged in.)
4 Insert AutoNooter SDcard into your NOOKcolor.
5 Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)
6 Your NookColor will reboot when it's done.
That was the hard part, now to the simple stuff.
7 Upon boot unlock your screen.
8 At the Android Welcome Screen skip Sign In.
9 Enable Location Services when given the option.
10 Connect to Wifi and launch Youtube from "Extras".
11 Click the Menu button (The one RIGHT of the Up Arrow).
12 Select "My Channel" and Login using your Gmail Account.
13 Exit Youtube and Launch Gmail from "Extras".
14 Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
15 Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
16 Enable Non-Market Installs by running the NookColor Tools App.
17 If your Youtube fails to launch Uninstall and Reinstall Youtube from /data/app
18 Go to Settings > Device Info > SdCard > UnMount > Format
Complete Wipe:
1 8 Failed Boots > Wipes /system
2 Factory Reset > Wipes /data
You must do both of these to completely wipe clean your NOOKcolor.
Is it safe to try this after already having done Nooter 0.2?
The manual market install hasn't done the trick for me. Every time I have to restage the thing, if I'm not at home, I have to run out and find a wi-fi point to re-register it (argh).
I've had no ill effects from running this over an already nootered system with Market already fully functioning.
Link broken? Not finding it.
Never mind. Got it. You've got an extra j on the end BTW
I already have the market hack working but I don't have calendar and live wallpapers and some other stuff listed.
So just to be extra clear, this is save to just install over what I have already?
EDIT: WOW, this worked really WELL! I didn't mess up my already done hacks
And a little surprise in in store! It has the NEW market installed!
EDIT: Never mind, tired.
I'll be your guinea pig...will try it now.
Thanks for pointing out the extra j. Took it out.
While you're at it, you might as well include the ADHOC fix...
http://forum.xda-developers.com/showthread.php?t=872521
Wow. I've got an Android setup wizard. Should I run through it? I haven't seen this before on the NC.
"Learn how to use your LogicPD Zoom2"
Ohs you can try, but it should fail at "sign in" you want to skip it so that you can enable location.
johnopsec said:
While you're at it, you might as well include the ADHOC fix...
http://forum.xda-developers.com/showthread.php?t=872521
Click to expand...
Click to collapse
I dunno. Some people don't tether and probably don't want to hassle switching back and forth. I think that one is kinda optional right now. Probably better off waiting for a good, permanent ad-hoc / infrastructure fix.
greenmky said:
I dunno. Some people don't tether and probably don't want to hassle switching back and forth. I think that one is kinda optional right now. Probably better off waiting for a good, permanent ad-hoc / infrastructure fix.
Click to expand...
Click to collapse
When installed, it defaults to the "stock" Infrastructure (AP) only wpa_supplicant that shipped with the NC. This simply gives them the option off switching to ADHOC mode if they need it.
I've been watching the progress on adhoc and it's currently unstable. As soon as there's a more stable adhoc solution it will most definitely be put in a future version.
Same server error as before for the Market.
"! Attention"
A server error has occurred. Retry, or cancel and return to the previous screen.
Anything else I should do?
This is the same thing that occurred with the manual Market enable process.
I'm convinced there's still something wrong with this whole process for some of us. I know there's 3-4 people getting the same server error as me for the market.
Should I try the manual editing of the packages.xml file?
You can always try to do a factory fallback then rerun autonooter or go look in freenode.net's #nookcolor, others have confirmed that Market works with this so there may be another issue someone in there can help you figure out.
There's been some suggestion that the androidID may not have been properly create, this may of happened if you messed with the db that holds it.
GabrialDestruir said:
You can always try to do a factory fallback then rerun autonooter or go look in freenode.net's #nookcolor, others have confirmed that Market works with this so there may be another issue someone in there can help you figure out.
Click to expand...
Click to collapse
Yeah, there's a problem with the process still somehow. This is the same results as the manual process.
This is much easier though and faster to redo. Maybe they'll find the bug in the process for those of us that it doesn't work for.
EDIT: Just a note. The Auto-Nooter didn't change my packages.xml file to remove these lines:
<sigs count="n">
<cert index="n" />
</sigs>
Not sure if it was supposed to...but it's in the manual install instructions.
Well if you can come into the irc chat maybe someone there can help you figure out the issue and we can see about adding the fix the next version.
Thanks to auto-nooter I was able to get farther than I did before with nooter .2 version. However, I've got a new problem.
After rebooting the NookColor, it started the Android tutorial. Then, when I tried to set up my Google account, I couldn't click on the "Enter Account" option since I already have a Google account. When I tried the enter account in the future option, Android seemed to immediately crash on me and the NookColor went to the normal B/N interface.
I power cycled the NookColor. However, now it immediately goes into the B/N interface, and I never see Android.
Any ideas?
Robert
Well you were suppose to skip the entering info so that it'd ask you if you want to enable location. I'm not sure if it's possible or not to get SetupWizard running again. I don't know anyone that's tried either.
Awesome! Market finally works. Thanks a lot for this! It didn't even break my previous mods.
It looks like we have to move our discussion here, so I went ahead and started a thread.
As of now, there is root for the mediapad, but the only way to root the springboard is by flashing it with a rooted mediapad cust.img - which gives you root but loses your 4g.
So for us Springboard users, we either need root or a way to get 4g back if flashing it as a mediapad. Anybody with thoughts or leads or any know-how?
Finally,
Special room for Huawei Media Pad created,
Thanks to TS
I'm very glad,
Now i'm waiting the master in here to modified this device
cause i still newbie
Actually I Prefer The 3G More THan The 4G For Some Reason I Felt 4G Wasnt Stable Enough....So Im Enjoiying My Mediapad In 3G More Than My Springboard In 4G......
from the other thread, Rumbi wrote:
Yap, only thing you have to do is install Superuser and Busybox from Market and copy "su" from /hwcust/oversea_hk/preload/fixed/bin/ to /system/xbin (e.g. with ES File Explorer with root and r/w enabled), and you are ready to go
I've installed SU & BusyBox. I cannot move the SU file over to /system/xbin. A message tells me that I am not root.
However, when I run Root Check Basic I am told I have root.
I ran Root Check before & after I installed S7-301u V100R001C232B012(Root_version) and Root Check said I did not have root.
So the real question is, How do I really know if I have root?
*****
Actually I installed BusyBox Installer. I'm asked to pick a version to install:
1.19.3
1.19.2
1.18.5
1.18.4
1.17.1
None of these will install.
I also have the option to install a "Custom Tune" is there one? I'd gladly pay for BusyBox pro to get BusyBox running
*******
I powered off the device. Put my sdCard back in (the rooted firmware was removed from it). Then installed the SuperUser update from the market.
Ran that - it said everything was OK. Then I forced it to update - it crashed - so I force closed it. I then realized I could not run the original SuperUser app anymore.
Next, I opened up Root Explorer and was able to move the su file over to the xbin. But now BusyBox is not acting right - It said that it was having problems installing, and I'd need to reflash (or reload - I can't recall) the rom.
I'm rebooting, and going to try to install BusyBox....to be clear on which BusyBox..it's this one:
https://market.android.com/details?...t=W251bGwsMSwyLDEsInN0ZXJpY3Nvbi5idXN5Ym94Il0.
*****
Just realized in Root Explorer, to tap the little gray box at the top. After you tap it it should read "Mount R/O"
Now you can long press a folder/file and change the read/write permission.
Rumbi,
You said to r/w enabled the su file....is that check ALL the boxes?...Read, Write, Execute Special?????
IIRC, i had some problems with busybox, too. Copy the file from the attachment to /system/xbin and try the installer again.
And i said to enable r/w support for the /system folder. There are two checkboxes in ES File Explorer. First checkbox is enable root permission for ES File Explorer and second checkbox is "Mount / and /system writable".
Now you should be able to copy whatever file you want to /system/xbin. That's how i have done it. If you have any further questions, feel free to ask. I'll try to explain.
PS. You don't ne to alter file permissions of the su-binary but mine are "rwx r-x r-x".
Rumbi, how do you feel about the High resloution mode, does it slow the tablet down? Have you had a chance to use any tegra 2 devices and if so how does the mediapad with the snapdragon compare when in standerd/high-res mode?
Nothing to complain about the Hi-Res-Mode but i don't have any Tegra2-Devices to compare, sorry.
Haven't tried any games in hi-res-mode but normal usage is just fine.
Thanks. Ill try this out. When i try to install busybox it hangs first, then i force close and run again. Then i get the message about reflashing Rom. But i know i have root. I installed connectbot and ran su and got #
Heres how i got root (im away from my pc right now so i try to be as accurate as possible) :
Installed Hauwei modified rom (its the one that says "(root) " in the file name.
Installed Root explorer
Installed Superuser
Install busybox
Install Connectbot
Put my microsd back in (with the firmware AKA dloa folder removed)
I could not get root explorer to allow rw permissions until i slid the sd card out and back in whil the device was on.
Then i ran connectbot as local and typed su hit enter then superuser popped up asking fo allow connectbot to access. Hit allow an type su hit enter an you should get # This took 3 reinstalls of the firmware to work wjthout errors. The first times resulted in superuser needing to be force closed.
I also ran superuser and went into settings and updated it eventhouh its not neede. There i got a read out saying that busybox is not installed, but it does say i have root.
Sent from my HUAWEI MediaPad using xda premium
Honestly i havent noticed a big difference between high resolution an standard.
The only issue with high res is the small icons and buttons are difficult to hit sometimes
Sent from my HUAWEI MediaPad using xda premium
Do i need to unzip this file first?....
.... Nevermind... I unzipped it and put the busybox file in th system/xbin folder.
I installed busybox installer by JRummy16. This time and it worked!!!!!!!
Now its on to figuring out 4G and tryiying to use it as a phone.
What is the xml file i need to edit?
Sent from my HUAWEI MediaPad using xda premium
Good, that you have worked it out now What exactly do you want to do? To get to the hidden menu, you have to open the calculator and type: ()()2846579()()=
To edit the XML-Files, you have to extract the cust.img... But now that you have root, yo can edit whatever is available via root explorer
€dit: To get 4G working again, maybe with someone with an original Springboard (not a flashed one) can copy the folder /system/lib/. This should be possible even without root. I think it has something to do with the ril-files...
after updating my mediapad to S301uV100R001C232B012, i have problem with 2x Client (RDP client) now, few second after conecting to rdp session, is app 2X client crashing, with error 2x Client has stopped unexpectedly (process com.tux.client), is here anybody with this problem? thanks...
Rumbi said:
€dit: To get 4G working again, maybe with someone with an original Springboard (not a flashed one) can copy the folder /system/lib/. This should be possible even without root. I think it has something to do with the ril-files...
Click to expand...
Click to collapse
How about this - link
I'll look at it, thank you And these are the libs from an unmodified Springboard, aren't they?
yes indeed. I broke the silly thing, so I haven't played with it much. guess I will have to call about how to get it fixed.
knoxjon said:
How about this - link
Click to expand...
Click to collapse
Even though I have no clue of what to do with this, THANKS! I tried to open an .so file in notepad, but no luck, but I'm assuming that the geniuses here know what to do.
On an off-root topic - How do you take a screen cap? I accidentally did it yesterday while my MediaPad was lagging, but don't know how I did it.
The Hi Suite that comes with the device can do this, but require a computer and usb hooked up. Useful, but not as practical as doing it from the tablet itself.
The *.so files are a bit like drivers for the internal components. I'll try to find differences between T-Mobile and Huawei so maybe we get 4G working again.
tedbone said:
Even though I have no clue of what to do with this, THANKS! I tried to open an .so file in notepad, but no luck, but I'm assuming that the geniuses here know what to do.
On an off-root topic - How do you take a screen cap? I accidentally did it yesterday while my MediaPad was lagging, but don't know how I did it.
The Hi Suite that comes with the device can do this, but require a computer and usb hooked up. Useful, but not as practical as doing it from the tablet itself.
Click to expand...
Click to collapse
I'm not sure how to screencap. It's so easy on CM that I've gotten lazy. Plus I rarely do it. I know there are a ton of apps for that, tho. But you could probably google "gingerbread screen capture" and find a better answer. But not with gingerbread. I'm blanking on the name for this version of android.
knoxjon said:
I'm not sure how to screencap. It's so easy on CM that I've gotten lazy. Plus I rarely do it. I know there are a ton of apps for that, tho. But you could probably google "gingerbread screen capture" and find a better answer. But not with gingerbread. I'm blanking on the name for this version of android.
Click to expand...
Click to collapse
Honeycomb
I've been Googling searches like that, and end up with actual screen shots of Honeycomb os..I'll keep looking...
Tried this (from here), but no luck:
Screen capture
Android natively supports the ability to capture a screenshot by method of pressing both the power and volume-down buttons at the same time on an Android device. This native support was first included within the Android 4.0 (Ice Cream Sandwich) update, which is first seen on the Galaxy Nexus smartphone.[86] Previously, Android did not feature native support for screen capturing which would have likely been due to security concerns. Furthermore, prior manufacturer and third-party customizations as well as using a PC connection (DDMS developer's tool) were the only known methods of capturing a screenshot on Android.
I've looked through the *.so files and many of them are exactly the same, but some are different. One file caught my interest. I've attached it here for anyone who wants to try. Please only use it, if you have a T-Mobile Springboard with flashed root Firmware. Copy the content of the zip-file to /system/lib and overwrite the existing file. But make a backup first! After copying you have to set the correct file permission (rw- r-- r--) and reboot the tab. Hopefully 4G works again with this little trick.
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
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.
Hi all,
EDIT
Thanks to techdudester on the second page, getting rid of the malware is now even easier!
Just flash the image he found here with the following procedure and you're good to go!
Instruction:
1. Flash the new ROM.
a. Get the ROM here . (Use this ROM only if you have a Venstar V140D tablet!)
b. Follow the linked tutorial to install the flash software and flash the new ROM on your device with: Phoenix Suit.
Voila, ready!
Enjoy your malware free tablet!
Tips and tricks. (or something...)
Get adb working (needed for all the other tricks down below):
1. Download the Google development tools (sdk) here and install them on your computer. I assume you have windows 7 installed during the rest of this tutorial.
2. Connect your device to your computer and make sure it is installed correctly.
a. Connect your device while its powered on via USB to your pc.
b. Go to Start, right click "My Computer" and select "Properties". Click "Device Manager".
c. Right click the Android device with the exclamation mark and select "Update Driver Software...".
d. Select "Browse my computer for driver software".
e. Select "Let me pick from a list of device drivers on my computer".
f. Keep "Show All Devices" selected and click Next.
g. Click "Have Disk..." and click "Browse..."
h. You can find the drivers in the "SDKInstallLocation"\sdk\extras\google\usb_driver directory and click OK. Replace SDKInstallLocation with the location that you selected during installation of the SDK.
i. Select the "Android ADB Interface" driver from the list and click Next.
j. Confirm installation by clicking on "Yes". Sometimes you also have to click on "Install" if a screen pops up to ask you again if you really want to install the driver...
k. Click "Close".
To use it:
Open a command prompt (in search type "cmd" followed by ENTER) and go to the following directory ""SDKInstallLocation"\sdk\platform-tools".
If you want a backup of your tablets system directory (highly recommended!) use:
"adb pull /system C:\system"
where C:\system is the target location on your local computer where you want the backup of the system directory.
Remove the update package (this doesn't work for updating the tablet, so, useless.)
adb remount
adb shell
cd system/app
rm Update.apk
exit
Remove the unwanted apps (dragonfire.apk etc)
adb remount
adb shell
cd system/preinstall
rm *
exit
If you would like to have your tablet in the correct time zone after factory reset, you will have to adjust the build.prop file.
First you need to get it to your pc so you can edit it:
in the command prompt window and at the same location as in the tutorial above type "adb pull /system/build.prop C:\temp\build.prop".
Just in case, make a copy of the build.prop in Windows Explorer so you always have the original file if something goes wrong.
Now you can edit the build.prop, but DON'T EDIT IT WITH THE WINDOWS NOTEPAD! Use Notepad++ or similar to edit the build.prop.
After you made the changes (and be careful here, you could end up with a tablet that does not want to boot up, solution further down below) you have to upload the file back to your tablet.
in the command prompt type:
adb remount
adb push C:\temp\build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
Don't forget the last line! If you do not chmod the file (set the correct permissions) your tablet will not boot up.
Changes in the build.prop:
Time zone:
Default time zone is "persist.sys.timezone=Europe/London"
you can change this to your locale time zone like "persist.sys.timezone=Europe/Amsterdam" (for the netherlands )
Search the internet for valid time zones.
Change the default language:
The default language is determined by these two values in the build.prop:
persist.sys.language=en
persist.sys.country=US
For dutch change them to:
persist.sys.language=nl
persist.sys.country=NL
and again, search the internet for valid language values.
Higher brightness after factory reset:
Add the following line to the build.prop file (at the top of the file)
ro.ph.def_brightness=225
You pushed the build.prop without changing the permissions:
No problem. Just connect your booting tablet to the PC, install the driver if its not installed correctly like explained in the tutorial, and then change the rights via adb. It's no problem that it's not fully booted!
in a command prompt in the adb directory:
adb remount
adb shell chmod 644 /system/build.prop
adb reboot
If you pushed a wrong non functioning build.prop, just use this method to push the original build.prop (you know, the copy you made ) back to the device (followed by setting the correct permissions of course).
Remove the (in my opinion) irritating boot sound:
adb remount
adb shell
cd system/media
rm boot.wav
exit
rom download
can you provide another way to download the rom file ,i cant seem to get the registration process to work
stevethesignguy865 said:
can you provide another way to download the rom file ,i cant seem to get the registration process to work
Click to expand...
Click to collapse
I have dropped it here. Hope this helps
I bought the same tablet for my daughter. She's (and so am I) suffering from a lot of annoying popups and ads.
Thanks for sharing your instructions here, very hard to find them!
Since I'm a complete newbie: one important question. When you flash the ROM, all of the apps (games) will be removed I guess?
Second question: can you put the stock rom on a different location? Both of the links (including Filedropper) don't contain any files...
Thanks!
1ce/ said:
I bought the same tablet for my daughter. She's (and so am I) suffering from a lot of annoying popups and ads.
Thanks for sharing your instructions here, very hard to find them!
Since I'm a complete newbie: one important question. When you flash the ROM, all of the apps (games) will be removed I guess?
Second question: can you put the stock rom on a different location? Both of the links (including Filedropper) don't contain any files...
Thanks!
Click to expand...
Click to collapse
Yes, all applications will be removed. As soon as you configure the tablet again with the same gmail account, it will probably start installing the applications and games automatically, but in game progress will be lost for most (not online) games.
I am re-uploading the file. Will update this post with the link as soon as it finishes
edit: upload finished, get it while its there LINK
BlueFlame said:
edit: upload finished, get it while its there LINK
Click to expand...
Click to collapse
Great! Thanks for the swift response. The file is about 307 MB. Is this correct? I'll start working on it, probably this weekend. I'll keep you posted.
1ce/ said:
Great! Thanks for the swift response. The file is about 307 MB. Is this correct? I'll start working on it, probably this weekend. I'll keep you posted.
Click to expand...
Click to collapse
Yes, thats correct. Once unpacked it will be around 520 MB.
Good luck!
Hi BlueFlame,
Thanks for the post. Is it possible to get the image uploaded again? Would be much appreciated.
Maylar said:
Hi BlueFlame,
Thanks for the post. Is it possible to get the image uploaded again? Would be much appreciated.
Click to expand...
Click to collapse
On request. You can find it here. (Adjusted link. Stored on Google Drive)
Thanking you. Very much appreciated.
Thank's for a fantastic procedure... Worked very well.
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
1ce/ said:
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
Click to expand...
Click to collapse
Is that the firmware that I provided?
If not, try to download it again.
If so, I think that your tablet has a newer firmware than this one. You could contact the seller of your tablet for the current (latest) firmware for this tablet.
If you get a newer firmware, please share
Image file invalid
Hi Blueflame,
I've tried to re-flash, but at some point i'm getting the message at livesuit V1.11 that the image file is invalid.
It's the 3rd time i have downloaded the file, what could be cause of this error?
Greetz Mike
mcwheelz said:
Hi Blueflame,
I've tried to re-flash, but at some point i'm getting the message at livesuit V1.11 that the image file is invalid.
It's the 3rd time i have downloaded the file, what could be cause of this error?
Greetz Mike
Click to expand...
Click to collapse
Not sure. Will upload it again this weekend just to be sure that it's not my uploaded image. (I will let you know once I've done that)
You can, on the other hand, contact the supplier (where you bought the tablet) and ask them for the latest version of the ROM. I would also be interested in that
BlueFlame said:
Not sure. Will upload it again this weekend just to be sure that it's not my uploaded image. (I will let you know once I've done that)
You can, on the other hand, contact the supplier (where you bought the tablet) and ask them for the latest version of the ROM. I would also be interested in that
Click to expand...
Click to collapse
Uploaded again! same link (just made it a new version in Google Drive).
Open Firmware failed - possible solution
1ce/ said:
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
Click to expand...
Click to collapse
Try to put the image file in a directory without special characters (i.e. c:\temp). Worked for me.
wundabua
Te real FIX is In!
Ok, i have one of these allwinner, Venstar, "whatever", A33 D140v tablets. It had all the usual problems and more, because the first thing I tried, was to use the built in recovery to "restore to factory". This made things even worse, because after the recovery, I couldn't reach the Google authentication servers.
I am pro tech with 25 years in the trenches and I have to admit this thing really threw me for a loop, because I spent an entire day researching the solution, installing Android SDK, drivers, Phoenix Suit, Live Suit, etc. These were all very complicated "solutions" that took me exactly nowhere. I finally found the answer in a rather stupid Youtube video.
The REAL answer is actually very quick and easy compared to all these other recommended methods.
In the first place, model V140d image is only used for these infected tablets. The actual model is V11 and once you use the quick restore method I discovered, you will have a malware free V11 model. The whole secret to this method, is the fact that these units were designed to be quickly, automatically and completely restored in less that 5 minutes through the use of their built in micro SD slot.
Imagine that!
If you check your tablet that came new in the box as something other than V140d, the method I used will most probably not work for you.
Anyway, the quick method I discovered, can be seen on my own tech support site. To find it, Google: Just Call Techdude
Then click on the support link at the top of the page on my site and all will be revealed.
techdudester said:
Ok, i have one of these allwinner, Venstar, "whatever", A33 D140v tablets. It had all the usual problems and more, because the first thing I tried, was to use the built in recovery to "restore to factory". This made things even worse, because after the recovery, I couldn't reach the Google authentication servers.
I am pro tech with 25 years in the trenches and I have to admit this thing really threw me for a loop, because I spent an entire day researching the solution, installing Android SDK, drivers, Phoenix Suit, Live Suit, etc. These were all very complicated "solutions" that took me exactly nowhere. I finally found the answer in a rather stupid Youtube video.
Click to expand...
Click to collapse
Hi techdudester,
The combination "pro tech with 25 years in the trenches" and "very complicated "solutions"" sounds a bit strange.
But either way, a THANK YOU is in order!
The ROM you found works on my tablet (flashed yesterday) and so far so good. No popups and no unwanted application downloads!
I will adjust my initial post to incorporate this image.