Related
*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.
I've compiled a simple app to be able to easily mount to your PC any given partition.
Feel free to donate if this app is of any use to you. Much appreciated.
Please note that changes to the drive will not be saved if you do not properly unmount/eject the drive from PC (in Ubuntu: right click, unmount. In Windows, eject.).
For those using stock browser, apk files often fail to download.. You can install Astro explorer and activate downloads in settings (last option). Then you should be able to download this file.
Dolphin should work without issues..
This is a Beta release.
This requires a working root (su). By that I mean your nook must be rooted. Regarding HC, see j4mm3r's thread.
This can be used, for example, to open your SD or internal data on your PC..
You can mount pretty much any partition to your computer with this app:
- SD
- Media (internal drive for your media and documents...)
- SD Partitions (up to 4)
- Internal storage - BE VERY CAREFUL WITH THIS!!
There are two "mount points" on the nook (lun0 and lun1)
So you can simultanously mount two partitons.
As an example, you can mount SD on 1st and MEDIA on the 2nd.
Each mount point has it's own tab.
Please try it out and post feedback.
Thank you.
EDIT (13.02.2011):
This has been tested on HoneyComb and Froyo (not in Eclair 1.0>1.1).
In Froyo: USB Mass Storage (Notification bar) should be turned off.
Compatibility mode will need to be disabled in Spare parts (reboot required).
If this doesn't work for you, try entering manually in ADB while NC plugged in to your PC:
Code:
adb shell
echo /dev/block/mmcblk0p8 > /sys/devices/platform/usb_mass_storage/lun0/file
And post result here.
Sam
----------------
UPDATES:
13-02-2011: 0.2b => minor bugs and made app scrollable for Froyo Landscape
26-02-2011: 0.3b:
- Changed 'settings' label (mistake) to system.
- Added a "Make sure you properly unmount/eject drive from PC when finished" message when mounting.
- Added dual boot system and data (p9 and p10).
- Changed 'Confirm mounting' to 'Confirm', as poster suggested. Thanks.
--------------
Hmm can't quite seen to get it to work right. The app does nothing for me when I select a partition to mount. I can get the SD card mounted via android's USB connected notification. I've tried the app with it turned on and off. It's got super user, so that's not it. By the way, I'm running Froyo 6.7 off the eMMC. Let me know what to try.
EDIT: Got it to work after running the ADB command in 1st post. Awesome app, thanks.
Sam,
Thank You, you program made my day. It works great, I have been messing with vold.fstab for days and I could only mount the boot of my sdcard. So, I went with manually pushing file to /sys/devices/platform/usb_mass_storage/luno/file which worked but your app make the process much better.
Again Thank you for everything you have done.
Biz
Could this work as a Xbox media storage? I want to get a new demo, and I got no Hard Drive
Works great!
this is great! i was thinking (since your help in the other thread) about trying to cobble something like this together myself in android app creator suite but didnt know if i could manage or not. Now i dont need to even try! thank!
EDIT: 2 things, one, is it possible to have this setting survive a reboot? and secondly, is the display supposed to be tiny? it only fills like a third of the screen and is centered at the top. this is on emmc froyo 0.6.7 the screen is scrollable as you said so just have to scroll down for the confirmed button
Does it unmount them on the nook when they are attached to the PC? I was playing with the echo command and it seems that the nook is unable to see any changes to the filesystem. I wrote a script that unmount them then runs the echo statement. Then another script that remount them once they are disconnected.
Good question. As I said, this is beta. I'm open to any suggestion. From what I tested, changes did actually occur even when mounted on android..
Unchecked compatibility mode in spare parts and reboot for fullscreen..
Sent from my HTC Desire using XDA App
samuelhalff said:
Good question. As I said, this is beta. I'm open to any suggestion. From what I tested, changes did actually occur even when mounted on android..
Unchecked compatibility mode in spare parts and reboot for fullscreen..
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
you did say that huh... sorry
This provided an easier way to fix root (SU binary) to make SuperUser work again on HC.
Glad it helped.
Over 100 downloads and very few feedbacks...
Sam
Sent from my HTC Desire using XDA App
samuelhalff said:
Over 100 downloads and very few feedbacks...
Click to expand...
Click to collapse
Interesting. I did see that if you try to download / install directly from the HC browser it doesn't work. Perhaps people do this instead of trying with their computer and assume it doesn't work? Downloads don't equal successful installs.
For Windows users, it (currently) provides the only way to mount the 4th partition of my HC SD card. Am I mistaken? Perhaps others don't realize what this is or are put off by the UI?
Keep it up. This is a much needed utility ATM.
The UI isn't THAT awful, is it?
Anyway, this can help a lot of people, especially the ones not too familiar with ADB..
Sam
Sent from my HTC Desire using XDA App
samuelhalff said:
The UI isn't THAT awful, is it?
Anyway, this can help a lot of people, especially the ones not too familiar with ADB.
Click to expand...
Click to collapse
To a person familar with partitions and the android file system it's fine. To those expecting a more fruity / friendly UI, it's far from it. However, you can't please everyone and it might be a waste of your energy to try. It's practical / functional and that's all I need it to be.
Indeed it can, much preferred over ADB even though I can use it just fine. You might want to make it more clear in the OP that users that have problems may need to type "adb shell" before the echo command. Not everyone will know this.
You app works well Sam! I can finally access my media partition via USB. I am looking forward to updates. Perhaps retaining setting after a reboot? Great work man!
Works great! I downloaded it with dolphin browser (running froyo on emmc) Then used root explorer to navigate to downloads and just clicked to install. Doesn't get any easier than that!
Would it be possible to have it mount media partitions? Like if I have dual boot setup would it be possible to mount the extra partitions to edit them?
Which media partitions?
Right, forgot about dual booters.. I'll implement that in 0.3..
Thanks.
Sent from my HTC Desire using XDA App
I want to thank you so much for this samuelhalff. I mean it. Something like this that may seem trivial to someone who can just do it means a WORLD to someone like me and i truly truly appreciate it. The devs/peeps here have made my little wanna be ereader ((hehe)) a great honeycomb tablet. I think its great for someone that cant afford the next great thing **xoom** to be able to join in the tech fun. You all have made me very happy with my little tablet.
Jamie.
Love the app!!!! but i got a issue now... There is no way for me to browse the media partition on the device... so I can not access my pictures that I placed on the internal storage...any insight?
Working great for me, HC on eMMC. Appreciate it!
Hello,
I have deep tested latest Cyanogen build from DerAtem.
The ROM seems stable but i have noticed several issues. I propose to lists those issues here.
1. Flash in not working : it installed fine but the plugin is not loaded in the browser
2. Many FC's : ex: Gun bro, Opera... with an error from java.lang saying a library is missing.
3. Some lags but system is still usable
4. SOD is still present
5. External SDCARD does not automount (manual mount is fine).
6. G-Sensors seems inverted in games but not in UI.
7. USB Key does not automount (manual mount is fine).
On the other side, WiFi is better than in stock rom. Bluetooth is working fine, touch screen is responsive...
Anyway, its a promising work.
Anyone else?
Akta
Could you explain how you manual mount with android ?
I have foliomod 1.4 and I cannot read a 1.5To HD, maybe manual mounting will help.
The usual way...
Code:
mount <device> <mountpoint>
using adb or a connectbot.
Hi all !
Concerning mounting of external devices :
As it's possible to re-activate sd cards automount by creating a sdcard-disk0 folder under /mnt/sdcard, is there a way to do something similar for USB keys ?
Thanks.
I think its not too complicated to achieve this result.
I will figure out how this is done for sdcards and apply the same recipe for usb flash disks.
And yes, you can mount what you want by just issuing mount /dev/mmc1blk1 /sdcard/<a directory>
Akta
To get flash working just install doom leaked apk for 10.2.
Works fine for me.
indeed mount has to be fixed. Will test more in short time.
Also tablet is occasionally get laggy on random UI moments
Thanks a lot for the mod!
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
I hope someone can help me. I have a 16gb nook tablet that I rooted using the method described here http://liliputing.com/2012/03/how-to-dual-boot-cyanogenmod-7-nook-tablet-os-with-a-microsd-card.html over a year ago and I've never had an issue until last weekend. My daughter was playing a game and the nook started acting up. The touch screen became unresponsive and the screen started to flash. I let the Nook charge overnight and when I turned it on the next day the screen became stuck at the white Nook welcome screen. After 20 minutes I tried the holding down power and N button to see if I could get it to restart, but unfortunately that may have made it worse. Now my Nook won't start at all. I've read many many threads here on how to fix it, but I am not tech savvy in the slightest. The first thing I tried was Rays method http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/ but instead of getting the green checkmark I got the red X and the "nook is shutting down" message. I tried so many things that I cannot remember them all but I do know that one of the methods I tried I got this message.
E:Can’t mount / cache/recovery/command/
E:Can’t mount / cache/recovery/log/
E:Can’t open / cache/recovery/log/
E:Can’t mount / cache/recovery/last_log/
E:Can’t open / cache/recovery/last_log
After that I tried to use the method described here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 and I did make the booktable cwm-sd and I went to lavero.burgos' thread to download the mmcblk files, but they weren't there.
Also I don't understand what adb is but I'm desperate, when I found the thread that explained it and tried to download the ADB + Fastboot + Drivers.zip that was in said thread (I'm sorry I can't remember which thread it was) the zip file didn't work.
I'm really sorry for posting yet another, "please help my nook is borked" thread but after all the reading I've done this past week the only thing I've become is very confused and frustrated. Thank you in advance to anyone who can help.
Notice on the link you posted
Ray Waldo; said:
If this procedure fails, try one of these:
Celtic has a possible solution on XDA here: http://forum.xda-developers.com/showthread.php?t=1513583
Succulent has more info on his Github page: https://github.com/succulent/acclaim_recovery_sdcard.
Click to expand...
Click to collapse
I can see how you got lost. There aren’t really any detailed instructions there.
I got the following zip from 2nd link
Flash the zip with CWM then try the bn_142_factory_recovery.zip SD card again and you should get a green checkmark this time.
udownwitopp said:
Notice on the link you posted
I can see how you got lost. There aren’t really any detailed instructions there.
I got the following zip from 2nd link
Flash the zip with CWM then try the bn_142_factory_recovery.zip SD card again and you should get a green checkmark this time.
Click to expand...
Click to collapse
Thank you for your reply. I will try this tonight and hopefully it will work.
Well I tried, and I hate asking but how exactly does someone add a zip file to an sd card after an image has been flashed to it? I've tried numerous times with sd cards of various sizes and I'm pretty sure I should have been able to do this with a 16gb card, but every time I try to drag and drop the flashstock zip over onto the card it says that there is no room available. Now I have been doing a lot of reading on here and I'm pretty sure I did not set the card up right, I did format it correctly with the sdformatter program, but I'm guessing I have to do something with the partitions on the card. I am not familiar with the programs because I've never had cause to use them before so I am not entirely sure how to do that. I tried following the directions found here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 but I couldn't figure out how to enable boot, and lba flags. I realize that this has probably all been answered already, but again, there programs are so foreign to me that I'm not even sure what to look up first. Thank you again for any help that any one can give me.
evm22 said:
Well I tried, and I hate asking but how exactly does someone add a zip file to an sd card after an image has been flashed to it? I've tried numerous times with sd cards of various sizes and I'm pretty sure I should have been able to do this with a 16gb card, but every time I try to drag and drop the flashstock zip over onto the card it says that there is no room available. Now I have been doing a lot of reading on here and I'm pretty sure I did not set the card up right, I did format it correctly with the sdformatter program, but I'm guessing I have to do something with the partitions on the card. I am not familiar with the programs because I've never had cause to use them before so I am not entirely sure how to do that. I tried following the directions found here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 but I couldn't figure out how to enable boot, and lba flags. I realize that this has probably all been answered already, but again, there programs are so foreign to me that I'm not even sure what to look up first. Thank you again for any help that any one can give me.
Click to expand...
Click to collapse
I'll try to explain the process for you. "The Red X" is a very common issue that people have with their devices. It's usually caused by digging into something that you don't fully understand. It's VERY important to understand the process of flashing custom ROMs because it could screw up your tablet, delete ROM partitions and such.
The first issue you need to attend to is "The Red X." First download the bn_142_factory_recovery.zip from the ray waldo site found here:
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Unzip the zip file and you should have a repart.img. Use win32diskimager to write this to an SD card. Once it's done writing, put the SD card in your device and it should boot from SD card and flash stock B&N 1.4.2 to your nook (if you have problems booting from SD card plug in the USB to your computer).
If you still get "The Red X" during this process please use the following method:
http://forum.xda-developers.com/showthread.php?t=1513583
If you have further problems please post or PM me. Once you have the issue fixed I HIGHLY recommend using the SDC version. It's a lot easier than the Internal Version and will prevent mistakes from happening.
Thank you for responding. I retried the method described on Ray's site, but sadly it's still a no go. I have downloaded the parted binary and I know how to get it onto the sd card, but what I don't know is how to ADB into my device. I'm not even sure I understand what ADB is.
evm22 said:
Thank you for responding. I retried the method described on Ray's site, but sadly it's still a no go. I have downloaded the parted binary and I know how to get it onto the sd card, but what I don't know is how to ADB into my device. I'm not even sure I understand what ADB is.
Click to expand...
Click to collapse
I'm not extremely knowledgeable with the ADB tool, but it's setting up your computer so you can write commands into your command prompt that will execute actions on your device. The link for setting it up is here:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you get it set up just follow the rest of the directions in the parted binary post.
datallboy said:
I'm not extremely knowledgeable with the ADB tool, but it's setting up your computer so you can write commands into your command prompt that will execute actions on your device. The link for setting it up is here:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you get it set up just follow the rest of the directions in the parted binary post.
Click to expand...
Click to collapse
Thank you for a link to the post with a working zip file for adb, I've downloaded and I've tried to follow the video, but unfortunately my laptop will not read my nook at all. Every time I connect it with a usb my device manager tries to find it, but it blinks, makes an error sound and I see
OMAP4330 under other devices. I' did a search for that error and came across this thread, but again the instructions call for installing an apk on the nook and since I can't get mine to turn on, it's a no go
evm22 said:
Thank you for a link to the post with a working zip file for adb, I've downloaded and I've tried to follow the video, but unfortunately my laptop will not read my nook at all. Every time I connect it with a usb my device manager tries to find it, but it blinks, makes an error sound and I see
OMAP4330 under other devices. I' did a search for that error and came across this thread, but again the instructions call for installing an apk on the nook and since I can't get mine to turn on, it's a no go
Click to expand...
Click to collapse
There is a possibility you could have deleted some partitions important to the nook then. Have you tried making an sdc version of cm10 to see if it could boot at all? You could see if you still have the device information to backup, recreate the partitions and flash back to stock.
Use this to make a bootable cm10 card:
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Just write the image file to an SD card and put it in your nook. It will boot into cm10. Once there go into your file manager and turn on root access. Go to your root drive/ROM/devconf to access all your device information. Make a backup of all them. There is a picture of my devices root drive. If you do not have the various partitions you will have to recreate them. There is a method on the Nook General Thread for doing this named "Unbrick Internal Partitions On NT" or something similar. You can use that recreate the internal partitions essential for your nook.
If you deleted the ROM partition with the Nook's product information you may be out of luck. The serial number and Mac address are the most essential, and can be found on your device hardware. The SN is under the SD slot (if readable) and Mac address is located inside your device. Not sure where I've never opened my nook to look, but probably on the WiFi chip.
Slight chance you may be able to fix it with this information and the rest of the device information you can use from a different nook since it doesn't have to do with internet and registration. There may be a way to fix that, but I don't know of any.
Best of luck. If you have problems just post a reply or send me an email.
I can get the Nook to turn on with the bootable cm10 card in it. I get the cyanoboot screen and see the boot menu, but honestly I don't know where to go from there. I think it's time for me to try and find someone who understands all of the programs involved in trying to fix this because I know I'm going to end up making things worse, if that's even possible. Thank you for trying to help me though. I do appreciate it
evm22 said:
I can get the Nook to turn on with the bootable cm10 card in it. I get the cyanoboot screen and see the boot menu, but honestly I don't know where to go from there. I think it's time for me to try and find someone who understands all of the programs involved in trying to fix this because I know I'm going to end up making things worse, if that's even possible. Thank you for trying to help me though. I do appreciate it
Click to expand...
Click to collapse
Hello! Did you ever figure out how to resurrect your Nook? I had trouble signing in Gmail and wanted to just unbrick and have the plain Nook again. I've been struggling getting the device to boot from the sd card with the repart imaged. I'm trying to get back to the ClockworkMod recovery screen but I can't at that moment. Someone suggested that I "flash" the B&N zip to the card but I'm trying to figure out how to do that.
Would love help!