hi
If someone else with a rooted device (KINDLE FIRE HD 2013 MODEL) would simply just do a copy of their system partition and host it, it would be very useful as my kindle is stuck on the boot logo... so desperate at this point.. please help me guys. i have a factory cable and can get it into fastboot mode. i have the update 11.3.1 bin from amazons website. not sure what to do now. please can someone guide me step by step on how to fix or restore my kindle! thanks so much.
dave
davethebrave14 said:
hi
If someone else with a rooted device (KINDLE FIRE HD 2013 MODEL) would simply just do a copy of their system partition and host it, it would be very useful as my kindle is stuck on the boot logo... so desperate at this point.. please help me guys. i have a factory cable and can get it into fastboot mode. i have the update 11.3.1 bin from amazons website. not sure what to do now. please can someone guide me step by step on how to fix or restore my kindle! thanks so much.
dave
Click to expand...
Click to collapse
That bin file is actually a zip file, but without adb access its kinda useless, we need someone to dd their system partition and host them somewhere like we did with the 2012 model.
stunts513 said:
That bin file is actually a zip file, but without adb access its kinda useless, we need someone to dd their system partition and host them somewhere like we did with the 2012 model.
Click to expand...
Click to collapse
damnn
Related
I cannot proceed with restoring my Streak 7 without the following information. Please, this is not meant to be a discussion thread. If you can help out, thanks, if not, please contribute any discussion in my other thread "NVFlash Only Method of Access". This will help to keep the information somewhat organized.
1) I need the partition data from a working unit
Mode: nvflash (Vol Up & Down while plugging in usb)
Command: nvflash --getpartitiontable partitiontable.txt
The outputted text file should specify the exact sectors that the images need to be written to.
Download NVFlash here: NVFlash
2) I need the actual partition img files for all but the System, Boot, & Recovery.
Mode: SAA (nvflash)
Command: nvflash --read x part-x.img (where x is the partition number so you will have to run the command for each partition 2-7)
If you can pull these files for me, I can provide an upload method if you do not have your own.
Again, thank you.
check your pm for other files.
Thank you, thank you, thank you. Except I am not able to download any of the part files. I was able to get the bootloader so the path is accurate, I think the problem is that the .img files will not transport, you will have to zip them. I had the same problem on my server.
try the img files now.
runee said:
try the img files now.
Click to expand...
Click to collapse
Awesome! Downloading now.
No p15.img. Just about got everything else downloaded, can you get that posted up as well? Thanks again!
See next post. Crappy internet connection.
I have successfuly restored my Streak 7 using nvflash and the img files provided by Runee. I will work up a how-to as soon as I can make the img files available. Currently I am trying to restore root, but it is not going too well.
Patience and cooperation have been the keys to my success.
It may be a while before I can make the img files available, if someone can get them online before me, awesome. You will need to start with the correct bct and cfg files. I have them included in the nvflash zip below. Also I have created a batch command included in the zip (Restore.bat) that you can launch once you have the 2 through 14 img files in the same directory as nvflash.exe.
http://illdill.org/streak7/files/nvflash.zip
Hi,
Could someone please dump a system image for the 10.1? It's reeeealy easy
There are a few soft-bricks already due to people flashing the wrong image or to the wrong partition ( you know who you are, people! ) and you would be doing them a massive favour if you did.
If you already have busybox, all you have to do is run this:
Code:
dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Then you can pick it up the system.img from /sdcard
Code:
adb pull /sdcard/system.img
ZIP it and upload it somewhere ( Dropbox ) and you're done!
TIA
BC
Http://droidbasement.com/galaxy/sys-backup
The system_extra backup contains extra stuff (from the 'tools' compilation).
Thanks. There are a couple of people who will really appreciate that
OT: I just repacked your su/busybox update with the boot.img from the Voda 10.1 and it works fine. Link to the Voda boot.img is here
Would it be possible to get the original system image without the extra tools? I am trying to flash this image however I keep getting a remote error when I do so. Could it have something to do with the fact that this image is 600MB compared to other system images that are around 200 MB like for the gt 10.1v? Thanks again for posting it.
the extra stuff is not making it 600mb (maybe 10-20). It is quite big on the IO.
In order to fastboot flash it you must have an unlocked bootloader to do so (which in unlocked by default on the IO).
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
nadewad said:
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
Click to expand...
Click to collapse
ill retake the dump and upload it. ill do it tonight. maybe some corruption ocurred, etc.
It might be the same trick where you have to create a sparse ext4 image instead of ripping the image straight, because fastboot transfers the entire image in RAM before flashing it...
Try
Code:
make_ext4fs -l 512m -s /sdcard/system.img /system
If anyone has created a system image but isn't quite sure if it is the correct one, I'll be glad to try it out as I am one of those people who soft bricked their device. Just PM me and I'll be more than happy to flash my device and verify the stability of the system image. Thanks.
Nader
bump? Did anyone end up getting a system image? Thanks.
Nader
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
nadewad said:
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Run it on the device instead of using dd on the device.
ydaraishy said:
Run it on the device instead of using dd on the device.
Click to expand...
Click to collapse
He has a soft-bricked device so that's not an option unfortunately.
You can do a MD5 checksum of the file and get pershoot to check it against the original.
Otherwise, in the mean time, you can try this tool:
http://www.diskinternals.com/download/
You want the tool called "Linux Reader 2.0". It says it can only read ext2 and ext3, but I just tried it on my 10.1v system image which I created using the same method as pershoot, and it works fine.
...and see if you can mount it in Windows. If you can, the image is (probably) OK.
bcmobile said:
He has a soft-bricked device so that's not an option unfortunately.
Click to expand...
Click to collapse
Well, obviously, someone _else_ has to provide that image from a working device.
Same error here, while trying to flash the system.img. Any alternatives?
Thanks,
Eduardo.
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
nadewad said:
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
Click to expand...
Click to collapse
Samsung may charge you for the repair
Before you send it back, just have one more go at flashing the boot.img which smaskell provided from here. Just do a:
Code:
fastboot flash boot boot.img
The boot loop may be due to a different (incompatible) kernel if you still have the boot partition from the 10.1v
Failing that, if you're still up for it, do a:
Code:
adb logcat > %userprofile%\desktop\logcat-out.txt
...then open the locgat-out.txt file on your desktop and post the contents here or just zip and attach the file. That might give us something to work with
I am also not able to flash this system.img file. I get the same error.
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
nadewad said:
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
Click to expand...
Click to collapse
My tablet is showing P7100 as well. I tested with my employee's GT LE, and it shows the same. So, this is not the problem...
adb is not accessible to me as well.
I have a factory cable and I am able to get to fastboot mode but when I use the recovery tool from the development thread, nothing happens. No matter which option I choose.
I had previously rooted the kindle and installed the google play store. I started getting bootloops so I wanted to restore using the recovery tool.
I can't figure out what to do!
Still bricked!
Any help would be appriciated.
Unbricking your Kindle Fire HD
Sorry that i couldn't respond to you much earilier anyway if you are still Bricked follow this steps:
1.) Download KF Firstaide Msg me i will pm you the link
2.) after the download is finished Make a folder on your Desktop for example KFfirstaide
3.) next extract the contents from the Zip file and place it in your folder.
4.) you want to open up the folder and double click runme.bat
5.) next press a button to skip the intro and connect your kindle to the PC with factory cable
6.) you want to first type 7 and press enter to install the ADB drivers
7.) after you installed ADB you type 2 which will Completly restore the KFHD to 7.2.3 with fast boot.
Let it download the files itself and do the everything it self.
Note after the porgram downloads the 3 files it will want you to press a button to start the flashing process.
Hope i helped please leave a thanks
If this worked
And any problems at all with your kindle fire hd Please msg me
im a complete newb to fixing mobile devices and my friend gave me a messed up kindle fire hd.He said he screwed around with the os files and deleted one and he doesnt not know what one it was and when i try to boot it tries to boot but kindle file system recovery comes up. Then it asks me to reboot or factory reset i have tried both multiple times to no avail.I have a fastboot cable so that isnt a issue.Can somebody help me with a step by step or link to one.
huntergero said:
im a complete newb to fixing mobile devices and my friend gave me a messed up kindle fire hd.He said he screwed around with the os files and deleted one and he doesnt not know what one it was and when i try to boot it tries to boot but kindle file system recovery comes up. Then it asks me to reboot or factory reset i have tried both multiple times to no avail.I have a fastboot cable so that isnt a issue.Can somebody help me with a step by step or link to one.
Click to expand...
Click to collapse
You will need that fastboot cord.
Here is a system restore tool. I prefer to push the files manually but it will run as a tool http://forum.xda-developers.com/showthread.php?t=1951254
When you turn the Kindle Fire HD 7 on, push up on the volume rocker for three seconds until the screen shows the blue TWRP screen and release rocker and enter TWRP. (you said it boots into recovery?)
If this is the case, you don't need to do a full system restore. You can push a ROM the zips onto TWRP. Get them from the system restore tool.
If you have questions, feel free to ask. The tablet is recoverable unless something wrong is flashed.
LinearEquation said:
You will need that fastboot cord.
Here is a system restore tool. I prefer to push the files manually but it will run as a tool http://forum.xda-developers.com/showthread.php?t=1951254
When you turn the Kindle Fire HD 7 on, push up on the volume rocker for three seconds until the screen shows the blue TWRP screen and release rocker and enter TWRP. (you said it boots into recovery?)
If this is the case, you don't need to do a full system restore. You can push a ROM the zips onto TWRP. Get them from the system restore tool.
If you have questions, feel free to ask. The tablet is recoverable unless something wrong is flashed.
Click to expand...
Click to collapse
When it failed to boot in went into kindles reboot software and when i asked the individual i got this from he said he didnt install any recovery software.Can I install twerp now
huntergero said:
Can I install twerp now
Click to expand...
Click to collapse
Nope, it has to be a factory restore using your fastboot cord. I will list instructions.
---------- Post added at 09:50 PM ---------- Previous post was at 09:30 PM ----------
huntergero said:
Can I install twerp now
Click to expand...
Click to collapse
First thing is to download the SDK package and set the environment up. Here is a great video tutorial https://www.youtube.com/watch?v=oaNM-lt_aHw This will allow you to use fastboot command which is what you will do to push the images you need onto the bootloader.
To make sure your computer issue fastboot commands, open up a comand prompt as an administrator and type "fastboot -i 0x1949 getvar product" with no quotes and it should return Tate-xxx-xxx. If you don't get that response, do not move forward.
Once your at this point, download this tool http://forum.xda-developers.com/showthread.php?t=1951254 and either use it per the instructions or extract the files and CD from inside the folder and manually flash the 3 images via fastboot issuing these commands
fastboot -i 0x1949 flash boot "image name here" include .img at end"
fastboot -i 0x1949 flash recovery "recovery name here" include .img at end
fastboot -i 0x1949 flash system "system image name here" include .img at end
Now give some time as the system image is quite large
when done, type fastboot -i 0x1949 reboot
Profit
Fire tablet has been recovered, thanks to @Kramar111! See the attachment to his post for the lk.bin file!
I'm on the verge of hard bricking my Fire tablet because the instructions on the [root][5.1.1] do not work. If someone could please retrieve the latest lk.bin from 5.1.1 stock (the latest Amazon made ROM), or from a custom rom that has been installed on top of FireOS 5.1.1 (by using FlashFire) and upload it, I would be greatful.
It's easy to do, and there isn't a risk of damage to your tablet. You do not need root, just adb shell access.
Run in adb shell:
Code:
dd if=/dev/block/platform/mtk-msdc.0/by-name/UBOOT of=/sdcard/lk.bin
this command means 'copy byte by byte the data on the UBOOT block device and save it in a file called lk.bin on the SD card'
and you should be able to find the lk.bin file on your internal storage (with a file manager or with Android File Transfer).
Thank you for doing this, as I will be able to use my tablet without fear of it running out of battery and never starting again!
@gwhite5
i'm just unpack it from update-kindle-global-37.5.4.1_user_541112720.bin
Hi @Kramar111, thanks for uploading this - are you sure this is the lk binary introduced in FireOS 5.1.1? It can't be from an older version.
Thank you so much, that's the correct version, I didn't even know you could manually download the files from Amazon!
Sent from my D816w using Tapatalk
@Kramar111, it works! Thank you so much again! I've rebooted my Fire and it's fine now!
@gwhite5
you can download it from Amazon.com
http://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
(by the way it contain lk.bin, logo.bin, preloader.img, preloader_prod.img, tz.img and boot.img as well as update-kindle-global-37.5.4.1_user_541112720\META-INF\com\google\android\updater-script in wich are all the magic with preloader and others .img)
I understand now. Thanks anyway.
Sent from my D816w using Tapatalk
Hi, I'm a newbie here. I have a soft-bricked fire which needs a recovery. Does this method helps to restore the device? How can I flash this lk.bin to the device? Thanks!!
gopipandra said:
Hi, I'm a newbie here. I have a soft-bricked fire which needs a recovery. Does this method helps to restore the device? How can I flash this lk.bin to the device? Thanks!!
Click to expand...
Click to collapse
It depends on what condition your device is in. Most likely not: it merely replaces the lk.bin with the 5.1.1 revision. And if this binary was modified, it's likely that if you rebooted your Fire it would be completely dead (apart from the preloader's upload port for SP Flash Tool).