Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA!
Do you know if you had amazon FireOS version 5.0.1 or 5.1.1?
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
drillster said:
I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
Click to expand...
Click to collapse
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
hAtE NeVeR dIeS said:
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
Click to expand...
Click to collapse
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
blueberry.sky said:
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
Click to expand...
Click to collapse
I have 5.1.1... yeah, thanks.
blueberry.sky said:
Do you know if you had amazon FireOS ve wrsion 5.0.1 or 5.1.1?
Click to expand...
Click to collapse
I have 5.1.1.
blueberry.sky said:
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
Click to expand...
Click to collapse
Yeah I selected apply update from adb, adb devices was blank, didn't work.
blueberry.sky said:
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Click to expand...
Click to collapse
I went into fastboot mode, installed twrp, and nothing happened because yes, its 5.1.1.
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
blueberry.sky said:
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
Click to expand...
Click to collapse
Do you have any ideas on how to do this? I would greatly appreciate it.
Thank you!
Since I haven't read anyone try it before, there would be some risk. I suppose you are already bricked, seemingly without a way to fix it, but you could brick it harder. You might be able to get adb working. I may not have any ideas on how to get adb working for you, but someone else might know. If you try flashing the stock OS via fastboot, there is a chance you could brick it in a different way.
The command would be
Code:
fastboot update <filename-of-stock-firmware.zip>
But we don't have a .zip stock firmware file. In twrp recovery you can just rename the .bin file to .zip & it works. Not sure if that will also work for fastboot. My guess is it won't work & might brick you.
Also be aware, on Fires that self-updated to FireOS 5.1.1 (or came with 5.1.1 new) you must only flash 5.1.1. Attempting to flash 5.0.1 will brick it 100% of the time & it's unrecoverable.
drillster said:
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
. . .
Click to expand...
Click to collapse
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
I have same issue.
[QUOTE=drillster;64617577]Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA![/QUOTE]
I did the same thing. Slim worked great, tried to flashfire CM12, ot bricked. Can get fastboot, but nothing else. Afraid to try update from fastboot.
I just want to say thanks to everybody who contributed, I'm really appreciative of the support, especially because I didn't expect it, haha! Listening to blueberry.sky I'm going to try the flashboot update, because it's either that or a bricked device. School just started so I got busy with that.
DoLooper said:
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
Click to expand...
Click to collapse
So when I have it in adb mode, the fire doesn't seem to show up anywhere in any of my devices, and I can only find it when it's in fastboot mode. So when it's in that mode, I've tried Android ADB Interface, Android ADB Composite Interface, and when I go back to adb sideload, it's just not there in device manager. I don't know what this means, so any speculation? But no matter what mode I'm in or what driver I'm using, I can't seem to get it to show up in adb when in sideload mode.
Again, thanks everybody, and I hope anybody else in the future with this issue can refer to this thread for a lead!
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I didn't rename the Slim and this is what I get:
C:\path\to\SuperTool>fastboot update Slim-ford-5.1.1.build.2.2b-20151210.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
drillster said:
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
Click to expand...
Click to collapse
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
thekrakah said:
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
Click to expand...
Click to collapse
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
drillster said:
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
Click to expand...
Click to collapse
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
thekrakah said:
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
Click to expand...
Click to collapse
On my device, I can get fastboot, but not adb. if I reboot from fastboot, I only get the
CM logo and it sticks there permanently until I power off. When I boot to fastboot, the screen is blank but my Windows PC can see the device and return the SN. I can issue the command to reboot to bootloader, but reboots to fastboot with "fastboot" in small letters at the bottom of the screen. What else can I try? Thanks for all the help offered so far.
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
blueberry.sky said:
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
Click to expand...
Click to collapse
When I try to get into recovery, it boots with a blank screen. At that point, I can connect to my PC, type fastboot devices, and it will show me device. Then I try to reboot-bootloader, and it reboots to fastboot, but this time it says fastboot on the screen. I can't seem to get to recovery
watch this video to see if it helps.
https://www.youtube.com/watch?v=RQLoH-ahjy4
Related
Okay, I have the Nexus 6 (T-Mobile), rooted stock. I also have the Nexus 10. On both, I tried to sideload the 5.0.1 OTA update... and it failed in the exact same manner.
Obviously, I'm doing something wrong, but I have no idea what.
I did the Nexus 10 on a Windows 7 box, and I'm trying the Nexus 6 on a Linux machine. Same. Exact. Problem.
What I'm doing is this:
adb reboot bootloader
Arrow up to recovery, hit the power button to select
Hold down the power button and press the up button
Select "Sideload from ADB" (can't remember the exact wording, but basically, that)
adb sideload <verylongfilename.zip>
The update starts... and gets to 48% on my computer, and then ends. (I don't mean that it pauses or hangs, I mean it "finishes" -- it's done and back at the prompt). On the phone, at that time, it says "system has been remounted r/w; reflash device to reenable ota updates"
So that's where I'm at. On my Nexus 10, I ended up wiping it and just doing the full stock image install to get 5.0.1 -- that worked fine. On my phone, though, I really don't want to lose my entire setup just to get the bump from 5.0 to 5.0.1.
Can anyone tell me what the heck I'm doing wrong? It has to be something I'm doing or something I have configured wrong or ... I don't know. But the process clearly works for many, many people, and the fact that I have the same problem with two different devices on two different computers... it has to be my process, or something I've done to my devices.
Both devices are rooted stock, with stock recovery.
Any help you guys can provide would be greatly appreciated!!
you cant update it via your phone. you need to flash the update via fastboot, while you are in your bootloader.
simms22 said:
you cant update it via your phone. you need to flash the update via fastboot, while you are in your bootloader.
Click to expand...
Click to collapse
Right, I'm not trying to do it from my phone, I'm doing it from my computer. What am I doing wrong with my adb sideload process?
commonplace said:
Right, I'm not trying to do it from my phone, I'm doing it from my computer. What am I doing wrong with my adb sideload process?
Click to expand...
Click to collapse
then why are you trying to sideload it???
download it via your computer, extract the files from the zip, boot your phone into the bootloader, connect it to your computer, run fastboot devices(to make sure that the computer sees your device, then run the flash-all script.
simms22 said:
then why are you trying to sideload it???
download it via your computer, extract the files from the zip, boot your phone into the bootloader, connect it to your computer, run fastboot devices(to make sure that the computer sees your device, then run the flash-all script.
Click to expand...
Click to collapse
I was following directions found elsewhere (AndroidCentral and another site). I see now that adb sideload is not the answer, and that fastboot flash IS.
Phone = upgraded. Thanks for steering me in the right direction!
I had rooted 5.0 and read on Google+ that update over the air would not work. I used this guide to update to 5.0.1 and lost no data, nor had to reinstall anything.
http://forum.xda-developers.com/nexus-6/help/help-5-01-wipe-t2970924
Hi all, I did a dumb thing and I took the recent Verizon OTA on my dev ed moto x with a custom recovery installed (TWRP).
Now my phone seems to always stop booting at recovery, then if i hit 'reboot system' from recovery, I can get into my system for about 2-3 minutes, and then it reboots to recovery again.
Any help would be greatly appreciated!
boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.
KidJoe said:
boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.
Click to expand...
Click to collapse
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.
switch81 said:
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.
Click to expand...
Click to collapse
First, if you can't boot your phone into Android, you can't use Rashr.
Next... ADB needs you to be up in Android, and have the "USB Debugging" options checked. Also, it can not be used to flash the components of the SBF/ROM like recovery.img.
Fastboot mode works with Fastboot.exe or mFastboot.exe... ADB commands do not work when the phone is in fastboot mode.
Here is what you want to do AFTER you have the stock reocvery.img you want to flash... (this is pretty much exactly what you did to flash TWRP on there in the first place, except you will be flashing a stock recovery.img instead)
have the latest Moto drivers installed. You can get them from -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Make sure you have the Android SDK/Platform Tools installed (don't know how, see -> http://mark.cdmaforums.com/ADB.htm )
You need the latest version of Moto's fastboot, and it needs to be put in your windows Path (there are steps on -> http://mark.cdmaforums.com/ADB.htm )
Once you have that... do the following...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in fastboot menu on phone.
Connect to PC.
open command prompt file and change to the folder you have your recovery.img you want to flash
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery recovery.img
mfastboot reboot-bootloader
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device will display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
You should enter STOCK recovery.
use the VOL DOWN Key to scroll and the POWER Key to select reboot.
The phone should reboot and and be ready for the update
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!
slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
I'm sure KidJoe will respond, but I found this thread of his very useful:
http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
switch81 said:
Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!
Click to expand...
Click to collapse
I was able to flash back to stock recovery and take the 212.166.3 build KXA21.12-L1.26-3 (which is still 4.4.4) OTA that Verizon is pushing out.
I didn't even have to disable Xposed or anything else. Then again, other than Xposed, root and twrp, I'm running stock. No tethering hacks, build.prop changes, no system files removed or renamed, etc.
---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------
slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
Yup., Clearing cache will delete the OTA ZIP file that was downloaded. So the next time you reboot, it wont try to install, instead you'll be back to being notified that an update is available asking you if you want to download it.
But yup, those instructions I just typed should work...
This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.
switch81 said:
This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.
Click to expand...
Click to collapse
The release notes on VZW's page only seems to mention bug fixes.. no real details.
So far I haven't noticed any changes.
It will likely be a required step to get to lollipop. So either take it now, or wait and take it later, just before you upgrade to Lolliop
Hey guys,
hope you can help me. Have a little problem: After trying to root my fire, it is in a bootloop and i don't know what to do. Hope you can help me. I guess it is bricked.
Thanks
EDIT:
I tried to sideload the software bin, but it didn't worked. Also my computer doesn't show the devices with "adb devices".
Also my computer doesn't show the devices with "adb devices".
Click to expand...
Click to collapse
Others have found that the fire will only show up on your pc after you select the sideload option on the fire. If it still doesn't show, try unplugging / replugging the usb. It seems to help some people to get it to appear. Also note that some devices will intentionally not allow you to flash bin if the battery level isn't high enough. It's a safety measure since running out of battery during a flash = brick. Be sure you're fully charged.
thanks, but..
Thank you for your response. I've tried everythin you said, but it didn't worked. Don't know what to do
cl.lio said:
Thank you for your response. I've tried everythin you said, but it didn't worked. Don't know what to do
Click to expand...
Click to collapse
If device is in adb sideload mode
Code:
adb devices
should return
Code:
G000HXXXXXXXXXXX.........sideload
if not drivers are not correct
Open device manager Settings>Devices>Device Manager
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
next
you may have to reboot pc
Hello, I'm a long time user of the forums I haven't had a new device to root since 2013 when I did my Nexus 7 FHD. I have always followed directions correctly and never bricked anything.... until now.
So anyway just got this tablet black friday sale and within minutes of opening the package I started to read up on rooting it.
I got into fastboot and started up TWRP_Fire_2.8.7.0 I made a backup on the device without error.
Then I installed UPDATE-SuperSU-v2.46 and tried to install open_gapps-arm-5.1-pico-20151129 but it failed.
I wiped cache/dalvik and rebooted. Now the tablet tries to boot into normal mode in a loop without success.
I have tried to get into recovery mode (volume down and power) but it fails and loops back to normal mode.
I can get into fastboot mode (volume up and power) and then back into TWRP however restoring the backup doesn't fix the boot loop.
I downloaded update-kindle-37.5.2.2_user_522053820.bin however I can't seem to figure out how to load it with TWPR sideload, and as I said I can't get into recovery mode.
Can anybody help me? @sd_shadow
EVOL-LOVE said:
Hello, I'm a long time user of the forums I haven't had a new device to root since 2013 when I did my Nexus 7 FHD. I have always followed directions correctly and never bricked anything.... until now.
So anyway just got this tablet black friday sale and within minutes of opening the package I started to read up on rooting it.
I got into fastboot and started up TWRP_Fire_2.8.7.0 I made a backup on the device without error.
Then I installed UPDATE-SuperSU-v2.46 and tried to install open_gapps-arm-5.1-pico-20151129 but it failed.
I wiped cache/dalvik and rebooted. Now the tablet tries to boot into normal mode in a loop without success.
I have tried to get into recovery mode (volume down and power) but it fails and loops back to normal mode.
I can get into fastboot mode (volume up and power) and then back into TWRP however restoring the backup doesn't fix the boot loop.
I downloaded update-kindle-37.5.2.2_user_522053820.bin however I can't seem to figure out how to load it with TWPR sideload, and as I said I can't get into recovery mode.
Can anybody help me? @sd_shadow
Click to expand...
Click to collapse
change update-kindle-37.5.2.2_user_522053820.bin to
update-kindle-37.5.2.2_user_522053820.bin.zip, place on sd card, install with twrp
Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery
sd_shadow said:
change update-kindle-37.5.2.2_user_522053820.bin to
update-kindle-37.5.2.2_user_522053820.bin.zip, place on sd card, install with twrp
Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery
Click to expand...
Click to collapse
:good: Awesome thank you very much, I thought about doing just that but figured I better ask the pros first.
I somehow missed that post on unbricking... :silly:
So let's say theoretically that someone in their first week of using an Android device (ever) were to boot up the TWRP recovery and wipe their Fire because YOLO. Would anyone have advice for any possible way to revive it? Here's a description of the device's state:
It boots the Amazon logo only, and adb lists the device as unauthorized. If I boot it in recovery it says it's in fastboot mode and adb doesn't recognize the device at all. (Edit: ) Fastboot does recognize it though, but I'm not sure of the best path to take since I can't use adb to push files to the device for reinstallation of the firmware.
So from my view it's a paperweight, and that's cool because what I did was all kinds of dumb (thinking I could still revive it after what I was doing). But before I use it as a door stop, I figured I might ask you guys what you'd do. I'm guessing maybe I boot from an image that allows me to push the firmware to the sdcard, then I can boot from TWRP recovery and install it, but the first image to use there is something I'm not yet sure of.
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
stultus2 said:
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
Click to expand...
Click to collapse
Thanks for the reply
I think that's along the lines of what I need to do, but I can't use adb sideload as adb no longer sees the devices in recovery. Fastboot does though.
stultus2 said:
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
Click to expand...
Click to collapse
Ah you know what, you just encouraged me to read over again and try one different thing. The CM recovery enables adb sideload, and I'm pushing the stock firmware to it now.
Thanks for the help
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
jgro1976 said:
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
Click to expand...
Click to collapse
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
MDV106 said:
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Click to expand...
Click to collapse
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
jgro1976 said:
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
Click to expand...
Click to collapse
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
jgro1976 said:
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
Click to expand...
Click to collapse
jgro1976 said:
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
Click to expand...
Click to collapse
Im guessing you finally realised they after getting the android icon with the red triangle u have to press volume up and hold it then tap the power key to enter the recovery. Good to know you managed to unlock the bootloader eventually.
A lot of people have been having issues with fastboot, especially on Windows machines . Try restarting the shell or use a different USB port on your computer?also maybe try a different driver version and see if it helps.