Okay, I've got a build of sailfish os 2.1.3.7 with a cm11 base for the 2012 kindle fire hd 7 tate. the only problem is that it boots right into fastboot. I saw a guy who tried to port this earlier and I simply figured it was typical wouldn't boot, but this is strange that it is behaving the exact same on two different bases and sfos versions. It boots right into fastboot, and I think it has something to do with the finnicky bootloader of the kindle fire. @Hashcode, I know its been a while since you've spared with the beast that is the 7 inch KFHD, but if there is a simple workaround you can think of, that'd be great.
Related
Hello everyone,
I just rooted my 2013 kindle fire hd 7'' tonight. Was having fun with it installed 1market, apex launcher, and root uninstaller. Well, i had the bright idea to de-amazon-ify my kindle by removing all stock kindle apps from my kindle with root uninstaller. unfortunately i deleted a package called "kindle system" or something along those lines and now it ts just blank when it boots up. kindle splash screen still shows as if booting normally.
Any way to fix this or am i bricked until a custom rom is out? i wish there was a way to flash to stock...
gregmay15 said:
Hello everyone,
I just rooted my 2013 kindle fire hd 7'' tonight. Was having fun with it installed 1market, apex launcher, and root uninstaller. Well, i had the bright idea to de-amazon-ify my kindle by removing all stock kindle apps from my kindle with root uninstaller. unfortunately i deleted a package called "kindle system" or something along those lines and now it ts just blank when it boots up. kindle splash screen still shows as if booting normally.
Any way to fix this or am i bricked until a custom rom is out? i wish there was a way to flash to stock...
Click to expand...
Click to collapse
it's dead.
you should have done your research before.It looks like you will be waiting for a long time,the 7'' HDX device is more popular among rom devs as they are fully functionnal tablets (as the pre-2013 HD models were), there might never be a genuine system recovery in the wild because of that.
that being said: you might have luck sending the device to amazon without disclosing what you did. Who knows
hopefully your story will serve as precautionnary tale to the G.P. around here, but I have doubts seeing how often those KFSOWI boot-looped stories come up.
kindle bricked
jonathanlyng said:
it's dead.
you should have done your research before.It looks like you will be waiting for a long time,the 7'' HDX device is more popular among rom devs as they are fully functionnal tablets (as the pre-2013 HD models were), there might never be a genuine system recovery in the wild because of that.
that being said: you might have luck sending the device to amazon without disclosing what you did. Who knows
hopefully your story will serve as precautionnary tale to the G.P. around here, but I have doubts seeing how often those KFSOWI boot-looped stories come up.
Click to expand...
Click to collapse
Already tried that. They wanted the serial number which conveniently is NOT physically on the back of the device. i need to actually get into the system to see what the serial number was. Thanks for the response though!
Try fastboot I believe you can use fastboot-getprop model to get information. abd may be able to accomplish something similar.
Sent from my KFSOWI using Tapatalk
I need help reviving a Nexus 7 2013 Flo 32G.
This tablet has sat forgotten and dead for a couple of years. I am trying to bring it back to life. It has been several years since I have done any rooting and flashing on Android, so I am looking for a little guidance. I honestly do not recall what has left the device in its current state. But, basically it has no OS installed. The boot-loader version is FLO-04.04. I can get into recovery. The installed recovery is TWRP v2.8.6.0. I do not possess any Windows machines. I have Android Debug Bridge version 1.0.39 installed on Ubuntu 16.04.3 LTS. MTP is enabled.
But that is it. I am not able to locate the device through ADB using ‘adb devices’. As I say it has been several years since I have rooted around Android or used ADB. I did not use Linux the last time I was doing things like this. So, I am stuck as to how to proceed. I was hoping it was going to be a pretty straightforward process of picking a ROM and GAPS and flashing.
Of course not even being able to ABD into the device leads me to believe that, while not in over my head, I made need some help going forward.
Anyone care to volunteer some first steps?
TIA
Wrong forum dude. This forum is for the 2012 Nexus 7, not the 2013 Nexus 7.
Wish39 said:
Wrong forum dude. This forum is for the 2012 Nexus 7, not the 2013 Nexus 7.
Click to expand...
Click to collapse
Oopsie daisy.
Thanks, I will repost in the proper forum!
drjboulder said:
Oopsie daisy.
Thanks, I will repost in the proper forum!
Click to expand...
Click to collapse
It's fine. People make mistakes sometimes.
Also it looks like something majorly screwed up your Nexus 7. Hope you find a solution to fix it up sooner or later.
drjboulder said:
I need help reviving a Nexus 7 2013 Flo 32G.
This tablet has sat forgotten and dead for a couple of years. I am trying to bring it back to life. It has been several years since I have done any rooting and flashing on Android, so I am looking for a little guidance. I honestly do not recall what has left the device in its current state. But, basically it has no OS installed. The boot-loader version is FLO-04.04. I can get into recovery. The installed recovery is TWRP v2.8.6.0. I do not possess any Windows machines. I have Android Debug Bridge version 1.0.39 installed on Ubuntu 16.04.3 LTS. MTP is enabled.
But that is it. I am not able to locate the device through ADB using ‘adb devices’. As I say it has been several years since I have rooted around Android or used ADB. I did not use Linux the last time I was doing things like this. So, I am stuck as to how to proceed. I was hoping it was going to be a pretty straightforward process of picking a ROM and GAPS and flashing.
Of course not even being able to ABD into the device leads me to believe that, while not in over my head, I made need some help going forward.
Anyone care to volunteer some first steps?
TIA
Click to expand...
Click to collapse
can you connect through fastboot?
My girlfriend bought a Fire 10 and now that she has opened it she is thinking her son would rather it be an Android. (He is autistic and does not deal with change well and his phone is Android but he has a dying iPad.) I found [ROM][unlocked][suez] Lineage-14.1 [26 SEP 2019] and I see this might be just what the doctor ordered but it is asking me to do a bunch of pre install items - Unlocked Bootloader - TWRP Installed. I have installed TWRP on a phone many eons ago and never had to unlock a bootloader (super early smartphone days when I used TWRP). Is there anything that gives a dummy, step by step method, on doing this Frankenstein change all from a Windows 10 PC? I have done the fastboot and ADB stuff in the past (got rid of specials and offers) so I am not squeamish with that portion of things. I do have some concerns on the link at the top to [UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 10 2017 (suez) since this is pointing to *nux which I have not used in the past. Help me obi-wan you are my only hope.
This will be easy unfortunately. There is no permanent root or TWRP for the new HD 10 yet, which, BTW, is known as Maverick. The ROM you found is for an older model, Suez, which does have root and TWRP. Sorry man. You can always try to the Fire Toolbox located in the development section to change the default launcher to Nova which is much more Android looking, but that's not permanent either and is prone to switching back to Amazon's default. It's early days right now.
StumpedTechy said:
My girlfriend bought a Fire 10 and now that she has opened it she is thinking her son would rather it be an Android. (He is autistic and does not deal with change well and his phone is Android but he has a dying iPad.) I found [ROM][unlocked][suez] Lineage-14.1 [26 SEP 2019] and I see this might be just what the doctor ordered but it is asking me to do a bunch of pre install items - Unlocked Bootloader - TWRP Installed. I have installed TWRP on a phone many eons ago and never had to unlock a bootloader (super early smartphone days when I used TWRP). Is there anything that gives a dummy, step by step method, on doing this Frankenstein change all from a Windows 10 PC? I have done the fastboot and ADB stuff in the past (got rid of specials and offers) so I am not squeamish with that portion of things. I do have some concerns on the link at the top to [UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 10 2017 (suez) since this is pointing to *nux which I have not used in the past. Help me obi-wan you are my only hope.
Click to expand...
Click to collapse
No root/unlock methods here for this device. You can only customize it using Fire toolbox.
I originally posted this in Kindle fire general, which was for 1st gen kindles. If you read the details, you'll know why i'm moving this here.
(Original Post)
Hello! I want to install LineageOS on my Kindle Fire HD8 5th Generation running fire os 5.6.8.0, build date december 31st, 2020 at 1:27 pm (not sure if that means anything). It's wiped right now, it's not even my main kindle, meaning nothing will be lost if i have to wipe it again.
I dont want to have to open it up and solder wires, because I dont have the equipment for that.
Also, I don't use linux, just windows, and I don't have a factory cable.
Where do i begin?
I waited days, and nothing. I'm hoping to have more luck on this section.
Hey I just wanted to ask if there is ANY way to bring 12L onto this Tablet.
Is it possible to follow this and then install the GSI?
I already downgraded,rooted and installed TWRP on my Fire. Also had to open it to make the short for the hacked bootloader.
Any Ideas would be appreciated!
The Fire HD 10 7th Gen likely doesn't have a vendor partition. Remember, this never launched with GMS, so these types of partitions may not be present. That's like saying that device has a vbmeta partition, it doesn't have it.
Oh just noticed i put in the wrong link.
I meant this Guide:Correct Link