So my Kindle Fire HD 7(2012) is bricked after trying to factory reset CM12.1. I took some advice and tried to run some ADB commands and then ADB says device unauthorized. Since my Kindle is stuck at the TWRP boot screen I cannot accept the RSA key. What should I do?
wizahh101 said:
So my Kindle Fire HD 7(2012) is bricked after trying to factory reset CM12.1. I took some advice and tried to run some ADB commands and then ADB says device unauthorized. Since my Kindle is stuck at the TWRP boot screen I cannot accept the RSA key. What should I do?
Click to expand...
Click to collapse
Reboot into TWRP, select Wipe -> Advanced Wipe, and then check all the boxes and swipe to wipe. At this point, all your system, data, and cache partitions will be completely empty, so you will need to reboot into TWRP again (ignore the warnings about not having an OS installed or root), copy a ROM zip from your PC to the kindle's internal storage, and flash it. Once you have it flashed, you'll be starting with a clean state (much like a factory reset), so you should have the ability to set up the device again once the ROM fully boots and get ADB to work.
monster1612 said:
Reboot into TWRP, select Wipe -> Advanced Wipe, and then check all the boxes and swipe to wipe. At this point, all your system, data, and cache partitions will be completely empty, so you will need to reboot into TWRP again (ignore the warnings about not having an OS installed or root), copy a ROM zip from your PC to the kindle's internal storage, and flash it. Once you have it flashed, you'll be starting with a clean state (much like a factory reset), so you should have the ability to set up the device again once the ROM fully boots and get ADB to work.
Click to expand...
Click to collapse
Device is stuck at the TWRP boot screen so I can't do any of that.
Related
Problem: I believe my Fire OS was accidentally deleted in the process described by the video "How to install CM12 1 on the Amazon Fire 5th gen Tablet" by Rootjunky.
I've hit a roadblock in getting my new Kindle Fire 5th Gen. up and running with Cyanogenmod. I will lay a few things out: how I got to this point and what I've tried in attempt to resolve my issue.
After I had TWRP running on my tablet I performed the back-up step, the wipe step and began the installation. During the installation TWRP reported an exception declaring that I did not have enough space to install "open_gapps-arm-5.1-stock-20151122.zip". The only difference between my setup and Rootjunky's was that I had not copied "cm-12.1-20151116-UNOFFICIAL-ford.zip", "open_gapps-arm-5.1-stock-20151122" and "SuperSU-v2.46" to my external SD card but to my internal storage. I decided that this may have been the issue and REMOVED my SD card from my tablet, copied the files to the SD card from my PC and then reinserted the card. I tried to select the .ZIP files in TWRP but it failed to recognize that the card had been reinserted. At this point I selected for the device to reboot (in hopes of it recognizing the card) and all I was met with was the "Amazon" splash screen and no continuing boot load.
To remedy this I have tried:
• To flash via Fastboot but I do not have an unlocked boot loader. When I try to flash it says "not allowed" and if I try to unlock the boot loader using either "fastboot oem unlock" or "fastboot flashing unlock" I get no results. The device is recognized, by the way.
• To upload the original Fire OS from Amazon's website and load it through the adb sideloader. This uploads successfully but the boot is stuck at the animated "Fire" splash screen.
• Attempted to perform a factory reset by using the Amazon System Recovery menu.
• Searched for over 5 hours tonight trying to find a solution.
Overall I believe the question is how do I get my device booted back up so I can restart this process and give it another shot?
Thank you all for the help in advance.
-Skye
Fixed
I decided to try to boot once more before retiring for the night and it just magically began to work.
The "Fire" splash animation displayed as the device began to install system updates.
I would say what worked was installing the Amazon Fire OS via the side loader.
However, I am new to modifying mobile technology and would like to ask a few questions for anyone to answer who should come across this thread.
• What is stored truly as ROM within the device? In other words, is it possible for me to delete enough data that the device would truly become bricked?
• Is it possible to perform a clean wipe and install from an empty storage device? I have dealt with plenty of desktop operating systems and find that a fresh hard drive is the best way to go when introducing a new Linux flavor to a growing build.
I am aware that, with root privileges and 3rd party utilities, that I could clean the system myself. However, it is easier to perform a full wipe and start from scratch.
Thank you all again.
-Skye
CieloLumine said:
I decided to try to boot once more before retiring for the night and it just magically began to work.
The "Fire" splash animation displayed as the device began to install system updates.
I would say what worked was installing the Amazon Fire OS via the side loader.
However, I am new to modifying mobile technology and would like to ask a few questions for anyone to answer who should come across this thread.
• What is stored truly as ROM within the device? In other words, is it possible for me to delete enough data that the device would truly become bricked?
• Is it possible to perform a clean wipe and install from an empty storage device? I have dealt with plenty of desktop operating systems and find that a fresh hard drive is the best way to go when introducing a new Linux flavor to a growing build.
I am aware that, with root privileges and 3rd party utilities, that I could clean the system myself. However, it is easier to perform a full wipe and start from scratch.
Thank you all again.
-Skye
Click to expand...
Click to collapse
The locked bootloader should prevent the device from getting bricked.
There are several partitions in an android device the some of them are: bootloader, recovery, system, data, cache.
System is were the rom is installed, data is your apps, settings and updated system apps.
When you install a new rom, you need to do a factory reset, which wipes data and cache.
You can wipe system, but it is usually wiped as part of the installing rom process.
Data isn't usually wiped by the rom installer, in case you are installing as an update.
Thanks
Thank you for the reply!
-Skye
Help for others
For anybody who finds themselves in a situation where you have lost your OS and you have only access to the ADB and fastboot...
You can still reboot TWRP by holding the power + volume down buttons on to power up and access Amazon's recovery mode. In recovery mode select "boot from bootloader" to enable fastboot. Connect your device to your PC and ensure you have your device driver installed and enabled. From here, use the Android SDK's fastboot.exe to send the command "fastboot boot <twrp image>". This will boot TWRP for you and enable you to give the process another go without having to reinstall the Fire OS.
You may find all commands used in these processes by referring to the scripting code of Rootjunky's batch file that helps to automate this process.
-Skye
CieloLumine said:
For anybody who finds themselves in a situation where you have lost your OS and you have only access to the ADB and fastboot...
You can still reboot TWRP by holding the power + volume down buttons on to power up and access Amazon's recovery mode. In recovery mode select "boot from bootloader" to enable fastboot. Connect your device to your PC and ensure you have your device driver installed and enabled. From here, use the Android SDK's fastboot.exe to send the command "fastboot boot <twrp image>". This will boot TWRP for you and enable you to give the process another go without having to reinstall the Fire OS.
You may find all commands used in these processes by referring to the scripting code of Rootjunky's batch file that helps to automate this process.
-Skye
Click to expand...
Click to collapse
Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery
Sent from my KFFOWI using Tapatalk
I think this is the one advantage of a locked boot loader. It's kinda hard to hard brick. Recovery and kernel remains intact too.
Stock Android 6.0 with stock recovery, no root, locked bootloader. Ran the device out of internal storage by writing too many files to the application's data directory. The device crashed and now it goes black after the boot animation. Able to get to the bootloader and recover menus. Lots of data stuck on the device. Any advice on pulling the files or getting Android to start again?
Try wiping the cache in the recovery menu.
Red_81 said:
Try wiping the cache in the recovery menu.
Click to expand...
Click to collapse
Tried this already. Thanks for the suggestion!
Sorry, I didn't see that I your original post so I had to start at the beginning with the most simple suggestion.
Go to recovery and try to use the adb shell to copy off the data you want to keep. Maybe also try a backup from adb (I forget the command).
If you know of a program that is taking up alot of data in the data partition that you don't care about losing then you could try using the shell to delete that data file.
Otherwise, you may just have to factory reset and start over.
Dear friends I need help!
I've tried to flash my tablet but I've got an error message while flashing Katkiss 6.0
What I did:
downloaded Rom.(md5sum is OK)
my bootloader is ww_epad-11.4.1.17-20140711
recovery CWM v6.0.5.0
previous rom zoombi pop
/format data
wipe data factory reset
install zip from sd card. (from internal storage or micro sd card)
And I have got the following error (in attachement)
Please help, my tablet boot only recovery now.
Thanks in advance for the help
trying to boot in fastboot mode when children let me try that...
Edit: fastboot ok.
I placed the the files
KatKiss-6.0_TF701T_033.zip
open_gapps-arm-6.0-pico-20170120.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
In
C:\Program Files (x86)\Minimal ADB and Fastboot
ok I don't know how to proceed now.
Seems I cannot change the recovery from CMW to TWRP,
My bootloader is 11.4.1.17 and the tutorial to install TWRP says in capital red:
MUST BE ON A BOOTLOADER 11.4.1.27, 11.4.1.29 or 11.4.1.30
So how can I do?
I there a way to upgrade the bootloader to be able to install TWRP?
Or should I Flash the custom rom from fastboot?
My TF701 in not booting anymore.... only bootloader and recovery CMW
the positive thing is :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
15C3E10090400000011FA8580 fastboot
Please help
I have been able to flash CROMI X (unfortunately with strong battery drain) so CMW is able to flash but for some reasons not Katkiss 6.0.
I have been told that my problem is not ROM related... So it is recovery related?
What is the better option to get katkiss on my tablet? Flash the recovery to get TWRP even if my bootloader is 11.4.1.17 and the tutorial to install TWRP says in capital red:
MUST BE ON A BOOTLOADER 11.4.1.27, 11.4.1.29 or 11.4.1.30????
There is a technical reason about this warning?
Edit: I found this on an old post:
You can try this:
Download the stock recovery from here: http://droidbasement.com/db-blog/?p=3210
Copy the image to your fastboot folder.
Download the Asus firmware, unzip the file once and copy it to your internal SD.
Boot tablet into fastboot
Issue this command
Code:
fastboot boot recovery.img
Note: Do not flash the recovery, just boot it.
It should recognize the firmware file on your tablet and flash it.
Click to expand...
Click to collapse
Would this method work to get the latest stock rom from Asus?
Got your PM and will try to find some time at work today. Hang in there and don't do anything to make it worse
Ok, work was crazy busy so it took a bit longer.
If you flash a recovery that is incompatible with the bootloader nothing happens. Until you use the recovery... That could permanently brick the tablet. So heed the warnings, they are there for a reason.
Ok, let's try to get you on the latest bootloader. It's no suprise at all that nothing boots if you try to flash a Android 6 rom on an Android 4 bootloader....
Download either WW or US package from here: https://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
That zip contains the latest bootloader and a compatible TWRP recovery. Flash the zip in your current recovery just like any rom, then reboot.
When you flash a bootloader or recovery you actually write those files to the staging partition. On the next boot the bootloader will unpack it and write everything to it's proper place.
So it's essential that you flash, then reboot. Does not matter that the boot does not go anywhere. The first part, flashing the contents of /staging to it's partition(s), will happen anyway.
You should see a brief blue bar filling up when that happens. It does not take long.
Boot back into fastboot and check your bootloader version.
Enter recovery through RCK and that should be TWRP now.
Then format /data. Do not wipe it, format it. Do not interrupt it. Wait for it to finish even if it takes an hour (a full battery is a must before you start this). The format command is under the Wipe menu.
Unfortunately the formatting in this kanged TWRP is pretty buggy, but I still like it better than CWM.... If you get lots of error messages after the format (cannot mount this, cannot mount that) go into Wipe > Advanced > select Data > Change or repair file system > Change file system > choose ext3 and execute
Note: The button you have to swipe is pretty "sticky". Swipe it slowly and fully
Reboot to recovery
Go back into Wipe > Advanced etc and change the file system back to ext4
Reboot to recovery
Now everything should be ok, try to mount/unmount data.
Finally you are ready to flash Katkiss
If the bootloader flash does not work, we can try to flash Asus firmware in fastboot, but try the above first.
berndblb said:
Ok, work was crazy busy so it took a bit longer.
If you flash a recovery that is incompatible with the bootloader nothing happens. Until you use the recovery... That could permanently brick the tablet. So heed the warnings, they are there for a reason.
Ok, let's try to get you on the latest bootloader. It's no suprise at all that nothing boots if you try to flash a Android 6 rom on an Android 4 bootloader....
Download either WW or US package from here: https://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
That zip contains the latest bootloader and a compatible TWRP recovery. Flash the zip in your current recovery just like any rom, then reboot.
When you flash a bootloader or recovery you actually write those files to the staging partition. On the next boot the bootloader will unpack it and write everything to it's proper place.
So it's essential that you flash, then reboot. Does not matter that the boot does not go anywhere. The first part, flashing the contents of /staging to it's partition(s), will happen anyway.
You should see a brief blue bar filling up when that happens. It does not take long.
Boot back into fastboot and check your bootloader version.
Enter recovery through RCK and that should be TWRP now.
Then format /data. Do not wipe it, format it. Do not interrupt it. Wait for it to finish even if it takes an hour (a full battery is a must before you start this). The format command is under the Wipe menu.
Unfortunately the formatting in this kanged TWRP is pretty buggy, but I still like it better than CWM.... If you get lots of error messages after the format (cannot mount this, cannot mount that) go into Wipe > Advanced > select Data > Change or repair file system > Change file system > choose ext3 and execute
Note: The button you have to swipe is pretty "sticky". Swipe it slowly and fully
Reboot to recovery
Go back into Wipe > Advanced etc and change the file system back to ext4
Reboot to recovery
Now everything should be ok, try to mount/unmount data.
Finally you are ready to flash Katkiss
If the bootloader flash does not work, we can try to flash Asus firmware in fastboot, but try the above first.
Click to expand...
Click to collapse
Thanks a lot to take time to help me.
Will try that tonight and I'll let you know the result.
Thanks a lot!
It was just like you said.
I had to format to ext3 and ext4 because I had errors.
Battery seems to be very good. Just the screen display is very white, needs color saturation and contrast I guess...
Thanks again you save my tablet.
Now that's what I like to read! :cyclops:
Hi, i'm just installed Tesla-gemini-7.1.2.RC.v4.3-Official-20170708-1851 on xiaomi mi5
After reboot my device ask for pattern to startup my phone, but it didn't accept my pattern, it says wrong pattern and i can't access my files.
But when i try to enter my pattern on TWRP to access my files. it works.
Any advice to recover my device, or disable encryption on my device using TWRP ?
Currently i'm backup my files using TWRP MTP mode, just in case i fail my last attemp, because unfortunetly i'm only have 1 attem to try unlock my device on boot, before it erase all my files.
Have try wipe data factory reset, and flash other rom but still unable to boot into system, the system still need pattern to startup the phone
Okay, this problem fixed :
1. Reboot to TWRP and Enter pattern
2. Backup your's data using MTP mode on Mount menu to PC
3. Reboot again to TWRP and don't enter your password or pattern (click cancel)
4. Wipe Data and Cache (THIS WILL WIPE ALL YOUR DATA INCLUDING ON SDCARD !!!!!) make sure all your important data backed up
5. Reboot to recovery and mount to MTP mode
6. Copy ROM to phone and install it.
So i was trying to install Liquid Remix rom on my op3t i wiped everything as the manual and have flashed opengapps magisk and the rom but when rebooted into the rom it asked me for my pin ive entered my pin but it said ur pin is correct but ur data has been corrupt u have to factory reset and automatically boots into twrp and when i try to boot into the system the process over and over again and i factory reset it nothing again says data is corrupt and ive flashed my recovery and try to boot into system nothing boots into fastboot iveand being a dummy i am i delted the system everything heard that u can fix it with adb sideloader but my question is can i flash a custom rom notthe stock rom please help me
Try to format data instead of wiping, either do it within TWRP (Wipe > Format Data > type "yes") or fastboot:
Code:
fastboot format userdata
Please note that all data is going to be lost, in case you didn't make a backup yet (if it's even possible to do it, since it says that data is corrupted).
przemcio510 said:
Try to format data instead of wiping, either do it within TWRP (Wipe > Format Data > type "yes") or fastboot:
Code:
fastboot format userdata
Please note that all data is going to be lost, in case you didn't make a backup yet (if it's even possible to do it, since it says that data is corrupted).
Click to expand...
Click to collapse
i already did that on accidentand deleted everything even the backups
Something similar happen to me. I was in twrp and was performing a full wipe(not factory reset), I installed RR, kernel, and then when I was installing gapps, the phone rebooted, and when I tried anything, it said e: legacy property not found( or something similar) and would not boot to system, would not flash anything, wouldn't boot to bootloader, but I was able to transfer files and use adb so I plugged into the computer and used adb reboot fastboot and booted to bootlaoder, now everything works
tergeltengo said:
i already did that on accidentand deleted everything even the backups
Click to expand...
Click to collapse
Backups are supposed to be stored outside the device you make a backup of, keep that in mind for future
Immortalis said:
Try to format data instead of wiping, either do it within TWRP (Wipe > Format Data > type "yes") or fastboot:
Code:
fastboot format userdata
Please note that all data is going to be lost, in case you didn't make a backup yet (if it's even possible to do it, since it says that data is corrupted).
Click to expand...
Click to collapse
Thank You, saved my phone.