Okay my friends wife had an unlucky bad file flash and ended up hard bricking somehow.
And keep this in mind that she never flashed a Int. version.
She flashed the SlimRom 3.1.0-D2SPR then she flashed the custom kernel unlocker file
to use the K747 kernel for slimrom, but the thing was ( She has TWRP ) when she slid the bar to flash
the file, the screen went back to the TWRP home page she waited 5-10 minutes then she tried reflashing the file again
and it said failed. Rebooted and the phone's hard bricked after installing the kernel. ( No LED when USB plugged in for recharge,
No power or haptic feedback. )
Her husband used the same method to install slim rom and his phone is fine
but the screen never went to the TWRP home page, it went straight into installing it.
The thing that boggles my mind is that she flashed everything in order and it hard bricked.
Rom first, rebooted recovery, kernel unlock, cache and dalvik cleared. rebooted recovery
When she tried flashing the K747 AOSP Kernel, she said it never went to the page screen that would show
it install, it just went straight to the home page, retry flashing but failed. ( here's the weird part I've never experienced. )
Is her devices bootloader corrupted? Because all I'm thinking is she's the one in a million of people that has a defective
device itself and a bad flash ( This is what I think ) hard brick her device.
But my suggested solution if correct would be force odin mode via USB Jig or send it in for jtag repairs if possible.
If there is no chance for the both of these solutions then a full blown replacement repair will be the last thing she'll do
because she doesn't have TEP or a warranty on the device.
Spark91 said:
Is her devices bootloader corrupted? Because all I'm thinking is she's the one in a million of people that has a defective
device itself and a bad flash ( This is what I think ) hard brick her device.
But my suggested solution if correct would be force odin mode via USB Jig or send it in for jtag repairs if possible.
If there is no chance for the both of these solutions then a full blown replacement repair will be the last thing she'll do
because she doesn't have TEP or a warranty on the device.
Click to expand...
Click to collapse
So, I'm just going to rattle through my thought process on this, just to get things clear in my mind:
Her phone cannot turn on at all. Do a battery pull/replace and make sure that there's no going into recovery or download mode. If that's the case, then JTAG might be your only solution.
This happened when trying to flash a kernel. It seems unlikely that a kernel would screw up the bootloader. I was under the impression that only recovery zips touch the bootloader/recovery partition.
If the kernel or Rom zip was for an international GS3, then it would try to write to the bootloader partition. But since you said your buddy's phone flashed the same files just fine, it seems unlikely that they flashed the international zips.
I've had TWRP fail to flash a zip. Each time I tried to flash a zip, it would say it failed. All I had to do was reboot into recovery (even if I hadn't flashed a ROM, so I had no system file), and then I could flash the file. Sometimes TWRP had those issues for me. Her story reminded me exactly of when that happened to me, but if hers won't load into recovery (or download mode), that's a major difference.
After all that, I honestly have no clue how this happened. It sounds to me like the JTAG is the best bet. You can find them online for around $60. Sorry this happened, and I hope you find a good fix for your friend's wife.
Its possible that you can still fix this....
Couple questions. When you try to turn it on, what exactly happens? does it vibrate? what occurs?
There is a possiblity that you can bypass the idea of holding the power button and vol button, try to adb reboot recovery command. ive had this save me about 5 times now when flashing goes bad.
http://droidlessons.com/how-to-install-adb-on-a-windows-7-pc/
make sure adb is installed...
while the phone is trying to boot, keep typing or copy/pasting or in cmd pressing up and enter after you enter the command.
adb devices
if it gives you the UID of your phone you at least know that you might have the ability to fix it.
From here just type
adb reboot recovery and it will reboot into the recovery to allow you to flash a "good" kernel again.
Bit of advice.. I am always paranoid after going through this so many times of a bad flash. As a result i never stack flashes.. for instance.
if i want to flash a rom, kernel, modem, radio..
i wipe dalvik, flash rom, wipe dalvik, wipe system, wipe cache.
Reboot let android do its thing...
reboot into recovery.
wipe dalvik, flash kernel, wipe dalvik, wipe system, wipe cache.
reboot, let android fully boot up.
reboot into recovery
wipe dalvik, flash radio, wipe dalvik, wipe system, wipe cache.
reboot...you get the point.
Just precations i started doing because of issues ive had in the past. If you have a mac, the commands are a bit different so let me know...
This is interesting, Hamspiced.
I didn't know that flashing a kernal can "brick" your phone.
Do you happen to know why or how this happens? You allude to stacking flashes... I normally only stack gapps with the ROM, but I was wondering if it's important to reboot and go through the setup prior to flashing gapps.
Thanks for the info!
topherk said:
This is interesting, Hamspiced.
I didn't know that flashing a kernal can "brick" your phone.
Do you happen to know why or how this happens? You allude to stacking flashes... I normally only stack gapps with the ROM, but I was wondering if it's important to reboot and go through the setup prior to flashing gapps.
Thanks for the info!
Click to expand...
Click to collapse
When i had my evo things flashed slightly different.
There were many issues in kernel flashing where if the kernel didnt download properly or you had a bad dl. it will what we called soft-brick. This would allow the phone to "act" like it was booting up but only display a black screen and never boot. Screen would flicker, phone was active but nothing would display and it will not boot loop. kind of just freeze.
We noticed that if we connect the phone to the computer we could actually use adb to access the phone. from there we noticed that we could push recoveries, and even push kernels and radios to the phone even though it wasnt displaying anything.
I figured the easiest way to get through this issue is to see if you can Reboot Recovery through adb if it allows you, and hopefully then you can restore functionality.
Help possibly?
Can you get it into download mode and just use Odin to flash it?
Related
Im having a problem with my phone booting. it does a variety of things from rebooting mid way through boot, hanging at the white HTC screen, getting to lock screen then rebooting...
point is, i cant get in to the system.. what i'd like to do is remove everything and get it to stock... the RUU would be nice, but it needs to be booted for that to happen. i've tried a couple of custom roms (vaelpak, synergy) but they all result the same way. cleared dalvik, data, .android_secure, cache with no impact..
RA 2.3 is what the recover console currently is...
what is the best way to recover the phone to stock?
im ok with working with the phone but not awesome so somewhat detailed directions would be appreciated.
hope i didnt leave anything out,
Thanks
What rom are you on? I am assuming you can get into recovery. May I recommend, fresh 4 rom by flipz to get everything back to normal first (Full wipe is necessary) ...then we can work on this further.
thanks for the response.
wiped data/secure/cache/dalvik
applied Fresh 4.2.0.0 rom
rebooted
showed HTC white screen for 2 seconds rebooted.. did this until it gave me the 3 vibrates and flashing green light..
reseated battery and powered on
HTC white hung for what seemed longer than normal than Fresh boots.. lock screen appears for a couple of sec and then it reboots.
thanks
Lets try a few more steps before concluding hardware issues.
1. wipe all
2. http://www.virusrom.com/Tools/VR_SUPERWIPE.zip (flash this)
3. Flash your favorite rom (try one of the newer ones if your SD is partitioned)
4. restart...and let the phone wait for 10 mins...before you unlock the screen
5. unlock screen and let it settle (DO NOT SET UP ACCOUNTS)
6. reboot recovery..wipe cache and dalvik and reboot
7. sign into market...
8. if it still reboots/FCs then flash latest radios http://forum.xda-developers.com/showthread.php?t=715485
cool i'll give that a try..
when you say wipe all, is the list i've provided "all"? i noticed with RA i can wipe system/boot and some others i believe... wasnt sure i should wipe the boot or system...
yes...start at format all factory reset...and then the list you've provided...dont wipe sdcard unless formatting it...and then follow from step 2
yeah basically what i listed was the factory reset + dalvik..
so, you mention if the SD card is partitioned (app2SD?) which i dont currently have setup, but its a new SDcard so i might.. but, if i put one of those newer roms on that assume App2SD (which i believe i did) then would the problems im having be a result of doing that??
no luck, still getting random reboots
what rom did you flash? But if you did all the steps from my earlier post, I am wondering if this is an hardware issue.Heres a thread about back to stock RUU . http://forum.xda-developers.com/showpost.php?p=7529500&postcount=1
here another for the latest froyo ruu
http://forum.xda-developers.com/showthread.php?t=874251
just in case you would want to root back
well that sucks... i just replaced the screen and LCD too....
thats the tool i was trying to use but couldnt keep the system up long enough to get it to run right... in order to run the RUU you need to be in android (is that right? sounds werid, like saying in windows, past boot, etc etc).. anyways.. it has to be loaded, the RUU then flashes a special boot loader to do the restore... i've gotten a handful of errors, some of which even say that i have the wrong version (i'll try the one you posted but i've used an RUU before and tried the same one again)
i'll keep screwing with it, or get a new phone i guess.. still a year left on my contact so i'll be hitting up ebay or something :-/
thanks for all your help, really apprecaite it
Hi!
Downloaded and clean flashed AOKP B30 and gapps, came from M4. Got into a bootloop. Went into recovery, wiped, still bootloop. Pushed an original image to the phone via Gnex Toolkit. Still bootloop!!
Now I have no idea what to do....
Please help!!
CWM cant find my sdcard either it seems!
If I try going into stock recovery, I get an android with a triangle.
Step 1: Take a deep breath. Your device is fine (although your data is probably gone).
Recovery cannot find /sdcard because there is likely an issue with your data partition, where /sdcard resides. The best thing to do is flash the stock images again. I recommend you do it manually so you can actually see what you are doing, instead of using a toolkit. Follow this procedure and you will be fine. And flash back CWM. (The android you are seeing with the red exclaimation point IS the stock recovery. To access the menu from there, repeatedly press volume up and power until you see the menu.)
Thanks for your help, but it seems the problem was that the phone was connected to the computer. So I probably just flashed stock and wiped my sdcard for nothing. Since everytime it bootlooped, the computer tried to install a driver.
I feel stupid.
eivi91 said:
Thanks for your help, but it seems the problem was that the phone was connected to the computer. So I probably just flashed stock and wiped my sdcard for nothing. Since everytime it bootlooped, the computer tried to install a driver.
I feel stupid.
Click to expand...
Click to collapse
Knowing is half the battle.. nexus is pretty brick proof
Sent from my francoPhone
so, for some weird, out-of-the-blue reason, i can't flash anything successfully through odin. i tried flashing sfhub's el29 one-click ROM (no data) and it flashed, however, when it's done flashing and it tries to boot, it just bootloops. i used to be able to just go into recovery, wipe data, reboot, and all would be fine, however i can't boot into recovery. when i hold down volume up + power, it shows the galaxy boot ani for a few seconds like it normally does when going into recovery mode, but then it'll disappear, the screen will go black, and then it will try to reboot normally again. it never goes into recovery mode.
i tried flashing EL26 stock CMW kernel, and odin goes through the motions as if it flashes, however, when i try to boot into recovery, it does what it did before: display the galaxy boot animation for a few seconds, disappear, then reboots normally.
now, i'm trying to flash sfhub's fb17 full restore and it's hung at data.img (like only 2% remaining). it's been stuck for about 10 minutes now.
WHAT DO? should i try using Kies to reinstall stock firmware?
Your phone might be bricked with a failure of the data partition on your emmc
http://forum.xda-developers.com/showthread.php?t=1504808
dammit that really blows! i need to order a jig now to clear my count. dammit i knew i should've used the triangle app last night when i had the chance. blahhhhhhhhh
okay so i was able to remove the yellow triangle, but am not able to reset the odin count. is there a way to reset the count via recovery or odin? obviousy i can't use the yellow triangle app cuz i can't even get android loaded. seems like whatever the yellow triangle app is doing should be able to duplicated in recovery too. what say?
cnstarz said:
okay so i was able to remove the yellow triangle, but am not able to reset the odin count. is there a way to reset the count via recovery or odin? obviousy i can't use the yellow triangle app cuz i can't even get android loaded. seems like whatever the yellow triangle app is doing should be able to duplicated in recovery too. what say?
Click to expand...
Click to collapse
Good info of the location the count is stored : http://forum.xda-developers.com/showthread.php?t=1494114
Sent from my MZ505 using XDA Premium HD app
yeah, i saw that earlier, but i can't make anything of it.
i tried "/sys/block/mmcblk0boot0/force_ro" via adb while in recovery, but got access denied. is it because su isn't included in rogue 1.1.2 recovery? if so, how do i install su?
At least you should have the original bootloader so a jig will work.
To help others, do you think you can remember when the problem happened.
Usually it happens when doing operations in an ics-based custom recovery, operations like wipe/factory reset, restoring backups, flashing ROMs, etc.
i guess the usb jig is my only option if i wanna take it to the store. i'm a cheapskate and dont feel like waiting to get a jig shipped to me and then waiting longer for sprint to replace the phone, so i really wanted to find any manual way of repartitioning or just resetting the count myself.
anywho, this all started when...
i was in the process of wiping my phone to install aokp build 31. i flashed calk's wipe all script, then used the factory reset option in cwm recovery (http://www.mediafire.com/?hkydca9ob98z89m, first post of aokp dev thread). everything was kosher. i started odin'ing el26 (cuz i like to play it the safe way, and this way has always worked for me). odin seemed successful cuz it said "passed!"; and i had done this numerous times with every build of AOKP and CNA so nothing seemed out of the ordinary. when it rebooted, it got stuck at boot loop, which is typical in my experience -- i just go into stock recovery and wipe data and all would be good again. however, this time when i went into stock recovery to wipe data, it just froze and didn't do anything. and that's how i met your mother.
also, apparently the only recovery image i can flash via odin is steady hawkin's rogue recovery 1.1.2.
Okay wtf im able to flash cm7 all of a sudden. Brb, blowing load into sock, will report back later.
nvm, it freezes about 5 seconds after loading the home screen.
cnstarz said:
i guess the usb jig is my only option if i wanna take it to the store. i'm a cheapskate and dont feel like waiting to get a jig shipped to me and then waiting longer for sprint to replace the phone, so i really wanted to find any manual way of repartitioning or just resetting the count myself.
anywho, this all started when...
i was in the process of wiping my phone to install aokp build 31. i flashed calk's wipe all script, then used the factory reset option in cwm recovery (http://www.mediafire.com/?hkydca9ob98z89m, first post of aokp dev thread). everything was kosher. i started odin'ing el26 (cuz i like to play it the safe way, and this way has always worked for me). odin seemed successful cuz it said "passed!"; and i had done this numerous times with every build of AOKP and CNA so nothing seemed out of the ordinary. when it rebooted, it got stuck at boot loop, which is typical in my experience -- i just go into stock recovery and wipe data and all would be good again. however, this time when i went into stock recovery to wipe data, it just froze and didn't do anything. and that's how i met your mother.
Click to expand...
Click to collapse
I've never used calks format all with anything ics related because I heard you don't want to format the data. also when you factory reset was that on el26?
I got yelled at for starting a new thread because this is the exact same problem that happened to me. I was in Calks ics rom, I had downloaded the new alpha build for CM9, and installed rom manager and clockwork and went into recovery and went to wipe everything and BOOM, froze, and then when I tried to restart it it got stuck on the galaxy s ii logo and kept cycling like yours did. I cant get into recovery, but can get into download mode.
So OP|, are we screwed? Did you find a way to fix er up? Cuz I haven't
level27xrock said:
I got yelled at for starting a new thread because this is the exact same problem that happened to me. I was in Calks ics rom, I had downloaded the new alpha build for CM9, and installed rom manager and clockwork and went into recovery and went to wipe everything and BOOM, froze, and then when I tried to restart it it got stuck on the galaxy s ii logo and kept cycling like yours did. I cant get into recovery, but can get into download mode.
So OP|, are we screwed? Did you find a way to fix er up? Cuz I haven't
Click to expand...
Click to collapse
check out this thread:
http://forum.xda-developers.com/showthread.php?t=1504808
i've basically moved my discussion to that thread. there's a user who was able to recreate the datafs partition using some of the sdcard storage space with success, obviously at the cost of storage space. check it yo.
level27xrock said:
I got yelled at for starting a new thread because this is the exact same problem that happened to me. I was in Calks ics rom, I had downloaded the new alpha build for CM9, and installed rom manager and clockwork and went into recovery and went to wipe everything and BOOM, froze, and then when I tried to restart it it got stuck on the galaxy s ii logo and kept cycling like yours did. I cant get into recovery, but can get into download mode.
So OP|, are we screwed? Did you find a way to fix er up? Cuz I haven't
Click to expand...
Click to collapse
Level27xrock,
To answer your question first, you're probably "hard" bricked. It's been posted many times that you'll be able to get into Download mode, ODIN *most* of the stock image and it will hang at data.img because a previous action that you did - suspected to be the CWM wipe operation but not definitively confirmed - caused a I/O problem within the embedded memory or eMMC. Please feel free to try this out on your own and verify the results for yourself - it seems that may be the only way of convincing you.
You can find out more in the thread linked above.
I hope you will read the threads more before you try again. Please start with the one that says "How Not To Brick Your E4GT" for example. You also missed the one that said ROM Manager is a no-no for the E4GT - believe it's in the Q&A forum.
If I read the earlier posts right, I believe something similar happened to my friend. He was on AOKP then tried to Odin FD05 and it wouldnt get past splash screen. He then went back to EG30 and ran that through Odin and it did work but if some ROMs effect Odin completely flashing and restoring a stock setup then we are going to have a new surge of problems
Edit..he did NOT wipe in ICS recovery either
Sent from my Nexus S 4G using XDA
I've been lurking for quite some time and haven't been able to find a solution for my issue. Here's what happened:
I cracked the screen on my Galaxy Nexus and got an insurance replacement. I then used ClockworkMod Recovery to copy over from my old device to my new device. All was good for about 12 hours when the new device started boot looping with the flashy color animation screen. I figured that might have been something I did, so I tried doing a factory reset and the like with ClockworkMod Recovery and managed to totally mess the phone. After trying to do a factory reset, the phone wouldn't boot up at all anymore -- I just get the dreaded red triangle with exclamation point. I tried formatting all the partitions with ClockworkMod (which was a bad idea). Ever since then, I've been stuck. I've spent several days so far trying to get this thing working. I have to note that Odin and fastboot modes work perfectly fine.
Among things I've tried unsuccessfully:
Flash to stock using Odin
--Odin says everything is fine, when I flash with a stock ROM that I downloaded. Upon reboot, nothing is any better and I still get the red triangle/exclamation point.
--When I try to use the tar files that ClockworkMod generated, Odin crashes immediately.
Push custom ROMs to /sdcard/ using adb while booted into ClockworkMod in hopes of getting the system to boot.
--This never works successfully. Sometimes I get no error but can't find the zip file. Other times I'll get an I/O error, or even a read-only error. The original backup is giving me checksum errors.
Flash factory ROMs using fastboot.
--I always get the red triangle/exclamation point.
Restore and flash with WUG's toolkit.
--Same thing as when I try to use fastboot. It seems that flashing the device goes fine, but the device will still not boot.
After every time I've flashed the device, whether using Odin or fastboot, I've tried doing a factory reset by pressing power+vol up+vol down and then selecting factory reset. This hasn't made any difference.
I'm about to give up on it and send the device back to the nameless insurance company, but I would like to lock the bootloader first. I can't even seem to lock the bootloader! In fastboot, I type the usual 'fastboot oem lock', and the device reports that it is locked, but after rebooting, the device always reverts back to having an unlocked bootloader.
Have I missed anything? Any thoughts? I'm lost.
Fyi, the red exclamation point is the stock recovery screen.
Try following the instructions in the "flash" link in my sig.
Sent from my Galaxy Nexus using Tapatalk 2
As well, issue the following commands when in fastboot:
Fastboot erase system
Fastboot erase userdata <- this will wipe by the way, including/sdcard
Fastboot erase boot
Fastboot erase recovery
Fastboot erase cache
And then flash the images in fastboot.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks a ton for the helpful info -- I hadn't tried flashing userdata and system using that method before, and your write-up was definitely one of the more helpful I've seen.
Unfortunately, it doesn't seem to have helped. I used the factory 4.0.2 mysid/toro image on the link you provided. While flashing, the system seems to work absolutely fine, but it just reboots into recovery at the end.
I followed your instructions twice, including erasing the partitions. Also, after each try, I've tried doing a factory reset from recovery and then rebooting (after trying to boot a couple times), though none of this helped.
enginerrd said:
Thanks a ton for the helpful info -- I hadn't tried flashing userdata and system using that method before, and your write-up was definitely one of the more helpful I've seen.
Unfortunately, it doesn't seem to have helped. I used the factory 4.0.2 mysid/toro image on the link you provided. While flashing, the system seems to work absolutely fine, but it just reboots into recovery at the end.
I followed your instructions twice, including erasing the partitions. Also, after each try, I've tried doing a factory reset from recovery and then rebooting (after trying to boot a couple times), though none of this helped.
Click to expand...
Click to collapse
If you've flashed the system, userdata and boot images using fastboot, and you are still not able to boot into Android, I can only suspect that you have either a corrupt bootloader or a hardware issue.
And if odin does not work, then unfortunately I would suspect that there is a hardware issue.
This sounds like what happened to my phone as well. Someone else had it happen too. That's 3 nexus's in a week. Mine didn't even last 2 months.
I have a thread about mine and another user posted another thread a day or 2 ago. Mine boots into the system but is not erasable, not writable. Can't lock my boot loader. I've tried odin, adb, everything possible. I wish we could start a lawsuit because Samsung won't help me. I'm in the US and it's a gsm nexus that was purchased before the play store sold it. USA wont accept an international phone and UK Samsung won't take a phone from overseas. Basically they said I'm sh*t outta luck.
Thanks again for the help. I'm going to bite the bullet and just call the insurance company and try to send it back as a defective device. Hopefully they don't rake me over the coals.
I'll post back with an update as to how that goes.
You guys need to learn how to use fastboot and adb commands correctly to restore google's stock images.
Stop realying on toolkits thinking it will help you.
Also learning that the Red Exclamation Android is stock recovery!
Press the Power and Vol Up button will get you the stock recovery menu options to come up!
Not to be mean, BUT I hope the insurance company denies you, you totally screwed up the phone yourself.
I did not screw my phone up myself. My phone was never even rooted. I know very well how to issue adb commands and install images. Learn what you are talking about before you jump onto people or come across as a total di*khead
Alright, replacement phone is on the way. Thanks again for the help. I tend to think it is a hardware issue because of how the issue originally presented itself, but I'm still pretty new to the Android platform. It seemed to me that a watchdog timer was timing out or something similar.
Perhaps this will be the push I needed to start developing Android hardware/software... I'm all about embedded systems and would like to move beyond basic ucontrollers.
Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
fza99 said:
Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
Click to expand...
Click to collapse
I have some very bad news for you.... Encryption is a one way street. Once encrypted the only way back is to flash stock via fastboot.
I can't even start to explain how to use fastboot as I have never been in a situation where I have needed it.
recoveries lose all access on encrypted devices so this is the only way.
Here is some links to get you started... Please do research before you begin the process and make sure you've obtained the appropriate files. I will take no responsibility for bricking your device.
Flashing via Fastboot:
http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
Installing Fastboot on Windows:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Sent from my SGH-I747 using xda app-developers app