Related
TWRP (Team Win Recovery Project) replaces a device's stock recovery and provides, among other options, the ability to install img (image) and zip files. TWRP for the Fire HDs was developed by JMZ and is described here.
How to install TWRP
These steps are for a first-time install on a rooted Fire HD running OS 4.5.3 with stock bootloader and recovery.
At this time, 4.5.3 bootloader is required. You're welcome to try to get it onto a different OS, but you need the 4.5.3 bootloaders and I'm not getting into that. So, if you're running a different OS, have messed with partitions or done something that requires a TWRP reinstall (other than reinstalling 4.5.3 and rerooting), you risk being unable to boot recovery or bootloop/brick.
OK, that doesn't sound so "newbie-friendly" but this really is a simple process that should always go smoothly on a "clean" OS 4.5.3.
You can easily install TWRP with either TWRP Manager (also by JMZ) or Flashify from the Play Store.
If you don't have Play Store access:
- Flashify - v 1.9.1 from APKMirror
- TWRP Manager - Download from JMZSoftwareFor installing TWRP, the only difference between the two is that TWRP Manager auto-downloads the correct TWRP version while Flashify requires you download it yourself.
[EDIT 8/16/2015] At this time, TWRP Manager doesn't seem to be working. Use Flashify, instructions below. Steps for TWRP Manager are at bottom of post.
Install TWRP with Flashify
Download JMZ's ariel TWRP image (https://www.androidfilehost.com/?fid=24052804347756852) to the Fire's download folder.
Install and run Flashify (download link above) and give it superuser access when prompted. It probably will also prompt to apply loki patch for Kitkat. Say yes.
Tap Recovery Image and then Choose a File.
Navigate to download folder, tap the TWRP file, and when Flashify asks if you are sure, tap Yup!
If install succeeds ("Flash Complete"): (a) Tap Reboot now. (b) When back in Fire OS, boot to recovery (below) and confirm you're in TWRP. Note: If tablet bootloops, post the problem in one of the bootloop threads.
If install fails (error messages displayed), first take a screenshot. If you can determine the problem, fix it and try again or try TWRP Manager. If you don't understand the error or can't resolve it, post in a "TWRP install failure" thread.
How to Boot to Recovery
Manual: (a) Power off tablet. (b) Hold down power and volume-up buttons at same time until you see "Amazon," then release. (If you just boot back into Fire, you didn't power off first or didn't hold buttons long enough.)
adb command from computer: adb reboot recovery
- If you see TWRP, great! Check it out and then press Reboot and System to go back to OS.
- If you get stock recovery screen ("reboot" and "factory reset"), TWRP didn't install. Reboot should be highlighted. (If it's not, use volume-up or -down to select it.) Press the power button to click reboot and when back in Fire OS, try the other app.
[EDIT 1] For simplicity, install TWRP Manager on the Fire and follow these steps.
Install TWRP with TWRP Manager
Install and run TWRP Manager and give it superuser access when prompted. It will also prompt to apply patch for Kitkat. Say yes.
Tap top-left of screen for slide-out menu and select Install TWRP.
Confirm Device Name shows "ariel" and then tap Install Recovery. [download begins]
At warning screen, tap yes.
If install succeeds ("Flash Successful"): (a) Go to slide-out menu and choose Reboot Options and then Reboot Device. (b) When back in Fire OS, boot to recovery (above) and confirm you're in TWRP.
Note: If tablet bootloops, post the problem in one of the bootloop threads.
If install fails (error messages displayed), take a screenshot in case you need to post the problem and then look at comments here for a solution. If you can determine the problem, fix it and try again or try Flashify. If you don't understand the error or can't resolve it, post in a "TWRP install failure" thread.
After step 5 a) only puts on the screen "Kindle Fire" and I can not make the "Power and Volume up buttons reboot".
Could you help me please?
Po069 said:
After step 5 a) only puts on the screen "Kindle Fire" and I can not make the "Power and Volume up buttons reboot".
Could you help me please?
Click to expand...
Click to collapse
I'm sorry I can't help you. This guide is for the 2014 Fire HD tablets. The Kindle Fires are ealier models. Look here to figure out which tablet you have and then post the problem in the forum for your tablet:http://forum.xda-developers.com/kindle-fire/help/index-amazon-kindle-fire-t3205350
DoLooper said:
I'm sorry I can't help you. This guide is for the 2014 Fire HD tablets. The Kindle Fires are ealier models. Look here to figure out which tablet you have and then post the problem in the forum for your tablet:http://forum.xda-developers.com/kindle-fire/help/index-amazon-kindle-fire-t3205350
Click to expand...
Click to collapse
Thank you very much for your answer.
Kind regards.
Sorry if this is a stupid question, but if I update the Fire OS after successfully rooting/installing TWRP will I mess up anything?
I rooted everything and installed TWRP succesfully on my Fire HD 6 running 4.5.3 (it was fresh out of the box and I didn't allow any OTA updates). If I update the OS now will it brick it or mess up TWRP in any way?
Also, ultimately I'm just trying to get Google Apps on my HD 6 (it'd be nice if I could get lollipop on it but I bricked the last HD 6 I had so I'm starting with the low-hanging fruit haha). However, I can't really find a guide to do this starting from 4.5.3 Fire OS... Could you point a noob anywhere to either a) install GApps or b) get lollipop installed?
I was trying to follow this tutorial but it's not really noobie-friendly and I think it's meant to start from 5.0.n which is why I'm asking if I can update without screwing anything up.
Thanks for your help!
SpaceBananas said:
Sorry if this is a stupid question, but if I update the Fire OS after successfully rooting/installing TWRP will I mess up anything?
I rooted everything and installed TWRP succesfully on my Fire HD 6 running 4.5.3 (it was fresh out of the box and I didn't allow any OTA updates). If I update the OS now will it brick it or mess up TWRP in any way?
Also, ultimately I'm just trying to get Google Apps on my HD 6 (it'd be nice if I could get lollipop on it but I bricked the last HD 6 I had so I'm starting with the low-hanging fruit haha). However, I can't really find a guide to do this starting from 4.5.3 Fire OS... Could you point a noob anywhere to either a) install GApps or b) get lollipop installed?
I was trying to follow this tutorial but it's not really noobie-friendly and I think it's meant to start from 5.0.n which is why I'm asking if I can update without screwing anything up.
Click to expand...
Click to collapse
If you update now without following that guide you will lose root and TWRP. You may not be able to root with Kingroot and you won't have the "friendly" bootloaders that can boot TWRP. Don't do it.
I'll have to get back to you about updating. Maybe bibikalka will jump in. Look around for a KitKat version of pico-uni Gapps, which you could install in TWRP now. There will be link in an old guide for OS 4.
SpaceBananas said:
I rooted everything and installed TWRP succesfully on my Fire HD 6 running 4.5.3 (it was fresh out of the box and I didn't allow any OTA updates).
. . .
Also, ultimately I'm just trying to get Google Apps on my HD 6 (it'd be nice if I could get lollipop on it but I bricked the last HD 6 I had so I'm starting with the low-hanging fruit haha). However, I can't really find a guide to do this starting from 4.5.3 Fire OS... Could you point a noob anywhere to either a) install GApps or b) get lollipop installed?
I was trying to follow this tutorial but it's not really noobie-friendly and I think it's meant to start from 5.0.n which is why I'm asking if I can update without screwing anything up.
Click to expand...
Click to collapse
OK, I looked at the guide again. @bibikalka may have a preferred route, but here's what I suggest: Pretend nothing else is there except steps 1) through 3) and just carefully follow those steps.
Download all the files to the pc first. Get the 5.1.1 update (only because we know it's rootable with Kingroot) and rename the extension from bin to zip. Skip Xposed (step 1-7). Do get 5.2.0_stock_recovery_uboot.zip (step 1-10). Copy or move all the files to the downloads folder on device. (This is the long way and you can download directly to device if you prefer. I just find it easier to download and double check that you have all the right files from the pc.)
Hold Power and volume+ to get into TWRP, then carefully do all the sub-steps under 1) except for step 7. (From what you say, I just don't think you need Xposed.) Just be sure you have the correct file at each step and you'll be fine.
DoLooper said:
OK, I looked at the guide again. @bibikalka may have a preferred route, but here's what I suggest: Pretend nothing else is there except steps 1) through 3) and just carefully follow those steps.
Download all the files to the pc first. Get the 5.1.1 update (only because we know it's rootable with Kingroot) and rename the extension from bin to zip. Skip Xposed (step 1-7). Do get 5.2.0_stock_recovery_uboot.zip (step 1-10). Copy or move all the files to the downloads folder on device. (This is the long way and you can download directly to device if you prefer. I just find it easier to download and double check that you have all the right files from the pc.)
Hold Power and volume+ to get into TWRP, then carefully do all the sub-steps under 1) except for step 7. (From what you say, I just don't think you need Xposed.) Just be sure you have the correct file at each step and you'll be fine.
Click to expand...
Click to collapse
Any point in using 5.1.1 ? Since SuperSu gets flashed during the update, it does not care which FireOS version it is. Nobody will be running Kingroot since SuperSu is already there
bibikalka said:
Any point in using 5.1.1 ? Since SuperSu gets flashed during the update, it does not care which FireOS version it is. Nobody will be running Kingroot since SuperSu is already there
Click to expand...
Click to collapse
No, 5.1.2 is fine. It was just a cya suggestion in case user missed a step and somehow lost root--but OF COURSE no steps will be missed.
TWRP failed to install, now have no recovery
So I'll start by saying I'm an idiot. I wasn't paying attention to which version OS is required and tried to install TWRP using Flashify. It went through the motions and did its reboot, and now I'm stuck with absolutely no recovery at all. I've tried searching these forums for a "TWRP installation failed" thread and have had no luck, at least not for the Fire HD 6 device. Really need help here, I have absolutely no way to get into recovery to flash anything back at all.
I bought a shield tv 2015 16gb. It was already rooted running full android lollipop. The person I bought it from said this is the best way to run it. I want to upgrade to latest full android. Because I ran out of storage. I believe with update I can add external hard drive and convert it to internal. Since I'm already rooted on full android how would I do it. I also have retroarch with many emulators and hyperspin set up. When I upgrade can I keep it set up or will I lose it. Thanks for any help
Hi, you need to flash stock Nvidia Lollipop recovery image for you SHIELD model (always make sure stock firmwares you download is for your device model).
Once in stock you need to manually upgrade little by little until you get the final prompt to install latest Nvidia Experience 5.1 which is Nougat based via OTA (Over the Air). Why you have to do all that? Because Nvidia also updates bootloader, kernel which are important, mostly bootloader (Warning: never mess or play with the bootloader) and using Nvidia OTA updates service is easy and safe to do.
Usually for Full Android firmware provided by @zulu99 which I bet is the one you have installed is required to flash only system.img and vendor.img so is safe to flash and you can't brick your Shield that way, but to update to latest Full Android Nougat as I said you MUST have to go back to equivalent stock (lollipop in your case) then manually update via Nvidia OTA and once you be in 5.1 stock firmware you can then flash full Android Nougat 1.2 to your device which only contain system.img and vendor.img.
That is why you need to flash full stock updates because you also need to update bootloader, kernel, recovery, etc etc not only system and vendor so that is the CORRECT and SAFE way to upgrade.
Do never try to skip important steps, is not worth it, you will safe yourself many headaches and your money won't be wasted because you device won't brick if you do things right.
Last word of advice, once you are in latest Nougat or above do not attempt to downgrade to MM or LP, otherwise you can brick your device.
From LP to MM to Nougat there are massive changes done, starting for the bootloader and so far there is NO safe way to reverse from Nougat to MM or below, only upgrade. I've seen around 6 users now that have bricked their devices for trying to FULLY downgrade from Nougat.
As always research, ask before doing flashing tasks.
Here is the website where you can read and find instructions. In Full Android Nougat thread you can also find my super video tutorial for step by step instructions to flash that ROM from stock:
http://www.videomap.it/forum/viewforum.php?f=25&sid=7939d87e6e7dd7f1110c20f8cdd28a6f
Everything you need can be found on that forum section.
Enviado desde mi Moto X mediante Tapatalk
Thanks for reply. Watched your video very informative. Do you have a video for me to follow to flash back to stock. I've never done this before but feel confident if I can follow along. Also I have retroarch with emulators , roms and hyperspin that took a long time to setup. What is the best way to back it up and reinstall after upgrade. Is there an backup app I should use
Gknyfd said:
Thanks for reply. Watched your video very informative. Do you have a video for me to follow to flash back to stock. I've never done this before but feel confident if I can follow along. Also I have retroarch with emulators , roms and hyperspin that took a long time to setup. What is the best way to back it up and reinstall after upgrade. Is there an backup app I should use
Click to expand...
Click to collapse
I also have RetroArch and hyperspin setup but for hyperspin all your setup should be in a folder called Hyperspin, all including Roms should be on that folder. I have it like that and I just have to copy that single folder to back it up, very simple. As per RetroArch I think the app has a setting to export the config, check that out. I have very little changes in RetroArch so I don't back up that app config.
Post a screenshot of Settings > About showing off Build, Kernel and Shield Android TV SW version to see if you really have @zulu99 ROM.
I don't have a video about how to flash back to stock but is the same in the way that you have to flash .img files via fastboot, the difference is that you flash stock images not custom.
If you go to the thread of full Android Lollipop for Shield TV, in second post there is a link to Stock Nvidia LP firmware. Download that package, verify the download and uncompress, then ONLY copy system.img to C:\ADB (Did you check my YouTube's video Description to download the tools?) because only system was flashed to have full Android Nougat, the rest is plain stock, it should be, unless the guy you purchased the Shield from also flashed custom recovery. Based on that use the following commands:
fastboot flash system system.img
fastboot flash recovery recovery.img (copy it to C:\ADB too and flash it just in case)
fastboot -w
fastboot reboot
Once done you should be back to stock, let it boot and if everything went well continue with the instructions upgrading via Nvidia OTA until you get to install Nougat 5.1
Write back if you run into an issue.
Edit: links in second don't point to 2.1 LP recovery image anymore. Use this link instead:
http://developer.download.nvidia.com/mobile/shield/ROM/SHIELD_ATV/Upgrade-2.1 - 707MB
Enviado desde mi Moto X mediante Tapatalk
I'm not sure how to post a screenshot on here. In settings my android version is 5.1. My kernel version is 3.10.61-ge817e80 [email protected] u64-396#1. My build number is lmy47d.35739_609.6420.. in my device storage I have a zip file named nv-recovery-image-shield-arc-upgrade2_1_dev_rooted.zip. Is this the image I need to go back to stock. It has the blob ,boot, flash all bat,flash all sh,flash base sh,recover Img,system img, tegra210-foster-e-p2530-0930-e02-00 dtb, and user data img
Gknyfd said:
I'm not sure how to post a screenshot on here. In settings my android version is 5.1. My kernel version is 3.10.61-ge817e80 [email protected] u64-396#1. My build number is lmy47d.35739_609.6420.. in my device storage I have a zip file named nv-recovery-image-shield-arc-upgrade2_1_dev_rooted.zip. Is this the image I need to go back to stock. It has the blob ,boot, flash all bat,flash all sh,flash base sh,recover Img,system img, tegra210-foster-e-p2530-0930-e02-00 dtb, and user data img
Click to expand...
Click to collapse
At the end of Build info says Full Android 2.2 or something similar, details are important.
I also have [email protected] in kernel info so I yes could be zulu99' ROM but I want to make sure, so confirm the build info.
So you have the developer image which comes rooted. I think if you flash the dev image it will upgrade to dev stock firmwares. Thing is I'm not sure if dev images differ in other things than normal stock images because Nvidia tried to screw zulu99 blocking many things so he had to do alot of hacking to have a fully functional full Android Nougat firmware. So, is better if you stick to the instructions, better download stock recovery image and continue:
http://developer.download.nvidia.com/mobile/shield/ROM/SHIELD_ATV/Upgrade-2.1 - download the one with 707MB , the other 709MB is for PRO model.
You may also go ahead and read the .txt file in that link with the instructions to flash back to stock.
Enviado desde mi Moto X mediante Tapatalk
It doesn't say anywhere in the build info full android with a version number. It is exactly like I posted it. The recovery zip I have in my devices storage was left there by person I bought it from. Is that the same as the one you directed me too. Did he leave that file there in the event it would need to be flashed back to stock. I want to make sure I get this right before I have a go at it. I do appreciate your patience thanks
Gknyfd said:
It doesn't say anywhere in the build info full android with a version number. It is exactly like I posted it. The recovery zip I have in my devices storage was left there by person I bought it from. Is that the same as the one you directed me too. Did he leave that file there in the event it would need to be flashed back to stock. I want to make sure I get this right before I have a go at it. I do appreciate your patience thanks
Click to expand...
Click to collapse
No, the files are not the same. Then one you have in your storage has dev_root in package name. Nvidia provides normal stock recovery images and developer recovery images as well for each new OTA release in all models.
The one I linked you to is the normal stock Android TV 16gb recovery image. Download and use that one better and flash (The one in the link I posted).
Enviado desde mi Moto X mediante Tapatalk
Got it, will do. Do you think you could list the steps in a way a noob would understand. Want to make sure I don't brick this
Gknyfd said:
Got it, will do. Do you think you could list the steps in a way a noob would understand. Want to make sure I don't brick this
Click to expand...
Click to collapse
Do this step by step. First let's get you back to stock:
Download the recovery firmware I linked you to, then follow my video but just use system.img and recovery.img of the downloaded firmware, NOTHING ELSE.
Once successfully flashed, reboot your device and report back.
Enviado desde mi Moto X mediante Tapatalk
Ok I'm ready I downloaded all necessary files. My queation when I click on fastboot or add it opens a window and quickly shuts. Should it stay open or not until I plug in shield tv and put it in fastboot mode. Want to make sure everything is right before I start
lavero.burgos said:
No, the files are not the same. Then one you have in your storage has dev_root in package name. Nvidia provides normal stock recovery images and developer recovery images as well for each new OTA release in all models.
The one I linked you to is the normal stock Android TV 16gb recovery image. Download and use that one better and flash (The one in the link I posted).
Enviado desde mi Moto X mediante Tapatalk
Click to expand...
Click to collapse
Ok I believe I'm ready I downloaded all all I need from your links. In c drive I have adb folder with fastboot adb , system img and recovery img. And adbwinapi.dll and adbwinusbapi.dll. If I click on fastboot or adb a windows opens and quickly shuts. Is this normal. Does it only stay open once I'm in boot loader . Want to make sure everything is right before I start
Gknyfd said:
Ok I'm ready I downloaded all necessary files. My question when I click on fastboot or add it opens a window and quickly shuts. Should it stay open or not until I plug in shield tv and put it in fastboot mode. Want to make sure everything is right before I start
Click to expand...
Click to collapse
Hmm seems you're not following the video. I asked before did you check my youtube's video description? because there i provide some links and the first link is to download the proper tools... https://bit.ly/satvtools, then in C:\ADB you have to double click the command line shortcut named ADB and NOT fastboot.exe
I suggest to first watch the entire video at least 3 times before proceeding, so you start understanding better the procedure.
Ok I will want to make sure I understand and do this right. I didn't connect shield yet for that reason. If shield isn't connected and I and I double click adb should window stay open or only when shield is connected
Gknyfd said:
Ok I will want to make sure I understand and do this right. I didn't connect shield yet for that reason. If shield isn't connected and I and I double click adb should window stay open or only when shield is connected
Click to expand...
Click to collapse
Use the ADB.Ink shortcut that is inside ADB folder (from the .zip tools i provided)
If you click on ADB.Ink, WIndows will then open the CMD/ Windows Shell/ Terminal Console or whatever you want to call it and remain open
Thanks for your patience got it I put it in c:/ adb folder. That's where it should be right. If yes I'm gonna go for it
Having a problem my computer isn't seeing the shield tv not able to install drivers
Gknyfd said:
Thanks for your patience got it I put it in c:/ adb folder. That's where it should be right. If yes I'm gonna go for it
Click to expand...
Click to collapse
Yes, everything (tools, .img files,etc) should be under C:/ADB folder
Gknyfd said:
Having a problem my computer isn't seeing the shield tv not able to install drivers
Click to expand...
Click to collapse
Try with other USB cables
Thanks for all your help and your time. I got it done. I'm back to stock and fully upgraded tomorrow I'll follow your video and root to full nougat. Couldn't have gotten it done without your guidance. Hopefully I'll be able to help out others in my situation now. It was the USB cable. I had 2 that didn't work. Finally the third I tried worked. Thanks
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images.
I have access to a 10.1 with keyboard (ONA19TB007) and without (ONA19TB003) that I can pull updates and images from, but I do not have access to the 8" (ONA19TB002) or newer 7" tablet. Any assistance with those two would be welcomed :good:
Onn 10.1" without keyboard - ONA19TB003
OTA
20191015-1827
Stock Images
October 2019
Full (Thanks @CaffeinePizza!)
Boot
Recovery
VbMeta
Vendor
System
May 2019
Full (Thanks @CaffeinePizza!)
Onn 10.1" with keyboard - ONA19TB007
OTA
20191011-1212
20190516-1437
Stock Images
October 2019
Boot
Recovery
Vendor
VbMeta
System
May 2019
Boot
Recovery
Vendor
VbMeta
System
Onn 8" - ONA19TB002
OTA
November 2019 (Thanks @martyfender)
July 2019 (Thanks @tek3195)
Stock Images
November 2019
Full (Thanks @CaffeinePizza!)
May 2019
Full (Thanks @CaffeinePizza!)
Onn 7" Surf - 100005206
OTA
November 2019 (Thanks @tek3195)
Stock Images
October 2019
Full (Thanks @deadman96385!!)
June 2019
Full (Thanks @deadman96385!)
*Reserved
NFSP G35 said:
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images.
Click to expand...
Click to collapse
I discovered that running the following command
Code:
pm uninstall -k --user 0 com.adups.fota.sysoper && pm uninstall -k --user 0 com.adups.fota
withing adb shell will disable the over the air updates.
I do not know if there is any truth to this, but Malwarebytes has an article on this, claiming that the software can be used to collect user data so I chose to disable it.
^ yep. I ran across a lot of worrysome information about that software. I figure I can 'take one for the team' and leave it enabled on mine, and collect updates here.
That way, if anyone wants to update while leaving com.adups.fota disabled or uninstalled, now they will have a way to do so
NFSP G35 said:
^ yep. I ran across a lot of worrysome information about that software. I figure I can 'take one for the team' and leave it enabled on mine, and collect updates here.
That way, if anyone wants to update while leaving com.adups.fota disabled or uninstalled, now they will have a way to do so
Click to expand...
Click to collapse
I am repeating some information I previously stated since we now have a section specifically for this:
I am sure @CaffeinePizza would not mind, he posted stock roms in this POST. Maybe a link to this information in the OP will help people looking for a STOCK rom for the 8' and 10' devices. The images he is hosting are patched to April 5, 2019. Anyone wishing to flash these images will need the SP Flash tools.
OTA for 8" ONA19TB002 https://drive.google.com/file/d/10vFETRunJEkyZXGUV05-rmJy60qrnSuy/view?usp=sharing
I can not remember date but somewhere around July 2019.
tek3195 said:
OTA for 8" ONA19TB002 https://drive.google.com/file/d/10vFETRunJEkyZXGUV05-rmJy60qrnSuy/view?usp=sharing
I can not remember date but somewhere around July 2019.
Click to expand...
Click to collapse
Thanks! Added to the OP
I guess this would be the place for the 7" SURF OTA's to reside for now ? Here is ota for Onn 7" Surf Model 100005206 downloaded 11/7/2019 have not installed yet so don't have security patch date.
https://drive.google.com/file/d/1U77dxYgO-ihbO1XP6c8AiEnEtUlJRcfI/view?usp=sharing
tek3195 said:
I guess this would be the place for the 7" SURF OTA's to reside for now ? Here is ota for Onn 7" Surf Model 100005206 downloaded 11/7/2019 have not installed yet so don't have security patch date.
https://drive.google.com/file/d/1U77dxYgO-ihbO1XP6c8AiEnEtUlJRcfI/view?usp=sharing
Click to expand...
Click to collapse
Thanks!
Added to the OP along with a couple of images from the 007.
More to come once I can get them uploaded.
Random OT... I just noticed you're in PC... Hi from Tallahassee!
Maybe we should have a thread on sptools too... I still need to read up on mtk told but there are so many...
You're welcome to reference my thread and post a link to my server with the x003 and x002 stock images. SP Flash Tools is needed.
https://forum.xda-developers.com/showpost.php?p=80574967&postcount=192
https://www.nathanbar.net/files/android
I plan on making a proper thread, perhaps this weekend, on how to backup with Wwr, and flash with SP Tools. I will try to upload updated images from the newest OTA.
I may even make a blog post with photos on my site.
Can the Onn 8 update.zip be flashed in TWRP, or must it only be flashed in spflashtool?
Thanks
UPDATE:
I tried both ways and neither works. How does one apply this update.zip? Do I need to reflash the stock recovery and apply it there?
I copied the update.zip to:
Code:
/storage/emulated/0/Android/data/com.adups.fota/files/fota
When I go to settings,system, about tablet, wireless Update, local updates, I navigate to where the update is and if I choose update.zip,: make sure the file is official, it states it may wipe your data and will reboot to recovery to install. (which I assume needs to be the stock recovery?)
I, of course do not want to do this until I hear from someone who can clarify all of this: @tek3195
Thanks
martyfender said:
Can the Onn 8 update.zip be flashed in TWRP, or must it only be flashed in spflashtool?
Thanks
UPDATE:
I tried both ways and neither works. How does one apply this update.zip? Do I need to reflash the stock recovery and apply it there?
Click to expand...
Click to collapse
To my knowledge, it has to be flashed with the stock recovery
NFSP G35 said:
To my knowledge, it has to be flashed with the stock recovery
Click to expand...
Click to collapse
Yeah, it has to be stock recovery and can be done with adb sideload or update from sdcard. I haven't tried yet but it may be able to be repacked and flashed with TWRP. I know as it sits now the compatibility.zip is of wrong format to be flashed. It's a possibility, but something that would have to be done at each update. Also, regardless of how installed will it re-lock bootloader or erase /data? Some brands do. I don't know mine was already wiped before the update.zip. Just installed it from sdcard and says success although two errors at end. loader1 & loader2 could not read misc-sd, unable to set boot part. Find out in a few if relocked.
Okay,cool. The ota when installed manually did not re-lock the bootloader.
tek3195 said:
Yeah, it has to be stock recovery and can be done with adb sideload or update from sdcard. I haven't tried yet but it may be able to be repacked and flashed with TWRP. I know as it sits now the compatibility.zip is of wrong format to be flashed. It's a possibility, but something that would have to be done at each update. Also, regardless of how installed will it re-lock bootloader or erase /data? Some brands do. I don't know mine was already wiped before the update.zip. Just installed it from sdcard and says success although two errors at end. loader1 & loader2 could not read misc-sd, unable to set boot part. Find out in a few if relocked.
Okay,cool. The ota when installed manually did not re-lock the bootloader.
Click to expand...
Click to collapse
Yes, I re-flashed the stock recovery and booted to it. I attempted to flash the update.zip from there, but there was some error that it was not and official verified file.
Keep in mind that is not what it stated, I am just relaying a very vague, poor memory version of what I saw then.
I tried to restore the just released, twrp version in fastboot in linux, but had errors, so I booted to Windows 7 and reflashed the just released version of twrp in fastboot in Windows 7 WTF? fastboot in Linux Mint Mate, has, until now, worked flawlessly.
To clarify, I could not install the ota with an unlocked bootloader and Magisk installed.
20191015 stock firmware for ONA19TB003 has been uploaded. https://www.nathanbar.net/files/android/ONA19TB003/
CaffeinePizza said:
You're welcome to reference my thread and post a link to my server with the x003 and x002 stock images. SP Flash Tools is needed.
https://forum.xda-developers.com/showpost.php?p=80574967&postcount=192
https://www.nathanbar.net/files/android
I plan on making a proper thread, perhaps this weekend, on how to backup with Wwr, and flash with SP Tools. I will try to upload updated images from the newest OTA.
I may even make a blog post with photos on my site.
Click to expand...
Click to collapse
Thanks a ton BTW, I tried to apply the October OTA on mine, and it failed because the system partition was modified (I'm sure I was doing some silly experiment)
Worse yet, the wifi stopped working for some reason... So I grabbed the backup from your server, dd'd the system image over mine, and the OTA was able to apply without a problem. Wifi started acting right again too.
I'm adding links to the OP now.
Thanks again!
NFSP G35 said:
Thanks a ton BTW, I tried to apply the October OTA on mine, and it failed because the system partition was modified (I'm sure I was doing some silly experiment)
Worse yet, the wifi stopped working for some reason... So I grabbed the backup from your server, dd'd the system image over mine, and the OTA was able to apply without a problem. Wifi started acting right again too.
I'm adding links to the OP now.
Thanks again!
Click to expand...
Click to collapse
MD5 hashes are also uploaded with DOS CRLF since I uploaded them from Windows (in the same directory as the zips on the server). Note: MD5SUM should be used only to verify that a file is not corrupt during transfer.
10"
af2e056b8b929540b3030f7dcbf07c1a stock_20190516_pie.zip
d5c6c4f8f1ea21bf18d2ee0fcb1e6335 stock_ONA19TB003_20191015.zip
8"
2244d235325b22a8a7225a736fbafaf6 stock_ONA19TB002_20190516.zip
Also, I know the 7" tablet exists now, and I have yet to purchase one. I do know, however, that it is not part of the same family. Technically (though I haven't tried it), the stock images between the 8" and 10" are exactly the same besides the ITEMS partition (items.ini).
Just got done adding boot, recovery, vbmeta, vendor and system images for the October updates on both the ONA19TB003 and ONA19TB007
Amazon has finally released FireOS 7 for the Amazon Fire 7 2019! What does this mean?
This means that developers have newer blobs and kernel to work with for Mustang roms! This could be good for development. I don't know if ggow will come back to this device, but I'll personally be trying to get LineageOS 16.0 working on here. I have mirrored the kernel on Github for convenience's sake. https://github.com/turtleletortue/android_kernel_amazon_mustang
One thing to note, do not install FireOS 7 if you want to continue using custom roms. I'm not sure, but it'll likely break amonet and leave you stuck on stock. So until we get an ok either way, just stay on the version you are on.
That being said, have a great day all of y'all! Hopefully something good comes out of this.
Karnak's Pie Source Code (mirror) here: https://github.com/R0rt1z2/android_kernel_amazon_karnak
I've downloaded the bin file, hoping it might be simple to extract the separate boot, recovery and system images from it but alas it's beyond the scope of my knowledge.
I'll try poking it later with binwalk or some other unpacking tools (I've got some amlogic tools on my laptop too) in case they provide me some hints but if anyone reading this can offer suggestions, I'd be happy to experiment
After re-reading the original post re: downgrade and root FireOS, I have bitten the bullet and am currently in process of flashing this.
I have pushed the .bin to device, renamed as .zip.
I've flashed zip, then flashed TWRP before rebooting to recovery and flashing magisk.
I am now looking at the "Amazon" logo whilst the device does its first-boot. Wish me luck!
I will report back as soon as I have more news
edit after 10 mins.
No change. Still looking at the amazon logo
30 mins - still no boot. rebooting to twrp to try again, but without magisk
45minutes - bootloop. amazon logo for a few seconds, black screen, looping indefinitely
Have flashed LOS14.1 as it's the only OS zip file I had sitting on internal storage. Waiting for it to do its first boot
No joy
In the end, the only way o could get device to boot up again was to flash fireos 6, from the original root guide
At this time, the link on the Amazon website for the current version of OS7 is wrong. It will download OS6 (6.3.1.5) instead. The correct link is below.
OS7 for Fire 7 (Mustang):
https://fireos-tablet-src.s3.amazon..._7_9th_Gen-PS7315_user_1958_0018354775684.bin
Click the link for a direct download.
MontysEvilTwin said:
At this time, the link on the Amazon website for the current version of OS7 is wrong. It will download OS6 (6.3.1.5) instead. The correct link is below.
OS7 for Fire 7 (Mustang):
https://fireos-tablet-src.s3.amazon..._7_9th_Gen-PS7315_user_1958_0018354775684.bin
Click the link for a direct download.
Click to expand...
Click to collapse
Have you had success in installing it? Rooting it, etc?
wodgey said:
Have you had success in installing it? Rooting it, etc?
Click to expand...
Click to collapse
If you have a stock tablet and copy the update.bin to '/sdcard' and reboot it can be installed by instigating a system update check. Even with a stock set up though the tablet won't boot if you flash OS6 bootloader files (TZ and LK). If you try and unlock with a modified version of amonet (keeping the OS7 bootloader files) you get a bootloop.
Unlocking and rooting may yet be possible but it is 'above my pay grade'.
MontysEvilTwin said:
If you have a stock tablet and copy the update.bin to '/sdcard' and reboot it can be installed by instigating a system update check. Even with a stock set up though the tablet won't boot if you flash OS6 bootloader files (TZ and LK). If you try and unlock with a modified version of amonet (keeping the OS7 bootloader files) you get a bootloop.
Unlocking and rooting may yet be possible but it is 'above my pay grade'.
Click to expand...
Click to collapse
Ah ok. I see. That makes sense. Thank you for explaining so concisely, yet in words I can understand
Hi everyone.
Bricked a 100011885 recently after messing around with GSIs. I can't get it to boot into anything. The preloader is still working as it gets recognized in sp flash tool and can be formatted (always with the except bootloader option) and have images written to it successfully. I've been trying to use the backup from https://forum.xda-developers.com/t/...8-surf-gen-2-100011885.4214167/#post-84291365
It seems a lot of people are confused about those files but if you open the ROM file in 7zip it contains all of the IMG files.
I couldn't find a scatter file in the Google drive folder or in the ROM file so I did a bit of searching and found this which I downloaded and adapted it to the file names from the files from ROM. Somehow along the way I ended up with a MT8168_android_scatter.img that is 32mb along the way which I couldn't find I'm the ROM when I looked again and didn't download it from anywhere myself or know how I would have made that file, no clue what it is or how to use it. Regardless, after getting the scatter file set up to the files I had from ROM I tried flashing it to my device and I am now stuck on the preloader.
Foolishly on the first flash attempt I did have preloader selected but it got stuck on 0% and eventually failed. After that I could still get it to recognize the preloader and successfully flash the IMG files but I'm unable to get past the preloader. I can still write IMG files to it and format it using so flash tool but I'm just stuck at a blank screen. No backlight or anything.. Any tips on how I could revive this tablet or is it dead?
Could I have the scatter file you used? I have a 8" 100003561 and It's stuck in preloader too
Mattinthahack said:
Could I have the scatter file you used? I have a 8" 100003561 and It's stuck in preloader too
Click to expand...
Click to collapse
Sorry. Meant to link it in my op. It was from this post. The scatter file was from https://forum.xda-developers.com/t/help-needed-onn-8-gen-2-100011885-no-boot.4246787/#post-84949449
Although since then someone has dumped a complete stock rom which includes a scatter file that is complete. It can be found here https://forum.xda-developers.com/t/...8-surf-gen-2-100011885.4214167/#post-86592343
I've tried to use that instead but I'm still having the same result.
Do you happen to know where I could find the stock rom for the 1st Gen 8"? 100003561?
Mattinthahack said:
Do you happen to know where I could find the stock rom for the 1st Gen 8"? 100003561?
Click to expand...
Click to collapse
I found a post on the thread for stock ROMs that has a link to a Google drive folder with a couple backups in it. I hope they help
[STOCK] Stock Backups/Images/OTAs
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images. I have access to a 10.1 with keyboard...
forum.xda-developers.com
Still doesn't flash. I don't understand see the same guy that posted that had posted factory firmware and the tablet was booting right. I flashed it successfully with his factory firmware but the post you linked me said do not use it cause it will brick. I didn't know that. Now it's stuck in preloader won't do anything else, won't flash nothing. Just recognizes the tablet. I'm unsure what to do don't know if I'm using wrong sp flash tools or what. Should I pop the tablet open and disconnect the battery I don't know at this point never have flashed incorrect firmware before.
The only reason I flashed the tablet is cause the touch wouldn't work.
I'm in that situation myself which is why I made this thread to get help. I can still use the preloader and flash the rom using sp flash tools but I can't get it to actually boot after that. I am stuck on the preloader.
Did you ever figure this out? I still haven't found anything out on it but possibly pulling the images from the 10.1 inch which has the same SoC do you think this would work?
Sorry but I haven't had any results either. I also tried the 10.1 rom and had the same result as any of the other backups I've tried. I'm going to keep trying to figure this out when I have the time and if I do fix my device I'll definitely update this thread with how I did it.