yashsingh1/xdaforums huggingface dataset:
[Xperia Arc Themes and Apps] ionezakuza:
thanks :)

i'll be waiting
[Xperia Arc Themes and Apps] jjkkyu:
Take it, Bro.

https://www.mediafire.com/?24ztt4qr7707782
[Xperia Arc Themes and Apps] ionezakuza:
thanks bro. what are the permission for each file?
[Xperia Arc Themes and Apps] FireWall123:
rw-r--r--

Vocaloid fan? Check out this thread!
[Xperia Arc Themes and Apps] ionezakuza:
thanks! it works
[Xperia Arc Themes and Apps] jjkkyu:
Do you use docomo launcher and what's your device?

I tried to port the launcher to my xperia sp, it did boot.

But after using for a period, it always cause the phone to a bootloop.

If you are using a non-problem launcher, can you share it?
[Xperia Arc Themes and Apps] ionezakuza:
yes. my device is andromax u2 (hisense eg98), that's a local device. i just search docomo launcher from google and i don't have any problem. i'm sorry, i don't know how to share file or upload file. can you help me?
[Xperia Arc Themes and Apps] jjkkyu:
You can sign an account at https://mega.co.nz/ or http://www.mediafire.com/ , then you can upload file and share.
[Xperia Arc Themes and Apps] ionezakuza:
i'm using this launcher bro :)

https://www.dropbox.com/s/hfrwoe59pngjs65/DocomoHome_xhdpi.apk/

i hope it will help you
[Xperia Arc Themes and Apps] jjkkyu:
I've tried much but still cannot download from Dropbox.

Can you upload to mediafire or mega?
[Xperia Arc Themes and Apps] jjkkyu:
I managed to get it. Thanks all the same.
[Xperia Arc Themes and Apps] ased223:
Is this Sony phones only? can I install miku home app on my lenovo?
[Xperia Arc Themes and Apps] Shiro Neko 98:
Could it work on android Nougat / Marshmallow / Lolipop ? ex. Xperia X Compact ( 720 x 1280 )

without ANY LAGS or FC ? :confused::confused:
[Xperia Arc Themes and Apps] xxshining01:
Can I use it on my Oneplus 3t?

I try to use Docomo Home on my phone but it can't change wallpaper, it will return to black screen.

The Kisekae theme too. When I put on Apps button it will return to black screen every times.

How can I install a custom Kisekae I would like to use Miku xperia. theme, tell me please?
[Xperia Arc Themes and Apps] NomNep:
A question!!

Mmm...can it be installed on a Samsung Galaxy Note 3 N19005? I want to try dis *Hype Hype* it is a Android 5.0
[Xperia Arc Themes and Apps] NeoMikuXperia:
FINALLY GOT FIND YOUR MIKU AND THE ENTIRE APPS WORKING ON A SAMSUNG PHONE RUNNING ANDROID 6.0.1!!! Except For Internet Apps & The V5A Version Of The Zip Doesn't Work, Find Your MIKU Crashes Only In The V5A Release, But, The V4A Doesn't Crash. And, It Sacrificed Tons Of Storage, I Only Have 30+ MB Of Storage Left.
[General Accessories] plane-crazy:
I bought a 1900 mAh battery from mobilfun.co.uk, appears as an official O2 battery but have had to send 3 back.

The first did not charge at all, either in the cradle or the phone.

The second charged fully in the craddle and lasted 2 hours before going dead. It would not recharge in the craddle or through the usb cable - battery not seen.

The third again seemed to charge OK in the cradle but when put on the phone it immediately caused a hard reset (internal battery at 100%).

The company has changed the battery each time but I'm at a loss to understand why this is happening. Is it a bad batch of batteries or the phone?

There were no instructions with the battery to indicate the need to charge the battery on the phone first instead of the cradle so I used the craddle.

Any adice gratefully appreciated.
[General Accessories] MugenPower:
to plane-crazy:

would u mind to send me the link? so that I know which battery u have bought....
[General Accessories] plane-crazy:
This is the link to the extended battery on the mobilefun site:

http://www.mobilefun.co.uk/product/5268.htm
[Galaxy S 4 Q&A, Help & Troubleshooting] angus_mcfisher:
Hsve you tried just the pit and repartition on its own, and then trying from there to flash the rom? I've read others who had success this way
[Galaxy S 4 Q&A, Help & Troubleshooting] Lalssa:
Go to this website

You will learn how to unbrick your soft bricked s4

http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
Been there - all methods do not work:

Cannot boot into recovery

Odin is not flashing ROMs with or without PIT
[Galaxy S 4 Q&A, Help & Troubleshooting] Lalssa:
http://m.ibtimes.co.uk/samsung-galaxys4-gti9500-gti9505-unbrick-softbrick-hardbrick-469557.html

If didnt work try again
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
Thanks for the reply, yes I've tried just flashing the PIT, then the rom with all variations e.g. unticking auto-reboot in ODIN, hard reset, boot into ODIN mode, then attempting to flash the ROM.

ODIN will flash the PIT but refuses to flash the ROM

Fail (WP)

I'm assuming (WP) is some kind of write protection
[Galaxy S 4 Q&A, Help & Troubleshooting] Lalssa:
Download another version of odin
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
I've just tried it with ODIN v3.04 and v1.85, with combinations of PIT alone with no auto reboot followed by flashing the rom along with doing both at once and unfortunately even though ODIN writes the PIT it fails to write the ROM.

<ID:0/025> NAND Write Start!!

<ID:0/025> recovery.img

<ID:0/025> system.img.ext4

<ID:0/025>

<ID:0/025> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

It appears to be a non-standard brickage to say the least i'm afraid.
[Galaxy S 4 Q&A, Help & Troubleshooting] Lalssa:
Try flashing using heimdall you can find some interesting tutorials if you google it
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
Thanks, reading up on it now. Will report back when i've learned enough to attempt to flash things
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
Using Heimdall:

As with ODIN, writing the PIT is completed.

Alas, Heimdall cannot write ANY partitions from the extracted .tar files from the GT-I9505-Factory-Firmware-Full-Wipe-DBT ROM.

It does seem that the flash memory is write protected - it certainly cannot be written to.
[Galaxy S 4 Q&A, Help & Troubleshooting] Obagleyfreer:
If I were in this situation I would do the following:

Download latest PhilZ recovery for i9505.

Flash this in PDA section of Odin.

Boot to recovery and go to mounts and storage.

Format system, data, cache, preload (and format SD card if there's nothing important you need like photos etc)

You now have a TOTALLY clean device.

Boot to download mode and flash MGA stock firmware with Odin.

I would download the MGA firmware from Sammobile as these are untouched stock firmware files.

If flash is successful boot to recovery (it will now be stock) and wipe data factory reset.

Now reboot.

Hopefully you should be good to go :)

P.S If once again Odin fails on nand write start the you probably have a corrupt nand and I hate to say it but a whole board replacement might be needed.

Good luck mate!
[Galaxy S 4 Q&A, Help & Troubleshooting] chickentuna:
Have you tried to flash the pit + stock firmware with the re-partition box checked?

BTW, be careful using Heimdall. I've hardbricked my phone to the point that I cannot go to recovery and download mode while using that tool. It was impossible to turn the phone off and charge the phone as well. I didn't know what caused it (probably incorrect bootloader/pit) but as a result I needed a board replacement. Luckily Samsung replaced it for free as they cannot revive the phone anymore lol.
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
Thanks for taking the time to provide the advice, I've tried flashing PhilZ recovery via ODIN and it tells me it has been successful, however when i try to boot into recovery it appears it's not flashed at all as I get stuck on the previous recovery TeamWin loading screen - it looks as if the nand maybe corrupted after all.
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
Yes, I've attempted to flash the pit + correct stock firmware with the re-partition box checked and while it writes the pit, Odin starts to write the firmware then fails about halfway through.

Perhaps, reading between the lines, it would be better for me if indeed I hard bricked the phone to a state where the recovery and download mode are not accessible as then it would not be obvious I had invalidated the warranty by previously rooting the phone and would get a free replacement!

Thanks for taking the time to reply.
[Galaxy S 4 Q&A, Help & Troubleshooting] chickentuna:
Damn that's quite unfortunate. Sorry mate, I'm out of ideas. I wouldn't actually advise to hard brick the phone intentionally because as far as I know there's still hope as you can still access download mode.

Well if you can't really flash anything it's probably best to just hard brick the phone to the point that the Samsung guys wouldn't be able to revive it then send the phone for repairs than having to send it in it's current state because they'll most likely find out that you've modified your phone. Again I strongly suggest not to do it.

Good luck. Hope you fix it soon buddy.
[Galaxy S 4 Q&A, Help & Troubleshooting] sbouzyk:
Download Kies and install samsung drivers with it. Click on tools tab and click emergency firmware restore. Type in your phone model e.g GT-I9505 and then type in your Serial Number (can be found in the battery compartment of the phone) Kies will then ask you to go to download mode and then it will start downloading firmware and installing it on your device.

:)
[Galaxy S 4 Q&A, Help & Troubleshooting] VoodooSix:
The write protection enabled message suggests to me that you've previously had one of the stock firmwares with the new bootloader. Have you had MH8 on there?

If you're desperate you could always try flashing MH8 firmware. The new bootloader won't let you downgrade to an older firmware giving a message as above.
[Galaxy S 4 Q&A, Help & Troubleshooting] xElementzx:
Had this issue

Hey There, i had this issue last night infact, i had bricked my phone, recovery not accessible and download mode only possible by plugging it in and then starting it, try this put your phone into download mode, via plugging it in then turning it on, when it is in download mode flash PhilZ recovery via the PDA option then turn it off after flashing by taking out the battery (after it has rebooted and flashed), then plug it in again, launch into recovery and wipe/format etc.. install a new MH8 stock firmware (with the new bootloader) then you should be okay.

It should be noted that i did these step and it worked, except i didn't ever install a new rom and kept stock and i used a nandroid backup instead of installing the stock rom
[Galaxy S 4 Q&A, Help & Troubleshooting] JustSueMe:
You say twrp logo shows up. Does it start adb ? Maybe u can remount partitions as RW with terminal . manually wipe it. And then try adb sideload to install a .zip

All I can think of as every other suggestions seem to have been mentioned.
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
Thanks for the reply - I've tried emergency firmware restore in kies and it connects fine, downloads the firmware then fails on the install.
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
Thanks for the reply, I haven't used the MH8 firmware - but was desperate so attempted to flash MH8 firmware with MH8 stock recovery.

Odin process showed recovery flashed (but it didn't as booting into recovery shows a stuck TeamWin image).

Odin failed when attemptine to flash firmware. FAIL (WP)

Really am running out of ideas now!
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
Thanks for the reply, I've downloaded android SDK for windows and a front end for ADB in an attempt to get into the phone as recovery doesn't properly boot.

Initial signs don't look good as I'm having difficulty getting my phone connected to the PC in any mode other than download mode, however it's early days yet and i've plenty of reading to do.
[Galaxy S 4 Q&A, Help & Troubleshooting] VoodooSix:
I was stuck at the boot screen and thought I had bricked my phone, then I tried flashing PIT at the same time as flashing the firmware. Perhaps give that a whirl? If that doesn't work I'm afraid I'm out of ideas.
[Galaxy S 4 Q&A, Help & Troubleshooting] VoodooSix:
Also try booting into recovery and clearing caches once you've flashed.
[Galaxy S 4 Q&A, Help & Troubleshooting] Styrke:
In my opinion, its a problem with the internal memory thats why flashing fails on nand write start or system.img.This happened with a half sds s3 of a friend.Pit file or repartition didn't fix it.

I know the two phones are different but the errors are same.

Hope you be able to fix it.
[Galaxy S 4 Q&A, Help & Troubleshooting] exprxp:
Phone is in warranty? So do a repair. There is a problem with U800 PMIC and need to be replaced.
[Galaxy S 4 Q&A, Help & Troubleshooting] MemoryController:
If you ticked Write Protect, you will need to flash fw via jtag or get it to boot into Qualcomm DLOAD
[Galaxy S 4 Q&A, Help & Troubleshooting] lzk123:
- Restart computer

- Use another usb port

- Close kies, disable antivirus

- Download odin 3.04

- Start odin with admin privilege

- Flash pit (make sure repartition is checked)

- Phone will reboot and stuck at Samsung Logo

- Take out battery and insert again.

- Enter download mode and flash stock firmware.

- Go stock recovery mode.

- Wipe data, cache

- Phone reboots.
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
I didn't tick write protect on anything, but being unable to flash any partitions leads me to believe that this may be the issue.

Thanks for the info - this jtag business doesn't sound much fun but am really now out of options i believe.

I was wondering whether the internal SD card can be removed, slotted into a card reader and played around with in Linux to alter permissions and format correctly. It's frustrating not to have access to it to see what is going on.
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
Thanks for the reply - it's not the first time I've tried this, but it was worth another shot. PIT flashes ok, however, any attempt to write to partitions fails with any and all roms, tried on different machines, motherboard connected USB ports, disabling all interfering software, different cables.

ODIN used to write the partitions, but cache wouldn't wipe in recovery, so i used "fixed permissions' to attempt to solve this in the TeamWin recovery which seems to have turned a softbrick into a non recoverable one.

<ID:0/025> Firmware update start..

<ID:0/025> cache.img.ext4

<ID:0/025> NAND Write Start!!

<ID:0/025>

<ID:0/025> Complete(Write) operation failed.

<ID:0/025> Added!!

<OSM> All threads completed. (succeed 0 / failed 1)

It seems the internal SD is screwed.
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
Thanks for the reply

Phone is still under the warranty period, however:

Trying to boot into recovery shows a stuck TeamWin logo - voided warranty as not stock.

Download mode shows yellow triangle and lists ROM: Custom - voided warranty as not stock.

And as I am unable to flash stock rom and stock recovery never mind being able to run triangle away it seems i am screwed.

If all else fails I could ideally do with a method to stop the phone booting AT ALL to hide all my messing about!
[Galaxy S 4 Q&A, Help & Troubleshooting] Styrke:
Yea.You may have luck with the service center if you hardbrick it.
[Galaxy S 4 Q&A, Help & Troubleshooting] lzk123:
What error do u have when you wipe data/cache in stock recovery? You should reboot the phone and wait for it to load after wiping. The phone will stuck at a screen with glowing Samsung word. It may take few minutes but the phone will finally boot up to lockscreen.
[Galaxy S 4 Q&A, Help & Troubleshooting] BSDgeek_Jake:
Hi Sorry to hear that you are loosing you phone as day passes.

Just little help. This might resurrect your phone.

Follow these steps carefully and it will recover the phone to STOCK.

Download and Setup

0. Make Sure your Phone has close to 80% Battery power else Charge.

1. First Remove all Kies and Samsung stuffs from your Windows.

2. Reboot.

3. Download the Samsung Android USB Driver for Smartphones.

4. Download Odin3 3.04.

5. Download i9505 Stock Firmware.

6. Download Philz Kernel.

7. Install Samsung Android USB Driver and Reboot Windows.

Flash and Wait

8. Run Odin.

9. Make sure that ONLY 'AutoReboot' & 'F.Reset Time' is ticked in options, nothing else.

10. Extract i9505 Stock Firmware.

11. Load extracted file (.tar.MD5) as PDA in Odin. Dont use PIT file unless you want to re-partition. First try flasing without pit.

12. Turn OFF your phone, Press&Hold POWER+HOME+VOLUME_DOWN buttons until phone boot into Download/Odin Mode

13. Connect phone to the computer and WAIT for the drivers to be prepared and installed for your phone. You will see blue or yellow indicator in left top corner of Odin, with phone connected to port: COM:x

14. Click START and wait until you see GREEN indicator [PASS], flashing is finished

15. Unplug USB cable and Reboot Phone.

16. Phone might be processing for 2-5 minutes or little more. Dont worry, just wait...

Root and Boot

17. Root your phone using Philz Kernel.

18. Run Odin.

19. Make sure that ONLY 'AutoReboot' & 'F.Reset Time' is ticked in options, nothing else.

20. Extract i9505 Stock Firmware.

21. Load extracted file 'philz_touch_5.15.0-i9505.tar.md5' as PDA in Odin.

22. Turn OFF your phone, Press&Hold POWER+HOME+VOLUME_DOWN buttons until phone boot into Download/Odin Mode

23. Connect phone to the computer and WAIT for the drivers to be prepared and installed for your phone. You will see blue or yellow indicator in left top corner of Odin, with phone connected to port: COM:x

24. Click START and wait until you see GREEN indicator [PASS], flashing is finished

25. Unplug USB cable and Reboot Phone.

26. Phone might be processing for 2-5 minutes or little more. Dont worry, just wait...

Hope i was helpful. :good: :)
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
Thank you very much for taking the time to write this guide for me, I followed every step as set out by you until step 14:

ODIN still won't write the stock firmware,

<ID:0/024> Firmware update start..

<ID:0/024> sbl2.mbn

<ID:0/024> NAND Write Start!!

<ID:0/024>

<ID:0/024> Complete(Write) operation failed.

Tried writing stock firmware with PIT file:

<ID:0/024> Set PIT file..

<ID:0/024> DO NOT TURN OFF TARGET!!

<ID:0/024> Get PIT for mapping..

<ID:0/024> Firmware update start..

<ID:0/024> sbl2.mbn

<ID:0/024> NAND Write Start!!

<ID:0/024>

<ID:0/024> Complete(Write) operation failed.

It appears that the PIT file writes, but again ODIN fails at NAND write start.

Tried flashing PhilZ recovery:

<ID:0/024> Get PIT for mapping..

<ID:0/024> Firmware update start..

<ID:0/024> recovery.img

<ID:0/024> NAND Write Start!!

<ID:0/024> RQT_CLOSE !!

<ID:0/024> RES OK !!

<ID:0/024> Completed..

<OSM> All threads completed. (succeed 1 / failed 0)

ODIN says Pass and gives green box, phone boots to samsung galaxy S4 screen and hangs.

Booting into recovery shows the TeamWin recovery, it hangs on the splash screen. No sign of Philz recovery.

Thanks again, but it seems the only solution is to use a hammer!
[Galaxy S 4 Q&A, Help & Troubleshooting] MrBrickedPhone:
Thanks for taking the time to reply, I really appreciate it.

I can't get into recovery:

To begin I had stock recovery, phone crashed after making a call and wouldn't boot.

I booted into recovery to wipe cache, phone would attempt to wipe cache, crash and then reboot to samsung galaxy s4 logo and then hang.

I installed TWRP as a recovery to see if this would wipe the cache and solve the problem, again, it was unable to wipe cache. In my foolishness, I chose to "reset permissions" and upon doing that, broke recovery, it loads only to the TeamWin splash screen.

The phone appears to be well and truly broken, but thanks again for taking the time to reply
[Galaxy S 4 Q&A, Help & Troubleshooting] BSDgeek_Jake:
hhmm... i once have hardbrick but recovered from it in few hours. Now the possible way is to try alternate flashing options and using alternate firmware for i9505. Use the one for Your country or Service Provider... might have some provider code which is not there on other firmware. Alternate is to use other firmwares. Hope your NAND is not damaged/read only.

You can also send your phone to Service Center but i doubt that it will be accepted. But anyways try and see.

Regards.
[Galaxy S 4 Q&A, Help & Troubleshooting] MemoryController:
Have you tried flashing only kernel? Since it fails at SBL maybe you updated to a write-protect bootloader
[Galaxy S 4 Q&A, Help & Troubleshooting] L.iam:
Same boat

In the exact same boat MrBrickedPhone, here is my experience >> http://xdaforums.com/showthread.php?p=46061433#post46061433

lost and running out of ideas what to do... It appears un-fixable perhaps it would be best to hardbrick and send back?

What have you or did you decide to do about it in the end?? did you find a fix??

Anyone have any suggestions?
[Galaxy S 4 Q&A, Help & Troubleshooting] jd1639:
Jtag, check out mobiletechvideos.com
[Galaxy S 4 Q&A, Help & Troubleshooting] Andr0id7:
Flash this via odin, pda section http://downloadandroidrom.com/file/GalaxyS4/GT-i9505/recovery/CWM/i9505-cwm-recovery-6.0.3.2-4.tar

Check Auto Reboot.

This works on my device, hope it'll work on yours too sir.
[Networking] Lalssa:
This a Tutorial tested in Lebanon Because Lebanese 3G Connection is very expensive​

ANDROID 2.2+ ONLY

PREREQUISITES:

- Rooted Android phone

- The WAP needs to be set up first, activated and working (web browsing).

Step One :

1 - Download ProxyDroid from the Market (free) via Wi-Fi

2 - Turn OFF Wi-Fi and make sure packet data is disabled.

3 - Configure ProxyDroid:

Host: 192.168.23.50

Port: 8080

Proxy type: HTTP

Tick Auto Connect

Binded Network: 2G/3G

Tick Enable Authentication

User: mic1

Password: mic1

4 - Enable packet data (WAP)

5 - In ProxyDroid, enable the proxy (tick Proxy Switch)

6 - Open For Example Whatsapp and wait up to 15 sec so that the configuration takes effect

Note : To block unwanted application from receiving internet, use DroidWall

ProxyDroid : https://play.google.com/store/apps/details?id=org.proxydroid&hl=en

DroidWall : https://play.google.com/store/apps/details?id=com.googlecode.droidwall.free&hl=en

Thank You For Your Support​
[Galaxy S 4 Q&A, Help & Troubleshooting] parvezthepop:
Hi,

I had installed the CyanogenMod 10.2 available in the original android development section on my I9500. I flashed it in the morning. everything was working fine except camera till afternoon. Suddenly on afternoon i observe that my phone has entered into emergency signals mode and was not connected to my mobile network. First i thought it was signal problem but upon reading found out that it is IMEI getting changed problem. I have installed Stock ROM again to try if it solves the problem but sadly it doesnt :(.

Anyone out there faced the same issue and can help me?

Thanks
[Galaxy S 4 Q&A, Help & Troubleshooting] marc_ecko28:
What is the firmware you are using before flashing cm rom?
[Galaxy S 4 Q&A, Help & Troubleshooting] malybru:
Hi,

Have you tried flashing a previous modem?

List is HERE

Choose the correct version for your phone.

:)
[Galaxy S 4 Q&A, Help & Troubleshooting] parvezthepop:
I have an Indian model I9500 . I tried flashing Omega Rom before trying CM. For Omega ROM i flashed XXUBMG9. After that i flashed back the Stock firmware I9500XXUAMDE_I9500ODDAMDC_INU. Then i flashed CM. CM worked fine for half a day. Then it failed connecting to my network.

With the method you are telling i flashed my stock firmware modem first, but it didnt work. Now i flashed XXUBMG9 and it worked.

Can't i go back to my stock firmware modem now? Am I stuck with this modem ?
[Galaxy S 4 Q&A, Help & Troubleshooting] naanireddy:
same

same here I am also having same problem phone works fine on xxubmg9 modem but not on stock modem as it gives generic imei,

is there any way to revert back to stock rom completely?