Database Info

trying to install rom, getting stuck at splash screen

i finally broke down and rooted my Tbolt. I installed Rom manager and am trying to install a new rom. I have tried cyanogenmod 7.1.1 and also Liquid smooth 3.2 . the process seemed to go fine, but each time it got stuck at the splash screen,not the white HTC one, but the "intro" screen for the rom i am installing, i let it run for several minutes, finally removed battery and restored my backup.
anything i am doing wrong?
here is some more info on the phone,
Downgraded to 2.3.4 , rooted with revolutionary root, running the most current free version of Rom manager free from market
any help would be appreciated

First thought
Have you wiped the data of the phone before you tried to install the ROM? I am now expert here but I had a similar problem and when I searched forums for the answer that came up quite a bit. I might start there.
Also the ROMs have very specific install instructions and I would follow them closely to avoid any problems.
I searched and read so much before I rooted and installed my first ROM, it does get easier.
Good luck.

Update your CWM version in ROM manager.
It should be the top choice when you open ROM Manager - update Clockwork Recovery.
Make sure you have ample space on a FAT32 formatted SD card, as well a the minimum radio(s) required for CM.
Prior to flash, in recovery, make sure you wipe data/factory reset and clear cache - also go into advanced and format system.
Post back your results and we'll go from there.

[Q] Problem with OTA update .24

I software OTA update from system and now can't reboot system now. Any one please help me?
Now my eee pad screen is recovery mode showing. Can't reboot system....HELP.....

I am having the same problem. I have tried multiple work arounds' with no luck. Any help would be appreciated.

Ok, just select reboot and press both volume up and down, and keep them in...
A new screen will appear from where the Transformer will boot into Android.
I'm having this exact same issue, quit annoying this is
I've already tried a dozen times to change the clockwork recovery to a newer version but the old crappy one sems to be not willing to make room for the newer touch version.
ps In Rom manager I see the correct version of the cloackwork recovery as being installed but once going into the real recovery it is the old one

Alternative way to result
I installed custom ROM (Android revolution HD) from SD card.
Now it's Ok....This ROM is rooted and fastest..
http://forum.xda-developers.com/showthread.php?t=1245892

ROM manager doesn't work well for the tf, just don't use it in general Dx
minnaing - Good choice of ROM Glad it could be resolved, that was the first thing I was going to suggest to do.

[Q] Verizon S3 locks up every reboot on rooted 4.1.2 > 4.3

I am having a really weird issue I'm hoping someone can help me out with. I was on 4.1.2 Clean ROM which was working great. I wanted to move to 4.3 Clean ROM (8.1 Core Edition). I did the upgrade and then flashed my modem to ML1 both via TWRP.
The ROM setup fine and ran great. However the first time I did a reboot, the phone gets stuck at the Samsung Galaxy S3 logo and never goes anywhere. I left it sit there for 30 minutes and it was hard locked. Only a battery pull would reset it. Through numerous reboots/pulls, the same thing would happen. I tried wiping Dalvik and Cache in TWRP and fixing permissions, to no avail. Reinstalling Clean ROM 8.1 via TWRP without formatting data did not fix the issue either. The only way to get my phone back up and running was a complete wipe and reinstalling from scratch. Then as soon as I reboot the first time, the issue comes back. I've tested this on a clean install - letting the phone go through the initial setup process but not installing or updating any apps - and it still happens.
So I moved on to try AllianceROM build 22, also a 4.3 build and wiped to do a clean install. No matter what options I choose in the setup, the same problem happens. Interestingly in AllianceROM I always get a acore process has failed error on the first boot.
Then I went to download the Knox-free rooted version of stock 4.3 available from Scott's website. I have the same issue with this. Also a wipe with clean install.
It's obvious there is something my phone doesn't like about moving from 4.1.2 to 4.3. In total, I have probably installed three different ROM's about 20 times now after the past couple days.
I've searched about this problem extensively and the only thing I found is a thread for the AT&T S3 that talks about this exact issue, and using Odin to go to stock 4.3 and loading a custom ROM to fix the issue. But I am under the impression that a 100% stock 4.3 will lock my bootloader.
What I plan to do next is use Odin to flash a stock 4.1.2, then go through the process of moving to a custom 4.3 ROM again.
If anyone knows of a tar'd version of 4.3 that won't lock my bootloader, I would be grateful!
If anyone knows of a different way to fix my problem, I would be grateful for that too!

Well I think I can declare victory. My phone is running Clean Rom 8.1 CE and has survived a reboot after every app install for a total of 15 so far.
As it turns out, I think being on TWRP 2.5 and trying to upgrade to Android 4.3 was the issue. Before I went the route of flashing a stock 4.1.2 release, I thought to check if my version of TWRP was the latest, and it was not. I flashed TWRP 2.7, and did a complete wipe and clean install of Clean Rom 8.1 CE, and it's running like a champ.
I know, I know...the install guide on most every ROM says to use the latest version of your recovery - until now I thought that was a "recommendation" or "best practice" and not a hard requirement. Turns out, at least for me, that it is very much a hard requirement. In reading the release notes for TWRP 2.6 and 2.7, they both appear to implement things specifically for Android 4.3 or 4.4.
Hopefully this info helps someone who may be having the same issue.

Unable to restore/mount/flash in TWRP and unable to achieve dl mode in LG Flashtool

Here's to hoping someone can help me out. My phone details before I messed up: LG G3 D850, rooted, TWRP 3.0, running Fulmics 5.2 for about 1 1/2 weeks
I noticed that I was not seeing the LTE indicator on my phone. I checked the HUB and saw the BootD850-30012016 data patch and figured that I just needed to install. So I flashed it and my phone wouldn't start. I was able to boot into recovery, so I figured I would do a clean install of the ROM so I did a full wipe, accidentally wiping EVERYTHING except for my external SD.
Result was that I can access TWRP but am unable to flash any of my backups or zips from my external SD, or OTG. I can see the files, but don't have the option to "swipe". I also am unable to 'mount' or 'install'.
At this point, I noticed that AT&T has finally released the OTA for Marshmallow, so I figured I would just use LG FlashTool and totally un-root and give the update a try. (BTW, I have used the flash tool many times with no problems/issues on both my phone and my son's D855).
Unfortunately, I am getting the dreaded "unable to change to download mode" after 15 seconds. I have uninstalled and re-installed Flash Tool, the LG Drivers and all files and used every port on both of my computers (Windows 10 btw) but can't get past the download error.
So...after many hours of digging, I took a leap of faith and was able to sideload Fulmics 5.1 successfully and install the 5.2 update from the HUB. I made backup of the ROM but TWRP still won't allow me to "swipe" and install/restore. I reinstalled TWRP using Flashify and it installed version 2.8 but still no go on flashing from recovery.
I realize that I'm lucky to have been able to figure out how to get the phone back using the sideload function in TWRP, but I really do want to go back to stock and it bugs me that I am unable to use my backups.
Sorry for the novel, but I wanted to be sure to include everything I did....if anyone can help me out I would be much obliged. My 11 year old is anxiously waiting on me to figure this out before she gets this phone (I'm moving up to the HTC 10 in a couple of weeks!). She still thinks I'm 'SuperMommy' so if I can fix this I get to keep my swagger!

I was also running fulmics 5.1 and updated to 5.2 in my phone but now i was having pretty good laggs and i finally realised that the update provided by the phone was corruped so i went on the official site and downloaded the same 5.2 OTAs from there and flashed it into TWRP recovery to finally get the latest version 5.3..know that is it always advisable to flash zip file when in recovery mode using TWRP recovery...The big mistake was cleaning also the internal memory of your phone.this caused the malfunction of twrp.

The issue is that most often i have seen cases of lagg in those updating to fulmics 5.2 from the Hub .sometimes in twrp recovery the update files will not successfully wipe and then reboot system with 5.2 installed but with many lagg the file downloaded there may be corrupted and not give you permission to swipe..if you really like fulmics and still update to the latest..Try this it may help you solve your problem:1 reinstall the fulmics 5.1 go to xdadevelopers.com/fulmics follow the link given by xpirit to www.fulmics.com and download the OTA 5.2(file size maybe 46 mb).. 2.reboot your phone now in twrp recovery it should now be able swipe and install..(if not then install Twrp 3.0 and try) 3-search the files in your internal memory or wherever you have downloaded it and flash it ..4.reboot system.That should be done!! In case you want to come back to stock and cant install from Twrp then the problem is with Twrp just download the latest version that goes with your phone.

Thanks guys for the suggestions. I finally figured it out after a couple days of sweating and swearing. Yaneddik, you were spot on about updating from the Hub. I ended up installing TWRP 2.8.6 and re-installed 5.1 from the Fulmics website along with the updates. Everything has been working great (except for losing LTE connectivity, but that's for another thread!). I'm not inclined to update TWRP to 3.0 unless absolutely necessary, 2.8.6 works just fine for me.

dcli23 said:
Thanks guys for the suggestions. I finally figured it out after a couple days of sweating and swearing. Yaneddik, you were spot on about updating from the Hub. I ended up installing TWRP 2.8.6 and re-installed 5.1 from the Fulmics website along with the updates. Everything has been working great (except for losing LTE connectivity, but that's for another thread!). I'm not inclined to update TWRP to 3.0 unless absolutely necessary, 2.8.6 works just fine for me.
Click to expand...
Click to collapse
Am a newbie here but a long time rooter on my older phones. This is the first time that I've seen the Hub mentioned. Can you kindly post a link?
TIA
Sent from my LG-H810 using Tapatalk

SofaSpud said:
Am a newbie here but a long time rooter on my older phones. This is the first time that I've seen the Hub mentioned. Can you kindly post a link?
TIA
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
Hey there....you can access the Hub after you flash the Fulmics ROM. It's where you can get your tweaks, downloads, mods, etc. You'll find it in your app drawer.

[Stock][Android 4.0.4 ICS] Nook HD/Nook HD+ [Hummingbird/Ovation] 2.2.1 [2018 Update]

NookOS 2.2.1 (2018 update) LTS Compliance Flashable zip:​
Nook HD+ (Ovation): nookos_ovation_2_2_1.zip​Nook HD (Hummingbird): nookos_hummingbird_2_2_1.zip​
Please note:
Installing stock will be the same as of flashing any ROM. Make sure to wipe everything before the flash.​
XDA:DevDB Information
[Stock][Android 4.0.4 ICS] Nook HD/Nook HD+ [Hummingbird/Ovation] 2.2.1 [2018 Update], ROM for the Barnes & Noble Nook HD, HD
Contributors
secretwolf98, secretwolf98, Barnes & Noble
Source Code: https://help.barnesandnoble.com/app/answers/detail/a_id/4212
ROM OS Version: 4.0.x Ice Cream Sandwich
ROM Firmware Required: TWRP or CWM
Based On: Nook, Barnes & Noble
Version Information
Status: Stable
Current Stable Version: NookOS 2.2.1 (2018)
Stable Release Date: 2018-06-30
Created 2018-09-09
Last Updated 2018-09-09

Installing stock ROM
You mentioned in your post to "Installing stock will be the same as of flashing any ROM. Make sure to wipe everything before the flash." Okay, so what does that mean? Do I connect my Nook HD+ to my computer and clear everything out, as in a reformat, or what. Seems nothing I do will get rid of the error message "Unfortunately, System UI has stopped".
Can you help me on this?
Thanks,
Roger

rmissildine said:
You mentioned in your post to "Installing stock will be the same as of flashing any ROM. Make sure to wipe everything before the flash." Okay, so what does that mean? Do I connect my Nook HD+ to my computer and clear everything out, as in a reformat, or what. Seems nothing I do will get rid of the error message "Unfortunately, System UI has stopped".
Can you help me on this?
Thanks,
Roger
Click to expand...
Click to collapse
In TWRP, advanced wipe, clear system, cache, divac-cache, data. If the package is on the internal storage, don't wipe that. If the package is on a SD Card, wipe the internal storage. No need to flash gapps, because the stock ROM already provides gapps.

I tried this, wiped everything. Flashed and got an error 7 that a xxxxxxxxxx.so filed was not touched.
Rebooted and it hangs at boot logo and twrp is gone.
Nice......
Sent from my moto g(7) power using Tapatalk

MrCamby said:
I tried this, wiped everything. Flashed and got an error 7 that a xxxxxxxxxx.so filed was not touched.
Rebooted and it hangs at boot logo and twrp is gone.
Nice......
Sent from my moto g(7) power using Tapatalk
Click to expand...
Click to collapse
Get a bootable SD card for CWM.

Thank you, this solved my issue

Hi,
Is it possible to get back to stock if internal storage shows 0 bytes?
I've been modified my Nook HD+ partitions with lanchon repit and installed CM11 which was worked fine for me about a year.
But when I tried to install "cm_ovation-ota-MOB31K.161125.zip" for some reason, installation was freeze at some point. I tried 2 more times but couldn't install the ROM.
Then I tried to install CM11 back but I even could not installed that too.
Now my tablet can not boot without bootable SD card.
Please help me to recover/revive my tablet.

Reckless71 said:
Hi,
Is it possible to get back to stock if internal storage shows 0 bytes?
I've been modified my Nook HD+ partitions with lanchon repit and installed CM11 which was worked fine for me about a year.
But when I tried to install "cm_ovation-ota-MOB31K.161125.zip" for some reason, installation was freeze at some point. I tried 2 more times but couldn't install the ROM.
Then I tried to install CM11 back but I even could not installed that too.
Now my tablet can not boot without bootable SD card.
Please help me to recover/revive my tablet.
Click to expand...
Click to collapse
Yeah, this should fix it. I used this before when my tablet had those issues that you have described. It's just hard to test things on my end, because my disk drive for my computer fell on both of my Nook HD and Nook HD+, now they are both completely shattered at the home button.

The download links for both ROMs are offline.
Can anyone provide my with a mirror link?
Specifically I need:
Nook HD (Hummingbird): nookos_hummingbird_2_2_1.zip

Links down

They took down the regular DevDB downloads that were directly linked on threads on the main site in Dec. 2020. They did stand up browsable and searchable archive of the downloads here: https://devdb.xda-developers.com/
https://devdb.xda-developers.com/2/8/9/9/3/nookos_hummingbird_2_2_1.zip
https://devdb.xda-developers.com/2/8/9/9/3/nookos_ovation_2_2_1.zip

Hi,
Thanks a ton for this download.
I had an old Nook HD and installed nookos_hummingbird_2_2_1.zip on it. It works well, except for being able to sign into google - it keeps saying "couldn't sign in".
Any leads on how to overcome this?

rustycasty said:
Hi,
Thanks a ton for this download.
I had an old Nook HD and installed nookos_hummingbird_2_2_1.zip on it. It works well, except for being able to sign into google - it keeps saying "couldn't sign in".
Any leads on how to overcome this?
Click to expand...
Click to collapse
Google has changed the way the connection to the login server is established. There's nothing you can do about it.
Unable to sign in on Android v4.0.4 ICS - Android Community