Database Develop

[Q] CM KFHD 7 was stable 5 months, now stuck at blue "Kindle" logo??

Hey everyone, first time caller, long time listener here. Apologies for the long post but I figured I'd rather provide all the details upfront.
I've had a KFHD 7" for about a year now and have been lurking around the KFHD dev forums ever since, anxiously awaiting ROM's made available for the 7. Finally in July I took the plunge, and using KFFA, downgraded to stock Kindle OS 7.2.3 and followed opensystem's thread here (http://forum.xda-developers.com/showthread.php?t=2347170) on using FireFlash to install kfhd7-Freedom-boot-7.3.0.img as the bootloader and kfhd7-twrp 2.4.4.0-recovery.img as the recovery. Success and all was beautiful!
Since then I've:
* Updated TWRP to version 2.5.0 via Hashcode's ZIP within TWRP
* Updated CM to version 10.2 (8/12/2013 build)
* Reverted CM to version 10.1 (had stability problems)
* Updated TWRP to version 2.6.3.0 via Hashcode's ZIP within TWRP
* Updated CM to version 10.2 (11/15/2013 build)
* Updated TWRP to version 2.6.3.1 via Hashcode's ZIP within TWRP
All this succeeded, and was stable until Thanksgiving Day (go figure). With my tablet acting somewhat laggy, I rebooted it as I have many times before. This time, when the "Kindle" logo went from Orange & White to Blue & White, it froze. I waited 5, 10, 20 minutes and longer, nothing. Wiped Cache, Dalvik, etc via TWRP and tried again... nothing. Reflashed TWRP 2.6.3.0 and CM 10.1 from zips, still freezes. And then it gets really weird when I factory reset it. Here's the sequence of events:
* Restored Kindle OS 7.2.3 via KFFA and fastboot, turned of Amazon updating
* Used FireFlash to install kfhd7-Freedom-boot-7.3.0.img and kfhd7-twrp 2.4.4.0-recovery.img
* Rebooted to TWRP 2.4.4.0 and installed TWRP 2.6.3.1 via Hash's ZIP
* Rebooted to TWRP 2.6.3.1 and installed CM 11.0 (11/25/2013 build)
* Reinstalled applications, etc.
Beautiful again! Worked for several hours with it yesterday, then decided to reboot again and... BAM! Back to the frozen "Kindle" blue & white logo again. Has anyone ever seen this before? Is there some way I can pull up a display of what the bootloader is doing behind the splash screen to see where it is falling over? (BTW, fastboot works, I can still boot into TWRP, and I have a factory cable)
Thanks in advance to all!

Netjerk said:
Hey everyone, first time caller, long time listener here. Apologies for the long post but I figured I'd rather provide all the details upfront.
Thanks in advance to all!
Click to expand...
Click to collapse
Using Freedom Boot with FireFlash does nothing. FireFlash is for images and freedom boot is not an image. You can push it manually no problem. That's why you have to downgrade your firmware to match the Amazon ROM you are about to flash. You may be having a software issue that can't be fixed. Verify your TWRP first. I would do a fresh install of the ROM you choose. Make sure to "swipe" first. Also, how full is your memory? Do you use the Greenify app to keep cpu usage down? Let me know..

LinearEquation said:
Using Freedom Boot with FireFlash does nothing. FireFlash is for images and freedom boot is not an image. You can push it manually no problem.
Click to expand...
Click to collapse
Hey, thanks for the reply. I'm even more confused now than before based on the statement above. Both the seokhun (http://forum.xda-developers.com/showthread.php?t=2271909) and Opensystem (http://forum.xda-developers.com/showthread.php?t=2347170) posts reference using FireFlash to install the kfhd7-Freedom-boot.img. Are you saying I shouldn't install it that way and should instead install via fastboot?
To further clarify, I am doing a full restore of 7.2.3 via Kindle Fire First Aide prior to beginning the procedure. KFFA "pre-roots" the 7.2.3 install and installs the SU app. From there, I'm disabling Amazon OTA updates and then installing ES File Explorer via the Amazon store. ES File Explorer is then used to install the freedom-boot.img as the boot and twrp as the recovery, using the stack override for boot and disabling updates on the recovery. A full reset is done afterwards and before installing CM (cache/dalvik/system wipe). Memory usage should be a non-issue as I haven't yet installed any other applications.
Any thoughts are greatly appreciated!

Opps, wow, I meant you can't flash the bootloader so that's why you downgrade firmware.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers
---------- Post added at 06:13 PM ---------- Previous post was at 06:12 PM ----------
Netjerk said:
Hey, thanks for the reply. I'm even more confused now than before based on the statement above. Both the seokhun (http://forum.xda-developers.com/showthread.php?t=2271909) and Opensystem (http://forum.xda-developers.com/showthread.php?t=2347170) posts reference using FireFlash to install the kfhd7-Freedom-boot.img. Are you saying I shouldn't install it that way and should instead install via fastboot?
To further clarify, I am doing a full restore of 7.2.3 via Kindle Fire First Aide prior to beginning the procedure. KFFA "pre-roots" the 7.2.3 install and installs the SU app. From there, I'm disabling Amazon OTA updates and then installing ES File Explorer via the Amazon store. ES File Explorer is then used to install the freedom-boot.img as the boot and twrp as the recovery, using the stack override for boot and disabling updates on the recovery. A full reset is done afterwards and before installing CM (cache/dalvik/system wipe). Memory usage should be a non-issue as I haven't yet installed any other applications.
Any thoughts are greatly appreciated!
Click to expand...
Click to collapse
See post above.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers

[Q] Trying to downgrade

Firstly, thanks to SafinWasi and Red_81 who both helped me on other threads, this question follows on from those threads.
I'm trying to downgrade from 7.4.9 user 4952320. Eventually, I will probably install CM11 (I tried once and bricked my device), but for now I just want to downgrade the OS and be able to change the wallpaper, I'm sick of the black paper. (I've tried Stunts wallpaper fix and it didn't work)
When the device upgraded to 7.4.9 I made backups of the whole 12 img files (inc boot0block).
I've read that you need a 7.2.3 boot image to be able to install TWRP as part of the CM11. I obtained a rooted 7.2.3 boot image from Red_81s google drive. I then flashed that boot image and tried rebooting the device. No joy. I got the red triangle. I flashed my 7.4.9 boot image and rebooted. The device rebooted and worked as normal.
I then flashed the 7.2.3 rooted system image and rebooted. Again I got the red triangle. I then flashed the 7.2.3 boot image, (so the device had 7.2.3 system and boot images) but again I got the red triangle.
So, how do you downgrade? Should I have flashed all 3 of the 7.2.3 images? (I don't have the checksums of the images so I recognise if one of the images was corrupted the exercise was doomed to failure.)
By flashing my 7.4.9 system and boot images, my device was restored to functionality, and I learned a bit, but not enough to achieve the goal. I'm hoping someone can show me how to downgrade.

Thought I'd add that I did try Kindle Fire First Aide but got lots of errors about dropbox not being available.

Did you flash the system and recovery? Both are needed to successfully downgrade. I always wipe data too.
Sent from my Nexus 7 using XDA Premium 4 mobile app

cecr said:
.
Click to expand...
Click to collapse
You need to flash a custom recovery on a second bootloader as well. You can't just flash the system. You also need to flash the 7.2.3 boot.img and stack override. Any tutorial dealing with this mod will include all the steps. It important to pay attention to details and not skip any steps. http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app

Red_81 said:
Did you flash the system and recovery? Both are needed to successfully downgrade. I always wipe data too.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't flash recovery, at my first attempt, just boot, then I tried boot & system. Both tries gave the red triangle.
I've tried again, with all 3 rooted images from your gdrive - recovery, boot & system, and again got the red triangle. I tried again with the 3 images from another source (my own unrooted 7.2.3 backup when I first got the HD7) and again, got the red triangle.
I haven't wiped the data because I would prefer to keep it so I can use the device (and think it should be possible to downgrade without wiping). I haven't been able to find a command to wipe just the cache...
So I'm more than a bit puzzled. The fastboot commands (eg fastboot -i 0x1949 flash boot boot.img) all return with "sending" then "OKAY", then "writing", then "OKAY" so I don't think there's any problem there.
I must be doing something wrong or missing something.

LinearEquation said:
You need to flash a custom recovery on a second bootloader as well. You can't just flash the system. You also need to flash the 7.2.3 boot.img and stack override. Any tutorial dealing with this mod will include all the steps. It important to pay attention to details and not skip any steps. http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your response, but at this stage I don't want to flash a new custom ROM, that may (probably will) come later, but at this stage I want to just downgrade. I've been warned that installing TWRP etc may leave the stock system in a bootloop, so a working stock backup won't be possible.
As I have to downgrade the stock boot image anyway in order to install a custom ROM, I thought I'd downgrade the whole OS in order to have a functioning stock system, then I can make a backup of it in TWRP, then install a custom ROM.
If I'm having problems with a simple downgrade, I might have more severe problems flashing a new ROM and be left with a dead device like I was previously, hence my caution and not wanting to move on until I know I can recover to the previous step if things go wrong.

Did you try downloading the original 7.2.3 from the thread and try flashing them ?

Red_81 said:
Did you try downloading the original 7.2.3 from the thread and try flashing them ?
Click to expand...
Click to collapse
Yes, I did. Tried them twice, in a different order (didn't think it would make a difference but you never know....). Anyway, tried again, this time, wiped data and cache (took 45 mins) and it worked! I now have 7.2.3 and access to Gplay (was already there).
I haven't registered it to my Amazon account yet, so email and contacts don't work, and am wondering if I should go straight to installing a custom ROM. I'm thinking if it isn't registered to Amazon, then they can't update it via OTA...... or can they?
It's been a bit of a task getting this far, but at least I'm more confident about getting into ADB and Fastboot!

cecr said:
I'm thinking if it isn't registered to Amazon, then they can't update it via OTA...... or can they?
Click to expand...
Click to collapse
well, I know the answer, yes, even though it hasn't logged into an Amazon account (I realise they pre-register them to your account before dispatch), it updated back to 7.4.9 just as I finished the above post and whilst I was thinking I should disable OTA updates using KFFA!
flip. This is turning into hard work. lol, still I know how to do it now.

I was having many issues after the last OTA and got mine to cm-11-20140609-SNAPSHOT-M7 last night. Mine was at 7.4.9 also. I followed rootjunky youtube videos to get mine re-rooted, flashed and working. After getting it rooted, he uses Fire Flash app to put twrp on the Kindle. I deviated a little and put the twrp 2.7.0.0 version other than that, I followed to a T. Once I got all that done, I went on the internet to Hashcode's repository and downloaded the newest cm-11 UNOFFICIAL he had listed directly to the device. I downloaded the latest Gapps from cyanogenmod and then booted into recovery(twrp) and installed. Everything is working beautifully now. Everything seems faster and smoother so far. I did go ahead and do an update from the about area in the settings to cm-11-20140609-SNAPSHOT-M7. I was also able to get all my books that I had purchased through kindle in the kindle reader.

greg2074 said:
I was having many issues after the last OTA and got mine to cm-11-20140609-SNAPSHOT-M7 last night. Mine was at 7.4.9 also. I followed rootjunky youtube videos to get mine re-rooted, flashed and working. After getting it rooted, he uses Fire Flash app to put twrp on the Kindle. I deviated a little and put the twrp 2.7.0.0 version other than that, I followed to a T. Once I got all that done, I went on the internet to Hashcode's repository and downloaded the newest cm-11 UNOFFICIAL he had listed directly to the device. I downloaded the latest Gapps from cyanogenmod and then booted into recovery(twrp) and installed. Everything is working beautifully now. Everything seems faster and smoother so far. I did go ahead and do an update from the about area in the settings to cm-11-20140609-SNAPSHOT-M7. I was also able to get all my books that I had purchased through kindle in the kindle reader.
Click to expand...
Click to collapse
Nice to know. Think I'll be doing something very similar, now I've made backups of 7.4.9 "just in case". Just have to go through all the above again!

[Q&A] [BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [05/27 CM11/TWR

[Q&A] [BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [05/27 CM11/TWR
Q&A for [BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [05/27 CM11/TWRP 2.7.x.x]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [05/27 CM11/TWRP 2.7.x.x]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Do I have to install the CM 11?

stuck after TWRP
I've run into a wall. I can get the Kindle to boot with stock OS with TWRP 1.7.0.0 installed but when I try to flash CM11 and GAPPS the kindle crashes. It will boot with the blue logo, then 1 of 2 things happen. Either in just hangs indefinately or after about 2-3 minutes the screen turns to "snow". When i reboot into TWRP, I find that all my data is gone. I flashed the system.img with the stock img and upon booting it says data corrupt and the kindle doesn't respond to adb. I then fastboot with the Skorpn cable, reflash the boot, recovery, system images, and i will go into a bootloop (stock logo, screenflash, stock logo, screen flash, and so on). So I then go through the steps of http://forum.xda-developers.com/showthread.php?t=2128848 by flashing u-boot-prod-7.2.3, freedom-boot-7.2.3, twrp-2.7.0.0. And then i believe I reflashed the stock boot, recovery, system images again which got me back to booting up into stock os (no blue logo when booting). I have gone through this process a few times with minor tweaks like going through the steps of the above thread using freedom-boot-7.4.6, and trying the freedom-boot and twrp-2.3.3.0 that came with KFFirstAide. All to no avail, and I go throught the long and seemingly redundant steps to get back to 7.2.3 stock-ish.
More background info if it helps:
I have the kindle fire HD 7" tate. It is rooted, and currently running on 7.2.3 (downgraded from 7.5.1). The boot, recovery, and system images i'm using came from the KFHD_SRT_v1.3.0 download.
When I try to flash the TWRP-2.3.3.0 that came with KFF, I can't seem to boot into the TWRP interface.
The CM version i've been trying is cm-11-20150112-NIGHTLY-tate with gapps-kk-20140105-signed. This is the step that kills my kindle.
According to TitaniumBackupPro I have only 43.1MB free in system ROM which may be an issue. I believe the low ROM space attributed to issues I had earlier in trying to downgrade via the KFF application. The script would error when trying to flash the images saying something of a max download size and would not flash. I was able to manually flash SRT v1.3.0 images via fastboot commands.
All help would be much appreciated. If there is any other info you need, I will be sure to do my best in providing it. I like tinkering, but am the type of person who learns by screwing things up haha.
EDIT: Also another thing that I have noticed when i get to the step just before trying to install cm11. When starting the kindle up after flashing u-boot.bin, freedom-7.2.3, TWRP-2.7.0.0... When i boot, the starting fire logo starts orange, goes blue, then turns orange again. I can enter TWRP from boot with the vol down button, and stock OS runs fine. I don't know if the orange > blue > orange is common or an indicator of anything. Downloading the newer cm-11-20140606 now and I am probably going to give that a go soon. Fingers crossed.

Kindle Fire "Tate" 2nd Bootloader plus TWRP issues
Hello,
first post, so i'll shoot away instantly I'm about to proceed with 2nd bootloader install (freedom boot) and TWRP. But: The files in user Hashcode's original post seem to be gone. Anyone ideas? Which leads to my second question: I'm on system version 7.4.5. - is it ok to use the 7.4.6 freedom bootloader, or should I do something different?
Thanks, much appreciated!

I have a similar question to the post above.
I have all the files needed to install the 2nd bootloader on 7.4.6, but my kindle is on 7.2.3 (rooted). Goo.im is down so i have no access to any of Hashcodes other files, i cant find a 7.2.3 freedom image.
If i were to go ahead and install (via fireflash) the 2nd bootloader with 7.4.6 files on my 7.2.3 kindle, i assume that it will not boot, but will twrp be installed properly?? If it does, i can forego booting into stock and go straight to installing a custom rom.

Jaa-Yoo said:
I have a similar question to the post above.
I have all the files needed to install the 2nd bootloader on 7.4.6, but my kindle is on 7.2.3 (rooted). Goo.im is down so i have no access to any of Hashcodes other files, i cant find a 7.2.3 freedom image.
If i were to go ahead and install (via fireflash) the 2nd bootloader with 7.4.6 files on my 7.2.3 kindle, i assume that it will not boot, but will twrp be installed properly?? If it does, i can forego booting into stock and go straight to installing a custom rom.
Click to expand...
Click to collapse
in the meantime, a member in the main thread posted files, which are 7.4.6 freedom boot and twrp 2.8.something. i just took these 2 files and flashed them right away via fireflash 1.1. after that flashing the latest CM11 nightly build was a normal go, without any issues. google apps can be flashed too, all at once out from TWRP. I read here, that your original system version should be equal OR lower than the version of freedom boot. Again as always: your choice, your responsibility

Thanks, i went ahead with installing the 2nd bootloader along with twrp. Rebooted into recovery and installed cm11, all went well.

2nd-bootloader for Custom ROMs on KFireHD 7" - Goo.im File Missing
Thank you only1kowalski and Jaa-Yoo

Jaa-Yoo said:
Thanks, i went ahead with installing the 2nd bootloader along with twrp. Rebooted into recovery and installed cm11, all went well.
Click to expand...
Click to collapse
no probs
---------- Post added at 08:37 AM ---------- Previous post was at 08:28 AM ----------
N3OMOD said:
Thank you only1kowalski and Jaa-Yoo
Click to expand...
Click to collapse
Did it work for you, as well? Glad to hear! If I'm correct, there may be issues, if the original system version on the KFHD7 is higher than the freedom boot one. Again, I also read somewhere here on the site, that somebody was successful in flashing with a lower version of the 2nd bootloader.

I've managed to successfully downgrade from OS 7.5.1 to OS 7.2.3 on a Kindle Fire HD 7" (2012 edition) prior to installing CM 11 with the following files:
kfhd7-freedom-boot-7.4.6.img
kfhd7-twrp-2.8.3.0-recovery.img
kfhd7-u-boot-prod-7.2.3.bin
fireflash11.apk
Just one side-note: TWRP 2.8.3.0 has a minor "graphical glich" on boot leading to grey area above the KindleFire logo (the blue one to be exact, the one leading to recovery) which appears for a few seconds before the device actually enters the TWRP. After that everything works correctly, but at first boot one might get "scared" by this thing.
Also please consider that after installing TWRP for the first time the loading time is significantly higher than what described on tutorials: my device took 9 minutes to first-boot into TWRP. But again, this happens only on first time.

Fine it worked out for you. BTW, I got this strange glitch at startup as well, when booting into TWRP. At first, I thought to myself "nice buddy, 1st brick". But then again, it would be intrresting to know what is causing this. Maybe the different system version to the freedom boot version?

only1kowalski said:
At first, I thought to myself "nice buddy, 1st brick".
Click to expand...
Click to collapse
This was exactly my first thought too! But luckly everything went well.
I suppose this may be due to the new version of TWRP or, ad you suggested, to the different freedom bot. Apart from being fastidious tough it did not compromise the functionality.
It would be nice to find the previous version of freedom bot just to verify if the problem was still present.

yeah, you're right. but since the site hosting these files is seemingly down and will be from what i can see, we might not get a hand on this so quick. nevertheless, the kfhd7 runs like an arrow with this os and i'm glad i did the switch from its original os. kudos to the developer(s) !

I've had my kfhd 7 for a few years. It is a tate device and rooted already, version shows 7.2.3. I've finally decided to install a custom rom but discovered goo.im is down and I can't get the kfhd7-u-boot-prod-7.2.3.bin file. Based on prior device modding experience I'm assuming this is meant to downgrade higher version software to this point in order to install twrp. Is that correct? Do I not need that file since I"m already on 7.2.3?
edit: looked through Q&A and found my answer. I should probably get better at using xda...

Bump on the request for a kfhd7-freedom-boot-7.2.3.img mirror, as goo.im is still down, please!
All i need is that file!

Sorry - google translate ))
Tell me how to set the custom 2nd bootloader to kindle fire hd 7 1gen (7,5,1 firmware, Root)? I always catch a red screen and have to constantly rebuild the boot
Sequence:
I downloaded the files 7,4,6 boot, 2,8,3,0 recovery files and the file 'stack'. Then, I put them in a directory with adb.
I launch a cmd and start typing commands:
adb push stack / sdcard /
adb shell su -c "dd if = / sdcard / stack of = / dev / block / platform / omap / omap_hsmmc.1 / by-name / system bs = 6519488 seek = 1"
_________________________________________________________
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" (here the periods that the device gives busy with something, and only a reboot helps
____________________________________________________________
adb shell
su
reboot bootloader
_____________________
fastboot -i 0x1949 flash boot kfhd7-freedom-boot-7.4.6.img
fastboot -i 0x1949 flash recovery kfhd7-twrp-2.8.3.0-recovery.img
fastboot -i 0x1949 reboot
___________________________________________
and after all the red screen and hi-service cable ((
6th point missed as there is no where to download from and the possible need to downgrade the firmware.
Please write how to do for firmware 7.5.1 and please give links to the necessary files.

Update TWRP
Hello
Im trying to udate twrp from 2.6.3.1. to this version (2.7.0). Im guessing that 2.7.0. is ther version to install the cm12.1 nighty.
From another topic of the forum I have read that I could use fireflash to do that. Could you tell me where could I get the twrp files and where should I place it to use fireflash?Do I need to use a fastboot cable, adb... or just fireflash to update it? All the instructions will be well received.
Thanks a lot!
Regards

Possibly bricked my tablet... rooted it and then used the fastboot instructions in this thread to install the stack overflow, the kfhd7-freedom-boot-7.4.6.img, kfhd7-freedom-boot-7.4.6.img, kfhd7-freedom-boot-7.4.6.img. The fastboot on the device showed that it was working and it appeared to be just fine until i rebooted it and now it won't turn on. Any advice on how to begin troubleshooting it?

Anyone looking for fireflash apk file could try:http://www.tekify.co.uk, he has a video on how to install twrp using fireflash on YouTube.This is for the kindle fire HD 2012 model
If you want to update twrp using fireflash,you have to be on the kindle stock OS ,to change the twrp version you have to tap on recovery image not flashed grey button and go to where you have your twrp IMG downloaded,tap on it, and the not flashed button should change to details about your twrp update, you must tick the button Disable recovery update before pressing the flash,install script button,I used fireflash to update twrp, but I couldn't use the swipe function, so I used fireflash to switch back to an earlier version of twrp.

Kindle Fire HD bricked to Fastboot only.
Hey I was told to post here. I am visiting a member of my family and their Kindle Fire "Broke". It seems as if its bricked to fastboot mode only, as when you power it on, the kindle fire logo shows up and then very quickly swaps to the Fastboot logo. Im not too big on kindle stuff so so far I havent gotten anywhere and am having trouble. They wouldnt have rooted, enabled ADB, or done anything beyond vanilla kindle stuff. ADB wont recognize the device on my computer and nothing works on the device to get it into recovery or anything besides fastboot. I am using the stock cable but I have also tried multiple cables and USB ports and restarting computer and kindle. Not sure how to proceed as it seems like theres no way I can communicate with the device.

[Recovery] [vk810] [2015-07-05] TWRP 2.8.7.0

Install Instructions:
You will need root.
With custom recovery already installed.
Download
Place zip file on phone
Reboot into recovery
Flash zip file through recovery
Reboot
With stock recovery - Need ADB installed.
Download zip file
Extract recovery.zip to your device's SD Card, not external but internal memory.
Open terminal window/command prompt to execute following commands
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
You should be in your updated recovery now
Download:
Download HERE
Sources:
My GitHub
Credits:
@Dees_Troy
TeamWin
Everyone involved with TWRP.

I see you used v500 repos as a base for this. If you want, I could try to make it official so we have the three variants of LG G Pad 8.3 supported on the same place: https://twrp.me/devices/lggpad83.html
EDIT: Where does the prebuilt kernel in your sources come from? LG official lollipop rom (35A)?

fefifofum said:
I see you used v500 repos as a base for this. If you want, I could try to make it official so we have the three variants of LG G Pad 8.3 supported on the same place: https://twrp.me/devices/lggpad83.html
EDIT: Where does the prebuilt kernel in your sources come from? LG official lollipop rom (35A)?
Click to expand...
Click to collapse
Sure, make it official. Thanks!
Yes the kernel came from the 35A stock ROM.
Trying to get TWRP to work on 5.0.2 but having some issues with the boot chain. Looks like LG changed something...

Thanks @AndroidUser00110001! Just wanted to report that it works 100% on a backup and restore of the stock 5.0.2 (with the known caveat of having to flash the old aboot to get into TWRP and then reflash the 5.0.2 aboot to get back into the ROM).

roirraW "edor" ehT said:
Thanks @AndroidUser00110001! Just wanted to report that it works 100% on a backup and restore of the stock 5.0.2 (with the known caveat of having to flash the old aboot to get into TWRP and then reflash the 5.0.2 aboot to get back into the ROM).
Click to expand...
Click to collapse
Thanks! Ran into that issue myself and was like WTF?
We had similar issues on the G2 going from JB to KK. Time permitting I am going to look into a solution so we don't have to do the aboot trick.

AndroidUser00110001 said:
Sure, make it official. Thanks!
Yes the kernel came from the 35A stock ROM.
Trying to get TWRP to work on 5.0.2 but having some issues with the boot chain. Looks like LG changed something...
Click to expand...
Click to collapse
Well, it seems @invisiblek already submitted a device repo to build twrp for the vk810, so I won't be taking care of that model. Now it's up to him to get official twrp support for the vk810 (or let someone else do it).

fefifofum said:
Well, it seems @invisiblek already submitted a device repo to build twrp for the vk810, so I won't be taking care of that model. Now it's up to him to get official twrp support for the vk810 (or let someone else do it).
Click to expand...
Click to collapse
Yeah...I believe his works with CM sources by replacing the bootable folder with Omni sources. I am too OCD at times so kept it simple to just Omni sources...

Sorry, when I had read about making it official, this was the first thing I thought of, from Thumb Wars:
https://www.youtube.com/watch?v=R1NEKS4nfmk

roirraW "edor" ehT said:
Sorry, when I had read about making it official, this was the first thing I thought of, from Thumb Wars:
https://www.youtube.com/watch?v=R1NEKS4nfmk
Click to expand...
Click to collapse
I ain't kissing anyone
...unless it is a hot chick to make it official

Do i need to do the aboot trick or can i just flash?

sporty377 said:
Do i need to do the aboot trick or can i just flash?
Click to expand...
Click to collapse
If you don't already have the 4.2.2 aboot on your VK810, then yes you need it. If you already put TWRP on your tablet and it's working now, then you can just flash the new TWRP zip file from your old TWRP, then choose "Reboot Recovery" in TWRP to get into the new one.

<deleted>

dang i could have sworn i had twrp recovery on my vk810 still so i flashed the 4.2.2 aboot to upgrade to this newer twrp then i rebooted it just went to fastboot so i tried to adb the 35a aboot so it would boot but my pc win10 adb says no device iv installed the drivers.. what in the world damn it..

4218kris said:
dang i could have sworn i had twrp recovery on my vk810 still so i flashed the 4.2.2 aboot to upgrade to this newer twrp then i rebooted it just went to fastboot so i tried to adb the 35a aboot so it would boot but my pc win10 adb says no device iv installed the drivers.. what in the world damn it..
Click to expand...
Click to collapse
You installed the Verizon specific LG drivers?
Try rebooting the PC? Using the original USB cable with a USB 2.0 (not 3.0) port? In Device Manager, is your VK810 listed? If it's not listed, that's the problem. It can take up to 10 minutes to load the driver you installed the first time you plug the tablet into a different USB 2.0 port on the PC, or on a new Windows installation.
Until you can see it in Device Manager, you won't be able to talk to it via ADB.
Good luck!

Hi,
I tried to do what you said in instruction but I have an error. I exctracter META-INF folder and recovery.img file to my sdcard root.
This is the error:
-------------------------------
Secure booting Error!
Cause: boot certification verify
---------------------------------
These are the terminal output of my commands (your commands actually )
Code:
[email protected]:~$ adb devices
List of devices attached
VK8104G509288a0 device
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recov>
dd: /dev/block/platform/msm_sdcc.1/by-name/recovery: No space left on device
49153+0 records in
49152+0 records out
25165824 bytes transferred in 3.383 secs (7438907 bytes/sec)
1|[email protected]:/ # dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/>
25332+1 records in
25332+1 records out
12970000 bytes transferred in 2.560 secs (5066406 bytes/sec)
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb reboot recovery

msaiducar said:
Hi,
I tried to do what you said in instruction but I have an error. I exctracter META-INF folder and recovery.img file to my sdcard root.
Click to expand...
Click to collapse
Look at my stickied thread in the General section (also linked in my signature below).
You have to downgrade your bootloader to 4.2.2 first and use the loki hack to install the initial version 2.7.0.1 of TWRP, then upgrade to this version from the old one.
Instructions in my thread.

Hi @roirraW "edor" ehT,
I noticed that after my reply. Sorry for that. Now my other problem is, I use Ubuntu 15.10 on my pc and I don't know how to downgrade without Lg Flash Tool. I tried to run Lg Tool with wine, but it didn't work. Is it possible to downgrade VK810 with ubuntu?

msaiducar said:
Hi @roirraW "edor" ehT,
I noticed that after my reply. Sorry for that. Now my other problem is, I use Ubuntu 15.10 on my pc and I don't know how to downgrade without Lg Flash Tool. I tried to run Lg Tool with wine, but it didn't work. Is it possible to downgrade VK810 with ubuntu?
Click to expand...
Click to collapse
No, but I assumed you were already rooted since you were trying to install TWRP. If you are already rooted you can skip to the step in my instructions about installing the initial v2.7.0.1 version of TWRP, which doesn't require a computer.
The main aim of downgrading is to make it the easiest to root and install TWRP, but as long as you're rooted you can still downgrade just your bootloader in order to use the Loki'd TWRP install.

Yes, I rooted my 5.0.2 VK810 via KingRoot app. But I'm new about all these stuff. How can I downgrade just bootloader?
---------- Post added at 11:35 PM ---------- Previous post was at 10:40 PM ----------
I, finally, understood whats going on and could manage to follow instructions. Now, I have a tablet that has no amazon and verizon apps Thank you @roirraW "edor" ehT

msaiducar said:
Yes, I rooted my 5.0.2 VK810 via KingRoot app. But I'm new about all these stuff. How can I downgrade just bootloader?
---------- Post added at 11:35 PM ---------- Previous post was at 10:40 PM ----------
I, finally, understood whats going on and could manage to follow instructions. Now, I have a tablet that has no amazon and verizon apps Thank you @roirraW "edor" ehT
Click to expand...
Click to collapse
You're welcome!

[CUSTOM RECOVERY] Cyanogen Recovery (2015-11-04)

Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before using it! YOU are choosing to make these modifications.
Notes
- The recovery cannot boot if flashed to the recovery partition instead it must be booted via fastboot using:
Code:
fastboot boot recovery.img
- The reason it cannot be flashed is that the bootloader is signature checking the flashed image against Amazon's RSA keys.
- External sdcard is not accessible from the recovery at the moment - will fix
- The touchscreen panel is not usable at the moment - instead use the volume up/down keys to navigate and power button to select
- The volume up/down keys are swapped - will fix this
- Apply update from internal memory and sideload are working.
- This is a basic recovery - it has no backup or restore function
- This does the job until TWRP is available
Download
- Amazon Fire Cyanogen Recovery
XDA:DevDB Information
Cyanogenmod Recovery, Tool/Utility for the Amazon Fire
Contributors
ggow
Version Information
Status: Beta
Created 2015-11-04
Last Updated 2015-11-06

So what can we sideload and cannot? And the amzn rsa is located in /system/vendor/data. Now I'm wondering if someone still has the rsa bug from the hdx the old one and we can replace that with that file and try unlocking the bootloader.

Awesomeslayerg said:
So what can we sideload and cannot? And the amzn rsa is located in /system/vendor/data. Now I'm wondering if someone still has the rsa bug from the hdx the old one and we can replace that with that file and try unlocking the bootloader.
Click to expand...
Click to collapse
- Pretty much anything we want to sideload, we can
- I have sideloaded:
Official Amazon Firmware
SuperSU.zip
Modified Gapps Package.zip
Xposed​- CVE-2014-0973 (the vulnerability which was exploited on the HDX) is patched in the Fire's bootloader

ggow said:
- Pretty much anything we want to sideload, we can
- I have sideloaded:
Official Amazon Firmware
SuperSU.zip
Modified Gapps Package.zip
Xposed​- CVE-2014-0973 (the vulnerability which was exploited on the HDX) is patched in the Fire's bootloader
Click to expand...
Click to collapse
Oh ok. So we can try sideload in or flashing a custom image now?

Awesomeslayerg said:
Oh ok. So we can try sideload in or flashing a custom image now?
Click to expand...
Click to collapse
Yes, we can flash a custom rom

ggow said:
Yes, we can flash a custom rom
Click to expand...
Click to collapse
And the bootloader won't recognise the different Rom? I have heard on some devices if you install a different ROM then it doesn't go past the bootloader.
Sent from my XT912 using Tapatalk

Vlasp said:
And the bootloader won't recognise the different Rom? I have heard on some devices if you install a different ROM then it doesn't go past the bootloader.
Sent from my XT912 using Tapatalk
Click to expand...
Click to collapse
- The bootloader has no knowledge of the Android ROM AFAIK
- We have to bear in mind that we are limited to the stock boot.img therefore
- Any rom we produce should be based off the stock boot.img
- If we did base the ROM off a custom kernel then we would have to "fastboot boot" the custom_boot.img each boot or reboot - so this is not feasible in terms of user experience.
- On the HDX, when it was a locked device I was able to boot AOSP in this manner

ggow said:
- The bootloader has no knowledge of the Android ROM AFAIK
- We have to bear in mind that we are limited to the stock boot.img therefore
- Any rom we produce should be based off the stock boot.img
- If we did base the ROM off a custom kernel then we would have to "fastboot boot" the custom_boot.img each boot or reboot - so this is not feasible in terms of user experience.
- On the HDX, when it was a locked device I was able to boot AOSP in this manner
Click to expand...
Click to collapse
We should be able to use custom boot.img when we get safestrap, right?
Sent from my KFFOWI using Tapatalk

ggow said:
- Pretty much anything we want to sideload, we can
- I have sideloaded:
Official Amazon Firmware
SuperSU.zip
Modified Gapps Package.zip
Xposed​- CVE-2014-0973 (the vulnerability which was exploited on the HDX) is patched in the Fire's bootloader
Click to expand...
Click to collapse
I'm actually interested in that modified gapps package... I'd like to keep the gapps as system apps properly.
Do you mind sharing which gapps package did you use and what modification you did?

this works on t he 50$ fire tab?

patt2k said:
this works on t he 50$ fire tab?
Click to expand...
Click to collapse
This is FOR it dummy

stkpxl said:
Is it possible to flash the OpenGApps package? I usually stick with the Pico one and install apps from there.
Click to expand...
Click to collapse
inscythe said:
I'm actually interested in that modified gapps package... I'd like to keep the gapps as system apps properly.
Do you mind sharing which gapps package did you use and what modification you did?
Click to expand...
Click to collapse
- Yes, I'll post it shortly
- I have only flashed it so far with no testing
- My Fire hasn't been online yet because I haven't blocked OTA updates yet
- Will test and provide a link for download
EDIT: Good news the Gapps package works with full play store functionality
I'll upload it and post a link in the General Section

Vlasp said:
We should be able to use custom boot.img when we get safestrap, right?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
- I started investigating this and Safestrap may not be possible
- Safestrap is usually for locked devices granted, however...
- Even if it were possible our kernel doesn't have kexec capabilities
- As with other amazon devices we really need a way to unlock the bootloader.

Modified Open Gapps Package
inscythe said:
I'm actually interested in that modified gapps package... I'd like to keep the gapps as system apps properly.
Do you mind sharing which gapps package did you use and what modification you did?
Click to expand...
Click to collapse
stkpxl said:
Is it possible to flash the OpenGApps package? I usually stick with the Pico one and install apps from there.
Click to expand...
Click to collapse
- I have posted the Modified Open Gapps package here.
- Tested and seems to be working fine.

ggow said:
- I have posted the Modified Open Gapps package here.
- Tested and seems to be working fine.
Click to expand...
Click to collapse
Very nice will have to play around with this later have this tablet for my grandma so at least with root and custom launcher I can make it easier to use at least

ggow is the ****ing bomb!
Between all your work on the FirePhone and this tablet, tell me what I owe you!

Moogagot said:
ggow is the ****ing bomb!
Between all your work on the FirePhone and this tablet, tell me what I owe you!
Click to expand...
Click to collapse
Your first born maybe?

If someone wouldn't mind explaining the process of getting this recovery in my tablet. I' mused to flashing on my phone. Thanks

sandman512 said:
If someone wouldn't mind explaining the process of getting this recovery in my tablet. I' mused to flashing on my phone. Thanks
Click to expand...
Click to collapse
No problem. You can find instructions here.

sandman512 said:
If someone wouldn't mind explaining the process of getting this recovery in my tablet. I' mused to flashing on my phone. Thanks
Click to expand...
Click to collapse
you need adb and fastboot files
several options there are some basic information in my Amazon Fire Index
Fire Index: Which Amazon (Kindle) Fire Do I have?
once you have adb setup
boot Fire into fastboot mode: power off, Hold volume down, power on
if it boots to recovery select bootloader
once in fastboot mode check device manager Fire should be listed as Android adb interface
If so you should test fastboot commands with
Code:
fastboot -i 0x1949 getvar product
should get this back
Code:
ford
if so
place recovery.img in the same location as listed in command prompt
then boot recovery.img with
Code:
fastboot boot 2015-11-04-cm-12-recovery.img
Sent from my KFFOWI using Tapatalk