I booted TWRP recovery onto kindle fire 2
- Thread starter powerpoint45
- Start date
mindmajick
Account currently disabled
I wish that was a real college
Me too bro! Me too.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I just put a switch between pins 1 and 4
Sent from my Amazon Kindle Fire2 using xda app-developers app
just an interrupt within the general 1-4 connection...
Xdacollege is pretty awesome. Been checking it out. Currently working on an actual degree in computer and software programming with a focus on linux operating systems. So I'm hoping to be making some pretty sweet stuff myself
Similar threads
- Sticky
Top Liked Posts
-
There are no posts matching your filters.
-
5hey guys! Using a factory cable I got into fastboot. Once in fastboot I downloaded TWRP image for the kindle fire 1 http://techerrata.com/file/twrp2/blaze/openrecovery-twrp-2.3.3.1-blaze.img then I typed
Code:fastboot -i 0x1949 boot Downloads/openrecovery-twrp-2.3.3.1-blaze.img
but after doing that it just booted back into fastboot so then I did the same thing but right after the image got downloaded onto the device, I entered the command again and it booted right into TWRP. It takes a few tries but it works. Touch points all work but I am not sure about anything else. Hope this helps with further development.
https://www.youtube.com/watch?v=5dL_QxFVRtc4* PLEASE DONT TRY ANYTHING UNLESS YOU OWN AND UNDERSTAND HOW TO USE A FASTBOOT CABLE. ALSO MAKE BACKUPS OF THE STOCK PARTITIONS IN CASE OF DISASTER RECOVERY *
Regarding building a TWRP for KFire2:
I replied in a PM but thought that maybe the information could also be used by the general KFire2 population.
recovery.fstab:
This is close. But, sdcard is handled very differently on otter2 (KFire2). Try this instead:
Code:/sdcard datamedia /dev/null /data ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata /cache ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache /system ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/system /boot emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/boot /recovery emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
I took the liberty of removing "dangerous" partitions from the list.
Now I don't think you'll want to actually flash anything other than: data/cache/system. As it will most definitely break the signature checking on the partition.
That being said, I am working on a long-term goal of supporting both kf1 and kf2 via a 2nd-bootloader and some adjustments to the current bootloader that the kf1 uses (IE: allow it to load the signed kernel/recovery partitions which are needed for kf2)
And changes to BoardConfig.mk
Also,
Make sure you have these options set in BoardConfig.mk (some may already be there which is ok):
Code:TW_NO_REBOOT_BOOTLOADER := true TW_NO_REBOOT_RECOVERY := true TW_INTERNAL_STORAGE_PATH := "/data/media" TW_INTERNAL_STORAGE_MOUNT_POINT := "data" RECOVERY_SDCARD_ON_DATA := true TW_ALWAYS_RMRF := true TARGET_USERIMAGES_USE_EXT4 := true3Hey guys! Just wanted to show you the tests that were done yesterday with Hashcode. We are testing a boot image made by Hashcode. A custom recovery was built by hashcode but we never got it to boot...
Test 1: https://www.youtube.com/watch?v=Af2QeTZSgyI&feature=youtube_gdata_player
Test 2:https://www.youtube.com/watch?v=TtT4BoHQLOM&feature=youtube_gdata_player
Test 2 boot selection https://www.youtube.com/watch?v=4fWVPBygQSA&feature=youtube_gdata_player
Test 3https://www.youtube.com/watch?v=ozr_62ssVkw&feature=youtube_gdata_player3Last night we fixed the following:
*audio
*adb
*MTP
*video (not HD)
*boot loader bug Fix's
