Database Develop

xp wont recognize tilt unless its connected for ~15mins then disconnects after a few.

This is really weird. I plug my tilt into my computer (tried every USB port on the machine) and it does nothing. The tilt doesnt light up, the computer doesnt notice that anythings been plugged in. Then about 15 minutes later you get the 'bipbipbip' sound that somethings been plugged in and activesync opens and it tries to connect but can not, then after a few minutes of trying I get an error about nothing being connected and you hear disconnect sound xp makes when you remove something form the usb port. Tired reseting both the phone and pc with no change in behavior.
Any ideas?
I've tried the USB-PC switch which did not work.
-Josh

slowjett said:
This is really weird. I plug my tilt into my computer (tried every USB port on the machine) and it does nothing. The tilt doesnt light up, the computer doesnt notice that anythings been plugged in. Then about 15 minutes later you get the 'bipbipbip' sound that somethings been plugged in and activesync opens and it tries to connect but can not, then after a few minutes of trying I get an error about nothing being connected and you hear disconnect sound xp makes when you remove something form the usb port. Tired reseting both the phone and pc with no change in behavior.
Any ideas?
I've tried the USB-PC switch which did not work.
-Josh
Click to expand...
Click to collapse
it seems you're having the same problem I do ( http://forum.xda-developers.com/showthread.php?t=397840 )
USB to PC isn't working here too
I don't know if it's related, but I'm using L26 ROM. Are you using the original ROM?

Lem0nHead said:
it seems you're having the same problem I do ( http://forum.xda-developers.com/showthread.php?t=397840 )
USB to PC isn't working here too
I don't know if it's related, but I'm using L26 ROM. Are you using the original ROM?
Click to expand...
Click to collapse
yes original rom. I got it to sync over BT. Still not making me happy though.

Have you tried /Connections/USB to PC: disable advanced network functionality ?

Yes I have tried that with no difference.
But oddly enough its working now after I plugged the usb into the combo adapter I just got... now it works without it. Maybe it re-aligned a pin or something?
{
"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"
}

slowjett said:
Yes I have tried that with no difference.
But oddly enough its working now after I plugged the usb into the combo adapter I just got... now it works without it. Maybe it re-aligned a pin or something?
Click to expand...
Click to collapse
hello
the problem keeps happening to me
don't you remember changing any other setting in the mean time?
do you use wisbar?
thanks

I think theres a batch of dodgy kaiser/tilts going round. My USB recently suffered many of the problems listed here and all over the forum. Won't connect to activesync, charges but nothing else, stuck in serial at bootloader. Tried on many pc's with many different cables, advanced USB functionality on/off, original SPL, the list goes on and on. I noticed one thing tho, the USB connector on my broken kaiser (O2 XDA stellar btw) looked different to my mates stellar. Mine had 5 holes on the front of it that lined up with the pins on the top. The one they sent me after i returned it doesn't have these holes and looks like my mates one. Ill try and get a pic of the difference.
Does yours have holes or no holes?
1st pic - with holes
2nd pic - no holes

Shub-Niggurath said:
I think theres a batch of dodgy kaiser/tilts going round. My USB recently suffered many of the problems listed here and all over the forum. Won't connect to activesync, charges but nothing else, stuck in serial at bootloader. Tried on many pc's with many different cables, advanced USB functionality on/off, original SPL, the list goes on and on. I noticed one thing tho, the USB connector on my broken kaiser (O2 XDA stellar btw) looked different to my mates stellar. Mine had 5 holes on the front of it that lined up with the pins on the top. The one they sent me after i returned it doesn't have these holes and looks like my mates one. Ill try and get a pic of the difference.
Does yours have holes or no holes?
1st pic - with holes
2nd pic - no holes
Click to expand...
Click to collapse
no holes
but it's weird because it used to work
it stopped from nothing

I guess the holes aren't it then. Mine just stopped too, nothing changed, just didn't work one day. Does yours get recognised by windows at all? Mine kept saying usb device not recognised. This was after it was plugged in for about 15 mins or so. Incidentally, my bluetooth also stopped working at the same time.

Shub-Niggurath said:
I guess the holes aren't it then. Mine just stopped too, nothing changed, just didn't work one day. Does yours get recognised by windows at all? Mine kept saying usb device not recognised. This was after it was plugged in for about 15 mins or so. Incidentally, my bluetooth also stopped working at the same time.
Click to expand...
Click to collapse
mine doesn't even says it's a not recognized device
it just doesn't really recognize anything
I mean, it's the same as if I didn't plug anything in the USB... it shows no message, do nothing
(and tytn doesn't charge... I guess you're at least charging)

Lem0nHead said:
hello
the problem keeps happening to me
don't you remember changing any other setting in the mean time?
No. But i did get it to sync over BT before it happened.
do you use wisbar?
Click to expand...
Click to collapse
Nope, using Quickmenu 2.7 or whatever its called. Great app.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

USB device not recognized

All of a sudden I started getting this error when plugging into my PC.
I booted into the bootloader (tricolor screen) and still didn't work. It charges but doesn't connect properly.
I have searched around and read a few things (disable advanced networking, take out battery for 30 mins) Nothing seems to work.
Seems like it's a device problem... any suggestions because I'm kind of screwed here.

gilligan8 said:
All of a sudden I started getting this error when plugging into my PC.
I booted into the bootloader (tricolor screen) and still didn't work. It charges but doesn't connect properly.
I have searched around and read a few things (disable advanced networking, take out battery for 30 mins) Nothing seems to work.
Seems like it's a device problem... any suggestions because I'm kind of screwed here.
Click to expand...
Click to collapse
Hit up htcwiki.com there is a solution there, I had the same problem and it sorted itself out by buying a docking station station. I also use a three adapter (3.5mm head, sync cable and headset)which also works.
If you have the same issue as me chances are that your pda does not charge when connected either.
Hope this helps

No, as stated, mine charges when plugged in... I have a cradle, but it hooks up with the same usb cable so I can't see how that would make it better... it's just essentially an extension isn't it?

Could be a glitch in the phones software, a cable going bad, a plug going bad or a windows problem.
I've gone through a few cables and a dock, something always gets bent or something and it won't sync, I just grab another cable and it works. It's a shame the dock is bad now, it will only charge.

ChumleyEX said:
Could be a glitch in the phones software, a cable going bad, a plug going bad or a windows problem.
I've gone through a few cables and a dock, something always gets bent or something and it won't sync, I just grab another cable and it works. It's a shame the dock is bad now, it will only charge.
Click to expand...
Click to collapse
+1 All of a sudden a few weeks ago, my phone stopped syncing, panic, because I flash a lot . Tried everything, the list of things to try over at htcwiki was edited by me, and nothing worked, until I changed the cable. Voila ! been working ever since.

No good... not working even on another PC with another cable... and it worked before on that setup.

Um you only have troubleshot half of it. Did you say you reset the phone? LOL oh yeah my phone never worked on the original cable. Just because something was cool for one minute doesnt' mean it won't **** up the next.
Hard reset the phone. If that doesnt' work, than you are one step closer to a broken phone.
Have fun lol.

gilligan8 said:
All of a sudden I started getting this error when plugging into my PC.
I booted into the bootloader (tricolor screen) and still didn't work. It charges but doesn't connect properly.
I have searched around and read a few things (disable advanced networking, take out battery for 30 mins) Nothing seems to work.
Seems like it's a device problem... any suggestions because I'm kind of screwed here.
Click to expand...
Click to collapse
Try here it may help ...

Found my problem in the last post (second to last post now )
My 2nd pin (closest to the middle) was laying flat and didn't have the curve the others had.. so it wasn't making contact. I used a caligraphy pen to get under it and pop it back up and now it works... I'm sure I'll have to keep an eye on it but for now it's working.
Hope this helps others that are reading everyone saying "it's the cable" and that isn't your problem
Thanks for all the suggestions, it had to be one of them!

ChumleyEX said:
Could be a glitch in the phones software, a cable going bad, a plug going bad or a windows problem.
I've gone through a few cables and a dock, something always gets bent or something and it won't sync, I just grab another cable and it works. It's a shame the dock is bad now, it will only charge.
Click to expand...
Click to collapse
Like I said, it could be the port. booya

Well, you did mention everything except for solar flares.

denco7 said:
+1 All of a sudden a few weeks ago, my phone stopped syncing, panic, because I flash a lot . Tried everything, the list of things to try over at htcwiki was edited by me, and nothing worked, until I changed the cable. Voila ! been working ever since.
Click to expand...
Click to collapse
Which OS on your comp. are you using Denco? I've been using vista with no problems until now and it's more than funny how this syncing issue has just been popping up all over (most likely from vista updates). First instinct with vista is updates and firewall; killed and accepted every option, still with no dice. I seriously doubt it's the cables since they worked just fine for the last several hundred syncs and now sync problems abound...any help would be appreciated brother

gilligan8 said:
Found my problem in the last post (second to last post now )
My 2nd pin (closest to the middle) was laying flat and didn't have the curve the others had.. so it wasn't making contact. I used a caligraphy pen to get under it and pop it back up and now it works... I'm sure I'll have to keep an eye on it but for now it's working.
Hope this helps others that are reading everyone saying "it's the cable" and that isn't your problem
Thanks for all the suggestions, it had to be one of them!
Click to expand...
Click to collapse
WTF?! That fixed it?

hmmm, I smell something fishy...so many people having issues with connecting at the same time...upgrade to newest devices? This war with Wm and Apple makes me want to get a simple razr; tired of all this bull****

gilligan8 said:
Well, you did mention everything except for solar flares.
Click to expand...
Click to collapse
I kept silent out my internal dignity

{
"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"
}
Everyone knows USB is shielded for solar flares.
GOSH!!!!

kaalgoosy said:
WTF?! That fixed it?
Click to expand...
Click to collapse
Yep... that pin is half of the data (1st pin is ground, last is power and two in the middle are data)... obviously ground and power are working as it charged, but if one of the data lines isn't making contact then the PC is going to be confused because it knows something is there just not getting enough info.

I tried everything, straightened my pins, shut off firewalls and security, I use Windows Xp running with Bootcamp on an iMac. I have never installed service pack 3, because I read that , that was a problem with syncing. Shut off advanced network functionality, everything I could think of.
I had sync'd a thousand times with that cable, and flashed at least one hundred roms. Then one day it just stopped syncing. After pulling my hair out for two days, trying everything, I pulled a new cable out of the overflowing cable draw, fixed, haven't had a problem since. Go figure !

denco7 said:
I tried everything, straightened my pins, shut off firewalls and security, I use Windows Xp running with Bootcamp on an iMac. I have never installed service pack 3, because I read that , that was a problem with syncing. Shut off advanced network functionality, everything I could think of.
I had sync'd a thousand times with that cable, and flashed at least one hundred roms. Then one day it just stopped syncing. After pulling my hair out for two days, trying everything, I pulled a new cable out of the overflowing cable draw, fixed, haven't had a problem since. Go figure !
Click to expand...
Click to collapse
HUh, It seems you might be right about a simple cable replacement. My previous cable synced me up for several hundred syncs and just crapped out one day; dug up one of my older cables and it synced just fine and now it just took a dive for charging but not syncing. Guess I'll have to hit Best Buy for a new one. Like you said; go figure. Although I noticed some new gray hairs sprouting from searching and tweaking for fix

Buy online.... Best Buy RAPES you on cables!

[Q] Stuck in low power (charging) mode, constant reboots

Hi, have a bit of an issue. My sister dropped her GXS in a pool today. she got it out and wiped it and it seemed to work fine (i told her that she should have taken the batt out immediately... she didn't) She went on then the phone died and got stuck in an endless reboot cycle. i opened it up and cleaned it and dried it, looks clean, from what i can tell. the screen shows the little refresh circle in the center, then shows the battery image for a few seconds then repeats the process (if i connect it to a wall charger, the battery image lasts about a second longer but it still restarts). it constantly restarts. and here is the problem, i can get it to download mode, but even in download mode it restarts after 3-4 seconds so i cant flash anything in such a short period. recovery does not work (even if it did i bet it would still restart after 3-4s). it starts doing this as soon as the battery is inserted.
It was running an old nightly of CM9 (about 2-3 months old)
Any help will be greatly appreciated
UPDATE:
Left it out on the sun for a few hours to dry even more off, now shows the galaxy I9000 splash screen and the semaphore kernel logo but it still restarts after 3-4s
UPDATE 2:
Dissasembled it and put it in a jar of rice, not expecting much. Took a look at the motherboard to prepare for the unbrickable mod. Those pads are TINY, i mean really tiny
{
"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"
}
FULL size image here:
http://dl.dropbox.com/u/11992935/2012-09-08 18.32.42.jpg
That HUGE thing on the chip above is the microsd card
So my new questions are, in the original unbrickable thread i dont quite understand the instructions. IS it like in the picture near the enlarged piece numbered 1. that you must resolder the yellow marked resistor to the blue marked pads, or like in number 2. you must remove the resistor and put a wire (drawn grey) like in the picture or do you do first number 1. and then attach the wire to the upper end of the moved resistor and then to the other pad?

Congrats to your sister, looks like she killed her SGS.
Looks like the battery's not the problem, if it reboots when it's unplugged (an almost empty battery -almost empty = already shut down, but reboots for a few seconds- shows at
least unlock screen for me when I turn it on).
If recovery and download mode don't last enough to flash, it's over IMHO. And even if your warranty is still valid, water damage is not covered..

I am starting to consider doing the unbrickable mod, but i dont know whether this is a software or a hardware problem. any way to test that?

quantity rostsrt
total.destroyer said:
I am starting to consider doing the unbrickable mod, but i dont know whether this is a software or a hardware problem. any way to test that?
Click to expand...
Click to collapse
Try to put the phone in a jar of rice for 24H.
After that try to flash a rom using odin.

total.destroyer said:
I am starting to consider doing the unbrickable mod, but i dont know whether this is a software or a hardware problem. any way to test that?
Click to expand...
Click to collapse
I doubt this has anything to do with Unbrickable mode solutions, anyway links to test mode tare on My Android Solutions, link below.
You problem would be most likely due to moisture shorting power and usb ports/contacts

xsenman said:
I doubt this has anything to do with Unbrickable mode solutions, anyway links to test mode tare on My Android Solutions, link below.
You problem would be most likely due to moisture shorting power and usb ports/contacts
Click to expand...
Click to collapse
I went over your list before posting, nothing helped in my situation, and there is no test mode on your list, or maybe i missed it. I cleaned the usb port and it looks clean, the battery contacts are also clean, no obvious damage shows, and the power on button can not be shorted because it is a potted foil membrane and the leading contacts are clean, and the button works otherwise i could not get temporarily in download mode. gonny try and mess about with adb if i can get the phone to be seen.

total.destroyer said:
and there is no test mode on your list, or maybe i missed it.
Click to expand...
Click to collapse
Problem:- Phone completely DEAD, Not Charging and NO response, only this SEC S5PC110 TEST B/D
you can only revive phone using unbrickable mode when phone is totally dead with only this words SEC S5PC110 TEST B/D, that why I said, i am doubtfull you need to use it.

xsenman said:
Problem:- Phone completely DEAD, Not Charging and NO response, only this SEC S5PC110 TEST B/D
you can only revive phone using unbrickable mode when phone is totally dead with only this words SEC S5PC110 TEST B/D, that why I said, i am doubtfull you need to use it.
Click to expand...
Click to collapse
I think i have no other choice, i have tried everything, my only options now are to get it repaired without warranty (probably will cost more than a new gxs off ebay), use it as a paperweight or try to do the unbrickable mod and see if that works.
Is there a possibility that a software error is constantly rebooting the phone or is there a hardware problem? I mean, could a corrupted bootloader constantly reboot the phone, no matter what mode the phone is in, like in download mode is the bootloader still runing in the background? or the kernel?

Good luck if you decide to try. I'm considered extremely good at soldering by many, I have all the proper tools including a top notch soldering station, and moving that 0201 resistor took me like an hour. One of the most difficult things I've ever had to do, and I didn't think it would work in the end. Having two irons and a microscope would have helped a lot but it's not a mod for the faint of heart. That said it saved my phone from some nasty software business.
I really doubt it would solve this problem, since it's water damage it's probably long gone. If you have no possible other option though, there's no harm in trying this.

FjarrKontroll said:
Good luck if you decide to try. I'm considered extremely good at soldering by many, I have all the proper tools including a top notch soldering station, and moving that 0201 resistor took me like an hour. One of the most difficult things I've ever had to do, and I didn't think it would work in the end. Having two irons and a microscope would have helped a lot but it's not a mod for the faint of heart. That said it saved my phone from some nasty software business.
I really doubt it would solve this problem, since it's water damage it's probably long gone. If you have no possible other option though, there's no harm in trying this.
Click to expand...
Click to collapse
I have a friend that does electronics and solders daily so he should be able to do it, but the big question is, is this actual hardware damage from water or a short caused data corruption and the problem is software, because the thing works, the display works, animation works, the buttons work, it only decides to repeat the process every 3-4s (it varies, sometimes it last about 6-7s, especially if i plug it in to charge, or it dies in a second or two). Could water damage it so precisely to do that, or was there a short that caused some data corruption of the rom/bootloader/kernel/whatever that makes it reboot after the boot process encounters that section of bad data, or the memory chip got corrupt. Is there a way to find out, can a log be dumped out while it is booting? my pc does not recognize anything is connected while it does its refresh battery thing, or maybe you need special drivers.

total.destroyer said:
I think i have no other choice, i have tried everything, my only options now are to get it repaired without warranty (probably will cost more than a new gxs off ebay), use it as a paperweight or try to do the unbrickable mod and see if that works.
Is there a possibility that a software error is constantly rebooting the phone or is there a hardware problem? I mean, could a corrupted bootloader constantly reboot the phone, no matter what mode the phone is in, like in download mode is the bootloader still runing in the background? or the kernel?
Click to expand...
Click to collapse
If your phone had no problems and this problem only developed after the water damage it has nothing to do with software and all to do with hardware . I think the Phone reboots due to minute shorts in the hardware ..moisture underneath the chips could be one...you can try heating a few of larger chips...best would be to keep the phone wrapped in tissue and in a pot of rice for a week or so

solved
i see one galaxy s like this before.
the phone boots if after u see a green battery on screeen
1.but u have to connect a strong charger (1 to 2 Amps) or a USB (1 Amp) laptop computer .
2.after connect the phone, u have to wait aprox. 30 sec, if nothing happened u ned to reconect (pull out battery , then insert it back in the same time with usb or charger plug )
3.if the grenn battery appears on screen wait to charge to 50% then press power button but not detach cable or charger
4.after complete boot , u are free to use your phone (ALL THINGS WORKS)

Which test points to short to flash locked device?

On the board I see six test points. The question is if any of these can be shorted to be able to get the device in a mode where it can be flashed despite being OEM locked.

OK, so the test points are below the fingerprint flex cable connector:
{
"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"
}
Here’s roughly how I proceeded:
Made sure that I’m grounded by touching a grounded metal piece in my apartment.
Removed the SIM tray.
Opened the device according to the instructions by Wit Rigs (youtu.be/1VIdpuXSFmI). Separating the top with the screen was quite hard as it is glued.
Popped out the battery flex cable connector, then the fingerprint flex cable connector.
On my laptop (Windows 7 X64) started MiFlash 2016.08.30.0, downloaded from en.miui.com/thread-345974-1-1.html.
Inserted the USB-C cable that came with the phone into the phone. (not yet into the laptop!)
Using a bent and cut staple, I connected the test points, then inserted the USB-C cable into my laptop.
Windows reported that a new device is connected.
Removed the staple, clicked refresh in MiFlash: A device showed up.
Flashed the latest official stock Android One ROM V9.6.10.0, downloaded from en.miui.com/download-353.html:
Initially I got a message that MiFlash cannot receive a “Hello” packet. It turned out that I was too slow. After connecting the device, one only has limited the time to start the flashing. I read elsewhere that it’s 15 seconds.
Success, my A2 boots up again! Now I’m only waiting for thermal paste to arrive in the mail, I will apply that, then close the phone again.

feklee said:
I found the points, and I would like to post a photo, but I can’t because I cannot add attachments to posts.
Click to expand...
Click to collapse
Can you upload the photo else where and provide a link maybe?

Please stop opening new threads for the same issue.
I think this is the third one I have seen now. I'm sure someone will be able to help you but with the phone being as new as it is you may have to wait or figure it out for yourself. I have the phone but have not tried root yet because it's too early in the phones life to be messing around with it. Let the community grow first.
I do hope you made to get it solved though and if so you could document it so we can all learn from it in the future

mauley said:
Please stop opening new threads for the same issue.
Click to expand...
Click to collapse
Coming from Q&A platforms such as StackOverflow, I was assuming it’s better to use separate threads: The other ones are about Magisk on the A2, about clean installing the A2 ROM, and about using a deep flash cable on the A2. Finally being able to upload pictures, I am now fleshing out my earlier posts with details.
Anyhow, I hope that the information can be of help for others!

feklee said:
OK, so the test points are below the fingerprint flex cable connector:
View attachment 4571595
Here’s roughly how I proceeded:
Made sure that I’m grounded by touching a grounded metal piece in my apartment.
Removed the SIM tray.
Opened the device according to the instructions by Wit Rigs (youtu.be/1VIdpuXSFmI). Separating the top with the screen was quite hard as it is glued.
Popped out the battery flex cable connector, then the fingerprint flex cable connector.
On my laptop (Windows 7 X64) started MiFlash 2016.08.30.0, downloaded from en.miui.com/thread-345974-1-1.html.
Inserted the USB-C cable that came with the phone into the phone. (not yet into the laptop!)
Using a bent and cut staple, I connected the test points, then inserted the USB-C cable into my laptop.
Windows reported that a new device is connected.
Removed the staple, clicked refresh in MiFlash: A device showed up.
Flashed the latest official stock Android One ROM V9.6.10.0, downloaded from en.miui.com/download-353.html:
View attachment 4571596
Initially I got a message that MiFlash cannot receive a “Hello” packet. It turned out that I was too slow. After connecting the device, one only has limited the time to start the flashing. I read elsewhere that it’s 15 seconds.
Success, my A2 boots up again! Now I’m only waiting for thermal paste to arrive in the mail, I will apply that, then close the phone again.
Click to expand...
Click to collapse
I bought a Mi A2 and tried to put android pie on it, but I failed successfully. I'm gonna try this endpoint method, cause I cant flash images with fastboot.
Unfortunately I can only try this on Monday, cause I don't have the tools, but a friend in college has. I wanna know a few stuff for the grand day:
You told that the device is glued. Is it really hard to open it? and do i need to glue it back?
In the endpoint method, I need to manage to connect the two points with a metal tool, right? And i'll do the process with the battery disconnected, correct?
You wouldn't believe it, but this is my first android and I had it working for less than an hour. I have always being an apple user, but my devices were always jailbroken. I thought that with android things would go easy, but I ****ed them up hahah
As I saw you posted somewhere else, I always like to push my devices to the limit and thats why I am a computer science student...
thanks a lot anyway, and wish me luck on Monday!! Hope I can do it...

zemariolac said:
You told that the device is glued. Is it really hard to open it?
Click to expand...
Click to collapse
I used an X-ACTO knives (careful!), and yes it was somewhat hard to open.
and do i need to glue it back?
Click to expand...
Click to collapse
The A2 is glued with double sided tape going along all the edges. I removed that tape, then applied pieces of double sided tape (red TESA) in select locations. Applying double sided tape along all the edges should be practically impossible to do manually. Notes:
The original tape provides a certain level of water protection. So I’m not sure that it was a good idea to remove it. Between the pieces of tape that I applied there now are gaps, which however are not visible from the outside.
The device can be put together without tape at all, and the screen keeps attached to the body. What happens without tape in situations of stress, I don’t know.
So far everything has been working out fine for me, and my A2 already survived a couple of crashes (don’t use the ugly case).
In the endpoint method, I need to manage to connect the two points with a metal tool, right?
Click to expand...
Click to collapse
Yes. Note that after shorting the contacts, you have limited time to start the flashing. I think it was 40 seconds.
And i'll do the process with the battery disconnected, correct?
Click to expand...
Click to collapse
Yes that’s the recommended method. It also allows you to quickly reset the device, i.e. by unplugging the USB cable.
I always like to push my devices to the limit
Click to expand...
Click to collapse
Same for me! Along the way I learned more than I wanted to. It’s interesting to see the device opened with all its components, removes a bit of the magic.
Anyhow, good luck!

feklee said:
OK, so the test points are below the fingerprint flex cable connector:
Click to expand...
Click to collapse
Why do I see a single camera module on the motherboard?

[email protected] said:
Why do I see a single camera module on the motherboard?
Click to expand...
Click to collapse
Front camera

Benjamin_L said:
Front camera
Click to expand...
Click to collapse
Oh, right. It's the front. My bad.

Typing from my unbricked MI A2!
Thank you for the post. Everything went well. It only took me more time than it needed cause i was trying to flash the comrpessed ROM (yes, I really did it). After that everything worked fine. Remind on your post for noobs like me that you need to extract the file before flashing it!

Hello
I just try the method but me it does not happen anything if I disconnect the battery I tried with several usb cable on several computers on several USB port and it is not strictly nothing

prblem
i have same problem

(Ask for help)Kindle Fire HD 3rd Gen - Could not boot into Fastboot mode

Hi all,
I would like to flash a custom rom for my Kindle Fire HD 3rd Gen(Fire OS 4.5.5.1).
I do have a 9008 cable(which worked for Qualcom devices).
However, my FireHD would not boot into Fastboot Mode when I powered it off and plugged the 9008 cable into it (It powers on normally and loads into the stock Fire OS without booting into fastboot mode.)
So I am not sure whether the cable I have is the right 'fastboot cable' (or was there something wrong I did during the process). I uploaded some photos here. Wish someone could help.
(My desktop is running Windows 10 64bit version.)
PS:
Since it's running Fire OS 4.5.5.1(based on Android 4.4.3). I was able to root it by using an app called 'kingroot'. It could now boot into stock recovery mode. The bootloader is locked still(I suppose). And I could not find a way to boot my kindle into fastboot.
{
"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 you managed to remediate this?

Fire Index: Which Amazon Fire Do I have?
Amazon (Kindle) Fire Tablets | Phone | Streaming Devices [INDEX] Helpful Information Welcome, this thread has been created to encompass everything you may need for your device. Please only post in this thread with feedback on how to improve...
forum.xda-developers.com
I had to make my own cable.
I originally had tried to buy a "fastboot" cable on ebay. But it was fake. I cut the rubber on the plug to see the 4th pin wasnt connectible really.
I then found a samsung cable and cut its cover off the micro usb end and found a pcb with each pin on the circuit. Then i simply soldered a wire between 4th pin and +.
But the only listing on ebay wasnt really fastboot.
I might make some cables to sell on ebay.
But shadow mentioned fastboot cables are available on amazon. Of course I cant say if they are presently. This stuff is pretty throwback. I guess if all else fails ill make some. Let me know if that sounds ideal. Id sell it cheap. Shipping international might complicate things though. But if you can solder. Rather than modifying a cable you could buy some micro usb solder plugs with phat pads to solder 1 yourself. Either way.
If you truly do have soho 3rd gen. 8gb or 16gb and its not bricked, Fastboot cable instantly boots fastboot if it is a fastboot cable.
So if its not booting its not fastboot cable. Excluding bricks perhaps or broken usb port.
But if you can get fire to mount on pc or charge likely the cables to blame.
Alternatively if you could find a motorola factory cable that allegedly fastboots.
Anyway good luck. I was dealing with the same issue.

Thanks a lot, @AstralA, but I unfortunately bricked the device by accessing fastboot to install twrp via an su binary, which failed midway through, therefore corrupting the recovery. It's just stuck in a bootloop.
(Do you happen to have any advice? Anything that I could poke to make its firmware reset itself to stock, like a BIOS recovery pin?)

rokejulianlockhart said:
Thanks a lot, @AstralA, but I unfortunately bricked the device by accessing fastboot to install twrp via an su binary, which failed midway through, therefore corrupting the recovery. It's just stuck in a bootloop.
(Do you happen to have any advice? Anything that I could poke to make its firmware reset itself to stock, like a BIOS recovery pin?)
Click to expand...
Click to collapse
So, when you say you accessed fastboot? You saw this screen?
What su binary was used?
Well if you didnt see that fastboot screen you werent in fastboot.
Theres a chance all you need is a fastboot cable if you didnt see that screen on your previous attempt. As soon as a fastboot cable is plugged it boots into fastboot.
But I also had the experience of purchasing a kindle, when I got it it bootlooped on grey logo.
I worried the system files or framework was edited, but thd battery had discharged 0.0x volts, and the lithium watchdog line would not allow it to charge or power on.
Replacing the battery cured it.
But I dont think the soho has a watchdog line. But im guessing on that. Because my soho has reported 0% battery charge but still works. But the hdx I got wouldnt charge the old battery which coincidentally had 0.0x volts
If you can explain a bit more of what was done on previous attempt I might have an idea.

AstralA said:
So, when you say you accessed fastboot? You saw this screen?
What su binary was used?
Well if you didnt see that fastboot screen you werent in fastboot.
Theres a chance all you need is a fastboot cable if you didnt see that screen on your previous attempt. As soon as a fastboot cable is plugged it boots into fastboot.
But I also had the experience of purchasing a kindle, when I got it it bootlooped on grey logo.
I worried the system files or framework was edited, but thd battery had discharged 0.0x volts, and the lithium watchdog line would not allow it to charge or power on.
Replacing the battery cured it.
But I dont think the soho has a watchdog line. But im guessing on that. Because my soho has reported 0% battery charge but still works. But the hdx I got wouldnt charge the old battery which coincidentally had 0.0x volts
If you can explain a bit more of what was done on previous attempt I might have an idea.
Click to expand...
Click to collapse
@AstralA, I might have seen that screen, but I might not have. Since I've definitely seen that screen in videos and screenshots demonstrating how to access it, I can't trust my memory in regard to that since this occurred 2 months ago.
However, I realize that I wasn't thinking much when I stated that – indeed, a fastboot cable would probably resolve this problem, since it would bypass the recovery, surely.
I used one of those seriously not recommended one-click root applications – KingoRoot it might have been – for the first time, since I didn't want to flash Magisk due to never having done so previously. It worked magnificently well, until flashing the recovery failed.
I should have just flashed PostmarketOS first...
If ever you do create a cable, and it only costs a few quid, I'll definitely nab one (if ya reckon it'll fix the problem), so thanks for the offer.

No worries. Happens to the best of em. I was guilty of making the mistake of using those espionage 1 click rooters before I knew better as well. Everybody was. Desperates measures for desperation.
Good news is if you can fastboot you can reflash a rom and not have any concerns of espionage. Since the flash wipes that.
Im still waiting on the plugs to show in the mail.
Well if worse comes to worse I could just mail it to you for free barring the shipping being ridiculous.
We will see. I will get back to you soon.