Related
So, I think I am screwed.
I am going to preface this by saying that I am very familiar with Android phones and am certainly not a noob. However, i am stumped here.
A few hours ago I tried updating my girlfriends phone to the latest version of MIUI 4. Well, it turns out that I was the poor guinea pig who found out for everyone that the uploaded file did indeed have an MD5 mismatch.
Anyhow, this borked my recovery (supposedly because a new kernel/cwm version was baked in to this flash).
Ok, I thought, I'll just put the phone in "Download Mode" and Odin back to stock and start over.
WRONG
The phone is NOT RECOGNIZED ON ANY COMPUTER. Not two different laptops running Windows 7 64-bit. Not a desktop running Windows 7 32-bit and not a Linux Box.
This isn't the typical "unrecognized device" error. I literally mean that it is NOT SEEN by any of these machines. There is no Windows "ding" or "noise" when it is plugged in. Nothing shows up in device manager as an unrecognized device. Nothing happens when I plug it in to my Linux machine.
I have tried FOUR different cable. The original Epic cable. My Epic Touch cable (which used to work great). A cable from a Nook Simple Touch and a cable from an HTC phone.
I am 99% certain that this is a hardware error and her phone is now ruined. She does not have TEP (she cancelled it for some reason -_-).
Has anyone ever heard of this? It can't be a driver issue because it would at least be seen by one of my devices correct? Or there would at least be a Windows "sound" when it is plugged in? The phone charges when connected, but nothing more whatsoever. I had issues in the past because of driver issues or bad cables. But, the fact of the matter is that the other day (when the phone was working fine) we plugged it into a computer and it would not recognize the phone at all (as I explained earlier). Even when storage was mounted, not a single thing was detected even though it used to work.
Sorry for the long winded and redundant post... It's quite late and i've been trying to fix this without freaking the woman out for the past 3+ hours. Driving me insane!
Anyone have any ideas? Or, any options I can take for if it truly is a lost cause?
Thanks everyone
uninstall all other phone drivers. Reboot. Install the drivers here : http://forum.xda-developers.com/showthread.php?t=728929
Windows is very very picky with drivers. If that doesn't work none of the cables you have used is a blackberry. I would say go out and buy a good blackberry cable or at least a good thick cable. Try another USB port as well. You can even try a fresh install of windows. If all fails then the USB is borked. Or it is dirty... see if you can't clean it out if you can see any lint or other gunk.
Sent From My Sprint Galaxy Nexus via XDA Premium
Try with your battery and SD card out. Sorry to hear this happened to you.
Sent from my GT-P7510 using Tapatalk 2
Battery out has worked for me in the past. Dude, good luck.
Sent from my SPH-D700 using XDA App
EmperorX said:
So, I think I am screwed.
I am going to preface this by saying that I am very familiar with Android phones and am certainly not a noob. However, i am stumped here.
A few hours ago I tried updating my girlfriends phone to the latest version of MIUI 4. Well, it turns out that I was the poor guinea pig who found out for everyone that the uploaded file did indeed have an MD5 mismatch.
Anyhow, this borked my recovery (supposedly because a new kernel/cwm version was baked in to this flash).
Ok, I thought, I'll just put the phone in "Download Mode" and Odin back to stock and start over.
WRONG
The phone is NOT RECOGNIZED ON ANY COMPUTER. Not two different laptops running Windows 7 64-bit. Not a desktop running Windows 7 32-bit and not a Linux Box.
This isn't the typical "unrecognized device" error. I literally mean that it is NOT SEEN by any of these machines. There is no Windows "ding" or "noise" when it is plugged in. Nothing shows up in device manager as an unrecognized device. Nothing happens when I plug it in to my Linux machine.
I have tried FOUR different cable. The original Epic cable. My Epic Touch cable (which used to work great). A cable from a Nook Simple Touch and a cable from an HTC phone.
I am 99% certain that this is a hardware error and her phone is now ruined. She does not have TEP (she cancelled it for some reason -_-).
Has anyone ever heard of this? It can't be a driver issue because it would at least be seen by one of my devices correct? Or there would at least be a Windows "sound" when it is plugged in? The phone charges when connected, but nothing more whatsoever. I had issues in the past because of driver issues or bad cables. But, the fact of the matter is that the other day (when the phone was working fine) we plugged it into a computer and it would not recognize the phone at all (as I explained earlier). Even when storage was mounted, not a single thing was detected even though it used to work.
Sorry for the long winded and redundant post... It's quite late and i've been trying to fix this without freaking the woman out for the past 3+ hours. Driving me insane!
Anyone have any ideas? Or, any options I can take for if it truly is a lost cause?
Thanks everyone
Click to expand...
Click to collapse
This might seem really crazy but i had the exact same problem about a year ago. It wasn't the cable, computer or the drives.
check the little connector piece in the phone where cable meets the phone. Its a small copper piece that can be notorious for bending up or down. I could charge my phone like you but couldn't figure out why the hell it wasnt syncing so try that and i could guess that's the issue. since its your gf's then Im sure she has some tweezers that an bend it back up but be very careful.
seoulseek80 said:
This might seem really crazy but i had the exact same problem about a year ago. It wasn't the cable, computer or the drives.
check the little connector piece in the phone where cable meets the phone. Its a small copper piece that can be notorious for bending up or down. I could charge my phone like you but couldn't figure out why the hell it wasnt syncing so try that and i could guess that's the issue. since its your gf's then Im sure she has some tweezers that an bend it back up but be very careful.
Click to expand...
Click to collapse
Tried bending it yesterday as I really think the connector is the issue. No dice
Sent from my SPH-D710 using xda premium
xboxfanj said:
Try with your battery and SD card out. Sorry to hear this happened to you.
Sent from my GT-P7510 using Tapatalk 2
Click to expand...
Click to collapse
Tried this as well
Sent from my SPH-D710 using xda premium
seoulseek80 said:
This might seem really crazy but i had the exact same problem about a year ago. It wasn't the cable, computer or the drives.
check the little connector piece in the phone where cable meets the phone. Its a small copper piece that can be notorious for bending up or down. I could charge my phone like you but couldn't figure out why the hell it wasnt syncing so try that and i could guess that's the issue. since its your gf's then Im sure she has some tweezers that an bend it back up but be very careful.
Click to expand...
Click to collapse
Also, the connector is physically bent. I'm going to try and bend it again today. The sides visibly form an ever so slight "u" shape.
I took the phone apart as well last night to get a better look. That piece does not appear to be interchangeable whatsoever. The entire input is like, awkwardly soldered to the system board...
Sent from my SPH-D710 using xda premium
Fiddling with the connector is not helping. I think I can safely say that this is a lost cause.
Sent from my SPH-D710 using xda premium
... you've failed to even read my suggestion?
Sent From My Sprint Galaxy Nexus via XDA Premium
ÜBER™ said:
... you've failed to even read my suggestion?
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
I've tried everything you suggested aside from reformatting windows.
Sent from my SPH-D710 using xda premium
EmperorX said:
I've tried everything you suggested aside from reformatting windows.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Blackberry cable? I know it seems miniscule but I've seen it before.
Sent From My Sprint Galaxy Nexus via XDA Premium
Uninstall the drivers, reboot, and do not install any driver. Connect to pc via usb and see if it finds the drivers and reads correctly on it's own.
Sent from my SPH-D700 CM9 ANDROID 4.0.4
Zeinzu said:
Uninstall the drivers, reboot, and do not install any driver. Connect to pc via usb and see if it finds the drivers and reads correctly on it's own.
Sent from my SPH-D700 CM9 ANDROID 4.0.4
Click to expand...
Click to collapse
Tried that as well
Sent from my SPH-D710 using xda premium
ÜBER™ said:
Blackberry cable? I know it seems miniscule but I've seen it before.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
Working on getting one now
Sent from my SPH-D710 using xda premium
Tried the blackberry cable. Still nothing. I guess it lived a good life
Sent from my SPH-D710 using xda premium
EmperorX said:
Tried the blackberry cable. Still nothing. I guess it lived a good life
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
you could get it JTAG'd. I'd Google for jtag services which will unbrick a hard brick. I doubt sprint will replace it unless you have a cool rep.
Sent From My Sprint Galaxy Nexus via XDA Premium
ÜBER™ said:
you could get it JTAG'd. I'd Google for jtag services which will unbrick a hard brick. I doubt sprint will replace it unless you have a cool rep.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
Do you think a JTAG would work? I truly think that this is a problem with the actual USB connector (we had problems with it before it got "stuck", EX: It wouldn't mount USB storage on any machines... Not detected at all when plugged in, aside from being charged). It isn't actually bricked... If my recovery would not have been wiped out by flashing the ROM with a bad MD5 OR, if I could get it to work on a PC/Linux machine I could easily Odin/Heimdall. I'm not exactly sure what a JTAG is, but I am 99% sure that I could fix this if it weren't for some crazy ass hardware issue. I'll try calling around.
Thanks man.
Its a direct communication with the board, is what I've grasped from hearing and reading about it. With this and a program it should rewrite things and allow you to flash things. Although now that I think about it your not hard bricked if you can get into Odin. And jtag usually puts it into download mode. Although I'm sure you can flash the stock firmware via jtag. Like I said Google things
Sent From My Sprint Galaxy Nexus via XDA Premium
ÜBER™ said:
Its a direct communication with the board, is what I've grasped from hearing and reading about it. With this and a program it should rewrite things and allow you to flash things. Although now that I think about it your not hard bricked if you can get into Odin. And jtag usually puts it into download mode. Although I'm sure you can flash the stock firmware via jtag. Like I said Google things
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
I found replacement power connectors for 5 bucks online... I am pretty skilled with soldering though (i own a tech company lol). Hmmmm
Sent from my SPH-D710 using xda premium
So here it is...I've had my kindle rooted using KFU since Jan. this year worked fine up till about 3 months ago when it just started turning on for 2 sec. then turning off. It will turn on untill it shows kindle fire v1.4a then shuts off. figured it was battery issue since i always let it run down to nothing. I've tried everything from KFU to rekindle to even making a factory cable and i have tried the shorting method all with no results. So this is where it gets weird my brother has a kindle rooted the same as mine so i thought i would try to access his with one of these methods. his battery was fully charged so i plugged it in to the usb on a windows vista computer with nothing else running just to see if it would recognize it and it instantly turn off and when i turned it back on it started doing the same thing mine was doing. I need help on this don't know what else to do.
My no root kf was doing that for a while to.
Sent from my Kindle Fire using xda app-developers app
It seems your computer's hardware jacked up your bootloader(s). I've seen similar issues in the past, although the "flashing", so-to-speak, IS kind of weird.
Rekindle, Firekit and of course fastboot can be rather troublesome to set up on Linux if you don't know what you're doing. There are a lot of factors that need to be considered before jumping to the conclusion that they don't work. Oh and then there's that whole "shorting trick" you have to master. People I have helped with this in the past have had to try many many times before getting it right.
So I would have to ask; How SURE are you that the USBboot method doesn't work?
soupmagnet said:
It seems your computer's hardware jacked up your bootloader(s). I've seen similar issues in the past, although the "flashing", so-to-speak, IS kind of weird.
Rekindle, Firekit and of course fastboot can be rather troublesome to set up on Linux if you don't know what you're doing. There are a lot of factors that need to be considered before jumping to the conclusion that they don't work. Oh and then there's that whole "shorting trick" you have to master. People I have helped with this in the past have had to try many many times before getting it right.
So I would have to ask; How SURE are you that the USBboot method doesn't work?
Click to expand...
Click to collapse
Well I can't say i'm 100% sure because I have never used linux until a couple of months ago. The whole terminal thing in ubuntu took some getting use to but figured it out I think. I do know my way around windows/dos command prompt. Do you think you might be able to help me out.
PM me
Hey all,
I picked up a used Nexus (VZW version) about a month ago and have been struggling with this issue. No matter what I've tried, I cannot get the phone to connect to any type of PC in MTP or PTP mode. I have been able to get it to connect in Fastboot mode on a PC, but that's about it.
I've tried NUMEROUS fixes after scouring the net for the past three weeks. I've tried on a Mac using Android Transfer, on an XP and Windows 7 PC using various drivers and toolkits, even the SDK, but nothing seems to work. I've used official Samsung drivers, naked drivers, wug's toolkit, another Nexus toolkit, pdanet, but none produced a different result. At one point I noticed that the pins on the USB terminal were bent and even went as far as replacing the USB port. I used factory Samsung cables and any other that I could get my hands on, but still no luck. It seems that the phone is not sending any type of signal for the computer to respond to. I get nothing popping up in Device Manager, not even an "unknown device" warning from Windows.
At this point I have to assume there is some sort of software issue (phone side) that is preventing the connection, but I don't know what. I thought I had a lead last week with changing something using the PhoneUtil settings, but I can't seem to find the right *, #, number combo to get into the settings.
Any ideas would be appreciated...I'm really not sure what my next step is.
Thanks in advance.
If fastboot devices lists your device when booted into the bootloader, I doubt this is a HW issue. Since you already tried so much, I can only write what I would do in your case:
1) get a clean install of Windows (XP or 7, doesn't matter). No restore point stuff, format C:\ and reinstall using the DVD.
2) do NOT install any drivers yet
3) open device manager
4) connect your GNEX and watch for changes
If you do see an unknown device now, update its driver using the naked driver.
Thanks for the suggestion. I'm gonna give that a shot in the morning and I'll report back.
The only other possibility that I could come up with was firmware. But I'm guessing that it since I tried stock 4.0.4 and 4.1.1 that it rules that out.
Sent from my Galaxy Nexus using Tapatalk 2
Ok, so after a clean install of XP, including formatting the drive, I still get no response in the Device Manager when I plug in my phone.
Sent from my Galaxy Nexus using Tapatalk 2
CCivale said:
Ok, so after a clean install of XP, including formatting the drive, I still get no response in the Device Manager when I plug in my phone.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Unexpected. Does your phone react when you connect it to the PC (starts charging, mentions 'connected as a media device')?
Yeah, I know. I'm baffled. No, doesn't show that it is charging, unless I turn it off completely. And no, doesn't say anything about being connected to the computer.
Sent from my Galaxy Nexus using Tapatalk 2
CCivale said:
Yeah, I know. I'm baffled. No, doesn't show that it is charging, unless I turn it off completely. And no, doesn't say anything about being connected to the computer.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It could be worth a try to inspect your USB port. Use a flashlight to see if something is bent or damaged inside.
If you are talking about the one on the phone, I replaced it about 2 weeks ago with a brand new one.
Sent from my Galaxy Nexus using Tapatalk 2
CCivale said:
If you are talking about the one on the phone, I replaced it about 2 weeks ago with a brand new one.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Oh yeah right, I didn't re-read your OP. Looks like I'm out of ideas for this one, sorry.
Have you tried switching to a higher priority USB port? There should be a few on the back of your tower (assuming its a tower).
Petrovski80 said:
Oh yeah right, I didn't re-read your OP. Looks like I'm out of ideas for this one, sorry.
Click to expand...
Click to collapse
No problem. Thanks for the ideas though. At least I'm somewhat narrowing it down. In the meantime, I picked up an OTG cable so I can load media files, and that seems to be working well.
Sent from my Galaxy Nexus using Tapatalk 2
063_XOBX said:
Have you tried switching to a higher priority USB port? There should be a few on the back of your tower (assuming its a tower).
Click to expand...
Click to collapse
I've been trying on multiple laptops and trying all of the USB ports, but no luck with any of them.
Sent from my Galaxy Nexus using Tapatalk 2
Hello! Been lurking for a while and just finally decided to post.
A little background: My first Kindle Fire 2 was rooted just fine. Everything worked for several months, then the screen went bad. Called Amazon and got a replacement sent over. The night I received said replacement, I decided that I wanted to try the 2nd bootloader + TWRP and install CyanogenMod. Unfortunately, I missed the part about reverting back to the older version of the bootloader before patching. Oops.
TLDR; Bricked KF2.
That brings me to the main focus of this topic: After reading a plethora of threads stating that there was no way to fix a bricked KF2 with the USB, I began thinking... Theoretically speaking, couldn't the e-MMC be accessed if it was taken out and mounted to an e-MMC to USB? This would allow reflashing the partitions and (hopefully) returning it to an unbricked state. Of course, that means remounting the e-MMC to the KF2 motherboard, but you can do wonders with a stencil, some solder paste, and a toaster oven, it seems.
Then, while searching for a good e-MMC to USB adapter, I stumbled across a very intriguing thread on hacking TomToms' NAV3 where the e-MMC is left on the device and wired to a MMC USB reader. Page 36 and 37 are the useful bits. (I can't post links yet, so this is the best to demonstrate): mobilescommunity.com/tomtom-discussions/178770-nav3-cracking-patching-copying-navcore-v10-v11-v12-36.html
At this point, I'm just waiting on an old, broken KF1 to arrive to track down where the leads go and possible solder points. I'll keep you posted as things progress.
Any comments, thoughts, suggestions?
P.S. I have a feeling that this would be better suited in the development forum, but as I am new, I can't post there. Assuming that this crazy idea actually works, (and considering that I'll probably have ten posts by then), I'll likely post a clean guide over on that forum.
i had my already taken apart cause of a broken screen, and one is for sure, there was no e-MMC or anything that you could take out and put into an adapter :\
I think you are not out of luck! Are you getting a red screen or is evrything dead?
Completely dead.
...and there is an e-MMC. On my KF2, it was under a piece of foam. If you look at it like you just took off the back cover (without moving the motherboard) from the bottom (the side with the usb port) it's on the right lower portion of the motherboard. It's a Samsung chip, KLM8G2FE3B-B001. There's also a line of solder points just below it. It looks like a decent number of the pins (which we can't see because it's a surface mount) go to that bank of solder points.
Since I still can't post real links/pictures: tinypic.com/r/20hppw5/5
Image credit: iFixit.
That picture is the motherboard from a KF1, but it's in the same location. It's the chip outlined in red.
Just a little update... Have a junk motherboard, the e-MMC is off, now I'm just tracking down where the pins go and possible solder points. It looks like the motherboard has exposed pads that will work well for soldering (my guess is they were originally access points for board/component testing?). I'll post again when I have more info.
Another update: I've tracked down solder points for DAT0-7, CMD, and CLK. I just need to track down the voltage (Vcc and Vss) and grounds (VccQ and VssQ). After that, I'll have pictures with it labelled. Then I need to work on soldering to said points and attaching them to a MMC reader, and praying that it works.
Hmm well if you can get your PC to recognize the emmc, with what I'm assuming is going to be Linux because of the fact the filesystem is ext4 on kindles last I checked, I'm curious if the modules that Linux have will recognize the device. If it does I wonder if u can simply use dd to flash the messed up partitions with the correct signed replacements. I wish I had your solder skills... I need a new tip for mine but I'm too lazy to go out and get one, much less do soldering on a kindle motherboard. If this works u could offer repair services to people, because I doubt most people would attempt this. I find this thread very interesting!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Then good luck to you!
Hopefuly we will have an unbrick method...
Finished tracking down solder points. Attached are some pictures with them labelled. I'll be working on the actual soldering and connecting it to my computer in the next few days here as my mini-vacation is over and I have to go back to work tonight.
So! I have good news. I soldered everything together and plugged it in. Ubuntu auto-mounted all the partitions from the e-MMC! I'll post pictures on Friday as I'm about to take a nap before spending the next 24 hours at work.
I have a couple minutes on break, so I'm uploading a screenshot of Ubuntu with the partitions mounted. All my pictures of the board/SD card reader and solder job are on my camera at home, so I'll post those later.
Note: The partitions are on the bottom left of the window, the 17 MB one through the 929 MB one. Once I track down which one is the boot partition, I'm going to rewrite it with the original boot image and pray that has fixed the problem.
Wow this is awesome, I am very impressed at this. Now to just use dd to shove the boot loader down the emmc's throat. I wonder does linux recognize the fact that any of the partitions are signed in like gparted under a partitions properties? Not sure if u have gparted installed, probably have to install it from the repos. Also kinda curious about the partition layout as to how everything is ordered on the emmc, as gparted shows.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Wow this is awesome, I am very impressed at this.
Click to expand...
Click to collapse
Thanks! Assuming this works, I'm thinking of designing a solder-less device to make all the connections. Soldering to those tiny pads on the motherboard was a pain!
stunts513 said:
I wonder does linux recognize the fact that any of the partitions are signed in like gparted under a partitions properties?
Click to expand...
Click to collapse
Is it the partition itself that's signed, or the boot files?
stunts513 said:
Also kinda curious about the partition layout as to how everything is ordered on the emmc, as gparted shows.
Click to expand...
Click to collapse
That's a really good idea. I'll make sure to take a screenshot of the partitions in gparted when I have a chance to work on it some more on Friday.
From what I understand not all, but some of the partitions are signed, like the boot loader, they have a 64kb signature in the partitions header if I remember correctly. That's also the reason we can't fix the device when we brick the boot loader, because these things show up as omap devices and we have the means to use that device and try to fix it, but we can't fix it because the initial file it loads up has to be signed. Your fix is kinda unorthodox, but hey, whatever works.:thumbup:bet amazon didn't think people would go this far to fix it. Heck technically if this works you could probably root it in this manor even if an exploit wasn't viable. Anyways for more I to on what I was talking about read q2, q3, and q4 of this post: http://forum.xda-developers.com/showthread.php?t=2228539
I personally want to look into why we can't just hex edit a image that's unsigned to clone a signed images signature, but I don't feel like opening up 2 huge files in a hex editor to compare the differences to see how the signature is in the file, not to me took that would be next to impossible I think since it would be difficult to try to make a partition exactly like the one on the kindle minus a signature (because even if u copied the files over, they wouldn't necessarily be in the stored in the exact same sectors of a partition), making it even more complicated for me to see the actual signature. Soupemagnet said this is impossible to do already and he knows what he's talking about so i seriously doubt I could do this.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I personally want to look into why we can't just hex edit a image that's unsigned to clone a signed images signature, but I don't feel like opening up 2 huge files in a hex editor to compare the differences to see how the signature is in the file
Click to expand...
Click to collapse
I'd venture an (un)educated guess that TI considered this sort of tampering and the header is essentially an encrypted checksum for the image. That would make sense when you consider the need for proprietary software to "generate" a signed header.
An interesting idea while we're going down this road... I'd think the only thing that prevents us from brute-forcing (through trial and error) our way to some sort of method of generating the signed headers is that an attempt could only be made once (assuming an incorrect algorithm) before you'd end up with a paperweight, meaning up until now you'd need a LOT of Kindles to even hope to get close; however, assuming that what I'm working on works to restore the KF2 to functioning, one could rig up a port to reflash the image (with a header generated with a new algorithm each time) until either you wore out the e-MMC or you managed upon one that worked.
Perhaps we could run the idea by soupmagnet and see what he thinks?
Yea that's an interesting idea, I have no idea how u could generate headers to try to forge what the kindle has though, and I'm assuming if it is a 64kb signature, that is a huge amount of combinations. I'm assuming figuring out how to make a signed image is similar to how some key generators are made that take a activation code and spit put another code for you to use. Though I have no idea how they figure out the common denominators for making a code based on such. Its one thing in simple math but to do it to strings of letters and numbers is beyond me. Luckily we have several partitions for reference, if it was just one we'd be pretty screwed, assuming I have any idea what I'm talking about. Feel free to run the idea by him, I chatted with him before a little about something like this in some PM's.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
kurohyou said:
I'd venture an (un)educated guess that TI considered this sort of tampering and the header is essentially an encrypted checksum for the image. That would make sense when you consider the need for proprietary software to "generate" a signed header.
An interesting idea while we're going down this road... I'd think the only thing that prevents us from brute-forcing (through trial and error) our way to some sort of method of generating the signed headers is that an attempt could only be made once (assuming an incorrect algorithm) before you'd end up with a paperweight, meaning up until now you'd need a LOT of Kindles to even hope to get close; however, assuming that what I'm working on works to restore the KF2 to functioning, one could rig up a port to reflash the image (with a header generated with a new algorithm each time) until either you wore out the e-MMC or you managed upon one that worked.
Perhaps we could run the idea by soupmagnet and see what he thinks?
Click to expand...
Click to collapse
Let's say you are able to restore the device every time you brick it. In order for brute force to work, you would need to be able to flash the image, attempt to boot, restore the device when it fails, create a new disk.img while somehow generating a new signature for it, flash that one, etc....and it all has to be done automatically.
Putting that aside for a moment, there's a lot of speculation online about how long it will actually take to brute force just a simple 128bit encryption key. I've seen everything from several years to several hundred years. Multiply that by about 500 and you'll have an idea of the amount of time it would take to brute force a 64Kb signature, and that's without having to repack, flash, restore, etc. for every single iteration....so I highly doubt a brute force attack is even feasible in this situation.
You should probably just focus on getting the device restored so you can have yourself a little side business of restoring hard bricked 2nd generation Kindle Fires...although, it would be extremely nice if you shared with the community how you were able to do so...if you are ever successful that is.
soupmagnet said:
Let's say you are able to restore the device every time you brick it. In order for brute force to work, you would need to be able to flash the image, attempt to boot, restore the device when it fails, create a new disk.img while somehow generating a new signature for it, flash that one, etc....and it all has to be done automatically.
Click to expand...
Click to collapse
Sounds like a lot of work; although, I didn't expect anything less.
soupmagnet said:
Putting that aside for a moment, there's a lot of speculation online about how long it will actually take to brute force just a simple 128bit encryption key. I've seen everything from several years to several hundred years. Multiply that by about 500 and you'll have an idea of the amount of time it would take to brute force a 64Kb signature, and that's without having to repack, flash, restore, etc. for every single iteration....so I highly doubt a brute force attack is even feasible in this situation.
Click to expand...
Click to collapse
What, you're telling me that cracking the encryption in a few million years from now wouldn't be useful?
It probably didn't help that in my sleep-deprived state last night, I failed to differentiate between 64kb and 64bit. Oops.
soupmagnet said:
You should probably just focus on getting the device restored
Click to expand...
Click to collapse
That's always been the focus, but I also figured that while we're here discussing things (and with confirmed access to the e-MMC now), why stop with just the basic restore to working when there's the possibility of more?
soupmagnet said:
although, it would be extremely nice if you shared with the community how you were able to do so...if you are ever successful that is.
Click to expand...
Click to collapse
Of course I'm going to share! As soon as I finish the last few steps here and confirm that it's working, I'm going to post a guide over on the Development forum. I don't know how many people will be comfortable with the soldering part, though. It was a beast trying to solder to the motherboard. I do plan on trying to develop a solderless method, probably by fabricating a board that connects to all the important points and secures to the motherboard itself (probably using the screw holes).
Some more images, now that I'm home.
Here's what everything looks liked when it's soldered together:
Here it is connected to the computer:
...and finally, a screenshot of the partitions in gparted:
Sweet, didn't realize how many partitions the kindle had. So now all we need to figure out is which partition of those is the bootloader partition, so u can try flashing the boot loader with the dd command. Might I suggest backing up the entire emmc device with dd instead of just some of the partitions? Also was wondering if all goes well, if the kfhd's emmc pin layout is the same, be nice if a solderless bolt on version could be truly "universal" for all kindles, shape wise it wouldn't be a problem as long as the bolt-on-board has multiple hole configurations.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
When I plug my phone pc gives me error that it doesn't recognize the USB device. I tried to adb to phone, still no luck. I was on cm11, reinstall rom. I uninstall driver from device manager, and adb drivers. Still can't connect. I was reading on the Internet maybe the device is bad. I had my nexus for 2 years and I never had this problem. Adb and my computer would always recognize my device. The thing that sucks my Verizon contract expired so I cancel my service. I was going to program my phone for page plus, but I can't because my computer won't recognize my phone. I had to activate my Samsung fascinate with page plus, but it sucks cuz I really wanted my nexus, can anyone help?
Sent from my SCH-I500 using Tapatalk 2
allcity187 said:
When I plug my phone pc gives me error that it doesn't recognize the USB device. I tried to adb to phone, still no luck. I was on cm11, reinstall rom. I uninstall driver from device manager, and adb drivers. Still can't connect. I was reading on the Internet maybe the device is bad. I had my nexus for 2 years and I never had this problem. Adb and my computer would always recognize my device. The thing that sucks my Verizon contract expired so I cancel my service. I was going to program my phone for page plus, but I can't because my computer won't recognize my phone. I had to activate my Samsung fascinate with page plus, but it sucks cuz I really wanted my nexus, can anyone help?
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Could be a few things, but I would try a different USB port on your PC, then I would try a different USB cord, and then try a different PC. If none of those get you a different result then could be the USB/charging port on your device, even though it may charge, it may still have trouble transferring data. I have seen on here where others have changed the port on their device and say it is fairly easy, I have not had to do so yet so I can't say from experience. If you are sure that you have the latest Samsung drivers installed on your PC then I doubt it is software related (not positive). Not sure if I am any help, just throwing out some suggestions. Maybe someone else can add some more definitive answers for you.
ThePhantom97 said:
Could be a few things, but I would try a different USB port on your PC, then I would try a different USB cord, and then try a different PC. If none of those get you a different result then could be the USB/charging port on your device, even though it may charge, it may still have trouble transferring data. I have seen on here where others have changed the port on their device and say it is fairly easy, I have not had to do so yet so I can't say from experience. If you are sure that you have the latest Samsung drivers installed on your PC then I doubt it is software related (not positive). Not sure if I am any help, just throwing out some suggestions. Maybe someone else can add some more definitive answers for you.
Click to expand...
Click to collapse
I try different USB ports and a different computer, still the same error. I'm like stuck.
Sent from my SCH-I500 using Tapatalk 2
Try this Universal Naked Driver
If you can work with device over ADB but system doesn't recognize phone, you must have bad drivers or OS. Try linux. I
Well I got my phone to work. I was reading how someone use a toothpick to lift up the tongue inside the USB port. So I use a tiny flathead messed with it for like a hour, kept plugging it to my pc until it connected. Once it did I push all the files I needed with adb to get it ready to get it ready to be program for page plus. Now I got my nexus on page plus, just activated it today, service is pretty good , they only that sucks is their is no 4G, but it feels good to only pay $50 for unlimited voice, text and 2.5 gb of data.
Sent from my Galaxy Nexus using Tapatalk