Related
Edit: this is about Streak 7 Honeycomb 514 installation tips, I fixed the tile
I have installed ROMs on my Viewsonic gPad. Piece of cake, the process is straightforward and there were no wild goose chases looking for drivers. I never appreciated how easy the gTab was until I dealt with this nightmarish Streak 7.
I started at 6 pm last night, gave up at 2:30am, woke up at 7:30 this morning, and now (at 8:15) it is HOPEFULLY going to reboot into Gingerbread. And it looks successfull!
Some tips:
The general process
I followed the general instructions on the 506 update thread, but I used a 514 ROM.
You can add the update.img file to your external SD card using windows explorer, but you can't use windows explorer to add the recovery file to the recovery partition. One way to do that, is with Fastboot. The whole fastboot process includes:
-placing the tablet in fastboot mode
-connecting the tablet to the computer via USB
-installing drivers (hopefully, first time only)
-running fastboot.exe
-using a command prompt to move the recovery.img file onto the tablet's recovery partition
Fastboot and the recovery file are where I had my problems, so I added a few tips here.
ROM and Recovery
Get the 514 ROM and recovery files from here: here
NOTE: I could not get the 514 US 4G recovery to work, so I used the US Stock Froyo recovery.img from the 506 update thread.
Fastboot Guide
Use this page as a general guide for installing Fastboot and Flashing/Updating, but it is by no means comprehensive.
Finding Fastboot Drivers
Drivers for fastboot were a big sticking point for me. To get Streak 7 drivers: I connected my Streak 7 to my computer, enabled USB sharing on my tablet, and then in Windows file explorer find the streak and do a search for 'drivers'. It will found the folder (using a search for 'drivers') on the Streak that contains the drivers I need. There are drivers included in the fastboot download but the fastboot drivers did not work for me.
My approach for setting up/using fastboot
Download fastboot (it's actually fastboot and adb)
Extract the zip (I put it in c:\android)
Enter fastboot mode on device
Connect phone pc with usb cable.
Install approporate driver extracted from your streak (or try the ones from fastboot, they didn't work for me but maybe they will work for you)
Note: I installed drivers in fastboot mode AND in regular android mode, but I spent a long time working on drivers so that might not be necessary
Note 2: I installed the free 'Nero' software from Dell because someone else with similar problems also installed that software, IDK if it helped either one of us but who knows. I recommend not installing Nero just for this task, because most people don't seem to need it.
Note 3: After driver is installed, the streak will still say what it always says in fastboot mode: some red text followed by some white text. The fact that you have installed fastboot on your PC will not cause a change on the screen of your Streak 7 when it is connected to the PC.
run 'fastboot.exe'
a black window will appear and disappear very quickly.
open a command prompt type c:\android>fastboot devices
the command prompt should return something like '? fastboot'
This step lets you know you have fastboot working properly.
Now that you know fastboot is working, it's time to move your new recovery file to the Streak's recovery partition. Type C:\android>fastboot flash recovery recovery.img
If you forgot how to use a command line: you will need to use the 'cd' command to navigate to the folder your recovery.img file is in. It will be easy enough to find on the internet, and I am too tired to explain now. If you happened to place your files in C:\android, you can get there by typing 'cd\' (no quotes) and hitting enter, then typing 'cd android' and hitting enter.
in the above text, 'C:\android>' is the prompt you will see after using the 'cd' command. If you have your recovery file somewhere else, you must alter this prompt with the CD command so it reflects the recovery file's location.
in the above text, 'fastboot' tells your computer to use fastboot commands. Make sure you ran fastboot.exe. There is also a way to change environmental settings/path so that it will work whenever you have an android device plugged in, but I couldn't find the thread that discussed it.
in the above text, 'flash' is a command to write a file to a particular partition.
in the above text, 'recovery' is the partition being written to is the recovery partition.
in the above text, 'recovery.img' is the name of the file being copied to the tablet.
in the above text, 'C:\android' is the location of the file being copied.
I know I'm overtired and I need to go back to sleep because I'm doing an anal-retentive job of explaining how to use functions that you can read by typing in 'fastboot help'. But I've lost a bit of rational thinking and I am compelled to work on formatting and adding bullets so it looks pretty.
The command prompt will give you a couple of lines saying how long it took to move the file.
Finished!
Make sure you have a new update.pkg file on your external SD card, boot into recovery, and install your update.
Are you sure you are in the right section? This is Streak7 not Streak5
giveen said:
Are you sure you are in the right section? This is Streak7 not Streak5
Click to expand...
Click to collapse
Lol I changed the title. Yup, I was talking about the Streak 7.
Now you are making some sense, lol.
mike_ekim said:
Edit: this is about Streak 7 Honeycomb 514 installation tips, I fixed the tile
I have installed ROMs on my Viewsonic gPad. Piece of cake, the process is straightforward and there were no wild goose chases looking for drivers. I never appreciated how easy the gTab was until I dealt with this nightmarish Streak 7.
I started at 6 pm last night, gave up at 2:30am, woke up at 7:30 this morning, and now (at 8:15) it is HOPEFULLY going to reboot into Gingerbread. And it looks successfull!
Some tips:
The general process
I followed the general instructions on the 506 update thread, but I used a 514 ROM.
You can add the update.img file to your external SD card using windows explorer, but you can't use windows explorer to add the recovery file to the recovery partition. One way to do that, is with Fastboot. The whole fastboot process includes:
-placing the tablet in fastboot mode
-connecting the tablet to the computer via USB
-installing drivers (hopefully, first time only)
-running fastboot.exe
-using a command prompt to move the recovery.img file onto the tablet's recovery partition
Fastboot and the recovery file are where I had my problems, so I added a few tips here.
ROM and Recovery
Get the 514 ROM and recovery files from here: here
NOTE: I could not get the 514 US 4G recovery to work, so I used the US Stock Froyo recovery.img from the 506 update thread.
Fastboot Guide
Use this page as a general guide for installing Fastboot and Flashing/Updating, but it is by no means comprehensive.
Finding Fastboot Drivers
Drivers for fastboot were a big sticking point for me. To get Streak 7 drivers: I connected my Streak 7 to my computer, enabled USB sharing on my tablet, and then in Windows file explorer find the streak and do a search for 'drivers'. It will found the folder (using a search for 'drivers') on the Streak that contains the drivers I need. There are drivers included in the fastboot download but the fastboot drivers did not work for me.
My approach for setting up/using fastboot
Download fastboot (it's actually fastboot and adb)
Extract the zip (I put it in c:\android)
Enter fastboot mode on device
Connect phone pc with usb cable.
Install approporate driver extracted from your streak (or try the ones from fastboot, they didn't work for me but maybe they will work for you)
Note: I installed drivers in fastboot mode AND in regular android mode, but I spent a long time working on drivers so that might not be necessary
Note 2: I installed the free 'Nero' software from Dell because someone else with similar problems also installed that software, IDK if it helped either one of us but who knows. I recommend not installing Nero just for this task, because most people don't seem to need it.
Note 3: After driver is installed, the streak will still say what it always says in fastboot mode: some red text followed by some white text. The fact that you have installed fastboot on your PC will not cause a change on the screen of your Streak 7 when it is connected to the PC.
run 'fastboot.exe'
a black window will appear and disappear very quickly.
open a command prompt type c:\android>fastboot devices
the command prompt should return something like '? fastboot'
This step lets you know you have fastboot working properly.
Now that you know fastboot is working, it's time to move your new recovery file to the Streak's recovery partition. Type C:\android>fastboot flash recovery recovery.img
If you forgot how to use a command line: you will need to use the 'cd' command to navigate to the folder your recovery.img file is in. It will be easy enough to find on the internet, and I am too tired to explain now. If you happened to place your files in C:\android, you can get there by typing 'cd\' (no quotes) and hitting enter, then typing 'cd android' and hitting enter.
in the above text, 'C:\android>' is the prompt you will see after using the 'cd' command. If you have your recovery file somewhere else, you must alter this prompt with the CD command so it reflects the recovery file's location.
in the above text, 'fastboot' tells your computer to use fastboot commands. Make sure you ran fastboot.exe. There is also a way to change environmental settings/path so that it will work whenever you have an android device plugged in, but I couldn't find the thread that discussed it.
in the above text, 'flash' is a command to write a file to a particular partition.
in the above text, 'recovery' is the partition being written to is the recovery partition.
in the above text, 'recovery.img' is the name of the file being copied to the tablet.
in the above text, 'C:\android' is the location of the file being copied.
I know I'm overtired and I need to go back to sleep because I'm doing an anal-retentive job of explaining how to use functions that you can read by typing in 'fastboot help'. But I've lost a bit of rational thinking and I am compelled to work on formatting and adding bullets so it looks pretty.
The command prompt will give you a couple of lines saying how long it took to move the file.
Finished!
Make sure you have a new update.pkg file on your external SD card, boot into recovery, and install your update.
Click to expand...
Click to collapse
i would just like to add that you can go to the folder with fastboot.exe and the recovery.img and in my win7 64bit i just hold shift + right click and choose open cmd windows here note* not sure if this is a special feature of my win7 or not tho so other user who dont see it dont panic use above steps thought it may help tho
and i read a post baout using the 506 recovery img but theres a post saying it was updated idk cant find link now to it but if it works then good i myself am in the process of charging my 7 before i can see if it will accept the update.pkg now cause i tryed without changing the img im on stock 2.2.2 4g tmobile one
colorsharpkid said:
and i read a post baout using the 506 recovery img but theres a post saying it was updated idk cant find link now to it but if it works then good i myself am in the process of charging my 7 before i can see if it will accept the update.pkg now cause i tryed without changing the img im on stock 2.2.2 4g tmobile one
Click to expand...
Click to collapse
Yup, I read that posty too and I tried several times with the 514 recovery with no success. I then tried with the 506 recovery, no other changes, and it worked. I would have preferred a 514 revocery from a warm-and-fuzzy standpoint but I don't really care now that it's done.
I am trying to restore my Kindle HD to version 7.2.3 using Windows XP and when executing the fastboot command to flash the system.img I get the following error:
Code:
C:\temp\KFHD_SRT_v1.2.3>fastboot -i 0x1940 flash system system.img
load_file: could not allocate 929038336 bytes
error: cannot load 'system.img'
The system.img file is in the same directory as the fastboot.exe.
I get my Kindle into fastboot mode using a factory cable and to verify fastboot I get the product and it returnsTATE-PVT-08. I have checked the max-download-size and I get
Code:
max-download-size: 1006632960
finished. total time: 0.000s
i have tried flashing with both the factory cable and the regular USB cable and I keep getting the same error. Any thoughts on what the error means?
rjgonzalez73 said:
I am trying to restore my Kindle HD to version 7.2.3 using Windows XP and when executing the fastboot command to flash the system.img I get the following error:
Code:
C:\temp\KFHD_SRT_v1.2.3>fastboot -i 0x1940 flash system system.img
load_file: could not allocate 929038336 bytes
error: cannot load 'system.img'
The system.img file is in the same directory as the fastboot.exe.
I get my Kindle into fastboot mode using a factory cable and to verify fastboot I get the product and it returnsTATE-PVT-08. I have checked the max-download-size and I get
Code:
max-download-size: 1006632960
finished. total time: 0.000s
i have tried flashing with both the factory cable and the regular USB cable and I keep getting the same error. Any thoughts on what the error means?
Click to expand...
Click to collapse
There was another user a while back with the same problem, but I could never figure out why. Your system image is obviously smaller than the max-download size, so it doesn't make much sense to me.
From my perspective, if you can't get it to work, I would think you can (theoretically) boot into TWRP using the method found by Powerpoint45 and that would give you access to the adb shell so you can 'dd' the system image in place. I don't have an HD so I can't confirm that it will work, but I can't see any reason why it wouldn't.
That being said, I suggest you don't even attempt it unless you know exactly what you are doing.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
There was another user a while back with the same problem, but I could never figure out why. Your system image is obviously smaller than the max-download size, so it doesn't make much sense to me.
From my perspective, if you can't get it to work, I would think you can (theoretically) boot into TWRP using the method found by Powerpoint45 and that would give you access to the adb shell so you can 'dd' the system image in place. I don't have an HD so I can't confirm that it will work, but I can't see any reason why it wouldn't.
That being said, I suggest you don't even attempt it unless you know exactly what you are doing.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
I noticed there was an error in the command I copied and pasted. The 0x1940 should be 0x1949, however I still get the same error message. I am of the opinion it is an issue with the computer I am using. I will try with a computer with Windows 7 and see if I have better results.
UPDATE: It was an issue with my XP machine. I was able to flash the system.img using a Windows 7 machine and was able to downgrade to version 7.2.1.
rjgonzalez73 said:
I noticed there was an error in the command I copied and pasted. The 0x1940 should be 0x1949, however I still get the same error message. I am of the opinion it is an issue with the computer I am using. I will try with a computer with Windows 7 and see if I have better results.
UPDATE: It was an issue with my XP machine. I was able to flash the system.img using a Windows 7 machine and was able to downgrade to version 7.2.1.
Click to expand...
Click to collapse
Sorry to revive this thread, but I'm having the same issue and I'm a little desperate.
I'm running a Vista, as are all the computers in my household.
My kindle got screwed up again after a restore from back up. Now it goes like this
a)shows Kindle fire (yellow) 1 second
b)shows fastboot 1 second
c)then screen goes blank, until I switch it off
As I switch it on, repeats a, b & c
The device manger keeps searching & refreshing OMAP4440 drivers every 2 second( with ding sounds)
This happens both with a factory cable as well as the standard usb.
Any one knows how to troubleshoot this?
Bump
OK I have no experience with bricked kindles that are bricked in that manner but I think kindle fire first aid may be useful, but if that device is not installing fast enough because of it shutting off before windows can complete installing the drivers I have to say and this may not be useful or something you want to try, but Linux might be the way to go, it typicly doesn't need to install the driver because drivers are either integrated into the kernel or loaded immediately as modules, and Linux comes with quite a few drivers by default. So your device would be recognized as its flashing off and on, from their I don't know what you could really do even if u have access to fast boot if it keeps shutting off evert two seconds I don't see you successfully flashing it unless u know how to write a bash script that waits for it to show up and then immediately flashes the boot loader, which is fairly small, it might be able to flash before it shuts off if your extremely lucky. From what my thought track is seeing i think it might stop with the constant rebooting once you manage to flash the bootloader, from their i woukd see fixing any other bad partitions as easy. This is all from a novice unbrickers standpoint. I may be completely off, haven't ever used kf first aid, so I don't know if your brick is fixable or not. Just thought I'd post my two cents since no one has been posting any help for you yet. Hopefully someone else that knows more about this can help you out.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
looks like your device doesn't have enough power to stay in fastboot. just leave it charging for about an hour even if it doesn't display anything. it should still be charging.
UMM!!
stunts513 said:
OK I have no experience with bricked kindles that are bricked in that manner but I think kindle fire first aid may be useful, but if that device is not installing fast enough because of it shutting off before windows can complete installing the drivers I have to say and this may not be useful or something you want to try, but Linux might be the way to go, it typicly doesn't need to install the driver because drivers are either integrated into the kernel or loaded immediately as modules, and Linux comes with quite a few drivers by default. So your device would be recognized as its flashing off and on, from their I don't know what you could really do even if u have access to fast boot if it keeps shutting off evert two seconds I don't see you successfully flashing it unless u know how to write a bash script that waits for it to show up and then immediately flashes the boot loader, which is fairly small, it might be able to flash before it shuts off if your extremely lucky. From what my thought track is seeing i think it might stop with the constant rebooting once you manage to flash the bootloader, from their i woukd see fixing any other bad partitions as easy. This is all from a novice unbrickers standpoint. I may be completely off, haven't ever used kf first aid, so I don't know if your brick is fixable or not. Just thought I'd post my two cents since no one has been posting any help for you yet. Hopefully someone else that knows more about this can help you out.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
1. I tried pluging it in ubuntu-12.04-desktop-i386 live usb, didnt detect the device. Do I have to download some thing before?
2. After a,b,c, the screen goes black but the OMAP4440 keeps refreshing in device manger it only stops when I push the power button for more than 20 seconds. I beleive the KFHD is not switching of but just goes to a black screen.
3. What is a bash script?
OK bash is a way more flexible scripting language you use in Linux. Think the Linux equivalent of a windows batch file but way better. You said it was going into fast boot for a brief moment. Before rebooting, I figured if its long enough for the fast boot command to recognize it in Linux, you could have the command for flashing the boot partition handy in a terminal. I figured if you had a stroke of luck, because the boot partition is so small, you might be able to flash it and unbrick it to at least get it to boot into fast boot to the point where you could restore the other partitions. I don't remember how exactly the fast boot command works in terms of waiting for the device to show up, that's why j was thinking use a batch script to repeat itself until sometching happened, but if it waits for the device u could simply run fastboot -i 0x1949 flash boot boot.img. Note boot.Img would be whatever the boot image restore file is called. Also Ubuntu probably is detect it, you must don't know it, its not going to popup anything or do anything unusual when its detected, only way u would know is to either install a device manager, I use a gnome one because I use an older distro of ubuntu, or run a command from a terminal the moment u see fast boot screen, I don't remember the command offhand, actually running dmesg would probably show it being picked up as a device connected, not sure what exactly it would say though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hey, the description is quite technical for me. Can you write a step by step guide, starting from once i boot up a linus live usb (12.4 ubuntu)?
stunts513 said:
OK bash is a way more flexible scripting language you use in Linux. Think the Linux equivalent of a windows batch file but way better. You said it was going into fast boot for a brief moment. Before rebooting, I figured if its long enough for the fast boot command to recognize it in Linux, you could have the command for flashing the boot partition handy in a terminal. I figured if you had a stroke of luck, because the boot partition is so small, you might be able to flash it and unbrick it to at least get it to boot into fast boot to the point where you could restore the other partitions. I don't remember how exactly the fast boot command works in terms of waiting for the device to show up, that's why j was thinking use a batch script to repeat itself until sometching happened, but if it waits for the device u could simply run fastboot -i 0x1949 flash boot boot.img. Note boot.Img would be whatever the boot image restore file is called. Also Ubuntu probably is detect it, you must don't know it, its not going to popup anything or do anything unusual when its detected, only way u would know is to either install a device manager, I use a gnome one because I use an older distro of ubuntu, or run a command from a terminal the moment u see fast boot screen, I don't remember the command offhand, actually running dmesg would probably show it being picked up as a device connected, not sure what exactly it would say though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I am literally falling asleep right now, I will write it tomorrow after I finish writing my résumé... I will warn you it will be slightly vague because I don't use the newer distributions of Ubuntu and am unfamiliar with the ui. Actually for simplicity I will upload a zip file with the fastboot binary and any files it requires, so I don't have to explain how to install stuff in Ubuntu. Hopefully the nautilus browser is the same. For the record nautilus is basically like Ubuntu version of windows explorer. As long as you can find your home folder and launch a terminal you should be able to follow my vague instructions. Anyways I will write a guide tomorrow since I am literally nodding off.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
OK I haven't finished my resume but I figured this wouldn't take long to explain and I will just keep procrastinating if I don't clear everything in my mind. OK so to start with you need to open a terminal, I am unfamiliar with exactly where that will be located on new versions version f Linux because it doesn't use gnome ui. Last I checked if u hit the Ubuntu logo a menu with apps would come out, if there's an accessories section it would probably be there, if not there's a search function, if not that try Ctrl alt t, not sure if that keyboard shortcut is standard or not though.OK now I feel I can use numbers.
1. Download included zip file( will post from my PC in a moment)
2. Open the home folder in Ubuntu, again unsure where this will be but usually it shows u some things on that bar on the left, if home isn't mong them then click on like videos or music and go up a level, that is usually home.
3. Extract the contents of the zip file to a folder in the home directory, let's call the folder kindlefix
4. Download http://goo.im/devs/Hashcode/tate/kfhd7-u-boot-prod-7.2.3.bin this file and put it in the kindlefix directory.
5. In the terminal and type "CD kindlefix", now type "md5sum kfhd7-u-boot-prod-7.2.3.bin". Now check that the string outputted is the same as the one on the website. If it is continue to next step if not try redownloading the file again and checking it again.
6. In the terminal now type ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
7. Try hitting enter with your device powered off and when fastboot says waiting for device, power it on with fastboot cable.
Like I've been saying this is going to take a bit of luck to flash successfully, and if it does try to flash and fail it will probably just brick it worse, at which point I'd return to amazon. You might have to repeat this step a few times to get the timing right to see if it will flash, its a fairly small file so u might get extremely lucky. Post back and tell me what kind of luck u manage to get.
Your problem is that you are using OMAP drivers instead of fast boot or adb drivers.
Sent from my Amazon Kindle Fire HD using xda app-developers app
It does that yes, but only after it stays in fast boot for a few seconds, so we are trying to catch the kindle while its in fastboot with Linux so it can try to reflash the boot loader, if we could succeed in that then getting the rest working would be the easy part, though this as is is very difficult, only reason I even suggested trying this is because the boot loader is so small it doesn't take that long to flash, so I am hoping for it to flash in the few seconds it is in fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
It does that yes, but only after it stays in fast boot for a few seconds, so we are trying to catch the kindle while its in fastboot with Linux so it can try to reflash the boot loader, if we could succeed in that then getting the rest working would be the easy part, though this as is is very difficult, only reason I even suggested trying this is because the boot loader is so small it doesn't take that long to flash, so I am hoping for it to flash in the few seconds it is in fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
If the device IS actually going into fastboot, then it's entirely possible to re-flash the bootloader.
In order to do this, you have to enter the command while the device is unplugged, then plug it in when you see "waiting for device". As soon as fastboot mode is detected, the command will execute and the bootloader will be flashed, but be warned....
While flashing the bootloader happens rather quickly, if for some reason only part of the bootloader is flashed, the device will likely be unrecoverable. I suggest that you make sure the md5sum of the downloaded u-boot-bin checks out, and that you aren't using an extraordinarily slow computer.
Yea at this point his kindle is going to go either way, either way though if he didn't try what he's doing or if he did and it didn't work he'd be sending it into amazon though more than likely and seeing if they'd take it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK I haven't finished my resume but I figured this wouldn't take long to explain and I will just keep procrastinating if I don't clear everything in my mind. OK so to start with you need to open a terminal, I am unfamiliar with exactly where that will be located on new versions version f Linux because it doesn't use gnome ui. Last I checked if u hit the Ubuntu logo a menu with apps would come out, if there's an accessories section it would probably be there, if not there's a search function, if not that try Ctrl alt t, not sure if that keyboard shortcut is standard or not though.OK now I feel I can use numbers.
1. Download included zip file( will post from my PC in a moment)
2. Open the home folder in Ubuntu, again unsure where this will be but usually it shows u some things on that bar on the left, if home isn't mong them then click on like videos or music and go up a level, that is usually home.
3. Extract the contents of the zip file to a folder in the home directory, let's call the folder kindlefix
4. Download http://goo.im/devs/Hashcode/tate/kfhd7-u-boot-prod-7.2.3.bin this file and put it in the kindlefix directory.
5. In the terminal and type "CD kindlefix", now type "md5sum kfhd7-u-boot-prod-7.2.3.bin". Now check that the string outputted is the same as the one on the website. If it is continue to next step if not try redownloading the file again and checking it again.
6. In the terminal now type ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
7. Try hitting enter with your device powered off and when fastboot says waiting for device, power it on with fastboot cable.
Like I've been saying this is going to take a bit of luck to flash successfully, and if it does try to flash and fail it will probably just brick it worse, at which point I'd return to amazon. You might have to repeat this step a few times to get the timing right to see if it will flash, its a fairly small file so u might get extremely lucky. Post back and tell me what kind of luck u manage to get.
Click to expand...
Click to collapse
I lost you on step 5. Which website? the md5sum that i get is (bb029673d8f186db4dff6d38f4aa28cf) <---Nevermind. I know what website you are talking about.
---------- Post added at 01:49 AM ---------- Previous post was at 01:22 AM ----------
Once I get to number 6 I get this?
[email protected]:~/Kindlefix$ ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
bash: ./fastboot: No such file or directory
And the fastboot file and kfhd7...bin file are inside the folder.
Update.. FIXED
Thanks @stunts513 for your help. I was able to fix my kindle. The linux didn't work. Somehow it managed to stay on fastboot screen. I went back to Windows. Opened a command prompt typed fastboot -1 0x1949 getvar product and hit enter. it waited for device. turned Kindle off. plugged fastboot cable to kindle then PC and was able to read it. Once that happened I was able to manually input the info
{fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
fastboot -i 0x1949 flash recovery "C:\KFFirstAide\path\to\recovery.img"
fastboot -i 0x1949 flash system "C:\KFFirstAides\path\to\ystem.img"} ofcourse changing the paths.
I downloaded Hashcode's Kindle OS from here http://forum.xda-developers.com/showthread.php?t=2218475.
And it worked.
[ Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Orlando>fastboot -i 0x1949 getvar product
< waiting for device >
product: Tate-PVT-08
finished. total time: 0.004s
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
target reported max download size of 1006632960 bytes
error: cannot load 'C:\KFFirstAide\path\to\boot.img': No error
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\images\boot.img"
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 2.826s]
writing 'boot'...
OKAY [ 0.688s]
finished. total time: 3.517s
C:\Users\Orlando>fastboot -i 0x1949 flash recovery "C:\KFFirstAide\images\recove
ry.img"
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.826s]
writing 'recovery'...
OKAY [ 0.681s]
finished. total time: 3.513s
C:\Users\Orlando>fastboot -i 0x1949 flash system "C:\KFFirstAide\images\system.i
mg"
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [312.188s]
writing 'system'...
OKAY [ 73.516s]
finished. total time: 385.710s]
THANKS to all the 50+ threads that I read about this. And all the people that make it happen!
lo pudiste solucionar?
ToPViP said:
Thanks @stunts513 for your help. I was able to fix my kindle. The linux didn't work. Somehow it managed to stay on fastboot screen. I went back to Windows. Opened a command prompt typed fastboot -1 0x1949 getvar product and hit enter. it waited for device. turned Kindle off. plugged fastboot cable to kindle then PC and was able to read it. Once that happened I was able to manually input the info
{fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
fastboot -i 0x1949 flash recovery "C:\KFFirstAide\path\to\recovery.img"
fastboot -i 0x1949 flash system "C:\KFFirstAides\path\to\ystem.img"} ofcourse changing the paths.
I downloaded Hashcode's Kindle OS from here http://forum.xda-developers.com/showthread.php?t=2218475.
And it worked.
[ Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Orlando>fastboot -i 0x1949 getvar product
< waiting for device >
product: Tate-PVT-08
finished. total time: 0.004s
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
target reported max download size of 1006632960 bytes
error: cannot load 'C:\KFFirstAide\path\to\boot.img': No error
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\images\boot.img"
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 2.826s]
writing 'boot'...
OKAY [ 0.688s]
finished. total time: 3.517s
C:\Users\Orlando>fastboot -i 0x1949 flash recovery "C:\KFFirstAide\images\recove
ry.img"
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.826s]
writing 'recovery'...
OKAY [ 0.681s]
finished. total time: 3.513s
C:\Users\Orlando>fastboot -i 0x1949 flash system "C:\KFFirstAide\images\system.i
mg"
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [312.188s]
writing 'system'...
OKAY [ 73.516s]
finished. total time: 385.710s]
THANKS to all the 50+ threads that I read about this. And all the people that make it happen!
Click to expand...
Click to collapse
hola soy latino pero frecuento bastante el foro, antes no opinaba puesto que no hablo ingles , alguno que hable español me podria ayudar? me pasa lo mismo que el joven que inicio el tema, veo que algo hizo para arreglarlo pero yo no entiendo , porfavor ayudenme:crying:
stunts513 said:
OK I haven't finished my resume but I figured this wouldn't take long to explain and I will just keep procrastinating if I don't clear everything in my mind. OK so to start with you need to open a terminal, I am unfamiliar with exactly where that will be located on new versions version f Linux because it doesn't use gnome ui. Last I checked if u hit the Ubuntu logo a menu with apps would come out, if there's an accessories section it would probably be there, if not there's a search function, if not that try Ctrl alt t, not sure if that keyboard shortcut is standard or not though.OK now I feel I can use numbers.
1. Download included zip file( will post from my PC in a moment)
2. Open the home folder in Ubuntu, again unsure where this will be but usually it shows u some things on that bar on the left, if home isn't mong them then click on like videos or music and go up a level, that is usually home.
3. Extract the contents of the zip file to a folder in the home directory, let's call the folder kindlefix
4. Download http://goo.im/devs/Hashcode/tate/kfhd7-u-boot-prod-7.2.3.bin this file and put it in the kindlefix directory.
5. In the terminal and type "CD kindlefix", now type "md5sum kfhd7-u-boot-prod-7.2.3.bin". Now check that the string outputted is the same as the one on the website. If it is continue to next step if not try redownloading the file again and checking it again.
6. In the terminal now type ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
7. Try hitting enter with your device powered off and when fastboot says waiting for device, power it on with fastboot cable.
Like I've been saying this is going to take a bit of luck to flash successfully, and if it does try to flash and fail it will probably just brick it worse, at which point I'd return to amazon. You might have to repeat this step a few times to get the timing right to see if it will flash, its a fairly small file so u might get extremely lucky. Post back and tell me what kind of luck u manage to get.
Click to expand...
Click to collapse
Lol,nice guide mate. I saw the title and just thought,"How the hell does OMAP4 refresh itself?" Anyway,I think that he would be better off installing android-tools-fastboot since he's running Ubuntu.
Yea true, I hadn't familiarized myself at the time with the package names and such, just checked that post and man is the date old, almost a year... Learned quite a bit since then.
stunts513 said:
Yea true, I hadn't familiarized myself at the time with the package names and such, just checked that post and man is the date old, almost a year... Learned quite a bit since then.
Click to expand...
Click to collapse
help me please please
Translation: hi i am latino but quite frequent the forum, not previously thought since I do not speak English , some speak Spanish could help me ? I feel the same as the young man who started the topic , see something done to fix it but I do not understand , please help : crying :
My Spanish is horrible so I ran it through Google.
If it is doing exactly what the original poster is doing rather than showing up only as a omap4boot and not turning on then I recommend using Linux and running "fastboot -i 0x1949 erase boot" once it clears the boot partition it should kick it into fastboot until the boot partition gets re-flashed.
I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
tjpearson said:
I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
Click to expand...
Click to collapse
Do you have fastboot.exe on your computer? It looks like CMD isn't finding fastboot.exe 1-because you don't have it 2- because you have not started your cmd prompt from your fastboot.exe folder
can you post a screenshot of your cmd prompt when you get this error?
ADB Installer
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
tjpearson said:
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
Click to expand...
Click to collapse
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
mb_guy said:
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Originally Posted by mb_guy
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Click to expand...
Click to collapse
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
alray said:
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
tjpearson said:
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
Click to expand...
Click to collapse
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
alray said:
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
tjpearson said:
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
Click to expand...
Click to collapse
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
clsA said:
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
Click to expand...
Click to collapse
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
tjpearson said:
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
Click to expand...
Click to collapse
can you check my guide under faq #2, if that solves it
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
tjpearson said:
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
Click to expand...
Click to collapse
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
d -darrrrr
nkk71 said:
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
Click to expand...
Click to collapse
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
tjpearson said:
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
Click to expand...
Click to collapse
Lol
Now that the phone is good, go spend some time with your better half!!!
No guides on xda, on "how to return my marriage to stock"
Put the phone on the charger or something, and spend time with your significant other.
Sent from my HTC One using Tapatalk
One last question
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
tjpearson said:
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
Click to expand...
Click to collapse
Shouldn't be a problem, use the flashable zip from the thread: http://forum.xda-developers.com/showthread.php?t=1538053
Yeah , sorted.
Thanks again for all your help.
tj
Hey folks, long time xda user heavy search user results in minimal posts..
ok here we go.
I unlocked bootloader and rooted device with magisk now im attempting to re lock my boot loader.
i factory reset device and flashed google factory image with supplied zip file from google
command im using is
"fastboot oem lock"
results
C:\Users\RyeMc>fastboot oem lock
FAILED (remote: 'Unknown OEM command')
fastboot: error: Command failed
this is first lines from google factory image...
Sending 'bootloader' (8761 KB) OKAY [ 0.253s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
next i opened cmd and entered
"fastboot flash boot" then went and moved boot file into cmd window and said successful also tried boot_a and boot_b
unsure why i have tried to re download sdk manager android studio and input the file locations in the path under advanced settings.
albeit iv been out of the root game for a couple years made the mistake of getting a note 8 so i was stuck in that eco system.
some help or advice would be nice thanks.
before i rooted i made sure i was able to lock and unlock bootloader .
Use Adb tools or Sdk tools to unlock your phone.
Sent from my Pixel 4 XL using Tapatalk
Thaiban said:
Use Adb tools or Sdk tools to unlock your phone.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
device is currently unlocked looking to relock device..
the correct command is: fastboot flashing lock
make 100% certain however that your device is 100% stock before relocking, very good chance of bricking it if it is not.
uicnren said:
the correct command is: fastboot flashing lock
make 100% certain however that your device is 100% stock before relocking, very good chance of bricking it if it is not.
Click to expand...
Click to collapse
C:\Users\RyeMc>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
im going to go double check my path make sure it still exist. i did try and download sdk tools again.
RyeMcFly17 said:
C:\Users\RyeMc>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
im going to go double check my path make sure it still exist. i did try and download sdk tools again.
Click to expand...
Click to collapse
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.
uicnren said:
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.
Click to expand...
Click to collapse
What he said! :laugh:
Easier Windows choice : r29.0.6
download the latest platform tools and extract it, in the folder with the PT files in the top search bar type cmd and then try.
oem unlocking already unlocked
uicnren said:
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.
Click to expand...
Click to collapse
resolved added sdk platform tools to path in advanced settings flashed new google image and retired fastboot flashing lock and seems to have worked, thanks for all your paitence and advice. ill head back to the shadows and read read read before i post again till next time folks.
RyeMcFly17 said:
resolved added sdk platform tools to path in advanced settings flashed new google image and retired fastboot flashing lock and seems to have worked, thanks for all your paitence and advice. ill head back to the shadows and read read read before i post again till next time folks.
Click to expand...
Click to collapse
:good::good:
glad you got it sorted.