My biggest issue that's bugging me right now is my home key(select) inside CWM is not working after flasshing VillainRom 3.0 . Has anyone ever had this happen to them? I've been browsing the forums for hours and can't find anyone with the same issue. I'm still searching.
I have been toying with my new SGS2 and I rooted it and tried out a few roms. I was anxious to try out VillainROM 3.0 for sgs2. I flashed the rom in CWM recovery. It booted up just fine. But now I can't make calls, connect to my carrier network/home network. My Menu/Home buttons don't work, back button works, search button brings up the menu... I've tried a few other roms and got the yellow triangle and was able to fix it by reflashing my backup in CWM using http://forum.xda-developers.com/showthread.php?t=1342728 .
I decided to stop looking for people with the same issue and try to get back to stock, I found this thread http://forum.xda-developers.com/showthread.php?t=1409634 . I'm crossing my fingers and hoping for the best.
That you can´t use the home button inside CMW, depends on the version you are using. The standard CWM version, does not support the homekey, therefore you can use the power putton.
You are in the wrong forum. You can't use I9100 roms on a Epic touch 4g device. Flash only roms for your device. That's why you can't make calls en buttons don't work anymore.
Thank you Lennyz1988. Anywho anyone who is dumb enough to try what I did can fix their problem with the link I posted in my first reply. I managed to get everything back up and running. I need to double check to make sure everything will work right next time I try out a new rom. I have had some success in flashing roms so far.
I was wondering if anyone could help me. My phone had froze and rebooted itself a couple of times which I didn't really think anything of until I replied to a text message and put the phone down, a couple of minutes later I saw out of the corner of my eye that the phone light had come back on. I'd noticed that the phone was rebooting itself again although this time it never got past the black boot screen with the "Samsung Galaxy S III" text in white on it.
My phone is rooted however I never bothered with custom ROM's etc. The only thing I did install was a volume hack package to increase the speaker volume as I kept missing calls because it was too quiet, this had been installed for months and I'd never had any problems with it.
The phone is running 'Stock Ice Cream Sandwich'.
Samsung told me that it sounds like the phone needs to be reflashed but because the phone had been rooted, they wouldn't touch it.
Is my phone now completely knackered? Is there anything I can do myself to get it to work again?
I might also add that I only have access to a Mac computer.
I'd be very grateful to anyone that could help me out as I'm now poor and can't really afford to lose the cash I paid out for this phone. :crying:
Thank you in advance. :good:
If you flashed a custom recovery when you rooted then you can reflash the latest stock rom for your country, read in general stickies how to do this. You should really have updated to this long ago, your phone is currently vulnerable to SDS.
If you have stock recovery then you need a pc with odin installed, I have no idea if this is possible with a mac.
The exact same thing happened to me a few months ago, the system partition just corrupted for no apparent reason - I just went to recovery and rolled back to a nandroid I'd made a few days earlier - it's been fine ever since.
s1mon87 said:
...
My phone is rooted however I never bothered with custom ROM's etc. The only thing I did install was a volume hack package to increase the speaker volume as I kept missing calls because it was too quiet, this had been installed for months and I'd never had any problems with it.
The phone is running 'Stock Ice Cream Sandwich'.
...
Click to expand...
Click to collapse
If you have already rooted your phone, you can easily flash the latest firmware corresponding to your country. This is the same way.
Your data were backup on your computer for example? If it's, you can start by cleanning the phone and try to restart it. For that, go to Recovery (Volume Up + Home + Power buttons) and do a "Wipe data/wipe cache". (In the menu, you can move up and down with the two buttons Volume et Select an entry with the Power buttun (by pressing, no holding it).
lelinuxien52 said:
If you have already rooted your phone, you can easily flash the latest firmware corresponding to your country. This is the same way.
Your data were backup on your computer for example? If it's, you can start by cleanning the phone and try to restart it. For that, go to Recovery (Volume Up + Home + Power buttons) and do a "Wipe data/wipe cache". (In the menu, you can move up and down with the two buttons Volume et Select an entry with the Power buttun (by pressing, no holding it).
Click to expand...
Click to collapse
CWM doesn't work anymore, I can only access the standard Samsung update thing (Volume down - power - home) I have no idea if I backed anything up to be honest, I just followed some instructions off this site to root it and it was months and months ago.
s1mon87 said:
CWM doesn't work anymore, I can only access the standard Samsung update thing (Volume down - power - home) I have no idea if I backed anything up to be honest, I just followed some instructions off this site to root it and it was months and months ago.
Click to expand...
Click to collapse
Flash stock rom via Odin .
You will need to search and find a Mac tutorial or borrow Windows .
jje
Help
Hey guys. I went to download the new cyanogen mod rom and and I installed the wrong gapps twice and but that didnt work and i went to a system restore and now i don't know to do. I need help ASAP.
ssingh0247 said:
Hey guys. I went to download the new cyanogen mod rom and and I installed the wrong gapps twice and but that didnt work and i went to a system restore and now i don't know to do. I need help ASAP.
Click to expand...
Click to collapse
Dont hijack threads
Read the basic faqs and guides before flashing all posted in General section .
Help
Never mind already fixed it.
Ok I know im a newbie...but went thru all the steps to root the device successfully
then I had 2.5 TWRP installed...i see the wipes there are two to perform before installing the cleanrom 2.0
so i go to do that..and I know the developer says to do a factory reset...but on 2.5 there is no button anymore to
do this..i looked thru each option..what am i doing wrong..so anyway, i do both wipes then chose the install
and clicked on cleanrom 2.0 ..it went thru a bunch of screens..and after a number of them nothing...so i waited 10
minutes...did a reboot and my device stayed on the opeing brilliant screen ...i could not even get into recovery to redo
the phone..i was ready to bring it back to swap it out as i bought it from costco..and would just play dumb
so I hooked it up to my power in car and that somehow made it turn off,, then i was able to go do a factory reset using
the backup and now phone is working..i'd still like to use clean rom..but kind of gunshy due to what happened...
anyone else care to shed some light...im sure it might have to do with not doing a factory reset...where is that option????
i see a factory reset in the list of options when i press power and vol down???? but i think they want the one in TWRP
Aroma installer may have frozen and didn't finish installing the Rom. Try it again. Make sure you verify the md5 just in case you got a bad download.
Sent from my HTC One using xda premium
abacus0101 said:
Ok I know im a newbie...but went thru all the steps to root the device successfully
then I had 2.5 TWRP installed...i see the wipes there are two to perform before installing the cleanrom 2.0
so i go to do that..and I know the developer says to do a factory reset...but on 2.5 there is no button anymore to
do this..i looked thru each option..what am i doing wrong..so anyway, i do both wipes then chose the install
and clicked on cleanrom 2.0 ..it went thru a bunch of screens..and after a number of them nothing...so i waited 10
minutes...did a reboot and my device stayed on the opeing brilliant screen ...i could not even get into recovery to redo
the phone..i was ready to bring it back to swap it out as i bought it from costco..and would just play dumb
so I hooked it up to my power in car and that somehow made it turn off,, then i was able to go do a factory reset using
the backup and now phone is working..i'd still like to use clean rom..but kind of gunshy due to what happened...
anyone else care to shed some light...im sure it might have to do with not doing a factory reset...where is that option????
i see a factory reset in the list of options when i press power and vol down???? but i think they want the one in TWRP
Click to expand...
Click to collapse
bro Cleanrom would NEVER brick your phone.. Scott is a beast at cooking roms.. He would Never make a rom that would do anything to your phone.. If u brick it its something u did not the roms fault
Nooblube said:
bro Cleanrom would NEVER brick your phone.. Scott is a beast at cooking roms.. He would Never make a rom that would do anything to your phone.. If u brick it its something u did not the roms fault
Click to expand...
Click to collapse
well i wouldnt be so sure,
I did an advanced wipe in TW recovery and wiped everything, then tried installing cleanrom 2.0. aroma froze at the first option and I cant get do anything, I cant hard reset. The lights at the bottom just flash. I let the battery die and now tried to get into recovery, just went to HTC screen, same thing. holding down any button just makes the capacitive buttons flash.
someone help out?
Edit: got into recovery with adb, should be good now
First, always check the MD5 checksum for any Rom, kernel, or mod that you intend to flash. It is a well documented issue that Aroma has a tendency to freeze up. Not always, but it does happen. I have flashed many roms, mods, and kernels from both the AT&T section, and the international section, and I have had smooth installs and freezes. If the phone is not responding, then press both the power button and the volume down button and hold them. When the capacitive buttons start flashing, keep holding the power and volumes buttons. Your phone will eventually reboot. When it does, keep holding the volume down button. It will take you into Hboot. If you miss it, power down the phone. Hold the power and volume down button to boot into Hboot. Select recovery and start over. When using Aroma installer use the volume keys and the power button to make your selections. This often helps prevent freezes, but not 100% of the time. It is something we just have to live with for now.
abacus0101 said:
Ok I know im a newbie...but went thru all the steps to root the device successfully
then I had 2.5 TWRP installed...i see the wipes there are two to perform before installing the cleanrom 2.0
so i go to do that..and I know the developer says to do a factory reset...but on 2.5 there is no button anymore to
do this..i looked thru each option..what am i doing wrong..so anyway, i do both wipes then chose the install
and clicked on cleanrom 2.0 ..it went thru a bunch of screens..and after a number of them nothing...so i waited 10
minutes...did a reboot and my device stayed on the opeing brilliant screen ...i could not even get into recovery to redo
the phone..i was ready to bring it back to swap it out as i bought it from costco..and would just play dumb
so I hooked it up to my power in car and that somehow made it turn off,, then i was able to go do a factory reset using
the backup and now phone is working..i'd still like to use clean rom..but kind of gunshy due to what happened...
anyone else care to shed some light...im sure it might have to do with not doing a factory reset...where is that option????
i see a factory reset in the list of options when i press power and vol down???? but i think they want the one in TWRP
Click to expand...
Click to collapse
If the ROM were to blame, then everyone that flashed it would be bricked, which is clearly not the case. It is completely irresponsible to create a thread titled "rom x almost bricked my phone" and on top of that, you start your first sentence with, "Ok I know im a newbie". Especially with all the very well known Aroma issues on this phone which is independent of the ROM. OP, your thanks meter will probably stay at zero for a while.
Yeah do not blame cleanrom for something you did wrong. I'm running it right now and it is fantastic and perfect for what I want right now. And it installed without a hitch.
Sent from my HTC One using Tapatalk 2
Not the rom. But aroma. Aroma installer is buggy
Bricking is like horseshoes. there is no close. you are bricked or not. A soft-bricking is a different story and the term brick is probably over used there too
As to wiping under TRWP 2.5.0.0, some options have been moved below the Advanced menu.
BTW, Cleanrom 2 is SWEET and worth the effort. Good luck
Hi, I have a Sprint Samsung s3, currently rooted with cm10.1. I've been having the freezing problem like a lot of people I've seen on here, but none of the suggestions helped me out. I tried to flash the rom to a older version on cyanogenmod (10.0). After that my phone would not even go pass the bootloader screen. I've tried to hold volume down and power button to go into recovery screen but it doesn't do that anymore, maybe it is because I don't have cwm because I am using twrp instead.
Any suggestions on how to get pass the bootloader screen?
Also any suggestions on how to fix the freezing problem?
The freezing problem only happens when I play games and only last for about 3 mins but it starts freezing again within 2-3 mins of playing time. I've already tried lagfix app, full wipe, dummy file generator app but to no success. Someone please help!
Try posting in the Sprint forum this is I9300 .
jje
vizi0nz said:
Hi, I have a Sprint Samsung s3, currently rooted with cm10.1. I've been having the freezing problem like a lot of people I've seen on here, but none of the suggestions helped me out. I tried to flash the rom to a older version on cyanogenmod (10.0). After that my phone would not even go pass the bootloader screen. I've tried to hold volume down and power button to go into recovery screen but it doesn't do that anymore, maybe it is because I don't have cwm because I am using twrp instead.
Any suggestions on how to get pass the bootloader screen?
Also any suggestions on how to fix the freezing problem?
The freezing problem only happens when I play games and only last for about 3 mins but it starts freezing again within 2-3 mins of playing time. I've already tried lagfix app, full wipe, dummy file generator app but to no success. Someone please help!
Click to expand...
Click to collapse
Flash a stock ROM with odin and see if that fixes anything.
Well, my problems with recoveries are sorta of a jokle by now, but I still feel compeled to share my experiences so maybe anyone can tell me what the hell is happening on my phone....
So as I said some time ago, I experienced problems with the PhilZ recovery, which I solved swapping to CWM version 6.0.3.2. The problem was the infinite bootloop of the Samsung Galaxy GT-I9300 logo, the black screen, which did not allow me to access to the recovery. But inmediatly after flashing to the old CWM the problem was gone away. Also, in a case of a possible kernel panic due to doing some stuff with Xposed modules CWM was the only recovery I could get access into.
Now, the problem is the following. Yesterday I installed the CWM Touch version 6.0.4.7, which I got from this thread http://forum.xda-developers.com/showthread.php?t=2052091. After installing it everything was normal. However, after one hour or so the phone screen wouldnt turn off when I pressed the Power Button. In fact the Power Menu appeared, but the screen, as I said, dindt get to sleep mode. To top that, after freezing for a second the phone suddenly turned off, and then get to the infamous black screen with the model logo looping and looping.
Fortunately, after pressing Volume Up+Menu+Power I could get to the Recovery, but not after quite some seconds pressing these three buttons. And in some times it would not get me to the recovery, but instead completely rebooting the phone and working again. Just to, in half an hour, freezing and looping again and again and again.
This problem happened to me with virtually every ROM I installed, being Neat ROM, Archi, and even CM11 from Temasek. Nothing would solve that problem. The only remedy I had was a temporary one, which consisted on uninstalling and reinstalling again the kernel (I used boeffla) and the problem would not disappear that way. Also, when wiping data, for some weird reason it gave an error message while wiping the /preload partition, in the Mounts and Storage menu.
Until I got home today, and then flashed through Odin the old CWM Touch version 6.0.3.2, that finally stopped the problems. I tested it by pressing the Power buton again and again and it hadnt redirected me to the black bootloop screen. Seriously, I am wakelocking my phone on an intensive basis and nothing has happened for now, and I think it probably wont happen again. Maybe it takes three seconds, maybe the Power Menu displays again, but no bootloop again.
So I ask to you, what is happening on my phone that it wont run recoveries younger than my old 6.0.3.2
IMPORTANT EDIT: THE PROBLEMS ARE NOT SOLVED YET
Some hours ago, I was chatting using Whatsapp while charging the phone on an USB charger, when it suddenly suffered the black screen bootloop again. This time was unexpected, since I was using the CWM Touch 6.0.3.2, the one supposed to work fine. So for now I feel completely finished. My phone is officialy into a unsolvable problem.
But, thinking about it, there were some things that might help you:
-This time I did not uninstall and reflash the kernel: When I got to the recovery menu, I just selected "reboot", as such, without flashing anything else, and the phone then worked as fine, booting into the ROM bootanimation screen (this time the Neat ROM bootanimation). So basically a manual reboot through Recovery got me out of this. Also, I kept using the phone until now and there werent more problems, at least for now.
-As far as I can recall, these problems started some weeks ago, when I accidentally formated the internal SDcard. I was using PhilZ Touch Recovery and flashing a ROM as usual, when I selected without knowledge the option "Format /data and /data/media (sdcard)" in the Mounts and Storage menu. I did this after doing the usual Full Wipe before flashing an new ROM, and after that I had to turn off the phone in order to insert a ROM in the external SD card to flash it through the recovery to make the phone working again. But when I wanted to get back to the recovery, I couldnt. I had to flash CWM 6.0.3.2 because it was the only recovery that let me access to the recovery menu-the already installed PhilZ wont allow me to access to the recovery menu. So in CWM I got to the External SD card and flashed a Neat ROM, and got the phone working again. And after that I reflashed PhilZ. But since then the phone started to experiment these freezes, reboots and bootloops. One happened to me when in College, and couldnt get out of it because PhilZ wont respond to the Manual Recovery command. I had to wait to get home, to reflash the CWM 6.0.3.2 recovery through Odin because that Recovery was the only responding. And in that moment it did well, and didnt have more reboot problems. Until I flashed 6.0.4.7, which is why I am here.
-Lastly, about the reason I trust in CWM 6.0.3.2: Some time ago, when flashing Blackbox ROM 2.0.2, I downloaded the Gravity Box module from Xposed, and installed it alongside with other modules, which, supposedly, caused a kernel panic problem that sent my phone into the dreaded black bootloop again. I was using PhilZ recovery, and as you may expect now, I couldnt get access to it, so I flashed the CWM 6.0.3.2 recovery, which let me access to a recovery. I too flashed TWRP, but it accessed for one second to the recovery menu, and then faded away, returning to the bootloop logo screen. So basically PhilZ and TWRP failed me during that kernel panic problem, while CWM stood the problem. And thats why I turn to this recovery when everything else fails.
And thats why I am troubled now, because this recovery is showing signs of failure
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
andrewwright said:
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
Click to expand...
Click to collapse
I used 6.0.4.7 and I had the problems previously described....I mean, I used a more updated version than the one you propose. Do you believe its gonna work better?
And thats why I will stick to 6.0.3.2 until someone tells me whats happening. If an updated version of 6.0.4.4 gives me problems...well, go imagine.
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
andrewwright said:
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
Click to expand...
Click to collapse
Interesting. And where do I get the 6.0.4.4? I dont see it neither in the new CWM thread nor in the old one.
Look down
here. zip so just flash in recovery
andrewwright said:
here. zip so just flash in recovery
Click to expand...
Click to collapse
I apreciate your help, but now some new problems have emerged, and I need more help, because maybe I might have a corrupted partition or such, who knows.
With this quote, I too try to bump the thread, in order to gain more attention to my new problems
If anyone is interested, please look the OP, as it has been edited to describe the new problems.
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
andrewwright said:
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
Click to expand...
Click to collapse
I will try that in a few weeks, I am a bit busy by now to test anything...
Fortunately, the CWM 6.0.3.2, while not infallible, works better than the other recoveries...today I only had one bootloop problem, solved by simply rebooting from the recovery....I can keep it for one week or two, it doesnt worry me for now.
Also, there is a guide to reflash stock? Sometimes I reflashed stock, but it kept bootlooping on the Samsung animation...probably because I didnt know how to wipe data while reflashing stock. Thats a little problem I have with reflashing stock, any help is appreciated.
Odin wipes the phone while flashing. What rom are you on? Custom
Well, I have to bump this post again because I am having the same problems again.
I am using CWM 6.0.3.2 as my current recovery. Today, I was browsing the Facebook app when I pressed the Power Button. Then, a lag of 2 seconds happened, the Power Menu displayed on screen, and the phone got into the black boot screen again. But this time I could not get to the recovery. Whenever I pressed Volume up+Power+Menu there appeared a black screen featuring the CWM logo and then it returned again to the black boot screen again. So what I did was to remove the battery, then eject the Exterior SD Card (A Lexar, 32 gb) and put again the battery in its place. The phone started all normal again, and when I put again the SD Card it continued to work normally.
So, what do you think its happening? Not even my old recovery, the one which works better for me, is reliable anymore. Could this be a component of my phone failing? Particulary the emmc chip? Or its not a hardware problem? Should I sent the phone to reparation?
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
andrewwright said:
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
Click to expand...
Click to collapse
I have almost 29 gb on the sd, but I had that data since the very first day I bought the card....thats more than one year ago. And I started having the problems since february of this year....
The problem has not reappeared. But what I still have is an insane battery consumption. See, I use apps like Facebook and Twitter, but I too use Greenify to hibernate them. It even drains too much battery by using the web browser. And I repeat, those problems trace back to February...which is the month when I accidentaly formatted the internal SD Card...
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
andrewwright said:
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
Click to expand...
Click to collapse
Thanks! Whenever I can, I will try those tips for battery saving.
But what still puzzles me is the "Sudden reboot problem". It vaguely happens, but when it does I am basically screwed, and each time the reboots seems to get worse from recovering....Also, the reboot problems started after formatting the int sd card for first time. And, after that, I remember that, when I wiped data for installing a new ROM, it gave me "(E: unknown volume for path [/sd-ext])" or, something similar. Does this help you for identifying my problem?
OK, now I am royally screwed
I have suffered another sudden bootloop problem, and this time, even by removing the ext SD Card, phone doesnt restarts. Also, I cant access to the Recovery Menu. It does appear for a while and then fades away. But the worst part is that I cannot get into the Download Menu. When I get to the select screen, when I cant choose between Continue and Cancel, the Volume buttons doesnt work. I can not get into Continue button. And then it restarts.
So this time I can not even access to the Download Menu.
I am using the same ROM as before: Neat ROM 6.7 with CWM Touch 6.0.3.2 and Boeffla Kernel
I dont know if I can even send the phone to repair, as seen that I may have the Binary Counter...and I cant even access to Download.
Please, really, help me to get out of this, so I can factory reset this.
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
andrewwright said:
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
Click to expand...
Click to collapse
I did that, and I got into the Download Menu. But the menu was frozen as usual. I could not access to the Odin Menu. It didnt matter which option I chosed, since both of them didnt work and the menu would still be frozen, and then restarting the phone a few seconds later. I mean, I got to the screen where you can choose to get to Download Mode or to restart the phone, and it still was a stuck screen, no matter what I chose, the options did not work, and then the phone restarted again.
And I have no jig next to me. So, I am screwed. For real.
Im going to take it to the store where I bought it, which is near where I live...To see if they can do something. Otherwise...I think I will throw away this phone. Its been almost 2 years, and recently it started to fail, probably because of a crappy emmc chip...that store sells the Moto G, which is great, since I dont plan to waste a lot of money on a new phone, watching how this has ended.
And it sucks that I can not recover the data in the Internal SD