Was on Auto Nooter Dual Boot edition. With AN 3.0 on the first partition and HC on second partition.
Was in Auto Nooter minding my own business. Went into Barnes and Noble software to look at my books and said it could not authenticate--"must reset". it sad. It proceeded to reboot immediately and do the de-register and erase routine. When it came back, on it was rooted with Auto Nooter but my internal was erased. I had to resign in, etc. Luckily I have a Titanium backup....
Any idea WHY it did this???? how frustrating.
I'd also like to get to the bottom of this issue. I've been running autonooter 3.0 and have been through 3 of these resets. After the first two, I tried renaming the ota_certs.zip file, which some have theorized would prevent it. It still reset itself. I'm wondering if this is even related to the rooting process or if there's something else going on with the device itself. It's really starting to piss me off. I'm trying to hold out until honeycomb is properly released and stable and just run that.
Related
I've gone thru the paces numerous times, even rolled a rooted install back to a full install of 1.0.1 and reapplied the HC v.4 (following all instructions carefully). I don't have any problems with the file extraction and get the Done message. However, when I reboot the nook it gives me a Loading screen then flickers a few times and then an ANDROID_ (flashing curson) and hangs. I've gotten this far every time I've tried to apply the zip. Once in awhile it will flash between the Loading and ANDROID_ screens a few times but ultimately I end up with ANDROID on my screen and nothing else.
Any ideas or direction I can move in? I'm anxious to try this out but prefer to run it from internal memory instead of an SD card...
There does seem to be one disparity between the instructions and the actual application of them, there doesn't appear to be a way to unmount /boot that I recall, only format it.
Make sure data and system have been formatted without issues before flashing the zip.
If that doesn't work, you might have a system partition size issue. Download shad0wf0x's stock image and dd it to your mmcblk0p5 partition (see specific thread). Then try flashing zip after having formatted both data and system.
Sent from my HTC Desire using XDA App
During the formats I haven't gotten any error messages, just a simple Done. when the format of each completes. I do hang when boot is done but a hard reboot, per the instructions, allows me to continue from there and I making sure /system and /data aren't mounted.
I'll give this a shot and let you know how it works out.
Thanks.
That didn't seem to do the trick. The last time I did this I started from a complete reinstall of 1.0.1 with an image I got from this thread.
http://forum.xda-developers.com/archive/index.php/t-914690.html
I'm able to boot into the stock install without difficulty, register the nook, setup my gmail association and then root. If I had a corrupted systems directory would I be able to do all those things?
I went to update to use autonooter 3.0.0 with nook 1.1.0 software. I went through the process of installing the autonooter 3 and it booted up with the Android splash screen but it kept replaying the android sequence (spelling android) and it would keep restarting sometimes not getting through the entire spelling of android.
I went to reset to factory defaults and now it constantly reboots after "installing a new software update is being installed..." completes. Autonooter no longer boots it justs sits blank forever.
Please help!
hmmm...
Autonooter seemed to work for me. I just had to make sure that I was on stock 1.1 and it worked.
Try to obtain another microSD card. A 1GB will work just fine for the Autonook img.
Also, I would download another copy of the image. What you are going through seems to be a bad image either burned to the microSD or from the source.
Just my 2 cents.
I am sure that it works but for some reason I seem to be in some exception case and I need input how to get out of this mode. My nook is essentially bricked right now.
Have you tried to restore to stock using these instructions?
http://nookdevs.com/Flash_back_to_clean_stock_ROM
I could not get the 8 times failed boot to happen, no matter what the nook boot always happens, I could not get ADB to recognize the device to for the failed boot, I tried the new SD card and image. I give up. I bought it from BN last week so I will just exchange it. thanks for the help.
I have the same issue. The Nook loops the boot screen. The first time it gets through the boot animation afterwards it stops at AND then it pukes. I'm going to try taking it back to stock.
To all of you stuck in this boot loop use my guide posted here to return to stock.
It even includes the link to decadences pre-rooted 1.1 so you can use that instead of flashing back to stock 1.0 or 1.0.1. Good luck and have fun!
Note: Make sure to format /data /system and probably /boot if you are going to flash one of these. Its always best to start from a clean build.
Try the CWR bootable SD...?
quickwitt said:
I have the same issue. The Nook loops the boot screen. The first time it gets through the boot animation afterwards it stops at AND then it pukes. I'm going to try taking it back to stock.
Click to expand...
Click to collapse
Try this... if you have 2 SD cards...
1) Download iMonster's bootable CWR image... (1GB card should be plenty)
2) Download the stock kernel/image from XDA forums and copy onto card #2
3) Using the bootable imaged SD, hold the "n" + power to boot up... you should see two crossbone/skulls image and in-between them, the words "loading"
4) Once it boots into CWR, go to "install from sd"
5) Select the stock image from the SD card...
It should boot back up into stock. Then try the nooter again... try to re-download the file, re-image, and start process over.
Out of curiosity... did you get your nook before or after the who "temporary pulling off of the shelves" incident? I'm wondering if these devices have been reworked at their factory? I know there have been articles that mention that this is just a rumor... BUT you never know.
I used winimage to write the 1.1 image here to an sd card
http://forum.xda-developers.com/showthread.php?t=945838
Put the sd card in the Nook and rebooted. It booted into CWR, I followed the onscreen instructions and now I'm back to stock 1.1.
Reflashed Nooter 3.0.
Back in business.
hvuong2 said:
Try this... if you have 2 SD cards...
1) Download iMonster's bootable CWR image... (1GB card should be plenty)
2) Download the stock kernel/image from XDA forums and copy onto card #2
3) Using the bootable imaged SD, hold the "n" + power to boot up... you should see two crossbone/skulls image and in-between them, the words "loading"
4) Once it boots into CWR, go to "install from sd"
5) Select the stock image from the SD card...
It should boot back up into stock. Then try the nooter again... try to re-download the file, re-image, and start process over.
Out of curiosity... did you get your nook before or after the who "temporary pulling off of the shelves" incident? I'm wondering if these devices have been reworked at their factory? I know there have been articles that mention that this is just a rumor... BUT you never know.
Click to expand...
Click to collapse
I think the "pulling off the shelves" is a myth but I purchased my nook the 1st week of January. I've loaded every version of Autonooter as well as Froyo and Honeycomb without incident until now. I'm sure I screwed something up in the process or just had a bad write to the sd. I'm pleased that you can't really brick this great little tablet.
I recently updated my cappy from Phoenix rising to Continuum following all instructions in the first couple posts except for flashing back to stock. "Including enabling lagfix"
Everything seemed to be running perfect. Rebooted a couple times to see how it behaved, plugged it in and turned in for the night. Seemed to be fine in the morning while I surfed the web, played games, etc. I ended up losing data service (a constant problem I get with custom ROMs that I've never been able to shake) so I rebooted, which normally solves the problem.
Instead, this time appears that all the apps installed in the internal SD card are missing... Weird but whatever. Titanium time and troubleshoot after school. Well, titanium says that there's no backups. Slight panic. Then I think about all my 3 stars from the angry bird series... MAJOR PANIC!
I can access my phone just fine via root explorer but my TiBU folder is empty, I have no games on my SD cards but a lot of other stuff is there including my dropbox and download folders as well as my ROM .zips. It's almost as if random stuff was removed.
Reboot into recovery to fix permissions and delete caches, etc. While I there I checked my backups (Nandroid?) and my lastest one (the one I did prior to flashing) was missing! Even more panicked!
Checked my phone... No luck. So I think that maybe I'll try some sort of undelete program when I get home. Plug the phone into compy and the mount cards options doesn't appear... Reboot to recovery and reflash ROM. No luck. Try to update back to TiBU pro and I notice a new problem. I can't install anything from the market, they just don't download. Tried to install .apks I have stored locally, no luck.
At this point I just want a working phone, screw dem birds, I can always redo all the levels and put music back on. Goto reformat SD cards. The format external is greyed out. Trying to reformat the internal one goes through the motions but there's no update in the available storage.
Flash to Firefly since I had a copy of it on the internal SD. Same issues listed above but with a pretty new interface.
So... Anyone have a suggestion aside from go back in time and buy titanium media sync or for me to suck less? I'm pretty much out of ideas
my first captivate was deleting files on the internal sd (mostly my music folder), returned for exchange. no problems since. hardware issues are fixed by the hardware manufactures!
And if you have other problems NO MATTER what rom you use, then its probably not the rom...
Oops! Sorry, I meant to stress that in the original post: I by no means hold any ROM responsible for the shenanigans my phone is currently experiencing, I originally omitted mentioning any names but decided to include them so I could be as explicit as possible in describing the issues and the steps I took.
Update 1: Attempted Odin3.
Since I'm apparently mentally handicapped, I clicked on "Master clear" instead of "Start". Yellow android guy has been digging a hole on my phone's screen for the last 10-15 minutes with no change.
Don't think that it's suppose to take this long and worried that whatever the SD card issue is may be affecting the master clear but currently too scared to unplug the phone.
Currently chain smoking nervously
----
Update 2: Revenge of the unborking
Unplugged phone and removed battery since master clear was clearly not working
Powered it back up and Odin -> Flash to stock
Stock working but unable to load SD cards
Rebooted a couple times -> problem solved
Mounted SD as USB card
Recurva -> Recovered TiBU folder.
Rooted phone
Reinstalled Clockwork mod
Reflashed Firefly
Installing stuff from the market is still a bit wonky with a custom ROM which is odd since I could install stuff with a stock rom but at least things are progressing
That's cool you got your stuff back. Now make a copy of it on your computer!! Now its just a call to att to get it replaced cause it's a hardware issue for sure.
Oh I'm sure you figured this out but master clear doesn't do anything in download mode, that works when the phone is actually booted.
master clear works booted with debugging on!
Yep, looks like installing stuff from either the market or from the SD card is hit or miss depending on time of day, prevailing winds, or the phase of the moon. Got some stuff installed but now nothing will go on the phone.
Going to complain to Samsung directly to see where what that gets me. Bought the phone used after my last android bit the dust while I was still on contract. Ended up getting a cappy since you could unlock it manually and was unaware that you were stuck on edge service. Wish me luck!
Boot into recovery
Onix Speed Features
LAGFIX options
Enable lagfix: Convert Data to Ext4
Convert SYSTEM to Ext4 /RFS
YES
Go back twice
Reboot System Now
EXT4: Convert to EXT4 (wait for the conversion to complete)
After reboot choose YES (for the rest of partitions to be converted)
Wait for the welcome screen and from the power menu reboot to Recovery
ONIX Speed features
ROOT / install superuser
Simple: Install busybox
Scrool to Yes - apply root to device and select it
Go back twice
Reboot system now
Click to expand...
Click to collapse
I think that I may have borked up my phone when doing this. I used the onix recovery to set everything back to rfs to no avail. I am still unable to install any apps or format the SD cards. Any advice? Currently on hold with Samsung support but apparently I am having a hard time convincing them that Hawaii is part of the United States and that we do in fact have UPS on this island.
Hey guys, I need some advice please. Have had a number of odd happenings with my i9000 in the last 24hrs and not sure if some of them are the fault of the phone, or my fault! Apologies up front too for the long post – didn’t know how to put it all more succinctly!
First things first – it’s a Galaxy i9000M Bell vibrant. Came as Éclair 2.1, upgraded recently via Kies to Froyo 2.2, Build UGKC1. Then rooted with SuperOneClick, successfully without drama. Can get into recovery and download modes no problem via 3-button method.
Bit of background info – int SD 16GB, inserted 16GB ext SD. Before any upgrade to the phone had some issues where some photos taken with camera on the phone would show up in gallery as a corrupted/damaged icon. Pretty sure this occurred on default int SD so changed save location to ext SD but same deal now and then. Formatted ext SD – still happened from time to time. Actually replaced ext SD (exchanged at shop with brand new one), but same thing happened again. Figured I’d learn to live with it as only happened now and then.
So, phone rooted last week. Had been doing reading on ROMs/kernels before trying to flash anything. Only root-type things I’d done were to get TiB (and do full backup), Root Explorer, Terminal Emulator and Wireless Tether. Y’day I noticed after taking a few pics that one of the ‘corrupt’ icons that had previously been in place of an older photo, was now in the spot of one of the pics I had just taken (and strangely, the older, apparently corrupted photo was now fine).
I tried to delete a few of the photos but the phone just got stuck trying to delete. Had to force close it with task manager. Same deal if I tried 1 or many photos. Did this a number of times but no joy. Eventually just took ext SD out, put it into PC and deleted them that way, then put back into phone. Now it took AGES to complete the media scan on ext SD – like 5-10 mins! This happened a couple of times if I tried to do anything with the SD eg. save a file to it. So reformatted the SD card (on PC) but same prob when put back in phone.
Figured it might finally be time to try a new kernel in hope it may fix this bug. Had speedmod all ready to go (but hadn't been brave enough yet to try my first flash) so flashed K13E-500Hz via Odin. It worked fine, but “media scanning” problem was still there. Figured I might as well go the whole hog so factory reset the phone via recovery 3e. Did this ok, and “media scanning” was no longer a prob when I put the ext SD card in, just took a couple of seconds – hooray!
Restored apps + system using TiB which also appeared at first to work fine. Put a few pics and ringtones on the ext SD and all seemed fine. Then some app icons disappeared from the Applications pages. They appeared ‘crossed out’ in TiB and when I went to restore them again the phone spazzed out saying (sorry can’t recall exact wording) there was not enough memory and to delete some things to try to fix this. A red SD-like icon appeared in the top bar. I tried rebooting the phone via recovery 3e and it went into a cycle of vibrating, flashing up the turn-on screen/display then shutting off, but vibrating occasionally and lighting the soft touch keys but nothing else. This did this for about 5 mins and in order to try to save battery/stop the whole process I ended up factory resetting yet again via recovery.
Today it works 'ok'. Have not braved putting an ext SD in yet! Got Tib off the market but have also not dared to try to restore any thing yet. Oddly, in TiB it shows “System ROM” as almost fully taken up ie. Full green bar (289MB, only 6.06MB free) – this can’t be right can it?
Internal, DB data and SD card all show as ~99% free.
Deleted Dalvik cache in case that was the RAM problem but it didn’t do anything much (freed up about 6MB only).
So, my questions!
1. is this all because of the ‘corrupt/damaged’ issues before I’d done anything to my phone?
1b) How do I find out what RAM is available and what is using it all up? RAM manager is showing 197MB/339MB used but is this what the 'memory' problem would be? Clearing memory doesn't seem to do anything.
2. I never installed any kind of lagfix (knowingly anyway) – could this be a reason - have seen lots of threads/posts about disabling lagfix before flashing roms or kernels
3. I thought factory reset would wipe everything – but it obviously kept the int SD info ok (I’d copied Tib backup to ext SD and also to dropbox just in case) –should I maybe reformat the int SD and factory reset again?
4. If the issue is the phone itself (with prior corrupt file problem) – would it be worth flashing back to stock kernel and unrooting phone to try to bring back and get fixed/replaced under warranty?
Thanks in advance for any help anyone can offer!!!!!!
Read your hole post its really long. Can't answer to all questions. But did you try to put your phone as massage storage to your pc and mark everything thats on int sd and just erease it. When turn your phone off, put it in download mode and flash a stock rom (with 3 files) from samfirmware.com with repartition enabled? Maybe that works. Good luck! Before i forgot ext 4 is the better filesystem. Rfs getting laggy after a while cause its not the correct filesystem for sgs. Thats why ext4 is the main format on sgs2.
Sent from my GT-I9000 using XDA App
hey thanks for the reply.
i know it was a super-long post, apologies again.
didn't try deleting the ext SD whilst connected via usb. got fed up with the phone not being able to delete & freezing when i tried that way so just took SD out and deleted them with card plugged directly into laptop.
as it happens, since 2nd factory reset, i've been cautious about what i do. no ext SD yet (though might try that tomorrow). didn't do full restore of missing apps and system files as i did the first time. so far have only restored about 6apps via TiB and wifi locations. Phone working ok...for now.
next steps:
1. try taking loads of photos to see if 'corrupt'-style icons occur again with int SD only;
2. maybe try an ext SD again after reformatting it and see how the media scanning goes and how it goes having music/vid/pic files on it etc;
3. gonna look more into the speedmod kernel ie. the tweaks which i think i need to access via recovery mode.
not quite ready to try and flash a custom rom with that little scare!
...but would like to try a custom rom at some point when i feel more educated about all this
Just look at the search function on xda or google. There enough guides about flashing. Know how you feel. The first time i flashing it was very scary for me. Got a heartbeat like a technosong. If you want i can write you a guide for every step. Trust me it is easier as it sounds. Just pm me and i will help you out.
Sent from my GT-I9000 using XDA App
I rooted my Nook Color, originally v. 1.3 (with Manual Nooter-4.5.18, -4.6.16). The rooting appeared to be successful, but was unstable in that it wouldn't survive a power-cycle. Eventually, I gave up, and decided to revert to straight B&N Nook. I did this by clearing data, root, system, and running "nook-complete-restore-1.0.1.zip. That worked, but with a couple of big flaws: 1) I now cannot "see" the NookColor internal rom when I plug its usb port into my computer! Cabling, computer software, etc., is in order, since when I have a microSD installed on the NC, it does mount on the computer (Mac), and allows file transfer to-and-from. (Also "invisible" on Linux and MSWin machines.)
2) A consequence is that I cannot copy "generic-sdcard-v1.3.img.zip" to NC for purposes of "upgrading" back to v.1.3; also when I attempt to download any archived books from N&B: the download starts, then abruptly stops, presumably because it can find no internal rom in which to store them.
In short, I've bricked the unbrickable NC! Anybody have any ideas?
Lol you cannot brick the Nook. You are using a firmware that your Nook was not designed to handle.
Flash this with clockwork to update to 1.2 and regain your internal storage: http://forum.xda-developers.com/showthread.php?t=1050520
---------------------------------
Sent from my LG Optimus V using Tapatalk
Can you revert straight to B&N 1.3 stock ROM? Why went all the way down to 1.0.1?
Indeed, koopakido8, it takes more of a Philistine than me to brick a NC! Your diagnosis and remedy were both spot on. Thanks