[Q] Bootloader problem

[stunts513]

Yes, yes, and vice versa. Its more flexible to have twrp access than fastboot. Twrp has access to a command line operating system while fastboot only has flashing and such capabilities. So twrp ftw.

Sent from my LG-P769 using Tapatalk

 

[rocketfans14]

Yes, yes, and vice versa. Its more flexible to have twrp access than fastboot. Twrp has access to a command line operating system while fastboot only has flashing and such capabilities. So twrp ftw.

Sent from my LG-P769 using Tapatalk

Ok, so I have backed up and wiped internal memory. I see that everything within /sdcard is gone so I used adb push to push the rom and gapp into the folder. Went into install and flashed both zip files. Reboot but it went into TWRP recovery. Did I miss a step? Or should I proceed to restore the device and start from the beginning again?

 

[stunts513]

Lemme ask hashcode when I get back home and i'm in the irc.

Sent from my LG-P769 using Tapatalk

---------- Post added at 06:53 PM ---------- Previous post was at 06:06 PM ----------

I haven't gotten a reply yet but i have another theory, it goes straight to twrp after the blue logo right? I'm wondering if somehow the bootmode is stuck in recovery, haven't really seen this happen since kf1. This is all just theory. As a test can you use run this command while in twrp from your pc?

adb shell reboot bootloader

tell me if it goes into fastboot, if it does then great, if not then i'm going to be a little bit on the wtf side.

 

[rocketfans14]

Lemme ask hashcode when I get back home and i'm in the irc.

Sent from my LG-P769 using Tapatalk

---------- Post added at 06:53 PM ---------- Previous post was at 06:06 PM ----------

I haven't gotten a reply yet but i have another theory, it goes straight to twrp after the blue logo right? I'm wondering if somehow the bootmode is stuck in recovery, haven't really seen this happen since kf1. This is all just theory. As a test can you use run this command while in twrp from your pc?

adb shell reboot bootloader

tell me if it goes into fastboot, if it does then great, if not then i'm going to be a little bit on the wtf side.

I tried typing that in cmd before I push the zip files previously but it didn't have any effect so I just used the reboot into bootloader option from TWRP itself. I was looking at other threads and posts and it really resembled to what some people said, the bootloop and had something to do with the bootmode. I did see that 'bootmode' was an option during the blue logo so when I selected that, it went to the cyanogenmod logo and into the android interface. However, to test if it was working normally (which I really hoped so), I turned it off and on again and this time, without having to manually select bootmode on the blue logo screen.And you know what, it went back into TWRP. So I think it is what you are saying, the bootmode stuck in recovery.

 

[stunts513]

I tried typing that in cmd before I push the zip files previously but it didn't have any effect so I just used the reboot into bootloader option from TWRP itself. I was looking at other threads and posts and it really resembled to what some people said, the bootloop and had something to do with the bootmode. I did see that 'bootmode' was an option during the blue logo so when I selected that, it went to the cyanogenmod logo and into the android interface. However, to test if it was working normally (which I really hoped so), I turned it off and on again and this time, without having to manually select bootmode on the blue logo screen.And you know what, it went back into TWRP. So I think it is what you are saying, the bootmode stuck in recovery.

Wait, so you got it to sucessfully boot up but you have to tell it to boot off the system partition everytime instead of just booting like a normal kindle?

 

[rocketfans14]

Wait, so you got it to sucessfully boot up but you have to tell it to boot off the system partition everytime instead of just booting like a normal kindle?

Yes, I can boot it into the android interface but I can't just let it run itself normally without selecting bootmode.

 

[stunts513]

*facepalm*

i can throw a guess it has something to do with the ota from cm. i don't understand how cm sends a message to tell it to update, i thought maybe it was just if twrp detected a zip in the /cache it automatically would attempt to flash it but if it doesnt work that way its possible somethign was stored on a partition that i don't know of that could be making the bootloader thing it needs to ota everytime it boots up hence the manual selection. This is just a guess at best, if the idme command hadn't been considered legacy or osmethign of the like i would get you to use "su -c idme print" from a adb shell to see what it says but you would have to flash back to amazon os again and its a pain because you need to wipe all the selinux xattribs from data or the amazon kernel wil freak out as it was pre-selinux. If you don't have much on there its not that big of a pain but given your circumstance i think it would be better to not flash back to amazon os. Leave it like it is for now and maybe i will find a solution. Atleast for now its just a minor inconvenience, as long as it isnt shut of its not a big bother right?

 

[rocketfans14]

*facepalm*

i can throw a guess it has something to do with the ota from cm. i don't understand how cm sends a message to tell it to update, i thought maybe it was just if twrp detected a zip in the /cache it automatically would attempt to flash it but if it doesnt work that way its possible somethign was stored on a partition that i don't know of that could be making the bootloader thing it needs to ota everytime it boots up hence the manual selection. This is just a guess at best, if the idme command hadn't been considered legacy or osmethign of the like i would get you to use "su -c idme print" from a adb shell to see what it says but you would have to flash back to amazon os again and its a pain because you need to wipe all the selinux xattribs from data or the amazon kernel wil freak out as it was pre-selinux. If you don't have much on there its not that big of a pain but given your circumstance i think it would be better to not flash back to amazon os. Leave it like it is for now and maybe i will find a solution. Atleast for now its just a minor inconvenience, as long as it isnt shut of its not a big bother right?

That sounds like a lot of work.. Yeah,other than manual boot, nothing else seems to bother me and it's working normally. For now, I guess I should refrain from updating?

 

[stunts513]

Hmm an update might actually fix it. Just a theory as I don't know the process, you can try updating to a nightly if you want, it might kick it out of doing that. You can always restore it again if it doesn't want to boot.

Sent from my Amazon Tate using Tapatalk

 

[rocketfans14]

Hmm an update might actually fix it. Just a theory as I don't know the process, you can try updating to a nightly if you want, it might kick it out of doing that. You can always restore it again if it doesn't want to boot.

Sent from my Amazon Tate using Tapatalk

I am currently on the 140508 nightly. Last time, I tried to update to the 140520 nightly but that was when I download it from the device itself and made the TWRP bootloop fuss. If I were to update to the latest one now, would it make a difference if I get the zip file from the site and drag it to /sdcard through the usb cable from my computer and flash it with TWRP?

 

[stunts513]

That probably won't fix it, I asked around and twrp basically checks the cache for a zip and a open recovery script, when you factory reset it it should have wiped the cache, you can still do that from advanced while if you want but I believe the culprit is your bootmode defaulting to the wrong value. I can't verify this without you wiping internal storage and flashing a amazon os zip from the dev section though.

If you flash back to amazon os I highly recommend not connecting to WiFi, an ota would be very bad if it got rid of second bootloader because Idk if you could force /system to boot. And that flashable zip I'm thinking of might be a kfhd7 zip which would be bad... Not sure if there is one for kf2.
Sent from my Amazon Tate using Tapatalk

 

[rocketfans14]

That probably won't fix it, I asked around and twrp basically checks the cache for a zip and a open recovery script, when you factory reset it it should have wiped the cache, you can still do that from advanced while if you want but I believe the culprit is your bootmode defaulting to the wrong value. I can't verify this without you wiping internal storage and flashing a amazon os zip from the dev section though.

If you flash back to amazon os I highly recommend not connecting to WiFi, an ota would be very bad if it got rid of second bootloader because Idk if you could force /system to boot. And that flashable zip I'm thinking of might be a kfhd7 zip which would be bad... Not sure if there is one for kf2.
Sent from my Amazon Tate using Tapatalk

Judging from the first part of your message, flashing a zip file to update through TWRP won't fix the bootmode value. But overall, this is still a theory unless I flash an amazon os?

About the second half of your post, I kinda get the ota through WiFi will most likely mess things up and how it might erase the second bootloader. But I have no idea which flashable zip you are talking about.

In conclusion, a possible solution to the bootmode issue is to update through the device itself and not flashing a zip of it? And if the device messes up again with booting into TWRP recovery only, I can try to fix it with wiping internal storage and flashing the rom and gapp again like before? Also, if I am brave enough and got nothing to do, another possible way to solve my problem is flashing back to amazon os?

Other than that, the safest option is to do nothing, leave it alone as it is, and enjoy having android on a kindle fire?

 

[stunts513]

Yea but I don't see a flashable zip lying around and if you use kffa you risk not being able to force booting into the os.

Sent from my LG-P769 using Tapatalk

 

[mindmajick]

Judging from the first part of your message, flashing a zip file to update through TWRP won't fix the bootmode value. But overall, this is still a theory unless I flash an amazon os?

About the second half of your post, I kinda get the ota through WiFi will most likely mess things up and how it might erase the second bootloader. But I have no idea which flashable zip you are talking about.

In conclusion, a possible solution to the bootmode issue is to update through the device itself and not flashing a zip of it? And if the device messes up again with booting into TWRP recovery only, I can try to fix it with wiping internal storage and flashing the rom and gapp again like before? Also, if I am brave enough and got nothing to do, another possible way to solve my problem is flashing back to amazon os?

Other than that, the safest option is to do nothing, leave it alone as it is, and enjoy having android on a kindle fire?

have you tried updating the bootmode via fastboot(this can also be done in the terminal with slightly different commands)? see post here:
http://forum.xda-developers.com/showthread.php?p=40339524

-》Sent from my mind to your screen.

 

[stunts513]

I think he tried it with adb, I would have recommended trying via fastboot but last I checked the bootloader values are different than on the kf1 and I always have a hard time finding where the values are posted on xda. I think I will bookmark that thread, thank you for that.

Sent from my LG-P769 using Tapatalk

 

[rocketfans14]

Update

Hey, haven't been back on here for a while but I would like to give an update on the device. So far, I haven't done any further changes nor any updates of the rom (still the nightly CM 11 from May 6th). The device doesn't boot into TWRP recovery anymore whenever I restart the whole thing. Thank you for all the help

Just a side question (which you can choose to ignore because it is probably not suitable in this thread because it is not about the bootloader), is there any support for OTG USB? I would like to be able to read files from an external flash drive directly on the tablet but I'm not sure if it is supported.

 

[stunts513]

Hey, haven't been back on here for a while but I would like to give an update on the device. So far, I haven't done any further changes nor any updates of the rom (still the nightly CM 11 from May 6th). The device doesn't boot into TWRP recovery anymore whenever I restart the whole thing. Thank you for all the help

Just a side question (which you can choose to ignore because it is probably not suitable in this thread because it is not about the bootloader), is there any support for OTG USB? I would like to be able to read files from an external flash drive directly on the tablet but I'm not sure if it is supported.

It isn't supported yet, it will be eventually but from what I heard it will require a powered USB hub to be attached because there's not enough power from the kindle by itself to power a external device.

Sent from my Amazon Tate using Tapatalk

 

[rocketfans14]

So...I finally updated to the newest nightly (July 3rd) and it happened again. After the download was complete and installation began after a reboot into TWRP, the device will only boot into TWRP recovery every single time unless you choose the third option (select bootmode) in the blue/white kindle logo screen. Should I assume in conclusion that the device will change the reboot path to TWRP everytime an update is installed?

 

[stunts513]

Possibly but I have no idea why it is doing this.