I flashed back to unrooted stock ed 13 took the ota update, flashed shabby kernel then cwm and finally shabby mod. everything went flawlessly and I haven't had the double reboot issue once.
i bought a phone stocked with EE14, i rooted it, then installed shabbymod 0.9, then i installed CWM (i did have a few issues installing CWM, but i was able to fix it enough to get everything running)
ever since then, whenever i go into recovery, no matter what you do next, once your choose reboot into system now, it always reboots you right back into recovery, once you choose reboot into system the 2ND time it will boot you into the system, and everything else seems to work ok
maybe i should reinstall CWM? and see if that clears it up?
does CWM take up space for internal memory?
and also backups take up sd memory right?
so more backups you have the less memory in your sdcard you're gonna have?
I created a ClockWorkMod Recovery V4.0.1.4 for Samsung Prevail SPHM820
:UPDATE:
If you have taken the EE14 official update you need to remove /system/ect/intall-recovery.sh
If you do not remove this file the stock recovery gets flashed back when phone is rebooted
I made a zip file that needs to be flashed from CWM as soon as CWM is installed, so you have to go into CWM as soon as Odin resets the phone, with out letting the phone boot up, a link to the fix is below
i just noticed this little gem, it turns out i still have install-recovery.sh on my phone, yet it doesn't get the stock recovery flashed back when i reboot (strange)
but maybe THAT is the reason, why i always have to double reboot??
i tried using File Explorer to delete that file but it doesn't work, do i need another app or special settings to accomplish this? (a free app hopefully)
Device(s): LG Nexus 4, HTC EVO 4G Sold, LG Esteem Wifes, Samsung Galaxy Prevail, Samsung Nexus S 4G, LG Optimus
Carrier: Not Provided
Thanks: 196
Thanked 859 Times in 634 Posts
Quote:
Originally Posted by protegemini
does CWM take up space for internal memory?
and also backups take up sd memory right?
so more backups you have the less memory in your sdcard you're gonna have?
if you want you can move the backups to your computer, using the cable provided your sd card is read as another drive on your computer and you can just leave one, on your sd card. and if you feel like changing to a different one you can just move that to the sd card then boot into cwm and flash it.
cwm does not take up user space. recovery on the phone has its own reserved memory which we can not access except by using odin to put cwm on.
btw for the nooby noobs #12 should say "install zip from sdcard" not "flash zip"
so after removing that /intall-recovery.sh file it now only takes 1 reboot from recovery when you get into recovery via vol up method
however anytime you use a software recovery such as with quick boot or ACS updater, it still requires 2 reboots??
i've run out of ideas, maybe i glitched my phone during one of the installs??
right after i removed that /intall-recovery.sh file i rebooted to see what would happen, and it got stuck in the infinite droid boot ani (just like the first time i installed CWM) wiped factory/cache and rebooted and back to "normal"
and just a final thing i noticed, (since i'm just blindly guessing) during the install on step 11. where you say go into vol up recovery mode,(i start holding vol up + power) it will boot into the the first two screens 1. samsung.com screen then 2. samsung prevail screen, (meanwhile i'm still holding vol up) then it will reboot again 1. samsung.com + 2. samsung prevail THEN it will open the CWM
i bought a phone stocked with EE14, i rooted it, then installed shabbymod 0.9, then i installed CWM (i did have a few issues installing CWM, but i was able to fix it enough to get everything running)
ever since then, whenever i go into recovery, no matter what you do next, once your choose reboot into system now, it always reboots you right back into recovery, once you choose reboot into system the 2ND time it will boot you into the system, and everything else seems to work ok
maybe i should reinstall CWM? and see if that clears it up?
you could try, or you can odin to ed13 stock, take the update, then install cwm and see if it still does it
btw for the nooby noobs #12 should say "install zip from sdcard" not "flash zip"
so after removing that /intall-recovery.sh file it now only takes 1 reboot from recovery when you get into recovery via vol up method
however anytime you use a software recovery such as with quick boot or ACS updater, it still requires 2 reboots??
i've run out of ideas, maybe i glitched my phone during one of the installs??
right after i removed that /intall-recovery.sh file i rebooted to see what would happen, and it got stuck in the infinite droid boot ani (just like the first time i installed CWM) wiped factory/cache and rebooted and back to "normal"
and just a final thing i noticed, (since i'm just blindly guessing) during the install on step 11. where you say go into vol up recovery mode,(i start holding vol up + power) it will boot into the the first two screens 1. samsung.com screen then 2. samsung prevail screen, (meanwhile i'm still holding vol up) then it will reboot again 1. samsung.com + 2. samsung prevail THEN it will open the CWM
i corrected step 12 thanks for pointing that out.
those programs like acs updater are designed for cmw 3 and when they send the phone into recovery they probay script it so it reboots in to recovery after what ever it just installed finishes
you can test this to see what happens
on a booted phone that has adb debugging enabled and is connected to a computer that has adb.exe
perform this command
adb reboot recovery
phone should go into cwm, then do nothing but choose reboot system now, and let me know what happens
Last edited by hroark13; August 12th, 2011 at 06:56 PM.
The Following User Says Thank You to hroark13 For This Useful Post:
those programs like acs updater are designed for cmw 3 and when they send the phone into recovery they probay script it so it reboots in to recovery after what ever it just installed finishes
you can test this to see what happens
on a booted phone that has adb debugging enabled and is connected to a computer that has adb.exe
perform this command
adb reboot recovery
phone should go into cwm, then do nothing but choose reboot system now, and let me know what happens
just did it. booted into cmw. thanks for the instruction, worked great.
hey hroark do you thing gingerbread can be ported over the prevail by using the leaked samsung galaxy ace leaked gingerbread build?
i think that major problems with that, is that it is a gsm based phone
and we have cdma so all the drivers would be different. i am not sure if the prevail froyo drivers would work on gingerbread, and I am pretty sure samsung wont give them to us
our best hope is if a samsung cdma phone with a qualcom msm cpu gets gingerbread, it would be alot eaisier
i think that major problems with that, is that it is a gsm based phone
and we have cdma so all the drivers would be different. i am not sure if the prevail froyo drivers would work on gingerbread, and I am pretty sure samsung wont give them to us
our best hope is if a samsung cdma phone with a qualcom msm cpu gets gingerbread, it would be alot eaisier
but i have no experience with
Oh yea i forgot bout the cdma and gsm differences. But yea I noticed that those phones are very similar and i thought it might make porting roms and kernals easier
Last edited by moses166; August 12th, 2011 at 07:52 PM.
Device(s): LG Nexus 4, HTC EVO 4G Sold, LG Esteem Wifes, Samsung Galaxy Prevail, Samsung Nexus S 4G, LG Optimus
Carrier: Not Provided
Thanks: 196
Thanked 859 Times in 634 Posts
Quote:
Originally Posted by hroark13
i think that major problems with that, is that it is a gsm based phone
and we have cdma so all the drivers would be different. i am not sure if the prevail froyo drivers would work on gingerbread, and I am pretty sure samsung wont give them to us
our best hope is if a samsung cdma phone with a qualcom msm cpu gets gingerbread, it would be alot eaisier
but i have no experience with
Metropcs is getting ready to launch a new phone, the samsung admire. It is 2.3 gingerbread, I know it may not help right away but it is a cdma gingerbread samsung.
The Following User Says Thank You to new optimus For This Useful Post:
Metropcs is getting ready to launch a new phone, the samsung admire. It is 2.3 gingerbread, I know it may not help right away but it is a cdma gingerbread samsung.
depends on if it has touchwiz or not, if its touchwiz 90% of it will be useless.
on a side note we got bmlwrite working, so me and hroark will be working on a bat/script to install cwm, so our linux friends can join the fun
__________________
I dont ask for much, but my friend is going through some rough times,
if you wish to donate to me send it his way, he needs it more than i do Donate here
Know an unloved device? swing by our new forums
Metropcs is getting ready to launch a new phone, the samsung admire. It is 2.3 gingerbread, I know it may not help right away but it is a cdma gingerbread samsung.
depends on cpu it may have a samsung cpu in it
i think they are coming out with an HTC Broyce or something like that
Device(s): LG Nexus 4, HTC EVO 4G Sold, LG Esteem Wifes, Samsung Galaxy Prevail, Samsung Nexus S 4G, LG Optimus
Carrier: Not Provided
Thanks: 196
Thanked 859 Times in 634 Posts
Quote:
Originally Posted by hroark13
depends on cpu it may have a samsung cpu in it
i think they are coming out with an HTC Broyce or something like that
The cpu is qualcomm, ms7276? I think let me double check that and get back to you.
The bryce is an lg. and it will be called the lg esteem, it looks like a decent mid to high device too.
1ghz snapdragon cpu 512 ram 4GB internal storage 5mp auto focus rear cam with led flash 4.3 inch screen with 400 x800 res, I think thats the res not positive. LTE 4g Front facing cam, 1.3 mp I think, could be less though. possibly other goodies, I keep up with metro too. lol I had them for a while but could not stand the 1x speed now my wife has my optimus M
that by far is a great first android by the way.
Device(s): LG Nexus 4, HTC EVO 4G Sold, LG Esteem Wifes, Samsung Galaxy Prevail, Samsung Nexus S 4G, LG Optimus
Carrier: Not Provided
Thanks: 196
Thanked 859 Times in 634 Posts
Quote:
Originally Posted by new optimus
The cpu is qualcomm, ms7276? I think let me double check that and get back to you.
The bryce is an lg. and it will be called the lg esteem, it looks like a decent mid to high device too.
1ghz snapdragon cpu 512 ram 4GB internal storage 5mp auto focus rear cam with led flash 4.3 inch screen with 400 x800 res, I think thats the res not positive. LTE 4g Front facing cam, 1.3 mp I think, could be less though. possibly other goodies, I keep up with metro too. lol I had them for a while but could not stand the 1x speed now my wife has my optimus M
that by far is a great first android by the way.
OK I have to make a correction, the cpu information I thought I read is not correct, or more accurately there isnt any specific information, it is just listed as single core 800mhz, could be the same one the prevail has really.
Quote:
Originally Posted by hroark13
I was gonna make a new thread called Gingerbread dash, and get people all excited and when they click the link they see that game
OK I have to make a correction, the cpu information I thought I read is not correct, or more accurately there isnt any specific information, it is just listed as single core 800mhz, could be the same one the prevail has really.
sorry I messed that up for you
prevail is dual core with the msm7627 uses one core for modem/radio which is arm9 and the second core is for os/apps which is arm11
Playing around with Titanium Backup today and noticed that it has an option to create an update.zip file to install TB from CWM. I tried both scripting options, Edify and Amend and neither one worked. Apparently, our CWM will no longer recognize Amend scripts and gives instructions to use Edify, which is fine. But, the Edify script also aborts.
Playing around with Titanium Backup today and noticed that it has an option to create an update.zip file to install TB from CWM. I tried both scripting options, Edify and Amend and neither one worked. Apparently, our CWM will no longer recognize Amend scripts and gives instructions to use Edify, which is fine. But, the Edify script also aborts.
Is there a way to get this to work?
amend is old and outdated, cwm 2.x was last time it was used. as for teh edify it may not have the correct script made for it. if you pm me a copy of the script ill take a look. whats the error?
amend is old and outdated, cwm 2.x was last time it was used. as for teh edify it may not have the correct script made for it. if you pm me a copy of the script ill take a look. whats the error?
I also tried it after manually mounting /system and /data, and same thing.
Now, lazy me, not having a copy of winzip, I just used whatever zip comes with Win 7. I would have expected it to crash when opening the package if this was a problem.
Last edited by wyelkins; August 13th, 2011 at 12:21 PM.
After 1.1 was released I used Clockwork to partition my SD card. I could have sworn I selected a ex3 partition but I could have been mistaken. After the 1.1 didn't work I Odined back to rooted stock and just removed the bloat til shabby got everything all figured out.
I was reading about Link2SD and decided to install it and just screw around with it. After setting it up it asked me to select the type of partition I wanted to use and it gave me a list. At first I selected ex3 and it said something about no partition being there or my phone didn't support it. So after that I selected ex2 and it found the 500 MB partition I had made earlier with clockwork. I been using it ever since and its been working great.
I'm kinda confused about this. I am pretty sure I selected ex3 in Clockwork. What are the major differences between ex3 and ex2? Could they be so similar that one could be read by the other kinda like being backwards compatible? If I did select ex2 by mistake instead of ex3 does that mean that the Prevail is compatible off the shelf with ex2 since mine is only rooted with the bloat removed?
this is quoted from the shabbymod thread, but i think it would be good to discuss it here
i've been having a bit of trouble using a disk partition for link2sd and using a backup recovery with CWM
anyone know enough about these two (link2sd & CWM) to help?
btw shabby, if we can get a few kinks worked out you should totally include link2sd with your mod
what problems are you having with backup and restore?
still trying to narrow it down, (as we speak) but from what i can initially guess, is that link2sd seems to work best by creating a secondary partition (as a primary fat32) to store its stuff
CWM doens't like that 2nd partition when it comes time to backup/restore/flash stuff
i think it says "unable to mount /sd-ext" or something like that and just skips over it
even worse whenever i do a backup recovery i think CWM reformats the secondary partition as a ext3 ?? which then causes link2sd to break the connection (even though it says it supports it??? but it doesn't seem to work)
so basically every time you do a backup recovery or flash a new mod, CWM will change the format of the partition to ext3 which requires a link2sd user to reformat the same partition again to fat32 to re-establish the connection to link2sd
i'm not very sure about all of this because i'm testing stuff now, unfortunately i don't have a link2sd expert here to help me determine which end this problem could be easier to resolve from, so i'll just make CWM suggestions for the time being
Last edited by psp_noob; August 14th, 2011 at 02:47 PM.
still trying to narrow it down, (as we speak) but from what i can initially guess, is that link2sd seems to work best by creating a secondary partition (as a primary fat32) to store its stuff
CWM doens't like that 2nd partition when it comes time to backup/restore/flash stuff
i think it says "unable to mount partition" or something like that and just skips over it
even worse whenever i do a backup recovery i think CWM reformats the secondary partition as a ext3 ?? which then causes link2sd to break the connection (even though it says it supports it??? but it doesn't seem to work)
so basically every time you do a backup recovery or flash a new mod, CWM will change the format of the partition to ext3 which requires a link2sd user to reformat the same partition again to fat32 to re-establish the connection to link2sd
i'm not very sure about all of this because i'm testing stuff now, unfortunately i don't have a link2sd expert here to help me determine which end this problem could be easier to resolve from, so i'll just make CWM suggestions for the time being
well it may be that link2sd works with etx files system, but maybe our prevail kernel does not support ext, but I am not sure
i did not create cwm i just made a version of it for this phone, so I am not a cwm expert, but it sounds like it tries to use the first fat partition it finds, when looking for files to flash, and backup and restore and such
Last edited by hroark13; August 14th, 2011 at 03:02 PM.
well it may be that link2sd works with etx files system, but maybe our prevail kernel does not support ext, but I am not sure
i did not create cwm i just made a varsion of it for this phone, so I am not a cwm expert, but it sounds like it tries to use the first fat partition it finds, when looking for files to flash, and backup and restore and such
for those people that have two fat partions on sd
what happens when you are in android, and plug phone into computer and connect to USB Mass storage, do you see both partitions?
Device(s): LG Nexus 4, HTC EVO 4G Sold, LG Esteem Wifes, Samsung Galaxy Prevail, Samsung Nexus S 4G, LG Optimus
Carrier: Not Provided
Thanks: 196
Thanked 859 Times in 634 Posts
Quote:
Originally Posted by psp_noob
what is /sd-ext?
Extended partition if your kernel supports it android sees that ext3 formated partition on your sd card and reads it just like it is part of the internal memory.
29Likes
