Hello XDA,
Up until last week, I was happily using my Transformer Prime tablet with CM9 Release Candidate 2 and AOKP Milestone 6. Then my Galaxy Nexus came in the mail and I fell in love with JellyBean and I wanted it immediately. I downloaded the latest CM10 Nightly. I started downloading every time GooManager told me there was an available update.
So I kept updating until one day GooManager helped me download a version of the CM9 NIGHTLY instead of the CM10. My tablet was then stuck in the boot animation until the battery died. I wiped and then tried to re-flash the rom hoping I won't be stuck but I was stuck again. I don't know how to add any files to my tablet since the only time it functions is when I'm in TWRP and I can't get past the boot animation. I can't update my TWRP because I don't know how, so I don't have external SD card support either. I had ONE recovery image from when I made the switch from CM9 to AOKP but it seems like I deleted it so I have no idea what to do.
Is it bricked? Can I fix it? I'm not getting error messages.
Related
Woke up this morning, unplugged my touchpad, and turned it on. And it's stuck in a bootloop. I've been using it daily since release and updated to the latest alpha at its release.
It's stuck on the cm7 boot animation.
I've rebooted it multiple times. No luck.
Swifted from my Atrix.
Have the same problem right now again, last time I got this I had to reinstall the system and it was so frustrating....
I'm on the same situation today for no reason ..It was working fine for over a month. Any way to solve this without reinstall ... I know alpha 3 is out so just want to update... if I'm on webos how can I get to "sd card" folder to put alpha 3 file for upgrade ?
Never mind, fixed it... transfer alpha 3 file in to root of touchpad from webos and reboot to cwm , wiped cache and dalvik cache, install zip file from sd card ..choose the latest alpha 3 zip file .. then install and reboot.. that took care of cm7 endless bootloop and got alpha 3 installed as well....
Mentioning you have a bootloop and not giving the output of logcat helps no one.
Total wipe/reinstalled to fix it, right before alpha3 got released, kinda pissed at the timing.
Swifted from my Atrix.
Been running CM 7.1 since it came out with no major issues.
Came in from outside today to find my phone stuck on the cyanogen boot logo.
Restarted phone\pulled battery and same deal. I used the phone fine before going outside and came back to find it like so.
Any ideas??? Am I going to have to wipe this thing? Can't boot into Recovery now using 3 finger either.
So is ODIN in my future or do I have another option?
Are you running the nightly or the RC? The newer nightly builds had working three finger boot into recovery working. If not, you may be able to use adb to boot into recovery.
Sent from my SCH-I500 using XDA App
Will try ADB and then move up to the nightly. Was on RC and I believe I could 3 finger prior.
Hi, I just installed this ROM [ROM][DEV][CM10][Port][Linaro] SGT7 Jelly Bean Rom 0.1 on m Nook Tablet 16gb.
Everything works great, except videos in Netflix won't play. It does have the 3.0 kernel. Anyone have any suggestions on how to make this work? Thanks.
asolo157 said:
Hi, I just installed this ROM [ROM][DEV][CM10][Port][Linaro] SGT7 Jelly Bean Rom 0.1 on m Nook Tablet 16gb.
Everything works great, except videos in Netflix won't play. It does have the 3.0 kernel. Anyone have any suggestions on how to make this work? Thanks.
Click to expand...
Click to collapse
That is one of the known issues. No fix at this time.
Sent from my Nook Tablet using xda premium
I loaded the o.2 updated version. Random reboot to black screen in about 5 minutes then went to a B&N screen where it was loading new software, but failed. Endless reboots to the same. I flashed over stock unrooted 1.4.2
If I restore a nandroid backup the NT boot to the restored version from CWM and thereafter back to the trying to installing new software
Did you wipe data/cache/factory reset in CWM? My Nook is truely broken (can't even load an sdcard; I think bootloader is broken)
Oh and BTW, random reboots are kernel related.
Before you go back to stock, please flash stock recovery.
It is stock recovery. Even the B&N Tom wouldn't boot. It did without the SD card installed. I moved all the zip files off the root directory and now it boots regardless of ROM.
I'm safely back to CM7 April 24th build. It has been flawless. Wifi comes back after sleep and everything I use is stable.
CWM on a SD saved may Bacon many times. I assume you have one. If that won't boot I don't know what to suggest. Is it broken enough to get a warranty replacement?
Bill
NookTabletsPower said:
Did you wipe data/cache/factory reset in CWM? My Nook is truely broken (can't even load an sdcard; I think bootloader is broken)
Oh and BTW, random reboots are kernel related.
Before you go back to stock, please flash stock recovery.
Click to expand...
Click to collapse
Whatever you do to your bootloader you always be able to boot from ext-sdcard.
So try another one and have ready a bootloader img to flash back to yours
Major problems with [ROM][DEV][CM10][Linaro] SGT7 Jelly Bean Rom 0.1
Hi, I was able to root my Nook and go into recovery by formatting the SD card to do it using these directions here http://forum.xda-developers.com/showthread.php?t=1466583. I then installed SGT7 Jelly Bean Rom 0.1. The issue is that Recovery doesn't work in this ROM, and internal storage doesn't mount. So, I really want to upgrade to SGT7 Jelly Bean Rom 0.3, which will hopefully resolve these issues that I'm having*The issue is that there is only 62MB left on the SD card after I format it to be a Recovery card, even though its a 16gb card. So, I can't put the SGT7 Jelly Bean Rom 0.3 zip on the card. I can't flash from the internal drive, even though the zip file is on there, because it won't mount.
So, I'm really, really stuck with a Nook that halfway works. I have banged my head against this for hours and I have made no progress. Someone please point me in the right direction here. Thanks so much.
SGT7 Install
Downloading all necessary files to try SGT7. Anyone get it working and have some feedback? I hear it is the best CM10 mod right now.
SGT7 Install
I installed it a few days ago and it is working fine for me for the most part. It does go to black screen on occasion but it seems to be when I leave the WIFI on. Also, since I do use it primarily as a reader with Moon+ Reader I have noticed that the CM10 is not as smooth as CM7 when doing page turns for instance. There seems to be more stuttering with this version than the nice, smooth flow of CM7.
I like the look and extras that come with Jelly Bean though so will continue to use it for now and wait on update and keep trying.
I had android 4.4 Omnirom on my phone earlier today and yesterday. Today there was an update for the nightly. I decided to download it and updated through the recovery as a normal update would've. However, after waiting for almost an hour for the android is upgrading prompt to go away, I figured it was stuck in a boot loop. Well it turns out it more than likely was so don't say I'm impatient :d. So I forced it to shut down and it rebooted, but it didn't get past the Omni logo for almost an hour as well. So I decided to downgrade to the previous nightly. That didn't fix anything. After that, I tried to restore to cm 10.2 but it wouldn't let me for some reason. So I figured I was screwed. I downloaded Odin and attempted to restore to the stock rom. Well, Odin failed. So I was literally desperate and out of nowhere decided to try to downgrade the kernel. I attempted a downgrade to AJK 4.9 mic swap and it worked. So I installed MIUI after that (I'm too lazy to try adb) and it loaded up fine. I was so happy that at least something worked. After that I noticed the back and search buttons were not functioning. I decided to restore to cm 10.2 and it worked. Everything SEEMS fine but I'm not too sure if everything is. Can anyone tell me if my process is correct? Or if I messed up everything
Thanks!
I had to wipe the caches after i flashed the nightly to get it to boot.
The CM nightlies didnt work for me either. Something about the build.prop in Omni calling my phone both the ATT and ST version of the phone. I did what you did. Flashed AJ 4.7 i had, rebooted the Recovery, and Nandroid restored.
I liked Omni and ill be back but that battery life right now Ugh. Good luck Entropy and Co!
Hello first of all I would like to thank all the great developers for the great ROMs out there.
Second I would like to warn everyone that this is a "first world problem rant" that I'm about to write up with a legit frustration I have.
I have a rooted Samsung Galaxy S4 from ATT and the only reason I got this phone over any other Android phone is the great camera and the screen.
I absolutely hate TouchWiz. It's bloated, slow and painfully ugly (to me). For this reason I decided to try out Flashing roms.
For the last couple of weeks (months maybe?) I have been using Cyanogenmod 10.1 stable with not many problems. Mostly camera issues but no biggie.
My frustration is the following: CyanogenMod has had two stable updates for my phone to go from 10.1 to 10.2 and, though it flashes perfectly, every time I reboot the phone the phone gets stuck on the "Samsung Custom (lock)" screen and I am forced to go into TWRP and reflash 10.1+Gapp from my SD carfd.. This happens EVERY TIME. With CM10.1 I can restart the phone just fine by the way. It's 10.2 and other Roms that make get stuck on the Samsung Custom (lock) screen.
So i decided to try out Gummy ROM because Kit Kat
I put the ROM in my SD card, Formated, Wiped and Installed. Worked like a charm until the camera wasnt working that well. I read the forums and said to restart to fix the camera.. Guess what?...AGAIN....Stuck on Samsung Custom (lock) screen.
My frustrations is that pretty much EVERY Rom that I have tried minus CM10.1 has done this to me and I have no idea what I'm doing wrong.
I have tried battery pulls, waiting 30 seconds, wiped dalvik, cache, etc. Fixed Permissions....everything and I have to reflash the ROMs almost 99% of the time unless I use CM10.1. I am tired of reading forums to fix this so here I am asking for your help.
NOTE: Most, if not all of these ROMs are designed for ATT.
/endrant
I have no idea what else to do so any help would be great.
INFO:
Current ROM: Gummy 1.1-11-21-13-UNOFFICIAL
Android 4.4
Baseband version
I3377UCUAMDL
Kernel Version
3.4 g0-Elite-Kernel-ga719cb
Build Number:
KRT16S
Google Apps:
Gapps-Kk-20131113.Zip
TWRP Version
I have no idea and I'm not about to restart phone and go through the pain of reflashing the ROM again as I just did. I will punch so many babies if I have to do this again!'
Thanks for listening.
I had the same problem and switched to Philz Touch instead of TWRP, I like TWRP a lot more and most people say its more stable, but that's what fixed it for me.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Umm... Don't reboot
Sent from my SCH-I545 using xda app-developers app
I have read, on CM's site somewhere I believe, they recommend using CWM for a recovery. I use 6.0.4.4 and have no issues with getting stuck at the boot logo. There was an issue with that but CM addressed it in one of the nightlies about two weeks ago.
I had that issue when I had a newer twrp recovery I have the .2 whatever one and I havnt had it since.