Related
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?
[ROM] CM7 8GB &16GB Compatible Beta for the Nook Tablet.., Updated 7th July to Beta
***** DISCLAIMER ******
Please note this software is still classed as experimental and you use this at your own risk. We have done some in house testing and all has worked fine but we cannot guarantee the exact same results for everyone. We accept no responsibility for any damage or loss of information with your Nook Tablet. You use this software at your own risk. By choosing to download and install this software on your device you accept that you are willing to risk your own device and that any damage and or total loss is your own responsibility.
FOR PROGRESS AND UPDATES CONTINUE TO READ THIS THREAD. FOR KNOWN BUGS AND ISSUES PLEASE SEE THIS THREAD
Below you will find Internal release of our Nook tablet CM7. This has been rebuilt from the most recent CM7 stable source. I'll update the 2nd posts with release information asap.
Please feel free to base your rom on ours, I believe it is now tested well enough and is sufficiently stable to use.
The Source for the CM7 android device folder, the kernel and meghd00ts Improved recovery can be found here Here
For information on what you can and can't do and reasons for this please visit HERE
INTERNAL VERSION 8GB & 16GB COMPATIBLE
Download HERE MD5 95043b08484aa218ccf93b5ef4785825
For the internal version you need have access to CWM either internally installed as your recovery or from an SD card. I'm not going to reinvent the wheel telling people how to do that. Just have a look through the development thread and you'll se numerous threads showing you how to do this.
This version has the ability to reboot to recovery added to the reboot option in the power menu. It does not however come with a recovery image, this was already released by lavero.burgos and can be downloaded from http://forum.xda-developers.com/showthread.php?t=1640958
PLEASE BACK EVERYTHING UP BEFORE YOUR BEGIN!!!!
Once you have CWM on screen with the downloaded update zip archive on your sd card, Follow these simple steps
1. Goto install zip from sdcard
2. Choose zip from sdcard ( if CWM hasn't recognized your SD card you need to eject it and re insert it once or twice, sometimes you need to go to mounts and unmount SD, pop it out and back in then select mount sd)
3. choose the CM7-TEAM-B-BETA1-signed.zip
4. scroll down and select Yes - Install CM7-TEAM-B-BETA1-signed.zip
5. sit back for a couple of minutes while the installation is carried out
That’s CM7 installed, next you need to prepare the rest of the device
1. press your power button once
2. ***OPTIONAL*** scroll down and select wipe data / factory reset, this is optional but if you are coming from a different OS it is recommended, if you don't it can sometimes causes force closes and various other issues.
3. you're ready to roll! scroll up and select reboot system, initial boot can take a while and does pause for a short while on the black screen between flash page and CM7 Animation, enjoy CM7 For Nook Tablet!
if you were already running a version of CM7 it is possible you may be able to skip the wipe data bit and just select wipe cache instead but it's best if you can wipe data and know that you have a clean install without any bugs remaining from a previous install. By all means try just clear cache and see how you go, if you seems to have lots of bugs we recommend doing a clear data and trying again.
SD VERSION IMAGE ***UPDATE NOT YET AVAILABLE this is the Alpha final version***
Download HERE
I've done the SD version a little different this time, it's as a 4gb SD image (the last partition is used as SDcard in CM7 so you can resize this partition to fill up your whole card if your card is bigger than 4gb). The image can be burn using windows Image writer or dd command in linux / OSX
The window software is available HERE.
To write the image on linux / osx do the following
WITHOUT your sd in the machine go to a terminal window and type
Code:
mount
Notice the drives that are showing they will be something like dev/sda. Now insert your SD and give it a moment to recognise it. Once again terminal type
Code:
mount
and you should have an extra device such as /dev/sdc showing which is your sdcard (it may say dev/sdc1 or something but you aren't interested in the number)
Once you have the SD device id use following code exchanging sdc for your device id
Code:
dd if=/location/of/SDfile.img of=/dev/sdc
Then sit back and wait, it will appear to be doing nothing and will take a long time but once done the command will complete and you have a nice new SD version of CM7 to run
Power off the nook, insert the sd and then power it on to enjoy your new CM7. If it done'st boot try completely powering of and ten connect power cable and wait for it to turn on and hopefully boot form SD. The first boot WILL take a few minutes. Consecutive boots will be faster
We've been asked a number of times for a donation link so I set one up you can click HERE. Or if you prefer to donate directly to myself or Goncezila by clicking on the donate buttons under our names. We thank you in advance for your generosity
***** DISCLAIMER ******
Please note this software is still classed as experimental and you use this at your own risk. We have done some in house testing and all has worked fine but we cannot guarantee the exact same results for everyone. We accept no responsibility for any damage or loss on information with you Nook Tablet. You use this software at your own risk.
First boot can take a little while. once in you will be requested to enter your Google account details, because your wifi is not yet connected you will be better of skipping these steps, you will be asked again as soon as you try to open Google Market anyway.
Tap the menu button and select settings (not adwsettings) go to wifi and setup your wifi connection, if for some reason wifi networks do not show, just toggle wifi off and on and it will sort it's self out
Feedback thread HERE so please make sure you post any questions and / or feedback in there and keep this thread for development only. Thank you!
Thanks and mentions
All those that support the new release, I'm sure you all know who you are
Quid246 - for his skills in photoshop to make our new splash screen (Alpha release)
Bauwks - Without him we would not be here. He blew the top off the bootloader and his thanks bar is no where near what it should be. Also a thank you for him agreeing to allow us to change his box image on the bootloader when we asked. Please find some of his posts and hit Thanks!
Loglud - again for helping us out with our research
AdamOutler - His guide was used to help us with kernel issues and build our SDcard version
succulent for pointing out that although we had commented out a file in the build, it was was still possible it was effecting up our new build. Also thanks to succulent for creating a build script that automatically added the 2nd boot onto the boot.img during source build. Thank Succulent! You’re a star, it just wasn't happening when I tried to do it
The Cyanogen Mod team for the initial build of Cyanogen mod that we ported over
Generally every other member of XDA - For being so supportive and throwing out ideas and experience!
Know issues, Hints and Tips
keyboard numbers layout when you hold a letter doesn't initially work, to fix just change keyboard language to your local setting e.g. US english
PROGRESS UPDATES
7th July 2012
Released beta update built on latest Stable CM7 source
Made some changes which will hopefully help with wifi issues
added some stability fixes
Added reboot to recovery in the reboot menu
Other minor issues tweaked to improve general overall performance and response
MARCH 20th{/I]
build.prop update zip added to support thread to cure mounting on USB issues
MARCH 9th
CM7 Final Alpha released
A complete relbuild of CM7 for the Nook Tablet. The new version is based on Gingerbread 2.3.7 CM7.2
All software updated to latest CM7.2 version and all files rebuilt to match
Full hardware video decoding for h264 encoded videos
Hardware acceleration for gfx
Wifi issues fixed so now connection should work without crashing
GAPPS removed as per Google requests and GAPPS download link added to OP
Many general system bugs fixed
Much much more that ill post here when home from vacation
MARCH 7th 2012
SD version of CM7 re-released
MARCH 5th 2012
Sorry for the lack of updates recently, Gonc and I have been really busy but we're happy to say a new build has been getting tested personally by us and has now been passed on to the testing team.
Bit more about it is HERE
FEB 19th 2012
2nd public release of CM7 for Nook Tablet.
Changes since original version are:
Format bricking issue fixed
Boot count issue where it resets your device to standard after 8 boots fixed
Market should now install any software you can get on there without the SD / USB issue
Browser should now happily play videos from mobile youtube
Graphics driver update allows playing of YouTube videos a720p without issue
Previous issues updating BusyBox should now be cured
Many games and applications that crashed on intro video will now work flawlessly
Internal media partition now fully accessible
internal media and sdcard now show when connected to USB on computer
more things which I'll add here when I remember them!
Feb 12th 2012
The new build which is alpha 8 is now ready and testing will begin in the next day or two.
Thanks to all members of the team for volunteering and to xIndirect for setting up the application forms online that everyone filled out to become members and the bug report forms he's also set up.
Goncezilla and I haven't really discussed a length of time for testing but generally Testing will continue until we believe that the remaining bugs do not cause severe problems for the end user. Once we are at that stage the donators will then get their copies which will allow us to gradually increase the testing coverage before finally being released as a beta to all member of XDA.
Myself and Goncezilla would like to take this opportunity to thank everyone for their support and understanding while we build you a version of CM7 for your Nook Tablets that we can be proud of
Feb 10th 2012
Following bugs have been fixed
SD format and bricking issue,
Market app install problem
Various software crashing when it tried to play video (even browser in mobile youtube)
Internal Media partition not mounting
Media partition not connecting to USB host when plugged in
Further information on updates and release are available HERE
Difference
Sorry for this question. What are the differences between internal and external? Does internal completely wipe and remove all Nook software, and external only boots CM7 with the card in and boots Nook style without?
For those on Windows machines (like me!), the free Mini Partition Wizard Home Edition can be used to create the SD card partitions. In this case just make the first partition Primary and Active; that will allow it to be seen as a bootable partition.
joeras said:
Sorry for this question. What are the differences between internal and external? Does internal completely wipe and remove all Nook software, and external only boots CM7 with the card in and boots Nook style without?
Click to expand...
Click to collapse
For Internal you need to have CWM running (either from SDcard or internally) and it WILL wipe your stock setup.
External runs purely from the SDCard and will not mess with your internal data.
Remember that Celtic and I are the only ones who have tested this as of yet so there may be unfound bugs! This is Beta after all
Please report all bugs here, do not PM us. We will try to validate and then correct them.
Enjoy everyone!
tonyp22 said:
For those on Windows machines (like me!), the free Mini Partition Wizard Home Edition can be used to create the SD card partitions. In this case just make the first partition Primary and Active; that will allow it to be seen as a bootable partition.
Click to expand...
Click to collapse
Yes sure just shrink the partitions a little to fit
We'll be adding a small modification to allow SDCard simulation when booting form card which will require adding a 4th partition later to act as the SDCard
Just thought to release as was to get it to everyone
I take it there is a way to go back to stock 1.4.0 just in case?
Unit is rebooting into cm7 as we speak. Looking great, speed is awesome. Great job guys.
arclite00 said:
I take it there is a way to go back to stock 1.4.0 just in case?
Click to expand...
Click to collapse
Yes you can flash a stock image the same way
did internal version. Downloaded to PC, unpacked, copied directly to directory via usb mount, restored. The restore went fast, and the initial boot-up was faster than my G2's backup restores...lol Connected to wifi, signed in, and up and running.. Fantastic!!! kudos!! and i used the "Thank You" button so i'm not thanking you in this reply...<snicker> Over all, everything done in less than 5 minutes. Now to tweak/customize/play with.
For those of us who don't know/have ubuntu, can you point to a good resource/post for creating the SD card under Windows 7 to run the SD card version of CM7?
Thanks!
If I don't see a clockworkmod folder I assume it installed wrong or I create the folder?
offlimitz said:
If I don't see a clockworkmod folder I assume it installed wrong or I create the folder?
Click to expand...
Click to collapse
I'm pretty sure Clockworkmod makes it as standard, as long as you have clockworkmod installed you should be able to just create the folders and drop your files in, do a backup from CWM and the folder should appear anyway
Thanks man. downloading sd release now. this doesn't affect the stock NT rom, right? the SD release ofc.
Celtic,
You may want to mention that the user may need to eject/reinsert the SD card for CWM recovery to recognize it.
Thanks for the good work!
darthvince said:
Celtic,
You may want to mention that the user may need to eject/reinsert the SD card for CWM recovery to recognize it.
Thanks for the good work!
Click to expand...
Click to collapse
I'll post that in first thread now.
Know-Fear said:
Unit is rebooting into cm7 as we speak. Looking great, speed is awesome. Great job guys.
Click to expand...
Click to collapse
After it's first boot it's a lot quicker than stock
In fact I think even the SD version is faster than stock, stock really is poor!
Just an FYI to everyone. We mounted the internal B&N partition (the 11 GB that used to locked out) to /data/media and the 1GB you used to have access to to /mnt/media.
Both fully rw!
Holy **** people!! 200 downloads already and only 20 of clicks of thanks on the first thread :s
I think my server bandwidth is going to get a hammering, I best check it's ok!
Sorry for the basic question, but when we go to CWM -> Advanced restore -> NTCM7, do we want to restore boot? system? data? cache? sd-ext? all?
Thanks!
This build is ported from http://forum.xda-developers.com/showthread.php?t=1867986 using Portadroid forum.xda-developers.com/showthread.php?t=1094372 Credits and thanks to Rick_1995, boonbing for Portadroid, cyanogenmod, cmhtcleo team (arif-ali, milaq, charansingh and all other cm developers) for device tree, tytung for kernel, Darkstone1337 for SuperRAM concept, and any others we forgot.
Instructions:
Well you know just extract everything and put the build folder (the one with all the files in, for example ics, jelly) in the root of your sd card. If WM6.5 tap on clrcad (nothing appears to happen) then haret, if magldr navigate to build folder using ad-sd dir and select build folder name then boot AD SD.
Please remember to REBOOT X 3.
Magldr users can get different sized blank data.ext4 from here forum.xda-developers.com/showpost.php?p=24930501&postcount=1353 edit; may get boot loops, please test. Magldr default=512Mb if you leave empty. edit2 here is blank 256mb one http://www.mediafire.com/?ey40c1wti77ni2w
Downloads
Barebone CM7 V3 -Latest SuperRAM build from Rick_1995 see this post http://forum.xda-developers.com/showpost.php?p=42007074&postcount=64
note that this is not a port from nand rom, but an exclusive SuperRAM build from Rick_1995
There is a problem for magldr users changing lcd density, a solution is posted here http://forum.xda-developers.com/showpost.php?p=47161712&postcount=78 (thanks to Calisto1986 for the heads up). HaRET users are unaffected and can edit startup.txt as usual
Barebone CM7 V2b SRAM
DEV-HOST LINK
Barebone CM7 V2 SRAM
DEV-HOST LINK
Barebone CM7 SRAM
DEV-HOST LINK
This is from parent thread by Rick_1995
Note: I compiled this rom for myself but figured sharing won't hurt, and hence I don't plan to provide much support though I'll see what i can if you find a bug.
What is the difference between this and the nightly ?
All libraries and native code is compiled in ARM mode (except for libwebkit which is still in thumb mode due to it's excessive size) and compiler side optimization is turned on (again, exception being libwebkit using -Os and sqllite using -fno-fast-math).
Important function calls and syscalls are aligned for faster response time.
I re-implemented some of the cpu atomic functions based on what I've learned so far, swp is used for atomic swap instead of ldrex/strex, register swapping of old value is done at success so if a context switch does occur, the loop will be aligned at the same boundary as the function. On best case, there shouldn't be any difference but can improve execution time for worst case of context switches.
Java libraries and bionic libc are compiled with NDEBUG, and the debug variable for java is also set to false.
Most crap (stuff that "I" do not use, has been removed ie. VPN, live wallpaper support etc..)
Fixed a few memory leaks in bionic, dalvik and ppp (also tether).
I've removed most locales except en_US and en_GB, though android still seems to be compiling strings from other languages in the build, so they might work but i can't guarantee anything with locales other than en_(US|GB). Arabic patch
Reverted the patch which auto closed notification bar when all notifications are canceled/removed. It was irritating me..
more stuff i don't remember.
For now the kernel is tytungs-r1 ics kernel patched for gingerbread, though I will be patching/updating and working on the cmhtcleo kernel once i have the build known to be bug free after some time.
Click to expand...
Click to collapse
One more............
thans wiss....very quick port ....
Touch selection sound does not work for me.... others looks good so far...
Is it possible to run SD build from CLK? Just dont wanna install MAGLDR again, it`s so terrible for compability with Linux
Just get new micro sd card from SanDisk, its class 10, 95 mb per second -- its the most speediest micro sd in the world (micro SDHC UHS-I Card: Extreme Pro 8 GB)
Update: I`ve installed this rom twice with custom size about 4096 but everytime ive got near 512 mb. WHY?
aion92 said:
Is it possible to run SD build from CLK? Just dont wanna install MAGLDR again, it`s so terrible for compability with Linux
Just get new micro sd card from SanDisk, its class 10, 95 mb per second -- its the most speediest micro sd in the world (micro SDHC UHS-I Card: Extreme Pro 8 GB)
Update: I`ve installed this rom twice with custom size about 4096 but everytime ive got near 512 mb. WHY?
Click to expand...
Click to collapse
Because you're not setting proper command line, if you're booting from magldr, you just can't do this. If you're booting from clk, while creating boot image, set the cmdline exactly as in startup.txt and modify the partition size then flash that to a secondary boot partition, now just boot on secondary boot partition for the SD rom. I think suspend wasn't working properly with clk on sd roms, have to see why.
If it's from haret (unlikely) just edit size in startup.txt
@wis, thanks for the port, might use it sometime in the future when i try the new WP builds
Thanks Rick_1995 and Learning Never Ends team for this GREAT ROM!
I tried to change the LCD density in the system.ext4/build.prob. 192 is shown if i open the /system/build.prob in root explorer but this doesnt effect the rom... What can i do to set it to 192?
Thanks Wis (although I think you should be concentrating on something outside xda!).
Any advice on how to get option for "Corporate" Accounts?
This could be my favourite
Cheers
Tom
Sent from my HTC HD2 using Tapatalk 2
Please make this ROM compatible with NativeSD mod. Cm7 is the most perfomance android series for me, for now...
aion92 said:
Please make this ROM compatible with NativeSD mod. Cm7 is the most perfomance android series for me, for now...
Click to expand...
Click to collapse
Hmm... I may be wrong here, but from my understanding...
The NativeSD method writes to partitions on an SDCard...
SuperRAM ROMS mount to RAM which is faster than both NAND and SDCard...
So I would assume by modifying this to use NativeSD would be more detrimental than good?
yep, RAM is faster but, for my needs, more free RAM better than overall speed and this rom\Android build eats as little RAM as possible, so its just great rom which perfactly fits for my needs but NativeSD gives me internal storage (up to 32 gigs from 512 mb) and it can be launched from CLK loader.
aion92 said:
yep, RAM is faster but, for my needs, more free RAM better than overall speed and this rom\Android build eats as little RAM as possible, so its just great rom which perfactly fits for my needs but NativeSD gives me internal storage (up to 32 gigs from 512 mb) and it can be launched from CLK loader.
Click to expand...
Click to collapse
For your internal storage needs (NativeSD's "internal" storage is determined by your ext partition size, you still require fat partition with nativesd, so, unless you have a 64gb card working with your hd2, you likely wouldn't have 32gigs "internal") you can resize your data.img file to whatever size you like. You can use the tool "Toporesize" I believe it's called, or something like that. Also, you can investigate other scripts to install such as Apps2sd.
Other than that, the only thing to tell you is that as of right now, from my understanding, the NativeSD method requires certain kernel mods apparently, which means it's limited to ics/jb builds for now.
Version V2 please!This is great, thanks:good:
strikelight said:
For your internal storage needs (NativeSD's "internal" storage is determined by your ext partition size, you still require fat partition with nativesd, so, unless you have a 64gb card working with your hd2, you likely wouldn't have 32gigs "internal") you can resize your data.img file to whatever size you like. You can use the tool "Toporesize" I believe it's called, or something like that. Also, you can investigate other scripts to install such as Apps2sd.
Other than that, the only thing to tell you is that as of right now, from my understanding, the NativeSD method requires certain kernel mods apparently, which means it's limited to ics/jb builds for now.
Click to expand...
Click to collapse
Ok, thanks, I`ll try expand my storage with "Toporesize" then.
Update: after some researching ive managed to have 4 gigs of storage even without toporesize - with MAGLDR startup.txt config of 4096 gb does nothig for me earlier, but with sboot + CLK it works great! My problem is solved, yay!
Update2: aaand... after 1 reboot the rom just doesnt boot at all ... ill try to install one more time then.
Barebone CM7 V2 SRAM
Barebone CM7 V2 SRAM is now on post 1:good:
So, every time when i make a reboot or shut down from working rom, the data.ext4 clean itself to 0 bytes. I use CLK + sboot \ sboot tools, 4096 mb automatic generated data file. Any ideas?
Strychnin said:
Thanks Rick_1995 and Learning Never Ends team for this GREAT ROM!
I tried to change the LCD density in the system.ext4/build.prob. 192 is shown if i open the /system/build.prob in root explorer but this doesnt effect the rom... What can i do to set it to 192?
Click to expand...
Click to collapse
As this a super ram version you need to change it in a special way but for the life of me i cant remember howlol
When Robbie reads this im sure he will post the instructions
Sent from my HTC HD2 using Tapatalk 2
This is so great project but why not releasing NativeSD version? Such minimal ROM would act routinely writing on SD much less than Paranoid or AOKP so it seems ideal SD-born! This way we could have fast SD Android for regular use dual booted with WM like Artemis (which is still maintained) thus yielding the fastest and the most versatile smartphone of the world!
ictimai said:
This is so great project but why not releasing NativeSD version? Such minimal ROM would act routinely writing on SD much less than Paranoid or AOKP so it seems ideal SD-born! This way we could have fast SD Android for regular use dual booted with WM like Artemis (which is still maintained) thus yielding the fastest and the most versatile smartphone of the world!
Click to expand...
Click to collapse
At the moment there is no surport for cm7 but i dont think it will be long
Sent from my HTC HD2 using Tapatalk 2
wis1152 said:
As this a super ram version you need to change it in a special way but for the life of me i cant remember howlol
When Robbie reads this im sure he will post the instructions
Sent from my HTC HD2 using Tapatalk 2
Click to expand...
Click to collapse
:laugh:
edit line in /bootsystem/build.prop ro_lcd_density=240 to whatever using a root browser, and reboot.
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
Hi,
I have been recently working on ways to boot AA 11 in Raspi 4 (4 GB) via manual build. Having followed all steps till build, when creating partitions and flashing each individual image to the partition
1. SDX1 -> boot files (manual copy setting boot flag)
2. SDX2 -> linux partition -> system.img
3. SDX3 -> linux partition -> vendor.img
the raspberry boot to the gradient wheel and resets, need to know how do i debug the issue or make the individual files as a single .img file for flashing via pi-imager
Thanks in Advance,
Patric
The issue has been resolved:
Used SD card instead of USB
Patric_phinehas said:
The issue has been resolved:
Used SD card instead of USB
Click to expand...
Click to collapse
Hello Patric,
can you send me the zip file of android automotive 11 operating system.
Hello Patric,
Could shared with us, the zip file of android automotive operating system please.
Yes , please share the image with us
I found one that is outdated , here https://images.snappautomotive.com/rpi/snapp_automotive_rpi4_32gb_20211119.img.zip
hightech316 said:
Yes , please share the image with us
I found one that is outdated , here https://images.snappautomotive.com/rpi/snapp_automotive_rpi4_32gb_20211119.img.zip
Click to expand...
Click to collapse
Hi, I downloaded the img file from the provided link, but after successfully flashing the image file to an SD card, the raspberry pi4 model b didn't boot up. It shows (attached are the images of shown error) :
Raspberry Pi 4 Model B - 8GB bootloader: 6efe41bd 2022/01/25
board: 003115 6485fcf2 e4:5f:01:ad:58:05 boot: mode SD 1 order f41 retry 0/1 restart 18/-1
SD: card detected 00035344534431323885fa236632a165 part: mbr [0x0c:00000800 0x83:00040800 0x83:00440800 0x83:00480800]
fw: start4.elf fixup4.dat
net: down ip: 0.0.0.0 sn: 0.0.0.0 gw: 0.0.0.0
tftp: 0.0.0.0 00:00:00:00:00:00
Trying partition: 6
type: 16 lba: 2048 oem: 'mkfs. fat' volume:
rsc 4 fat-sectors 256 c-count 65399 c-size 4
root dir cluster 1 sectors 32 entries 512 Read config.txt bytes 206 hnd 0x00000000
Read start4.elf bytes 2214880 hnd 0x00000000 Read fixup4.dat bytes 5433 hnd 0x00000000
Firmware: 4b4aff21f72c5b9ba39d83c7b0f8fa910a6ef99b Dec 15 2020 14:48:29
0x00d03115 0x00000000 0x0000003f
start4.elf: is not compatible This board requires newer software
Get the latest software from https://www.raspberrypi.com/software/
Help me solve the issue. What should I follow?
Fails
marchnz said:
Fails
Click to expand...
Click to collapse
Yes, Failed to bootup. I need to know , Is there any issue in using the mentioned img file? How can I overcome this problem?
nithin936 said:
Yes, Failed to bootup. I need to know , Is there any issue in using the mentioned img file? How can I overcome this problem?
Click to expand...
Click to collapse
has the issue been resolved?
ferovbee said:
has the issue been resolved?
Click to expand...
Click to collapse
yes... resolved by editing the config.txt
nithin936 said:
yes... resolved by editing the config.txt
Click to expand...
Click to collapse
The image booted okay for me. However, it flickers now and then (tried two different displays). And most of the features do no work (e.g. calling, clicking on a contact doesn't do anything; maps do not load even after Bluetooth internet tethering to my phone).
Are you experiencing the same?
For those with success with the snapp image, did you have to do anything special? I downloaded it, used the raspberry image writer to write it to a 64gb sdcard (only one I have on hand, it works with raspbian) and attempted to boot. It shows the rainbow screen but then a blank screen. Is there anything I need to do? I am using the 8gb version of the board.
eyeball123 said:
For those with success with the snapp image, did you have to do anything special? I downloaded it, used the raspberry image writer to write it to a 64gb sdcard (only one I have on hand, it works with raspbian) and attempted to boot. It shows the rainbow screen but then a blank screen. Is there anything I need to do? I am using the 8gb version of the board.
Click to expand...
Click to collapse
I had the same issue at first. Changing the display worked for me (I was using a waveshare 4.3" display, changed to my computer monitor and it showed up).
dogemaster11 said:
I had the same issue at first. Changing the display worked for me (I was using a waveshare 4.3" display, changed to my computer monitor and it showed up).
Click to expand...
Click to collapse
Thank you - I was trying with the official 7" touch screen. I tried again with the micro HDMI but it also didn't work - but I will look further to display related settings and see if I can spot anything.
Patric_phinehas said:
Hi,
I have been recently working on ways to boot AA 11 in Raspi 4 (4 GB) via manual build. Having followed all steps till build, when creating partitions and flashing each individual image to the partition
1. SDX1 -> boot files (manual copy setting boot flag)
2. SDX2 -> linux partition -> system.img
3. SDX3 -> linux partition -> vendor.img
the raspberry boot to the gradient wheel and resets, need to know how do i debug the issue or make the individual files as a single .img file for flashing via pi-imager
Thanks in Advance,
Patric
Click to expand...
Click to collapse
Hi i will point you to the easy way to do it .
1-create SD card the same way you have created the first one
but put in mind to use the smallest capacity sd card that can hold the three partitions
the smaller sd card you use will help you creating smaller.img
2- use software called Win32DiskImager to make img file of your sd card.
3- And walla you have one image file .
note : you may add auto resizing script to Expand File System after installation.
or just let user do it manually using raspi-config .
if my answer is helpful please use thanks button
and consider send me pm of created img for self use