I think I messed up my fire tablet 7(5th gen) - Fire Q&A, Help & Troubleshooting

I flashed cyanogenmod onto my Fire tablet 7 gen 5 and it all worked fine. However I decided to remove the trebuchet launcher to save space and it caused random crashes so I tried to use flashfire to reflash cyanogenmod and my device will get stuck on the boot screen(I left it on for a solid 15-20 minutes). The method I used to flash doesn't use TWRP and I couldn't get supertool to install TWRP(it would fail everytime) so I linked the picture of the recovery my device is using. Is my device bricked or is there any way to fix my device?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

This is the picture if the link doesn't work
drive.google.com/open?id=0BydfdK3oLqJRTWhIUlcybElQdTQ
This is the method I used to flash cyanogenmod
reflectivecode.com/2016/03/installing-cyanogenmod-12-1-on-the-amazon-fire-2015/

berttheturt said:
I flashed cyanogenmod onto my Fire tablet 7 gen 5 and it all worked fine. However I decided to remove the trebuchet launcher to save space and it caused random crashes so I tried to use flashfire to reflash cyanogenmod and my device will get stuck on the boot screen(I left it on for a solid 15-20 minutes). The method I used to flash doesn't use TWRP and I couldn't get supertool to install TWRP(it would fail everytime) so I linked the picture of the recovery my device is using. Is my device bricked or is there any way to fix my device?
Click to expand...
Click to collapse
berttheturt said:
This is the picture if the link doesn't work
drive.google.com/open?id=0BydfdK3oLqJRTWhIUlcybElQdTQ
This is the method I used to flash cyanogenmod
reflectivecode.com/2016/03/installing-cyanogenmod-12-1-on-the-amazon-fire-2015/
Click to expand...
Click to collapse
Obsolete guidance. And no - you can't install TWRP on this device.
Reinstall FireOS 5.3.1 following guidance in this thread/video. Then return to this forum for instructions on how to root 5.3.1 and properly prepare device for the installation of a custom ROM. Once you have CM 12.1 working again think twice about removing trebuchet (or any other system component) even if you prefer a different launcher. Those pesky system apps serve a purpose including fallbacks should something go wrong with user installed alternatives. If desired you can move just about any app (including most system apps) to a suitable SD card using Link2SD or similar tool that leverages symbolic links. The native Apps2SD functionally is a crap-shoot at best for reasons that are beyond the scope of this post.
As an aside, if you want GAaps don't go for anything larger than mini (nano recommended) due to limited free space in the system partition - regardless of ROM.

Thanks so much, that worked perfectly
Davey126 said:
Obsolete guidance. And no - you can't install TWRP on this device.
Reinstall FireOS 5.3.1 following guidance in this thread/video. Then return to this forum for instructions on how to root 5.3.1 and properly prepare device for the installation of a custom ROM. Once you have CM 12.1 working again think twice about removing trebuchet (or any other system component) even if you prefer a different launcher. Those pesky system apps serve a purpose including fallbacks should something go wrong with user installed alternatives. If desired you can move just about any app (including most system apps) to a suitable SD card using Link2SD or similar tool that leverages symbolic links. The native Apps2SD functionally is a crap-shoot at best for reasons that are beyond the scope of this post.
As an aside, if you want GAaps don't go for anything larger than mini (nano recommended) due to limited free space in the system partition - regardless of ROM.
Click to expand...
Click to collapse

Related

[RECOVERY] Cyanogen recovery for Nexus 5

EDIT: Post removed since there's an official download now!
Just open download.cyanogenmod.org, choose your device and download the latest recovery
Much fun! Thanks CyanogenMod!
How to get back the automatic recovery update!
I activated 'Update Cyanogen update' but it doesn't work?!
Okay, so you activated the option + flashed a new build and Cyanogen recovery is still not there? Here's what's the cause and how to fix it:
Some third-party recovery systems (e.g. TWRP) prevent to be overwritten by deactivating the automatic recovery update function. This happens by renaming the file /system/recovery-from-boot.p into recovery-from-boot.bak.
To get that functionality back:
- Rename /system/recovery-from-boot.bak back to recovery-from-boot.p
- Execute /system/bin/install-recovery.sh to actually install Cyanogen recovery.
Both steps can be done with CM file manager. You have to give the app root access!
After performing the steps above you can use 'Update Cyanogen recovery' for the future builds to keep your recovery up to date.
You can use this method if you don't want to download/use the img file above or don't want to regularly update the recovery manually.
Questions:
If you have any questions don't hesitate to ask in this thread! I'm not a developer but I'll try my best to help you out
Note to users: I'm not responsible if you brick your phone.
Note to admins/moderators: I'm not a developer / contributor of CyanogenMod and not associated with Cyanogen, Inc. in any way. If this thread is inappropriate, please move/delete it.
Reserved
Seems like you're not having trouble with CM recovery. I've tried this before using the 2nd method of renaming and executing. I might go back to CM recovery in a while. I notice the latest TWRP 2.8.5.2 is not really clearing the data partitions of my device. Already gave you a +1 on the CM thread, but I will still give you one for this thread! Nice job!.
Yeah.. it's working fine for me
Thanks for the first comment on this thread! Really appreciate it
Just want to clear this one, does "Wipe data/factory reset" includes internal storage?
No, it doesn't Or at least shouldn't It didn't format internal storage on CWM and TWRP and the same should apply for CM recovery Would be freaking thankful if you could try that (of course backup ur internal storage before if you want to try)
experience7 said:
No, it doesn't Or at least shouldn't It didn't format internal storage on CWM and TWRP and the same should apply for CM recovery Would be freaking thankful if you could try that (of course backup ur internal storage before if you want to try)
Click to expand...
Click to collapse
Okay, I will. I'll report back soon.
@Moderators:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just wanted to pop into this thread and say that I installed cyanogen recovery (homebrewed)- it seems fine- gestures work well. There is no option to wipe system, but hey, dirty flashing is the in thing nowadays. Life is too short to wipe data and and then restore it from backup.
I did install PA gapps with cyanogen recovery - the PA script and the recovery graphics fight each other, but it's not like I have to look at it all the time. There is a lot of scrreen flashing between the script output and the little android dude. If you blink your eyes fast enough, you can see just one or the other.
Yeah, i also found out that CM recovery tries to 'hide' what's going on so that you can only see the green Andy Looks weird with PA GApps but works fine with official CM nightly builds
Am I able to update official nightlies with cyanogen recovery?
is the touch screen swipe based or touch based?
Did you even read the OP?
I removed my Google Drive link with the image files since there's an official download now!
hammerhead-recovery: http://download.cyanogenmod.org/?device=hammerhead
hammerheadcaf-recovery: http://download.cyanogenmod.org/?device=hammerheadcaf
Have fun!

[HELP] Storage is full on Google Play but system has access to app-lib

Hi, this is my first time rooting and android phone, so please excuse me if this sounds like a dumb request. I've been going about this for almost 2 days and ran out of options. First off, here is what I'm using:
- Redmi S2
- Android 9
- Root: Yes, Magisk 20.4
- MIUI 11.0.2 stock (flashed after I wiped system data by accident before my first backup)
So, my issue is the following: whenever I try to install an app through google play or attempt to download a Magisk module, the system fails to do so. In particular, Google Play shows a "Storage is full, please remove any of these apps:" message, however, I have about 20GB left from my storage. I googled this plenty, and came up with this solution: https://forum.xda-developers.com/general/general/how-to-fix-insufficient-storage-t2855191, which says that I have to give access to the system user to the app-lib folder in order for things to install. However, when I check the permissions on this folder (and its subfolders) I can see that the permissions for them are already granted to the system, as can be seen here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Besides that, I have cleared caches, wiped data storage and system, and reinstalled Magisk many many times since, but none of these have helped with this issue. Something to note here is that if I uninstall Magisk, I can download apps again. It is only when Magisk is installed that the system is unable to access the storage.
Please if someone has any idea on how to fix this I'd be the most thankful!
Possible solution
Jandresgomez said:
Hi, this is my first time rooting and android phone, so please excuse me if this sounds like a dumb request. I've been going about this for almost 2 days and ran out of options. First off, here is what I'm using:
- Redmi S2
- Android 9
- Root: Yes, Magisk 20.4
- MIUI 11.0.2 stock (flashed after I wiped system data by accident before my first backup)
So, my issue is the following: whenever I try to install an app through google play or attempt to download a Magisk module, the system fails to do so. In particular, Google Play shows a "Storage is full, please remove any of these apps:" message, however, I have about 20GB left from my storage. I googled this plenty, and came up with this solution: https://forum.xda-developers.com/general/general/how-to-fix-insufficient-storage-t2855191, which says that I have to give access to the system user to the app-lib folder in order for things to install. However, when I check the permissions on this folder (and its subfolders) I can see that the permissions for them are already granted to the system, as can be seen here:
Besides that, I have cleared caches, wiped data storage and system, and reinstalled Magisk many many times since, but none of these have helped with this issue. Something to note here is that if I uninstall Magisk, I can download apps again. It is only when Magisk is installed that the system is unable to access the storage.
Please if someone has any idea on how to fix this I'd be the most thankful!
Click to expand...
Click to collapse
I had the same problem 2 years ago. What I did was buy another phone (an iPhone). It didn't fix the problem, but a friend of mine was very happy. Strongly recommended.
XiaomiFixer69 said:
I had the same problem 2 years ago. What I did was buy another phone (an iPhone). It didn't fix the problem, but a friend of mine was very happy. Strongly recommended.
Click to expand...
Click to collapse
Stupid solution [emoji1787]
Enviado do meu ASUS_I001DC através do Tapatalk

Samsung Tab A7 SM T500 Update to Android 11

First, an editorial comment:
For the money this is a great device. Compare it to the Flagship Tab S7 ($650 Fall 2021 - 128GB) versus the Tab A7 at $180 (32GB with a few $ more for a MicroSD). It is quick, plenty of storage with the MicroSD, and about the right size.
But my Rooted Tab A7 (via Magisk) kept bugging me about updating. It even started restarting in an effort to update itself.
I spent way too long yesterday reading instructions for updating to Android 11. It seems that everyone wanted to make it harder than it needed to be.
It isn't that difficult:
No loss of Data, apps, etc.
The details below have numerous steps, mostly for the unfamiliar. But there really are just three steps
Download the update
Use your existing Magisk installation to create a magisk-patched AP_T500
Flash it using Odin
DEVICE
Galaxy Tab A7 SM-T500, previously rooted with Magisk
Download Oden, the latest version. I used Odin3 v3.13.1_3B_PatcheD. https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Download the Android 11 update. There are several ways to do this (Google it.) I found that the old standby, SamMobile lacked the latest update. I used https://samfrew.com/download/Galaxy__Tab__A7__-Wi-Fi-__/wte0/XAR/T500XXU3BUF3/T500OXM3BUF3/
Inside the ZIP file you'll find AP_T500XXU3BUF3_CL21871393_QB40910992_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5
Move that to the Tablet. I put it in the root of the MicroSD card.
Open Magisk. Top Right, tap Install. Radial Button (put little black dot in circle) "Select and Patch a File"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tab LET'S GO
Magisk puts the patched file in your Download Folder of your internal memory (the internal directory called "sdcard"
Move patched file magisk_patched-XXXXX_XXXX.tar to your computer (for convivence, the same folder as your unzipped SM-T500_1_20210617XXXXXX
Open Magisk and Turn off all your Magisk modules. (If your modules are all compatible with the version you're going to this is ok but mine were not which sent my tablet into a bootloop after the update)
Now unzip Oden, from step #1, into that same SM-T500_1_20210617XXXXXX folder (for convivence.)
Turn your Tablet OFF
Launch Odin
Boot to Download Mode - hold BOTH the VolumeUP and VolumeDOWN buttons down ans simultaniously plug in your Samsung USB-C , THAT IS ALREADY CONNECTED to the PC
Put the BL_T500XXU3BUF3_XXXXX???.md5 in the Odin BL, the HOME_CSC_OMC_OXM_T500OXM3BUF3_XXXXX???.md5 in the CSC and the magisk_patched-XXXXX_XXXX.tar in the AP
Tap the Tab Start
That should do it.
16. Open Magisk and uninstall the module and reinstall compatible modules
If you forget to turn off the Magisk modules and end up in a bootloop, hold the volume up button. The the tablet should go into Safe Mode which will cause magisk to disable all the modules. Manually reboot from Safe Mode
CREDITS
https://www.thecustomdroid.com/install-ota-update-rooted-android-device-guide/
https://forum.xda-developers.com/t/...-t860-without-wiping-data-using-odin.4250457/
I would have stayed with Q. Even Q is too restrictive with trusted apps, R went Apple wild.
There are reasons I don't want an Apple, Android is moving in the same lame direction trying to make a "safer" OS. Predictable and unacceptable.
Security was never an big issue for me when using Android... you just need to take out the trash.
My conclusion, you lose more than you gain with Android 11 and above.
Go ahead Gookill, prove me wrong...
if you can big sister☠
if i get this right, by flashing the new ota updatet firmware version with home_csc i will not get a fatory reset ?
Gianni_10 said:
if i get this right, by flashing the new ota updatet firmware version with home_csc i will not get a fatory reset ?
Click to expand...
Click to collapse
yes
Mister Monday said:
yes
Click to expand...
Click to collapse
but both firmware needed to be either non rooted or rooted right?
Gianni_10 said:
but both firmware needed to be either non rooted or rooted right?
Click to expand...
Click to collapse
No.

(ROM)(A5)(Stock)(8.0) N'CreamOSv2 (Tweaked, Deodexed, Busybox, DeKnoxed, Decrypted and Rooted)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer
I am NOT responsible for bricked devices, dead SD cards or any
damage to you device. You are doing this at YOUR OWN RISKS. It's
reccomended to do a full SYSTEM BACKUP in case something went wrong.
Features
Tweaked with Build.prop for better experience
Deodexed for easy system apps modifications
DeKnoxed to remove annoying settings
Decrypted for keeping data when performing system changes trough TWRP of CWM recovery
Pre Rooted with Magisk to get superuser access and for some interesting advantages
Many others features coming from stock Oreo ROM
Busybox added to xbin
How to install
First of all, make sure you have downloaded the ROM flashable zip (Download link in bottom of this post)
Put the zip file in your phone storage or SD card if not already in
Reboot in custom recovery such as TWRP or CWM with hardware buttons (if not installed, this is a Tutorial)
Go to WIPE section and select advanced wipe
wipe Data, System, Preload, Cache-Dalvik, Cache and Internal Storage (I highly recommend to do a full backup of your ROM BEFORE WIPING)
Now, go back to home and to INSTALL section
Select storage where the ROM zip is stored and choose it
Start the operation with -zip signature check- unchecked or it will fail
If everything goes well, reboot to system and after booted, complete the setup wizard
That's it
Devices supported
Samsung Galaxy A5 2017 (SM-A520W) the one which i have tested (works fine)
Maybe F, K, L and S variants (Tell me if it works please)
Not for DS (dual sim) versions and Snapdragon
Requirements
A computer (for custom recovery flash)
Latest Oreo bootloader unlocked (developpers options from settings)
SD card (at least 4Gb)
Internet connection
A minimum of knowledge in Samsung phones
TWRP/CWM/OrangeFox recovery installed
Downloads
flashable rom zip file---------- N'CreamOS_8.0_v2_a5y17lte
Thanks to
AndroDef------ For his helpfull Classy Kitchen XDA Link
Topjohnwu------ For his irreplacable Magisk Root Magisk Github
sfirmware.com------ For the stock TAR.MD5 file SM-A520W(XAC)
If you see some bugs, please inform me
its just like samsung experience, i relly like it )
It is working fine on my Galaxy A520F Exynos Model, so you can check that out from the compat. checklist. For some reason the os thinks this is a A520W, but this is a F Model. I had a problem where TWRP said that flashing failed with error 7, but then I restarted it and I flashed it and it worked. Also you actually don't need a SD Card for the flasheble zip, you can actually just turn MTP on and Mount the DATA partition and copy the zip from your computer to your phone. This ROM is pretty good!
Oops, wrong post.

[MODULE] [Discussion] Data / Internal Storage Backup module for rooted / Magisk devices with TWRP

First I would just like to say this module mysteriously appeared on fox magisk module manager a few weeks ago and I am not the coder.
Links to backup & restore module on github:
GitHub - ziandzivan/data_backup: User Data backup creator from system for Google Pixels and other devices. (subsequent restoring by data_restore.zip script)
User Data backup creator from system for Google Pixels and other devices. (subsequent restoring by data_restore.zip script) - GitHub - ziandzivan/data_backup: User Data backup creator from system f...
github.com
GitHub - ziandzivan/data_restore_Courier: Courier-module for delivering to user and updating a Script data_restore.
Courier-module for delivering to user and updating a Script data_restore. - GitHub - ziandzivan/data_restore_Courier: Courier-module for delivering to user and updating a Script data_restore.
github.com
I tried both of them and they work pretty good / fast with a few bugs, such as: Using OTG storage causes the backup to work slow and fail,maybe it's the OTG I was using. I did this backup and restore operation on OnePlus 9 pro. It works fast if u backup to internal storage.
I know people are always looking for internal storage backup, I believe this module does the job.
You can backup without being in TWRP, but I believe this module requires people to be in TWRP recovery to restore internal storage backup.
/BUMP I noticed another few bugs with this script SOMETIMES. It does restore data and internal storage perfectly, but sometimes it may cause systemui to repeatedly bootloop. If that happens, you need to format everything and reinstall from scratch the firmware and then restore again the data backup
immortalwon said:
bugs, such as: Using OTG storage causes the backup to work slow and fail,maybe it's the OTG I was using
Click to expand...
Click to collapse
You have a trouble with your USB OTG. Use better SSD storage device or use intSD.
It works good. Here is mine (for example):
Spoiler: Pictures
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Restoring speed from SSD USB-OTG in TWRP:
from internal storage in running System :
So, you can see the restoring from my USB-OTG is faster.
Just out of curiosity has anyone tried side loading the restore zip to their phone with a temporary recovery such as lineage or some other similar aosp recovery? I read it supposedly works by flashing it through twrp although it's already on the phones internal storage. I wonder if someone could potentially edit the restore zip to tell the phone it's an update or a rom being flashed and make this work if it won't work as is. I may try this sometime just to see what happens. I imagine it won't be that simple or someone would have already done it but how awesome would it be if it did work!? IMO it would be the next best thing to having twrp on my pixel 7 If anyone has any thoughts or suggestions on how/if this could be possible please let me know!
Thanks,
DroidRommer

Categories

Resources