Just installed Rom Manager messing around and found that our device is listed but when I tried to flash it's recovery it shows 5.0.2.6 installed, but when I boot into recovery it's still showing 5.0.2.3.
Was it already listed and just not working? I'm running Starburst 1.7 with the stable kernel if it matters.
Sent from my SPH-D710 using xda premium
poppygt said:
Just installed Rom Manager messing around and found that our device is listed but when I tried to flash it's recovery it shows 5.0.2.6 installed, but when I boot into recovery it's still showing 5.0.2.3.
Was it already listed and just not working?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
No, it wasn't listed previously.
Probably the first stages of giving us official support.
I never installed it before because it was easy enough to use Odin and I knew we weren't supported when I got my device. That's cool though because I had read he was gonna nail down recovery and pass the phone onto the team for development. Nice step in the right direction.
Sent from my SPH-D710 using xda premium
mattykinsx said:
No, it wasn't listed previously.
Probably the first stages of giving us official support.
Click to expand...
Click to collapse
Exactly. Koush writes cwm and he is supposed to be our dev for cm7 too.
I flashed it from rom manager. It didn't work. I tried booting into recovery by turning off the phone and using volume up and power and it brought up stock recovery but then gave me a "!" Error. I also tried booting into it through rom manager with the same results.
Sent from my Samsung Galaxy S II Epic 4G Touch
Has anybody successfully flash cwm from rom manager or boot into recovery from rom manager?
This is good news! Koush is obviously working on support. Cool!
Samsung Galaxy S II
I tried flashing... And pushing the files but always seem to boot into the old recovery i had... But this means that he or teamhacksung will work on cm7 when its done
Sent from my SPH-D710 using XDA App
deano0714 said:
I tried flashing... And pushing the files but always seem to boot into the old recovery i had... But this means that he or teamhacksung will work on cm7 when its done
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Still good because rom manager allows you to select quick backup and restore which speeds thing up.
I have sussessfully flashed with rom manager. I can boot into recovery from a cold boot but if i do reboot to recovery from rom manager it will start to flaash something amd stop a quarter ways... I made a bold move and did a battery pull and it booted into recovery fine from the cold boot
Sent from my SPH-D710 using xda premium
mauricehall said:
I have sussessfully flashed with rom manager. I can boot into recovery from a cold boot but if i do reboot to recovery from rom manager it will start to flaash something amd stop a quarter ways... I made a bold move and did a battery pull and it booted into recovery fine from the cold boot
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Really? Still didn't work for me... I just went into rom manager, flashed cwm and then selected reboot into recovery and when it rebooted I got the box with the arrow then the triangle with the "!" In it.
I'm fully stock(kernel and rom) just rooted.
Sent from my Samsung Galaxy S II Epic 4G Touch
Worked great I formatted usb and ad storage, odined the new recovery, and flashed the new recovery through rom manager by selecting download recovery, after it downloads click install rom from sd, go into clockwork folder/downloads and select the new recovery, choose wipe dalvik and Ok. It boots into recovery, flashes, performs back ups seems to be fully functional so far. Thanks Koush! You daMan, may we please, respectfully request some CM7 bits? Been waiting a year and half to get some bacon again. (had the OG Epic previously)
Sent from my SPH-D710 using XDA App
mauricehall said:
I have sussessfully flashed with rom manager. I can boot into recovery from a cold boot but if i do reboot to recovery from rom manager it will start to flaash something amd stop a quarter ways... I made a bold move and did a battery pull and it booted into recovery fine from the cold boot
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Same exact thing happens to me!
Sent from my Samsung Galaxy S2 Epic Touch 4g using Tapatalk
mauricehall said:
I have sussessfully flashed with rom manager. I can boot into recovery from a cold boot but if i do reboot to recovery from rom manager it will start to flaash something amd stop a quarter ways... I made a bold move and did a battery pull and it booted into recovery fine from the cold boot
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Instead of pulling the battery, I held the power button until the phone rebooted in CWM itself.
What kernel are you guys on that this worked for?
Sent From My Evo Killer!!!
musclehead84 said:
What kernel are you guys on that this worked for?
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
Midnight rom with lostkernal
Sent from my Samsung Galaxy S2 Epic Touch 4g using Tapatalk
musclehead84 said:
What kernel are you guys on that this worked for?
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
Chris' pulled stock with cwm, although the version now up has some problem-wait until he fixes it. I'm using the first version.
move_over said:
Chris' pulled stock with cwm, although the version now up has some problem-wait until he fixes it. I'm using the first version.
Click to expand...
Click to collapse
And you can confirm cwm updated? Does the version in cwm show 5.0.2.6? Or does it still show 5.0.2.3? When I try to flash over compleatly stock kernel it doesnt work, it says it flashes but I cant get into cwm. When I flash over chris' stock with cwm packed it appears to flash just like on the stock kernel but when I load cwm it shows the older version 5.0.2.3. I have tried everything I can think of and no matter what, 5.0.2.6 doesnt load up for me.
Sent from my Samsung Galaxy S II Epic 4G Touch
graffixnyc said:
And you can confirm cwm updated? Does the version in cwm show 5.0.2.6? Or does it still show 5.0.2.3? When I try to flash over compleatly stock kernel it doesnt work, it says it flashes but I cant get into cwm. When I flash over chris' stock with cwm packed it appears to flash just like on the stock kernel but when I load cwm it shows the older version 5.0.2.3. I have tried everything I can think of and no matter what, 5.0.2.6 doesnt load up for me.
Sent from my Samsung Galaxy S II Epic 4G Touch
Click to expand...
Click to collapse
Same for me rom manager says i have 5.0.2.6 but when i boot into recovery it shows the older version
Chris's CWM now shows up as 5.0.2.6,and rom manager can reboot into recovery
Sent from my SPH-D710 using Tapatalk
Related
So, strangely enough, I went to boot into recovery this morning and my rogue hit man recovery got changed to the CWM 5.8.1.5. I definitely did not flash that and had to troubleshoot it because it would keep booting to that recovery. I got it fixed but why would it get changed without me flashing it? I am running Caulkin's Rom and have not done anything with the recovery since I flashed it. Some advice on how to avoid this is the future would be nice. and I am not using Rom Manager
ryandoubleu said:
So, strangely enough, I went to boot into recovery this morning and my rogue hit man recovery got changed to the CWM 5.8.1.5. I definitely did not flash that and had to troubleshoot it because it would keep booting to that recovery. I got it fixed but why would it get changed without me flashing it? I am running Caulkin's Rom and have not done anything with the recovery since I flashed it. Some advice on how to avoid this is the future would be nice. and I am not using Rom Manager
Click to expand...
Click to collapse
I'm a flash-a-holic, and have come across a couple of Kernels that have their own recovery versions included. Off the top of my head, Phoenix and Siyah come to mind. If you recently flashed a Kernel, there is your answer.
Not sure what else could have caused your issue, but it will be interesting to see what other members have to say.
tneS morf ym yxalaG II S (777i-HGS) gnisu ADX muimerP.
...
I have not flashed any kernels or recovery other than rogue's hitman. The phone just reverted back to CWM 5.8.1.5 again. I may try a new rom after I reflash the rocovery
Stop using hitman! Its bricking phones right now because somethings wrong with the original touch recovery. Switch to an old rouge recovery right away.
Sent from my SPH-D710 using XDA App
...
MrDowntown12 said:
Stop using hitman! Its bricking phones right now because somethings wrong with the original touch recovery. Switch to an old rouge recovery right away.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
OK, thanks.
It has done soft bricks on my phone when I go into recovery it would go to the CWM 5.8.1.5. At that point the recovery would keep rebooting to that recovery without letting me control it. I found that if you hit the home button a bunch of times it would boot back into the ROM, just fyi.
MrDowntown12 said:
Stop using hitman! Its bricking phones right now because somethings wrong with the original touch recovery. Switch to an old rouge recovery right away.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
+1,00000000 on this. Avoid hitman like a fat kid avoids salad. I don't know why that mod is still active.
tneS morf ym II S yxalaG (777i-HGS) gnisu ADX muimerP.
Click link below to read XDA Rules. Only takes a few minutes.
http://forum.xda-developers.com/announcement.php?a=81
Hi i used the wrong recovery to backup my Samsung epic touch and now all I get is a blue light it won't start or boot to recovery or odin any help will be appreceiated. I'm using EL26 kernal to flash ICS roms I went to cwm touch recovery instead of rouge recovery and now I'm stuck.
I do also have the FE02 plus recovery I forgot to mention that with having all my stress.
Sounds like another hard brick... Your only small hope would be in a usb jig and then a jtag service, but both might fail and you now have an expensive paperweight.
Sent from my SPH-D710 using Tapatalk 2
Try the manual method to get into download mode (copied from sfhub's TAR posts):
Code:
Method #1
Power down phone
Wait for capacitative button lights to turn off
Simultaneously Press and Hold [Power] [VolDn] until confirmation screen appears
Press [VolUp] to enter Download mode
Without getting into download mode you're probably a victim of the eMMC lockup. But to know for sure, what kernel version were you on when you last tried a CWM restore or wipe?
I was using EL26 kernal. I should have booted into recovery manually but I used rom manager it booted me into cwm touch instead of rouge recovery. I was going to flash a new ICS rom so I wiped everything and formated system and when I pressed reboot recovery, and rather then just going back it froze so I waited a bit then pulled the battery that's when it wouldn't do anything except the blue light.
I used the e4gtauto file to flash FE02+recovery. Which I understand is the one you need if you are flashing ICS roms but i used cwm touch before I realized it was the wrong recovery it was to late.
BTW it won't go into download mode
bigdaddy619 said:
I was using EL26 kernal. I should have booted into recovery manually but I used rom manager it booted me into cwm touch instead of rouge recovery. I was going to flash a new ICS rom so I wiped everything and formated system and when I pressed reboot recovery, and rather then just going back it froze so I waited a bit then pulled the battery that's when it wouldn't do anything except the blue light.
Click to expand...
Click to collapse
OK, the behavior - specifically that the phone froze and wouldn't respond until you pulled the battery - matches the eMMC lockup. Unfortunately yours appears to be locking up during the boot process which is why you can't get to download mode. Only way to fix is to take to Sprint for replacement.
Still curious how you did it though - and let's try our best to find it so that others don't suffer the same fate:
bigdaddy619 said:
I used the e4gtauto file to flash FE02+recovery. Which I understand is the one you need if you are flashing ICS roms but i used cwm touch before I realized it was the wrong recovery it was to late.
Click to expand...
Click to collapse
Can you link to the post containing the file you used to flash? I'm not aware of an FE02 build - maybe Agat's FF02 repack? And can you also include source of CWM touch if from a different ROM?
Sounds like he used CWM Touch on an ICS build. It flashed the recovery through rom manager, but the recovery isnt built correctly for our phones. Its a hard brick and will need to get a replacement. YOU HAVE TO USE A GINGERBREAD RECOVERY FOR IT TO WORK RIGHT
shiftr182 said:
Sounds like he used CWM Touch on an ICS build. It flashed the recovery through rom manager, but the recovery isnt built correctly for our phones. Its a hard brick and will need to get a replacement. YOU HAVE TO USE A GINGERBREAD RECOVERY FOR IT TO WORK RIGHT
Click to expand...
Click to collapse
Yea even then he stated fe02? Isnt that an ics kernal and also used touch which neither is good for flashing a new rom.. either way people make mistakes and like said already you have a nice paperweight.. to sprint you must go lol
Sent from my SPH-D710 using XDA
http://forum.xda-developers.com/showthread.php?t=1342728 this the link where i got the e4gtauto.
If you want CWM use Option C in the Auto Root Package to install EL26+CWM (you are already rooted so Option A is not necessary)
OOOOOPS it was the FD02+recovery sorry
bigdaddy619 said:
OOOOOPS it was the FD02+recovery sorry
Click to expand...
Click to collapse
There's your culprit. Once you get it replaced you'll want to stick with GB or FF02 repack which was done with care to avoid triggering the lockup for now. Sorry you had to find out this way...
Sent from my SPH-D710 using XDA
Close please
Sent from my MB855 using xda app-developers app
where did you find cmw touch?
I've been looking all over for it!
emottau said:
I've been looking all over for it!
Click to expand...
Click to collapse
Looking for what?
Sent from my MB855 using xda app-developers app
when i hit reboots it will go through, vibrate once and show the samsung logo and black screen and it doesnt power on.
had this issue with different roms.
anyway to fix???
Try TDJ's Darkside cache wipe script in the development section
Sent from my SGH-T989 using Tapatalk 2
VoiD_Dweller said:
Try TDJ's Darkside cache wipe script in the development section
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
already did, used it before flashing each rom, i got this phone brand new last week too
AngryDinosaur said:
already did, used it before flashing each rom, i got this phone brand new last week too
Click to expand...
Click to collapse
Using it before flashing isn't particularly helpful. Use it when you have the boot issue, like now.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
What recovery are you using? Please include the version too.
RTFOP said:
Using it before flashing isn't particularly helpful. Use it when you have the boot issue, like now.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
will try it
Afeety said:
What recovery are you using? Please include the version too.
Click to expand...
Click to collapse
used the toolkit to root and flash recovery
v5.0.2.6 for recovery
on JB miui right now
AngryDinosaur said:
used the toolkit to root and flash recovery
v5.0.2.6 for recovery
on JB miui right now
Click to expand...
Click to collapse
Try using TWRP 2.22
Sent from my SGH-T989 using xda premium
you may be semi-bricked. Just try a gingerbread rom or something.
AngryDinosaur said:
already did, used it before flashing each rom, i got this phone brand new last week too
Click to expand...
Click to collapse
So you did this before the flash.. Do this.. Pull the battery, insert the battery, turn phone on and boot it into recovery (not into ROM) and flash the cache wipe script.. See if that works.
Am I correct in you saying the roms work and it just doesnt reboot properly?
ya when i hit reboot it vibrates once to power off but then it will vibrate one more time and show the samsung logo and black screen, need to pull battery to get out of it
Mine was doing the same thing, I installed "Quick boot" from the market, and that works everytime
idbl_fanatic said:
Mine was doing the same thing, I installed "Quick boot" from the market, and that works everytime
Click to expand...
Click to collapse
Doesn't quick boot do basically a hot reboot? Where the phone actually is not turned off but more or less just restarting the ui?
sent from my BAD A$$ Epic touch
patrao_n said:
Doesn't quick boot do basically a hot reboot? Where the phone actually is not turned off but more or less just restarting the ui?
sent from my BAD A$$ Epic touch
Click to expand...
Click to collapse
No, you can do shut down, reboot, recovery, boot loader, and hot boot.
idbl_fanatic said:
No, you can do shut down, reboot, recovery, boot loader, and hot boot.
Click to expand...
Click to collapse
ill try quick boot too then
Mine did that too when I first installed a cm9. I did a complete wipe from cwm (dark side super wipe because I was on non-touch) then reflashed my recovery (flashed twrp via cwm) and it stopped having issues and not one since.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Isn't the CWM supposed to be updated to 5.0.2.7?
I just updated to the newest CMW, and I no longer have this problem, also, my "root going away" problem has been fixed as well.
idbl_fanatic said:
I just updated to the newest CMW, and I no longer have this problem, also, my "root going away" problem has been fixed as well.
Click to expand...
Click to collapse
I switched from CWM to TWRP and the problem went away.
I still has the issue with CWM's 6.0.1.4 recovery.
d01100100 said:
I switched from CWM to TWRP and the problem went away.
I still has the issue with CWM's 6.0.1.4 recovery.
Click to expand...
Click to collapse
Cwm 6.0.1.4 works for me I just prefer twrp. Moral of the story if you flash a recovery and have issues rebooting to it check the md5 (should do this with anything you flash) and re-flash in case it was a bad download or bad install.
Cwm when flashed from Odin always gave me issues until I did a dark side and reflashed.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
mr1080p said:
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
SysAdmNj said:
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
Click to expand...
Click to collapse
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
U have to make sure u are rooted first.
Sent from the TermiNOTEr!
mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
SysAdmNj said:
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
Click to expand...
Click to collapse
Yes. CWM and ported ROM. Everything works well I just want TWRP. But I guess I'll do with CWM. If it aint broke then why fix it. It works I guess. Thanks.
Sent from my SAMSUNG-SGH-I317 using xda premium
Check your build prop for device name. Maybe its not correct because of the Rom you're on. Whats the error you're getting?
Did you ever get TWRP on your phone?
I've had goofy issues with TWRP but much prefer it to CWM. Originally rooted using CWM and SuperSu and switched to TWRP when I flashed CleanRom several times via Romtoolbox pro I've flashed updated Twrp it said it was successful but when it rebooted was soft bricked! Had to use Odin and original CWM to get back in and re-install everything (nandroids were twrp backups) found file downloaded to sdcard that worked fine! Odd...
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
wargear said:
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
Click to expand...
Click to collapse
If by "installed" you are referring to the recovery program itself (and not your backups), you can only have one recovery 'installed' at one time as there is only 1 "Recovery" partition on the device (/dev/block/mmcblk0p9). So if you want to install CWM instead of your current TWRP (or visa-versa), either flash the appropriate new recovery zip via your current recovery... or Odin3 flash your desired new recovery tar. Either way, it will write to the same recovery partition. If you are referring to your backups... these are stored in the designated path you selected (either internal sd or external sd)... in the TWRP/BACKUPS folder. In that folder, you will have a device id #... in that folder are your backups.
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
wargear said:
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
Click to expand...
Click to collapse
Which version of Odin3 are you using? When I used Odin3 v1.85 I would get the "PASSED" but with Odin3 v3.07, I also only got "RESET" (on an WindowsXP box)... but both flashed it correctly (and auto rebooted after flash)
Galaxy Note2 TOOLKIT V3.0.0 ATT]
I tried the [Galaxy Note2 TOOLKIT V3.0.0 ATT] http://forum.xda-developers.com/showthread.php?t=2052779 out of curiosity sake. Worked for me installing TWRP 2.3.2.3 without a hitch. Great tool from what I can see, and that's just one of it's many features. Great for simplifying things for new Android users just entering the customizing scene and regulars alike. Big ups to mskip for making this available. I can foresee myself grabbing the donate version here real soon.
And to get yourself SIM unlocked, get yourself back to 4.1.1 and give this a whirl.http://forum.xda-developers.com/showthread.php?t=2014982 Bought my device used, was supposedly unlocked, wasn't. Even came with an unlock code that the previous owner purchased. Firstly it's a no go on 4.1.2, secondly still didn't work when I dropped back to 4.1.1. But this http://forum.xda-developers.com/showthread.php?t=2014982 will set you free. Big thanks owl74 for posting. Once again XDA forums saves my hair from being pulled out.
I've searched relentlessly for a solution to this, but I haven't come up with anything, so it's time to ask for help.
I just used mskip's Galaxy S3 QCOM Toolkit v2.3 (http://forum.xda-developers.com/showthread.php?t=1746682) to flash CWM and root my GSIII. The recovery flashed successfully, using "recovery-cwm-lte-sgs3-v5.tar" included with the toolkit.
CWM recovery works. However, when I tried to boot the phone, I got the first Samsung splash screen, then the screen turned black, a second later the boot tune played (with no splash screen showing), and then... nothing. The blue notification light blinks infinitely, and the phone is unresponsive except for holding the power button down for 10 seconds, which restarts it, and the same thing happens again.
I can boot into CWM recovery, as well as download mode. I tried wiping the cache and doing a factory reset, which changed nothing. However, when I tried to flash a stock ROM (again using the toolkit), I got an "unsupport dev_type" error. I presume that USB debugging has been defaulted to disabled now from this, but maybe I'm wrong. In any case, I'm not sure where to go from here. I don't want to claim that I've bricked it yet, when I have both recovery and download, but I don't know what to do now.
Help?
EDIT: I'm sorry, I forgot basic information : I'm using a SGH-T999 (T-Mobile GSIII).
I would defiantly boot in to cwr and do a clean install on a diferent rom. Not a back up u made with cwr but a .zip rom... n u sgould b ok.. I would try jb smooth
Sent from my SGH-T999 using xda app-developers app
See if you can flash CM10, if you don't have to have stock.
kipster3001 said:
I would defiantly boot in to cwr and do a clean install on a diferent rom. Not a back up u made with cwr but a .zip rom... n u sgould b ok.. I would try jb smooth
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Looks like the toolkit installed an older version of CWM. I flashed 6.0.1.2 via ODIN (http://forum.xda-developers.com/showthread.php?p=30806933) and then flashed CyanogenMod 10.0.0. Works great.
Thanks so much!
Jacooni said:
Looks like the toolkit installed an older version of CWM. I flashed 6.0.1.2 via ODIN (http://forum.xda-developers.com/showthread.php?p=30806933) and then flashed CyanogenMod 10.0.0. Works great.
Thanks so much!
Click to expand...
Click to collapse
Glad you had it resolved. Another method would have been ODIN back to stock.
Sent from my SGH-T999 using xda app-developers app