So everyone says never do this, but what can I say, I was curious
My Optimus was previously rooted using sublimewolf's method: http://forum.xda-developers.com/showthread.php?t=935312
I then proceeded to brick it by using the Factory Reset found in the Privacy Screen. This forced my phone into a recovery loop.
If you can't even get to your custom recovery, your phone might be your newest paperweight But as long as you can both get to recovery and access the phone via adb, you'll be okay.
So here's how to unbrick it:
This is the flash_image: http://www.mediafire.com/?bx14hzq5i2pq3ps
And here's the stock recovery image + nand backup: http://www.mediafire.com/?ac0e2ksq0eslytk
(In my case, I was able to skip to Step 4 in the Nandroid Instructions because I had performed a Nand Backup when I rooted, therefore the necessary files were already in place)
Nandroid Instructions:
1) Unzip both downloaded archives
2) Move the BCDS-20110203-0357 dir into /sdcard/nandroid/mem=477M (also extract recovery.img and flash_image to root dir of your SD card, as you will need to later anyway)
2a) For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup
3) Mount SD into phone if it isn't already, boot into recovery if your phone isn't already there
4) Go into the "Backup/Restore" menu, and select "nand restore", confirm and wait
5) Reboot, proceed to Recovery Instructions below
Recovery Instructions:
1) Extract recovery.img and flash_image to root dir of your SD card if you haven't already done so
2) Connect to your phone via the adb shell and input the following commands:
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
# flash_image recovery /sdcard/recovery.img
# reboot recovery
3) If everything was done correctly, your phone should boot up normally to the OS
If the links above go down, let me know and I'll re-up
(thanks to tankhull for putting this info together)
(oh and you're welcome for being a guinea pig )
Thank you very much for putting this together
I am one of the curious one too.
You saved me....
If you can't get into recovery, I'm sure you can flash one through fastboot. No?
Sent from my VM670 using XDA App
Hi!
I had stock rom, but my phone was rooted.
So if whenever I turn my phone on, it goes to Clockwork Mod, does that mean it is bricked?
And will there be any way to unroot my phone after I do this? BC my 3G wasn't working at all, it should be working, but its not, so I did a factory reset.
Didn't work for me
when typing su after nand restore i get
/sbin/sh: su: not found
Ok so I have followed the instructions to the letter. And am attemptingto access adb shell. But in cmd prompt when I type adb devices it comes up with list of devices attached and says nothing. So how are we supposed to be accessing adb shell?
In clockworkmod, I went to the option for mounting and mounted the sd card, and a folder popped up on my comp, and there was no folder called Nandroid or clockworkmod
Any help guys?
I don't understand how to do the Nandroid instructions part... do I have to go to ADB?
atr0phy said:
So everyone says never do this, but what can I say, I was curious
My Optimus was previously rooted using sublimewolf's method: http://forum.xda-developers.com/showthread.php?t=935312
I then proceeded to brick it by using the Factory Reset found in the Privacy Screen. This forced my phone into a recovery loop.
If you can't even get to your custom recovery, your phone might be your newest paperweight But as long as you can both get to recovery and access the phone via adb, you'll be okay.
So here's how to unbrick it:
This is the flash_image: http://www.mediafire.com/?bx14hzq5i2pq3ps
And here's the stock recovery image + nand backup: http://www.mediafire.com/?ac0e2ksq0eslytk
(In my case, I was able to skip to Step 4 in the Nandroid Instructions because I had performed a Nand Backup when I rooted, therefore the necessary files were already in place)
Nandroid Instructions:
1) Unzip both downloaded archives
2) Move the BCDS-20110203-0357 dir into /sdcard/nandroid/mem=477M (also extract recovery.img and flash_image to root dir of your SD card, as you will need to later anyway)
2a) For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup
3) Mount SD into phone if it isn't already, boot into recovery if your phone isn't already there
4) Go into the "Backup/Restore" menu, and select "nand restore", confirm and wait
5) Reboot, proceed to Recovery Instructions below
Recovery Instructions:
1) Extract recovery.img and flash_image to root dir of your SD card if you haven't already done so
2) Connect to your phone via the adb shell and input the following commands:
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
# flash_image recovery /sdcard/recovery.img
# reboot recovery
3) If everything was done correctly, your phone should boot up normally to the OS
If the links above go down, let me know and I'll re-up
(thanks to tankhull for putting this info together)
(oh and you're welcome for being a guinea pig )
Click to expand...
Click to collapse
In the nandroid instructions, for placing BCDS-20110203-0357 into the /sdcard/nandroid/mem=477M
Do I have to do that, or step 2a if I have Clockworkrecoverymod, "For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup"
Also, how do I put this directory into the /sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M
Do I use ADB? And if so, how do I, because I have no idea about what commands/etc to use.. or could somebody please link me to a guide on how to push a file/folder into a folder like the ones I previously mentioned (/sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M)
Thank you in advance for your help!
Wreak_Peace said:
In the nandroid instructions, for placing BCDS-20110203-0357 into the /sdcard/nandroid/mem=477M
Do I have to do that, or step 2a if I have Clockworkrecoverymod, "For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup"
Also, how do I put this directory into the /sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M
Do I use ADB? And if so, how do I, because I have no idea about what commands/etc to use.. or could somebody please link me to a guide on how to push a file/folder into a folder like the ones I previously mentioned (/sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M)
Thank you in advance for your help!
Click to expand...
Click to collapse
You are making this harder than it has to be. All you are trying to do is place a folder and some files on your micro sdcard. Place the micro sd card on your computer. Grab the folder "BCDS-20110203-0357" and drag it to "/sdcard/clockworkmod/backup" (yes, that one because you have the clockworkmod recovery). If you have no way of placing the micro sd card onto your computer (card reader, micro sd to sdcard converter), then leave the card in the phone, connect the phone to your compter via USB, boot into the recovery, and then turn on USB massstorage mode through the recovery options. This should make the micro sd card pop up on your computer like a usb harddrive. Drag and drop the files.
mmarz said:
You are making this harder than it has to be. All you are trying to do is place a folder and some files on your micro sdcard. Place the micro sd card on your computer. Grab the folder "BCDS-20110203-0357" and drag it to "/sdcard/clockworkmod/backup" (yes, that one because you have the clockworkmod recovery). If you have no way of placing the micro sd card onto your computer (card reader, micro sd to sdcard converter), then leave the card in the phone, connect the phone to your compter via USB, boot into the recovery, and then turn on USB massstorage mode through the recovery options. This should make the micro sd card pop up on your computer like a usb harddrive. Drag and drop the files.
Click to expand...
Click to collapse
I put my microsd card into my computer, and there are no folders called sdcard, clockworkmod, or nandroid :/
Wreak_Peace said:
I put my microsd card into my computer, and there are no folders called sdcard, clockworkmod, or nandroid :/
Click to expand...
Click to collapse
Lol, first off, the sd card IS the folder "sdcard". That will only show up on your phone. Secondly, if the folders aren't there, just make them. They are not magic folders. Just right click, and select new -> folder, and name them as described.
clockworkmod\backup\
And then copy "BCDS-20110203-0357" into the "backup" folder.
You do have the Clockworkmod Recovery, right?
I do, and now, when i opened up my cmd
I did "cd c:\android\platform-tools"
then "adb shell"
then this came up "~#"
so even then, I went ahead and did "su"
and it said,
"su
/sbin/sh: su: not found"
So, what do I do now?
and I went ahead anyways did the next step
i typed in "mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system"
then it said
"mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
(next line) mount: mounting /dev/block/mtdblock5 on /system failed: invalid arguement"
Try doing only the last two lines,
Code:
flash_image recovery /sdcard/recovery.img
reboot recovery
So I just do
"cd C:\android\platform-tools
adb shell
flash_image recovery /sdcard/recovery.img
reboot recovery"
Or do i add the su in an additional line after adb shell
?
Wreak_Peace said:
So I just do
"cd C:\android\platform-tools
adb shell
flash_image recovery /sdcard/recovery.img
reboot recovery"
Or do i add the su in an additional line after adb shell
?
Click to expand...
Click to collapse
You don't need the su because you already have the "#" sign. That means you have super user privileges.
mmarz said:
Try doing only the last two lines,
Code:
flash_image recovery /sdcard/recovery.img
reboot recovery
Click to expand...
Click to collapse
K, so this is what I came out with when doing what you said.. this is without typing in su after adb shell.
Code:
cd c:\android\platform-tools
c:\Android\platform-tools>adb shell
~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # reboot recovery
reboot recovery
This is what I came up with when i did type su after adb shell..
Code:
cd c:\android\platform-tools
c:\Android\platform-tools>adb shell
~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # reboot recovery
reboot recovery
c:\Android\platform-tools>adb shell
I've never done this method so I can't tell you why it is not working or how it should work. Sorry.
I do have my own method for solving the bootloop issue. Try flashing this with your recovery: http://www.mediafire.com/?fbaoutnaw717pnb
Place it on your SD card and then use your recovery's flash zip option to flash it. It has helped others. It will replace your recovery with the Xionia recovery. If it works, you should boot into the LG logo. Once you can do that, boot into your recovery by using the correct button combo and flash any rom that you want to use.
mmarz said:
I've never done this method so I can't tell you why it is not working or how it should work. Sorry.
I do have my own method for solving the bootloop issue. Try flashing this with your recovery: http://www.mediafire.com/?fbaoutnaw717pnb
Place it on your SD card and then use your recovery's flash zip option to flash it. It has helped others. It will replace your recovery with the Xionia recovery. If it works, you should boot into the LG logo. Once you can do that, boot into your recovery by using the correct button combo and flash any rom that you want to use.
Click to expand...
Click to collapse
So i extract it to root of the micro sd? all of it? and then instead of recovery.img its vrecovery.img?
And so if it replaces my recovery with xionias recovery, it will boot into android and I can use my phone normally?
Here is the process
adb shell
cd cache
mkdir recovery
cd /
cp /sdcard/log /cache/recovery/
cp /sdcard/last_log /cache/recovery/
dd if=/sdcard/updaterecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
idme bootmode 0x5001
reboot
The cp command doesn't work on windows, IDK why but thats how it is, i figured I substitute cat /mnt/sdcard instead of cp/sdcard, but again dd command doesn't work even with /mnt/sdcard. Can someone please help me through the rest of the process? And no i don't have linux/mac computers.
Here are the rest of the steps
Now in recovery, you will see that the first option highlighted, is Install update.zip from sdcard. Press the Power button (ok).
When prompted to install, press the Power button again. The recovery is modded because it can’t be navigated through right now. No here is actually Yes so just select that.
Once the ROM is flashed, without rebooting your phone, open up command prompt or terminal and navigate to the location where the stock recovery is.
Now enter the following commands:
adb shell
mount sdcard
exit
adb push/sbin/
dd if=/sbin/stockrecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
adb reboot
The device will reboot twice now, and once it’s done, the CM7 logo will appear. For updates and queries,
It's simple install Ubuntu in windows using wubi .... It installs like a program and then u boot into it ... Don't be afraid of a penguin ....
You may just fall in love with a real operating system and check out mint ... Too
Sent from my SPH-D710 using xda premium
i believe you are missing a "su" command after adb shell
Yeah....you need adb shell, then SU to make the prompt go from $ to #. Try the commands then. They all work in win7, as I did it last night....three or four times.
Sent from my Kindle Fire using Tapatalk
Wrong forum!!!
I am stuck on:
Now enter the following commands:
adb shell
mount sdcard
exit
adb push/sbin/
dd if=/sbin/stockrecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
adb reboot
it just wont mount the sdcard says its busy, nevermind i rebooted and it worked.
But now i am stuck on the sbin part, i must be missing something
Ok, once again nevermind, i just modified the first recovery command to:
dd if=/sdcard/stockrecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
and it worked out at cm7 boot anim right now.
Try "ADB shell" then "Su" then "Mount /sdcard"
Minus the " "
Sent from my Kindle Fire using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2277105
I'm trying to follow above tutorial on how to install 2nd bootloader
I put "fastboot -i 0x1949 getvar product" in cmd, it showed "waiting for device" but when I turned it on, it doesn't change
I'm having a rooted 8.3.1 KF
Please help
tkien212 said:
http://forum.xda-developers.com/showthread.php?t=2277105
I'm trying to follow above tutorial on how to install 2nd bootloader
I put "fastboot -i 0x1949 getvar product" in cmd, it showed "waiting for device" but when I turned it on, it doesn't change
Please help
Click to expand...
Click to collapse
With the Kindle powered down, type the following command into a cmd/terminal window on your PC (should return with: < waiting for device> ):
fastboot -i 0x1949 getvar product
Then connect USB to the Kindle and it will boot. It *SHOULD* show a Fastboot screen and your terminal window should show something like:
product: Jem-PVT-Prod-04 this has to be done in a command window opened where fastboot is located. Shift + right click in the folder where fastboot is located select open command window here, then run the command and follow above instructions to get it into fastboot.
Edit also to let you know if you are running system version 8.4.1 other thing will need to be done to install freedom boot and recovery just to send an air of caution if you use the present instructions for this you will become stuck at the blue kindle fire logo so I would wait till methods have been updated.
yes I did that, unplugged my kindle and powered down -> type the command in cmd < waiting for device> -> Plug my kindle in and automatically turn on
The cmd still show < waiting for device> even after it's fully boot, it doesn't show fastboot screen
I managed to go to Fastboot mode by using KF First Aide, but my computer couldn't recognize kindle while it's in fastboot mode. So I couldn't do anything
Edit 1st post: I'm using 8.3.1 rooted
Thepooch helped me through teamviewer on how to install Android and here I share my experience on how to do it.
Your kindle need to be rooted. I suggest to use KF First Aide and root. It's easier
You will need ADB enable by go to settings in Kindle.
Download this file (Amazon 8.4.1 OS): http://d-h.st/VnR and put it in sdcard for backup purpose.
You don't extract ZIP files.
1. Download and extract #1 on below link
http://forum.xda-developers.com/showthread.php?t=2191010
2. Go to Root_with_Restore_by_Bin4ry_v21\stuff -> Shift + Right Click on folder -> Open command window here
*Steps 3,4,5,6,7 are from http://forum.xda-developers.com/showthread.php?t=2128201
3. Use these command to backup your stock partitions, these *.img will be in the Root_with_Restore_by_Bin4ry_v21\stuff folder.
Take 4 of those *.img to somewhere else safe
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img
4. Download these files (go to different topic above for latest version)
http://goo.im/devs/Hashcode/jem/stack
http://goo.im/devs/Hashcode/jem/kfhd8-freedom-boot-8.3.0.img
http://goo.im/devs/Hashcode/jem/kfhd8-twrp-2.4.4.0-recovery.img
5. Install stack:
Code:
adb push stack* /data/local/tmp/
adb shell su -c "dd if=/data/local/tmp/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
*Replace stack with location to your stack file
Example: adb push C:\Users\Admin\Desktop\stack /data/local/tmp/
6. Stop the auto recovery update script (this file may or may not be present): Mine was not present, it will show file not sound after enter 2nd command
Code:
adb shell su -c "mount -o remount,rw ext4 /system"
adb shell su -c "mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak"
adb shell su -c "mount -o remount,ro ext4 /system"
6.5: APPLIES IF YOU ARE ON SOFTWARE VERSION 8.3.0 OR GREATER
Download this: http://goo.im/devs/Hashcode/jem/kfhd8-u-boot-prod-8.1.4.bin
Enter fastboot mode and flash:
Code:
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
*You will need a file called fastboot.exe, open command from there, KF First Aide have it
or you can download from here: http://d-h.st/ttL <- Do not use anything from this, just go to tools and open command from there
7. Continue with these command in fastboot mode:
Code:
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.3.0.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.4.4.0-recovery.img
fastboot -i 0x1949 reboot
***If everything is done correctly, when you booting up, the word Kindle Fire should switch from orange -> blue -> orange, then fully boot
***If you get orange screen, then you didn't do step 6.5
8. Download these and put them in sdcard:
http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130604-UNOFFICIAL-jem.zip
http://goo.im/gapps/gapps-jb-20130301-signed.zip
To enter recovery mode, unplug, shut the kindle down. Plug in (it should power on), when the word Kindle Fire is orange, hold the volume up button, it should switch to blue and then twrp recovery mode. If you failed, hold the power button until it shut down and try again.
8.5. Drivers problem: Kindle not recognized
When I get into recovery mode, my computer couldn't recognize Kindle. So this is what you have to do.
Download this and extract: http://d-h.st/9We
Open android_winusb.inf
Go to/Search for
Code:
;Kindle Fire HD
Now go to Device Manager -> Right Click on "couldn't recognize driver kindle" -> Details -> you will see there are two codes.
Edit android_winusb.inf (below your device, mine is Kindle Fire HD) to match with the two codes.
Then just right click, update driver
9. Now back to Kindle, you should be in TWRP Recovery Mode.
You should backup first: Go to backup -> backup everything and check compression
Next go to Wipe -> Wipe 4 of the thing on the first line (Caches, Dalvik Caches, Factory Reset, System)
Next go to Install, choose 2 of the files at step 8.
Code:
cm-10.1-20130604-UNOFFICIAL-jem.zip
gapps-jb-20130301-signed.zip
Then reboot system
10. Now you should see CyanogenMod (Android) loading
After you are in, don't let Google backup your things. It will somehow messed up your system and will crash when you try to run apps.
Next, go to settings, go to about, and tap the last line 8 times to enable developer mode
Next, check advanced boot and ADB
After that, when hold your power button for a little bit, you will see a boot button, tap it and there should be 3 options to boot in case something happens.
Nice job you make a helper proud.
By Hashcode, Senior Recognized Developer on 1st February 2013, 10:57 AM over 5 years ago
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
with that being said here is what happens, i can see adb is working
C:\adb>adb devices
List of devices attached
B0CC060324930545 device
C:\adb>adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
/system/bin/sh: su: not found
C:\adb>
I could go on on but, that would be more gibberish.
So, what is wrong? Did the commands change? Is my path set wrong on my pc? Is there a updated thread i just have not come across yet? Anyone?
I'll thank you now for any help
Nothing changed. If you get the device to show up with the adb devices command, then everything's theoretically set up. The only reason you're getting an error with su not being found is that you aren't rooted. Here's a quick way to get root (like actually super simple, considering you already have ADB working):
1) download the attached 8.1.4 bootloader file (this is ripped straight from my Kindle before I "upgraded" to 8.5.1 to test this out). you may consider placing it in the same folder as the adb program. Also download SuperSU and the latest TWRP build for this device.
2) shut down the kindle and make sure it's plugged in.
3) run fastboot -i 0x1949 getvar product, then power the kindle on. when you see "fastboot mode" on the kindle, you should see something in the command prompt that begins with "Jem". if you do, then it's working.
4) type fastboot -i 0x1949 flash bootloader jem_8-1-4_bootloader.img to flash the 8.1.4 bootloader. this is ESSENTIAL because the kindle won't boot custom (unsigned) images otherwise. more explanation below...
5) next, type fastboot -i 0x1949 flash recovery twrp.img, where twrp.img is the file name of the TWRP image you downloaded earlier.
6) type fastboot -i 0x1949 oem recovery to kick the Kindle into recovery mode. if all goes well, you should see "TWRP" on your device after a few moments.
7) copy the SuperSU zip you downloaded to the kindle's internal storage. then on the kindle, tap Install. Next, on the side menu to the left, swipe up from the bottom and tap "sdcard" (referring to the internal storage that you see on the computer when the kindle's plugged in). Tap the SuperSU .zip, and then swipe where indicated. Feel free to reboot the system, and then voila, you're rooted. You should be able to run those backup commands. As a bonus, you won't have to download TWRP or the bootloader image from that virus-laden d-h.st site - avoid it like the plague.
8) Because TWRP's already flashed, you can type adb reboot recovery from the stock OS to begin flashing a new ROM right away.
A couple side notes...
1) Because you've flashed TWRP, a custom recovery, there is no need whatsoever to run the stock recovery backup command. It's already been overwritten, and if you really need it (which, again, is highly doubted because it only lets you run a factory reset), you can actually extract the recovery image from the system partition. Just run adb pull /system/recovery-prod.img stock-recovery.img instead of the adb shell su... stock-recovery.img one.
2) You have to flash the 8.1.4 bootloader because the one you currently have is more than likely a newer version. Custom ROMs (and even recoveries like TWRP) rely on an exploit in the 8.1.4 bootloader in order to trick the device into running the image (and newer bootloaders have this exploit patched already). So technically, because the exploit has to be run every time, the bootloader is never "unlocked" - merely tricked. Without the older bootloader in place, you get what is referred to as the "red screen of death". It's not pretty, but it's not permanent either. (Just power off the kindle, and then run the fastboot command involving "getvar product" to get it to the bootloader so you can flash the 8.1.4 bootloader and go forward.)
Hope this helps!