Hi,
I recently installed Google Edition 4.3 ROM for i9505, found here: http://forum.xda-developers.com/showthread.php?t=2348272
It booted up fine, I put in my google account details etc, but Play Store kept crashing, no matter what I did, it kept on crashing.
So I tried rebooting, and then it got stuck on the Samsung logo.. I went back to recovery and flashed the 4.2.2 Google Edition ROM.
Play Store is fine on this but I have not yet attempted to reboot it. I would really like to have 4.3, but I am unaware of why it's doing this.
He provided a bootloop fix which I also tried, although I suspect that's not for the Samsung logo but the Google one.
Does anyone know what's causing Play Store to crash?
EDIT: I have just rebooted 4.2.2 and all is fine, so it's just the 4.3 ROM
Have you tried this 4.3 ROM?
http://forum.xda-developers.com/showthread.php?t=2341026
I have not, however I will in a little while.
Does this one have any advantages or disadvantages over the one I attempted to use?
juckeyy said:
Have you tried this 4.3 ROM?
http://forum.xda-developers.com/showthread.php?t=2341026
Click to expand...
Click to collapse
Got bootloop on that ROM today :-|
Related
I really need some help getting the dialer and phone working again on my s4 from t mobile (I'm on mobilicity) , I had installed the google play edition 4.2 rom by jamal on my stock samsung g4 which went smoothly enough and today I tried updating to 4.3 using this rom:
http://forum.xda-developers.com/showthread.php?t=2370213
and it installed fine but now whenever I try and call someone it says "unfortunately dialer has stopped working." I basically can't make any calls at all. help would be appreciated!!
I think I've also lost root access as I can't run the su app.
update*
I tried reinstalling the 4.2 google rom by jamal and it started looping during bootup, so I installed 4.3 back on it.
crimsonsoulz said:
I really need some help getting the dialer and phone working again on my s4 from t mobile (I'm on mobilicity) , I had installed the google play edition 4.2 rom by jamal on my stock samsung g4 which went smoothly enough and today I tried updating to 4.3 using this rom:
http://forum.xda-developers.com/showthread.php?t=2370213
and it installed fine but now whenever I try and call someone it says "unfortunately dialer has stopped working." I basically can't make any calls at all. help would be appreciated!!
I think I've also lost root access as I can't run the su app.
update*
I tried reinstalling the 4.2 google rom by jamal and it started looping during bootup, so I installed 4.3 back on it.
Click to expand...
Click to collapse
Hi,
Look HERE
Get back to stock, then, start again.
Sent telepathically from my S4
I have a 1337m gs4 and am currently on beanstalk 4.3 and love it.I was waiting for the kit kat canadian 4.4 rom version to come out and it did.
I installed the rom and it went on ok, but after the beanstalk screen finally loaded igot the messages unfortunately the process com google process location has stopped. it also says unfortunately the set up wizard has stopped. ive looked through the whole thread and cannot see anything regarding using a special kernel unless i have missed something, and the checksum was ok . has anyone encountered this?
Hello, I have an unlocked Samsung S4 GT-i9505 UK model, and would like to put it back to stock Samsung Android.
Originally on Touchwiz Android 4.2 > changed to ‘GALAXY S4 Google Play Edition 4.3 v1.3 CoOoL_BoY’, which has been working ok, but now I’d like to go back to stock Samsung Android.
I have ‘openrecovery-twrp-2.6.3.1-jfltexx.tar’ installed on my phone.
When trying to wipe/install the latest ‘BTU-I9505XXUEMK8-20131123173333.zip’ via TWRP I encounter many errors such as ‘unable to mount system/cache/efs/modem’ etc.
I tried wiping and repairing permissions etc but whenever I try to install stock Samsung android I get an error similar to ‘Error flashing zip’.
Could this be due to using Google Play Edition VS Stock Samsung Android? Has anyone encountered this, or would be able to help?
In the meantime I had to go back to the 'Google Play Edition 4.3 v1.3 CoOoL_BoY' rom. :crying:
Many thanks
Jez_ said:
Hello, I have an unlocked Samsung S4 GT-i9505 UK model, and would like to put it back to stock Samsung Android.
Originally on Touchwiz Android 4.2 > changed to ‘GALAXY S4 Google Play Edition 4.3 v1.3 CoOoL_BoY’, which has been working ok, but now I’d like to go back to stock Samsung Android.
I have ‘openrecovery-twrp-2.6.3.1-jfltexx.tar’ installed on my phone.
When trying to wipe/install the latest ‘BTU-I9505XXUEMK8-20131123173333.zip’ via TWRP I encounter many errors such as ‘unable to mount system/cache/efs/modem’ etc.
I tried wiping and repairing permissions etc but whenever I try to install stock Samsung android I get an error similar to ‘Error flashing zip’.
Could this be due to using Google Play Edition VS Stock Samsung Android? Has anyone encountered this, or would be able to help?
In the meantime I had to go back to the 'Google Play Edition 4.3 v1.3 CoOoL_BoY' rom. :crying:
Many thanks
Click to expand...
Click to collapse
You can try this rom
http://forum.xda-developers.com/showthread.php?t=2250824
In the second post are the flashing instructions
bragra said:
You can try this rom
http://forum.xda-developers.com/showthread.php?t=2250824
In the second post are the flashing instructions
Click to expand...
Click to collapse
Yeah I tried the same stock one from this link thanks, but no joy.
I've now restored to stock using this link http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/
Hello Guys,
I'm with a problem in my #nexus4 .. If i update my device to #android 4.3 or newer my phone gets #bootloop and don't start anymore. I read a lot of tips to solve that but nothing worked. I tried to reflash with stock firmware from google (developers images to nexus devices) but didnt work (flash-all.bat), i tried use #NexusRootToolkit but happened the same situation. I tried to install the versions 4.3, 4.4, 4.4.2, 4.4.4, 5.0 and happened the same problem at all.
Someone could help me? Because i didnt find how to solve since a last year. I'm using android 4.2.2 because its the only one that works.
I tried all methods like flash stock rom, but, wont works. ....
Could someone help me with that please??
I have the same problem, can someone help ?
Any updates?
I have the same problem. I used to get the bootloop when I updated from 4.4.3 to 4.4.4 and from 4.4.4 to 5.0 and from 5.0 to 5.01 and in all those times, from what I can recall, a wiping of the cache/delvik + fix-permissions + install the modified boot image from NRT - solved the problem.
However - a couple of days ago, after getting the Google Cardboard and playing around with it, installing all the VR stuff and playing with magnets around my phone to get it to work with the VR - I think I must've damaged something because it suddenly died and refused to get back up and out of a bootloop. I tried the above procedures and it didn't work. I went back to version 5.0, then 4.4.4 and further back till only 4.2.2 worked, as with the first post here. It's the only version that doesn't give me the bootloop. If I try then to upgrade I again get the bootloop, whether it's a full flashing or an OTA update (to 4.3).
One thing I noticed with 4.2.2 - it's not acting all that well: when I download apps through Google Play some of them seem to get stuck at 85-95% on the download and won't install. Maybe I have a faulty storage issue...?
Any insight on how to fix that?? Any news from those who experienced the same issue?
Thanks!
tiagomoraisc said:
Hello Guys,
I'm with a problem in my #nexus4 .. If i update my device to #android 4.3 or newer my phone gets #bootloop and don't start anymore. I read a lot of tips to solve that but nothing worked. I tried to reflash with stock firmware from google (developers images to nexus devices) but didnt work (flash-all.bat), i tried use #NexusRootToolkit but happened the same situation. I tried to install the versions 4.3, 4.4, 4.4.2, 4.4.4, 5.0 and happened the same problem at all.
Someone could help me? Because i didnt find how to solve since a last year. I'm using android 4.2.2 because its the only one that works.
I tried all methods like flash stock rom, but, wont works. ....
Could someone help me with that please??
Click to expand...
Click to collapse
no good news ...
hummus said:
I have the same problem. I used to get the bootloop when I updated from 4.4.3 to 4.4.4 and from 4.4.4 to 5.0 and from 5.0 to 5.01 and in all those times, from what I can recall, a wiping of the cache/delvik + fix-permissions + install the modified boot image from NRT - solved the problem.
However - a couple of days ago, after getting the Google Cardboard and playing around with it, installing all the VR stuff and playing with magnets around my phone to get it to work with the VR - I think I must've damaged something because it suddenly died and refused to get back up and out of a bootloop. I tried the above procedures and it didn't work. I went back to version 5.0, then 4.4.4 and further back till only 4.2.2 worked, as with the first post here. It's the only version that doesn't give me the bootloop. If I try then to upgrade I again get the bootloop, whether it's a full flashing or an OTA update (to 4.3).
One thing I noticed with 4.2.2 - it's not acting all that well: when I download apps through Google Play some of them seem to get stuck at 85-95% on the download and won't install. Maybe I have a faulty storage issue...?
Any insight on how to fix that?? Any news from those who experienced the same issue?
Thanks!
Click to expand...
Click to collapse
I think it's a defective device. You have to repair or change it. Sorry
No Sensors
Looks like none of my sensors are working, judging from 3 sensor testing apps I've downloaded. Seems as if the motherboard is defective.
tiagomoraisc said:
no good news ...
Click to expand...
Click to collapse
hummus said:
Looks like none of my sensors are working, judging from 3 sensor testing apps I've downloaded. Seems as if the motherboard is defective.
Click to expand...
Click to collapse
The same situation I have
Fix
tiagomoraisc said:
Hello Guys,
I'm with a problem in my #nexus4 .. If i update my device to #android 4.3 or newer my phone gets #bootloop and don't start anymore. I read a lot of tips to solve that but nothing worked. I tried to reflash with stock firmware from google (developers images to nexus devices) but didnt work (flash-all.bat), i tried use #NexusRootToolkit but happened the same situation. I tried to install the versions 4.3, 4.4, 4.4.2, 4.4.4, 5.0 and happened the same problem at all.
Someone could help me? Because i didnt find how to solve since a last year. I'm using android 4.2.2 because its the only one that works.
I tried all methods like flash stock rom, but, wont works. ....
Could someone help me with that please??
Click to expand...
Click to collapse
I made a similar thread, and found a fix.
Here http://forum.xda-developers.com/nexus-4/help/nexus-4-jellybean-4-2-2-t3472292#post68941174
Hello guys!
I'm a new guy here, but found no answers to the following issues.
So i've got the 6.0.1 update to Note 4, and now im stuck with issues like the Phone just freezes, crashes and hangs for like 1 minute after i can use it again, so i had to download the WakeLock application from the google play store.
I'm just curious, is this a phone issue, or its releated to the stock rom? I should flash a new ROM based on guides here, or is there any fixes to this issue?
Thanks.
You may have to try a factory reset. I haven't heard of this issue
Mine went into the same issues since a day or 3. Factory reset, cache wipe, no dice until now.
clawlancer said:
Hello guys!
I'm a new guy here, but found no answers to the following issues.
So i've got the 6.0.1 update to Note 4, and now im stuck with issues like the Phone just freezes, crashes and hangs for like 1 minute after i can use it again, so i had to download the WakeLock application from the google play store.
I'm just curious, is this a phone issue, or its releated to the stock rom? I should flash a new ROM based on guides here, or is there any fixes to this issue?
Thanks.
Click to expand...
Click to collapse
i had this problem with my n910C but it was after flashing custom kernel ,
factory reset and it was working like a charm then