Related
So here's the story...
I had 6.2.1 rooted until 6.2.2 came out.. Left it stock for a while. Decided to re-root tonight, worked like a charm with Burrito Root 3.
Then I decided to take it a step further... I wanted to install CM9. So I went about my business and installed TWRP 2.0 and copied the files over to the SD card no problem.
Here's where the problem starts: I wiped the Kindle Fire. My stock backup is gone, my CM9 image is gone, as is everything else on the SD card, meaning I can no longer boot into an OS. Neither adb nor fastboot recognize the KF on either Mac OS or Windows. The Kindle Fire Utility doesn't work either.
When I let it boot, it sticks at the static "Kindle Fire" logo and does nothing beyond that.
Using Mount USB Storage in TWRP doesn't work either.
I've been searching for an answer all night, but everyone seems to go through adb.. Well, mine doesn't work (it did.. after something happened it just stopped)
So here's the question: How can I go about fixing this, if at all possible? It's out of warranty (Best Buy only has a 14 day warranty as I learned like three hours ago...) If this thing had a removable memory stick it would've been fixed four hours ago
Thank you for any help
would try firekit:
http://forum.xda-developers.com/showthread.php?t=1430038
Doesn't seem to work. No matter which command I try it always says "< waiting for device >" or something equally as saddening.
iFargle said:
So here's the story...
I had 6.2.1 rooted until 6.2.2 came out.. Left it stock for a while. Decided to re-root tonight, worked like a charm with Burrito Root 3.
Then I decided to take it a step further... I wanted to install CM9. So I went about my business and installed TWRP 2.0 and copied the files over to the SD card no problem.
Here's where the problem starts: I wiped the Kindle Fire. My stock backup is gone, my CM9 image is gone, as is everything else on the SD card, meaning I can no longer boot into an OS. Neither adb nor fastboot recognize the KF on either Mac OS or Windows. The Kindle Fire Utility doesn't work either.
When I let it boot, it sticks at the static "Kindle Fire" logo and does nothing beyond that.
Using Mount USB Storage in TWRP doesn't work either.
I've been searching for an answer all night, but everyone seems to go through adb.. Well, mine doesn't work (it did.. after something happened it just stopped)
So here's the question: How can I go about fixing this, if at all possible? It's out of warranty (Best Buy only has a 14 day warranty as I learned like three hours ago...) If this thing had a removable memory stick it would've been fixed four hours ago
Thank you for any help
Click to expand...
Click to collapse
Of course it is possible, you just need to make a special Factory Cable.
http://forum.xda-developers.com/showthread.php?t=1392693
Thank goodness I have an extra cable. I'm.. fairly proficient with a soldering iron as well.
I will begin this process and post here when finished.
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
drk.hd said:
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
Click to expand...
Click to collapse
There is a way to do this with adb... I just do not know the proper commands. Sorry
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
sengwall said:
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
Click to expand...
Click to collapse
No, I don't think it does, but I'd rather not take the chance.
drk.hd said:
No, I don't think it does, but I'd rather not take the chance.
Click to expand...
Click to collapse
YES! It absolutely does. The second the device was rooted it broke warranty.
Sent from my myTouch_4G_Slide using XDA App
The same thing actually happened to me earlier today. I was just browsing some sites on the ICS rom when it just stopped responding. I couldn't get it to recognize any touches even after a bunch of reboots, so I just figured it to be some bug that hadn't been squashed yet. When I dropped down to recovery and saw the same issue, I knew I had a real problem.
Hoping against hope, I tried both CWMR and TWRP on it and got no results. Like you, I figured it would have to go back to Amazon, so I started searching for a way to get it back to stock... nothing obvious jumped out at me because everything is written with access to recovery in mind... which doesn't help.
So, I started reading about adb and going through the built-in help. As I was familiarizing myself with some basic adb commands and options, I left TWRP open in front of me. I don't know how long I had it that way when I mindlessly tapped on the screen and thought I saw it flicker. Yes! I had pressed the Wipe button and it had taken me to that section. It's been working fine ever since.
I'm not claiming I did anything and I don't have a how-to on how to fix it, but it couldn't hurt to just leave the thing running in recovery for a while and see if the touchscreen comes back to life for you too.
Still, I'd love to see someone with more adb knowledge provide a simple tutorial on how to get it back to stock without access to recovery. I'm sure it would be helpful to someone in the future... maybe even me if the same problem comes up again.
Best of luck to you.
Just ignore my comment
Sent from my Amazon Kindle Fire using Tapatalk
If your on the rooted stock rom you could always wait until Amazon pushing the next OTA
You will have to make a fastboot image and flash that with fastboot. But before you create the image, you will have to create all the appropriate symlinks. Then you run...
Code:
make_ext4fs -l 512m -a system -s /path/to/fastboot_system.img /path/to/system_folder
That will create the fastboot image. Then when FFF gives you fastboot access, you run...
Code:
fastboot flash system fastboot_system.img
You will also need a fastboot image for recovery and the bootloader.
Isn't there any easy way like with my desire, simple ruu.
Or hasn't anyone created these images to flash. I also need to get back to stock everything and send it to amazon, my wifi gets error after some period of time and some times when screen goes off, try'd 3 roms and stock.
There is a way to tell the device to install /sdcard/update.zip via shell commands. I forget what they are tho. Something about the extendedcommands. If I have time tomorrow I'll look it up.
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
b63 said:
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
Click to expand...
Click to collapse
Thanks for the link. I'm back on this thread because I think my Kindle Fire touchscreen is now dead for good. However, those instructions do not work as-is because you need to press a button on the screen to tell the Kindle Fire to allow the host to mount it as a USB Mass Storage device. Although those instructions don't get you all the way there, I was able to use the core idea to get my Kindle Fire back to stock. So, many thanks for pointing me in the right direction.
On top of the touchscreen not working, I ended up partially bricking the device trying to find a way to flash it back to stock, so I had also posted in the Unbricking thread. I posted my solution there....
http://forum.xda-developers.com/showpost.php?p=23226260&postcount=701
Odds are, if you have a device that is booting correctly, you will be able to ignore steps 3 and 4 and get it booting back to stock. I do have a couple of other suggestions... Leave your USB cable hooked up to the Kindle Fire as it boots into stock for the first time. This is the only time that it will automatically mount the /sdcard to your computer and you will have a chance to reclaim (and delete) all the files stored there. You can also do something like 'adb pull /sdcard C:\sdcard' before you flash. Also, depending on what ROM and apps you were using before starting the process, you might want to delete your user data and reset the device to factory defaults. You can do this with 'fastboot erase userdata' and the next time you start the device, you'll get a warning that it's about to reset. Hit the power button and you should have a clean, fresh from the factory Kindle fire... albeit with a broken touchscreen. Good luck!
After several failed attempts to follow this guide (no offense to posters; I appreciate your contributions), I found this to be the simplest method.
http://stackoverflow.com/questions/10817721/wipe-data-factory-reset-through-adb
Download stock update, then it's basic procedure in adb:
adb push C:/update.zip /sdcard/update.zip
adb shell
recovery --wipe_data
After reboot, go back into to adb shell and do "recovery--update_package=/sdcard/update.zip"
Factory reset, etc. and you're good to go.
Hello, so this is my first time trying to root an android device, and I think I messed up. I watched a tutorial on youtube on how to do it and successfully installed superuser and twrp from a batch file ( I had to install adb drivers first ). I wasn't really sure I did it in the correct steps, so I wanted to revert back to the stock os. I booted into twrp and wiped the data ( cache, system, etc) from twrp. I then mounted it and transfered the kindle fire update 6.3.1 to my KF. I used the option on twrp to revert back to stock using the newly transferred zip. It ran for awhile then prompted me to click reboot. So I did. And this is where it gets tricky
After the reboot, all I see is the boot screen displaying "kindle fire." It never booted and lasted like this for hours. I tried to boot into twrp but I think it got deleted. I googled the problem and found it was in some sort of fastboot loop. I tried many fixes, using adb and other fastboot commands. Every time I tried anything, all I got was "waiting for device." Also, I couldn't use adb shell because it said system/bin/sh was not found. I went to my computer and found that the kindle fire no longer showed up as a removable device, but it showed up in device manager as adb composite interface under android phone. I thought that somehow all of my system files got deleted and thats why it says system/bin/sh not found. I tried to use the adb push command to manually send the update.zip to the KF but it is no longer a mounted drive, so there is nowhere to send it to. I'm at a loss here, Ive tried numerous utilities such as KFU, firekit, unbrick utility. I just need to figure out a way to remount the KF and copy over the folder "system" in the update.zip. If anyone could help me that would be great, as I have been trying to fix this for three days now.:fingers-crossed:
Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.
tazmanhawaii said:
Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.
Click to expand...
Click to collapse
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.
Marblesnake said:
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.
Click to expand...
Click to collapse
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.
soupmagnet said:
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.
Click to expand...
Click to collapse
Thanks for the help. Yeah, I tried the firekit method but didn't use the shorting trick. I have scoured the internet for information and tricks and it seems like these are my last two options before I throw this thing out the window. I have seen your posts in other threads and you have been a great help throughout this ordeal.
factory cable
thank you for this information. I am in the same predicament. I am purchasing a factory cable from Amazon $1.27.
It is sold by Earlybirdsavings and is a 3ft micro USB factory cable for kindle fire and Motorola Xoom.
thank you for all the helpful information!
Hi there,
i got a little question prior rooting my Shield TV 2017 pro.
I read a bit about the L1 +L2 Widivine keys on the shield so my question is, does rooting the shield has any influence with the keys, for example will Amazon + Netflix 4k stream work after?
The second question is, is twrp on the shield able to create a backup of thoose partitions in case the hdd bricks or something went wrong during flashing?
EDIT:
In case anyone needs the answer, too just read the two following posts by lavero.burgos and mr-tee and some warnings from ichijoe in 3rd, which are very detailed and helpfull
Thanks in advance
JeckyllHavok
Hello, the answer is NO, rooting your device will NOT mess with your keys nor damage them, simply because as systemless root it only safely modify boot.img and the rest goes to the data partition, so it won't touch sensitive data. The recommended method is to install SuperSU which is developed by Chainfire (the guy know what he does, he's an excellent dev).
Netflix and Amazon work for me with root, but yes there are services out there with their own apps that don't allow root. If they detect root you won't be able to play their content (IMO bad practice, i would change service if that is the case).
About TWRP, no it won't allow you to backup the relevant partitions because TWRP handle standard partitions that every Android device has, so unless someone makes a custom TWRP to include that the only way i know off is running dd comands from linux distro to backup the needed partition(s). I have done it myself in the past (many years ago) with the old Nook Tablet.
I made videos about that but you first need to know the partition block name, for example mmcblk0p8, once you have that info you can go to YouTube and search how to backup partitions with dd command and also check the following playlist where you can find the videos i made long ago:
Community Forums: http://www.youtube.com/playlist?list=PL216837379418927A
I'm very curious why many 500 PRO users have bricked their devices. What you really need to be careful with is the bootloader (blob file), don't mess with it. You can no longer downgrade bootloader from Nougat or newer to MM or older and in case you want to upgrade your hdd with a ssd and clone it then you also have to prepare to damage your device in the way.
I only have the 16GB 2015 model but would be great if someone post a screenshot of the famous backup a user has posted for the 500GB PRO, i would like to see what is inside.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
First of all I would say, try root first, see if it affects the apps you want to use.
Don't FLASH TWRP, yet tell fastboot to boot the recovery image. But even flashing it won't harm anything. There are stock ROMs on the nvidia developer website, with the original recovery image, so you can always flash back the stock recovery, but well, not flashing a different recovery will save some effort and time.
If you have installed supersu you'll be able to fully UNROOT inside the supersu app. So, first try it out, without changing any system files, see if the apps you use work, then you could consider going further with customizations. But you can always return to stock, just don't mess around with files outside the system or vendor folder. And especially not the bootloader (blob). But there is a blob file inside the official stock ROM from nvidia.
One warning: DON"T use the flash-all.bat file included in the nvidia ROM.. use the commands manually...!!
Thanks for the detailes answers, yeah i know about dd commands, and fastboot or adb, just wanted to be sure that nothing strange happens.
Cause i never got any Widevine L1 certified device
So tonight rooting a shield...
To answer some of your questions.
Rooting will NOT mess with your Keys directly. But, sooner or later nVIDIA are going to start lobbing Updates again. And, if you have a setup which involves say a 4k (2160p) TV*. Then you CAN NOT just simply load up TWRP from some location. To do your business (i.e. rooting it), then exit back out and leave the Shield otherwise stock. (e.g. you never actually replaced 3e (or whatever nVidia calles the Recovery, with TWRP.)
This does not mean that you can not install (i.e. replace) 3e, with TWRP, and then just boot into that. That, would work perfectly, and that's what got me into the deep Dodoo.
Again whatever you do DO NOT replace your Recover with TWRP! Sooner or latter this will bite you in the 455! The moment when nVIDIA decide to push out an update, and sends your Device into a bootloop. Which will make you want to downgrade, and then hardbrick the Device.
But, beyond all that, there are plenty of other good reasons to make that backup of the original SSHD. Beyond having a simple backup of just the Keys. As these Drives, like all Drives eventually fail.
* I gather those with them old fangled 720p, 1080p Sets out there will NOT have this problem. Which I can confirm, as I can load up TWRP just fine over the fastboot command line on my Old Man's 1080p Samsung. Alas back home it's just the One 4k Set. And that will not work. Unless loaded directly on the Device.
Ichijoe said:
To answer some of your questions.
Rooting will NOT mess with your Keys directly. But, sooner or later nVIDIA are going to start lobbing Updates again. And, if you have a setup which involves say a 4k (2160p) TV*. Then you CAN NOT just simply load up TWRP from some location. To do your business (i.e. rooting it), then exit back out and leave the Shield otherwise stock. (e.g. you never actually replaced 3e (or whatever nVidia calles the Recovery, with TWRP.)
This does not mean that you can not install (i.e. replace) 3e, with TWRP, and then just boot into that. That, would work perfectly, and that's what got me into the deep Dodoo.
Again whatever you do DO NOT replace your Recover with TWRP! Sooner or latter this will bite you in the 455! The moment when nVIDIA decide to push out an update, and sends your Device into a bootloop. Which will make you want to downgrade, and then hardbrick the Device.
But, beyond all that, there are plenty of other good reasons to make that backup of the original SSHD. Beyond having a simple backup of just the Keys. As these Drives, like all Drives eventually fail.
* I gather those with them old fangled 720p, 1080p Sets out there will NOT have this problem. Which I can confirm, as I can load up TWRP just fine over the fastboot command line on my Old Man's 1080p Samsung. Alas back home it's just the One 4k Set. And that will not work. Unless loaded directly on the Device.
Click to expand...
Click to collapse
Thanks for the hints, the way i would root the shield would be:
-Unlock Bootloader
-fastboot boot twrp.img
-flash the su stuff
I got no need atm to replace recovery, so i keep it stock, just want root for droid mote, launcher and maybe xposed, and a dd backup of the whole shield hdd
JeckyllHavok said:
Thanks for the hints, the way i would root the shield would be:
-Unlock Bootloader
-fastboot boot twrp.img
-flash the su stuff
I got no need atm to replace recovery, so i keep it stock, just want root for droid mote, launcher and maybe xposed, and a dd backup of the whole shield hdd
Click to expand...
Click to collapse
As long as you do NOT replace the Recovery with TRWP. But, just call it up though Fastboot ~boot recovery <path to TWRP> then you should be nearly 100% safe.
But, having learnt my own lessens I would personally recommend leaving the Shield alone I'm not sure what good Rooting it actually has. And I'm a very big fan of AdAway, but AdAway just doesn't seem to do jack on the Shield. And, though you have to root to add Unofficial channels to Plex. At the end of the day. Those Channels have like for like Kodi Addons.
But again as long as you don't flash (replace) the stock Recovery with TWRP, you should be ok. Assuming an Update rolls along, (as they do), you should just be able to load up TWRP, like before, and flash SuperSU, and then go on with your business.
JeckyllHavok said:
Thanks for the hints, the way i would root the shield would be:
-Unlock Bootloader
-fastboot boot twrp.img
-flash the su stuff
I got no need atm to replace recovery, so i keep it stock, just want root for droid mote, launcher and maybe xposed, and a dd backup of the whole shield hdd
Click to expand...
Click to collapse
Those steps are correct, just know that in a 500gb PRO model unlocking the device will securely wipe your device and that task takes around 2 hours to complete in that specific model.
You can also use adb to sideload SuperSU package while in TWRP (Advanced >> ADB sideload):
adb sideload supersu_package_name.zip
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Alrighty... So I'm in the weeds here after going through three variants of the Samsung JPop (Which have bootloaders locked up like Fort Knox) and decided today to break down and dish out $59 for this bargain device. First thing I did upon getting it home was fastbooting it, and was able to unlock the bootloader with no issue. (So easy, a caveman could do it)
I've read just about every thread in here and though there seems to be TWRP support for quite a few models of the Onn tablets, I didn't see this one in here. Right now I have a throwaway laptop which is installing ubuntu for building TWRP for this device. Now, I have NEVER built TWRP. But I have plenty of free time, ambition, and am willing to learn. I have the basic guide to building TWRP open elsewhere. I will take whatever help I can get on doing this, big or small. Building a basic TWRP image should be easy enough, but the guides don't really go into device specific details (as expected), so this is where I could use some veteran help.
Device Specs:
Model: 100026191
Out-of-the-box Android Version: 11
Display: 7" 1024 x 600 Resolution
Processor: 2.0 GHz Quad-core CPU
RAM: 2GB
Cameras: 2MP front & back
USB: Type-C
Ubuntu just finished, and I am getting the build environment ready as we speak. Will keep this thread updated with progress and hickups that may occur along the way. Wish this noob some luck!!!!
Alrighty, so here's what I've been able to come up with as far as more detailed system information. Sorry for the late post, had trouble getting wifi working on ubuntu but got it going.
I suspected a MediaTek CPU and was eager to do a readback with SP Flash Tool, but as you can tell from the provided screenshots, it's actually a Cortex-A53 CPU. my goal here is to some how pull my stock recovery out of here. I thought about dd'ing it but someone in another thread advised against it. Does Onn have stock firmwares hidden away in the internet somewhere? Or is there another tool I can use to pull recovery?
Good evening guys and gals. New day, new opportunity. So i'm still stuck at pulling off boot and recovery from this tablet. I used
Code:
/adb shell cat /proc/mtd
to no avail. Permission denied just like with dd.
Today, I got the MTK droid tool and hooked the tablet to it and got these results. Still no scatter file, still no progress on pulling these partitions. (I apologize for my dumbness yesterday, this device is in fact MediaTek)
Alright. Eighty of you have clicked in this thread, zero of you show any motivation to do anything to contribute. You guys must hate this tablet because I went through this entire board, and each thread that even mentioned this model were left with no response. I just want the boot and recovery partitions off of the stock tablet. I am willing to do the rest. I said before, I'd take any help I could get but since this device is "so" insignificant, I'm not trying anything else on it.
I don't know if you guys dodge this device because it's Android 11, or what. But the least you veterans could do is either tell us it's not going to happen (given that you tried), or give us some other ideas we could try. Hell I'll paypal you enough for you to have the device in your hands in order to help. But that's where I stand. Moderator can lock this thread if he wishes. There's nothing else I can do for this device at the moment.
guess i'll return it to walmart
was hoping to root it easily with twrp
just gonna go grab the 8' if this is how it ended for the 7'
thanks for the help though!
I need a firmware for the 100026191
TWRPN00b said:
Alright. Eighty of you have clicked in this thread, zero of you show any motivation to do anything to contribute. You guys must hate this tablet because I went through this entire board, and each thread that even mentioned this model were left with no response. I just want the boot and recovery partitions off of the stock tablet. I am willing to do the rest. I said before, I'd take any help I could get but since this device is "so" insignificant, I'm not trying anything else on it.
I don't know if you guys dodge this device because it's Android 11, or what. But the least you veterans could do is either tell us it's not going to happen (given that you tried), or give us some other ideas we could try. Hell I'll paypal you enough for you to have the device in your hands in order to help. But that's where I stand. Moderator can lock this thread if he wishes. There's nothing else I can do for this device at the moment.
Click to expand...
Click to collapse
I have the boot and recovery images if you want them.
I unfortunately accidentally deleted the original boot image, but I have a magisk patched image still present.
I can walk you through the process of extracting the original if you would prefer that, it's quite simple, I just don't feel like buying a second Onn tablet at the moment.
Just note that if you want to extract the original boot image, do NOT flash the Magisk image, it will permanently erase the original boot image. There is another way, I can walk you through it.
PseudoDistant said:
I have the boot and recovery images if you want them.
I unfortunately accidentally deleted the original boot image, but I have a magisk patched image still present.
I can walk you through the process of extracting the original if you would prefer that, it's quite simple, I just don't feel like buying a second Onn tablet at the moment.
Click to expand...
Click to collapse
I oicked up one of the gen3 tablets. Do you think your way of pulling the boot image would work on it?
alarmdude9 said:
I oicked up one of the gen3 tablets. Do you think your way of pulling the boot image would work on it?
Click to expand...
Click to collapse
My way of pulling the images should work on any Android device that ships Android 8.0+, however if you got it brand new, don't update it.
Factory reset it if it downloaded an update, then disable OTA updates before enabling Wi-Fi.
You can run `adb logcat` while the update is downloading to find out where to download the OTA, and dump the boot partition from that.
From there, if you install Magisk, you can dump the recovery partition with `adb shell`.
PseudoDistant said:
Factory reset it if it downloaded an update, then disable OTA updates before enabling Wi-Fi.
You can run `adb logcat` while the update is downloading to find out where to download the OTA, and dump the boot partition from that.
From there, if you install Magisk, you can dump the recovery partition with `adb shell`.
Click to expand...
Click to collapse
Ok I will have to reset it then go from there. Do you have a guide on how to pull the image?
alarmdude9 said:
Ok I will have to reset it then go from there. Do you have a guide on how to pull the image?
Click to expand...
Click to collapse
When doing first time setup, don't connect to Wi-Fi.
Enable Developer Settings
Disable OTA Updates
Enable USB Debugging
Connect to Wi-Fi
Connect the device to your computer
Run `adb logcat > ota.txt`
Reenable OTA Updates
Go to Software Updates and start downloading the Android 12 update (If it's not the Android 12 update, disable OTA updates again after this one finishes installing, then try logcat again after rebooting)
Search for a link that looks like `https://android.googleapis.com/packages/ota-api/package/827ee737174e0e8f761bcaeb12738221a924c810.zip` in the logcat.
Put the update link in your browser, and download the zip file.
Extract the zip file
There's your boot.img, very conveniently.
The update link I have provided is for the 100074181, the 3rd gen Onn 7, if you happen to have that one then go ahead and just use my link.
Though update to Android 12 before actually using that boot.img with Magisk, it won't work with Android 11.
After you're done with that, and you're rooted.
`adb shell`
`su`
`dd if=/dev/block/by-name/recovery of=/storage/emulated/0/recovery.img`
Then connect your tablet to your PC and enable file transfer in USB settings, then just pull recovery.img out of your tablet and you have the recovery image.
PseudoDistant said:
When doing first time setup, don't connect to Wi-Fi.
Enable Developer Settings
Disable OTA Updates
Enable USB Debugging
Connect to Wi-Fi
Connect the device to your computer
Run `adb logcat > ota.txt`
Reenable OTA Updates
Go to Software Updates and start downloading the Android 12 update (If it's not the Android 12 update, disable OTA updates again after this one finishes installing, then try logcat again after rebooting)
Search for a link that looks like `https://android.googleapis.com/packages/ota-api/package/827ee737174e0e8f761bcaeb12738221a924c810.zip` in the logcat.
Put the update link in your browser, and download the zip file.
Extract the zip file
There's your boot.img, very conveniently.
The update link I have provided is for the 100074181, the 3rd gen Onn 7, if you happen to have that one then go ahead and just use my link.
Though update to Android 12 before actually using that boot.img with Magisk, it won't work with Android 11.
Click to expand...
Click to collapse
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!
alarmdude9 said:
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!
Click to expand...
Click to collapse
Update to Android 12 before using Magisk, just in case.
alarmdude9 said:
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!
Click to expand...
Click to collapse
Could you share the ota? This is the same model I'm using but its bricked rn
MoistSpoon said:
Could you share the ota? This is the same model I'm using but its bricked rn
Click to expand...
Click to collapse
I will look for it. Saved it to a USB drive and of course it decided to be stupid and it is repairing now. Slow going but as soon as it gets done I will look to see if it survived and if so I will get it uploaded.
MoistSpoon said:
Could you share the ota? This is the same model I'm using but its bricked rn
Click to expand...
Click to collapse
Sorry just noticed that the file that PseudoDistant posted is still good. I used this one....
https://forum.xda-developers.com/attachments/magisk_patched-25200_fvdeh-img.5794395/