I recently flashed my GT-i9506 and installed CyanogenMod. After finishing, the back and menu buttons (more often the menu button) kept getting pressed with the backlight on and vibrations too without me touching them. The weird thing is that while I was trying to fix it by going to various recovery modes after constantly switching the problem happened there too. The screen was recently replaced but I don't recall this happening at all on the stock ROM after the repairment.
Here's what happened:
I used Heimdall to flash TeamWin recovery but kept getting a common problem with PIT files while in download mode (can't post links because I'm a new user)
I compiled SaburoJiro's Heimdall fork as suggested and that seemed to fix the issue. TeamWin recovery was flashed succesfully.
I flashed the official CyanogenMod rom for gt-i9506 following the instructions on their wiki page. Everything seemed to work fine up until the point where the OS started up.
What I tried:
Tried various recovery images including TeamWin and ClockworkMod Recovery. The problem happens on both.
Used both Odin and Heimdall to flash.
Factory resets and cache clearing
A temporary solution is to enable the on screen navbar, which disabled the hardware keys which were causing the problem. The keys still keep lighting up while the screen is on but they don't do anything.
Is there any way to restore the phone beyond recovery mode (which this seems to happen in too)? I'm pretty sure this isn't a hardware issue.
SwoodGrommet said:
I recently flashed my GT-i9506 and installed CyanogenMod. After finishing, the back and menu buttons (more often the menu button) kept getting pressed with the backlight on and vibrations too without me touching them. The weird thing is that while I was trying to fix it by going to various recovery modes after constantly switching the problem happened there too. The screen was recently replaced but I don't recall this happening at all on the stock ROM after the repairment.
Here's what happened:
I used Heimdall to flash TeamWin recovery but kept getting a common problem with PIT files while in download mode (can't post links because I'm a new user)
I compiled SaburoJiro's Heimdall fork as suggested and that seemed to fix the issue. TeamWin recovery was flashed succesfully.
I flashed the official CyanogenMod rom for gt-i9506 following the instructions on their wiki page. Everything seemed to work fine up until the point where the OS started up.
What I tried:
Tried various recovery images including TeamWin and ClockworkMod Recovery. The problem happens on both.
Used both Odin and Heimdall to flash.
Factory resets and cache clearing
A temporary solution is to enable the on screen navbar, which disabled the hardware keys which were causing the problem. The keys still keep lighting up while the screen is on but they don't do anything.
Is there any way to restore the phone beyond recovery mode (which this seems to happen in too)? I'm pretty sure this isn't a hardware issue.
Click to expand...
Click to collapse
It's 100% a hardware issue. No software would cause this and even then it also happens in recovery. It's impossible to have the same behavior in recovery and in normal android without it being a hardware issue.
SwoodGrommet said:
I recently flashed my GT-i9506 and installed CyanogenMod. After finishing, the back and menu buttons (more often the menu button) kept getting pressed with the backlight on and vibrations too without me touching them. The weird thing is that while I was trying to fix it by going to various recovery modes after constantly switching the problem happened there too. The screen was recently replaced but I don't recall this happening at all on the stock ROM after the repairment.
Here's what happened:
I used Heimdall to flash TeamWin recovery but kept getting a common problem with PIT files while in download mode (can't post links because I'm a new user)
I compiled SaburoJiro's Heimdall fork as suggested and that seemed to fix the issue. TeamWin recovery was flashed succesfully.
I flashed the official CyanogenMod rom for gt-i9506 following the instructions on their wiki page. Everything seemed to work fine up until the point where the OS started up.
What I tried:
Tried various recovery images including TeamWin and ClockworkMod Recovery. The problem happens on both.
Used both Odin and Heimdall to flash.
Factory resets and cache clearing
A temporary solution is to enable the on screen navbar, which disabled the hardware keys which were causing the problem. The keys still keep lighting up while the screen is on but they don't do anything.
Is there any way to restore the phone beyond recovery mode (which this seems to happen in too)? I'm pretty sure this isn't a hardware issue.
Click to expand...
Click to collapse
I think Lennyz knows best but did you erased the internal storage too while doing a factory reset?
I've got some strage issues after I flashed a ROM and I could resolve it when I erased the internal storage too on factory reset.
Lennyz1988 said:
It's 100% a hardware issue. No software would cause this and even then it also happens in recovery. It's impossible to have the same behavior in recovery and in normal android without it being a hardware issue.
Click to expand...
Click to collapse
Okay, I guess something went wrong when the screen was repaired. I'll call the company that fixed it later. Is there no possible way that any software can enable these buttons?
PePeMoke said:
I think Lennyz knows best but did you erased the internal storage too while doing a factory reset?
I've got some strage issues after I flashed a ROM and I could resolve it when I erased the internal storage too on factory reset.
Click to expand...
Click to collapse
I factory reset a couple of times using both ClockworkMod and TeamWin. It still kept all the images from the camera though. How would you erase all internal storage using ClockworkMod? Format /system? Or perharps just /data and /storage/sdcard1? Asking since I don't want to brick my phone by doing something I shouldn't be doing.
SwoodGrommet said:
Okay, I guess something went wrong when the screen was repaired. I'll call the company that fixed it later. Is there no possible way that any software can enable these buttons?
I factory reset a couple of times using both ClockworkMod and TeamWin. It still kept all the images from the camera though. How would you erase all internal storage using ClockworkMod? Format /system? Or perharps just /data and /storage/sdcard1? Asking since I don't want to brick my phone by doing something I shouldn't be doing.
Click to expand...
Click to collapse
For CWM I do not know..
I use TWRP and there you can select what should be wiped under "advanced wipe".
You can select system, boot, data, cache and internal storage.
If you got TWRP use this!
Note that everything on your phone will be deleted including custom recovery.
You'll have to flash it again via Odin afterwards.
Then flash the ROM and Gapps via custom recovery.
I do not know whether this will solve the problem because it really could be a hardware issue as Lennyz said..
Maybe you should wait with that after the company repaired it again.
SwoodGrommet said:
Okay, I guess something went wrong when the screen was repaired. I'll call the company that fixed it later. Is there no possible way that any software can enable these buttons?
I factory reset a couple of times using both ClockworkMod and TeamWin. It still kept all the images from the camera though. How would you erase all internal storage using ClockworkMod? Format /system? Or perharps just /data and /storage/sdcard1? Asking since I don't want to brick my phone by doing something I shouldn't be doing.
Click to expand...
Click to collapse
It's possible but not in your case. There is no software booted when you are in the recovery except the recovery itself.
@SwoodGrommet
Could you figure it out?
Related
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
Which ROMs are you installing? On I337M your best bet is T-Mobile ROMs and Kernels. I have Bell I337M and have no issues.
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
Are you wiping with TWRP? I heard there are issues with using it to wipe and restore or loading a new rom after wipe. Just restore using Odin and then load a new rom (or restore a backup) without wiping. See if that solves your problem of bootlooping
kiru said:
Are you wiping with TWRP? I heard there are issues with using it to wipe and restore or loading a new rom after wipe. Just restore using Odin and then load a new rom (or restore a backup) without wiping. See if that solves your problem of bootlooping
Click to expand...
Click to collapse
i just went through this all last night what a pita , problem is twrp , if you do a full wipe when you type the word yes , you can only bootup 1 time then it gets stuck next time you boot , theres no way to fix it , even going back to old version of twrp wont do it , you have to compleatlly remove root and return to stock , re root and install twrp again , then if your luck your nandropid backup will work , it took me 5 hrs to fuger this all out , stupid twrp drove me nuts .,...
in short , return to stock and reroot , then never do a full wipe where you have to type yes
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
i had the same problem, im with rogers so i downloaded the rogers rom 4.2 and i cant make any phone calls or listen to music or watch videos. my phone came with 4.3 does anyone have any ideas to help me?
Having an issue that I cant seem to figure out. I have been using various roms eg Omega V7,S4 Google Edition V16, Fox Hound 1.1 etc. They all install fine, factory reset before and after wiping the various cashes as required. I also format the SD storage to be sure, but once up and running, apps installed, every time I restart the phone or for some reason it freezes it just get stuck at the white Samsung S4 logo.
If i go back in to recovery (TWRP 2.6.0.0) factory reset does nothing to fix this. I have also noticed that sometimes the internal SD shows as 0 Mb, and I have to reformat this to re-install a ROM. (Getting corrupt some how?) Only re-installing the ROM from fresh seems to get my phone up and running again. Until something happens. Any ideas?
I follow all instructions as detailed, and never come across this issue with my S3.
Ok after trying a few things the only thing that seemed to fix the problem was reflashing stock firmware using oden.
I had to reformat the internal storage again as this was acting like it was encrypted, which it was not. Think this problem that caused my phone not to boot when when restarted.
No Idea why it did this but its fixed now.
john81uk said:
Ok after trying a few things the only thing that seemed to fix the problem was reflashing stock firmware using oden.
I had to reformat the internal storage again as this was acting like it was encrypted, which it was not. Think this problem that caused my phone not to boot when when restarted.
No Idea why it did this but its fixed now.
Click to expand...
Click to collapse
same problem. As long as i dont reboot it works fine...first reboot it get stucked....
willhave to reverse to stock then...
too bad i loved GE!!!
So simple and fast!
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
not_su said:
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
Click to expand...
Click to collapse
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Rhymey said:
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Thanks - that's exactly what I've been trying to do. I haven't tried reflashing back to stock with Odin though. Hmmm...
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Click to expand...
Click to collapse
Bell, up here in the Great White North. I don't think locked bootloader is an issue - I was on the previous version of Danvdh's ROM, and everything was hunkydory. I just made the unfortunate decision to encrypt. Big mistake.
May try flashing back to stock. Nothing to lose, at this stage...
Thanks!
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
not_su said:
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
Click to expand...
Click to collapse
Good to hear. Should be able to flash to the rom once again no problem now that it's unencrypted!
This is on two standard Galaxy S5's, with standard ROM, etc - not rooted, or anything else.
Every time I turn off WiFi, or enable Mobile Hotspot, I get 'Unfortunately System UI has stopped'.
To fix I have to Power off/on the phone.
(Turning on WiFi is no problem, just turning it off.)
I have gone into 'Safe Mode', and same issue, so it looks to not be a bad App.
I have also uninstalled 'Google' updates, and again no change...
Any thoughts?
All of a sudden my S5 showed the exact same error message for no aparent reason... I didn't do anything, and now I can't use my phone at all because of that bug. It happens on every boot so I can't even unlock my phone. Tried reinstalling everything, ROM, recovery, kernel, with/without root = still same, what just happened here??
EDIT: Same thing if I'm in Safe Mode -_-
Seeing noone knows a solution here's what I did yesterday.
1. Backed up all my stuff from internal storage to the sd card
2. Did factory reset in TWRP recovery
3. Flashed completely stock official firmware from Samsung
4. Waited for it to boot up and try to restore some of my settings (it restored all folders on their places, made same amount of home screens as I had before the reinstall and downloaded all of my previously installed apps from the Play Store, ofcourse without the cracked ones, and it also restored most apps' data as well so it's not as bad as you may think to factory reset and reinstall everything)
5. Started rooting, flashing TWRP again, installing Dolby Audio, Xposed and everything I had before, took me one full day to set it up as it was before.
Now when I set it up I always make a nandroid backup from when things are working fine, in case it goes crazy for no reason again... Good luck!
when the wifi radio is acting weird, a dirty flash of your current ROM susually fixes is as its probably a radio issue. Id do that before doing anything drastic like the boot-n-nuke Odin flash and starting from scratch (which will fix that issue)
I don't think I have a ROM issue, as I have two S5's, and both have the same issue... and both are standard ROMs.
I will do a factory re-set on one at some point, but this looks to be a 'simpler' issue.
I have tried a full Cache delete, as well as other 'clean' processes.
Nothing works.
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
koragg97 said:
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
Click to expand...
Click to collapse
well, you can wipe cache, and dalvik 3x each (not kidding about the 3x each), then dirty flash the rom, pray to the gods of android, reboot. If failure occurs, its Odin Nuke time unless you want to try to flash an individual radio file by itself (not recommended)
I restarted my S4 this evening and now it won't boot past the SAMSUNG logo. I have tried a variety of things to get it going but none have worked.
1) Soft boot
2) Pulled battery and let it sit awhile
3) Tried to boot into Safe Mode (stuck on the same spot with no indication of going into safe mode)
4) Wipe cache from CWM recovery mode
5) Reboot from CWM recovery mode
Everything is pretty well backed up but after looking at my sdcard it appears that my camera reverted to internal memory about a month ago so I am after any ideas to get those images.
My phone is rooted and running an old 4.2.2 stock Android OS with USB debugging enabled. I was wondering if by re-flashing the OS it might fix the boot issue and be able to recover the images. Or maybe even flash CM. Or maybe some other thing. I found something about adb but I don't want to do anything else yet until someone more savvy than me weighs in.
Unless it's a hardware issue, then flashing a ROM might work.
The other option is to try a reflow. Reflow means heating your phone up so that the solder becomes liquid and any cracks in the solder (which can cause a bad contact), or any piece that isn't seated right, will be remedied.
did u tried to flash stock firmware using odin?
Deleted
I got it going. I first spent a number of hours getting to know adb which was a dead end because I couldn't get it to see beyond the base directory. I then just flashed the stock rom and everything was there including things that shouldn't be like apps, contacts and texts. The phone is back exactly where it was before it boot locked without having to mess with a single thing. I am grateful but a bit confused.