Hi, my kf2 is stucked at fastboot, i'm not able to boot into recovery or system, i have succesfully installed fff-1.4a using a factory cable (because it was bricked with the stock bootloader) and have installed the otter2-twrp-2.4.4.0-recovery.img from hashcode..
It boots and i see the blue kindle logo, and have a menu, but when i select recevery it just turns on the amber light and stays there, i have left it for about 5 minutes waiting to see if it get to revery with no luck.
I tried this:
Code:
sudo fastboot -i 0x18d1 getvar product
< waiting for device >
product: kindle
finished. total time: 0.000s
sudo fastboot -i 0x18d1 oem format
...
OKAY [ 0.068s]
finished. total time: 0.068s
Then
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
< waiting for device >
sending 'boot' (243 KB)...
OKAY [ 0.065s]
writing 'boot'...
OKAY [ 0.051s]
finished. total time: 0.115s
sudo fastboot reboot
rebooting...
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
< waiting for device >
sending 'boot' (243 KB)...
OKAY [ 0.065s]
writing 'boot'...
OKAY [ 0.051s]
finished. total time: 0.115s
It succeed as you can see, it has the fff bootloader and twrp recovery is installed!!
Then i tried
Code:
sudo fastboot -i 0x18d1 flash zip cm-10.1-20130704-NIGHTLY-otter2.zip
< waiting for device >
sending 'zip' (155204 KB)...
OKAY [ 38.806s]
writing 'zip'...
FAILED (remote: partition does not exist)
finished. total time: 38.813s
It seem like a partition table problem maybe because i'm trying to install Cyanogenmod and not a stock image...
I think maybe i must reformat the partitions but i only have access to fastboot and i have read the documentation of Android Fastboot in OmapPedia but i'm not sure it's a "generic" information and don't want to mess up things more.
I have read many trheads in the forum but all of them use adb and there's not a thread with instructions about it..
Or maybe i need to flash all the images (system, kernel, etc..) with fastboot but i don't know where to get it, the main problem is that i'm not able to boot into recovery and maybe that point to the real problem
Any help is appreciated !!
Thank's
You can't write CyanogenMod from fast boot.
Sounds like somewhere in there you formatted the system partition. You need the stack file on the system partition in order to boot into recovery.
Restore to stock using fast boot and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
How?
mindmajick said:
You can't write CyanogenMod from fast boot.
Sounds like somewhere in there you formatted the system partition. You need the stack file on the system partition in order to boot into recovery.
Restore to stock using fast boot and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Maybe it is the problem as fastboot oem format seems to do the job...
I have downloaded the stock update-kindle-6.3.2_D01E_4110520.bin, please can you point to the thread explainig how to do that using fastboot or it's just as easy as rename the file to update.zip and flash it directly?
Edited: also i'm not completely sure it's a kf2 and can't get a hint on how to discover it without knowing the is version :banghead: I've looked one the motherboard and is a MB0090 F3F.
I've downloaded the stock bin for the kf2 too...
Thank' for your quick reply
Well. If you have a kf2... The update you downloaded is wrong. IT'S FOR THE ORIGINAL KINDLE FIRE.
Without knowing what device u have u better slow down a sec. Any advice i give COULD permabrick u of you're on the wrong device.
What color was the BOX it came in? What is the model# on the back? (Same for kf1 AND 2 BUT NOT THE KF HD 7" OR 8").
Be advised- this device is EASY TO BRICK. BE CAREFUL.
--
Sent from my mind to your screen.
---------- Post added at 02:48 AM ---------- Previous post was at 02:40 AM ----------
Also. The correct update file wont work either.
You can only flash image files from fastboot.
--
Sent from my mind to your screen.
It's apparent you have a KF1 and not a KF2. The command "fastboot -i 0x18d1..." would not work on the KF2 because it still has the stock bootloader (unless something miraculous happened while I was AFK). The stock bootloader has a VID of 1949, and will not answer to commands using a different VID. 18d1 is Goggle's VID and is indicative of having FFF installed (KF1 only).
BTW, the "-i 0x18d1" part is completely unnecessary on FFF.
That's not your biggest problem though....
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
That command is completely wrong. What you're doing there is flashing the bootloader (fff-u-boot_v1.4a.bin) to the boot (kernel) partition. Obviously, there is no way that could possibly would work out for you. After the "fastboot" portion of the command, you need to specify what you want done with the image in question: flash or boot. "Flash" is persistent, "boot" is for one boot only. In the next part of the command, you need to specify which partition the image in question goes to; bootloader, recovery, boot, etc.
What you need to do is get an actual recovery.img and flash it to your recovery partition before you can even think of accessing said recovery to flash a ROM and get your device working again.
soupmagnet said:
It's apparent you have a KF1 and not a KF2. The command "fastboot -i 0x18d1..." would not work on the KF2 because it still has the stock bootloader (unless something miraculous happened while I was AFK). The stock bootloader has a VID of 1949, and will not answer to commands using a different VID. 18d1 is Goggle's VID and is indicative of having FFF installed (KF1 only).
BTW, the "-i 0x18d1" part is completely unnecessary on FFF.
That's not your biggest problem though....
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
That command is completely wrong. What you're doing there is flashing the bootloader (fff-u-boot_v1.4a.bin) to the boot (kernel) partition. Obviously, there is no way that could possibly would work out for you. After the "fastboot" portion of the command, you need to specify what you want done with the image in question: flash or boot. "Flash" is persistent, "boot" is for one boot only. In the next part of the command, you need to specify which partition the image in question goes to; bootloader, recovery, boot, etc.
What you need to do is get an actual recovery.img and flash it to your recovery partition before you can even think of accessing said recovery to flash a ROM and get your device working again.
Click to expand...
Click to collapse
Well you are completely right!! Didn't realize I was flashing it to the kernel partition, I bought this on eBay and it was already bricked, when I used the factory cable first time I got a lab26 device, and it was a 1949 so, if I'm right it's a kf2.
I've already flashed a twrp recovery but it won't boot.. I'll try sintering else and post the results here
Sent from my SPH-D710 using xda premium
LUC4X said:
when I used the factory cable first time I got a lab26 device, and it was a 1949 so, if I'm right it's a kf2.
I've already flashed a twrp recovery but it won't boot.. I'll try sintering else and post the results here
Click to expand...
Click to collapse
No. The stock bootloader on all generations and variants of Kindle Fires have vendor IDs of 1949. The fact that your device responds to the "fastboot -i 0x18d1..." clearly means you have a custom bootloader installed in its place. If you have an actual custom bootloader installed (not 2nd bootloader) then you clearly cannot possibly have a KF2.
In this thread, you say you have installed recovery twice, but the information given seems to suggest otherwise.
So to try and get to the root of the problem, what is the exact command you used to install custom recovery, and what custom recovery (version) did you install?
Glad you are here soupmagnet!
I didn't even look at the commands he was using but i definitely learned stuff from your posts. Thanks again
--
Sent from my mind to your screen.
Commands used
soupmagnet said:
No. The stock bootloader on all generations and variants of Kindle Fires have vendor IDs of 1949. The fact that your device responds to the "fastboot -i 0x18d1..." clearly means you have a custom bootloader installed in its place. If you have an actual custom bootloader installed (not 2nd bootloader) then you clearly cannot possibly have a KF2.
In this thread, you say you have installed recovery twice, but the information given seems to suggest otherwise.
So to try and get to the root of the problem, what is the exact command you used to install custom recovery, and what custom recovery (version) did you install?
Click to expand...
Click to collapse
Sorry guys i was out of town...
These are the commands (bootloader & recovery) i've used till now:
sudo fastboot -i 0x18d1 flash bootloader fff-u-boot_v1.4a.bin
< waiting for device >
sending 'bootloader' (243 KB)...
OKAY [ 0.065s]
writing 'bootloader'...
OKAY [ 0.083s]
finished. total time: 0.148s
sudo fastboot -i 0x18d1 flash recovery otter2-twrp-2.4.4.0-recovery.img
sending 'recovery' (8153 KB)...
OKAY [ 2.042s]
writing 'recovery'...
OKAY [ 2.705s]
finished. total time: 4.748s
Click to expand...
Click to collapse
Also tryed the twrp from teamw's site in both versions (otter & blaze) just to make sure, by issuing the following commands:
sudo fastboot -i 0x18d1 flash recovery openrecovery-twrp-2.5.0.0-blaze.img
< waiting for device >
sending 'recovery' (6144 KB)...
OKAY [ 1.540s]
writing 'recovery'...
OKAY [ 1.514s]
finished. total time: 3.054s
Click to expand...
Click to collapse
With this, when i reboot and select the recovery it turns on the amber light for 2 seconds and shuts down.
Then when i install the other recovery version (blaze from teamw):
sudo fastboot -i 0x18d1 flash recovery openrecovery-twrp-2.5.0.0-otter.img
< waiting for device >
sending 'recovery' (6144 KB)...
OKAY [ 1.540s]
writing 'recovery'...
OKAY [ 0.684s]
finished. total time: 2.224s
Click to expand...
Click to collapse
When select recovery i get the same result: amber light for 2 seconds and turns off.
And with hashcode otter2-twrp-2.4.4.0-recovery.img:
sudo fastboot -i 0x18d1 flash recovery otter2-twrp-2.4.4.0-recovery.img
< waiting for device >
sending 'recovery' (8153 KB)...
OKAY [ 2.042s]
writing 'recovery'...
OKAY [ 0.894s]
finished. total time: 2.937s
Click to expand...
Click to collapse
It hangs on amber light and i have to manually turn it off holding the power buttom for 10 seconds...
So you think it is a kf1 based on the device id?, it shows that id after i installed the fff-u-boot_v1.4a.bin from hashcode that i intended for the kf2...
Well, based on that i have installed a kf1 bootloader:
Downloaded the Kindle Fire Utility v0.9.9.zip from http://forum.xda-developers.com/showthread.php?t=2192818
Unzipped it (as i'm GNU/Linux)
"Grepped" recursively till find the web address to download files from
Downloaded fff-u-boot_v1.4a.bin
Downloaded openrecovery-twrp-2.4.4.0-blaze.img
Followed the install procedure
Same result !!, still can't get it to boot into recovery...
Really i hope someone here can point me to the right direction to fix this tablet, can't figure out what's wrong with kf(?)
LUC4X said:
So you think it is a kf1 based on the device id?, it shows that id after i installed the fff-u-boot_v1.4a.bin from hashcode that i intended for the kf2...
Well, based on that i have installed a kf1 bootloader:
Downloaded the Kindle Fire Utility v0.9.9.zip from http://forum.xda-developers.com/showthread.php?t=2192818
Unzipped it (as i'm GNU/Linux)
"Grepped" recursively till find the web address to download files from
Downloaded fff-u-boot_v1.4a.bin
Downloaded openrecovery-twrp-2.4.4.0-blaze.img
Followed the install procedure
Same result !!, still can't get it to boot into recovery...
Really i hope someone here can point me to the right direction to fix this tablet, can't figure out what's wrong with kf(?)
Click to expand...
Click to collapse
Lets get a few things clear right off the bat. The file named fff-u-boot_v1.4a.bin is the custom bootloader for the KF1. The bootloader flashed in the KF2 2nd bootloader installation is named otter2-u-boot-prod-10.2.4.bin. If you flash the fff-u-boot_v1.4a.bin (FFF1.4a) onto a KF2, you would end up with something that is slightly less useful than a doorstop.
Why you re-installed it is a mystery to me. You already had FFF1.4a installed. I know this (as I explained earlier) by the fact that your commands, using the "-i 0x18d1" switch, were successful. If you had a stock bootloader, no commands containing that particular vendor ID would work at all. If you had a KF2, there is absolutely NO WAY you would have a device that responds to fastboot commands using "-i 0x18d1". Even with a modified KF2, with 2nd bootloader installed, the vendor ID would still be 1949 and all fastboot commands must include "-i 0x1949" or they will not work. You can confirm the fact that you have FireFireFire installed by entering a fastboot command without adding "i- 0x18d1". With FireFireFire (KF1 only), the commands will still work because it is unnecessary to specify the vendor ID.
That being said, I'm not entirely sure what's going on with TWRP using both "otter" and "blaze" for the board name (I think it has something to do with Goo Manager?), but anything you get from the TWRP website should work for the KF1 (for the time being at least). Anything you get from Hashcode will be for the 2nd generation KFs.
I would suggest, to avoid complicating things any further, that you download Cannibal Open Touch recovery, confirm that the MD5sums match after downloading, and flash it to recovery in fastboot. COTR only works for the KF1 (not made for the 2nd Generation devices yet) so there is "practically" no way you can get the wrong one. If that works and you still want to try TWRP, download the one for Blaze, check the MD5 (as you should with everything), and try flashing it in recovery again.
If you still can't get your device to boot into recovery, try the command again, but replace the word "flash" with the word "boot" and leave out the partition (i.e. 'fastboot boot openrecovery-twrp-2.4.4.0-blaze.img'). If the device boots into recovery, then you know you have the right one and you may have bad blocks in your recovery partition preventing it from booting, but you won't know for sure without checking a few things out first.
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, but where can i get those files?
What do you think?
soupmagnet said:
Lets get a few things clear right off the bat. The file named fff-u-boot_v1.4a.bin is the custom bootloader for the KF1. The bootloader flashed in the KF2 2nd bootloader installation is named otter2-u-boot-prod-10.2.4.bin. If you flash the fff-u-boot_v1.4a.bin (FFF1.4a) onto a KF2, you would end up with something that is slightly less useful than a doorstop.
Why you re-installed it is a mystery to me. You already had FFF1.4a installed. I know this (as I explained earlier) by the fact that your commands, using the "-i 0x18d1" switch, were successful. If you had a stock bootloader, no commands containing that particular vendor ID would work at all. If you had a KF2, there is absolutely NO WAY you would have a device that responds to fastboot commands using "-i 0x18d1". Even with a modified KF2, with 2nd bootloader installed, the vendor ID would still be 1949 and all fastboot commands must include "-i 0x1949" or they will not work. You can confirm the fact that you have FireFireFire installed by entering a fastboot command without adding "i- 0x18d1". With FireFireFire (KF1 only), the commands will still work because it is unnecessary to specify the vendor ID.
That being said, I'm not entirely sure what's going on with TWRP using both "otter" and "blaze" for the board name (I think it has something to do with Goo Manager?), but anything you get from the TWRP website should work for the KF1 (for the time being at least). Anything you get from Hashcode will be for the 2nd generation KFs.
I would suggest, to avoid complicating things any further, that you download Cannibal Open Touch recovery, confirm that the MD5sums match after downloading, and flash it to recovery in fastboot. COTR only works for the KF1 (not made for the 2nd Generation devices yet) so there is "practically" no way you can get the wrong one. If that works and you still want to try TWRP, download the one for Blaze, check the MD5 (as you should with everything), and try flashing it in recovery again.
If you still can't get your device to boot into recovery, try the command again, but replace the word "flash" with the word "boot" and leave out the partition (i.e. 'fastboot boot openrecovery-twrp-2.4.4.0-blaze.img'). If the device boots into recovery, then you know you have the right one and you may have bad blocks in your recovery partition preventing it from booting, but you won't know for sure without checking a few things out first.
Click to expand...
Click to collapse
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, i've found you uploaded a system.img to androidfilehost...
What do you think?
I posted that ages ago. I'm not even sure what device it's for.
Check the file size. If it's around 350MB go ahead. If it's closer to 500MB then it's probably for the HD.
I can't imagine why you couldn't load recovery using the 'fastboot boot recovery.img' command. Did you receive any errors when trying?
soupmagnet said:
I posted that ages ago. I'm not even sure what device it's for.
Check the file size. If it's around 350MB go ahead. If it's closer to 500MB then it's probably for the HD.
I can't imagine why you couldn't load recovery using the 'fastboot boot recovery.img' command. Did you receive any errors when trying?
Click to expand...
Click to collapse
There's not error message, this is the output:
Code:
sudo fastboot boot CannibalOpenTouch-v2.1_otter.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.394s]
booting...
OKAY [ 0.004s]
finished. total time: 1.398s
But it never boots up and stays off.
I'm seriously thinking it may be a hardware failure but i wont give up until i'm completely sure about it.. that's why i though i should reformat partitions at the first time but the fastboot oem format command "seems" to work, perhaps it takes very short time to execute 0.068s and it is a very short time, so i though maybe it isn't really formatting anything, is it a "normal time"?
Right now i'm downloading the file it's 380MB maybe something good could happen!!
I'll try the following and will post the results:
Code:
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
LUC4X said:
There's not error message, this is the output:
Code:
sudo fastboot boot CannibalOpenTouch-v2.1_otter.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.394s]
booting...
OKAY [ 0.004s]
finished. total time: 1.398s
But it never boots up and stays off.
I'm seriously thinking it may be a hardware failure but i wont give up until i'm completely sure about it.. that's why i though i should reformat partitions at the first time but the fastboot oem format command "seems" to work, perhaps it takes very short time to execute 0.068s and it is a very short time, so i though maybe it isn't really formatting anything, is it a "normal time"?
Right now i'm downloading the file it's 380MB maybe something good could happen!!
I'll try the following and will post the results:
Code:
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
The command 'fastboot oem format' will only make sure the partition layout is stock, it does not format the partitions themselves. The information within the limits of the partitions will remain untouched, so it won't do you much good in this situation. The only way to properly format any partition is with recovery (or 'parted' which is usually run from recovery anyway). Your situation is rather unique because the "fastboot boot' command doesn't write anything to the recovery partition. It loads the disk image you choose, into active memory, as if your computer were a separate partition on which that image is stored. There shouldn't be any reason for it to not work properly.
Try to flash the system partition you downloaded and see how it goes. I would also suggest that you make absolutely sure the md5sums match before installing any image to your device, including the recovery images you downloaded before.
soupmagnet said:
The command 'fastboot oem format' will only make sure the partition layout is stock, it does not format the partitions themselves. The information within the limits of the partitions will remain untouched, so it won't do you much good in this situation. The only way to properly format any partition is with recovery (or 'parted' which is usually run from recovery anyway). Your situation is rather unique because the "fastboot boot' command doesn't write anything to the recovery partition. It loads the disk image you choose, into active memory, as if your computer were a separate partition on which that image is stored. There shouldn't be any reason for it to not work properly.
Try to flash the system partition you downloaded and see how it goes. I would also suggest that you make absolutely sure the md5sums match before installing any image to your device, including the recovery images you downloaded before.
Click to expand...
Click to collapse
Code:
sudo fastboot flash system system.img
sending 'system' (389120 KB)...
OKAY [ 97.308s]
writing 'system'...
OKAY [ 36.819s]
finished. total time: 134.131s
sudo fastboot erase userdata
erasing 'userdata'...
OKAY [116.935s]
finished. total time: 116.935s
sudo fastboot erase cache
erasing 'cache'...
OKAY [ 29.189s]
finished. total time: 29.189s
sudo fastboot reboot
rebooting...
finished. total time: 0.000s
Must be hardware, it's sad... if it where a SMD flash memory i would try to changed it but it's a tyni BGA chip...
Thank you very much for your help
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
soupmagnet said:
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
Click to expand...
Click to collapse
I'll try tonight !!
Sent from my SPH-D710 using xda premium
soupmagnet said:
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
Click to expand...
Click to collapse
./usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
... OKAY
Installing x-loader...
sending 'xloader' (128 KB)... OKAY
writing 'xloader'... OKAY
Flash FFF...
sending 'bootloader' (211 KB)... OKAY
writing 'bootloader'... OKAY
Flash TWRP...
sending 'recovery' (5260 KB)... OKAY
writing 'recovery'... OKAY
Resetting bootmode to standard boot...
... OKAY
Loading TWRP...
downloading 'boot.img'... OKAY
booting... OKAY
Click to expand...
Click to collapse
Same as before, it won't reboot after sending the boot to recovery command and if try to get into recovery it turns off after an amber light..
LUC4X said:
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, but where can i get those files?
What do you think?
Click to expand...
Click to collapse
At the begining i saw you were using "fastboot flash zip...." that's wrong command.. should be "fastboot flash update xxxx.zip"
so if you find the totally package, youcan use it.
also you has mixture the boot.img and bootloader.bin..
recovery is not needed if you can flash the right bootloader and boot.:laugh:
Hey guys i just flashed the 3.28.401.6 firmware and in the process i relocked the phone. I flashed the firmware and everything works fine, but now i can't unlock it for some reason i'm S-OFF and my CID is 11111111. I tried the command to flash the token but no luck and have even tried getting a new token.
C:\Users\haswell\Desktop\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1830711296 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.124s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.129s
i've also tried this (http://forum.xda-developers.com/show....php?t=2708571) however i got this:
1|[email protected]_m8:/ $ echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
lock/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied
1|[email protected]_m8:/ $
C:\Users\haswell\Desktop\platform-tools>
i also realized that my recovery is no longer working as well as superSU... please someone help me
My Phone is after booter responsive to the volume buttons, but the HTC Bootscreen keeps hanging... so cant do anyhting
No clue why your token didn't work, but it may be that you just need to request a new one. Perhaps they changed something in the OTA that invalidated older tokens? If so, ask for a new one. This is, by far, the safest choice.
However, if you just really want a challenge, you can try this. I haven't done this exact procedure myself, but it should work. The manual unlock is failing because you aren't in a root shell. If you have lost root, you will need to temp-root to recover.
Get Sunshine and let it temp-root your phone. Then, start up a local terminal and su into a root shell. You can't use ADB commands because Sunshine kills the ADB connection. Then, very carefully copy/paste the required dd command into it from the XDA forum thread. I use Mobile Firefox, but I know the built in "Internet" browser works too. Note - be very careful not to pick up any stray characters when you copy/paste. If you accidentally pick one up, the command will execute immediately.
That should do it.
Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.
That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
I'm on 2.18 and rooted. Problem is, I uninstalled or disabled a bunch of ASUS apps, will I have an issue if I use SuperSU to unroot and try to restore or upgrade my phone to 2.19?
Also, I have model number ASUS_Z00AD. Is this firmware OK to install on my phone?
cmendonc2 said:
That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
Click to expand...
Click to collapse
Fixed.
edit: nvm...
Both download links link to the same file. splashscreen.img
Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love
jpacleb85 said:
Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love
Click to expand...
Click to collapse
LOL... Gotta love the devs who tinker on here... Now we might actually get a recovery that will do nandroid backups in case of those "little" mistakes/problems that crop up from time to time...
MiCmAsTa said:
Both download links link to the same file. splashscreen.img
Click to expand...
Click to collapse
Fixed.
This is probably a silly question, but I have the ZE550ML and the latest update is 2.18, meaning that unlocking the bootloader it is still not possible can I install droidboot.img(fastboot img) from the 2.19 ZE551ML on my device? Or that will just hard brick my device?
Let me know your thoughts on this.
Continue the great work XDA crew =)
I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated
PsychoKilla666 said:
I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated
Click to expand...
Click to collapse
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.
rafyvitto said:
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.
Click to expand...
Click to collapse
Link please? and how to?
error
rafyvitto said:
Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.
Click to expand...
Click to collapse
I follow this method and received the following error on CMD
writing 'fastboot'....
FAILED (remote: falsh_cmds error!
Finished. total time: 0.830
im on 2.20 and it wont let me do anything.. i get the white boot screen instead of black but bootloader doesnt exist and it wont download twrp any suggestions?
Success
My phone's recovery stopped working, and the bootloader was locked, but I found this thread. I think I was able to get it working.
I extracted the droidboot.img from the file in the OP.
I copied the droidboot.img to my working directory, and tried to flash it.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.661s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.826s
Ok, I got the error. Maybe the "unlock" command will work.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.203s]
finished. total time: 0.204s
Same output as the last hundred times I tried to run it.
I rebooted the phone.
Code:
C:\myworkingdirectory>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.108s]
finished. total time: 0.109s
I put the phone into the bootloader mode. (For anyone reading, to get into the bootloader, turn the phone completely off. Hold the power button until it vibrates. Then hold the volume up key.)
I ran the unlock command twice.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.291s]
finished. total time: 0.326s
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.216s]
finished. total time: 0.216s
Then I tried to flash the image again.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.690s]
writing 'fastboot'...
OKAY [ 0.692s]
finished. total time: 1.384s
No error?! I have progress!
------
I believe my bootloader is unlocked. Let me try to flash the recovery. (My recovery was corrupted longggg before doing this.)
Code:
C:\myworkingdirectory>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11676 KB)...
OKAY [ 0.579s]
writing 'recovery'...
OKAY [ 0.571s]
finished. total time: 1.153s
No permission error! (Before this, I would usually have gotten an error that says "FAILED (remote: Permission denied".)
---- Important Notes ----
NO WHITE BACKGROUND IN BOOTLOADER.
Many people have reported seeing an inverted background in the bootloader. I don't have that.
TRIPLE DOTS IN COMMAND PROMPT
The triple dots you see when I run the unlock command are actually there. They are not placeholders.
------------
Right now I'm booting into recovery mode to flash a ROM to the phone. I'll update if I get the phone working.
Hi,
I was following the guide to install Rbox's boot menu from aftvnews. I had done it on my other aftv fine. The bootloader on the aftv was unlocked, but when I rebooted the aftv just sat at the white Amazon screen. The last few commands are below.
255|[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/syste
m/boot/boot.img
_sdcc.1/by-name/boot of=/system/boot/boot.img <
20480+0 records in
20480+0 records out
10485760 bytes transferred in 0.884 secs (11861719 bytes/sec)
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ # dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by
-name/boot
dev/block/platform/msm_sdcc.1/by-name/boot <
13164+0 records in
13164+0 records out
6739968 bytes transferred in 1.289 secs (5228834 bytes/sec)
[email protected]:/ # reboot
I tried hooking up a keyboard, but the alt i prtscn doesn't seem to work. I tried fastboot, but it doesn't look good. I haven't come across what tampered true, unlocked false means. As you can see from above though I had root, so that should have meant the bootloader was unlocked. Any help would be appreciated. I have done a fair bit of looking and it seems unless I want to take up soldering I am probably out of luck.
Thanks in advance!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
OKAY [ -0.000s]
finished. total time: -0.000s
Sox35 said:
Hi,
I was following the guide to install Rbox's boot menu from aftvnews. I had done it on my other aftv fine. The bootloader on the aftv was unlocked, but when I rebooted the aftv just sat at the white Amazon screen. The last few commands are below.
255|[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/syste
m/boot/boot.img
_sdcc.1/by-name/boot of=/system/boot/boot.img <
20480+0 records in
20480+0 records out
10485760 bytes transferred in 0.884 secs (11861719 bytes/sec)
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ # dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by
-name/boot
dev/block/platform/msm_sdcc.1/by-name/boot <
13164+0 records in
13164+0 records out
6739968 bytes transferred in 1.289 secs (5228834 bytes/sec)
[email protected]:/ # reboot
I tried hooking up a keyboard, but the alt i prtscn doesn't seem to work. I tried fastboot, but it doesn't look good. I haven't come across what tampered true, unlocked false means. As you can see from above though I had root, so that should have meant the bootloader was unlocked. Any help would be appreciated. I have done a fair bit of looking and it seems unless I want to take up soldering I am probably out of luck.
Thanks in advance!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
OKAY [ -0.000s]
finished. total time: -0.000s
Click to expand...
Click to collapse
Having root does not mean the bootloader is unlocked. Can you run:
Code:
fastboot boot recovery.img
rbox said:
Having root does not mean the bootloader is unlocked. Can you run:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Sorry, I was going by the guide of aftvnews that says if you have root it is unlocked. I ran the command, but I am guessing it is not good news.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.296s]
booting...
FAILED (remote: boot not allowed for locked hw)
finished. total time: 0.296s
Sox35 said:
Sorry, I was going by the guide of aftvnews that says if you have root it is unlocked. I ran the command, but I am guessing it is not good news.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.296s]
booting...
FAILED (remote: boot not allowed for locked hw)
finished. total time: 0.296s
Click to expand...
Click to collapse
You didn't follow all the instructions properly, and it is bricked now. I wrote instructions in a post somewhere on how to unlock with fastboot. I don't know where it is though. You could try searching my posts. @AFTVnews.com might know where it is.
rbox said:
You didn't follow all the instructions properly, and it is bricked now. I wrote instructions in a post somewhere on how to unlock with fastboot. I don't know where it is though. You could try searching my posts. @AFTVnews.com might know where it is.
Click to expand...
Click to collapse
Do I need to generate an unlock file using the output from the commands below? I am not able to find it again right now, but I believe you mentioned something about not using the 1949 part of the command. I don't have a Linux machine. Is there anyone that has the script installed already? If not I can hopefully find someone at work that has one. I just want to make sure I am using the correct commands. I am not sure if I can make the AFTV worse that it is now, but you never know!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem emmc-info
(bootloader) 0x154f04bad7
7090030242070BNB fastboot
//github.com/dpeddi/Cuber
./cuber_unlockbl --sign ./unlock.img ./unlock.signed
connect the hdx to a linux box and do following command:
./fastboot -i 0x1949 devices
./fastboot -i 0x1949 flash unlock unlock.signed
./fastboot -i 0x1949 reboot
Sox35 said:
Do I need to generate an unlock file using the output from the commands below? I am not able to find it again right now, but I believe you mentioned something about not using the 1949 part of the command. I don't have a Linux machine. Is there anyone that has the script installed already? If not I can hopefully find someone at work that has one. I just want to make sure I am using the correct commands. I am not sure if I can make the AFTV worse that it is now, but you never know!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem emmc-info
(bootloader) 0x154f04bad7
7090030242070BNB fastboot
//github.com/dpeddi/Cuber
./cuber_unlockbl --sign ./unlock.img ./unlock.signed
connect the hdx to a linux box and do following command:
./fastboot -i 0x1949 devices
./fastboot -i 0x1949 flash unlock unlock.signed
./fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Yeah, Cuber. That's it. And yes, you dont need the -i. http://forum.xda-developers.com/showpost.php?p=61812290&postcount=213 That has some instructions for doing it on Windows.
rbox said:
Yeah, Cuber. That's it. And yes, you dont need the -i. http://forum.xda-developers.com/showpost.php?p=61812290&postcount=213 That has some instructions for doing it on Windows.
Click to expand...
Click to collapse
Thank so much for the Windows link. The instructions on the couple different posts all mention the argument being 0xmmsssssss, but I am getting the following. I have to assume that isn't going to work without using the emmc-info.
C:\Python27>python.exe cuberHDX.py 0xd77090030242070BNB
Usage: cuberHDX.py [boot.img|serial]
Sox35 said:
Thank so much for the Windows link. The instructions on the couple different posts all mention the argument being 0xmmsssssss, but I am getting the following. I have to assume that isn't going to work without using the emmc-info.
C:\Python27>python.exe cuberHDX.py 0xd77090030242070BNB
Usage: cuberHDX.py [boot.img|serial]
Click to expand...
Click to collapse
Your ID is from the previous line:
(bootloader) 0x154f04bad7