Related
Hello XDA,
I just purchased a new Acer Iconia One 8 B1-850 and was wondering if I could root it.
I see many posts on B1-810 and similar, but nothing for the B1-850.
CoreyGamingTV said:
Hello XDA,
I just purchased a new Acer Iconia One 8 B1-850 and was wondering if I could root it.
I see many posts on B1-810 and similar, but nothing for the B1-850.
Click to expand...
Click to collapse
same here
i want to root to enable the multi user option by updating the build.prop file, i've been able to connect with ADB but the device isn't visible in windows or mac (tried both) when you reboot into boot loader, in fact it doesn't appear to boot into boot loader it just seems to power off (when using ADB reboot command or choosing boot loader from the recovery menu) so i wonder if its locked out somehow??
Need it too. Did anyone find a way to root B1-850?
Thanks!
dtalas said:
Need it too. Did anyone find a way to root B1-850?
Thanks!
Click to expand...
Click to collapse
I too just purchased a B1-850 tablet, but I've figured out how to root it. Really quite simple. Just use Kingroot:
1.) Navigate to https://kingroot.net/ from your tablet
2.) Download the APK for android
3.) Install said APK (this requires you to have allowed installation from unkown sources in the "Security" panel of the settings menu)
4.) Load up the app and follow its instructions
5.) Reboot and try it out
For good measure, I would also unlock the "Developer Options" panel and allow USB debugging (adb access) and such; I did this before proceeding. You'll have to search for instructions on that yourself, its well documented.
This all worked for me this morning! Really looking forward to unlocking the potential of this cheapy tablet.
Kingroot worked first try, just swap their super user program with supersu. I am having trouble installing the xposed framework though if anyone has any tips.
I was able to root, now I need to install a custom recovery. CWM says this model is not in the supported list. Has anyone been able to install a recovery? I need NANDROID backup functionality.
I made a thread walking you through how to do it on this tablet in the guides area but just use flash fire for recovery and xposed install
Did the B1-850 hardware updated in anyway? I was able to root it in June 2016, but after a screen repair and factory reset and fresh rom from acer, king root and all others can't work. I'm stuck without any root options. Any idea?
Same here
Dylfaus said:
Did the B1-850 hardware updated in anyway? I was able to root it in June 2016, but after a screen repair and factory reset and fresh rom from acer, king root and all others can't work. I'm stuck without any root options. Any idea?
Click to expand...
Click to collapse
There was recently new firmware released for this tablet (08/24/16, Build #: AV0L0.RV09RC04.WW.GEN1), and a handful of updates (08/25/16, 08/26/16) from Acer. I have this same tablet, and I'm unable to root after flashing to the firmware released on the 24th, and latest firmware (Build #: AV0L0.RV0BRC02.WW.GEN1) as well. Hopefully someone can find a fix, as the few different methods I've attempted simply will not work with the latest firmware from Acer.
On KingRoot Please click submit search if enough people do they will find a root until then just hold tight.
jared407 said:
On KingRoot Please click submit search if enough people do they will find a root until then just hold tight.
Click to expand...
Click to collapse
I have done this a bunch, sadly still no love. It's annoying me not being able to root a relatively cheaper tablet, as these tend to get rooted first since they get in more people's hands faster. Oh well, just have to have patience.
Thanks, I was having problems, two different rooters failed and I wondered if it was the recent software update! The image version on my B1-850 is the same as you have quoted! Please post if you find a solution, some apps that need deleting are annoying.
---------- Post added at 06:23 PM ---------- Previous post was at 06:13 PM ----------
random4t4x14 said:
There was recently new firmware released for this tablet (08/24/16, Build #: AV0L0.RV09RC04.WW.GEN1), and a handful of updates (08/25/16, 08/26/16) from Acer. I have this same tablet, and I'm unable to root after flashing to the firmware released on the 24th, and latest firmware (Build #: AV0L0.RV0BRC02.WW.GEN1) as well. Hopefully someone can find a fix, as the few different methods I've attempted simply will not work with the latest firmware from Acer.
Click to expand...
Click to collapse
I was having a problem rooting my device and wondered if it was the recent software update, and my image version is as you have quoted! I f you manage to root your device please post!
knockout350 said:
I made a thread walking you through how to do it on this tablet in the guides area but just use flash fire for recovery and xposed install
Click to expand...
Click to collapse
Which recovery do you install with flash fire; I don't see a link to it in your other thread?
Success!
The latest release of KingRoot is able to root the latest firmware for this tablet. I saw there was a new release of KingRoot back on the 23rd, and it's working as it should. I grabbed the working version here -> http://forum.xda-developers.com/devdb/project/dl/?id=21707
hi guys. any idea how to recover b1-850 from bootloop?
I no its a little late but i rooted mine with the kingoroot one click root apk. Ive installed xposed framework and customized like crazy everything from fonts to boot animation. Cant find a custom recovery tho.
I cannot root it with any of the tools I have tried (Kingo ROOT, KingRoot, etc). Anyone know any method that works?
Acer B1-850. Is this device even rootable?
This device has made an idiot of me. If I can be of any assistance finding a root exploit for this device let me know. I will gladly write a detailed procedure of the process. I made the mistake of assuming since it was an entry level, inexpensive device, the path to root would be simple. Three months later none of the common "one-click" programs has found an exploit. I have a copy of stock rom for recovery so testing is not a problem for me. It's a matter of pride at this point. So much so I found one on sale for $60 and bought it just for this purpose. I have followed every link I can find associated with this device to a dead end. Any help will be appreciated.
pdnorman said:
This device has made an idiot of me. If I can be of any assistance finding a root exploit for this device let me know. I will gladly write a detailed procedure of the process. I made the mistake of assuming since it was an entry level, inexpensive device, the path to root would be simple. Three months later none of the common "one-click" programs has found an exploit. I have a copy of stock rom for recovery so testing is not a problem for me. It's a matter of pride at this point. So much so I found one on sale for $60 and bought it just for this purpose. I have followed every link I can find associated with this device to a dead end. Any help will be appreciated.
Click to expand...
Click to collapse
Same here, still no root for me. Usually these cheapo tablets are not as locked down.
Still waiting!?
I have given up getting assistance from xda on this device. Its as political here as anywhere else. I don't drive a Samsung so nobody wants to help with root. I've heard every excuse from locked bootloader (unlockable in dev options) to what one dev actually told me,"There's little interest in spending energy on an inexpensive device." I understand, but why misrepresent the site by implying all android devices are treated the same? Hell on the Iconia One 8 thread, it says that the B1-850 does not have a MTK SoC, but instead has an Intel Atom chip. Then they send you to another thread where, of course, there is no B1-850 listed! That's because it uses a MTK8163 SoC. In both tablets.
Hello and thanks for reading!
I have a Kindle Fire 5th Gen that was just given to me. I'd like to get rid of the Amazon OS and install anything (I'll take CM or whatever). It is currently running 5.1.2 yet KingRoot v4.9.2 says it is 5.1.1.
I've tried KingRoot a few times (apparently you need root to get TWRP going) and nothing happens - it keeps failing.
I've gone through some RootJunky videos but those aren't updated for 5.1.2 via Windows.
I'm at a loss of what to do next. This video says that installing an old version of Fire OS will brick your Kindle.
All of these different threads have me confused.
My questions are:
I understand that TWRP doesn't work on 5.1.2, so how do I get to a different version of Fire OS? And how do I disable OTA's? Turn off Wifi?
When I get to a different version of Fire OS, will RootJunky's tools work like in his videos?
I apologize if this is already answered in another thread as I can't find it and am new to the Kindle Fire.
I'd like to be able to use it for my school books next semester instead of having to bring the big effin things back and forth. For $50 bucks (retail), this seems like a steal to get a vanilla version of Android running on it!
Thanks in advance!
Pcprik said:
Hello and thanks for reading!
I have a Kindle Fire 5th Gen that was just given to me. I'd like to get rid of the Amazon OS and install anything (I'll take CM or whatever). It is currently running 5.1.2 yet KingRoot v4.9.2 says it is 5.1.1.
I've tried KingRoot a few times (apparently you need root to get TWRP going) and nothing happens - it keeps failing.
I've gone through some RootJunky videos but those aren't updated for 5.1.2 via Windows.
I'm at a loss of what to do next. This video says that installing an old version of Fire OS will brick your Kindle.
All of these different threads have me confused.
My questions are:
I understand that TWRP doesn't work on 5.1.2, so how do I get to a different version of Fire OS? And how do I disable OTA's? Turn off Wifi?
When I get to a different version of Fire OS, will RootJunky's tools work like in his videos?
I apologize if this is already answered in another thread as I can't find it and am new to the Kindle Fire.
I'd like to be able to use it for my school books next semester instead of having to bring the big effin things back and forth. For $50 bucks (retail), this seems like a steal to get a vanilla version of Android running on it!
Thanks in advance!
Click to expand...
Click to collapse
- although your device shows 5.1.2 it is likely running 5.1.2.1 which can not be rooted at present
- you need to reload (sideload) 'pure' 5.1.2 via the stock recovery menu; there are instructions and videos posted elsewhere in this forum
- once on 5.1.2 use the SuperTool to root, block OTA, swap out Kinguser for SuperSU and obtain FlashFire which is used to install custom roms
- TWRP is not an option for your device at this time (nor is it likely in the near future)
- suggest looking through the index for relevant material (link below)
- keep reading; you'll get the hang of it
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Davey126 said:
- although your device shows 5.1.2 it is likely running 5.1.2.1 which can not be rooted at present
- you need to reload (sideload) 'pure' 5.1.2 via the stock recovery menu; there are instructions and videos posted elsewhere in this forum
- once on 5.1.2 use the SuperTool to root, block OTA, swap out Kinguser for SuperSU and obtain FlashFire which is used to install custom roms
- TWRP is not an option for your device at this time (nor is it likely in the near future)
- suggest looking through the index for relevant material (link below)
- keep reading; you'll get the hang of it
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Click to expand...
Click to collapse
Thanks!
I may have hit a 'small' snag though. When I put 5.1.2 from the Index page on, Kingroot still didn't work so I put the next oldest version on (5.1.1 I believe). Now it won't startup and just has a black screen - I believe I forgot to select wipe cache before restarting. When I plug it into my Surface, Device Manager keeps making noises and I have installed the MTK VCOM drivers. I'm going to try to put 5.1.2.1 back on but I'm wondering if this thing is actually bricked? According to this thread it's possible to 'unbrick' it but if it doesn't turn on, how does it get into recovery mode?! Perhaps it's in recovery mode now with the blank screen? When I do 'adb devices', nothing shows up so I'm guessing it's not connected? Even doing 'adb sideload <filename>' shows no devices connected.
Thanks again!
Pcprik said:
Thanks!
I may have hit a 'small' snag though. When I put 5.1.2 from the Index page on, Kingroot still didn't work so I put the next oldest version on (5.1.1 I believe). Now it won't startup and just has a black screen - I believe I forgot to select wipe cache before restarting. When I plug it into my Surface, Device Manager keeps making noises and I have installed the MTK VCOM drivers. I'm going to try to put 5.1.2.1 back on but I'm wondering if this thing is actually bricked? According to this thread it's possible to 'unbrick' it but if it doesn't turn on, how does it get into recovery mode?! Perhaps it's in recovery mode now with the blank screen? When I do 'adb devices', nothing shows up so I'm guessing it's not connected? Even doing 'adb sideload <filename>' shows no devices connected.
Thanks again!
Click to expand...
Click to collapse
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Davey126 said:
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Click to expand...
Click to collapse
That's what I thought.
Thanks again for your help!
Davey126 said:
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Click to expand...
Click to collapse
Just to confirm, I should have put 5.1.2 and then rooted, correct? I may buy a new one.
Pcprik said:
Just to confirm, I should have put 5.1.2 and then rooted, correct? I may buy a new one.
Click to expand...
Click to collapse
Correct. Summary here; see index for more robust coverage.
Did anyone's amazon fire tablet 7 come with 5.3.1 out of the box? What version did it come with? I am planning to buy one soon and I was wondering if anyone has bought one that had lower firmware on it? Thanks a lot!!
cyberdude020 said:
Did anyone's amazon fire tablet 7 come with 5.3.1 out of the box? What version did it come with? I am planning to buy one soon and I was wondering if anyone has bought one that had lower firmware on it? Thanks a lot!!
Click to expand...
Click to collapse
Based on self reporting the general trend seems to be 5.3.1 but you might receive any version depending on what the shipping warehouse has in stock. If you are seeking an older build (presumably 5.1.4 or lower) your best bet is a local retailer where you can check it out in the store before committing to a purchase. Turnover is often slower so better chance of scoring a 'dated' device.
Ok so my gf bought a Kindle fire for my birthday next month because I thought buy it sooner and it's more likely to have the firmware I want. I just opened it up to check the firmware before packing it away and fortunately it came with 5.1.3 out of the box. I didn't dare connect it to WiFi incase it updated lol. Just incase anyone is interested I bought this from Argos (UK) now I just need to figure out if I can downgrade and install a custom android ROM or just stick with fire OS and root. Fun times ahead
cyberdude020 said:
Ok so my gf bought a Kindle fire for my birthday next month because I thought buy it sooner and it's more likely to have the firmware I want. I just opened it up to check the firmware before packing it away and fortunately it came with 5.1.3 out of the box. I didn't dare connect it to WiFi incase it updated lol. Just incase anyone is interested I bought this from Argos (UK) now I just need to figure out if I can downgrade and install a custom android ROM or just stick with fire OS and root. Fun times ahead
Click to expand...
Click to collapse
5.1.3 can be rolled back to 5.1.2 which is fully rootable. From there you can flash several custom roms. See forum index for detailed procedures.
Davey126 said:
5.1.3 can be rolled back to 5.1.2 which is fully rootable. From there you can flash several custom roms. See forum index for detailed procedures.
Click to expand...
Click to collapse
Thanks, I looked into it. I just wasn't sure about using flashfire with 5.1.2 because I read before you can't get supersu on 5.1.2 only kingroot. Now I see there's a way to get supersu Can't wait for my birthday now, I feel like a kid again haha.
One question I haven't found the answer to yet which you might be able to answer for me. Well actually two Does the stock recovery have a backup feature like TWRP does? So if I mess up installing something and get a boot loop for example I can just recover the ROM and will that work with backing up an android ROM?
The second question is if I install android and something messes up can I just recover back to fire os by just installing the 5.1.2 .bin file? I've not looked at the stock recovery so I haven't seen the features or how exactly it works.
Thanks again for your help
cyberdude020 said:
Thanks, I looked into it. I just wasn't sure about using flashfire with 5.1.2 because I read before you can't get supersu on 5.1.2 only kingroot. Now I see there's a way to get supersu Can't wait for my birthday now, I feel like a kid again haha.
One question I haven't found the answer to yet which you might be able to answer for me. Well actually two Does the stock recovery have a backup feature like TWRP does? So if I mess up installing something and get a boot loop for example I can just recover the ROM and will that work with backing up an android ROM?
The second question is if I install android and something messes up can I just recover back to fire os by just installing the 5.1.2 .bin file? I've not looked at the stock recovery so I haven't seen the features or how exactly it works.
Thanks again for your help
Click to expand...
Click to collapse
- stock recovery offers no backup/restore capability (thanks, Amazon)
- FlashFire does offer this feature along with an experimental restore from fastboot; read docs carefully to understand capabilities/limitations
- 3rd party backup tool offers best option to protect against personal data loss
- FireOS can be restored via stock recovery; be sure to use 5.1.2 bin; anything lower will brick device
Davey126 said:
- stock recovery offers no backup/restore capability (thanks, Amazon)
- FlashFire does offer this feature along with an experimental restore from fastboot; read docs carefully to understand capabilities/limitations
- 3rd party backup tool offers best option to protect against personal data loss
- FireOS can be restored via stock recovery; be sure to use 5.1.2 bin; anything lower will brick device
Click to expand...
Click to collapse
OK cool thanks a lot, it's all making much more sense now, it a bit daunting at first as all my flashing experience is through TWRP which is much easier While I'm picking your brain though, one more question. Is there a way to backup the android ROM? Or if I get into a boot loop I have to restore 5.1.2 and then reinstall android again?
I'm feeling much more comfortable doing this now though knowing even if I completely mess up the rooting or installing android I can just restore the 5.1.2 firmware. For £50 this thing is a steal.
cyberdude020 said:
OK cool thanks a lot, it's all making much more sense now, it a bit daunting at first as all my flashing experience is through TWRP which is much easier While I'm picking your brain though, one more question. Is there a way to backup the android ROM? Or if I get into a boot loop I have to restore 5.1.2 and then reinstall android again?
I'm feeling much more comfortable doing this now though knowing even if I completely mess up the rooting or installing android I can just restore the 5.1.2 firmware. For £50 this thing is a steal.
Click to expand...
Click to collapse
Answered this in previous post.
Mine just showed up yesterday. 5.0.1.
I just bought a new Fire 7 (7th generation) tablet. But all I found so far were for root is for Fire 7 (5th generation). Any new 7th generation root method and custom rom? Or is it compatible between 5th and latest 7th generation? Thanks for the help guys.
nyknight77 said:
I just bought a new Fire 7 (7th generation) tablet. But all I found so far were for root is for Fire 7 (5th generation). Any new 7th generation root method and custom rom? Or is it compatible between 5th and latest 7th generation? Thanks for the help guys.
Click to expand...
Click to collapse
If the OS Version is 5.3.2.1, or 5.3.3.0, then no...not root yet.
nyknight77 said:
I just bought a new Fire 7 (7th generation) tablet. But all I found so far were for root is for Fire 7 (5th generation). Any new 7th generation root method and custom rom? Or is it compatible between 5th and latest 7th generation? Thanks for the help guys.
Click to expand...
Click to collapse
The stock version is 5.3.3.0 so, no root.
DragonFire1024 said:
If the OS Version is 5.3.2.1, or 5.3.3.0, then no...not root yet.
Click to expand...
Click to collapse
Thanks for your reply. I haven't received it yet to check the OS version but I'm hearing it will be OS Version 5.4
nyknight77 said:
Thanks for your reply. I haven't received it yet to check the OS version but I'm hearing it will be OS Version 5.4
Click to expand...
Click to collapse
Mine came with 5.3.3.0.
nyknight77 said:
I just bought a new Fire 7 (7th generation) tablet. But all I found so far were for root is for Fire 7 (5th generation). Any new 7th generation root method and custom rom? Or is it compatible between 5th and latest 7th generation? Thanks for the help guys.
Click to expand...
Click to collapse
In addition to other responses no assessment of custom rom compatibility on 7th gen devices can be conducted without root. IMO it is highly unlikely an exploitable vulnerability will be found in recent builds of FireOS or the device bootloader anytime soon given recent efforts to shore up all Android based ROMs.
I just got 4 Fire 7 gen 7s in the mail today; two with a red case, two with a yellow case.
The odd thing is that the yellow colored ones came with 5.4.0.0, while the red ones came with 5.3.3.0. The red ones must not be as popular and I was sent slightly older stock I assume.
Even worse is that the 5.4.0.0 yellow ones won't even let you bypass/skip the initial wifi setup and amazon account login. You MUST be connected to the internet and login with an Amazon account to setup the tablet.
AlwaysLucky said:
I just got 4 Fire 7 gen 7s in the mail today; two with a red case, two with a yellow case.
The odd thing is that the yellow colored ones came with 5.4.0.0, while the red ones came with 5.3.3.0. The red ones must not be as popular and I was sent slightly older stock I assume.
Even worse is that the 5.4.0.0 yellow ones won't even let you bypass/skip the initial wifi setup and amazon account login. You MUST be connected to the internet and login with an Amazon account to setup the tablet.
Click to expand...
Click to collapse
I would highly advise you not allow those to update, flash 5.3.2.1 (the oldest version you can safely revert to if you haven't yet hit 5.4.0.1), and then use the tool linked below to remove all of the Amazon bloatware and install the launcher of your choice. This will get you as close as possible to a stock Android experience.
https://forum.xda-developers.com/amazon-fire/general/amazon-fire-utility-tool-bloat-removal-t3641151
Technocian said:
This will get you as close as possible to a stock Android experience.
https://forum.xda-developers.com/amazon-fire/general/amazon-fire-utility-tool-bloat-removal-t3641151
Click to expand...
Click to collapse
I appreciate the link to the updated tool. The added features are nice indeed and I will try it out.
Technocian said:
I would highly advise you not allow those to update, flash 5.3.2.1 (the oldest version you can safely revert to if you haven't yet hit 5.4.0.1), and then use the tool linked below to remove all of the Amazon bloatware and install the launcher of your choice.
Click to expand...
Click to collapse
Unfortunately, these are the 7th generation Fire 7 tablets (not 5th gen 'ford'). AFAIK, the earliest initial firmware shipped with these gen 7s is the 5.3.3.0. Even worse, is that I've tried to adb sideload every firmware version since 5.3.2.1 (even tried 5.3.3.0), but I got the same error every time at 47% progress:
"whole-file signature verification failed"
"aborted"
On that note, do you or anyone know if there is a way to adb sideload older firmware versions to a gen7? I was using the Windows 10 built-in USB drivers and that seems to be working but I have read elsewhere that the newer Fire generations require the Amazon USB ADB drivers to communicate properly with the computer. So my next step is to try using the Amazon USB driver and try again.
AlwaysLucky said:
On that note, do you or anyone know if there is a way to adb sideload older firmware versions to a gen7? I was using the Windows 10 built-in USB drivers and that seems to be working but I have read elsewhere that the newer Fire generations require the Amazon USB ADB drivers to communicate properly with the computer. So my next step is to try using the Amazon USB driver and try again.
Click to expand...
Click to collapse
Bootloader is locked and anti rollback measures are in place. If you are on 5.4.0.0, the lowest you can downgrade to currently is 5.3.2.1. Trying to go lower will result in a hard bricked tablet. Look at it this way...if you want to experiment, knock yourself out. If you do brick it beyond repair, you have 30 days from date of purchase (or delivery? Not sure how that works) to return it for another. Just get a color you haven't gotten and who knows what those are on, if the event you described regarding colors is true.
EDIT: I am in no way encouraging you to brick your device or do any harm to it.
DragonFire1024 said:
Bootloader is locked and anti rollback measures are in place. If you are on 5.4.0.0, the lowest you can downgrade to currently is 5.3.2.1. Trying to go lower will result in a hard bricked tablet. Look at it this way...if you want to experiment, knock yourself out. If you do brick it beyond repair, you have 30 days from date of purchase (or delivery? Not sure how that works) to return it for another. Just get a color you haven't gotten and who knows what those are on, if the event you described regarding colors is true.
EDIT: I am in no way encouraging you to brick your device or do any harm to it.
Click to expand...
Click to collapse
haha, nice edit.
Well I read your previous post stating that downgrading to 5.3.2.1 was possible, but I get the same above error trying to sideload any version firmware file to it. I am assuming this is because I am on the gen 7 (aka austin), not the gen 5 (aka ford). I have done some extensive searching on xda but it seems not many people actually have a gen 7, so I think I'm pioneering this a little bit.
With that, I can say that the Amazon USB driver for ADB made no change. Any ideas?
AlwaysLucky said:
haha, nice edit.
Well I read your previous post stating that downgrading to 5.3.2.1 was possible, but I get the same above error trying to sideload any version firmware file to it. I am assuming this is because I am on the gen 7 (aka austin), not the gen 5 (aka ford). I have done some extensive searching on xda but it seems not many people actually have a gen 7, so I think I'm pioneering this a little bit.
With that, I can say that the Amazon USB driver for ADB made no change. Any ideas?
Click to expand...
Click to collapse
Debugging mode is on I presume (ADB Enabled)? Have you installed any Google Services (Play Store etc)? Go here and please and follow the installation steps for Total Commander and tell me the info for the 1st and 2nd lines on your device.
DragonFire1024 said:
Debugging mode is on I presume (ADB Enabled)?
Click to expand...
Click to collapse
I truly appreciate your time into this, however I do not think I am explaining myself well. The ultimate purpose of these 4 gen7 (austin) tablets is for all 4 to be rooted and use a custom ROM. On one of the 7gens (5.3.3.0), I have successfully removed bloat from the stock rom and installed the play store (using your guide and others :good: ). It's much better than stock, but still not applicable for my purposes.
This leaves me with one option; downgrade the firmware to a rootable version (ideally 5.3.1). To do this, I enter the recovery menu by holding the volume down button and power button when powering on the tablet. While in the recovery menu (yellow on black text), I attempt to sideload firmware (any version, with md5s matching) and get the same error every time on all 4 tablets at exactly 47% completion:
"E: failed to verify whole-file signature"
"E: signature verification failed"
"installation aborted."
This doesn't brick any of the tablets and they reboot just fine out of recovery into the stock firmware. It must have something to do with the 7th gen tablets. While connected via USB to the tablets while in sideload mode in recovery, the hardware ID for the USB connection shows up as "USB\VID_1949&PID_0001". After googling that a little bit, it kept coming back to HD8 drivers! Soooo maybe I need the HD8 version of the firmwares so I can downgrade? Hmmmmm.....
AlwaysLucky said:
I truly appreciate your time into this, however I do not think I am explaining myself well. The ultimate purpose of these 4 gen7 (austin) tablets is for all 4 to be rooted and use a custom ROM. On one of the 7gens (5.3.3.0), I have successfully removed bloat from the stock rom and installed the play store (using your guide and others :good: ). It's much better than stock, but still not applicable for my purposes.
This leaves me with one option; downgrade the firmware to a rootable version (ideally 5.3.1). To do this, I enter the recovery menu by holding the volume down button and power button when powering on the tablet. While in the recovery menu (yellow on black text), I attempt to sideload firmware (any version, with md5s matching) and get the same error every time on all 4 tablets at exactly 47% completion:
"Whole-file verification failed"
"Aborting installation"
This doesn't brick any of the tablets and they reboot just fine out of recovery into the stock firmware. It must have something to do with the 7th gen tablets. While connected via USB to the tablets while in sideload mode in recovery, the hardware ID for the USB connection shows up as "USB\VID_1949&PID_0001". After googling that a little bit, it kept coming back to HD8 drivers! Soooo maybe I need the HD8 version of the firmwares so I can downgrade? Hmmmmm.....
Click to expand...
Click to collapse
I have no idea. Regardless, you CANNOT downgrade to anything lower than FireOS 5.3.2.1 (which cannot be rooted). If your tablets are on 5.3.3.0 or 5.4.0.0, the lowest you can go is 5.3.2.1. If you are having ADB trouble, I would download Android Studio full version and make sure the SDK is up to date and start a new ADB folder from there. If your Kernel is of a later date than June 2017, you might not be able to rollback at all.
AlwaysLucky said:
I truly appreciate your time into this, however I do not think I am explaining myself well. The ultimate purpose of these 4 gen7 (austin) tablets is for all 4 to be rooted and use a custom ROM. On one of the 7gens (5.3.3.0), I have successfully removed bloat from the stock rom and installed the play store (using your guide and others :good: ). It's much better than stock, but still not applicable for my purposes.
This leaves me with one option; downgrade the firmware to a rootable version (ideally 5.3.1). To do this, I enter the recovery menu by holding the volume down button and power button when powering on the tablet. While in the recovery menu (yellow on black text), I attempt to sideload firmware (any version, with md5s matching) and get the same error every time on all 4 tablets at exactly 47% completion:
"Whole-file verification failed"
"Aborting installation"
This doesn't brick any of the tablets and they reboot just fine out of recovery into the stock firmware. It must have something to do with the 7th gen tablets. While connected via USB to the tablets while in sideload mode in recovery, the hardware ID for the USB connection shows up as "USB\VID_1949&PID_0001". After googling that a little bit, it kept coming back to HD8 drivers! Soooo maybe I need the HD8 version of the firmwares so I can downgrade? Hmmmmm.....
Click to expand...
Click to collapse
Have seen this before (crap out at 47%). Usually pops up when attempting to sideload an inappropriate '.bin' file. Likely the 5.3.1 build you are using is for 5th gen devices. Different mainboard/SOC than 7th gen. Be happy Amazon's firmware detects this and doesn't allow the device to brick.
DragonFire1024 said:
Regardless, you CANNOT downgrade to anything lower than FireOS 5.3.2.1 (which cannot be rooted).
Click to expand...
Click to collapse
Ohhh I understand, so even if downgrading to 5.3.2.1 actually worked, I can't even root on that firmware anyways. Ugh, well I will be patient. Thanks for the info and your time.
If your goal is to have these all ultimately rooted, I would return them and get your money back (if you still can). It's not likely a root method will be found.
This isn't a hot new device like the Pixel 2 where hoards of talent will be flocking to try and make it more usable. I got mine second hand for 25 bucks, this device from a monetary standpoint just isn't worth anyone's time.
The only realistic way I see root happening is if they release firmware based on a new version of Android or Kingroot find an Android exploit that would be compatible with our device.
AlwaysLucky said:
Ohhh I understand, so even if downgrading to 5.3.2.1 actually worked, I can't even root on that firmware anyways. Ugh, well I will be patient. Thanks for the info and your time.
Click to expand...
Click to collapse
Correct...but keep in mind, so far it seems anyone on 5.4.0.1 won't be be able to debloat anymore. So downgrading to 5.3.2.1 is a better option than being so close to the latest version.
I'm not looking to root (i am, but i understand its not possible right now)... So is there any possibility to install apps other than the amazon app store?
thygreyt said:
I'm not looking to root (i am, but i understand its not possible right now)... So is there any possibility to install apps other than the amazon app store?
Click to expand...
Click to collapse
Please see this thread.
My tablet just jumped from 5.3.2.1 to 5.3.3.0 in one day. I tried kingroot several times hoping it would work. It did not. I performed factory reset on it and signed into amazon. When i woke up it was at 5.4.0.0. My question is if a root exploit is found for 5.3.2.1 or 5.3.3.0 can it be rolled back? This all started from a bad SD card that kept resetting my old fire. I thought there was something wrong with the tablet and bought a used one off eBay hoping it would come with 5.1.2. I love AOSP on these machines.
daniel3016 said:
My tablet just jumped from 5.3.2.1 to 5.3.3.0 in one day. I tried kingroot several times hoping it would work. It did not. I performed factory reset on it and signed into amazon. When i woke up it was at 5.4.0.0. My question is if a root exploit is found for 5.3.2.1 or 5.3.3.0 can it be rolled back? This all started from a bad SD card that kept resetting my old fire. I thought there was something wrong with the tablet and bought a used one off eBay hoping it would come with 5.1.2. I love AOSP on these machines.
Click to expand...
Click to collapse
If I recall correctly, 5.3.3.0 COULD be rolled back to 5.3.2.1. And 5.4 supposedly, or theoretically can be rolled back to 5.3.3. So theoretically, yes it could be rolled back to 5.3.2.1 from 5.4.
Hello guys. I really appreciate what is done on this forum. Keep on doing it, it really helps a lot of people out there. I would like an explanation on how to roll back from OS 5.3.3.0 to OS 5.3.2.1 on Amazon fire 7" 5th gen. Thanks
ulrngui said:
Hello guys. I really appreciate what is done on this forum. Keep on doing it, it really helps a lot of people out there. I would like an explanation on how to roll back from OS 5.3.3.0 to OS 5.3.2.1 on Amazon fire 7" 5th gen. Thanks
Click to expand...
Click to collapse
There is no benefit to be gained with that action. However, if you insist: https://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
Just for heck it i adb sideloaded 5.3.2.1 while on 5.4.0.0 just to see what happened and it appears to have downgraded just fine. I know there was nothing to be gained from this but I needed to know. This tablet is to be kept off of wifi
daniel3016 - how did you sideload to downgrade 5.4 to 5.3.2.1? Thanks
smolie701 said:
daniel3016 - how did you sideload to downgrade 5.4 to 5.3.2.1? Thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
daniel3016 said:
Just for heck it i adb sideloaded 5.3.2.1 while on 5.4.0.0 just to see what happened and it appears to have downgraded just fine. I know there was nothing to be gained from this but I needed to know. This tablet is to be kept off of wifi
Click to expand...
Click to collapse
Hey, do you have a link (or tips) to how you did this? I have 5.4.0.0 and the advice I'm getting is that this system version cannot be rooted or downgraded, that trying will brick it. You're the only one who seems to have had success. The follow-up link given by someone else (https://forum.xda-developers.com/ama...h-gen-t3285294) doesn't have a shred of info on 5.4.x.x.
I just downgraded to 5.3.2.1 from 5.4.0.0 i have never acheived root. You gain nothing by doing it. I did it just to see if i could. Hope that helps.
Mr2nSmith said:
Hey, do you have a link (or tips) to how you did this? I have 5.4.0.0 and the advice I'm getting is that this system version cannot be rooted or downgraded, that trying will brick it. You're the only one who seems to have had success. The follow-up link given by someone else (https://forum.xda-developers.com/ama...h-gen-t3285294) doesn't have a shred of info on 5.4.x.x.
Click to expand...
Click to collapse
Clarification: you can not downgrade from 5.4.x.x+ to a rootable version of FireOS as of the date of this post (5.3.1.0/5.3.2.0 are the highest rootable builds). Amazon updated the bootloader concurrent with delivery of FireOS 5.3.2.1; manually rolling back to a lower version will brick the device. At present there is not a method for downgrading FireOS independent of the bootloader on an unrooted device.
Davey126 said:
Clarification: you can not downgrade from 5.4.x.x+ to a rootable version of FireOS as of the date of this post (5.3.1.0/5.3.2.0 are the highest rootable builds). Amazon updated the bootloader concurrent with delivery of FireOS 5.3.2.1; manually rolling back to a lower version will brick the device. At present there is not a method for downgrading FireOS independent of the bootloader on an unrooted device.
Click to expand...
Click to collapse
To Clarify - Can I downgrade 5.4.4 to 5.3.2.1 Safely?
savvytechwinner said:
To Clarify - Can I downgrade 5.4.4 to 5.3.2.1 Safely?
Click to expand...
Click to collapse
Probably 'yes' based on a couple user reports. However, there is no benefit to offset the potential brick risk if the version of FireOS currently on your device has an incompatible bootloader. 5.3.2.1 can not be rooted so what's the point?
Davey126 said:
Probably 'yes' based on a couple user reports. However, there is no benefit to offset the potential brick risk if the version of FireOS currently on your device has an incompatible bootloader. 5.3.2.1 can not be rooted so what's the point?
Click to expand...
Click to collapse
I downgraded. I had the system updates uninstalled so have no clue if it worked but I downgraded anyways because root might be found in a different method and got patched? have no clue and no suspecting it. Just proving that dowgrading is safe from 5.4 to 5.3.2.1
savvytechwinner said:
I downgraded. I had the system updates uninstalled so have no clue if it worked but I downgraded anyways because root might be found in a different method and got patched? have no clue and no suspecting it. Just proving that dowgrading is safe from 5.4 to 5.3.2.1
Click to expand...
Click to collapse
savvytechwinner, Can you please link to the tutorial you followed in order to downgrade?
ormaoz said:
savvytechwinner, Can you please link to the tutorial you followed in order to downgrade?
Click to expand...
Click to collapse
I believe you can find the 5.3.2.1 software here. I believe all you have to do is place the .bin into the internal storage (SDcard) and boot into recovery to flash it. I'm not 100% certain though.
DragonFire1024 said:
I believe you can find the 5.3.2.1 software here. I believe all you have to do is place the .bin into the internal storage (SDcard) and boot into recovery to flash it. I'm not 100% certain though.
Click to expand...
Click to collapse
You download the 5.3.2.1.bin file from rootjunkysdl.com and adb sideload it
ormaoz said:
savvytechwinner, Can you please link to the tutorial you followed in order to downgrade?
Click to expand...
Click to collapse
DragonFire1024 said:
I believe you can find the 5.3.2.1 software here. I believe all you have to do is place the .bin into the internal storage (SDcard) and boot into recovery to flash it. I'm not 100% certain though.
Click to expand...
Click to collapse
savvytechwinner said:
You download the 5.3.2.1.bin file from rootjunkysdl.com and adb sideload it
Click to expand...
Click to collapse
...or from the forum index which contains a ton of information and resources that most choose to ignore.
Davey126 said:
...or from the forum index which contains a ton of information and resources that most choose to ignore.
Click to expand...
Click to collapse
Or just forget. Not used to the index material.
Hi can i rollback from 5.4.0.1 to 5.3.2.1 ? or to 5.4.0.0 !?
Edit. The the rollback from 5.4.0.1 to 5.3.2.1 has worked well .
Any news in the community about a 5.6.0.0 rollback?