Related
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.
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).
Wifi and OTA updates were working fine before I rooted my kids' Nabi 2. I never tried an OTA update until after I rooted them, which doesn't work (I tried 2.1 since it said it was available). I followed the directions at http://forum.xda-developers.com/showthread.php?t=2041224 and it worked great to restore to stock 1.9.12, but wifi doesn't work now (mine could have been 1.9.37 originally). I tried the "wifi fix" mentioned, but there are still no wifi networks displayed like there were earlier today. I do not have a micro SD card to install the updates from, as mentioned in the replies. If I were to buy one, can I just put the OTA updates from http://forum.xda-developers.com/wiki/Fuhu_nabi_2 on it, and install from it somehow?
I tried to copy fuhu_nabi2_138139_1937_ota.zip to the device and install through the recovery kernel, but got an "assert failed" error. Any ideas as to what can be done to at least update this to 1.9.37, or maybe do a "stock install" of 1.9.37 instead of 1.9.12 so I have a better chance of wifi working? Please be specific as to what I need to try and in what order...some of the tools I tried seem to be inconsistent in results (Nabi Lab was latest I used). I am comfortable using what t499user has to go back to 1.9.12, I just wish I could use the same method to go to something newer...
I had the wifi problem this past spring. I backed up all my apps and data then flashed back to stock with NabiLab. Re-rooted and all was fine again.
You should also be able to use TWRP to flash back to stock. See TWRP thread http://forum.xda-developers.com/showthread.php?t=2074501
Some more info that may help http://forum.xda-developers.com/showthread.php?t=2248495
This experience is only my second time with TWRP and updating the Nabi. I've previously tried reverting to the backup in the "stockunrooted" folder, which is where I think the original was. I now recall that this had been updated to 2.0 using OTA before it was rooted.
Using TWRP, I tried reverting back to stockunrooted just now. Wifi works again, but OTA still does not (2.1 downloaded and seemed to install quicker, but upon reboot all I saw was "an error installing" message and it went directly to TWRP (where I just rebooted and it went to the Nabi screen). I am not sure what else to try. There is also an "oem" folder available for restore in TWRP, but that is the one created using t499user's process to go to 1.9.12. I initially used t499user's tutorial because I thought maybe something was wrong with the stockunrooted backup.
I have a few questions. Is updating TWRP to the latest version important? If yes, how do I do that (I've seen http://forum.xda-developers.com/showthread.php?t=2074501 before, but still not sure how to download/install 2.6.1.0)? If this has been reverted to "stock" and OTA updates still don't work, how do I apply them manually (from http://forum.xda-developers.com/wiki/Fuhu_nabi_2)?
I just noticed that the "stockunrooted" backup has things that aren't stock. Internal Storage has an Android folder with com.google.apps subfolders, etc. I am back to the original problem, and that is going to "stock" (something other than 1.9.12).
Cool, I figured out how to install 205to210.zip (TWRP 2.3.3.0)...For anyone interested, I copied the zip to Nabi/Internal Storage/TWRP, booted while holding +, pressed - to 'recovery kernel,' pressed + to choose it, then chose install. There is one more update I tried (2127stock.zip), but I get a flash error and it did not install. Considering (so far) I cannot get back to "stock unrooted" and use OTA updates, does anyone know how I can install this?
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
brentford said:
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
Click to expand...
Click to collapse
Yes its probably wise to update to TWRP 2.6.1.0. Get the file
Download
Follow "Method 3" here
http://forum.xda-developers.com/showthread.php?t=2074501&highlight=nabi
As for getting a stock image. You were using the zips here http://forum.xda-developers.com/wiki/Fuhu_nabi_2
You dont "Install" those zips. You need to extract the contents. boot.win, system.win, etc. and put them in the TWRP folder.(TWRP/BACKUPS/XXXXXX/folder)
Make a folder called 2127 put the filed in there. Then "Restore in TWRP. Then you should have a stock system. Same goes for 1937stock.zip 205stock.zip
If you have questions ask away.
Thank you all! I think I am getting it. Since I am reading (and had first hand experience) that Google Play isn't working very well with 2.1.27, I will go back to 2.05. That should keep the kids happy. I will let you know if I have more questions.
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
brentford said:
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
Click to expand...
Click to collapse
Google play won't work with 2.1.27 unless you delete some apps from /system/vendor/apps before installing gapps
As long as you have the bootloader(with the 4 options boot normal, fastboot, recovery kernel, forced recovery) and working USB port there are always options.
So is ADB not working in TWRP or in Android or both? It's probably best to copy boot.emmc.win, data.ext4.win and restore those too since you have done so much stuff. Boot contains you kernel, and data the apps. You will be back to a stock tablet with no game saves or anything so make sure you got off the tablet what you needed
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
brentford said:
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
Click to expand...
Click to collapse
Before browsing with TWRP file manager you need to go to the "Mount" tab, put an X in system. Then go to file manager.
Probably have to remove around ~50MB, maybe a bit less. Lots of people choose Wings, but obviously Wings is something some kids love. Really depends on the user.
When you flash stock, it often reset USB debugging to off in Android settings, if you flashed data too.
USB debugging is still on. Do you know anything about whether or not gapps has any problems with rooted Nabi 2.1? You have been a great help!
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
brentford said:
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
Click to expand...
Click to collapse
The only problem gapps has is there isn't enough room for it with a stock 2.1. You have to remove something.
Mount everything in TWRP. Go to file manager. /data/media is internal storage. You will find your files. Copy them back to /system/vendor/apps. Might have to set permissions.
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
brentford said:
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
Click to expand...
Click to collapse
You might be out of space again depending on what you copied back and why the icons are blank. Check with
adb shell df (in Android)
Look at system and see how much space you have free.
Or it could be permissions. You can use a file manager in Android such as ES File Explorer or Astro. You need to go to the setting in the app and enable whatever option they have to browse and remount "system" as read/write that will require root and should prompt you to accept. Then you can browse to the directory. You could also use TWRP File manager the same as when you copied files. There is a permissions tab.
I think the permission you want is 0644(for TWRP), or wr-r--r--(for ES). Same thing just different nomenclature.
Similar issue as OP
Hi guys, I have done pretty much the same thing as the OP. The wireless will not turn on or find any networks. I have tried reverse tethering, but have lost root and pretty much any other way to get internet to the nabi 2, so I can update from version 1.9.12. The big problem is I cannot use TWRP because when I boot into recovery and try to get there I get the dead green android guy with the exclamation point error and it hangs there until a hard restart. Any ideas on how to fix this. Is there a way to push an update through the SD card? Any ideas and suggestions would be greatly appreciated. I have already spent more time than I would have liked trying to fix this.
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
aicjofs said:
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
Click to expand...
Click to collapse
Well I swear I have tired this, but decided to give it another go and it worked! Got TWRP up and running then ran NabiLab to return to stock 1.9.37. Wireless is working and updating to 2.1 and then will give root a shot and GApps. Thanks for getting back on track!
Bought a quad core Onda clone tablet (AOC Leopard hardware designation) from China - yes i know, i know, it was a bad idea but the spec was so good i thought it might get me into the tablet fun everyone seems to be having - i repair em but dont really have a lot of knowledge on the software side of things for hacking these things - although after the last two weeks of hacking the thing I am becoming a bit of an expert.
Here is a link to the same one albeit with a different manufacturer made up name - as you can see the spec (Quad core, 1Gb ram, 16Gb storage and hdmi) is amazing for the price of £42 I won it for at the auction so it was more of a plaything to learn on than a big purchase for me.
I am pretty good with Linux so be as technical as you need to be.
Basically the thing buggered up when my mate plugged in the wrong power supply and thankfully it still booted albeit with the OS or bootloader I suspect corrupted.
It is stuck on the Onda loading screen leading to my assumption that it is in a boot loop.
I have spent the last two weeks trying to find drivers for windows , a compatible os and a way to get it restored - ahh the perils of buying chinese!!!
Problem I have now is that the sdcard slot is completely snafu due to my careless and fat fingered fiddling and to be honest a slight bit of temper with the thing after two weeks of head scratching - do you blame me!!!
I have managed to get it recognised by windows by trying driver after driver on the internet until i found one that worked - the perils of buying a no name chinese clone are myriad.
Without the sdcard slot the problem is now worse as i have to use the usb slot connected to the pc and sideload the apps and os but thankfully that is sorted now - Have installed the Android development Bridge - SDK toolkit and adb devices linux command was coming up with no devices but i figured it out with a lot of fiddling with the android ini file in the user profile and the dev id in system device drivers in case anyone else is trying to figure that one out - its a very obscure fix but it works.
So all is swoopy and seemed to be going well until i got the same error i was getting with the sdcard when i tried to sideload a new os - sideloads the new "update.zip" perfectly and even passes the file verification but crashes out with the fatal "unexpected error" have tried Onda official zips and Cyanogenmod flashes but i reckon the problem is because the system is not rooted and doesnt have the cyanogen bootloader installed even though i rooted it with supersu before it went up the khyber so in essence I need root to get the new os on and yes "shell su" command doesnt work as the device is only in sideload mode - only option on the 3e emergency recovery mode on the tablet is either reload from usb , sideload from usb as well as the usual clear cache, reset system and clear user data.
I should add that the hardware isnt snafu as I can see my old files and the operating system on the flash drive when i use recovery mode (power button / up volume combo) - load from sdcard option when i choose browse to sdcard - Linux always mounts the onboard flash as sdcard and an external sdcard as ext-sdcard on a tablet or smartphone - so i can select sdcard and then browse the main flash storage where i can see all my movies , development programs apk's and the Linux system itself but obviously cannot do anything else other than browse the thing for a ZIP to upload onto the \temp which is then extracted by the Emegency recovery environment - checked for verification - it then seems to prepare to install but fails with as you say the usual "unknown error" which i only assume is because I dont have root i cant go any further.
Oneclick root doesnt work.
Also tried the pad product tool v1.05 for direct flash to the tablet using Ainol Novo 10 Captain firmware and it wont even work.
Flashboot adb doesnt work.
Rockchip android tool doesnt work.
Kinda running out of ideas now!!!
Ok ok so what i need to know is basically - Does anyone know if it is possible to root and install a new bootloader from the usb sideloader - ie Adb sideload "filename".
And yes i have tried the pinhole reset button on the back of the tablet and the wipe system and reload option in the recovery menu so hopefully there are some good techies on here who know how to su the bootloader and reload the os or if it is even possible!!!
Hi everyone,
I'm trying to fix my mistake since several days but no luck.
Few days ago I rooted and updated my phone to version VIBEUI_V1.5_1423_10_ST_K910 with Gapps. Everything went fine but then while I was cleaning up the phone from useless apps I made a huge mistake by unistalling a file or apk called Idea….something(can’t remember the entire name)! I thought it was a theme file as the name was very similar to another real one. After that a neverending popup started to appear and I decide to restart the phone. Never got it back! It remains stuck on Lenovo log. I’m able to get into stock recovery where on every test or sd card format it says sdcard not found. Same when I connect it on the pc, the autorun popup only, no storage.
Seems like the sdcard is not recognized anymore so I can’t even launch an sd update.
I’m pretty new on Android systems so I’m about to give up, I don’t really know what to do anymore.
I’m beg you for some help. Any advice will be more than welcome.
Thanks
cianomanera said:
Hi everyone,
I'm trying to fix my mistake since several days but no luck.
Few days ago I rooted and updated my phone to version VIBEUI_V1.5_1423_10_ST_K910 with Gapps. Everything went fine but then while I was cleaning up the phone from useless apps I made a huge mistake by unistalling a file or apk called Idea….something(can’t remember the entire name)! I thought it was a theme file as the name was very similar to another real one. After that a neverending popup started to appear and I decide to restart the phone. Never got it back! It remains stuck on Lenovo log. I’m able to get into stock recovery where on every test or sd card format it says sdcard not found. Same when I connect it on the pc, the autorun popup only, no storage.
Seems like the sdcard is not recognized anymore so I can’t even launch an sd update.
I’m pretty new on Android systems so I’m about to give up, I don’t really know what to do anymore.
I’m beg you for some help. Any advice will be more than welcome.
Thanks
Click to expand...
Click to collapse
Hi guys, is there any way to get access into the phone root by using some tool?
I can't see the sdcard and I can't boot the phone with fastboot.
Please help.
Unfortunately I didn't get many answers but fortunately I solved the problem so I believe it would be nice to share with whom may need it:
here you have the steps I followed:
- buy a OTG cable
- Buy a USB stick 2-4GB
- Format USB stick with FAT (!)
- Put sdfuse directory on it and a K910 .qsb image inside the directory
- Plug stick via OTG in the phone
- start phone with Vol- & Power
- Choose point 4 - SD Update from the Lenovo recovery Menu
Phone will show this picture then:
Attachment 2826922
- Hit "start"
- Wait
- Be Happy
- Buy me a cigar (Partagas Series D No.4 preferred)
That's it!
Cheers