Related
I can't seem to figure out how to enter into recovery mode on my T-Mobile G4. It's running everything completely stock. I have tried holding power button and volume up until the logo comes on and releasing both buttons and then immediately holding them both down again waiting.. and nothing happens. I've even tried waiting for one second after I initially release to hold them down again. Same outcome. It always just boots back up into Android. I have tried volume down instead.. Nothing. Can someone please show me how to boot into recovery mode? Again, running stock rom.
I had the same issue. This is what I did to resolve it.
1. Enable Developer Options (see here).
2. root the phone (see here).
3. Download TWRP for the LG G4 H811 from here.
4. Install Flashify from the Play store.
5. Open Flashify and select Recovery Image -> Choose file and select the file from Step 2 to install TWRP
6. Reboot to TWRP from Flashify
When I was on the factory ROM I had to repeat steps 5 & 6 any time I wanted to boot into recovery (TWRP). None of the other boot options worked for me. Not button combinations and not even using adb (adb reboot bootloader). So what I did next is I decided to try another ROM. I installed one of the CM12.1 nightlies. Now running on CM12.1 I can boot into recovery without issue. I have no idea what is in the stock ROM that made it impossible to boot to recovery. I haven't been very motivated to go back to the stock ROM to do any further troubleshooting.
Demati said:
I had the same issue. This is what I did to resolve it.
1. Enable Developer Options (see here).
2. root the phone (see here).
3. Download TWRP for the LG G4 H811 from here.
4. Install Flashify from the Play store.
5. Open Flashify and select Recovery Image -> Choose file and select the file from Step 2 to install TWRP
6. Reboot to TWRP from Flashify
When I was on the factory ROM I had to repeat steps 5 & 6 any time I wanted to boot into recovery (TWRP). None of the other boot options worked for me. Not button combinations and not even using adb (adb reboot bootloader). So what I did next is I decided to try another ROM. I installed one of the CM12.1 nightlies. Now running on CM12.1 I can boot into recovery without issue. I have no idea what is in the stock ROM that made it impossible to boot to recovery. I haven't been very motivated to go back to the stock ROM to do any further troubleshooting.
Click to expand...
Click to collapse
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
From the T-mobile website: https://support.t-mobile.com/docs/DOC-21911
stringz90 said:
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
Click to expand...
Click to collapse
If there is a way I didn't find one. There very well may be a way to do this. I just didn't put in more than a couple of hours of effort.
That's not what I'm talking about. That's talking about factory resetting your phone with the hardware keys. I'm talking about entering recovery mode (kinda like the bios of the phone) using the hardware keys.. It's different.
Demati said:
If there is a way I didn't find one. There very well may be a way to do this. I just didn't put in more than a couple of hours of effort.
Click to expand...
Click to collapse
I'm starting to think T-Mobile did something different with their variant to disable people from entering recovery mode.. This is irritating. I'd like to have the option of doing so in case I need to re-calibrate my battery or anything else that I'd need access to the recovery for.
stringz90 said:
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
Click to expand...
Click to collapse
stringz90 said:
I'm starting to think T-Mobile did something different with their variant to disable people from entering recovery mode.. This is irritating. I'd like to have the option of doing so in case I need to re-calibrate my battery or anything else that I'd need access to the recovery for.
Click to expand...
Click to collapse
I have been trying a few different ROMs over the last few days. The modified stock ROM (Genisys) is pretty much the same as the stock minus some bloatware and it is rooted. I have no issue booting into recovery from it. Maybe that is worth a try for you?
Demati said:
I have been trying a few different ROMs over the last few days. The modified stock ROM (Genisys) is pretty much the same as the stock minus some bloatware and it is rooted. I have no issue booting into recovery from it. Maybe that is worth a try for you?
Click to expand...
Click to collapse
Alright.. I guess, I'll have to try that, but first is there any way to do a backup of some sort in case I have to go back to stock rom rooted? I got my G4 about a month ago and haven't done much research on rooting this specific device. I haven't had a high end phone with rooting and rom options in a long time. The last phone I had a chance to root and install cool custom roms on was a Samsung Galaxy S2. If you can guide me in the right direction I'd appreciate it. I guess I have to start from square one again. In the past I remember that in order to go back to completely stock you had to have a usb jib to reset the flash counter. Is it the same for this case? I welcome anyone's helpful input. Thanks, everyone.
I currently am trying to install CM12.1 onto my Amazon Fire 7, but unfortunately, it looks like I may have messed up in the process (I am stuck with the Amazon logo re-looping every ~15-20 seconds). I am able to go into the safe recovery mode, so I assume I haven't bricked the device completely, but I was wondering, what exactly is the best way to flash CM12.1 onto this device?
There seems to be an excessive amount of information, but very little organization, so would love to hear what the "best" steps would be to get CM12.1 on this bad boy.
I don't have the device yet but from what i read you need to tell us more info like what was your amazon v. 5.0.1 or 5.1.1 and how you install cm by TWRP or flash fire
Sent from my iPhone using Tapatalk
it will all depend on the version you have, but here you will find most info.
http://forum.xda-developers.com/amazon-fire/general/videos-tutorials-how-to-root-flash-roms-t3254268
shabuboy said:
it will all depend on the version you have, but here you will find most info.
http://forum.xda-developers.com/amazon-fire/general/videos-tutorials-how-to-root-flash-roms-t3254268
Click to expand...
Click to collapse
So I went ahead and installed the original firmware (5.1.1), but now am wondering where do I go from here. I have the device rooted and installed Flashify, but I am not sure how to install TWRP for 5.1.1, as I was using Rootjunky's .bat file.
darkgiant said:
So I went ahead and installed the original firmware (5.1.1), but now am wondering where do I go from here. I have the device rooted and installed Flashify, but I am not sure how to install TWRP for 5.1.1, as I was using Rootjunky's .bat file.
Click to expand...
Click to collapse
You can't install TWRP on 5.11, if you want to flash roms you have to use FlashFire now.
This is due to the 5.11 ota update including a bootloader update which removes the ability to fastboot boot.
Just follow the instructions to install CM 12.1 and wait for it to boot.
Ownster said:
You can't install TWRP on 5.11, if you want to flash roms you have to use FlashFire now.
This is due to the 5.11 ota update including a bootloader update which removes the ability to fastboot boot.
Click to expand...
Click to collapse
Yeah, so I just found that out few seconds ago. I tried to flash and install CM, but after the reboot, it just goes back to the FireOS "Optimizing system storage and applications..." screen, no idea what I am doing wrong...
I am also wiping everything too before I flash the CM and GAPPS zip files
darkgiant said:
I am also wiping everything too before I flash the CM and GAPPS zip files
Click to expand...
Click to collapse
I would be very careful using flashfire if your coming from fire os 5.1.1, we cannot use TWRP and a few people(myself included) have lost access to Amazon recovery, if you get stuck in a boot loop you have no way to recover your device, your best bet is to wait to see if a more secure way appears of flashing a device that has been using fire os 5.1.1.
abacabie said:
I would be very careful using flashfire if your coming from fire os 5.1.1, we cannot use TWRP and a few people(myself included) have lost access to Amazon recovery, if you get stuck in a boot loop you have no way to recover your device, your best bet is to wait to see if a more secure way appears of flashing a device that has been using fire os 5.1.1.
Click to expand...
Click to collapse
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
Click to expand...
Click to collapse
Glad it worked well for you. Not everyone has been so fortunate. One persons favorable experience does not equate to everyone. Some of those impacted are veteran users who 'lost' devices testing out code and techniques that you are now benefiting from.
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
Click to expand...
Click to collapse
If you read my post properly i said " lost access to Amazon recovery" , there is no way to transfer the file from ADB as ADB is not there, due to the fact that there is no Amazon recovery, holding volume down + power does nothing, if you look around the forum you will see this has happened to a few people myself included .
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
Click to expand...
Click to collapse
He's talking about how his device got buggered from a dirty Rom load. In his case and for a few others, they've lost the option to sideload back to stock.
Anyway here's the bare minimum process, since it sounds like you've gone through the details parts of Rom loading before.
#1 restore to stock rom 5.1.1
#2 install SuperSU/Root
#3 install flashfire
#4 install CM/SlimLP and Gapps (pico, micro, mini) of your choice, and your done.
When I put CM on my 5.1.1 Fire device, I installed flashfire.apk manually, used open Gapps pico, and the CM 12-30-2015 image.
abacabie said:
If you read my post properly i said " lost access to Amazon recovery" , there is no way to transfer the file from ADB as ADB is not there, due to the fact that there is no Amazon recovery, holding volume down + power does nothing, if you look around the forum you will see this has happened to a few people myself included .
Click to expand...
Click to collapse
Gotcha, didn't know there was level of increments the relooping represented. Well either way, hopefully something gets developed to all the "hard-bricked" users.
Hello,
I've recently installed CMOD 13 Marshmallow on my Xperia Z phone. I've decided that I also need Xposed app for other cool features but it seems that I've had to install some other I don't understand why things via Recovery. I was using TWRP to install CMOD 13 but when I've went back just to install this Xposed Frimware.zip file It wasint TWRP but CyanogenMod Recovery instead. I've tried to find out how to install it with this but no luck obviously... So then I found out that if I disable something I already don't remember what in developer options I can Install TWRP again with no big deal and this Android will stay without changing anything. I did just like that and just like that first time when Installing CMOD 13 it didn't boot up the OS but went to TWRP recovery. Once again I though eh ok who cares then Installed Xposed Frimware for Marshmallow and rebooted the device. Results are that It loaded the Sony logo but then the screen is black (working of course with light on the screen etc. yet it also goes to sleep if not touched for some time.). I don't know why did that happen and I don't know what to do. Anything I can do now? I can't even turn it off by holding the power button.
Regards,
Alex.
@frostp1 U can turn off the phone by pressing Power+Vol up until it vibrates 3 times
frostp1 said:
Hello,
I've recently installed CMOD 13 Marshmallow on my Xperia Z phone. I've decided that I also need Xposed app for other cool features but it seems that I've had to install some other I don't understand why things via Recovery. I was using TWRP to install CMOD 13 but when I've went back just to install this Xposed Frimware.zip file It wasint TWRP but CyanogenMod Recovery instead. I've tried to find out how to install it with this but no luck obviously... So then I found out that if I disable something I already don't remember what in developer options I can Install TWRP again with no big deal and this Android will stay without changing anything. I did just like that and just like that first time when Installing CMOD 13 it didn't boot up the OS but went to TWRP recovery. Once again I though eh ok who cares then Installed Xposed Frimware for Marshmallow and rebooted the device. Results are that It loaded the Sony logo but then the screen is black (working of course with light on the screen etc. yet it also goes to sleep if not touched for some time.). I don't know why did that happen and I don't know what to do. Anything I can do now? I can't even turn it off by holding the power button.
Regards,
Alex.
Click to expand...
Click to collapse
do this ^^ although the phone must have run out of battery, then you will have to root and install cm13 all over again
PS: You can flash it through cm recovery by going to '' Apply Update ''
Hi guys, I need help please!
I am using Samsung Note 3 SM-N9005 ARMv7 Lollipop 5.0. Rooted it with Kingoroot. "installed" TWRP through Flashify.
I downloaded Xposed Framework xposed-v86-sdk21-arm.zip onto my phone and installed it through TWRP in Flashify. Everything seemed fine, got the message install successful, I selected "reboot" instead of "clear cache/dalvik". Phone went into reboot...Samsung Note 3...Samsung logo...and stuck there. I understand that it takes some time for first boot, and I waited, but almost an hour and its still showing the same screen. So I tried to power off the phone, but it restarted again and stuck in the same logo screen. I tried to go into recovery mode hoping to get TWRP to do a reset or something, but no TWRP! Was only given option of "volume up - continue(to odin mode)" and "volume down - cancel(restart phone)". No option for factory reset either. So i booted odin, and tried to flash openrecovery-twrp-2.6.3.7-hlte.img.tar, got the messaged passed, phone rebooted and again stuck in Samsung logo. Tried recovery mode and still no TWRP! Please help!!:crying: :crying: :crying:
p.s. phone won't power off, only way to do it is to remove the battery.
Samsung phones stock ROMs need an special version of Xposed framework. Geez, it is on the official thread:
Known issues:
- Bootloops on Samsung stock ROMs. That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
Click to expand...
Click to collapse
Archy12 said:
Hi guys, I need help please!
I am using Samsung Note 3 SM-N9005 ARMv7. Rooted it with Kingoroot. "installed" TWRP through Flashify.
I downloaded Xposed Framework xposed-v86-sdk21-arm.zip onto my phone and installed it through TWRP in Flashify. Everything seemed fine, got the message install successful, I selected "reboot" instead of "clear cache/dalvik". Phone went into reboot...Samsung Note 3...Samsung logo...and stuck there. I understand that it takes some time for first boot, and I waited, but almost an hour and its still showing the same screen. So I tried to power off the phone, but it restarted again and stuck in the same logo screen. I tried to go into recovery mode hoping to get TWRP to do a reset or something, but no TWRP! Was only given option of "volume up - continue(to odin mode)" and "volume down - cancel(restart phone)". No option for factory reset either. So i booted odin, and tried to flash openrecovery-twrp-2.6.3.7-hlte.img.tar, got the messaged passed, phone rebooted and again stuck in Samsung logo. Tried recovery mode and still no TWRP! Please help!!:crying: :crying: :crying:
p.s. phone won't power off, only way to do it is to remove the battery.
Click to expand...
Click to collapse
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220
io_gh0st said:
Samsung phones stock ROMs need an special version of Xposed framework. Geez, it is on the official thread:
Click to expand...
Click to collapse
Thank you for you reply. Yes, I understand that, which was why I have been trying to find the correct version. Did a few searches using my phone type and version and found a list of sdk21.zips...so i selected the latest version..
mattzeller said:
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220
Click to expand...
Click to collapse
Thank you for your reply, I'll try that now.
mattzeller said:
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220
Click to expand...
Click to collapse
I tried it, unchecked "reboot", flashed TWRP, power off. When I tried button combo, I can't boot into recovery. It either keep giving me the restarting loop (power on, samsung note 3..then power off, and on again..) or if i let go of the power button at note 3, it goes to the samsung logo and stuck there.
update: I kept trying, and finally got a little different response. I pressed volume up + home + power buttons, and got 3 small lines of colorful words...
Recovery booting
Recovery is not seandroid enforcing
Set warranty bit : recovery
and then the phone turns off and start again
Tried different combinations, so far only the volume up sequence showed something a little different.
Archy12 said:
I tried it, unchecked "reboot", flashed TWRP, power off. When I tried button combo, I can't boot into recovery. It either keep giving me the restarting loop (power on, samsung note 3..then power off, and on again..) or if i let go of the power button at note 3, it goes to the samsung logo and stuck there.
update: I kept trying, and finally got a little different response. I pressed volume up + home + power buttons, and got 3 small lines of colorful words...
Recovery booting
Recovery is not seandroid enforcing
Set warranty bit : recovery
and then the phone turns off and start again
Tried different combinations, so far only the volume up sequence showed something a little different.
Click to expand...
Click to collapse
If you your phone does not boot into TWRP right after you flash it it will not stick and you need to flash it again. To get into recovery is power+home+volume up
Sent from my SCH-R220
mattzeller said:
If you your phone does not boot into TWRP right after you flash it it will not stick and you need to flash it again. To get into recovery is power+home+volume up
Sent from my SCH-R220
Click to expand...
Click to collapse
Could it be the TWRP versions doesn't work on my phone?
I tried openrecovery-twrp-2.6.3.7-hlte.img.tar and also twrp-2.8.7.0-hlte-4.4.img.tar both getting the same results "recovery is not seandroid enforcing" when I pressed vol up + home + power
Archy12 said:
Could it be the TWRP versions doesn't work on my phone?
I tried openrecovery-twrp-2.6.3.7-hlte.img.tar and also twrp-2.8.7.0-hlte-4.4.img.tar both getting the same results "recovery is not seandroid enforcing" when I pressed vol up + home + power
Click to expand...
Click to collapse
That is ok, you get that when you have modified system/recovery. Means your are not fully stock. If you had full stock unrooted unmodified system and recovery that goes away, nothing to worry about. If you are still having problems follow these step exactly:
1) Pull battery out of phone then put it back in
2) boot to download mode (power+home+volume down)
3) open Odin on computer (run as admin)
4) plug phone into computer
5) Uncheck a. Reboot and f. Reset time in Odin
6) flash TWRP (TWRP.img file goes in AP)
7) after successful flash unplug phone and pull battery
8) put battery back in and boot directly to recovery (power+home+volume up)
If you let it boot normally without going into TWRP first, it does not stick
Sent from my SCH-R220
mattzeller said:
That is ok, you get that when you have modified system/recovery. Means your are not fully stock. If you had full stock unrooted unmodified system and recovery that goes away, nothing to worry about. If you are still having problems follow these step exactly:
1) Pull battery out of phone then put it back in
2) boot to download mode (power+home+volume down)
3) open Odin on computer (run as admin)
4) plug phone into computer
5) Uncheck a. Reboot and f. Reset time in Odin
6) flash TWRP (TWRP.img file goes in AP)
7) after successful flash unplug phone and pull battery
8) put battery back in and boot directly to recovery (power+home+volume up)
If you let it boot normally without going into TWRP first, it does not stick
Sent from my SCH-R220
Click to expand...
Click to collapse
Thank you very much!!! I am finally able to boot into TWRP and did a restore, now my phone is back on!! Strange though, I was doing exactly those steps earlier but not successful. Anyways, Thank you very much!! <3
Oh, since I'm here, can you give me advise on which version xposed framework I should get? (Although I don't think my phone is touchwiz, is there a way to find out/confirm? I'm a noob as you can see)
Archy12 said:
Thank you very much!!! I finally able to boot into TWRP and did a restore, now my phone is back on!! Strange though, I was doing exactly those steps earlier but not successful. Anyways, Thank you very much!! <3
Oh, since I'm here, can you give me advise on which version framework I should get? (Although I don't think my phone is touchwiz, is there a way to find out? I'm a noob as you can see)
Click to expand...
Click to collapse
Ok, now that TWRP is on there things should be easier. You are on Stock ROM, it is TouchWiz. You will need to flash a custom ROM that is deodexed. If you like the stock look, feel, and options look in the threads for your device for a stock deodexed ROM. Or you can flash CM. Depending on what version of Android you decide to run will dictate which version of Xposed you install.
Sent from my SCH-R220
I am getting a note3 and wanted to install xposed on it. the phone is running 4.3. with that version there is no need for flashing correct? simply download apk and install?
mattzeller said:
Ok, now that TWRP is on there things should be easier. You are on Stock ROM, it is TouchWiz. You will need to flash a custom ROM that is deodexed. If you like the stock look, feel, and options look in the threads for your device for a stock deodexed ROM. Or you can flash CM. Depending on what version of Android you decide to run will dictate which version of Xposed you install.
Sent from my SCH-R220
Click to expand...
Click to collapse
I am quite used to the look and functionity of the current version I am using...which is lollipop 5.0. My phone is Samsung Note 3 SM-N9005 ARMv7 international Qualcomm. I'll need to flash custom ROM and then get a "matching" xposed framework,correct? Could you please direct me as to how to get xposed framework to work please?
Archy12 said:
I am quite used to the look and functionity of the current version I am using...which is lollipop 5.0. My phone is Samsung Note 3 SM-N9005 ARMv7 international Qualcomm. I'll need to flash custom ROM and then get a "matching" xposed framework,correct? Could you please direct me as to how to get xposed framework to work please?
Click to expand...
Click to collapse
Just go to the threads for your device and flash a TouchWiz based deodexed ROM
Sent from my SCH-R220
---------- Post added at 07:41 AM ---------- Previous post was at 07:38 AM ----------
trulosdoulos said:
I am getting a note3 and wanted to install xposed on it. the phone is running 4.3. with that version there is no need for flashing correct? simply download apk and install?
Click to expand...
Click to collapse
Correct, you would need this one:
http://dl-xda.xposed.info/modules/de.robv.android.xposed.installer_v33_36570c.apk
Sent from my SCH-R220
There is now an Xposed framework package supporting Stock (odexed) TouchWiz ROMS: http://forum.xda-developers.com/showpost.php?p=65373013&postcount=3960
i have absolutely no clue what i am doing here, i tried to reboot my tablet into TWPR menu
but i could not figure it out it has TWRP, and RR rom and root
i held the power button down and did reboot recovery and i did not get TWRP menu
so rebooted it and then i chose bootloader, and now all i get is a black screen that says fastboot..
holding power and it won't reboot it wont turn off or do anything
how do i fix this ****?
how do i get to the twrp menu screen?
how do i create a backup of my system to the SD card?
i want to try an experimental APK but i want to make sure i can recover if it messes up my tablet
but 1st how do i fix this?
gdroid666 said:
i have absolutely no clue what i am doing here, i tried to reboot my tablet into TWPR menu
but i could not figure it out it has TWRP, and RR rom and root
i held the power button down and did reboot recovery and i did not get TWRP menu
so rebooted it and then i chose bootloader, and now all i get is a black screen that says fastboot..
holding power and it won't reboot it wont turn off or do anything
how do i fix this ****?
how do i get to the twrp menu screen?
how do i create a backup of my system to the SD card?
i want to try an experimental APK but i want to make sure i can recover if it messes up my tablet
but 1st how do i fix this?
Click to expand...
Click to collapse
Clean up the language.
- no TWRP (custom recoveries) on this device
- to exit from fastboot untether and long press power until it turns off
- start with the forum index and read what you can/can't do with this device and how to accomplish it
Davey126 said:
Clean up the language.
- no TWRP (custom recoveries) on this device
- to exit from fastboot untether and long press power until it turns off
- start with the forum index and read what you can/can't do with this device and how to accomplish it
Click to expand...
Click to collapse
yes got it to reboot by holding volume and power finally ,it did not work the 1st few tries for some reason
i know i was in the TWRP screen before when i flashed the rom and xposed but now i forget how to get back to it now
so what happens if i mess up my system with an experimental APK, i am trying to add miracast
if it messes up something then will i be able to recover? or would i have to make a backup with TWRP 1st?
gdroid666 said:
yes got it to reboot by holding volume and power finally ,it did not work the 1st few tries for some reason
i know i was in the TWRP screen before when i flashed the rom and xposed but now i forget how to get back to it now
so what happens if i mess up my system with an experimental APK, i am trying to add miracast
if it messes up something then will i be able to recover? or would i have to make a backup with TWRP 1st?
Click to expand...
Click to collapse
Clean up thread title...go from there. Miracast won't work on this device.
Davey126 said:
Clean up thread title...go from there. Miracast won't work on this device.
Click to expand...
Click to collapse
sorry i can't edit it, it won't let me
also i have looked around and i found this .apk
http://cord-cutters.wonderhowto.com...rooted-android-device-running-kitkat-0156212/
(it says kitkat but there was a thread on here on it and it said kitkat or above)
https://www.androidfilehost.com/?fid=95784891001616583
and i searched and searched but i have not found any reports of it ever being tried on the 2015 5th gen fire 7
i can only seem to get to the thread in google cache ,and there are only reports of it being tried on the HD fire 7 and all posts end around 2014 so i am not sure if it will work, but what is the worst thing that could happen if i try this? with no backup and TWRP installed? could i still revert everything back?
have you ever heard of anyone trying this specific .apk on this device before?
gdroid666 said:
sorry i can't edit it, it won't let me
also i have looked around and i found this .apk
http://cord-cutters.wonderhowto.com...rooted-android-device-running-kitkat-0156212/
(it says kitkat but there was a thread on here on it and it said kitkat or above)
https://www.androidfilehost.com/?fid=95784891001616583
and i searched and searched but i have not found any reports of it ever being tried on the 2015 5th gen fire 7
i can only seem to get to the thread in google cache ,and there are only reports of it being tried on the HD fire 7 and all posts end around 2014 so i am not sure if it will work, but what is the worst thing that could happen if i try this? with no backup and TWRP installed? could i still revert everything back?
have you ever heard of anyone trying this specific .apk on this device before?
Click to expand...
Click to collapse
- have not heard of anyone trying linked apk on this device
- in general custom roms on Amazon devices do not support miracast (multiple devices/multiple roms)
- if you can access the stock recovery menu via <power>+<vol-up> recovery is possible (reload FireOS)
- unlikely a straight apk install will bork the rom; more likely it simply won't work
Davey126 said:
- have not heard of anyone trying linked apk on this device
- in general custom roms on Amazon devices do not support miracast (multiple devices/multiple roms)
- if you can access the stock recovery menu via <power>+<vol-up> recovery is possible (reload FireOS)
- unlikely a straight apk install will bork the rom; more likely it simply won't work
Click to expand...
Click to collapse
yup you are right it dod not work the app gave a message right away about not having some file for audio something t other i forget ,just uninstalled th eapk and no damage done