Does the NC have a recovery? - Nook Color General

I'm just curious if the NC has a recovery so that someone can start to create custom Roms and Kernels. I just installed dolpin,k-9,launcher pro, root explorer,kindle(haha) and home switcher. Now it's like a tablet not just an ereader!! I was able to set launcher pro as default so now when I hit the n button it goes straight to launcher pro.
Anyways It would be awesome if we could get custom roms on this thing

WOW 120 views and not a single reply...

To my knowledge there is no custom recovery available at this time. The device does have a builtin recovery mechanism however, you can check out the wiki for information about how to acticvate it.
In addition, the device attempts to boot from the sdcard before the internal memory, so that is a very low risk way to develop for the device until a custom recovery is available.

http://www.nookdevs.com/Flash_back_to_clean_stock_ROM

Novarider said:
I'm just curious if the NC has a recovery so that someone can start to create custom Roms and Kernels.
Click to expand...
Click to collapse
There is no custom recovery and actually no stock recovery for the NC yet. This doesn't mean that custom roms and kernels can not start cooking as the NC is happy as a clam booting from the SD which can be used to start developing customs ROMs while we wait for a recovery (or an alternate flashing method like the nooter for custom roms)

Well, some of us are idiots and we're waiting for the really smart guys to wow us with their magic. Hang in there.

Related

Sorry

so i got my g1, ive rooted it and all that, so now i want to flash a custom rom on it. i actually flashed one, and it worked, but the theme of the rom is not on my g1? is there a reason why? all i did was put it on the sd card, boot it up in recovery mode and install it from there. Now i want to install another rom with a cool theme, but all the roms in the development sections dont have pics?
http://db.androidspin.com/androidspin_developer_display.asp?developerid=85
this was the rom
wipe and reflash?
ThroughHymn said:
so i got my g1, ive rooted it and all that, so now i want to flash a custom rom on it. i actually flashed one, and it worked, but the theme of the rom is not on my g1? is there a reason why? all i did was put it on the sd card, boot it up in recovery mode and install it from there. Now i want to install another rom with a cool theme, but all the roms in the development sections dont have pics?
http://db.androidspin.com/androidspin_developer_display.asp?developerid=85
this was the rom
Click to expand...
Click to collapse
Most roms do not require screenshots because everyone knows what the basic Android system looks like. Why waste time and space posting screenshots that looks like every other rom and what you already have on your device (by default).
I think what you should consider is flashing a basic rom and then look for a theme that supports it. A can be anywhere between 35mb to 130mb in size. Most themes are only around 5mb to 20mb depending on what is included.

[Q] first android

im making the big move from android i was will the cydia community from the begining and i want to move on to bigger and better things now this is true android noob coming out of me what is the best noob thread to root my phone sgh-I897 with 2.1 update 1
i dont even know where to start and after waiting 2 weeks to make this post hoping that i could find what i need has come down to asking for help
Read all the noob threads that are stickied. This little tool is great AIO Toolbox
i have read everyone but there is still this part of me that asks why is everyone different m scared to do this and then find out o wait i should have used that post how can i positive what thread will work for me and if it is the AIO toolbox how do i can that's what im getting at
Is there anyway be positive that aio will work
There isn't 1 sure way. Most of the times there are many right ways to do it. If your phone is on 2.1 then its will take well to JF6 and might have the 3button glitch. AIO will get you root access to your phone. If you are going to flash a rom then you can just ODIN a kernel with Clockwork recovery and just flash the rom there, no real need to root it.
ok i think thats what im stuck on why should i not root and do a custom rom a lot of ppl keep saying that to me plus if i root them i can change roms on the fly with the right apps right? so if someone could fill in my blank here
jesterofdeath666 said:
ok i think thats what im stuck on why should i not root and do a custom rom a lot of ppl keep saying that to me plus if i root them i can change roms on the fly with the right apps right? so if someone could fill in my blank here
Click to expand...
Click to collapse
I'm not sure who is telling you that you shouldn't root your phone or install custom roms. The only (minor) reason to not do it is that it technically voids your warranty, but as long as you flash back to a stock rom before sending it to AT&T, you'll be fine.
If you are rooted and have ClockworkMod Recovery, you will be able to flash other roms that you've downloaded at any time.
jesterofdeath666 said:
ok i think thats what im stuck on why should i not root and do a custom rom a lot of ppl keep saying that to me plus if i root them i can change roms on the fly with the right apps right? so if someone could fill in my blank here
Click to expand...
Click to collapse
he wasnt saying not to do it at all. what he meant was there is no reason to root before you flash a rom. the rom itself will be rooted after the flash.
the apps you are thinking of is rom manager, it is useful on other devices but on the captivate not so much. all is does is download an update.zip to your phone with cwm on it and boots you into it. whch you would need root to use the app.
BUT you can do it manually quite easily without the need to root. I've attached the update.zip that rom manager would download. put this and a froyo rom (gingerbread roms require an extra step) on root directory of your sdcard then boot into recovery by holding all three buttons and releasing when the screen comes on. you will see a blue menu, scroll down with the volume buttons to "reinstall packages" and select ut with the power button then do that last part again and this time it will boot into cwm. choose install zip from sdcard, then choose zip, find the rom and flash it.
I didn't mean to confuse. Just ment that If he was thinking of loading a costume rom he doesn't even need to root and he can skip it by flashing with ODIN a kernel with CWM. My apologies.
see whats the point of a custom room over a theme anyway however i would love to know what you all think is the best rom for this phone
and the wain reason i want to root is to have more control over the phones settings
and what is the point of cmod7 never really understood that even with the research
Custom rom has been tweaked. Theme is just how it looks. Most roms have themes as well, others keep a "stock" look. There is no "best" rom since its a matter of opinion. If by Cmod7 you mean Cyanogenmod its a AOSP rom (Android Open Source Project).
so Cyanogenmod is a rom so all the other layouts and themes that i see for this are just themes not different roms?
studacris said:
BUT you can do it manually quite easily without the need to root. I've attached the update.zip that rom manager would download. put this and a froyo rom (gingerbread roms require an extra step) on root directory of your sdcard then boot into recovery by holding all three buttons and releasing when the screen comes on. you will see a blue menu, scroll down with the volume buttons to "reinstall packages" and select ut with the power button then do that last part again and this time it will boot into cwm. choose install zip from sdcard, then choose zip, find the rom and flash it.
Click to expand...
Click to collapse
so would the rom file need to just be dropped in the root and not touched or does it have to be renamed?
and can i update to gingerbread with out root or a new rom if so whats the other step?

[Q] MIUI for the galaxy beam!! ^^

Hello, people of xdadevelopers! I'm new here and keen to learn up on custom Android roms. Sorry if i sound really noob or am doing things wrong in this forum, but... everybody has their own starting phases right?? ^^ Please guide me where I'm going wrong...
Anyway, I'm from Singapore and i own a SAMSUNG GALAXY BEAM GT-I8520 (rare and unheard of phone released only in Singapore x.x). I won't elaborate much, but basically I'm kind of still a student (therefore no money to buy other phones) and my mobile plan is left with about 11 months to go before i can renew my plan and select another phone for a cheaper price... I don't really like my phone because the moment Samsung released it, they decided to stop updates because there is not enough users of this phone so I'm stuck with 2.1 eclair. It also has a slow 500/700mhz processor and lags like he**. By the way, it was released around July 2010 at the same time with the Galaxy S, and they have really similar specs, that's why i posted in this area of the forums.
So, i was thinking of switching over to the MIUI rom which i desperately want... and i decided to follow the Galaxy S I9000 (because they are sister phones!) tutorials to flash over to MIUI in hope it would revitalise my phone, stop the laggyness and crashes, give it a new look, allow me to use features that i miss out in froyo or gingerbread!!
I can understand most terms and softwares about flashing... been researching for a few days... and i found this guide
http://forum.xda-developers.com/showthread.php?t=1101601
which tells me to replace my bootloader with a gingerbread bootloader through ezodin, then boot into recovery mode which is the custom cwm recovery, and from there straight up install my rom that was placed in the sd card, and walla i get my MIUI. I assume that the bootloader will give me CWM recovery because the guide doesnt tell me to get it through rom manager. I currently have the base google stock recovery, so question <1> do i have to install cwm recovery through rom manager first or will the gb bootloader give it to me once flashed? and question <2> i've tried to install it through rom manager but it didnt work the first try (i chose my phone model as the S) and even erased all my apps and data :S Is there a way to go around installing clorkworkmod? I understand my phone isn't EXACTLY Galaxy S, but they're similar...
Also, another problem i face is that i DON'T have the 3 button shortcut to recovery mode or download mode. I'm following this tutorial to try repair it, since I've heard a batch of Samsung galaxy s have flawed recover and download modes that can't be accessed by the 3 buttons. since the two phones were released around the same time, it could be that the galaxy beam was affected also. Everything is fine going through this tutorial (even getting to download mode trough ADB is fine), problem is i get stuck every single time in ODIN at SetupConnection. Question <3> any freaking idea how to solve this? I've gone through google and searched through this forum... Now i don't know what to do and don't dare try anything else or other flashing unless i fix this 3 button shortcut because i know i can only access recovery or download through ADB REBOOT RECOVERY / DOWNLOAD and the phone has to be plugged in, turned on, booted into android, and in usb debug mode. the ADB command won't work if the phone is off and i'm worried the GB bootloader will stop eclair from loading.
This leads to the question <4> if i decide not to follow this repairing tutorial and just flash the gingerbread bootloader up front, will it give me the 3 button shortcut boot? because if i am not able to load the eclair rom with gingerbread bootloader, and have no 3 button shortcut, i will not be able to boot into recovery to install rom and wipe data and cache etc. Also, if i flash the gingerbread bootloader, can i still load into my stock eclair rom? If i can load into the stock eclair rom, then i don't need the 3 button shortcut, i can go straight to doing usb debug and the ADB command again after flashing bootloader and rebooting to go straight into recovery and installing MIUI.
Question <5> What about gingerbread bootloaders that can backtrack and load froyo roms and eclair roms? Do these exist? Where to download? If so, i can load into my eclair rom and use ADB for recovery mode, eliminating the step: repairing the 3 buttons.
Question <6> Also, i noticed the guide didn't speak anything about kernels etc. From what I understand about kernels, it is the architecture or system between the hardware and the software. People can tweak kernels (leading to custom kernels) for different and maybe even better sound and video etc right? But the guide doesn't say anything about installing a custom kernel, so am i supposed to keep my current Zues kernel from Samsung, or is a custom kernel recommended by MIUI ALREADY provided in the zip folder i downloaded from here? (the I9000 one) When i flash this zip through CWM recovery, is the kernel changed together? Does this apply for the bootloader also? Is the bootloader supplied in the zip and flashed together at the same time? if everything, (rom kernel bootloader) is flashed together at the same time then i can eliminate many steps and just work on installing CWM recovery through rom manager. then use adb to boot into recovery and flash that one simple MIUI zip. no need for 3 button boot...
Question <7> Is there another way to get MIUI to install on my device without so much hassle? haha..
Thanks for the trouble, I know it's a lot of questions... Please answer whatever you can
umm, almost a 100 views... but no replies? :'(
I'd never heard of it until this post, I looked at some specs and they're quite significantly different to the SGS's ones, smaller screen and completely different processor(which is most important(TI OMAP 3440 720MHz in the Beam and Hummingbird S5PC110 in the SGS)). It's a completely different phone, don't even try to install MIUI for the I9000 on it unless you don't mind your phone being in a bricked state. I may not be right but it's my strong opinion. Here is the Xda wiki for it: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Beam Which shows how to root and then OC it which may increase performance. And if you like the Miui look there is a look a like launcher floating round if you search. Good luck
true, they aren't exactly the same. the processor is definitely different, but i think MIUI was made for performance, which fits well with this lousy processor haha. screen shouldn't be a problem, most softwares fit to screens automatically. I've already Rooted and OC'ed it but its still slow.
Is there any way to flash everything at once, e.g. kernel rom everything flash together at the same time using ODIN, then maybe i will reboot and see if the MIUI works... The problematic part is the 3 buttons download mode. I'm willing to flash everything at once then see if i'm lucky and MIUI will work for me. I'm not willing to flash just kernel or etc, then can't get in to download mode already because phone cant be booted, thus cannot install ROM...
Does anybody know exactly what when flashed into the phone gives me the 3 button recovery and download...?
I also realised something in the wiki link u gave me...
Power+Menu+Volume Down -> Soft Reset
Power+menu+Volume Up -> Ready for Flash Screen
Could this be my recovery and download...? I'll try later.
I'll try and give you an example, the Galaxy SL or the I9003 came out the start of this year as a replacement for the original with the only difference being the chipset and display type. Quite a few people have got this phone and have being trying to get Miui to work on it hasn't happened. The I9000 kernel for Miui is made for the I9000, it only works with the Hummingbird chipset, end of story. I'm not stopping you from trying but expect the most likely consequence to be the phone dead, not running Miui.
Wow, if the I9003 which was even closer (spec-wise) to the I9000 can't flash I9000 MIUI, then my I8520 won't make it... :'( I understand what you mean, any kernel made for I9000 phones, even custom user-made ones, only work with specific hardware, like that chipset, unless that kernel some how is clever enough to work with my hardware, or probably just lucky enough to be compatible with my chipset.
I didn't know the software had to confirm so tightly to the hardware... I'd always thought software would automatically work with basic hardware, albeit there would be some issues and glitches, but at least it would still work. I thought maybe it would be possible to keep my Zues kernel, and just flash the rom, and let the rom use my kernel.. It wouldn't be very optimised because they weren't made for each other, but at least with a few bugs, still usable... But now I know my Zues kernel works with my hardware but probably wont work with I900 MIUI unless it was coded for my phone... Though, if my phone does have the same chipset and gpu, maybe it will work?
Seems like I'll have to continue to use this lousy unsupported phone :S
Thanks for your help

Root!!!

Please HELP!!! How to root DS7 Honeycomb 3.2 without Clockworkmod Recovery?
You cant, 3.2 has no known exploits at the moment.
konikg said:
Please HELP!!! How to root DS7 Honeycomb 3.2 without Clockworkmod Recovery?
Click to expand...
Click to collapse
What reason is there for rooting yet not installing a custom recovery?
Since I've never really seen any good use of CW other than flashing it might be just as sensible to ask "why add custom recovery to a rooted device?"
I rooted my Archos tablet almost a year ago but never felt a need for a custom recovery on it. If there was a way to root HC on my Streak I'd have done that instead of the CW + flash method that's needed now.
My Archos stock recovery had a bunch of useful things like reset touchscreen, an fdisk like repair disc utility and some other useful things. None of which show up with CW which might make me reconsider its usefulness.
Sent from my Dell Streak 7 using Tapatalk
I"ve had a variety of tablets. The only tablet I've ever had that I needed to root and install a custom rom was the Viewsonic G-Tablet(Bad UI). I think some folks just like to tinker and getting the most out of their gadgets. At this point I see no reason to root my DS7.
If you're fine with not being able to do much of anything but play games on your device there is not much reason to root... but say you live internationally and need to modify the build.prop or say you want ad hoc support.... or say you wanna get rid of all the BS bloatware that comes with your device, you can only do that with root, or applything custom themes, only with root...
As far as custom recovery, well there are updates, and overclocking, and modifications and theming, and all those things can be more easily done with a custom recovery than pushing with adb, IMHO, but some are tried and true to adb
So it's all about the user.... I'm a tweaker, I can't stand anything in its factory form because we all know it leaves the factory with set back parameters, whether it's your cell phone or the car you drive everyday, there's always room for tweaking

Custom Recovery Loop

I know a lot of people are in this sticky situation with me.
But hey guys, XDAers, Googlers, Developers & the rest of y'all
So I have a S3 Mini (with NFC so i8190N) and I hack it a lot, I mod, I do a lot of root-y stuff on it.
Well today's objective for my phone was to flash a Custom ROM that blended together TouchWiz and KitKat since I can't get that officially for my phone, I found LostVirginity V2 from the guy who made the Virginity ROMs (I forgot his name but big ups to him, thanks for the crazy cool ROMs bro!)
So I tried to flash it in TWRP.....and it didn't work because TWRP consistently freezes when I press anything and i have to do a battery pull.
Then I used Odin to flash CWM and it flashed it but when I rebooted it my phone decides to not listen and just go back to CWM like CWM has a leash on it or something, I mean come on! TWRP replaced you for a reason and you're trying to get us all back, you're old and forgotten CWM...
So now I've got that frigging annoying TWRP/CWM loop where whatever you do it just reboots to the custom recovery, pretty much the only thing I can do is use Odin to flash another custom recovery (only ones I can switch between are (any version of) CWM, PhilZ's Advanced CWM and any version of TWRP)
I've been trying everything, some guys on redmondpie, android central and rootzwiki (I think that was the website) fixed the problem on the ASUS Transformer Pad but they installed terminal emulator, I've got that but if I could access that that'd defeat the whole point of this thread because that would mean I'd have access to the Android system.
So my question is: Now that I'm imprisoned by the claws of the custom recovery, how do I escape?
Do I flash another firmware through Odin or something?
Somebody help me, and anybody who's been through this problem or is going through this problem at the moment, tell me what you did/what you're doing so we know what to rule out and stuff
Thanks guys

Categories

Resources