PLEASE READ ENTIRE THREAD BEFORE ATTEMPTING!! I AM NOT RESPONSIBLE FOR ANY DAMAGE
FILE WAS DOWNLOAD FROM AT&T VIA OTA UPDATE FROM MY MEGA & EXTRACTED FROM THERE - I527UCUBNE7 CFG FILE OTA UPDATE
I only recommend running adb sideload to install.
ADB SIDELOAD DETAILED INSTRUCTIONS
- Make sure USB debugging is ENABLED
- Reboot device into recovery
- Plug device into computer
- Select adb sideload from your devices recovery screen (drivers might need to install, wait for this and then continue)
- load up command prompt for adb
From here I will give examples (adjust according where your file is stored)
As example say I saved my file in my documents folder this would be the command to sideload
adb sideload c:/users/owner/my documents/ATT OTA 4.4 UPDATE.cfg .............you can rename the file whatever you want but I changed the name for confusion as to what it was.
The file will start to load onto the device and show percentage in adb until upload is complete. Once the file is loaded your device will start the update process. If it fails it will show where it stopped at most likely being that a factory file is missing or changed. Everything must be original from previous mr2 firmware.
AGAIN IF YOU REMOVED, MODIFIED, FROZE APPS LIKE KNOX MOST LIKELY YOUR UPDATE WILL FAIL AFTER 25-30%. FOR BEST RESULTS YOUR ROM MUST HAVE ALL ORIGINAL FILES. THIS UPDATE SCANS YOUR FILE SYSTEM TO ENSURE NOTHING HAS BEEN CHANGED. ANY CHANGE WILL CAUSE A FAILURE.
IF YOU GET AN ERROR DURING UPDATE - INSTALL INSTRUCTIONS IF YOU GET AN ERROR
- Download mr2.tar.md5 file located in my signature under galaxy mega repository
- Install via Odin & make sure "Auto-Reboot" is UN-CHECKED
- Once install is finished reboot device into recovery
- Select adb sideload install then follow the steps above to install update via sideload
THIS UPDATE IS NOT ROOTED OR UNLOCKED. INSTALLING WILL CAUSE YOU TO LOOSE ROOT!!
IF YOURE NOT SURE WHAT YOUR DOING - DONT DO IT - RECOMMEND REMOVING BUSYBOX - ROOT BEFORE INSTALL -
AT&T I527UCUBNE7 OTA UPDATE - CFG FILE - DROPBOX CURRENTLY DOWN DUE TO CONGESTION
- GOOGLE DRIVE LINK - I527UCUBNE7 OTA UPDATE - GOOGLE DRIVE LINK -
- MEGA LINK - I527UCUBNE7 OTA UPDATE - MEGA LINK -
AGAIN USE AT YOUR OWN RISK.
Can I remove apps and flash?
updated no problems but now i have no touch on the screen. no buttons light up or nothing. has anybody else ran into this problem.
thanks
hedgehogmd said:
updated no problems but now i have no touch on the screen. no buttons light up or nothing. has anybody else ran into this problem.
thanks
Click to expand...
Click to collapse
did you run update while your phone was rooted?
KDKobes said:
did you run update while your phone was rooted?
Click to expand...
Click to collapse
No i did a full system reload with Odin then applied the OTA. everything went fine no errors rebooted and no touch.
hedgehogmd said:
No i did a full system reload with Odin then applied the OTA. everything went fine no errors rebooted and no touch.
Click to expand...
Click to collapse
I have seen this happen before. Which "full system reload file" did you use and where was it downloaded? Usually is fixed by re-installing a lower version rom then reapplying the update. I would recommend reinstalling the official rom if thats what you used if you can. This would be the mr2 tar.md5 file in odin. Which way did you install update? Did you try reinstalling the update?
*currently uploading stock official att mr2.tar.md5 to my repository. File should be up shortly*
KDKobes said:
I have seen this happen before. Which "full system reload file" did you use and where was it downloaded? Usually is fixed by re-installing a lower version rom then reapplying the update. I would recommend reinstalling the official rom if thats what you used if you can. This would be the mr2 tar.md5 file in odin. Which way did you install update? Did you try reinstalling the update?
*currently uploading stock official att mr2.tar.md5 to my repository. File should be up shortly*
Click to expand...
Click to collapse
i replaced the screen about 4 months ago with a aftermarket lcd assy and i had to hookup my cracked factory screen boot phone the plug in my aftermarket screen and touch works.
My phone is unlocked. If I do this, what are the chances I lose that unlock?
I updated to 4.2.2 via Kies and didn't lose the unlock, so curious about this.
kwed73 said:
My phone is unlocked. If I do this, what are the chances I lose that unlock?
I updated to 4.2.2 via Kies and didn't lose the unlock, so curious about this.
Click to expand...
Click to collapse
I updates and didn't lose my unlock
Is someone working on a odin version of this update
Great!
Wow..... I have been here and there before I got here. It worked flawlessly!
Related
I unrooted my phone yesterday along with uninstalling Freedom and ended up updating my phone this morning. Now I can't connect to any gapp because it seems like this is a common problem when you uninstall this app. Now I can't reroot my phone again because I got an update and didn't know that it was patched. How can I do this without reinstalling the stock rom?
http://forum.xda-developers.com/showthread.php?t=2110225
Another Way Playstore not working after Installing/Uninstalling Freedom App?
- Go to Root Explorer and Mount R/W then delete Hosts file under system/etc/
- Reboot
- Shutdown & Boot to Recovery
- Wipe Cache/Dalvik Cache
- Reboot
- Presto! back to normal.
My phone is a AT&T Samung Galaxy S5 Active.
evantheis said:
I unrooted my phone yesterday along with uninstalling Freedom and ended up updating my phone this morning. Now I can't connect to any gapp because it seems like this is a common problem when you uninstall this app. Now I can't reroot my phone again because I got an update and didn't know that it was patched. How can I do this without reinstalling the stock rom?
http://forum.xda-developers.com/showthread.php?t=2110225
Another Way Playstore not working after Installing/Uninstalling Freedom App?
- Go to Root Explorer and Mount R/W then delete Hosts file under system/etc/
- Reboot
- Shutdown & Boot to Recovery
- Wipe Cache/Dalvik Cache
- Reboot
- Presto! back to normal.
My phone is a AT&T Samung Galaxy S5 Active.
Click to expand...
Click to collapse
Which update did you take? The NG3 one? If so, the only option is to downgrade to NE4 with Odin.
es0tericcha0s said:
Which update did you take? The NG3 one? If so, the only option is to downgrade to NE4 with Odin.
Click to expand...
Click to collapse
I'm not sure if i'm fully understanding what you're saying? I'm on stock firmware and it was an AT&T update that popped up and said there was a new update. This update patched towelroot and I can't find a stock firmware that isn't through rapid gator since that is taking 3 hours for only 15 MBs and I have good internet. Is there a way to trick an app thinking it got root access so I can delete the file?
evantheis said:
I'm not sure if i'm fully understanding what you're saying? I'm on stock firmware and it was an AT&T update that popped up and said there was a new update. This update patched towelroot and I can't find a stock firmware that isn't through rapid gator since that is taking 3 hours for only 15 MBs and I have good internet. Is there a way to trick an app thinking it got root access so I can delete the file?
Click to expand...
Click to collapse
You need to check which update you are on. Settings > About Phone > Build Version > Does it end in NG3? If so, you have to downgrade to the one that ends in NE4. You can't trick apps into root access.
So i recently just got my system update settings back after a minor mishap where the apk went missing. So the problem i am having is that when i try to download the 12B update since im still in 11C however the download fails. And im slightly confused as to why the update fails on the download seconds after clicking download now
ToF_Itachi said:
So i recently just got my system update settings back after a minor mishap where the apk went missing. So the problem i am having is that when i try to download the 12B update since im still in 11C however the download fails. And im slightly confused as to why the update fails on the download seconds after clicking download now
Click to expand...
Click to collapse
Have you done ANY modification of the system files (freezing) or did you bump (install TWRP)? If you installed TWRP, you cannot take OTAs and install them. You must be on the stock recovery.
iBolski said:
Have you done ANY modification of the system files (freezing) or did you bump (install TWRP)? If you installed TWRP, you cannot take OTAs and install them. You must be on the stock recovery.
Click to expand...
Click to collapse
Actually i managed to fix it myself had to go through a long 2 hour factory reset and reflashing using the flash tool just to get the update to work. But thanks for replying :good::fingers-crossed:
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
If you have this exact problem, unbrick instructions here:
Try using Phone Flash Tool from the Dell site, and this zip:
https://mega.co.nz/#!Vgw1CTYT!y1_tSTCMmzrhJSQy0lxwY59iyRhdJovC-IDMF25PB4k
It's the new boot firmware binaries packed in the developer edition firmware zip with the xml changed to point to the new files.
For the flashing process of this zip, start with the tablet completely off and disconnected, then in Phone Flash Tool, load the zip file, click "Start to flash" (the button near the bottom should be blue/clickable), then once it's counting attempts (attempt #0, attempt #1, etc.) then connect USB. It should proceed to flash.
Click to expand...
Click to collapse
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
xBIGREDDx said:
I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
What is the process to unroot on our device?
Install es file explorer or root explorer.
Grant root access to the app.
in es you need to enable root explorer in the settings menu.
Go to
Code:
/system/bin
delete su (mine was not locate in here)
/system/xbin
delete su (mine was here)
/system/app/Superuser.apk delete this
SuperSu has a selection of uninstall options in the app's menus.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
I've applied plenty of OTAs in the past to other devices on top of rooted systems, and never had a problem as bad as bootlooping.
(Not saying it's not my fault, as I knew there was a risk, I guess I was just running on a series of good luck, or maybe other companies write better OTA pre-checking features.)
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
kage69 said:
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
Click to expand...
Click to collapse
It's hard to say, as lollipop was just released, only you guys with lollipop can test and see.
Neither SDC nor myself have lollipop so we can't test.
sent from my kingSing T1 via taptalk
On mine, I forgot to un-root with no issues, but it defaults to encrypting the tablet and now I can't re-root.
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
old root method dont work :crying:
kage69 said:
old root method dont work :crying:
Click to expand...
Click to collapse
Well you tried, did you get an error? Can you give more details?
sent from my kingSing T1 via taptalk
xBIGREDDx said:
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
ely105 said:
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
Click to expand...
Click to collapse
@kage69 says no, only you guys with lollipop can confirm or deny if root works or not.
sent from my kingSing T1 via taptalk
the tool flashes temp cwm but the tab dont boot to recovery
stays in bootloader where you can choose boot normal, power down and recovery
choosing recovery boots to stock recovery
there were errors while flashing, ill post them tomorrow
reading a book in bed on my lollipopped tab now
hope we can root it again, need that for customizations and airaudio
see u tomorrow
So how were you able to flash after bootlooping the first time when you tried to update with root? I cannot get into the bootloader or anything :silly:
Does any one have the ota so I can patch the stock firmware to investigate rooting it?
might be stored in cache i think
cant get to that without root
kage69 said:
might be stored in cache i think
cant get to that without root
Click to expand...
Click to collapse
Yeah I we hoping someone captured it before updating
xBIGREDDx said:
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
Click to expand...
Click to collapse
Exactly which binaries did you flash back? In the zip I see:
dnx_fwr_ann_a0-mofd_v1.bin
dnx_fwr_ann_a0-mofd_v1-DBG.bin
dnx_fwr_blackburn_preqs_preqs.bin
dnx_fwr_blackburn_qs_qs.bin
dnx_fwr_preqs.bin
dnx_fwr_qs.bin
ifwi_ann_a0-mofd_v1.bin
ifwi_ann_a0-mofd_v1-DBG.bin
ifwi_preqs.bin
ifwi_qs.bin
I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
DroidDogg said:
I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
Click to expand...
Click to collapse
Be happy 4.5.5.1 didn't take when SafeStrap recovery was installed; device would have bricked. Assume you used the Safestrap compatible variant of 4.5.2 (here). After flashing that (stock slot only; never use secondary slots in SS v4) reboot device and remove Safestrap recovery via SS app. Power down and boot into stock recovery via <power>+<vol-up> and perform a factory reset (you'll loose all apps/data). Reboot again and initialize FireOS. It should then accept OTA updates.
Be 100% sure Safestrap recovery is uninstalled prior to doing a factory reset.
Curious - why to you want 4.5.5.1? Offers no advantage over 4.5.2 if running custom ROMs. Nor will it automatically update to FireOS v5 as Amazon has no plans to release a v5 update for 3rd gen devices.
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
DroidDogg said:
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
Click to expand...
Click to collapse
DroidDogg said:
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
Click to expand...
Click to collapse
IDK - should work. You can try downloading the latest version of FireOS here; installation instructions here. Also verify OTA apk is installed and properly named (here).
It's likely 4.5.x is the terminal release of FireOS for 3rd gen devices; potential buyers will not be severely disadvantaged on 4.5.2.
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
As previously posted - IDK and I do not think anyone else does either. What I do know is every flash (some which appear questionable) presents another failure opportunity that could yield an unrecoverable device. Keep experimenting and posting results; others will learn from your efforts. Just recognize the risk and know when to say 'good enough'. Pushing from 4.5.2 to 4.5.5.1 buys you no additional capability/functionality/stability at this time.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
Do you checked if the DeviceSoftwareOTA.apk is there? (which @Davey126 mentioned above).
I was in the same situation and had to rename it back, which I'd renamed before as described in the OTA blocking tutorial. http://forum.xda-developers.com/showpost.php?p=59160158&postcount=1
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
mzk1 said:
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
Click to expand...
Click to collapse
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Davey126 said:
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Click to expand...
Click to collapse
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
mzk1 said:
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
Click to expand...
Click to collapse
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Davey126 said:
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Click to expand...
Click to collapse
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
mzk1 said:
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
Click to expand...
Click to collapse
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Davey126 said:
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Click to expand...
Click to collapse
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
mzk1 said:
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
Click to expand...
Click to collapse
Yep - that would be my choice too. Take note there are two Nexus builds, one for devices that have a 4.5.5.1 kernel, the other for older kernels. Try the former first as it as actively maintained and has a broader feature set. Links below:
old: http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-v4-0-1-t3125808
new: http://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
Currently rooted and on 5.2.7.3 but having issue with single sign on apps not working as well and NBC.
NBC saying that I need the latest software.
I unblocked the updates and let it do a system update, and rebooted and then it tries to get 5.2.7.4.
So it is updated as much as it can be as far as I know.
I think I can use TWRP to flash 5.2.7.4 and then magisk and still remain rooted if I read that correctly.
I just can't find this OS anywhere.
Can someone please help..??
mytunes said:
Currently rooted and on 5.2.7.3 but having issue with single sign on apps not working as well and NBC.
NBC saying that I need the latest software.
I unblocked the updates and let it do a system update, and rebooted and then it tries to get 5.2.7.4.
So it is updated as much as it can be as far as I know.
I think I can use TWRP to flash 5.2.7.4 and then magisk and still remain rooted if I read that correctly.
I just can't find this OS anywhere.
Can someone please help..??
Click to expand...
Click to collapse
If you unblocked the updates, the ota updater should download the update (bin) file to the box.
Wait until the update app says that the download is 100% ready, reboot into TWRP and take a look at cache partition for the bin file (with TWRP file manager).
PS: If you flash that update, root is probably gone, maybe you brick the box...
Sus_i said:
If you unblocked the updates, the ota updater should download the update (bin) file to the box.
Wait until the update app says that the download is 100% ready, reboot into TWRP and take a look at cache partition for the bin file (with TWRP file manager).
PS: If you flash that update, root is probably gone, maybe you brick the box...
Click to expand...
Click to collapse
Thank you!
And maybe i'll wait for the prerooted version LOL