[GUIDE][TOOL] Dreamtab increase internal storage - Fuhu Nabi 2

Summary​
Uses an external micro sd as "internal storage". Accomplished by a ramdisk edit to the boot image. The bootloader must be unlocked to use this tool and unlocking the bootloader will erase all personal data, game saves, etc on your device. For devices that already have their bootloader unlocked there is an option to transfer the current data to the external microsd card.
Considerations​
-The bootloader needs to be unlocked. The unlocking procedure erases all data on the device. If games saves, etc, are important use a tool that can back them up first.
-If you already have an unlocked bootloader the script allows you to transfer the data over and it should be like nothing ever happened but an increase in space. However, scripts are not perfect, nor can I take in to account every situation that might arise. If you have an unlocked bootloader and your data is important, please, please, please make a backup before trying this script.
-Micro SD card quality. All data will be read and written to the micro sd card. Not all cards are created the same. Many have very poor write performance, especially 4K writes. I tested about 6 or 7 cards and found the Samsung EVO+ as the best performing card. I didn't test the SanDisk extreme but it will likely be good as well. Increasing the size available is of no use if the speed is terrible and the tablet is laggy.
-Drivers. You must have fastboot and ADB drivers already set up and ready to go. The drivers are always a pain because so many different computers have different setups, previous drivers installed, conflicting drivers, etc. I attached the NabiLab2017 drivers to the post, even they can be buggy but provided an option if you choose. More about driver setup can be found here https://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Procedure​
ONLY FOR NVIDIA NV08B
Video: https://www.youtube.com/watch?v=aka8nUu7qQY
Video with data transfer: https://www.youtube.com/watch?v=ZbxqtzV33jI
ADB and fastboot drivers setup and tested
Micro SD card you want to use installed
Device connected and booted to Android
Unzip and run convert.bat
________________________

Thanks (again) @aicjofs for all the work you continue to do on these Nabi Dreamtab HD8s. TWRP, fsck fixes, stock 137 TWRP backups, and now this (which cures my biggest gripe about these tablets).
My kids are rough on them, but, because of the work you do, I've been able to keep them going & they grow with my kids. I just picked up 2 more refurbs from eBay today for $50 each. I'll be applying this internal storage fix as soon as they arrive.
I'm a Linux guy, not Windows. Would it help if I contributed a bash script that mimics your convert.bat? I'd have to assume that adb & fastboot are already installed & running, but I could probably script most of if from that point.

jvonhoff said:
Thanks (again) @aicjofs for all the work you continue to do on these Nabi Dreamtab HD8s. TWRP, fsck fixes, stock 137 TWRP backups, and now this (which cures my biggest gripe about these tablets).
My kids are rough on them, but, because of the work you do, I've been able to keep them going & they grow with my kids. I just picked up 2 more refurbs from eBay today for $50 each. I'll be applying this internal storage fix as soon as they arrive.
I'm a Linux guy, not Windows. Would it help if I contributed a bash script that mimics your convert.bat? I'd have to assume that adb & fastboot are already installed & running, but I could probably script most of if from that point.
Click to expand...
Click to collapse
Absolutely contribute, I don't do this for fame or money, just try to help others. Any and all additions are always welcome.
It should be easy enough to convert as most of the magic happens on the tablet itself, I think I only pushed a couple files to the tablet and made the ramdisk changes on the tablet too to keep the file size down. Weird how TWRP, the kernel, the tablet itself is all done in Linux but I only make windows scripts/apps.
I have quite a few of these tablets too, 5 maybe?. Kind of weird because Fuhu/Nabi screwed up that fsck thing so many people dump the tablet for next to nothing because they seem like garbage and crash all the time with loss of all the kids data but they are really a solid tablet. Try and find a screen of the HD8 quality on a modern kids tablet for $50. Shame about the crappy source code, if I could have got the camera to work right in the kernel I think I would have pressed on with the lollipop ROM and instead lost interest. This mod though breathes a lot of life into it still though. I have 3 of these running the mod and the kids still use it all the time with 64GB cards as their main storage and have had no issues.

aicjofs said:
Any and all additions are always welcome.
Click to expand...
Click to collapse
I've attached my attempt at a bash script for the swap. I got time to run one of my tablets through the gauntlet with this version, and only hit a snag at the check for fsck. Since I was that far, I just fixed the bug & applied the rest by hand. So, beware.
aicjofs said:
if I could have got the camera to work right in the kernel I think I would have pressed on with the lollipop ROM and instead lost interest.
Click to expand...
Click to collapse
I hear you there. I was hoping to see you get Lollipop going (even w/o a camera), just to have the battery saver. But, Greenify does a pretty good job keeping the battery going a while. So, again, thank you, and let me know if this script needs fixing.

Thanks for the work on this tablet. I am trying to salvage our dreamtab with your method. Unfortunately, I have a card inserted but the convert.bat never gave me any information about the sdcard like it did for you in the youtube video. Any idea what I might be doing wrong?
Thanks again!

Related

[BOOT] Worse news (was "Bad news everyone.")

I now have proof that the Nook Tablet is efuse locked and bootloaders signed. We can only boot signed bootloaders, kernels, and ramdisks from microSD.
Don't buy this if you expect any real development to happen on it. The only possible way is through kexec, and that's a lot of trouble to go through considering all the other tablet options.
For what it's worth, the u-boot in the recently posted update image from the Kindle Fire does not appear to have the signed header that the one on the NT has.
Things I learned in the process:
-USB boot is enabled, as is SD boot
-I can boot from a microSD if I format it the same as for Nook Color (modified CHS, fat on p1) and copy the MLO, u-boot, and boot.img renamed to flashing_boot.img
-There is a serial port inside that will let you at the u-boot console and a shell after the OS boots
-x-loader is signed. A known-good x-loader on microsd will not even execute, and the next item in the boot list checked (emmc)
-u-boot is signed. I know this because a known-good u-boot from Pandaboard that should be close enough to boot causes x-loader to take the code path where the secure ROM call with a pointer to the image returns nonzero
-kernel and ramdisk are signed individually in the boot.img. I can modify a byte in the boot.img on the microsd that's in the middle of the kernel or the ramdisk section and u-boot will fail the same exact call that x-loader uses to validate u-boot, but this time emitting a message complaining that the image is corrupt
-Comparing the first part of u-boot grabbed from the NC, NT, and the KF, shows that the signature that's at address 0 of the KF and NC versions is seen about 300 bytes into the NT version, with some unknown junk above. I assume that's the signature, and that the call to the secure ROM returns the image pointer (which is passed by reference, a good clue) plus the size of the header.
Wait.. Nook Touch or Nook Tablet?
DarkDvr said:
Wait.. Nook Touch or Nook Tablet?
Click to expand...
Click to collapse
Tablet. I blame BN's marketing.
what about this?
http://code.google.com/p/pandroid/downloads/detail?name=u-boot.bin&can=2&q=
That's certainly... interesting. Definitely not the direction I assumed they would go given those quotes from the B&N guys that have been thrown around.
I'll hold off any true disappointment until more people have had more time to poke at this thing. Nothing against you pokey, and thanks for your investigations so far.
diamond_lover said:
what about this?
http://code.google.com/p/pandroid/downloads/detail?name=u-boot.bin&can=2&q=
Click to expand...
Click to collapse
Close enough to the one for Pandaboard minimal Linux, which I tried.
pokey9000 said:
Close enough to the one for Pandaboard minimal Linux, which I tried.
Click to expand...
Click to collapse
I hope we can find a workaround, there will be a way to do that, because they installed android in some way.
BTW, have you tried a bootable SD card? I think it's the right path to follow.
EDIT: I see you can't boot by sd card.. what about if you try some file from Nook Color?
pokey9000: what kind of a response you can get when trying to boot your test SD in BB Playbook, I wonder?
diamond_lover said:
I hope we can find a workaround, there will be a way to do that, because they installed android in some way.
BTW, have you tried a bootable SD card? I think it's the right path to follow.
EDIT: I see you can't boot by sd card.. what about if you try some file from Nook Color?
Click to expand...
Click to collapse
Trust me, I've tried every trick used when we figured out how to boot on the NC.
might need some combination of keypress while the thing powers on...
I bet BN built-in some backdoor 'boot off SD' mode. This would allow them to grab the Nook Tablets and reformat the onboard space/memory however they see fit.
This was done in the past with the NC.
discothan said:
might need some combination of keypress while the thing powers on...
I bet BN built-in some backdoor 'boot off SD' mode. This would allow them to grab the Nook Tablets and reformat the onboard space/memory however they see fit.
This was done in the past with the NC.
Click to expand...
Click to collapse
I agree, but it sounds like the problem is not with it blindly skipping the SD card but with it not seeing a signed image on the SD card. In that case B&N might just be providing their stores with SD cards with a properly signed image that doesn't need any other tricks
If B&N really is requiring signed images to boot from the SD card, I guess there might a different method to change the bootloader - after all, most (all?) phones won't boot off of a SD card, and it is still possible to change bootloaders on many of them.
BUT, I don't think this device is going to have nearly the same dev support as a year ago to discover/crack the bootloader issue.
I'll wait a little bit longer, but the quick progress rooting the Kindle Fire makes me think that that might be my next device to replace my lost Nook Color.
Sorry B&N - you might have lost me!
jasoraso said:
If B&N really is requiring signed images to boot from the SD card, I guess there might a different method to change the bootloader - after all, most (all?) phones won't boot off of a SD card, and it is still possible to change bootloaders on many of them.
BUT, I don't think this device is going to have nearly the same dev support as a year ago to discover/crack the bootloader issue.
I'll wait a little bit longer, but the quick progress rooting the Kindle Fire makes me think that that might be my next device to replace my lost Nook Color.
Sorry B&N - you might have lost me!
Click to expand...
Click to collapse
agreeed. there's so many low-cost devices out there and devs are going to have to pick "sides": kindle fire, nook tablet, and who can forget the hp touchpad
Considering most people havent had this in their hands more than 24 hours, I think it's a bit premature to make any calls.
That being said, I'll be holding on to my $$ a wee bit longer it seems.
I really hope it can be rooted and then be able to put ICS on it. I guess I will hold onto my money a little longer also.
Even though I want the NT more, I would get a KF since it can be rooted.
DarkDvr said:
Fill your heart with patience, people =)
Click to expand...
Click to collapse
Let's all just take a deep breath and not get carried away, this stuff hasn't been out for a week yet.
Nuenjin said:
Let's all just take a deep breath and not get carried away, this stuff hasn't been out for a week yet.
Click to expand...
Click to collapse
It isn't even "officially" out at all yet
so far I am happy with it but root would be nice.
I thought it was officially out today?
Ellerbestyle said:
I thought it was officially out today?
Click to expand...
Click to collapse
Official date is 18/11

[Q] Internal SD Card "Read Only"

I am having a rather challenging issue. I moved from branch 1.1 and Vegan GE-7.0.0.0 RC1 to 1.2 NVflash 20110508 CWM5504 and flashed the TeamDRH-AOSP-Preview-1F-LDPI. So the issue is that I cannot write to, wipe, reformat or partition my internal sdcard. I had to flash the ICS ROM from my external sdcard and reboot system, but the screen locks on the TeamDRH title graphic page after loading all of the apps. I tried different releases of CWM55XX, but no difference.
Running CWM, I have re-partitioned to 4096/0, then 2048/0, formatted/cleared/wiped every partition, run the keycheck and tried pretty much every function CW has but nothing can touch the files on the drive!
I can get into APX and CWM. I can mount the USB port and view the internal drive. I can move, add and delete files and windows explorer shows that each action is completed. I renamed the old Update.zip to Update-Old.zip and it changes in explorer. But as soon as I unmount USB the changes are lost. When I go into CWM and try to install the zips, the only zip files showing are the update.zip and Vegan…zip. I tried to go back to Vegan, but it boot loops.
I tried rr5678’s G-Tablet Format utility that completely erases all traces of anything in the G-Tablet's ROM storage space. It showed all of the steps as completed. I got the red letter message at power on, immediately flashed the 1.2 NVflash/CWM and it functioned perfectly. But, still, no change or effect on the old files on the internal sdcard.
At this point, after way too many hours researching, reading and rereading, it may be that either I have a corrupt config file, (which is beyond my limited expertise to determine) or a bad microdrive.
I would appreciate any thoughts or ideas on resolving this. I want my GTab back!!! (It would be extra nice to have ICS, as well!)
Cheers,
Geary
galyons said:
Running CWM, I have re-partitioned to 4096/0, then 2048/0, formatted/cleared/wiped every partition, run the keycheck and tried pretty much every function CW has but nothing can touch the files on the drive!
Click to expand...
Click to collapse
This is a known problem that sometimes develops on some gTabs with a non-standard kind (compared to the majority of gTabs) of internal SD card.
There is no known "fix" for the problem. There is a workaround on page 5 of that thread, though.
But, first, I'd like you to get me the output of a dmesg command and then run through a set of tests (see posts #88 and #66) and get me their exact output.
Ok, I will read enough to see if i can figure out how to get the test results. Gonna take me a couple of days. Thank you for the guidance!
Cheers,
Geary
Well, I downloaded the Knoppix image, burned a bootable CD, booted Knoppix, hassled through getting connected to the internet, reread the threads and gave it a "go". Got buried in abd...dmesg and bailed. I would love to provide all of the diagnostic messages, but quite honestly, do not want to invest more time to become marginally able to do so.
So...RMA and boxed off to US Merchants. Hopefully you can discover a fix, rather than a work around for this issue. But the work around is infinitely better than an ever boot looping tablet!!
Thanks again for your help to me and others!!
Cheers,
Geary

[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] I'm stuck on a boat without paddles!

I WANT TO START OFF BY SAYING THAT THIS IS THE FIRST TIME I HAVE MADE A THREAD ON THIS SITE.
I FEEL MY ISSUE IS UNIQUE AND ALL HELP WILL BE MUCH APPRECIATED. THANK YOU
Click to expand...
Click to collapse
The tablet that I am dealing with is a "Cruz Velocity Mini Tablet" running android 2.0 and no means of installing apk's.
Currently this is the situation:
A friend of mine lent me her Chinese reader tablet.
I told her that I could probably flash a newer version of Android on it, thinking that I could finally try my hand at making a ROM because I know for a fact that there aren't many ROMs if any at all out there for a chinese off brand reader like this.
After rooting the tablet I deleted the pre installed bloatware via ADB commands (shell) including a file manager (Astro) that I believe was the only way that you could browse files on the tablet, as well as some other pre installed applications that must have been necessary in retrospect. There is no existing vending capability or market application.
I am looking to make a custom ROM (Using android Kitchen and Cywign) through following this tutorial by lokeshsaini94 yet I feel like following that tutorial won't even get me where I need to be.
Click to expand...
Click to collapse
Things that I have tried at this point include:
Attempting to connect the tablet to my computer with the SD inserted (with and without debugging turned on) [Failed to show up on my computer as a device or anything]
Downloading the APK that I need from a file sharing website [Downloads fail]
Uploading the APK that I need to my Google drive and downloading it from the tablet [Says waiting for data connection and doesn't download even though connected to our WiFi]
Inserting the SD card into my computer, copying the APK I need over to it, then inserting the SD card back into the tablet, going into the browser and typing "File:///sdcard/<name here>.apk" to install an APK but getting an error in the installer after pushing 'install' -> 'Application not installed'
Trying to perform a factory reset; this simply makes the tablet reboot with everything the same as it was before.
Essentially guys and gals, my tablet here is running Android 2.0, I want to update it by making my own rom for it to something at least >4.0, and it seems that I've made things worse and have no way out of this mess. I think I've essentially bricked it even though it still works. :silly:
What do I need to do to make a custom ROM let alone flash/wipe this tablet?
All help will be incredibly valuable
There should be plenty of info here http://www.slatedroid.com/forum/93-velocity-micro-cruz-reader/ to get you on the right track. Not likely you'd be able to get anything beyond Gingerbread on there running due to lack of source code. Your only hope would be to see if there is a newer tablet with the same chipset that has something newer on it to port over.
Still no paddles
es0tericcha0s said:
There should be plenty of info here < > to get you on the right track. Not likely you'd be able to get anything beyond Gingerbread on there running due to lack of source code. Your only hope would be to see if there is a newer tablet with the same chipset that has something newer on it to port over.
Click to expand...
Click to collapse
Thank you very much for your response. It looks like on that website I've already found multiple useful roms!
In fact I already downloaded one and put it onto the SD card. Apparently for these tablets you're supposed to, while powered off, turn it back on by holding the power button and the volume up button but all this seems to do as a whole load of nothing.
I fear that what I've done to it by deleting potentially sensitive programs previously, I have somehow managed to make this process impossible.
Is there some kind of way that I can plug this tablet into my computer and be able to completely wipe it so I can, at the very least, have a functional tablet that will work at all? I've done approximately 5 factory data resets yet the background image that my friend has on the tablet as well as seemingly every single setting and application is remaining untouched..
Try the ones here that also install a custom recovery: http://www.slatedroid.com/topic/33586-a-clockworkmod-rom-compendium-for-the-cruz-reader/
You'll want to make sure and rename the file exactly as mentioned there on the OP. Install instructions are included too. I don't think there is a way to reload via the PC. The right zip should get everything working properly.

cifs.ko module / Busybox / mounting CIFS shares

Hello all. In the last 24 hours I've racked my head against a wall and I can't seem to get past this. So some pointers would be very welcome.
Backstory - Been doing backups of Titanium Backup onto my Nexus 9 (16GB internal storage) and I'm running into problems with running out of storage space. So I thought I'd look into doing a CIFS share mountpoint to my tablet and backup directly to the CIFS shares on my FreeNAS box. I figure a couple TB of storage is enough to store my Titanium Backups.
So first I read about CIFS Manager. Seems it may be discontinued or not functional on Lollipop.
Then I read about Busybox. Very cool, I think I'd marry Busybox if it was a woman. It seems so amazing I bought the Busybox Pro version.
So I tried to mount the CIFS/SMB share but I keep getting the dreaded "no device found" which means the cifs.ko isn't loaded. Apparently it's not in OS by default, so I need to compile it. (I'm not against someone giving me the .ko file, but I'd rather learn how to fish for myself than expect someone to give me a fish when I'm hungry) I have no clue how to compile it or even where to start to get a resemblance of the necessary steps. My experience is mostly Windows and FreeBSD, with only enough knowledge of linux to be very dangerous. I've tried searching all over for some kind of guide, pointers on what files I need to get, where to go to compile, etc but there seems to be nobody out there with any kind of good guide, even an outdated one I could use to fill in the blanks. I was hoping to put together a fairly detailed guide that includes steps on how to compile the cifs.ko yourself from source as well as mount your share on the device for whatever purposes you desire. But I'm finding that there is basically no info online on how to do this, where the source is, how to compile it, etc. If you know how to do this and are willing to help me write the guide (I've written quite a few articles on FreeNAS and ZFS) I'd be more than happy to give you some credit. I have no doubt lots of people will use the document once it is created.
Alternatively I considered doing the same with NFS but again I'd need to compile the nfs.ko module, so I'm stuck at the same point there.
Anyone have any pointers on how to do this? Or, anyone have any other options that will work just as well that allow me to not have to store the actual titanium backup files locally?
About the only thing I can find is someone saying that you need a Linux VM, the kernel sources, sdk, some knowledge in unix, and patience. But hell, I don't know if by saying "kernel sources" they are talking about the kernel source for the Linux VM or the Android OS I'm running (or both), if the SDK is referring to the Android SDK or not, etc.
Thanks in advance!
Joshy8 said:
Or, anyone have any other options that will work just as well that allow me to not have to store the actual titanium backup files locally?
Click to expand...
Click to collapse
I was in the same boat as you a few years back. Basically I would root, find a kernel that had the CIFS module, then use CIFS Manager to mount the shares. I would also use rsync & busybox. This stuff is tricky. The command to get Android to mount the shares, the CIFS module and kernel always has to be up to date, changes in busybox, etc.. I dreaded Android system updates. It starts to feel like a Rube Goldberg machine.
I started using an app called FolderSync (there's a paid version, too) and never looked back. It works quietly in the background and have never had any problem with it. It's one of the best apps on Android.
I do thank you for the advice, but that's how I've been doing backups for several years. I bought it back when the original Droid phone came out.
However in this case, since my tablet has only 16GB of internal memory and you can't easily have permanently attached external storage I'm forced to come up with an alternative of some kind.
I have had some problems lately with FolderSync. Not sure exactly what the problem is, but FolderSync seems to have issues from time to time and it gets stuck on random files and never finishes, even if left to complete for several days. I've had this issue randomly on 3 different devices, and one of my friends that also uses FolderSync has had the same issue on his. So I'm pretty sure there's a bug of some kind in FolderSync that sometimes breaks it.
Anyway, since my tablet has only 16GB of internal memory and you can't easily have permanently attached external storage I'm forced to come up with an alternative where the data is never actually stored on the device itself. :/
I know this isn't the answer you were looking for, but have you seen these:
http://www.meenova.com/st/p/mrg2.html
It's the closest thing I've found to convenient usable external storage.
Sent from my Nexus 9
The Fire-Ice kernel (http://forum.xda-developers.com/nexus-9/orig-development/kernel-fire-ice-t2930451) supports CIFS. I use it to connect to my SAMBA linux server. I also did the following, not sure if both of these are necessary: set SELinux to permissive with SELinux Mode Changer, and use the "patched" version of CIFS Manager (found on this forum).
I'm still hoping somebody will just write or cross-compile a FUSE module (like SMBnetFS) that works on all rooted devices, so we don't have to rely on custom kernels/modules anymore...
Since you asked for alternatives, you can also just get an OTG cable and hook up a USB stick or external HD to your phone (needs root and an app like StickMount).
Thanks for the reply. Been a bit busy with life stuff and just finally got to sit back down and look at this again.
I agree that a FUSE module would be useful for something like this. I don't have a need for high performance with regards to this problem, so a FUSE module would seem very appropriate.
I do have an OTG cable and I do have a 64GB thumbdrive I can use. I was just hoping for something that was a little non-obtrusive and passive so that I'm not actively having to be involved in the backup process itself. As soon as someone in the meat-world has to take active steps to make a backup every time, that's when backups typically stop happening, and then the next thing that happens is data loss. So I'm trying to remove myself from the equation as much as possible.

Categories

Resources