How to get in fastboot mode? - Amazon Fire Phone

Seems that the recovery has broken on my firephone,I cant sideload bin files anymore.how can i get in fastboot mode to flash recovery.img?Please help me and sorry for my bad english.
Sent from my SBM303SH using XDA Free mobile app

I "tortured" my device a lot during testing, never had that problem though. Recovery is rock solid (for now ^^).
What exactly happens when your phone is in recovery mode? Is your device still showing up when you try to use adb commands?
I guess you're not really talking about a literal *.img file...
You're from Japan?
regarding Hydros post: I think he's still able to get into adb / recovery, only the sideloading fails... (since he stated: "...can't sideload bin files anymore")

Boot Up. Enable adb and type
Adb reboot Bootloader

Bingo Bronson said:
I "tortured" my device a lot during testing, never had that problem though. Recovery is rock solid (for now ^^).
What exactly happens when your phone is in recovery mode? Is your device still showing up when you try to use adb commands?
I guess you're not really talking about a literal *.img file...
You're from Japan?
regarding Hydros post: I think he's still able to get into adb / recovery, only the sideloading fails... (since he stated: "...can't sideload bin files anymore")
Click to expand...
Click to collapse
Hi @Bingo Bronson. My fire phone is running rooted 4.6.1. I have removed many system apps. If I do a factory reset without sideloading stock 4.6.1 image, my
phone won't work since I removed dialer, sms, lockscreen, etc.
If I first do a factory reset first, then sideload stock 4.6.1 image, will my phone get restored back to working condition, just like what it was when i first started this phone?
Thanks

@ leonidas1573 In this case: Factory reset won't help.
Reason: It only resets the settings and data for the apps installed.
You have to sideload the stock image, reboot.
After that, it will work fine (And yes, you have start all over again with your configuration). I did about 5 times already ^^.
I will post a new guide next week, with apps / content / settings that are safe to remove.

Bingo Bronson said:
@ leonidas1573 In this case: Factory reset won't help.
Reason: It only resets the settings and data for the apps installed.
You have to sideload the stock image, reboot.
After that, it will work fine (And yes, you have start all over again with your configuration). I did about 5 times already ^^.
I will post a new guide next week, with apps / content / settings that are safe to remove.
Click to expand...
Click to collapse
Thank you for your reply. Yes, i did factory reset without sideloading the first time
I just sideloaded the stock image without factory resetting. It seems everything is working fine already I will try to wipe/factory reset, then sideload, make sure it's a clean phone before i start messing with the os again.

Yes, we would all like to know what's safe to remove.

@Bingo Bronson when i sideload ,it says
"E:failed to mount the cache(Invalid arguement)
E:cant open /cache/recovery/log"
my friend tell me this means that my rec is broken.
I dont know what i delete after root,cant start my phone,just stay on the fire logo.

@ dropiit
This is really bad. Cache partition is corrupt.
You would be able to fix this problem on any android device that uses an unlocked bootloader / custom recovery.
With the fire phone, you don't have any other options, only recovery mode (which is useless in this case).
I'm sorry, as far as I know, there is no solution to this problem for this device.
A "Factory Fastboot Cable" doesn't work / exist for this device (as well as Kindle HD latest gen. / HDX).
If you bought the phone directly from a retailer or Amazon, you might want to contact them first and ask how much it will cost to fix / replace the phone.

dropiit said:
@Bingo Bronson when i sideload ,it says
"E:failed to mount the cache(Invalid arguement)
E:cant open /cache/recovery/log"
my friend tell me this means that my rec is broken.
I dont know what i delete after root,cant start my phone,just stay on the fire logo.
Click to expand...
Click to collapse
How did this end up happening?

Related

[Q] Stuck trying to restore to stock

Hi guys,
I've been running custom AOKP rom and decided to return back to stock.
I have the rogers version of the M8, and intended to flash a stock TWRP backup of someone's rogers save.
I made the poor decision of relocking and unlocking the bootloader again, leaving me without a functional OS and with only fastboot and TWRP recovery available to me. As a result, I can't get the rogers backup folder onto my phone ( I don't have a miscro SD), and the only other option I see is to manually push each file in the stock TWRP recovery with ADB to my phone, but I'm horrible with anything that involves command lines.
Any suggestions to get me out of this situation would be great. My end goal is to get the stock ROM / kernel running so I can get OTA's.
Edit: Solved by doing an advanced wipe and format in TWRP, and I flashed a stock Rogers nandroid
Just adb push or adb sideload a stock rooted ROM to your phone. Just a single command line.
If you want OTAs, you will also need stock recovery. But my recommendation is that OTAs have no place on a modded device.
redpoint73 said:
Just adb push or adb sideload a stock rooted ROM to your phone. Just a single command line.
If you want OTAs, you will also need stock recovery. But my recommendation is that OTAs have no place on a modded device.
Click to expand...
Click to collapse
I've tried flashing a ROM and unfortunately I get stuck on the boot animation.
Attempting to wipe my phone through TWRP before the zip install yields a failure:
E: Unable to mount '/data'
E: Unable to mount internal storage
Those two lines are repeated a couple times in the error screen.
It looks like I need to flash some form of backup but am not sure which one will hard reset my phone to stock from this scenario.
Flashnova said:
I've tried flashing a ROM and unfortunately I get stuck on the boot animation.
Click to expand...
Click to collapse
Which ROM? How did you try to flash it (how did you get it on the phone, did you adb sideload?)/
Flashnova said:
Attempting to wipe my phone through TWRP before the zip install yields a failure:
E: Unable to mount '/data'
E: Unable to mount internal storage
Click to expand...
Click to collapse
Select "Mount" in TWRP main screen and make sure data is checked (cache should also e checked by default). If so, and still getting this error, di you by chance try to factory reset in bootloader (not TWRP)?
redpoint73 said:
Which ROM? How did you try to flash it (how did you get it on the phone, did you adb sideload?)/
Select "Mount" in TWRP main screen and make sure data is checked (cache should also e checked by default). If so, and still getting this error, di you by chance try to factory reset in bootloader (not TWRP)?
Click to expand...
Click to collapse
I flashed dirty unicorns 4.4.4. I had a 2gb SD card which managed to get it to the phone (the 2gb isn't enough to move the system backup).
I can't check Mount in the settings and it remains unchecked, and yes, I did hit the factory reset in the bootloader thinking that it would help me (I assume this was another bad decision).
Flashnova said:
I can't check Mount in the settings and it remains unchecked, and yes, I did hit the factory reset in the bootloader thinking that it would help me (I assume this was another bad decision).
Click to expand...
Click to collapse
Yes, that was a bad decision. But probably not one that you could have known about. Doing a factory reset in bootloader on a modded M8 corrupts the internal memory. This is your main problem right there.
If you have a Windows PC, connect the phone, go to Device Manager and find the phone. Then select the option to format the memory.
In the future only do a factory reset within the OS (in Settings) or in recovery, not in bootloader.
If you've gone through this much, I'd highly recommend getting comfy with a few command line commands. These may very well save you some time and additional headache (speaking from experience).
After recently running into issues with my newly purchased Roger's M8, I needed to restore to stock as well. Honestly, I followed these instructions to the T and it got me out scrape-free.
But, note Step #6 may require you to "adb push" your unzipped folder. And that's it.
Once you've ADB'd the massive nandroid backup, you should be out of the woods (in TWRP, Restore, Select the pushed backup file).
Good luck, and as long as you've got recovery/hboot looking back at you, you should be fine.
redpoint73 said:
If you have a Windows PC, connect the phone, go to Device Manager and find the phone. Then select the option to format the memory.
Click to expand...
Click to collapse
I'm not too sure where that option is located, would you know how to get there?
esuohe said:
But, note Step #6 may require you to "adb push" your unzipped folder. And that's it.
Once you've ADB'd the massive nandroid backup, you should be out of the woods
Click to expand...
Click to collapse
After pushing the folder to my device I receive "protocol failure", so the push isn't working unfortunately.
Flashnova said:
I'm not too sure where that option is located, would you know how to get there?
Click to expand...
Click to collapse
On Win7, go to Start Menu, use the search function at the bottom that says "Search programs and files" and type "Device Manager".
Or go to Start Menu>Control Panel>Hardware and Sound; and under "Devices and printers" you will see Device Manager.
Flashnova said:
After pushing the folder to my device I receive "protocol failure", so the push isn't working unfortunately.
Click to expand...
Click to collapse
You aren't going to be able to write to the memory when its still corrupt.
redpoint73 said:
On Win7, go to Start Menu, use the search function at the bottom that says "Search programs and files" and type "Device Manager".
Or go to Start Menu>Control Panel>Hardware and Sound; and under "Devices and printers" you will see Device Manager.
Click to expand...
Click to collapse
Device manager does not provide a format option. Perhaps you mean disk manager? If I do format it will I have to somehow reinstall the android system?
Flashnova said:
Device manager does not provide a format option. Perhaps you mean disk manager? If I do format it will I have to somehow reinstall the android system?
Click to expand...
Click to collapse
I've often read it described as Device Manager. Can't personally say from experience as I've never actually had to do it myself, but seen this described on XDA quite a few times. If the option comes up in Disk Management, that should be fine, too.
Formatting internal storage should not affect the Android OS, as its a separate partition (note how Windows is only reading the internal storage as around 25 GB of the total 32 GB). But you have to re-install a ROM anyway, as you presently do not have one installed.

Help with Nexus 7 (2013)

I have a Nexus 7 (2013) that I installed an Android 5.0 lollipop ROM on. I also had TWRP recovery installed. It was working fine. I took the OTA update for 5.0.1. It would not install with the recovery installed. Long story short, I believe I wiped something I shouldn't have. I can install the factory images using WUGS toolkit. The tablet boots and I can do the set-up. Wi-fi works, bluetooth works. I can't download files from the internet, I get a No SD card message. The play store, camera, gallery do not work. Trying to use the gallery I get a No Storage, no external storage available message. I'm not sure where to go from here. Any help would be appreciated. Thanks.
starrider1300 said:
I'm not sure where to go from here. Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Did you try a factory reset from recovery?
You should learn how to flash manually with fastboot, as you can see toolkits are not always helpful.
meekrawb said:
Did you try a factory reset from recovery?
You should learn how to flash manually with fastboot, as you can see toolkits are not always helpful.
Click to expand...
Click to collapse
I tried flashing with fastboot with the same results. When I go to recovery, all I get is the red triangle.
starrider1300 said:
I tried flashing with fastboot with the same results. When I go to recovery, all I get is the red triangle.
Click to expand...
Click to collapse
At the red triangle screen press power button and volume up at the same time and then let them both go. That should get you into recovery.
Or you can flash a custom recovery and use that.
Hopefully the factory reset will fix your problem.
meekrawb said:
At the red triangle screen press power button and volume up at the same time and then let them both go. That should get you into recovery.
Or you can flash a custom recovery and use that.
Hopefully the factory reset will fix your problem.
Click to expand...
Click to collapse
Thanks for the help. I got into recovery and did a factory reset. Tablet booted and I went through the tablet setup. Same results, no playstore, camera, or gallery. Can't download from the internet, shows no SD card.
I would try downloading the factory images directly from Google and flashing the whole thing. Once that flashes, you can run Chainfire Auto Root (CFAR) to get root back, if desired. Or you can flash TWRP and then flash SuperSU from within TWRP.
It sounds like your partitions may have gotten FUBARed.
I would highly recommend just staying with the "full" releases of ANY OS on any smart phone, as any x.x.1/x.x.2 etc can have more bugs than what is trying to be fixed in the original (not all cases, but some)
Using NRT I would suggest dropping back to 5.0 and COMPLETELY setting it back to stock (re lock boot loader, stock recovery, no root), then doing it OTA (if thats how you prefer to update) THEN re-root, re-unlock etc
Or just stay on 5.0 until something like 5.1 comes about
fury683 said:
I would try downloading the factory images directly from Google and flashing the whole thing. Once that flashes, you can run Chainfire Auto Root (CFAR) to get root back, if desired. Or you can flash TWRP and then flash SuperSU from within TWRP.
It sounds like your partitions may have gotten FUBARed.
Click to expand...
Click to collapse
Tried all the above with the same results. Any solutions for partitions that have gotten FUBARed?
starrider1300 said:
Tried all the above with the same results. Any solutions for partitions that have gotten FUBARed?
Click to expand...
Click to collapse
Seems like the actual flash storage could have issues... is it still under warranty? May need to send it in..
i have exactly the same problem and still no solution (since september)
I tried to wipe everything, twrp, cwm, factory , CM, omnirom ... something is broken in the storage folder and nothing can repair it. wiping maybe erase the data but doesnt seems to rebuild the tree
starrider1300 said:
I have a Nexus 7 (2013) that I installed an Android 5.0 lollipop ROM on. I also had TWRP recovery installed. It was working fine. I took the OTA update for 5.0.1. It would not install with the recovery installed. Long story short, I believe I wiped something I shouldn't have. I can install the factory images using WUGS toolkit. The tablet boots and I can do the set-up. Wi-fi works, bluetooth works. I can't download files from the internet, I get a No SD card message. The play store, camera, gallery do not work. Trying to use the gallery I get a No Storage, no external storage available message. I'm not sure where to go from here. Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
check if you can pull/push some files in bootloader mode .
use android platform tools :
Code:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
neo13oy said:
check if you can pull/push some files in bootloader mode .
use android platform tools :
Code:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
Click to expand...
Click to collapse
My son has the same model nexus 7 tablet. Are there any files that I can pull from his and then transfer to mine to restore my partitions?
starrider1300 said:
My son has the same model nexus 7 tablet. Are there any files that I can pull from his and then transfer to mine to restore my partitions?
Click to expand...
Click to collapse
No , I just suggest it to check if your internal SD card is damaged.
as you say , you can flash your partition with Nexus factory images but your data will be lost !!!

Nexus stuck in boot loop - unrooted - Backing up photos from bootloader or recovery

Hi.
Apologies if this is a very naive question, I am not particularly familiar with mods, roms and so forth.
I have rooted another phone in the past, but that is all.
The situation:
- Samsung Galaxy Nexus
- Not rooted/unlocked. Stock android automatically updated to the latest Android version supported
- Android developer option NOT set in settings
- Stuck in a boot loop: boots to android and then after a few seconds reboots, so no time to do anything
- Not sure how it happened, I had it for years, it was in my pocket and suddenly started doing that.
- Android fastboot and recovery loads up no problem
- I have tried anything I could find online to fix it: deleted cache, rebooted in safe mode, removed battery for 10 hours
- Nothing seems to fix it, it keeps rebooting
- I want to try a factory reset, but my family photos are in the phone
- Google synch seems to have stopped functioning for this device a year ago, all my 2016-17 photos and videos are locked in the phone.
Admitting there is nothing to do about the loop problem:
Is there any way I can copy photos and videos via usb while in recovery mode?
After I will reset the phone via recovery menu, hoping it will fix it. IF that does not fix it, I will flash another rom in. But I really do not want to wipe my data before backing them up.
I am assuming the answer is no, you cannot access the internal memory in fastboot/recovery unless your phone is rooted.
But I would like an expert opinion before I resolve to wipe one year of photos and videos which I will regret losing.
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
____Mdd said:
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
Click to expand...
Click to collapse
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
mcaldo said:
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
Click to expand...
Click to collapse
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
____Mdd said:
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
Click to expand...
Click to collapse
Thanks for the advice.
I followed the instructions closely, and nearly got there.
adb devices returns
#serialnumber sideload
so all good
but adb pull /sdcard returns
adb: error connect failed: closed
I tried several other commands with no success
kill-server and start-server work fine but do not solve the problem
adb usb returns
error closed
So, I am starting thinking that the problem is in the bootloader being locked.
However, if I unlock it, it will be wipe all my data, I understand?
Googling about it, I found this:
The behavior is status-by-design. Your stock recovery is not designed to grant shell access. Your only choice here is to somehow manage to flash a custom recovery. – Firelord Dec 30 '15 at 14:19
3
To achieve something similar to what @FireLord suggested: TWRP can be booted on many devices without being installed. For that, find a matching image, then boot to the bootloader and run fastboot boot twrp.img. Btw: you can check with fastboot devices resp. adb devices whether a device is visible to the corresponding tool. – Izzy♦ Jul 8 '16 at 19:40
So I understand one could boot TWRP without installing it, but I am not sure if that means I could do that with the bootloader locked?
I found WugFresh nexus root toolkit which seems to do that, among many other things, but again it warns that the phone must be unlocked (using the android build "Android *.* Any", I did not know what else to choose, not sure if that makes any difference as for locked/unlocked requirements)
EDIT: my fastboot screen reads "FASTBOOT STATUS - Failbootloader locked" as the last line, when trying to run TWRP without installing.
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
____Mdd said:
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
Click to expand...
Click to collapse
What actually you did ? Why it went into bootloop ???
Click to expand...
Click to collapse
A very good question, to which I have no answer, unfortunately.
The phone was used by my wife for 2 years and then by me for other 2. I recently changed the battery.
Never rooted or unlocked. No unusual apps installed. I am a very basic user, as you might have guessed, and being my only phone at the moment, I really would not risk experimenting with it.
It went very slow over the last 4 months, so I was planning to reset it.
I put in my coat pocket for a few hours, when I took it out it had a train ticked stuck to the screen and was quite warm and on the lock screen. It froze, so I took the battery out and restarted it. From then on it is stuck in a loop, not sure why really.
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex
Click to expand...
Click to collapse
That's good to know. I'll research more than.
It seems there might be a problem with the fastboot drivers on my computer, even selecting them from device manager did not work. Win7 refuses to install. The ADB drivers in theory work fine though.
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
____Mdd said:
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
Click to expand...
Click to collapse
Thanks so much.
Looking at google's documentation on the nexus:
You can remove data from your Pixel phone or Nexus device by resetting it to factory settings. Resetting to factory settings is also known as formatting the device or doing a "hard reset".
If you're factory resetting your device to fix an issue, make sure that you've tried all other troubleshooting options first. Find out how to troubleshoot your issue.
Important: Performing a factory reset will erase all data from the device.
Click to expand...
Click to collapse
It would seem that indeed all data will be removed.
This point, I will research a bit more into drivers, in case that is what it's preventing adb pull from working.
I really need a working phone, so if that fails I will hard reset, then unlock, root, flash in an alternative bootloader and perhaps a rom, and put ubuntu touch in dual boot. That will hopefully prevent me from loosing data in the future.
Sorry, this is out of topic to my question, but, , could you suggest any stable, solid rom for the nexus?
I read good things of CM12, and I ran into one which seemed to do to quite well with split windows, but I do not remember the name right now.
EDIT: I remember the name of the rom now, it's https://omnirom.org/about/
A last question if you can..
I tried to solve my boot loop problem by sideloading an update from google (maguro yakju yakju-jwr66y-factory-4cadea65.zip)
It loaded it fine but then failed because the installation it says it is not signed.
Basically, being a stock bootloader recovery from Samsung, it will only sideload OTAs from samsung, not the stock ones from google..
I cannot find the samsung ones anywhere, not for the nexus anyway, just the newer devices..
By any chance do you know where I could download proper Samsung OTA zip updates for the nexus?
Well, I talked with an android developer who confirmed that, unless you have a friend working in criminal forensic technology or similar, there is no way to get around a lock on this phone to pull data out.
So, sadly, I have wiped my phone by unlocking it, flashed TWRP and then omnirom with gapps.
My photos are gone, including a bunch of stuff my kid had made and asked me to photograph for safeeping. Very safe indeed
He kept asking me why they make the lock like that, instead of allowing some kind of password, perhaps he has a point.
So, it is quite unlikely that somebody who knows as little as I did will ever read this *before* finding themselves in the same situation.
But if you do, back up your data, unlock and flash TWRP, clockworks or some alternative, and thank yourself if and when disaster strikes..
@mcaldo wiping data/factory reset in STOCK RECOvERY will wipe everything... There is very few chances to get backup...
And yeah i found something interesting..
You can flash system.img.. only system files will be corrected not anything else..
Get appropriate zip from here : https://developers.google.com/android/images
Now take system.img to ADB/Fastboot folder ( i assume you know how it works )
Just go "Fastboot flash system system.img"
It will rewrite system partition..
Another one:
See downloads on this thread..
One says NON-WIPE, if you want me to try that zip, i will again require time for that. See here : https://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------
I don't saw your reply, it was on next page.. its sad... Sorry i am late..

Updated to 8.1 without disabling Substratum overlays... device now unusable

So, I tried flashing the 8.1 Final using Chainfire like a tutorial suggested. That was my second mistake.
My first mistake was not disabling my Substratum overlays before doing the above, even though I knew better. So anyway...
I knew something wasn't right the way my device rebooted in the middle of Chainfire doing its thing, and was on the G/progress bar for a long time. I decided to dirty flash the complete factory image, and I removed the '-w' from the flash-all script so it wouldn't wipe my data.
Now the device boots, and of course I have the System UI issue because I didn't clear the overlays. But wait... it gets better!
I found this thread which has ADB commands that supposedly fix this. So I fastboot booted into TWRP to run the commands. It asks for my password- and when I enter it, it says it's invalid!! I tried numerous times, rebooted etc, and it still does not accept my passcode.
It appears I should be able to use ADB in TWRP without my passcode, so I give it a try. I am able to sideload no problem, however when I type 'adb shell' it tells me 'error:closed'. I've searched that error, which everyone says was fixed for them with either a reboot or updating their adb/fastboot. I did both of those things, and the error still persists.
I have also tried sideloading the substratumrescue.zip file I found in another thread, however it doesn't seem to be made for this systemless setup or something.
I have had to set this device up twice since I got it, and I am really not looking forward to doing it a third time, so if anyone has any suggestions that will keep my data, I would be happy to hear them out!!
What could be causing TWRP not to accept my passcode?
Why do I get the 'error:closed' when I try to adb shell?
Any help is greatly appreciated!
Ran into almost the same thing last night (not using flashfire, but with the factory flash-all.bat). Forgot to clear my theme and got the system UI error with everything borked. Even had the invalid password in twrp.
I hate to say it, but I had to just flash the factory image with a wipe and start everything over. Lost all my pics and music from the few days I had the phone. I have now learned how not to update in the future.
IrocD said:
So, I tried flashing the 8.1 Final using Chainfire like a tutorial suggested. That was my second mistake.
My first mistake was not disabling my Substratum overlays before doing the above, even though I knew better. So anyway...
I knew something wasn't right the way my device rebooted in the middle of Chainfire doing its thing, and was on the G/progress bar for a long time. I decided to dirty flash the complete factory image, and I removed the '-w' from the flash-all script so it wouldn't wipe my data.
Now the device boots, and of course I have the System UI issue because I didn't clear the overlays. But wait... it gets better!
I found this thread which has ADB commands that supposedly fix this. So I fastboot booted into TWRP to run the commands. It asks for my password- and when I enter it, it says it's invalid!! I tried numerous times, rebooted etc, and it still does not accept my passcode.
It appears I should be able to use ADB in TWRP without my passcode, so I give it a try. I am able to sideload no problem, however when I type 'adb shell' it tells me 'error:closed'. I've searched that error, which everyone says was fixed for them with either a reboot or updating their adb/fastboot. I did both of those things, and the error still persists.
I have also tried sideloading the substratumrescue.zip file I found in another thread, however it doesn't seem to be made for this systemless setup or something.
I have had to set this device up twice since I got it, and I am really not looking forward to doing it a third time, so if anyone has any suggestions that will keep my data, I would be happy to hear them out!!
What could be causing TWRP not to accept my passcode?
Why do I get the 'error:closed' when I try to adb shell?
Any help is greatly appreciated!
Click to expand...
Click to collapse
What a mess hahah! It sounds like your password file got corrupt; doing all that dirty flashing is messy. If I were you I would connect the phone to a computer and get off what data you can (most stuff is cloud now days anyway). And flash a 8.1 stock factory image using fastboot on the bootloader. You can never go wrong with flash a stock factory image. Yes you loose your data, but you get a working phone haha. If your really worried about data see if you can get MTP to work and transfer it off.
Dumbass me
Yep, that was me yesterday. Genius me sideloaded the 8.1 OTA without disabling my Substratum overlays and so I was met with the "System UI Tuner has stopped" message. Then an automatic reboot to the bootloader asking me to either "Try again" or "Factory reset phone". Guess what I had to do to get my phone working again? Had to factory reset that sh*t.
Oh well, at least I made sure to unlock my bootloader this time around before setting up my phone.
But to be fair, would've been f*cked either way even if I had waited for the OTA because it's essentially the same thing as the zip file anyways. Lesson learned: disable Substratum when you update your sh*t.
Fastboot boot TWRP beta 2, and go to advanced and sideload the substratum recovery zip and it'll fix it
Strange. I didn't disable my Themes and I had no issues at all sideloading.
fantasy2c said:
Fastboot boot TWRP beta 2, and go to advanced and sideload the substratum recovery zip and it'll fix it
Click to expand...
Click to collapse
This is exactly what I did. When it asks for your password, click cancel and it'll let you get into twrp. Go to adb sideload and sideload the rescue zip. I've attached it below. When you boot, uninstall the old overlays, then build and enable them.
I only update once a month when a new patch comes out.
I set my apps to not auto update
After a new patch comes out in the first week of the month I
-disable the overlays and remove them
-update swift black and compile new overlays
-update all my apps
-adb to recovery and flash ota
-apply new overlays
- reboot and good to go
I have done it before to you can just boot TWRP as long as you have that rescues zip on your flash drive you can do it that way too
rajlulla said:
This is exactly what I did. When it asks for your password, click cancel and it'll let you get into twrp. Go to adb sideload and sideload the rescue zip. I've attached it below. When you boot, uninstall the old overlays, then build and enable them.
Click to expand...
Click to collapse
Thought I was screwed, Thank you so much for this post.
Try formatting your internal memory using TWRP. It should be "formatting", no other type of wipe will be sufficient. Then flash your favourite ROM and enjoy!

Unbrick Fire TV Stick 4K. Help!

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.

Categories

Resources