Messed up rooted Galaxy A3, com.android.phone stopped - General Questions and Answers

Okay. This week I rooted my new Samsung Galaxy A3 and started removing some system apps. Until a couple of hours ago I nothing went wrong, but then I found this list on XDA and removed some more. Half an hour later a received a phone call and noticed that the name of the caller didn't appear. I assumed this had something to do with some apps and services I just removed. So I tried to reinstall an app who I blamed for to be the reason for my problem. But after that it went wrong. 'Unfortunately the process com.android.phone has stopped' almost every second. And also a Google Search error appears every now and then. My phone is unusable now.
After some Googling I found that clear the cache could solve the problem. But it didn't. Then I tried to do a factory reset, but still the problem occurs.
I didn't back-up the system because it was a new phone and no personal things were on it.
What can I do about this?

Omkoal said:
Okay. This week I rooted my new Samsung Galaxy A3 and started removing some system apps. Until a couple of hours ago I nothing went wrong, but then I found this list on XDA and removed some more. Half an hour later a received a phone call and noticed that the name of the caller didn't appear. I assumed this had something to do with some apps and services I just removed. So I tried to reinstall an app who I blamed for to be the reason for my problem. But after that it went wrong. 'Unfortunately the process com.android.phone has stopped' almost every second. And also a Google Search error appears every now and then. My phone is unusable now.
After some Googling I found that clear the cache could solve the problem. But it didn't. Then I tried to do a factory reset, but still the problem occurs.
I didn't back-up the system because it was a new phone and no personal things were on it.
What can I do about this?
Click to expand...
Click to collapse
Which Galaxy A3 model is yours? SM-A300(...)

LS.xD said:
Which Galaxy A3 model is yours? SM-A300(...)
Click to expand...
Click to collapse
It is an SM-A300FU.
Build-id: KTU84P.A300FUXXU1ANL4

Omkoal said:
It is an SM-A300FU.
Build-id: KTU84P.A300FUXXU1ANL4
Click to expand...
Click to collapse
Just flash the matching firmware via ODIN and your phone will be fine again
- Connect phone in "DOWNLOAD" mode (Power off the phone , then press "Vol down + home + power" at the same time)
- Start ODIN
- Select the firmware file as "AP"
- Press start ( Will take about 10 minutes)

LS.xD said:
Just flash the matching firmware via ODIN and your phone will be fine again
- Connect phone in "DOWNLOAD" mode (Power off the phone , then press "Vol down + home + power" at the same time)
- Start ODIN
- Select the firmware file as "AP"
- Press start ( Will take about 10 minutes)
Click to expand...
Click to collapse
Great. Will try it straight away.
Do I need to root again?

Omkoal said:
Great. Will try it straight away.
Do I need to root again?
Click to expand...
Click to collapse
Yes, you will need to gain root access again.

LS.xD said:
Yes, you will need to gain root access again.
Click to expand...
Click to collapse
Okay.
And just to be sure. As a Dutchman I picked this download:
2014-12-01
Netherlands
4.4.4
A300FUXXU1ANL4
A300FUPHN1ANL2
Does it matter which one I choose?

Omkoal said:
Okay.
And just to be sure. As a Dutchman I picked this download:
2014-12-01
Netherlands
4.4.4
A300FUXXU1ANL4
A300FUPHN1ANL2
Does it matter which one I choose?
Click to expand...
Click to collapse
Should be the right region for you if you bought it in your country. Different regions may have diffrerent firmware/modem versions. You should only use the version your phone came with to avoid trouble.

Related

Samsung Galaxy Tab 2 (10.1) won't shut down after the latest firmware update

Hi. I hope this is the correct forum. My Samsung Galaxy Tab 2 (10.1) won't shut down after the latest firmware update. I believe I had 4.2.1 and now I have 4.2.2. My device name is is GT-P5113. I plugged the Tab into my computer and Kies opened automatically. It said there was an update for my device so I updated.
All seems to be ok, but now when I choose to "shut down" the tablet shuts down and then cycles back on as if I had just pressed the power button to turn it back on.
I guess it could be worse - it could be refusing to turn on.
Is there a fix for this? Anybody else had this problem?
It is not rooted and I don't really want to do so.
Thanks in advance for any help!
I think u could wipe cache in stock recovery I would do that and see if that fixes it. Hold down vol up and power at the same time till the device reboots into recovery. Dunno how it is on the bigger ones but on the 7" I have to keeo holding the buttons for a second longer after the samsung gtab2 logo comes on to boot in to recovery.
Remember u dont want to factory reset just wipe cache
Sent from my GT-P3113 using xda app-developers app
wipe cache
Thank you for the reply. I tried that and got an "error". I was able to get to recovery mode and choose "wipe cache". It begins and I get an error message.
mymeatb18 said:
I think u could wipe cache in stock recovery I would do that and see if that fixes it. Hold down vol up and power at the same time till the device reboots into recovery. Dunno how it is on the bigger ones but on the 7" I have to keeo holding the buttons for a second longer after the samsung gtab2 logo comes on to boot in to recovery.
Remember u dont want to factory reset just wipe cache
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
beezerhale said:
Thank you for the reply. I tried that and got an "error". I was able to get to recovery mode and choose "wipe cache". It begins and I get an error message.
Click to expand...
Click to collapse
What type of error?? :cyclops:
error
It just read "error" and a image of the little android on it's back.
mythi said:
What type of error?? :cyclops:
Click to expand...
Click to collapse
beezerhale said:
It just read "error" and a image of the little android on it's back.
Click to expand...
Click to collapse
can you take a picture of it ??
mythi said:
What type of error?? :cyclops:
Click to expand...
Click to collapse
mythi said:
can you take a picture of it ??
Click to expand...
Click to collapse
I just uploaded 4 pics to a section of a website that I already have running.
Here is the link:
http://6thgraderocks.wix.com/galazyerror
The images show the end process of updating through Kies (I screen captured), the current tab info, the recovery screen and the error I get when I try to erase cache. Keep in mind, I am able to reboot and my tablet comes on like normal - no issues except when I try to turn it off - it comes right back on.
beezerhale said:
I just uploaded 4 pics to a section of a website that I already have running.
Here is the link:
http://6thgraderocks.wix.com/galazyerror
The images show the end process of updating through Kies (I screen captured), the current tab info, the recovery screen and the error I get when I try to erase cache. Keep in mind, I am able to reboot and my tablet comes on like normal - no issues except when I try to turn it off - it comes right back on.
Click to expand...
Click to collapse
Did you try flashing pit?? did you flash jb bootloader ?? did your device be rooted before flash ?? were you on cm/aokp/pac/slim/etc ??? if yes whic h build did you flash black hawk next kernel ?? <--- may be it what caused it ---> did you try to downgrade to 4.0.3/4.0.4/4.1.2 if yes what happened what did you flash before going to stock rom like mod and etc ???? hope you answer these questions !!
also try this
enable usb debugging
turn off your tab fully
connect tab to pc pull a logcat dsmg ksmg and post them as txt or pastbin
does your tab stuck in recovery loop like rebooting always to recovery sometimes until you compeletly shut down the tab?
if it is under warranty return it to SAMMY TO FIX IT IT IS THEIR FAULT !!
i think it is not hard ware related don't worry !!
This tab is not rooted or tampered with at all. I have no desire to do so.
mythi said:
Did you try flashing pit?? did you flash jb bootloader ?? did your device be rooted before flash ?? were you on cm/aokp/pac/slim/etc ??? if yes whic h build did you flash black hawk next kernel ?? <--- may be it what caused it ---> did you try to downgrade to 4.0.3/4.0.4/4.1.2 if yes what happened what did you flash before going to stock rom like mod and etc ???? hope you answer these questions !!
also try this
enable usb debugging
turn off your tab fully
connect tab to pc pull a logcat dsmg ksmg and post them as txt or pastbin
does your tab stuck in recovery loop like rebooting always to recovery sometimes until you compeletly shut down the tab?
if it is under warranty return it to SAMMY TO FIX IT IT IS THEIR FAULT !!
i think it is not hard ware related don't worry !!
Click to expand...
Click to collapse
I have the exact same problem with BOTH my Galaxy Tab 2 10.1 (Wi-Fi only) It's a software problem for sure...
Also flashing back to 4.1.1 or lower will eliminate the problem
Sent from my GT-P5113 using xda app-developers app
I know I could probably do that (flash back) myself, but I just don't want to. I have bricked a Kindle Fire before while trying to make it do what I wanted it to. I don't want to mess with this Galaxy - it does exactly what I want it to --- surf the web, Netflix/Hulu, and comic books - I'm not too complicated!
I spoke with Samsung yesterday and they said to try a hard reset. That did not work. I spoke with another rep this morning and they are going to repair or replace it for me. He sent a shipping label to my email. This was a gift and I have no receipt. I am VERY pleased with the service from Samsung.
SebasC said:
Also flashing back to 4.1.1 or lower will eliminate the problem
Sent from my GT-P5113 using xda app-developers app
Click to expand...
Click to collapse
So you're going to replace a perfectly good product with a software mistake? I've two tablets, unrooted, 4.2.2 with the same problem... Your better off waiting for a fix..
Why shoukd he feel burdened for something he had no control over. Samsung sent the update, iys not his fault its not doing what it should. If he wants to return it cuz it doesnt turn off as it should he has every right to do so. At least he didnt brick it and is expecting samsung to pay for it.
Sent from my GT-P3113 using xda app-developers app
I had the same problem
Hello,
I registered here to just answer your question since I've been searching around on the internet as well for this problem. I have a Samsung Galaxy Tab 2 10.1 with version 4.2.1. I updated to version 4.2.2 and all hell broke loose. Before I get into it, I had a perfectly working tablet that never had any problems. I installed all updates through OTA or Samsung Kies. It's not rooted.
Anyway, after the update to 4.2.2 my tablet wouldn't turn on. I had to plug it into the wall outlet and then it finally turned on. After playing around with it, some of the widgets didn't work so I thought maybe I should turn it off and reboot it. When I chose "power off" it wouldn't turn off. Instead it would automatically restart. After trying several attempts it still wouldn't turn off so I contacted Samsung. They made me clear the cache and then wipe out the whole system and install a fresh copy of the software. The tablet then went black and now all that was shown on the screen was the little android bot with the error message like how yours is now. It wouldn't boot up to the main screen anymore.
So I had to return the tablet back to Samsung yesterday and they are going to attempt to fix it. It's still under warranty but I'll be pissed if I won't be able to install the new software on my tablet since I like the new updates they did for it.
Anyway, sorry for my long response but I hope this helps you out even though nothing was resolved. I'll post what happens once I get back my tablet.
Similar "Reboot after turn off" issue
I have the same "can't turn off" issue on my stock Tab 2 10.1 updated to 4.2.2 via Kies. After turning off and confirming on the screen, the tablet simply turns back on. This typically happens several times in a row before something happens and it stays off. I emailed Samsung to request support.
d86 said:
Hello,
I registered here to just answer your question since I've been searching around on the internet as well for this problem. I have a Samsung Galaxy Tab 2 10.1 with version 4.2.1. I updated to version 4.2.2 and all hell broke loose. Before I get into it, I had a perfectly working tablet that never had any problems. I installed all updates through OTA or Samsung Kies. It's not rooted.
Anyway, after the update to 4.2.2 my tablet wouldn't turn on. I had to plug it into the wall outlet and then it finally turned on. After playing around with it, some of the widgets didn't work so I thought maybe I should turn it off and reboot it. When I chose "power off" it wouldn't turn off. Instead it would automatically restart. After trying several attempts it still wouldn't turn off so I contacted Samsung. They made me clear the cache and then wipe out the whole system and install a fresh copy of the software. The tablet then went black and now all that was shown on the screen was the little android bot with the error message like how yours is now. It wouldn't boot up to the main screen anymore.
So I had to return the tablet back to Samsung yesterday and they are going to attempt to fix it. It's still under warranty but I'll be pissed if I won't be able to install the new software on my tablet since I like the new updates they did for it.
Anyway, sorry for my long response but I hope this helps you out even though nothing was resolved. I'll post what happens once I get back my tablet.
Click to expand...
Click to collapse
Reboot issues
avm1 said:
I have the same "can't turn off" issue on my stock Tab 2 10.1 updated to 4.2.2 via Kies. After turning off and confirming on the screen, the tablet simply turns back on. This typically happens several times in a row before something happens and it stays off. I emailed Samsung to request support.
Click to expand...
Click to collapse
I had a live chat with Samsung just now. It is interesting that the tech I communicated with did not know of any issue with the rebooting and there was no mention in their system that a problem even existed (so I sent a link to this page to him).
Anyway, the end result was that it I wanted to fix the problem, I would have to restore Android through KIES:
samsung.com/us/support/faq/FAQ00052690/61266/GT-P3113GRSXAR
This will delete all data and get back to Android 4.2.1
Since I have already have seen issues with KIES, I wonder if it wouldn't be easier to just use ODIN? Any suggestions from those who might have tried both?
update #1
Just wanted to give an update. Samsung sent me an email yesterday stating they "fixed" my tablet. I should be getting back my tablet by the end of this week or early next week. The receipt said that it was a "software problem" and they reinstalled new software with the latest update. I'm just wondering if it's 4.1.2(that worked fine with my tablet) or 4.2.2(which messed up my tablet)
I'll give another update once I get it in my possession.
---------- Post added at 05:33 PM ---------- Previous post was at 05:28 PM ----------
SamsungTab2User said:
I had a live chat with Samsung just now. It is interesting that the tech I communicated with did not know of any issue with the rebooting and there was no mention in their system that a problem even existed (so I sent a link to this page to him).
Anyway, the end result was that it I wanted to fix the problem, I would have to restore Android through KIES:
samsung.com/us/support/faq/FAQ00052690/61266/GT-P3113GRSXAR
This will delete all data and get back to Android 4.2.1
Since I have already have seen issues with KIES, I wonder if it wouldn't be easier to just use ODIN? Any suggestions from those who might have tried both?
Click to expand...
Click to collapse
I tried this when I chatted with Samsung and it messed up my tablet completely where as when I rebooted my tablet it would show an android robot with "error"
Plus, I don't know about you but I don't want to have 4.2.1. I want to have the 4.2.2 update on my tablet. It's a much more sleeker interface. Just the only problem is that it wouldn't shut off. I will see what happens once I have it. If 4.2.1 is on my tablet I will try again updating the software to 4.2.2.
There are some problems like boot fail or can't poweroff I've seen at some posts, they do the same things:
1.flash a 4.2.2 stock rom
2.have some problems: boot fail or can't poweroff eg..
3.boot to recovery and want to wipe the cache
4.get a error with the robot logo lie down
I found a post mentions that he've fixed this problem by using odin 3.07 flash the 4.2.2 stock rom with a matched kernel boot file.
The post is here, it's in chinese:
http://b.it168.com/thread-4690107-1-1.html
His solution is get to this site to find the 4.2.2 stock rom and matched kernel file of your device and use odin 3.07 flash them:
http://samsung-updates.com/
do it at your own risk maybe solve your problem.
Update #2
So I got my tablet today and I turned it on to see that it had android software 4.1.1. Then the software update icon popped up and I updated to 4.2.2. Then the same problem happened again like the last time. The tablet wouldn't turn off and it would automatically restart. I contacted Samsung Support again and they had me do a factory reset which then fried my tablet again. It doesn't turn on. So now I have to send it back again for a 2nd time. This time they said they may have to replace the tablet either with the same tablet or a different model tablet. But I stressed to them to make sure to update the tablet this time to 4.2.2 so they can see the problem I'm facing. We shall see next week I guess what happens.

[Q] Verizon Samsung Galaxy SIII (SCH-1535) BOOT LOOPED, LOST RECOVERY AND OS!!

HELP!!!
About 1 month ago, my Galaxy S3 running 4.4.2 (Completely stock: no root, rom, or custom firmware), suddenly got into a boot loop about 3 weeks after receiving the 4.4.2 update. At first, it would boot up completely into the OS, then shut down before I even had time to enter PIN. Sometimes, after shutting down, it would restart by itself, but only on some occasions. I was able to enter and constantly use recovery and download mode with no shutdowns, so it wasn't a battery problem, instead a software/firmware one. I found that if the phone was plugged in while booting, I was able to use the phone with no problem, but it shut off as soon as the charger was removed. I then factory reset it, wiped the cache and such, but the problem still persisted. After about not touching it for a week, the phone wouldn't even make it past the first Samsung boot animation and jingle without turning off. However, the plugging in method would make it go further into the boot sequence, but it still wouldn't boot into the OS. After leaving it alone for one more week, I then LOST RECOVERY ACCESS! It would boot up to the android figure, but shut off immediately. I was able to access download mode, and therefore, tried to flash an earlier firmware with ODIN.
The phone was recognized by ODIN, but the flashing process failed. I first tried to root the stock ROM, but ODIN couldn't find the recovery. I then tried to downgrade my firmware to 4.1.2. I got a FAIL message on my PC and an error message on the phone (in ODIN mode) saying, " SW REV CHECK FAIL: FUSED 2 BINARY 0" Now every time I try to turn on the phone, it goes straight into ODIN mode, and it shows the message, : Firmware upgrade encountered an issue, Please use Software Repair Assistant & try again" with an image of a phone and PC linked together, but being interrupted by a yellow triangle with an exclamation mark in it.
HELP ME PLEASE. I LOVE THIS PHONE AND I STILL HAVE A WHILE UNTIL I CAN GET A NEW ONE!!!!
Is your phone still under warranty with your wireless carrier? If it is, you may want to contact the customer support department. You may be able to get a new phone as a warranty replacement.
Cindy
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
cindylike24 said:
Is your phone still under warranty with your wireless carrier? If it is, you may want to contact the customer support department. You may be able to get a new phone as a warranty replacement.
Cindy
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
Click to expand...
Click to collapse
Good point cindy if its an internal hardware issue verizon will replace it at no charge
From my Wicked S3 running MIUI
how is this even possible?
gorilla29 said:
HELP!!!
About 1 month ago, my Galaxy S3 running 4.4.2 (Completely stock: no root, rom, or custom firmware), suddenly got into a boot loop about 3 weeks after receiving the 4.4.2 update. At first, it would boot up completely into the OS, then shut down before I even had time to enter PIN. Sometimes, after shutting down, it would restart by itself, but only on some occasions. I was able to enter and constantly use recovery and download mode with no shutdowns, so it wasn't a battery problem, instead a software/firmware one. I found that if the phone was plugged in while booting, I was able to use the phone with no problem, but it shut off as soon as the charger was removed. I then factory reset it, wiped the cache and such, but the problem still persisted. After about not touching it for a week, the phone wouldn't even make it past the first Samsung boot animation and jingle without turning off. However, the plugging in method would make it go further into the boot sequence, but it still wouldn't boot into the OS. After leaving it alone for one more week, I then LOST RECOVERY ACCESS! It would boot up to the android figure, but shut off immediately. I was able to access download mode, and therefore, tried to flash an earlier firmware with ODIN.
The phone was recognized by ODIN, but the flashing process failed. I first tried to root the stock ROM, but ODIN couldn't find the recovery. I then tried to downgrade my firmware to 4.1.2. I got a FAIL message on my PC and an error message on the phone (in ODIN mode) saying, " SW REV CHECK FAIL: FUSED 2 BINARY 0" Now every time I try to turn on the phone, it goes straight into ODIN mode, and it shows the message, : Firmware upgrade encountered an issue, Please use Software Repair Assistant & try again" with an image of a phone and PC linked together, but being interrupted by a yellow triangle with an exclamation mark in it.
HELP ME PLEASE. I LOVE THIS PHONE AND I STILL HAVE A WHILE UNTIL I CAN GET A NEW ONE!!!!
Click to expand...
Click to collapse
I would love to help, but please help me first. how do you claim to have 4.4 kitkat when for the i535 there is confirmed to only be 4.3 for a stock OS? this will make a big difference in the outcome of who can help you. Google and android both confirm that 4.3 is the last update for this phone coming from verizon. How can you have 4.4 stock with touchwiz and everything? unless you have AOSP, which is another things entirely. this phone does poorly for 4.4 in AOSP because we don't have a proper kernel or baseband for it. it wasn't officially released.
anyway, that is my question to you.
cyberkeeper1 said:
I would love to help, but please help me first. how do you claim to have 4.4 kitkat when for the i535 there is confirmed to only be 4.3 for a stock OS? this will make a big difference in the outcome of who can help you. Google and android both confirm that 4.3 is the last update for this phone coming from verizon. How can you have 4.4 stock with touchwiz and everything? unless you have AOSP, which is another things entirely. this phone does poorly for 4.4 in AOSP because we don't have a proper kernel or baseband for it. it wasn't officially released.
anyway, that is my question to you.
Click to expand...
Click to collapse
4.4.2 is the latest and probably the last update for the i535. This should fix your problem OP. http://forum.xda-developers.com/showthread.php?t=2791801
I wish it was.
cindylike24 said:
Is your phone still under warranty with your wireless carrier? If it is, you may want to contact the customer support department. You may be able to get a new phone as a warranty replacement.
Cindy
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
Click to expand...
Click to collapse
No, Cindy, it isn't under warranty anymore. It has been more than one year. I wish it was though!
Thanks, but...
JudgeFutta said:
4.4.2 is the latest and probably the last update for the i535. This should fix your problem OP. http://forum.xda-developers.com/showthread.php?t=2791801
Click to expand...
Click to collapse
Thank you so much for your help. I flashed the file, and I got recovery back. However, the phone has just returned to the state that this problem begun with. It still goes further into the boot sequence (still won't start) when plugged in, but it will shut off before it finishes and as soon as it's unplugged. It won't even start the sequence without the charger.
Any other suggestions?
Is that so? I had no idea. I was told by Verizon the 4.3 is the last one. I certainly will investigate. On ODIN, make SURE you check the bootloader update option, F. Reset Time, and auto reboot. Otherwise, the bootloader will not allow you to boot.
Sent from my SCH-I535 using XDA Free mobile app
gorilla29 said:
Thank you so much for your help. I flashed the file, and I got recovery back. However, the phone has just returned to the state that this problem begun with. It still goes further into the boot sequence (still won't start) when plugged in, but it will shut off before it finishes and as soon as it's unplugged. It won't even start the sequence without the charger.
Any other suggestions?
Click to expand...
Click to collapse
Try flashing the .tar file from the second post. Also make sure you have odin setup correctly like cyberkeeper1 said.
cyberkeeper1 said:
Is that so? I had no idea. I was told by Verizon the 4.3 is the last one. I certainly will investigate.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
VRUDNE1 4.4.2 has been available for roughly two months.
Verizon PDF (laziness, Verizon did not change the software name to VRUDNE1): http://www.verizonwireless.com/support/system_update/galaxys3.html
Samsung PDF (click first question under FAQ): http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW?
Quick online search: http://www.droid-life.com/2014/06/19/verizons-samsung-galaxy-s3-galaxy-s4-mini-kit-kat/
SlimSnoopOS said:
VRUDNE1 4.4.2 has been available for roughly two months.
Verizon PDF (laziness, Verizon did not change the software name to VRUDNE1): http://www.verizonwireless.com/support/system_update/galaxys3.html
Samsung PDF (click first question under FAQ): http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW?
Quick online search: http://www.droid-life.com/2014/06/19/verizons-samsung-galaxy-s3-galaxy-s4-mini-kit-kat/
Click to expand...
Click to collapse
Many thanks, Slim.
Should be made a sticky. This is important stuff for this phone.
Sent from my SCH-I535 using XDA Free mobile app
cyberkeeper1 said:
Is that so? I had no idea. I was told by Verizon the 4.3 is the last one. I certainly will investigate. On ODIN, make SURE you check the bootloader update option, F. Reset Time, and auto reboot. Otherwise, the bootloader will not allow you to boot.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Would the file go under PDA (AP) or BL?
gorilla29 said:
Would the file go under PDA (AP) or BL?
Click to expand...
Click to collapse
PDA (AP)
JudgeFutta said:
PDA (AP)
Click to expand...
Click to collapse
I tried everything you suggested. I am able to boot into the OS, but only while connected to power. Definitely helped, but didn't solve.
Any suggestions?
gorilla29 said:
I tried everything you suggested. I am able to boot into the OS, but only while connected to power. Definitely helped, but didn't solve.
Any suggestions?
Click to expand...
Click to collapse
However, the phone will still shut down once booted, despite it being connected to power.
gorilla29 said:
However, the phone will still shut down once booted, despite it being connected to power.
Click to expand...
Click to collapse
It may be the battery or the phone just went out.
JudgeFutta said:
It may be the battery or the phone just went out.
Click to expand...
Click to collapse
Maybe, but the phone never shuts off during recovery. I bet the phone is just done. Lol

Okay XDA, I need your help getting my phone running. (Black screen problem)

Okay so I bought this S6, 2 days ago from a guy really cheap. I have some experience with Samsung devices so I thought I could fix it piece of cake turns out I can't. So I got twrp, and download mode working and I can transfer files to the phone while in twrp no problem. Download mode works fine too. The problem I have is that whatever I do the phone shows the "Samsung Galaxy S6, powered by android" logo and then the screen turns black. The little led light keeps shining blue light and the phone even vibrates sometimes.
At first I though that I could just flash stock 6.0.1 rom though odin and I did that. Same problem black screen (I got the firmware from sammobile). After that I tried the tyrannus rom and I followed his instruction and same problem again. At last I tried XtreStoLite and same problem. A guy in another thread told me that I need to reflash a kernel so I tried the SpaceX MM Kernel and still the same problem.
Oh almost forgot the device is the SM-G920F.
Any thoughts?
So you have TWRP, format all data.
Download the modem and bootloader for MM and flash with odin in download mode.
https://www.androidfilehost.com/?fid=24531172553916563 under BL button
https://www.androidfilehost.com/?fid=24531172553916564 under CP button
Then flash stock 6.0.1 firmware
*links are from XtreStoLite DeoMod Edition 3.3.1 MM thread
Nedrozak said:
So you have TWRP, format all data.
Download the modem and bootloader for MM and flash with odin in download mode.
https://www.androidfilehost.com/?fid=24531172553916563 under BL button
https://www.androidfilehost.com/?fid=24531172553916564 under CP button
Then flash stock 6.0.1 firmware
*links are from XtreStoLite DeoMod Edition 3.3.1 MM thread
Click to expand...
Click to collapse
I've done exactly that and now I tried it again. So after everything is flashed I get the "Samsung Galaxy S6, powered by android" and then a blue droid logo that said "Installing system update" and something about erasing data, then it went back to "Samsung Galaxy S6, powered by android" and then black screen with a blue/cyan light. How long should I wait on that screen? I waited about 10 minutes and then I got a vibration from the phone but still black with the light. The samsung boot animation should come up if it's working right?
JD. A said:
I've done exactly that and now I tried it again. So after everything is flashed I get the "Samsung Galaxy S6, powered by android" and then a blue droid logo that said "Installing system update" and something about erasing data, then it went back to "Samsung Galaxy S6, powered by android" and then black screen with a blue/cyan light. How long should I wait on that screen? I waited about 10 minutes and then I got a vibration from the phone but still black with the light. The samsung boot animation should come up if it's working right?
Click to expand...
Click to collapse
Can you check if the EFS partition is not erased? In TWRP it should be like 2MB data.
Nedrozak said:
Can you check if the EFS partition is not erased? In TWRP it should be like 2MB data.
Click to expand...
Click to collapse
I clicked "backup" and it says that Boot is 28MB, System 3352MB, Data 766MB, Cache 0MB, Modem 42MB and EFS 2MB. This is so weird, I've never had this problem on any phone. By the way I let it "boot" for 20 minutes and after that vibration I got nothing more out of it.
EDIT: I tried to get it to boot again by just pressing reboot in twrp and now the "Samsung Galaxy S6, powered by android" keeps poping up and then it turns black and then it pops up again.
Are you flashing the correct country/carrier firmware?
Nedrozak said:
Are you flashing the the correct country/carrier firmware?
Click to expand...
Click to collapse
Should that matter? The guy I bought the phone from said that it was unlocked and I've tried to flash the Nordic firmware from Sammobile. There's 2 swedish stock firmwares, one is "Tre" and the other one is "VDS". I don't know what "VDS" means even though I tried to google it and Tre should be really bad for my reception. Should I try to flash the vds one?
JD. A said:
I clicked "backup" and it says that Boot is 28MB, System 3352MB, Data 766MB, Cache 0MB, Modem 42MB and EFS 2MB. This is so weird, I've never had this problem on any phone. By the way I let it "boot" for 20 minutes and after that vibration I got nothing more out of it.
EDIT: I tried to get it to boot again by just pressing reboot in twrp and now the "Samsung Galaxy S6, powered by android" keeps poping up and then it turns black and then it pops up again.
Click to expand...
Click to collapse
Is it still like that? You can stop it by holding the buttons for download mode and it will power off to go into download mode but when it powers off just press buttons for recovery and you will be back there.
---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------
JD. A said:
Should that matter? The guy I bought the phone from said that it was unlocked and I've tried to flash the Nordic firmware from Sammobile. There's 2 swedish stock firmwares, one is "Tre" and the other one is "VDS". I don't know what "VDS" means even though I tried to google it and Tre should be really bad for my reception. Should I try to flash the vds one?
Click to expand...
Click to collapse
Sure give it a try, you have nothing to loose! On the upper post when I said format all data, did you factory reset or used the "format all data" button?
Nedrozak said:
Is it still like that? You can stop it by holding the buttons for download mode and it will power off to go into download mode but when it powers off just press buttons for recovery and you will be back there.
---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------
Sure give it a try, you have nothing to loose! On the upper post when I said format all data, did you factory reset or used the "format all data" button?
Click to expand...
Click to collapse
I stopped the Samsung Galaxy S6 logo bootloop after a while. I pressed the advanced wipe and selected everything except for USB Storage, that's the same thing as format all data right?
JD. A said:
I stopped the Samsung Galaxy S6 logo bootloop after a while. I pressed the advanced wipe and selected everything except for USB Storage, that's the same thing as format all data right?
Click to expand...
Click to collapse
Yes! In the advanced wipe section look for the file system of the partitions.
System, Data and Cache should be ext4
Nedrozak said:
Yes! In the advanced wipe section look for the file system of the partitions.
System, Data and Cache should be ext4
Click to expand...
Click to collapse
I'm 99% sure that they're ext4 right now I'm flashing the Sweden(VDS) stock rom after that if it's not working I'll check. :good:
Nedrozak said:
Yes! In the advanced wipe section look for the file system of the partitions.
System, Data and Cache should be ext4
Click to expand...
Click to collapse
So after flashing the Sweden(VDS) it went back to the black screen, so I did a battery pull vol down + power and then I tried to start it again. Now it got to 2 cog wheels spinning and saying Android is starting optimizing app x out of 32. Then it went to Android is starting and starting apps. I waited there for 10 minutes and I got a vibration and then nothing, the cog wheels only kept spinning. Seems like it got stuck there. So I did the battery pull again, black screen then I tried to do a factory reset in the stock recovery and nothing change. Now I'm getting the black screen again.
This is so weird :crying:
OK! Try to flash it again and when you see optimizing turn the phone off. Then make a factory reset and boot up to see what is going to do.
Nedrozak said:
OK! Try to flash it again and when you see optimizing turn the phone off. Then make a factory reset and boot up to see what is going to do.
Click to expand...
Click to collapse
Okay, so I flashed the Sweden(VDS) and then when it booted it ended up with black screen, and then I did the battery pull and I got back to the android is starting screen with the cog wheel. Then I turned the phone off and and did a factory reset with samsungs recovery. Then when I started it I ended up with black screen again so I did a battery pull once again and started it. Then I got to the Android is starting screen with the cog wheels again, it changed the language to swedish though. Then it started optimizing apps xx of 34 and now its stuck at Android is starting starting apps. Do you think this might be a hardware problem? I'm have no clue what to do anymore.
Right now I'm downloading the Sweden(Tre) stock rom from sammobile, will report back later of if there's some changes.
If it is a hardware problem I can't think of what could it be. Anyways, waiting on the report. Hope this will work!
@Nedrozak Okay after a break I continued to try, the Sweden(Tre) firmware won't flash in odin. I've also tried to flash the phone in Kies and Smart Switch PC. Both programs ended up the same as before with the black screen with the blue led light. I couldn't even get it to the optimizing screen. I've also tried 5.1.1 and I can get it to the optimizing apps screen too, 5.0.2 can't be flashed.
I also found out using Kies and Smart Switch PC that the original firmware the phone used to have is the NEE firmware (Nordic Countries). Tomorrow I might go and ask some tech shop to estimate a repair cost, I might be able to get a new motherboard too for free we'll see what happens. I'm like out of options anyway seems like no one else on this forum seems to have the same problem so maybe it's the hardware that's faulty.
The last thing I might try is a custom rom like cyanogenmod, that I can try to flash otherwise I'm out of ideas, and energy too :silly:
Maybe leave it on cogwheels Android is starting and Starting apps during night? Then I'm afraid that the screen will burn and the screen in almost new and worth a bit of money.
JD. A said:
@Nedrozak Okay after a break I continued to try, the Sweden(Tre) firmware won't flash in odin. I've also tried to flash the phone in Kies and Smart Switch PC. Both programs ended up the same as before with the black screen with the blue led light. I couldn't even get it to the optimizing screen. I've also tried 5.1.1 and I can get it to the optimizing apps screen too, 5.0.2 can't be flashed.
I also found out using Kies and Smart Switch PC that the original firmware the phone used to have is the NEE firmware (Nordic Countries). Tomorrow I might go and ask some tech shop to estimate a repair cost, I might be able to get a new motherboard too for free we'll see what happens. I'm like out of options anyway seems like no one else on this forum seems to have the same problem so maybe it's the hardware that's faulty.
The last thing I might try is a custom rom like cyanogenmod, that I can try to flash otherwise I'm out of ideas, and energy too :silly:
Maybe leave it on cogwheels Android is starting and Starting apps during night? Then I'm afraid that the screen will burn and the screen in almost new and worth a bit of money.
Click to expand...
Click to collapse
Yes, it will be very bad to leave it on. Maybe going to the tech shop is the best option even if you can't get free motherboard.

Failed to install Xposed - phone is stuck on loading screen

Hello,
I tried to flash Xposed using TWRP on my brand new rooted Samsung Galaxy S7. The installation seemed to fail, and I tried rebooting the phone, and now it gets stuck on the starting Samsung Galaxy S7 screen. After a couple of minutes, it loads the Samsung logo, and then gets stuck on that.
I tried to hard reboot a few times using Power + Vol Down, but it doesn't help, and I don't know how to just turn the phone off as opposed to reboot it (holding down Power by itself does nothing) so I can attempt to access Recovery.
Can anyone suggest what to do?
Thanks in advance, help is much appreciated.
EDIT: So, I managed to get into TWRP Recovery by quickly pressing Power + Vol Up + Home after hard rebooting, and I tried to wipe the Cache and Dalvik, but even that fails. I get the same "unable to mount storage" error. :/
YamiWheeler said:
Hello,
I tried to flash Xposed using TWRP on my brand new rooted Samsung Galaxy S7. The installation seemed to fail, and I tried rebooting the phone, and now it gets stuck on the starting Samsung Galaxy S7 screen. After a couple of minutes, it loads the Samsung logo, and then gets stuck on that.
I tried to hard reboot a few times using Power + Vol Down, but it doesn't help, and I don't know how to just turn the phone off as opposed to reboot it (holding down Power by itself does nothing) so I can attempt to access Recovery.
Can anyone suggest what to do?
Thanks in advance, help is much appreciated.
Click to expand...
Click to collapse
Hi mate
more info.........phone model , files used , procedure used......
check here
MAX 404 said:
Hi mate
more info.........phone model , files used , procedure used......
check here
Click to expand...
Click to collapse
Hi, sorry.
The phone model is SM-G930F.
I followed this guide: http://www.androidbeat.com/2016/05/install-xposed-framework-on-samsung-galaxy-s7/
Using the Installation ZIP file listed under "For 64-bit Android devices like HTC One A9, Nexus 6P and Nexus 5X" from here: http://www.androidbeat.com/download-xposed-framework-installer/ - the filename is "xposed-v86-sdk23-arm64.zip"
And I flashed it using TWRP Recovery.
The error it gave me when it failed was akin to "cannot mount storage."
So, I managed to get into TWRP Recovery by quickly pressing Power + Vol Up + Home after hard rebooting, and I tried to wipe the Cache and Dalvik, but even that fails. I get the same "unable to mount storage" error. :/
YamiWheeler said:
So, I managed to get into TWRP Recovery by quickly pressing Power + Vol Up + Home after hard rebooting, and I tried to wipe the Cache and Dalvik, but even that fails. I get the same "unable to mount storage" error. :/
Click to expand...
Click to collapse
Hi
Un install the framework you used is not the correct one , for Samsung devices you need the unofficial one from Wanam, the official does not work correctly
you need this one.
xposed-v86.0-sdk23-arm64-custom-build-by-wanam-20160709.zip
MAX 404 said:
Hi
Un install the framework you used is not the correct one , for Samsung devices you need the unofficial one from Wanam, the official does not work correctly
you need this one.
xposed-v86.0-sdk23-arm64-custom-build-by-wanam-20160709.zip
Click to expand...
Click to collapse
Well, I've ****ed my phone.
I formatted the data to remove encryption on storage, which another thread on XDA suggested, and now TWRP is telling me I have no OS.
YamiWheeler said:
Well, I've ****ed my phone.
I formatted the data to remove encryption on storage, which another thread on XDA suggested, and now TWRP is telling me I have no OS.
Click to expand...
Click to collapse
Mate you had the wrong framework that was it..........
well start all over flash stock rom with Odin , re root , install xposed
No big deal.....just wasted time
MAX 404 said:
Mate you had the wrong framework that was it..........
well start all over flash stock rom with Odin , re root , install xposed
No big deal.....just wasted time
Click to expand...
Click to collapse
Yeah, I know, but I couldn't flash anything with TWRP. :/ including the Uninstaller. So I followed the suggestion on this thread:
http://forum.xda-developers.com/s7-edge/help/twrp-mount-data-unable-to-crypto-footer-t3360331
Which said to format data to remove encryption, but that ended up removing the OS somehow...
Can you please point me in the direction of the stock ROM? I Googled it and searched XDA but I can't find anything but this:
http://forum.xda-developers.com/galaxy-s7/how-to/s7-s7e-stock-rom-bootloader-modem-t3383963
And the link for "G930FXXU1APD3 (BTU United Kingdom Unbranded)" doesn't work there...
This is really frustrating. Thanks for your help so far.
YamiWheeler said:
Yeah, I know, but I couldn't flash anything with TWRP. :/ including the Uninstaller. So I followed the suggestion on this thread:
http://forum.xda-developers.com/s7-edge/help/twrp-mount-data-unable-to-crypto-footer-t3360331
Which said to format data to remove encryption, but that ended up removing the OS somehow...
Can you please point me in the direction of the stock ROM? I Googled it and searched XDA but I can't find anything but this:
http://forum.xda-developers.com/galaxy-s7/how-to/s7-s7e-stock-rom-bootloader-modem-t3383963
And the link for "G930FXXU1APD3 (BTU United Kingdom Unbranded)" doesn't work there...
This is really frustrating. Thanks for your help so far.
Click to expand...
Click to collapse
Just take it easy .....
I like this guide to flash / upgrade stock roms
http://forum.xda-developers.com/galaxy-s7/how-to/official-stock-firmware-update-odin-t3369431
or from here
UK unbranded (BTU)
http://www.sammobile.com/firmwares/database/SM-G930F/BTU/
or 3 network
http://www.sammobile.com/firmwares/database/SM-G930F/H3G/
if you are rooting unbranded should be fine
MAX 404 said:
Just take it easy .....
I like this guide to flash / upgrade stock roms
http://forum.xda-developers.com/galaxy-s7/how-to/official-stock-firmware-update-odin-t3369431
or from here
UK unbranded (BTU)
http://www.sammobile.com/firmwares/database/SM-G930F/BTU/
or 3 network
http://www.sammobile.com/firmwares/database/SM-G930F/H3G/
if you are rooting unbranded should be fine
Click to expand...
Click to collapse
Thank you so much for your patience and help.
Normally I have no problem flashing things. :/
YamiWheeler said:
Thank you so much for your patience and help.
Normally I have no problem flashing things. :/
Click to expand...
Click to collapse
is one of those day........ S**** happens

Bootloop after succesful odin flash.

Hello,
I tried flashing TWRP recovery with Odin. Everything went fine, Odin said "PASS". But when I tried to get into TWRP right after the flashing was completed, my device got stuck on the booting screen where it just says "Samsung galaxy s8 plus - powered by android"
If I hold down the power button, nothing happens. I've held it down for longer than a minute and still nothing happened.
If I hold down the power button, bixby button and volume up, nothing happens.
If I hold down the power button, bixby button and volume down, the device seems to be rebooting but still gets stuck on booting screen.
What can I do to fix this? I'm getting quite desperate..
What were you on and what were you flashing to?
djcrystals said:
What were you on and what were you flashing to?
Click to expand...
Click to collapse
I previously flashed TWRP along with stuff like magisk manager.
All I did was flash a newer version of TWRP after having resetted my device.
Which EXACT Model and version of phone do you have? Do you know which build number it was? I'm just trying to get more info so we can help.
djcrystals said:
Which EXACT Model and version of phone do you have? Do you know which build number it was? I'm just trying to get more info so we can help.
Click to expand...
Click to collapse
I was asleep, sorry.
Anyways, it's the G955F, unlocked Galaxy S8+ from the Netherlands. By build number, do you mean the OS version? If so, it was the latest november security patch (I don't know the exact number). If you mean the TWRP version, that was 3.1.1-2.
Check this https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
djcrystals said:
Check this https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
Click to expand...
Click to collapse
I tried getting the bootloader of the build before the latest one. But I can't seem to download it anywhere without having to pay 50 dollars or without having to wait 20 hours for it to download..
Try http://updato.com ?
djcrystals said:
Try http://updato.com ?
Click to expand...
Click to collapse
Oh thanks.
I actually already started a download halfway through yesterday and that just finished. I did that method that you linkedin the video, which worked like a charm. I then flashed the latest firmware and everything worked fine! However, halfway through the "Starting android.." screen, the battery died.. It's charging up right now but I hope nothing was corrupted by that..
Should be ok... ?
djcrystals said:
Should be ok... ?
Click to expand...
Click to collapse
The device works fine again!
Thanks dude, saved my (phone's) life!!
cyborgium said:
The device works fine again!
Thanks dude, saved my (phone's) life!!
Click to expand...
Click to collapse
Yea! Coolio...
not working, pls help. stuck in bootloop
my s8 keeps bootlooping. i cant get into hard reset. only volume down+bixby+power. i download 45gb of firmware. i tried many times different methods didnt work. odin gives a pass but still bootloops. i tried with android 9 and 8 firmware. please help
SM-G950FD (XSG)

Categories

Resources