Is there a way to revert to stock rom [Problem] - Kindle Fire Q&A, Help & Troubleshooting

I was recently using the KFU on a First Gen Kindle when Windows stops recognizing and it immediately stops at the Kindle Fire logo. The only way I could revert to normal mode was getting the PC to recognize it by doing the shorting method.
My problem is exactly like this one from a previous user:
"Ok I know tons of people think they have bricked their device, but usually it is just a soft brick....hopefully I am the same. I tried to root my kindle fire using KFU. Something happened, it didn't work. Now it just stays on the boot screen. In windows it isn't recognized, I have read the forums and know to reinstall the drivers, but I can't because Windows recognizes it as an unknown device, (code 43), so they won't install. I have tried using the unbrick utility, but it doesn't work since windows isn't recognizing the device. I have a mac too that won't recognize it, at least I don't think it does. Maybe there is a way to get the drivers installed I am missing, but I tried following all of the tutorials here, and its not wokring. Is it possible that I can still fix it, or is it done. Thanks for any help."
Now I want your opinions on what to do. The top touch screen is not recognizing and is NOT like before, touch screen is hardly reading. I don't know if this is software, but another thing is after turning it on each time the Kindle Fire Logo flashes 1once, goes black for about 3 seconds and flashes again before booting up.
Anybody have any suggestions.

ccs2ds said:
I was recently using the KFU on a First Gen Kindle when Windows stops recognizing and it immediately stops at the Kindle Fire logo. The only way I could revert to normal mode was getting the PC to recognize it by doing the shorting method.
My problem is exactly like this one from a previous user:
"Ok I know tons of people think they have bricked their device, but usually it is just a soft brick....hopefully I am the same. I tried to root my kindle fire using KFU. Something happened, it didn't work. Now it just stays on the boot screen. In windows it isn't recognized, I have read the forums and know to reinstall the drivers, but I can't because Windows recognizes it as an unknown device, (code 43), so they won't install. I have tried using the unbrick utility, but it doesn't work since windows isn't recognizing the device. I have a mac too that won't recognize it, at least I don't think it does. Maybe there is a way to get the drivers installed I am missing, but I tried following all of the tutorials here, and its not wokring. Is it possible that I can still fix it, or is it done. Thanks for any help."
Now I want your opinions on what to do. The top touch screen is not recognizing and is NOT like before, touch screen is hardly reading. I don't know if this is software, but another thing is after turning it on each time the Kindle Fire Logo flashes 1once, goes black for about 3 seconds and flashes again before booting up.
Anybody have any suggestions.
Click to expand...
Click to collapse
Like I said on your other question thread you put in the Development section, questions go in Q&A. People there will answer your questions. If you put it in development, no one will answer because it's the wrong thread.

Related

[Q] Might be bricked.

I rooted my fire a couple weeks ago. Used the KFU and everything worked perfectly. I have the android marketplace. I even downloaded the OTA something that allows you to temporally disable so I can still watch prime videos.
But tonight it powered off on its own and got stuck on the yellow triangle screen. I tried using the KFU and change it to normal boot mode. which seemed to work. It got to the Kindle fire screen and booted up. As soon as the carousel popped up it shutdown immediately and got stuck on the yellow triangle screen. It keeps doing this. Any ideas.
I tried reading many of the other threads, but I got majorly confused. So any help is appreciated. Thanks
edit: I noticed i had a few seconds before it would shutdown on me. I was able to open OTA rootkeeper and turn the root back on before it shutdown. As soon as I click restore root, it shutdown again, but it booted up fine. Im thinking the issue was caused by the root temporally being disabled. Is this a known problem. Seems to be working fine, will update tomorrow.
Edit: seems I have to changed it no normal boot everytime. Is there a way to unroot my fire. Hopefully its not too complicated.
Thanks for anything guys.
And I think the root is disabled at the moment, but not a %100 sure. NOt sure if that matters.
Mine's doing the same thing. I think it has something to do with the new OTA update? Mine will start up then reboot into recovery...any thoughts guys?
I'd start here, since it appears many others had similar problems with the OTA push:
http://forum.xda-developers.com/showthread.php?t=1634075&page=2
Supposedly KFU rooting still works. You may need to try this method again. Check this thread and see what others had to say as far as what worked for them. Good luck!
How do I unroot it completely. Its still getting stuck on yellow triangle. I used it for 30 minutes last night. Now unless I make it boot up normally, it gets stuck. getting frustrated.
Now when I use KFU to start it in normal mode, it gets to the Kindle fire screen, and occasionally the screen where I typed in my code to unlock it and it turns off, black screen, It will only turn on when plugged in.
edit: I guess my battery somehow died overnight. Swear it was full when I went to bed
Would updating my fire with the usb get rid of the root? I just want it back to normal. What is easiest way to do that?
Now its stuck on this cycle where it says theres an error and the kindle fire must reset to its original factory settings its does this. Reboots I think and does it again. Its stuck like this.
To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034
soupmagnet said:
To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034
Click to expand...
Click to collapse
Thanks but I cant get out of the cycle of what I said in my last post. I think my Fire is broken for good.
Can you boot into recovery? Do you know how?
soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I was able to before. My computer doesn't recognize the Kindle anymore
Guess I will be buying a new one.
TURBO1112 said:
I was able to before. My computer doesn't recognize the Kindle anymore
Click to expand...
Click to collapse
Your computer doesn't need to be recognized by the computer to boot into recovery.
soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then <waiting for device>. Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.
fzdolfan said:
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then . Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.
Click to expand...
Click to collapse
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109
soupmagnet said:
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109
Click to expand...
Click to collapse
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.
fzdolfan said:
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.
Click to expand...
Click to collapse
A "factory cable" is specially made to interact with the device in a way that is different from the OEM Motorola USB cable you are currently using. With a little research and a little more reading you'll be able to find out what the difference is and why it works for fixing dead battery issues.
Using the stock charger was one of the very first things covered in the first link that I gave you. I'm trying to help you fix your problem so please try to pay attention to the information I'm giving you.
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375
soupmagnet said:
Using the stock charger was one of the very first things covered in the first link that I gave you.
Click to expand...
Click to collapse
I realize that, and I acknowledged it in my post by stating that it solved the drained battery issue. I also gave thanks on your post.
Accusing me of not paying attention is not necessary.
I only said that I don't see the difference in the factory cable because a) my drained battery was resolved by other means and b) I did read in the factory cable thread that "Seems like you have power and this cable is maininly for when your ... battery is dead and you need to ... fastboot with no battery life left.... So the cable does not matter in your case since your battery has power you can use any usb cable."
soupmagnet said:
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375
Click to expand...
Click to collapse
I also looked at this thread, but the initial post seems to imply that I already know how to "Apply this flash.zip from recovery just like any other ROM or kernel .zip file.", which I do not.
As I said, my fire is currently stuck at the kindle fire logo and does not respond to being plugged in to the PC (other than turning on to the kindle fire screen).
Admittedly, I only went about 4 pages deep into the thread, but it seemed to be all posts of thanks (for the most part) to the original post. I will continue reading the thread if you're saying that it indeed contains more helpful information.
I apologize if my post came across as ignorant or lazy, but the fact is that I've been researching this for the better part of the day, and I see plenty of info on what to do if I can get my PC to communicate with my Fire, but the first problem is that I cannot find out how to hurdle that first very important obstacle.
Just to save us both some time (and I do appreciate your patience and willingness to help), are you saying that I need a factory cable regardless of the state of the battery? Because if that's the case, then my first priority is to figure out how to get one, because my knowledge, means, and experience in soldering and inner workings of electronics is zero, so making one myself is not an option.
Forgive my impatience but playing twenty questions with other, less motivated to learn users, gets kind of old after a while (not to say that you fall into that category). Not to mention, I'm a prick and have very little patience to begin with.
With a good charge on your battery there is no longer a need for a factory cable.
Most of the users here are fairly proficient with the use of recovery so its easy to overlook those who aren't. That's why it's important to know up front what your level of experience is, to avoid such assumptions.
Your recovery (TWRP or CWM) has a mount function for mounting certain partitions as external drives onto your computer. Your computer will recognize it in the same way it does a thumb drive. Use it to mount your sdcard and transfer the FFF1.4 so it can be installed while in recovery.
Once installed, reboot and hold the power button as if you were trying to enter recovery again and you will be able to select which mode to boot with. Choose "Normal Boot".

[Q] Need Some help with a bootloop

Hey guys, I'm not sure how I got my Kindle stuck in a boot loop, but I need some help getting it out. I have this thread http://forum.xda-developers.com/showthread.php?t=1399889 for unbricking. The problem I run into is that for some reason the utility wont show my device at all. In my device manager on my computer it shows the kindle as Amazon with the yellow triangle. I have tried everything I could find to get my computer and thus the utility used in the above thread to pick it up and get it out of the boot loop. In case you need to know the ROM I tried to flash before I had this issue can be found here http://forum.xda-developers.com/showthread.php?t=1614004 .
Exact same issue doesn't connect to computer
Sent from my iPhone using Tapatalk
Bahamutmaester said:
Hey guys, I'm not sure how I got my Kindle stuck in a boot loop, but I need some help getting it out. I have this thread http://forum.xda-developers.com/showthread.php?t=1399889 for unbricking. The problem I run into is that for some reason the utility wont show my device at all. In my device manager on my computer it shows the kindle as Amazon with the yellow triangle. I have tried everything I could find to get my computer and thus the utility used in the above thread to pick it up and get it out of the boot loop. In case you need to know the ROM I tried to flash before I had this issue can be found here http://forum.xda-developers.com/showthread.php?t=1614004 .
Click to expand...
Click to collapse
ncvikingx97 said:
Exact same issue doesn't connect to computer
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
If you are getting stuck at the ROM's bootanimation and it won't go any further, your system software is broken. You'll have to get to recovery or at least into fastboot mode to fix it. If you have the stock bootloader, you have no easy way to get into recovery, so you'll probably need a factory cable. Read this...
http://forum.xda-developers.com/showthread.php?t=1668159
This probably won't hurt either...
http://forum.xda-developers.com/showthread.php?t=1552547
Thanks
Just contacted amazon about getting a new factory cable. Also, as much as I hate to admit it, I could probably use that guide
ncvikingx97 said:
Just contacted amazon about getting a new factory cable. Also, as much as I hate to admit it, I could probably use that guide
Click to expand...
Click to collapse
I hope you are joking...
http://forum.xda-developers.com/showthread.php?t=1550999
didn't work
Okay so I plugged my kindle in with a samsung charger I had, and it turned on when I plugged it in. Now it is plugged in, and it can't get past the kindle fire logo. What should I do? The computer doesn't recognize it either
ncvikingx97 said:
Okay so I plugged my kindle in with a samsung charger I had, and it turned on when I plugged it in. Now it is plugged in, and it can't get past the kindle fire logo. What should I do? The computer doesn't recognize it either
Click to expand...
Click to collapse
Download in use Kindle Fire Utility from the development section. Use it install window driver for KF, install TWRP, and reset boot mode. It is the tool for you. You just need to study how to use it.
Hope it helps.

[Q] Possibly Hard Bricked kindle Fire

Ok I know tons of people think they have bricked their device, but usually it is just a soft brick....hopefully I am the same. I tried to root my kindle fire using KFU. Something happened, it didn't work. Now it just stays on the boot screen. In windows it isn't recognized, I have read the forums and know to reinstall the drivers, but I can't because Windows recognizes it as an unknown device, (code 43), so they won't install. I have tried using the unbrick utility, but it doesn't work since windows isn't recognizing the device. I have a mac too that won't recognize it, at least I don't think it does. Maybe there is a way to get the drivers installed I am missing, but I tried following all of the tutorials here, and its not wokring. Is it possible that I can still fix it, or is it done. Thanks for any help.
DIRKxxxDIGGLER said:
Ok I know tons of people think they have bricked their device, but usually it is just a soft brick....hopefully I am the same. I tried to root my kindle fire using KFU. Something happened, it didn't work. Now it just stays on the boot screen. In windows it isn't recognized, I have read the forums and know to reinstall the drivers, but I can't because Windows recognizes it as an unknown device, (code 43), so they won't install. I have tried using the unbrick utility, but it doesn't work since windows isn't recognizing the device. I have a mac too that won't recognize it, at least I don't think it does. Maybe there is a way to get the drivers installed I am missing, but I tried following all of the tutorials here, and its not wokring. Is it possible that I can still fix it, or is it done. Thanks for any help.
Click to expand...
Click to collapse
Is it a 1st Gen Kindle Fire or 2nd? If it's a 2nd Gen you "might" be in trouble
Sent from my Fire Kindling A-Pad
guitarman2010 said:
Is it a 1st Gen Kindle Fire or 2nd? If it's a 2nd Gen you "might" be in trouble
Sent from my Fire Kindling A-Pad
Click to expand...
Click to collapse
Its first generation...
DIRKxxxDIGGLER said:
Its first generation...
Click to expand...
Click to collapse
In most cases I've seen of Windows complaining of an unknown device, it seems to be a problem with the bootloader. The fact that you can't even get it to accept commands from the Mac leads me to believe it is the same in your case.
You'll likely need to put the device in USBboot ("shorting trick") and install a working bootloader with Firekit.
"That's a special kind of stupid. The kind that makes me laugh."
What Soup said will work. This is what I did, as I was having the same problem as you.
1. Turn off your KF
2. peel off back cover from KF.
3. Make sure the A side of the usb cable is plugged in to your PC.
4. Find the short spot and put something there like a small screw driver point or a paper clip.
Here's a link to the picture. http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
5. While you have your metal on the short spot turn on the KF.
6. After about 20 seconds or so Windows will now recognize it. Use KFU to put it in recovery mode, installing Fire, ETC.
Thanks guys, I'll try that when I get home from work today and report back.
Sent from my SAMSUNG-SGH-I747 using xda premium
Thanks for your help, it's up and working now with stock kernel and rom. Really appreciate your help!
Sent from my SAMSUNG-SGH-I747 using xda premium
Relikk356 said:
What Soup said will work. This is what I did, as I was having the same problem as you.
1. Turn off your KF
2. peel off back cover from KF.
3. Make sure the A side of the usb cable is plugged in to your PC.
4. Find the short spot and put something there like a small screw driver point or a paper clip.
Here's a link to the picture. http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
5. While you have your metal on the short spot turn on the KF.
6. After about 20 seconds or so Windows will now recognize it. Use KFU to put it in recovery mode, installing Fire, ETC.
Click to expand...
Click to collapse
I having the same problem but for Kindle fire hd 7". I tried to use both stock cable and factory cable but it didn't work anyway. Any solution? please help me. Thank you

[Q] Help! black screen and 0x5003

Hi everyone,
as recommended I read all the guide of Kindle Fire for Beginners and looked around other topics of the forum but I still couldn't solve my problem
I rooted my mother's KF and instaled the jellybeam Rom in it.
Then I tried to do the same in my dad's KF, but something went wrong when I was using the KFU to root the KF.
All I did back then was to plug the kindle in my pc and run the KFU (the drivers were already installed and it was online)
After I installed the permanent root and the TWRP I tried to turn my kindle on but the screen remained black!
the on/off button lights up green but there is nothing in the screen
I turned it on and off several times but nothing appeared
Then I tried to fix it by using the kindle unbrick and flashing the stock version among other options but afterwards the KFU still recognizes the device and the status but the boot status is 0x5003
I looked around in the forum but I couldn't find a solution for my problem
can somebody please help me?
I'm pretty desperate and I think I might have screwed up my father's KF =/
sorry If I made some writing mistakes because inglish is not my mother tongue.
avshimanoe said:
Hi everyone,
as recommended I read all the guide of Kindle Fire for Beginners and looked around other topics of the forum but I still couldn't solve my problem
I rooted my mother's KF and instaled the jellybeam Rom in it.
Then I tried to do the same in my dad's KF, but something went wrong when I was using the KFU to root the KF.
All I did back then was to plug the kindle in my pc and run the KFU (the drivers were already installed and it was online)
After I installed the permanent root and the TWRP I tried to turn my kindle on but the screen remained black!
the on/off button lights up green but there is nothing in the screen
I turned it on and off several times but nothing appeared
Then I tried to fix it by using the kindle unbrick and flashing the stock version among other options but afterwards the KFU still recognizes the device and the status but the boot status is 0x5003
I looked around in the forum but I couldn't find a solution for my problem
can somebody please help me?
I'm pretty desperate and I think I might have screwed up my father's KF =/
sorry If I made some writing mistakes because inglish is not my mother tongue.
Click to expand...
Click to collapse
That's interesting. You may want to start with a Linux liveUSB and run Firekit.

[Q] Go right to factory cable if having problems?

So I picked up a refurbished Kindle Fire 1st Gen for dirt cheap. Tried to root with KFU 0.99. It downloaded the necessary files, and said it would reboot the device, which it did, then got stuck in Fastboot. I have read this forum for about an hour straight and it looks like my best option is to get a factory cable and save myself hours of trying things. Most of the suggestions I find are way out of date, so I'm not sure what the CURRENT recommended suggestions are to fix this problem.
I can't get the Kindle Fire to show in Device Manager since it has been stuck in Fastboot mode. It just shows as "unknown device" in the USB section, even after uninstalling old drivers and reinstalling the ones with KFU, rebooting, etc. Should I just order a factory cable, or does anyone have suggestions for up-to-date things to try? (Today is 6/7/2013) Or will a factory cable not even work if I can't get the device to register in Device Manager anymore?
I have probably rooted 30 devices from Apple TVs to Android tablets and phones. This is the first problem I've ever run into!
Any suggestions are much appreciated. Thank you!
Something similar happened to me. I used KFU and then the Kindle got stuck in the logo screen. I reinstalled the drivers on a different computer and plugged in the Kindle. I just reset the boot mode and it worked fine.
Sent from my XT907 using xda premium
notdeadyet01 said:
Something similar happened to me. I used KFU and then the Kindle got stuck in the logo screen. I reinstalled the drivers on a different computer and plugged in the Kindle. I just reset the boot mode and it worked fine.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
Thanks, that works for me. :victory:

Categories

Resources