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.
This is a Safe Upgrade to the latest 6.0.1 firmware (N910VVRU2CPD1) for VZW Samsung Galaxy Note 4 (SM-N910V).
YOU NEED TO UPGRADE THE BOOTLOADER AND UNLOCK IT
★ Disclaimer:THIS SERVICE IS FREE OF CHARGE, USE IT AT YOUR OWN RISK, TAKE IT OR LEAVE IT !
★ Instructions:
Follow the instructions here to upgrade and unlock the bootloader
Extract the N910VVRU2CPD1_StockRestore.tar.md5 file using 7-Zip
Extract Odin v3.11.1 & open it
Reboot to Download Mode (press and hold Home + Power + Volume Down)
Connect phone and wait until you get a blue sign in Odin
Add the N910VVRU2CPD1_StockRestore.tar.md5 file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back & wait a few minutes
Reboot into recovery (press and hold Home + Power + Volume Up)
Wipe data (Factory Reset)
Reboot to system
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
N910VVRU2CPD1 Stock Restore: N910VVRU2CPD1_StockRestore.tar.md5.7z
md5: a9fa3e15729474955bee6e42a1cc86b8
Click to expand...
Click to collapse
Hi , I already unlocked my phone bootloader on the 5.1.1 firmware , do I now odin directly the N910VVRU2CPD1_StockRestore.tar.md5 and all set .
thanks
machhho said:
Hi , I already unlocked my phone bootloader on the 5.1.1 firmware , do I now odin directly the N910VVRU2CPD1_StockRestore.tar.md5 and all set .
thanks
Click to expand...
Click to collapse
No, you must upgrade to the marshmallow bootloader and unlock that one by following the directions in hsbadr's other thread. Then you flash the Stock Restore in Odin.
So i have a developer edition, can i just odin this and go? or do i have to install and unlock a bootloader as well? root/unlocking took so long i didnt keep up.
Is the safe upgrade PD1 rom is Pre-rooted.
buhohitr said:
Is the safe upgrade PD1 rom is Pre-rooted.
Click to expand...
Click to collapse
It probably isn't, since it's not a custom ROM but just a set of Stock firmware files.
Gravemoss42 said:
So i have a developer edition, can i just odin this and go? or do i have to install and unlock a bootloader as well? root/unlocking took so long i didnt keep up.
Click to expand...
Click to collapse
The only time you guys can flash directly any MM ROM is when you already on MM Unlocked bootloader and rooted. If you are on 5.1.1 Unlocked and rooted, you have to follow the OP instructions, doesn't matter if you have retails or Dev Edition.
And here we go.
Anyone have any recommendations on how to backup my Android install before I flash this?
FMXP said:
And here we go.
Anyone have any recommendations on how to backup my Android install before I flash this?
Click to expand...
Click to collapse
Are you rooted? You should be able to backup in recovery if you are.
This won't replace Recovery, right?
---------- Post added at 02:54 AM ---------- Previous post was at 02:19 AM ----------
The first link goes to the BPA1 download. I didn't notice, and ended up waiting about 30 minutes for it to download before I saw it .
This method is exclusively for Developer Editions, right? Retail users have to follow the steps listed in this thread? Otherwise both methods get users to CPD1?
Never mind, I see it says Retail/Dev in the thread title...
Missing Applications Manager?
So I went through this process twice, the first time because wifi wasn't working and the application manager (Settings -> Application) was missing.
On the second shot, wifi was working again, but I'm still missing the app manager.
Where I expect Applications, I see Application Settings (the part where you can set the default program, etc.)
Did this happened to anyone else?
Anyone have a fix for this?
I have a developer edition Note 4 and am currently on 4.4.4 ANJ5. If I upgrade to CPD1, can I safely downgrade to any prior release (4.4, 5.0, 5.1, etc.)?
Would I follow the same process as going from 4.4 to 5.1 and vice versa?
I've found that I like 4.4 better than any of the 5.0 ROM's, but I want to try 6.0 now that it is out.
Thank in advance for your help!
I'm curious as anyone been able to root this.
Sent from my SM-N910V using Tapatalk
dkahs23 said:
I'm curious as anyone been able to root this.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
If you unlock it and install twrp, you can try flashing SuperSu then. But if you root the stock rom it might not boot, that was the case with LL. Had to flash custom kernel.
Sent from my Unlocked/Rooted SM-N910V using XDA-Developers mobile app
tolymatev said:
If you unlock it and install twrp, you can try flashing SuperSu then. But if you root the stock rom it might not boot, that was the case with LL. Had to flash custom kernel.
Sent from my Unlocked/Rooted SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm on stock LL now unlocked BL and rooted retail edition. I didn't know if king root would work
Sent from my SM-N910V using Tapatalk
dkahs23 said:
I'm on stock LL now unlocked BL and rooted retail edition. I didn't know if king root would work
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Kingoroot will work but you have to follow this guide http://forum.xda-developers.com/showthread.php?t=3398144
Sent from my Unlocked/Rooted SM-N910V using XDA-Developers mobile app
Well I am on MM via this way and have Retail version w/developer mode with boot loader unlock and twrp installed but cannot get root via kingroot. So I flashed SuperSu. And still no root
dkahs23 said:
Well I am on MM via this way and have Retail version w/developer mode with boot loader unlock and twrp installed but cannot get root via kingroot. So I flashed SuperSu. And still no root
Click to expand...
Click to collapse
If you use the Jasmine ROM v6.0.1 by hsbadr - which is almost like stock MM - you can get root. Jasmine ROM has the custom Multisystem kernel for MM to root.
---------- Post added at 02:01 AM ---------- Previous post was at 01:53 AM ----------
gowronshammer said:
So I went through this process twice, the first time because wifi wasn't working and the application manager (Settings -> Application) was missing.
On the second shot, wifi was working again, but I'm still missing the app manager.
Where I expect Applications, I see Application Settings (the part where you can set the default program, etc.)
Did this happened to anyone else?
Anyone have a fix for this?
Click to expand...
Click to collapse
Did you get Wifi back?
chappatti said:
If you use the Jasmine ROM v6.0.1 by hsbadr - which is almost like stock MM - you can get root. Jasmine ROM has the custom Multisystem kernel for MM to root.
---------- Post added at 02:01 AM ---------- Previous post was at 01:53 AM ----------
Did you get Wifi back?
Click to expand...
Click to collapse
I did, but not with the Applications manager. After going ODIN back to 5.1.1, unlocking and upgrading the bootloader and then applying the MM Safe upgrade, twice, I got wifi, but not Applications manager.
I ended up using the full firmware found here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937 and just flashing straight to 6.0.1.
I don't have root, a locked boot loader, complaints about dm-verity and DRK in recovery mode, but I have a working MM with Wifi and Applications manager and Android Pay.
I'm happy at the moment, thanks for the help.
This thread is strictly for info regarding Root/Twrp/Roms
If you have any ideas or have tried anything please post here
I AM IN NO WAY A DEV ,i am using google and common sense
Here is the link to the sprint boot.img (https://drive.google.com/file/d/0B9Vkl8ldvnNdOGlyLW4wOXNDRUk/view?usp=drivesd)-Thanks to @XirXes
Heres what i have tried
-So far i have tried signing the sprint boot.img to magisk with no luck,it gives me files are read only errors.I was able to get past the the first two steps of this post for systemless root via adb (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
-Flashing the stock sprint boot.img to confirm compatibility hint hint its compatible
ROOT HAS BEEN ACHEIVED!!
UPDATE- As of 9/13/17 we now have root in the form of a patched boot.img thanks to @themustached for patching the boot.img so gracefully for us
To install the boot img you need to reboot to fastboot and run the command "fastboot flash boot (name of boot.img).img
https://drive.google.com/file/d/0B8kodjBRTHoZR2Zob1VLX0xOVkU/view?usp=sharing
Just a update as I have been away from this phone for a bit
We have kernel source now (like 2 months ago) and there are 3 AOSP ROMs that I know about being worked on so far I don't know any details or anything but what I do know is that they completed the build process they are working on getting it running on our phone
joemossjr made the the ncp Rom and got TWRP for us so big thanks to him!
Substratum works on legacy with root and newest version of TWRP just in case anyone was wondering.
https://pastebin.com/uk8uCTX2 created one!
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
https://drive.google.com/file/d/0B1tqDJm_qQf4Y2VibG5fZ3NzZmc/view?usp=sharing
joemossjr said:
https://pastebin.com/uk8uCTX2 created one!
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
https://drive.google.com/file/d/0B1tqDJm_qQf4Y2VibG5fZ3NzZmc/view?usp=sharing
Click to expand...
Click to collapse
Booted but no root
Also when toying around do not do Fastboot flash, do fastboot boot. We dont have a clean T Mobile kernel and could really wind up in a bad place due to a bad flash.
altimax98 said:
Booted but no root
Also when toying around do not do Fastboot flash, do fastboot boot. We dont have a clean T Mobile kernel and could really wind up in a bad place due to a bad flash.
Click to expand...
Click to collapse
i tried flashing to the a and b partition no luck used the magisk 13.6 thinking we need to get hold of the pixel magisk
I have insurance and I'm willing to risk my device worst case,it's not a problem,I've noticed if you boot it,it doesn't like to set correctly
joemossjr said:
i tried flashing to the a and b partition no luck used the magisk 13.6 thinking we need to get hold of the pixel magisk
Click to expand...
Click to collapse
I totally forgot about the dual partitions with this.
We really need the stock recovery to get TWRP built. Even the Sprint/AT&T versions should be fine
Sent from my Moto Z (2) using Tapatalk
Downloaded them all found no recovery
Verified ATT & Sprint boot.img works om Tmobile
Ok I have verified these 2 posted images boot ok on the TMobile Z2 Force. What do I need to do to use fastboot to extract system images? I cant use adb to get any system partition yet. I dont have the info, I tried to use adb and it would not let me read /dev/ permission denied. If you tell me what to do from fastboot or adb I can dump it, bootloader is already unlocked. Thanks!
bart bart said:
Ok I have verified these 2 posted images boot ok on the TMobile Z2 Force. What do I need to do to use fastboot to extract system images? I cant use adb to get any system partition yet. I dont have the info, I tried to use adb and it would not let me read /dev/ permission denied. If you tell me what to do from fastboot or adb I can dump it, bootloader is already unlocked. Thanks!
Click to expand...
Click to collapse
We are all in this situation. It is likely going to be quite some time before we get root due to the dual partition system.
Based on the Pixel info, we need TWRP first
Sent from my Moto Z (2) using Tapatalk
The recovery is in the boot.img of 7.1 and up devices
Dumper US Cellular Boot.img
altimax98 said:
I totally forgot about the dual partitions with this.
We really need the stock recovery to get TWRP built. Even the Sprint/AT&T versions should be fine
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Here is dumped boot.img of US Cellular Boot.img. There is a recovery under sbin folder. Hopefully you can make a bootable TWRP from it?
https://www.dropbox.com/s/hjfr8wj2da...ootus.zip?dl=0
If anyone wants to join our efforts the let us know and we can add you in
I want to join your efforts.
Figured I'd give a status update on people looking for root. So as it looks roots gonna have to be put on the back end for right now as magisk isn't updated to 13.6 for the Google pixel it's on 13.4 which means we can't use the 13.6 manual boot image patching funtionallity. The reason we are using the pixel is because as of right now it's the only other device to use the a and b partitioning that has magisk. So what this all means is we need to try to get twrp going so we can at least get backups going and pre rooted roms. I personally have pmed everyone I could with little to no response. I'll update when I get any responses.
joemossjr said:
Figured I'd give a status update on people looking for root. So as it looks roots gonna have to be put on the back end for right now as magisk isn't updated to 13.6 for the Google pixel it's on 13.4 which means we can't use the 13.6 manual boot image patching funtionallity. The reason we are using the pixel is because as of right now it's the only other device to use the a and b partitioning that has magisk. So what this all means is we need to try to get twrp going so we can at least get backups going and pre rooted roms. I personally have pmed everyone I could with little to no response. I'll update when I get any responses.
Click to expand...
Click to collapse
Thank you
Sent from my SM-N930F using XDA-Developers Legacy app
Deleted
Any progress? Anything I can do to help? I have T Mobile variant with unlocked bootloader.
We brought in another guy from the pixel forum who made their twrp recovery he's going to take a look and see what can be done
Question before I delve further.
fastboot -i 0x2b4c flash:raw boot <kernel> [ <ramdisk> ] rather than just flash <partition> [ <filename> ] perhaps for the twrp? Just a spit ball idea as I wrap my head around. Been a few years since I bothered with phones rather than.. other systems. I'm sure this round probably already been tried but curious of the turn before I fry the new toy xD.
joemossjr said:
If anyone wants to join our efforts the let us know and we can add you in
Click to expand...
Click to collapse
I can test stuff when the time comes.
Hello all,
I was wondering if there has been any development / root process for the E5 Play XT1921-1?
Thanks
smeogle said:
Hello all,
I was wondering if there has been any development / root process for the E5 Play XT1921-1?
Thanks
Click to expand...
Click to collapse
If you have unlocked your bootloader, you should be able to use @CodyF86's TWRP and root method from this thread. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page23
The xt1921-1 appears to be the unbranded variant of xt1921-5.
MotoJunkie01 said:
If you have unlocked your bootloader, you should be able to use @CodyF86's TWRP and root method from this thread. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page23
The xt1921-1 appears to be the unbranded variant of xt1921-5.
Click to expand...
Click to collapse
I will give it a go, thank you for your info!
smeogle said:
I will give it a go, thank you for your info!
Click to expand...
Click to collapse
To play it completely safe, instead of actually flashing TWRP as an initial step, use the boot-only method:
fastboot boot twrp.img
This way, you can ascertain whether the TWRP build functions on your device normally before flashing the /recovery partition.
MotoJunkie01 said:
To play it completely safe, instead of actually flashing TWRP as an initial step, use the boot-only method:
fastboot boot twrp.img
This way, you can ascertain whether the TWRP build functions on your device normally before flashing the /recovery partition.
Click to expand...
Click to collapse
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!
smeogle said:
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!
Click to expand...
Click to collapse
Very glad you tried and confirmed this. I'll add the info to my stock ROM thread regarding the intercompatability between these two devices.
MotoJunkie01 said:
Very glad you tried and confirmed this. I'll add the info to my stock ROM thread regarding the intercompatability between these two devices.
Click to expand...
Click to collapse
Upon further use, there is some stability issues. When I navigate to Settings -> System -> About Phone -> Hardware Information, the popup 'Motorola Settings has stopped' appears. Additionally, camera doesn't launch.
smeogle said:
Upon further use, there is some stability issues. When I navigate to Settings -> System -> About Phone -> Hardware Information, the popup 'Motorola Settings has stopped' appears. Additionally, camera doesn't launch.
Click to expand...
Click to collapse
Interesting. That would appear to indicate some minor differences between the two devices in terms of firmware configurations. Try this, using the factory firmware package for your device, flash the /boot and /oem partitions only (since the camera drivers are located in /boot). Then boot into TWRP recovery and flash Magisk (or a no-verity script) in order to disable dm-verity and for root patching. Wipe the cache and Dalvik and reboot system.
If that doesn't do the trick, do a clean firmware install and do a TWRP dump of your system image and /boot partition. Upload them to a host like Google Drive, send me a link, and I'll build you a TWRP flashable stock ROM specifically for xt1921-1.
MotoJunkie01 said:
Interesting. That would appear to indicate some minor differences between the two devices in terms of firmware configurations. Try this, using the factory firmware package for your device, flash the /boot and /oem partitions only (since the camera drivers are located in /boot). Then boot into TWRP recovery and flash Magisk (or a no-verity script) in order to disable dm-verity and for root patching. Wipe the cache and Dalvik and reboot system.
If that doesn't do the trick, do a clean firmware install and do a TWRP dump of your system image and /boot partition. Upload them to a host like Google Drive, send me a link, and I'll build you a TWRP flashable stock ROM specifically for xt1921-1.
Click to expand...
Click to collapse
After following the flash boot and oem steps, it got caught in a bootloop. Once that occurred, I wiped and reflashed your stock rom (followed by Magisk). Once it booted again, the previously mentioned instability (camera and hardware settings) have disappeared. Good job!
smeogle said:
After following the flash boot and oem steps, it got caught in a bootloop. Once that occurred, I wiped and reflashed your stock rom (followed by Magisk). Once it booted again, the previously mentioned instability (camera and hardware settings) have disappeared. Good job!
Click to expand...
Click to collapse
Give me a TWRP backup of your system image and boot partition and I'll make a TWRP flashable stock ROM for the XT1921-1.
Thanks for testing. I'll add the intercompatability info to my stock ROM and firmware threads.
Unlocking Bootloader on XT1921-1
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?
---------- Post added at 09:57 PM ---------- Previous post was at 09:46 PM ----------
smeogle said:
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!
Click to expand...
Click to collapse
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?
dcluvsme said:
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?
---------- Post added at 09:57 PM ---------- Previous post was at 09:46 PM ----------
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?
Click to expand...
Click to collapse
I followed the guide the on the following Motorola website:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Thanks
smeogle said:
I followed the guide the on the following Motorola website:
Click to expand...
Click to collapse
Using Linux, I was refused, did the exact same thing in Windows,and it worked.
Who knows.
Thanks for the tip.
dcluvsme said:
Using Linux, I was refused, did the exact same thing in Windows,and it worked.
Who knows.
Thanks for the tip.
Click to expand...
Click to collapse
When you tried in Linux, what do you mean it did not work? I performed mine with Linux Mint. Did you get any specific error? How did you install adb and fastboot?
smeogle said:
When you tried in Linux, what do you mean it did not work? I performed mine with Linux Mint. Did you get any specific error? How did you install adb and fastboot?
Click to expand...
Click to collapse
I used Puppy Xenial,but I also have Linux Mint. I am sure it was an error on my part. No worries.
smeogle said:
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!
Click to expand...
Click to collapse
can u please help me i think im stuck in the same boat you were in
MotoJunkie01 said:
If you have unlocked your bootloader, you should be able to use @CodyF86's TWRP and root method from this thread. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page23
The xt1921-1 appears to be the unbranded variant of xt1921-5.
Click to expand...
Click to collapse
is there a way to do it without twerp? my phone is in a boot loop i installed the wrong rom i think i cant find the correct one for this phone.
Hello all,
I currently just got a new Kindle Fire 7" 9th Gen. It's running Fire OS 6.3.1.4 Any way that it can be rooted easily and add Lineage OS to it? Or can someone help me out on going to the right thread?
Thanks in advance.
Reiixas said:
Hello all,
I currently just got a new Kindle Fire 7" 9th Gen. It's running Fire OS 6.3.1.4 Any way that it can be rooted easily and add Lineage OS to it? Or can someone help me out on going to the right thread?
Thanks in advance.
Click to expand...
Click to collapse
Start here -
Fire 7 (2019, mustang) unbrick, downgrade, unlock & root
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
once you are unlocked you will have freedom, post questions in the threat, or post back here and i will help. 14.1 LOS for mustang is solid after you are unlocked...
[ROM][unlocked][mustang] Lineage-14.1 [27 AUG 2019]
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329
Michajin said:
Start here -
Fire 7 (2019, mustang) unbrick, downgrade, unlock & root
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
once you are unlocked you will have freedom, post questions in the threat, or post back here and i will help. 14.1 LOS for mustang is solid after you are unlocked...
[ROM][unlocked][mustang] Lineage-14.1 [27 AUG 2019]
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329
Click to expand...
Click to collapse
I appreciate the help, however my device out of the box has 6.3.1.4 OS and that method only works until 6.3.1.2. Anyway on how to downgrade it to where it needs to be?
Reiixas said:
I appreciate the help, however my device out of the box has 6.3.1.4 OS and that method only works until 6.3.1.2. Anyway on how to downgrade it to where it needs to be?
Click to expand...
Click to collapse
The hardware unlock version should still work ( i am not sure how amazon could block it) The software version just gave you access to the bootrom without opening the tablet. Once you get into the bootrom you are golden to run the bootrom-step script which will give you a hacked fastboot, to allow you to flash TWRP recovery (fastboot-step script). Once in recovery you can flash LOS instead of fw.zip.
Michajin said:
The hardware unlock version should still work ( i am not sure how amazon could block it) The software version just gave you access to the bootrom without opening the tablet. Once you get into the bootrom you are golden to run the bootrom-step script which will give you a hacked fastboot, to allow you to flash TWRP recovery (fastboot-step script). Once in recovery you can flash LOS instead of fw.zip.
Click to expand...
Click to collapse
I understand that. I'm trying to do the software version instead of opening it. In the software version I get stuck on step 4. and I get this prompt:
mustang:/ $ cd /data/local/tmp
mtk-sumustang:/data/local/tmp $ ./mtk-su
Failed critical init step 4
This platform cannot be supported
So, I assume that the only way to do so is with the hardware version?
Reiixas said:
I understand that. I'm trying to do the software version instead of opening it. In the software version I get stuck on step 4. and I get this prompt:
mustang:/ $ cd /data/local/tmp
mtk-sumustang:/data/local/tmp $ ./mtk-su
Failed critical init step 4
This platform cannot be supported
So, I assume that the only way to do so is with the hardware version?
Click to expand...
Click to collapse
From Rapid Temporary Root for HD 8 & HD 10
https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595
Fire 7 9th gen (2019) (thanks @Michajin) -- up to Fire OS 6.3.1.2 build 0002517050244 only
Yes , the hardware way is the only way. Opening the tablet is easier than is sounds and shorting it fairly easy too, a wire or a piece of aluminum foil rolled up works well.
Michajin said:
From Rapid Temporary Root for HD 8 & HD 10
https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595
Fire 7 9th gen (2019) (thanks @Michajin) -- up to Fire OS 6.3.1.2 build 0002517050244 only
Yes , the hardware way is the only way. Opening the tablet is easier than is sounds and shorting it fairly easy too, a wire or a piece of aluminum foil rolled up works well.
Click to expand...
Click to collapse
Hello,
Thank you for your help. I managed to install TWRP and Lineage OS 14 with Gapps. However, I removed the micro sd card to change Gapps nano to pico and my device won't boot now and won't be recognized by adb. Did I make this kindle a paperweight?
Reiixas said:
Hello,
Thank you for your help. I managed to install TWRP and Lineage OS 14 with Gapps. However, I removed the micro sd card to change Gapps nano to pico and my device won't boot now and won't be recognized by adb. Did I make this kindle a paperweight?
Click to expand...
Click to collapse
No, from a power off state you should be able to boot into recovery. I think it's volume up (possibly down) and power button. From there your can go back and flash it again or restore a backup... Are you boot looping? You can fix it. Might need to run the scripts again. But likely you can get into recovery to fix it.
---------- Post added at 10:13 PM ---------- Previous post was at 09:58 PM ----------
Are you looping in Amazon or los? Or just black screen?
Michajin said:
No, from a power off state you should be able to boot into recovery. I think it's volume up (possibly down) and power button. From there your can go back and flash it again or restore a backup... Are you boot looping? You can fix it. Might need to run the scripts again. But likely you can get into recovery to fix it.
---------- Post added at 10:13 PM ---------- Previous post was at 09:58 PM ----------
Are you looping in Amazon or los? Or just black screen?
Click to expand...
Click to collapse
Hello,
I managed to fix it. But I REALLY appreciate your help. You helped A LOT.
THANK YOU :victory:
How did you manage to downgrade and install it in the end? I am also stuck on 6.3.1.5 Nand getting
mtk-sumustang:/data/local/tmp $ ./mtk-su
Failed critical init step 4
This platform cannot be supported
How to downgrade to 6.3.1.2 or how to get past it on existing version? thanks
brankota said:
How did you manage to downgrade and install it in the end? I am also stuck on 6.3.1.5 Nand getting
mtk-sumustang:/data/local/tmp $ ./mtk-su
Failed critical init step 4
This platform cannot be supported
How to downgrade to 6.3.1.2 or how to get past it on existing version? thanks
Click to expand...
Click to collapse
You need to do the hardware hack by opening the tablet.
Start here -
Fire 7 (2019, mustang) unbrick, downgrade, unlock & root
https://forum.xda-developers.com/ama...grade-t3944365
Michajin said:
No, from a power off state you should be able to boot into recovery. I think it's volume up (possibly down) and power button. From there your can go back and flash it again or restore a backup... Are you boot looping? You can fix it. Might need to run the scripts again. But likely you can get into recovery to fix it.
---------- Post added at 10:13 PM ---------- Previous post was at 09:58 PM ----------
Are you looping in Amazon or los? Or just black screen?
Click to expand...
Click to collapse
OP says local video playback in LOS is still not supported. Is this still true?
thisisnotatest said:
OP says local video playback in LOS is still not supported. Is this still true?
Click to expand...
Click to collapse
Seems like it was all working. I haven't had it on in months. Make a back up flash it and test it. If you don't like it or it has many issues, restore the backup.
Reiixas said:
Hello all,
I currently just got a new Kindle Fire 7" 9th Gen. It's running Fire OS 6.3.1.4 Any way that it can be rooted easily and add Lineage OS to it? Or can someone help me out on going to the right thread?
Thanks in advance.
Click to expand...
Click to collapse
For everyone that has the fire tablet 7 gen 9 , aka mustang , if your tablet was made
in 2020 or later you won't be able to unlock , or flash it .
After 2019 and the first production run , they hardware locked this model tablet.
Starting in 2020 the fire tablet 7 gen 9 aka mustang was shipped with the
chip hardware locked and even opening it up to perform the bypass won't work.
They basically did a bait and switch at Amazon ,
Mid production run for this model they secretly changed the major
possibilities and functions that could be done on it .
Essentially you were buying an inferior unit with the same model number .
Personally I think Amazon should give millions of people their money back for
unethical and wrong business practices being used on its customers.
I talked to Amazon corporate offices and they said that their policy is that at any time
They can modify a current model unit and change its hardware features , all without
informing the customer that their current model being sold was now
with a hardware lock . just like in 2019 , people bought this model tablet , but by 2020
The same model tablet was redesigned secretly to now be fully hardware locked.
People who were unaware like me bought this model in 2020 , and yes it
unfortunately was made hardware locked , but people who bought the first
production run of them in 2019 were lucky enough to buy ones that were not made with any
Hardware lock .
There's different methods to see if your mustang model tablet is locked ,
Either way it all means one thing . your tablet will never be unlocked or flashed ,
At least not without specific engineering , and ROM flashers anyway.
Even then , good luck .
It don't look good .