[Q] Help with Cybernav Mini tablet. Cant flash firmware - Android Q&A, Help & Troubleshooting

Help needed. I turned off my chinese tablet (Cybernav Mini) and the next time I turned in on it showed: "Sorry! The process com.android.phone has stopped unexpectedly... Force Close. ". It shows up again, one after another. I press Force Close and then quickly another pops up, showing the same or a similar message.
I can't use the tablet as those messages block any other function of the tablet, i can turn it off by long press the power button or pressing the reset button but when it reboots, it happens all over again. Even after draining the battery for few days, when i boot it again, same problem happens. The problem is after i click on Force Close, it gives me another error too fast and i can't do anything like installing or use any app.
I contacted support and they sent me the last firmware for the device (YFPI08), but when I put the folder it in the external microSD card and power it on, it wont read it and instead it will go through the normal boot process and the Sorry! force close problem comes back again. I can't find a combination of pressing the two only hardware buttons it's got that could take me into some sort of rescue boot either.
I tried fastboot from my computer but it doesnt recognize the connected tablet.
I can't find any other way, as I am not too familiar with Android, and every solution seems to be very device specific oriented. So please, if there is a solution, I would appreciate your help.
Cheers

try rom
if u look on to my opinoin try out any custom rom

Shrihari007 said:
if u look on to my opinoin try out any custom rom
Click to expand...
Click to collapse
I doubt there is any custom rom for that tablet, nevertheless, if you know where I can find one, and how to do it, please, link me to the right place.
Also it is worth to mention that when this problem happened, I was playing with the Z4root app, so there is a possibility that I accidentally messed up with the rooting of the tablet. Would that make sense?
Cheers

45 reads no reply, someone must have at lest a simple suggestion, like bin the tablet or something, but I was told that here I was going to get some help in this forum. No one?
cheers

(Cybernav Mini II - PW08)
There are some firmware files on yinlips dot com website.
·YDPG18 Upgrade
· YDPG18 upgrade tool LiveSuit_v20
· A10 android2.3 (resistance screen)v4.24-20120531
· A10 Android4.0(resistance screen)-20120726
Can these be used on the cybernav mini 2?
The download is pretty slow, but have anyone tried them?

Me too..
Hello.. Do you still have this problem?. Even I had this problem.. They sent me the original firmware and I flashed it with my MMC card and then i inserted the card to the Cybernav Mini and pressed the reset button.. it flashed to the original firmware and now all fine.. do let me know if you want the original firmware for Cybernav Mini GPS tablet. :good:
regards

(Cybernav Mini II - PW08)
craigsoup said:
There are some firmware files on yinlips dot com website.
·YDPG18 Upgrade
· YDPG18 upgrade tool LiveSuit_v20
· A10 android2.3 (resistance screen)v4.24-20120531
· A10 Android4.0(resistance screen)-20120726
Can these be used on the cybernav mini 2?
The download is pretty slow, but have anyone tried them?
Click to expand...
Click to collapse
OK. Tested with the device using PhoenixCard img writer. The tablet boots up, but in safe-mode.
WIFI not working. But everything else seems to work.
I'm guessing the wifi chip in this device (PW08) isn't the same as in the YDPG18, though almost everything else is, except it's only a gps device.
Didn't test if the gps works ... still testing to see if there are some ics firmwares working for the device.
Dracotek did send me a link to the stock firmware, downloadable from 4shared - ask them for it I guess.
Link had this image in it:
pw08_20120428.img
Android 2.3.4, radioversion 2.0, kernel #r1-91-g1cd40ad, build #r1-151-g46cf014
persist.sys.language=zh - so default language is chinese unfortunately
---------- Post added at 08:10 PM ---------- Previous post was at 07:46 PM ----------
VX580WH_Android4.0.3-1.0
Way more chinese then the ydpg18 one. Also no wifi
But this rom dons't put ics in safe mode...
Argh. Anyone able to run ICS with wifi on the Cybernav Mini 2 device?

(Cybernav Mini II - PW08)
Another china tablet firmware tested without success.
Teclast_P76-Android4.0.1-AF0E.zip
ICS loads up fine, but super slow response and no support for the PW08 features.

(Cybernav Mini II - PW08)
Sorry for spamming.
Same device: http://www.coscod.com/wi-fi-gps-5-inch-touchscreen-gps-navigator/
Firmware download at their site too: http://www.coscod.com/download/os/pw08_FLASH_20120428.rar
(version 2.3.4 gb)
Please someone do ICS. Clockworkmod recovery (Needs to be touch, device only has power-button and hard reset button)

(Cybernav Mini II - PW08)
Very cool firmware, tested
TAB224 GoTab Velocity 7" Tablet - Firmware TAB224_A404.img
- wifi and gps not supported I guess when used on PW08.
Resolution is 800x480 / but text seems a bit small possibly because of PW08 is only 5".
Clean and simple, touch works and graphics is smooth and fast. Sound works.
-It is made by Yarvik.
Hope this can help - this is from stock PW08 firmware GB 2.3.4
# lsmod
ar6000 455564 0 - Live 0xbf101000
kt080x 5109 0 - Live 0xbf0fa000
sun4i_gps_ctrl 1157 1 - Live 0xbf0f4000
rtl8150 8232 0 - Live 0xbf0ec000
asix 15585 0 - Live 0xbf0e2000
usbnet 12534 1 asix, Live 0xbf0d8000
sun4i_csi0 24387 0 - Live 0xbf0cc000
videobuf_dma_contig 2934 1 sun4i_csi0, Live 0xbf0c6000
mali 110951 2 - Live 0xbf09c000
ump 22324 9 mali, Live 0xbf08f000
bma250 5268 0 - Live 0xbf082000
sun4i_keyboard 1971 0 - Live 0xbf07c000
sitronix_ts 18292 0 - Live 0xbf071000
goodix_gt82x 15739 0 - Live 0xbf067000
ft5x_ts 7608 0 - Live 0xbf060000
sun4i_ts 14702 0 - Live 0xbf056000
hdmi 14243 0 - Live 0xbf04c000
lcd 2559 0 - Live 0xbf046000
disp 218083 9 hdmi,lcd, Live 0xbf000000
cat /system/usr/keylayout/sun4i-keyboard.kl
key 102 HOME WAKE
key 1 BACK WAKE
key 139 MENU WAKE_DROPPED
key 115 VOLUME_UP
key 114 VOLUME_DOWN
Click to expand...
Click to collapse

(Cybernav Mini II - PW08)
xTAB-50 http://www.wayteq.eu/en/xtab50gps
(suppost to be 5-point capasitive screen)
The firmware on the website works with Cybernav Mini II.
xTAB-50.img
Android 2.3.4
kernel #r1-94-gfe1ef8f
build #r1-160-g863ed23

(Cybernav Mini II - PW08)
Bumping for the last time
Head over to 'hungariandroid' and register at the forums to download ICS compatible with PW08.
xTAB-50 GPS Ice Cream Sandwich (version RC2.1)
Thanks Wayteq
A few pics with the final result

craigsoup said:
Bumping for the last time
Thanks Wayteq
Click to expand...
Click to collapse
No... keep going Please!
I've just launched into all this as I mucked my CyberNav. Thanks to your research (and a whole lot of googling on my own), I've now got serveral ROMs to chose from. Feeling a lot better now, actually.
Just wanted to say thanks,
David...

craigsoup said:
OK. Tested with the device using PhoenixCard img writer....
Click to expand...
Click to collapse
A question about this...
I use PhoenixCard on a Win7 computer to "burn" an image to inserted sdcard. Mounting the result shows a "dynamic" folder full of 512 byte bin files.
So, I put said card in the CyberNav and turn it on. It boots normally and, after a short while, says "safe to remove sdcard." No rom update.
Am I doing anything wrong here?
Now, I'm attempting this because I mucked the internal sdcard partitions and it is entirely possible that said mucking is stopping the external sdcard from being read on boot. But, I just wanted to verify the proceedure I'm following before I start down the partition editing route.
Any suggestions?
David...

Your device should boot up showing a progress-bar if you insert a working upgrade sdcard.
When finished screen will say CARD OK and the device will shut down.
Remove the sdcard before booting up again.
If you do not remove the upgrade card the device will start to upgrade itself over again.
The sdcard indeed show a folder called dynamic with 100+ small files.
The upgrade files are in a hidden (to windows anyways) partition.
What firmware are you trying to flash?
---------- Post added at 05:47 PM ---------- Previous post was at 05:34 PM ----------
Kinda of an important sidenote:
Cybernav Mini: CPU: IMAPX200 ARM11 800MHz
Cybernav Mini II: CPU: 1.2ghz Cortex A8 ARM Core
OP was using Cybernav Mini
I have Cybernav Mini II and tested firmware for that device.

craigsoup said:
Your device should boot up showing a progress-bar if you insert a working upgrade sdcard.
When finished screen will say CARD OK and the device will shut down.
Remove the sdcard before booting up again.
If you do not remove the upgrade card the device will start to upgrade itself over again.
The sdcard indeed show a folder called dynamic with 100+ small files.
The upgrade files are in a hidden (to windows anyways) partition.
What firmware are you trying to flash?
---------- Post added at 05:47 PM ---------- Previous post was at 05:34 PM ----------
Kinda of an important sidenote:
Cybernav Mini: CPU: IMAPX200 ARM11 800MHz
Cybernav Mini II: CPU: 1.2ghz Cortex A8 ARM Core
OP was using Cybernav Mini
I have Cybernav Mini II and tested firmware for that device.
Click to expand...
Click to collapse
Ahh, CyberNav Mini, not Mini II. I tried the pw08_20120428 and xTAB-50 images.
So, now I'm left wondering... is the failure to load the rom because the bootloader is smart enough to recognise an incorrect rom or is it dumb enough to give up on a bad partition? I'm still thinking it's the partitions.
But, I guess now I'm still looking for a working rom for the thing too. I may not need it if I can fix the partition problem without causing further damage. But, it would be nice to have that backup. Thanks for pointing out my error above... I missed the Mini to Mini II transition.
I'm just trying to get the CyberNav working again... not really interested in a latest/greatest upgrade as it did exactly what I wanted very well. I mounted it on the handlebar of my dirtbike with custom maps. Worked great, right up until I downloaded the latest track and left it there attached to my computer... that evening I went to make an Ubuntu USB startup disk... stupid, stupid, stupid...
Then again, my new tablet should arrive today or Tuesday... 10" and, yes, I'm going to mount that on my dirtbike too Thus is the benefit of using cheap Chinese tablets... If I don't fix my little CyberNav, no real tears. It would be nice, and I'm looking at it as a learning opportunity, but if it bricks in the end... such is life, only $100. Even the 10" is still in the disposable price range.
Thanks for confirming that I was doing the PhoenixCard part correctly - that's good to know,
David...

Re: Cybernav Mini (yfpi08)
http://club.dx.com/forums/ 5" (thread has a link with firmware)
http://club.dx.com/forums/ 7"
Perhaps it is possible to get a working firmware from Freeway AX
This device looks like a match. Just replace the boot-logo with something you like (if you can stand to read some polish)
Put the firmware files in a folder called 'yfpi08' on the sdcard.
It looks like the firmwares are all android 2.2 - ICS on a 800mhz device is perhaps too much to ask?
saluzinside Thursday, September 13, 2012 4:41 AM
I contacted the producer (YF) and they gave me the latest revision of the firmare:
FRF85B.yf.v2.2-104-g1b33231
They also told me that the YFPI08 is now out of production and this will be the last firmware revision.
http://dl.dropbox.com/u/18965091/YFPI08_yf.v2.2-104.zip
Just unpack the zip in your SD, make sure the "YFPI08" folder is present.
If you don't want to change the start image, remove "logo.bmp".
With this firmware my YFPI08 runs smooth and fast and all seems to work fine.
Bye
Click to expand...
Click to collapse
Thanks saluzinside

craigsoup said:
Re: Cybernav Mini (yfpi08)
... This device looks like a match. Just replace the boot-logo with something you like (if you can stand to read some polish)
Put the firmware files in a folder called 'yfpi08' on the sdcard.
It looks like the firmwares are all android 2.2 - ICS on a 800mhz device is perhaps too much to ask?
Click to expand...
Click to collapse
Yes, I've already grabbed the yfpi08 image (3 versions actually, no idea what's different between them yet) but got the impression they were for the 7" rather than the 5". Also, it could explain why I'm reading conflicting methods for the update: Mini = put img file on sdcard (in folder ??), Mini 2 = PhoenixCard. This Android fragmentation is crazy... so many different versions and methods to deal with each. Still trying to get my head wrapped around that.
> ...if you can stand to read some polish...
Ah... I'm Canadian... Japanese wife, Chinese tablet... we don't care I was a little surprised after the first factory reset and having Android come up entirely in Chinese... took a few minutes to find the language options It's all part of the fun,
David...
More: now YFPI08_yf.v2.2-104.zip from the above clubdx forums looks very interesting. My CyberNav lists 2.2-103-gb456292 as the OS version. An UPGRADE 2.2-103 to 2.2-104. Thanks for the link. Now I have 4 versions of that yfpi08 rom to try.

well, this is looking better.
I just did the system img (left all the others out, for now) and it actually did the update as expected. So, yes, the bootloader can read the sdcard if there's something useful on it.
Sadly, after switching the system back into English, it still can't access the internal sdcard.
So, I did it again with all the the files (nice background image by the way) and that updated the bootloader. With the same result. It appears that reverting to another ROM, factory default or otherwise, does not fix my partition errors. But, the good news is that I now most definitely have a factory ROM to revert to if I need it.
So long as I don't brick the device, I'm good. I can be a little more aggressive on the partition editing... just need to make sure i don't wipe out that bootloader and I should be okay.
I did notice that the other image from the links above has a "force.bin" file included. I also noticed that my second update didn't bother doing the system.img file. I suspect said 'force.bin' file forces this? No google hits on that at all... might try it one day if all else fails.
I think I'll start a new thread on partition editing rather than hijacking this one. At this point, I'd say the thread is solved, thanks to craigsoup, for both for the Mini and Mini-2. Thanks again,
David...

Related

Help All changes lost after reboot even after flashing ROM

Here's the victim, I believe it's a Wopad V7+ ..
7" /Capacitive 5 point Touch Screen/ Android 2.3 / HDMI /
vimicro VC882 ARM Cortex-A8 1GHz
It seems to be AKA: HAIPAD M8 /Zixoon V78c / McPad V7+ /
MOMO 1000 (BUT Resistive touchscreen)
I bought it at dealextreme. sku104916
You can see it at wopadusa.com store
I rooted it , confirmed via rootcheck, modified the build.prop to make it appear as a nexus s. All went good for many days...
I realised a few days ago that my tablet was unable to PERMANENTLY install an apps... or install a new one... Or change internal parameters or flash it(wallpaper won't be different after flashing)
In fact the weirder part is that the change appear as being applied but when it reboot, it returns to the same state (uninstalled apps still appear as installed) . The tablet indicate it's low on disk space , I uninstalled most application I could but it won't go away since the apps still appear as installed after a reboot.
I tried to flash it. The apps to flash it via Win7 confirmed the flash was successful... but I didn't notice any change. I flashed it with Zixoon and wopadusa and it didn't change anything. I tried different apps to flash it including those: chinadigitalcomm.com/flashtool-packtool-for-m8-incl-latest-1028-firmware-v3-0-update-23-11-2011-t11091
I'm not sure when the problem appeared... I believe it's after I followed the following procedure: ClockworkMod Recovery 5.0.2.6 unofficial port v1.0 alpha by mikeNG chinadigitalcomm.com/post23360. .
Because when i tried to enter in recovery mode the screen became ''fuzzy'' unreadable... but I confirm i was able to select the menu at that moment. Maybe i did something wrong. And I dont' know how to undo the change.
I believe it may be related to read/write/chown permission via adb... I dont' know.
I may have to correct via adb shell chmod ?SOMETHING? /system / at different place of the filesystem but I don't know what and where to look for...
I'm not very teck savvy. But I have good will. Please help me.
I don't want to send the tablet back to china. I use it to study. I really like android.
BONUS: By any chance, can someone tell me where to buy the power adapter for that tablet ? It doesn't recharge via USB and my actual charger have a shortcut and this adapter have a very RARE tiny pin connector, slightly larger than some nokia. it's 5v 2amps.
English isn't my first language but I believe I amde myself understandable. I'll clarify anything i'm able to.
Thanks.
I can't post outside links in my message as per forum rules. After approximately eight posts, I'll be able to post outside links. Thanks for understanding!

[Q] REVERT TO 4.0.3 (pre R5)

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

[Q] Development for Tizzbird N1 ?

Hi! So I'm wondering if anyone know if there is\have been any development for
the Tizzbird Stick N1 (M\G) ?
We have this Android-stick in stock at my store, but I'm not sure if I'm going to get it or not yet. Depends the development, as I'd really like to see the capabilities for it. I believe it's a lowbrand tho. so I might be out of luck.
Anyone know anything?
I searched the forums, and did a google search. Didnt find much.
regards,
Dag M.
Hi there!
I own one of those, and there are a handful of (german-speaking) people activly posting in this forum http://forum.tizzbird-tv.de/ about the Tizzbird N1. - The problem with that forum is that they heavily censor it - as soon as anyone posts info on how to "get in", or if someone asks uncomfortable questions - those posts gets deleted.
They sell it really cheap for 30€ (not all the time, but twice for one day @ redcoon) and although the Wifi-Chip (or the drivers for it) are really crappy, the media player part is really nice.
update: I've did a little research, and here is a little list of relevant links about the tizzbird n1:
==== Marketing Product Pages ====
http://valueplus.co.kr/english/product/product_player_n1.html
http://www.tizzbird.com/eng/index.php?mm_code=719&sm_code=755
http://tizzbird-tv.de/tizzbird/tizzbird-n1.html
==== Official Firmware ====
http://www.tizzbird.com/eng/index.php?mm_code=726&sm_code=727&board_search_head_word=stick+n1
http://download.tizzbird-tv.de/TizzBird_N1G_update_GMS_V3_20_13072719.tzbird
==== German Support Forum (posting info about root-access prohibited) ====
http://forum.tizzbird-tv.de/viewforum.php?f=11
==== GPL-Code for Tizzbird N10, N20 & N30 - but not for N1? ====
http://www.tizzbird.com/eng/index.php?mm_code=752&sm_code=754
==== Kernel Sources ? ====
http://www.cnx-software.com/2012/03...k-n1-android-ics-hdmiusb-dongle-media-player/
http://www.cnx-software.com/2012/07...hips-tcc8925-mini-pcs-cx-01-z900-tizzbird-n1/
https://github.com/cnxsoft/telechips-linux
Yeah, the pretend to be "community friendly and supportive" but once you actually start digging in, they get quite agressive and boot you out.
Anyways, I got a N1 a couple of days myself now (snagged it for 30 bucks at another RedCoon sale ) and I am surprised.
Got it pretty much only to tinker around with it and this thing suits more perfectly for that than I imagined.
Esp. that fact they used a simple SD card as "internal flash storage" - my guess is because a simple SD is cheaper than an actual eMMC flash chip, but it's so cool on so many levels for us.
I already found out how to replace the 4GB SD with a bigger one (have a 16GB in mine ATM).
I'll post some more details about it here later, got a few things I want to test and/or prepare first (thinking of some "easy to use cloning script"), but long story short:
You need to copy the bootloader to the very end (last few blocks) of the SD you want to use.
Once the BL is at the proper place it already boots from the new SD again, to be sure everything is as it's supposed to be one should apply an update via USB (I'm not 100% sure about a possible pointer to the BL that needs to be corrected, which the update does).
After that the partition information has to be edited to make the userdata partition larger and you're done.
thanks for the info HellcatDroid!
It would be great if you could elaborate on how to put the bootloader at the end of the sd-card.
Also I would love to get info how to get root into the stock firmware, that crippled down root-firmware that they allow to exist in the official tizzbird forum doesn't really satisfy my needs
I did it via a hex editor, but it should be doable with a few "dd" commands as well - that's one of the things I still want to try, find the propper dd params to copy the BL over.
If you dumped the original SD into a file using dd, at the very end of the image file you will find the bootloader and the very last block of the SD is a "header" telling the bootrom of the N1 a few things about it, so it can properly locate and load it.
So what you got to do is to copy those last ~230k from the image to the end of the new SD card.
As said, I'll try to write a small shell script that does it.
The rooting is even more easy (Stonecold would kill me if he'd read this, lol):
For when running on Linux (no can do on Windows, as Windows doesn't know the ext4 FS):
Since you got the SD in your PC anyways already, just mount partition 2 (e.g. if the SD is sdc on your PC, mount /dev/sdc2).
That is the partition where the Android system is sitting on.
Then just copy over the files needed for root to where they need to go, chown/chmod them properly, unmount and done
I used the "update-supersu.zip" I had for my Nexus7 to grab the required files.
But I'm planning to make a simple rooting script as well.
So if all goes as planned it'll come down to
- insert original SD
- run script 1
- insert new SD
- run script 2
- to root run script 3
brilliant! I would love to see those scripts
way easier than start tinkering with that stuff myself
One thing I wonder about - over at the official forum you said that a simple dd copy didn't work - is that if the target sd-card is bigger or also for an sd-card of equals size? because with equal size simple dd copy of the sd-card should still work, even if some things need so be exactly at the end.
Yup, just a dd didn't work because the new SD card was larger and the bootloader ended up being somewhere in the middle of the card instead of at the end.
While your thought of "dd to equal size cards" is totally correct, it might still fail due to the fact every card is not 100% exact same size counting down to last byte.
There ususally is a tiny size difference (a few bytes to kbytes) between cards, even if they are supposed to be same, so the bootloader might end up truncated or not exactely at the end.
If, however, the size of the cards is 100% the same, down to the last byte, then yes, a simple dd clone would work.
HellcatDroid said:
... There ususally is a tiny size difference (a few bytes to kbytes) between cards, even if they are supposed to be same, so the bootloader might end up truncated or not exactely at the end. ...
Click to expand...
Click to collapse
Oh! Didn't know that. I thought same marketing size means not the same size they write on the box, but at least the same size between those that are marketed with the same GB numbers on their stickers.
OK, here we go, I slapped together a few scripts for prepping a new (and larger) SD card to work in the N1 and while having the SD in the PC to aplly some root.
* hints at attachment of this post
The scripts might still have problems and not work on any Linux out there, but it's a start.
If there's more people interested and joining in on this I might continue but for now I got what I wanted - more storage and root.
Hi
I think I destroyed my MiniSC cand! The N1 is dead. I tried to insert the card in a linux and gparted did not see anything. What can I do?
thank you for your help
somade said:
Hi
I think I destroyed my MiniSC cand! The N1 is dead. I tried to insert the card in a linux and gparted did not see anything. What can I do?
thank you for your help
Click to expand...
Click to collapse
Could you post how you got there? what did you do to the sd-card that destroyed it?
Hi.
If you got a dump from a working state of the SD you can just dd it back onto the card.
If you don't, it can still be recovered but might need bit more work.
Two options:
find someone who gives you a dump of their card and use the write-card script from my above post to write it to your SD.
Problem with this: a working dump contains copyrighted code, like the bootloader, it technically it's "not OK" to share it
we come up with another script that only contains an "empty" image (i.e. only partitioning information) and that takes the bootloader and recovery from the official update and gets the card into a state that it boots into recovery and lets you install a working system using the official update from USB (option in the recovery menu)
Option 2 would be nicer, IMO.
I'll try to make up said script
Thank you for your immediate answer!.
Actually I dont know what has happened, maybe the sharp instrument I used to remove the plastic cover scratch it...But now when I put it in a card reader the led of the reader switch off and the card is heated!!!. And also when I put it in the N1 the blue led turns off!.
So I bought a new empty micro Sd .
Waiting for your script to partition the new card and then boot in recovery mode and install a firmware....
Because I am not expert to linux please give me a lot of details how to do this.
Thanks again!
HellcatDroid said:
we come up with another script that only contains an "empty" image (i.e. only partitioning information) and that takes the bootloader and recovery from the official update and gets the card into a state that it boots into recovery and lets you install a working system using the official update from USB (option in the recovery menu
Click to expand...
Click to collapse
Do you think the bootloader is even part of the offical updates? wouldn't it be "best practice" to leave the bootloader partition alone as long as possible (and normally firmware updates don't need to change the bootloader)
update: something else I've just found, those might be kernel sources for our Tizzbird N1:
http://www.cnx-software.com/2012/07...hips-tcc8925-mini-pcs-cx-01-z900-tizzbird-n1/
-->
https://github.com/cnxsoft/telechips-linux
Yep, the bootloader is in the update - at least in the 3.20 one.
And yes, usually the bootloader shouldn't be touched because that's usually the one thing that can "perma-brick" Android devices.
However, sometimes the manufacturer updates it (fixing bugs, adding functionality) - on my Nexus7 they updated the bootloader on pretty much every update and also Samsung updates their bootloaders every now and then (and every single update flashes the current one).
Last, not least, on the N1 the bootloader isn't on a partition but at unpartitioned space at the very last blocks of the SD (=> reason for a simple dd to a larger card not booting).
Ohyay at the possible kernel sources!
It'd be so cool if that's really sources able to build a kernel for the N1 with - I think we might be able to even get custom recovery (CWM and the likes) on the N1 if those sources work
OK, while trying to recreate a working SD card w/o using a dump of a working one I found out a few more things - some of them still need figuring out if we wanna do it properly.
There seem to be TWO bootloaders!
A stage1 bootloader of ~1kB size located at the third and second last block of the SD. If it's missing the N1 can't boot and it looks like ARM code (haven't tried to disassamble it yet), I assume the bootrom loads and executes that piece of code which in turn parses the header (see below) and load/starts the stage2 bootloader (the one also found in the FW update).
The very last block of the SD is a "header block" with some information beeing parsed either by the bootrom or (more likely) the stage1 bootloader.
The headerblock contains (among numerous other unkown data) the size of the ("stage2") bootloader (the one that then actually loads and boots the Linux kernel of the Android OS, this is also the one contained in the FW update) and the usable size of the SD card! (everything works fine though if the SD size is wrong and a proper FW update updates the header during writing of the bootloader and also sets the correct size).
Also, the headerblock has a checksum of which I have no clue on how it is generated.
All that is just educated guesses and might be totally off, but for now it looks like it's not too far off.
So, for now we can assume the following boot sequence:
Boot-ROM
-> loads stage1 bootloader from fixed position "SDsize - 3 blocks" (1 block = 512bytes)
stage1 bootloader at fixed position on SD
-> checks checksum of headerblock (?), gets size of stage2 bootloader from headerblock, locates stage2 bootloader based on it's size and loads/executes it
stage2 bootloader on variable position on SD
-> base initialisation of hardware
-> checks for recovery trigger (the red button on the remote control) and boots kernel from partition 6 if trigger present
-> boots kernel from partition 1 if recovery was not triggered
-> enters fastboot mode when booting the kernel fails
Kernel
-> loads base drivers and boots up the system
you're brilliant Hellcat!
And did you also find both bootloader stages inside the firmware updates?
Another question that came to my mind while reading your post (fastboot..)
Is there a way to use the Tizzbird as USB-slave? So to make use of adb and fastboot and such stuff? Okey adb could also be used via network I guess..
somade said:
Hi
I think I destroyed my MiniSC cand! The N1 is dead. I tried to insert the card in a linux and gparted did not see anything. What can I do?
thank you for your help
Click to expand...
Click to collapse
Somade, do you have a linux running on your pc? If no, download and get a knoppix running. and then contact me via pm. I have the original n1 image so no problem to recover the n1.
sebastian.heyn said:
Somade, do you have a linux running on your pc? If no, download and get a knoppix running. and then contact me via pm. I have the original n1 image so no problem to recover the n1.
Click to expand...
Click to collapse
Welcome to our rouge and non-censored Tizzbird N1 forum Sebastian!
I wonder if you found us here, if the German Tizzbird support also already knows about us
update: I just remembered, I've sent you the link as PM over in the official forums, thats how you landed here.
Sharing your sd-card image might be a copyright violation, and if you're profile name is strongly linked to you're real identity you should definitly be cautious with such things on public forums...
kaefert said:
And did you also find both bootloader stages inside the firmware updates?
Click to expand...
Click to collapse
Nope, unfortunately the stage1 bootloader is not in the update :-/
kaefert said:
Is there a way to use the Tizzbird as USB-slave? So to make use of adb and fastboot and such stuff? Okey adb could also be used via network I guess..
Click to expand...
Click to collapse
Yeah, it works, even officially XD
Go to the TizzBird settings -> "System Settings" -> "Advanced Settings"
It has an option "OTG Mode" there, set it to "Debug".
If you have your N1 connected to your PC via the micro-USB port (and hence your PC powering the N1!) you can use ADB and fastboot just as usual
I have not yet tried if that option is persistant, i.e. it survives a power loss.
When booting the kernel fails it should fall back to fastboot mode, so flashing a new kernel w/o pulling the SD should be possible - need to test this a bit more, though.
What works is, if you're rooted and and you fire the command "reboot bootloader" from a root shell, that gets you into fastboot mode no matter what (given you applied above mentioned setting first).
But needing a running system to get into fastboot mode kinda defeats the purpose of it - this aint Ouya which is a total fail when it comes to fastboot XD
---------- Post added at 09:26 AM ---------- Previous post was at 09:05 AM ----------
kaefert said:
I wonder if you found us here, if the German Tizzbird support also already knows about us
Click to expand...
Click to collapse
Eventually they will, I'd say.
And I'd love to see their faces when they do XD

[Q&A] [MOD] [root] [CHUWI] [Vi7]

Q&A for [MOD] [root] [CHUWI] [Vi7]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD] [root] [CHUWI] [Vi7]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
root chuwi vi7
casacristo said:
Try again from the beginning, you will be able to mount read/write system now...
ALSO VERY IMPORTANT, download the new attachment and use instead ...
Click to expand...
Click to collapse
I am trying too to root this Chuwi... With the 1st attachment, it was created a temp file in "0" space. With the new attachment, its created in tmp in sdcard1. Does this stay correct in my case? Thanks in advance.
Rom
Hi!
If possible please upload anywhere the original chuwi Vi7 rom.
Thanks!
Hi,
Yes, there is a 0 byte file created (that is what the touch command does)
This is so that custom recoveries can check for the presence of the file and then ´know´ the phablet is rooted.
Vi7 can not switch wify on
dear
i am VI7 seller
jsut sell out 2200 orders out
now our customer just do not switch the wify on
they need to brush teir tablet
but i just do not knwo how to brush it
would you give me a instrunction ?
Hi,
I just wanted to let you know that I made a similar rooting procedure and script for the Chuwi Vi7. I got good results using SuperSU instead of Kingoroot.
I posted it on this Github repository:
Code:
https://github.com/Pacien/vi7-root
thanks for your contribution, cleaner coding than mine
Just 2 observations...
1) you do not verify that remount worked
2) line 39
rm /system/bin/install-recovery.sh
you loose the original patch command in the file
should be instead:
mv /system/bin/install-recovery.sh /system/etc/install-recovery-2.sh
This way it will still be loaded.
Also ... why do you ask to install superSU on data when the script is installing it on system?
casacristo said:
thanks for your contribution, cleaner coding than mine
Just 2 observations...
Click to expand...
Click to collapse
Hi, thank you for you reply
casacristo said:
1) you do not verify that remount worked
Click to expand...
Click to collapse
Good point, I should really have put a check here! I'll correct that!
casacristo said:
2) line 39
rm /system/bin/install-recovery.sh
you loose the original patch command in the file
should be instead:
mv /system/bin/install-recovery.sh /system/etc/install-recovery-2.sh
This way it will still be loaded.
Click to expand...
Click to collapse
I actually do make a backup copy of this file on line 38, naming it `install-recovery.sh.bckp`.
I'll change the script to name it in the way you mentioned so that it will still be loaded.
casacristo said:
Also ... why do you ask to install superSU on data when the script is installing it on system?
Click to expand...
Click to collapse
In fact I did not have realized that the APKs put in `/system/app` would be automatically extracted x)
The format is
/system/app/appname/appname.apk
(used to be different in older android builds)
Now the next challenge is to unlock the bootloader so a custom recovery can be put together with a Vi7 specific fstab.recovery
Personally I will start once I get my hands on a Vi7 with a working touch screen
Serious Lee said:
In fact I did not have realized that the APKs put in `/system/app` would be automatically extracted x)
Click to expand...
Click to collapse
I registered on this site just to say a big THANK you for this.
I've never touched android devices before, and promptly bricked this tablet. your guide to reflashing it saved me.
One note that I had to do to get it to flash, was fastboot oem lock. It will not work unlocked. Also, it still took under 30 seconds to flash correctly for me, so having that as a check probably isn't valid for everyone.
Chuwi VI7 Gapps not present
Hi,
Recently i have bought a Chuwi Vi7 Tab from Aliexpress.
On making it on , i didn't found Gapps ,which is a basic app for mobile phones and Tab .
I tried multiple times of installing Gapps but its of no use.
Please help.
Subho
At 1st boot there are no Gapps, but - if you check the 'Update...' tab in Settings - you'll see there's an update firmware available. If you proceed to install the update, then you'll have the Play Store...
At least, that was my case.
mircea1380 said:
At 1st boot there are no Gapps, but - if you check the 'Update...' tab in Settings - you'll see there's an update firmware available. If you proceed to install the update, then you'll have the Play Store...
At least, that was my case.
Click to expand...
Click to collapse
Thanks for your reply.
Are you referring to the update which is there inside settings
Settings ---> About phone --> system update.
If it is the same , i already have tried but its showing me no new update available.
If you are referring of some other update then please specify.
Do you have the update stored in your TAB , in that case if you can upload the same ,
[email protected] said:
Thanks for your reply.
Are you referring to the update which is there inside settings
Settings ---> About phone --> system update.
Click to expand...
Click to collapse
Yes, I' m reffering to that one.
I'll specify the version I installed the moment I arrive home...
The current version I have on my Vi7 is:
CW-Vi7-20150724-1900
Quick question: how many partitions and what size each of them has?
On mine there's only one partition - Internal storage - with some 3.6Gb (after installing a few GPS apps only 1.5Gb free).
I'm pretty intrigued as my other tablet - a Pipo S1 Pro - with similar features has two partitions: a 2Gb Internal storage (on which apps are installed) and a 4.5Gb NAND flash (at my discretion).
Sent from my X8 using Tapatalk
mircea1380 said:
The current version I have on my Vi7 is:
CW-Vi7-20150724-1900
Quick question: how many partitions and what size each of them has?
On mine there's only one partition - Internal storage - with some 3.6Gb (after installing a few GPS apps only 1.5Gb free).
I'm pretty intrigued as my other tablet - a Pipo S1 Pro - with similar features has two partitions: a 2Gb Internal storage (on which apps are installed) and a 4.5Gb NAND flash (at my discretion).
Sent from my X8 using Tapatalk
Click to expand...
Click to collapse
When you have received the Tablet, was it pre-loaded with Gapps and other softwares.
As my Tablet is not having any of the important software.
When I received the tablet, there was no Gapps present (not even PlayStore). I had no possibility of adding a Google account to the tablet (only other mail account or Exchange account). I downloaded a playstore apk, installed it, but couldn't make it work.
Then I searched for updates, found the update mentioned above, installed it and added Google account (it was now possible); concerning Gapps, only Play Store was installed as part of the new update (if I remember correctly)...
Sent from my X8 using Tapatalk
In the 1st post towards the bottom there is now a mega link with a full rom to flash that is NOT the crane but the Chuwi v1.1 with gapps installed
I'm sorry if this is the wrong thread but it seems this is the only place to ask.
Is it possible to save/move apps to a SD card? i can't find any option to do so and app2sd report this tablet doesn't support. not rooted and stock
Part I: description on this ChuWi vi7 tablet with 1GB RAM and 8GB flash.
Intel x3-C3230RK (j.v. with Rochip built by 28nm TSMC fab, has 2x 512KB L2 cache) SoFIA
which runs 32-bit Android 5.1.1.
Quad Core CPU is clocked at 416-900MHz (728MHz nominal) is a bit weak (Intel data brief says it's 1.2GHz x 4): GeekBench3 321 & 956.
I think the tablet is downgraded for thermal throttling (plastic case, not metal.) Suspect SDP is somwhere in between 2-3W.
GPU is ARM Mali450 4-core clocked at 600MHz which Antutu gives high score (at 1280x600 LCD resolution.) It should be good at 1080p (not on this tablet.)
It has 3-axis accelerator, USB OTG, GPS and single SIM slot. Proximity sensor seems to be emulated by touch screen multi-point. Li-Ion is on low capacity (~2500mAh) side.
This tablet when first received from China, there is no Google Play Store nor rooted. After performing phone system update, Google Play now works.
---------- Post added at 01:24 AM ---------- Previous post was at 01:14 AM ----------
Part II Rooting and mishaps
Rooting is difficult.
Find adb 1.0.32 (exact version needed) and install in a Windows PC (C:\adb).
Install Intel Android device driver first, then (Volume up then plug-in the USB, wait for 15 seconds.) Wait until in Device Manager the Vi7 device is recognized as the Intel Android Device.
At the same time, the tablet screen should show the Android robot with a minimal menu.
I transferred the files (unzipped, from main thread, first post) and
Using XDA vi7root script indeed gained the root.
However, I immediately found the Play Store problem, can't install any app (error 504) nor the existing apps can be updated.
---------- Post added at 01:39 AM ---------- Previous post was at 01:24 AM ----------
Hope this could help:
After Intel Inside flash screen,
It shows one additional screen right before the Home screen showing up.
Android is starting...
Starting apps.
==============
Also the vi7rootscript removed these (and others):
[email protected]
[email protected]
[email protected]
googlepinyin.apk
/data/dalvik-cache/x86/[email protected]@[email protected]@classes.dex
/data/dalvik-cache/profiles/com.android.launcher
/system/app/dataapp/chiweimarket.apk
Can one of these related to Google Play?
Thanks
ccshello

OTT TV BOX A95X Amlogic S905W 2G/16G Original Factory Image/Recovery

I had this TV Box I'd bought from Wish. I thought I would share a (nearly) stock image. I pulled it after having to play around with the Google Play Store for a while because it ceased functioning.
I had noticed several other people having issues with obtaining a stock ROM, possibly on other forums.
https://1drv.ms/f/s!AtYTbQWzzbfRiBZEsUFK73q2H-pX
Thought it thru some more today and I'm adding a raw image of boot, bootloader and system. There may be more on this device that someone will find useful, if it's the case, let me know so I can dumped and post it.
File availability
Hi engineerchad
I am seeking the files you previously linked to, however they no longer appear available.
I'd be very grateful if you could make them available again please, if you do not mind?
Thank you
Andy
Link dead
engineerchad said:
Thought it thru some more today and I'm adding a raw image of boot, bootloader and system. There may be more on this device that someone will find useful, if it's the case, let me know so I can dumped and post it.
Click to expand...
Click to collapse
I am searching for this ROM but the link seems to be dead. Can you re-upload it?
abpdora said:
I am searching for this ROM but the link seems to be dead. Can you re-upload it?
Click to expand...
Click to collapse
I will go ahead and put it back up, give me a little bit seems like I lost the files on my online drive so I'll have to go ahead and either pull from a backup or take it off the device again. Check back later today or tomorrow and I should have a new link posted for you.
Onedrive:
https://1drv.ms/f/s!Am__eYU6nzsDgYMcl4D4gdMkAnLIuw
Mega:
https://mega.nz/#F!u8t3ECYS!HH8I-DPraAsc1CwMeTt-1Q
I hope it helps! I would post the link for the TWRP recovery that I used, but it was specifically stated to -please- not link up to it, reproduce, copy, re-upload, etc by the author. I located it with a Google search for "TWRP Amlogic S905W" or something of the like. It doesn't function perfectly (on my high-def TV, it displays on the top half of the screen, with the bottom half just kind of filled with garbage and you NEED a mouse hooked to the box to use it, but it's workable).
engineerchad said:
Onedrive:
https://1drv.ms/f/s!Am__eYU6nzsDgYMcl4D4gdMkAnLIuw
Mega:
https://mega.nz/#F!u8t3ECYS!HH8I-DPraAsc1CwMeTt-1Q
I hope it helps! I would post the link for the TWRP recovery that I used, but it was specifically stated to -please- not link up to it, reproduce, copy, re-upload, etc by the author. I located it with a Google search for "TWRP Amlogic S905W" or something of the like. It doesn't function perfectly (on my high-def TV, it displays on the top half of the screen, with the bottom half just kind of filled with garbage and you NEED a mouse hooked to the box to use it, but it's workable).
Click to expand...
Click to collapse
Pull original recovery and send me a link ill try porting a fully functional version
Ricky Divjakovski said:
Pull original recovery and send me a link ill try porting a fully functional version
Click to expand...
Click to collapse
It should show in both links "recovery.stock.img" is the filename.
The conventions of naming partitions on the box are quite simple /dev/block/system /dev/block/recovery /dev/block/boot etc (I believe. I actually haven't plugged this one in for a minute after I got a slight upgrade for it that I'm using now.) I had originally intended to do this myself, but have been trying for a long time to recover from the mental/physical effects of a quarter million dollar set of injuries last year and it's been pretty brutal.
I see where someone has done an unofficial TWRP in https://forum.xda-developers.com/android-stick--console-computers/amlogic/recovery-twrp-3-0-2-0-touch-recovery-t3454549 for this device with 8GB ROM, so I'm not sure if this would work just as well, or if it needs to be remade (this box is labelled as A95X and it's the amlogic s905x chipset with 2GB/16GB so I'm not sure if it would somehow be different from the link above or not.)
I figured I'd update, it seems like I may have misread the post originally on freaktab the author requested people share this link as opposed to mirroring. Here it is (had to search it up again, by coincidence it's also working for my a95x max + box which is also OTT TV brand I'll try to get an image up from that but my computer shows it has a root trojan in the stock image?)
http://konstakang.com/devices/nexbox_a95x/TWRP/
twrp complete backup
Hi Can you post a full backup with all partitions?
I have a a95x pro s905w too, and lost L1 widevine
Thanks for your support.
Best Regards from Spain
Here you have the last update.zip from the vendor:
A95X(905w2_16)_PRO-7.1.2-201806201412 2018062016101756843 zip
https://drive.google.com/file/d/1aSNU51sA3hm2bI-S1w7fz2l_jrmjD6Ks
try and see if it solve your problem
afaik, the OTT TV BOX stock firmware has a su included. There's just no SuperSU or other app to control access to it from what I've seen (and it's been pretty touchy while trying to install one, IME)
hi
i have A95X R1 Android 7.1 CPU Amlogic S905W 2.0GHz GPU Mali-450MP5 RAM 2G ROM 16G, anyone have a firmware or ROM for it pls??
is-serb said:
hi
i have A95X R1 Android 7.1 CPU Amlogic S905W 2.0GHz GPU Mali-450MP5 RAM 2G ROM 16G, anyone have a firmware or ROM for it pls??
Click to expand...
Click to collapse
seeking that same firmware ..
firmware
deetucks said:
seeking that same firmware ..
Click to expand...
Click to collapse
I have a95x 1g 8g and was at android 6 (this has 2 g 16g as well posted below)
Link posted is for ALL firmwares for the ott nexbox devices. Pretty sure some of you will need this. The listing does not say 7.1.2 but it is. It says 7 or 7.1 no worries. I got it, used it.
It is nexbox... so if you have the nexbox logo on your screen this is your stock 7.1.2 as I have just upgraded my box today.
You can use twrp, but do it from SD and never install it as you don't need to. Put twrp .img file NOT the zip with the blank update zip below. Never need to lose stock recovery.... I think. Not sure about custom roms yet but will lknow in an hour I'd say. Also included a zip of a program that will format your sd card fat32. I had a 64 gig card and windows won't make it fat32. Stupid.
As far as making the bootable sd card, I kept only getting 2 files when I ran the burn card maker you may have seen. That uboot one never was put in. Then by mistake I loaded the main img file after one completion. So not sure if you have to hit make twice or maybe because I used a 64 gig card. But with all 3 files there, I stuck in the sd card, nothing except hdmi plugged in.... held the reset button in and powered on..... got the android guy and a long update bar.......updated!
If you can put stock by SD card... do it! That other method via USB with USB burning tool app? If it works, yay. But I never got it working. That fat32 maker was very handy!
Link if you have nexbox:
https://mega.nz/#F!F9xjTSSa!R0vJfTC2U6Qc2skNMrr1iQ!4wpwzJyS
Has twrp but all crappy like mentioned earlier... pretty sure. But all firmware from 5 to 7 and I got 7 from there.
its not a nexbox..and its 2g 16g.. i cant find its stock rom anywhere,, the ds card thing does not work either ..i tried with numerous custom rom jus dont boot with the ds card,,
deetucks said:
its not a nexbox..and its 2g 16g.. i cant find its stock rom anywhere,, the ds card thing does not work either ..i tried with numerous custom rom jus dont boot with the ds card,,
Click to expand...
Click to collapse
That sucks. The link posted has 2 gig 16 gig. All firmwares... think my board is the same.
hmm.. think it is the same box. I will re-read your specs if you listed them
How did you get firmware to sd card, is it fat32 and only stock will work... so not sure but I think if you try from the link I posted, it won't screw you up? I think?
Ott tv box
model: R1
cpu: Amlogic s905w
ram: 2gb rom :16gb
[email protected]
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
i can always try ,, i definately will look into it and give a try,,
deetucks said:
Ott tv box
model: R1
cpu: Amlogic s905w
ram: 2gb rom :16gb
[email protected]
Click to expand...
Click to collapse
oh you got the w.....have you looked on freaktab? Some site I just discovered. There is a good chance you'll find it there or someone can help.
I just tried looking and there is almost nothing. Weird because I could have sworn I saw a lot of s905w when I first started this.. Now you got me looking.
trust me i,m on freaktab cant find nothing.. request help nothing so far..
---------- Post added at 12:08 PM ---------- Previous post was at 11:55 AM ----------
trust me i,m on freaktab cant find nothing.. request help nothing so far..

Categories

Resources