Now that we have our own forum, time to stake a claim.
Nooter is an image that's loaded to a microSD card that can boot the Nook Color into a basic Linux environment. It automatically enables adb and turns off ro.secure on bootup, so no interaction is necessary to get root. Nooter sets up the USB port as a USB ethernet device (RNDIS) compatible with most modern OSes to allow SSH logins. From there the ROM can be dumped, partitions mounted and edited, and (hopefully someday) bricks debricked.
Get it here: Nooter 0.2.
Up-to-date directions at http://nookdevs.com/NookColor_Rooting
Changes
0.1
first release
0.2
replaced composite CDC USB device with RNDIS. This should "just work" under most XP and later Windows
add ext2tools, dosfstools, util-linux for manual flash disk reformatting
Thanks to [mbm] for the root procedure, kernel config, and not sleeping; KCHASE731 for dissecting his NC for vital clues about the hardware config; and the rest of #nookdevs
If we've already rooted with Nooter v.01, and are using windows, is there any harm in rooting again with Nooter v.02?
Oh, and THANKS!
jasoraso said:
If we've already rooted with Nooter v.01, and are using windows, is there any harm in rooting again with Nooter v.02?
Oh, and THANKS!
Click to expand...
Click to collapse
Both versions will write the file to turn on adb every time they boot, but will only patch the ramdisk if it hasn't been done already. There's no difference in the rooting procedure from 0.1 and 0.2, just the tools for people wanting to get a shell outside of Android.
Not working for me
I must have done something wrong, but my NC just boots like normal, it never boots off the microSD card.
I am using Ubuntu Maverik.
I install the SD card while the nook is powered down and then I plug the USB cable to the computer, which automatically starts the NC, but it just boots in the OS like normal. after the NC boots, it will connect the sd card and flash memory like normal, and show the nooter02 sd contents.
Any suggestions?
EDIT: OK, figured it out, I used mmcblk0p1, instread of mmcblk0
Yesss !delivered
Hi
I receive my NC today !. It's great nooter 0.2 is awesome for two points :
it gives root access and ...
It demonstrates that the overclock is possible, because the uImage/u-boot force the clock to 1Ghz and it's working well
Code:
cat cpuinfo_cur_freq
1000000
About 997 bogomips
Cheers
Occip
Woot! Thanks for the revised tool to root from the Windoze world!
I'll have to give this a try when I get home...
So, if we used Nooter0.2, we are running 1Ghz?
occip said:
It demonstrates that the overclock is possible, because the uImage/u-boot force the clock to 1Ghz and it's working well
Click to expand...
Click to collapse
I imagine that only while running off SDCard
occip said:
Hi
I receive my NC today !. It's great nooter 0.2 is awesome for two points :
it gives root access and ...
It demonstrates that the overclock is possible, because the uImage/u-boot force the clock to 1Ghz and it's working well
Code:
cat cpuinfo_cur_freq
1000000
About 997 bogomips
Cheers
Occip
Click to expand...
Click to collapse
Heh, I never even checked! I used the config for the Zoom3 sdk (OMAP3630 like the DX) for x-loader and u-boot and I guess that's where that gets set.
We should have BN's sources for both soon enough, and it will be a very easy change to the stock bootloader to get 1GHz in Android.
ryoojin83 said:
I must have done something wrong, but my NC just boots like normal, it never boots off the microSD card.
I am using Ubuntu Maverik.
I install the SD card while the nook is powered down and then I plug the USB cable to the computer, which automatically starts the NC, but it just boots in the OS like normal. after the NC boots, it will connect the sd card and flash memory like normal, and show the nooter02 sd contents.
Any suggestions?
EDIT: OK, figured it out, I used mmcblk0p1, instread of mmcblk0
Click to expand...
Click to collapse
Um, help? I'm following the directions and I'm familiar with the mmcblk0 from my multiple phones, but I don't understand how that applies here. I'm using Maverick and get the same thing you do...it just boots normally.
Thanks
weiln12 said:
Um, help? I'm following the directions and I'm familiar with the mmcblk0 from my multiple phones, but I don't understand how that applies here. I'm using Maverick and get the same thing you do...it just boots normally.
Thanks
Click to expand...
Click to collapse
are you using a dedicated microsd reader or your phone or the nook itself to flash the image?
I just confirmed that nooter broke the NC's in-store features, such as read any book for up to 1 hour per day. Any chance of looking into this?
daveknights said:
I just confirmed that nooter broke the NC's in-store features, such as read any book for up to 1 hour per day. Any chance of looking into this?
Click to expand...
Click to collapse
All Nooter does is set a flag to turn on adbd and turn off the root lockdown flag. Either the BN app checks that root or adbd aren't enabled, or the ramdisk is signed and the process of unpacking, changing the security flag, and repacking the ramdisk screws up the signature. You could try copying the ramdisk.img from partition 3 over uRamdisk in partition 1, which would unroot but leave adbd running, and see if that re-enables the store features. Of course, you'd have no root, but if you just want basic apps then that might be enough.
I am using windows vista 32 sp2 and could not get root. help question. In the windows USB ADB instructions with the copy and paste part
;B & N Nook Color ; %SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002 %CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
why do i get
this bottom part stuck to it
Read more: http://nookdevs.com/NookColor_USB_ADB#ixzz17adJ0qwv
Under Creative Commons License: Attribution Non-Commercial Share Alike
along with my copy and paste. anyone know where this last line come from.
Also about this part of the process with rooting
Once the devices show up, wait another 30 seconds while the script makes the changes to enable ADB. (ADB will be available after you reboot into Android)
is it 30 sec or 5 min's I have read hear on the XDA boards it is 5 mins to enable ADB. It is hard to tell cause nothing really happens.
Once rooted is there a firmware (#) difference i can check to see if it worked
This is the 2nd time i am posting this as before i got no answers
I've been trying this for up to 2 mins, both with Windows and Mac and I'm kinda sure the root isn't working for me. I just received the NC, so is it possible B&N updated over the weekend in response to the news?
Is there a way to check version of firmware/bootloader/etc?
EDIT: Ok got it working amazingly. I uninstalled the driver (Android ADB Interface) and checked the delete files option. When I rescanned it found it and installed the correct drivers under W7.
pokey9000, is the uRamdisk.bak file on partition 1 something nooter created or is that a how the stock NC comes? and if nooter creates it, would deleting uRamdisk and renaming uRamdisk.bak to uRamdisk unroot the NC just like copying the ramdisk.img file over from partition 3?
do you have any documentation on what else (specific files) nooter modifies?
would it be possible to unroot a NC without doing a factory reset?
ruze said:
EDIT: Ok got it working amazingly. I uninstalled the driver (Android ADB Interface) and checked the delete files option. When I rescanned it found it and installed the correct drivers under W7.
Click to expand...
Click to collapse
I had to do the same exact procedure to get a Win7 machine to talk with my NC over ADB.
jsmith.nook said:
pokey9000, is the uRamdisk.bak file on partition 1 something nooter created or is that a how the stock NC comes? and if nooter creates it, would deleting uRamdisk and renaming uRamdisk.bak to uRamdisk unroot the NC just like copying the ramdisk.img file over from partition 3?
do you have any documentation on what else (specific files) nooter modifies?
would it be possible to unroot a NC without doing a factory reset?
Click to expand...
Click to collapse
Nooter modifies the default.prop to allow root in uRamdisk after copying the original to uRamdisk.bak. Then it creates /data/property/persist.service.adb.enable to turn on adb. So copying uRamdisk.bak to uRamdisk and deleting /data/property/persist.service.adb.enable will put things back to normal. But you'll still have app specific content in /data/app, /data/dalvik.cache, /data/data, anything you do to /system, etc.
pokey9000 said:
Nooter modifies the default.prop to allow root in uRamdisk after copying the original to uRamdisk.bak. Then it creates /data/property/persist.service.adb.enable to turn on adb.
Click to expand...
Click to collapse
Would modifying default.prop to enable adb there, rather than create the property file, also work? Or does that have no effect?
Thank you for this great tool. Your work is greatly appreciated.
Related
Hello,
I have prepared a few update.zip's with kernels to boot linux:
There are two different zips.
One to boot linux from a USB Flashdrive and the other from a SD card.
Installation Instructions:
ALWAYS HAVE CHARGER CONNECTED WHEN UPDATING A FIRMWARE.
1. Please follow the instructions here to prepare your SD / USB Drive - start at "== Create a rootfs SD card ==". http://ac100.gudinna.com/README/
2. Extract contents to a folder and follow instructions below.
copy the update.zip to a sdcard, and insert sdcard into folio.
Enter "Recovery menu" when folio is just turned on and press (POWER) once and (VOL up) next.
press (VOL up) Factory reset or system update.
press(VOL down) to continue to system update.
press (VOL up) to confirm system update.
during installation progress bar will show har far it is.
folio will reboot after installation.
insert the usb or flashdrive with the prepared filesystem into the folio and the tablet will boot automaticly from it
This sounds very interesting, might give it a try when im done playing with my new folio, ubuntu on it would be awesome
Does it boot to a full Ubuntu desktop or a bash prompt?
key combination to boot ubuntu
DerArtem said:
Hello,
I have prepared a few update.zip's with kernels to boot linux:
Please follow the instructions here to prepare your SD / USB Drive - start at "== Create a rootfs SD card ==".
Unzip the zip and then use the zip inside to update your kernel.
There are two different zips.
One to boot linux from a USB Flashdrive and the other from a SD card.
Click to expand...
Click to collapse
Hi DerArtem,
once the media (SD) is setup, you need special key combo in order to let folio boot from the SD? thanks in advance.
zoken4 said:
Does it boot to a full Ubuntu desktop or a bash prompt?
Click to expand...
Click to collapse
It depends on what you have put on your sd / usb flash.
Ivalex said:
Hi DerArtem,
once the media (SD) is setup, you need special key combo in order to let folio boot from the SD? thanks in advance.
Click to expand...
Click to collapse
I have updated the 1st post.
DerArtem said:
It depends on what you have put on your sd / usb flash.
I have updated the 1st post.
Click to expand...
Click to collapse
gorgeous!
got it, the first step, is exactly the same as uploading a mod. then the SD modified as per gudinna instr. will bring you to linux.
thanks again.
how fast/responsive is this? Can you benchmark it against the AC100 netbook running the same image - that had a noticeable lag at least on SD card access.
How prepare the SD?
Thank you for your work!!!
I did all the process but I can't start linux.
The kernel boots but stop without start the desktop.
You can see when stops in this image:
ifisc.uib-csic.es/~edu/fotos_folio100/1.jpg
(Put the http:..., I can't put links because the system)
I prepared the filesystem in a SD card only decompressing the tar.gz, ¿Is necessary recompile the kernel or something like configure it?
Shark.
Shark17 said:
Thank you for your work!!!
I did all the process but I can't start linux.
The kernel boots but stop without start the desktop.
You can see when stops in this image:
ifisc.uib-csic.es/~edu/fotos_folio100/1.jpg
(Put the http:..., I can't put links because the system)
I prepared the filesystem in a SD card only decompressing the tar.gz, ¿Is necessary recompile the kernel or something like configure it?
Shark.
Click to expand...
Click to collapse
I have not tested it using a SD-Card. I will try it out when I have some time...
I met the same problem : stuck at the "no console found" point, and this either with an sd-card or a usb key. I also tried wolfx's method (boot via fastboot), and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
DerArtem : could you tell us what distro you put on your usb-key ? (and maybe even with links for download ?)
Regards,
eRaph
USB tried
I tried with the USB and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
Click to expand...
Click to collapse
I'm agree with your opinion.
I confirm that the method is not agressive for the tablet, restore android works for me.
Actually, I just found what the problem was : on the image I uncompressed on the usb key (tegra-rootfs.tgz), the /dev directory was empty, and lacked a console and a null entry (see h**p://ubuntuforums.org/showthread.php?t=28550)
The folowing command solved the problem (to do on your sdcard/usbkey) :
cd dev
mknod -m 660 console c 5 1
mknod -m 660 null c 1 3
Hi,
eraph2 said:
I met the same problem : stuck at the "no console found" point, and this either with an sd-card or a usb key. I also tried wolfx's method (boot via fastboot), and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
DerArtem : could you tell us what distro you put on your usb-key ? (and maybe even with links for download ?)
Regards,
eRaph
Click to expand...
Click to collapse
I have used gentoo linux on a usb flash:
http://dev.gentoo.org/~armin76/arm/tegra2/install.xml
http://www.gentoo.org/doc/en/handbook/handbook-arm.xml
eraph2 said:
Actually, I just found what the problem was : on the image I uncompressed on the usb key (tegra-rootfs.tgz), the /dev directory was empty, and lacked a console and a null entry (see h**p://ubuntuforums.org/showthread.php?t=28550)
The folowing command solved the problem (to do on your sdcard/usbkey) :
cd dev
mknod -m 660 console c 5 1
mknod -m 660 null c 1 3
Click to expand...
Click to collapse
Yes, this files exists in the gentoo in the .tgz ....
I think that ubuntu might require a initrd...
And ubuntu works?
Can you start ubuntu fixing this?
Console
Creating the console in the dev..., ¿are you started ubuntu?
I successfully managed to boot the ac100 ubuntu image (tegra-rootfs.tgz) copied on my sdcard. X started well, and hooking a keyboard, I managed to create a user, edit his password, ...
Nevertheless, I did not manage yet to make both a keyboard and a mouse work at the same time (the usb hub does not seem to work), and unpluggin/replugging the keyboard did not work either.
So, the ac100 ubuntu image works somewhat (in text mode via ALT-F1, i managed to get root access), but seems to lack some hardware support (which is quite normal).
The first problem is probably that the boot.img I used was the one DerArtem provided with his modified sdmmc-update.zip archive, which contains a 2.6.32 kernel, whereas the ubuntu image uses a 2.6.29-ac100 kernel, hence no modules get loaded. I should find how to rebuild a boot.img with the good kernel (or better : add the good modules to the ubuntu image).
DerArtem : may I ask you how you did rebuild the boot.img in your various packages ?
Regards,
eRaph
eraph2 said:
I successfully managed to boot the ac100 ubuntu image (tegra-rootfs.tgz) copied on my sdcard. X started well, and hooking a keyboard, I managed to create a user, edit his password, ...
Nevertheless, I did not manage yet to make both a keyboard and a mouse work at the same time (the usb hub does not seem to work), and unpluggin/replugging the keyboard did not work either.
So, the ac100 ubuntu image works somewhat (in text mode via ALT-F1, i managed to get root access), but seems to lack some hardware support (which is quite normal).
The first problem is probably that the boot.img I used was the one DerArtem provided with his modified sdmmc-update.zip archive, which contains a 2.6.32 kernel, whereas the ubuntu image uses a 2.6.29-ac100 kernel, hence no modules get loaded. I should find how to rebuild a boot.img with the good kernel (or better : add the good modules to the ubuntu image).
DerArtem : may I ask you how you did rebuild the boot.img in your various packages ?
Regards,
eRaph
Click to expand...
Click to collapse
Hi,
please search on the web how to rebuild the boot.img. This is not a problem. My zip also contains the config to rebuild the kernel. The sources of the kernel are also documented in the readme inside the zip. The initrd is just empty.
But running ubunu on the folio might be a bad idea. Ubuntu is compiled for NEON instruction set, but the Tegra 2 CPU does not support this, so a lot of applications can crash when they will try to execute more advanced code....
Debian (optimized for ARMv6 without NEON) or Gentoo are better for the Folio.
Then, if I want to install gentoo instead ubuntu, do I have to follow the same steps but changing the distro linux for the gentoo? Or is it necessary to do anything else?
Thanks
I tried to install gentoo in a USB, but it's a long process and it's not usual for me.
I'm very lost!
halu:
If you obtain a opetative distro image, can you upload in any place?
I'm thinking in write a howto with the results.
Bests
(Saludos desde Mallorca!! )
*ALL THE USUAL DISCLAIMERS AND WARNINGS*
*THIS IS FOR VERSION 1.1 ONLY, DON’T TRY ON 1.0.0 OR 1.0.1*
Credit goes to: GabrialDestruir for the original auto-nooter, GLa’DOS for the boot animation, pokey9000 for nooter, Mistar Muffin for Market and GTalk Fix, clockworx for the “non-ugly” patch that is used to get androidID, mastapsi for testing and coding of the original auto-nooter, lewellyn for coding, [mbm] for ABI Fix, Hotaru for the Gingerbread keyboard, rpollard00 for DroidX keyboard with bigger font, bpk for Soft Keys, Ben74 for NookColor Tools which enables Non Market Installs and re-enable of ADB , Freenode's #nookcolor chat for code checking. A special thanks to all developers out there, without all of you this community would not be as great as it is.
Please Note: If you are the developer of an app that is included in this work, and would like me to remove it, feel free to contact me.
*I am copying the following step from the original auto-nooter, because they are tried and true, and people are already familiar with seeing them*
What it does:
Installs su and Superuser.apk
Installs Busybox with whoami
Installs Softkeys 3.0.6
Installs NookColor Tools (To Enable Non-Market Installs, and re-enable ADB)
Installs Calendar and Calculator.
Installs Android Market, Gmail, Youtube
Installs Gingerbread Keyboard
Enable ADB
Enable Multi-touch for Android Apps
Enables Live Wallpapers
Enables Android Market and Gmail.
App Auto Install (Open up NooterFiles from sdcard drop in /data/app)
Known Problems:
With the version 1.1 update, ADB will not stay active after a reboot or unplug of the cable. To enable each time you want to use it, you will have to go into NookColor Tools /All Settings/Development/USB debugging, you will have to uncheck the box and then recheck it.
How to Use:
Before you begin:
* To update to 1.1 you must do a complete wipe.
* You must update to 1.1 to use Auto-Nooter 3.0.0 Instructions HERE.
1 You must already have a registered NOOKcolor
2 You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
3 You must either have dd (Linux) or WinImage (Windows) software.
4 You must have an external microSDCard reader or this will not work. Do NOT use the NC.
5 You must have enough intelligence to follow instructions.
Let's get started:
1 Download Auto-Nooter from here: MultiUpload or MediaFire
*MD5 FB74865663B8D797A486A85022FAD9B2*
2 Linux: Unzip and use dd if=auto-nooter-3.0.0.img of=/dev/sdcard
2 Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
2 Windows Alternative: https://launchpad.net/win32-image-writer/+download
3 Unplug your NOOKcolor from computer. (If Plugged in.)
4 Insert AutoNooter SDcard into your NOOKcolor.
5 Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)
6 Your NookColor will reboot when it's done.
That was the hard part, now to the simple stuff.
7 Upon boot unlock your screen.
8 At the Android Welcome Screen skip Sign In.
9 Enable Location Services when given the option.
10 Connect to Wifi and launch Youtube from "Extras".
11 Click the Menu button (The one RIGHT of the Up Arrow).
12 Select "My Channel" and Login using your Gmail Account.
13 Exit Youtube and Launch Gmail from "Extras".
14 Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
15 Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
16 Enable Non-Market Installs by running the NookColor Tools App.
17 If your Youtube fails to launch, download the attached EVO HQ, and follow this code in adb
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb uninstall com.google.android.youtube
adb push YouTube.apk /system/app
adb reboot
18 Go to Settings > Device Info > SdCard > UnMount > Format
Complete Wipe:
1 8 Failed Boots > Wipes /system
2 Factory ResetFactory Reset > Wipes /data
*You must do both of these to completely wipe clean your NOOKcolor.*
*Before anyone starts to say that I took this project away from GabrialDestruir, I posted this file in the original post, and sent the OP a PM asking to update the current project. I have yet to hear back, and the post was not updated. My post can be found HERE, dated February 2, 2011. I felt that this would be of a benefit to the community, so I am posting it now. If I am asked at some point to take it down I will do so at that time.*
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
I have never really seen an explanation as to why you don't format on the NC. I have formated via the NC and the card works fine both in the NC and my PC. When I want to burn an image, I have been able too. Been able to flash other images on it too.
Excellent!
Can you please add an MD5 to the first post?
Homer
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
Formatting the SDcard doesn't touch the onboard storage. It is one of the easier ways to remove bonus partitions to recover the full card. UPDATE: I should clarify this: when running Eclair internally.
Homer
Any benefit of this over the 1.1r2 many of us did from autonootered 1.0.1?
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
You're thinking of Nookie Froyo. The stock B&N system is fine for formatting the card.
I think formatting the SD card is an issue when you use one of the Froyo images and boot from eMMC. When you format the SD card it actually formats the internal boot partition or some such. I remember reading it in one of the threads which led me to only boot the Froyo images from an external card.
I am at 1.1.0. When did 1.1.1 appear & how do I get it?
BTW Is this exactly the same as the interim A-N 2.12.25 modified for 1.1?
k
I'd say it's a typo and should be v1.1?
Canadoc said:
Any benefit of this over the 1.1r2 many of us did from autonootered 1.0.1?
Click to expand...
Click to collapse
also interested to know that!
And if there is benefits, can we use the auto nooter?
Just for clarification, in steps 3 & 4 should the NC be turned off? I have never been sure if it matters, but the following statement makes me think that it should be off,
"5 Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)"
Thanks,
kev
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
Only with the froyo image.
Canadoc said:
Any benefit of this over the 1.1r2 many of us did from autonootered 1.0.1?
Click to expand...
Click to collapse
The main difference I see is that Clockwork recovery is not involved.
johnny054 said:
also interested to know that!
And if there is benefits, can we use the auto nooter?
Click to expand...
Click to collapse
I guess it should be the same, but I had a couple of games break after up'ing with 1.1_r2. So I wanted to try stock/clean 1.1 and then root...hoping this would bring them back.
help please
I'm having a problem rooting my nook color. 2 weeks ago I was fully rooted and for some reason I forget why? but I went back to stock. recently I updated to the newest Barnes & noble firmware. seeing the recent developments of honeycomb I wanted to root my nook again. so I tried downgrading to firmware before the most recent update and using that version of auto nooter. I followed the instructions exactly to a tee. the problem is my nook wont load the disk image from the sd card. I made sure to fully format the sd card before writing the img with Win32DiskImager. I made sure the nook was completely off then plugging in the usb to into the pc to wake up the nook. but nothing? the nook boots up like normal then says sd card damaged. I've formatted the sd card again and have used the newest nooter for my current 1.1. but nothing. the only difference is the first time I rooted I was at my mothers and used her pc. it was a windows vista 64 bit. my computer is windows seven 64 bit. anyone have any idea's as to why the nook wont load the sd card with the nooter image? I'm using the same sd card I was able to root from before. so I seriously doubt its the sd card. I am properly formatting it before writing the img. I am having no problem writing the img. any help would be appreciated
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
brianf21 said:
Only with the froyo image.
Click to expand...
Click to collapse
Ok thanks for that clarification. I was pretty sure I read it somewhere!!
trentmaynard said:
I'm having a problem rooting my nook color. 2 weeks ago I was fully rooted and for some reason I forget why? but I went back to stock. recently I updated to the newest Barnes & noble firmware. seeing the recent developments of honeycomb I wanted to root my nook again. so I tried downgrading to firmware before the most recent update and using that version of auto nooter. I followed the instructions exactly to a tee. the problem is my nook wont load the disk image from the sd card. I made sure to fully format the sd card before writing the img with Win32DiskImager. I made sure the nook was completely off then plugging in the usb to into the pc to wake up the nook. but nothing? the nook boots up like normal then says sd card damaged. I've formatted the sd card again and have used the newest nooter for my current 1.1. but nothing. the only difference is the first time I rooted I was at my mothers and used her pc. it was a windows vista 64 bit. my computer is windows seven 64 bit. anyone have any idea's as to why the nook wont load the sd card with the nooter image? I'm using the same sd card I was able to root from before. so I seriously doubt its the sd card. I am properly formatting it before writing the img. I am having no problem writing the img. any help would be appreciated
Click to expand...
Click to collapse
You probably have a bad burn on the sdcard. Are you writing to the sdcard from the sd card reader or from the nook? Also, if you return to stock, (8 failed boots, then Power+N) You should be on firmware 1.0.0 or 1.0.1. Then root using one of the two original auto nooters, download rom manager from the market and flash the 1.1 pre-rooted firmware.
Thanks buddy, I try doing that. and I don't have an sd card reader so I just put the sd card that I'm going to write into my cell phone. then mount the sd card and write the img to the same storage device that represents the sd card. I'm sure this is the wrong way of doing it but I have gotten root doing the same thing before
Giving this a go now, coming from auto-nootered 1.0.1.
So i recently installed urukdroid 1.0 on my A101IT.
I've been loathing the stock battery icon and though I'd install the batterymod found here:
http://forum.xda-developers.com/showthread.php?t=982529
(took the 2.3.20 firmware one)
Now I don't have ADB on my pc anymore so I thought I'd just use root explorer and drop both files in /system/framework/
After i copied the framework file however i'm stuck in the endless booting animation. (didn't copy services.jar yet)
Anybody that can help me resolve this issue ?
Why didn't you copy both files while doing it, or did it reboot as soon as you over-wrote your framework? One would assume that you need both of them copied (because the instructions say to).
Copying through root explorer with Android running could have been the problem. That's why the instructions have you issue a stop command first.
Rebooted as soon as i copied the framework.
(even trying to acces the uruk partition with a linux and recovery usb msc didn't work, only got to see my internal storage)
Well I guess I'll just have to reinstall urukdroid.
Greenthy said:
Well I guess I'll just have to reinstall urukdroid.
Click to expand...
Click to collapse
This s the fastest and best thing you can do about soft problems
Greenthy said:
Rebooted as soon as i copied the framework.
(even trying to acces the uruk partition with a linux and recovery usb msc didn't work, only got to see my internal storage)
Well I guess I'll just have to reinstall urukdroid.
Click to expand...
Click to collapse
You should really get an SD card reader. It's 5 bucks, and lets you fix things like this very easily. Or you can use an Android phone to mount it.
In the future, use adb and the "stop, copy, sync, start" method. If you get stuck in a bootloop, you will still be connected through ADB, and can restore the original framework very quickly.
I have an sd reader
It's just that :
- it's ext4 so my windows 7 is failing
- on ubuntu i don't have ownership : no write :s
(that last can be fixed i read with sudo nautilus)
messed it up again and even dropped my tablet : croocked mini-usb :S
Fail I hope it's just the cable that's giving me somewhat of a loose-contact now though, i have another mini-usb -just not at hand atm- but not another archos
Greenthy said:
So i recently installed urukdroid 1.0 on my A101IT.
I've been loathing the stock battery icon and though I'd install the batterymod found here:
http://forum.xda-developers.com/showthread.php?t=982529
(took the 2.3.20 firmware one)
Now I don't have ADB on my pc anymore so I thought I'd just use root explorer and drop both files in /system/framework/
After i copied the framework file however i'm stuck in the endless booting animation. (didn't copy services.jar yet)
Anybody that can help me resolve this issue ?
Click to expand...
Click to collapse
Strange since i had no problems doing it with root explorer, though i might have done int the other way round, might have copied services.jar first and then the framework-res.apk after that
TjaXanK said:
Strange since i had no problems doing it with root explorer, though i might have done int the other way round, might have copied services.jar first and then the framework-res.apk after that
Click to expand...
Click to collapse
Using Root Explorer will give you a boot-loop 40-50% of the time. You really shouldn't use it. Processes start terminating immediately after you start overwriting the framework. If the copy process terminates before it's done, you get a boot-loop. The only way to avoid that is to issue a "stop" command through ADB first. Use ADB to do the "stop, copy, sync, start" method.
Greenthy said:
I have an sd reader
It's just that :
- it's ext4 so my windows 7 is failing
- on ubuntu i don't have ownership : no write :s
(that last can be fixed i read with sudo nautilus)
messed it up again and even dropped my tablet : croocked mini-usb :S
Fail I hope it's just the cable that's giving me somewhat of a loose-contact now though, i have another mini-usb -just not at hand atm- but not another archos
Click to expand...
Click to collapse
I had to resolder my usb back onto the board. Ripped it completely out.
msticninja said:
Using Root Explorer will give you a boot-loop 40-50% of the time. You really shouldn't use it. Processes start terminating immediately after you start overwriting the framework. If the copy process terminates before it's done, you get a boot-loop. The only way to avoid that is to issue a "stop" command through ADB first. Use ADB to do the "stop, copy, sync, start" method.
Click to expand...
Click to collapse
Actually now that i think about it I didn't use root explorer I moved the files with the terminal on the deivce
TjaXanK said:
Actually now that i think about it I didn't use root explorer I moved the files with the terminal on the deivce
Click to expand...
Click to collapse
Terminal is a bad idea as well! It has the same issue, it can terminate in the middle of copying. You must put the system into "stop" to avoid that, but you cannot use the device itself when in "stop" mode, thus ADB.
Okay guys, so here's a weird one.
My g-tablet was working great. Was running VEGAn-Tab Build, BETA 5.1.1, no reason to update it, because it did everything I needed. I finally had it to where I wanted it, then it all kind of started falling apart. Here's how.
I power it on and notice my home screen got all messed up for some reason (using launcher pro). All of the settings defaulted to the original. I tweaked it back to more or less how I wanted it, and when I had it back to normal, thought nothing better of it. Must have glitched out some how.
Then I notice a bunch of things starting to force close, specfically android market, amazon market, titanium backup, google services framework, launcher pro, etc. Odd thing is it would do it one at a time, but otherwise my tablet would carry on as normal.
I go ahead and restart the tablet, to see if that helps at all, and what do you know, the homescreen is messed up again! I thought launcher pro might have been the culprit, so I un-installed the app and rebooted... And launcher pro is still there.
I go ahead and delete it again and start deleting other apps, restarting the tablet, and no matter what I do, everything stays the same. time for some clockwork mod action. I go into clockwork mod, and try to do the factory reset option, thinking what the hey, I'll try anything right now. Hit it, mourn the loss of my user data, and reboot the system... and again, everything is still the same.
I hook up my tablet to the computer via usb, and it looks like I'm able to at least delete misc. files that way. But when I return to good old Tabatha (my nickname for Gtab) everything is stuck just the way it is.
Needless to say, it feels like I'm stuck in the twilight zone.
I know I should have researched it by now, but I'm going to finally look it up to see if I can recover with NVFlash (I know I know, very noobish of me, using strange roms and not knowing any of the basics).... but I'm increasingly worried I've got some kind of a hardware malfunction on my hands. Could it be the memory? The internal SD card?
Oddly enough, my tablet still functions... I can browse the web, hook it up to my computer, etc etc, but no matter what I do I can't alter the data I already have on my tablet. Can't delete things, can't change settings, update apps, etc. etc. Which makes it pretty much useless for what I wanted to use it for.
I finally realized what this is like. The movie groundhog day, and I'm stuck in the same day, over and over again.
Any help or input that might get me out of this mess would be greatly appreciated.
Phil: "I was in the Virgin Islands once. I met a girl. We ate lobster, drank piña coladas. At sunset, we made love like sea otters. *That* was a pretty good day. Why couldn't I get *that* day over, and over, and over..."
This is now the second time that I've seen this exact same problem. I was in the process of troubleshooting the original one when the user returned his gTablet for replacement. If you can stand the deja vu, read this thread.
Do not nvflash your tablet--nvflash cannot fix SD-card related problems. Read this post for why not.
Instead, do this for me: Reboot the gTablet, then open a Terminal, or, use adb and run this command:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
Attach that dmesg.txt which will contain messages from the kernel to your next post.
I'll check this thread in the evening.
rajeevvp said:
This is now the second time that I've seen this exact same problem. I was in the process of troubleshooting the original one when the user returned his gTablet for replacement. If you can stand the deja vu, read this thread.
Do not nvflash your tablet--nvflash cannot fix SD-card related problems. Read this post for why not.
Instead, do this for me: Reboot the gTablet, then open a Terminal, or, use adb and run this command:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
Attach that dmesg.txt which will contain messages from the kernel to your next post.
I'll check this thread in the evening.
Click to expand...
Click to collapse
Thanks for the direction, at least I know it isn't an isolated incident. It's 1:45 AM where I am right now, and I have to wake up for work in about 5 hours... So I probably won't be able to get in depth with the follow up on this stuff untill after work tomorrow night (so long as the wife doesn't hog the computer )
Again thanks for the quick response, I appreciate you pointing me into some sort of direction. Can't wait to try to get this sorted out!
Currently trying to figure out how to get ADB going.... pretty intimidating, but I'm trying. I got the Java JDK installed, installing the SDK, but can't find the "SDK Setup.exe" file or even a USB driver folder in the SDK directory. Got a good resource for getting ADB set up?
Save yourself some trouble. Got to http://www.knoppix.org/ and download the latest Knoppix live CD image.
Burn it, boot it, then use the adb executable from this post. For simple things like just running adb, you don't need the entire Android SDK.
Get me a dmesg while inside ClockworkMod:
Code:
$ [B]sudo ./adb shell dmesg > dmesg.txt[/B]
ADB commands documentation
Thanks, I'll try it out sometime this weekend!
Well, I really screwed myself now. I got the Linux distro loaded but still couldn't figure out how to get ADB to work. For whatever reason, When I boot from the DVD, I can't download the zip from within linux (get errors) and I could not open the ADB command by navigating to where I have it extracted in my hard drive. [Do I need to load the OS onto a flash drive instead?]
So I started messing with some stuff in clockwork mod. I apparently really goofed it, and I got a "Magic Value Mismatch" error everytime I tried to boot it up.
I looked up Magic Value Mismatch, and from there it pointed to using NVFlash to try to fix that problem. So tried that. After I flashed it, I thought for sure I finally had it back to stock, as the intro screen started to show the tap n tap logo... but i basically got stuck in a boot loop, tap n tap, then "n", then tap n tap, then "n", etc, until it dies.
I looked up this issue and apparently the key is to get into clockwork mod and do factory reset, reset cache, and partition the SD card to 2048 and 0, which I did... (per post #4 on this thread: http://www.slatedroid.com/topic/17501-helpstuck-in-bootloop/ ) but still no dice.
Not sure where to go from here, or if I can even get it to interface with ADB in its current state. Looks like I'm done for
Thanks for trying though
On second thought, I may have had a breakthrough, at least in getting ADB to see my tablet!!! Woohoo! It finally sees the device and has a serial number. Was following the device on this thread:
http://www.androidtablets.net/forum/viewsonic-gtablet-technical/5377-adb-g-tab-step-step.html
7. under the "[Google.NTx86]" section, paste the following:
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
save the file and exit.
But I have a 64 bit machine, so I finally figured it out and plopped that into the 64 bit portion of the .inf file. DOH!
So now let me see what I can drum up through the previous commands above.... though the parameters have changed now to be sure... Due to my haste things may have taken a turn for the worse.
To recap, now my tablet is stuck in a boot loop after having done NV Flash, after having screwed up some settings in clockwork mod trying to fix a "Magic Value Mismatch" error.
Tried:
$ dmesg > /mnt/sdcard/dmesg.txt
I just run this in the cmd prompt at my platform-tools directory where the adb is correct?
All it says is, "The system cannot find the path specified."
Am I doing something wrong, or is my tablet that messed up?
Okay, this is slightly weird. So I was browsing around in clockwork mod, and lo and behold, the original zip flies for vegan tab are all STILL THERE. So I reloaded them... And My tablet zips back to exactly the way I had it before!
Only this time, so far no force closes. This looks way too good to be true after what I've been through. I'm going to try modifying some files and settings and restart my tablet to see what it does. I'm pretty sure I can't be out of the woods yet. Allthough it is 3:33 AM as this is happening... magic hour. I may be going insane.
EDIT: Nope, was definitely way too good to be true. All my data is as stuck as it was ever was. But at least now I can get into it again. But now we're back to square one. Lemme figure out this dmesg business and get back to you. X(
So I would try issuing the following exactly in the command line at the adb platform tools folder:
$ dmesg > /mnt/sdcard/dmesg.txt
Is that code supposed to be copy and paste in? I don't seem to be getting anything. I can do the following command and get the info to pop into the command interface:
adb shell dmesg
But I can't figure out how to save that to a text file. And you want me to do that while the g tablet is in recovery, correct?
FYI, trying to do it through Windows 7. Would that command only operate in the linux environment via knoppix?
Thanks
titobetlogs said:
I can do the following command and get the info to pop into the command interface:
adb shell dmesg
But I can't figure out how to save that to a text file.
Click to expand...
Click to collapse
Redirect the output to a file:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
titobetlogs said:
I got the Linux distro loaded but still couldn't figure out how to get ADB to work. For whatever reason, When I boot from the DVD, I can't download the zip from within linux (get errors) and I could not open the ADB command by navigating to where I have it extracted in my hard drive.
Click to expand...
Click to collapse
I suggested using Knoppix just because it is so easy to use adb in Linux. Broken-down steps for future reference:
1. Download and burn the latest Knoppix Live CD iso image. Check the downloaded file size. The .iso file should be ~700MB in size. Also, test the CD by booting it and then typing at the boot prompt: knoppix testcd
2. Boot Live CD and skip the creation of any partition or file to store user data. After all, we just want to run adb.
3. After Knoppix has booted into the desktop, run a browser, right click on the adb.zip attachment in this post, then select "Save Link As..." and save the zip file into /tmp.
4. Connect the gTablet to the PC via the USB cable.
5. Open a terminal window, then type in it:
Code:
hostpc$ [B]cd /tmp[/B] [I]Change to the dir. where adb.zip was saved[/I]
hostpc$ [B]unzip adb.zip[/B] [I]Unzip zip file[/I]
hostpc$ [B]ls -l adb[/B] [I]Check if the adb program was extracted OK[/I]
-rwx------ 1 rvp rvp 159620 Dec 1 22:23 adb
hostpc$ [B]chmod 555 adb[/B] [I]Make adb executable.[/I]
hostpc$ [B]sudo ./adb shell dmesg > dmesg.txt[/B]
Note 1: do not type in the shell prompt, 'hostpc$'. It is only there to show you what the screen should (roughly) look like.
Note 2: If adb says something like "device not found", just unplug the USB cable from the PC, wait a few moments, then re-plug the cable and re-run the adb command again.
6. Go back into the browser and attach the dmesg.txt file that is there in /tmp. You will have to tell the Noscript plugin to allow scripts from xda-developers to enable attachments. Right click on the page, then select the Noscript menu item, then choose "Temporarily allow xda-developers.com".
I thought for sure I finally had it back to stock, as the intro screen started to show the tap n tap logo... but i basically got stuck in a boot loop, tap n tap, then "n", then tap n tap, then "n", etc, until it dies.
Click to expand...
Click to collapse
I'm not surprised. If the files on the internal SD card cannot be modified then that boot loop behaviour is to be expected. Here's why:
Android requires certain partitions to exist on the system. These partitions can be either on the flash or on SD cards. The partitions are:
/system: This is where the binaries and system apps that come with the firmware are stored. This partition is usually mounted read-only to protect it. On the gTablet, this partition is on the 512MB built-in NAND flash chip.
/cache: As the name indicates, this is the partition used to speed up the execution of the Java apps. Temporary files are also created here. This partition too is on the built-in NAND flash chip.
/data: This is where user-downloaded apps are stored by default, and also where Android stores its system configuration data. This partition, on the gTablet, is on the internal SD card.
/sdcard: This is where user content like media files, books, and the apps moved to SD card are stored. This partition too is on the internal SD card.
The first 3 partitions are critical and Android won't come up without them being present (or, if there are any errors on them). Among these 3, only /system needs to be correctly populated (When you install a ROM, new stuff is copied here). The other 2 partitions, /data and /cache can be empty and the system will boot up fine--with defaults. In fact, when you select "wipe data/factory reset" in CWM, /cache and /data are re-formatted--effectively, wiped clean.
(There are 2 other important partitions on the NAND flash chip, but, these are not mounted because they don't contain a proper filesystem. You have to use special tools to create the contents of these 2 partitions.
The first of these is the "boot" partition. This one and "system" are re-written when you install a new ROM. The "boot" partition holds the Android Linux kernel. If you install a new kernel, only the "boot" partition is rewritten.
The second is the "recovery" partition. This contains a separate, and usually different (and safe), Linux kernel and a mini filesystem image. This is a fail-safe partition. Stock recovery and ClockworkMod sit here.)
In your case, nothing on the internal SD card can be modified, so the stuff in /data will still be from your old ROM. (nvflash also cannot modify SD card contents, as I mentioned before.) When the stock firmware boots up, it will find incompatible stuff in /data. Critical apps will then die. Android will restart them, they will die again. This is your boot loop.
Get me the dmesg output and then we'll run a few tests using CWM, but, judging from your previous posts, I don't think your internal SD card can be fixed. You have 2 options:
1. Return the tablet for a replacement.
2. If you can't return it, I can switch the internal and external SD cards on your ROM so that you can boot and use the system (almost) normally. But, this is a custom solution and you will need to have an external SD card in its slot always. Read through this thread.
Wow, you really know you're stuff! I'll see what I can get you later on in the day with regard to the dmesg, I'm currently still at work.
I had suspected a hardware error... bummer. I'll definitely be interested in seeing if I can just use the external micro sd slot to sub out for the internal sd card. I would at least like this thing to be functional again, though I suppose I'll never be able to try any of the honeycomb roms when those get past alpha. Oh well.
Do you know if this thing takes 32 gb micro sd cards? That would be pretty awesome, I at least wouldn't feel too limited on space.
By the way, thanks for all your help on this, I know I'm a huge noob. I greatly appreciate your patience and taking the time to break everything down for me. I have absolutely zero background in programming or anything computer related, though I do find this stuff extremely fascinating! If I could rewind the clock and study this stuff in school, I would do it in a heartbeat.
Again, thanks so much, can't thank you enough.
titobetlogs said:
I would at least like this thing to be functional again, though I suppose I'll never be able to try any of the honeycomb roms when those get past alpha. Oh well.
Click to expand...
Click to collapse
No, you should be able to run whatever ROM you want. I'll send you an installable zip file, in a few days, which should get you going again on Vegan-Tab, at least. You'll just need to remember to flash this zip file right after you've flashed the ROM (of your choice).
Right now, I don't know if I need one zip file for each kind of ROM in existence for the gTablet, or, if I can use some scripting and do the internal/external SD card switch using just a single installable zip file. I'll look into this on the weekend.
Do you know if this thing takes 32 gb micro sd cards?
Click to expand...
Click to collapse
Yes, it does.
By the way, thanks for all your help on this, I know I'm a huge noob...
Click to expand...
Click to collapse
I was a complete noob to Android myself back in April of this year. I've picked all of this up in just a few months. I'm pretty sure you can do it too, with a bit of poking around in the system. Of course, having a background in Unix/Linux helps a lot.
In your honor, below are some inspiring lyrics from the Karate Kid soundtrack:
You’re the best!
Around!
Nothing’s gonna ever keep you down
You’re the Best!
Around!
Nothing’s gonna ever keep you down
You’re the Best!
Around!
Nothing’s gonna ever keep you dow-ow-ow-ho-how-ho-own
INSPIRING GUITAR SOLO
Dude! you're embarrassing me -- I haven't send you the zip file yet... and, you haven't sent that dmesg output I wanted.
I know I've been stuck at work and family functions every day this week so far. Hopefully I'll get to it soon
Finally got to this! Here you go! Thanks again!
titobetlogs said:
Finally got to this! Here you go!
Click to expand...
Click to collapse
Can't see any problems in that dmesg output. Time for some tests on the internal SD card.
Boot into CWM, then run on PC (on Linux run: sudo ./adb shell):
Code:
C:\SOME\PATH> [B]adb shell[/B]
~ # [B]mount /dev/block/mmcblk3p1 /sdcard[/B] [I] Mount internal SD card partition[/I]
~ # [B]mkdir -p /sdcard/a/b/c[/B] [I]Make a directory tree[/I]
~ # [B]echo test > /sdcard/a/b/c/test.txt[/B] [I]Create a file[/I]
~ # [B]cat /sdcard/a/b/c/test.txt[/B] [I]Read it back again[/I]
test [I]Correct[/I]
~ # [B]echo 3 > /proc/sys/vm/drop_caches[/B] Flush kernel caches
~ # [B]cat /sdcard/a/b/c/test.txt[/B] Read it back again
test Correct
~ # [B]umount /sdcard[/B] [I]Unmount[/I]
~ # [B]mount /dev/block/mmcblk3p1 /sdcard[/B] [I]Remount /sdcard[/I]
~ # [B]cat /sdcard/a/b/c/test.txt[/B] [I]Reread file[/I]
test [I]You should see "test" here[/I]
~ # [B]umount /sdcard[/B]
You should see "test" after the kernel flush and the remount.
Next, reboot the tablet--back into CWM, then run the cat command again. `cat' should output "test", again, if the SD card is OK.
Here's a screen of the commands I entered and what I got back. Did I do anything wrong? Looks like something's a bit off.
I made it for all of you who prefer to have their Android to be installed on SD card.
What do we need:
SD card with ext2 as a second partition (I believe that most of you know how to use gparted or any other linux partition manager)
filesystem: http://www.2shared.com/file/8p5Ci18r/SDAndroid.html
fota (the same as in Shodow's tut, so if you have this, there is no need to reflash it)
Step 1
Unzip downloaded filesystem.
Step 2a
Copy the "galaxyboot" folder into internal memory of your phone (or, as Shadow named it "Bada root").
Step2b
Copy the content of "filesystem" folder into ext2 partition on your card.
Step3
Open the terminal in this directory and type:
sudo chmod -R 0777 ./*
sudo sync
Step4
Unplug your sd card and boot by pressing start call button + on/off button.
Of course, all those steps must be done under Linux.
For those who do not have custom fota flashed:
Step5
Under Windows open Multiloader, select LSI, serach for fota and download it to your phone.
This is mixed version of first version of Android port and the filesystem posted by mylove90. It provides all functions which the newest version of Android from Shadow's tutorial has.
Great thanks to Bedson from bada-os.info for keeping all the old files.
Would this port still have "easy crash" after several reboot?
*yet again mumbles something about the annoyances of more than one tutorial*
part of the reason we moved to the scripted moviNAND version is because people time and again have difficulty running commands on a Linux commandline, if someone wants to create more tutorials it would be preferred that their filesystems have chmodding and partitioning scripted requiring no user intervention through a Linux distro, if possible.
EDIT: also be prepared to answer questions and to make it known that your tutorial isn't dev-created and thus for people following it to not PM devs asking why it won't work
@nbates66
As you said, the version for movinand is a way more simple to apply. On the other hand using this version is meant to be only for those with fast small files write on their SD card (fast, i mean aroud 1 - 2MB for 4KB Q1, where most of cards are about 0,01 - 0,04MB).
And there is one more thing... Bada 2.0 which made this section a bit less popular within couple of last weeks (and I think this won't change till Oleg give us new version).
@NitramNach
The entire process hasn't been changed when compared to the old version from Shadow's TUT, so it might be as unstable as you said. I think it's rather the matter of SD card, cause I haven't crashed my phone yet.
I'm using Class 4 Sandisk SDSDQM-032G-B35, but it's like rebranded Class 2 (9MB sequential read, about 5,5MB sequential write, 1MB random 4KB Q1 read, and 2MB random 4KB Q1 write).
i'm sorry, so may i ask, it means it's stable now?
does installing android on sd card will affect the already presend bada in the phone by any way ?
am asking this becoz am very very newbie,,, never tried flashing and dont want to have the risk of flashing ,,, so , if this way dont affect the already presend bada 1.2 in the phone , i may try to install android on sd card coz really want to c android on my s8500 ...
my firmware is jpkc1 ....
@chriszue
It depend on that what do you mean by stable.
It's the same version as published by devs in Shadow's tut, but this one is prepaired to be installed on SD card.
Though the speed and stability depends on your card I can say that I've used it for 4 days without any problem.
Now I'm using Bada 2.0, so I had to resign of Android.
@sarmoodi
Nor this or the version presented on Shadow's tut have any influence to Bada.
But if, you're not familiar with linux I suggest using the movinand version.
@Qron
thanx alot for the super fast reply..
Was the microphone working in this version?
Dude I want u r help...
i compare galaxy 3 and wave 723 and they are almost got same things..>
so i m thinking about about port galaxy 3 android froyo on wave 723 is that possible to do?
if wave 2 can run android they y not wave 723?
I'm not capable to help you. I simply made a conversion of newest filesystem so it could be installed on SD card. Nothing less, nothing more. I don't have proper knowledge to make any port.
what do you meaning by "It provides all functions"?
can you make calls on this methods?
Are You kidding me??
You rip this out of context. The whole sentense was "It provides all functions which the newest version of Android from Shadow's tutorial has."
So NO!, you can not make calls using this method.
Terminal commands
I cannot access the ext2 partition through the terminal and execute sudo chmod -R 0777 ./* and
sudo sync, that is I cannot find the folder in the FileSystem where Ubuntu places the mounted partitions. Could you tell me how to do this?
I have Ubuntu 11 installed through wubi if that makes any difference.
10x in advance
Root
It would be really helpful if someone could give the syntax for rooting froyo for this SD card version.
rohitman said:
It would be really helpful if someone could give the syntax for rooting froyo for this SD card version.
Click to expand...
Click to collapse
chmod -v -R 4755 ./system/xbin/*
badelemental said:
chmod -v -R 4755 ./system/xbin/*
Click to expand...
Click to collapse
Thanks for the reply.
I've come up with another problem though, On starting Market a white screen opens & the market closes, no message though.
Should I reinstall Android to fix the problem ?
rohitman said:
Thanks for the reply.
I've come up with another problem though, On starting Market a white screen opens & the market closes, no message though.
Should I reinstall Android to fix the problem ?
Click to expand...
Click to collapse
Yes, give it a try, as far as I'm aware it should work. Maybe the installation went a little wrong, probably nothing to do with you ^^.
Hope I've helped.
i followed all the steps several times and my phone keeps hanging at galaxy s screen.
any idea of what im doing wrong?already tried ext2 and ext3.
I am unable to use the touchscreen functionality properly in android on bada. I have loaded on SD card dual boot with Bada 2.0.
I am finding difficulty in scrolling or long-press (to create shortcut in home screen) or play "angry bird" , I cannot pull and hold the catapult.
Is there any workaround ? Have others faced this problem ?