Database Users

[Q] Couple of questions...

Hi! I just got my xplay a month or two ago, and my last phone was a iphone. As such, stepping from the relatively easier to handle ios to android system's not exactly a piece of cake...
And I still have a couple questions despite lurking in this forums for a while...
1) im running 2.3.2 , rooted with gingerbreak. I heard there's an improvement in battery life.. so im quite tempted to update, but the thought of bloatware coming back kind of scares me.. ._.
So should I update?
2) is unlocked or locked bootloader better?
3) finally, will there be a final or complete version of cm7?
Also, would be great if anyone could explain what is an OTA and kernel...
Thanks!

1) its up to you, it is possible to upgrade with root as long as you have any model except a r800 x
2) I dont think either is better just depends on what you want to do to your phone
3) It depends what you mean by complete. There will probably be a stable version that is better than the stock rom eventually, but im not a dev
Ota means "over the air" and a kernel if im not mistaken is the part of the phone responsible for managing sysyem resources and the like. Not that I know much about anything and I could be wrong lol
Sent from my R800i using XDA App

LemonPlusTea said:
Hi! I just got my xplay a month or two ago, and my last phone was a iphone. As such, stepping from the relatively easier to handle ios to android system's not exactly a piece of cake...
And I still have a couple questions despite lurking in this forums for a while...
1) im running 2.3.2 , rooted with gingerbreak. I heard there's an improvement in battery life.. so im quite tempted to update, but the thought of bloatware coming back kind of scares me.. ._.
So should I update?
2) is unlocked or locked bootloader better?
3) finally, will there be a final or complete version of cm7?
Also, would be great if anyone could explain what is an OTA and kernel...
Thanks!
Click to expand...
Click to collapse
This will be my second numbered answer today. Anyway:
1) What model do you have? I assume it's an r800i or r800a. If it is, I would head over to the development section and check out how to get the UK generic firmware on your phone without unlocking the boot loader. I did that, rooted it, then updated to 2.3.3 and removed a lot of bloat and it's good to go now.
2) I have unlocked the boot loader on every Android I've owned, but I haven't on this phone. I wouldn't until development takes off a little bit more. It will soon, but I probably won't even do it then, personally.
3) Yes, we have great people working on it. It's progressing majorly with each update.
Just next time search before posting...nah, I'm just kidding. Welcome to Android.
adb shove iPad2post.apk to /forum/thread

OTA means you are updating the firmware on your phone through your phone over wifi.
If you didn't remove the boats you can still do it by pressing the software update button on your phone. Just make sure that your bootloader is is still LOCKED.
Sent from my XPlay using XDA App.

Thanks guys! I'll try to flash the firmware on my phone after I get home from school. my xplay is a r800i. Also, if I use the UK firmware and update to 2.3.3, will it affect my ability to update to 2.3.4 as I live in Singapore?

No, when 2.3.4 comes out it would probably be available to generic uk before any other versions. As long as you freeze and not remove boats, you would be able to ota update to 2.3.4
Sent from my XPlay using XDA App.

Hey guys Im back from school.
Is it this thread to follow ?
http://forum.xda-developers.com/showthread.php?t=1119074
Because I saw another one ..
http://forum.xda-developers.com/showthread.php?t=1097591
^ which requires an unlocked BL. :O

Oh my god.. I didnt enable debugging and the process stopped halfway.. now the phone displays an exclaimation mark next to a phone.. did i just brick my phone? ...
EDIT : googled around and now im trying to restore my phone via SEUS...

Ok.. my phone started up fine after running SEUS.. but I clicked restore to factory instead of update..
I want to try updating to 2.3.3 with root again.. So can anyone point out anything I did wrong the previous time?
1. I downloaded the generic UK version (http://forum.xda-developers.com/showthread.php?t=1119074) and flashtool 0.2.8 (http://forum.xda-developers.com/showthread.php?t=920746)
2. I used flashtool and flashed the .tft file and followed the onscreen instructions...
3. the flashing stops halfway cause i didnt enable usb debugging (?) and it causes my phone to be unable to boot up and trauma for me for panicking for 30 minutes. ._.
I tried flashing again with USB debugging on..?
My version is now 2.3.3 after I restored with SEUS, however.
07/046/2011 18:46:02 - INFO - Flashing adsp.sin
07/046/2011 18:46:05 - INFO - Flashing kernel.sin
07/046/2011 18:46:07 - INFO - Flashing amss_fs.sin
07/046/2011 18:46:07 - INFO - Flashing fota1.sin
07/046/2011 18:46:08 - INFO - Flashing fota0.sin
07/046/2011 18:46:09 - INFO - Flashing apps_log.sin
07/046/2011 18:46:09 - INFO - Flashing amss.sin
07/046/2011 18:46:19 - INFO - Flashing cache.sin
07/046/2011 18:46:20 - INFO - Flashing system.sin
07/046/2011 18:46:44 - ERROR - Error flashing. Aborted
07/046/2011 18:46:44 - INFO - Now unplug the device and power it on
07/046/2011 18:46:44 - INFO - Then go to application settings
07/046/2011 18:46:44 - INFO - turn on Unknown Sources and Debugging
( after that resulted in the same problem as before but luckily I knew how to fix it again.. ._. )

It might be that you're not using the latest version of flashtool, it's 0.2.9.1 and it's the beta one and afaik it's the only one to support the play.
Regards Dousan...

Dousan said:
It might be that you're not using the latest version of flashtool, it's 0.2.9.1 and it's the beta one and afaik it's the only one to support the play.
Regards Dousan...
Click to expand...
Click to collapse
I see.. Cause I thought beta might not be stable!
Thanks alot! Time to go try again ^_^
EDIT : Same error with the newest flashtool.. ._.
Crapp...
I unpacked the 0.2.9.1 and ran the X10 Flash Tool... and it still doesnt like me..
It seems it hates me more and more..
now instead of even starting flashing after i send my phone into flash mode it gives me this error..
ERROR - USB\VID_0FCE&PID_ADDE\5&1F015A4B&0&5
Triple edit : Now Im back to square one of flashing till system.sin and getting an error.. ._.

LemonPlusTea said:
I see.. Cause I thought beta might not be stable!
Thanks alot! Time to go try again ^_^
EDIT : Same error with the newest flashtool.. ._.
Crapp...
I unpacked the 0.2.9.1 and ran the X10 Flash Tool... and it still doesnt like me..
It seems it hates me more and more..
now instead of even starting flashing after i send my phone into flash mode it gives me this error..
ERROR - USB\VID_0FCE&PID_ADDE\5&1F015A4B&0&5
Triple edit : Now Im back to square one of flashing till system.sin and getting an error.. ._.
Click to expand...
Click to collapse
Maybe it's a corrupt download or the unpacking of the .zip/.rar file went bad. Could try a reunpacking or/and redownload?
Regards Dousan...

Redownloaded the flashtool 2 times and the generic UK ftf 3 times already.. could it be my computer's problem?

LemonPlusTea said:
Redownloaded the flashtool 2 times and the generic UK ftf 3 times already.. could it be my computer's problem?
Click to expand...
Click to collapse
I know back in my Galaxy S days the firmware tool Samsung used worked on one of my computers but didn't work on the other. I would try another computer if you had access to one.
adb shove iPad2post.apk to /forum/thread

TheBassman369 said:
I know back in my Galaxy S days the firmware tool Samsung used worked on one of my computers but didn't work on the other. I would try another computer if you had access to one.
adb shove iPad2post.apk to /forum/thread
Click to expand...
Click to collapse
Alright, I'll try it with my sister's laptop ^^..
Entire day has been miserable without my apps... :l

Nope.. still doesnt work.. ._.

LemonPlusTea said:
Nope.. still doesnt work.. ._.
Click to expand...
Click to collapse
Man. That's crazy. I have no idea what to do. Hopefully you can get it.

When flashing, have you ticked the 'erase data' (I'm not sure it's the exact name) or are you flashing without erasing? Cus it looks like that's where the error occurs when it's supposed to flash the data?
Regards Dousan...

Did you install the Sony software from your phone first?
Mine needed it to get the drivers. It said it had errors but I let it go for a while and it finished no problem.

Dousan said:
When flashing, have you ticked the 'erase data' (I'm not sure it's the exact name) or are you flashing without erasing? Cus it looks like that's where the error occurs when it's supposed to flash the data?
Regards Dousan...
Click to expand...
Click to collapse
Yeah I checked the erase data box all the time...
@ncaissie, im not entirely sure what you mean... Would you mind explaining?

[Q] Can't flash, Cant root !

Hello, i have an Xperia Play 2.3.3/3.0.1.A.0.145 Clean Bootloader locked version.
And i want to root it with this thread : http://forum.xda-developers.com/showthread.php?t=1116090
(And the unlocking bootloader way is not an option because i had a lot of problems with it and i can't flash anything with it)
anyway, the problem is when i plug my phone and the flashtool asks me what device i choose X10 (the first option)
then i choose the FW and select all the files and cleck flash.
and i fallow the instructions by unplugging my phone and hold the back button and plug it again.
So far so good, but when the flashing begins and start with the first file, this massage appears:
13/013/2011 05:13:49 - ERROR - Error flashing. Aborted
13/013/2011 05:13:49 - INFO - Now unplug the device and power it on
13/013/2011 05:13:49 - INFO - Then go to application settings
13/013/2011 05:13:49 - INFO - turn on Unknown Sources and Debugging
And yes i did what the massage told me to do.
and i tried to flash so many times with no good.
so please help me or tell me what i'm doing wrong.

Are you using the beta version of flashtool? (think it's 2.9.1). It's the only one supporting the play. The reason I ask is I don't choose any phone when flashing I only have a x10 .exe when flashtool is extracted to my desktop
Regards Dousan...

When I go to use FlashTool, I get like 3 options as far as 'firmware'. Two X10 ones, and a 'Generic UK Xperia Play' one. The latter has about 8 or 9 different files in the pop-up column, while the other two only have like 2 files each. I think I'm supposed to flash the firmware that says Xperia Play UK Generic, correct?

Dousan said:
Are you using the beta version of flashtool? (think it's 2.9.1). It's the only one supporting the play. The reason I ask is I don't choose any phone when flashing I only have a x10 .exe when flashtool is extracted to my desktop
Regards Dousan...
Click to expand...
Click to collapse
Yes i use that version. And it only ask me that if i plugged my phone and it was on with the debugging enabled. And i also tried flashing with my phone turned off from the start.

kershner25 said:
When I go to use FlashTool, I get like 3 options as far as 'firmware'. Two X10 ones, and a 'Generic UK Xperia Play' one. The latter has about 8 or 9 different files in the pop-up column, while the other two only have like 2 files each. I think I'm supposed to flash the firmware that says Xperia Play UK Generic, correct?
Click to expand...
Click to collapse
Yes. And when it's done you root it with gingerbreak or any way you like. and finally you do OTA update.
Note: Your bootloader must be locked.

ddsds said:
Yes. And when it's done you root it with gingerbreak or any way you like. and finally you do OTA update.
Note: Your bootloader must be locked.
Click to expand...
Click to collapse
And my bootloader is more than likely going to be locked, right? I bought my XPlay by renewing my contract with Verizon.

kershner25 said:
And my bootloader is more than likely going to be locked, right? I bought my XPlay by renewing my contract with Verizon.
Click to expand...
Click to collapse
If you didn't unlock it your self, Then it should be locked.

@ddsds it might be the file you're trying to flash that's corrupt or something, maybe a redownload will help. Have you installed the ggsetup.exe? You might also try deleting flashtool and re-extract it again?
This is how I proceed with flashing:
1. Turn phone off.
2. Start flashtool.
3. Hit flash button in program and wait for it to tell me to plug in phone.
4. Plug in phone - it flashes.
5. Turn on phone.
(first time I flashed I chose the fw file and I only have the UK generic for the play located in that folder wich I downloaded from a thread here on xda).
(make sure unknown sources and debugging is on)
Regards Dousan...

Try http://www.google.ca/m/url?ei=M71LT...IQFjAA&usg=AFQjCNECIZB1p3FODBns0hmMTmHO4GOJvA very noob friendly

sdlaurin said:
Try http://www.google.ca/m/url?ei=M71LT...IQFjAA&usg=AFQjCNECIZB1p3FODBns0hmMTmHO4GOJvA very noob friendly
Click to expand...
Click to collapse
I fanally got it to work with the hilp of your link.
But now i am stuck with rooted .184 FW .
And can't do OTA update, Because if i did i will end up with 4.0.A.2.368.
And so far it's unrootable

[Official] XT1052 Retail.en.GB OTA + FXZ/SBF (Full Rom)

As per screenshot 5.1 OTA update for Retail GB is out.
Files:
--> Retail.en.GB 4.4.4 FXZ. (Full ROM) (Google Drive)
--> Retail.en.GB 5.1 OTA zip. (3 Parts) (Google Drive)
--> Retail.en.GB 5.1 OTA zip. (1 Part) (Mega) [May be having issues]
--> Retail.en.GB 5.1 OTA zip. (1 Part) (Google Drive)
--> Numerous 5.1 & 4.4.4 FXZ (FULL ROMS) (FileFactory)
Credits:
@mlodykaras
@beljim7419
NB: REMEMBER TO BE ROOTED BEFORE SO YOU CAN ACCESS /CACHE PARTITION AFTER DOWNLOAD OF THE OTA ZIP HAS FINISHED. I learnt this the hard way.
NB: SO FAR MOTOROLA DOWNLOAD MANAGER DOESN'T WORK FOR NEWER PHONES UPDATING.
NB: REMEMBER TO HIT THAT THANKS BUTTON AND TO RATE THE THREAD. THANKS :good:
Last Updated: (YYYY-MM-DD)
2015-07-04

Bugs:
--> Dialog for bluetooth file sending progress is still KK.
--> Wave to wake up (I know they removed it therefore its a bug in my eyes)
--> I'm having Wi-Fi issues with not seeing certain routers and connecting, even though its saved and even after a radio cache clear using fastboot.
--> I'm having YouTube video playback issues in the YouTube App, even after I set to use the old AwesomePlayer.
--> I'm having general UI lag and apps hanging.
--> For me boot animation lag is now a norm, even after I updated Moto Boot Services. On KK it was extremely rare.
--> YOU LET ME KNOW...!
Last Edited: (YYYY-MM-DD)
2015-07-04

Reserve No. 2

To trick MDM into seeing the update, put your phone into airplane mode, reboot to recovery, erase cache, reboot normally, then connect to MDM and check for updates.

How do i clear cache in stock recovery?

stealtheye said:
How do i clear cache in stock recovery?
Click to expand...
Click to collapse
In stock recovery, you will see an option to clear cache.

_litz said:
To trick MDM into seeing the update, put your phone into airplane mode, reboot to recovery, erase cache, reboot normally, then connect to MDM and check for updates.
Click to expand...
Click to collapse
kenosis said:
In stock recovery, you will see an option to clear cache.
Click to expand...
Click to collapse
Only the see the open android with red triangle?
Edit: Got the menu.
Edit 2: This is taking quite a while. Normal?

Yes, it can take 10-20 minutes.

_litz said:
To trick MDM into seeing the update, put your phone into airplane mode, reboot to recovery, erase cache, reboot normally, then connect to MDM and check for updates.
Click to expand...
Click to collapse
Should the cache erasing take a while. Its quite long now.

_litz said:
Yes, it can take 10-20 minutes.
Click to expand...
Click to collapse
Oh wow ok thanks.

stealtheye said:
Only the see the open android with red triangle?
Edit: Got the menu.
Edit 2: This is taking quite a while. Normal?
Click to expand...
Click to collapse
Yes, Normal. you will see "M" in Green colour circle for a few minutes before it boots

Yeah, beats me why stock recovery takes so long to do something TWRP does in 2 seconds.

_litz said:
Yes, it can take 10-20 minutes.
Click to expand...
Click to collapse
Nope MDM still says no update.

_litz said:
Yeah, beats me why stock recovery takes so long to do something TWRP does in 2 seconds.
Click to expand...
Click to collapse
MDM still saying no update. Should I just OTA?

That's very strange ... it SHOULD be detecting the update.
If you can get the FXZ/SBF file from another source then you may as well take the OTA, or just get the full file from elsewhere and use RSD-Lite directly (just like you would have done otherwise).
sometimes you have to unplug/replug your device a few times with MDM ... also if it says "current version : NA" then try enabling USB Development mode, unplugging and replugging.
If everything is working OK, it should say either no update, or update, and then list your device's current version.

_litz said:
That's very strange ... it SHOULD be detecting the update.
If you can get the FXZ/SBF file from another source then you may as well take the OTA, or just get the full file from elsewhere and use RSD-Lite directly (just like you would have done otherwise).
sometimes you have to unplug/replug your device a few times with MDM ... also if it says "current version : NA" then try enabling USB Development mode, unplugging and replugging.
If everything is working OK, it should say either no update, or update, and then list your device's current version.
Click to expand...
Click to collapse
Yeah it lists device correctly but says no update.
I'll just OTA for now and use the FXZ later if it appears. It may be due to the fact that moto have only allowed OTAs for now.

_litz said:
That's very strange ... it SHOULD be detecting the update.
If you can get the FXZ/SBF file from another source then you may as well take the OTA, or just get the full file from elsewhere and use RSD-Lite directly (just like you would have done otherwise).
sometimes you have to unplug/replug your device a few times with MDM ... also if it says "current version : NA" then try enabling USB Development mode, unplugging and replugging.
If everything is working OK, it should say either no update, or update, and then list your device's current version.
Click to expand...
Click to collapse
I've downloaded the OTA. But i wasn't rooted and need to be to capture the OTA. Can I flash TWRP and then SU zip without losing the OTA downloaded in cache? Or is there a way to get it without root? I tried the ADB way...not very well but kept on getting access denied when I remounted.
PLEASE ANY HELP!?

I think you're going to have to go to one of the "capture the OTA" specific pages for help on that, but I think you can flash TWRP and grab it from cache directly in TWRP.
Moto X, unfortunately, doesn't support booting TWRP from fastboot.

_litz said:
I think you're going to have to go to one of the "capture the OTA" specific pages for help on that, but I think you can flash TWRP and grab it from cache directly in TWRP.
Moto X, unfortunately, doesn't support booting TWRP from fastboot.
Click to expand...
Click to collapse
Ya the problem there aren't many of those and helpful ones. Ill just Install it. If i need to wipe I'll just factory reset. I'm sure others in a while will get the file or the FXZ will eventually make its way out. But thanks for your help. Had I known I had to be rooted I would,ve done it before. But i don't want to try now and loose the file in cache. It may clear it when I shutdown or reboot up to install anyway and then I'll also have to remove root if its there to copy. TOO MANY MISSIONS. But thanks bro!

I have got the OTA file.
The problem is now to upload it somewhere. My home ADSL upload speed is abysmal (no, really, 0.5MegaBit/s is about the standard here) and my work connection is behind a proxy that blocks EVERYTHING.
drive.google is blocked, but docs.google isn't... I'll try to find a workaround.
btw file name is: Blur_Version.212.44.26.ghost_row.Retail.en.GB.zip (669 MB (701.692.377 byte))

J500F two problems, recovery screen is corrupt, custom roms will not boot.

Hello all,
I've got a couple of problems with a J500F. As usual, I rushed into doing things to the phone before reading fully (I've been installing various ROMS on my phones for quite a while now).
First of all, I've managed to install TWRP 3.0.2-0. But it seems that the calibration of the screen is way off what it should be. Clicking the "Install" button actually registers as the "Advanced" button. So I can still do things, I just need to guess where to click. Anyone else had this problem?
Secondly, every ROM I try and install will not work. I get a couple of horizontal lines across the screen, and nothing else.
Any help/suggestions are more than welcome.
Thanks in advance,
Tony.

Tony only tme you should panic is you mess efs . If you hve stock rom flash it via odin this would solve ur calibration issues. And install nickverse version of twrp maybe you installed a version for 6.0.1 instead of 5.1.1
Sent from my SM-J500F using Tapatalk

Thanks for the speedy reply.
I don't have the stock ROM, is it available on this site (I'm having trouble locating it).

tonybod said:
Thanks for the speedy reply.
I don't have the stock ROM, is it available on this site (I'm having trouble locating it).
Click to expand...
Click to collapse
Go and try sammobile or google it ull get it make sure to flash it through odin. Am sure you will be fine. Download the right firmware according to your country and region send me ur device name and region i see if i can share a download link
Sent from my SM-J500F using Tapatalk

The model is SM-J500F/DS, and it's a UK phone. Sammobile does not seem to have any UK image, I'm wondering if it actually came from somewhere else (I purchased it on Amazon UK, but it did not have a UK charger).

tonybod said:
The model is SM-J500F/DS, and it's a UK phone. Sammobile does not seem to have any UK image, I'm wondering if it actually came from somewhere else (I purchased it on Amazon UK, but it did not have a UK charger).
Click to expand...
Click to collapse
Go to settings then send me screen shot of about phone. You can download an app from playstore called Samsung phone info(something like that) can tell you which region its from...
Sent from my SM-J500F using Tapatalk

I cannot get into the settings (cannot get a ROM to boot).
I've just tried the Nick Verse recovery, it continually reboots the phone unfortunately without ever getting to the recovery screen.
I'll try one of the European ROMs from Sammobile, hopefully that will get things working again.

ok, I've got a stock ROM on the phone and it's booting up. But the screen calibration problem is still there which makes it unusable.
Going to see if I can use the app on Google play (not sure how I'm going to connect to the wifi though).

tonybod said:
ok, I've got a stock ROM on the phone and it's booting up. But the screen calibration problem is still there which makes it unusable.
Going to see if I can use the app on Google play (not sure how I'm going to connect to the wifi though).
Click to expand...
Click to collapse
Then you might hve flashed the twrp without unlocking oem.https://boycracked.com/2016/03/30/official-samsung-galaxy-j5-j500f-stock-rom/ try that link.
Sent from my SM-J500F using Tapatalk

When you say unlocking OEM, do you mean for the FRP error? I did unlock that (but don't recall unlocking anything else).

tonybod said:
When you say unlocking OEM, do you mean for the FRP error? I did unlock that (but don't recall unlocking anything else).
Click to expand...
Click to collapse
Yea but its not frp its OEM hehe. Just reflash the stock rom again then try flashing the twrp again.
Sent from my SM-J500F using Tapatalk
---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------
You need to enable oem to unlock ur bootloader then you can flash twrp. Ensure that usb debugging is on. You might hve missed one of this two
Sent from my SM-J500F using Tapatalk

tonybod said:
ok, I've got a stock ROM on the phone and it's booting up. But the screen calibration problem is still there which makes it unusable.
Going to see if I can use the app on Google play (not sure how I'm going to connect to the wifi though).
Click to expand...
Click to collapse
I'm guessing you probably need to upgrade your rom. Strange lines and out of whack touches are usually due to an incorrect firmware vs kernel.
Ensure you are flashing the latest MM rom for your device if the TWRP you are using was built using a MM kernel.

Try flashing stock via Odin. Guides are available all over XDA on that.

I'm just getting back to this.
I've shot a quick video to show what I mean is happening.
https://www.youtube.com/watch?v=yR5dF9lURcU
Jump to 10 secs, you can see that click location is way off/.
Anyone got any ideas? I've flashed a number of stock images so far, all have the same issue. I've currently got a mouse connected via bluetooth so I can actually do things as trying to work the keyboard like this is impossible.

tonybod said:
I'm just getting back to this.
I've shot a quick video to show what I mean is happening.
Jump to 10 secs, you can see that click location is way off/.
Anyone got any ideas? I've flashed a number of stock images so far, all have the same issue. I've currently got a mouse connected via bluetooth so I can actually do things as trying to work the keyboard like this is impossible.
Click to expand...
Click to collapse
Are you actually allowing the firmware to complete its update?
It must boot into recovery after odin finishes flashing otherwise the install isn't complete.
It should auto reboot to recovery and you should see 'erasing'
Then it will reboot and the update should be completed.
If it does not boot to recovery then this is likely why you have the described issues.

ashyx said:
Are you actually allowing the firmware to complete its update?
It must boot into recovery after odin finishes flashing otherwise the install isn't complete.
It should auto reboot to recovery and you should see 'erasing'
Then it will reboot and the update should be completed.
If it does not boot to recovery then this is likely why you have the described issues.
Click to expand...
Click to collapse
Yes. I've just reflashed to check. It downloads the image to the phone, reboots into recovery where it says erasing, installing system update etc. Then reboots and I get the "Android is upgrading" message where it does all it's "optimizing apps". The touchscreen error still persists .
I did video this (or portions of it) and can upload.

tonybod said:
Yes. I've just reflashed to check. It downloads the image to the phone, reboots into recovery where it says erasing, installing system update etc. Then reboots and I get the "Android is upgrading" message where it does all it's "optimizing apps". The touchscreen error still persists .
I did video this (or portions of it) and can upload.
Click to expand...
Click to collapse
Which firmware are you using and what is your device spec?

I've got a few ROMs that I've tried
SM-J500F_20160812_J500FXXU1BPH1_J500FODD1BPH1_6.0.1
SM-J500F_20160512_J500FXXU1APE1_J500FOXX1APE1_5.1.1
J500FXXU1BPF4_J500FODD1BPF4_SLK
Same behaviour with all of them. I'm not entirely sure what region the phone was originally from, I purchase it on Amazon and believe it came from somewhere in Eastern Europe, so I've been trying images marked as Austrian, Slovakia, even Greece.
If it helps, the following is under the battery.
Model : SM-500F/DS
FCC ID : A3LSMJ500F
SSN : J500F/DSGSMH

tonybod said:
I've got a few ROMs that I've tried
SM-J500F_20160812_J500FXXU1BPH1_J500FODD1BPH1_6.0.1
SM-J500F_20160512_J500FXXU1APE1_J500FOXX1APE1_5.1.1
J500FXXU1BPF4_J500FODD1BPF4_SLK
Same behaviour with all of them. I'm not entirely sure what region the phone was originally from, I purchase it on Amazon and believe it came from somewhere in Eastern Europe, so I've been trying images marked as Austrian, Slovakia, even Greece.
If it helps, the following is under the battery.
Model : SM-500F/DS
FCC ID : A3LSMJ500F
SSN : J500F/DSGSMH
Click to expand...
Click to collapse
Install Samsung phone info and post a screen shot of the CSC info.
It should show your original CSC.

Thanks, I've uploaded the screen. Sorry it took so long, I've been away and forgot the bluetooth mouse that I use on the phone.
It looks like the original CSC is SM2J500FZKDAUT, I cannot seem to find that on Sammobile.

[Samsung A8] Phone UI won't boot after changing DPI

Hi guys,
So I was messing around in the developer menu settings (big mistake) on my galaxy A8 when I found an option to change the DPI of my phone. I changed the value from 360 to 800 and inmediately a 'UI stopped working' message popped up and the whole screen went black. I quickly restarted my phone but the boot up animation ends everything is still black (if i a hold the power button a very small version of the Power off, Restart, Emergency alerts show up but they are not responsive). I had not enabled USB debugging before, and I tried to make a backup with KIES but it won't work since it says the phone screen is locked.
I looked around on some forums and found out adb, but all the methods involved having USB Debugging turned on (since adb does not recognize my phone).
Everything on my phone is stock and android version was up to date.
Is there anything you guys think I can do? I have a lot of info I would hate to lose on that phone :crying:

Unfortunately you have compromised the phones bootloader and Samsung has banned the bootloader and currupted ur kernel...... Bad luck
---------- Post added at 03:52 AM ---------- Previous post was at 03:48 AM ----------
Cheemaa said:
Unfortunately you have compromised the phones bootloader and Samsung has banned the bootloader and currupted ur kernel...... Bad luck
Click to expand...
Click to collapse
I'm just kidding. Learn how to put your phone in download mode and download Odin and your firmware and flash your firmware in download mode in Odin (on ur computer)

Re:
Cheemaa said:
Unfortunately you have compromised the phones bootloader and Samsung has banned the bootloader and currupted ur kernel...... Bad luck
Click to expand...
Click to collapse
Almost gave me a heart attack :laugh:.
Thanks for your reply! So I already have Odin installed and I'm currently looking for my firmware. I noticed that most have country name followed by a phone carrier. My phone was factory unlocked, so I guess this should be the one? sammobile.com/firmwares/galaxy-a8/SM-A530F/BAT/ (can't post a url since I'm new here)

Flash didn't work?
I downloaded the XEU firmware for my phone and followed the steps to flash it. Odin gave a PASS! message, but it took a really short amount of time (0:02). After that it rebooted the phone, but after putting my password the screen went black again just as it did before. Did I do something wrong? I used the HOME_CSC since it said that it wouldn't wipe my data (I haven't been able to make a backup)

dinartec said:
I downloaded the XEU firmware for my phone and followed the steps to flash it. Odin gave a PASS! message, but it took a really short amount of time (0:02). After that it rebooted the phone, but after putting my password the screen went black again just as it did before. Did I do something wrong? I used the HOME_CSC since it said that it wouldn't wipe my data (I haven't been able to make a backup)
Click to expand...
Click to collapse
Did it work? I can still help you. Took a time off

Cheemaa said:
Did it work? I can still help you. Took a time off
Click to expand...
Click to collapse
Because you flashed the HOME_CSC version, the system ui was also saved, therefore dpi changes stayed with the new stock flash. I don't think you can get your phone back without losing data.