So I decided to root the nook this weekend and I'm having some issues that I can't get around.
I've rooted and ROM'd a few droids so far without an issue. I'm not an expert but I'm also not a noob.
I built up a bootable 1gb CWM and loaded up manualnooter-4-5-18 and manualnooter-4-6-16. CWM was pretty simple, and allowed me to load both of them up without an issue. (I've done both with and without a full wipe)
Once it reboots, it's perfect. market works, web works, rom manager permission fixes..everything works well.
The issue is once I power it off and back on, it's done. It hangs at the "Nook Color" splash screen (After the Read Everywhere and big grey N) and refuses to power up the OS. The onyl way i can get it back is to do a complete factory restore (power+vol button+N)
What am I doing wrong?
It sounds like you are suffering from the Flash / Air lockup problem. If you search the forums, there are links to download the zips that fix the issue.
I would also go to CWM 3.2.0.1 2.8 is rather old and 0.1 is a much easier experience especially on the new nooks.
I rooted two new nooks for my friend's kids Christmas presents last week. I used 3.2.0.1, Nooter 4-6-16 and used the adobe flash and air fixes and it went smooth.
Check this thread concerning the flash fix:
http://forum.xda-developers.com/showthread.php?t=1208896
Props to GMPOWER for his published answer.
Hope it works for you.
Ok cool, thanks OrionLTD. That sounds like my EXACT issue.
“jaromrnelson” continued the project, and has a more up to date version at the link below. His updated one will fix Adobe flash and Adobe Air. Once the fix has been applied, you should not have a problem whenever they update again.
LINK
Thanks GMPOWER, I'll try that one tonight.
Well... I tried these methods and I'm still boot looping as soon as Adobe updates from the Market.
el_bobbo said:
Well... I tried these methods and I'm still boot looping as soon as Adobe updates from the Market.
Click to expand...
Click to collapse
Take a look at http://forum.xda-developers.com/showpost.php?p=20456719&postcount=1631
Wiping and updating to 1.4.1 followed by the above should do nicely. It's working beyond expectations for me and some others.
That worked for me as well!
Although I had the old market at first after root.
I erased and deregistered and registered again and then applied the root 5-12-20 again and have newest market and so far so good, all is well
I might give that one a whirl, thanks guys.
The issue I had is that a newer version of Adobe had come out since GMPOWER's zip was released. There was another link in that thread to a newer zip (From another member) that ultimately resolved the issue.
There was one fix for boot loop involving Titanium backup, I used that one and never had the problem again.
I think that may be the one you are referring to?
Related
I don't understand what's going on. I am not a noob; I've rooted 10+ android devices and have been in the mobile game since windows mobile 5.
I follow all instructions to the T from here
http://nookdevs.com/NookColor_Rooting
Everything goes as it should until it is time for the final reboot. Instead of displaying a new boot animation, it simply gets stuck at the screen with the lowercase "n" that says the blurb about adobe at the bottom.
Same both with the SD card in, and without it.
I am able to salvage the situation by doing the 8 interrupted boot plus the homescreen and power key. Started from scratch again - updated to 1.01, reflashed the sd card, etc.
Same result. This is a brand new device, just bought today.
Any ideas? You don't think they killed the root exploit, do you?
I believe I just figured out the problem. The link in the WIKI to the B&N 1.01 update is outdated and incorrect - it links to the incompatible 1.1 update instead, which is not autonooter supported.
Those instructions worked for me. It sounds as if your boot partition is completely empty. Are you using Auto-nooter 2.12.25? That is the version you need to use if your NC is already running 1.0.1.
edit:
Just saw your update. In that case in the B&N link replace 1.1.0 with 1.0.1 eg:
http://images.barnesandnoble.com/presources/download/nookcolor/v1.1/Sideload_update.zip
should be:
http://images.barnesandnoble.com/presources/download/nookcolor/v1.0.1/Sideload_update.zip
otherwise there are a couple other threads where people have thrown up the 1.0.1 sideload update.
computerpro3 said:
I believe I just figured out the problem. The link in the WIKI to the B&N 1.01 update is outdated and incorrect - it links to the incompatible 1.1 update instead, which is not autonooter supported.
Click to expand...
Click to collapse
The link has not changed, the B&N reference within it has. But perhaps something should be tweaked on the URL for now, or the instructions. Done.
I was given a g Tablet last week for my birthday. I've spent hours digging through this site and I installed Clockworkmod and TNTLite 4.2.4. I have the following questions/problems...
1) I can't get Market to run. I've installed it using the instructions in this thread but when I click it, the screen briefly flashes white and then the menu page returns. When I go to the Applications menu, the cache is empty.
My other two spring from not being able to get Market running.
2) I desperately need to get Root Explorer running so I can unprotect the system directory and enable Graffiti. I loathe virtual keyboards.
3) I'd like to figure out how to sideload apps. I learned how to install .apk files, but not how to install an app that doesn't have an .apk file.
Again: I've spent hours on this site looking for answers, so please don't 'search is your friend' me. That being said, I'm more than happy to get a snarky, "This took me 3.5 seconds to find" with a link to the answer.
Thanks in advance for any help.
Shawn Stanford said:
That being said, I'm more than happy to get a snarky, "This took me 3.5 seconds to find" with a link
Click to expand...
Click to collapse
This took me 0.4 seconds to find...
http://forum.xda-developers.com/showthread.php?t=861044
Once you get market working, you can install root explorer and you're good.
Shawn Stanford said:
3) I'd like to figure out how to sideload apps. I learned how to install .apk files, but not how to install an app that doesn't have an .apk file.
Thanks in advance for any help.
Click to expand...
Click to collapse
Sideloading apps just means installing the apk from somewhere other than the market. You can't install an app if it doesn't have an apk. The apk is the app. Unless they give you an update.zip or something, and even then, there is an apk in it.
I know this is off topic I got one for my best too I love it
Sent from my VEGAn-TAB using XDA Premium App
Shawn Stanford said:
I was given a g Tablet last week for my birthday. I've spent hours digging through this site and I installed Clockworkmod and TNTLite 4.2.4. I have the following questions/problems...
1) I can't get Market to run. I've installed it using the instructions in this thread but when I click it, the screen briefly flashes white and then the menu page returns. When I go to the Applications menu, the cache is empty.
My other two spring from not being able to get Market running.
2) I desperately need to get Root Explorer running so I can unprotect the system directory and enable Graffiti. I loathe virtual keyboards.
3) I'd like to figure out how to sideload apps. I learned how to install .apk files, but not how to install an app that doesn't have an .apk file.
Again: I've spent hours on this site looking for answers, so please don't 'search is your friend' me. That being said, I'm more than happy to get a snarky, "This took me 3.5 seconds to find" with a link to the answer.
Thanks in advance for any help.
Click to expand...
Click to collapse
Try this to fix your market
Step 3.
Open the Market app. Once it loads close it (press the home button).
Step 4.
Go into Settings - Applications - Manage Applications - Market - Clear CACHE - Force Stop
(For TnT/TnT Lite... Settings - Applications - System Applications)
Step 5.
Press back once - Google Services Framework - Clear DATA - Force Stop
Step 6.
Go back to your home screen and open up the market. You should get an error. If not, redo steps 4 and 5 until you do.
Step 7.
Reboot your device. After it starts back up let it sit for a minute or two to let things in the operating system normalize. Open the Market. Reboot your device.
Step 8.
Open the market again and enjoy
And to side load my apps i use something like dropbox and place the apps in there and then load the dropbox app on your gtab and any files and folders that you placed in there you can side load. Hope this helps!
Might as well gotten the TNTL 4.4.0, has alot the fixes implented already and stable.
Here the page if you are interested
http://forum.xda-developers.com/showthread.php?t=842004
Here's the problem: all of the fixes to Market require that Market actually loads:
6) Now you are going to re-do the original Market Fix. ... First, make sure Market is running, and browse around in it for a few seconds. If you don't do this, there may be no cache to clear and for some reason the market fix may not work. ...
Click to expand...
Click to collapse
As I mentioned: Market has never successfully loaded for me. I get a brief white screen and then the panel I launched from reloads. This is the only app where I'm having this problem.
And, of course, without Market, I'm dead in the water on pretty much everything else...
Use an updated ROM
As posted before, use the latest ROM for what you are trying to accomplish. The fix has already been done. Try the Vegan 5.1 then the 5.1.1 supplement. It is really stable and stuff works.
I know you're asking about getting the market to work with TNT lite, but nobody seems to have an answer for you. So, if you want your tab to just work, including the market, google apps, etc...
1 - Go here http://vegantab.gojimi.com/downloads/ and download VEGAn-TAB GingerEdition
2 - Plug in a USB cable and drop that zip file onto the root of your SD card
3 - Reboot into ClockworkMod (power off, then hold volume + while powering on)
4 - Use ClockworkMod to do these steps:
- wipe data/factory reset
- wipe cache partition
- wipe dalvik cache (it's under advanced)
- install zip from sdcard
- - choose zip from sdcard
- - - select VEGAn-GE-7.0.0-RC1-Harmony-signed.zip
- reeboot system now
5 - after it boots up, do the setup
6 - POWER OFF once setup is done - don't skip this
7 - power back on
8 - enjoy the Gingery goodness including the market, google apps, a juicy speed boost, etc, etc, etc.
It will be running VTL.Launcher v1.5. If you like the launcher, or if you just want to thank Gojimi for the awesome rom that was so easy to install (and it just worked with no futzing around), go into the market and buy the new version of VTL.Launcher. It costs almost nothing and you're not going to find a better launcher for a tablet. More info on VTL.Launcer here http://forum.xda-developers.com/showthread.php?t=1046302
Just in case you got desperate, started playing around with things and accidentally upgraded to the locked bootloader:
http://forum.xda-developers.com/showthread.php?t=1036956
And here's the official post about the release of GingerEdition:
http://forum.xda-developers.com/showthread.php?t=1031250
DanLynch said:
8 - enjoy the Gingery goodness including the market, google apps, a juicy speed boost, etc, etc, etc.
Click to expand...
Click to collapse
Ah, man...
Initial reboot after installing VEGAn is unsuccessful: I'm not getting past the birds.
Crappity, crap, crap...
Is this the 'locked' bootloader? If so, I wish I'd figured that out before I moved on. I can see the instructions for fixing it in that thread, but how do I get the .zip file to tablet memory now?
NVM: Found the 'mount' option in CWM. I'm on it like a jimmie hat. Further updates as events warrant...
Frack! Still stuck on the birds...
After several painstaking attempts to get VEGAn installed, I'm going to reinstall the downgrade to regain use of my pad while I decide where to go from here.
It is a common issue for the tablets to have been shipped with some mixed up partitions. It doesn't seem to bother the Froyo based ROMs, but it causes the GB based roms to hang at the 'birds'.
Find the thread/directions on doing nvFlash. That will restore the tab to the true stock state (including the proper partitions) and you can then flash GB based roms with no issues.
I got my gtab less than a week ago. In this short time, i have tried the stock rom, vegan 5.11, vegan 7 gingeredition and cynogenmod 700/702 and TNT lite 44! And i have to tell you that i loved each one of them!
But before I flashed anything, i followed the instructions in this thread to the letter.
httpi://forum.xda-developers.com/showthread.php?t=865245i
My recommendation to you will be to start over and read first then read again and then implement!
For now i am settling on TNTlite 44 as it offers the best combination of what i need. I decided to stay away from gingerbread as hardware acceleration and video playback suffers on it. Vegan 511 is based on 2.2 but somehow i felt graphics were not up to my expected level. Again these are all my personal preferences, so you definitely want to try them all before you settle on your rom.
Having said all this, i greatly appreciate all the hard work from all developers of these rom and thank them for such great options for the gtab!
Shawn Stanford said:
After several painstaking attempts to get VEGAn installed, I'm going to reinstall the downgrade to regain use of my pad while I decide where to go from here.
Click to expand...
Click to collapse
Shawn, take a break from it and come back later. It really is worth your time once you get rolling.
nimiaj said:
I got my gtab less than a week ago. In this short time, i have tried the stock rom, vegan 5.11, vegan 7 gingeredition and cynogenmod 700/702 and TNT lite 44! And i have to tell you that i loved each one of them!
But before I flashed anything, i followed the instructions in this thread to the letter.
httpi://forum.xda-developers.com/showthread.php?t=865245i
My recommendation to you will be to start over and read first then read again and then implement!
For now i am settling on TNTlite 44 as it offers the best combination of what i need. I decided to stay away from gingerbread as hardware acceleration and video playback suffers on it. Vegan 511 is based on 2.2 but somehow i felt graphics were not up to my expected level. Again these are all my personal preferences, so you definitely want to try them all before you settle on your rom.
Having said all this, i greatly appreciate all the hard work from all developers of these rom and thank them for such great options for the gtab!
Click to expand...
Click to collapse
Could you clarify what you mean by this?
I am currently running VEGAn 5, and have no huge problems with it at all, but if TnT offers something better, then I may jump on that.
What do you mean by the graphics not being up to the expected level?
Thanks for the advice, everyone. I did a repartition when I started installing TNT Lite. I assumed it would 'stick', but I'll restart from scratch and shoot for VEGAn for a change of pace. Prolly give it a try tomorrow if I hit a slow patch at work.
Just had a thought...if you just got your Gtab the other day, there is a chance you may have been running the new 1.2 dev instead of the old 1.1(which is what most all the ROMS available are based on) and supposedly the two don't really play well without NVFlashing first...so that may be the issue you are having. Then again it may not. Good luck and I hope it all works out.
When using Vegan 5.1.1 I noticed that some of the graphic elements of the UI would look "shaded" or "grainy" (from a proper viewing angle). Also I have some standard wallpapers that I migrate over whenever I reflash. These were also looking a little lower in quality. Now it may be just me or my specific GTab, but that's what I observed. I did not see this when using either of the Gingerbread roms or the stock rom or the TNTLite.
Before you jump on, remember that TNT Lite 4.4 is essentially closed, and I moved over to try it and plan to stay on it until there is any news about hardware accelerated drivers for Gingerbread or Honeycomb comes along! Hope this helps.
Okay, I tried getting Ginger to work three additional times, including following the original instructions I followed to load TNT Lite step by step: no dice. I'm out of patience with it; at this point I'm running the 4349 downgrade.
I was planning on reloading TNT Lite, but I'm not sure it's worth the effort. I never did get Market or Graffiti to work.
Alright I rooted my Nook a few days ago. I have a 1.2.0 so unfortunately I used an older version of ManualNooter and then installed the latest version on top of it. It worked fine until I downloaded Angry birds from the market, after that NO GOOGLE apps worked, such as Gmail, market, etc.
So I unrooted my Nook. Unfortunately the only apparent stock image out there for unrooting is 1.0.1....but I did it anyway.
It seemed to work but when I looked for the storage on my Nook, it said 0B of 0B used. So it seems that my internal storage has disappeared!
Aside from that....nothing will download and I can't hook my Nook to my computer, it just doesn't recognize it. (believe me I tried everything, I even called support, they just wanted to give me a new USB, but that's not the problem)
I was trying to update it back to 1.2.0 but clearly I can't if I can't even download it on my Nook! What is going on? I never hooked it to my computer before I rooted it, so I don't know if it truly couldn't connect beforehand (but I've heard its a common problem)
Anyone have these issues? I just want to get the storage found, hook up to my computer so I can properly re-root my nook to hopefully cm7 this time because I've heard that is much more stable than ManualNooter.
I'm at the end of my wits, I got this a few days ago, so I'm thinking of trying to exchange or return it if I can't fix it.
Any suggestions?
It appears you are having a similar issue to this user:
http://forum.xda-developers.com/showthread.php?t=1184458&page=2
Did you start with a "blue dot" Nook with the new partition sizes? If so, I don't know how trying to restore with a 1.0.1 image made for the old partitions affects your device. That may be the problem. This would require you to repartition your device (see thread in this forum) and restore again with 1.0.1. Just a thought. Maybe someone else will chime in. Might be something very simple that we are not thinking about.
Edit: What version of CWR are you using?
Just wanted to get the work out that B&N announced on FB this morning (18 minutes ago as I post this) that there is a 1.3 upgrade to the NC.
From the B&N Community link on FB:
Starting today, NOOK Color owners have access to firmware version 1.3, a software update that enhances the best-in-class NOOK Newsstand by offering even more interactive versions of the country’s favorite magazines and newspapers.
Not only does this update offer access to new bestselling titles including People, Time, Sports Illustrated, Fortune, Parents and Fitness magazines, the new capabilities allow for Special Interactive NOOK Editions with enhanced content—like videos, audio podcasts, animations, photo galleries, and more—for select titles. Plus, print subscribers to People, Time, Sports Illustrated and Fortune can enjoy the NOOK Magazine™ versions on their NOOK Color at no additional cost.
Also included in the update are performance improvements and new features.
NOOK Color customers can enjoy these new features through a free software update available at www.nookcolor.com/update or provided over the air (OTA) to customers connected to Wi-Fi beginning this week.
For more details about this update, please read the full press release here.
Click to expand...
Click to collapse
Okay, I have an interesting situation...
I purposefully installed CM7 on a uSD (using verygreen's guide) to keep my NC stock while I am in my warranty and for other reasons.
At some point however, I must have used CWM's (ROM Manager) feature to Flash CWM Recovery. I know this because when I follow B&N's instructions to manually update to 1.3 the NC reboot's into CWM (I had previously removed my uSD with CM7 on it so there would be no trouble with the update process).
When the NC boots into CWM, it is with errors that it does not find a "signed" zip file and I can only reboot (which reboots back into the stock ROM just fine).
I haven't had much time (as I'm at work at the moment) to investigate this so my question is...does anyone know how to remove CWM that has been installed from the "Flash CWM Recovery" feature in ROM Manager? Or is there a way to bypass CWM during the 1.3 update process?
I was hoping to have this on 1.3 so I could play with it at lunch
Any ideas?
P.S. I am hoping to be able to remove CWM without resorting to flashing a new stock ROM if possible....
cdaters said:
Just wanted to get the work out that B&N announced on FB this morning (18 minutes ago as I post this) that there is a 1.3 upgrade to the NC.
From the B&N Community link on FB:
Click to expand...
Click to collapse
You are a little late.... http://forum.xda-developers.com/showthread.php?t=1231136
patruns said:
You are a little late.... http://forum.xda-developers.com/showthread.php?t=1231136
Click to expand...
Click to collapse
Saw that after I posted...I guess I'll have to follow them on twitter, heh
fwiw, I just loaded the stock rom over the top of my stock rom that had CWM flashed to the eMMC.
I wish that CWM had a feature to "un-flash" and that locations were not hard coded in the app (because it seems that it wants to install to eMMC every time) so it could be used interchangeably with the eMMC or a uSD installation of custom ROMs.
Perhaps verygreen's instructions should be updated. I have seen far too many people who ended up with custom coding on their eMMC and that is definitely a no no..... verygreen has not posted in over a month though he has been here.....
patruns said:
... verygreen has not posted in over a month though he has been here.....
Click to expand...
Click to collapse
Yeah. I had PM'd him regarding his installer a while ago but he has not responded either...he has fallen into "lurker mode"
I don't even know what I was thinking when I flashed it, probably just to see what it did with regard to running from the uSD more than anything else. I had previously been using CM7 on the eMMC before I went the CM7 from the uSD route.
Verygreen very clearly outlines the update process though if we just read his guide. I'll be the first to admit that I usually skim through things and jump right to it, heh, I am sure others do this too. So I can see where it is easy to miss. Even seasoned IT people like me miss things.
Hi all,
I have a very strange issue after the latest official OTA update to version 7.4.1.
I recognized that my KFHD updated the firmware and after this, I had no root anymore. I used Root_with_Restore_by_Bin4ry_v30 and my KFHD was rooted again (confirmed with root checker). Now I see that I am no longer able to user the settings menu at the top, for wireless network connection, brightness, etc., because it is no longer available. From time to time it appears for a very short period, but disappeared at the same time and I have no chance to drop down this menu.
Anyone here with the same problem or who can help me?
Cheers,
Ingo
Guys, no one, who can help me?
arnakin said:
Guys, no one, who can help me?
Click to expand...
Click to collapse
If you have a recovery installed, I would say just grab the rooted 7.4.1 from the development section and flash that after full wiping. That should solve your issues.
arnakin said:
Hi all,
I have a very strange issue after the latest official OTA update to version 7.4.1.
I recognized that my KFHD updated the firmware and after this, I had no root anymore. I used Root_with_Restore_by_Bin4ry_v30 and my KFHD was rooted again (confirmed with root checker). Now I see that I am no longer able to user the settings menu at the top, for wireless network connection, brightness, etc., because it is no longer available. From time to time it appears for a very short period, but disappeared at the same time and I have no chance to drop down this menu.
Anyone here with the same problem or who can help me?
Cheers,
Ingo
Click to expand...
Click to collapse
When (if) Kinology gets updated (for 7.4.1 support), flash that and your problem will be solved. Unless you don't care about what software version you are on. In that case just flash it now.
A similar problem
-a- said:
When (if) Kinology gets updated (for 7.4.1 support), flash that and your problem will be solved. Unless you don't care about what software version you are on. In that case just flash it now.
Click to expand...
Click to collapse
The OTA updated to 7.4.1 and i tried flashing a custom ROM by Hashcode but, recovery isn't working and with a force recovery in FireFire Flash. It shows a yellow triangle with an explanation point. Also, my audio has stopped working but, i may have found a solution.
To keep in mind: Already Rooted with B4NARY's root, and Google Play Installed.
All Help is appreciated!
CVanB said:
The OTA updated to 7.4.1 and i tried flashing a custom ROM by Hashcode but, recovery isn't working and with a force recovery in FireFire Flash. It shows a yellow triangle with an explanation point. Also, my audio has stopped working but, i may have found a solution.
To keep in mind: Already Rooted with B4NARY's root, and Google Play Installed.
All Help is appreciated!
Click to expand...
Click to collapse
Personally the only tool I've ever used because I got myself in so deep at one point I had no options was the Kindle SRTool, the others seem to create problems, not because the tools were written bad or anything, but because amazon seems to like pushing out updates that don't really update much, but change things just enough to mess with the functionality of the tools. If you can get back to fast boot, you should just use the SRTool and start fresh. Then go to prokkenexxusa's rooting thread and use the manual root method not the automatic.
Solved
DroidIt! said:
Personally the only tool I've ever used because I got myself in so deep at one point I had no options was the Kindle SRTool, the others seem to create problems, not because the tools were written bad or anything, but because amazon seems to like pushing out updates that don't really update much, but change things just enough to mess with the functionality of the tools. If you can get back to fast boot, you should just use the SRTool and start fresh. Then go to prokkenexxusa's rooting thread and use the manual root method not the automatic.
Click to expand...
Click to collapse
I didn't click flash script when I rebooted into recovery from fire flash. In fire flash you have a couple options, two mandatory, using a older bootloader as the 2nd. flash a boot partition image, apply stack override, flash a recovery partition image, disable auto recovery auto update, then wipe cache wipe data wipe system install zip files, flash and install script. Lastly reboot and reboot into recovery. :victory:
So did you get your issues sorted OK, or are you still having problems?