I tried updating my ROM (to CM11) and came across so many issues. For some reason, it kept rebooting and then at one point just got stuck at the animation screen. So I decided to just start everything from scratch again.
I tried to get into download mode to install CWM, but the phone kept shutting off as soon as I got in. After MANY tries, I finally got in and got it installed. When it finally worked, I tried to get into recovery mode and the same thing happened. Finally after many tries I was able to get in there too. I then installed my ROM and then when it finally loaded, the phone then shut off and tried rebooting but wouldn't get passed the animation screen again.
I did a lot of research and found that some people had their internal power button either get stuck or become defective. Mine clicks so I don't know if that's the problem, but the symptoms that others have mentioned have all happened to me.
Does this in fact sound like a button issue to anyone? Any help is appreciated.
moraha1287 said:
I tried updating my ROM (to CM11) and came across so many issues. For some reason, it kept rebooting and then at one point just got stuck at the animation screen. So I decided to just start everything from scratch again.
I tried to get into download mode to install CWM, but the phone kept shutting off as soon as I got in. After MANY tries, I finally got in and got it installed. When it finally worked, I tried to get into recovery mode and the same thing happened. Finally after many tries I was able to get in there too. I then installed my ROM and then when it finally loaded, the phone then shut off and tried rebooting but wouldn't get passed the animation screen again.
I did a lot of research and found that some people had their internal power button either get stuck or become defective. Mine clicks so I don't know if that's the problem, but the symptoms that others have mentioned have all happened to me.
Does this in fact sound like a button issue to anyone? Any help is appreciated.
Click to expand...
Click to collapse
Seems like your hardware button could be broken, I would all do in this order:
Download Philz Touch Recovery from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300/
Official Firmware from here: http://www.sammobile.com/firmwares/3/?download=28378
Flash Philz touch through Odin
Reboot to Recovery, selct "Clean to install a new rom"
Wipe cache and dalvik cache
Go to downoad mode and flash the md5.tar file through odin
Related
I recently installed a gingerbread rom Lidroid. it was working ok till i realized i could not stand some bugs. I decided to try cyanogen that was released today. It looked like it installed fine but the phone is stuck trying to install clockwork recovey. it keeps going on and looping at the same screen. the last message it shows before it reboots off is "Replacing stock recovery with Clockworkmod" it just keeps looping doing the same thing. I have tried to get into download mode without success. I have been able to put my phone in download mode the past couple times i have run into trouble. Now i simply cant be able to do it. Any help?
I dont know how it happened but after trying for the past 5 hours, i have been able to get it to work. I took the battery out inserted it back in. I held the volume down button and the power button together. i immediately plugged the phone into USB cable while still holding Vol down and power button. After 10-15 seconds, it brought up the clockworkrecovery. I Wiped everything and the cache. I then tried to reinstall cyanogen(the one that brought all this in the first place) because it was the only one on my sd card. It installed and booted up and now i have CM 7. I can also successfully get into Download Mode
Am not sure what i did, but if anyone can run into such a problem you might try this.
hello, my name is shahrukh and i need some help. i downloaded animmod (from 4shared) and then i donwloaded busybox. then i pressed blur and then it asked me if i want to reboot it. i pressed yes. this is when the problem starts. It turned off and then it turned on half way and then it turned off. it kept doing that and then i just left it for the night. in the morning it was not doing anything. when i held the power button it turned off and on for like two times and then turned off. i cant even start it up so i have no idea what to do.
i don"t know what to do
please help!!!!
Okay, we need details, describe exactly when "halfway on" is. We need your full model number and rom version (if you know it). Have you tried plugging it in to charge? Does it show anything now that you try to boot it? try holding volume up and powering on to enter recovery menu.
details
ok so when it turns on it says samsung. then after like 10 seconds it turns off. it does that for a few times and then it just goes in a black screen. the model number is YP-G7OC/NAW. when i plug it in to charge it goes on and off two times and then off. if it has low battery it just shows the sign. as for the rom i don't think i have any. i just rooted it using superoneclick. if it goes to recovery mode what do i do?
thanks!
(you got me really fired up when i saw the recovery menu!)
If you can get to recovery menu, try a factory reset, and clear cache. I am not sure if there is a recovery rom for your device, you should check samfirmware.com
tried both of them...no luck. and i couldn't find a recovery rom on samfrimware.com.
Your device has capacitive or mechanical home button?
it has a capacitive home button...the usa version
shahrukhraza said:
it has a capacitive home button...the usa version
Click to expand...
Click to collapse
The phone boots in recovery?
If so, I can investigate a little more what's happening.
I'll try to post a return-to-stock image soon... The problem is that mine is cluttered with crap that the zergRush exploit added (it insisted on installing busybox instead of just rooting...)
(I'm not sure, but I think someone else already posted a stock zImage and system image...)
Here is the post about fixing capacitive buttons. A quick search of forum should have found it.
http://forum.xda-developers.com/showthread.php?t=1421797
Sent from my YP-G70 using Tapatalk
nooooooo!!! you guys have all got it wrong. first of all it doesnt boot in recovery. the only way to get in recovery mode is when it shows the battery sign i hold "up volume"+ power button.and the capaciative button is completely fine. im just stuck in a bootloop (i think) and it has nothing to do with a broken capacitive button! i will try to post a video today to show you guys exactly whats happening.
i kind of had the same problem, one time i thought i had entropy's kernel on and i had CWM well i didn't but i still thought i had so i tried rebooting into recovery using the terminal:
su
reboot recovery
then i turned off and went to this weird recovery menu it had four options, reboot system, apply update from SD card, wipe data partition, and power off and it had a ton of red letters and words saying like, couldn't access data partition or cache partition and couldn't access /data/media, or system, and then i just turned it off because i wouldn't let me choose an option, and then i got stuck in a loop but not during when it says SAMSUNG mine happened during the animation music part that look like fireworks and then SAMSUNG would light up blue then go through it again and 2 more times then go black and i tried flashing the US stock ROM in download mode but still would go through the loop and it doesn't even charge so i got nothing
so did you somehow fix yours? and i never got a recovery menu that showed something about shut down.:confused
Before brick
xxxxxxxxxxxxxxxxx
wait....are you asking me those questions? just to tell you im no developer or something. im just a 12 year old who has his galaxy player stuck in a boot loop. you have to make another thread if you have a problem.
sorry!
Ok. : ) You got it wrong. No problem. His case is different from mine. Just wanted to use her Brick in case. Nothing more. good luck.
I resolve my doubts alone. Nothing that Google does not respond. haha
At least before brick.
ok. let me ask google too xD
anyways..anyone have any idea of how to fix this boot loop?
im trying to do the Linux thing by running the ressurector ans the VM windows the forum is posted under development called hard brick recovery for galaxy 5.0
ok.(i have no idea what you are saying...just saying!)
Here's my situation, maybe someone will find it interesting or know what's going on. I was running the EOS Jelly Bean (EOS-tf201-20120728-31.zip). Everything was running pretty well for a few days, then yesterday the device simply powered off. When I rebooted it got to the splash screen then shut off before it could get any farther. I figured it was a power issue, so I plugged it in and charged it for a while but get the same response. Around this point I started to get suspicious and tried to boot into recovery. It got to "Booting Recovery Kernel Image" then powers off the same way.
So then I proceed to go into fastboot and fastboot works great no power offs. Through that I am able to flash openrecovery-twrp-2.2.1-tf201.blob and the virtuous packaged boot as per this thread http://forum.xda-developers.com/showthread.php?t=1773280 as well as factory reset. I also tried a few other boot/recovery combinations and was able to make it into recovery. In twrp recovery I was able to install the latest Virtuous rom which got me back to stock and I thought good case closed. I even made it all the way into the OS and was able to install apps, wifi worked great, run the apps etc. Eventually the screen went blank though and I was stuck back in the same shutdown on boot scenario as described above. Now I'm able to fairly consistently flash openrecovery-twrp-2.2.1-tf201.blob, reboot, get into teamwin recovery, but now even that appears to be randomly powering off.
So now I'm guessing that it may just be bricked and is probably a hardware issue since the reboots appear so random, the unit was refurbished. At the same time I'm still holding out some hope that it's simply some boot code somewhere that was corrupted and I can flash something and get things back to normal again since I can still access fastboot and occasionally ADB and recovery. I've flashed from fastboot system/recovery/boot, any other thoughts or potential combinations I could try? Also anything I can do with those tools to debug it further and get more data on what may be the root cause?
Hello everyone!
I have a Lenovo a820 with Lambda rom 2.4v.
I'm using it for a couple of weeks now with this last version, and everything was fine, until suddenly it froze for a while, I unplugged the battery and plugged it again, and what I notice was that the phone restored itself to when after I installed the rom (meaning all of the apps were gone).
So I tried going into Google play, installing some apps back, and I get this error -24 telling me its unable to install the app, happened with any app I tried. so after trying a few suggestions from the internet about this error, I decided to format it and install the rom all over again.
I go back to recovery mode with CWM, try to install the lambda rom like I did before, and in the middle of the installation it reboots and gets stuck in the "lenovo" screen like when you boot it. so after waiting for a long time I unplugged and plugged the battery again, went through the procedure again this time it installed it 100% rebooted so it would boot with the mod, and again, it freezes at "lenovo" start screen unable to boot.
went on recovery mode, formatted system, data, emmc, everything... I think that's the issue here. but im not sure.
After that, tried to install again with the same problem.
The problem now is. it won't even start I press the on/off button to start it normally, and I dont even get the "lenovo" screen, I tried going into recovery mode and no luck.
It's like the phone is dead! Although I have another Lenovo A820 and I tried the battery, and its 60% so that's not the battery.
Do you guys know any tricks? or any tools that I could use to get my phone running again?
I would appreciate it very much, any help you can give.
Matt.
MatWho said:
Hello everyone!
I have a Lenovo a820 with Lambda rom 2.4v.
I'm using it for a couple of weeks now with this last version, and everything was fine, until suddenly it froze for a while, I unplugged the battery and plugged it again, and what I notice was that the phone restored itself to when after I installed the rom (meaning all of the apps were gone).
So I tried going into Google play, installing some apps back, and I get this error -24 telling me its unable to install the app, happened with any app I tried. so after trying a few suggestions from the internet about this error, I decided to format it and install the rom all over again.
I go back to recovery mode with CWM, try to install the lambda rom like I did before, and in the middle of the installation it reboots and gets stuck in the "lenovo" screen like when you boot it. so after waiting for a long time I unplugged and plugged the battery again, went through the procedure again this time it installed it 100% rebooted so it would boot with the mod, and again, it freezes at "lenovo" start screen unable to boot.
went on recovery mode, formatted system, data, emmc, everything... I think that's the issue here. but im not sure.
After that, tried to install again with the same problem.
The problem now is. it won't even start I press the on/off button to start it normally, and I dont even get the "lenovo" screen, I tried going into recovery mode and no luck.
It's like the phone is dead! Although I have another Lenovo A820 and I tried the battery, and its 60% so that's not the battery.
Do you guys know any tricks? or any tools that I could use to get my phone running again?
I would appreciate it very much, any help you can give.
Matt.
Click to expand...
Click to collapse
The boot.img must be wrong try rom for your phone.
Sent from my Moto G
I have a vankyo matrixbox x95 plus that I turned into a retro gaming center. Anyway, I asked how to make emulators close when I pressed the home button and was told Tasker and supersu. I installed supersu and it said that I needed to update. Did that and have been stuck in boot loop since. For the last 3 hours I have been trying to get it to boot. Tried resetting to factory 1000 times, didn't work. Tried flashing another supersu zip file, read about it in another group, didn't work. Instead it just said "bad recovery detected no unzip". Hunted down, what I hope is, the original rom and tried to flash and it says the same thing "bad recovery detected no unzip". Please someone shed some light on this I'm going crazy
Keep trying different freshly formatted usb thumb drives until it works properly again.
Days later and still in boot loop hell. So glad I installed supersu and turned my box into a paperweight. Got firmware from here and followed the directions for burning tool, doesn't work just errors out after 1 percent. Then I tried a bootable USB, can't get it to boot. Ahh the joy