Kindle touch get bricked, Need mmcblk0p1.img

[wsxhwyy]

My Kindle touch got bricked. It got stuck in the loading screen.

I found a download address in this thread:
https://www.mobileread.com/forums/sho...=169645&page=6
But I cannot download it.

Who could provide a download address for a backup image?
My firmware version is 5.03.

[geekmaster]

You could install a 5.0.0 image and then install an amazon upgrade to 5.0.3.

It looks like the website that was hosting the touch "debricking repair" images is down today. Going to individual pages gives server errors, and the website home page is at a domain name parking service. Their domain name must have expired. I hope they renew it.

Hosting firmware images could lead to a takedown notice by amazon, which might have happened to that website.

[hostar]

To me this site works correctly and can download the files.

[knc1]

Originally Posted by geekmaster

Hosting firmware images could lead to a takedown notice by amazon, which might have happened to that website.

Or siezure by the U.S. Department of Justice, as happened to megaupload.com last week.
(Yeah, just try it, they have a new front page now. )

[geekmaster]

Originally Posted by hostar

To me this site works correctly and can download the files.

The gitbrew website is still not working for me in the USA.

The web host computer may still be on the internet at its old IP address, but it looks like the domain name expired and the root DNS servers are pointing to a domain parking service. It can take up to a week for it to disappear from secondary DNS server caches, and when they renew it, it can take another week for the domain parking service IP address to drop out of secondary DNS server caches and get the new (original) IP address.

Meanwhile, can somebody who CAN access the gitbrew site (not the domain parking service) please post the IP address here (ping it at a command line). We can provide an IP-based (no domain name) URL to the mmcblk0p1.img download file.

If the website is still up for some people who still have the old IP address in their DNS server cache, then it was just the domain name that probably expired at their DNS registrar, and they need to renew it. Again, even after they renew it, it might be up to 7 days before some of us can download that file using their domain name, but we can all download it using their original IP address.

Originally Posted by knc1

Or siezure by the U.S. Department of Justice, as happened to megaupload.com last week.
(Yeah, just try it, they have a new front page now. )

If it was a domain name seizure, I think we would see some scary government logos on the gitbrew website now.

Megaupload had a LOT of legitimate content too. Even mobileread forum posts pointed there and now have dead links.

Instead of removing the offending files, the feds heavy-handedly removed the entire megaupload website. That is like not bothering to prosecute and imprison the bad guys in your country, but instead just declaring the whole country a national prison and letting the bad guys roam free within that "prison system" (of which you become a fellow prisoner).

[knc1]

megaupload.com MUST have been doing someing much worse than posting the wrong files.
As BMBB posted, in the USA it is up to the copyright holder to defend their rights (with take-down orders).

[Not that I am suddenly a supporter of "Big Brother" - BB can defend itself.]

[dasmoover]

domain will be renewed today.

[geekmaster]

Originally Posted by dasmoover

domain will be renewed today.

But because I already viewed the parking service, I will only be able to access it by IP address until in times out it the DNS server cache of my ISP.

I can get around it by changing to manually assigned DNS server addresses for servers that have not yet cached the wrong address, or by using the IP address instead of the domain name.

What is the correct IP address? We can supply a link with IP only for those who cannot access it by domain name (and remove it in a week).

Thanks...

[geekmaster]

Originally Posted by knc1

megaupload.com MUST have been doing someing much worse than posting the wrong files.
As BMBB posted, in the USA it is up to the copyright holder to defend their rights (with take-down orders).

[Not that I am suddenly a supporter of "Big Brother" - BB can defend itself.]

Not megaupload.com that did something wrong -- they were busted because a piss-ant little law firm that buys "Intellectual Property" from porn sites went after one of the OTHER (porn) websites owned by the same people as megaupload.com. According to what I read about this, claims like this can usually be ignored, but this time the website owners chose to defend themselves, and a (big media company-friendly) judge decided against them. That gave the feds a crack in the door to step through, when they needed some publicity to show that they had "balls" due to recent news events.

This was in the news, if you clicked the links a few levels deep (and you were interested enough to do that). Megaupload fell victim to politics after thinking that they should defend themselves against a weak claim by an "ambulance chaser" IP law firm (or at least that is how I choose to interpret what I read on the internet, and we all know that if information is found on the internet, it must be true).

[hostar]

IP address: 108.54.248.54/~dasmoover/kindle/touch/forensic/

[geekmaster]

Originally Posted by hostar

IP address: 108.54.248.54/~dasmoover/kindle/touch/forensic/

Thanks. I added that right after the link with the domain name.

[geekmaster]

Good news! Got it all figured out. My touch is recovered, except the battery died while writing mmcblk0p1 in my RUNME.sh. Fastboot works if you stay within its limits (mmcblk0p1 is too big for it).

Read more here:
https://www.mobileread.com/forums/sho....php?p=1983418

[wsxhwyy]

I tried to recover the image, but it bricked even more.
When recover completes I rebooted the system. It loops at "RUNME.sh is running." It seems the image is broken and now I even don't have the dd program.

Who could provide me a correct way to recover the image?

[geekmaster]

Originally Posted by wsxhwyy

I tried to recover the image, but it bricked even more.
When recover completes I rebooted the system. It loops at "RUNME.sh is running." It seems the image is broken and now I even don't have the dd program.

Who could provide me a correct way to recover the image?

We can do it ALL from prebuilt custom images now for main and diags partitions. I even flashed the main and diags kernels.

If the kernels are damaged, you have to flash them first, after extracting them from inside an mmcblk0.img dump. I will provide that in my recovery package.

Then you have to flash diags mmcblk0p2.img if it is broken, or if you want one that already has the good stuff preinstalled in it.

You cannot flash mmcblk0p1 with fastboot -- it is too big. You need to boot diags, export usb, put a copy of mmcblk0p1.img on the usb drive (probably one with jailbreak and developer keys other good stuff already installed), Then my data.tar.gz and RUNME.sh that will restore the mmcblk0p1.img on the USB drive to the main partition. And finally, an ENABLE_DIAGS file because the main partition can only be restored when booted in diags.

I will provide detailed instructions, and all the stuff you need. I have it all figured out now...

[wsxhwyy]

Originally Posted by geekmaster

We can do it ALL from prebuilt custom images now for main and diags partitions. I even flashed the main and diags kernels.

If the kernels are damaged, you have to flash them first, after extracting them from inside an mmcblk0.img dump. I will provide that in my recovery package.

Then you have to flash diags mmcblk0p2.img if it is broken, or if you want one that already has the good stuff preinstalled in it.

You cannot flash mmcblk0p1 with fastboot -- it is too big. You need to boot diags, export usb, put a copy of mmcblk0p1.img on the usb drive (probably one with jailbreak and developer keys other good stuff already installed), Then my data.tar.gz and RUNME.sh that will restore the mmcblk0p1.img on the USB drive to the main partition. And finally, an ENABLE_DIAGS file because the main partition can only be restored when booted in diags.

I will provide detailed instructions, and all the stuff you need. I have it all figured out now...

Now I successfully recovered the correct mmcblk0p1.img. And I get stuck at the boot image.
Maybe I need a factory reset. How can I run factory reset in diag mode?