I just rooted my Nook Tablet.
After rooting it I made the mistake of installing cm10.1.2 without wiping first. My first issue was that it stuck on the cm loading gif. I figured out I could get into recovery by holding the power and home button and do a factory reset which let me boot up fully, but it had a weird screen glitch right before the cm loading gif.
So, now I have all my problems. I want to make whatever I did clean so I don't have any issues come up in the future. First of all I can't get Google Apps set up. None of the APKs work for it. To counter this I tried to get Rom Manager installed directly from the CW website but within Rom Manager it tells me I need the latest version in order to download any roms.
To make things worse I cannot seem to get into recovery mode. Every time I try to boot into recovery mode I get the screen that says I need to reboot my tablet and if the problem persists I need to contact B&N support.
What I'd like to do is somehow get ROM Manager working and install a fresh version of CM with a data/cache wipe and then I feel like it would work but if anybody knows a better way to do it or what please let me know.
See http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123 for pointers on how to flash CM10 internally on emmc.
If you prefer to stick with pure CM10.1.2, just use its ROM zip file in step 2(c) but in which case you'll also need to flash CWM recovery separately (e.g., flashing flashable_CWM_6.0.2.x.zip from http://goo.im/devs/succulent/acclaim/recovery).
Thanks for the link. I followed his steps as close as i could and everything seems to be working flawlessly.
Related
Recently decided to try and switch over to CM10, and have been having an issue with recovery. Both of the latest CWM and TWRP recoveries freeze for me after booting into them. The only recovery that works for me is the one that is flashed with the old app by Indirect but that flashes a really old CWM recovery. The recoveries that I have tried flashing are the ones linked to in the http://forum.xda-developers.com/showthread.php?t=1877217 thread. Both http://celticstorage.co.uk/cm10/CWM_v6.0.1.5_emmc.zip and http://celticstorage.co.uk/cm10/TWRP_v2.3.1.1_emmc.zip are doing it. I have a 16GB that ive kept (rooted) stock forever.
What happens is i go to boot to recovery, go through cyanoboot to recovery, and then CWM freezes up and blackscreens after I try to wipe something or install a zip, TWRP just locks up immediately and gives me a black screen. Any help fixing this would be greatly appreciated.
Use this thread to install CWM, I'm not a fan of TWRP. http://forum.xda-developers.com/showthread.php?p=25786947 I used this and had no problems updating
Sent from my NOOK Tablet running CM10
deltantor said:
Recently decided to try and switch over to CM10, and have been having an issue with recovery. Both of the latest CWM and TWRP recoveries freeze for me after booting into them. The only recovery that works for me is the one that is flashed with the old app by Indirect but that flashes a really old CWM recovery. The recoveries that I have tried flashing are the ones linked to in the http://forum.xda-developers.com/showthread.php?t=1877217 thread. Both http://celticstorage.co.uk/cm10/CWM_v6.0.1.5_emmc.zip and http://celticstorage.co.uk/cm10/TWRP_v2.3.1.1_emmc.zip are doing it. I have a 16GB that ive kept (rooted) stock forever.
What happens is i go to boot to recovery, go through cyanoboot to recovery, and then CWM freezes up and blackscreens after I try to wipe something or install a zip, TWRP just locks up immediately and gives me a black screen. Any help fixing this would be greatly appreciated.
Click to expand...
Click to collapse
This has been happening to me occasionally. I have found that when I get the black screen, pressing the Power button launches Recovery (CWM in my case). See if that works for you.
I now have the exact same problem. I've always ran off emmc. It says cwm 6.0.1.5 is installed. When I try to either wipe, or install zip-from-sd, cwm freezes then goes to the black screen. I cannot install any zips, so right now the tablet has nothing installed only a freezing cwm recovery it seems. I can use the power button to get out of the black screen and into cwm thru cyanoboot all day, but get nothing but these same steps reoccurring. Freeze, then black sod. I'm ready to try anything but cannot flash anything.
To the rescue
Ok, I have posted this on a different day. Try this with a blank sd card. Look at the bottom post called "Here is a video"
It a external boot cwm v.5 but you can copy this into your sd then flash and you have cwm v6.0.1.5 internal. Either way you have two ways to do recovery (external and internal):victory:
djd338 said:
I now have the exact same problem. I've always ran off emmc. It says cwm 6.0.1.5 is installed. When I try to either wipe, or install zip-from-sd, cwm freezes then goes to the black screen. I cannot install any zips, so right now the tablet has nothing installed only a freezing cwm recovery it seems. I can use the power button to get out of the black screen and into cwm thru cyanoboot all day, but get nothing but these same steps reoccurring. Freeze, then black sod. I'm ready to try anything but cannot flash anything.
Click to expand...
Click to collapse
Thanks very much for the reply & link!
I'll do this ASAP when I get back home & report. Thx again!
Sent from my Nexus 7 using Tapatalk 2
Well, I think I need to clarify more. Maybe somebody can help if I give more info. I've had cm7 running perfect, then decided to install cm10. I first flashed a cwm 6.0.1.5 zip to emmc. I did a factory reset via this recovery thinking my next move would be to flash the cm10 zip I'd put on the sd. No joy. This is where I'm at now.
In recovery it freezes and reboots to the "2 androids" screen with a sod. I hold power for 20 sec.s to turn off, then turn back on and get to cyanoboot fine. There, if it's allowed to just boot it freezes at the 2 androids. If I hold "n" to get the menu and recovery (6.0.1.5) it looks normal, will boot to recovery OK until anything is selected like the cm10 zip. It freezes before any selections can be finalized, and boots to that sod screen.
I know nothing of ubuntu! Sorta scared to go there with my limited knowledge. But will read up if it's required. Is it possible that this new recovery image don't play with what is currently on the sd? Is there anything I can put there that it may recognize in order to get a flash? Man, I'm lost!
Look pass the fear and go one step at a time, before you know it, your there.
It looks like you have already resolved this from this thread.
Ok, basically I'll go step by step.
1. Download ubuntu iso from ubuntu website (you can donate or put 0$ then download iso) and burn it to cd. 5 minutes
2. Stick the cd into a system that you don't plan to look at the video that is showing you the process and boot it up from a reboot and not from within windows. Select the left square which basically load the ubunbu from cd but does not install anything to your hard drive.3 minutes
3. You can view the whole video but I would skip to the section in video (3:28 watch to 4:43, 6:56 watch to 8:06 ) where I mentioned the setting the two flags in your sd after quick format fat32 and extracting the four files into your sd within ms windows platform from the post . I did this with a normal mini sd card adapter and not the usb stick adapter he used in the video. Since you are doing this to a blank mini sd then there really nothing to worry about since it is blank in the first place. 2 minute
4. If you had your apps backup with titanium backup then it still will be on the main mini sd and not the one that working with for this recovery.
5. I notice you did not mention wipe dalvik cache from your post. You should always wipe dalvik then wipe factory then do a single flash to test boot up.. You can flash gapps after a successful boot up into jellybean. (here's a video showing that I'm using external cwm v.5 even though its recommended to use v.6 .) You can always use cwm v.6 on your next cm10 test rom or use cwm v.6 to reflash to same rom once a successful boot up have been obtained with external cwm v.5. This purpose is to get it running on your nt.
6. Be patient for the first boot. Should not be more than 5 minutes max. It will look black then load. If it boot loops then wipe dalvik then wipe factory and do a single flash to test boot up again.
This will at least get cm 10 flavored rom on to your nt.
djd338 said:
Well, I think I need to clarify more. Maybe somebody can help if I give more info. I've had cm7 running perfect, then decided to install cm10. I first flashed a cwm 6.0.1.5 zip to emmc. I did a factory reset via this recovery thinking my next move would be to flash the cm10 zip I'd put on the sd. No joy. This is where I'm at now.
In recovery it freezes and reboots to the "2 androids" screen with a sod. I hold power for 20 sec.s to turn off, then turn back on and get to cyanoboot fine. There, if it's allowed to just boot it freezes at the 2 androids. If I hold "n" to get the menu and recovery (6.0.1.5) it looks normal, will boot to recovery OK until anything is selected like the cm10 zip. It freezes before any selections can be finalized, and boots to that sod screen.
I know nothing of ubuntu! Sorta scared to go there with my limited knowledge. But will read up if it's required. Is it possible that this new recovery image don't play with what is currently on the sd? Is there anything I can put there that it may recognize in order to get a flash? Man, I'm lost!
Click to expand...
Click to collapse
Got it back! Thank you for your help & patience. Also for the timely responses. I now have a bootable "recovery sd card" for curing these type problems. I've labeled it & filed away for any future borks of this kind! And I have cm10 up & running stable.
Thank you!
Sent from my Nexus 7 using Tapatalk 2
Hi,
I have a rooted (using Indirect's method, I believe, with help from Albert W.'s video) Nook Tablet 16GB. I'd like to try a custom ROM and installed GooManger (1.2.1). I can download a recovery file (openrecovery-twrp-2.3.1.1 -blaze.img), and it says it installed it, but when I try to boot into recovery ("Reboot recovery" option) it just reboots normally. If I try to browse compatible ROMs, it says "No roms were found".
Googled but could not find an answer. I would appreciate if someone could point me in the right direction!
Thanks,
Pat
miapjp said:
Hi,
I have a rooted (using Indirect's method, I believe, with help from Albert W.'s video) Nook Tablet 16GB. I'd like to try a custom ROM and installed GooManger (1.2.1). I can download a recovery file (openrecovery-twrp-2.3.1.1 -blaze.img), and it says it installed it, but when I try to boot into recovery ("Reboot recovery" option) it just reboots normally. If I try to browse compatible ROMs, it says "No roms were found".
Googled but could not find an answer. I would appreciate if someone could point me in the right direction!
Thanks,
Pat
Click to expand...
Click to collapse
I think you're trying to use the wrong recovery file. Try downloading CWM or TWRP from the links listed in the first post of this thread -- I've used both with no problems on my NT.
Saludos,
Steve
Removing CM9
HELP! I installed CM9 on my nook tablet 8gb and I am not happy with it. I want to take it back to stock so I can load CM7. HOWEVER I cannot find a single website with this information. I keep trying to power it off and then hold the power and n to no avail. The cyanoboot menu just loads and I cant load any of the ROMs. Its really pissing me off and I would like to just get rid of this os. Can anyone help?
Mauler85 said:
HELP! I installed CM9 on my nook tablet 8gb and I am not happy with it. I want to take it back to stock so I can load CM7. HOWEVER I cannot find a single website with this information. I keep trying to power it off and then hold the power and n to no avail. The cyanoboot menu just loads and I cant load any of the ROMs. Its really pissing me off and I would like to just get rid of this os. Can anyone help?
Click to expand...
Click to collapse
You don't need to go back to stock to downgrade from CM9 to CM7. All you need to do is boot into recovery and flash the new ROM. With that being said, it would be well worth your time to start by installing Titanium Backup and backing up your system before you do anything else... That will let you restore any apps you've downloaded and want to keep (along with their settings and data), which will eliminate one headache after you flash the new ROM...
Review this thread from Lavero.Burgos about installing a customer recovery on your tablet. You've already got one installed if you're running CM9, but the thread has got lots of really good info, and if you have the Clockwork Mod 6.x recovery installed, you need to replace that with Clockwork Mod 5.x to flash CM7.
Next, check this thread from Celtic Web Solutions. The link to the internal CM7 ROM is in the first thread, along with the instructions for installing this ROM to your emmc (internal) storage.
Now, when you start you tablet, instead of holding Power + n to boot into recovery, wait for the Cyanoboot splash screen to open (the one that says CYANOBOOT, not the animated CM9 splash screen), then press and hold the n button until the boot menu appears. From here you can select to boot normally into CM9, into your internal recovery, or into a recovery.img loaded on your SD card. Select one of the recovery options, and you should be able to do a nandroid backup of your device, then install CM7. Since you're changing to a completely new ROM, I strongly recommend that you do a factory wipe/reset as well as wiping the cache partition and Dalvik cache.
NOTE: There's a big difference between an Titanium Backup backup and a Nandroid backup! You'll want to do both as you go through this. Titanium Backup will take a snapshot of your apps (including the settings and data associated with them) that you can restore after installing the new ROM. Super helpful, since you don't have to re-install everything from the Play Store, nor do you lose data like savegames, etc. Nandroid runs from recovery mode, and will do a complete image of your system, including the ROM. It protects you in case you run into a major problem while flashing a new ROM -- it's saved my life a couple of times...
I have Samsung Vibrant T959. Currently has clockworkmod 6.0.3.6 .
I'm trying to install the latest unofficial cyanogenmod 11, which will install kitkat 4.4.4, however I run into the error message "set_metadata_recursive: some changes failed" . According to my research all I need to do to solve it is update clockworkmod to a version of at least 6.0.4.5 .
I've searched all over, most sources point towards using rom manager, but this is not working. Rom manager seems to think the latest version is 2.5.1.2. The official clockworkmod site also lists 2.5.1.2 as the latest version for my phone.
So how do I upgrade this clockworkmod so that I can install kitkat? I know others have done it, but I can't find any info how.
Thanks.
I just installed Sada's 4.4.4 today (coming from the official CM 11 [4.4.2]) and what I did was go into CWM and install the rom (which will fail). During the process it will install CWM 6.0.4.9. Reboot. Now you will have 6.0.4.9.
FYI - I had to reformat the internal SD card to get the 4.4.4 install to stick. (factory reset and clearing caches wasn't enough and would throw errors on first boot)
-Mike
Thanks for the advice. Thats the exact thing I was doing. Coming from latest official Cyanogenmod, to the latest unofficial.
So I did exactly what you said, tried to install, it failed, rebooted straight from recovery back into recovery, and I indeed had clockworkmod 6.0.4.9.
So I did the install again, it worked, installed the minimal gapps, but I did not format the SD card. I figured I would try without it first.
Well upon booting I couldn't get past the first screen of the setup wizard, it would just crash. Had a very difficult time getting back into recovery mode, as the typical 3 button combo wouldnt work, but finally figured out a way by sheer luck and experimentation (hold volume down, and power, and plug in a usb cord. Keep the buttons held for about 30 seconds, then release the power button while still holding volume down, after 10 seconds it would go to recovery)
So I did the format of the internal SD card as well, but no luck, the wizard still crashes. Ended up just restoring my old nandroid. I wonder if there was anything else you did different than me. Perhaps different Gapps?
Hi everyone
My sister updated her MEGA OTA last month. She cant remember which version she was on. I am assuming it was 4.3. shes doesnt know much,
Her phone got stuck in bootloop.
Initially a got a hard time even getting into restore mode. however after a lot of goggling and trials and errors here is where i am today :
1- I can install TWRP and/or Philz recovery and boot into them.
2- I can enter download mode
3- I have tried installing many ROMS and different versions. I was only partially successful with 4.4 versions because I get a passed message in Odin however upon restart the phone enters boot loop again.
4- I have tried multiple wipe data/dalvik cache/cache and restoring factory settings but i still get the same results.
5- Only in Philz recovery i can mount the external SD card and copy zip files. I was able to root the phone that was (but im not sure if it still is). However all ROMs zip files I tried to install (both from PC and from extSD card) wouldnt open in recovery mode.
Because I get a passed message when I install a ROM from Odin , I dont know what the issue could be. But there is something wrong that happens as soon as this phone boots up.
I seriously do not know what to do anymore. I just need this phone to be working again. At this point I dont care about warranties/ROM versions/stock or custom...
Please help and sorry for my bad English
It sounds like you need to download the stock rom and flash it in Odin (you gotta put the phone in download mode to flash in Odin). The stock rom can be found on the sammobile website in the firmware section. That should get you back to square one (stock rom, stock recovery, no root). Then you start over from scratch.
Sent from my SGH-M819N using XDA Free mobile app
Thanks
I did and I still get the same problem.
In fact after installing stock rom, i could not enter "stock" so I installed philz recovery, logged in philz and wiped cache a couple of time, did a factory reset.
and yet when i restart , the phone is stuck in bootloop.
Maybe she has a Galaxy Mega with a repaired screen. Starting with 4.4 Samsung only supports a digitizer with Synaptics brand chip. It's a big mess and there are countless screens and digitizers made worthless. I think unofficial 4.4 by Cyanogen and others might work, but not official Samsung. With some Galaxy Megas you get a bootloop. With others it boots however the digitizer and touch functions no longer work. I don't know how to go back after you are on official 4.4 because last I saw, there was no root for it. If I'm wrong, someone else please clarify and continue to help.
IMHO only one way out from such situation is try to flash MegaFire MJ2 which is derived from stock 4.2. It's only one 4.2 ROM which can be safely flashed onto KK.
Iformation about MegaFire you can find HERE
Hello, i will try to be thorough.
BUT, i am a noob and didnt write down everything i did.
Have a I717 at&t note 1. with the 4.1.2 update originally OTA installed by keis.
I recently rooted it using Saferoot. it went well and i didnt see any problems. i flashed a custom rom and didnt like it so using clockworkmod recovery i went back to the 4.1.2. I then tried pac lollipop >pac_quicyatt_lp.beta-1.unofficial_20150327< i liked this rom but needed to flash Gapps.
This is where the trouble started. i didnt/dont know the proper procedure to flash the Gapps on top of or into the rom.
I first tried >gapps-5.0.x-20150404-minimal-edition-signed.zip< and it looked like it loaded correctly. but nothing appeared in the phone. the pac rom was still working well.
I then did more research and tried >gapps-lp-20150222-signed.zip< , again it looked like it loaded well but nothing showed up "in" the phone.
right here is where things got screwy. i had been using clorkworkmod for recovery and rebooting. and i think somewhere in developer settings i clicked something about how rebooting is handled.
because after trying to install the Gapps it went into Cyanogen recovery... and loops.
no matter what i do it goes back to cyanogen recovery.
I never knowingly installed cyanogen and dont know why it all of a sudden is going into cyanogen recovery over and over.
a list of things that may have bearing:
1. i tried reinstalling the pac rom. it loads and completes but it still just goes to recovery.
2. tried different ways of clearing cache and data wipes.
3. computer, kies, and odin 3.09 do not recognize phone.
4. have proper drivers on computer. phone was previously recognized by kies and cpu (4.1.2).
5. currently the only way to get anything into phone is by pulling sd card and reinstalling with info on it then using cyanogen recovery.
6. i have searched for about 11 hours and tried a bunch of things. but just restarts in cyanogen recovery
7. i was scared to fully try things i found that wernt specifically for the i717.
8. i could not find an original gingerbread rom. they all seemed fishy (needed downloaders. or ended in .zip.rar)
9. had backed up with clockworkmod and with titanium recovery (while in 4.1.2).
I dont know if i can reach the clockworkmod save through cyanogen recovery.... if so it seems like a great option.
10. at the bottom of the screen while loading rom is.... ---->>> E: cannot load volume /misc
11. only pac rom will successfully re-flash (even though it still just goes back to cyanogen). any other flash and it crashes halfway through.... i then restart and it just loops back to cyanogen recovery.
I searched here and tried the five recommended posts.
I could not try a lot of the "fixes" because the phone isnt recognized by cpu or odin (computer does beep when connected but doesnt show up anywhere).
Can you help me get back my phone please?
Randall
added
This is the only site i am asking for help on. I am willing to reply quickly and put in the time!
Thank you very much for reading this far.
Randall