I just now received the 6.3.1.2 OS on my 8th gen Fire HD 8. The build number is 1852.
It's still loading the update, so I don't know if it messes with my launcher hijack or not. Should know soon.
I think the main OS version is the same one that came on the recent 9th gen Fire 7 tablets.
Just thought I'd share. We'll see what happens.
What's new/working on Fire OS 6.3.1.2
On another Fire HD 8 we updated.
Does mtk-su still works? I didn't unlock my tablet yet, waiting to know if it still works for upgrading.
lfom said:
Does mtk-su still works? I didn't unlock my tablet yet, waiting to know if it still works for upgrading.
Click to expand...
Click to collapse
Not with latest FireOS build(s); vulnerability apparently blocked/patched. Can still unlock and root, just no temp root via mtk-su.
Can anyone catch this OTA Update and post the link?
Can someone test out if it's possible to downgrade to 6.3.0.1 via recovery without bricking? If it ends up not booting, you can recover it through the amonet+hardware method.
Can you block the internet access from OTA updates using NoRoot Firewall from Google Play Store
Can you also downgrade it the Fire OS 6.3.1.2 to 6.3.0.1 via ADB sideload without bricking (Wipe all the cache and data first, before downgrade it). If your Fire tablet gets boot-loop or bricking, Get solution: https://forum.xda-developers.com/hd...d-8-2018-downgrade-unlock-root-t3894256/page1
AmznUser444 Dev said:
Can you block the internet access from OTA updates using NoRoot Firewall from Google Play Store
Click to expand...
Click to collapse
Typically VPN based firewalls (VPNs in general) do not function well on FireOS. Are you stating NoRoot Firewall operates correctly on FireOS v6 ... or simply speculating based on feature set?
How can install CH play on this update? Thank you
DB126 said:
Not with latest FireOS build(s); vulnerability apparently blocked/patched. Can still unlock and root, just no temp root via mtk-su.
Click to expand...
Click to collapse
are you talking about the hardware method? or is there some other software method that doesn't rely on mtk-su?
How I can find the Ignore Battery Optimization in Settings?
acme64 said:
are you talking about the hardware method? or is there some other software method that doesn't rely on mtk-su?
Click to expand...
Click to collapse
Search is your friend :
https://forum.xda-developers.com/hd8-hd10/general/tut-root-hd82018-via-magisk-t3906554
---------- Post added at 11:30 AM ---------- Previous post was at 11:27 AM ----------
AmznUser444 Dev said:
How I can find the Ignore Battery Optimization in Settings?
Click to expand...
Click to collapse
Not accessible via FireOS settings.
DB126 said:
Not accessible via FireOS settings.
Click to expand...
Click to collapse
Want to ignore the battery optimization using ADB without root?
This link: https://forum.xda-developers.com/hd8-hd10/general/root-ignore-battery-optimization-using-t3963413
diplomatic said:
Can someone test out if it's possible to downgrade to 6.3.0.1 via recovery without bricking? If it ends up not booting, you can recover it through the amonet+hardware method.
Click to expand...
Click to collapse
FYI:
https://forum.xda-developers.com/showpost.php?p=80164459&postcount=162
Your Fire tablet is updated to Fire OS 6.3.1.2.
New features and working bugs from Fire OS 6.3.1.2:
- Search bar on lock screen
- mtk-su not working
- You get a some malicious, virus apps from Amazon Appstore (Do not install it to your Fire tablet):
-> Malware (Malicious actions and performance on your Fire tablet)
-> Malvertising (Malicious advertising)
-> Trojan Horse
-> Spyware
-> Ransomware (Can you lock or encrypt your Fire tablet)
-> Adware (Intrusive and inappropriate ads)
-> Backdoor
- New bloatwares and cr*pwares
- Google services is still working
- Downgradable Fire OS
- Still rootable (requires to downgrade it to Fire OS 6.3.0.1)
AmznUser444 Dev said:
- Downgradable Fire OS
- Still rootable (requires to downgrade it to Fire OS 6.3.0.1)
Click to expand...
Click to collapse
What do you mean? Have you actually downgraded it using stock recovery, and it booted back up?
diplomatic said:
What do you mean? Have you actually downgraded it using stock recovery, and it booted back up?
Click to expand...
Click to collapse
Yea, he's posted the same thing in several threads w/o substantiation. I challenged the assertion in one thread but have yet to receive a response.
Might work, just need some evidence it doesn't yield a (soft) brick. Seems strange Amazon would tweak the bootloader given changes baked into 6.3.1.2 and above.
AmznUser444 Dev said:
- Downgradable Fire OS
- Still rootable (requires to downgrade it to Fire OS 6.3.0.1)
Click to expand...
Click to collapse
diplomatic said:
What do you mean? Have you actually downgraded it using stock recovery, and it booted back up?
Click to expand...
Click to collapse
DB126 said:
Yea, he's posted the same thing in several threads w/o substantiation. I challenged the assertion in one thread but have yet to receive a response.
Might work, just need some evidence it doesn't yield a (soft) brick. Seems strange Amazon would tweak the bootloader given changes baked into 6.3.1.2 and above.
Click to expand...
Click to collapse
Just to confirm, downgrade to 6.3.0.1 is NOT POSSIBLE using stock recovery (It will result in a brick).
Code:
[4646] [ANTI-ROLLBACK] Processing anti-rollback data
[4650] mmc_rpmb_send_command -> req_type=0x1, type=0x4, blks=0x1
[4654] mmc_rpmb_send_command -> req_type=0x2, type=0x4, blks=0x1
[4657] [ANTI-ROLLBACK] PL: 6 TEE: 103 LK: 2
[4658] [ANTI-ROLLBACK] Checksum validated
[4658] [ANTI-ROLLBACK] LK version mismatch!
[4659] [ANTI-ROLLBACK] L: 2 R: 1
LK-Version has been updated from 1 to 2. (TZ and PL remain at the same version)
Yeah, that makes sense, @k4y0z, because someone else reported getting a brick. This AmznUser guy, I suspect if he did try it, it was using TWRP. That's why I emphasized stock recovery...
diplomatic said:
Yeah, that makes sense, @k4y0z, because someone else reported getting a brick. This AmznUser guy, I suspect if he did try it, it was using TWRP. That's why I emphasized stock recovery...
Click to expand...
Click to collapse
I suspect he didn't try at all, since 6.3.1.2 can still be rooted fine using Magisk when unlocked, no downgrade necessary.
To be honest I don't understand most of what this guy is posting
Related
As of August 25 or 26, 2017, the current updated FireOS version is 5.4.0.1. Last build date prior to this was on May 31, 2017. As of this post, the updated OS is not yet available on Amazon's site.
Please comment if you receive any errors when attempting to 'uninstall' Amazon Apps, whether automatically or manually. Some users report errors.
Please download Droid Examiner or Droid Hardware Info or a like minded app (these types of apps vary from developer to developer. I use these two primarily).
Droid Examiner: Tap build and look at the time. It will have the date of the last build updated to your tablet.
build.prop (/system/build.prop): Look for these values. Please post dates and versions if possible. Last Kernel patch for 5.4.0.0 was for June 2017.
Yes, 5.4.0.1 broke the junkware uninstall process referenced in this thread: https://forum.xda-developers.com/hd8-hd10/general/root-required-remove-amazon-bloatware-t3636796
As the "pm uninstall --user 0 xxx.yyyyy.zzzzzz" command runs, you get
Failure [DELETE_FAILED_INTERNAL_ERROR]
after every line.
Fire OS 5.4.0.1
Build Date: August 13, 2017 9:04 pm
jpm122 said:
Yes, 5.4.0.1 broke the junkware uninstall process referenced in this thread: https://forum.xda-developers.com/hd8-hd10/general/root-required-remove-amazon-bloatware-t3636796
As the "pm uninstall --user 0 xxx.yyyyy.zzzzzz" command runs, you get
Failure [DELETE_FAILED_INTERNAL_ERROR]
after every line.
Fire OS 5.4.0.1
Build Date: August 13, 2017 9:04 pm
Click to expand...
Click to collapse
What a shame. I wonder why it took them so long?
Is it possible to downgrade a 2017 model back to 5.4.0.0 and disable the OTA updates? I never understood that needed to be done and now it's probably too late.
GreenElephants said:
Is it possible to downgrade a 2017 model back to 5.4.0.0 and disable the OTA updates? I never understood that needed to be done and now it's probably too late.
Click to expand...
Click to collapse
5.4.0.0 CAN be downgraded to 5.3.2.1, but NOTHING lower or you will brick. i am not sure if the model matters or not.
How about 5.4.0.1? I want to downgrade so I can install Play Store and Titanium Backup to uninstall all the crap.
iknight8 said:
How about 5.4.0.1? I want to downgrade so I can install Play Store and Titanium Backup to uninstall all the crap.
Click to expand...
Click to collapse
Also interested in this because I was too late in stopping the update to 5.4.0.1 last night
InfamousDX said:
Also interested in this because I was too late in stopping the update to 5.4.0.1 last night
Click to expand...
Click to collapse
I was able to install Play Store and have it working but still not satisfied with all the other restrictions!!! I returned it yesterday! I suggest you get a normal Android tablet and not this crappy locked up Fire tablet!
Let me know if you still need to know how to install Play Store...
Titanium backup will not work on 5.4.0.1 because it doesn't have root and you need root access to run TB. *SIGH*
Restore OS 5.4.0.0 - amazon.com/gp/help/customer/display.html?nodeId=202144590 ( adb sideload )
then use the fire utility tool
I have done the same for 7th Gen Fire Tab which was auto updated to 5.4.0.1
@nccchirag
nccchirag said:
I have done the same for 7th Gen Fire Tab which was auto updated to 5.4.0.1
[/MENTION]
Click to expand...
Click to collapse
Please clarify.
Did you mean to say that you have succeeded in downgrading to Fire OS 5.4.0.0 "FROM" Fire OS 5.4.0.1 ?
Thank you.
Dan_firehd said:
Please clarify.
Did you mean to say that you have succeeded in downgrading to Fire OS 5.4.0.0 "FROM" Fire OS 5.4.0.1 ?
Thank you.
Click to expand...
Click to collapse
Early reports suggest 5.4.0.1 cannot be downgraded.
5.4.0.1 to 5.4.0.0???
nccchirag said:
Restore OS 5.4.0.0 - amazon.com/gp/help/customer/display.html?nodeId=202144590 ( adb sideload )
then use the fire utility tool
I have done the same for 7th Gen Fire Tab which was auto updated to 5.4.0.1
@nccchirag
Click to expand...
Click to collapse
Yes, please clarify. How were you able to get 5.4.0.1 back down to 5.4.0.0 ?
Thanks
krisesco said:
Yes, please clarify. How were you able to get 5.4.0.1 back down to 5.4.0.0 ?
Thanks
Click to expand...
Click to collapse
If it works, put the file linked above into your ADB folder. Then you would power off device, reboot to recovery, press and hold volume down first then press power button (hold both at the same time) until you see the Amazon logo. On the recovery screen, select ADB update. From an ADB window, type:
adb sideload name.of.file
A few users said they hard bricked their tablet trying to downgrade. So be careful. Not sure if true or not, but just warning you.
DragonFire1024 said:
If it works, put the file linked above into your ADB folder. Then you would power off device, reboot to recovery, press and hold volume down first then press power button (hold both at the same time) until you see the Amazon logo. On the recovery screen, select ADB update. From an ADB window, type:
adb sideload name.of.file
A few users said they hard bricked their tablet trying to downgrade. So be careful. Not sure if true or not, but just warning you.
Click to expand...
Click to collapse
Thanks for the response, and the warning. I am definitely curious if this would work, but perhaps I will hold off until someone braver can confirm that this works or doesn't.
If anyone out there has tried downgrading 5.4.0.1 to 5.4.0.0 successfully, by side-loading 5.4.0.0, please let me know.
Thanks!
krisesco said:
Thanks for the response, and the warning. I am definitely curious if this would work, but perhaps I will hold off until someone braver can confirm that this works or doesn't.
If anyone out there has tried downgrading 5.4.0.1 to 5.4.0.0 successfully, by side-loading 5.4.0.0, please let me know.
Thanks!
Click to expand...
Click to collapse
So far only a few new users have have reported such claims. And there have only been a few. Maybe 3.
Downgrade no go
DragonFire1024 said:
So far only a few new users have have reported such claims. And there have only been a few. Maybe 3.
Click to expand...
Click to collapse
I just tried to downgrade my Fire HD8 (7th Gen) from 5.4.0.1 to 5.4.0.0 by sideloading it and it just said that the signature verification failed. I then rebooted. It did not brick my device.
montizzl3 said:
just said that the signature verification failed. I then rebooted. It did not brick my device.
Click to expand...
Click to collapse
Because installation didn't started yet It's like: "I downloaded image to my PC but it didn't brick my device"...
sensboston said:
Because installation didn't started yet It's like: "I downloaded image to my PC but it didn't brick my device"...
Click to expand...
Click to collapse
Users are reporting that a Fire 7 (current generation) running FireOS 5.4.0.1, CAN be downgraded to 5.4.0.0. It appears the HD 8 CANNOT be. However I am not sure how this is possible. Maybe someone with a bit more knowledge about the specifics can chime in.
5.4.0.1 down to 5.4.0.0
nccchirag said:
Restore OS 5.4.0.0 - amazon.com/gp/help/customer/display.html?nodeId=202144590 ( adb sideload )
then use the fire utility tool
I have done the same for 7th Gen Fire Tab which was auto updated to 5.4.0.1
@nccchirag
Click to expand...
Click to collapse
Please Clarify: Do you mean to say that you downgraded successfully from 5.4.0.1 back to 5.4.0.0?
I had reset my devices and reinstalled no root firewall but stupid me forgot to check start at bootup. So when my kindle restarted, ota was not blocked...
Provided said:
Please Clarify: Do you mean to say that you downgraded successfully from 5.4.0.1 back to 5.4.0.0?
I had reset my devices and reinstalled no root firewall but stupid me forgot to check start at bootup. So when my kindle restarted, ota was not blocked...
Click to expand...
Click to collapse
The Fire 7, 7th generation apparently can be downgraded yes.
Okay so as the fire just updated to 5.4.0.0 and now 5.4.1.0 this means there is an exploit somewhere. If it doesnt have a changelog, Amazon probably increased security.
I would recommend getting No Root Firewall of the play store. Block internet for all amazon apps except Amazon Downloader, and Google play services (this could show as an Amazon app)(This prevents auto updates)
When an update comes out with no changelog DO NOT UPDATE TO IT. AmazonFresh this when they find an error. And an error could mean possible root.
If you did the steps above you shouldn't be receiving updates, there for meaning, you have the possibility of root.
Cancel Update?
Hi,
I installed Netguard and blocked System Update and some Alex services.
At first that kept system updates from connecting and it said: "can't check update" or something.
10 Minutes later suddenly the 5.6.0.0 update shows up and it says it will install when inactive.
What can I do to prevent it from updating?
Running 5.4.0.1
P.S.
Kingroot still not working,
"rm -f /sdcard/Android/data/com.amazon.device.software.ota/files/*.bin" did nothing (no files)
"rm -rf /cache/*" gives 'Permission denied'
using adb shell
Has anyone tried the root yet?
https://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
0v3rdr1v3 said:
Has anyone tried the root yet?
https://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
Click to expand...
Click to collapse
The last comment on that post is from 2016. It says:
"This root method is no longer supported and does not work on recent devices. Thread closed."
lehnin said:
Hi,
I installed Netguard and blocked System Update and some Alex services.
At first that kept system updates from connecting and it said: "can't check update" or something.
10 Minutes later suddenly the 5.6.0.0 update shows up and it says it will install when inactive.
What can I do to prevent it from updating?
Running 5.4.0.1
P.S.
Kingroot still not working,
"rm -f /sdcard/Android/data/com.amazon.device.software.ota/files/*.bin" did nothing (no files)
"rm -rf /cache/*" gives 'Permission denied'
using adb shell
Click to expand...
Click to collapse
Hmm, maybe PM clear <packagename>
sorry new guy here...
thefanum said:
The last comment on that post is from 2016. It says:
"This root method is no longer supported and does not work on recent devices. Thread closed."
Click to expand...
Click to collapse
Does this mean that rooting these is NEVER going to be a possibility? Or a new method is being developed and is not out yet? Also I have 2 HD 8's, one is on 5.6 and the other is on 5.4.0.1. Does the factory reset bring it back to 5.4.0.1?
Aethernoob said:
Does this mean that rooting these is NEVER going to be a possibility? Or a new method is being developed and is not out yet? Also I have 2 HD 8's, one is on 5.6 and the other is on 5.4.0.1. Does the factory reset bring it back to 5.4.0.1?
Click to expand...
Click to collapse
These have been out for months without a root solution. I would guess it could easily be months more before we find a solution. Or longer, if at all.
Factory resetting will not downgrade your firmware ever on any device. Do not attempt to downgrade manually, as it would brick it.
If you factory reset, it will try to auto update as soon as you connect to WiFi. If you set it up without network access, and then remote the OTA feature, it may not upgrade the firmware. I just did exactly this, and it went fine. But there's no room for error.
Your best bet for root is to block OTA's and wait. As far as we know, there is no root method even under development currently. Although, if I were working on one, I sure wouldn't tell anyone, and get "ETA'd" to death.
[QUOTE="thefanum, post: 74729008, member: 4404866"]These have been out for months without a root solution. I wo
thefanum said:
These have been out for months without a root solution. I would guess it could easily be months more before we find a solution. Or longer, if at all.
Factory resetting will not downgrade your firmware ever on any device. Do not attempt to downgrade manually, as it would brick it.
If you factory reset, it will try to auto update as soon as you connect to WiFi. If you set it up without network access, and then remote the OTA feature, it may not upgrade the firmware. I just did exactly this, and it went fine. But there's no room for error.
Your best bet for root is to block OTA's and wait. As far as we know, there is no root method even under development currently. Although, if I were working on one, I sure wouldn't tell anyone, and get "ETA'd" to death.
Click to expand...
Click to collapse
Being super green in this field if you "brick" it and then "unbrick" it will that just fastboot it back to factory set points? Also is there a glossary for all these acronyms... it would be glorious if there was!!!
Aethernoob said:
Being super green in this field if you "brick" it and then "unbrick" it will that just fastboot it back to factory set points? Also is there a glossary for all these acronyms... it would be glorious if there was!!!
Click to expand...
Click to collapse
Brick means physically broken, usually forever. As in, your tablet is now as useful as a brick. There are soft bricks where just the firmware is broken, but can be fixed by reflashing (still won't downgrade). But we're taking about a full brick. As in, you destroy your tablet and have to buy a new one.
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.
l7777 said:
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.
Click to expand...
Click to collapse
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!
bluh5d said:
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!
Click to expand...
Click to collapse
The similarities are only on the surface my friend. When dealing with computers, similar and close is rarely good enough. You need exact.
bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.
evilwombat said:
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.
Click to expand...
Click to collapse
Can I root with latest supersu without recovery ?
Someone's bound to hose up their phone. Wondering where factory images are?
Born<ICs said:
Someone's bound to hose up their phone. Wondering where factory images are?
Click to expand...
Click to collapse
Yes. I agree. Might be me right. I wasn't planning on flashing recovery though just booting it.
If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.
If your bootloader is unlocked and you want root.
Try installing Chain fire's Supersu from the play store or install the apk.
I do not have my P2 yet to try.
Sent from my Nexus 5X using Tapatalk
me_droid said:
If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.
Click to expand...
Click to collapse
I think this may be a waste of time because it was modded to work on Oreo. They have already released a version that works on Oreo 3-1-1 that I already tried it wouldnt boot it. I will probably just wait even though i want to play. So i guess I can just say yep I have a pixel 2 with the bootloader unlocked and thats about it.
This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(
The_Fuzz22 said:
This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(
Click to expand...
Click to collapse
Yeah, I take having root completely for granted. I guess I've never bought a phone right at the moment of release before. If I didn't really need a new phone, I suppose I would have waited. Anyway, I figured out that you can block ads, without root, with apps that run all your traffic through a vpn (that's really only running locally on the phone). The best options after much research seem to me to be Netguard and AdGuard (though I haven't tried them yet). They both also include a firewall (Netguard is primarly a firewall), which I want.
https://github.com/M66B/NetGuard/blob/master/ADBLOCKING.md
https://adguard.com/en/adguard-android/overview.html
DNS66 also seems to be higly regarded, but it doesn't include a firewall. There are other firewall only apps, which work with the VPN method, but you can only run one VPN on Android at a time, so if you want both functions, without root, you need an app that does both.
https://forum.xda-developers.com/android/apps-games/app-dns66-source-host-ad-blocker-root-t3487497
Anyway, that's my plan until root comes along. Then I will go back to AdAway and AFWall+.
There is no kernel source released for the Pixel 2/XL yet. It is based on the 4.4 kernel, this should make development very smooth.
https://forum.xda-developers.com/pixel-2/development/psa-fastboot-booting-bad-image-confuse-t3692932
If you want to repost this internal OTA to other websites (other than XDA itself), please ask me for permission, thanks.
Click to expand...
Click to collapse
WARNING!
This is early internal test build, so LATER OTA UPDATES CAN'T BE GUARANTEED!
If you don't have unlocked bootloader, you'll unable to roll back to stable build!
Please be careful when testing!
Click to expand...
Click to collapse
Now I think it's time to bring you back to canary labs faster than beta labs.
Internal build version: B2N-4040-0-00WW-B01
It will be updated from: B2N-354K-0-00WW-B01, which is not pushed to public
As I've warned before - having an unlocked bootloader is strongly recommended.
So recent builds removed handy 874 dialing codes, we have to install them under recovery or Nokia Extensions.
Non-Chinese speaking users should ignore this quote.
中国用户如需从百度网盘下载,这些内测包发布在了诺记吧。
Click to expand...
Click to collapse
UPDATE: Thanks everyone. To fix microphone bug, please disable the microphone permission of the "Google" app.
You'll lose "OK Google" ability, but you can make telephone call properly.
Click to expand...
Click to collapse
Let me tell you how to verify:
1. Dial *#*#227#*#* to check current Version. If older than B2N-354J-0-00WW-B01 (check if the letter is greater than J), update to 354J before proceed.
FYI, 354J is August 2019 Security Update.
Alternately, you can use command "fastboot oem getversions" under fastboot mode / Download mode to check current firmware version.
If newer than 354J (probably 354N when this post released), you'll need to downgrade your phone back to at most 354H - which can't be done easily without unlocked bootloader.
2. Install B2N-354K-0-00WW-B01-354J-0-00WW-B01-update.zip with Nokia Extensions OTA Update module or adb sideload under recovery.
3. Reboot your phone.
4. Install B2N-4040-0-00WW-B01-354K-0-00WW-B01-update.zip with Nokia Extensions OTA Update module or adb sideload under recovery.
5. Reboot your phone.
That's it.
If minor fixes released, I will upload them as well, then use the same method to install it.
To root the phone, you may want to use Magisk 20 released today (October 12th, 2019) or newer.
Download link:
This thread is now deprecated.
https://android.googleapis.com/pack.../afd338bfb14d447b716c220424b2ad2c66213183.zip (B2N-410C-0-00WW-B03-update.zip)
https://www.androidfilehost.com/?w=files&flid=299363
could you please describe how to downgrade from 354M to 354H with unlocked bootloader? i have no idea...
About rollback to stable release
You said "it can't be easily done without unlocked bootloader"
Soz should ai consider the possibility of "it STILL can be done but with much difficulty " ???
Liftedcorn said:
About rollback to stable release
You said "it can't be easily done without unlocked bootloader"
Soz should ai consider the possibility of "it STILL can be done but with much difficulty " ???
Click to expand...
Click to collapse
For detailed, there's a backdoor left for customer care to allow them flash your phone with locked bootloader, but need to be elevated from server side, which can't be done by average person.
Oh .. thank you for the info.
Tried on TA-1055
Downgrade not permitted ?
ExaHamza said:
Tried on TA-1055
Downgrade not permitted
Click to expand...
Click to collapse
why did you want to downgrade? did you also try to flash the "old" rom to the other slot? https://forum.xda-developers.com/nokia-7-plus/how-to/finally-downgrade-phone-official-t3849437
well, okay, nokia extensions doesn't see the update zip (yes, superuser granted), sideloading doesn't work as it's asking for 354J version which i have. what am i doing wrong,
---------- Post added at 08:58 PM ---------- Previous post was at 08:36 PM ----------
ExaHamza said:
Tried on TA-1055
Downgrade not permitted ?
Click to expand...
Click to collapse
How did you manage to flash this? I simply can't, though I'm on version 354J aug patch
Bro you said we cant roll to stable version unless we have our bootloader unlocked ..
My question is can i flash stable android 10 when its released after flashing beta one ??
donjamal said:
well, okay, nokia extensions doesn't see the update zip (yes, superuser granted), sideloading doesn't work as it's asking for 354J version which i have. what am i doing wrong,
---------- Post added at 08:58 PM ---------- Previous post was at 08:36 PM ----------
How did you manage to flash this? I simply can't, though I'm on version 354J aug patch
Click to expand...
Click to collapse
Tried different ota packages on adb sideload and failed I'm on 00WW_354H_SP3
@hikari_calyx so how's Android 10 so far (build 4040) ?
Major bugs to be aware of ?
Nokia apps are ported already and working properly ?
so we'll never learn anything about this, will we? like we can't flash it (or at least i could not), no feedback if all good or if there are any major issues, nada. maybe i'm impatient
I'm running 4040 build and the only bug I have is the camera doesn't work...
Micahvdm said:
I'm running 4040 build and the only bug I have is the camera doesn't work...
Click to expand...
Click to collapse
So, we can expect an early surprise release for nokia 7 plus ?
Probably not...camera locks up most of the phone functionality...quite a few wakelocks too
Micahvdm said:
Probably not...camera locks up most of the phone functionality...quite a few wakelocks too
Click to expand...
Click to collapse
There's ONLY one bug of camera. And no other major bugs. And no daily life functionality is affected unless you do no other work with your phone except taking photos.( No offense ) ?
There might be a possibility that even after this camera bug is resolved, hmd might carry out extended testing and only release 10 at the time they've already mentioned.
Just a possibility.
Wakelocks are also a bit of an issue with regards to battery life...and I also work from my phone daily...not just used for camera, which is why I'm still on this build
Micahvdm said:
Wakelocks are also a bit of an issue with regards to battery life...and I also work from my phone daily...not just used for camera, which is why I'm still on this build
Click to expand...
Click to collapse
Oh. ?
Micahvdm said:
I'm running 4040 build and the only bug I have is the camera doesn't work...
Click to expand...
Click to collapse
Have you tried this magisk module for the camera ?
Found it on N7P Telegram group
It contains 3 libraries related to camera2 and a SEpolicy rule.
CamFix-Android10.zip
The fix doesn't work and the selinux thing was my discovery. Not a single freeze since. Camera remains broken. Still working on a fix
I'm trying to flash a new android rom to my kindle using this video, but it won't root. The cmd script works fine and it "should" be rooted. Could someone point me in the right directions? Thanks for the help!
Multi-platform 1-Click bootloader unlock for *ANY* 3rd Gen HDX (with VirtualBox)
UPDATE 2022-03-05: Network Access Snafu During the last week or so, a server-side issue caused 1-Click to fail either silently or with a "1-Click needs network access!" message on startup. If you experienced the above, please try again...
forum.xda-developers.com
Dr4g0k1n said:
I'm trying to flash a new android rom to my kindle using this video, but it won't root. The cmd script works fine and it "should" be rooted. Could someone point me in the right directions? Thanks for the help!
Click to expand...
Click to collapse
Flashing a Custom ROM doesn't require current FireOS is got rooted, but flashing a Custom Recovery (e.g. TWRP ) before.
More info here:
Amazon Kindle Fire HD (3rd Generation)
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Kenora_I said:
Multi-platform 1-Click bootloader unlock for *ANY* 3rd Gen HDX (with VirtualBox)
UPDATE 2022-03-05: Network Access Snafu During the last week or so, a server-side issue caused 1-Click to fail either silently or with a "1-Click needs network access!" message on startup. If you experienced the above, please try again...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks! I've already come across this thread, but it says I need to be a member for 2 weeks in order to get a download link.
jwoegerbauer said:
Flashing a Custom ROM doesn't require current FireOS is got rooted, but flashing a Custom Recovery (e.g. TWRP ) before.
More info here:
Amazon Kindle Fire HD (3rd Generation)
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Click to expand...
Click to collapse
I downloaded twrp from the link, but how do I use it?
IMO it's clearly described at the TWRP site linked to above.
Dr4g0k1n said:
I downloaded twrp from the link, but how do I use it?
Click to expand...
Click to collapse
The instructions will be their in the site.
Here is the 1 click zip i got.
Kenora_I said:
Here is the 1 click zip i got.
Click to expand...
Click to collapse
Is this still available?
Looking for a way how to root my Kindle Fire HDX 4.5.5.3 to get Spotify running - any ideas?
beatcooking said:
Looking for a way how to root my Kindle Fire HDX 4.5.5.3 to get Spotify running - any ideas?
Click to expand...
Click to collapse
How to Root Kindle
www.xda-developers.com
xXx yYy said:
How to Root Kindle
www.xda-developers.com
Click to expand...
Click to collapse
This does not seem to work for me - I'm using Mac OS and my Kindle is 3rd Gen