So I was pretty determined to get Cm 10.1 running on my Galaxy Note 2 for Verizon. Before hand, I was using TWRP to do all my ROM flashings but when I tried to use CM 10.1, I was told I must use CWM for it to work properly.
Here's my issue, I tried using CWM but it kept on giving me an error and after searching for awhile, it said its because I'm trying to use TWRP instead of CWM. So I flashed CWM and it gave me the same error. Tried both Touch and regular, downgraded and upgraded to the latest CWM but still same error. So I said **** it and installed the lastest TWRP. Then all the ROMs that were giving me issues started to install flawlessly. Then I went to CWM and it gave me the same error.
Am I doing something wrong when I flash CWM? I tried both Odin and APP Update way and both with same results. After using TWRP for awhile, I actually am starting to like the CWM Touch a lot better and I want to switch but not if its going to be giving me problems every flash.
Any insight would be helpful,
and as always to everyone on this forum, thanks
Just make sure you are using the latest version of TWRP 2.5 and you will be fine. You also may need to re-download your ROM file.
Well I am, in a way, stuck using the TWRP right now but I would like to know if I can actually change it to CWM. And if so, how would I go about doing that? because flashing the CWM alone isn't doing anything for me.
wythyntime said:
Well I am, in a way, stuck using the TWRP right now but I would like to know if I can actually change it to CWM. And if so, how would I go about doing that? because flashing the CWM alone isn't doing anything for me.
Click to expand...
Click to collapse
That is the way I have always gone about getting CWM on my phone back when I wanted it. I would just flash over TWRP in TWRP and then reboot system and then reboot back into recovery and it would always be CWM. If it doesnt work for you that way then see if they have a Odin tar and if so follow the instructions to flash it in Odin. They may not have an Odin flashable though, its been a long time since I have used it and on a different phone so....
Sent from my SCH-I605 using XDA Premium HD app
Let me actually rephrase this. (My bad for any confusion)
So if I try to flash a rom using TWRP, it goes through without any issues, even the CM rom. But when I flash CWM and try flashing, it gives me the getdevice-"(t0vzwte)"-not exact".. When researching, I was kept on told its because it is running TWRP. I tell them its CWM and they told me to update my CWM. I actually like CWM a bit better, idk why. but I was just trying to get my phone 100% the way I want it.
Related
gtab wifi, stock tw3.2., cwm 5.8.3.1
i've tried flashing several roms using cwm and through rom manager. every time i get stuck on the the samsung screen after reboot, which takes about 30 seconds after initiating flash. i've never had a problem installing anything on my phones or my nook color. it's been nothing but a paper weight for the last year and it's going to the landfill if i can't figure it out soon.
Did you try to wipe data/factory reset/ wip cachd and wipe dalvik?
all of it. follow directions for each rom exactly. i always end up in the same spot
burnitdown said:
all of it. follow directions for each rom exactly. i always end up in the same spot
Click to expand...
Click to collapse
How much you wait? After I flashed the Galaxy Task 14 room earlier this day it took several minutes to load.
Certain ROMS require an older version of CWM, such as CM9. If that is the latest version you have installed it may not work. Maybe try using ODIN to flash the recommended version (you can easily find that in the CM9 Nightly threads or simply by searching around)?
bar_rodoy
Click to expand...
Click to collapse
i let it sit long enough.
this_is_nick6
Click to expand...
Click to collapse
i'm using the most up to date cwm. right now i'm trying to flash aokp m4
burnitdown said:
gtab wifi, stock tw3.2., cwm 5.8.3.1
i've tried flashing several roms using cwm and through rom manager. every time i get stuck on the the samsung screen after reboot, which takes about 30 seconds after initiating flash. i've never had a problem installing anything on my phones or my nook color. it's been nothing but a paper weight for the last year and it's going to the landfill if i can't figure it out soon.
Click to expand...
Click to collapse
Can you link us to the CWM 5.8.3.1 recovery your using???
As far as I know this is the latest version of CWM http://droidbasement.com/db-blog/?p=2655 as of 6/30 and it's only 5.5.0.4.
As far as Googling is telling me...
1. It may be a touch recovery?
2. I couldn't find a many search returns that mentioned it being for Tab10.1s
3. The search returns I did find that mentioned Galaxy Tabs were in languages I don't read.
Just curious don't ya know...
Sent From My Galaxy10.1 Class Starship....
Questions go in the Q&A section
my recovery is listed on the cwm site under rom manager. it's not touch
now i'm curious as to what version everyone else is using
okay. so i flashed 5.5.0.4 through odin then flashed aokp m4 plus gapps. all seemed to go well until boot time. i've been sitting at the samsung screen for a full 20 minutes now. i suppose my next course of action would be to revert to stock via odin and start the process over? i'd really like to use this thing but absolutely can't stand tw
you may have gotten a corrupt partition somewhere. I'd odin back to stock and start fresh. fwiw, I wouldn't trust ROM Manager for the latest recovery, it doesn't always have the correct file for your device. For example, for may particular phone Rom Manager had never worked properly and soft-bricks the phone every time.
Always check here on XDA for the proper recovery files for this device first.
that's all i needed to hear. now, can anyone point me in the direction of the file i need? my searches all point to S0ckM0nk3y's link which results in a 404 error
disregard my last post. i flashed sam's ics via odin. i'll play with it and try to like it. thank you sir
huh. still can't flash a custom rom...
Well, I don't know what I did but i was able to get MapleSyrup's CM10 preview to run. I'm happy for now
Are you doing a factory reset and wiping the cache in CWM before you flash? I always do that and then use titanium backup to restore my apps.
Also, what version of recovery are you using? I'm on CWM 5.5.0.4 which I've used to flash a couple of different roms, including the latest stock ICS from Toldo I think.
you can get it here and use ODIN to flash. Just make sure you download the correct version for your device:
http://droidbasement.com/db-blog/?p=2668
i had the same problem. i flash stock ics rom for my 7510. at first it looks fine until i try to reboot my tab. it starts to hang at the bootscreen. i try to reflash the rom via recovery but fail. try to install nandroid backup and also fail. the last resort is to do clean flash from odin. this thing happened 5 times in 3 days. one time after i install all the apps and try to restart my tab then it happened again, stuck at bootcscreen.
Got my Note a few hours ago. Charged it up. Downloaded Odin. Rebooted to download mode. Used Odin to flash some pda.tar that I got from a thread here which said it would install root.
My phone rebooted, and it has been stuck at "Samsung" ever since. Reboots and pulling battery do nothing. Reboots to a stuck samsung logo. I've also, since, flashed CWM successfully, and I'm able to boot to CWM.
I attempted to flash the CM10 builds from these boards, and it errors out with a build.prop thing and refuses to install the package.
Am I bricked without ever making even 1 phone call on my new phone? ..
You are not bricked. If you were bricked you would not be able to get into CWM.
What ROM did you try to install and can you still see it from CWM?
Also which CWM did you install? I think the version of CWM is probably the issue with CM10, just a guess.
Can you get in to download mode?
Also, what version of the Galaxy Note do you have? I717 or what?
From what I've seen all cmw versions posted on the board are too old to flash cm10.
Flashing cmw and then booting up to install/download/flash ROM manager and the latest version of cmw will fix the cm10 problem. But if you attempted to flash a cmw tar and it got stuck at the boot screen you likely flashed the wrong version for your os.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
kinghorsey said:
From what I've seen all cmw versions posted on the board are too old to flash cm10.
Flashing cmw and then booting up to install/download/flash ROM manager and the latest version of cmw will fix the cm10 problem. But if you attempted to flash a cmw tar and it got stuck at the boot screen you likely flashed the wrong version for your os.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
I flashed a factor(?) build. It's an old gingerbread. Booted up. Tried to run Kies. It, of course, told me to fly a kite. Ran the pda.tar again and it installed a kernel, succesfully, that then allowed me to install superuser. Then I flashed my CWM again. It works. Just did a backup.
When I try to use it to install CM10, i get a status 7 error. I'm using the 4-14-2012 touch recover found at http://forum.xda-developers.com/showthread.php?t=1584576
From what I'm gathering from your post, if I install ROM Manager, it will update me to a better CWM, and that CWM will flash CM10 without status 7ing on me?
Thanks for the quick responses guys. I've done a number of Droid's, nexus 7, and my Acer a500, but I'm new to Odin. The thought of bricking a phone without owning it 3 hours had me in a panic.
edit: installed ROM manager. It doesn't give me the option to download CWM for a note. Not sure what to do there.
I don't believe your Note is bricked. This thing seems to be bullet proof.
Anthony820 said:
I flashed a factor(?) build. It's an old gingerbread. Booted up. Tried to run Kies. It, of course, told me to fly a kite. Ran the pda.tar again and it installed a kernel, succesfully, that then allowed me to install superuser. Then I flashed my CWM again. It works. Just did a backup.
When I try to use it to install CM10, i get a status 7 error. I'm using the 4-14-2012 touch recover found at http://forum.xda-developers.com/showthread.php?t=1584576
From what I'm gathering from your post, if I install ROM Manager, it will update me to a better CWM, and that CWM will flash CM10 without status 7ing on me?
Thanks for the quick responses guys. I've done a number of Droid's, nexus 7, and my Acer a500, but I'm new to Odin. The thought of bricking a phone without owning it 3 hours had me in a panic.
edit: installed ROM manager. It doesn't give me the option to download CWM for a note. Not sure what to do there.
Click to expand...
Click to collapse
First don't use rom manager it is crap software caused me more headaches than help. Use twrp here http://forum.xda-developers.com/showthread.php?t=1647575. Wipe your Note than flash cm10 than flash jb google apps and you will be up and running.
Anthony820 said:
I flashed a factor(?) build. It's an old gingerbread. Booted up. Tried to run Kies. It, of course, told me to fly a kite. Ran the pda.tar again and it installed a kernel, succesfully, that then allowed me to install superuser. Then I flashed my CWM again. It works. Just did a backup.
When I try to use it to install CM10, i get a status 7 error. I'm using the 4-14-2012 touch recover found at http://forum.xda-developers.com/showthread.php?t=1584576
From what I'm gathering from your post, if I install ROM Manager, it will update me to a better CWM, and that CWM will flash CM10 without status 7ing on me?
Thanks for the quick responses guys. I've done a number of Droid's, nexus 7, and my Acer a500, but I'm new to Odin. The thought of bricking a phone without owning it 3 hours had me in a panic.
edit: installed ROM manager. It doesn't give me the option to download CWM for a note. Not sure what to do there.
Click to expand...
Click to collapse
first things first
GET RID OF CWM. it will just cause more issues then it needs to.
second
INSTALL TWRP2.2.1.1
third
enjoy your day. *and make a new backup in twrp2.*
Anthony820 said:
I flashed a factor(?) build. It's an old gingerbread. Booted up. Tried to run Kies. It, of course, told me to fly a kite. Ran the pda.tar again and it installed a kernel, succesfully, that then allowed me to install superuser. Then I flashed my CWM again. It works. Just did a backup.
When I try to use it to install CM10, i get a status 7 error. I'm using the 4-14-2012 touch recover found at http://forum.xda-developers.com/showthread.php?t=1584576
From what I'm gathering from your post, if I install ROM Manager, it will update me to a better CWM, and that CWM will flash CM10 without status 7ing on me?
Thanks for the quick responses guys. I've done a number of Droid's, nexus 7, and my Acer a500, but I'm new to Odin. The thought of bricking a phone without owning it 3 hours had me in a panic.
edit: installed ROM manager. It doesn't give me the option to download CWM for a note. Not sure what to do there.
Click to expand...
Click to collapse
First don't use rom manager it is crap software caused me more headaches than help. Use twrp here http://forum.xda-developers.com/showthread.php?t=1647575. Wipe your Note than flash cm10 than flash jb google apps and you will be up and running.
One last thing if you want Adobe flash to work in your browser (i.e. Dolphin) you have to stay with ICS builds. Adobe stop supporting Android after 4.0.X releases.
Thanks guys. I swear I'm only a completely flustered noob with the note. I've got a custom ROM'd nexus 7 on one side of me and I'm using my sdcard from my CM10'd acer a500.
I can't thank you all enough. Everything is now running -- cm10 and booting -- and I'm live.
@ Anthony820.....
I have edited your topic to show [Solved] so that other users can see the status.
@ everyone else.....
Thank you for assisting the OP. This is what XDA is all about.
JamieD81 said:
first things first
GET RID OF CWM. it will just cause more issues then it needs to.
second
INSTALL TWRP2.2.1.1
third
enjoy your day. *and make a new backup in twrp2.*
Click to expand...
Click to collapse
Nothing wrong with ROM manager and I've never had an issue with it on the note. It does only flash newer cwm on ICS and doesn't seem to support gb well but that is easily bypassed.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
I did a backup in TWRP before flashing the PA alpha ROM, realized I needed CWM, so flashed that over in TWRP. Fine. Installed PAalpha in CWM. Fine. Decided to go back to the ROM I'd backed up (Beans), so attempted to flash TWRP over in CWM. Rebooted recovery. Sent me straight to stock recovery. Still boots into PAalpha fine.
I've tried to install TWRP via goo manager, and it says it's successful, but I'm still on stock recovery. Did I f- something up? How can I get back to custom? Did I screw my unlock somehow (doesn't seem like it would...)?
I've been doing the flashing thing since the Eris, but have been out of the game for a cycle, and am wary of messing around with things now that I'm at a point I don't quite understand. Much thanks.
Unlocked and rooted.
vxkid said:
I did a backup in TWRP before flashing the PA alpha ROM, realized I needed CWM, so flashed that over in TWRP. Fine. Installed PAalpha in CWM. Fine. Decided to go back to the ROM I'd backed up (Beans), so attempted to flash TWRP over in CWM. Rebooted recovery. Sent me straight to stock recovery. Still boots into PAalpha fine.
I've tried to install TWRP via goo manager, and it says it's successful, but I'm still on stock recovery. Did I f- something up? How can I get back to custom? Did I screw my unlock somehow (doesn't seem like it would...)?
I've been doing the flashing thing since the Eris, but have been out of the game for a cycle, and am wary of messing around with things now that I'm at a point I don't quite understand. Much thanks.
Unlocked and rooted.
Click to expand...
Click to collapse
If you used the website in the twrp thread it does not work. I did the same thing. I had to odin the suck it verizon zip again. After that all was good. Hope this helps.
Sent from my SCH-I605
Android_Fr3ak said:
If you used the website in the twrp thread it does not work. I did the same thing. I had to odin the suck it verizon zip again. After that all was good. Hope this helps.
Sent from my SCH-I605
Click to expand...
Click to collapse
EDIT: I held my breath and flashed it over. Everything's great now. Thanks.
That's exactly what I used. Thanks so much. To be clear, flashing suck it verizon through odin is all i need to do (no need to mess with the other unlock steps?)
Best
vxkid said:
That's exactly what I used. Thanks so much. To be clear, flashing suck it verizon through odin is all i need to do (no need to mess with the other unlock steps?)
Best
Click to expand...
Click to collapse
yes...you should never need to relock bootloader.
Hi there,
I tried to flash a new rom and it some how is stuck on the reboot screen.
Any help in what to do, would be great!
Thanks!
Pull the battery, put it back. Hold button combo to boot to recovery. Flash the ROM again but do not wipe. Reboot and you should be good.
FFR please list which ROM you are coming from and the ROM you are flashing.
Sent from my SCH-I535 using xda premium
Thanks, for your help!
I ended up taking out the battery, and then rebooting it, and it went to the Recovery mode.
I actually did wiped everything all over again, like you were doing it from the start originally, and it seemed to work fine.
I cant even remember what I was coming from, I had it on my Phone for almost two years, and it was old and the battery life was terrible.
I tried RemlCS-JB its not bad, but I think I am going to try another one. Any suggestions? I have been away from this forum for over a year, so anything recent with good battery life and good GPS is ideal.
The rom did not seem to come with an app downloader such as google play, or Clockwork manager.
Anyone know how to get into reboot recovery mode without clockworkmanager?
When I try to download clockworkmanager online it does not let me really download it.
When I try to install a new Auxura rom it states the following:
It says Installation aborted
Above that, it states please switch Edify scripting
Anyone know, if I have to do something else? I am just doing a normal Clockwork Flash.
I wiped the data/factory set, then tried to install the rom
molson24 said:
When I try to install a new Auxura rom it states the following:
It says Installation aborted
Above that, it states please switch Edify scripting
Anyone know, if I have to do something else? I am just doing a normal Clockwork Flash.
I wiped the data/factory set, then tried to install the rom
Click to expand...
Click to collapse
Did you Odin back to stock before trying to flash a ROM that is a previous version of android? It could cause a lot of problems if you don't Odin back to stock first!
Did you flash gapps on the ROM that you said was missing apps etc?
Gapps is a package of Google apps that devas can't include in the ROM.
I wouldn't use ROM manager, in most ROMs, there is an option to reboot to recovery in power menu. You can also power down and use button combo to boot to recovery.
I highly suggest reading through some of the dev threads for any ROMs you are interested in. It will answer most of your questions and prevent future issues.
Sent from my GT-P5113 using xda premium
Oh yeah, it said to flash GAPPS after, but I never did. Where do you get GAAPS?
No, I dont even have ODIN installed on my computer and all of those drivers, so It is something I do not want to do.
It has been 2 years since, I switched, so I randomly flashed to this new one, but I want to try a different one, but seems to get an error.
Ill try a few other roms to see if they work though.
molson24 said:
Oh yeah, it said to flash GAPPS after, but I never did. Where do you get GAAPS?
No, I dont even have ODIN installed on my computer and all of those drivers, so It is something I do not want to do.
It has been 2 years since, I switched, so I randomly flashed to this new one, but I want to try a different one, but seems to get an error.
Ill try a few other roms to see if they work though.
Click to expand...
Click to collapse
You can get the gapps from the op of the ROM thread or go to www.goo.im/gapps
As far as Odin etc
If you are on an ICS or JB ROM and want to go back to a froyo or GB ROM, you need to odin to stock first.
General rule of thumb, you can flash up but to flash down, Odin to stock first.
Sent from my SCH-I535 using xda premium
Hey guys, I need help.
I consider myself fairly adept at handling rooted devices, but I have not been following development for the GS4 for the last several months and have been running the last release of Synergy before their hiatus.
I was going to try out something different. I always enjoyed Beanstown's Jelly 'Beans', and thought I would try Build 7.
Now I am stuck at the Samsug Galaxy Boot Logo and it never goes to the Custom Boot Screen.
WORSE...I managed to break my recovery...so it will not boot their either.
Only mode I can boot to is Download.
Maybe I am just blind but I searched and could not find any Odin flashable recoveries...does anyone have one? Is there a rooted MDK file out there that I can flash via Odin?
Someone please help
Did you do the proper wipes when flashing the new rom? There arent any odin flashable recoveries for the s4. I would probably use the no wipe mdk image to recover (wont lose any user data) since you have no custom recovery to flash something with. Youll have to start over but youll have a working phone at least.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
jbg25 said:
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
Click to expand...
Click to collapse
Yeah looks like you got everything in order. Rom manager or rom toolbox will auto loki the recoveries. No need to update radios when flashing beans either. Itll already have the radios included unless your wanting to flash the mj7 radio seperately then I believe youll be ok doing that. I havent done alot of reading on the newest radios.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
jbg25 said:
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
Click to expand...
Click to collapse
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
beanstown106 said:
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
Click to expand...
Click to collapse
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
jbg25 said:
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
Click to expand...
Click to collapse
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
jbg25 said:
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
Click to expand...
Click to collapse
Go here. Get 2.5.0.2
http://techerrata.com/browse/twrp2/jfltevzw
Instructions
http://teamw.in/project/twrp2/181
At the bottom of the page.
Edit;
Or flash this in recovery
http://forum.xda-developers.com/showthread.php?p=45006486
I would reboot to recovery after flashing to make you got it on the right version.
Then make sure you can still boot back to your rom.
Then go back to recovery
Wipe
Factory reset.
Advanced
Check system, Data, davlik and cache
Wipe
Go back to main screen
Install
Fund your rom to flash.
Sent from my SCH-I545 using xda app-developers app
Me too. I tried the [ROM][TW4.3]STOCK-ROOTED-MJ7-AROMA-LOKI'd ROM with CWMR. Wiped Dalvik. Cache, Ractory Rest/Data. Seemed to install fine but then hung at "Custom". Fortunately I was able to a Nandroid Restore but not sure where this went wrong. Finally got TWRP to install after several failed GooManager attempts over the past month. May CWMR is the problem.