Related
I rooted my kindle fire 6.3.1 using the utility and installed twrp, everything is fine , once i install a custom rom it wont boot. No matter what rom Installed . it will turn on to the black and blue kindle screen then go black and nothing happens. Or the rom will boot but hangs at the boot image.
Did you "factory reset" before flashing the rom?
I'd download the newest version of kfu, then re-flash twrp , then fire fire fire, put the from on the SD card, then factory reset, wipe both caches, then install from and wipe caches again
Sent from my Galaxy Nexus using XDA Premium HD app
chris_m128 said:
I'd download the newest version of kfu, then re-flash twrp , then fire fire fire, put the from on the SD card, then factory reset, wipe both caches, then install from and wipe caches again
Click to expand...
Click to collapse
There is no reason to re-flash twrp and there is definitely no reason to re-flash FireFireFire unless absolutely necessary. Flashing a bootloader is potentially dangerous and shouldn't be done just for the hell of it.
The OP has one post on XDA, this one; which leads me to believe he was unaware of or has overlooked the importance of performing a factory reset before flashing any new rom.
[Edit:] That wasn't intended to sound so brash, but you get the point.
I get the point that you think you know a lot more than you do.
Edit: that was intended to sound exactly like it does
chris_m128 said:
I get the point that you think you know a lot more than you do.
Edit: that was intended to sound exactly like it does
Click to expand...
Click to collapse
I tried to convey to you that my intention was not to be rude, yet you respond with unnecessary hostility. What exactly do you expect to accomplish with this? Change my mind? Hurt my feelings? Cause me to be any different than I am? I'm guessing it's probably not going to happen.
forgive me o' mighty one
i have a droid x2 that i have rooted and switched roms on numerous times, as well as sbfing becoming one of my close friends. not sure what to do with the 3 different pages on rooting applications and methods. does a link to actual step by step instructions on how to root and intall roms exist? last night i rooted and installed twrp using the utility, but could not get it to boot for anything. held power down and all i get is a normal boot . when i went to install AOKP , i used the utility to get into twrp RIGHT after putting FFF on it. i flashed the rom and gapps after wiping data, and i got a blank screen for an hour. i found a tutorial on mounting sd card through twrp and saved it. my question is what is the proper way to root 6.2.2? and will installing roms through working twrp actualy work? if so how do i get twrp to work? thanks in advance guys.
clarity
just to clarify , i have read all of the guides on here and have a bsic understanding (not much) of fastboot and adb. does this device need adb things done to it to work? <--- third question...lol
I used the kindle fire utility. It is a little more complicated than other devices I have rooted/rommed, but not impossible. http://forum.xda-developers.com/showthread.php?t=1399889 is the thread for KFU. You install it on your computer and follow the instructions. I soft bricked mine because I wasn't paying attention and flashed the wrong bootloader, if something like that happens there is another utility for unbrick.
Sent from my Galaxy Nexus using xda premium
Lorenzo VonMatterhorn said:
just to clarify , i have read all of the guides on here and have a bsic understanding (not much) of fastboot and adb. does this device need adb things done to it to work? <--- third question...lol
Click to expand...
Click to collapse
Yes, you use adb but it instructs you what to type.
Sent from my Galaxy Nexus using xda premium
pyroscott said:
I used the kindle fire utility. It is a little more complicated than other devices I have rooted/rommed, but not impossible. http://forum.xda-developers.com/showthread.php?t=1399889 is the thread for KFU. You install it on your computer and follow the instructions. I soft bricked mine because I wasn't paying attention and flashed the wrong bootloader, if something like that happens there is another utility for unbrick.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
i used the utility for my first blunder on this device. is the first step install permanent root? thats what i did first. then install latest twrp. did that second. said it was installed, unplugged from my computer and tried to boot into twrp. nothing. from off just hitting power sould show the triangle sign correct? if so i dont even get this.
Yes the first step should be root... which in my case also installs twrp...
If you're planning to install a custom ROM, there's no point in rooting. FFF and TWRP are more than enough.
aokp
ok well i rooted. and now twrp works flawlessly. but when i try to flash aokp, i wipe data/factory reset, install aokp and then gapps, i get nothing but a black screen after rebooting. after waiting a minute or two, i rebooted into recovery and restored a backup. am i doing something wrong? i started on 6.2.2 if that helps at all.
You should -always- wipe cache and dalvik-cache when flashing ROMs.
When you're upgrading the same ROM from a lower version to a newer one (for example, going from gede 1.65 to 1.7) you may skip factory reset, so long as there isn't a major change (going from normal to linaro, for example).
However, it is good practice to let Titanium Backup handle all of your /data backups and just factory reset every time as well.
You have the two most important steps done.
1. You have TWRP installed and you can boot into it. That is one of the hardest steps it appears.
2. You did a backup before doing anything else.
As Dasanko said you also need to wipe cache and dalvik-cache. When I do a new rom I wipe data, system, cache and dalvik-cache.
Titanium Backup (TiBu) is also awesome to restore your apps. However, you will need to install TiBu to use it to restore other apps. Some ROMS have it installed already and some don't. If you don't have access to TiBu from the Rom your are flashing you will need the GApps installed to get the Play Store. You can then download TiBu be able to restore your chosen apps.
Lorenzo VonMatterhorn said:
i used the utility for my first blunder on this device. is the first step install permanent root? thats what i did first. then install latest twrp. did that second. said it was installed, unplugged from my computer and tried to boot into twrp. nothing. from off just hitting power sould show the triangle sign correct? if so i dont even get this.
Click to expand...
Click to collapse
Yes, you should get the screen with the triangle. I would try flashing the recovery again
Sent from my Galaxy Nexus using xda premium
also when you are installing a new rom I always wipe system so you dont have any errors because that is where the old rom is located. btw cm9 and aokp are both really nice on this device
I have been running Xenon HD rom for some time now, but just recently, every time I try to update to the newest version when I reboot the system, it get stuck on the boot image. I end up pulling the battery and then a bunch of my apps are missing. I have never had this issue before. If I do a clean install, it loads just fine but I obviously have to reload everything. I would really like to not have to do a clean install every time when I am just updating the same rom. Any help would be greatly appreciated.
When you update a rom your boot screen will stay for a lounger amount of time because of the changes it made so wait a bit longer (5min) or try another recovery in my opinion TWRP is the best or maybe you could make a backup of your data before flashing it and the restore the data and there you go or you could also try using another rom if this problem stays and go back in 2 weeks to xenon hd and see if you have still the issue.
victor00100 said:
When you update a rom your boot screen will stay for a lounger amount of time because of the changes it made so wait a bit longer (5min) or try another recovery in my opinion TWRP is the best or maybe you could make a backup of your data before flashing it and the restore the data and there you go or you could also try using another rom if this problem stays and go back in 2 weeks to xenon hd and see if you have still the issue.
Click to expand...
Click to collapse
Yeah, I left my phone for 30min and it was still on the boot screen. Pardon my ignorance, but I am not familiar with TWRP. Right now I use ROM Manager. Is TWRP in place of ROM Manager? How do I get TWRP and load it?
Thanks for your help.
how old is the version you are running vs the age of the new one?
are they different android version?
Zepius said:
how old is the version you are running vs the age of the new one?
are they different android version?
Click to expand...
Click to collapse
Just their most recent release. I believe the previous version was 11.30.12 and I was updating to 12.8.12, so same version of Android.
you might have to wipe depending on what was changed between those 2 dates.
if you're having bootloop problems, you have to wipe.
rivman20 said:
Yeah, I left my phone for 30min and it was still on the boot screen. Pardon my ignorance, but I am not familiar with TWRP. Right now I use ROM Manager. Is TWRP in place of ROM Manager? How do I get TWRP and load it?
Thanks for your help.
Click to expand...
Click to collapse
TWRP is a recovery it is the best in my opinio because you don't have as many problems like you have with cwm you just flash TWRP after doing some research and then you flash and then you update your rom with you recovery
I got the stock ROM off of amazon. Converted it to update.zip, couldn't flash it cuz it said "blaze" as the codename in the updater script. Updated it to otter, still can't flash it. What am I doing wrong? Help is appreciated, thanks.
GalaxyExhibit said:
I got the stock ROM off of amazon. Converted it to update.zip, couldn't flash it cuz it said "blaze" as the codename in the updater script. Updated it to otter, still can't flash it. What am I doing wrong? Help is appreciated, thanks.
Click to expand...
Click to collapse
Revert to an earlier version of TWRP (preferably one before the different "otter" and "blaze" versions) or install COTR. I'd recommend COTR though.
Also, DON'T FORGET TO FACTORY RESET!!! Otherwise, you will need a factory cable to fix it.
soupmagnet said:
Revert to an earlier version of TWRP (preferably one before the different "otter" and "blaze" versions) or install COTR. I'd recommend COTR though.
Also, DON'T FORGET TO FACTORY RESET!!! Otherwise, you will need a factory cable to fix it.
Click to expand...
Click to collapse
Thanks, will do.
Ok, so here is what I did to fix the issue. Instead of installing TWRP (this is a smarter idea), I installed ubuntu as a side OS, after installed, downloaded stock firmware. After that, changed it to zip format and named it update.zip. After that, I changed the name from blaze to otter in the update-script. Guess what, it worked. Recommending this method to anyone who has either this issue, TWRP 2.6 installed, or just likes to play around with their KF.
LGHater said:
Ok, so here is what I did to fix the issue. Instead of installing TWRP (this is a smarter idea), I installed ubuntu as a side OS, after installed, downloaded stock firmware. After that, changed it to zip format and named it update.zip. After that, I changed the name from blaze to otter in the update-script. Guess what, it worked. Recommending this method to anyone who has either this issue, TWRP 2.6 installed, or just likes to play around with their KF.
Click to expand...
Click to collapse
Alright, I'm having the same issue, but I'm not sure how to do the things you've described here, being a complete noob. Could you provide a bit more of a detailed instruction, including what difference installing Ubuntu made and how one goes about changing the name from blaze to otter in the update-script? (Starting with where does one find the script.)
I'm currently running TWRP 2.6.0.0 and just want to go back to stock...which is now 6.3.2.
Thx.
bembley said:
Alright, I'm having the same issue, but I'm not sure how to do the things you've described here, being a complete noob. Could you provide a bit more of a detailed instruction, including what difference installing Ubuntu made and how one goes about changing the name from blaze to otter in the update-script? (Starting with where does one find the script.)
I'm currently running TWRP 2.6.0.0 and just want to go back to stock...which is now 6.3.2.
Thx.
Click to expand...
Click to collapse
Get a virtual machine, download ubuntu and select the ISO file in whatever VM software you use. When it's done installing, download the stock software and when it's done downloading, change the format from BIN (I think it's a bin I might be wrong) to ZIP. Then go into the ZIP file and go into Meta-Inf, and edit the update-script with the text software on ubuntu and change the code name from blaze to otter if you're having a status 7 error. And you're done. Get ready to flash the software by performing a factory reset. Then go back and install the update.zip. And you're done. If this didn't work, post on this thread again with any confusion or errors.
LGHater said:
Get a virtual machine, download ubuntu and select the ISO file in whatever VM software you use. When it's done installing, download the stock software and when it's done downloading, change the format from BIN (I think it's a bin I might be wrong) to ZIP. Then go into the ZIP file and go into Meta-Inf, and edit the update-script with the text software on ubuntu and change the code name from blaze to otter if you're having a status 7 error. And you're done. Get ready to flash the software by performing a factory reset. Then go back and install the update.zip. And you're done. If this didn't work, post on this thread again with any confusion or errors.
Click to expand...
Click to collapse
Worked marvelously...and confirmed my suspicion of hardware problems. The stock image loaded, but processes keep failing and it reboots itself over and over again...similar to what it was doing with the cyanogen mod I was using.
Anyway...Thanks for your help!!
bembley said:
Worked marvelously...and confirmed my suspicion of hardware problems. The stock image loaded, but processes keep failing and it reboots itself over and over again...similar to what it was doing with the cyanogen mod I was using.
Anyway...Thanks for your help!!
Click to expand...
Click to collapse
Well I'm glad things worked out for you and the error was gone. Enjoy stock, I guess. lol
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a prerooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Retch_100 said:
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a prerooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Click to expand...
Click to collapse
A Lineage OS rom is still under development and not released yet. Have you tried flashing the stock image (6.2.7.1)? Flash this in recovery, to see if it fixes the update error. You may need to flash Magisk to be rooted again. And this stock image WILL NOT overwrite TWRP. The prerooted roms that are released have Magisk built in so there's nothing different between those and the stock image in which has no root at all. Let me know if you have any questions!
Stock Image for Fire TV Stick 4K: https://drive.google.com/open?id=1LlOFUO8o_8GKm-kQLR9QCMmql2Zyu8W8
Retch_100 said:
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a pre-rooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Click to expand...
Click to collapse
From what I have seen, the tutorial for flashing the prerooted is really a dirty flash, and certainly from my experience (where I forgot to reset the device before flashing the image) all my apps were still there.
I'm sure you can wipe your system & data partition from TWRP, and then flash the image.
The only problem I can foresee is that the pre-rooted image might not be a full image which would cause your Firestick not to boot.
I suggest you head over to the pre-rooted image thread and ask if it's ok to wipe those partitions and also what the actual commands are.
I'm curious also - just for future reference....
p.s I just found this
https://twrp.me/faq/openrecoveryscript.html
which lists TWRP's commands, Just check first to see if it's safe to wipe those partitions.
Okay, i will install it tomorrow. Is there a Source to the lineage Development? The Stick is unusable for me, so i Would install anything to Pass the error.
@tinybilbo
Good question, i didnt Know Either what to do so i Wiped cache and dalvik and data, but That should be considered as a Dirty Flash thought, i will ask there.
@Skel40
What to Wipe before flashing?
Retch_100 said:
Okay, i will install it tomorrow. Is there a Source to the lineage Development? The Stick is unusable for me, so i Would install anything to Pass the error.
@tinybilbo
Good question, i didnt Know Either what to do so i Wiped cache and dalvik and data, but That should be considered as a Dirty Flash thought, i will ask there.
@Skel40
What to Wipe before flashing?
Click to expand...
Click to collapse
I think the system partition would be the important one to wipe, data is mostly user data from what I remember.
If Skel40's link is a full image (as the prerooted one i might be), then maybe do all the wipes and try that one 1st..
Normally when I use TWRP I don't dirty flash, and I wipe system,data,dalvik,cache...
Good luck with whatever you try
Retch_100 said:
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a prerooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Click to expand...
Click to collapse
Retch_100 said:
Okay, i will install it tomorrow. Is there a Source to the lineage Development? The Stick is unusable for me, so i Would install anything to Pass the error.
@tinybilbo
Good question, i didnt Know Either what to do so i Wiped cache and dalvik and data, but That should be considered as a Dirty Flash thought, i will ask there.
@Skel40
What to Wipe before flashing?
Click to expand...
Click to collapse
You need to wipe system, data, dalvik-cache, and cache before flashing. Upon boot up after flashing 6.2.7.1, it skips the updates, I have a backup if needed!
I wiped all Partitions and Flashed the Image, but it searches for backups and the error appears. Could you send me the Backup? @Skel40
Retch_100 said:
I wiped all Partitions and Flashed the Image, but it searches for backups and the error appears. Could you send me the Backup? @Skel40
Click to expand...
Click to collapse
You wiped everything (data, system, internal, cache, dalvik). There is nothing else, if you are flashing the full stock upgrade image. The device finds remote, connects to bluetooth, then finds Wifi, connects to wifi. Then the device errors (when checking for an update). Since you bought this device used, i highly suspect the device is blacklisted. Firestick 4k's are on sale for $25 again. I would cut my loses and hope someday for a custom (you can ask for a copy of the buggy one diegocr and Rortiz2 over in the tank 12.1 thread. But it is likely unusable at this time.
Okay thank you @Michajin
What do you think, would be installing TWRP on one of the others and restoring a backup from them onto the broken one help?
Retch_100 said:
Okay thank you @Michajin
What do you think, would be installing TWRP on one of the others and restoring a backup from them onto the broken one help?
Click to expand...
Click to collapse
I don't think so. I believe it is sending its serial number to amazon when it connects to the internet. There used to be a work around that would bypass registration, but i believe that was blocked about a year ago. Maybe someone on here knows a work around since you have access with TWRP (file manager), If it were me, i would find the update files in TWRP and rename or delete them... i think they are in the root/system folder. Since you have a full backup i dont see much risk. If it fails to boot or work, just restore your system from a backup.
The files should be called:
device.software.ota
com.amazon.device.software.ota.override
Michajin said:
I don't think so. I believe it is sending its serial number to amazon when it connects to the internet. There used to be a work around that would bypass registration, but i believe that was blocked about a year ago. Maybe someone on here knows a work around since you have access with TWRP (file manager), If it were me, i would find the update files in TWRP and rename or delete them... i think they are in the root/system folder. Since you have a full backup i dont see much risk. If it fails to boot or work, just restore your system from a backup.
The files should be called:
device.software.ota
com.amazon.device.software.ota.override
Click to expand...
Click to collapse
Okay thanks I will see.
BTW: the Stick does not have any value to me anymore, so bricking it would be okay if I learned something this way
But it'd be better if the Stick could be resurrected to work as a Stick.
Maybe anything of this.
Pass OOBE:
==========
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
adb shell settings put secure install_non_market_apps 1
adb shell settings put global adb_enabled 1
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
pm disable com.amazon.tv.oobe
Your fire stick blacklisted by Amazon.