The Honeycomb thread is getting swamped right now, so i thought i would make this for those interested.
The install of this is identical to the Froyo install method (but the Froyo kernel does not work! Use the Eclair) -
Plug in the SD card to your computer (Linux/Mac is preferred)
Download the Eclair 1.1Ghz Kernel Zip file
Extract the zip somewhere you know.
Open the SD card, and in the /boot partition, replace the uImage on the card with the one from the zip
*This is where linux works best*
If you have a linux/mac box, open the /data partition, and clear the contents of the dalvik-cache folder (but not the folder itself).
Running quadrant advanced on this build -
Before OC - 1450
After OC - 1838
And things are a bit smoother. Once again, thanks for your great work devs, and for your kernel dalingrin!
Thank you!!!
Divine_Madcat said:
The Honeycomb thread is getting swamped right now, so i thought i would make this for those interested.
The install of this is identical to the Froyo install method (but the Froyo kernel does not work! Use the Eclair) -
Plug in the SD card to your computer (Linux/Mac is preferred)
Download the Eclair 1.1Ghz Kernel Zip file
Extract the zip somewhere you know.
Open the SD card, and in the /boot partition, replace the uImage on the card with the one from the zip
*This is where linux works best*
If you have a linux/mac box, open the /data partition, and clear the contents of the dalvik-cache folder (but not the folder itself).
Running quadrant advanced on this build -
Before OC - 1450
After OC - 1838
And things are a bit smoother. Once again, thanks for your great work devs, and for your kernel dalingrin!
Click to expand...
Click to collapse
Thanks!
I tried the Froyo 1.1 and it was a no go, tried this and first boot hung, but second boot I'm up and going setCPU sees 1.1Ghz (no SU though).
I am on a mac, where is the /data partition?
dambrosioj said:
I am on a mac, where is the /data partition?
Click to expand...
Click to collapse
Hmm.. perhaps i wrongly assumed it would show up like it did on Linux (ubuntu) systems. It should show up as a partition just like /boot does. Perhaps somebody with a Mac can double check this for me?
Clear dalvik cache using adb
adb remount
adb shell rm -rf /system/sd/dalvik-cache
For the windows users out there...
Edit: Not actually sure if this will work as I'm currently burning the Honeycomb image as we speak....
Is there a way to clear Dalvik from the device like maybe in terminal?
Novarider said:
Is there a way to clear Dalvik from the device like maybe in terminal?
Click to expand...
Click to collapse
I am not sure, but really, i would advise clearing the cache before the first boot-up on the different kernel. It really reduces the amount of possible problems, though i guess you may be able to boot up OK without doing it.
Novarider said:
Is there a way to clear Dalvik from the device like maybe in terminal?
Click to expand...
Click to collapse
Anything you can do with adb shell you can do in the terminal. So if the shell command is
adb shell rm -rf /system/sd/dalvik-cache
Just go into the shell and do
rm -rf /system/sd/dalvik-cache
Also, I can confirm booting with the 1.1ghz kernel in Honeycomb.
dirtygreek said:
Anything you can do with adb shell you can do in the terminal. So if the shell command is
adb shell rm -rf /system/sd/dalvik-cache
Just go into the shell and do
rm -rf /system/sd/dalvik-cache
Also, I can confirm booting with the 1.1ghz kernel in Honeycomb.
Click to expand...
Click to collapse
No root access on honeycomb so no shell
so copy JUST the uImage file from "kernel-1100mhz-omap3630.zip" to the boot partition (which shows up as the only browseable partition in Windows)?
i'm getting the blinking "Android" turquoise text while trying to boot after doing that
So far this is working great for me. Thanks for the tip!
I reverted mine...
Maybe I did something wrong, but I found that the touch responsiveness went into the toilet
Put it back the way it was.
Can't wait til we can install and boot this thang internal-like
-K
jleecong said:
Thanks!
I tried the Froyo 1.1 and it was a no go, tried this and first boot hung, but second boot I'm up and going setCPU sees 1.1Ghz (no SU though).
Click to expand...
Click to collapse
So it hung a few times and loaded once more, but now will not load with the 1.1 kernel. Had no problems with this on Froyo.
I will say is doesn't freaze, it just is stuck at ANDROID_ (flashing)
jleecong said:
So it hung a few times and loaded once more, but now will not load with the 1.1 kernel. Had no problems with this on Froyo.
I will say is doesn't freaze, it just is stuck at ANDROID_ (flashing)
Click to expand...
Click to collapse
Same here...
jleecong said:
So it hung a few times and loaded once more, but now will not load with the 1.1 kernel. Had no problems with this on Froyo.
I will say is doesn't freaze, it just is stuck at ANDROID_ (flashing)
Click to expand...
Click to collapse
Because you use the eclair one, not froyos.
Sent from a NC on [email protected] using tapatalk pr0z
camwinnn said:
Because you use the eclair one, not froyos.
Sent from a NC on [email protected] using tapatalk pr0z
Click to expand...
Click to collapse
That, and you may have issues if you didn't clear dalvik..
kaicherry said:
Maybe I did something wrong, but I found that the touch responsiveness went into the toilet
Put it back the way it was.
Can't wait til we can install and boot this thang internal-like
-K
Click to expand...
Click to collapse
Once you've booted just lock the nook and then unlock it. This an issue with current kernels compiled from source.
FWIW, I have updated my original thread.
camwinnn said:
Because you use the eclair one, not froyos.
Sent from a NC on [email protected] using tapatalk pr0z
Click to expand...
Click to collapse
I tried the 1.1 Froyo kernel (that still works fine with Froyo) before this post with Honeycomb, it did NOT work, but the Eclair kernel did as the OP said.
Divine_Madcat said:
That, and you may have issues if you didn't clear dalvik..
Click to expand...
Click to collapse
Yes I cleared dalvik... Like I said it booted twice and didn't boot about 20 times.
If it work for others GREAT! I'm just posting my feedback. Applying Honeycomb v.02 now.
Booting Honeycomb .02 with the 1 Ghz kernel... The 1.1 did the same thing. Either way this is rockin!
Won't boot for me using the Eclair 1.1 kernel. I cleared dalvik, but won't get past the turquoise "ANDROID" with the blinking cursor.
Related
I read in the bootloader development thread that it'd reached a level where it could almost boot into a custom system image stored on the SD card. Some questions about that:
1. The creation of that image, is it similar to how it's done for use with the XDAndroid project? (The porting of Android to HTC WinMo devices)
2. Is there a way to avoid having to reflash the device after every attempt? It looks like the boot-scripts take control pretty early in the process so having a choice if you want to proceed would be awesome, especially since I can't figure out how to get hold of a bootlog.
Thanks
ddewbofh said:
1. The creation of that image, is it similar to how it's done for use with the XDAndroid project? (The porting of Android to HTC WinMo devices)
Click to expand...
Click to collapse
I have no clue how they do it for XDAndroid, but here's how I created mine:
dd if=/dev/zero of=rootfs.ext2 bs=1M count=512 (for 512Mb fixed size)
mkfs.ext2 rootfs.ext2 (press y to accept)
mount somewhere
copy your stuff into
umount
ddewbofh said:
2. Is there a way to avoid having to reflash the device after every attempt? It looks like the boot-scripts take control pretty early in the process so having a choice if you want to proceed would be awesome, especially since I can't figure out how to get hold of a bootlog.
Click to expand...
Click to collapse
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
zdzihu said:
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
Click to expand...
Click to collapse
I've tried hammering all the keys without any success, since it works for you maybe I'm doing it at the wrong time. Where in the boot process do you do it?
And thanks for the tip about the image, didn't want to risk messing something up since I had to reflash after every try.
ddewbofh said:
I've tried hammering all the keys without any success, since it works for you maybe I'm doing it at the wrong time. Where in the boot process do you do it?
Click to expand...
Click to collapse
Bash them for a while as soon as you see SE logo appearing
ddewbofh said:
And thanks for the tip about the image, didn't want to risk messing something up since I had to reflash after every try.
Click to expand...
Click to collapse
Make sure you either name your image rootfs.img (not .ext2) or edit the init in the ramdisk accordingly.
Cheers
Thanks, that should make things much, much easier.
zdzihu said:
I have no clue how they do it for XDAndroid, but here's how I created mine:
dd if=/dev/zero of=rootfs.ext2 bs=1M count=512 (for 512Mb fixed size)
mkfs.ext2 rootfs.ext2 (press y to accept)
mount somewhere
copy your stuff into
umount
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
Click to expand...
Click to collapse
is there different form flash?
I've figured out why my phone refuses to go back to normal after testing the chroot. It needs grep and the standard sh doesn't provide it nor is there a grep symlink/binary in /system/bin so I'll add those manually.
Anyways, if anyone has a script or something to do all this it would be very helpful. I'm not looking forward to going over tons of symlinks manually.
ddewbofh said:
I've figured out why my phone refuses to go back to normal after testing the chroot. It needs grep and the standard sh doesn't provide it nor is there a grep symlink/binary in /system/bin so I'll add those manually.
Anyways, if anyone has a script or something to do all this it would be very helpful. I'm not looking forward to going over tons of symlinks manually.
Click to expand...
Click to collapse
How about busybox --install -s /your_destination_dir ?
zdzihu said:
How about busybox --install -s /your_destination_dir ?
Click to expand...
Click to collapse
Awesome, thanks. My knowledge about busybox is limited at best so when I saw install listed as a busybox function I assumed it was the "normal" install command.
In the quest for finding a way to use custom kernels I'm playing around with the splboot module but I need to find a way to get hold of dmesg or kmsg from failed attempts. Is there a reliable way to get any of these logs?
I've tried adding a line in the mount_iso script which cats kmsg to a file right before executing the splboot but I'm seeing nothing that would indicate that I'm running anything but the stock kernel.
Any ideas?
hi can some one tell me how to Enable JIT on my Optimus One.
I need a very simple guid.
Thy.
imapjonny said:
hi can some one tell me how to Enable JIT on my Optimus One.
I need a very simple guid.
Thy.
Click to expand...
Click to collapse
Root your phone
Install custom recovery
Download flashable zip that enables JIT
flash it
kite86 said:
Root your phone
Install custom recovery
Download flashable zip that enables JIT
flash it
Click to expand...
Click to collapse
I'm pretty sure that he wants a easy and detailed guide.
Domenic.
1. Does Z4Root work on this work?
2. What is a good custom recovery to use? does cwm work?
imapjonny said:
hi can some one tell me how to Enable JIT on my Optimus One.
I need a very simple guid.
Thy.
Click to expand...
Click to collapse
Once you've got the custom recovery on it's easy. Copy the jit enabling zip file to the root of your sdcard, reboot into recovery and choose flash zip from the recovery menu.
yes z4root is working!
I need a giud how to install custom recovery to
imapjonny said:
I need a giud how to install custom recovery to
Click to expand...
Click to collapse
http://androidforums.com/getitnowma...ry-optimus-one-p500-thunderg.html#post1896517
To use copy flash_image and recovery-RA-GNM-thunderg-1.1.0.img to the root of your sdcard.
To flash: via adb shell or terminal type this from root # shell
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
# flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
# reboot recovery
Key combo to boot custom recovery from powered off is vol_down + home + power and release keys at LG splash.
Click to expand...
Click to collapse
I m realy new in this scene
what is adb shell and where can i get it ?
imapjonny said:
I m realy new in this scene
what is adb shell and where can i get it ?
Click to expand...
Click to collapse
You can download Android SDK - this shell is part of this development tool
imapjonny said:
I m realy new in this scene
what is adb shell and where can i get it ?
Click to expand...
Click to collapse
Or root and get terminal app.
Either way, I tweaked mine for a vm.heapsize of 48mb.
JIT sure is handy but what about GPU accel?
I have flashed with jit zip.
I test the phone before,
with linpack,average result 3.5M
After flash with jit,actual result 7.8M
During the normale use i don't see evident boost performarce,
but for me is a good update.
Bye.
Sorry, but I thought Android 2.2 had the JIT compiler built in? It's turned off on the Optimus T?
This is my wife's phone, and in general it has good performance. But Angry Birds runs a slow on some of the screens. I was wondering if enabling the JIT compiler might help.
BTW, I've rooted the phone already to modify the SMS send limits.
Froyo normaly make active jit,
but on O1 this feature is not active by default.
If you have rooted the phone,install the recovery menu and flash with jit zip.
greno1 said:
But Angry Birds runs a slow on some of the screens. I was wondering if enabling the JIT compiler might help.
Click to expand...
Click to collapse
No that does not help, I have tested that. Removing the ads with adfree android seems to help a little bit, but generally the phones cpu has not enough power for angry birds.
The Angry Birds developers are working in a lower spec version that will run on 600mhz Arm6 processors more smoothly.
Just in case, figured someone would want it at some point.
dl-dropbox-com/u/13427114/signed_thunderc_thungerg_jit_disable.zip
(add http and replace - for dots)
Noejn said:
Just in case, figured someone would want it at some point.
dl-dropbox-com/u/13427114/signed_thunderc_thungerg_jit_disable.zip
(add http and replace - for dots)
Click to expand...
Click to collapse
you can also delete /data/local.prop and reboot too.
Or, flash this one which will not only enable JIT and change the vm.heapsize to 48mb but also enable hardware acceleration. Homescreen should be snappier.
dl"dot"dropbox"dot"com/u/13427114/mone/o1_jit-hwacc_enabler.zip
(add http and replace "dot" for .)
how should i install this? (Searched over the net and couldn't find how to install)
Will this increase my gaming and mobile performance ??
I have lg official 2.3.3 Rom, With franco kernel and also have SetCpu installed.
globeent1980 said:
how should i install this? (Searched over the net and couldn't find how to install)
Will this increase my gaming and mobile performance ??
I have lg official 2.3.3 Rom, With franco kernel and also have SetCpu installed.
Click to expand...
Click to collapse
Its enabled by default
Sent from my LG-P500
What we have here is a set of images to flash to your Nook and run Honeycomb on your internal storage. (Currently based on Deeper_Blue's v02) The method for installing is the same as for Nookie Froyo on EMMC (http://forum.xda-developers.com/showthread.php?t=926749)
To Install HC to your Nook Color flash CWR to your sd card (http://forum.xda-developers.com/showthread.php?t=922870)
Copy the two image files to the sd card.
Boot to CWR and ADB Shell into your NC.
Run the following commands to flash Honeycomb:
mount data
mount sdcard
rm /data/* -r
dd if=/sdcard/hcboot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/hcsystem.img of=/dev/block/mmcblk0p5
reboot
ATTENTION! Do not use CWR to format your SD card, also remove your SD card after installation so it will boot to HC and not CWR!
I would like to thank MattJ951 for his work with Samuelhauf on getting the uRamdisk working to boot, and Deeper_blue for porting honeycomb to the Nook Color. (If i have forgotten anyone PM me and I will give credit!)
hcboot.zip (24.41 MB) http://www.multiupload.com/153I3TA6JN
hcsystem.zip (204.69 MB) http://www.multiupload.com/1MDP2LYJMG
Original Project by MattJ951 (http://forum.xda-developers.com/showthread.php?t=943724)
Woo! Nice!
Once again, you forget to mention not to use sdcard format on the NC after having installed this.. your going to have black screen complaints..
Sent from my HTC Desire using XDA App
Nothing should get formatted as these are dd images.... run the commands above and everyone should be fine..
Sent from my LogicPD Zoom2 using Tapatalk
AMAZING! worked Perfectly!!!!!! WOW! (I had to take samuelhalff's advice and removed the sdcard just in case on boot) everything is working perfectly! thank you very much for your work!
anyone notice any speed increase than say a class 6 sd card?
anyone notice any speed increase than say a class 6 sd card?
same question here!
HC v3, eMMC 1100 kernel, launcherpro.
Smooth.
Tried converting data and cache to ext4. No go. Seems deeperblue hasn't added ext4 support to his kernel yet..
By the way, no problem with v3.
You must have missed something while copying system. Maybe your partition was too small..
Sam
Sent from my HTC Desire using XDA App
How would I add gapps and market after I install HC eMMC?
what is EMMC
beezy69 said:
what is EMMC
Click to expand...
Click to collapse
The internal storage on the nook (flash memory) rather than SD Card
can someone help me out here. im booted from sd into cwr, and when i try and run the command "mount sdcard" it says it failed no such file or directory.
i built the sdcard per the instructions. anyone have an idea what is wrong?
samuelhalff said:
HC v3, eMMC 1100 kernel, launcherpro.
Smooth.
Tried converting data and cache to ext4. No go. Seems deeperblue hasn't added ext4 support to his kernel yet..
By the way, no problem with v3.
I must have missed something while copying system. Maybe your partition was too small..
Sam
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Did you not have a rotation problem (i.e. it never rotated to the side you were using, always one past) with v03?
jewnersey said:
can someone help me out here. im booted from sd into cwr, and when i try and run the command "mount sdcard" it says it failed no such file or directory.
i built the sdcard per the instructions. anyone have an idea what is wrong?
Click to expand...
Click to collapse
You don't use dd images with CWR (actually you might be able to, but i prefer my way).
You download a nookie froyo sd image (or just use your honeycomb one and add the two images to the sd partition of it (You can adb push them or just use your computer to copy them).
Then open up a terminal emulator (i believe there is one in dev tools) and type these commands:
dd if=/sdcard/hcboot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/hcsystem.img of=/dev/block/mmcblk0p5
Also as Sam said
DO NOT FORMAT YOUR SD CARD FROM INSIDE THE NOOK COLOR please update the OP saying this
Most excellent! I will be giving this a try shortly (at work now but RDC home to start the download!)
Question: Any plans to "update" to deeper-blue's V03 image? I know it's a "preview" right now so perhaps you are waiting for a more stable release???
Thanks!
V3 is flawless here. Check you don't get: nit enough space error, while copying system..
Ill probably make a flashable version of v4..
Sam
Sent from my HTC Desire using XDA App
I restored my nook to Stock 1.01 yesterday after a random catastrophic failure with my previously stable 1.01 AN setup; so, I'm ready to try anything.
The choices are HC v3, Froyo 0.6.6, or the 1.1 AN setup.
1) How difficult would it be to update these emmc HC images to v3?
2) Which of the three options is the most stable for the following?
--ADW Launcher
--Clockwork Mod / ROM Manager
--HQ Youtube app
--Market (AppBrain as well)
--Gmail w/calendar sync (I use the Pure Grid Calendar app)
--Xscope browser / Dolphin HD
--Aldiko 2.0
--Live Wallpapers
--Scrollable widgets
--Rockplayer
--Perfect Viewer (for comics)
--WidgetLocker
--Tapatalk
--Su/Superuser apps (Root Explorerer, Terminal, Wireless adb, etc)
--TV Shows Stream
--Angry Birds (all versions)
3) Which capabilities does HC v3 still lack?
4) Do any of these options have a global copy/paste capability?
5) Do any of them have working Flash 10.1 (for apps like TV Shows Stream, or Droid Stremer Pro)?
samuelhalff said:
V3 is flawless here. Check you don't get: nit enough space error, while copying system..
Ill probably make a flashable version of v4..
Sam
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
How far away is v4?!
paleh0rse said:
I restored my nook to Stock 1.01 yesterday after a random catastrophic failure with my previously stable 1.01 AN setup; so, I'm ready to try anything.
The choices are HC v3, Froyo 0.6.6, or the 1.1 AN setup.
1) How difficult would it be to update these emmc HC images to v3?
2) Which of the three options is the most stable for the following?
--ADW Launcher
--Clockwork Mod / ROM Manager
--HQ Youtube app
--Market (AppBrain as well)
--Gmail w/calendar sync (I use the Pure Grid Calendar app)
--Xscope browser / Dolphin HD
--Aldiko 2.0
--Live Wallpapers
--Scrollable widgets
--Rockplayer
--Perfect Viewer (for comics)
--WidgetLocker
--Tapatalk
--Su/Superuser apps (Root Explorerer, Terminal, Wireless adb, etc)
--TV Shows Stream
--Angry Birds (all versions)
3) Which capabilities does HC v3 still lack?
4) Do any of these options have a global copy/paste capability?
5) Do any of them have working Flash 10.1 (for apps like TV Shows Stream, or Droid Stremer Pro)?
Click to expand...
Click to collapse
Eclair is by the most stable but lacking flash. Froyo supports flash but has some issues with talpatalk (at least for me). Honeycomb is more of a PoC and you will get a lot of crashes on some apps.
MattJ951 said:
Eclair is by the most stable but lacking flash. Froyo supports flash but has some issues with talpatalk (at least for me). Honeycomb is more of a PoC and you will get a lot of crashes on some apps.
Click to expand...
Click to collapse
That's about right. Though I haven't had any trouble with Froyo and Tapatalk (XDA does crash, on the other hand).
HC v3 on eMMC probably is my favourite experience so far with the NC. Although, I'm most certainly not objective, as HC is very new, compared to our old Froyo buddy..
If I had to choose, taking under account your criterions, I would go with Froyo. Perfect blend of stability and performance.. As Matt said, HC is very nice, but still isn't stable enough for the average user.. HC, as of right now, should only be installed for the thrill of it, or to start dev'ing around..
Eclair? Well, it's ok. But without flash, it can't possibly be an option. You might as well buy an iPad (sarcasm)..
PS: v4? Pretty soon, I guess...
samuelhalff said:
That's about right. Though I haven't had any trouble with Froyo and Tapatalk (XDA does crash, on the other hand).
HC v3 on eMMC probably is my favourite experience so far with the NC. Although, I'm most certainly not objective, as HC is very new, compared to our old Froyo buddy..
If I had to choose, taking under account your criterions, I would go with Froyo. Perfect blend of stability and performance.. As Matt said, HC is very nice, but still isn't stable enough for the average user.. HC, as of right now, should only be installed for the thrill of it, or to start dev'ing around..
Eclair? Well, it's ok. But without flash, it can't possibly be an option. You might as well buy an iPad (sarcasm)..
PS: v4? Pretty soon, I guess...
Click to expand...
Click to collapse
Alright, excellent! Thanks for the feedback... it sounds like I'll be going for Froyo on emmc tonight!
Do you see any apps in my list above that I might have problems with?
I apologize if this has been covered in another thread but I have been doing multiple searches on XDA and in google trying to find a solution but so far no luck. Long time reader of XDA but first time poster.
Details -
I successfully used NVFLASH, loaded Clockworkmod 0.8 and loaded Vega-Ntab gingerbread edition (stable RC1 I believe its called). I have been running this for a month or so with no major issues but I want to test out Vega-Ntab 5.1 and Brilliant Corners. Thinking of going with 5.1 for the hardware acceleration for gaming etc. Oh I also received my new Gtab with bootloader 1.2 and I downgraded that to 1.1 successfully before loading Vega-Ntab gingerbread. I think I can handle loading the new roms etc (may have to switch to 1.2 for Brilliant Corners I believe) but I want to do a full backup before doing so with clockworkmod so I can go back to gingerbread if I decide I liked it the best. But clockworkmod will not do a backup for me. I have tried multiple times and it always freezes/hangs at the same point. On the screen I see
ClockworkMod Recovery v2.5.1.1-bekit-0.8
SD card space free: 9697MB
Backing up boot...
Backing up recovery...
Backing up system... and here it will go no further
I have let it set at that point for hours but nothing changes. I checked the clockworkmod backup folder and it has a folder dated the current date of the backup but the contents is only boot.img and recovery.img and nothing else so I think that confirms it really isnt completing the backup.
I am unsure what the cause or solution to this is. I thought about reloading clockworkmod 0.8 but I don't think I can do this since it's already loaded. I thought about loading a newer version but from what I have read gingerbread and the other 1.1 roms will not work with anything but 0.8. I could just do a melt and repour and just go back to stock level and load 5.1 or Brilliant Corners but then I lose any apps I have loaded. I am not concerned about the majority of them but I have loaded a couple good ones as of late from Amazon that were the free app of the day and I am unsure whether I can "reload" these at a later date without being forced to pay. I have also paid for a couple games but I am assuming I can reload those without issue. I did back up all of the apps I paid for and amazon games that I loaded that I got for free (normally have to pay) with titanium backup. So assuming I can restore these with titanium backup after loading brilliant corners or vegan 5.1 then I guess the only thing that I lose by not being able to do a full backup/restore with clockwork is that if I want to go back to gingerbread then I have to start from scratch for reloading the rom.
So is the problem I am having running the back up successfully a known issue that I just can't seem to find a discussion thread about?
Thanks in advance for any help or advice.
Boot into ClockworkMod Recovery and get me a dmesg output (kernel messages) using adb. See this post for how.
Attach the dmesg.txt to your next post.
thanks for the reply. Unfortunately I am not having any luck getting the dmesg.txt file for you. I downloaded the iso image for Knoppix 6 but when I boot off the disc it starts processing everything but then it gives an error "the file /mnt-system/knoppix/knoppix is broken. then after about 30 secs it gives the following
/sbin/init: line 76: syntax error near unexpected token '/usr/share/fonts/type1/gsfonts/a010013l.pfb'
/sbin/init: line 76: '/URWGothicL-Book (usr/share/fonts/type1/gsfonts/a010013l.pfb);
I will try and download the iso from a different site and burn another disc.
I also tried a different route and loaded SDK manager to get to ADB by that route. I am running windows 7 if that makes a difference. I am not 100% sure when I am supposed to run the adb command line you listed. Do I have my gtab running clockworkmod and then mount USB so it will show up on my pc? Do I have to try and perform a backup and then run the adb command when it freezes? I don't think I can do that because if I navigate away from the mount USB it automatically unmounts it. Anyway adb doesn't appear to be seeing the gtab anyway. When I run the SDK manager it does not find any android devices. If I run the "adb devices" command it comes back with no devices. So I am not sure what basic thing I am missing to get adb or SDK to recognize the gtab.
I apologize for my lack of knowledge on adb. Your first link says if I have adb already set up to run adb shell dmesg > dmesg.txt while in clockworkmod so I am assuming I do this after mounting USB to get the pc to recognize the gtab.
I will try download and burn another iso image from a different location and see if I can boot off a disc. Assuming this time it is successful do I run the ADB command you listed in the second link while the GTab is mounted to USB and recognized by the pc? Hopefully ADB will see it if I can get this to work.
*update* I downloaded the ISO image from a different location. When I went to the folder it was downloaded to I noticed that the first ISO image I downloaded was only approx 100MB in size instead of 700+ mb. So I am re-burning another disc. Hopefully this will allow me to boot properly.
*update #2* I was able to successfully boot off of the new disc. Now I just need to figure out how and where to enter the adb command line in your link ($ sudo ./adb shell dmesg > dmesg.txt) i tried this using the Shell option but it says command not found. If I choose the File Manager option and navigate to where the adb file is that was in your linked zip file it just prompts me to edit/copy/move/rename or delete the file. I am out of time tonight so I will work on it more tomorrow. The good news though is that when I use File Manager the Gtab is listed so it is at least recognized. Now I just need to figure out how to get the dmesg.txt file you request but making some progress... I think
ashton555 said:
*update #2* I was able to successfully boot off of the new disc. Now I just need to figure out how and where to enter the adb command line in your link ($ sudo ./adb shell dmesg > dmesg.txt)
Click to expand...
Click to collapse
Step by step instructions in this post.
thanks a bunch. Those instructions were easy to follow and made sense. I have never used linux before but alot of it reminded me back of my old unix days (terminal commands that is).
Anyway I think I did everything correct and I am now attaching the txt file.
Thanks again for your help and patience with this Linux newbie let me know if I need to provide any additional information.
ashton555 said:
Anyway I think I did everything correct and I am now attaching the txt file.
Click to expand...
Click to collapse
You did indeed. And I can't see any obvious problems with the NAND-flash device, judging from the kernel messages.
Since you've already tried to take backups using CWM before, that action should've created a log file. This file might be useful. Retrieve it. Inside an xterm window on Linux, run:
Code:
hostpc$ [B]sudo ./adb pull /cache/recovery/log recovery.log[/B]
Attach this "recovery.log" file.
Next, try to read, one by one, the NAND flash partitions that CWM usually backs up. Here's an example run on my gTablet:
Code:
hostpc$ [B]sudo ./adb shell[/B] [I]Get into the shell in CWM[/I]
~ # [B]dump_image boot /dev/null[/B]
~ # [B]dump_image recovery /dev/null[/B]
~ # [B]dump_image system /dev/null[/B]
mtd: read error at 0x029a0000 (I/O error)
mtd: read error at 0x02da0000 (I/O error)
~ # [B]dump_image cache /dev/null[/B]
~ #
Type in only the commands in bold.
As you can see, my "system" partition on the NAND flash has errors (and the kernel also report this when it boots), but, the command will not hang. According to the kernel message that you just supplied, you don't have any errors on your onboard NAND flash, so, theoretically, you shouldn't get any errors at all. But, we'll see if the dump_image command hangs when reading system just like CWM does.
And if the dump_image command does hang somewhere, we can see if formatting just that system partition will get it working again. There is a utility on this board which we could use for doing that, though I've never tried it.
I successfully completed the next two tasks. I am attaching the recovery.log file. Note I had an issue copying the .log file to where I could access it in win7 (for some reason I cant attach a file while in linux). I opened it with a word processor and then saved it to my c drive which messed up the formatting. So I opened it in Word to get the formatting correct and saved it as a txt file so thats why the attached file is recovery.txt. Let me know if it messed it up to where its not useable.
On the second task
~ # dump_image boot /dev/null
this worked fine and quick
~ # dump_image recovery /dev/null
this worked fine and quick
~ # dump_image system /dev/null
this worked but took maybe 10-15 seconds
~ # dump_image cache /dev/null
this one gave an I/O error but completed the dump
mtd: read error at 0x00080000 (I/O error)
ashton555 said:
Let me know if it messed it up to where its not useable.
Click to expand...
Click to collapse
The file is just fine... and I can't see any error messages in it.
~ # dump_image system /dev/null
this worked but took maybe 10-15 seconds
Click to expand...
Click to collapse
This is normal -- "system" partition is ~200MB.
~ # dump_image cache /dev/null
this one gave an I/O error but completed the dump
mtd: read error at 0x00080000 (I/O error)
Click to expand...
Click to collapse
This also looks like normal behaviour, but, I'm puzzled that the kernel did not report any bad blocks on this partition. Check if this is a transient error:
1. Repeat the "dump_image cache ..." command a few times and see if the I/O error location is the same.
2. Try to "fix" the error on the cache partition by using the "wipe cache partition" menu item in CWM. Do this a couple of times.
3. Run the "dump_image cache ..." command again.
4. Attempt another full system backup using CWM.
If step 4 fails, we'll see if the writing of the backup to the sdcard is the problem, because the reading seems to be completing without any hangs as of now.
BTW, the most important partitions are all being read fine. The "cache" partition is not that important -- it can be empty (but not corrupt) each time the system boots and only the initial bootup might go a little slower.
And, if, in the end of all this, you can't use CWM at all, you can still make a full system backup using nvflash and a few Unix commands.
1. Repeat the "dump_image cache ..." command a few times and see if the I/O error location is the same
....i did the dump 4 times and it always gave the same I/O location
2. Try to "fix" the error on the cache partition by using the "wipe cache partition" menu item in CWM. Do this a couple of times
.... I wiped the cache 4 times successsfully
3. Run the "dump_image cache ..." command again.
.... same I/O error location
4. Attempt another full system backup using CWM
.... still freezing at backing up system
So I guess I need to try and do the backup with NVFlash and unix/linux commands? If you have a link on how to do that I will give it a try or I can search for it and see if there is a discussion thread on it.
Thanks again for your help and trying to resolve this
Question - if I started over from scratch and went back to stock and then loaded vegan gingerbread would this issue possibly correct itself? Also more importantly if I back up some apps using titanium backup before I go back to stock can I then restore them with Titanium once I have vegan ginger back loaded? Also if I loaded vegan 5.1.1 could I restore the same apps I backed up in vegan ginger? Hopefully that made sense. I don't mind starting from scratch if I need to I just wasnt sure if I would permanently lose certain apps I have loaded. It's only about 10 apps I care about
*update* - well I think I am going to be forced to start over anyway. After wiping the cache a couple times and attempting another backup (froze again at backing up system) I now can't get the gtab to boot completely. It is stuck at the flashing vegan ginger edition screen. It flashes for awhile then the screen goes black then it goes back to the flashing screen again. I know you said it would take longer to boot up the first time after wiping the cache but was doing the flash cycling for over an hour which I assume is too long? I tried wiping the cache again and I also wiped the davlik cache as someone suggested in another thread but it is back to being stuck in the flashing screen loop. Assuming I do have to start over can I at least boot to CWM, mount ext USB and copy off the titanium backup files I made so I can restore some of the paid for apps?
ashton555 said:
3. Run the "dump_image cache ..." command again.
.... same I/O error location
Click to expand...
Click to collapse
Looks like a permanent I/O error in the cache partition, then. But, I don't understand why it is "system" which is hanging on backup.
4. Attempt another full system backup using CWM
.... still freezing at backing up system
Click to expand...
Click to collapse
Get me the recovery.log.
So I guess I need to try and do the backup with NVFlash and unix/linux commands?
Click to expand...
Click to collapse
I'll think this over during the weekend. In the mean-time, read through this thread. You can safely take a complete backup of your tablet while I do a bit of experimentation on a clockworkmod-like solution. But, I suspect that you may not be able to backup "cache" using nvflash going by the I/O errors. I have errors on my "system" partition and a nvflash backup fails on it, but CWM doesn't have any problems backing up and restoring.
Question - if I started over from scratch and went back to stock and then loaded vegan gingerbread would this issue possibly correct itself?
Click to expand...
Click to collapse
Probably not. But, see this thread. It shows you how to wipe all the partitions on the NAND flash device. We don't need to format the entire NAND flash. We can see if doing a few repeated formats of the "system" and "cache" partitions gets CWM working again, if you're willing to wipe "system"--you will have to load Vegan-Ginger right after this.
Also more importantly if I back up some apps using titanium backup before I go back to stock can I then restore them with Titanium once I have vegan ginger back loaded? Also if I loaded vegan 5.1.1 could I restore the same apps I backed up in vegan ginger? Hopefully that made sense. I don't mind starting from scratch if I need to I just wasnt sure if I would permanently lose certain apps I have loaded. It's only about 10 apps I care about
Click to expand...
Click to collapse
I haven't used Titanium backup so I can't say how well it works, but, judging from the reports that other users have made, what you're suggesting should work without any problems. User downloaded applications are stored either on /data or on /mnt/sdcard (for apps moved to SD card). Since your SD cards don't seem to be affected, you can go ahead with Titanium backup.
ashton555 said:
Assuming I do have to start over can I at least boot to CWM, mount ext USB and copy off the titanium backup files I made so I can restore some of the paid for apps?
Click to expand...
Click to collapse
Yeah, copy the files in CWM, then just do a "wipe data/factory reset" and see if it boot loop goes away.
But, before you do that, gimme a half-hour and I'll send you commands which you can use to save the files in /data and /sdcard. I just have to compile and test a new version of busybox. The tar command already present in CWM doesn't seem to work properly for me.
Attaching the recovery file
I am running the nvflash back up right now.
It successfully did part-1.img through part-11.img with no errors. The last thing it said though is
"rem CACHE PARTITION BACKUP NOT NEEDED
"nvflash.exe" -r --read 12 part-12.img
press enter to continue
Is this maybe because I wiped the cache and it's empty?
I looked on my ext SD card and the titanium backup files are there (except for a couple I had forgotten do ....) so I think I am okay for going back to square one if need be.
I will go ahead (tomorrow probably) try doing what is described thread about wiping partitions on the NAND device and just formating the system and cache partitions. I am assuming that at this point I guess its okay to go ahead and try to load vegan tab 5.1.1 instead of ginger again since I wanted to try out 5.1.1 anyway or if you have any experience with it would you recommend Brilliant Corners instead since its a newer rom. I think I will have to reload the 1.2 bootloader which is okay.
ashton555 said:
Attaching the recovery file
Click to expand...
Click to collapse
No errors in there.
The last thing it said though is
"rem CACHE PARTITION BACKUP NOT NEEDED
"nvflash.exe" -r --read 12 part-12.img
press enter to continue
Is this maybe because I wiped the cache and it's empty?
Click to expand...
Click to collapse
I think so. The cache partition isn't that important anyway, so it can be skipped.
I will go ahead (tomorrow probably) try doing what is described thread about wiping partitions on the NAND device and just formating the system and cache partitions.
Click to expand...
Click to collapse
I would suggest that you copy the Titanium backed-up apps safely away immediately, then format just the system and cache partitions as per that thread. You will need to be in APX mode to use nvflash.
Immediately after the nvflash, (since the system partition is now gone), boot into CWM, then do a factory reset, repartition the internal sdcard, copy the Vegan-5.1.1 update file onto the now clean sdcard through the PC and then flash it. This should give you a clean slate.
Then check if you can do a backup using CWM. If you still can't, then I'll see if a solution can be devised to do partial backups.
And, I have tried neither Vegan* nor Brilliant Corners, so the choice is up to you.
Sorry, my test commands aren't working so I can't send you those commands I promised to back up your /data and /system--I suspect a bad USB cable.
I have a GTab that was running Calkulin + Clemsyn Combo Overclock at 1.5 ghz V8 on the 1.2 branch fine for a couple months now, then something happened today. Woke up to find there was no sound coming from it (I'd left an Anti-mosquito app running all night), so I tried to play a couple music files. Seemed to get frozen instead of playing, so I restarted. That's when it went into a boot loop from 3 birds to the first splash screen of the loaded ROM.
Attempted to do a backup via CWM, and it failed on /data. Tried a data wipe/reset, then reflashing the ROM and finally NVFlash. Still goes into a bootloop. Repartitioning and mounting doesn't do anything; ADB doesn't see the device at all in CWM or APX; /data cannot be mounted and /sdcard mounts only when a card is inserted (doesn't see the internal space) but still doesn't mount USB storage and says: "E:Unable to write to ums lunfile (No such file or directory)"; drive shows in Win7, but is inaccessible;
As mentioned, APX mode and NVFlash along with CWM works fine. And I can mount /cache and /system fine. I've gotten to Code Double Red here and now I'm draining the battery for the next step (really don't want to pull any screws). Also tried the fix here, but it seems that's just for CM7, which I'll probably try flashing some time.
I'm going to return to the 1.1 branch and try a couple ROMs there, but I have a really slow connection and it's taking a while to get nvflash 1.1.
Did a quick search of the forum and didn't find anything quite similar. Obvious question is, has anyone ever experienced this before? What are some other steps I can take to fix this? Is there a way to backup the internal SD before I probably have to wipe it?
Connect the USB cable to the tablet, then boot it into CWM, and run this command on your PC:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
Post that dmesg.txt file here. We'll see what's wrong.
Connected the charger long enough to run the command, but all I get is "error: device not found". As I'd said, ADB doesn't detect the tablet, even though Windows knows when it's connected and disconnected. Is there anything that I can flash to get me a terminal? That's the only way I can think of to get that command run and hopefully direct the output to my SD. Thanks.
I now have a completely dead battery. Wondering what to do next since it's supposed to have been hard reset now. Not seeing anything different after booting; same boot loop even though I just flashed a ROM again.
rajeevvp said:
Connect the USB cable to the tablet, then boot it into CWM, and run this command on your PC:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
Post that dmesg.txt file here. We'll see what's wrong.
Click to expand...
Click to collapse
I had seen this thread before where you were helping someone last year. Wish I'd read further to see that he eventually got the same problem I now have. I'm currently working my way through everything. First I need to get ADB running though, so I'm working on that now. Think I may be needing that partition swap trick, but we'll see...
Having issues getting the right USB drivers installed for ADB on Windows 7 64 bit. Using instructions here. But each time I uninstall the device, as soon as I plug in the tablet, it installs the default drivers. Using both Device manager and USBDeview. Updating and other options are also disabled when there is nothing installed. Considering to do a direct registry hack of the device info if I can, and hopefully not break anything important.
Try using Linux.
I finally got ADB working on my system and did some experimenting. Seems there's definitely something wrong with my internal SD according to the dmesg output. Luckily I have a SD which I used in my SG3, and it is already properly partitioned, so I'll try using that. Tried making a fstab file in /etc (mtdblock3) but I got "Magic Value Mismatch" error, so I NVFlashed to return it to how it was. I'm currently researching how to create update files, because it seems that's the only way I can get the SDs swapped. Any guidance is still welcomed. Thanks alot.
Skele Drew said:
Seems there's definitely something wrong with my internal SD according to the dmesg output.
Click to expand...
Click to collapse
Yeah. There are clear error messages relating to the internal SD card. You can either return the tablet and get a replacement, or, use my SD card device swapping technique to use the external SD in place of the non-working internal one.
Tried making a fstab file in /etc (mtdblock3) but I got "Magic Value Mismatch" error, so I NVFlashed to return it to how it was. I'm currently researching how to create update files, because it seems that's the only way I can get the SDs swapped.
Click to expand...
Click to collapse
If you use my files, you don't need to modify anything manually. What're you trying to change, BTW?
I can definitely use some help there. Where are the files? I tried modifying the custom ROM I use by adding a custom fstab and vold.fstab to /etc, an init script to init.d and replacing the /data mounting command with:
Code:
ui_print("Copying Data Files");
run_program("/sbin/mount", "-t", "ext3", "/dev/block/mmcblk2p2", "/data");
ui_print("Mount information:");
ui_print(run_program("/sbin/mount"));
Not sure what you're attempting to do here...
If you just want to use an external SD card in place of your non-working internal one, then all you have to do is a) flash either one of the CWM zip files and then b) flash the SD card swapping zip file right after you install the ROM of your choice. And, if you tell me which ROM you plan to install, I can look inside it and tell you if my scripts will work with that ROM.
If you can read shell/awk scripts, you can look inside the zip files to see what they do and how they do it.
rajeevvp said:
Not sure what you're attempting to do here...
If you just want to use an external SD card in place of your non-working internal one, then all you have to do is a) flash either one of the CWM zip files and then b) flash the SD card swapping zip file right after you install the ROM of your choice. And, if you tell me which ROM you plan to install, I can look inside it and tell you if my scripts will work with that ROM.
If you can read shell/awk scripts, you can look inside the zip files to see what they do and how they do it.
Click to expand...
Click to collapse
I was trying to make a swap script myself, but it's not working. /system dir gets corrupted. I'm using Clemsyn_Caulkinver8final2, a Froyo ROM.
Look at my scripts. If you have any questions, just ask.
Where are the scripts? That's what I've been asking...
EDIT: If this is what you use, then all should be ok. Let you know the result when I'm again online. Thanks alot for your help!
That's what I was talking about. I modified the device-swapping script today to fix-up an additional shell script, /system/etc/inandop.sh, on the various Clemsyn/Beasty ROMs (incl. yours), so use the newer zip file.
rajeevvp said:
That's what I was talking about. I modified the device-swapping script today to fix-up an additional shell script, /system/etc/inandop.sh, on the various Clemsyn/Beasty ROMs (incl. yours), so use the newer zip file.
Click to expand...
Click to collapse
Appears it still doesn't work. However, now instead of having a boot loop, it's just stuck at the splash screen after the 3 birds. I'm going to try combining your script and the ROM to see if I can get better results. I'm also going to try inserting some log/debug messages where I can.
Skele Drew said:
Appears it still doesn't work. However, now instead of having a boot loop, it's just stuck at the splash screen after the 3 birds. I'm going to try combining your script and the ROM to see if I can get better results. I'm also going to try inserting some log/debug messages where I can.
Click to expand...
Click to collapse
THANK YOU RAJEEV!!!!!!!
Today I got the time to work on my tablet again, since I just restarted college and it's been a bit hectic. Decided to try CM7 since when I looked into your script I saw direct management for it, so I NV'd back to 1.1 (I didn't know what branch CM7 was on, but flashing CM7 on 1.2 gave an error and aborted). The first time I tried the CM7, it got to the CM7 logo, then was there for a while until I only had a black screen. The only way I knew the tablet was still on was because ADB was still connected. Then I flashed your script and VOILA! everything started great. So now I have my tablet again for my classes .
I am planning to still run a few tests to see if I can somehow recover/fix the internal SD, so I downloaded your set of e2fsprogs. Think I'll make a flashable file for the entire package.
Again, thanks for all your assistance. It's much appreciated. I really didn't have that much time anymore to work on it myself too. I will continue to learn more as time goes on though, and I hope one day I'll become a guru like you .
Skele Drew said:
Decided to try CM7 since when I looked into your script I saw direct management for it, so I NV'd back to 1.1 (I didn't know what branch CM7 was on, but flashing CM7 on 1.2 gave an error and aborted).
Click to expand...
Click to collapse
The official CM7 is, right now, only for 1.1. However, since you can replace just the kernel and instantly make a 1.2 ROM, you'll have to look at the kernel messages to tell which bootloader version you have (Note: this is only for pershoot kernels).
The first time I tried the CM7, it got to the CM7 logo, then was there for a while until I only had a black screen. The only way I knew the tablet was still on was because ADB was still connected.
Click to expand...
Click to collapse
This is to be expected. When a ROM first runs, it writes a whole bunch of stuff into /data; but, your internal SD card is messed up, so every write would've ended up with the kernel retrying for quite a bit and then failing.
You should've flashed the ROM and immediately afterwards my script to fix-up the mount points on the ROM--ie. before the first boot.
I am planning to still run a few tests to see if I can somehow recover/fix the internal SD, so I downloaded your set of e2fsprogs. Think I'll make a flashable file for the entire package.
Click to expand...
Click to collapse
I doubt if you can "fix" your internal SD card error using any of the e2fsprogs--it looks like a card-controller error rather than a media error. You have one of the non-standard internal SD cards which has caused problems for some other users as well.
Ok. I do have a few issues I hope I can get some help on. For one, flash player doesn't work, and that's something very important. All my browsers direct me to get flashplayer. It worked pretty well in my previous ROM, so it may be an issue with CM7, but I haven't seen any similar issues on their site.
Also, the tablet is less responsive now, though I think this has to do with the /data partition being on external SD, though it's a class 6 card.
Sent from my GTablet using Tapatalk
Did you partition the external SD card correctly into 2 partitions (the first as VFAT and the second as ext3) before you installed CM7? I'm not sure what steps from my post you followed and what steps you skipped: you mentioned you were planning to modify the scripts/ROM, right?
It is also possible that my script is not doing the right thing on CM7 since it doesn't touch the vold.fstab on it. Get me the output of a mount command in CM7, and these files:
Code:
/system/etc/vold.fstab
/system/build.prop
Also make sure that you, or the ROM provider, haven't enabled the SD card switching in Settings > Cyanogenmod settings.
The SD I'm using was in a SG3 using this ROM, so I think it's correctly partitioned. I've accessed the partitions before and the correct names are associated with the contents. I only followed steps 1 & 4. The option to use removable for apps and media is disabled.
build.prop
mount.txt
vold.fstab