i was using my phone running aokp mod 40. everything fine then i get FC on like every app so i rebooted. after reboot i got regular boot loop. then i went to my cwm. after that it just says Samsung then flashes twice and goes to cwm. i wiped everything and rebooted and nothing. please help
There us a guide called droidstyles guide here. You should check it out. It might help you
Sent from my SCH-I500 using Tapatalk 2
i went back to stock with odin, then went back to a ics rom but now it just bootloops the AOKP unicorn.
ramongarza said:
i went back to stock with odin, then went back to a ics rom but now it just bootloops the AOKP unicorn.
Click to expand...
Click to collapse
after hooking your phone up via usb cable do 'adb devices' make sure your computer sees your phone then try this command in cmd 'adb reboot recovery' (you have to have android sdk installed to do that command, btw)
i fixed it. i odined back to stock then i re-rooted. and flashed a teamhacksung build 1. that worked well but it was 4.01 then i flashed milestone 6 aokp and it worked. i guess i was on the wrong build
ramongarza said:
i fixed it. i odined back to stock then i re-rooted. and flashed a teamhacksung build 1. that worked well but it was 4.01 then i flashed milestone 6 aokp and it worked. i guess i was on the wrong build
Click to expand...
Click to collapse
good and youre welcome for the help, sir
now enjoy that bit of icecream sandwhich before it gets replaced with some jelly(bean)!
Related
Hi all
I'm not new to flashing but I'm new to flashing cm7.
I odin back to stock jfd eclair. Root and Install CWM 2.xxx. I downloaded the stable cm7 and I started flashing. (after I wipe data/cache of course)
IN recovery, it said finding package, opening package, then my phone processed a series of lines and reboot automatically. On the startup, it says VIBRANT SAMSUNG, then GALAXY S CYANOGEN(mod) then the same recovery screen with many lines. It moved too fast into another reboot I couldn't read what was on the screen. And it kept doing this for quite 10 mins now.
Is it normal? if not, what did I do wrong? I can get into download mode and odin back to stock but I did it last night and I couldn't think what i did wrong.
Please help!
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
stumpyz9 said:
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
wavestar92 said:
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
Click to expand...
Click to collapse
Try reflashing cwm when your rooted, may have not flashed right
Sent from my Gewgle Phone via XDA App
This happened to me also, I went directly back to recovery, 3 button, and reflashed. Worked the second flash for some reason.
Thanks. I turn it off, get into recovery again, and re flash it successfully
Same exact thing happened. I have no idea how many time I odened back to stock trying to figure it out.
I did as you guys said, as soon as that loop began, pulled the battery and got back into recovery. flashed again and worked just fine!
same thing happened to me...i got back into recovery...i noticed cwm updated to 5.0.2.8 then i reflashed and all good...when i tried to flash at first. cwm was 2.5 ..maybe thats the issued it wont flash on that...has to be cwm 5.0
anyway getting ready enjoy some cm7 on my vibrant...
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
Has anyone else had a boot loop problem with the new V of TWRP?? I'm running SOAv3 ROM and had ZERO problems, upgraded my twrp and had about a dozen restarts and freezes and then when I tried to boot into recovery, it boot looped. Fixed it with ODIN, then tried installing it fresh, and got the same thing. Went back to my older version and things are fine once again just wondered if this is isolated or just a known bug??
Yes its a know issue right now go back to the previous working version of twrp and wait for it to get fixed.Also be sure to check big Biff's twrp page before trying to update again to make sure everything is good.
Sent from my SGH-I717 using xda premium
Just update from Padawan V8 to SOA build 3. Was skeptical for a day or so but finally did it last night. Was just about to update to the New TWRP, thank fully I read through all those pages before I did, I usually don't. Saved me a head ache except I forgot to wipe cache's before installing the GAPPS, going to have to re-do that I believe to get the new camera functions from what I've read.
Demmonnixx said:
Just update from Padawan V8 to SOA build 3. Was skeptical for a day or so but finally did it last night. Was just about to update to the New TWRP, thank fully I read through all those pages before I did, I usually don't. Saved me a head ache except I forgot to wipe cache's before installing the GAPPS, going to have to re-do that I believe to get the new camera functions from what I've read.
Click to expand...
Click to collapse
you are correct Sir.....wipe caches and re-flash gapps.....g
psycoartwork said:
Has anyone else had a boot loop problem with the new V of TWRP?? I'm running SOAv3 ROM and had ZERO problems, upgraded my twrp and had about a dozen restarts and freezes and then when I tried to boot into recovery, it boot looped. Fixed it with ODIN, then tried installing it fresh, and got the same thing. Went back to my older version and things are fine once again just wondered if this is isolated or just a known bug??
Click to expand...
Click to collapse
How did you fix with odin? I can't get mine into the download mode to connect to odin. it just keeps boot looping?
whitebrw said:
How did you fix with odin? I can't get mine into the download mode to connect to odin. it just keeps boot looping?
Click to expand...
Click to collapse
Hold volume down and power ...it will go into download mode
Sent from my SGH-I717 using xda app-developers app
thanks but no thanks, when i do that it does the same thing as any other way of starting, just loops.
check out my post if you want.
http://forum.xda-developers.com/showthread.php?t=2202663
I've been trying to load a new rom onto my fascinate sch-i500v for a few hours now. I previously had a 4.1 build (milestone I think) and cwm 4.0.1.0 installed. I've tried every rom from cw10 to hellybean to avatar and they all do the same thing. I wipe the cache, factory reset. Then installed from the zip file. At this point, the install starts to initiate, but the phone suddenly reboots and after a few seconds tries to load up the old rom (unsuccesfully, hence why I said I'm seeing the "initiating swagger" load screen forever)
Yesterday, I did this exact upgrade successfully to my other fascinate sch-500 (no v on the end for that one, not sure if that makes any difference).
That one rebooted suddenly as well, but it went back into the clockwork recovery and completed the install without a hitch.
Anybody have any suggestions? I'm sort of a noob, but I have flashed over ten phones...
Go back to stock and start over
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Go back to stock and start over
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Thank you. i fugured that was what I needed to do, but I was afraid of how complicated it would be. LMFAO, it was pretty simple!
A couple of months back I was using Carbon 4.4 on my phone. I realized that I grabbed the wrong model number and install an galaxy s3.
Everything was working fine for a while before I knew that I messed up. Then one day app started messing up and that when I saw that it was wrong. I tried flashing the Note 2 version of the ROM and got stuck in a boot loop. Which resulted in a battery pull and booting back into recovery. Only SlimKat has worked for me now. Carbon, Liquid Smooth, Pac Man don't work. They all get stuck in booting image and spin forever.
Is there anything I can do to get these roms working again?
superdusto said:
A couple of months back I was using Carbon 4.4 on my phone. I realized that I grabbed the wrong model number and install an galaxy s3.
Everything was working fine for a while before I knew that I messed up. Then one day app started messing up and that when I saw that it was wrong. I tried flashing the Note 2 version of the ROM and got stuck in a boot loop. Which resulted in a battery pull and booting back into recovery. Only SlimKat has worked for me now. Carbon, Liquid Smooth, Pac Man don't work. They all get stuck in booting image and spin forever.
Is there anything I can do to get these roms working again?
Click to expand...
Click to collapse
Would flashing it to stock via odin fix any errors I might have created?
Yeah, typically if you Odin back to stock, and reroot. Choose the correct package though, don't want 4.3 Odin, or you end up locked tight.
Sent from my SCH-I605 using Tapatalk
JeramyEggs said:
Yeah, typically if you Odin back to stock, and reroot. Choose the correct package though, don't want 4.3 Odin, or you end up locked tight.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Do you have a recommended one?