yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] sturmer:
Greetings , i tried to install CM 10.2 using the official CM tutorial and heimdall , but the install failed in an endless CWM boot loop (i have tried to install the CM10.2 .rom using the CWM but every time I have ended in boot loop.After few trys i decided to revert back to stock.

but here is the problem , after using this tutorial

http://xdaforums.com/showthread.php?t=2247484

to try to revert to stock using ODIN ... and i got the mobile bac online booting to the main setup screen -BUT

as soon as i try to touch the next button the mobile spits out list of crashed applications , (Aplication google services framwork( proces com.google.process.gapps ) unexpectedly quit -force quit ...this is only one of the long list of errors that pop out.

but the strange part is that i have chosen the factory reset, cache reset before i have even tried to install CM ,and mobile after i push on few times to hard quit and enter the normal operation spits out the lock screen picture that was before (custom picture taken by the phone prior to attempt to flash), then i noticed that mobile phone defaults to Croatian language ...this is strange as the rom should be English,and one more thing, now when i try to open SDCARD -i cant it is not mountable ( not by pc choosing the MOUNT option in CWM )nor by CWM.

If i copy the CM rom file to the internal memory i can't install the CM with error Install fail (BAD)

Can anyone give me idea what to do next? How to do full clean install of custom rom?how to return to stock or any rom ....?

Sorry for my bad English
[Galaxy S I9000 Q&A, Help & Troubleshooting] sturmer:
Any idea what to do?

No solutions?
[Galaxy S I9000 Q&A, Help & Troubleshooting] sturmer:
BUMP ?:confused:
[Galaxy S I9000 Q&A, Help & Troubleshooting] freakymod2120:
Look here hope it can help you...

http://xdaforums.com/showthread.php?t=2444308
[LG Optimus L9 P760, P765, P768, P769] rashq:
I tried to update to JB v20b Ind form V20a. I was rooted with cwm . so after downloading 38 mb data it asked to reboot for update . but as cwm was there so it didnt go to stock recovery. now whatever am doing its coming back to CWM. if i flash another rom also and reboot again back to CWM . cant do anything . please help.
[LG Optimus L9 P760, P765, P768, P769] rashq:
Please any1
[LG Optimus L9 P760, P765, P768, P769] mrmathematica:
a) OTA update doesn't work with CWM. That's the reason you get stuck at first place.

b) What do you mean by "flash another rom also and reboot again back to CWM". Did you offline flash KDZ file, factory reset and it still go back to CWM? That is impossible as offline flash KDZ will definitely destroy CWM.

c) Be patient. People come here to help, but it take time.
[LG Optimus L9 P760, P765, P768, P769] rashq:
Flashing other rom means i have few roms on ext sd. slimbean and cm . after flashing when i reboot it comes back to CWM .

I am not able to do offline KDZ flash as it is not able to detect phone.

Trying with LG mobile support tool now.
[LG Optimus L9 P760, P765, P768, P769] teddybalan:
Had the same thing. Look up LG Mobile support tool. It will update your phone to the latest software version. Of course you will lose all data & root.
[LG Optimus L9 P760, P765, P768, P769] rashq:
Finally got it working via lg mobile support tool.

Just out of curiosity what might have happened that system was not going beyond CWM.

Also what if i had the latest version of JB, still lg mobile support tool would have worked ??
[LG Optimus L9 P760, P765, P768, P769] kuma82:
A faster fix what have been doing the following

http://xdaforums.com/showpost.php?p=44814547&postcount=13

CM 10.1 P769
[LG Optimus L9 P760, P765, P768, P769] rashq:
Great , now i can again start experimenting :p

Thanks for the quick solution.

Next time for sure. But i hope not to repeat the same mistake :p
[LG Optimus L9 P760, P765, P768, P769] rashq:
[MENTION=4447066]kuma82[/MENTION] Is there any way to remove CWM. Yesterday i searched but couldnt find any. Some said using rom manager but p765 is not supported by rom manager only p760 ( oficially)
[LG Optimus L9 P760, P765, P768, P769] kuma82:
twrp by Lelus for your model number.

You can use nandroid manger to install it or use that zip I made to flash it with cwm. If you use my zip rename twrp.img to 3-recovery.img

CM 10.1 P769
[Galaxy S 4 Q&A, Help & Troubleshooting] galaxiasS4:
I bought a Galaxy S4 i9505, and update it to the latest firmware 4.2.2. After 7 days of usage, some green and black dots appear in the screen and they are blinking randomly on the screen (Please see the attached screenshot. The site uploaded the images in very low resolution and think the dots cannot be seen).

I think is a software problem, because it also appears in the screenshots.

Did anyone see this problem before?:confused:

P.S. I have already done a factory reset but the green dots problem still remained
[Galaxy S 4 Q&A, Help & Troubleshooting] Tunestwo:
I think that u have Deadpixels. Try a pixel test from the app store.
[Galaxy S 4 Q&A, Help & Troubleshooting] galaxiasS4:
Thank you for your quick response. I don't think they are dead pixels because they are appearing in the screenshots. If they were dead pixels they will not be able to appear in the screenshots because this is a hardware problem. Isn't it?

i.e Think about your computer and PrinScreen Button. If you have a dead pixel on your monitor it never appears in the print screen picture.

Also, these dots are randomly produced anywhere and they are blinking all the time.:confused:
[Galaxy S 4 Q&A, Help & Troubleshooting] Tunestwo:
Yep that was a derp reaction of me....sorry can't help u further. Did u tried flashing a rom?
[Galaxy S 4 Q&A, Help & Troubleshooting] OSiRiSNZ:
Hi there,

I have the exact same problem currently running 4.3 XXUEMI8, however it has been a problem since I bought the phone brand new from stock.

Refer to screen shot attached, where the pixels are clearly visible at 1:1 zoom.

The green and red pixels are also very visible when viewing YouTube videos or anywhere that is displayed as solid BLACK or WHITE.

Did you ever find a resolution?

Here is a link to a full resolution image (XDA image uploader masks the pixels on resize): osiris-developments.co.nz/temp/Screenshot_2013-10-09-15-59-39.png
[Galaxy S 4 Q&A, Help & Troubleshooting] galaxiasS4:
:(:(:( ohh! I am so sorry about that. Exactly the same problem. Also, when I took pictures, they were fine, but when I made video calls, I saw the dots to my pc screen. I thought is like a VGA problem. If so, the damage is very huge, and maybe the motherboard needs to be replaced.

I didn't find any solution, so I sent the phone for a repair. A month passed, no news yet. I suggest you to return the phone as soon as possible!!

When I have news, I will write back to you.
[Galaxy S 4 Q&A, Help & Troubleshooting] OSiRiSNZ:
Just to follow up on this, phone was replaced under warranty. Samsung did not specify what exactly was repaired, however it was turned around in about 3 working days.

I have since moved to the G900F anyway :cool:
[MDA II, XDA II, 2060 General] longshanks:
Can you access the XDA2i internal ROM?

We support users who have and XDAIIi. Our application is a Java app that runs within the IBM J9 VM - both are installed on the internal flash memory.

The problem we have is that on a number of cases the users have let the backup battery go flat and then everything is installed from scratch. The shortcut in the program file directory of course is not installed from hardware reset and therefore we get a great deal of grief from the users.

Has anyone been able to access the XDA2i ROM?
[Kindle Fire 2 Android Development] kurohyou:
This guide is a work in progress.

Please be patient as I work on completing this guide, as I work full time and am a full time student.

You can find the original discussion thread for this topic here!

DISCLAIMER: I am not responsible for any damage to yourself, your Kindle, or other property incurred by following any or all parts of this guide. Proceed at your own risk.

WARNING: Do not attempt to follow this guide unless you are fairly familiar with soldering and Linux commands. Serious harm to yourself, your Kindle, and/or your computer can result if you are not careful.

Q. What devices will this work on?

A. This how-to works for the Kindle Fire 2 only. (There are other methods of restoring a bricked original Kindle Fire; refer to the FAQ for that device)

Q. Why won't this work for KFHD7"/8.9"?

A. The motherboard designs for the KFHDs are different. That means that the entire process of finding all the solder points for those motherboards (including desoldering the e-MMC) has to be repeated before the same method for fixing hard-bricks on them can be used. (Note: If you have a hard-bricked or otherwise broken KFHD7"/8.9" that you'd be willing to donate for this endeavor, please PM me)

Q. Under what circumstance does will this guide help?

A. This guide is intended to restore the KF2 that was previously thought to be beyond restoring, or hard-bricked, as a result of flashing the incorrect image to your ROM. This means a KF2 that does not display anything on the screen and does not light up the power LED when the power button is pressed (i.e. it appears dead even after charging). If your KF2 still shows signs of life but is not working, please try one of the other methods of repairing it. Might I suggest Q16-23 of the FAQ?

Q. Is there any way to do this without all the soldering?

A. At this time, no; however, I am in the process of developing a device to do this that does not require soldering.

Q. I don't feel comfortable doing this myself. Can I have you fix it for me?

A. Send me a PM and we'll work out the details.

Required materials:

Hard-bricked Kindle Fire 2

USB SD card reader (one with only one slot, NOT the multi-card readers)*

30 AWG wire (I found mine at Radioshack)

solder (the smaller the diameter, the better)

soldering iron (pencil iron will work, but soldering station is better)

plastic opening tools

a small Phillips screwdriver (mine came with my plastic opening tool kit)

a computer with Linux (a live CD of a distro should theoretically work, but I used an installed copy of Ubuntu 13.04)

*For cheap card readers near me (literally three blocks up the road), I found this one from Microcenter and this one from Tigerdirect. Go with whatever is cheapest for you.​

Suggested materials:

Helping hands tool

A good light source

Magnifying glass/magnifying visor (I used a x7 magnifying glass with built-in light)

Desoldering pump/wick (in case you mess something up, need to desolder the SD card reader, or want to clean up your board after you're done)

Lots of patience​
[Kindle Fire 2 Android Development] kurohyou:
Preparing the motherboard

Warning: Take care to protect sensitive electrical components (like the ones found on your KF2) from ESD.

1. Remove the motherboard from the Kindle. If you need directions on how to do that, please refer to ifixit (stop at step 8). Note: You do not need to remove the battery from the case.

2. Take a moment and familiarize yourself with the layout of the motherboard.(Solder points are marked. Keep these images handy for reference)

Front:

(Click for larger image)

This is just an FYI (not required to do this): When you first take out the motherboard, the e-MMC will be covered by a piece of grey foam. Underneath that is a sticker that covers the chip information.​

Back:

(Click for larger image)

Note: For CMD and DAT1, you will be soldering to the marked leads of the SMD components. All other soldering will be to the marked copper pads.​

3. Place it to the side in a safe location
[Kindle Fire 2 Android Development] kurohyou:
Preparing the SD card reader

There are a few different variations when it comes to SD card readers. In addition to through-hole vs. SMD, there may be variation in the location of the card-detect switch pins. All other pins (DAT0-3, Vcc, GND, CMD, and CLK) will always have the same location relative to each other.

Examples:

SMD with card detect switch at the top

Through-hole with card detect switch in the middle (Front) (card connector removed)

Through-hole with card detect switch in the middle (Back)​

1. Remove your reader from the package.

It should look something like this:

​

2. Remove the plastic housing and any metal shielding from the SD card connector.

You're left with this:

​

3.There are two ways to proceed from here: (a) For through-hole, use the pads (b)For through-hole or SMD, solder directly to the connector pins.

4. (a) Carefully desolder all the pins from the card connector. (b) Skip this step.

5. Cut your wire. You will need 10 pieces. 9 of them need to be long enough to get from the MB to the card reader (I went with about 6-8 inches) with 6 of them the same length (for DAT0-1, CMD, and CLK to minimize chance of signals arriving at different times). The last wire should be long enough to jump the card detect switch (CD_SW) to ground (GND).

6. Carefully strip about 0.5-1 cm of the insulation each end of all the wires.

7. (Refer to example images at beginning of post) Take your small wire and jump CD_SW to GND by (a) placing the wire through CD_SW and GND and soldering or (b) soldering one end of the wire to the CD_SW connector pin and the other to a GND connector pin.

8. (Refer to example images at beginning of post) Take your 6 wires of equal length and solder one each to DAT0-3, CMD, and CLK (a) through the hole or (b) to the card connector pins.

9. (Refer to example images at beginning of post) Take one of the remaining wires and solder it to GND by (a) or (b) as above.

10. (Refer to example images at beginning of post) Take your last two remaining wires and twist one end of the exposed wire together. Solder this end to Vcc by (a) or (b) as above. These will be used to connect to Vcc and VccQ on the motherboard.

11. Your finished product should look something like this (for a):

Front:

Back:

​
[Kindle Fire 2 Android Development] kurohyou:
(Blank)
[Kindle Fire 2 Android Development] kurohyou:
Connecting it all together

Soldering to the copper pads is tricky. The solder doesn't like to stick, and when it does, you have to be very careful not to move the wire until it cools. Also, if you have to attempt to solder the same pad more than once, lacquer tends to build up. Keep something handy (like tweezers) to scrape it off if it gets in the way

Reference photos:

Front:

(Click for larger image)

Back:

(Click for larger image)

Card reader:

​

1. Solder the wire from the card reader to the corresponding pads as marked in the images above. Using the helping hands tool to hold the board and the reader makes things much easier. It's probably easiest if you solder DAT0 on the front first, then turn the board over and with audio jack, etc. on the left, solder each spot from top to bottom, left to right. Note: Solder one Vcc wire from the card reader to one Vcc pad on the board and the other to VccQ.

Once finished, it should look like this:

​
[Kindle Fire 2 Android Development] dc_nc123:
Next Step?

Wanna try this with my bricked kf 2nd gen. But I need to research more on it first...

On what state will the tablet be when you plug in the finished product to the computer?

can you please put the next steps ?

Thanks!
[Kindle Fire 2 Android Development] mode_ss:
What's next??

Hello there... I was reading your steps to repair my dead KF2 on your post... and I noticed you said on the requirements that we need a Linux PC, preferably with Ubuntu, to proceed... but There are no more steps after you show how to solder.

Can you tell me, please, What's next? What happens when I connect the logic board with the soldered wires to the SD adapter, to the linux PC? how do I revive it?

Please, help me... I want to give that Kindle as a gift to someone on my church who needs it, And I want to try to fix it!!

Thanks for your time and sharing your knowledge. God bless you.

-----
[Kindle Fire 2 Android Development] stunts513:
Once you have a Linux PC up and running or even just a Ubuntu live is will do, download the boot loader for your kindle, I don't have links at the moment, but one place you can get it is download the latest official update for your device from Amazon's support section, I am pretty sure Linux should automatically recognize it as a zip file even though it ends in .bin, if not just changes the end to .zip. Extract the file called u-boot.bin to wherever you find convenient, for my convenience I will say extract to the home folder( the terminals default to that directory so it makes things simpler). Now plug in the USB adapter you have soldered to the kindle. If it mounts anything I suggest unmounting it just to be on the over protective side. You will now need to determine the device path that is given to the kindles emmc, easiest way is to check in gparted or disks, or by running the mount command from a terminal if you haven't yet unmounted the other partitions and know what you are looking for. Once it has been determined you should run a command similar to this in a terminal:

sudo dd bs=1 if=u-boot.bin of=/dev/sdb2

take note to replace sdb2 with the device name your PC assigned to the device, but remember to leave the 2 so it only flashes that to the second partition instead of over the entire emmc. Once you run this and it succeeds, you should eject the device or just shut the PC down, disconnect your wires and try powering on the kindle. [MENTION=5378103]kurohyou[/MENTION] did I leave anything important out? I will probably make this formatted better later on when I am actually on a PC.
[Kindle Fire 2 Android Development] kurohyou:
Looks good to me. The semester is almost over and someone is sending me a KF2 to fix, so once it arrives, I'll go through and take screenshots of the process and finish up the guide. At that time, I'll ask the mods to clean up this topic (delete posts) so it flows well.
[Kindle Fire 2 Android Development] bournezhang:
super！

but if you know how the AMAZON lab126 guys fix it you will know it‘s very easy

y.
[Kindle Fire 2 Android Development] stunts513:
Yes but they have signed files we don't have access to that are necessary for reflashing it with usbboot/aboot or w/e that utility is called.
[Kindle Fire 2 Android Development] xanthian23:
Has anyone managed to write up a walk through on exactly what to do once you've gotten the board soldered up and ready to go? I have Linux up and running, and the soldering shouldn't take more than 20 minutes, but I'm holding off on doing this until I know I can do the software side of things. I am a complete noob with linux, and don't want to make things worse by making a mistake. Part of me really wants to try this out but not knowing what to do after I'm wired up keeps me from trying this.
[Kindle Fire 2 Android Development] overlode:
Bit of an interesting one if anyone could try and shed some light onto it. Connect everything up as usual but with VccQ every time it is connected something must short and fries the SD card reader, without VccQ connected the light on the SD card adaptor flashes continually but it's not recognised by Ubuntu.
[Kindle Fire 2 Android Development] mbwf:
Thank you!

:D:DI just wanted to drop by and say a HUGE thank you to [MENTION=5378103]kurohyou[/MENTION] for starting this thread and for all who have contributed to it :)

BEFORE I CONTINUE, PLEASE BE MINDFUL THAT THE PARTITION NUMBER/DESIGNATION BEING SHOWN AND WRITTEN TO IN THIS THREAD, BY MYSELF AND OTHER PEOPLE, WILL NOT NECESSARILY BE THE SAME WHEN YOU CONNECT YOUR KINDLE eMMC TO YOUR SD CARD READER AND FLASH THE CORRECT BOOTLOADER, TO DE-BRICK IT. LINUX ASSIGNS DIFFERENT PARTITION NODES BASED ON VARIOUS CRITERIA, SO YOU MUST ALWAYS ENSURE YOU ARE "dd'ing" TO THE CORRECT PARTITION, OTHERWISE YOU COULD BE WRITING TO *ANY* DEVICE ON YOUR PC, POSSIBLY YOUR MULTIPLE TERABYTE FAMILY PHOTO ARCHIVE... ARGH! DO *ALWAYS* ENSURE YOU ARE WRITING TO A 256KB PARTITION - REFER TO MY PHOTOS, BELOW; THEY SHOW A PARTITION LISTING AND WHERE THE BOOTLOADER PARTITION IS, AND IN WHICH ORDER THE PARTITIONS ARE.

I bought a pristine, boxed *DEMO* Kindle (2? Gen 2? "Otter2" anyway the 7" one, 600x1024) from eBay for just £6.99, and when I tried to flash the bootloader with my fastboot cable, as soon as I rebooted... it DIED. Being a long time qualified electronics engineer, this kind of disassembley is all part of life for me, and doesn't phase me one iota, but the soldering of wires is a VERY precise and delicate operation -

PROCEED VERY VERY SLOWLY, DOUBLE CHECK AND THEN AGAIN, ALL YOUR PIN DESIGNATIONS AND SOLDER JOINTS OR THERE'LL BE TEARS BEFORE BEDTIME!

Anyhow, I simply booted into 32 bit Ubuntu (I have a huge repository of ISOs to hand, so that was no big deal, and bash commands I can do in my sleep) so I flashed the bootloader to the relevant

unmounted

partition [MENTION=319375]mohibr[/MENTION] attached to this post: http://xdaforums.com/showpost.php?p=49549083&postcount=13

... using "dd" command, et VOILA! it works! (I knew it would, this is hardly rocket science, but still an extremely joyful moment to behold, seeing my less-than-one-day-old KF revived!)

I'm rather too tired to expand thoroughly on all the details, but if anyone needs any help, let me know soon before this whole episode is lost and forgotten (you've no idea HOW much of this kind of thing I do weekly, to myriad devices).

Here's my witness photos - please feel free to add me to the testimonys of people who took their time and revived their KF(2? not sure that it's a "2", just that it's a later version using "otter2", whatever that pertains to.)

Photos---> https://www.flickr.com/photos/22008695@N03/albums/72157660358184524

Thank you so much, and God bless you all and have a lovely Christmas :)

Matthew.
[Kindle Fire 2 Android Development] Vaynok:
Vcc location on mobo?

Trying to find a Vcc point on the fire gen2 mobo. multimeter took a crap and im getting scary readings. anyone have a picture of location so i can short to ground. My gen2 is currently stuck at "boot, then blackscreen". its not a loop and windows doesnt recognize the device at all.

Any pictures of the location would be greatly appreciated. ciao.

On a side note, i apologize for reviving this thread. I accidentally flashed a zipped boot image to my kindle. its been sitting for a few weeks. just finally ordered a fastboot cable.
[Testing] vbarthel:
Do you want to be part of something new, something unusual? Let me introduce you to "Chase Whisply", an augmented reality game. My friend and I, two computer science students, have been working on this open source project since early July. And we are glad to annnouce the beta 2.0.

"Chase Whisply" turns your smartphone into a gun sight that can reveal ghosts living around you. Your goal is to find them and hunt them! We use Google Play Game Services to provide leaderboards and achievements, and a player profile keeps track of your progress.

Since we are still students, we can't really compete with a game studio. That is not a valid excuse to provide poor quality content, however. Please help us improving the content of "Chase Whisply" by testing our application from the XDA Android App Tester Google Plus Community.

Be sure that we will appreciate every single feedback, especially on the concept.

From France, with love !
[Testing] Madaditya:
You will get help,but make sure you don't use Xdaer's juz for your testings!

Coz beta testing of apps is somewhat aways from xda's rules!

#no offence

Well wherz the link to your project/app?
[Testing] inaqi69:
Where to download?
[Testing] vbarthel:
Hi! I tried to follow the rules of the Google Plus XDA Android App Tester Community, a moderator posted a thread on the community where you can find a link to the beta =) Unfortunately I am a new user, I can't post outside link in my messages. I will try to contact a moderator of the G+ Community to give you a direct link.
[Testing] martinusbe:
Link to the google play beta --> Here

Xda Beta testing community --> Here

Installing to give it a look now ;)