Related
My wife's 7" Kindle Fire HD keeps rebooting into the TWRP recovery. I had rooted it and installed a custom ROM several months ago, but could never get it stable and working correctly. So I gave up and restored the original images backup and all was well for several months. She used it quite regularly without issues.
Then a couple of weeks ago, she would charge it up 100%, use it to read then go to bed. By the next evening it would be as dead as a door nail. So thinking it was a bad battery I did some investigating and found that when she puts it into standby mode it will eventually reboot and go into TWRP. Of course it never enters sleep mode while on the recovery screen and the battery will eventually run down.
A couple of notes - If I reboot it to the system from TWRP but never unlock the screen it never reboots to recovery. Only when I unlock the screen and enter the Home screen, or open ANY program will it eventually reboot to TWRP.
I am suspecting that some program updated itself and that is causing the problem, but since she has numerous programs and I had auto update installed it is impossible to know which one is the culprit.
It is running software version 7.4.8_user_4849020, TWRP 2.6.3.1
Has anybody seen this issue? Any suggestions?
Amazon'n software doesn't want to play nice with the 2nd bootloader and recovery. I suggest you to flash a custom rom like CM. The unofficial builds and monthly snapshots are pretty stable.
Oh,and you need to upgrade TWRP to 2.7.0.0 to install CM 11.
SafinWasi said:
Amazon'n software doesn't want to play nice with the 2nd bootloader and recovery. I suggest you to flash a custom rom like CM. The unofficial builds and monthly snapshots are pretty stable.
Oh,and you need to upgrade TWRP to 2.7.0.0 to install CM 11.
Click to expand...
Click to collapse
Not going to happen. I went down that obstacle course several months ago and had nothing but problems with CM. Never could get the tablet stable and working in spite of following all of the suggestions and tweaks.. That is why I went back to stock. It worked without issues for several months so as far as I'm concerned it is a problem that can be fixed. It is just going to take me a while to solve it. In the meantime, it seems that as long as she is in the Kindle Reader software and actively using it the reboot doesn't happen. If it gets to where it is not usable I'll just bite the bullet and buy her a new tablet.
pastorbob62 said:
Not going to happen. I went down that obstacle course several months ago and had nothing but problems with CM. Never could get the tablet stable and working in spite of following all of the suggestions and tweaks.. That is why I went back to stock. It worked without issues for several months so as far as I'm concerned it is a problem that can be fixed. It is just going to take me a while to solve it. In the meantime, it seems that as long as she is in the Kindle Reader software and actively using it the reboot doesn't happen. If it gets to where it is not usable I'll just bite the bullet and buy her a new tablet.
Click to expand...
Click to collapse
So far no one has found a way around Amazon's bootloader checks, so there's no way to solve it. And CM has become much much more stable now (we're considered official now ). So CM may be worth another go
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Ph0enix_216 said:
So far no one has found a way around Amazon's bootloader checks, so there's no way to solve it. And CM has become much much more stable now (we're considered official now ). So CM may be worth another go
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Click to expand...
Click to collapse
Hmmmm. Well, I may give this a shot after I replace her Kindle for her. I have about $100.00 in my Amazon account that I can apply to the price of a new tablet (not another Kindle, she wants a REAL Android device ). Then I can experiment as much as I desire and if things go badly, she will still have a tablet.
Thank you for the feedback!
pastorbob62 said:
Hmmmm. Well, I may give this a shot after I replace her Kindle for her. I have about $100.00 in my Amazon account that I can apply to the price of a new tablet (not another Kindle, she wants a REAL Android device ). Then I can experiment as much as I desire and if things go badly, she will still have a tablet.
Thank you for the feedback!
Click to expand...
Click to collapse
Cm11 has changed ALOT in the past 9 months. It's very stable, and has the latest android version 4.4.4. Also think about upgrading your Twrp version to 2.7.0.
Bao289 said:
Cm11 has changed ALOT in the past 9 months. It's very stable, and has the latest android version 4.4.4. Also think about upgrading your Twrp version to 2.7.0.
Click to expand...
Click to collapse
Upgrading to TWRP 2.7.0 is understood. I had to do that in order to run a Kit-Kat based ROM on my Asus TF300. (Which, by the way, is MUCH easier to customize than this Kindle.)
The main problem I previously had with CM was getting the Kindle app to work without crashing and causing a reboot. or locking the tablet up. Has that issue been resolved?
pastorbob62 said:
Upgrading to TWRP 2.7.0 is understood. I had to do that in order to run a Kit-Kat based ROM on my Asus TF300. (Which, by the way, is MUCH easier to customize than this Kindle.)
The main problem I previously had with CM was getting the Kindle app to work without crashing and causing a reboot. or locking the tablet up. Has that issue been resolved?
Click to expand...
Click to collapse
Yes that issue has been resolved. Hascode changed the build prop file to make amazon apps work. I can acess books, apps but NOT prime videos.
NO one can access Prime videos outside of a Kindle OS. It seems like the one thing devs can't crack yet.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Bao289 said:
Yes that issue has been resolved. Hascode changed the build prop file to make amazon apps work. I can acess books, apps but NOT prime videos.
Click to expand...
Click to collapse
Okay, I bought my wife a new tablet (Asus 10.1") and I am finally at the point where I am ready to give this a try.
Just to recap, I am running software version 7.4.8_user_4849020, TWRP 2.6.3.1.
Can I just flash TWRP 2.7.0.0 from TWRP 2.6.3 and then flash CM 11 from TWRP 2.7.0.0? I was able to do that with my Asus tablet without any issues. Or do I have to go back through using fastboot.
pastorbob62 said:
Okay, I bought my wife a new tablet (Asus 10.1") and I am finally at the point where I am ready to give this a try.
Just to recap, I am running software version 7.4.8_user_4849020, TWRP 2.6.3.1.
Can I just flash TWRP 2.7.0.0 from TWRP 2.6.3 and then flash CM 11 from TWRP 2.7.0.0? I was able to do that with my Asus tablet without any issues. Or do I have to go back through using fastboot.
Click to expand...
Click to collapse
flash twrp 2.7.0.0 using fire flash app DO NOT FLASH TWRP IN OLD TWRP. So that you have the latest twrp version. Make sure you do a full back up then clear davalik, cache (factory reset) in twrp. THEN flash cm 11 with gapps.
Bao289 said:
flash twrp 2.7.0.0 using fire flash app DO NOT FLASH TWRP IN OLD TWRP. So that you have the latest twrp version. Make sure you do a full back up then clear davalik, cache (factory reset) in twrp. THEN flash cm 11 with gapps.
Click to expand...
Click to collapse
Can't seem to locate a version of Fire Flash to download. Where might I find it?
pastorbob62 said:
Can't seem to locate a version of Fire Flash to download. Where might I find it?
Click to expand...
Click to collapse
LINK TO TRWP 2.7.0.0= https://goo.im/devs/Hashcode/tate/kfhd7-twrp-2.7.0.0-recovery.img/
FireFlash = http://forum.xda-developers.com/showthread.php?t=2168512
Under RECOVERY PARTITION put the TWRP image file. LEAVE OTHER BOXES ALONE.
Then Reboot into recovey.
You will have the latest twrp recovery. Backup in twrp then flash cm11 with gapps.
Bao289 said:
LINK TO TRWP 2.7.0.0= https://goo.im/devs/Hashcode/tate/kfhd7-twrp-2.7.0.0-recovery.img/
FireFlash = http://forum.xda-developers.com/showthread.php?t=2168512
Under RECOVERY PARTITION put the TWRP image file. LEAVE OTHER BOXES ALONE.
Then Reboot into recovey.
You will have the latest twrp recovery. Backup in twrp then flash cm11 with gapps.
Click to expand...
Click to collapse
Thank you. I had TWRP 2.7.0.0 but could not find fire flash.
pastorbob62 said:
Thank you. I had TWRP 2.7.0.0 but could not find fire flash.
Click to expand...
Click to collapse
At the bottom of the fireflash app youshould be able to boot into recovery. do not boot into eecovey by shutting it down and holding the volume butoons. Use the app to reboot as the reboot makes the change.
Just to let you know if you haven't done so.
Fabulous!! I now have a nice 7" tablet with decent resolution, performance and all of the accessibility to Android apps that my 10.1" tablet has.
Thank you to all for your help.
Bao289 said:
At the bottom of the fireflash app youshould be able to boot into recovery. do not boot into eecovey by shutting it down and holding the volume butoons. Use the app to reboot as the reboot makes the change.
Just to let you know if you haven't done so.
Click to expand...
Click to collapse
Yes, I had it figured out and am now running CM 11 with TWRP 2.7.0.0. I am running it in ART and OC'ed at 1.5 Ghz. So far no reboots or crashes.
Thank you for your help.
pastorbob62 said:
Yes, I had it figured out and am now running CM 11 with TWRP 2.7.0.0. I am running it in ART and OC'ed at 1.5 Ghz. So far no reboots or crashes.
Thank you for your help.
Click to expand...
Click to collapse
No Problem make sure you are updated to the latest cm11.
pastorbob62 said:
Yes, I had it figured out and am now running CM 11 with TWRP 2.7.0.0. I am running it in ART and OC'ed at 1.5 Ghz. So far no reboots or crashes.
Thank you for your help.
Click to expand...
Click to collapse
Wait. You're using ART? I normally use Dalvik but it's mostly up to personal preference.
Sent from my device running CyanogenMod 11
SafinWasi said:
Wait. You're using ART? I normally use Dalvik but it's mostly up to personal preference.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Yup! Been using ART on my TF300T for about six months so I enabled it on this tablet too.
ART runs circles around Dalvik as far as performance is concerned. I've heard that there are some apps that won't run with ART and Xposed Framework is not compatible with it, but I don't use Xposed and I have never run into an app that has caused me any problems.
Has anyone managed to get it working? I just tried to install via FlashFire and wound up getting an animation loop on the SlimLP boot logo. I applied the 5.1.1 firmware through the "apply update through adb" option in the recovery, can anyone confirm Xposed even working on SlimLP?
I'd like to know this also. Have not tried it yet.
I think you have to use the slim-rom version from the 4th post. The original slim rom is not running with xposed beacause of some ART optimizations... Read the slim rom thread. There you can find something about it.
Thanks! Think I found an easier solution than installing Xposed for what zip needed though (just needed YouTube to play in the background). That will come in handy if I want it later for any reason though.
Yes, xposed works fine. Big thanks to csolanol!
You must use the xposed compatible SlimLP 0.13 build + the correct xposed version (see the howto xposed thread in Fire General forum).
Anybody had success with getting .013 build running successfully with eXposed.. I've tried the ' Slim-ford-5.1.1.beta.0.13-UNOFFICIAL-20151221-0949.zip ' build from root junkies tutorial i think in section 4 or something if i remember vaguely, but with no luck... The Flash just proceeds as expected then reboots while opening/loading .zip.. But the standard release 'non-eXposed' runs without any problems.
Need to include more information. You're flashing with twrp or flashfire? If you used flashfire, what are you coming from? Stock 5.1.1 or another rom.
Do you mean after flashing the rom your Fire will not boot / start up?
I flashed SlimLP 0.13 via twrp without a problem on two different Fires. Xposed runs fine.
thanks for your reply, I'm flashing with flashFire from a r00ted fresh clean stock fire-os 5.1.1 on Amazon Fire 7" 5th Gen. i execute flash after selecting wipe all partitions except sd and then load .zip via ota then push button to commence flash, it proceeds to blank screen and then flashing screen and begins to attempt rom install i see rom info and 'char pic' of rom then it self terminates and reboots to existing r00ted fire-os, i do this exact same process with the rom not currently supporting Xposed from rootjunkie download site, and everything completes successfully spending a slightly longer period at the rom install/upload stage completing successfully with slimlp running nice... minus a few almost irrelevant bugs i noticed...
Twrp via adb doesn't work with 5.1.1 right? only works on 5.0.1&2? .. unless im mistaken.. any ideas?
Yep, we can't use twrp on 5.1.1.
So you select to wipe, system data, 3rd party apps, dalvik cache, cache partition, correct? I'm afraid I have no suggestions.
exactly that's correct , then i select rom, then i select gapps. then press flash button and it halts on the next screen as it begins to flash rom and quits to a reboot .. everything still unchanged as it was.. i have tried this process installing from stock os fire 5.1.1 & slimlp 5.1.1 with unsuccessful results.. but hey at least i have a SlimLp non-Xposed edition installed that beats Fire-BS#"*t any day. guess I'll have to wait for a new build to be released. bummer.
---------- Post added at 12:32 ---------- Previous post was at 12:25 ----------
in the future i guess more concentration is needed on the 5.1.1 Xposed edition skimlp rom to be flashed from 5.1.1 stock, for the true android custom eXperience .. i have also seen a fw roll back to 5.0.1or5.0.2 is not possible from any 5.1.1 os. never mind.
What I find is odd is that you've selected to wipe first. Flashfire should be wiping before trying & failing to flash SlimLP 0.13, leaving your Fire wiped & unable to boot back into the stock FireOS (you would then need to restore FireOS 5.1.1 via adb sideload in the amazon recovery). FlashFire is in beta & I think it's currently a bit buggy.
Bib_x said:
I think you have to use the slim-rom version from the 4th post. The original slim rom is not running with xposed beacause of some ART optimizations... Read the slim rom thread. There you can find something about it.
Click to expand...
Click to collapse
Sorry, I feel I joined the conversation mid-way but, which SlimROM thread are you talking about?
There is only one SlimLP-Thread in android development section.
Newest SLim-Version for Fire is without Art-Optimizations, so you can use xposed now with the latest slimlp 0.14.
With the older SlimLP 2.3 there was Art-Optimization inside - so there no xposed was working.
Bib_x said:
There is only one SlimLP-Thread in android development section.
Newest SLim-Version for Fire is without Art-Optimizations, so you can use xposed now with the latest slimlp 0.14.
With the older SlimLP 2.3 there was Art-Optimization inside - so there no xposed was working.
Click to expand...
Click to collapse
Thanks for the reply. I actually don't have a Fire and came across this thread after a lot of googling. I'm running SlimLP 0.12 I think on a Note Edge. I absolutely love this ROM. Seriously, I was close to selling the phone for scraps until I flashed this ROM. Now I think I will never buy another phone unless there is SlimROM support already
Anyway, I've been looking everywhere for a solution to get Xposed running. I found people saying that SELinux needs to be set to Permissive which I have done but still no luck. Are you saying that it's impossible with SlimLP versions before 0.14? Somehow, I doubt that would come to the Note Edge
marcolorenzo said:
Thanks for the reply. I actually don't have a Fire and came across this thread after a lot of googling. I'm running SlimLP 0.12 I think on a Note Edge. I absolutely love this ROM. Seriously, I was close to selling the phone for scraps until I flashed this ROM. Now I think I will never buy another phone unless there is SlimROM support already
Anyway, I've been looking everywhere for a solution to get Xposed running. I found people saying that SELinux needs to be set to Permissive which I have done but still no luck. Are you saying that it's impossible with SlimLP versions before 0.14? Somehow, I doubt that would come to the Note Edge
Click to expand...
Click to collapse
Maybe try looking in the Note Edge forum not the Amazon Fire one?
Pond-life said:
Maybe try looking in the Note Edge forum not the Amazon Fire one?
Click to expand...
Click to collapse
Maybe you shouldn't presume, with no information, that people are imbeciles? Don't you think I would've have done that at the beginning? Anyway, I may be wrong but I presumed that whether or not Xposed worked was more dependent on the ROM and not the phone? So if people here, who are discussing Xposed on SlimROM can help me, why not ask?
Bib_x is correct, i confirm Xposed working on slimlp build 0.14 beautifully for Fire 7 5th Gen.. be wary of modules you install other wise you'll have to start everything from scratch when you reach a boot hang because of a not yet compatible module.. you have no custom recovery remember so no quick fix, can always fresh install everything lol., which is good training lol.
This is a collection of fire os FW for the 5th gen and 7th gen with no bootloader flashing.
Dsclaimer
- This is for flashing with TWRP or flash fire only.
-This doesn't stop you from flashing on other devices but it won't hard brick because there are no bootloader files in the ROM file
-newer releases will Not have OTA updates removed anymore
why...
I'm going to expand to the hd 8 and hd 10, I want to keep it stock. its a lot less time consuming to not edit system files
- I'm going to go back and do this with all previous versions of fire os FW (it will take a while)
available to download
-5.3.6.8 (7th gen only)
-5.6.3(won't work on older bootloaders)
-5.4.0
removing ads
this is the best way to remove ads.
it requires root
Code:
adb shell
su
settings put global LOCKSCREEN_AD_ENABLED 0
settings put global ksoHash 0
Then uninstall special offers and do a reboot
removing ota
The two apps you need to delete is DeviceSoftwareOTA and Forced OTA. that's all
Downloads
Everything will go to android file host but the 7th gen is the only thing up there for right now
5th gen
7th gen
enjoy!
Updates list
update 4-25-19
-fixed the links for the 5th gen
update 4-21-2019
-added 5.3.6.8 for 7th gen
update 2-12-2019 for 5.4.0
-fixed flashing the boot image
-fixed flashing for newer TWRP recovery
prime video not working
ANDROID2468 said:
update 2-12-2019 for 5.4.0
-fixed flashing the boot image
-fixed flashing for newer TWRP recovery
Click to expand...
Click to collapse
Thanks for your work on this ROM.
I'm using the 5.6.3 version on my 5th Gen:
When playback in Prime video is happening, there is audio but no video. I tried playing with the dpi and had mix results. It appears to be a resolution issue? What do you think could be wrong? When I revert back to stock recovery and flash the same version everything is fine. Does this have something to do with the unlocked bootloader?
bruinsrule said:
Thanks for your work on this ROM.
I'm using the 5.6.3 version on my 5th Gen:
When playback in Prime video is happening, there is audio but no video. I tried playing with the dpi and had mix results. It appears to be a resolution issue? What do you think could be wrong? When I revert back to stock recovery and flash the same version everything is fine. Does this have something to do with the unlocked bootloader?
Click to expand...
Click to collapse
Do you have the same issue on YouTube? If you only have this issue on prime video and only on this rom then it's possible that I removed a dependency, but I don't think that there is any.... sorry, I was thinking of the wrong rom. the only thing I removed from this rom was OTA updates. sometimes you might have issues like not having wifi when you do the unlock. try to redo the unlock. make sure you have the latest version of it.
ANDROID2468 said:
Do you have the same issue on YouTube? If you only have this issue on prime video and only on this rom then it's possible that I removed a dependency, but I don't think that there is any.... sorry, I was thinking of the wrong rom. the only thing I removed from this rom was OTA updates. sometimes you might have issues like not having wifi when you do the unlock. try to redo the unlock. make sure you have the latest version of it.
Click to expand...
Click to collapse
I've tried the revamped OS, this OS, and stock. When I unlock the prime video has the same behavior in each instance. Youtube works fine and the commercials within prime video work, oddly. I'll try doing a second unlock to see if that will do the trick. I was just wondering if anyone else was experiencing this, or they just don't use prime video.
@ANDROID2468 add stock android Lollipop lockscreen wallpaper in the next build please.
Add in the updater-script a command that extracts the wallpaper in
/data/securedStorageLocation/com.android.systemui/ls_wallpaper/0
See this:
https://forum.xda-developers.com/hd8-hd10/help/root-change-lock-screen-wallpapers-t3859459
Rortiz2 said:
@ANDROID2468 add stock android Lollipop lockscreen wallpaper in the next build please.
Add in the updater-script a command that extracts the wallpaper in
/data/securedStorageLocation/com.android.systemui/ls_wallpaper/0
See this:
https://forum.xda-developers.com/hd8-hd10/help/root-change-lock-screen-wallpapers-t3859459
Click to expand...
Click to collapse
The only thing I am changing in this rom is removing the ota updates. If you want a more costume fire os version please check out my fire os revamped . I'm keeping this rom as stock as possible.
In that rom I tried to change the wallpaper by decompiling the framework.res.apk and change it from there but I had no luck with that. If you do it how you mentioned above you will lose it when you factory reset.
bruinsrule said:
I've tried the revamped OS, this OS, and stock. When I unlock the prime video has the same behavior in each instance. Youtube works fine and the commercials within prime video work, oddly. I'll try doing a second unlock to see if that will do the trick. I was just wondering if anyone else was experiencing this, or they just don't use prime video.
Click to expand...
Click to collapse
Try the one in the play store
bruinsrule said:
I've tried the revamped OS, this OS, and stock. When I unlock the prime video has the same behavior in each instance. Youtube works fine and the commercials within prime video work, oddly. I'll try doing a second unlock to see if that will do the trick. I was just wondering if anyone else was experiencing this, or they just don't use prime video.
Click to expand...
Click to collapse
I get the same problem with the Fire 7, 5th gen. tablet. The FIre 7, 7th gen. (unlocked in the same way) is fine though: Prime Video works correctly. Could it be due to the OS 5.01 TZ file?
The problem with Prime Video is caused by flashing the OS 5.01 TZ file with Amonet. With the latest TZ file used (OS 5.6.3.0), video is displayed correctly. However doing this disables Wi-Fi on the tablet. I will post about this in the most relevant thread (see here). BTW, downloading Prime Video from Google Play is not a solution. Even if you delete the prime folder (com.amazon.avod) and contents from '/system/priv-app' and reboot, then install the Google Play version, the app crashes after opening.
There is a fix for the Prime Video playback issue described in the above posts: see here for details.
I just saw that there is a new FW available for all 7th gens, not 5th gens. fire os 5.3.6.8. I will have a non bootloader zip up soon
As a new guy, I am not sure how to use the "fire os 5.6.3-no BL+ no ota_adds" after I unzipped it. My device is 7 inch 5th gen with OS 5.6.8 Any help with this, please?
hi guys,
I flashed cyanogenmod for my mom's amazon fire (ford 2015 version) many years ago, and sadly even after reformatting its just not snappy anymore and a tad buggy.
I'm thinking of upgrading to the May 2020 unofficial Lineage OS 5.1.1. Back then, I remember just using FlashFire or smth without a custom recovery to flash cyanogenmod. Is there any way to upgrade to Lineage OS now given that bootloader is still locked and I can't flash twrp?
Thanks in advance all!
aojc1992 said:
hi guys,
I flashed cyanogenmod for my mom's amazon fire (ford 2015 version) many years ago, and sadly even after reformatting its just not snappy anymore and a tad buggy.
I'm thinking of upgrading to the May 2020 unofficial Lineage OS 5.1.1. Back then, I remember just using FlashFire or smth without a custom recovery to flash cyanogenmod. Is there any way to upgrade to Lineage OS now given that bootloader is still locked and I can't flash twrp?
Thanks in advance all!
Click to expand...
Click to collapse
You can try this (follow the steps carefully)
https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
The T-Mobile website is showing the update is complete and it is going out to devices. Has anyone received the update?
OnePlus 7 Pro: Update to Android 11
OnePlus 7 Pro Software version: Android 11 Phase: Complete The software has been approved to launch and is now available. When it's ready for you, your device will provide a notification that t
www.t-mobile.com
Wondering if anyone has taken the update and been able to keep root and TWRP.
Edit: Just getting the update now. Will let you know how it goes.
Edit 2: I was not able to keep root and TRWP, the update installs after it restarts so flashing the TWRP retention script then Magisk into inactive slot just cause the update to fail. Will have to boot TWRP then install both liked normal I hope...
Please update us. I just installed the global firmware a couple weeks ago on my t-mobile unit and haven't had great battery life so I might switch back but want to keep root
_-..zKiLLA..-_ said:
Please update us. I just installed the global firmware a couple weeks ago on my t-mobile unit and haven't had great battery life so I might switch back but want to keep root
Click to expand...
Click to collapse
Battery life is great, not having the same issues I had with the beta/international firmware except I am still having issues with calls coming through the stereo speaker and not the phone ear speaker.
Also, I can't get TWRP to boot so I can't install TWRP and root with Magisk. I've tried the TWRP from the forum and the latest from the TWRP website.
DylanTheVillian said:
Battery life is great, not having the same issues I had with the beta/international firmware except I am still having issues with calls coming through the stereo speaker and not the phone ear speaker.
Also, I can't get TWRP to boot so I can't install TWRP and root with Magisk.
Click to expand...
Click to collapse
Does that mean we need the update file? I haven't come across much info on rooting our stock t-mobile roms nor have I seen them for download
_-..zKiLLA..-_ said:
Does that mean we need the update file? I haven't come across much info on rooting our stock t-mobile roms nor have I seen them for download
Click to expand...
Click to collapse
I will try some more versions of TWRP tonight hopefully. I had to stop and work. E should be able to use the normal process, just need a working TWRP.
Twrp isn't supported for oos11 on 7 series yet
I haven't seen the rom to download...but switching to inactive slot should work....for magisk...if not...search how to extract n patch boot.img with payload dumper and magisk....I did it super easy...however...while doing I decided to install magisk to inactive slot (Global) and install keep_data.apk n all went well ...so I didn't have to push the rooted boot.img externally
DylanTheVillian said:
Battery life is great, not having the same issues I had with the beta/international firmware except I am still having issues with calls coming through the stereo speaker and not the phone ear speaker.
Also, I can't get TWRP to boot so I can't install TWRP and root with Magisk. I've tried the TWRP from the forum and the latest from the TWRP website.
Click to expand...
Click to collapse
Same issue with the speaker here too.. this is on a virgin/untouched t-mobile 7pro
I'm on a stock phone with the calls only coming through speakerphone issue as well. Is there a known workaround?
to the guys having that speaker issues are you guys having black screen issues at 90hz and wake up issues at full resolution?
because I have those all those.
Danton1316 said:
I'm on a stock phone with the calls only coming through speakerphone issue as well. Is there a known workaround?
Click to expand...
Click to collapse
Saw this on the OnePlus forum. For those with the issue where the callers voice comes out the microphone instead of the earpiece, here is something to try: "Stop HearingAidService under Bluetooth running services in Developer options under system. I had the same issue. Hearing aid services are being turned on without Bluetooth being on." Someone on the forum tried it with success. I have gone back to 10 so I cannot test it.
Danton1316 said:
I'm on a stock phone with the calls only coming through speakerphone issue as well. Is there a known workaround?
Click to expand...
Click to collapse
toggling the bluetooth on and off works for me
technocrat7 said:
toggling the bluetooth on and off works for me
Click to expand...
Click to collapse
Do you have to do this for every call, or does it work after doing it just once?
tperki said:
Saw this on the OnePlus forum. For those with the issue where the callers voice comes out the microphone instead of the earpiece, here is something to try: "Stop HearingAidService under Bluetooth running services in Developer options under system. I had the same issue. Hearing aid services are being turned on without Bluetooth being on." Someone on the forum tried it with success. I have gone back to 10 so I cannot test it.
Click to expand...
Click to collapse
do you have to do this every boot or just once?...because i downgraded just like you to 10 because it was annoying and the worst is the lockscreen dpi change that made it hard to put my fingerprint or pattern...forcing me to reboot...
A few days ago I got another update. It fixed the speakerphone issue.
guitardoc64 said:
A few days ago I got another update. It fixed the speakerphone issue.
Click to expand...
Click to collapse
Can someone upload the TMobile update?? Why is it nowhere online?
teflon252 said:
Can someone upload the TMobile update?? Why is it nowhere online?
Click to expand...
Click to collapse
OnePlus7ProTMOOxygen_11.O.20_GLO
Full Android 11 T-Mobile OTA ,Haven't seen it anywere . If for some reason someone needs. Don't think you can flash with twrp, but I have unpacked and flashed in fastboot...
forum.xda-developers.com
does anyone have a oos 10 tmobile rom that i can use to downgrade?
teflon252 said:
Can someone upload the TMobile update?? Why is it nowhere online?
Click to expand...
Click to collapse
[ROM][STOCK][GM1915][FASTBOOT][11] T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional) This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY WARNING Proceed at your own risk. I am not responsible for any damage to your device. Performing the instructed...
forum.xda-developers.com
weakNPCdotCom said:
[ROM][STOCK][GM1915][FASTBOOT][11] T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional) This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY WARNING Proceed at your own risk. I am not responsible for any damage to your device. Performing the instructed...
forum.xda-developers.com
Click to expand...
Click to collapse
People do not know how to get root with the stock Tmo Rom. Took me forever to figure that out.