Related
Hello everyone, I'm trying to install te 2nd bootloader + TWRP. But I always get this error while trying to push the stack file to the device:
"C:\Android\adt\sdk\platform-tools>adb push stack /data/local/tmp/
failed to copy 'stack' to '/data/local/tmp//stack': Permission denied"
I'm following the instructions found in the [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 7" [07/08 Updates]
I have the files in the same folder where I'm running adb.
So I really don't know whats happening. If someone could point what I'm doing wrong I would thank it a lot. Or if someone knows how can I install a apk if I'm in Guatemala and can't actually download from Amazon would be very apreciated too!
So thanks in advance for your help.
Weird I have seen this error on occasion with people that use my wallpaper fix so I used a directory on the sdcard I stead, don't know if that's a good idea in this scenario though. What version of the amazon os are you running because I can think of a much easier method to install twrp and 2nd boot loader, I did it from 7.4.1, so I don't know how well it would work from latest update since I flashed cm 10.1.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
*************************************************************
INCORRECT USE OF THESE FILES WILL BRICK YOUR DEVICE
PLEASE ENSURE YOU KNOW WHAT YOU ARE DOING AND
I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG
*************************************************************
Here you can find stock firmware for both thor and apollo devices which are safestrap flashable.
Please note the following:
- These updates do NOT flash a new kernel or recovery - only a new /system image
- Before flashing ensure you know which stock base/kernel/safestrap you have installed and choose the appropriate version for that stock base/kernel.
- Do NOT use these images to downgrade or upgrade your base firmware.
I will be uploading them as and when I have time.
Thor Images:
- 13.3.1.0 <- Flashable on Safestrap 3.7.2
- 13.3.2.6 <- Flashable on Safestrap 3.7.5
*** THESE ONES DO NOT HAVE ROOT OR BLOCK UPDATES ***
- 13.4.5.2 <- Flashable on Safestrap v4.0.1
Apollo Images:
- 14.3.1.0 <- Flashable on Safestrap 3.7.2
- 14.3.2.6 <- Flashable on Safestrap 3.7.5
*** THESE ONES DO NOT HAVE ROOT OR BLOCK UPDATES ***
- 14.3.2.8 <- Flashable on Safestrap v3.7.5
- 14.4.5.2 <- Flashable on Safestrap v4.0.1
If you want to re-enable over the air updates then do the following:
- Skip this if you are using the 4.5.2 files - As stated above this does not apply so be careful.
- rename /system/etc/security/otacert.old to otacert.zip
- rename /system/app/com.amazon.dcp.old to com.amazon.dcp.apk
ggow said:
Hi All,
Here you can find stock firmware for both thor and apollo devices which are safestrap flashable.
Please note the following:
- These updates do NOT flash a new kernel or recovery - only a new /system image
- Before flashing ensure you know which stock base/kernel/safestrap you have installed and choose the appropriate version for that stock base/kernel.
I will be uploading them as and when I have time.
Thor Images:
- 13.3.1.0
Apollo Images:
- 14.3.1.0
If you want to re-enable over the air updates then do the following:
- rename /system/etc/security/otacert.old to otacert.zip
- rename /system/app/com.amazon.dcp.old to com.amazon.dcp.apk
Click to expand...
Click to collapse
Excellent! I am able to revert back to this stock firmware after nearly bricking my device. Thank you!!
Since I"m heavily tied into the Amazon ecosystem and have other Kindle devices, installing HDX Nexus 2.01 didn't work for me.
However, thanks to @ggow, using the same upgrade guide, Iwas able to get my 3.1.0 to 3.2.6, allowing my fire hdx devices to finally be able to do screen sharing with my fire TVs! I did have to restore /data, enable xposed + hdxposed, re-install kindlefree + Google play store APKs & stucks wallpaper fix to be back at 100%...
Will you make a pre rooted 4.5.1 image for the HDX 7.0 Thor?
Can I flash this over a Stock 4.5.1 device?
D0ubl3_X said:
Will you make a pre rooted 4.5.1 image for the HDX 7.0 Thor?
Can I flash this over a Stock 4.5.1 device?
Click to expand...
Click to collapse
As of right now, it's impossible to root 4.5.1.
No, you can't flash them over a newer version just like that. If you want to downgrade, check this thread.
Hey @ggow, would it be possible for you to release a rooted 14.3.2.6?
_Alex_ said:
Hey @ggow, would it be possible for you to release a rooted 14.3.2.6?
Click to expand...
Click to collapse
Hi _Alex_, yes I'll sort one out for you.
ggow
I goofed - flashed the apollo zip over my already properly up(down)graded stock. Now of course I get a blank screen when trying to boot the stock - not that I do it that often of course. I can still get into safestrap and boot the nexus 2.01 rom with no issues so am okay for now. Would I need something like a rooted 14.3.2.6 to fix this?
aren't these roms very old? Is there any way to get the latest AMAZON STOCK apps AND keep root? I really like the FIRE OS (way more than stock Android) but I also want all apps etc.
_Alex_ said:
Since I"m heavily tied into the Amazon ecosystem and have other Kindle devices, installing HDX Nexus 2.01 didn't work for me.
However, thanks to @ggow, using the same upgrade guide, Iwas able to get my 3.1.0 to 3.2.6, allowing my fire hdx devices to finally be able to do screen sharing with my fire TVs! I did have to restore /data, enable xposed + hdxposed, re-install kindlefree + Google play store APKs & stucks wallpaper fix to be back at 100%...
Click to expand...
Click to collapse
Was screen sharing to Fire TV not available on 13.3.2.3.2? Furthermore, what exactly does 13.3.2.6 offer that's new/improved? Does anyone have the changelog for this?
OK, so the LATEST FIRE OS Version that is rootable is "13.3.2.6" for the THOR device, is that correct? Or is there any other way to root a newer OS Version?´
Oh, and how can I flash this update? My device is rooted, but I have a very old OS Version on my kindle hdx.
Hey guys.. I screwed up.
I have a fire hdx Apollo that had been properly up(down)graded and running fine with 2.01. For some reason (and my lack of understanding the correct versions of things) I thought it would be a good idea to install the Apollo update on my stock rom. This of course has now caused boot loops on my stock boot but not my 2.01 boot.
Would love to be able to restore the stock as I do use some of the fire's capabilities from time to time. Sadly I did not do a backup before the update (kicks self furiously).
I DO have a backup from before the upgrade/downgrade so maybe I could restore that then push through the upgrade steps again or something. I'm worried that I will bork my safestrap or do something worse based on my proclivity for damage and chaos.
E.
_Alex_ said:
Hey @ggow, would it be possible for you to release a rooted 14.3.2.6?
Click to expand...
Click to collapse
Hi _Alex_,
Sorry about the long wait, I have posted a zip for 14.3.2.6. See OP.
Hey @ggow,
Thanks for your hard work. Could you possibly make an image for 13.3.2.4 (Thor)? It would be nice to have along with Nexus HDX 2.0.2.
NextDroid said:
Hey @ggow,
Thanks for your hard work. Could you possibly make an image for 13.3.2.4 (Thor)? It would be nice to have along with Nexus HDX 2.0.2.
Click to expand...
Click to collapse
Yes, I'll sort one out for you. Let you know when its up.
Sent from my Nexus 6 using Tapatalk
Looks like we're going to need it with the new bootloader bypass!
Just to clarify because someone asked, users of the HDX Nexus ROM would need it to downgrade to a firmware that the unlock works on.
ggow said:
Yes, I'll sort one out for you. Let you know when its up.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thank you!
Sent from my device
recreated the error with the Symlink. Crossposting from the TWRP Thor thread
Wiped system manually
The error log is:
Code:
Wiping system...
Symlinking...
symlink: some symlinks failed
[COLOR="Red"]E: Error executing updater binary in zip '/sdcard/TWRP13.3.1.0.zip'[/COLOR]
Error flashing zip '/sdcard/TWRP13.3.1.0.zip'
Updating partition details
Interesting... Getting the same error when I try to flash the original HDX 13.3.2.3 firmware, after I renamed it from .bin to .zip
Hi @ggow !
I made a flashable zip of the 4.5.2 update for Thor which is compatible with the signing exploit (bootloader/fw flashing removed and modified bootimage with happened dt) as there was some demand.
I'm not sure i should again create a thread for this rom(s) as we may be easily lost. Maybe all our "stock/modified stocks" roms should be in the same thread. What do you think about this ? Here is the link in case : http://android.mydedibox.fr/hdx/update-kindle-13.4.5.2_user_452004120-twrp.zip
Note that i only renamed "otacert.zip" to "otacert.old" on this rom as the "dcp" apk name has changed and i don't remember how i fixed that ... so ota updates may still be enabled isnt it ?
---------- Post added at 03:21 PM ---------- Previous post was at 03:16 PM ----------
aquaphun said:
recreated the error with the Symlink. Crossposting from the TWRP Thor thread
Wiped system manually
The error log is:
Code:
Wiping system...
Symlinking...
symlink: some symlinks failed
[COLOR="Red"]E: Error executing updater binary in zip '/sdcard/TWRP13.3.1.0.zip'[/COLOR]
Error flashing zip '/sdcard/TWRP13.3.1.0.zip'
Updating partition details
Interesting... Getting the same error when I try to flash the original HDX 13.3.2.3 firmware, after I renamed it from .bin to .zip
Click to expand...
Click to collapse
I don't know if it's the problem but the appolo recovery is based on an older kernel (3.1.0?) which doesn't have full selinux support. This prevented some zip to be properly flashed (at least on thor) until i use the 4.5.2 kernel sources. Unfortunately we will have to wait for @ggow to receive his new device, in the hope of an exploitable one (but this may be a different problem)
Edit : oups, you are on thor so it's not the problem !
Cpasjuste said:
Hi @ggow !
I made a flashable zip of the 4.5.2 update for Thor which is compatible with the signing exploit (bootloader/fw flashing removed and modified bootimage with happened dt) as there was some demand.
I'm not sure i should again create a thread for this rom(s) as we may be easily lost. Maybe all our "stock/modified stocks" roms should be in the same thread. What do you think about this ? Here is the link in case : http://android.mydedibox.fr/hdx/update-kindle-13.4.5.2_user_452004120-twrp.zip
Note that i only renamed "otacert.zip" to "otacert.old" on this rom as the "dcp" apk name has changed and i don't remember how i fixed that ... so ota updates may still be enabled isnt it ?
---------- Post added at 03:21 PM ---------- Previous post was at 03:16 PM ----------
I don't know if it's the problem but the appolo recovery is based on an older kernel (3.1.0?) which doesn't have full selinux support. This prevented some zip to be properly flashed (at least on thor) until i use the 4.5.2 kernel sources. Unfortunately we will have to wait for @ggow to receive his new device, in the hope of an exploitable one (but this may be a different problem)
Edit : oups, you are on thor so it's not the problem !
Click to expand...
Click to collapse
Hi @Cpasjuste,
Yes that's fine, I'll put your 4.5.2 image up on the same thread - no point replicating things
On 4.5.2 I wasn't sure which services needed to be disabled to prevent OTA. I'll add a note for this file to warn people to be careful when using it.
Hello XDA,
Ive looked somewhat specifically for this and havent found any clean cut answers to my questions - so first and foremost, if its a RTFM jobby, please do tell me and I'll go back to the search page and carry on reading. With that said, I was hoping someone might be able to assist me with the following:
[Current Build/SW version = P7-L00V100r001C17B117SP01 - EUI2.3 - I kept this version as I read that it became harder to root after that or on the latest build so thought not to make my life harder with what is completely new to me.]
1) I have a P7 L00 model and plan on using this in the UK - Ive checked the will my phone work website and o2 and EE will both work (contrary to what Ive read on both the huawei site and another one (which I cant remember) stating that the only Baseband that will work with the L00 model is EE) so wanted to ask if anyone can confirm o2 usage?
2) Can I use an L10 stock Rom to get rid of all the chinese default apps on this? I did get to a Chinese website with lots of EMUI roms but wasnt sure what to go with.
3) Is there a vanilla 5.1 or CyanogenMod ROM available? I have indeed just read the post on ubergizmo about 5.1 coming to the P7 but there wasnt a set date for it, and I'd assume that L00 model might be a different date altogether.
4) When Rooting and unlocking the bootloader via a thread I found on here (made by SeverusSnape and a few others ), I get to the part where I can use ROM Manager, but when I go into it and get auto prompted for Recovery set, it asks me to setup a custom recovery, and neither of the options I select give me anything - I select ClockworkMod REcovery and my device isnt listed, I hit the Device not listed selection and it tells me that there isnt an officially supported CWMR yet, have you installed a CWM based recovery manually? Yes takes me to a selection of CWM 2.xx or 3.xx and no tells me Until CWMR us available, ROM manager will not work with p7-L00.
Im unsure what Im doing wrong or what Ive missed?
5) Lastly, what I think I do get is if I've rooted using RootGenius, pulled over the play store APK, installed what I need to/want to use, I can use this as if it wasn't the L00 model?
Are there any future consequences (banking apps I know probably wont work with a rooted device) that would stop me from using the phone as a UK phone, and not possibly routing me through some central Chinese DB? (I ask this as im using WiFi on it now, and its pulling the latest version for it from somewhere, so would like to know where)
Again, apologies if this is all somewhere, but I do find that reading one thread links you to another, and then to another and another. Rinse repeat and its just got me a bit confused - its like Youtube videos except with lots of reading...
Many thanks for your time.
(PS. Id post a hilarious cat GIF but I cant do links yet )
Even some help pointing me in the right direction would be great.
Questions
I have similar questions
I don't believe there is a 5.1 CM available.
Would be great if we could flash L10 rom, but not sure if this will lose bands / functionality
Hey, I could not help you at all questions.. But anyway..
2.) No you can't. They're not compatible, so you risk to hard brick your device.
3.) There is no vanilla/ aosp/ cm Rom available, and probaly won't be also in future unfortunately. But for your L00 there is a miui v6 Rom available (just look in xda or Chinese forums). These days the official lollipop beta test is running, at the end of this month we might expect the final rom for all P7 devices (if all works as it is supposed to do..).
4.) It may be the best to look for a custom recovery in the "Android development" section and flash it per adb. Take a look to the right emui version, otherwise the recovery system won't work.
5.) I'd recommend to root your device, to delete all stuff you do not need and to flash Google Apps through your custom recovery afterwards. If you only install the apps you need in classical way, I assume you do not get all services running.
I hope I could help you a bit, even if some other people could do way better. I would recommend to ask specific question in smaller local forums.. Often they could help you more.
Thank you l3Nni.
I'll have a look through that and get back to you.
not sure if this belongs here, but couldn't find a teclast x80 pro section
I was looking to make this tab android only and then root it
found on the internet different sources for each procedure, so decided to compile everything in one place with full credits
teclast x80 pro [root + keep android only for 25gb storage]
---------------------------------------------------------------------------------------------------------------------------------------
[for 25gb of storage and android only]
first get the tools: https://www.mediafire.com/?qxwxz1mz47g7mkv
install PhoneFlashTool, iSocUSB-Driver-Setup-1.2.0, IntelAndroidDrvSetup1.5.0
then you need to check what firmware your tab is on, it's written on the back of the tablet
mine was on E3E9 however teclast site didn't have the firmware so I used the e3e8 instead and it works fine
download the firmware from http://www.teclast.com/en/firmware/
you need to get the android.rar
when it's done, unpack the android.rar
then unpack the gpt.rar
take the gpt.bin and copy-paste it in the android folder, replacing the original gpt.bin
put tablet in dnx mode, press volume +, volume - and power at the same time
connect tab to pc with usb cable
run the phone flash tool browse for the android folder and flash the android image
after it is done you have 25gb all for android
--------------------------------------------------------------------------------------------------------------------------
[for root access]
you must have adb drivers installed for this to work
copy+paste the UPDATE-SuperSU.zip to the tablet
with the tab switched on normally and connected to pc with usb cable go to settings>developer options and check "oem unlocking" and "usb debugging"
then go to the toolbox folder and double-click 1.Unlock_Bootloader.bat
wait for it to do the work, then reboot and again go to settings>developer options and check "oem unlocking" and "usb debugging"
then double-click 2.Unlock_Verity-boot.bat, reboot and repeat oem and debug settings
then double click 3 Flash-boot.bat , reboot and repeat oem and debug settings
steps 4 and 5 from the toolbox folder didn't work for me, if it works for you after double-click all good
if it doesn't: shift+right click the toolbox folder with tab connected to pc and "open command window here"
copy and paste this in the command window:
adb reboot fastboot
"press enter"
fastboot flash recovery TWRP-X80-pro.img
"press enter"
adb reboot recovery
"press enter"
from the twrp menu, select install and browse for the UPDATE-SuperSU.zip you copy+pasted earlier
reboot and you should have root access + fully working twrp recovery
---------------------------------------------------------------------------------------------------------------------
full credits
machetekills from techtablets.com for porting this twrp and the toolbox!
https://techtablets.com/forum/topic/x80-pro-toolbox-unlock-new-tablet-twrp-2-8-7-0-root/
allember for the .gpt file
https://techtablets.com/forum/topic/x80-plus-android-os-only/#post-42636
-----------------------------------------
other stuff
this tab gets really hot when gaming by the way
one way to fix this is to get the no frills cpu control from the play store and set the max speed for the processor to
1,2 or 1,3, from 1,92, this gets the heat down to almost normal and won't burn your hand anymore like it used too
now I can play and read in peace
http://imgur.com/a/OZtGw
**********************************************************
here is WalterNimoy's solution to root on E3E9
thanks for sharing buddy ~
------------------------------------------------------------------
The problem is in the boot.img. So, to root the E3E9, you mus essentially follow the tutorial above, but instead of the backup for the E3E8, download the version for the E3E9. You can do it here.
E3E9 Teclast X80 Pro : http://www.teclast.com/tools/pad/pad.php?t=p
Then after, the real solution. You must absolutely use another version of the boot.img. If you use the one in the tutorial with the E3E9, you won't have sound, touchscreen buggy, etc. So use this one instead. It's also v. 1.07. I believe it's was originally made for the X80 Power, but it work perfectly with the X80 Pro E3E9.
boot.img v. 1.07 E3E9 https://yadi.sk/d/78MARiHGtyfdG
Finally, if you have a problem when it's time to root, inthe step 4, enter the command manually. It was the solution to make it work for me.
Here you go! Your X80 Pro E3E9 should be rooted, with everything working. Let me know if it also worked for you!
--------------------------------------------------------------------------
Houston, we have a problem. First, thank you for your work. Unfortunately, it doesn't go well from here. I have the E3E9 version of the tablet. I also used the firmware for this tablet , and not the E3E8 as you did. The firmware have about 50 %less brightness in the E3E8 firmware than in the E3E9, and is also compiled for a slower cpu. So, after I flash the ROM, all go well. The two first steps for root access also go well. The problem begin at the third step, after I flash the boot.img. The Gsensor stop working, and the sound as well. I succeed to root, but the tablet is not really usable... Do you have any idea? I really want to root, but with these limitations, it is better not to. Thank you.
A couple of notes for anyone attempting this:
1. There's a v1.07 ROM for E3E9 which I dug up from the Chinese website (don't ask me how I did this, I tried to replicate my steps with no success XD). Uploaded the file as-is to my Dropbox: https://www.dropbox.com/s/eoo8stw1xxyrif3/
2. In my testing, after rooting, I lost audio and access to SD card. The touch screen would also occasionally stop working. I used the ROM mentioned above, and not the one that the op used, so your mileage may vary.
3. I was extremely unpleased with the performance of the stock ROM, and the phenomenon I experienced after rooting made me look of an alternative solution - which I found in a Russian forum (https://4pda.ru/forum/index.php?showtopic=741990&st=1640#entry55200079). A gem in the form of custom CM12.1 ROM baked for the E3E7 model. Installed it on my tablet and it worked flawlessly! The default language is Russian, but your're prompted to change it on the first installation screen.
I'm using this for a couple of hours now and everything seems to be working extremely well, with no dropped frames or choppy animations I experienced in the stock version.
I'll keep testing and report back if I find any bugs.
Edit 1:
So I noticed just a couple of drawbacks for using the CM Rom:
1. Camera is not working (however, I don't think it's a big deal given its quality anyway)
2. I made sure to backup the "Boot to Windows" apk beforehand, but it won't let me install it. If anyone could grab their apk and upload here, I could try it and report back.
Succède, finally
I succeed to root v1.07, E3E9. Let me know if you want to know how I manage to do this. ?
WalterNimoy said:
I succeed to root v1.07, E3E9. Let me know if you want to know how I manage to do this. ?
Click to expand...
Click to collapse
Share it man. I want to buy this device
WalterNimoy said:
Houston, we have a problem. First, thank you for your work. Unfortunately, it doesn't go well from here. I have the E3E9 version of the tablet. I also used the firmware for this tablet , and not the E3E8 as you did. The firmware have about 50 %less brightness in the E3E8 firmware than in the E3E9, and is also compiled for a slower cpu. So, after I flash the ROM, all go well. The two first steps for root access also go well. The problem begin at the third step, after I flash the boot.img. The Gsensor stop working, and the sound as well. I succeed to root, but the tablet is not really usable... Do you have any idea? I really want to root, but with these limitations, it is better not to. Thank you.
Click to expand...
Click to collapse
in e3e8 that I flashed, everything but the camera works - the quality is [email protected] anyway so no real loss - g sensor works fine and underclocking makes the battery last a lot longer
I'm using this as a reader and some gaming with a 32gb sd card that has a tiny part of my library and some games and plays fine
this screen is perfect for reading
it looks like you found a way to root e3e9 tho
WalterNimoy said:
I succeed to root v1.07, E3E9. Let me know if you want to know how I manage to do this.
Click to expand...
Click to collapse
share away
11wallace11 said:
A couple of notes for anyone attempting this:
1. There's a v1.07 ROM for E3E9 which I dug up from the Chinese website (don't ask me how I did this, I tried to replicate my steps with no success XD). Uploaded the file as-is to my Dropbox: https://www.dropbox.com/s/eoo8stw1xxyrif3/
2. In my testing, after rooting, I lost audio and access to SD card. The touch screen would also occasionally stop working. I used the ROM mentioned above, and not the one that the op used, so your mileage may vary.
3. I was extremely unpleased with the performance of the stock ROM, and the phenomenon I experienced after rooting made me look of an alternative solution - which I found in a Russian forum (https://4pda.ru/forum/index.php?showtopic=741990&st=1640#entry55200079). A gem in the form of custom CM12.1 ROM baked for the E3E7 model. Installed it on my tablet and it worked flawlessly! The default language is Russian, but your're prompted to change it on the first installation screen.
I'm using this for a couple of hours now and everything seems to be working extremely well, with no dropped frames or choppy animations I experienced in the stock version.
I'll keep testing and report back if I find any bugs.
Edit 1:
So I noticed just a couple of drawbacks for using the CM Rom:
1. Camera is not working (however, I don't think it's a big deal given its quality anyway)
.
Click to expand...
Click to collapse
camera is not working even in the stock rom I flashed haha
I just asked stratos7 to post the solution to root the E3E9. I still cannot post outside link. So, just wait a little. He will surely see the message in his inbox.
So guys, how is your experience with teclast x80 pro. What is the pros and cons? I want to buy cheap tablet but still confused.
Teclast x80 pro
Onda v80 plus
Onda v891w CH
All below $100. Which one is your recomendation? Sorry a bit OOT
here is WalterNimoy's solution to root on E3E9
------------------------------------------------------------------
The problem is in the boot.img. So, to root the E3E9, you mus essentially follow the tutorial above, but instead of the backup for the E3E8, download the version for the E3E9. You can do it here.
E3E9 Teclast X80 Pro : http://www.teclast.com/tools/pad/pad.php?t=p
Then after, the real solution. You must absolutely use another version of the boot.img. If you use the one in the tutorial with the E3E9, you won't have sound, touchscreen buggy, etc. So use this one instead. It's also v. 1.07. I believe it's was originally made for the X80 Power, but it work perfectly with the X80 Pro E3E9.
boot.img v. 1.07 E3E9 https://yadi.sk/d/78MARiHGtyfdG
Finally, if you have a problem when it's time to root, inthe step 4, enter the command manually. It was the solution to make it work for me.
Here you go! Your X80 Pro E3E9 should be rooted, with everything working. Let me know if it also worked for you!
--------------------------------------------------------------------------
link to the e3e9 firmware is stating that a baidu account is needed to download some of the files, is there a way to get the files without this account?
avi321 said:
link to the e3e9 firmware is stating that a baidu account is needed to download some of the files, is there a way to get the files without this account?
Click to expand...
Click to collapse
You can download the full firmware from here: https://yadi.sk/d/2Fes5npR3GykqT it downloads quickly and its the correct files.
Just found it on the Russian forum: https://w3bsit3-dns.com/forum/index.php?showtopic=741990&st=2280
lost sound
I flashed E3E9 firmware from the yandisk above, the sound doesn't work after. I tried also the boot image from the post before, the tablet didn't boot.
I am now stuck with the device with no sound, using the E3E9 image. is there anything that can be done?
phone flash tool: "F..ailed to load" "There is no flash file in the archive". Please help.
...
..
If anyone still replies to this thread, im stuck at step 3 with the boot.img. after flashing the boot.img my tablet is stuck in a bootloop teclast screen. E3E9 model
With a X80 Pro E6E9 the procedure for remove the partition with Windows still work? i dont need the root but just remove Windows
...has anyone SUCCESSFULLY rooted thier Teclast-x80 pro...WITHOUT complications...?!?...
...and can I root my tablet without taking out the Windows part...?!?...
---------- Post added at 07:09 PM ---------- Previous post was at 07:06 PM ----------
...has anyone SUCCESSFULLY rooted thier Teclast-x80 pro...WITHOUT complications...?!?...
...and can I root my tablet without taking out the Windows part...?!?...
Android 6 and 7
This works well: http://www.android-x86.org/download
Someone should get the sound to work.
---------- Post added at 10:15 PM ---------- Previous post was at 10:11 PM ----------
Connect usb hub with keyboard and unetbootin Android ISO usb key. Boot into bios and select usb key as boot device.
shez2 said:
This works well: http://www.android-x86.org/download
Someone should get the sound to work.
---------- Post added at 10:15 PM ---------- Previous post was at 10:11 PM ----------
Connect usb hub with keyboard and unetbootin Android ISO usb key. Boot into bios and select usb key as boot device.
Click to expand...
Click to collapse
What is that? I see CM 14.1.
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 .