Related
I've read through hundreds of similar threads and haven't been able to find a solution - I'll gladly give up my firstborn (and/or make a paypal donation) to anyone who is able to help solve my issue!!
From my research, I seem to have no OS installed on the Kindle, and as far as I can tell, I'm booting into fastboot mode (screen hangs on the blue/white Kindle Fire logo, screen does not ever dim). I AM able to access TWRP Recovery, but don't have any backup to load from, am unable to successfully flash the ROM that I have saved to my SD card. My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles. Typing ADB Devices into Command Prompt gets me: [device number ] offline. Typing fastboot devices into Command Prompt gets me nothing (blank line).
Background/How I 'Bricked' It: I have a Kindle Fire 2 and was able to successfully unroot/flash Cyanogenmod 10 onto it. Worked perfectly for about 6 months, when I decided that it would be a good idea to flash back to stock so that I could give it to a relative. I have TWRP 2.3.3.0, so I used a guide on xda to do the following:
I used a guide from xda and followed these instructions
-Download latest KF2 stock software from amazon. Re-name the file to update.zip
-Moved it to the root of the SD card
-Booted in to TWRP
-Factory Wipe/Restore
-Wiped Cache
-Wiped Dalvik Cache
-Wiped System
-Installed the "update.zip"
-Wiped cache/dalvik again
-Rebooted
Unfortunately, wiping the system seems to have wiped the CM10 OS (ROM) that I had installed, and there was a failure in installing the amazon stock:
Installing '/sdcard/download/update.zip...
assert failed: is_substring ("Otter2 , file_getstring("/proc/product_name"))
E: Error in /sdcard/download/update.zip
(Status 7)
Error flashing zip '/sdcard/download/update.zip'
Updating partition details...
Trying to reboot the system from TWRP results in a message that states: "No OS installed! Are you sure you wish to reboot?"
Investigating using ADB: So it looks like I have no OS on the Kindle Fire 2. This seems to be a problem because without an OS, I am unable to use adb (from what I've read, no OS = no way to accept/authenticate the computer RSA fingerprint to whitelist the kindle and allow adb to function). Trying to use KFU, KFFirstAide, or the Kindle UnBrick Utility results in Error: Device offline or Error: Device not found types of messages (I am assuming due to the fact that I can't "turn" adb on by accepting the RSA fingerprint prompt)
What does Device Manager tell me? My computer can 'see' the Kindle Fire in device manager [as I stated earlier: My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles] but going to My Computer and looking under mass storage devices, the computer doesn't seem to recognize the device as a USB storage device, which is a problem because I can't drag/drop or push/pull files to the SD card so I can't try to flash anything *other* than the original file that failed.
Fastboot Mode...? From what I can tell (http://forum.xda-developers.com/showthread.php?t=1668159), my device is in fastboot mode. My Kindle screen hangs on the blue/white Kindle Fire logo screen, which from what I understand is hashcode's bootloader/fastboot screen. However, when I look at the Hardware IDs in the device manager, it tells me that my hardware IDs are:
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
So...my kindle seems to be stuck on the blue/white fastboot screen, but register on my computer as the stock kindle fastboot? I'm not really sure what's going on there, and couldn't find too many people with the same discrepancy that I have...
I tried plugging in my cord (making sure to use a USB 2.0 port), going into Command Prompt and using some fastboot commands. (ie: fastboot flash bootloader \path\update.zip) but all I get is a <waiting for device> for a LONG time. As in, a few hours. Some basic googling/investigation seems to indicate that I don't have fastboot drivers installed, OR that I wasn't running fastboot in an 'elevated mode' but I haven't been able to find too many details about how to fix those, IF that is the problem.
TWRP 2.3.3.0: I can get into TWRP recovery just fine, although I can't seem to figure out how to get files onto my device. So I've tried re-installing the original update.zip file that failed the first time several times, with no success. trying to 'Mount' the device doesn't seem to do anything (at least, my computer doesn't see the device as USB storage regardless of whether it's mounted or not) I tried using Advanced --> ADB Sideload, but trying to send the file in Command Prompt using the adb sideload <filename> command just gets me an Error: Device not Found message. I thought maybe I could try Advanced --> Terminal Command, but have no idea how to do that or what it does, and most sites are very vague about the step-by-step details, so I didn't really touch it.
Not sure if this is relevant or not, but when my KF2 is plugged into (attached) to my computer with the cord and is in TWRP, device manager shows the device under 'Other Devices' --> Amazon Kindle Fire2, and there is a yellow triangle on it. Not sure why...going back to 'fastboot' mode gets rid of yellow triangles and is recognized as a Kindle Fire again.
At this point - I'm pretty much stumped and have (hopefully) demonstrated that I've done my best to do my own research/read through threads/done due diligence. Is there anyone out there that might have any suggestions? Or do I now have a very large paperweight?
ANY input/suggestions/encouragement is welcome! I absolutely and sincerely appreciate your time in reading through this thread and trying to help noobs like me!
Use fast boot mode to recover to stock: http://forum.xda-developers.com/showthread.php?t=2096888
Or
If you have access to twrp. Use the ADb sideload feature to push CyanogenMod or another ROM over.
One thing though- if you can boot into TWRP you didn't wipe the system partition. Twrp for kf2 requires a file named stack to be there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
...tried those, but maybe am doing them incorrectly?
mindmajick said:
Use fast boot mode to recover to stock: http://forum.xda-developers.com/showthread.php?t=2096888
Or
If you have access to twrp. Use the ADb sideload feature to push CyanogenMod or another ROM over.
One thing though- if you can boot into TWRP you didn't wipe the system partition. Twrp for kf2 requires a file named stack to be there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Trying to use the ADB sideload feature to push CM or another ROM over doesn't seem to be working for me (unless I'm doing it wrong?)
I tried using Advanced --> ADB Sideload, but trying to send the file in Command Prompt using the "adb sideload C:\users\Name\update.zip command just gets me an Error: Device not Found message". Could I be using the command incorrectly?
Trying to use any fastboot command in Windows Command Prompt results in <waiting for device> to hang for hours, with no changes to command prompt and no changes to the kindle (still sits at the blue/white boot logo).
Ah. Sorry. Missed that in the OP.
Sounds like you probably need the drivers installed.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Fastboot Drivers
mindmajick said:
Ah. Sorry. Missed that in the OP.
Sounds like you probably need the drivers installed.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Are there difference drivers for fastboot and adb? I don't get a 'yellow triangle' and my device manager identifies the device as a Kindle Fire [Android ADB Interface], so I thought I was okay.
Should I be looking for fastboot drivers?
And btw, thanks so much for your willingness to help and input!
ME TOO
Just purchased a KF from someone...thay had rooted it...I tried to unroot...got stuck...now mine is doing the same as yours. I hope someone has a fix for you as I too have a large paperweight.
Follow Up
tessa33 said:
I've read through hundreds of similar threads and haven't been able to find a solution - I'll gladly give up my firstborn (and/or make a paypal donation) to anyone who is able to help solve my issue!!
From my research, I seem to have no OS installed on the Kindle, and as far as I can tell, I'm booting into fastboot mode (screen hangs on the blue/white Kindle Fire logo, screen does not ever dim). I AM able to access TWRP Recovery, but don't have any backup to load from, am unable to successfully flash the ROM that I have saved to my SD card. My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles. Typing ADB Devices into Command Prompt gets me: [device number ] offline. Typing fastboot devices into Command Prompt gets me nothing (blank line).
Click to expand...
Click to collapse
tessa33,
I just sent you a response. Call me at 707-774-5923 when you have a moment.
Solution?
I figured I could post in this thread before staring my own because I am having a very similar issue trying to revert my Kindle Fire 2 back to stock from cyanogen so I can sell it. I downloaded the official software from Amazon but every time I try to flash it through TWRP I get the exact same error you were getting. Did anyone ever figure out how to resolve the issue for you?
Had the same problem, so I chatted with an Amazon associate, told him I turned it on one day and it showed the grey triangle and he sent me a new Kindle Fire 2nd Gen for free. Try that...
Sent from my iPhone using Tapatalk
Hello
I have rooted KF2 and I did factory reset I lost TWRP&Os I can see the device as ADB device, Howeverm when the device in fastboot the pc not recognize it.
issuing fastboot devices command return nothing.
I used ubuntu and windows still the same issue. any idea?
First - sorry for my English. Last monday i received my KF2 and when I could not find the instructions on this forum for version 10.4.3 - i decided to try it myself.
Introducing: Kindle Fire 2 (v10.4.3 & v10.4.6 already tested) installing CyanogenMod
** YOU SHOULD HAVE A WORKING NORMAL (NOT FASTBOOT) CABLE + ADB DRIVERS/ACCESS ON YOUR PC. **
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
*** READ CAREFULLY BEFORE DOING ANYTHING ***
*** Kindle Fire 1st-gen ROMs/KERNELS are *NOT* compatible with the Kindle Fire 2. Please only flash ROMs/KERNELS that are made for the Kindle Fire 2. ***
** IF YOU HAVE QUESTIONS, RE-READ THROUGH THE THREAD FOR ANSWERS. WHEN YOU'RE ABSOLUTELY SURE NO ONE HAS ASKED YOUR QUESTION, GO AHEAD AND RE-READ THE THREAD AGAIN AND USE THE SEARCH FEATURE. THEN POST YOUR QUESTION IF YOU STILL CAN'T FIND THE ANSWER **
INITIAL SETUP INSTRUCTIONS
STEP 1. Install ADB Drivers for Kindle HD and enable ADB on tablet Settings->Security->Enable ADB->On
Check ADB:
Code:
C:\> adb devices
List of devices attached
0123456789ABCDEF device
If you do NOT see this, then make sure you have the SDK installed correctly and you have the right setup for ADB on your PC before proceeding.
STEP 2. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb pull /dev/block/mmcblk0boot0
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/boot
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/system # This will take a few minutes
Take those files and put them somewhere safe.
STEP 3. Getting root
Just follow this threat http://forum.xda-developers.com/showthread.php?t=2075959 -> everything working fine
STEP 4. Downgrade your bootloader
Download the older 10.2.4 bootloader file and flash to your device via fastboot:
http://goo.im/devs/Hashcode/otter2/otter2-u-boot-prod-10.2.4.bin
md5sum 5b03a7b428325de8d360ec201a745498
(You SHOULD check this before using fastboot -- downloads CAN be corrupted)
Open cmd and promt:
Code:
adb shell su -c "reboot bootloader"
Your Kindle should reboot in fastboot mode, and now flash bootloader:
Code:
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 reboot
STEP 5. Install TWRP
First, download CM and GAPPS and copy it to SDCARD:
CM-10.1 for the Kindle Fire 2 (choose the latest version from):
http://www.get.cm/?device=otter2
Google Apps from: http://goo.im/gapps (choose the top rom CM10.1 version)
1. Copy com.powerpoint45.FMKilo-2.apk to the tablet (you can get this apk from here http://d-h.st/n7L)
2. Enable on Kindle: Device -> Allow Installation of Applications
3. Use file browser (i recomended to use ES Explorer) to install apk.
4. Run Tweezermod Installer and answer on all question about Super User -> "Allow"
** If everything was done correctly you will at this point see the bootmenu with a BLUE logo during the reboot. **
In this time your kindle can not boot, u'll see BLUE logo, then ORANGE and then device restarted again. Don't worry - it's ok
STEP 6. Install CyanogenMod
TO ENTER RECOVERY:
During the blue logo screen press the power button to cycle through options and select "Recovery" to enter TWRP.
Once in TWRP you can Install" the CM-10.1 by selecting "Install" and then browsing the device and selecting it, then "Add Zip" and select the Gapps .zip as well.
Use the slider to start the install.
Dont forget to do FULL WIPE - cache, dalvik cache, factory reset, system.
Enjoy
Tested on my Kindle Fire 2 v10.4.3 & v10.4.6
7" KF HD 2, 10.4.6
This tutorial worked perfectly, up until the end, step 6.
I'm new to Kindle, but not Android. I got into TWRP prior to downloading CM10.2 and Gapps. And when i try to mount as USB, and this line shows in the log:
"Unable to locate volume information for USB storage mode"
Googling didn't help much with investigating that error. ADB sideload doesn't seem to work.
I don't know what to do from here.
pythonjosh said:
7" KF HD 2, 10.4.6
This tutorial worked perfectly, up until the end, step 6.
I'm new to Kindle, but not Android. I got into TWRP prior to downloading CM10.2 and Gapps. And when i try to mount as USB, and this line shows in the log:
"Unable to locate volume information for USB storage mode"
Googling didn't help much with investigating that error. ADB sideload doesn't seem to work.
I don't know what to do from here.
Click to expand...
Click to collapse
Check STEP 1 to check ADB. If it not working check this manual https:// developer.amazon.com/sdk/fire/connect-adb.html
When ADB start working - copy CM and GAPPS to kindle:
Promt in CMD:
Code:
adb push /path/to/filename /sdcard/download/filename
I'm also on Win7 x64.
When it is on ADB Sideload, I see in my Device manager Amazon Kindle Fire2, but it appears to not be loading the drivers correctly.
ADB Devices are not showing any attached devices. Ideas?
---------- Post added at 09:37 AM ---------- Previous post was at 09:29 AM ----------
Also in my Device Manager, Portable Devices, it shows F: but there's no F: in my windows explorer.
I found instructions via terminal emulator to get it rebooted into fastboot, in hopes of flashing CM 10.2 via fastboot.
Looking up the fastboot syntax for flashing a new rom, I've always used recovery on my other devices, but i don't have that option now.
pythonjosh said:
I'm also on Win7 x64.
When it is on ADB Sideload, I see in my Device manager Amazon Kindle Fire2, but it appears to not be loading the drivers correctly.
ADB Devices are not showing any attached devices. Ideas?
---------- Post added at 09:37 AM ---------- Previous post was at 09:29 AM ----------
Also in my Device Manager, Portable Devices, it shows F: but there's no F: in my windows explorer.
Click to expand...
Click to collapse
ADB Sideload - good idea. Try this manual:
1. Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
2. From the command line on PC, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
My mistake in manual. Better way - copy rom file to sdcard before STEP 5.
I'm still unable to use adb sideload, reports "device not found". I have the usb drivers installed, your tutorial is the only one I have used, I can't use TWRP at all.
It works, but USB drive mounting doesn't work, ADB sideload doesn't seem to work. No errors in the log, but ADB reports device not found.
I don't know what to do from here. It's nothing like 4EXT or CWM.
Ok so I have got it in fastboot by going to Advanced->Terminal, idme bootmode 4
Once in fastboot , fastboot -i 0x1949 devices returned a device number
I flashed CM10.2 using "fastboot -i 0x1949 flash system CM102.zip
Then I ran fastboot -i 0x1949 oem idme bootmode 1
Then rebooted, doesn't load ROM, got back into TWRP, changed bootmode back to 1, reboot, says I have no OS.
That's my current status. Seems others have been at this point before, still workin on this.
Ok you can give up on thinking now, I've bricked it. No signs of life.
I flashed the 7.23 bootloader and TWRP 2.6 from: http://forum.xda-developers.com/showthread.php?t=2128848
via fastboot, and now it's done for.
Found a rooted one on craigslist for $120 to replace this one for my father in law.
I've rooted a good few other Android devices, but never a tablet, first try on a KFHD2.
I give up on Kindle's.
pythonjosh said:
Ok you can give up on thinking now, I've bricked it. No signs of life.
I flashed the 7.23 bootloader and TWRP 2.6 from: http://forum.xda-developers.com/showthread.php?t=2128848
via fastboot, and now it's done for.
Found a rooted one on craigslist for $120 to replace this one for my father in law.
I've rooted a good few other Android devices, but never a tablet, first try on a KFHD2.
I give up on Kindle's.
Click to expand...
Click to collapse
Don't trash the old one after u get the new one, we have a viable method now to unbrick a hard bricked kindle. The person behind the fix is working on a more user friendly version of the device that doesn't require soldering. Check it out: http://forum.xda-developers.com/showthread.php?t=2391047
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
kindle fire 2 completely dead
:crying: after
Code:
fastboot -i 0x1949 reboot
, my kindle fire just shutted off and never response again, who can help me? :crying:
jeffrey00345 said:
:crying: after
Code:
fastboot -i 0x1949 reboot
, my kindle fire just shutted off and never response again, who can help me? :crying:
Click to expand...
Click to collapse
Assuming you have a Kindle Fire 2nd Generation, it's "hard-bricked."
Read the FAQ if you haven't already, specifically Q14 (although, read them all). Then, I would see if you can get Amazon to send you a replacement.
If they won't do that, take a look at this thread and this thread by me. As of now, I've succeeded in returning a hard-bricked KF2 to soft-bricked, but working out some bugs in order to return it to fully functional after that.
kurohyou said:
Assuming you have a Kindle Fire 2nd Generation, it's "hard-bricked."
Read the FAQ if you haven't already, specifically Q14 (although, read them all). Then, I would see if you can get Amazon to send you a replacement.
If they won't do that, take a look at this thread and this thread by me. As of now, I've succeeded in returning a hard-bricked KF2 to soft-bricked, but working out some bugs in order to return it to fully functional after that.
Click to expand...
Click to collapse
thanks for your reponse I would try to get a replacement from Amazon.
---------- Post added at 03:29 PM ---------- Previous post was at 02:59 PM ----------
kurohyou said:
Assuming you have a Kindle Fire 2nd Generation, it's "hard-bricked."
Read the FAQ if you haven't already, specifically Q14 (although, read them all). Then, I would see if you can get Amazon to send you a replacement.
If they won't do that, take a look at this thread and this thread by me. As of now, I've succeeded in returning a hard-bricked KF2 to soft-bricked, but working out some bugs in order to return it to fully functional after that.
Click to expand...
Click to collapse
I have contacted Amazon and they said that they would send a replacement to me but now I'm worried because I didn't tell them that it was my fault, I just told them the Kindle is not working.Is this ok?
Trying to make it work
I've followed the linked guide to installing the sdk and driver (windows 7 64 bit) and I still cannot get the adb devices to list the kf2. What am I doing wrong?
"STEP 4. Downgrade your bootloader
Download the older 10.2.4 bootloader file and flash to your device via fastboot:
http://goo.im/devs/Hashcode/otter2/o...rod-10.2.4.bin"
On 2nd gen Kindle Fire Non-HD. ver 10.4.6 rooted , can this step be completed without a fastboot cable?
I have the original usb cable. Maybe with Kindle Aide?
or tweezermod?
http://forum.xda-developers.com/showthread.php?t=2106463
Hello, I also I have the 10.4.6 rooted.
I have the same question that adaweawe, I can install bootloader / recovery with the original cable?
thanks
movesandpepper said:
I've followed the linked guide to installing the sdk and driver (windows 7 64 bit) and I still cannot get the adb devices to list the kf2. What am I doing wrong?
Click to expand...
Click to collapse
try other USB ports. one of my usb ports did not recognize. try install both driver exe from the zip.
Hello again.
I try, but I have a problem at this point:
fastboot-i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
Once put the kindle in fastboot mode, write the code in CMD and gets stuck saying <waiting for device>
What I'm doing with the standard USB cable.
edit
After trying on a USB, now the error is this:
target reported max download size of 486539264 bytes
error: cannot load otter2-u-boot-prod-10.2.4.bin
galaxyn84 said:
Hello again.
I try, but I have a problem at this point:
fastboot-i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
Once put the kindle in fastboot mode, write the code in CMD and gets stuck saying <waiting for device>
Click to expand...
Click to collapse
how you get into fastboot mode? did u try Kindle First Aide?
i'm hesitant to try install new bootloader + TWRP on my kf2 without fastboot cable:
" *Note: After several conference calls with the Amazon Development Team we found Amazon applied a patch to the Bootloader in an effort to lock down the Bootloader, this patch rarely causes the Bootloader to stick or Bootloop, please use the above link to release the Bootloader. We have removed this patch from the boot-prod.img eliminating future issues with recovered HD 8.9" users. "
http://forum.xda-developers.com/showthread.php?t=2096888
Click to expand...
Click to collapse
and
+Note: As of Amazon OS update 7.3.x+, there has been a lot of issues with rooting and flashing the 2nd-bootloader. Many users reported bootloops during the completion of the guide. Those with tablets running 7.3.0 or higher, please proceed with caution, and make sure you have a factory cable on hand if you wish to advance. I strongly recommend you make backups in Step 2.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2271909
applies to 2nd gen nonHD too i think
also hesitant to try tweezermod due to some bricks:
http://forum.xda-developers.com/showthread.php?t=2106463&page=4
I'm rooted and downgraded to bootloader version 10.2.3 and it still causes the red screen? I used the computer method and the terminal doesn't have any errors but recovery is not there. My Kindle Fire 2 is disconnected from wifi so it won't be updated to 10.4.1 Any idea why?
Click to expand...
Click to collapse
i really want to install cyanogenmod 10.1 on my rooted 10.4.6 without fastboot cable, but i think amazon updated bootloader to make it impossible without fastboot cable.
i disabled OTA updates and hope someone figures out 10.4.6 -> CM 10.1 without fastboot cable
adaweawe said:
how you get into fastboot mode? did u try Kindle First Aide?
i'm hesitant to try install new bootloader + TWRP on my kf2 without fastboot cable:
Click to expand...
Click to collapse
HI
I enter fastboot mode as shown in the tutorial
"" "" Adb shell su-c "reboot bootloader" "" "" "
I ask for superuser permissions, accept and restart in fastboot mode
Appear a black screen with fastboot logo in red, and a traffic light with flashing green light.
But I can not move from there ....
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
enjoyingsilence said:
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
Click to expand...
Click to collapse
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
monster1612 said:
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
Click to expand...
Click to collapse
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
enjoyingsilence said:
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
Click to expand...
Click to collapse
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
monster1612 said:
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
Click to expand...
Click to collapse
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
enjoyingsilence said:
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
Click to expand...
Click to collapse
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
monster1612 said:
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
Click to expand...
Click to collapse
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
enjoyingsilence said:
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
Click to expand...
Click to collapse
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
monster1612 said:
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
Click to expand...
Click to collapse
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
enjoyingsilence said:
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
Click to expand...
Click to collapse
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
monster1612 said:
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
Click to expand...
Click to collapse
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
edit: Found the latest CM ROM and Gapps files. Just need options for full recovery back to FireOS if needed in the end.
enjoyingsilence said:
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
Click to expand...
Click to collapse
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
monster1612 said:
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
Click to expand...
Click to collapse
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
enjoyingsilence said:
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
Click to expand...
Click to collapse
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
enjoyingsilence said:
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
Click to expand...
Click to collapse
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
monster1612 said:
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
Click to expand...
Click to collapse
Thanks. I was able to update twrp and get the 23rd of Dec's nightly CM12 build installed. It didn't seem to work properly though, and gapps wouldn't install. So I've resigned to the fact that I need to put the original OS back on it. After updating twrp, this doesn't seem possible. When I connect it to the computer, all I'm getting is error: device offline when typing adb shell. This is in linux and windows.
I tried connecting it and mounting the usb storage, then dragging over the fireos images, but after installation it went into this reboot loop due to a corrupt something or other... Now, I can't get cm or the original os back on it.
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
enjoyingsilence said:
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
Click to expand...
Click to collapse
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
monster1612 said:
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
Click to expand...
Click to collapse
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
enjoyingsilence said:
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
Click to expand...
Click to collapse
Do you have adb installed system-wide? If you do, try cd'ing to the directory where you placed the boot, recovery, and system images and then running those commands again. If you don't, then move the files to the folder where the adb and fastboot executables are located and run the commands in that folder.
Have read a ton on XDA and elsewhere, to the point that I have too much information, and I think it's likely someone with more experience could point me to the right area to focus on. Any help is much appreciated! Thanks!
Where I started:
Was a total noob, had never tried to flash anything or use command line
One day my stock Kindle Fire HD 8.9 just stopped working on its own. Not sure why -- I never tried to root it or hack into it. I had left it plugged in for a week and it felt a little warm.
Powering on would get to the orange/white Kindle Fire screen, and then the screen would go blank and stay that way until powering off.
I just wanted to get the Kindle running again, preferably with stock OS or something that still allowed me to use Amazon Instant Video.
What I've accomplished so far:
Successfully got fastboot running! Originally through First Aide and now through command line too.
Successfully got TWRP 2.8.7 running! Downloaded the TWRP image and used fastboot to flash recovery.
Also flashed kfhd8-freedom-boot-8.4.6.img and kfhd8-u-boot-prod-8.1.4.bin from the instructions on XDA's 2nd bootloader page.
Tried using both First Aide and the SR Tool to restore system back to stock, but neither seemed to do anything. Even flashed the system.img included with the SR Tool manually using fastboot, but Kindle still won't successfully launch. Also tried the "Restore 2 Stock" program, which says it cannot find a device in TWRP mode (likely related to my ADB issue cited below).
Where I'm at now:
Now when powering on (in normal mode), Kindle stays at orange/white Kindle Fire boot screen forever. Screen no longer goes blank afterwards.
Can get to TWRP, but only by using "fastboot oem recovery -i 0x1949"
Strangely, ADB NOT working. While in TWRP mode, I use command line "adb devices" and it returns "B0C91004245614ME Offline". I'm pretty sure I have the correct ADB drivers (while in TWRP mode, device manager shows two entries: "Kindle ADB Mode" and "Recovery ADB Mode").
Obviously I have no backups of original system/boot images because the Kindle broke on its own and I've never seemed to have ADB access.
Questions:
Is there something big I'm missing in order to restore to stock? Intuitively, it seems like I should be able to just flash a working system image from fastboot. If I can't restore to stock, I'm fine installing another OS -- would just like to get the device working again.
I doubt I would have enabled ADB access before the Kindle broke. Is that the reason that the "adb devices" command returns "Offline"?
Have not tried gaining root access. Is that a prereq for using ADB and/or restoring to stock?
-Joe
joes6789 said:
Have read a ton on XDA and elsewhere, to the point that I have too much information, and I think it's likely someone with more experience could point me to the right area to focus on. Any help is much appreciated! Thanks!
Where I started:
Was a total noob, had never tried to flash anything or use command line
One day my stock Kindle Fire HD 8.9 just stopped working on its own. Not sure why -- I never tried to root it or hack into it. I had left it plugged in for a week and it felt a little warm.
Powering on would get to the orange/white Kindle Fire screen, and then the screen would go blank and stay that way until powering off.
I just wanted to get the Kindle running again, preferably with stock OS or something that still allowed me to use Amazon Instant Video.
What I've accomplished so far:
Successfully got fastboot running! Originally through First Aide and now through command line too.
Successfully got TWRP 2.8.7 running! Downloaded the TWRP image and used fastboot to flash recovery.
Also flashed kfhd8-freedom-boot-8.4.6.img and kfhd8-u-boot-prod-8.1.4.bin from the instructions on XDA's 2nd bootloader page.
Tried using both First Aide and the SR Tool to restore system back to stock, but neither seemed to do anything. Even flashed the system.img included with the SR Tool manually using fastboot, but Kindle still won't successfully launch. Also tried the "Restore 2 Stock" program, which says it cannot find a device in TWRP mode (likely related to my ADB issue cited below).
Where I'm at now:
Now when powering on (in normal mode), Kindle stays at orange/white Kindle Fire boot screen forever. Screen no longer goes blank afterwards.
Can get to TWRP, but only by using "fastboot oem recovery -i 0x1949"
Strangely, ADB NOT working. While in TWRP mode, I use command line "adb devices" and it returns "B0C91004245614ME Offline". I'm pretty sure I have the correct ADB drivers (while in TWRP mode, device manager shows two entries: "Kindle ADB Mode" and "Recovery ADB Mode").
Obviously I have no backups of original system/boot images because the Kindle broke on its own and I've never seemed to have ADB access.
Questions:
Is there something big I'm missing in order to restore to stock? Intuitively, it seems like I should be able to just flash a working system image from fastboot. If I can't restore to stock, I'm fine installing another OS -- would just like to get the device working again.
I doubt I would have enabled ADB access before the Kindle broke. Is that the reason that the "adb devices" command returns "Offline"?
Have not tried gaining root access. Is that a prereq for using ADB and/or restoring to stock?
-Joe
Click to expand...
Click to collapse
Regarding your questions:
1) Hashcode created a TWRP-flashable ROM zip for Amazon's stock OS., which you can find in this thread. You should download the 8.4.1 version from the d-h.st link in the thread, as the goo.im links no longer work because Goo.im (a former file hosting service for Android developers) shut down. However, beware the d-h.st (Dev-Host) links, as they are notorious for causing unwanted downloads and popups. Do NOT download anything executable (the file we want is a .zip, not anything else), as it can cause unwanted software or even malware to be inadvertently installed onto your PC (and in some cases, your android device).
2) Yes, that is why the command returns "offline" when you run it with the kindle in recovery mode.
3) No, root is not a prerequisite for either of those commands. (In fact, you'd have to have adb enabled before rooting the stock OS in most cases.) However, should you need root, the stock ROM that Hashcode built as a flashable TWRP .zip is rooted, and as long as you don't update the OS, your root should remain intact.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Regarding your questions:
1) Hashcode created a TWRP-flashable ROM zip for Amazon's stock OS., which you can find in this thread. You should download the 8.4.1 version from the d-h.st link in the thread, as the goo.im links no longer work because Goo.im (a former file hosting service for Android developers) shut down. However, beware the d-h.st (Dev-Host) links, as they are notorious for causing unwanted downloads and popups. Do NOT download anything executable (the file we want is a .zip, not anything else), as it can cause unwanted software or even malware to be inadvertently installed onto your PC (and in some cases, your android device).
2) Yes, that is why the command returns "offline" when you run it with the kindle in recovery mode.
3) No, root is not a prerequisite for either of those commands. (In fact, you'd have to have adb enabled before rooting the stock OS in most cases.) However, should you need root, the stock ROM that Hashcode built as a flashable TWRP .zip is rooted, and as long as you don't update the OS, your root should remain intact.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thanks for the answers and explanations Monster. I downloaded Hashcode's 8.4.1 ROM zip, but I cannot figure out how to copy the zip file onto my Kindle, given that I don't have ADB access.
I did some research and it seems that one workaround is to use the Mount USB Storage feature within TWRP, but I can't get that to work. When I try to Mount USB Storage, no new storage drive shows on my computer (nor in Disk Management), and the TWRP error log says "Unable to mount storage. Unable to mount '/data'. Unable to mount '/cache'. Unable to find storage partition to mount to USB." Furthermore, the mount menu in TWRP says "Storage: Internal Storage (0 MB)" -- that doesn't seem good.
Do you have any other suggestions, either on how to get the zip file on my Kindle, or another alternative method to get my Kindle functional? Perhaps flashing something else directly from fastboot? Again, appreciate the help!
joes6789 said:
Thanks for the answers and explanations Monster. I downloaded Hashcode's 8.4.1 ROM zip, but I cannot figure out how to copy the zip file onto my Kindle, given that I don't have ADB access.
I did some research and it seems that one workaround is to use the Mount USB Storage feature within TWRP, but I can't get that to work. When I try to Mount USB Storage, no new storage drive shows on my computer (nor in Disk Management), and the TWRP error log says "Unable to mount storage. Unable to mount '/data'. Unable to mount '/cache'. Unable to find storage partition to mount to USB." Furthermore, the mount menu in TWRP says "Storage: Internal Storage (0 MB)" -- that doesn't seem good.
Do you have any other suggestions, either on how to get the zip file on my Kindle, or another alternative method to get my Kindle functional? Perhaps flashing something else directly from fastboot? Again, appreciate the help!
Click to expand...
Click to collapse
Boot into TWRP, then when you're in, choose Advanced -> ADB Sideload. Check the boxes that say "Wipe cache" and "wipe dalvik cache." Swipe where indicated to sideload, and hook up your kindle to your PC if it's not already connected. Type "adb devices" into a terminal/command prompt, and you should see a device that registers itself as "sideload" in the list. If you do, then type "adb sideload path/to/file.zip", where path/to/file.zip is the location of the downloaded 8.4.1 ROM zip. The ROM should automatically copy and flash; keep the kindle plugged in until the flashing process is complete. Any luck?
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Boot into TWRP, then when you're in, choose Advanced -> ADB Sideload. Check the boxes that say "Wipe cache" and "wipe dalvik cache." Swipe where indicated to sideload, and hook up your kindle to your PC if it's not already connected. Type "adb devices" into a terminal/command prompt, and you should see a device that registers itself as in "sideload" in the list. If you do, then type "adb sideload path/to/file.zip", where path/to/file.zip is the location of the downloaded 8.4.1 ROM zip. The ROM should automatically copy and flash; keep the kindle plugged in until the flashing process is complete. Any luck?
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, the adb sideload worked!!! (just had to update my adb version to 1.0.32) Kindle seems to be fully functional. Thank you so much Monster!
Last thing, do I need to worry about OTA updates or anything in the future that might create a conflict with the bootloader or ROM I'm using?
joes6789 said:
Yes, the adb sideload worked!!! (just had to update my adb version to 1.0.32) Kindle seems to be fully functional. Thank you so much Monster!
Last thing, do I need to worry about OTA updates or anything in the future that might create a conflict with the bootloader or ROM I'm using?
Click to expand...
Click to collapse
I believe that the OS is properly patched in Hashcode's stock ROM, so you shouldn't need to worry about OTAs or a conflicting bootloader. Glad to see it works again!
Sent from my Amazon Jem using XDA Labs
How were you able to get into fastboot with kf first aide? Which drivers and which options?
Gesendet von meinem Nexus 6P mit Tapatalk
I have a Motorola Z play which was running 7.1.1. It is a Verizon version, so it is said to be unrootable. But I tried it anyway.
I flashed twrp-3.2.1-addison first. After I did some thing (data wiping, etc), it does not reboot to normal os anymore. At one point, I noticed it says "no OS to boot into”. I searched online and found that the only solution is to install new rom. So I downloaded oreo zip and ran adb to sideload it to my phone. However it failed due to the following error:
Code:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Then I tried another option which is to save the zip to my phone and install it in recovery mode ( installed twrp this way). When I opened my phone with PC, it is empty. I tried to drag the zip file to the root dir of my phone, I got the following error:
Code:
Cannot copy item
The device has either stopped responding or has been disconnected.
I think it probably had to do with the data wiping. "adb devices" still shows the device is connected with the ID though.
How do fix this?
jiddy0001 said:
I have a Motorola Z play which was running 7.1.1. It is a Verizon version, so it is said to be unrootable. But I tried it anyway.
I flashed twrp-3.2.1-addison first. After I did some thing (data wiping, etc), it does not reboot to normal os anymore. At one point, I noticed it says "no OS to boot into”. I searched online and found that the only solution is to install new rom. So I downloaded oreo zip and ran adb to sideload it to my phone. However it failed due to the following error:
Code:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Then I tried another option which is to save the zip to my phone and install it in recovery mode ( installed twrp this way). When I opened my phone with PC, it is empty. I tried to drag the zip file to the root dir of my phone, I got the following error:
Code:
Cannot copy item
The device has either stopped responding or has been disconnected.
I think it probably had to do with the data wiping. "adb devices" still shows the device is connected with the ID though.
How do fix this?
Click to expand...
Click to collapse
Uhhh.......yeah I have the same phone as u and I'm pretty sure u just bricked your phone as the Droid version DOES NOT have a unlockable bootloader which u would need to be able to install the stock firmware/rom that came from the phone from the fact....
Sent from my XT1635-01 using Tapatalk
Yeah dude, you just bricked your phone probably. Take it to Verizon and hopefully they will help reset it to stock but since you put twrp on, they might not. Always unlock your bootloader unless following a guide that is SAFE for locked bootloader
so no way flash custom rom to verizon moto z play?