Related
Hello,
I have prepared a few update.zip's with kernels to boot linux:
There are two different zips.
One to boot linux from a USB Flashdrive and the other from a SD card.
Installation Instructions:
ALWAYS HAVE CHARGER CONNECTED WHEN UPDATING A FIRMWARE.
1. Please follow the instructions here to prepare your SD / USB Drive - start at "== Create a rootfs SD card ==". http://ac100.gudinna.com/README/
2. Extract contents to a folder and follow instructions below.
copy the update.zip to a sdcard, and insert sdcard into folio.
Enter "Recovery menu" when folio is just turned on and press (POWER) once and (VOL up) next.
press (VOL up) Factory reset or system update.
press(VOL down) to continue to system update.
press (VOL up) to confirm system update.
during installation progress bar will show har far it is.
folio will reboot after installation.
insert the usb or flashdrive with the prepared filesystem into the folio and the tablet will boot automaticly from it
This sounds very interesting, might give it a try when im done playing with my new folio, ubuntu on it would be awesome
Does it boot to a full Ubuntu desktop or a bash prompt?
key combination to boot ubuntu
DerArtem said:
Hello,
I have prepared a few update.zip's with kernels to boot linux:
Please follow the instructions here to prepare your SD / USB Drive - start at "== Create a rootfs SD card ==".
Unzip the zip and then use the zip inside to update your kernel.
There are two different zips.
One to boot linux from a USB Flashdrive and the other from a SD card.
Click to expand...
Click to collapse
Hi DerArtem,
once the media (SD) is setup, you need special key combo in order to let folio boot from the SD? thanks in advance.
zoken4 said:
Does it boot to a full Ubuntu desktop or a bash prompt?
Click to expand...
Click to collapse
It depends on what you have put on your sd / usb flash.
Ivalex said:
Hi DerArtem,
once the media (SD) is setup, you need special key combo in order to let folio boot from the SD? thanks in advance.
Click to expand...
Click to collapse
I have updated the 1st post.
DerArtem said:
It depends on what you have put on your sd / usb flash.
I have updated the 1st post.
Click to expand...
Click to collapse
gorgeous!
got it, the first step, is exactly the same as uploading a mod. then the SD modified as per gudinna instr. will bring you to linux.
thanks again.
how fast/responsive is this? Can you benchmark it against the AC100 netbook running the same image - that had a noticeable lag at least on SD card access.
How prepare the SD?
Thank you for your work!!!
I did all the process but I can't start linux.
The kernel boots but stop without start the desktop.
You can see when stops in this image:
ifisc.uib-csic.es/~edu/fotos_folio100/1.jpg
(Put the http:..., I can't put links because the system)
I prepared the filesystem in a SD card only decompressing the tar.gz, ¿Is necessary recompile the kernel or something like configure it?
Shark.
Shark17 said:
Thank you for your work!!!
I did all the process but I can't start linux.
The kernel boots but stop without start the desktop.
You can see when stops in this image:
ifisc.uib-csic.es/~edu/fotos_folio100/1.jpg
(Put the http:..., I can't put links because the system)
I prepared the filesystem in a SD card only decompressing the tar.gz, ¿Is necessary recompile the kernel or something like configure it?
Shark.
Click to expand...
Click to collapse
I have not tested it using a SD-Card. I will try it out when I have some time...
I met the same problem : stuck at the "no console found" point, and this either with an sd-card or a usb key. I also tried wolfx's method (boot via fastboot), and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
DerArtem : could you tell us what distro you put on your usb-key ? (and maybe even with links for download ?)
Regards,
eRaph
USB tried
I tried with the USB and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
Click to expand...
Click to collapse
I'm agree with your opinion.
I confirm that the method is not agressive for the tablet, restore android works for me.
Actually, I just found what the problem was : on the image I uncompressed on the usb key (tegra-rootfs.tgz), the /dev directory was empty, and lacked a console and a null entry (see h**p://ubuntuforums.org/showthread.php?t=28550)
The folowing command solved the problem (to do on your sdcard/usbkey) :
cd dev
mknod -m 660 console c 5 1
mknod -m 660 null c 1 3
Hi,
eraph2 said:
I met the same problem : stuck at the "no console found" point, and this either with an sd-card or a usb key. I also tried wolfx's method (boot via fastboot), and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
DerArtem : could you tell us what distro you put on your usb-key ? (and maybe even with links for download ?)
Regards,
eRaph
Click to expand...
Click to collapse
I have used gentoo linux on a usb flash:
http://dev.gentoo.org/~armin76/arm/tegra2/install.xml
http://www.gentoo.org/doc/en/handbook/handbook-arm.xml
eraph2 said:
Actually, I just found what the problem was : on the image I uncompressed on the usb key (tegra-rootfs.tgz), the /dev directory was empty, and lacked a console and a null entry (see h**p://ubuntuforums.org/showthread.php?t=28550)
The folowing command solved the problem (to do on your sdcard/usbkey) :
cd dev
mknod -m 660 console c 5 1
mknod -m 660 null c 1 3
Click to expand...
Click to collapse
Yes, this files exists in the gentoo in the .tgz ....
I think that ubuntu might require a initrd...
And ubuntu works?
Can you start ubuntu fixing this?
Console
Creating the console in the dev..., ¿are you started ubuntu?
I successfully managed to boot the ac100 ubuntu image (tegra-rootfs.tgz) copied on my sdcard. X started well, and hooking a keyboard, I managed to create a user, edit his password, ...
Nevertheless, I did not manage yet to make both a keyboard and a mouse work at the same time (the usb hub does not seem to work), and unpluggin/replugging the keyboard did not work either.
So, the ac100 ubuntu image works somewhat (in text mode via ALT-F1, i managed to get root access), but seems to lack some hardware support (which is quite normal).
The first problem is probably that the boot.img I used was the one DerArtem provided with his modified sdmmc-update.zip archive, which contains a 2.6.32 kernel, whereas the ubuntu image uses a 2.6.29-ac100 kernel, hence no modules get loaded. I should find how to rebuild a boot.img with the good kernel (or better : add the good modules to the ubuntu image).
DerArtem : may I ask you how you did rebuild the boot.img in your various packages ?
Regards,
eRaph
eraph2 said:
I successfully managed to boot the ac100 ubuntu image (tegra-rootfs.tgz) copied on my sdcard. X started well, and hooking a keyboard, I managed to create a user, edit his password, ...
Nevertheless, I did not manage yet to make both a keyboard and a mouse work at the same time (the usb hub does not seem to work), and unpluggin/replugging the keyboard did not work either.
So, the ac100 ubuntu image works somewhat (in text mode via ALT-F1, i managed to get root access), but seems to lack some hardware support (which is quite normal).
The first problem is probably that the boot.img I used was the one DerArtem provided with his modified sdmmc-update.zip archive, which contains a 2.6.32 kernel, whereas the ubuntu image uses a 2.6.29-ac100 kernel, hence no modules get loaded. I should find how to rebuild a boot.img with the good kernel (or better : add the good modules to the ubuntu image).
DerArtem : may I ask you how you did rebuild the boot.img in your various packages ?
Regards,
eRaph
Click to expand...
Click to collapse
Hi,
please search on the web how to rebuild the boot.img. This is not a problem. My zip also contains the config to rebuild the kernel. The sources of the kernel are also documented in the readme inside the zip. The initrd is just empty.
But running ubunu on the folio might be a bad idea. Ubuntu is compiled for NEON instruction set, but the Tegra 2 CPU does not support this, so a lot of applications can crash when they will try to execute more advanced code....
Debian (optimized for ARMv6 without NEON) or Gentoo are better for the Folio.
Then, if I want to install gentoo instead ubuntu, do I have to follow the same steps but changing the distro linux for the gentoo? Or is it necessary to do anything else?
Thanks
I tried to install gentoo in a USB, but it's a long process and it's not usual for me.
I'm very lost!
halu:
If you obtain a opetative distro image, can you upload in any place?
I'm thinking in write a howto with the results.
Bests
(Saludos desde Mallorca!! )
I have been using VEGAn-Tab Ginger Edition for about 2 weeks and it was nearly perfect. THEN, yesterday I started the Tab and it only made it to the "G-TABDEVs" screen and stayed there.
I turned it off and every start gave the same response.
I applied the NVflash and only got past the Viewsonic bird screen then the Gtablet screen got stuck...same.
I applied the NVflash with the CWmod in part 9 and was the same, but now I can access the CWmod screen.
I tried to partition (2048, 0) and it gets stuck every time (have to power down)
It seems that the partition table or something is lost or corrupted.
I can not perform any of the CWmod commands, it just freezes and I have to power down.
Is there any other way to set partitions or does this seem like another issue.
I have looked tirelessly among all the great information here to no avail.
Thank you in advance!!
nevermind........ didnt read carefully and my answer was not going to be helpful so I deleted it
Ditto for me.. except
Except that my tablet will eventually run CWM, but everything is SSSSLLLOOOWWW............................................. as in 5 minutes to wipe cache, plus the 10 minutes and errors about "Can't mount /dev/block/mtdblock4 (Not a directory)" before I even get a menu in CWM.
All of this happened after flashing Clemsyn's latest PIMP kernel (and wiping appropriate areas, cache and Dalvik)... obviously the two incidents seem related, but I see reports of folks on the forums running this combination all the time and my tablet booted three times with no problem before it experienced terminal slowdown...
So why the "nevermind"... how was this fixed?
Not fixed yet.... Don't know what the "nevermind" was about...
Oh, OK, sorry. possibly a mis-post... I am currently backing up my internal SD card and preparing to NVFlash, repartition and reformat my internal SD card and load everything new. I am hoping that the issues are filesystem related and that a total clean out will fix it. I will most likely not use Titanium Backup to restore my apps, as that has been mentioned as a source of issues with the GB Vegan ROM - especially boot issues. Long process ahead - I have over 350 apps to sift and sort through manually - not looking forward to it...
I will post here if this fixes the problems in the chance that our issues are related.
heliav8r said:
I have been using VEGAn-Tab Ginger Edition for about 2 weeks and it was nearly perfect. THEN, yesterday I started the Tab and it only made it to the "G-TABDEVs" screen and stayed there.
I turned it off and every start gave the same response.
I applied the NVflash and only got past the Viewsonic bird screen then the Gtablet screen got stuck...same.
I applied the NVflash with the CWmod in part 9 and was the same, but now I can access the CWmod screen.
I tried to partition (2048, 0) and it gets stuck every time (have to power down)
It seems that the partition table or something is lost or corrupted.
I can not perform any of the CWmod commands, it just freezes and I have to power down.
Is there any other way to set partitions or does this seem like another issue.
I have looked tirelessly among all the great information here to no avail.
Thank you in advance!!
Click to expand...
Click to collapse
Little more info.... Using ClockworkMod v2.5.1.1 Bekit 0.8
no problem accessing APX mode and applying NVflash.
After a full NVflash and reload, not restoring anything from Titanium Backup, i am running again. I am also booting faster... <1 minute. Not the simplest fix but it worked.
huntar said:
After a full NVflash and reload, not restoring anything from Titanium Backup, i am running again. I am also booting faster... <1 minute. Not the simplest fix but it worked.
Click to expand...
Click to collapse
This happened to me as well. I had vegan ginger rc1 running for a couple of weeks and then I chose to reboot the gtab because I couldn't get an app to work when I was trying to open it. Upon reboot, I got stuck in a boot loop. It would make it to the flashing vegan ginger screen and would just keep looping. I nvflashed and then got stuck at the gtablet screen like yourself. I had to nvflash with cwm built in to get back into cwm. It was a real pain and I thought my gtab was toast. I'm back running and haven't had a problem yet (knock on wood). But a few weeks have gone by and it is running stable.
heliav8r said:
Little more info.... Using ClockworkMod v2.5.1.1 Bekit 0.8
no problem accessing APX mode and applying NVflash.
Click to expand...
Click to collapse
Hi,
I'm having a very similar issue. I can NVFlash till I'm blue in the face bug I can't repartition the SDCARD; just hangs or spits an error (1.1 or 1.2). I notice that NVFlash only ever starts flashing at part4.img; wondering why it doesn't do the ealrier part2 etc.
How can I get the partitions fixed without CWMod as it ain't working for me. I've disco'd the battery also, no luck. All the flashing with and without CWMod works but I hit the bootloop or stuck on gtab logo (after birds). I'm really leaning toward "It's dead Jim"
Seems I have to repartition but can't do with CWMod of any flavour; also tried format.zip image; no joy.
HELP ME PLEASE!!!
jroger0707 said:
Hi,
I'm having a very similar issue. I can NVFlash till I'm blue in the face bug I can't repartition the SDCARD; just hangs or spits an error (1.1 or 1.2)
Click to expand...
Click to collapse
nvflash cannot fix your SD-card partition problems. See this post for why. You have to either use ClockworkMod or the system commands available in recovery mode to re-partition your SD cards.
If you can get a working adb set up, I can walk you through the steps to manually repartition the internal SD card.
WhyDidI
rajeevvp said:
nvflash cannot fix your SD-card partition problems. See this post for why. You have to either use ClockworkMod or the system commands available in recovery mode to re-partition your SD cards.
If you can get a working adb set up, I can walk you through the steps to manually repartition the internal SD card.
Click to expand...
Click to collapse
Thanks for the reply. I've got adb installed and working and have been trying to do it with parted and sdparted. I've tried sdparted -es 2048 -ss 0; it just sits there forever checking requirements. Parted can't seem to find anything. I don't have /dev/block/mmcblkXXX shown only mtd and loop (for current state at least)
I also tried mknod b 179 XX based on my good gtab to try to recreate but I'm a little over my head there so may be doing something wrong or missing additional steps.
For s+g I've uploaded dmesg for my good gtab and badtab. Some notable diffs including version; likely because one is Vegan 5.1.1 based and the other is 4349 based and the Warning and backtrace info. later in init.
This should help someone who knows what to look for.
Still trying and looking for help!
This is the kind of problem report that we'd like to see on the board, ie., one with log files and pertinent information.
Let's look at the important differences between the kernel messages. Lines prefixed with a '- ' are from the good kernel, and those prefixed with a '+ ' are from the bad kernel.
$ diff -u <(cut -d] -f2- JR_dmesg_GoodGtab.txt) <(cut -d] -f2- JR_dmesg_BadGtab.txt) | less
--- /dev/fd/63 2011-06-12 00:30:26.863474335 +0530
+++ /dev/fd/62 2011-06-12 00:30:26.943474334 +0530
@@ -1,6 +1,5 @@
- Initializing cgroup subsys cpu
- Linux version 2.6.32.9-00000-10.8.2-dirty ([email protected]) (gcc version 4.4.0 (GCC) ) #9 SMP PREEMPT Thu Oct 21 12:40:01 EDT 2010
- CPU: ARMv7 Processor [411fc090] revision 0 (ARMv7), cr=10c53c7f
+ Linux version 2.6.32.9-00001-g0e0c333-dirty ([email protected]) (gcc version 4.4.0 (GCC) ) #1 SMP PREEMPT Fri Jan 28 14:45:21 EST 2011
+ CPU: ARMv7 Processor [411fc090] revision 0 (ARMv7), cr=10c5387f
Click to expand...
Click to collapse
The good kernel was compiled in Oct 2010, and the bad one in Jan 2011 by the same person.
- Kernel command line: [email protected] [email protected] vmalloc=192M video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 cpuid=200102 devicetype=1002 btmac=95abe7131a00 tegraboot=nand mtdparts=tegra_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](bootbmp),[email protected](logodata)
+ Kernel command line: [email protected] [email protected] vmalloc=192M video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 cpuid=200102 devicetype=1002 bspversion=0202100907 btmac=9c5ed6131a00 tegraboot=nand mtdparts=tegra_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](bootbmp),[email protected](logodata) recoverykey=1
Click to expand...
Click to collapse
This is where it gets interesting. I've formatted the differences in the NAND flash partitioning schemes for better readability:
Good gTablet:
Kernel command line:
[email protected]
[email protected]
vmalloc=192M
video=tegrafb
console=ttyS0,115200n8
usbcore.old_scheme_first=1
cpuid=200102
devicetype=1002
btmac=95abe7131a00
tegraboot=nand
mtdparts=tegra_nand
16384K @ 7424K (misc)
4096K @ 24320K (bootbmp)
32768K @ 28928K (logodata)
16384K @ 62208K (recovery)
16384K @ 79104K (boot)
204800K @ 96000K (system)
222464K @ 301312K (cache)
Click to expand...
Click to collapse
Bad gTablet:
Kernel command line:
[email protected]
[email protected]
vmalloc=192M
video=tegrafb
console=ttyS0,115200n8
usbcore.old_scheme_first=1
cpuid=200102
devicetype=1002
btmac=9c5ed6131a00
tegraboot=nand
mtdparts=tegra_nand
4096K @ 7424K (bootbmp)
16384K @ 12032K (misc)
32768K @ 28928K (logodata)
16384K @ 62208K (recovery)
16384K @ 79104K (boot)
253696K @ 96000K (system)
173568K @ 350208K (cache)
recoverykey=1
bspversion=0202100907
Click to expand...
Click to collapse
1. The second message fragment indicates that the bad gTablet is one of the non-standard (because newer?) ones with the swapped (misc) and (bootbmp) partitions. Mine is the same, and as a consequence I have to be careful about which nvflash files I use. For this gTablet, make sure you use the nvflash zip file which has a '46_2010112600' in its name, instead of this version: 'nvflash_gtablet_2010110500'. This latter you can use on your good gTablet.
2. Here's my gTablet's NAND flash partition structure:
Kernel command line:
[email protected]
[email protected]
vmalloc=192M
video=tegrafb
console=ttyS0,115200n8
usbcore.old_scheme_first=1
cpuid=200102
devicetype=1002
btmac=9c5ed6131a00
tegraboot=nand
mtdparts=tegra_nand
4096K @ 7424K (bootbmp)
16384K @ 12032K (misc)
32768K @ 28928K (logodata)
16384K @ 62208K (recovery)
16384K @ 79104K (boot)
204800K @ 96000K (system)
222464K @ 301312K (cache)
androidboot.hardware=harmony
Click to expand...
Click to collapse
and you can see that there are differences compared to yours. Your system partition has been expanded in favour of the cache partition following it.
Q: Did you try to install Honeycomb on the bad gTablet? That would account for the size differences.
- 0x000005dc0000-0x0000125c0000 : "system"
- 0x000012640000-0x00001ff80000 : "cache"
- tegra_nand tegra_nand: Block 0x97c is bad [chip=0,offset=0x12f80000]
- tegra_nand tegra_nand: Block 0xe52 is bad [chip=0,offset=0x1ca40000]
- 0x0000017c0000-0x000001bc0000 : "bootbmp"
+ 0x000005dc0000-0x000015580000 : "system"
+ 0x000015600000-0x00001ff80000 : "cache"
+ tegra_nand tegra_nand: Block 0xd25 is bad [chip=0,offset=0x1a4a0000]
+ 0x000000740000-0x000000b40000 : "bootbmp"
0x000001c40000-0x000003c40000 : "logodata"
Click to expand...
Click to collapse
Looks like you have bad blocks on both gTablets affecting the cache partition in both cases. This is not unusual for this hardware--I've got a couple in my system partition.
Next. From the good kernel:
Open SDIO2
- tegra-sdhci tegra-sdhci.2: request en gpio failed
mmc1: Invalid maximum block size, assuming 512 bytes
mmc1: SDHCI controller on tegra-sdhci.2 [tegra-sdhci.2] using ADMA
tegra-sdhci tegra-sdhci.2: probe complete
-
- tegra_sdhci_probe complete
-
- tegra_sdhci_probe
Click to expand...
Click to collapse
I'm not sure what this is, but the SD card controller seems to finish ok.
Now, we get to the problem message:
- mmc2: new high speed MMC card at address 0001
- mmcblk3: mmc2:0001 MAG4EM 14.9 GiB
- mmcblk3: p1 p2
- mmc_rescan out
+ mmc2: error -110 whilst initialising SD card
Click to expand...
Click to collapse
The bad gTablet is unable to initialize the internal SD card (mmcblk3) for some reason. The -110 is actually a -ETIMEDOUT error, meaning, "Card took too long to respond" to a command.
This could either be a kernel problem (you have an old kernel) or a SD card hardware fault. Get pershoot's latest Froyo kernel and see if installing it fixes the problem. boot-cm_2632.41-oc-uv-xtra-vfpv3_fp-060311.zip for the 1.1 bootloader or boot-cm_2632.41_newbl-oc-uv-xtra-vfp_fp-060311.zip if you have the 1.2 bootloader.
If an updated kernel does not fix the problem, you can
a) either send the tablet back for replacement, or,
b) open that gTab up and replace the internal SD card--if it's in a removable socket--with another similar capacity (16GB) SDHC card. You could also try removing the card and cleaning the contact points.
rajeevvp said:
This is the kind of problem report that we'd like to see on the board, ie., one with log files and pertinent information.
Let's look at the important differences between the kernel messages. Lines prefixed with a '- ' are from the good kernel, and those prefixed with a '+ ' are from the bad kernel.
The good kernel was compiled in Oct 2010, and the bad one in Jan 2011 by the same person.
This is where it gets interesting. I've formatted the differences in the NAND flash partitioning schemes for better readability:
Good gTablet:
Bad gTablet:
1. The second message fragment indicates that the bad gTablet is one of the non-standard (because newer?) ones with the swapped (misc) and (bootbmp) partitions. Mine is the same, and as a consequence I have to be careful about which nvflash files I use. For this gTablet, make sure you use the nvflash zip file which has a '46_2010112600' in its name, instead of this version: 'nvflash_gtablet_2010110500'. This latter you can use on your good gTablet.
2. Here's my gTablet's NAND flash partition structure:
and you can see that there are differences compared to yours. Your system partition has been expanded in favour of the cache partition following it.
Q: Did you try to install Honeycomb on the bad gTablet? That would account for the size differences.
Looks like you have bad blocks on both gTablets affecting the cache partition in both cases. This is not unusual for this hardware--I've got a couple in my system partition.
Next. From the good kernel:
I'm not sure what this is, but the SD card controller seems to finish ok.
Now, we get to the problem message:
The bad gTablet is unable to initialize the internal SD card (mmcblk3) for some reason. The -110 is actually a -ETIMEDOUT error, meaning, "Card took too long to respond" to a command.
This could either be a kernel problem (you have an old kernel) or a SD card hardware fault. Get pershoot's latest Froyo kernel and see if installing it fixes the problem. boot-cm_2632.41-oc-uv-xtra-vfpv3_fp-060311.zip for the 1.1 bootloader or boot-cm_2632.41_newbl-oc-uv-xtra-vfp_fp-060311.zip if you have the 1.2 bootloader.
If an updated kernel does not fix the problem, you can
a) either send the tablet back for replacement, or,
b) open that gTab up and replace the internal SD card--if it's in a removable socket--with another similar capacity (16GB) SDHC card. You could also try removing the card and cleaning the contact points.
Click to expand...
Click to collapse
Thanks alot; you seem to have a handle on this stuff. Ya, I've tried the 46 route. I end up in what appears to be an APX loop in that case; although I did try it as you suggested.. and this time I did it fresh in linux (typically in windows). My tab could very well be newer. I got it fresh last month from tigerdirect and it came with 4349. I can give you the s/n if that might help. Damn, if I knew the SDCARD could be in a socket I would have paid more attention when I had it open. So, now I'm back to Roebeet's 4349 stock w/CWMOD. Not sure I can mount SD-EXT anymore (been a while since I tried) but if I can does it make sense for me to update the kernel with the one you suggest (I have it now). I assume I just put it on SD-EXT as update.zip and then use CWMOD to navigate to it... Any suggestion as to why I end up in APX loop with 46 and not the others; doesn't that mean that the non-46 is my 'mapping'? If you can help further I would appreciate it; just let me know what to try and what logs, captures etc. I was thinking to dump my entire good gtab and put that on the bad one; but I don't know if that makes sense nor how to do it completely. I know of the dump_flash etc. commands but that's only a piece. HELP STILL!!
how can i tell if I have one of the non std gtablets?
I have mount /dev/block/mmcblk0p2 file exists error when wiping dalvic. I dont have any of the other issues.
tjsooley said:
how can i tell if I have one of the non std gtablets?
Click to expand...
Click to collapse
1. Check the kernel messages.
2. Or, use nvflash to get your partitioning scheme.
I have mount /dev/block/mmcblk0p2 file exists error when wiping dalvic. I dont have any of the other issues.
Click to expand...
Click to collapse
That's a harmless diagnostic. See this post.
And, BTW, that is not the correct error message string. For any sort of troubleshooting, it would help if you supplied the exact error messages in your posts.
rajeevvp said:
1. Check the kernel messages.
2. Or, use nvflash to get your partitioning scheme.
That's a harmless diagnostic. See this post.
And, BTW, that is not the correct error message string. For any sort of troubleshooting, it would help if you supplied the exact error messages in your posts.
Click to expand...
Click to collapse
I get this "E:Can't mount /dev/block/mmcblk2p2
(File exists)" when trying to wipe Dalvik Cache.
How do I fix it.
I see the link and the information is helpfull but how do i fix it?
Same error when I remove the external microsd card and try to wipe Dalvik
jroger0707 said:
I assume I just put it on SD-EXT as update.zip and then use CWMOD to navigate to it...
Click to expand...
Click to collapse
Correct.
Any suggestion as to why I end up in APX loop with 46 and not the others; doesn't that mean that the non-46 is my 'mapping'?
Click to expand...
Click to collapse
I'm not a nvflash expert--I've never needed to do a full nvflash--but, I suspect it is because your gTablet came installed with the newer 1.2 bootloader and the newer NAND-flash partitioning scheme. Roebeet, who's probably seen more gTabs than the rest of us ever have, can comment on this.
For your SD card problems, try the latest pershoot kernel. If that doesn't work, I can compile a custom kernel for you. While trawling through the MMC device driver source in the kernel I saw an option, which, if enabled, might fix the detection of your SD card. The option is only there to support marginal and quirky MMC SD cards and so it's normally left disabled.
Note that if the custom kernel fixes your probem, it won't be a permanent solution, as you'll have to come to me every time you decide to upgrade the kernel (or you'll have to compile one yourself from pershoot's or clemsyn's sources).
tjsooley said:
How do I fix it.
I see the link and the information is helpfull but how do i fix it?
Click to expand...
Click to collapse
1. Hardware fix: Always have an SD card with 2 partitions in the external SD card slot.
2. Software fix : Modify the ClockworkMod source so it doesn't print an error message if the second partition does not exist on the external SD card (or there is no SD card in the external slot).
3. User fix: Just ignore it.
rajeevvp said:
1. Hardware fix: Always have an SD card with 2 partitions in the external SD card slot.
2. Software fix : Modify the ClockworkMod source so it doesn't print an error message if the second partition does not exist on the external SD card (or there is no SD card in the external slot).
3. User fix: Just ignore it.
Click to expand...
Click to collapse
Thanks, Why would it come up one? it did not before.
I have a 16gb micro sd in the ext slot.
tjsooley said:
I have a 16gb micro sd in the ext slot.
Click to expand...
Click to collapse
Does it have 2 partitions on it? The first one a VFAT partition and the second an ext3 partition?
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 for [TOOL][NABI2] NabiLab - Root, Play, Recovery
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 [TOOL][NABI2] NabiLab - Root, Play, Recovery. 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!
State of Nabi 2 Root as of 12/14?
So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.
So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
Eyebolt said:
So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.
So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
Click to expand...
Click to collapse
Nabilab will still work as long as you use a version with a Jellybean TWRP(since you are on 2.4.6).
katinatez repackaged it for jellybean here:
http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
Sent from my Nexus 5 using XDA Free mobile app
jaxbierley said:
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For the sake of anyone else looking for this information we are discussing it at the main Nabi thread starting at post #2477
http://forum.xda-developers.com/showthread.php?t=1905674&page=248
Stock Restore
Hi
I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
Firepants said:
Hi
I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
Click to expand...
Click to collapse
What version of software? Use Nabilab2015 http://forum.xda-developers.com/showpost.php?p=59073456&postcount=2544
It has more diagnostic info. Just be in Android or TWRP with ADb enabled. It also can see if drivers are loaded.
Hacking Nabi2 to Allow Data2SD
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
ashahin1 said:
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
Click to expand...
Click to collapse
If you are not sure which line to change, I have the fstab.mt799 file attached with this post. You can simply replace your file with this one.
ashahin1 said:
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
Click to expand...
Click to collapse
If you don't have the time to do all these steps, I have the modified boot file attached here.
Yo can either follow steps 7 and 8 above to write it, or use the fastboot command as follows:
Code:
fastboot flash boot new_boot.img
Nabi2 not found
Hi, I purchased a reconditioned Nabi, which was reset back to stock. The wifi worked fine, until I updated it through the tablet. I am now on version 2.0 with no wifi. I have tried various options through NabiLab , however my Nabi is not recognised as being connected (although windows picks it up). Please help!
Swipe to restore
I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
Aytul said:
I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
Click to expand...
Click to collapse
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.
did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
n3wt said:
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.
did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
Click to expand...
Click to collapse
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?
I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
Aytul said:
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?
I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
Click to expand...
Click to collapse
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
n3wt said:
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
Click to expand...
Click to collapse
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
Aytul said:
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
Click to expand...
Click to collapse
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
n3wt said:
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
Click to expand...
Click to collapse
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
Aytul said:
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
Click to expand...
Click to collapse
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
n3wt said:
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
Click to expand...
Click to collapse
Hi, I bought it as a reconditioned did unit. Turned it on, updates it (wifi worked) and then had this problem, so no backup to go back to unfortunately
Hi All,
Android Lolipop 5.1.1
features
Android 5.1.1
kernel of badadroid
change or delet Some app
smooth
stable
Battery is very good
Downloads
v8
http://www.mediafire.com/download/qhuk4ypwhialp21/omni+5.1.1+LionDroid+V8.zip
V7
http://opizo.com/N1ATZ
V6
http://opizo.com/Xakla
V4
http://opizo.com/F2bZr
V3
http://opizo.com/J1PpH
V2
android 5.1.1
http://opizo.com/f2eWy
V1.1
http://opizo.com/nHkIT
2015/02/25 Initial release
http://opizo.com/A2Tvt
changelog ROM
better battery & smoother
more optimization
more speed & free ram
more stable
update source
and other...
INSTALLATION
FIRST INSTALLATION
Bada 2.0 is required
Warning! It will remove Bada!
Download BOOTFILES, Kernel and FOTA for your device:
for 8500:
BOOTFILES https://yadi.sk/d/KhxqKyg4bP2nu
"start" kernel https://yadi.sk/d/ilhyKTaEfTo6L
FOTA https://yadi.sk/d/OtpVoaXpfNggE
for 8530
BOOTFILES https://yadi.sk/d/cBPD41VEbP2od
"start" kernel https://yadi.sk/d/wVGzUA96fGW55
FOTA https://yadi.sk/d/-WnbHbFHfNgZK
Flash BOOTFILES, "start" kernel and FOTA using Multiloader.
After reboot it will open android recovery
Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait before on screen you will see "Partitions had been prepared"
Back -> Back -> Back -> Reboot -> Recovery -> Swipe to Reboot
Mount -> Enable MTP (if you see disable MTP - it is already activated) on this step PC can ask to install driver, use Android MTP driver
Copy Zip with ROM to Internal Storage or Sdcard -> Disable MTP -> Back
Install -> choose zip with ROM(mount point /sdcard for Internal storage and /external_sd for SD card) -> Swipe to Confirm Flash
Wait for flashing (about 10 min) -> Reboot System
First start take about 10-15 min, be patient.
Enjoy OMNI!
ROOT
Omni is without root support from default
To activate root flash zip via Recovery from XDA thread http://forum.xda-developers.com/showthread.php?t=1538053
GAPPS
GAPPS make our ROM slowler, because also slim GAPPS take about 15-20 MB RAM permanently
https://mega.co.nz/#F!G0QXXRAC!pZ063qCaa5lxdD73SarU6Q
Thanks to
volk204 [for any things]
omni team
code rom team
@jeffreyvh
Rebellos
blue59
hero355
Tigrouzen
Benzox
and other Badadroid devs
reserved ....
first build android 5.1.1 but very Slow
now build android 5.0.2 smoother and more ram
please test rom and tell me bug
thnaks
good news!!!!!!
Sent from my GT-P5100 using Tapatalk
thank you nima
new version uploading ....
edit: uploaded
Thanks for your dedicated work to support the Waves!
One question: Will updating from Omni4.4 work in the same manner as described here?
Renth said:
Thanks for your dedicated work to support the Waves!
One question: Will updating from Omni4.4 work in the same manner as described here?
Click to expand...
Click to collapse
your welcome
Yes, the same is
nima.yavari said:
your welcome
Yes, the same is
Click to expand...
Click to collapse
Thanks again. Forgot to ask: Will it remove Bada and all its contents or stay in parallel like the OMNI does?
And is there a list of problems/missing features or similar regarding this version?
Renth said:
Thanks again. Forgot to ask: Will it remove Bada and all its contents or stay in parallel like the OMNI does?
And is there a list of problems/missing features or similar regarding this version?
Click to expand...
Click to collapse
remove Bada and all its contents.But then returned Flash Bada
i can't found bugs
features on post 1
nima.yavari said:
remove Bada and all its contents.But then returned Flash Bada
Click to expand...
Click to collapse
Thansk again. That's a little bit of a pitty since I am still regularly using Route66 navigation of Bada (bought the lifelong version) - did not find any reliably and suitably working free offline Android navi app.
Unfortunately I cannot copy over the zip when mounting the USB from recovery, in Windows Vista it is only shown as %SingleADBInterface% so I cannot copy data onto it.
Is there any way to get this fixed? Search in Google and here did not help yet (still investigating).
Ok. Managed to copy it via ADB push but cannot install: Flashing gives error:
executing updater ... failed
and before
failed to mount dev/lvpool/system ... ... ..at /system no such file or directory AppliedParsedPerms: ... removeexeattr of /system/binbackuptool.sh to 0 failed: operation not supported on transport endpoint
ß
When copying the zip into / folder I get:
Unable to find partition for path /omni 5.0.2 LionDroid V1.1.zip
Anything I can do here? Do I have to copy the .zip file to a special place? Or do I have to extract the boot.img and copy it separately (since the one in the 5.0.2 Liondroid is different from the one of OMNI4.4.4 which is currently on my S8500)?
Currently I've got the OMNI4.4.4 on SDCard, booting from SDCard. So I have not /external_sd as a directory. So maybe I need to set something as mountpoint (if so - how?) or have to copy the ROM ZIP to another place?
Renth said:
Thansk again. That's a little bit of a pitty since I am still regularly using Route66 navigation of Bada (bought the lifelong version) - did not find any reliably and suitably working free offline Android navi app.
Unfortunately I cannot copy over the zip when mounting the USB from recovery, in Windows Vista it is only shown as %SingleADBInterface% so I cannot copy data onto it.
Is there any way to get this fixed? Search in Google and here did not help yet (still investigating).
Click to expand...
Click to collapse
Renth said:
Ok. Managed to copy it via ADB push but cannot install: Flashing gives error:
executing updater ... failed
and before
failed to mount dev/lvpool/system ... ... ..at /system no such file or directory AppliedParsedPerms: ... removeexeattr of /system/binbackuptool.sh to 0 failed: operation not supported on transport endpoint
ß
When copying the zip into / folder I get:
Unable to find partition for path /omni 5.0.2 LionDroid V1.1.zip
Anything I can do here? Do I have to copy the .zip file to a special place? Or do I have to extract the boot.img and copy it separately (since the one in the 5.0.2 Liondroid is different from the one of OMNI4.4.4 which is currently on my S8500)?
Currently I've got the OMNI4.4.4 on SDCard, booting from SDCard. So I have not /external_sd as a directory. So maybe I need to set something as mountpoint (if so - how?) or have to copy the ROM ZIP to another place?
Click to expand...
Click to collapse
It is a bad copy
you can't copy files on recovery
go to bada or with ram reader and copy .zip
after go to recovery and install rom
nima.yavari said:
It is a bad copy
you can't copy files on recovery
go to bada or with ram reader and copy .zip
after go to recovery and install rom
Click to expand...
Click to collapse
Already tried this (copied within Bada) when I posted/edited my entries above - the error keeps the same - I cannot install this ROM (I used the one from V1.1 download)! Do I have to copy it on a certain place?
I took the OMNI4.4.4 from here (German only) which leaves Bada unharmed and completely runs from SD card. I managed to install that version again after wiping but whenever I try to install the version from here I get this very long cryptical error message from above (the one ending with "operation not supported on transport endpoint").
Since the boot.img of OMNI4.4.4 is different from the one contained in the OMNI5.0.2 here. Do I have to extract and copy it manually before trying to flash this rom here?
Ok, tried that but it damaged Bada installation and also Android did not work anymore. Had to flash a Bada update version and my previous OMNI4.4.4 FOTA to restore everything.
Any hints appreciated (cannot get rid of this cryptic error)!
Renth said:
Already tried this (copied within Bada) when I posted/edited my entries above - the error keeps the same - I cannot install this ROM (I used the one from V1.1 download)! Do I have to copy it on a certain place?
I took the OMNI4.4.4 from here (German only) which leaves Bada unharmed and completely runs from SD card. I managed to install that version again after wiping but whenever I try to install the version from here I get this very long cryptical error message from above (the one ending with "operation not supported on transport endpoint").
Since the boot.img of OMNI4.4.4 is different from the one contained in the OMNI5.0.2 here. Do I have to extract and copy it manually before trying to flash this rom here?
Ok, tried that but it damaged Bada installation and also Android did not work anymore. Had to flash a Bada update version and my previous OMNI4.4.4 FOTA to restore everything.
Any hints appreciated (cannot get rid of this cryptic error)!
Click to expand...
Click to collapse
full flash bada
format memory to fat32
flash fota and start kernel and bootfile JUST for this rom
now go to recovery Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait before on screen you will see "Partitions had been prepared"
Back -> Back -> Back ->wipe every thing without external ->Swipe to wipe
now you can install rom
nima.yavari said:
full flash bada
format memory to fat32
flash fota and start kernel and bootfile JUST for this rom
now go to recovery Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait before on screen you will see "Partitions had been prepared"
Back -> Back -> Back ->wipe every thing without external ->Swipe to wipe
now you can install rom
Click to expand...
Click to collapse
Meanwhile I already did so. Partitioning worked, installation worked but after reset Wave only shows its startscreen (Samsung Wave GT-S8500 in white letters) for about 15 minutes now and nothing happens (besides Wave getting really warm, nearly hot). Also restarting the wave does not change anything!
Anything else I can try? Do I have to checkmark Master Rom in Multiloader?
Renth said:
Meanwhile I already did so. Partitioning worked, installation worked but after reset Wave only shows its startscreen (Samsung Wave GT-S8500 in white letters) for about 15 minutes now and nothing happens (besides Wave getting really warm, nearly hot). Also restarting the wave does not change anything!
Anything else I can try? Do I have to checkmark Master Rom in Multiloader?
Click to expand...
Click to collapse
sure flashed fota this rom?
wave 1 or 2?
nima.yavari said:
sure flashed fota this rom?
wave 1 or 2?
Click to expand...
Click to collapse
It is Wave 1. Yes I flashed all 3 parts: Bootfiles, FOTA and kernel. But not sure what to checkmark in Multiloader. Decided to go with Master Rom.
Meanwhile tried a 2nd time with full flash of bada + the wipe you mentioned (but no formatting of SD since it already has been for OMNI4.4.4). Still no change. Everything worked fine but Wave stays in Start Screnn (Samsung Wave GT-S8500 in white letters) for 20 minutes now - just getting very warm.
And now? Doesnt seem to work for my devive.
Renth said:
It is Wave 1. Yes I flashed all 3 parts: Bootfiles, FOTA and kernel. But not sure what to checkmark in Multiloader. Decided to go with Master Rom.
Meanwhile tried a 2nd time with full flash of bada + the wipe you mentioned (but no formatting of SD since it already has been for OMNI4.4.4). Still no change. Everything worked fine but Wave stays in Start Screnn (Samsung Wave GT-S8500 in white letters) for 20 minutes now - just getting very warm.
And now? Doesnt seem to work for my devive.
Click to expand...
Click to collapse
to multiloaeder just chek bootfile / rc1 / fota
nima.yavari said:
to multiloaeder just chek bootfile / rc1 / fota
Click to expand...
Click to collapse
For flashing bootfiles you need either checkmark "Boot Change" or "Full Download" in Multiloader. Otherwise Boot will be grayed out.
But as said - already did so 2 times: Flash Bada (Full flash at 2nd time), wiped everthing (2nd time) partitioned everything, flashing omni5.0.2. Everything worked but wave1 stays in Startscreen forever afterwards. Neither bada nor android starts at all.
Any idea on how I can support hunting down this problem?