I've been having problems with random restarts, apps closing, etc. and decided to try to leave the beta program. Was trying to copy some files that weren't backed up to USB and the phone suddenly bricked. It's like it was in a restart and never completed. I have the SAMSUNG
Galaxy
screen frozen there but can't shut the phone off or do anything.
Any recommended steps short of a hammer?
Flashing the stock firmware usin HOME_CSC can help as it will not wipe the internal storage if I remember correctly
Resolved. With the phone attached to the charger, press and hold volume down and power buttons unlocked the phone and started a reboot.
Related
So basically, I registry hacked my PC so that I could update using the official 2.2 update in Kies for the Galaxy S.
Since I updated it, the phone has come unusable. Whenever it boots up I am plagued by force close messages (calendar storage, media, memo etc.).
I’ve tried getting into safe mode and hard resetting it. I can’t get either of these menus up. Tried holding down [vol down] key and pressing the power button, it just boots as normal when I do this.
Anyone have any ideas what’s wrong here?
I have the same problem as well, except that I am in a Scandinavian country. I did remove the lagfixes, and the only thing left was the rooting. I heard that the USB disconnected and reconnected in Windows under the firmware upgrade. When the smartphone was booted up, it still appeared to be 2.1-update1. So I did a hard reset, and that's where it begun to be softbricked with all the looping crash messages ("The process X has stopped unexpectedly. Please try again."), which are the following processes:
android.process.acore
com.sec.android.app.twlauncher
com.sec.android.provider.logsprovider
com.cooliris.media
com.android.calendar
com.sec.android.widgetapp.infoalarm
com.android.phone
alexdrans said:
Tried holding down [vol down] key and pressing the power button, it just boots as normal when I do this.
Click to expand...
Click to collapse
you have to hold down both [vol down] + [start] and then press the power button to start the phone in download mode. [vol up] + [start] and power to get into recovery mode. in all there are three buttons involved which have to be pressed all together. [start] is the big one on the front side of the Galaxy btw.
I had similar problems with the Kies update. So i wiped it clean, installed an old 2.1 version with odin and then installed on of the modifed 2.2 version from the development section here, also with odin. Now it works like a charm and with OCLF blazingly fast too.
I am experiencing the same problems...
how would i go about wiping the phone clear and back to the 2.1 version?
i only got the phone the other day and can barely use it now!
cheers
Guys i didnt wanted to open up a new thread so ill go ahead with my problem here.
The question is about the Kies Registry Patcher so i can force Kies to show me the 2.2 update.
My native country is Macedonia, and i can see two options to pick from with the Kies registry patcher for my country. One of them is the current versions i have on my phone and its representing the 2.1 update 1 android version.
To what 'Spoof Product Code As' i should set the registry patcher considering my location to get the proper update for my phone ?
alexdrans said:
So basically, I registry hacked my PC so that I could update using the official 2.2 update in Kies for the Galaxy S.
Since I updated it, the phone has come unusable. Whenever it boots up I am plagued by force close messages (calendar storage, media, memo etc.).
I’ve tried getting into safe mode and hard resetting it. I can’t get either of these menus up. Tried holding down [vol down] key and pressing the power button, it just boots as normal when I do this.
Anyone have any ideas what’s wrong here?
Click to expand...
Click to collapse
Have you tried click settings on your phone then privacy then factory reset that should solve it
Well, I had the same issue and here is what I did. I'm in Canada (not sure which thread my phone falls under as our Vibrant is not the same as the U.S. one) and my provider is Bell Canada. Well...what I did was this; I saw the update out there, so I connected through Kies, ran the update and waited nervously for it to boot. After it did boot, I got several Force Close errors, so I rebooted it. It came up more easily the second time. After it got done it's card scanning and crap, it was ready to go. BUT...I started getting random Force Close errors with different apps. I simply could not use ANY email app other than the GMAIL one itself, they just kept crashing. Handcent crashed too, but with a reboot would work. Well...this just didn't seem right as a college of mine did his at the same time and was working fine. So, today I did this; I copied ALL my useful data off the internal SD onto my external SD and then removed that external SD card. Then I formated the interal SD. Then I went and did a factory reset. After that, my phone worked perfectly! I put my external SD card back in and all is good now. Haven't had one error since. Now, before I did this, I'd get at least 1-2 Force closes per hour but I re-did my phone up about 3 hours ago now and like I said, no errors.
Maybe try this before you update:
1: Save old data off of Internal SD
2. Remove External SD card (just to be safe)
3: Format Internal SD card
4: Apply Froyo update
5: Reinsert External SD card upon completion and sucessfull reboots
6: Part-tay!!!!!
Just make sure you do a cache wipe and a user settings wipe.....you should have already backed up your stuff so worst case you will just have to reinstall everything. HOLD down Volume UP button, Home button and power button all at once, it will boot into recovery mode, use the volume rockers to select wipe cace and then use them to wipe the user settings, reboot and should be good.
Hello everyone,
I seem to have a problem upgrading my GT-N7000 to JB, the phone downloaded a 494MB update, and restarted to FOTA mode.
The progress bar went from 0-100% in about 15-20mins, but the phone has since then not completed the FOTA.
If I restart the phone by long-pressing power key, the FOTA restarts, but again gets stuck at the 100% mark. Pressing Vol Keys and powering on makes no difference.
Further the phone isn't recognised in Windows - says 'Device Malfunction'. The cable is fine, as it works with another phone.
My bad luck it was, the phone data isn't backed up - I never expected anything to go wrong. Is there a remote possibility of data recovery before I wipe the phone?
Now, how do I get back access to my phone, and how do I complete the upgrade, or reset the phone? I would be grateful if you help me or guide me how to proceed. Taking it to the service point would be the last resort, I want to try out everything I can before I send this in - it's out of warranty.
Regards
Abhishek
AbhishekKr said:
Hello everyone,
I seem to have a problem upgrading my GT-N7000 to JB, the phone downloaded a 494MB update, and restarted to FOTA mode.
The progress bar went from 0-100% in about 15-20mins, but the phone has since then not completed the FOTA.
If I restart the phone by long-pressing power key, the FOTA restarts, but again gets stuck at the 100% mark. Pressing Vol Keys and powering on makes no difference.
Further the phone isn't recognised in Windows - says 'Device Malfunction'. The cable is fine, as it works with another phone.
My bad luck it was, the phone data isn't backed up - I never expected anything to go wrong. Is there a remote possibility of data recovery before I wipe the phone?
Now, how do I get back access to my phone, and how do I complete the upgrade, or reset the phone? I would be grateful if you help me or guide me how to proceed. Taking it to the service point would be the last resort, I want to try out everything I can before I send this in - it's out of warranty.
Regards
Abhishek
Click to expand...
Click to collapse
Dont worry. In general your personnel data are stored in internal SD and external SD, not disturbed by a system install process.
In that situation you'd better to install a new JB4.1.2 ROM using Odin in download mode.
Firstly see what ROM to be flashed. Official stock ROM, custom ROM, download it.
Read how to use Odin in download mode by connection USB PC-phone.
Odin is utility under PC. Download mode on the phone is entered after hold in the same time volume-down, home and power.
I'm sorry if this has been answered before, I searched but wasn't able to find anything.
It started when my phone suddenly didn't recognize the sd card. I took the card out and put it back in a couple of times, and reebooted the phone a couple of times. After that didn't work, I figured I would factory reset the phone, and as I did, it started to reboot, but was never able to boot back up.
When I now try to boot the phone, I get to the initial Samsung-S4 Active GT-I9295 -logo, and it says BOOTING RECOVERY in the top left corner, but after ~2 seconds it shuts off.
Interesting: It only boots a couple of seconds after I let go of the power button.
The phone was rooted using this guide: (not able to post links. The guide is on android geeks, and can be found by searching for Root Galaxy S4 Active (International I9295 and AT&T I337 models))
And Xposed was installed, but no modules were activated.
Firmware was 4.2.2 MF/MU 3 - something, I think. Sorry I cannot remember. I got it OTA some two weeks ago.
Any suggestions?
Thank you!
EDIT: When playing around with it, I managed to solve it. When booting, as soon as the logo appeared, I pressed and held the volume up + home button, which caused it to not shut down (?). It then preceeded to boot for a long time while, I guess, the phone was factory reesetting itself. Now it boots just fine, factory reset =D . (SD card still not detected )
Hi All,
Sorry if this is asked before. I have a new Note 5 unlocked. I turned it on yesterday and started using it. Late at night, its screen froze. I tried pressing Power+Volume_Down buttons to restart the phone. The phone restarted but the the screen was black. Only the notification light was on (blue).
In the morning, the light was still on and the phone was froze. I tried restarting it and I succeeded it. Then I realized the phone was very, I mean veeeery slow. By the time, a firmware update notification popped up. I believe it was Marsmallow update. I hit the yes button. The phone started the update and was stuck at %24. Then it restarted itself. The update process starts over and when it reaches %24, it starts over.
This happened before with my note 4 when I tried to root it. This phone is brand new and is not rooted. However, I transferred my Google profile but I did not select to download my previous apps. So, I don't think it is rooting issue but stucking at the same percentage makes me nervous.
I tried to get into recovery mode but the button combination does not work at all. So I can neither factory reset nor clear the cahe partition. When I press Volume_Down+Home+Power buttons, a custom rom download screen appears but Volume_Up+Home+Power buttons do not work at all. I cannot shut off the phone. It constantly restarts itself, starts the update, fails at %24 and starts the process over again.
What might be the problem? How can I fix this?
Regards
Hi,
Try flashing some stockfirmware via Odin (ideally something of the same android version i.e. lollipop/marshmallow). Once it's installed you should be able to access recovery from which I strongly recommend clearing your cache afterwards as you've already suggested. If you are not worried about loosing any data, then flash new firmware that is inclusive of BL/CP/CSC files too (each one has a category for such in Odin). With the latter, by all means flash marshmallow etc. :good:
Regards
This is my first post, but I've had my phone rooted for a few months now with no problems until today out of the blue. What I've done to root my phone in the first place was flash to 4.4.2 NE3, root it, then upgrade to 5.0.1 OC 7 DeOdexed while keeping the root according to the link below. And then I put Xposed framework on it.
https://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355
And this has worked well for me for a few months since that was back at the end of December. Flash forward to today when my phone was being rather slow to respond to my actions so I decided to restart it. And upon restarting it, it's been stuck on the AT&T logo screen for a very long time. I can power it down with the power button, but think it actually just restarts it because then it boot ups again on its own. I cannot enter recovery mode with power+home+volume up, but I can get to the custom OS screen with power+volume down. My computer cannot see it as an adb device either. I've also tried removing the SIM card and the SD card and it's still gets stuck at the AT&T logo.
I've done nothing different with the OS or Xposed recently. The only new thing was about 2 hours prior to restarting it, I connected it to my computer to transfer some video files to the sd card. While I had it connecting to the computer and looking at the files on it through the phone's My Apps, it was sluggish to respond to my actions. But after disconnecting it, it was fine. I don't know if this is related, but I haven't done anything else different with it. Is there anyway to get my phone to boot up correctly? Or am I going to have to reflash it all over again? Thank you for any help.
Edit: I can enter recovery mode and I tried wiping the cache. It still gets stuck at the AT&T logo screen. I should also note that it no longer shows the Samsung "custom" boot screen anymore like it used to after rooting, now it just has the default Samsung boot screen, so it would certainly seem like my OS has been corrupted.