I'm trying to understand the different roms that are available for the tablet but I'm overwhelming myself with information. I see from the posts I've read that there are several available from Gb to Jb but I'm trying to run down the one that isn't Gingerbread and is most stable with the fewest bugs. I understand from dropping roms on my Droid X that whatever I choose will not be perfect but I'd like to find a balance.
My follow-up question would be what is regarded as the best way to flash the rom to the internal memory of the tablet? If I try to reboot into recovery the nook crashes on reboot.
I'm running CM7 already but I would like to try other flavors.
Thank you for taking the time to read my posg.
Sent from my DROIDX
I'll try to find the link later, but there's an app that flashes a functional emmc cwm recovery, or you can use goo manager to get TWRP. Also the most stable is chroffman's CM9 from with the 2.x kernel. That's what I typically use.
Sent from my NookTablet using xda app-developers app
I really do appreciate the help. I've flashed the nook tablet recovery app but when I use it to reboot I just get a message that there's a problem and to contact barnes and noble
Sent from my DROIDX
Then download goo manager from the play store, use that to install recovery, then use it to flash CM9, then use the app again to flash CWM. Then you should be fine. Then you can reboot straight into recovery, or use cyanoboot to load recovery.
Sent from my NookTablet using xda app-developers app
Related
I'm sorry but i couldnt find anything about it.
So, basically my question is: Is it actually compatible with the XT720 and, if so, what model should i pick when i try to install clockworkmod recovery?
(The XT720 option is absent.)
I'm currently using dexter's froyo and planning on trying out a few other ROMs so ROM manager would be quite nice to have.
Thanks in advance.
It can run this but its dangerous to use it advice stick to open recovery.
Sent from my XT720 using xda premium
OK, thanks.
Is it normal to be stuck on system dumping for more than an hour while making a backup? The media LED is blinking the whole time.
I'm doing it with open recovery, as adviced
Soo I tried again after an hour and a half of waiting and another half hour after that, the result - two 3.5MB files... I gave up and decided to go ahead and install CronosX-RC1-br301-g but openrecovery just sais there's nothing in the cronosx folder, i try to restore all, and basically nothing happens. After rebooting dexter's froyo is intact so i'm going to bed and hoping somebody will help
What Open recovery are you using.
Sent from my XT720 using xda premium
1.46, if i understand right. it's system recovery in app drawer, which kinda puts me off
Install open recovery apk then open install open recovery system and boot in to recovery.
Sent from my XT720 using xda premium
Quick question I have been unable to get a rom to install on slot 1 of boot manager i was close but at the end I got error: unable to create new boot.img... So close. I am running 3.14.605.10 firmware, s off, viperrez. I on boot manager I have small image selected, screen force on, and ext4 selected any help would be appreciated. Oh and I tried doing cm9 and also neomax roms on slot 1
Sent from my ADR6425LVW using xda app-developers app
Bump
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Bump
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Same problem here. I don't know what is causing the problem but I read somewhere that a work around for the boot manager problem is to restore nandroids to each slot. Just make a nandroid of your current ROM, wipe device, install new ROM, set it up and make a nandroid of the new ROM. Do this for each ROM you want to use in boot manager. Once that is done restore whatever ROM you want to be the phone ROM using regular recovery. Once that boots open boot manager (follow instructions) and restore each nandroid to adifferent slot. I'm trying now.
motenak said:
Same problem here. I don't know what is causing the problem but I read somewhere that a work around for the boot manager problem is to restore nandroids to each slot. Just make a nandroid of your current ROM, wipe device, install new ROM, set it up and make a nandroid of the new ROM. Do this for each ROM you want to use in boot manager. Once that is done restore whatever ROM you want to be the phone ROM using regular recovery. Once that boots open boot manager (follow instructions) and restore each nandroid to adifferent slot. I'm trying now.
Click to expand...
Click to collapse
Yeah. That was my last resort lol ill try it out also, good luck!
Edit: no dice still get the error building boot.img
Sent from my ADR6425LVW using xda app-developers app
So, I've been on 10.1 for a while, and ever since, I can not Reboot to Recovery using normal options.
The only way I can get in to recovery is to open Rom Manager, flash recovery, then reboot recovery from INSIDE rom manager.
No other way works.
It's kind of annoying. I decided today to flash back to stock using ODIN and start fresh again.
From stock, I install CM7. I can reboot to recovery using CM7 no problem.
From CM7, I install CM10.1 nightly (the latest), and after the phone finally gets in to 10.1, I can no longer reboot to recovery from the reboot menu.
I have to install Rom Manager, then flash recovery from it, then reboot from it.
I have to do this process EVERY time I want to reboot recovery.
Any other way I try, it just reboots normally and not in to recovery.
What gives? Anyone else with this problem?
Thanks.
I just tried to use Terminal Emulator and that fails as well.
su
reboot recovery
It just reboots normal.
Have you tried using any other 4.2.1 ROMs?
Sent from my SGH-T959 using xda app-developers app
No, i haven't.
Well then try like hellybean
Sent from my SGH-T959 using xda app-developers app
You should expect to run into problems when using a "nightly" build ROM. Its practically beta stages, find a ROM that is complete like the poster above mentioned. Cant really recommend any 4.2.ROMS , I stick with froyo ROMS for better performance.
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
You should expect to run into problems when using a "nightly" build ROM. Its practically beta stages, find a ROM that is complete like the poster above mentioned. Cant really recommend any 4.2.ROMS , I stick with froyo ROMS for better performance.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
The reason why I recommended that is because he was on a 4.2 ROM that he was having problems with. Sometimes its painful to go to a lower ROM as far as looks and speed goes therefore I recommended a 4.2 that he could try
Sent from my SGH-T959 using xda app-developers app
No one else using this rom has this problem.
dE.fUsEd said:
No one else using this rom has this problem.
Click to expand...
Click to collapse
Well some phones do actually have random differences. On aokp milestone 6 I had to use a linario build because me and like two other people werwbt getting signal
Sent from my SGH-T959 using xda app-developers app
Still having this problem. Using multiple roms. Now I'm on Baked 4.2.2.
Still can't boot to recovery.
This is annoying as hell.
After running just about every ROM for this device, I recently flashed my first stock based ROM (cooked 1.8). However since this time I've been unable to flash back to any aosp ROM. I get boot looped on every one. I've tried everything. Yet, I can flash cooked again no problem. I know there's something I'm missing. Any help would be great.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
You have a nandroid backup right? Restore that then flash whatever you want.
Sent from my SGH-I777 using Tapatalk 2
Backup won't boot either. That was my first plan.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Have you tried to format system under mounts and storage after your factory reset, and before you flash your rom and gapps? Just a suggestion. Not sure it will fix you problem or not. It seems as if I had a problem similar to what you are describing after running a Samsung based rom in the past. I believe that was the cure to my issue.
adrock74 said:
Backup won't boot either. That was my first plan.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Search for Siyah kernel v4.3.3 in the forums and install, restart recovery and flash away. Should take care of it.
T
Sent from my SGH-I777 using Tapatalk 2
I always have kept that kernel on standby but that didn't work. I've tried every kernel. Can't believe backups won't even boot. I flashed cook's ROM wipe before his ROM the first time, wonder if that did something.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Try Odin to stock and start from scratch. A lot of work but hey what do you have to lose. :beer:
Sent from my SGH-I777 using xda app-developers app
First find a compatible Kernel for the AOSP ROM your trying to flash. Flash that Kernel.
Second, after the flashing is done, reformat the device; cache, dalkiv cache and system and system settings.
Third, reboot into recovery mode from the recovery menu itself.
Fourth, flash the kernel one more time.
Fifth, flash the AOSP ROM of your choice.
Sixth, reboot back into recovery menu.
Seventh, reformat once more.
Eigth, reboot the device.
As you should know, the first boot up after flashing a ROM takes the longest. Give it like a minute or two.
If this doesn't work, you have to flash a kernel that was compatible with the "cooked" rom you were using. Then from there do a reformat from the recovery menu. Once reformat is done, flash the AOSP kernel, then flash the AOSP ROM right after. Then reformat once more and reboot as normal.
If that doesn't work, flash compatible kernel with the "cooked" ROM your using now and also relay the cooked ROM, and then use Odin to bring it back to stock un-rooted. From there, do as you wish.
Butchr said:
Have you tried to format system under mounts and storage after your factory reset, and before you flash your rom and gapps? Just a suggestion. Not sure it will fix you problem or not. It seems as if I had a problem similar to what you are describing after running a Samsung based rom in the past. I believe that was the cure to my issue.
Click to expand...
Click to collapse
That is exactly what needed to be done. Mr cook actually has another thread with cwm flashable wipe scripts that would have done that. Quite handy :thumbup:
I do not see myself having access to a computer anytime in the near future. I had no problem rooting my fascinate from my phone using the framaroot method but I am having no luck flashing a new rom. I want to flash hellybean to get rid of this froyo crap but I just can't seem to do it. If anyone has a way to do this without a computer your advice will be greatly appreciated. Thank you
Sent from my SCH-I500 using xda premium
CyanogenMod installer is coming out soon, and apparently it's going to be compatible with this phone right out of the gate (since it uses download mode and already has an unlocked bootloader)
I did try to use ROM Manager but my install of CM10.1 was pretty much borked after using it. Results may vary, but if you really can't use a computer, download ROM Manager and get the newest CM10.1 build for your phone from get.cm. Flash it through there. It is strongly recommended to use a computer though, since ROM Manager uses an outdated version of ClockworkMod Recovery that may or may not work.
skepticmisfit said:
CyanogenMod installer is coming out soon, and apparently it's going to be compatible with this phone right out of the gate (since it uses download mode and already has an unlocked bootloader)
I did try to use ROM Manager but my install of CM10.1 was pretty much borked after using it. Results may vary, but if you really can't use a computer, download ROM Manager and get the newest CM10.1 build for your phone from get.cm. Flash it through there. It is strongly recommended to use a computer though, since ROM Manager uses an outdated version of ClockworkMod Recovery that may or may not work.
Click to expand...
Click to collapse
See that's my problem, I can't get cwm recovery or twrp recovery to flash, I used Ron manager to flash the recovery and I got a successful confirmation but when I boot into recovery its always android and not the custom.
Sent from my SCH-I500 using xda premium
Tried again with the cm 10.1 and I get the same problem I get booted into stock recovery and I get "can't verify whole file signature" error
Sent from my SCH-I500 using xda premium
i don't mean to be rude but what is your situation where you absolutely can not use a computer?
Don't have one and don't have any friends or family close by to use one
Sent from my SCH-I500 using xda premium
PoiSpin said:
Don't have one and don't have any friends or family close by to use one
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
well unless you can get to like an internet cafe or something i'd say stick to what you have now and wait for CM installer to come out