Related
I have had a Bad ESN Fascinate for a while that I was playing around with, trying to get it to work on Sprint... No go. Anyway, it was rooted with a stock GB ROM and I decided I wanted to try out some of the ICS or Jellybean offerings that XDA has in its forums.
To be honest, I am no noob, but I didn't do enough research to begin with. First I installed GeeWiz 2.9 Kernel, System, and 2.8 Recovery. I didn't like the 2.8 Recovery, so I tried to flash something else, but nothing would replace it. Then I tried to install Baked CM10 from the GeeWiz recovery, and it went downhill from there.
Long story short, I have ODIN'd back to stock EH03 and tried to update to a couple of CM10 ROMs using the guides I have found here and on a few other forums. I have a working install of Hacksungs CM9 build 5 as of right now, but I can't get any further.
After using ODIN to get to Stock EH03, I ODIN the CWM4 for CM7. 3-fingering brings me to CWM4 where I begin the install of CM9. When it examines the partition BML/MTD it reboots the recovery (took me a while to figure that out) in to CWM 5.5.0.4 where it finishes the CM9 install. When I soft reboot into recovery, I get CWM 5.5.0.4. According to the guides, this is where I would flash CM10. It runs the update, but when I go to reboot the system, it reboots into a recovery of CWM 6.0.1.4. Also, if I reboot the system from CWM5 without installing anything, it boots back into CM9 just fine.
I am pretty sure I installed CWM 6.0.1.4 sometime in the past, but to be honest I have no recollection of when.
My question is multi-part: How do I get rid of CWM6; why is it still there after all the repartitioning with ODIN (with and without PIT file), MTD partition formatting, etc; why can't I get CM10 to install?
While this is a fairly wordy post, I have to say, I do have a working Fascinate with CM9 that I am enjoying playing with. I just thought if nothing else, people might get a laugh out of my struggles with this phone, that is basically a web browser and toy.
FWIW I have seriously ODIN'd back to stock about 5 or 6 times today alone.
Thanks for any help or suggestions in advance.
Unlike Gingerbread and earlier, with ICS and JB kernels they include whatever version of recovery the developer wants to include.
Is there a reason you don't want the latest CWM?
Sent from my SCH-I500 using xda app-developers app
Its been awhile for me since I had to go back to stock, but unless something has changed the three finger reboot into cwm caused some problems when flashing. Try rebooting to recovery through power menu.
Some ROMs are requiring to be installed a second time to "stick" due to partition layout changes.
Sent from my SCH-I500 using xda app-developers app
Thanks for the info on the ICS and JB attached recoveries. I was unaware of that. Maybe that's where the CWM6 came from.
And it isn't that I don't want to most current, it just didn't seem to want to play nice with the ICS and JB Roms I was trying to installed.
Now my problem is that the phone won't boot when powered down from ICS. Glad this isn't my main phone.
Sent from my EVO using xda app-developers app
That's what I had read everywhere... NEVER 3-Finger into Recovery from ICS or JB. I still managed to do it a few l times when I wasn't thinking.
It definitely screws up the install. I can attest to that.
I just don't get why there are all three CWM versions present during the install, and if I am installing CWM4 fixed for CM7, and one of the other two is included with the ICS Rom, where did the 3rd one come from? Just a big, confusing mess
Sent from my EVO using xda app-developers app
From my limited knowledge,,,
I know the fixed cwm is what you need to get out of a 3 finger boot loop,,, I've had to do that...
Cwm 6 is what runs and works with cm10/jb roms,,,
Causes no errors that I'm aware of...
No more 3 finger,, always use power button/reboot
Once you have started an install of say cm10 ... Let it run its course , so to speak,,, if it comes up with cwm5 or cwm6 then that is the one the developer designed it to work with,,,
Let it come all the way up,, and then reboot through the power button method always,,,, you'll get used to that quick enough , as i remember the old gb froyo stuff didn't offer this method
I keep a copy of the fixed cwm just in case i happen to accidentally 3 finger ever again...
Sent from my swagger
spikeekips said:
That's what I had read everywhere... NEVER 3-Finger into Recovery from ICS or JB. I still managed to do it a few l times when I wasn't thinking.
It definitely screws up the install. I can attest to that.
I just don't get why there are all three CWM versions present during the install, and if I am installing CWM4 fixed for CM7, and one of the other two is included with the ICS Rom, where did the 3rd one come from? Just a big, confusing mess
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Not sure if you are still looking for advice but here is a little guide that has not failed me at all. If you follow this then you should come to the latest JB rom that you want.
Click here
First of all, I want to thank everyone working on the CM7, CM9, CM10, SGT7, TWRP, CWM projects for the Nook Tablet. I've really been enjoying trying different ROMs on my Nook Tablet.
I started with CM7, and it ran pretty well. I also tried the CM9 (NX-Fire?) port, and I liked it as well.
I have been using the SGT7+CM10+Cherry Picks and it has been fine up to the 27/9 release. I cannot run anything higher than this on my NT.
I have tried CWM (up to 6.0.1.2) and TWRP (up to 2.2.2.0) to flash the newer ROMS, but the ROMS will not boot. The screen blanks, and after a time, it goes back to the boot screen.
I also can't seem to use the CWM 6.0.1.5 or TWRP 2.3.1.1 from the SGT7+CM10 thread.
I know I have the 16GB Nook Tablet. I have repartitioned the userspace, as mentioned in other threads. I can't help but feel like I'm missing a step somewhere.
Presently, my NT is running TWRP 2.2.20 and SGT7+CM10+Cherry Picks 27/9. Any one have any hints? A thread on the boards I have missed? Any help would be appreciated.
Again, thanks for all the hard work!!
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Moved. Questions belong in the Q&A section.
Thanks
AvRS
demetris_I said:
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Click to expand...
Click to collapse
Thanks! I'll try that this weekend. I knew I was missing something.
demetris_I said:
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Click to expand...
Click to collapse
Sorry, but how does one manually update a recovery? I've tried flashing the newer TWRP from CWM as well (from an older version of CWM), and while the flash doesn't fail, it won't let me boot into TWRP, and the new CWM crashes before I can do anything. I've also tried flashing the recovery from fastboot, but I get a "bad boot magic" error when I try to boot.
Just flashed couple of days ago: pretty nice ROM
Besides annoying "SD card unmounting" problem I found that B&N Nook app does not work, it just keeps restarting, some error message shows up but goes away so quickly I can't read it. I wiped before I installed the ROM and reinstalling the app didn't help.
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
jnorrisman said:
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
There is a search function on here...
Sent from my NOOK Tablet running CM10
jnorrisman said:
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
The OP in the developers section has links to both CWM and TWRP for your use. Remember, SEARCH is your FRIEND!
play store/goomanager closing
First let me say this rom is awesome! I had no idea my nook could run this smoothly. The only problem I seem to have is that on the newest build(10/25) both playstore and goo manager will open then close. I have tried clearing the app cache, re flashing rom and gapps, full wipes then reflash. I also tried reflashing the newest gapps without success. The 10/12 build works with both play store and goo manager. I am using the 10/12 build now so no worries if it can't be fixed. Again thanks for the time and effort on an awesome rom:good:
edit: I am using the latest twrp for my recovery (also awesome). the tablet is the 16gb version
Same problem as OP, latest SGT7 not loading
I am having the exact same problem as Byron and Spurious. I've really enjoyed this series of ROMs up until the last couple, which give the same symptoms as described in the OP - the ROMs will appear to load up to a certain point, then the device reboots. For me, the the device will load up to a seemingly random point -- sometimes it will reboot itself during the boot animation, and once it got all the way to the point where it starts updating the applications. But it never actually finishes booting up before it reboots itself.
In addition, the latest CWM and TWRP do not work for me. TWRP does not come up at all, and sometimes CWM will come up and I can move around the menus for a few seconds, then it hangs. It happens whether they were flashed via fastboot or SD, I've tried every combination. I can fastboot back to TWRP 2221 or CWM 6013 and they work fine.
I've been keeping my NT (16G) updated with the latest builds since early ICS and everything has worked as described up until now. I follow all instructions to the letter as regards to wiping, etc. so I don't think I'm doing anything wrong.
Is anybody else having the same issue with these latest ROMs? Byron, Spurious - did you get yours sorted? Could it be a hardware issue?
jarvz said:
I am having the exact same problem as Byron and Spurious. I've really enjoyed this series of ROMs up until the last couple, which give the same symptoms as described in the OP - the ROMs will appear to load up to a certain point, then the device reboots. For me, the the device will load up to a seemingly random point -- sometimes it will reboot itself during the boot animation, and once it got all the way to the point where it starts updating the applications. But it never actually finishes booting up before it reboots itself.
In addition, the latest CWM and TWRP do not work for me. TWRP does not come up at all, and sometimes CWM will come up and I can move around the menus for a few seconds, then it hangs. It happens whether they were flashed via fastboot or SD, I've tried every combination. I can fastboot back to TWRP 2221 or CWM 6013 and they work fine.
I've been keeping my NT (16G) updated with the latest builds since early ICS and everything has worked as described up until now. I follow all instructions to the letter as regards to wiping, etc. so I don't think I'm doing anything wrong.
Is anybody else having the same issue with these latest ROMs? Byron, Spurious - did you get yours sorted? Could it be a hardware issue?
Click to expand...
Click to collapse
Sort of. I figured out what I was doing wrong flashing the recovery from fastboot (you apparently have to extract the .img file from the zip) but was still having the exact same issues with CWM and TWRP as you. I've managed to get a newer version of CWM installed without it hanging by using the 5 touch enabled one from here. Using this I still have the same issues with the meghd00t rom going into a bootloop though.
I noticed OP said he has repartitioned his Nook, and I have as well. I wonder if this could be causing problems, have you done this as well, jarvz? Does anyone else have any input about if repartitioning could effect this?
spurious_access said:
Sort of. I figured out what I was doing wrong flashing the recovery from fastboot (you apparently have to extract the .img file from the zip) but was still having the exact same issues with CWM and TWRP as you. I've managed to get a newer version of CWM installed without it hanging by using the 5 touch enabled one from here. Using this I still have the same issues with the meghd00t rom going into a bootloop though.
I noticed OP said he has repartitioned his Nook, and I have as well. I wonder if this could be causing problems, have you done this as well, jarvz? Does anyone else have any input about if repartitioning could effect this?
Click to expand...
Click to collapse
Yes I have repartitioned mine as well, so that must be it. I was hesitant to go to the 5-touch because it was indicated in the thread that there was no way back after you do the firmware update, and so far there is only one rom that worked with the new firmware, so I didn't want to take a chance.
At least I'm pretty sure I'm not doing anything wrong, lol.
jarvz said:
I was hesitant to go to the 5-touch because it was indicated in the thread that there was no way back after you do the firmware update, and so far there is only one rom that worked with the new firmware, so I didn't want to take a chance.
At least I'm pretty sure I'm not doing anything wrong, lol.
Click to expand...
Click to collapse
Yeah, I don't have the new touch firmware installed either. CWM worked fine, though TWRP didn't seem to work properly (maybe it needs the new touch firmware?).
Do you know if there is any mention of re-partitioning causing an issue? I looked in the rom dev thread but didn't notice anything. I guess one of us who are seeing this issue could post there to see if anyone knows what could be causing this.
I finally got it to work. My PC is running Ubuntu, so YMMV.
Here is what I did:
1. Used "gparted" to create 2GB FAT32 partition that is bootable.
2. Used the instructions in the this thread thread to create a bootable SD disk that boots into CWM 6.0.1.2.
3. CWM 6.0.1.5 just doesn't seem to work on my Nook Tablet. So, I downloaded CWM 6.0.1.3 from here
4. I downloaded the latest ROM here
5. Downloaded the latest gapps: here
6. Copied the CWM, ROM, and gapps to the SD disk.
7. Inserted the SD and booted the Nook Tablet.
8. On first boot, it boots to CWM 6.0.1.2, so I flashed the CWM 6.0.1.3, and rebooted.
9. This time it boots to Cyanoboot, so I entered the boot menu and selected EMMC Recovery.
10. From CWM 6.0.1.3, I formatted /storage, and did a factory wipe. (I didn't format /storage the first time, and the wireless would not come up.)
11. Installed ROM from SD card.
12. Installed gapps from SD card.
13. Rebooted, this time letting cyanoboot boot from EMMC.
14. Profit!
I haven't tried 6.0.1.4 to see if that would work.
I am looking for some help bc of all the roms out there I am really confused. Ihad a droid X before this and flashed several roms without a problem. Here is when I get lost:
Right now I am back on stock I605VRAMC3.
I use adam outliers root method to get rooted with super user acess.
This gives me TWRP not CWM.
If I use TWRP to flash a rom I end up with a bricked phone.
I would like to use a CM11 4.4 rom or something similar. When I watch the video on galaxynote2root.com the user uses CWM and if I use that on my phone it turns into a brick even after rooting. What step am I missing? I see some roms are touchwiz based. I'm not familiar with what touchwiz is or how to install ot before flashing roms or if I even need it for CM11. Anyone on the same build as me that has flashed several roms I would greatly appreciate any info so I can start to enjoy some of these roms and decide which one I like. Thanks.
Sorry, I haven't done this stuff to know exactly where the issue is, but I will assume you're more likely to get the answer in the development section since it's all about themes, roms, rom flashing, rooting etc. If not there, then the trouble shooting section. Hope that helps. (assuming you're still looking)
You can flash Philz recovery in twrp & switch to it. Then you can flash CM11.
http://forum.xda-developers.com/showthread.php?t=2552655
You can use casual to root and unlock bootloader.... And then install cwm via rom manager apk... Hope this solves your concern
Sent from my SCH-I605 using XDA Premium 4 mobile app
How is TWRP bricking your phone? I rooted with Outler's method and have had no problems with TWRP. You've mentioned that CWM has bricked your phone too. If that's the case, how were able to flash anything at all? As for TouchWiz, it's not anything you install. There are two basic types of ROMS for the N2. TouchWiz based, which have more of the Samsung apps along with the ROM customizations, and AOSP (Android Open Source Project). AOSP is more like stock Android, but with custom features. CM11 is an AOSP ROM. Here are the steps I took when I initially rooted:
Installed Samsung drivers to my laptop
Made sure Java was up to date
D/L Outler's Casual
Put phone in USB Debugging Mode
Attached phone
Ran Casual
Rooted phone (at this point I believe I had to select between CWM or TWRP)
There you have it. If you missed any of these steps, that could be the problem. Another issue might be that you're trying to use TWRP and CWM simultaneously
I'm assuming you are not wiping(factory reset. I do it three times) prior to your install. If you're not then your trying to install a rom on top of a rom and bam...boot loop.
nikhil.kdhand said:
You can use casual to root and unlock bootloader.... And then install cwm via rom manager apk... Hope this solves your concern
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+1 for this... when i tried to flash CM11 using TWRP I ended up in a bootloop.. restored my backup, downloaded rom manager apk from google play and used that to install CWM... then in CWM did a backup, wipe everything, and flashed CM11 + gapps and everything works without a hitch
one more note... my CWM backup was hanging on generating the MD5 sum, so i changed the encryption method away from the default... takes up more space on the ext-sd, but it works.
Hello everyone.
As the title says I recently got my hands on a Samsung Vibrant. I have it from a friend who just left the apartment we lived in together for 5 months as she didn't need it anymore. It currently has a MIUI ROM on it and I'd like to change it to sada23's unofficial CM 11.0
The problem is however that my only previous experience with flashing ROM was with a Samsung Galaxy Chat when I slapped Jelly Bean on it which was only released in a few countries. So I went right ahead but found the amount of things I have to do overwhelming compared to when I just used ODIN on the old phone.
I'm trying to tell what the current status is of the phone and this is what I've been able to come up with so far. (also after googling what everything is and does lol)
- MIUI present so custom ROM install definitely possible
- When I booted into recovery mode I saw it has: "Semaphore CWM Recovery v6.0.1.9" (which I presume is outdated)
- BY default the MIUI ROM apparently has a superuser app (which lead me to think that the device is rooted), however everytime I try to use an app that requires root I encounter errors.
I just did a backup using the recovery mode with semaphore cause I saw this is usually a first step in all the guides I've read. However from here on out I am completely clueless on what to do because all the guides were so different from eachother and I have a feeling my phone is in a vague situation. (root/not rooted?)
So I was hoping someone here could point me into the right direction and help me get to CM from MIUI. Thank you in advance.
I'll be following this thread.. kinda in a similar situation. Although a bit worse. I had an old vibrant in a drawer from years back in mint condish!.. last thing I did was root and install recovery. Unfortunately I'm a stooge and without thinking threw a 4.4 rom zip on the phone.. booted to recovery and cleaned and tried to flash.. bottom line i'm in a bootloop now... and I gave up when odin wasn't detecting the phone.. I"ll figure that out eventually, but it would be great to just have a 4.4 Odin tar for a quick and painless install... or at least a tar from a 4.0 with root and recovery to make the 4.4 upgrade easy.
Also would be interested in knowing if the 4.4 roms work well.. Gps will be most important to me since I plan to use this as my jogging phone.
alrighty.. let's get this party started!
Edit - I think the best thing for you to do is odin back to stock then root install custom bootloader and then flash your new rom, I've heard that you can go straight to kk from stock but the guy who posted above me has problems because of that so I would try flashing an ICS ROM for the recovery first, and don't forget to make a nandroid backup
You can find all the files and programs you'll ever need here http://forum.xda-developers.com/showthread.php?t=1982728 in NOOB_IN_NEED 'S ref thread
Hope I was of some help if I was hit the thanks button
sent from the depths of paradise - Jamaica
using SGH-T959
ROM: unofficial CM11 4.4.4 by sada
Kernel: stock
$$ SOLVED $$
I am continuing my support request from here:
http://forum.xda-developers.com/showthread.php?p=56110069
I am new to the i9205 but very experienced and knowledgeable with Android.
My device was secondhand and came with 4.2.2.
First thing I did was flash philz via Odin. I ran root via twrp.
I instantly booted to TW and backed up my EFS via terminal
I then went to philz. I wiped everything. Flash slim rom and gapps.
Upon boot to system, it just sticks on bootloader screen.
However. When I flash AOSP, it works amazing on it now. But I want to flash other Roms aside from AOSP.
It appears most of the custom roms aside from AOSP don't work and get stuck on bootloader
So I tried to flash slim again then recovered just booting and it booted to just a black screen this time I know the rom booted though and it got past bootloader because I was hearing lockscreen sounds etc even though I had a black screen
I did try updating via pc Odin to 4.4.2 in attempt to see if bootloader update would help, to no avail.
It appears the older AOSP kernel works. But anything with a newer kernel doesn't
If anyone can help I will be forever indebted to you
Sent from my GT-I9205 using Tapatalk
Question for you and may seem random but was the screen replaced on this unit by the seller. There are some reports that the newer boot loader and or kernel had rendered certain KitKat ROMs innnc. Stock to present a black screen. However if it was me I would flash a stock Odin file pre KitKat if you can. The root via the original alda-v guidelines then flash philzs again from.
Then update to the latest philz recovery only file from his main thread.
thering1975 said:
Question for you and may seem random but was the screen replaced on this unit by the seller. There are some reports that the newer boot loader and or kernel had rendered certain KitKat ROMs innnc. Stock to present a black screen. However if it was me I would flash a stock Odin file pre KitKat if you can. The root via the original alda-v guidelines then flash philzs again from.
Then update to the latest philz recovery only file from his main thread.
Click to expand...
Click to collapse
Interesting, I will try that. I have NO clue what the previous owner did
Was that also affecting AOSP based Kitkat roms
Did anyone ever find a resolution?
Sent from my GT-I9205 using Tapatalk
Thanks to @Silesh.Nair our beloved device developer, he has found a commit that appears to fix the issue. Until its implemented in his builds the test kernel is here. http://forum.xda-developers.com/showthread.php?p=56122008
Sent from my GT-I9205 using Tapatalk