Database Users

Tips and tricks when Odin and Kies dont work

Ok, I want to leave a message on here for future noobs like me with a Galaxy S
i9000 but it might work for others too.
My issue when flashing custom roms is that I have not been able to access my galaxy from my computer via usb since literally day 1 (when it did work once).
I spent a week trying to connect to Kies on multiple computers (vista and Windows 7). Tried via Android SDK, even tried hiemdall. I almost tried in ubuntu also but I never did get that working as I really don't know linux well enough. I've now given up...
So then I saw that you can do flashing all on the phone with the clockwork mod. With clockwork, my first rom flashed, well, like clockwork! But then I had some issues with lag and hang ups and reception and I decided to switch to another rom (seearms jl2 based rom - good stuff so far).
However this rom install went sideways... It said that it had installed ok but on reboot it stalled on the Galaxy I9000 screen and froze. Luckily I could still use the 3 button recovery to boot to clockworks but the hitch was that I HAD NO OTHER ROM to flash back to.
I had done a backup through clockworks but when I tried to restore it said the systems.img file was missing so it skipped it and the end result was the same freeze.
Normally everone says to reflash at this point with odin but that was not an option for me. So this is where I got lucky. The SeeARMs rom included Steam recovery module (though I thought it was the stock 3 button recovery menu for a while - I was panicking a little). I highly recommend seeing if you can get steam because it allows access to the External SD card for flashing which can be a lifesaver. Ahh, finally I could get the old rom on that, reflash it and go one with my life. My theory being that at least the issues would be aligned with the this rom and it worked.
So the lessons I learned:
1) Always have your new rom and your old rom on the interanal SD card in case of issues.
2) check your nandroid backup - even try testing it? - they don't always work perfectly with every device.
3)I highly recommend finding out if Steam or similar will work if you cannot access the USB connection and load things on when things go wrong.
Some tips I saw that also worked for me
1) flash a new kernel before you flash a new whole rom.
2) if things go sideways, try redownloading or retransferring the file to make sure there were no errors.
I did both and then reflashed (with my old rom Voodoo Doctor, SeeArms Rom and Darky's 8.1 rom on the card just to have options) and all was good!
PS: the steam recovery knocked off the first letter of the file when executing for some reason so I had to make 2 copy's of each rom I wanted access to ie Darkysrom.zip and arkysrom.zip just look for that error when you are doing this.

Good post - hopefully it'll help someone out who's stuck.

Hopefully
I'd like to stick some of that in on the thread for your rom but I need put another 7 half relevent messages out there before I am worthy... I understand the rule but I'd rather only post where it is meaningful...
GF

[Q] just got my nook color looking for some clarity

so i just bought my nook color today and i have some questions, i was searching around in the android development forum and their were about 50 different methods of doing everything.
i am experienced with android and how to do anything just if somebody could post up links in an order i need to follow to be able to get CM7 on to it.
if possible flashing to nand would be preferable but if all we have is SD support thats okay too
thanks for the help guys
also i know i will likely get flamed for this thread but just know i am experienced with android and i have ran it on a non native device before (htc vogue).

My go-to link for flashing CM7 to the internal memory:
http://forum.xda-developers.com/showpost.php?p=11452450&postcount=19

thoughtlesskyle said:
i am experienced with android and how to do anything just if somebody could post up links in an order i need to follow to be able to get CM7 on to it.
if possible flashing to nand would be preferable but if all we have is SD support thats okay too
thanks for the help guys
Click to expand...
Click to collapse
You can get just about anywhere with the nook via two steps:
1) run autonooter for your software version (THIS is for 1.1, obviously for the other versions it will be a different thread)
2) use the market to download ROM Manager, then flash the CWM recovery and download 7.0.2 from the app (or pull a different CWM zip from the forums onto your card if you prefer) and flash.
Simple enough

EpicFail236 said:
You can get just about anywhere with the nook via two steps:
1) run autonooter for your software version (THIS is for 1.1, obviously for the other versions it will be a different thread)
2) use the market to download ROM Manager, then flash the CWM recovery and download 7.0.2 from the app (or pull a different CWM zip from the forums onto your card if you prefer) and flash.
Simple enough
Click to expand...
Click to collapse
thanks, i was reading it from the app so i missed the 2nd part about loading it to my sd card thanks for all the help guys im going to try this now

so i did the rom manager thing picked nook color (old) that might have been the wrong choice but now it wont boot past recovery it just keeps rebooting into recovery
also it wont allow me to flash anything it says i have the wrong prop=encore help somebody

okay got that fixed thanks to one of the tutorials on here (thank god thought i bricked it)
so cm7 is booting now how long does this thing take, mine has been going for like 10 minutes but its not like bootlooping is this just because the tablet builds are huge or do i have cause to be uneasy (nook builds like stock software def didnt take this long)

http://wiki.cyanogenmod.com/index.php?title=Barnes_&_Noble_Nook_Color:_Full_Update_Guide Just in case
First boot will take 5min+.

Nburnes said:
http://wiki.cyanogenmod.com/index.php?title=Barnes_&_Noble_Nook_Color:_Full_Update_Guide Just in case
First boot will take 5min+.
Click to expand...
Click to collapse
we are on like 20 minutes now

thoughtlesskyle said:
okay got that fixed thanks to one of the tutorials on here (thank god thought i bricked it)
so cm7 is booting now how long does this thing take, mine has been going for like 10 minutes but its not like bootlooping is this just because the tablet builds are huge or do i have cause to be uneasy (nook builds like stock software def didnt take this long)
Click to expand...
Click to collapse
This isn't your Hero!!! I don't think you can brick this thing.... The Nook always tries to boot from SD before internal memory!!! I had a hell of a time getting CM7 to load originally (at least 10+ minutes). Once you get it loaded, put away that SD card you burned the recovery image too.....Put a new SD card in, install Rom Manager, and flash recovery to it from Rom Manager. Once you get there you can Nand and flash stuff just like you do on your phone.
**Edit** If you get really jammed up, here's the thread on returning to stock unrooted B&N firmware, so you can start over....
http://forum.xda-developers.com/showthread.php?t=914690&highlight=return+stock

[Q] ok i've got myself into a pretty sticky situation (stuck at google logo)

First off, I'm an idiot. I know this. But I would also appreciate any helpful advice that may teach me a thing or two about how to rectify my idiocy and prevent any future idiocy.
was fooling around with my n4 (which was on the cm 10.2 stable) and decided to give the 4.4 bandwagon a go.
downloaded roms and gapps ready to flash ect.. (ive done this multiple times before)
did a full reset (inc. system and external sd storage) from the android setting menu after backing up sd card and apps because i wanted a fully clean phone to upgrade
Then plugged in again but was dismayed to see that the pc and android memory wasnt clean, it said stuff was taking up storage space but the file system listed no files...?
so i went into recovery
and due to my tiredness and general lack of IQ, decided to format everything under the sun in mounts and storage (yes, this included /system)
and i dont have a nandroid (since i have the 8gb one and could never justify the space cost of a nandroid, plus i though i was pro at flashing)
and now my usb is acting up so i tried to fix that, uninstalled my drivers ect..
but realised for many driver installations especially for adb/fastboot drivers this requires you to plug in the phone and turn on debugging for the right drivers to install
so now i have a bricked phone which wont connect to fastboot and i dont know how to solve this and cant boot into android to mess around with adb and nothing on the memory like a backup or any seblance of an os.
Feel free to call me more of an idiot than I've previously mentioned. But i would GREATLY appreciate any helpful tips and would wish you all the christmas cheer i can muster
yours,
brickedmyphoneat3a.m.onboxingday

kickassy said:
First off, I'm an idiot. I know this. But I would also appreciate any helpful advice that may teach me a thing or two about how to rectify my idiocy and prevent any future idiocy.
was fooling around with my n4 (which was on the cm 10.2 stable) and decided to give the 4.4 bandwagon a go.
downloaded roms and gapps ready to flash ect.. (ive done this multiple times before)
did a full reset (inc. system and external sd storage) from the android setting menu after backing up sd card and apps because i wanted a fully clean phone to upgrade
Then plugged in again but was dismayed to see that the pc and android memory wasnt clean, it said stuff was taking up storage space but the file system listed no files...?
so i went into recovery
and due to my tiredness and general lack of IQ, decided to format everything under the sun in mounts and storage (yes, this included /system)
and i dont have a nandroid (since i have the 8gb one and could never justify the space cost of a nandroid, plus i though i was pro at flashing)
and now my usb is acting up so i tried to fix that, uninstalled my drivers ect..
but realised for many driver installations especially for adb/fastboot drivers this requires you to plug in the phone and turn on debugging for the right drivers to install
so now i have a bricked phone which wont connect to fastboot and i dont know how to solve this and cant boot into android to mess around with adb and nothing on the memory like a backup or any seblance of an os.
Feel free to call me more of an idiot than I've previously mentioned. But i would GREATLY appreciate any helpful tips and would wish you all the christmas cheer i can muster
yours,
brickedmyphoneat3a.m.onboxingday
Click to expand...
Click to collapse
i'm on a similar situation hope ur problem get solved mate, if i get any fix i will forward it to u
EDIT:
Check this tut, may help:
http ://darkness4every1.blogspot .ro/2013/07/flash-official-android-43-on-google.html
i followed the tut an my N4 is working like a charm! try it out

saanteeh said:
i'm on a similar situation hope ur problem get solved mate, if i get any fix i will forward it to u
EDIT:
Check this tut, may help:
http ://darkness4every1.blogspot .ro/2013/07/flash-official-android-43-on-google.html
Click to expand...
Click to collapse
SOLVED. researched more into the wee hours of the morning and learnt how to adb sideload which solved all of my problems. simply sideloaded the rom i was in before and problem solved in 5 mins

kickassy said:
SOLVED. researched more into the wee hours of the morning and learnt how to adb sideload which solved all of my problems. simply sideloaded the rom i was in before and problem solved in 5 mins
Click to expand...
Click to collapse
:good:

[Q] NST not booting

Hi,
First of all, sorry about my english. It's not my primary language.
I recently bought a used Nook Simple Touch on eBay. The previous owner had tried to root it, but failed somewhere along the way. I got it dirt cheap and figured I could fix it..
I've read "all" the unbricking guides here on the forum, but I'm yet to make it start. I can boot CWM, but for some reason noogie is not starting at all.
At first, the device said "Rooted forever" all the time, but after some messing around in CWM it's instead displaying "Your NOOK is starting up..." in five different languages, and stops there.
The thing is, I'm not even interested in the reading features (B&N apps, e-books, etc.), I just want to use the device to display a status webpage that I've made (weather updates, bus/subway/tram departures, etc. etc.), so as long as it can run Chrome or similar I would be perfectly happy! Is there a vanilla android ROM available so I don't need to care about the "device specific" data that I've been reading about (the one you're supposed to take a backup of)? Or can I just flash it with any NST firmware if I'm not interested in the reading functionality?
Thanks!

Have you tried Nook Manager? I've had really good luck with it and it includes a factory image reset. It may be a way to get back to something you can work with.

nmyshkin said:
Have you tried Nook Manager? I've had really good luck with it and it includes a factory image reset. It may be a way to get back to something you can work with.
Click to expand...
Click to collapse
I agree. I just received my nook from ebay a couple of days ago. I've tried a number of different root methods and google apps installers. Nook Manager + NTGApps was by far the simplest for me.
Also, have you tried the stock factory reset?? I'm new to this, so I'm not sure if it will work -- but I thought I bricked mine 3-4 times and the factory reset saved me every time.
0) Take out any SD cards (just making sure you don't have anything bootable on the card)
1) Press and hold the power button until it resets
2) As soon as it begins to reboot press and hold the bottom left and bottom right physical buttons until you see a prompt.
3) Wait for the prompt and press the "n" button once to confirm the factory reset
4) Press the "n" button again to begin the factory reset again.
After you factory reset, upgrade to 1.2.1 and then root using Nook Manager. Then, you'll have the browser available to you.
* Use Nook Manager to make a backup *

Thanks for the suggestions you guys! I finally got it to work!
Noogie finally booted up. I just left the nook, with the noogie sd card in, connected to my computer when I went to work. When I got home, it had started. Since then it started every reboot. No idea why it didn't work in the beginning?
Alright, this is how I did. This information is scattered around the forum already, but hopefully it can help someone in my position.
1) I realized that the partitions table was probably messed up, so after "aligning" it using fdisk and the table found here:
http://forum.xda-developers.com/showpost.php?p=29585690&postcount=6
I could restore my /rom partition. After I've made a backup of the /rom files...
2) ... I flashed this file using noogie:
http://forum.xda-developers.com/showpost.php?p=49389880&postcount=2
3) I mounted partition2 on my computer (still using noogie) and copied my /rom files back to it.
4) It started! So I applied the official 1.2.1 update from B&N. After update I realized that I actually have a glowlight! It was listed as a regular Simple Touch, so that was a pleasant surprise.
5) Rooted using NookManager. Worked flawlessy. Installed Opera Mobile 12.1 (which have websocket support that I needed). I now have an awesome status "frame".
Thank you for all you help, including the guys & girls posting in the threads linked in this post.

Updating from rooted/registered 1.1.0 to a newer minimal rom?

Hey all,
I rooted my NST waaaay back and haven't touched it again until now. I want to use it for another project now but want to update it first.
I'd like a rom with adb, button savior, usb host mode, su, busybox, and that's it (unless i'm missing something that i should really have).
I'll sideload anything else I need, and I don't want gapps or amazon appstore or anything.
Though I wouldn't mind an 'e-ink friendly' theme or whatever.
Is the best process to erase and deregister, or can I just use CWM and whatever rom I want on an SDCard and update it directly?
Thanks

There only seems to be three ROMs still being developed. Two of them are somewhat full of bloats. But the CM11 port being worked on right now is operable off a micro SD card and it is barebone. Doubt that it have the requested features (button savior?) but out of the three, that one seems to be the best match. And it will only gets better once the porting stabilize some more.

Deafcyclist said:
There only seems to be three ROMs still being developed. Two of them are somewhat full of bloats. But the CM11 port being worked on right now is operable off a micro SD card and it is barebone. Doubt that it have the requested features (button savior?) but out of the three, that one seems to be the best match. And it will only gets better once the porting stabilize some more.
Click to expand...
Click to collapse
That is partly true, but the current CM11 build is nowhere near stable enough to run as a daily driver.
Our friend here should probably go the NookManager route to start off; what do you think?

I'm far from using it as a daily driver, and I might even be able to drop the host mode requirement. It just needs to run an android app I'll develop, but wifi will need to work too. I'll check out CM11.
If I can start with a rooted version of the latest firmware, that'd be fine, but NookManager says: "For best results, however, you should be on 1.2.1 before using this tool." So, what's the best path to update to 1.2.1 or the latest firmware, given that I'm already on a rooted (and registered ) 1.1.0?

Modulus said:
I'm far from using it as a daily driver, and I might even be able to drop the host mode requirement. It just needs to run an android app I'll develop, but wifi will need to work too. I'll check out CM11.
If I can start with a rooted version of the latest firmware, that'd be fine, but NookManager says: "For best results, however, you should be on 1.2.1 before using this tool." So, what's the best path to update to 1.2.1 or the latest firmware, given that I'm already on a rooted (and registered ) 1.1.0?
Click to expand...
Click to collapse
A factory wipe will be the first thing to do. Restore your Nook to the state in which it came out of the box.
Then, either register or bypass Oobe to get into your "new" Nook. Once that's done, you can follow the instructions here to update to 1.2.1.
After that, you can use NookManager.

I found some instructions that you had previously given to someone in another thread here
It took me forever to get the 8-interrupt restore to work, and afterwards, it still had ADW launcher and some other stuff that I had installed.
I did not do the 'Erase and deregister this device' at any point.
After the 8-interrupt restore, I transferred the 1.2.1 update to the root of the Nook, rebooted and let that install.
Then after it booted, it pleasantly informed me it was at 1.2.1 but it still had the ADW launcher, so I rebooted onto NookManager and rooted it.
Now it's rooted, but still has ADW launcher and also has ReLaunch obviously.
Should I have done the 'Erase and deregister' to fully wipe it back to how it was when it came out of the box?
If I use the NookManager option to factory restore it, will that get me a clean slate?
Thanks for the help man, I know this thing is ancient

Modulus said:
I found some instructions that you had previously given to someone in another thread here
It took me forever to get the 8-interrupt restore to work, and afterwards, it still had ADW launcher and some other stuff that I had installed.
I did not do the 'Erase and deregister this device' at any point.
After the 8-interrupt restore, I transferred the 1.2.1 update to the root of the Nook, rebooted and let that install.
Then after it booted, it pleasantly informed me it was at 1.2.1 but it still had the ADW launcher, so I rebooted onto NookManager and rooted it.
Now it's rooted, but still has ADW launcher and also has ReLaunch obviously.
Should I have done the 'Erase and deregister' to fully wipe it back to how it was when it came out of the box?
If I use the NookManager option to factory restore it, will that get me a clean slate?
Thanks for the help man, I know this thing is ancient
Click to expand...
Click to collapse
To avoid potential issues in the future, you definitely should use the Restore factory.zip function of NookManager. That will assuredly get you back to the factory state.
Then, update to 1.2.1, root with NookManager, and you're on your way.
And you'd be surprised at how much development is still underway for the Nook Touch - it may be old, but it sure isn't obsolete. In fact, the Nook Touch is my personal specialty, as you might have guessed from my username.
Anyways, if you ever need help with your Nook in any way, shape or form, don't hesitate to PM me or post on the forums. Either way, I'll see it and reply.

ИΘΘK¡€ said:
To avoid potential issues in the future, you definitely should use the Restore factory.zip function of NookManager. That will assuredly get you back to the factory state.
Then, update to 1.2.1, root with NookManager, and you're on your way.
And you'd be surprised at how much development is still underway for the Nook Touch - it may be old, but it sure isn't obsolete. In fact, the Nook Touch is my personal specialty, as you might have guessed from my username.
Anyways, if you ever need help with your Nook in any way, shaoe or form, don't hesitate to PM me or post on the forums. Either way, I'll see it and reply.
Click to expand...
Click to collapse
Just posting to say that this is sound advice. I was in a similar situation, wanted to give my Nook ST the latest and greatest developments,. What worked for me was to use NookManager to restore factory.zip, this actually upgraded the Nook to 1.2.0, so I assume that comes with NookManager somehow. Then I used the Nook 'Settings' to go to unregister/reset the device, then finally, bypass the OOBE setup using crazy_jake's method ...
http://forum.xda-developers.com/showthread.php?t=1162693
... and now I'm off to re-root it and add all the apps again!
Big thanks all!

Grab what you need from here: https://drive.google.com/folderview...EwRndzUklrN1dRVTRuZVJXRlp1N0hWRTQ&usp=sharing
All zips install via CWM.
But for What you want grab & Flash these in this order:
nook_1_2_update.zip - This is just an optimized version of the default UK ROM with init.d+Busybox.
ReLaunch-ONLY.zip - This will replace the Home with ReLaunch.
USB-Audio+FastMode+Host.zip - Also enables ROOT/SU - Install this after logging into your B&N account. If you install it before you won't be able to register with B&N.