Unfortunately, I updated the tablet at the beginning. After that I recognised that the latest rom is not rootable. So how can I gain root? By reverting to original firmware.....?By factory data reset......?Or it is no way to work around? Thanks for reviewing my question
Solved: I use the offline method to root...
On HD 10, 2017 edition only, you can root all the way up to 5.6.2.0 (the latest known version). If you think it's an update preventing it, go here and download ONLY the firmware for your current version of FireOS from here: https://forum.xda-developers.com/showpost.php?p=74987123&postcount=2 If you are on 5.6.1.0 or later you cannot downgrade so make sure you have the exact correct firmware or you will brick permanently.
DragonFire1024 said:
On HD 10, 2017 edition only, you can root all the way up to 5.6.2.0 (the latest known version). If you think it's an update preventing it, go here and download ONLY the firmware for your current version of FireOS from here: https://forum.xda-developers.com/showpost.php?p=74987123&postcount=2 If you are on 5.6.1.0 or later you cannot downgrade so make sure you have the exact correct firmware or you will brick permanently.
Click to expand...
Click to collapse
Thanks so much! ! I eventually root it using the offline method.
Related
Bought a brand new Fire HD 8, and am assuming it is on 5.0.1. Don't want to connect to the internet right away, because the last thing I want it to do is upgrade to 5.1.2 which means no rooting.
I heard some people saying that downgrading firmware bricks their device, but what about upgrading firmware? My plan is to at least manually upgrade to 5.1.1, which is the latest upgrade able to root. Is there a risk in doing so, or should I just stay on 5.0.1 and root from there? Not sure if there are crucial differences between 5.0.1 and 5.1.1.
Thanks!
ozpearlman said:
Bought a brand new Fire HD 8, and am assuming it is on 5.0.1. Don't want to connect to the internet right away, because the last thing I want it to do is upgrade to 5.1.2 which means no rooting.
I heard some people saying that downgrading firmware bricks their device, but what about upgrading firmware? My plan is to at least manually upgrade to 5.1.1, which is the latest upgrade able to root. Is there a risk in doing so, or should I just stay on 5.0.1 and root from there? Not sure if there are crucial differences between 5.0.1 and 5.1.1.
Thanks!
Click to expand...
Click to collapse
upgrading is fine
Sent from my KFFOWI using XDA Labs
What can i do to solve this problem? is there a way to restore a previous version without rooting it? because i obviously can't do that... N900VVRSEPL1 is the version i have.
See page 3 of "Official Verizon Update???" thread
https://forum.xda-developers.com/verizon-galaxy-note-3/general/official-verizon-update-t3538935
This (PL1) update appears to be a security patch release, so it's probably not surprising that former rooting methods for OB6 & OF1 no longer are working - that's the point of security updates.
Same experience here. I would bet that however these tools are getting root will probably work on PL1. It seems that in running the tools, the tools simply don't recognize PL1 as a working version and don't try. I don't know that for certain, it's just a guess.
LSkeeno said:
What can i do to solve this problem? is there a way to restore a previous version without rooting it? because i obviously can't do that... N900VVRSEPL1 is the version i have.
Click to expand...
Click to collapse
Just get to sammobile and search your device then select 5.0 OF1 and flash whit odin, the it gonna get back again you will get root by using arabicktool. Saludos!!
I am having xt1686 indian variant .. i unlocked the bootloader and installed the custom roms.. now while going back to stock i mistakenly installed NPNS (US VARIANT, I suppose) ..
I am unable to install the NPN version now .. i guess the bootloader is not matching ..
Right now i am having a bootloader - C0.8(*) in NPNS ...
PLEAAE SUGGEST HOW TO MOVE TO INDIAN VERSION OF NPN... THNKS..
S does not mean US or any other variant specific build... there are literally different builds for different variants. My US Retail version is NPN25.173-83
In previous Moto models, the S meant it had been upgraded from an OTA, but in looking in my current device it has received several OTAs and does not have the S, so either that has been depreciated or our original assumptions in earlier models was incorrect.
Either way, the fact the S is there does not mean US (or any other country), just a slightly different build... I don't have an answer of why you can't go back though.
https://forum.xda-developers.com/g5-plus/help/npns-nps-firmware-t3677576
Fastboot NPN25.137-15 build (may be found as brasil-latam)
Lock bootloader (necessary to receive ota) google it
Reboot device
Update phone via ota received in system
Done.
Use this link to download 137-15 build
http://www.stechguide.com/download-moto-g5-plus-stock-firmware/
abhi.a3s said:
Fastboot NPN25.137-15 build (may be found as brasil-latam)
Lock bootloader (necessary to receive ota) google it
Reboot device
Update phone via ota received in system
Done.
Use this link to download 137-15 build
http://www.stechguide.com/download-moto-g5-plus-stock-firmware/
Click to expand...
Click to collapse
Generally, OTA updates can be received with a locked or unlocked bootloader. Only requirement is to have a stock and unmodified system.
However, I personally would caution against downgrading from NPNS firmware to NPN, as you run a risk of hard bricking if you take OTA updates after you've downgraded. As acejavelin has mentioned, the NPNS firmware should reflect OTA/security updates (but seems that Motorola's naming convention is a bit inconsistent), which means your bootloader is likely updated by the firmware. If you've flashed a NPNS firmware, you'd likely be at least on the may security patch. The Indian firmware you'd need is the January patch (NPN25.137-15, as I don't think the NPN25.137-67 or 67-5 firmwares have been leaked). Thus, downgrading to an earlier firmware might give you problems if you then use OTA updates to update. We've already seen a similar situation in the Moto G5 plus unbrick thread.
Instead of reflashing the Indian stock ROM and risking a hard brick, you may wish to look into using the TWRP flashable images which only touch the system.
echo92 said:
Generally, OTA updates can be received with a locked or unlocked bootloader. Only requirement is to have a stock and unmodified system.
However, I personally would caution against downgrading from NPNS firmware to NPN, as you run a risk of hard bricking if you take OTA updates after you've downgraded. As acejavelin has mentioned, the NPNS firmware should reflect OTA/security updates (but seems that Motorola's naming convention is a bit inconsistent), which means your bootloader is likely updated by the firmware. Thus, downgrading to an earlier firmware might give you problems if you then use OTA updates to update. We've already seen a similar situation in the Moto G5 plus unbrick thread.
Instead of reflashing the Indian stock ROM and risking a hard brick, you may wish to look into using the TWRP flashable images which only touch the system.
Click to expand...
Click to collapse
I had same issue.
I unlocked my bootloader when I was on NPN25-137-67, installed custom roms as well. My bootloader got corrupted.
I tried flashing the twrp stock zip but it didn't work.
I know the risks of downgrading and it can hardbrick the device. But since I already downgraded and my fone is still alive I thought it could help him as well. So it's tested. And it did not mess up anything.
About locked/unlocked bootloader, you might be right that ota updates can be received. But since I locked my bootloader and then did the update process. twice. it worked.
Well ofcourse there are lots of ifs so I would also suggest downgrading firmware as a last resort.
P. S. I have xt1686 Indian variant.
---------- Post added at 07:37 AM ---------- Previous post was at 07:31 AM ----------
Twrp images
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Build 67-5
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Credit to rickk
Use vpn if unable to download
abhi.a3s said:
I had same issue.
I unlocked my bootloader when I was on NPN25-137-67, installed custom roms as well. My bootloader got corrupted.
I tried flashing the twrp stock zip but it didn't work.
I know the risks of downgrading and it can hardbrick the device. But since I already downgraded and my fone is still alive I thought it could help him as well. So it's tested. And it did not mess up anything.
About locked/unlocked bootloader, you might be right that ota updates can be received. But since I locked my bootloader and then did the update process. twice. it worked.
Well ofcourse there are lots of ifs so I would also suggest downgrading firmware as a last resort.
P. S. I have xt1686 Indian variant.
---------- Post added at 07:37 AM ---------- Previous post was at 07:31 AM ----------
Twrp images
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Click to expand...
Click to collapse
Okay, when you hard bricked and then used the blankflash, then by flashing the NPN25.137-15 update, you may not have run into any issues as that was the update prior to NPN25.137-67. Thus, you may have been okay as the OTA update simply patched the same files as before. You may also have been able to downgrade without issue as the NPN25.137-67 firmware is only up to the March 2017 patch level.
The opening poster has the different problem of having NPNS25.137 firmware, which at the moment is either NPNS25.137-33-5/NPNS25.137-33-11 or NPNS25.137-35-5 (EU or US firmware) with the May 2017/August 2017 security patch. Downgrading from the May 2017 patch or later and then accepting OTA updates appears to cause a hard brick, especially if you cross downgrade from the NPNS firmware to the Indian firmware: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
echo92 said:
Okay, when you hard bricked and then used the blankflash, then by flashing the NPN25.137-15 update, you may not have run into any issues as that was the update prior to NPN25.137-67. Thus, you may have been okay as the OTA update simply patched the same files as before. You may also have been able to downgrade without issue as the NPN25.137-67 firmware is only up to the March 2017 patch level.
The opening poster has the different problem of having NPNS25.137 firmware, which at the moment is either NPNS25.137-33-5/NPNS25.137-33-11 or NPNS25.137-35-5 (EU or US firmware) with the May 2017/August 2017 security patch. Downgrading from the May 2017 patch or later and then accepting OTA updates appears to cause a hard brick, especially if you cross downgrade from the NPNS firmware to the Indian firmware: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
Click to expand...
Click to collapse
Well ofcourse there is a big potential of hard bricking the device by the method. That's why I said last resort.
So what do you suggest?
TWRP image? And if it doesn't work, he should probably wait up for next NPN build? @toyesh.patra you should consider keeping a custom rom if possible.
Btw
The ota update which I received was August patch. After which I unlocked my bootloader. It was either NPN25.137-67 or NPN25.137-67-5. I'M not sure about version. But it was definitely August patch.
Or maybe I was lucky one time.
Won't do it another time.
anuraag.neo said:
Build 67-5
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Credit to rickk
Use vpn if unable to download
Click to expand...
Click to collapse
For 1686? Full fastboot firmware leaked?
yea, right now i m using the 67-5 build using twrp..
although i wanted to use the 67-5 with locked bootloader.. nevermind ..
psychopac said:
For 1686? Full fastboot firmware leaked?
Click to expand...
Click to collapse
Yes
So if I wanted to go full stock after flashing any custom ROM, all I need to do is flash the 67-5 firmware and I'll be good to go, right?
PS: I'm already on stock and updated to 67-5
psychopac said:
So if I wanted to go full stock after flashing any custom ROM, all I need to do is flash the 67-5 firmware and I'll be good to go, right?
PS: I'm already on stock and updated to 67-5
Click to expand...
Click to collapse
Yes
I can't download it. How Can I download? please upload googel Thanks bro
birkhoffChang said:
I can't download it. How Can I download? please upload googel Thanks bro
Click to expand...
Click to collapse
use search function before asking
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738
Successfully upgraded from 5.6.2.0 to 5.6.3.0 via the misnumbered 5.3.6.4 OTA update. Device had been previously rooted and the first OTA update failed, but I lost root in the process. OTA downloaded a second time and successfully updated to 5.6.3.0.
Root was quickly and painlessly restored following the procedure in this post by retyre:
http://forum.xda-developers.com/hd8-hd10/general/hd-10-2017-offline-rooting-t3734860
Has anyone else confirmed root is successful on the FireHD10? One other user had problems in this forum and could not get root working.
otisw said:
Has anyone else confirmed root is successful on the FireHD10? One other user had problems in this forum and could not get root working.
Click to expand...
Click to collapse
Confirmed. See my post (#140) on here....https://forum.xda-developers.com/hd...ne-rooting-t3734860/post78250635#post78250635
Hi, I've updated my HD 10 with the official 5.6.3.0 version from Amazon and it shows 5.3.6.4 according to the Amazon support this is correct so, the old version was 5.2.
I don't know why but the version before was showing 5.6.2.0 I'm not sure if the support people knows anything about the correct version
Success!!
Hi I accidentally update one of my new Fire HD 10 to 5.3.6.4 which has been rooted while it was on 5.6.1.0. with the offline method by retyre.
It was only 1 attempt and it succeded.
Cool, root methods are still working for the latest update 5.6.3.0 (which I saw there was an update only today, as I have disabled OTA). Any noticeable changes in the latest 5.6.3.0 when compared to 5.6.2.0 in terms of features and speed/performance? (I could not find any release notes on AMZN website).
Cheers!
My firehd10 was rooted with the Kingsport method at 5.6.2.0 and I would like to upgrade to the latest 5.6.3.4. Since the method disables the OTA, how do I upgrade? I've read that the same rooting method works for 5.6.3.4, but don't know how to proceed from wherein am now on 5.6.2.0.
Sent from my KFSUWI using Tapatalk
klausb65 said:
Hi, I've updated my HD 10 with the official 5.6.3.0 version from Amazon and it shows 5.3.6.4 according to the Amazon support this is correct so, the old version was 5.2.
I don't know why but the version before was showing 5.6.2.0 I'm not sure if the support people knows anything about the correct version
Click to expand...
Click to collapse
It's just a typo...real version is 5.6.3.4 :good:
Just want to say great job on the rooting keep it up and wanted to ask if you were going to root the current updated version or if its possible to roll this update back to root the device?
Thanks again
Cod3waX said:
Just want to say great job on the rooting keep it up and wanted to ask if you were going to root the current updated version or if its possible to roll this update back to root the device?
Thanks again
Click to expand...
Click to collapse
If you rolling back the Fire OS version, will cause a brick.
You can root using exploit (follow the step carefully): https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-8-2017-douglas-t3962846
AmznUser444 Dev said:
If you rolling back the Fire OS version, will cause a brick.
You can root using exploit (follow the step carefully): https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-8-2017-douglas-t3962846
Click to expand...
Click to collapse
The rooting thread can be confusing, as the OP assumes an older version of FireOS. It is still easy to root 5.3.7.0 though.
Look specifically at posts 272, 377 and 472 which specifically list which files to download from the OP and have all the steps required to root 5.3.7.0
scoutdriver73 said:
The rooting thread can be confusing, as the OP assumes an older version of FireOS. It is still easy to root 5.3.7.0 though.
Look specifically at posts 272, 377 and 472 which specifically list which files to download from the OP and have all the steps required to root 5.3.7.0
Click to expand...
Click to collapse
im having trouble understanding the thread as it states
NOTE: If you are already rooted, continue with the next step, otherwise get mtk-su by @diplomatic from here and place (the unpacked binary) into amonet/bin folder
STATUS
Confirmed Working
Fire HD 8 7th gen (2017) -- up to Fire OS 5.6.4.0 build 636558520 only
Note that for Fire OS 5, OS version 5.3.x.x is newer than 5.6.x.x.
there is no root my OS/Build ?
I got the error, "This firmware cannot be supported". What do I do?
This means that your device's firmware is not prone to the mechanism used by mtk-su. Check the firmware version and build number of the OS on your device. If your version is higher than that next to your device on the list above, then mtk-su will no longer work on your device. There may be other ways to achieve root. Check elsewhere on the forum.
Cod3waX said:
im having trouble understanding the thread as it states
NOTE: If you are already rooted, continue with the next step, otherwise get mtk-su by @diplomatic from here and place (the unpacked binary) into amonet/bin folder
STATUS
Confirmed Working
Fire HD 8 7th gen (2017) -- up to Fire OS 5.6.4.0 build 636558520 only
Note that for Fire OS 5, OS version 5.3.x.x is newer than 5.6.x.x.
there is no root my OS/Build ?
I got the error, "This firmware cannot be supported". What do I do?
This means that your device's firmware is not prone to the mechanism used by mtk-su. Check the firmware version and build number of the OS on your device. If your version is higher than that next to your device on the list above, then mtk-su will no longer work on your device. There may be other ways to achieve root. Check elsewhere on the forum.
Click to expand...
Click to collapse
mtk-su vulnerability was patch by Amazon, and is no longer a valid method to obtain root on firmware 5.3.7.0.
Download brick-douglas.zip and amonet-douglas-v1.2.zip from the OP. Then from linux, run the steps as outlined in post 377. You do not need to open the tablet.
Amazon messed up the version numbers. 5.3.7.1 is actually the most current firmware version, even though numerically, it comes before the versions that the mtk-su exploit worked on
Ok im not happy at attempting this, i cant afford to brick this tablet
Instead of having to root thru the forums for bits and pieces of information
I would like if someone could give me a dummies guide / rundown to rooting and installing mods to this tablet
It would be very helpful to me and possibly many others
Thanks in advance
Cod3waX said:
Ok im not happy at attempting this, i cant afford to brick this tablet
Instead of having to root thru the forums for bits and pieces of information
I would like if someone could give me a dummies guide / rundown to rooting and installing mods to this tablet
It would be very helpful to me and possibly many others
Thanks in advance
Click to expand...
Click to collapse
What fireOS version are you on? this will be the key to having to open the device or a software exploit. To be clear, you have a 8hd (2017) - Douglas correct?
Michajin said:
What fireOS version are you on? this will be the key to having to open the device or a software exploit. To be clear, you have a 8hd (2017) - Douglas correct?
Click to expand...
Click to collapse
Fire HD 8 7th Gen Running Fire OS 5.6.6.0 (654620620) installed 2nd June
Cod3waX said:
Fire HD 8 7th Gen Running Fire OS 5.6.6.0 (654620620) installed 2nd June
Click to expand...
Click to collapse
You might have to do the hardware option. I seen that kingoroot was rooting the hd10 (2017) so that might be an option if you dont want to open the device.
Attempt to get root with this, dont reboot if is works, Run the first step...
https://forum.xda-developers.com/hd...hd-8-hd-10-t3904595/post82713979#post82713979
or check this out... post #513
https://forum.xda-developers.com/hd...unlock-fire-hd-8-2017-douglas-t3962846/page52
Read through the last few pages...