Hi,
For some reason my phone is booting to TWRP every time I try to Power On the phone or charge my phone while its turned off. I am facing this for these couple of weeks. I don't think I did any sort of change to device. It started to happen all of the sudden. The problem started on Stock TouchWiz 5.0. So I thought maybe flashing custom rom may fix it. So I tried to flash AospExtended ROM and the problem is still not gone. On top of it the phone also reboots randomly and boots to recovery. The frequency of the reboots on Stock TW was low but in Custom ROM it is frequent. I didn't tried flashing stock firmware yet for now because I don't have access to my PC yet.
Please can anyone help me with the problem. My phone is SM-G530H running on XCU1BPB1 Firmware.
Thanks
Just flash the stock rom using odin everything will be fine
tasnim_tamim said:
Hi,
For some reason my phone is booting to TWRP every time I try to Power On the phone or charge my phone while its turned off. I am facing this for these couple of weeks. I don't think I did any sort of change to device. It started to happen all of the sudden. The problem started on Stock TouchWiz 5.0. So I thought maybe flashing custom rom may fix it. So I tried to flash AospExtended ROM and the problem is still not gone. On top of it the phone also reboots randomly and boots to recovery. The frequency of the reboots on Stock TW was low but in Custom ROM it is frequent. I didn't tried flashing stock firmware yet for now because I don't have access to my PC yet.
Please can anyone help me with the problem. My phone is SM-G530H running on XCU1BPB1 Firmware.
Thanks
Click to expand...
Click to collapse
I'm facing the same problem :crying:
Sent from my fortunave3g using XDA Labs
Related
Hello,
I have posted this on the cyanogenmod forum but everyone seems to be on holiday as I'm getting no replies. I'm hoping someone on here can help.
I recently had CM12.1 running on my S5 SM-G900F for about six months with no problems. I then switched over to CM13 and used that for about a month without any problems.
I decided to go back to CM12.1, I flashed the same CM12.1 Snapshot file that I had been using previously and it installed without error but when I rebooted the phone it would crash and reboot in a loop during start up. I wiped the phone and tried the install again about four or five times having the same problem until on the final attempt it managed to load the OS. Now that I have the OS running I cant connect to WIFI, the 'back' and 'recent apps' buttons on the phone don't respond (the home button does work), the camera app doesn't work (I get the error 'Can connect to Camera') and it keeps crashing and restarting on reboot. Everything else seems to work but the phone seems sluggish and there may be other errors that I haven't come across yet.
I thought that there may be a problem with the zip file I was flashing so I downloaded it again but it did the same thing. I've tried wiping and reinstalling several times but I get the exact same problems. The file I'm flashing is:
cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
If I go back to CM13 everything works fine so the problem is only with CM12.1.
I'm at a lost to explain why this keeps happening as I've had this running fine on my phone previously and wiping the phone and starting again doesn't do anything to solve the problem.
Any ideas please?
Come on people! Have a guess, I'm really stuck here!
I myself have not installed any custom roms on my s5 yet (bc of knox 0x0 lol) but try reverting back to the stock rom and then install cm12.1 again, maybe it could work.
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Can you tell what bothered you to go away from cm13 back to cm 12.1?
caned_monkey said:
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Click to expand...
Click to collapse
ezantera said:
Can you tell what bothered you to go away from cm13 back to cm 12.1?
Click to expand...
Click to collapse
CM13 sucks!!! snapchat and instagram keeps on crashing, now I'm using resurrection remix 5.7.3, that sucks too!!
Hi Guys
I have a N910F Runing 5.1.1 working fine but I have a big issue when I switch off or Restart the phone it won't boot up so I have to pull out the battery and let it for 1 minute or more then it boots up somtimes it gives me emmc error
The problem started when I updated to 6.0.1 then I tryed flashing the 4 files firmware with PIT for both LL and MM but with no avail the same symptoms so I decided to flash TWRP and Keyubi V5 Rom it's Smooth but not able to restart the phone or switch off to switch on again the only thing thats working is the Hot reboot. I need you guys to help me sometimes I need to switch off my phone so I don't have to take the battery out everytime I want to switch on the Phone
I will be glad to hear some suggestions or fixs please.
Thank you
AndroMor said:
Hi Guys
I have a N910F Runing 5.1.1 working fine but I have a big issue when I switch off or Restart the phone it won't boot up so I have to pull out the battery and let it for 1 minute or more then it boots up somtimes it gives me emmc error
The problem started when I updated to 6.0.1 then I tryed flashing the 4 files firmware with PIT for both LL and MM but with no avail the same symptoms so I decided to flash TWRP and Keyubi V5 Rom it's Smooth but not able to restart the phone or switch off to switch on again the only thing thats working is the Hot reboot. I need you guys to help me sometimes I need to switch off my phone so I don't have to take the battery out everytime I want to switch on the Phone
I will be glad to hear some suggestions or fixs please.
Thank you
Click to expand...
Click to collapse
So, you're running 5.1.1 or 6.0.1?
Sent from this galaxy
pr1jker said:
So, you're running 5.1.1 or 6.0.1?
Sent from this galaxy
Click to expand...
Click to collapse
Running Note 5 port Kyubi SDX R2 (5.1.1) for now
Hello, I am facing the same issue. Mine is note with att unlocked recently by att. Currently running 6.0.1 with Feb 2017 security patch. I have changed nothing in terms of software still facing this issue. Let me know if you have got any solution.
Thanks
P.D.
lash a Note 7 port, My phone went off in the process... ever since then.... Its impossible to make a reboot without pulling out the battery.....
Plz help me!!!!
Im installing custom rom in sm core prime 360H via twrp but its shows error number7
How to fix it..???
Any one help me plz i need it
Probably your internal storage if full or something. Which ROM were you installing anyway?
rms112 said:
Probably your internal storage if full or something. Which ROM were you installing anyway?
Click to expand...
Click to collapse
I tried every custom rom but same issue
Error code 7
My phone storage is almost 70%free
Plz help me to solv this
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
Yes in 100% sure its 360H stock rom
I also try ins and inu both stock rom but issue is same
Can u tell me which stock are you use
Bdw are you indian....? Because my English is lil bit week?
rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
I use this method also which is given in link but same issue ?
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Thnx for ideas
my problem solved
Now Installed​ lineage 7.1
Bdw how to close this Thread ?
rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine
I trywd this but home button and resent apps cnt shows
Any idea about it...
rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine ??
I trywd this but home button and resent apps cnt shows
Any idea about it...
Works fine with me. RR beta 1 based on 7.1.2.
You should ask on that thread of ROM. Maybe hash can help you!
Good luck.
Help i'm not sure but i think i might have bricked my sm-g360h.
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
yemialabipurpose said:
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
Click to expand...
Click to collapse
Sounds like problem of dirty flash not hard brick.
Here's what you should do.
1) go to twrp recovery using power + vol up
2) wipe everything except storage
3) Flash cm 13 beta 5 or 6 ( the latest beta) or lineage OS or RR
4) if the problem still exists, then used Odin to flash stock ROM and repeat steps 1 to 3
Also don't use cm 12. Its EOF and you won't get any bug fixes and updates.
Hello.
I've recently flashed a ROM through TWRP on my smartphone. Since the ROM was buggy, I tried to flash the stock firmware, but I didn't know which firmware was my old firmware before I flashed the ROM. So I just installed AP_J510FXXU2AQA3_CL10498928_QB12376838_REV00_user_low_ship_MULTI_CERT.tar.md5, and it's working like a normal new phone before. But one problem, WiFi is not turning on. I've also encountered this problem when I was using a ROM. WiFi won't turn on. When I slide it on, it automatically slides off back. I already tried the WiFi fix trough TWRP but it also didn't work.
Please help me.
Zarlen said:
Hello.
I've recently flashed a ROM through TWRP on my smartphone. Since the ROM was buggy, I tried to flash the stock firmware, but I didn't know which firmware was my old firmware before I flashed the ROM. So I just installed AP_J510FXXU2AQA3_CL10498928_QB12376838_REV00_user_low_ship_MULTI_CERT.tar.md5, and it's working like a normal new phone before. But one problem, WiFi is not turning on. I've also encountered this problem when I was using a ROM. WiFi won't turn on. When I slide it on, it automatically slides off back. I already tried the WiFi fix trough TWRP but it also didn't work.
Please help me.
Click to expand...
Click to collapse
Flash custom kernel with wlan.ko
My MI A1 is is rebooting and crashing when I am using custom ROMs but there is no such problem when I am using the stock ROM. This problem started recently when I installed Android 12 on my device. Firstly I thought it was some kind of bug and then I checked my logs and indeed there was one bug which was causing reboots for a certain while but when the developer fix that bug I am still getting those reboots and crashes. I don't know why this is happening to me I come from a really poor background and cannot afford a new phone anybody who can help me with this situation I will be really thankful to them. Also the custom ROMs were working fine before. I have used the latest TWRP recovery and also I have tried flashing that room with orange Fox recovery and adb sideload but no luck. Still getting those reboots. Flashed the latest firmware a couple of times as well but no luck. Also I am getting this issue in Android 11 custom ROMs as well
My phone only vibrates after that with black screen . You solved your phone problem?