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.
Related
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
I am trying to find a how to root idea usa 7" tablet from fry's for $77.00. Their is a lot of rooting programs but I have not been able to find anything on this model.
Also what would be a good rom to flash it with? I tried finding out if uberoid or cyanogenmod would work but I could not find any info on this model.
Not to sure what model I have that I would be able to flashing this rom with, either uberoid, cm7/cm9 or miui? Help
Model: MID, sv7206 v1.4, kernel 2.6.35.7-infotm
processor armv6 rev5,
hardware imapx200,
android 2.3.3,
brand infotmic,
display gri40,
release codename REL
bootloader unknown
I don't know if this is the right model IDea USA IUMID-0071 because the spec's are off. Http ://ideausa.us/produects.html but similar. I am looking for rom that is more update/modern. any potters?
Does anyone have the original rom for this or know how to make a backup this rom?
Well I am thinking that is might be this model but not to sure wm8650,SV7206 v1.4 or IDea USA IUMID-0071.
The screen is very slow on this model. Unless you use a pen then is works better.
Also hoping to be able to flash this to ics 4
Just trying to get some clarification.
Try running the superoneclick batches. Shortfuse.org
Sent from my HTC Sensation Z710e using XDA App
Thanks, I am download it right now.
Also can you use airdroid to do a backup or has anyone tried this yet and maybe upload a rom that way? any thoughts?
Thanks
Never heard of airdroid
Sent from my HTC Sensation Z710e using XDA App
AirDroid is a fast, free app that lets you wirelessly manage & control your Android device from a web browser Over-The-Air. Just for anyone that wants to know.
I don't know if airdroid can copy all of your file to the desktop from your browser. But I don't know how the file system works for the android. So I wouldn't know if it can or is there a good place to read about the android file system? Wait I know I will google that. google is my friend. But I was hoping for a more advance person that could answer on this topic than me.
Thanks
U have to have a custom recovery to do nandroid backups
Sent from my HTC Sensation Z710e using XDA App
I have not been able to connect this device to the computer. Nothing is being recognize. It does not show up under linux os either. I am not sure what drivers will work for this thing. USB debugging is also enabled.
Any ideas?
Thanks
Rooting Idea USA Tablet
Oh my, what a mess...
This post is in regards to the Idea USA Tablet (Unable to Root)
My specs:
- Idea USA Tablet (Made in China)
- Model Number: MID (Unknown)
- Android Version: 2.3
- Kernel Version: 2.6.35.7
- Build Number: MID-userdebug 2.3 GRH55 (ENG)
Issues:
Whelp, I have tried the basics and I can't get this thing to root for anything. I was able to get it to hook into the PC through USB. There are 2 usb slots on the side of the tablet. I believe one is for HOST and the other usb is for OTG (Charging). Once I figured out the host port, then I had to download the drivers for this poorly made tablet...But, what drivers? You go to the Idea US website and you get no helpful information. So, there are no drivers made specifically for this $100 dollar generic tablet from FRY's. Ok... No big deal... So, I download the default "Android USB Drivers".
Peachy, it worked! Now, I can transfer files back and forth between the card(s). Wonderful, first step down, next step was to root. So, I read up on how to root with Super One Click.
Ok, so now, I set the tablet to "USB Storage" and "Host"...Then I download and run Super One Click.
Ok, I run the "Super One Click v.2.3.3"; by clicking the root button and then all I get is a frozen screen that reads:
Code:
Killing ADB Server.... Kill Server 0.11s
Starting ADB Server.... StartServer 4.09s * daemon not running. starting it now on port 5037* *daemon started successfully*
And then it just freezes the program. So, now I'm completely stuck. I mean I learned a great deal, that I can hook up a keyboard, mouse, etc to this thing, but, obviously Super One Click was not designed for these generic tablets. I have read other articles which have suggested that the .inf driver for the default "Android USB Drivers" needs to be edited for your specific tablet model and you must enter the specific CODE# for it to recognize for rooting with Super One Click... But, god forbid, I haven't found any useful information on where that might be. Also, someone suggested to install the Android SDK and edit those files along with the .inf files to make this work. But, that didn't work either. I did everything right. I turned off USB debugging and then I would wait for super one click to come up with waiting for device...but that never happened. I even tried it with USB debugging on... still nothing.
Has anyone created a generic batch program to root these types of devices? What am I doing wrong here?
Since every tablet is different with different boot mangment. Makes it hard to make a generic root kit.. and being a frys computer salesman I try very hard to talk people out of those things unless. They swear they are only us8ing it for facebook
Sent from my SPH-D700 using xda premium
Rooting Idea USA Tablet
Well, this took me all night to read and learn about how to root this basic tablet from Fry's.
First off, I tried many different things and it just didn't work. Using super one click is definitely out of the question for this particular tablet.
I read all night and thankfully found the forum article on how to solve this issue on xdadevelopers own forum.
As per quoted quotes below:
.....You can use gingerbreak to root this. Run it once and let it reboot, then use supermanager free from market to rename the su symlink from /bin/ to "old" or something, and reboot again.
You should now have root ........ It might take a couple of trys but it works.
You need to download supermanager from the market. Enable root in supermanager settings and click yes when superuser pops up.
Then use the file explorer within supermanager to navigate to the /bin/ directory and you will find a sysmlink called su
You need to rename this su symlink to old - completely take out the name su.
Just to be safe run gingerbreak again and then you can install busybox from market.
pablo11
Click to expand...
Click to collapse
Thank you so much Pablo11. The idea is to download the APK for GingerBreak from online onto your IDEA USA tablet directly. The trick here is that the brand name is IDEA "USA", but the real workings behind the "MID" is "ViMicro". You will notice that displayed as you turn on your tablet. So, in order to find real information about your MID device, you have to search articles for vimicro.
Once you run gingerbreak, your tablet will go completely nuts. Nothing will run right. Things will break and it will be a complete mess. It will however, install superuser apk. However, it will not work. You can download the Root Checker from the market and you will notice it is NOT rooted. So...thanks to pablo11, you will want to download supermanager from the google play market. Install it.
Next go into the supermanager settings and click on ROOT. Make sure root is enabled and checked marked in the settings. When you enable root in the settings, it will prompt you with "allow root?" Click on Yes. This will give you the access you need.
But, your not done, once again as per Pablo11, go to the super managers file manager section. Get to the root directory by clicking up, and then find the folder "bin". Look for the file "SU" and rename this to "old".
Now, you will be able install busybox and any thing else thats root.
By the way, restart your tablet again, and I "personally" recommend that you go into your settings> Privacy> Check mark both (Backup my data and Automatic Restore) and then click on Factory data reset. Start the tablet from like it was brand new. Don't worry it will keep the root that you did intact. You will just have to re-register the tablet with your existing gmail that you originally used with that tablet.
Lastly, use the root checker from the market and you will see that it is successfully rooted.
Okay... Now, my next step. To crack open this tablet and put in a bigger SD Card as the 2G SDCARD is way too small, especially if you want to use new roms and install a linux operating system onto it....
@njbsuperman story telling of Pablo11's method worked for me. I have a generic android 2.2 7 in. "MID" white box, picture of the tablet on each side all of that and it worked for me. Had to restart and run ginger break a couple times but I followed the directions and it worked.
Thanks for posting this, got this for my 6 yr old for his b-day and of course I gotta ****in tim allen it and I happened to stumble across your findings and your post you put up 2 days before the unwrap. Thanks...smoke blunts.
Using Unlock Root to Root IDeaUSA Tablet
I know that this thread is a few months old, but I thought that I'd share what I used to root my 7" IDeaUSA YG A777 Android Tablet. I used Unlock Root. It's a simple program that rooted my tablet in minutes with one click. This site won't let me insert links in posts (I'm new to this site), but you can find the program by typing "Unlock Root" into Google. It should be the first site that comes up.
Same here
Yes i used unlock root also and it worked for me/....
Rooting IdeaUSA CT-702
kokomelala said:
Yes i used unlock root also and it worked for me/....
Click to expand...
Click to collapse
I have the CT-702 with Android 4.0.3 and can't get past the USB connecting to the storage devices. I can manipulate the files on the internal and external cards but any attempts to use the unlockroot package (from unlockroot.com which is full of adware) or other packages (z4root, ICS Root Unlocker 1.0) do not detect the device. There is a payware unlockroot package at unlockroot.org. Is this the package that works? Is there a no computer apk like gingerbreak (which fails) available or a procedure to get past the USB business.
is there a way to root the idea USA ct-705
I've recently purchased the CT-705 and been trying to find any information on rooting this device but all if have found are other people with the same problem can anyone help
specs
Model:
CT705
Android version:
4.1.1
Kernel version:
3.0.8+
[email protected] #877
SMP PREEMPT Fri Jan 11 10:12:03 CST 2013
Firmware version:
([email protected])_([email protected])_N2.59_V411.01_TL12
Build number:
RK30_ANDROID4.1.1-SDK-V1.00.00
rk30sdk-eng4.1.1 JRO03H 20130111.093246 release-keys
any and all info is appreciated thanks
Another CT-705
@captinmudslide,
I'm in the same boat as you, in fact we must have bought them about the same time. I'm hoping that you are following this thread, and that you found something that works to root this beast. I 've been digging and trying any and everything I can find that works on other android devices. I was hoping that holding the power button and vol+ or vol- would get me somewhere. Vol+ at least gives me the dead robot, but can't do anything with it. Was hoping that if the adb server was running it would connect. Nope.
Anybody monitoring this thread, feel free to offer something that hasn't already been covered previously.
Thanks.
njbsuperman said:
The idea is to download the APK for GingerBreak from online onto your IDEA USA tablet directly. The trick here is that the brand name is IDEA "USA", but the real workings behind the "MID" is "ViMicro". You will notice that displayed as you turn on your tablet. So, in order to find real information about your MID device, you have to search articles for vimicro.
Once you run gingerbreak, your tablet will go completely nuts.
Click to expand...
Click to collapse
Holy crap, I rooted the device.
If anyone needs this later, here's what I did:
Fist I pulled down SRS Root, Unlock Root, Gingerbreak and the generic Google USB drivers.
I went into the properties of the missing driver CT1006 and checked the hardware ID. I opened android_winusb.inf and added the lines:
;ProScan plt-7035
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&REV_0222&MI_01
under the headings of [Google.NTx86] and [Google.NTamd64].
I ran Gingerbreak a few times, per a thread I read, but the app would hang. I tried it 3 times.
Then, I went back to Device Manager and selected "Update Driver" and pointed to the .inf I edited earlier. I detached and reattached the device via USB to my PC and ran SRS Root, which still reported an error. Then I ran Unlock Root and the first time it said my device was already rooted, but I told it to root again. It did and my device rooted. I then looked in my apps and found SuperSU installed and was able to run Sixaxis Controller, which requires root to run, which confirmed root worked.
I don't know which step actually solved the issue, but hopefully if anyone has this issue in the future, they can figure that part out.
iDeaUSA CT705 (RK3066) Rooted
... CT-705 ... [email protected])_([email protected])_N2.59_V411.01_TL12 ...
RK30_ANDROID4.1.1-SDK-V1.00.00 rk30sdk-eng4.1.1 JRO03H 20130111.093246 release-keys...
any and all info is appreciated thanks
Click to expand...
Click to collapse
I've been able to root this tablet using Kingo ROOT, with the "latest_usb_driver" from Google (1/27/2014).
I have set:
c:\users\{USERNAME}\.android\adb_usb.ini
with the value: 0x2207
And have used the RK_DriverAssitant available online
It takes a lllllllloooooooooonnnnnnnnggggggg time for my Windows 8.1 x64 to recognize it, but eventually it will show with:
c:\adt\sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
Then run Kingo ROOT.
C.U.tech
You can root with:
POOT: This app is a one click root app. No computer needed
Framaroot: Framaroot is a oneclick root app . No computer needed
This is the most popular one!
Z4Root: Z4Root is an oneclick root app . No computer needed
Towelroot: Towelroot is an oneclick root app. No computer needed
Baidu: No information
Vroot: No information
Gingerbreak: This app can root almost all gingerbread devices
Downloads:
Poot - Download the app >>here<<
Framaroot - Download the app inside this XDA Thread - >> CLICK HERE <<
Z4ROOT - Download the app inside this XDA Thread - >> CLICK HERE <<
Towelroot - Download the app inside this XDA Thread - >> CLICK HERE <<
Baidu ROOT - Download the app >> HERE <<
vROOT - Download the app >> HERE <<
Gingerbreak - Download the app inside this XDA Thread - >> CLICK HERE <<
Flash a SU ZIP - Download the ZIP >> HERE << and flash it on your unlocked bootloader phone !
Hit thanks if you liked this post or this post has helped you out !
Does anyone have any information on rooting the AZPEN A701 Tablet (ICS OS)?
All my searches keep popping up for the Acer Iconia A701.
drivers
I found the correct address for the drivers for this tablet, and 2 others from Azpen.
www.mediafire.com/azpensupport
The links on their webpage incorrectly spell mediafire and also include .com in the last part of the link.
Note: I recently got an email from Azpen telling me the exact same url that I had already figured out. Their email is about week to a week and a half after I sent them a request for the proper address. Also, as of the time I am posting this update, they have not corrected the address on their website.
Tried methods
I have tried SuperOneClick which reports that the system is rooted, but ADB Wireless says it is not.
I have tried Bin4ry's Root Many Android! (options 1, 3, and G) and briefly got temp root on option 3 but I lose wireless functionality (I get one or the other message from ADB Wireless (no root or no wireless), verified that Wireless connection has been turned off and won't turn back on until reboot which loses me the root again).
Retries
Ok, finally rooted the Azpen A701.
What I did:
First, I went back to SuperOneClick, and choose Unroot to reverse anything it did.
Retried Bin4ry's Root Many Android! v31, option 1 (new standard method), test, failed, unroot, 3 (old method), test, failed, unroot, then G (Google Glass method), test, WORKED this time.
Verified by using a root browser (can see files/folders(subdirectories) in /data after giving permission), a root checker (note: do not turn on SuperUser's Autoanswer, gives false information from some checkers), and ADB Wireless works while in range of a wireless router/source.
I am guessing that somehow the leftovers from SuperOneClick were affecting my results with Bin4ry's collected scripts.
Props to all that developed each of those programs and scripts.
I don't know if anyone will be seeing this but I hope it helps anyone needing the info.
Just curious to know if there is a rom available in case this method bricks the tablet? I bought this tablet a couple of weeks ago because I wanted to mess with one and I didn't have a lot of cash to spend. I use it daily and my kids play games on it. I can't afford to get another anytime soon, however I'd like to have it rooted so that I can remove factory installed apps that I don't want or need.
no idea
BizarreMan said:
Just curious to know if there is a rom available in case this method bricks the tablet? I bought this tablet a couple of weeks ago because I wanted to mess with one and I didn't have a lot of cash to spend. I use it daily and my kids play games on it. I can't afford to get another anytime soon, however I'd like to have it rooted so that I can remove factory installed apps that I don't want or need.
Click to expand...
Click to collapse
I have absolutely no idea. The only additional rom I have seen ANYWHERE is the Jellybean update for it (see driver link above). This seems to not be a very popular tablet to work with, going by the fact I received no help from anyone here. All research on this so far has been done by me. I stumbled on to Bin4ry's rooting method by accident. I'm not a ROMer, I don't know how to build one. Also I don't know which ROM backup method to use on it/will work with it.
Alright
I'll give it a shot during the weekend, I've grabbed the jelly bean update (thanks for the link). Hopefully all goes well. I figured there would be little to no support for this device, however due to a tight budget I chose to get this tablet.
I don't really mind the lack of support, however I'd like to have root because like on my old phone I had a few programs I used that required root.
Thanks again.
*Edit*
I attempted last night as I had free time to do the root method and unfortunately it did not work on my device. Not sure why it did not work. I'll try it again at a later time when I can. I also attempted to upgrade to 4.2 but it seems as though I am having issues with it as well.
Maybe I'm just stuck with the tablet as is
trying again...
BizarreMan said:
I'll give it a shot during the weekend, I've grabbed the jelly bean update (thanks for the link). Hopefully all goes well. I figured there would be little to no support for this device, however due to a tight budget I chose to get this tablet.
I don't really mind the lack of support, however I'd like to have root because like on my old phone I had a few programs I used that required root.
Thanks again.
*Edit*
I attempted last night as I had free time to do the root method and unfortunately it did not work on my device. Not sure why it did not work. I'll try it again at a later time when I can. I also attempted to upgrade to 4.2 but it seems as though I am having issues with it as well.
Maybe I'm just stuck with the tablet as is
Click to expand...
Click to collapse
It may have been the sequence I used. Tried SuperOneClick several times (as above it said tablet was rooted but several apps said it wasn't) which installed su, busybox, and superuser. Then found Bin4ry's method, got temp root (tryied 1, 3, and Glass). Then went back to SuperOneClick and unrooted, returned to Bin4ry's and finally got it with Glass method.
Don't know if that helps
Well
After several attempts via Bin4ry and SuperOneClick I have obtained root on this tablet.
Not quite sure which actually did it though as with super one click it froze on me during both times I used it and each time I tried Bin4ry's method I kept getting messages about connecting my device (which was connected fro the get go).
After several tries with these programs yesterday and finally saying screw it I decided to add some apps that required root. I don't know why I did it I just figured it was worth a shot. I added Super User which told me I was rooted, then I added Titanium Backup and was able to use it as it is intended. For added measure I also installed and ran root checker which as well as super user verified that the tablet had been rooted.
Good to see that your were able to root.
BizarreMan said:
After several attempts via Bin4ry and SuperOneClick I have obtained root on this tablet.
Not quite sure which actually did it though as with super one click it froze on me during both times I used it and each time I tried Bin4ry's method I kept getting messages about connecting my device (which was connected fro the get go).
After several tries with these programs yesterday and finally saying screw it I decided to add some apps that required root. I don't know why I did it I just figured it was worth a shot. I added Super User which told me I was rooted, then I added Titanium Backup and was able to use it as it is intended. For added measure I also installed and ran root checker which as well as super user verified that the tablet had been rooted.
Click to expand...
Click to collapse
So I think we can safely say that using both methods together + patience will root this tablet (don't know why one or the other wouldn't do it).
Not having any luck
CyberSpiderPrime said:
Does anyone have any information on rooting the AZPEN A701 Tablet (ICS OS)?
All my searches keep popping up for the Acer Iconia A701.
Click to expand...
Click to collapse
I have been trying to root AZPEN A701 for the past week, I have tried everything written on this forum. Any help PLEASE!
clean slate
Are you willing to do a full restart on the tablet (factory reset)? I had to do that before my root took, as I found on other systems that I have rooted some programs you load can interfer with rooting. Save any personal data before you do this, programs can be reinstalled from Google Play or (hopefully you saved them if you downloaded them) your computer
Factory reset:
Press and hold up volume button then press and hold power button. The screen will remain black (no backlight)
Wait 4 seconds then release both buttons (backlight will come on). Shortly the android on it's back with the open torso (the sick android) will be displayed.
Press the down volume button. You should see 5 options available- You are now in the System Recovery program.
Using the up or down volume button to highlight an option then press power to select the option.
1) select Wipe Cache Partition
let the unit reboot, then turn it completely off
reenter System Recovery again.
2) select Wipe data/factory reset
let the unit reboot, then turn it completely off
The system is as clean as it is going to get now.
On your pc (don't know for MAC's) download the drivers, Android programs needed (Android Debug Bridge -ADB- is part of the Android Development kit and some Java Development Kits), and both SuperOneClick and Bin4ry's root software. Install all software and drivers as per their instructions. Run SuperOneClick and Bin4ry's root programs. Busybox and SuperUser will be added automatically by these root programs.
While having wifi and internet access (McDonalds anyone?), re-sign up for Google Play (sorry, but the settings got wiped earler). Go to Google Play and let all the programs update. Update Busybox and SuperUser if needed/possible.
Download any root enabled file system browser (FSB) (permission will have to be granted in program to use root functions) - I used Ghost Commander for mine. It may take a bit to find it in the directory structure for the FSB you downloaded but you need to get to the root system folder.
Ghost Commander has a Local Storage option press it and an new list of folders/files will be displayed, move to the previous folder level (double dots at the top) and give permission to move to a system folder, move to the previous folder again to get to root directory, "/mnt" is the directory you just came out of and is highlighted but you will be at the root of the file system.
Enter the "/data" directory. If you can see files listed there, you have root; if not rooting attempt failed.
Once rooted, doing a system cleaning and Factory reset will not remove root but will remove SuperUser and Busybox (re-run one of the root programs to re-install then update the next time you are on the internet/web). Updating/upgrading the rom will remove root if the rom does not have root activated - I don't know of any custom roms for this tablet (there is a Jellybean upgrade in the Azpen website, if they haven't updated to the correct web address then use the one I listed on the front page, mediafire is spelled wrong in the address). Nandroid level system backup is not available yet for this tablet to my knowledge.
For several reasons, do not turn on SuperUser's automatically give permission option (the one that affects all programs), except on a one for one basis: 1) some root testing programs will fail if this option is turned on, 2) security: turning this on will allow ALL programs - including some malicious ones - to have super-user rights, 3) you will get to know which programs are asking for root permissions beforehand not after, you may want some to have automatic access (like DroidWall in my case, a firewall) and not others.
Also other information that can be useful:
/sdcard does not refer to the removeable SDCard but to the internal user data area. All programs that can be moved to a SDCard (like by Apps2SD) will be moved to this directory by default (some may allow re-assignment of the destination location) instead of the removeable SDCard (blame Azpen, it was their decision to use the directory and name that way). On most other systems /sdcard is the removeable SDCard.
/extsd is the removeable SDCard, when installed, maximum size is 32Gb.
/usbhost1 is for any usb flashdrive connected by a USB-OTG cable (OTG means On-The-Go, special usb cable that puts the tablet into host mode, similar to connecting a flashdrive to a computer, the cable is not a standard Data Connect/transfer cable, one USB-OTG comes with this tablet). Note about USB-OTG cables: if one is connected you can connect either a flashdrive, usb keyboard, usb mouse, combo keyboard/mouse unit, or a powered usb 2.0 hub. Only one flashdrive can be connected at a time (anyone know of downloadable software that would allow 2 or more? I know some modified kernels can allow more than one) so with a hub you can connect a flashdrive + keyboard + mouse (I use the RII wireless combo keyboard and mouse with mine). Maximum size appears to be 8GB, format must be FAT32; will be testing with a 16GB key shortly.
Azpen A701 and Jelly Bean
Shortly after I wrote the above I had to re-flash my tablet, but Azpen had deleted the ICS image (after a request it was restored to the site, get it while you can) and had to flash Jelly Bean. I found there were troubles with this image.
First: I could not write to either the external SDCard (called extsd) nor an attached USB flash key; reading was unaffected. I found this out when I attempted to reassign my backup location to the external sdcard and it was unable to create the directories.
Second: I couldn't find a rooting program.
After a little research, I found that the external media had not been given R/W permission in the platform.xml file - I could actually navigate the FS and read the file even without root.
Also I finally found after 2 days of searching a root program, VROOT, http://forum.xda-developers.com/showthread.php?t=2434453, that would work. Be prepared to deal with Chinese for a little bit and follow the instructions on that page (press the buttons to see screenshots). The superuser app needed to fix/replace the Chinese app is SuperSU (Google Play) which supposedly fixes problems found with other superuser apps. Once you have downloaded SuperSU, had it download/update its binaries and have rebooted, you will have to disable the Chinese Superuser app as you are unable to uninstall it using the app manager: I located it by its icon (shield with cog) in /system/app and appened '.old' to the name: "Superuser.apk" => "Superuser.apk.old'. I didn't use Titanium Backup as suggested because I am not a fan of the program .
platform.xml is located in /system/ext/permissions. After you have root, open platform.xml in what ever text processor you want locally or transfer it to your computer and work with it. You will have to add '<group gid="media_rw">' to the 'WRITE_EXTERNAL_STORAGE' group, on the line after '<group gid="sdcard_rw">' (don't type the single quotes but the double quotes are needed) and write the file back to its location (need root for that, adb pull/push may be possible to fix this). Remember on this tablet, sdcard refers to the internal user storage, media_rw will give permissions to the extsd (external sdcard) and USBHost1 (using included USB-OTG cable and a flash drive). I rebooted the tablet and tested the RW state of extsd, and voila, it now is write capable.
I wish there was more aid on this tablet but since it is not mainstream (not made by a big manufacturer like LG, Motorola, Samsung, etc.) I doubt that it is coming (I am not a ROMmer but have been using computers since the 80's, so I know a few tricks and am always learning). I will keep adding info as I find or fix it.
I will probably go back to ICS as some of my programs are not working right, and JB is sluggish.
I just picked up the A700 from Microcenter, and this is the ONLY reference to rooting the device I could find. The Azpen website doesn't even acknowledge the device's existence. I just came across this yesterday: Azpen A700 - Cyanogenmod forums. I used the Kingo method without a hitch.
Hopefully, all the other folks who get that tablet for the pre-Black Friday sale who found this link will benefit.
johncro13 said:
I just picked up the A700 from Microcenter, and this is the ONLY reference to rooting the device I could find. The Azpen website doesn't even acknowledge the device's existence. I just came across this yesterday: Azpen A700 - Cyanogenmod forums. I used the Kingo method without a hitch.
Hopefully, all the other folks who get that tablet for the pre-Black Friday sale who found this link will benefit.
Click to expand...
Click to collapse
I picked up this tablet also. Not bad for $40. I used this method to root http://www.cydiaimpactor.com/ It worked the first time. I just had to do it on an old XP machine. Windows 8 would not load the right android drivers. Now I'm working on getting Titanium backup to see my external SD card.
comstar said:
I picked up this tablet also. Not bad for $40. I used this method to root http://www.cydiaimpactor.com/ It worked the first time. I just had to do it on an old XP machine. Windows 8 would not load the right android drivers. Now I'm working on getting Titanium backup to see my external SD card.
Click to expand...
Click to collapse
I was going to return it as no rooting procedure would work....(I only bought it so I could have a android tab to fool with...i'm windows tablet all the way)...and once I tried out that rooter it worked...thanks alot for the info!
cheeb said:
I was going to return it as no rooting procedure would work....(I only bought it so I could have a android tab to fool with...i'm windows tablet all the way)...and once I tried out that rooter it worked...thanks alot for the info!
Click to expand...
Click to collapse
Glad it worked for you! I started this thread for the A700 http://forum.xda-developers.com/showthread.php?t=2532464 - No activity in it yet. But if you come across anything good post it over there.
Sent from my Transformer TF101 using XDA Premium HD app
Update
I am glad to see that others are taking an interest in this tablet.
I found 2 methods that worked and am glad that others are finding more.
Now if I can get the boot loader cracked I could finally make a nandroid copy and save myself 4+ hours restoring everything when it goes wonky. This has happened twice- OS partition fills up (and don't know why) and the device resets to near factory reset level (even some of the factory apps are missing) and won't install anything but the smallest of apps which are deleted on the next reboot; the only solution is to re-flash the tablet. Note that I have gone back to using ICS as JB has other problems (external media including its own sdcard partition is not rw enabled for one).
I WANT TO START OFF BY SAYING THAT THIS IS THE FIRST TIME I HAVE MADE A THREAD ON THIS SITE.
I FEEL MY ISSUE IS UNIQUE AND ALL HELP WILL BE MUCH APPRECIATED. THANK YOU
Click to expand...
Click to collapse
The tablet that I am dealing with is a "Cruz Velocity Mini Tablet" running android 2.0 and no means of installing apk's.
Currently this is the situation:
A friend of mine lent me her Chinese reader tablet.
I told her that I could probably flash a newer version of Android on it, thinking that I could finally try my hand at making a ROM because I know for a fact that there aren't many ROMs if any at all out there for a chinese off brand reader like this.
After rooting the tablet I deleted the pre installed bloatware via ADB commands (shell) including a file manager (Astro) that I believe was the only way that you could browse files on the tablet, as well as some other pre installed applications that must have been necessary in retrospect. There is no existing vending capability or market application.
I am looking to make a custom ROM (Using android Kitchen and Cywign) through following this tutorial by lokeshsaini94 yet I feel like following that tutorial won't even get me where I need to be.
Click to expand...
Click to collapse
Things that I have tried at this point include:
Attempting to connect the tablet to my computer with the SD inserted (with and without debugging turned on) [Failed to show up on my computer as a device or anything]
Downloading the APK that I need from a file sharing website [Downloads fail]
Uploading the APK that I need to my Google drive and downloading it from the tablet [Says waiting for data connection and doesn't download even though connected to our WiFi]
Inserting the SD card into my computer, copying the APK I need over to it, then inserting the SD card back into the tablet, going into the browser and typing "File:///sdcard/<name here>.apk" to install an APK but getting an error in the installer after pushing 'install' -> 'Application not installed'
Trying to perform a factory reset; this simply makes the tablet reboot with everything the same as it was before.
Essentially guys and gals, my tablet here is running Android 2.0, I want to update it by making my own rom for it to something at least >4.0, and it seems that I've made things worse and have no way out of this mess. I think I've essentially bricked it even though it still works. :silly:
What do I need to do to make a custom ROM let alone flash/wipe this tablet?
All help will be incredibly valuable
There should be plenty of info here http://www.slatedroid.com/forum/93-velocity-micro-cruz-reader/ to get you on the right track. Not likely you'd be able to get anything beyond Gingerbread on there running due to lack of source code. Your only hope would be to see if there is a newer tablet with the same chipset that has something newer on it to port over.
Still no paddles
es0tericcha0s said:
There should be plenty of info here < > to get you on the right track. Not likely you'd be able to get anything beyond Gingerbread on there running due to lack of source code. Your only hope would be to see if there is a newer tablet with the same chipset that has something newer on it to port over.
Click to expand...
Click to collapse
Thank you very much for your response. It looks like on that website I've already found multiple useful roms!
In fact I already downloaded one and put it onto the SD card. Apparently for these tablets you're supposed to, while powered off, turn it back on by holding the power button and the volume up button but all this seems to do as a whole load of nothing.
I fear that what I've done to it by deleting potentially sensitive programs previously, I have somehow managed to make this process impossible.
Is there some kind of way that I can plug this tablet into my computer and be able to completely wipe it so I can, at the very least, have a functional tablet that will work at all? I've done approximately 5 factory data resets yet the background image that my friend has on the tablet as well as seemingly every single setting and application is remaining untouched..
Try the ones here that also install a custom recovery: http://www.slatedroid.com/topic/33586-a-clockworkmod-rom-compendium-for-the-cruz-reader/
You'll want to make sure and rename the file exactly as mentioned there on the OP. Install instructions are included too. I don't think there is a way to reload via the PC. The right zip should get everything working properly.
The multi user and guest account feature is not available on either of the two recent releases of Lollipop for the Z3v. I did some research and it appears this is the case, not only on other Verizon handsets like the Droid Turbo and the Galaxy S5 / S6, but a few other non-VZW devices as well. I'm not sure why it was removed but apparently it's just hidden. It can be enabled and I followed the instructions for doing this for the various other devices and can report that it works for our Z3v (see attached screenshots).
I've kind of cleaned up the instructions and put them below. Usual disclaimer - I'm not responsible for anything that may happen to you or your cat if you choose to do the following. You DO need root access to edit and write to the system file.
** To be safe, please make a backup of your phone and/or a copy of the build.prop file that you are going to edit.
Get ES File Explorer. Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)
With ES File Explorer, go to device/system/ and find the file: build.prop
Choose to edit it with ES Note Editor.
Scroll to the end of the file and type in the following:
fw.max_users=5
fw.show_multiuserui=1
Save the file.
I'm not sure if the next step is required but it was in half the instructions I saw, and I did it myself: Click and hold the file, go to Properties, and then change the permissions to Read, Write & Execute. [all three]
Reboot your phone.
When you're up and running, access multi user mode by pulling down your notification shade and then clicking on your user icon at the top right corner.
Notes so far:
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Therefore, an app such as Movie Creator can and will create a "highlight" movie that is composed from photos that are saved on the external SD Card. Just keep this in mind as far as privacy.
There is a per user option that lets you decide whether or not the additional users can use the phone and access the text messages. If you disable this ability, while they cannot open the phone app to make a call, the CAN receive an incoming call.
You can find out more about the nuances of additional users with your Google Fu.
Enjoy!
Wow! Great work!
AddictedToGlass said:
Wow! Great work!
Click to expand...
Click to collapse
Thanks! I really wanted this feature and it seemed like not many people care too much about it. It's my way of circumventing the awful permissions control we currently have in Android. That is, there are apps I want to use but refuse to install because of their overreaching permission requirements (contacts, etc) and so I can now create a second user with a new "dummy" Gmail account that has no sensitive information and install these apps without worrying.
By the way, something neat I figured out about this. Additional user accounts are not allowed to side load apps (the toggle to install from unknown sources is grayed out). I figured out that if the main user / owner restores an app through Titanium Backup, any other currently existing user will have it installed for some reason. I don't know why this happens but it's a neat glitch that gets you around that restriction.
Well I think most people simply don't let others touch their phones and so don't have a use for multiple user accounts. I find that my phone, as big as the screen is, is becoming more and more of a computer / tablet replacement. I like the idea of a multiuser functionality, but mostly to hide my own stuff. I'll silk never let anyone else touch my phone!
The use for multi-user that I've seen that makes the most sense is people with children. They will create a user profile for the child so they can't get into any of the parent's stuff or settings. That or the guest profile which will let them do whatever the heck they want without screwing up the phone.
Aside from that I have read that devs find the feature very useful for testing. Heck, that's not a bad idea to install and test apps, in general.
uh oh.
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
rpelljr said:
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
Click to expand...
Click to collapse
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Tigerhoods said:
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Click to expand...
Click to collapse
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
rpelljr said:
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
Click to expand...
Click to collapse
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
it is guys if done right your system needs to be switched to r/w then go back to r/o after modifying the build prop if you modify in r/o you will get bootloop to a hard brick it depends.
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
Well I kinda fixed it. I went and bought a HTC M9. Lol but not yet, I'm still working on it. I have found scripts to run, even a specific build.prop fix to push, but I have windows 10 and couldn't get adb to find the device. Plus I'm a little rusty. So I broke out my old windows 7 laptop I have used just for rooting an modding phones and tablets. I did get adb and fastboot to find it once. Then some reason lost it. I didn't have it ready to go. But I'm almost 100 percent sure I can get it. Just need to play around with it a little bit more. Having trouble with drivers etc. I will let you know when I have it.
And didn't really hurt my feelings getting the phone I truly want. I never had problems with HTC since I was flashing roms on my old window phones. I just want my pictures I cannot replace.
"Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)"
Alas- I am not rooted, and therefore can not enable "Root Explorer" option. Unless someone has some other suggestions- I think I can't do this unless I'm rooted.
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
AddictedToGlass said:
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
Click to expand...
Click to collapse
a backup usually means going into your twrp and hit the back up button and make a copy of your system including data and all that. This is mandatory before messing with the build prop. If you want Pm me your build prop and I will send it back to you. With multi user enabled.
Yup, I know what a back-up is and how to do it, and I know it's a must before messing with the build.prop. I just really thought I had done it recently...
-and I had! But I forgot that a few days ago I bought myself a Christmas present; a 200 Gb micro SD, and copied most of the contents to the new card from my old one. I chose not to copy the backup because I had planned to make some changes and create a more recent backup. Never happened though because I got side tracked loading music and such. Lol!
So I'm all back together, but would still like to play with this feature. So I'm going to give it another shot.
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Click to expand...
Click to collapse
Perhaps the wrong thread but: enabled multi user on a Cube T8 only to find that guest and other user can access INTERNAL sd but not external sd. I'd rather have it the other way round. So the kids (other users) can use the whole of 32 GB sd card rather than me having to share the small internal sd with them.
Any ideas how to fix this? Phablet is not rooted btw.
got bootloop..... but i'm safe as i've backup.... through recovery..
I've inserted two lines and fell in bootloop
Thanks bro.. working....!!!! but second step is not needed...