Database Develop

[Q] [info] - [I9000m] Bell Galaxy S Vibrant - internal SD failure

Hi Guys,
Here's some history on the phone:
- Purchased in Aug 2010, came withJK3 (not sure but it was ECLAIR)
- Since then the phone has been performing unbelievable, I had put several ROMs on the phone custom and stock as well as multiple kernels to fix battery drain, etc.
- A few days back after flashing Hamster's 6.3 ROM (which I had been using for a month prior, thus is completely irrelevant to my issue - find it here), I tried to access an app I had recently used when the phone completely froze on me, even power button would not respond; so I did a hard reboot only to be greeted by the cwm recovery window notifying me that the FS partition had changed and what I would like to do.
Knowing I had not changed anything, I simply picked "remove new configuration and boot phone"
Thats where I crapped my pants, the phone would reboot itself every 2 seconds and would not go past the first samsung boot screen.
I tried everything without luck, when finally 2 days later with special thanks to the following people listed below I found out exactly what's wrong with the phone and how to actually get to recovery and get a working boot on the phone.
I tried many many combinations of ROMs and kernels through ODIN and nothing seemed to work, initially I could get past the first boot screen if I re-partitioned with 512 and flashed JM8, but even that stopped working eventually. Finally late last night, I got the phone to boot. Here's what I did:
re-partition the phone with 803
Flash the phone with stock JLU (you will need the complete ROM with PDA, PHONE and CSC files)
Flash JPY
FLASH CF ROOT
FLASH SPEEDMOD kernel k12j
After the final step above you should have working recovery with adb for the first time! so now try the following umount commands and if they work then you are okay and do not have a dead sdcard/controller
Code:
umount /dev/block/mmcblk0p1
umount /dev/block/mmcblk0p2
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
Thanks to codeworkx for the above commands. If you try the above and they dont work or recovery shows the errors such as:
E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
or cannot mount SD card
then most likely you have either a bad internal SD or bad controller.
Regardless, your phone should now boot. if you can mount your SD card, you should do a complete format in windows after running the commands above; otherwise you still will not be able to access your internal SD and even though you can boot, your data will be lost after each boot and you cannot download anything from market or update current apps.
-------------------------------------------------------------
So now, I have a phone that boots up and works but cannot mount internal nor external SDs, here's the error dmesg gives in this regard, which again codeworkx helped me disect out of the logs:
Code:
"mmc0: error -110 whilst initialising MMC card"
I recently opened the phone up to try and see if I could find the location of the internal SD and to my surprise it only took 5 minutes and a little help from diagrams at phonewreck.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I know where the internal SD is, but no clue where the controller would be and whether its even possible to replace or any otherway to get the data back from the current internal SD which MAY still be okay in my case...
Any help with this would be appreciated - at this point im willing to try anything.
Thanks and if you have any questions feel free to ask.
People to note and thank for spending hours with me, walking me through what they know: virnik0, Jim_Panse, codeworkx, Josaatt, uppon2 & eitama - thanks guys!

that's what they do when you send it back in for repair
they just replaces the damaged PCB with the internal SD
usually error code 303 or 330 something like that

Just an update here.
My "Brand New" replacement from Bell - mk 10.11 just had the exact same failure as above, running stock 2.2 with absolutely no mods.
edit: phone came this way from bell/samsung | last thing I remember doing on it was loading google maps, then it started rebooting... and would boot up to JL2, and after 10 seconds of usability would reboot again... I could still see the internal and external SD... through recovery and adb, all the files were there...
after that happened, I decided its time to flash a custom rom, and at the first step (repartitioning + JM8/JM4) phone went to the infamous boot loop and thats that.

Did you upgrade to UGJL2 via kies prior to installing 2.2.1? If you didn't, or if you did it in odin without ticking "phone bootloader update", that's your problem. There's a problem with the I9000m 2.1 bootloaders wear control on the sd card. If that's not updated before going to any 2.2 or 2.2.1 firmware, you're phone is going to die.
Sent from my GT-I9000M using XDA App

I did not touch the phone, it came with GJL2 on it 2.2 - that's what I had on it.

@tekkneak,
Firstly... Your first phone that you bought in August did NOT have JL2 firmware on it as JL2 is a FroYo firmware and did not come out until late December 2010. The firmware you had on your first phone was probably JH2 which is Eclair.
I bought my i9000M in August 2010 (on the 30th of the month as a matter of fact) but mine came with JG9 Eclair and I had to upgrade to JH2.
This being said and since you mistyped the firmware version in your first post, are you sure that your NEW phone diddnt come with JH2 and NOT JL2? If this is the case then Electroz theory would hold true.
It has been said by both Bell and Samsung that the JL2 Froyo firmware has a new .SBL file that fixes the crashing internal SD cards.
This being said... IF your new phone did have JL2 FroYo on it and it crashed and gave you the internal sd card failure then I would say that for your phone it was a LEGIT hardware issue.

@yiannisthegreek I'm really not sure what came with my phone originally to be honest, back then I didn't think I'm going to have all these problems or I would have paid more attention to what was on the phone prior to me messing with custom ROMs. It DID have eclair, originally.
The new phone have Froyo I9000UGJL2 and I did everything I could to revive and many (listed above) helped with various methods which I have re-attempted with the recently deceased. It is indeed another Hardware failure, but WHY? shouldnt it have been fixed in the new versions??

tekkneak said:
@yiannisthegreek I'm really not sure what came with my phone originally to be honest, back then I didn't think I'm going to have all these problems or I would have paid more attention to what was on the phone prior to me messing with custom ROMs. It DID have eclair, originally.
The new phone have Froyo I9000UGJL2 and I did everything I could to revive and many (listed above) helped with various methods which I have re-attempted with the recently deceased. It is indeed another Hardware failure, but WHY? shouldnt it have been fixed in the new versions??
Click to expand...
Click to collapse
I feel where you are coming from for sure. Yes... You would think that these issues should have / would have been fixed by now but... The general concensus regarding failing internal sd cards is that the MAJORITY of the failures were due to a software issue and NOT a hardware issue. That being said, as I mentioned before... Bell and Samsung have stated that the JL2 Firmware with the new .SBL Bootloader File has fixed the "software" issue that was causing our devices to suffer internal SD failure so that is why I am assuming that your new phone may actually have fallen prey to a TRUE "hardware" failure in which case there is no remedy other than to have it replaced or repaired.
For example... Last night I had flashed my phone with a few different files and it "soft bricked" to the point where I was scared that it was my internal sd card too. It would hit the Samsung animation screen, vibrate once, go black screen with the buttons lit up then vibrate with three small bursts. I could go into recovery and download mode no problem and I did NOT see any error message in recovery so what I did is a Factory Reset from recovery and it rebooted just fine.
I lost my contacts and apps but not my phone. Perhaps try a Factory Reset from recovery and see what it does if you have not tried already.
In any case... I wish you luck...

tekkneak said:
@yiannisthegreek I'm really not sure what came with my phone originally to be honest, back then I didn't think I'm going to have all these problems or I would have paid more attention to what was on the phone prior to me messing with custom ROMs. It DID have eclair, originally.
The new phone have Froyo I9000UGJL2 and I did everything I could to revive and many (listed above) helped with various methods which I have re-attempted with the recently deceased. It is indeed another Hardware failure, but WHY? shouldnt it have been fixed in the new versions??
Click to expand...
Click to collapse
It's probable that whoever update the phone to UGJL2 just forgot to hit the Phone Bootloader update option in Odin as well. After all, Odin is Samsung software released to their tech's. So, something that simple could have done it.
As one last chance, download UGJH2 and UGJL2 from Samfirmware.com and use Odin 1.7, no pit, no repartition.
Flash UGJH2 first, without bootloader update is fine..
Then, after that is flashed, go ahead and flash UGJL2. Make sure to click Phone Bootloader update.
Give that a try and see if it comes back to life.

Hi guys, I'm having the same issue that tekkneak is having, i was able to get mine to reboot with UGJL2 but I had to add the Speedmod-k12j-256hz Kernel. If i dont add the speedmod, the phone will either go into the boot loop or boot past the splash screen and then just give me the black screen with the lit up buttons.
When I boot now I dont seem to have any sort of memory space available, It says 0.0B available and i am unable to format the internal SD card and/or mount an external SD.
I've tried loading UGJH2 and then UGJL2 with bootloader update but like i said before if i dont load the speedmod kernel it will not boot.
Any ideas?

packers17-0 said:
Hi guys, I'm having the same issue that tekkneak is having, i was able to get mine to reboot with UGJL2 but I had to add the Speedmod-k12j-256hz Kernel. If i dont add the speedmod, the phone will either go into the boot loop or boot past the splash screen and then just give me the black screen with the lit up buttons.
When I boot now I dont seem to have any sort of memory space available, It says 0.0B available and i am unable to format the internal SD card and/or mount an external SD.
I've tried loading UGJH2 and then UGJL2 with bootloader update but like i said before if i dont load the speedmod kernel it will not boot.
Any ideas?
Click to expand...
Click to collapse
What error are you getting in recovery?

Samdroid_G_S said:
What error are you getting in recovery?
Click to expand...
Click to collapse
When i run the report error option in the "advanced ClockWorkMod features" i get this:
"E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0"
I've been reading that some people have been able to mount and or format their internal sd cards by using the adb console but I'm not really too familiar on how to do this. Anyone had any luck fixing this?

packers17-0
though that was not the final score, I would like to congratulate on you the win.
If you are getting that error, and you have tried the commands through adb on my first post without luck, then you have either a bad internal memory or a bad controller and will need to seek warranty options.
tekky

tekkneak said:
packers17-0
though that was not the final score, I would like to congratulate on you the win.
If you are getting that error, and you have tried the commands through adb on my first post without luck, then you have either a bad internal memory or a bad controller and will need to seek warranty options.
tekky
Click to expand...
Click to collapse
Haha Thanks! the 17-0 was supposed to be the season record but I must not have been thinking cuz there can't be a 17-0 regular season record - or at least not yet...
I think I may be out of luck on this as I do not have a bill of sale for this device. It was actually given to me by my work to test out user experience on our new network and I'm not sure where it was purchased from or how they got it. I also have a feeling that if i send it back to them I will not see it again or it will be traded for a lesser phone.
Any idea if Samsung will service it without a bill of sale? could they just go by the manufacture date maybe?
Thanks

Yes, they will accept it, I did not have it for my phone, they checked when it was sold on their system and said I still had 7 months of warranty left.
Tekky
packers17-0 said:
Haha Thanks! the 17-0 was supposed to be the season record but I must not have been thinking cuz there can't be a 17-0 regular season record - or at least not yet...
I think I may be out of luck on this as I do not have a bill of sale for this device. It was actually given to me by my work to test out user experience on our new network and I'm not sure where it was purchased from or how they got it. I also have a feeling that if i send it back to them I will not see it again or it will be traded for a lesser phone.
Any idea if Samsung will service it without a bill of sale? could they just go by the manufacture date maybe?
Thanks
Click to expand...
Click to collapse

[GUIDE] Fix an unflashable or soft bricked I9100G

Hello everybody
Due to some demand and request, I've decided to adapt my guide to the I9100G. It deserves some love too!
This is a guide dedicated to noobs, so if you're not one, I would advise to stop reading now! (altough feedback would be great! )
Yes, there have been quite a few threads about fixing a soft brick. But what I'm writting now is another solution to a different kind of problem : unflashable GSII (which also works with a soft brick of course ), which is a soft brick and a corrupted NAND rw (read/write) function.
Just in case you don't know, a soft brick occurs when you flash a ROM or Kernel, and it doesn't go your way, thus bricking the "soft part", aka Software, of your phone. Therefore, it is easy to recover from. Now, regarding NAND rw (NAND's read and write function being the corruption) it means that it is an issue deeper than a soft brick.
It is obvious when you can flash a kernel, but you can't flash a ROM, because it can't properly read the NAND, but can flash a kernel. But you ask, why the kernel? Because flashing a kernel is a bit deeper than flashing a ROM. When you flash a kernel, you're changing/putting new instructions to the hardware, and when flashing a ROM, the instructions that are drewn are different and more "simple", so when flashing, ODIN will say "FAIL" instead of "PASS", or suddenly stopping the flash out of nowhere.
BUT UNFORTUNATELY, this guide will not be able to fix a NAND r/w corruption, due to tyhe fact that I do not have either the .PIT, the bootloader or the kernel, I only have a stock ROM, which will only fix a soft brick.
As soon as I get my laptop back from RMA (this Pentium Dual core I'm using right now isn't trustworthy), I'll extract the zImage and sbl.bin from each ROM, zip it, upload it, and add the rest of the guide.
UPDATE 02/05/2012
GOOD NEWS EVERYONE!Thanks to maui75, I have the .PIT and the gingerbread bootloader! When my laptop arrives from RMA, I'll download and unzip all the packages in this thread, add the .PIT, zip, upload again, and add the rest of the guide! ​__________________________________________________
VERY IMPORTANT ANNOUNCEMENT​
I would like to first apologize for my absence. My past months have been super busy, and they don't seem to be ending anytime soon. And "anytime soon" meaning in a couple of years. And I'm actually glad that this is happening, since I've been working pretty hard to achieve the state I'm in.
This thread has evolved into something I've never imagined. Only because of YOU guys, we managed to turn a normal thread into a pretty popular and well used Guide, and it made me so happy and joyous of being apart of the XDA community. I feel proud in being a XDA nut. This whole success is just because of YOU guys.
As painful as it is to say this... I believe that I will be dropping support on this thread after the New Year, because a) I lost my Galaxy S2 in Paris in a taxi with no hope of getting it back when I went there 3 weeks ago and b) I'm probably getting a Galaxy Note 2 in the New Year, so this thread will be most likely ported and maintained over at the Note 2 forums.
I'm extremely sorry it has come this way, and I hope you guys will understand. In the following days I'll be updating the files to their latest versions, and will try to find new bootloaders and kernels, but without sources, I'm unable to do so. I'll update whatever I'll be able to
Regards and thanks to all of you that have supported me,
Rafael K.​
Click to expand...
Click to collapse
________________________________________________
IMPORTANT ANNOUNCEMENT #2
Please welcome neerajganga, your new thread maintainer (along with me)! He has been of great help, so I think he deserves this kind of announcement!​________________________________________________
IF YOU ONLY HAVE A BOOTLOOP​
Wipe data/factory reset and wipe cache. IF THAT DOESN'T WORK, MOVE ON WITH THE GUIDE
__________________________________________________
Let's start with the basic files, downloads and requirements​
1) You have to know the basics of ODIN and flashing (duh )
2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers
3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II
4) Download the necessary ROM (they are Gingerbread 2.3.6) : Africa (Iraq), Asia (Malaysia), Europe (Open Austria), Middle East (Saudi Arabia). (password is samfirmware.com)
5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano
And that is it! Let's get down to business
__________________________________________________
If your GSII has the folowing symptoms :
Bootloop
Stuck on GSII logo, but already removed the battery to try to fix it
Enters Download mode and Recovery mode
It means that you are soft bricked and is easy to solve.
But if your symptoms are the mentioned above, PLUS the symptoms below
Enters Download mode but does NOT enter recovery mode (usually means a NAND rw corruption)
Doesn't flash
Bad flash in odin (FAIL after flashing, or the flashing suddenly stops)
Then it means that you have a bigger issue, such as the aforementioned NAND rw corruption.
It's time to open up ODIN and start reviving your phone!
__________________________________________________
First of all, let's just have a quick glance of how ODIN looks like, and where we should put the files :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As the picture clearly shows, the green rectangle is where you can tick. Those 2 which are ticked must remain that way. And the red one is well... Where you SHOULDN'T touch
But where are the files going, you say?
.tar -> PDA
__________________________________________________
Recovering a soft bricked phone​
1) Grab the Recovery Package, and put the file in its place.
2) Turn off your phone. Enter Download mode by presing Vol. Up + Home + Power button.
3) Plug in your phone. It will show you, in a yellow box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9, or other numbers)
4) Once ready and done all your prayers, press Start. Wait patiently. It usually takes 5 minutes to flash.
Have you done everything correctly until now? Then...
Congratulations on recovering your phone!​
You deserve some cake afterwards, and some rest
I hope that this guide was helpful, and if it was, hit the thanks button!
Credits mainly go to Intratech and Sammobile, for his amazing gallery of ROMS and files
_______________________
Disclaimer
This is to be used as educational information. I am not liable of any damage that may occur to your phone.

Very good and useful guide. Keep up the good work!

Much simpler
Yesterday i faced a similar problem , i just flashed a kernel and got rid of this problem...

Simple and easy.
I even fixed my Galaxy S2 which was stuck in "Phone-Exclamation-Computer" icon mode. Couldnt even get into Recovery or Download mode.
My phone showed up on Odin so i just flashed it with the stock firmware.
Thanks for the guide!!

When I tried to do a small update via OTA, it got stuck on the Bootlogo.. Did a factory reset, tried to flash via ODIN, but never worked.. Odin just says Checking CS and then closes. It doesn't flash the OS.. Help guys.

WolVish said:
When I tried to do a small update via OTA, it got stuck on the Bootlogo.. Did a factory reset, tried to flash via ODIN, but never worked.. Odin just says Checking CS and then closes. It doesn't flash the OS.. Help guys.
Click to expand...
Click to collapse
What version of ODIN are you using? What fw are you flashing? Have you tried changing cables/use ports?
madbutnotstupid said:
I even fixed my Galaxy S2 which was stuck in "Phone-Exclamation-Computer" icon mode. Couldnt even get into Recovery or Download mode.
My phone showed up on Odin so i just flashed it with the stock firmware.
Thanks for the guide!!
Click to expand...
Click to collapse
No problem!
ashwinsrihari said:
Yesterday i faced a similar problem , i just flashed a kernel and got rid of this problem...
Click to expand...
Click to collapse
Then you just had a corrupt kernel

What version of ODIN are you using? What fw are you flashing? Have you tried changing cables/use ports?
Click to expand...
Click to collapse
The ones found in this very thread only.. Asian firmware. I tried with USB 3.0 USB 2.0 ports, but forgot to try a new USB cable.. It didn't recognise the device i think.
Plug in your phone. It will show you, in a yellow box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9, or other numbers)
Click to expand...
Click to collapse
It didn't happen with my I9100G. Maybe the cable is the culprit.

WolVish said:
The ones found in this very thread only.. Asian firmware. I tried with USB 3.0 USB 2.0 ports, but forgot to try a new USB cable.. It didn't recognise the device i think.
It didn't happen with my I9100G. Maybe the cable is the culprit.
Click to expand...
Click to collapse
Either is the cable, or the USB drivers

TBH i prefer using Toxic Rom to get out of a pickle.

triobot said:
TBH i prefer using Toxic Rom to get out of a pickle.
Click to expand...
Click to collapse
this is for i9100G..not i9100..hihi

triobot said:
TBH i prefer using Toxic Rom to get out of a pickle.
Click to expand...
Click to collapse
ODIN or not, when recovering from a soft brick, it's always better to go stock. It's safer and that can prevent discrepancies between ROMs.
Plus, that's a I9100 ROM, this is the I9100G guide

Odin 1.85 will recognize the phone if it is soft bricked too.
To be updated and have available the original firmware that i want, I verify with "checkfusdownloader". Furthermore, it is faster and easyer than Kies.
It will download the whole files to write with ODIN...

maui75 said:
Odin 1.85 will recognize the phone if it is soft bricked too.
To be updated and have available the original firmware that i want, I verify with "checkfusdownloader". Furthermore, it is faster and easyer than Kies.
It will download the whole files to write with ODIN...
Click to expand...
Click to collapse
Interesting... But does it include a 3-file package, or is it only a 1-file package?

Phistachio said:
Interesting... But does it include a 3-file package, or is it only a 1-file package?
Click to expand...
Click to collapse
...In my case it is only one file .tar.md5

maui75 said:
...In my case it is only one file .tar.md5
Click to expand...
Click to collapse
There we go It's better to flash a 3 part, since sometimes in a soft brick, a single files doesn't pass, but a 3 file pack will.

Phistachio said:
There we go It's better to flash a 3 part, since sometimes in a soft brick, a single files doesn't pass, but a 3 file pack will.
Click to expand...
Click to collapse
I agree with you and in special way for soft brick due to the wrong firmware.
I wish to add the link for all the file ( PIT, PDA, MODEM, CSC, BOOTLOADER, APBOOT) of i9100G CHN KH4, it is a little old but good to repair the chn version.
ht * tp:/ /115.com/file/dnecfzp4
To download the file push the green button... in the begin I had some problem to find all the file for the chn version.... hope will be helpfull

maui75 said:
I agree with you and in special way for soft brick due to the wrong firmware.
I wish to add the link for all the file ( PIT, PDA, MODEM, CSC, BOOTLOADER, APBOOT) of i9100G CHN KH4, it is a little old but good to repair the chn version.
ht * tp:/ /115.com/file/dnecfzp4
To download the file push the green button... in the begin I had some problem to find all the file for the chn version.... hope will be helpfull
Click to expand...
Click to collapse
Oh wow, thanks a LOT! I was looking for the .PIT and the bootloader since always! I'll download the file and upload it to mediafire to facilitate (but that'll only be up when I get home, I'm at school at the moment )
Also, when my laptop arrives, I'll download each package, and add the .PIT so people can have a full recovery (the bootloader will be in a separate download)

Phistachio said:
Oh wow, thanks a LOT! I was looking for the .PIT and the bootloader since always! I'll download the file and upload it to mediafire to facilitate (but that'll only be up when I get home, I'm at school at the moment )
Also, when my laptop arrives, I'll download each package, and add the .PIT so people can have a full recovery (the bootloader will be in a separate download)
Click to expand...
Click to collapse
Great idea...I can not do it, here mediafire does not work
In the begin I did not know the difference from the 9100G and the 9100 so I flashed the wrong rom to root I drived crazy to find the link
Now will be better

maui75 said:
Great idea...I can not do it, here mediafire does not work
In the begin I did not know the difference from the 9100G and the 9100 so I flashed the wrong rom to root I drived crazy to find the link
Now will be better
Click to expand...
Click to collapse
No problem! You already helped me like so much! Thanks a lot again!
It will be better indeed

i9100G ROMS seem to all have different pit files
I ran across a problem while trying to flash the latest ROM from India on a phone bought in China, it always failed at "MSO" and was never recoverable until I flashed back the Chinese ROM, it seems the Indian ROM pack had some different files the Chinese ROM did not have. In short the partitioning appears to be different between some of the ROMS. So is it possible to find the pit files that are connected to each ROM?

My Samsung Galaxy Ace won't turn on!!!!!

Hello, recently i've flashed my galaxy ace with rom manager (ClockworkMod) so i can make the partition thing to my sd card, so i flashed it, turn it off, and then i won't turn on. I can't even charge my phone! I tried to turn it on in reboot mode but it doesn't do anything. I even tried to turn on download mode and nothing. Not even the samsung logo shows up. Nothing! I'm desesperated, I don't know what to do now. I'm new in this forum, so I will be very very thankful if someone could help me on this. Please.

First, ROM MANAGER BRICKS SAMSUNG GALAXY ACE!
Second, YOUR PHONE IS DEAD. TRY A USB JIG OR GOTO SERVICE CENTER.
Third, WHO TOLD YOU TO USE ROM MANAGER?
Fourth, LIE TO SERVICE CENTER TELLING THAT YOU WERE CHARGING YOUR PHONE AND IT TURNED OFF AND IT NEVER TURNED ON. DO NOT MENTION WORDS LIKE "BRICK","ROOT","ROM MANAGER".
Fifth, Welcome to the world of XDA Developers. DO read the threads with a pin icon in front (A.K.A Sticky)

Xr01d_GT said:
First, ROM MANAGER BRICKS SAMSUNG GALAXY ACE!
Second, YOUR PHONE IS DEAD. TRY A USB JIG OR GOTO SERVICE CENTER.
Third, WHO TOLD YOU TO USE ROM MANAGER?
Fourth, LIE TO SERVICE CENTER TELLING THAT YOU WERE CHARGING YOUR PHONE AND IT TURNED OFF AND IT NEVER TURNED ON. DO NOT MENTION WORDS LIKE "BRICK","ROOT","ROM MANAGER".
Fifth, Welcome to the world of XDA Developers. DO read the threads with a pin icon in front (A.K.A Sticky)
Click to expand...
Click to collapse
I never understand, that people who buys a new device, why don't read something about it??? Before I buy my Ace, I read a lot about it, I knew, that it's prohibited to use Rom Manager on Ace... There's a lot of info about it...

Another lost to the dark side of rom manager. Rip the poor thing.

Firstly..CWM ROM Manager?
and ROM manger for partition? all you needed was the CWM Recovery.
We have stickies here for a reason and if you dont read them, do not create new threads when you have problems..

a time try to flash my phone with new firmware, and my phone can't turn on, becouse one input of firmware wrong, and then i try to leave baterry and then, try to go download mode again and flash with new firmware, wait flashing finish and my phone can turn on again.
hopefully working with your phone.

v-ace-1 said:
a time try to flash my phone with new firmware, and my phone can't turn on, becouse one input of firmware wrong, and then i try to leave baterry and then, try to go download mode again and flash with new firmware, wait flashing finish and my phone can turn on again.
hopefully working with your phone.
Click to expand...
Click to collapse
Let's give a try, but I think it won't work. Rom Manager hard bricks Ace, and even download mode won't work. Bring it to service center...

armando58 said:
Hello, recently i've flashed my galaxy ace with rom manager (ClockworkMod) so i can make the partition thing to my sd card, so i flashed it, turn it off, and then i won't turn on. I can't even charge my phone! I tried to turn it on in reboot mode but it doesn't do anything. I even tried to turn on download mode and nothing. Not even the samsung logo shows up. Nothing! I'm desesperated, I don't know what to do now. I'm new in this forum, so I will be very very thankful if someone could help me on this. Please.
Click to expand...
Click to collapse
fashing your handphone via odin and you must download firmware in samfirmware.com
maybe your CWM not support or crash for yoaur handphone

armando58 said:
Hello, recently i've flashed my galaxy ace with rom manager (ClockworkMod) so i can make the partition thing to my sd card, so i flashed it, turn it off, and then i won't turn on. I can't even charge my phone! I tried to turn it on in reboot mode but it doesn't do anything. I even tried to turn on download mode and nothing. Not even the samsung logo shows up. Nothing! I'm desesperated, I don't know what to do now. I'm new in this forum, so I will be very very thankful if someone could help me on this. Please.
Click to expand...
Click to collapse
You can use usb jig to force boot into download mode but there's a small chance for it to work
Google usb jig
Sent from. . . . .NOWHERE!

Have you ever heard something like "don't do something unless you know what you are doing", well this is very useful. There's a reason that none on ace developement doesn't use or recomends ROM manager. Brick.
Sent from my GT-S5830 using XDA

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-N7000 using Tapatalk

Xr01d_GT said:
Fourth, LIE TO SERVICE CENTER TELLING THAT YOU WERE CHARGING YOUR PHONE AND IT TURNED OFF AND IT NEVER TURNED ON.
Click to expand...
Click to collapse
This actually happened to my phone. Is it a known fault? Is there a way to repair it without taking it to a service centre 30 miles away?

Your device wont turn on?
I wonder why?
Perhaps its got something to do with the fact that you have broken your device into pieces. Not literally but oh well u get the point.
Sent from my GT-S5830 using xda premium

Sikorsky96 said:
Your device wont turn on?
I wonder why?
Perhaps its got something to do with the fact that you have broken your device into pieces. Not literally but oh well u get the point.
Click to expand...
Click to collapse
If you're responding to me, I don't get your point. I haven't broken it into pieces, literally or otherwise. I haven't modified the OS in any way since I got it. I plugged it in to charge. It is meant to be able to charge.

You're ace is brick go to repair centre if you have the warranty just say you don't know how this happen, or buy a new phone...

gn1989 said:
If you're responding to me, I don't get your point. I haven't broken it into pieces, literally or otherwise. I haven't modified the OS in any way since I got it. I plugged it in to charge. It is meant to be able to charge.
Click to expand...
Click to collapse
He isnt replying to you!

i face that problem too, after i search the entire thread in this forum then i found this method. try this, maybe it can help :
- pull out your battery
- press the vol down+home+power n in the same time then pull in your battery (if you can't do it alone, ask somebody to help you pull in the battery)
- wait (n pray maybe ) until download mode appear
hope it can help you..:fingers-crossed:

happened the same
i tried flashing stock rom froyo 2.2.1 from odin it cme up as pass but when i dsiconetted nothing happened my phone is ****ed help me anyone it wont even show the samsung logo what do u advise me to do i live in india should i go o the service center or what

Come on everyone!!
Rather than making snide comments, we SHOULD be helping him.
Here, check this out it helped my friend when he bricked his SGA.
Un-Bricking SGA
And remember, from now on use CWM Recovery, or if you want then use ODIN,
BUT NEVER, EVER USE ROM MANAGER. IT'S THE SHINIGAMI FOR OUR PHONE!!!

Another victim of ROM Manager. RIP.
Inviato dal mio GT-S5830

[Q][SOLVED] i9000, front buttons not working with custom ROM: rebranded SHW-M110S!!!

Hi,
I just bought a Samsung Galaxy S i9000 white, and started to work on getting CyanogenMod on it.
Then I noticed that someone in the shop (I guess) had already messed with it. It came with Lidroid ROM installed, but no ClockworkMod recovery.
Anyway, I started having strange issues trying to flash first the ClockworkMod recovery with Heimdall.
Then I decided to try going back to a stock rom, and take it from there.
After a lot of messing around, here is the status:
I have used Heimdall to flash a stock ROM, using first the 512 .pit, and then the 803 .pit.
Then I used the hardcore-speedmod.tar zImage with Heimdall, and finally got ClockworkMod recovery going.
I flashed CyanogenMod 7.2, which "works", but has some strange problems. See below.
I am becoming suspicious that this is not a 100% real Galaxy S (not sure if that's possible, though).
Problems:
Front buttons (Settings, Home, Back) don't work.
Screen rotation is messed up: it's like the sensor is 90 degrees rotated.
No GSM network, fortunately WiFi works. With some effort, I have made it to the Settings menu on CM9.1, and I have lost my IMEI I'll have to research into getting it back.
Can anyone give me some hints? Here are my questions:
There is a sticker with IMEI and model under the battery, it says i9000gsmh. How can I check 100% sure which model of Samsung Galaxy S i9000 I have?
Lidroid is a Chinese ROM, is that a clue? I can't find any useful information on it in English. Maybe I need to flash that and stay with it? (if I can find it)
Thanks for your help!!

kbloodstone said:
I just bought a Samsung Galaxy S i9000 white, and starte
Can anyone give me some hints? Here are my questions:
There is a sticker with IMEI and model under the battery, it says i9000gsmh. How can I check 100% sure which model of Samsung Galaxy S i9000 I have?
Lidroid is a Chinese ROM, is that a clue? I can't find any useful information on it in English. Maybe I need to flash that and stay with it? (if I can find it)
Thanks for your help!!
Click to expand...
Click to collapse
read this thread http://forum.xda-developers.com/showthread.php?t=1844821&page=2 and also this http://forum.xda-developers.com/showthread.php?t=1880689 and a few others, I have forgotten about
This units i9000gsmh seem to have an Anycall boot loader , which by right be used only on a M110S, but seems to be used by Lidroid ( Chinese developer) ..keeps me wondering if its a clone..problem here, they seem to get stuck and not being able to be changed by flashing a i9000 boot loader .
leads me to think that this units could be switched with motherboard or chips meant for Anycall M110S ...anyway solutions for IMEI issues are mentioned on My Android Solutions, link below

I'm going to try that M110S repair kit. See if I can get back to something that can be used as a phone, first priority.
I saw the Anycall logo on my screen, but back then I didn't know that I wasn't supposed to see that on a real i9000.
I think someone in South-East Asia has obtained a bunch of M110S, and has realized that swapping the case makes them worth more money...
xsenman said:
read this thread http://forum.xda-developers.com/showthread.php?t=1844821&page=2 and also this http://forum.xda-developers.com/showthread.php?t=1880689 and a few others, I have forgotten about
This units i9000gsmh seem to have an Anycall boot loader , which by right be used only on a M110S, but seems to be used by Lidroid ( Chinese developer) ..keeps me wondering if its a clone..problem here, they seem to get stuck and not being able to be changed by flashing a i9000 boot loader .
leads me to think that this units could be switched with motherboard or chips meant for Anycall M110S ...anyway solutions for IMEI issues are mentioned on My Android Solutions, link below
Click to expand...
Click to collapse

Ok, some progress..
EDIT: It works!!!!!!
I realized I had forgotten to flash the modem.bin file with Heimdall from the repair kit. I did that now, and I am connected to the GSM network!!!
Still running Eclair 2.1, stock M110S firmware.
I think it's quite clear that this is actually the M110S, and that they took Lidroid, hacked it to make it say i9000, and are now selling these phones as if they were the international version.
Now I need to make up my mind if I go back to the shop to try to get my money back, or swapped for a real i9000... if they have one. Life with the M110S doesn't seem so nice...
Thanks again, xsenman!!!!
=============================================================
Ok, I have flashed the files and .pit from the rescue kit using Heimdall. Now I have the Eclair 2.1 version for the M110S running. I couldn't flash the movinand file, though.
In any case, the front buttons work now, as well as the correct screen orientation. Model says M110S, but baseband unknown, and still no GSM network.
Now I can't get the phone into Download mode anymore. Does the M110S use a different 3-key combo? I can't find anything about that.
EDIT: Nevermind, now it's just holding the Home button.
I was able to recover the /sdcard/backup/efs/ folder, so I have that now, hopefully with my IMEI in there...
Any suggestions to get the phone into Download mode? Or how to root it so I can try to restore IMEI? It looks like the instructions for rooting are for a later firmware than 2.1.
kbloodstone said:
I'm going to try that M110S repair kit. See if I can get back to something that can be used as a phone, first priority.
I saw the Anycall logo on my screen, but back then I didn't know that I wasn't supposed to see that on a real i9000.
I think someone in South-East Asia has obtained a bunch of M110S, and has realized that swapping the case makes them worth more money...
Click to expand...
Click to collapse

Awesome! (sort of)
Ok, now that I have become so fluent in Heimdall usage, I just flashed the latest Korean .pit I have, from the repair kit, combined with the latest GFAN ROM WF07 SP8 XDA edition. So I'm on GB 2.3.6, GSM works, WiFi works. Now that I at least have a phone again, time to consider my options about going to the shop and sticking it to the guy where the sun don't shine...
It seems I have my IMEI working, too.
Once again: xsenman, thank you!!!
kbloodstone said:
EDIT: It works!!!!!!
I realized I had forgotten to flash the modem.bin file with Heimdall from the repair kit. I did that now, and I am connected to the GSM network!!!
Still running Eclair 2.1, stock M110S firmware.
I think it's quite clear that this is actually the M110S, and that they took Lidroid, hacked it to make it say i9000, and are now selling these phones as if they were the international version.
Now I need to make up my mind if I go back to the shop to try to get my money back, or swapped for a real i9000... if they have one. Life with the M110S doesn't seem so nice...
Thanks again, xsenman!!!!
=============================================================
Ok, I have flashed the files and .pit from the rescue kit using Heimdall. Now I have the Eclair 2.1 version for the M110S running. I couldn't flash the movinand file, though.
In any case, the front buttons work now, as well as the correct screen orientation. Model says M110S, but baseband unknown, and still no GSM network.
Now I can't get the phone into Download mode anymore. Does the M110S use a different 3-key combo? I can't find anything about that.
EDIT: Nevermind, now it's just holding the Home button.
I was able to recover the /sdcard/backup/efs/ folder, so I have that now, hopefully with my IMEI in there...
Any suggestions to get the phone into Download mode? Or how to root it so I can try to restore IMEI? It looks like the instructions for rooting are for a later firmware than 2.1.
Click to expand...
Click to collapse

kbloodstone said:
Ok, now that I have become so fluent in Heimdall usage, I just flashed the latest Korean .pit I have, from the repair kit, combined with the latest GFAN ROM WF07 SP8 XDA edition. So I'm on GB 2.3.6, GSM works, WiFi works. Now that I at least have a phone again, time to consider my options about going to the shop and sticking it to the guy where the sun don't shine...
It seems I have my IMEI working, too.
Once again: xsenman, thank you!!!
Click to expand...
Click to collapse
thanks , so most likely they removed the antenna and used a i9000 back cover to make it look like the i9000...anyway everything with regards to the M110S can be found at PIT STOP .
well at least this would resolve the problems faced by many i9000gsmh units

Sharing my fix...
Hi,
xsenman: I have compressed all the files that I used for converting my i9000gsmh into a "proper" SHM-M110S, for stock Eclair 2.1, and for GFAN's ROM, including a small script (just one line) that flashes them with Heimdall, including working .pit files and repartitioning the phone just in case.
I want to share them, to help out whoever is stuck with one of these phones. How do you recommend that I do that?
Do you want to look at them first and then share them yourself?
On a side note: it looks like the guy that sold it to me has absolutely no clue about Android, so he is as scammed as I was. So I guess I am the proud owner of a SHM-M110S, and not a i9000 like I hoped...
Hopefully someone will get a ICS or JB kernel going for this someday...

kbloodstone said:
I want to share them, to help out whoever is stuck with one of these phones. How do you recommend that I do that?
Do you want to look at them first and then share them yourself?
Click to expand...
Click to collapse
just put the links here as I have already linked this page here
Just wondering did the M110S repair kit fail in solving this problem?
---------- Post added at 12:17 PM ---------- Previous post was at 12:06 PM ----------
the model is SHW M110S, kindly edit your Header

Oops, I'll fix the header as soon as I can.
The Repair kit helped. It had the right files in but two things made life a bit more difficult for me:
I use Linux, so I can't use Odin. I had to do the flashing with Heimdall.
At least using Heimdall, it wouldn't finish flashing the movinand file. I had to ignore that one. Luckily it all still worked.
Besides that, I had to look at the Word file included, and from the screenshots figure out what was happening. I combined all three steps in one go, flashing directly the latest files. I put all the files of step 1 in a folder. Then I overwrote those files with the files from step 2, and then with the files from step 3. I made sure to use the .pit file that was used last (although it seems only in the first step the Repair kit was repartitioning the phone).
Does it make sense?
xsenman said:
just put the links here as I have already linked this page here
Just wondering did the M110S repair kit fail in solving this problem?
---------- Post added at 12:17 PM ---------- Previous post was at 12:06 PM ----------
the model is SHW M110S, kindly edit your Header
Click to expand...
Click to collapse

kbloodstone said:
Does it make sense?
Click to expand...
Click to collapse
No problem, a heimdall kit would of great help too , just upload to wherever you like and I will link it to PIT STOP too.
The actual guide for using the M110S kit is available as How to Flash guide
You can prepare something like this for using heimdall an include into your upload, would surely be helpful .

Repair your "i9000gsmh"
Ok, so I have uploaded the files that I used for fixing my phone, and getting it to 2.3.6.
There are some minimal instructions in both files, and they require Heimdall installed.
http://www.4shared.com/folder/WB8Bbk3z/SHW-M110S.html

And I forgot to mention, but I also went to check my IMEI in one of those websites, and it is the IMEI of a SHW-M110S.
So... yes, what we thought: now I have a DVB receiver that I'll never use, and a phone that can't run Jelly Bean
kbloodstone said:
Ok, so I have uploaded the files that I used for fixing my phone, and getting it to 2.3.6.
There are some minimal instructions in both files, and they require Heimdall installed.
http://www.4shared.com/folder/WB8Bbk3z/SHW-M110S.html
Click to expand...
Click to collapse

kbloodstone said:
Ok, so I have uploaded the files that I used for fixing my phone, and getting it to 2.3.6.
There are some minimal instructions in both files, and they require Heimdall installed.
Click to expand...
Click to collapse
How did you get into download mode?

jamesdubit said:
How did you get into download mode?
Click to expand...
Click to collapse
press home + Power, but this model will be in download mode if you see "UPGRADE" screen, so just connect to odin3, if it connects, just flash
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

[Q] Internal SD card bricked can't install cyanogen mod or other roms

Hay Guys
I've one big problem probably I think its a big problem but...
So I can't format my Internal SD on German it says USB Speicher
so after every restart the apps, files from the guy before me are coming back to my tab and i can't delete them
and I've install the Cyanogenmod but after the boot screen there was an error i can't remember what name it was but there was a long text which says that the internal memory can't be formated?! But why? :/
I hope u can help me

Can you go to Download mode? Restock to stable gingerbread build
Sent from my GT-N8000 using XDA Premium HD app

i´ve restocked 7 times
but it don´t change anything :/

Now there is this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
have i bricked my SGT ?

No, it's not bricked, it's in download mode, you can still flash a rom via heimdall or Odin.

yesssssssssssssssssssssss!!!!!! your phone is totally -SOFT BRICKED- term used when something in the software is destroyed there are many videos on how to fix soft bricked sgt on youtube... just secure odin, stock firmware and youre sgt drivers. this is my first time to actually post a help cause i have encountered this problem too

royban123 said:
yesssssssssssssssssssssss!!!!!! your phone is totally -SOFT BRICKED- term used when something in the software is destroyed there are many videos on how to fix soft bricked sgt on youtube... just secure odin, stock firmware and youre sgt drivers. this is my first time to actually post a help cause i have encountered this problem too
Click to expand...
Click to collapse
There is no such thing as "soft brick", Your device is either "bricked" or it isnt. When your device is bricked only option is to replace mobo or repair via some method like JTAG connection.
If you can enter recovery or download mode you can simply reflash a rom, Which means you dont have a "bricked" device at all, It just means that your rom wasnt booting because you didnt read instructions correctly or flashed an incorrect kernel or rom etc.

TheATHEiST said:
There is no such thing as "soft brick", Your device is either "bricked" or it isnt. When your device is bricked only option is to replace mobo or repair via some method like JTAG connection.
If you can enter recovery or download mode you can simply reflash a rom, Which means you dont have a "bricked" device at all, It just means that your rom wasnt booting because you didnt read instructions correctly or flashed an incorrect kernel or rom etc.
Click to expand...
Click to collapse
i dont know... very well explained by the way, but just give time to google search the term soft bricked then results will come out (just to verify the term)

It starts again
But the problem with the internal sd card still there :/
Online with Galaxy Tab

If you tab has an internal sdcard problem, you might want to read this: http://forum.xda-developers.com/showthread.php?t=1463756

royban123 said:
i dont know... very well explained by the way, but just give time to google search the term soft bricked then results will come out (just to verify the term)
Click to expand...
Click to collapse
Yes ofcourse the term will come in results because there are a zillion topics with n00bs saying things like hard brick and soft brick. Technically there is only "bricked". It may be easier to create a different type of brick but in reality its simply not bricked at all, You just need to re-flash correctly.
n00bs like to call their device soft-bricked when they have screwed up flash in some way so system wont boot to OS, that isnt bricked that just means your rom isn't booting. "bricked" is when your device wont boot period or you cant get into recovery/download at all or they are faulty in a way you cant use them to flash the nand. Perfect example is when you flash incorrect pit file or corrupt your bootloader etc.

Okey but how i can flash the rom correct?
i mean to full wipe the sgt?
and one more question....
how i can change my signature?

TheATHEiST said:
There is no such thing as "soft brick", Your device is either "bricked" or it isnt. When your device is bricked only option is to replace mobo or repair via some method like JTAG connection.
If you can enter recovery or download mode you can simply reflash a rom, Which means you dont have a "bricked" device at all, It just means that your rom wasnt booting because you didnt read instructions correctly or flashed an incorrect kernel or rom etc.
Click to expand...
Click to collapse
I know his device is not bricked. The important thing for the op is to find how to get his device working again. If he would like to find info. on the web, for a device that lost communication at the middle of a flash, he will have to do a google search on bricked or soft bricked devices. Who cares about terminology if you are not going to find what you are looking for.
Here's a video, on flashing a Galaxy tab wich has a disconnected status: http://www.youtube.com/watch?v=a3htbNck38w
Here's a full page of youtube videos on soft bricked galaxy tab: http://www.youtube.com/watch?v=a3htbNck38w
So, your agument doesn't help the op, it just help in confusing him a little more.
SL!D3 said:
Okey but how i can flash the rom correct?
i mean to full wipe the sgt?
and one more question....
how i can change my signature?
Click to expand...
Click to collapse
Find the full original rom for your device, including the pit file, and flash using either Odin or heimdall. The pit file is very important, as you tried installing cwm/cm9, and your device will have to be repartitioned.
As for your signature, click on user cp at the top left of the page.
BTW, there is over 30 models of the original Samsung tablet, so, how the hell do you think people tell you exactly what to download and what to flash to get your tab working again?

Okey but where i can find roms?
On samfirmware are only tar files no pit files :/
But guys at this point thanks for help! !
Gesendet von meinem GT-P1000 mit Tapatalk 2

Check in the dev forum, I'm sure you'll be able to find a pit file for you tab.
Sent from my SCH-I800 using xda premium

So and if i'll flash my tab with the right rom and pit all be fine again?
Gesendet von meinem GT-P1000 mit Tapatalk 2

It should
Sent from my SPH-P100 using XDA Premium

I was thinking that all pit files are the same for the sgt
Gesendet von meinem GT-P1000 mit Tapatalk 2

I think so too. As long as you take a pit file made for the same Android version of your gsm galaxy tab, you should be good to go.

You will also read some nand chips just turns bad and becomes like yours.
Sent from my GT-P1000 using xda app-developers app