Related
Whats good XDA community?
I dont know exactly what happened (I bugged this little dude out awhile ago I've just been too lazy to fix it) but now that I want to flash my kindle fire back to the original... I cant seem to. It seems I've wiped the ICS rom I had running on it and now when I hit the power button(and dont boot into TWRP 2.0) it just loads a blank black screen. Also, I cant seem to mount my kindle via the TWRP mount option, do I need the android debug bridge for this? I changed computers recently so I dont have any of the tools that I had when flashing this the first go around(for the record I'm on a mac).
Thanks for your help, my first post so please be kind
Aslan11 said:
Whats good XDA community?
I dont know exactly what happened (I bugged this little dude out awhile ago I've just been too lazy to fix it) but now that I want to flash my kindle fire back to the original... I cant seem to. It seems I've wiped the ICS rom I had running on it and now when I hit the power button(and dont boot into TWRP 2.0) it just loads a blank black screen. Also, I cant seem to mount my kindle via the TWRP mount option, do I need the android debug bridge for this? I changed computers recently so I dont have any of the tools that I had when flashing this the first go around(for the record I'm on a mac).
Thanks for your help, my first post so please be kind
Click to expand...
Click to collapse
I guess you didn't make a nandroid backup? You don't need adb to mount the SD partition though, If you can i would try a different computer because when you mount SD through TWRP you should have no problem accessing the SD on your computer and dropping a ROM or in this case the update.zip from here
http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620
since you are already wiped, all you will need to do is rename this .bin file to update.zip and install like a normal ROM. you will then be left with an unrooted, stock version of the kindle fire (without TWRP or FFF also)
I rooted my Kindle Fire using KFU 0.9.5 and flashed a custom ROM. It worked fine for a few days and then just crashed -- The options bar located on the bottom disappeared and the error message was: System UI has crashed. (I have attached two pictures for better clarity)
Also, whenever I boot up, there is no yellow flame that appears, it goes to the moving colourful discs straight on.
I tried using terminal emulator and entered many codes in some hope of mounting USB Mass Storage so that I can use KFU and restore my Kindle, but in vain.
I have tried EVERYTHING. I've been at this for 6 days now and am at wits end. :crying: I have read up close to a 100 articles; this was my last resort.
I just want to get the Kindle's stock OS back - no root, nothing.
And the only was is, I suppose, if I am able to mount my Kindle as USB Mass Storage onto my computer.
ANY help is appreciated!
AndroBoss.
I don't have a kindle but did you try wiping it and reinstalling it?
Sent from my SPH-L710 using xda app-developers app
jr71x said:
I don't have a kindle but did you try wiping it and reinstalling it?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
As it now runs on ICS, there is no Gingerbread for Kindle anymore on it. I can't wipe it clean from the device or atleast I don't know how to, please help?
All the wipes you should need to perform can be done in twrp recovery. Wipe factory reset , wipe cache , wipe dalvik and wipe the system. Reflash ROM , reflash gapps , reboot then system if prompted and you should be good to go.
Edit: failing to use the correct method to return to stock will just cause more problems. Rather than trying to go back to pure stock without fff and twrp I suggest you perform the above wipes and flash this instead http://forum.xda-developers.com/showthread.php?t=1439916 its just modified stock with Google play and it will not wipe out your recovery and bootloader.
Thepooch said:
All the wipes you should need to perform can be done in twrp recovery. Wipe factory reset , wipe cache , wipe dalvik and wipe the system. Reflash ROM , reflash gapps , reboot then system if prompted and you should be good to go.
Edit: failing to use the correct method to return to stock will just cause more problems. Rather than trying to go back to pure stock without fff and twrp I suggest you perform the above wipes and flash this instead http://forum.xda-developers.com/showthread.php?t=1439916 its just modified stock with Google play and it will not wipe out your recovery and bootloader.
Click to expand...
Click to collapse
Okay, I will flash what you suggested but that's the problem. I am unable to access TWRP recovery from my Kindle. When it boots up there is no yellow flame that appears as the custom ROM is ICS 4.0.
I tried mounting a twrp.img on to the SD Card after downloading one straight onto the tab but of no avail :/
What do you suggest? Is there any way I can get the TWRP Recovery to come up so that I can get the modified stock that you suggested?
Thanks for your help, regardless
Androboss1994 said:
Okay, I will flash what you suggested but that's the problem. I am unable to access TWRP recovery from my Kindle. When it boots up there is no yellow flame that appears as the custom ROM is ICS 4.0.
I tried mounting a twrp.img on to the SD Card after downloading one straight onto the tab but of no avail :/
What do you suggest? Is there any way I can get the TWRP Recovery to come up so that I can get the modified stock that you suggested?
Thanks for your help, regardless
Click to expand...
Click to collapse
I know you said you read "close to a 100 articles" in your OP, but I suggest you do a little more reading. Get yourself acquainted with the key software components of the Kindle Fire and how they work together. Some of the things you say in your posts suggest you would benefit from the first post here...
http://forum.xda-developers.com/showthread.php?t=1552547
- The yellow flame you are looking for is an older version of the FireFireFire (FFF) bootloader, but there is a newer/better version.
- The KF cannot go to "the moving colorful discs straight on" because the first thing you will see is the bootloader's bootlogo.
- You must determine what bootloader is currently installed on the device because it is key in determining how you can get into recovery (TWRP).
- "Mounting" sdcard means to make the storage space available to either the host computer or the Kindle Fire, but it almost always means the former. Your comment about having "tried mounting a twrp.img on to the SD Card" doesn't make sense.
My guess is you do not have FFF installed and the device is booting with the stock bootloader. Odds are you will still be able to boot into your current ICS system and execute an adb command to set the bootmode to recovery (5001). Then a reboot should take you into TWRP. At that point, you should try to mount the sdcard partition onto your computer and transfer the latest FFF and whatever ROM you want to flash. Be sure to install FFF as soon as possible. This will allow you to get back into TWRP even if your system software becomes unbootable. Only when you are comfortable with FFF and TWRP should you consider flashing another ROM onto the device.
In broad strokes, the above paragraph contains the steps you will take to get your device running properly again. If any part of it doesn't make much sense to you, I suggest you read the above article again. Then, you can figure out the specifics commands from the third post of the link above and the following...
http://forum.xda-developers.com/showthread.php?t=1638452
kinfauns said:
I know you said you read "close to a 100 articles" in your OP, but I suggest you do a little more reading. Get yourself acquainted with the key software components of the Kindle Fire and how they work together. Some of the things you say in your posts suggest you would benefit from the first post here...
http://forum.xda-developers.com/showthread.php?t=1552547
- The yellow flame you are looking for is an older version of the FireFireFire (FFF) bootloader, but there is a newer/better version.
- The KF cannot go to "the moving colorful discs straight on" because the first thing you will see is the bootloader's bootlogo.
- You must determine what bootloader is currently installed on the device because it is key in determining how you can get into recovery (TWRP).
- "Mounting" sdcard means to make the storage space available to either the host computer or the Kindle Fire, but it almost always means the former. Your comment about having "tried mounting a twrp.img on to the SD Card" doesn't make sense.
My guess is you do not have FFF installed and the device is booting with the stock bootloader. Odds are you will still be able to boot into your current ICS system and execute an adb command to set the bootmode to recovery (5001). Then a reboot should take you into TWRP. At that point, you should try to mount the sdcard partition onto your computer and transfer the latest FFF and whatever ROM you want to flash. Be sure to install FFF as soon as possible. This will allow you to get back into TWRP even if your system software becomes unbootable. Only when you are comfortable with FFF and TWRP should you consider flashing another ROM onto the device.
In broad strokes, the above paragraph contains the steps you will take to get your device running properly again. If any part of it doesn't make much sense to you, I suggest you read the above article again. Then, you can figure out the specifics commands from the third post of the link above and the following...
http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
WOW! Okay, thank you so much; I'll keep you updated. I'll do all this tonight! Cheers :good:
I have a problem with my kindle fire system , i had install jandycane_otter-v1.7.2_0xD34D with TWRP , after that i install the official Kindle fire software update without ( WIPE ) > now i cant use my kindle >> plzzzz help me
Do you have FireFireFire installed?
i can't do anything with my kindle , when i switch it on the device reboot automatically, How can i install it ?
How long does it stay on before it reboots?
soupmagnet said:
How long does it stay on before it reboots?
Click to expand...
Click to collapse
30 sec
You never told me whether or not you have FireFireFire installed.
soupmagnet said:
You never told me whether or not you have FireFireFire installed.
Click to expand...
Click to collapse
i installed it
What color is your boot logo? Blue?
soupmagnet said:
What color is your boot logo? Blue?
Click to expand...
Click to collapse
yes, blue
what happens when you select recovery in the boot menu? More gets accomplished faster here when you refresh your browser frequently
Thepooch said:
what happens when you select recovery in the boot menu? More gets accomplished faster here when you refresh your browser frequently
Click to expand...
Click to collapse
there is no boot now
I sent you a pm or we can just play post tag. Unread your private messages. Just use kfu to reinstall twrp, get into recovery, mount your sdcard, transfer a rom to your sdcard, unmount your sdcard, wipe everything except your sdcard or external storage , flash the rom and reboot.
If you can give us more detailed information up front and more than just two to three word answers to questions we can help you far more easily and accurately. We need as much information as possible as to what you are experiencing so that we know how to help and guide you in the right direction.
That being said if you have twrp installed you need to start there with a complete wipe, wipe the cache dalvik cache and system and do a factory reset. If you don't already have a Rom or Amazon kindle update transferred to your device you can click mount in twrp and then click mount usb. This will make the kf visible to your pc when connected via usb cable and allow the transfer.
Sent from my Amazon Kindle Fire using xda app-developers app
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Amazon Kindle Fire[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: I have a new Kindle Fire (purchased after Nov 2012). What do I need to know first?
[/SIZE]You will BRICK YOUR KINDLE if you don't READ THIS FIRST!!![SIZE=+1]Q2: I have an older Kindle Fire (1st generation). What do I need to know first?[/SIZE][GUIDE] Kindle Fire For Beginners[SIZE=+1]Q3: How can I tell if I have a 1st or 2nd generation Kindle Fire?[/SIZE]If you have a software version of 6.3.2 or earlier, it is a 1st generation Kindle Fire. Anything after that is a 2nd generation Kindle Fire.[SIZE=+1]Q4: Where do I find information on how to root the 1st generation Kindle Fire?[/SIZE][HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)[SIZE=+1]Q5: Can I root the Kindle Fire without a computer?[/SIZE]No[SIZE=+1]Q6: Is there a “One-Click” or scripted root method for the 1st generation Kindle Fire?[/SIZE][Root][TWRP][FFF][CWM]Kindle Fire Utility v0.9.6 (5/09/12) (Windows) - or - BreakDroid (Mac)
Be careful when using these tools and make sure you understand how to fix problems that may arise before attempting anything. Failure to do so will most likely lead to problems.[SIZE=+1]Q7: Is there an easier way to root the 1st generation Kindle Fire?[/SIZE]Install custom recovery, then install a custom ROM. If you want a rooted version of the stock OS, install MoDaCo.[SIZE=+1]Q8: What custom recoveries are available for the Kindle Fire?[/SIZE]Team Win Recovery Project (TWRP) - and - Cannibal Open Touch Recovery (COTR)[SIZE=+1]Q9: Is there an easy way to install a different custom bootloader or recovery without using ADB or fastboot?[/SIZE][smirkit-v2.4][02/05]install recovery+bootloader COTR or TWRP[SIZE=+1]Q10: Where can I find a list of available ROMs?[/SIZE][INDEX] Kindle Fire Development *REVISED NIGHTLY*[SIZE=+1]Q11: What is the best ROM available?[/SIZE]What is considered to be the best ROM is always a matter of opinion. Just pick one and try it out to see if you like it. If not, try a different one. If you are looking to find the most popular ROM, you can search the development forum for the ROM thread with the most views.[SIZE=+1]Q12: I just want to root my 1st generation Kindle Fire. Do I have to install FireFireFire?[/SIZE]No, but not having FireFireFire installed on a rooted device opens you up to the potential of serious problems in case anything goes wrong, and things will almost always go wrong.[SIZE=+1]Q13: Where do I find information on how to unroot the 1st generation Kindle Fire?[/SIZE][HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)[SIZE=+1]Q14: Where do I find information on how install ADB/fastboot drivers for the 1st generation Kindle Fire?[/SIZE][GUIDE] Kindle Fire For Beginners – Post #2 - & - Let's take some of the mystery out of getting ADB working in Windows[SIZE=+1]Q15: I've exhausted all available options and still can't get ADB/fastboot to connect in Windows. What else can I do?[/SIZE]Soupkit
[SIZE=+1]Q16: What does it mean when my device is stuck at the Kindle Fire logo?[/SIZE]It depends on which Kindle Fire logo you're talking about. If you're talking about the Kindle Fire logo that stays brightly lit without any change in brightness, it means the device is in fastboot mode. Just change the bootmode to normal or recovery and reboot. If you are unable to change the bootmode, then you need to fix your drivers. If the Kindle Fire logo you're talking about flashes and goes dim after being brightly lit for a few seconds, then your device is trying to boot normally to a malfunctioning operating system, likely caused by not wiping the data partition (factory reset) before flashing a ROM. If that's the case, you will likely need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then reinstall a ROM properly.[SIZE=+1]Q17: What can I do that will fix 90% of all Kindle Fire problems?[/SIZE]Get access to custom recovery and reinstall a ROM, making sure to wipe the data partition (factory reset) first.[SIZE=+1]Q18: Where do I find information on some of the various commands and how to use them?[/SIZE][GUIDE] Kindle Fire For Beginners – Post #3[SIZE=+1]Q19: Where do I find information on how to use fastboot mode?[/SIZE] [GUIDE] Fastboot Mode[SIZE=+1]Q20: How do I install a custom ROM?[/SIZE][HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)[SIZE=+1]Q21: I need to get a ROM or file onto my Kindle Fire. What are the various methods of doing so?[/SIZE]You can download the ROM or file onto your device via the Internet. You can use an app like Wifi File Explorer to transfer the ROM or file to your sdcard over wifi. While booted normally, you can mount your sdcard as a USB storage device and transfer it from your computer. If neither of those options are available, you can use ADB to push the ROM or file to your sdcard or use the “Mount” function in custom recovery to mount your sdcard as a USB storage device and transfer it from your computer.[SIZE=+1]Q22: What can I do if I am unable to mount my sdcard to USB in recovery?[/SIZE][HOW TO] Fix "Failure to mount" sdcard, system, data or cache[SIZE=+1]Q23: I like the stock OS but is there an easier way to install Google Play, Google Apps, Disable OTA updates, change wallpapers, etc., rather than doing it manually?[/SIZE]Install MoDaCo while in recovery[SIZE=+1]Q24: Where do I find information on how to restore the Kindle Fire to it's original unmodified state?[/SIZE][HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)[SIZE=+1]Q25: I tried to restore the stock OS and now my device is stuck at the Kindle Fire logo. What happened?[/SIZE]It is most likely that you forgot to wipe the data partition (factory reset) in recovery before flashing the stock update.zip. As a result, you will need a factory cable to get into fastboot so you can reinstall custom recovery and flash the update.zip properly.[SIZE=+1]Q26: What is a factory cable? What is it used for? How do I use it?[/SIZE]A factory cable, not to be confused with the OEM USB cable that comes with the Kindle Fire, is a USB cable made to emulate a Motorola factory programming cable. With the Kindle Fire, it is an easy way to access fastboot mode, especially when no other options are available. To use it, while plugged into your computer, simply plug it into a Kindle Fire that has been completely powered down.[SIZE=+1]Q27: Where do I find information on making or purchasing a factory cable?[/SIZE][Info]Making/Using a Factory Cable - or - SkOrPn [SIZE=+1]Q28: What needs to be wiped when installing a ROM?[/SIZE]When installing a minor update to a ROM, it is generally considered safe to just install the ROM without wiping anything. When installing a major update or a different ROM altogether, you must, at the very least, perform a factory reset in custom recovery, which wipes the data and cache partitions. Not doing so will usually result in major problems.[SIZE=+1]Q29: I tried to install a ROM and now my device is stuck at the ROM's boot animation. What happened?[/SIZE]It is most likely that you forgot to wipe the data partition (factory reset) in recovery before flashing the ROM. If you have FireFireFire installed, you can use the power button at startup to access custom recovery and reinstall the ROM properly. Otherwise, you may need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then reinstall the ROM properly.[SIZE=+1]Q30: Is it true that letting the battery die will reset the device and fix whatever problem I'm experiencing?[/SIZE]NO!!! NO!!! NO!!! NO!!! The flash memory storage of the Kindle Fire is capable of holding data without ANY power until your grandchildren's grandchildren have their own grandchildren...probably even longer. Not to mention, a dead battery will cause much bigger problems than you ever had to begin with, on top of the problems you had to begin with. Whatever problem you're dealing with, it is always best to avoid letting the battery die at all costs.[SIZE=+1]Q31: Why is my boot logo flashing every 5-10 seconds?[/SIZE]You have a near dead battery. The most effective way fix it is to power the device down by holding the power button for 10 seconds, plug the device into a power source, then IMMEDIATELY hold the power button until it shuts off again. If it shuts off and stays off (no display, no led), let it charge for at least half a day. Otherwise keep trying, or get another battery.[SIZE=+1]Q32: My Kindle shows the boot logo for 20-30 seconds and either goes to a black screen or reboots itself.[/SIZE]You either don't have a ROM in place or your ROM is seriously malfunctioning. If you have FireFireFire installed, you can use the power button at startup to access custom recovery and install a ROM . Otherwise, you may need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then install a ROM.[SIZE=+1]Q33: When my Kindle Fire boots, a message keeps popping up, preventing me from doing anything, how do I fix it?[/SIZE]This is either caused from not wiping the data partition (factory reset) in recovery before flashing a ROM or you installed an app that is incompatible with the Kindle Fire and it is causing problems. If it the latter is true, use ADB to access the shell and locate and remove the offending app. Otherwise, if you have FireFireFire installed, you can use the power button at startup to access custom recovery and reinstall the ROM properly. If not, you may need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then reinstall the ROM properly.[SIZE=+1]Q34: My Kindle Fire does not power on or show any outward signs of life; no display, no sound and no LED when plugged in. What does this mean?[/SIZE]There was a problem while installing a custom bootloader, or the bootloader partition was, in some way, compromised and the device was shut down before it was fixed. If the device is a 1st generation Kindle Fire, you have to use Firekit or usbboot along with the shorting trick to reinstall the bootloader. If the device is a 2nd generation Kindle Fire, unfortunately there is nothing you can do about it.[SIZE=+1]Q35: I have a question about a particular ROM but I can't post in the Development section. What can I do to get the help I need?[/SIZE]The Development forum is for sharing ideas on development. If you have a question about a particular ROM, ask it in the Q&A section. Contrary to what some may believe, the Developers of this community are very aware of questions being asked in the Q&A section, especially when it comes to their ROMs.*Forum Rules | New Users Guide | XDA Tour | Report PostsThis FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
reserved
reserved - just in case
Nice job Soup
[Edit:] Tapatalk acting stupid again
Hi guys I no longer own a KF1 I have a KF2. But I am wondering if anyone would be able to confirm that /sys/class/leds/led-green exists? I am planning on building an app that connects up to your notifications and allows for the use of the charger light as a notification light. And of course it will require root
Sent from my Amazon Otter2 using Tapatalk
see op
Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.
Click to expand...
Click to collapse
sd_shadow said:
yes it's there, charging is orange, charged is green, please start a new thread if you need more info.
see op
Click to expand...
Click to collapse
Ok thanks. I talked to hashcode and he said he might be adding that feature anyways so I guess I wont finish the app. Thanks anyways
Sent from my Amazon Otter2 using Tapatalk
NEED HELP......
i have a kindle fire hd that i rooted to kit kat no problem but now im trying to help my mom she has a 1st gen kindle fire with 6.3.3 on it, i know its a first gen cus i bought it for her brand new when it came out. so im trying to install jelly bean on it or maybe even kit kat but everything i see is for the 6.3.2 firmware and earlier could use a little help here maybe with downgrade to the 6.3.2 or figure out if there is a anything for the 6.3.3 firmware.. thanks
Please read first...
If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.
Click to expand...
Click to collapse
cavila1988 said:
i have a kindle fire hd that i rooted to kit kat no problem but now im trying to help my mom she has a 1st gen kindle fire with 6.3.3 on it, i know its a first gen cus i bought it for her brand new when it came out. so im trying to install jelly bean on it or maybe even kit kat but everything i see is for the 6.3.2 firmware and earlier could use a little help here maybe with downgrade to the 6.3.2 or figure out if there is a anything for the 6.3.3 firmware.. thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1859851
head here.
there are some kitkat rom for kindle fire. take note that there is a new development for kindle fire:
read THIS and THIS, please read carefully and throughly.
as for otterX partition there are two type of partition.. larger system partition (smaller data partition), and smaller system but larger data partition.
as for file system there are ext4 and f2fs..
choose which one you want to use first, and then ask or if you already know, download the correct bootload, recovery, and ROM that support it.
hello,
-I have bootloader v2.05, otterx mode, twrp 2.8.3.0,
- i wiped everything else,
-now I can't mount SDcard (TWRP)(unable to find storage partition to mount to USB) , ADB is 'unauthenticated' mode and can't transfer ZIP to flash any ROM
Please help: how to transfer ZIP / flash ROM via fastboot / change ADB into recovery mode so I can use push/pull
Any solution will work.
Best,
For1n said:
hello,
-I have bootloader v2.05, otterx mode, twrp 2.8.3.0,
- i wiped everything else,
-now I can't mount SDcard (TWRP)(unable to find storage partition to mount to USB) , ADB is 'unauthenticated' mode and can't transfer ZIP to flash any ROM
Please help: how to transfer ZIP / flash ROM via fastboot / change ADB into recovery mode so I can use push/pull
Any solution will work.
Best,
Click to expand...
Click to collapse
Do not use this as a general help thread.
---------- Post added at 12:08 PM ---------- Previous post was at 12:06 PM ----------
see [How To] Fix Otter X Install Errors, Partition sizes, Unable to Mount System...
The every Kindle with firmware 6.3.2 and under is a 1st gen is slitghly outdated. 6.3.3 was released to the 1stgen.
MineMasterHD said:
The every Kindle with firmware 6.3.2 and under is a 1st gen is slitghly outdated. 6.3.3 was released to the 1stgen.
Click to expand...
Click to collapse
6.3.4
see 2015 - update-kindle-6.3.4_D01E_4120220 by sd_shadow
Hello! I was trying to clone one Fire TV Stick 4K to another. I've backup with TWRP from one FireTV Stick 4K next partitions: System, System Image, Vendor, Vendor Image, Data, Boot. Then was trying to restore all of them on another stick with changing backup folder serial number and when another FireTV Stick 4K has been rebooted it stuck on the FireTV logo ((( And I don't know what to do with it know.
I was trying to flash Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.6.8_r1] but receive an error "Failed to mount '/vendor' (Invalid argument)"
Could you help, please? Thank you!
Simpson84 said:
Hello! I was trying to clone one Fire TV Stick 4K to another. I've backup with TWRP from one FireTV Stick 4K next partitions: System, System Image, Vendor, Vendor Image, Data, Boot. Then was trying to restore all of them on another stick with changing backup folder serial number and when another FireTV Stick 4K has been rebooted it stuck on the FireTV logo ((( And I don't know what to do with it know.
I was trying to flash Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.6.8_r1] but receive an error "Failed to mount '/vendor' (Invalid argument)"
Could you help, please? Thank you!
Click to expand...
Click to collapse
I think this is where I would start. Hope it helps.
https://forum.xda-developers.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459
Simpson84 said:
Hello! I was trying to clone one Fire TV Stick 4K to another. I've backup with TWRP from one FireTV Stick 4K next partitions: System, System Image, Vendor, Vendor Image, Data, Boot. Then was trying to restore all of them on another stick with changing backup folder serial number and when another FireTV Stick 4K has been rebooted it stuck on the FireTV logo ((( And I don't know what to do with it know.
I was trying to flash Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.6.8_r1] but receive an error "Failed to mount '/vendor' (Invalid argument)"
Could you help, please? Thank you!
Click to expand...
Click to collapse
Hi, I am facing the same issue, did you manage to get it fixed??
Simpson84 said:
Hello! I was trying to clone one Fire TV Stick 4K to another. I've backup with TWRP from one FireTV Stick 4K next partitions: System, System Image, Vendor, Vendor Image, Data, Boot. Then was trying to restore all of them on another stick with changing backup folder serial number and when another FireTV Stick 4K has been rebooted it stuck on the FireTV logo ((( And I don't know what to do with it know.
I was trying to flash Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.6.8_r1] but receive an error "Failed to mount '/vendor' (Invalid argument)"
Could you help, please? Thank you!
Click to expand...
Click to collapse
I had the same problem in the past before, try flashing the original stock rom in TWRP and reboot. Rerun the exploit and push this zip file to the 4K Fire Stick.
Original Stock Rom: https://drive.google.com/file/d/1-8Md0W6V7UNKkGb1uS2WfIKjjevEEaN7/view?usp=drivesdk
Also if you're having problems pushing the zip, try adb shell, twrp sideload, then adb sideload (the zip file). It'll say copying system image unconditionally along with the vendor images so you shouldn't get the failed to mount vendor anymore and the brick will be gone. Let me know if you have any questions.
Got the same problem. Did this work?
---------- Post added at 04:43 AM ---------- Previous post was at 04:14 AM ----------
Can you also help me with some of the terminology used here - for example on phones I have rooted in the past, I have used backup/restore and install many times but I am not sure how to do this "try adb shell, twrp sideload, then adb sideload (the zip file)".
On the advanced menu of TWRP I see Copy Log, File Manager, Terminal and ADB Sideload. When I choose the last on the list,ADB Sideload the screen gives me another failed to mount /vendor message with "Starting ADB sideload feature, which I am not sure what to do with any of this section of TWRP and if TWRP is to be used rather than a PC to do this. Thanks
theflashfromthecw said:
I had the same problem in the past before, try flashing the original stock rom in TWRP and reboot. Rerun the exploit and push this zip file to the 4K Fire Stick.
Original Stock Rom: https://drive.google.com/file/d/1-8Md0W6V7UNKkGb1uS2WfIKjjevEEaN7/view?usp=drivesdk
Also if you're having problems pushing the zip, try adb shell, twrp sideload, then adb sideload (the zip file). It'll say copying system image unconditionally along with the vendor images so you shouldn't get the failed to mount vendor anymore and the brick will be gone. Let me know if you have any questions.
Click to expand...
Click to collapse
I resolved the problem after sleeping on the problem and found you can use the Install option to restore the factory image even though you get the same /vendor error initially.
I'd still like to learn how to issue ADB push and ADB commands to this stick considering the only way I can see to get to the TWRP menu is to use a mouse via an OTG USB connection and that blocks a PC from connecting and supplying mouse support at the same time - unless I'm really missing something.
Donphillipe said:
I resolved the problem after sleeping on the problem and found you can use the Install option to restore the factory image even though you get the same /vendor error initially.
I'd still like to learn how to issue ADB push and ADB commands to this stick considering the only way I can see to get to the TWRP menu is to use a mouse via an OTG USB connection and that blocks a PC from connecting and supplying mouse support at the same time - unless I'm really missing something.
Click to expand...
Click to collapse
How did you get the factory image onto the stick? I'm stuck with no recovery on the stick currently and ADB is not recognized in TWRP.
I plugged the Windows formatted USB stick in the PC (eFat works for read like this but has problems with backing up to it but you are OK reading off an eFat), downloaded the zip file to the stick., plugged the stick into the powered hub where the mouse is plugged in and the hub is powering the AFS through an internal or extra OTG, powered off and back on the stick which booted to TWRP, clicked cancel to get TWRP Menu, clicked Install, clicked Select Storage, looked at the file sizes of all the storage options and selected the one that matched the total capacity of the stick, then opened the folder where the zip restore file was, selected the full zip restore image and slid the slider to the right with the mouse to begin install. I then saw the text going across the TV screen stating which directories were being restored, then it stopped, then I selected the option to wipe the two caches and clicked the reboot option and the the firestick rebooted with no TWRP menu this time but back to the black and white menu, then to the orange over white background where the device takes a long time to go through its initialization sequence and then after a few minutes it boots back into the option to pair the remote, sign on and do all that stuff again. I did a complete initial configuration again and checked out the quality of the restore by signing in and poking around, then got up my nerve and applied the exploit once more.
Hi! I have exactly the same problem as @Simpson84. I've cloned the 4 partitions (system image, vendor image, data and boot) from one 4K stick to another (same model) via TWRP backup / restore, and now the stick which I've restored into is stuck at the black screen with with fire tv logo (does not reach the white and orange screen boot with the 3 dots). I have access to TWRP and I've already tried everything I could remember:
- flash stock images (update-kindle-mantis-NS62* - tried with several versions)
- wiping cache, dalvik and data
- flash rooted images
- re-run exploit again
- rename backed-up partitions from win to img and flash with fastboot
However, the result is always the same. The normal boot does not get past the black screen with white logo.
Does anyone know any other possible solution?
Thanks!
rpmuploads said:
Hi! I have exactly the same problem as @Simpson84. I've cloned the 4 partitions (system image, vendor image, data and boot) from one 4K stick to another (same model) via TWRP backup / restore, and now the stick which I've restored into is stuck at the black screen with with fire tv logo (does not reach the white and orange screen boot with the 3 dots). I have access to TWRP and I've already tried everything I could remember:
- flash stock images (update-kindle-mantis-NS62* - tried with several versions)
- wiping cache, dalvik and data
- flash rooted images
- re-run exploit again
- rename backed-up partitions from win to img and flash with fastboot
However, the result is always the same. The normal boot does not get past the black screen with white logo.
Does anyone know any other possible solution?
Thanks!
Click to expand...
Click to collapse
Redo the unlock process.
Then format data (type "yes) and then push your rooted rom and magisk back to mantis /sdcard.
Reflash
Wipe dalvik and cache
Reboot
Don't rename any partitions just let kamikiri do its work
rpmuploads said:
Does anyone know any other possible solution?
Click to expand...
Click to collapse
If you can get into twrp, maybe try the 'format' data option, type yes, then wipe system/vendor, cache, dalvik, then install the kamakiri.zip and the latest stock rom followed by magisk.
Many thanks both to @Bertonumber1 and @Sus_i
I tried your suggestions but the 4k stick keeps stuck at the black and white logo. I have another two 4k sticks, one for android development and testing and another one for the living room, so I don't really need it. I just wanted to fix it for the challenge and because it seems that there's nothing wrong on the hardware side.
You can see in the attached images my attempt to recover.
rpmuploads said:
Many thanks both to @Bertonumber1 and @Sus_i
I tried your suggestions but the 4k stick keeps stuck at the black and white logo. I have another two 4k sticks, one for android development and testing and another one for the living room, so I don't really need it. I just wanted to fix it for the challenge and because it seems that there's nothing wrong on the hardware side.
You can see in the attached images my attempt to recover.
Click to expand...
Click to collapse
Looks almost ok from here.
Only thing to remember is that you've to flash magisk behind the stock rom, as the last step just before the reboot... If you flash Magisk infront the rom, Magisk gets overwritten during the stock boot image flash.
In case that won't help, I would flash the kamakiri GPT-fix from here:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)
NOTE: There have been multiple reports of devices with serial numbers containing VM190 or higher being shipped with DL-Mode disabled in BROM. These devices cannot be unlocked using kamakiri. These devices do not show up at all on USB when...
forum.xda-developers.com
Extract the two files from the zip in the kamakiri folder, make sure that the gpt-mantis.bin file goes to the bin folder... then run this using the fireISO:
./gpt-fix.sh
(you need to short again).
Thanks @Sus_i. Indeed I'm always flashing the rom first and then magisk.
I've shorted the stick again and ran successfully ./gpt-fix.sh but it's still stuck at the black and white logo.
Probably I'll try to install the LineageOS to see what it looks like.
rpmuploads said:
Thanks @Sus_i. Indeed I'm always flashing the rom first and then magisk.
I've shorted the stick again and ran successfully ./gpt-fix.sh but it's still stuck at the black and white logo.
Probably I'll try to install the LineageOS to see what it looks like.
Click to expand...
Click to collapse
Unfortunately, there isn't a lineage rom for the 4k.
Have you tried to install a rom + magisk behind the gpt-fix?
If yes, I can't think of a reason why the stick won't boot at this point.
rpmuploads said:
Thanks @Sus_i. Indeed I'm always flashing the rom first and then magisk.
I've shorted the stick again and ran successfully ./gpt-fix.sh but it's still stuck at the black and white logo.
Probably I'll try to install the LineageOS to see what it looks like.
Click to expand...
Click to collapse
You may try returning the stick to stock,
fire stick 4k - return to stock?
Hello, can anyone link me to where I will find the windows drivers for the Firestick in fastboot mode? I have followed the above and entered fastboot which can be seen here: However powershell doesn't display and connected devices and I am...
forum.xda-developers.com
lock the bootloader again and do the whole process over.
I had this problem before with mantis and the only way I could get it to work again (Unlocked/Rooted) was by locking it down back to stock, letting the stick do all the ota updates :
Then after doing the short process over.
Adb Push to /sdcard
6.2.7.1 prerooted (or a rom of your choice)
Magisk 21.1 zip
Install prerooted first
Then flash magisk
Wipe dalvik/cache
Reboot
It's a pain in the ass and a long way to go but it workes in my case anyway. If your sticks not working then it's worth a shot
Thanks @Sus_i. Yes, I've tried to install a rom + magisk behind the gpt-fix, but it is still stuck in the black and white logo.
Thanks @Bertonumber1, I'll try your suggestion and I'll let you know.
Bertonumber1 said:
You may try returning the stick to stock,
fire stick 4k - return to stock?
Hello, can anyone link me to where I will find the windows drivers for the Firestick in fastboot mode? I have followed the above and entered fastboot which can be seen here: However powershell doesn't display and connected devices and I am...
forum.xda-developers.com
lock the bootloader again and do the whole process over.
I had this problem before with mantis and the only way I could get it to work again (Unlocked/Rooted) was by locking it down back to stock, letting the stick do all the ota updates :
Then after doing the short process over.
Adb Push to /sdcard
6.2.7.1 prerooted (or a rom of your choice)
Magisk 21.1 zip
Install prerooted first
Then flash magisk
Wipe dalvik/cache
Reboot
It's a pain in the ass and a long way to go but it workes in my case anyway. If your sticks not working then it's worth a shot
Click to expand...
Click to collapse
Thanks @Bertonumber1, I tried your suggestion, locking the bootloader again and doing the whole process over, but it still doesn't pass the b&w logo. I've attached step by step images.
@rpmuploads
Just curious, have you tried to boot the stick without the otg stuff? Powered via the orig. usb cable/power supply?
Sus_i said:
@rpmuploads
Just curious, have you tried to boot the stick without the otg stuff? Powered via the orig. usb cable/power supply?
Click to expand...
Click to collapse
yep , id second that .....its the only thing else that i can see stopping your 4K booting up as everything else seems bang on.