Ominous screen after downgrading and installing recovery - Fire TV Q&A, Help & Troubleshooting

I rooted a new aftv last night and all went smooth. Today downgrading and installing cwm very different story.
My aftv now boots to a plain screen displaying the time (incorrectly), a lock symbol and the word "charged" I'm not sure which scared me more. But I'm not bricked. I could still connect with adb and reboot recovery. AND if I hadn't panicked I would've found out sooner that pressing the context menu key on remote takes me right back to the homescreen.
I swear I followed the guides on aftvnews (well done btw!) But every time there was a "if this happens" stipulation in the guides, it happened to me. I can't say it was hard but it was tedious.
Now my issue to I've pushed the correct Rom.zip to my sd card, rebooted recovery but the install fails with this error--Assert failed !less_than_int getprop ro.build.date.utc
I might be missing critical details here to help with diagnosing. Sorry. I've got to work. That process took way longer than expected. I'm hoping it might be enough info to get some ideas. I'll try to check back here later. Thanks.

KLit75 said:
I rooted a new aftv last night and all went smooth. Today downgrading and installing cwm very different story.
My aftv now boots to a plain screen displaying the time (incorrectly), a lock symbol and the word "charged" I'm not sure which scared me more. But I'm not bricked. I could still connect with adb and reboot recovery. AND if I hadn't panicked I would've found out sooner that pressing the context menu key on remote takes me right back to the homescreen.
I swear I followed the guides on aftvnews (well done btw!) But every time there was a "if this happens" stipulation in the guides, it happened to me. I can't say it was hard but it was tedious.
Now my issue to I've pushed the correct Rom.zip to my sd card, rebooted recovery but the install fails with this error--Assert failed !less_than_int getprop ro.build.date.utc
I might be missing critical details here to help with diagnosing. Sorry. I've got to work. That process took way longer than expected. I'm hoping it might be enough info to get some ideas. I'll try to check back here later. Thanks.
Click to expand...
Click to collapse
There's been a few people who have reported the lockscreen oddness. Once you install the update and do a factory reset it will be fine. As for the error, you are not using the correct update. You need to use the prerooted roms.

rbox said:
There's been a few people who have reported the lockscreen oddness. Once you install the update and do a factory reset it will be fine. As for the error, you are not using the correct update. You need to use the prerooted roms.
Click to expand...
Click to collapse
Not being home right now...But following the guide and working from memory...I've got the latest cwm, unlocked boot loader and running 51.1.2.0, my next step would've been to flash
51.1.4.0
If those steps are accurate then from the info I put in the op, I did not install 51.1.4.0 and that's why it failed. I'll bet you're right but I'm pretty sure I pushed the correct version.
It's a bit confusing but doesn't this version require your boot menu. I'm fairly certain the newest cwm does need it. So assuming I pushed the correct version of prerooted fw...would not having boot menu cause the install to fail. Or maybe it's 2 errors on my part but I do remember downloading 51.1.4.0
Thanks a lot! It's in everyone's best interest you don't spend time assisting people like me with something that's probably simple. So if anyone has a comment on my posts please share.

KLit75 said:
Not being home right now...But following the guide and working from memory...I've got the latest cwm, unlocked boot loader and running 51.1.2.0, my next step would've been to flash
51.1.4.0
If those steps are accurate then from the info I put in the op, I did not install 51.1.4.0 and that's why it failed. I'll bet you're right but I'm pretty sure I pushed the correct version.
It's a bit confusing but doesn't this version require your boot menu. I'm fairly certain the newest cwm does need it. So assuming I pushed the correct version of prerooted fw...would not having boot menu cause the install to fail. Or maybe it's 2 errors on my part but I do remember downloading 51.1.4.0
Thanks a lot! It's in everyone's best interest you don't spend time assisting people like me with something that's probably simple. So if anyone has a comment on my posts please share.
Click to expand...
Click to collapse
The only way to get the ro.build.date.utc failure is by using a stock package. My prerooted roms simply do not have that check in them. It fails on that line precisely to prevent people from installing stock packages.

rbox said:
The only way to get the ro.build.date.utc failure is by using a stock package. My prerooted roms simply do not have that check in them. It fails on that line precisely to prevent people from installing stock packages.
Click to expand...
Click to collapse
Thanks a lot! You probably saved me a lot of time trying to figure out where I went wrong. When I get home I'll delete the Rom I pushed, push the correct one, if it installs right I think my next move is your boot menu. But I'll double or triple check that later on tonight.
Edit--install 51.1.4.0 updated version then, if I follow correctly, I can install the latest prerooted fw.

I did everything I said I was going to do and it went smoothly. I'm now running prerooted 51.1.40
There's just one thing. I was certain I unlocked bootloader earlier today. From what I know it's not possible to have the latest cwm with a locked bootloader. But when I clicked unlock bootloader in adbfire (the program I use for my other aftv) it says "bootloader not unlocked"
So I was second guessing myself. But couldn't explain how I missed it and still had the latest cwm. I checked and aftv-unlock was there in my adb folder. I wouldnt have put it there if I didn't transfer it. But to be on the safe side I went back into the terminal and unlocked my bootloader (I believe for the 2nd time). THEN i hit the unlock bootloader on adbfire again and it still returns with "bootloader not unlocked"???
Is it because busybox was not installed through adbfire? If I use it on my other aftv it says "bootloader unlocked" so the software definetly can confirm it. It's just not...
Normally I'd go ahead and install rbox's boot menu then the latest firmware, but many more things have gone wrong in the last 24 hours (not tragically wrong) but just enough for me to wait for an answer on this and maybe stop for the night. Everything's working great (knock-wood) but I assume when rbox finishes android tv I'll need the boot menu. So I'll wait here patiently for both. Thanks.

Related

EVO 2.2 UPDATE (Froyo), HELP !!!

Guys,
My Evo says Froyo 2.2 is avail for download when I check HTC Updates... I hit accept, it downloads, then asks if I want to install NOW... I HIT YES, and it takes me to the boot loader page, THEN DOES NOTHING.. It doesn't boot into recovery mode like it is supposed to, and it just sits on the Boot loader screen, NO TRIANGLE, NO BAR on the bottom showing the progress, IT JUST SITS THERE on the boot loader page with the 3 Androids on the bottom... I have already tried to hard reset the phone, BUT that didn't work... PLEASE HELP !!! Is there a way to HARD reset my EVO BACK to BEFORE ALL OF THE UPDATES??? IS THERE A WAY TO Force boot into recovery to apply the "update.zip" ??? Please advise...
Mine did'nt go no where near the bootloader screen...
I hit the download...then it just installed like any other app...except it brought me to a bar progress page a couple of times. Then the phone rebooted and whala...froyo.
I must say this...I was previosly rooted but unrooted to do it!!!
Are you rooted or unrooted to start off with?
Was rooted, but then I did the "update of June 29th" and ruined ALL of my fun... Is there even a way for me to root my phone now??? How do I get it to go into recovery?
Same issue
My EVO ISN'T ROOTED, and I'm having the same exact problem
You're hosed root wise until someone cracks the rom, if they crack the rom. Most likely you'll need to update to the official version once HTC releases an upgrade as they claimed they would eventually do on Twitter.
im not trying to root my phone, i just want froyo
right, I WAS rooted, the update in JUNE fixed that for me =(... NOW I just want FROYO which is available from Sprint/HTC OTA, it just wont install?????????? I think I can install it as an update.zip if I could get my phone into RECOVERY mode... When at the bootloader, if I hit Recovery, it just boots back to the BOOT LOADER????
I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
This is the route I took and was just like you...I had no probs this way!
This is a great recommendation, but I haven't done any ROOT or ROMing to my phone since I've owned it, I've stayed true to the true image they released, and I'm not comfortable downgrading it to some other image that wasn't on the phone. I attempted to do the instructions outlined and I was unable to get pas the stage of pushing the:
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459
to the phone. It says USB error, and I have debugging mode enabled.
cardiox said:
I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
This is the route I took and was just like you...I had no probs this way!
Click to expand...
Click to collapse
I RE-Loaded this version, as the other "older" versions would not work (re-loaded, as this is what I already HAD on my phone)... It wiped the system, and ALL of my info/apps (make sure you back up) and then I was able to do the Froyo Update... YES !!!! Thanks...
http://shipped-roms.com/shipped/Sup...51.1_Radio_2.05.00.06.10_release_CL195459.exe
I did the same, thank you !
No prob...have fun!!!
Froyo Update Won't Install
To start off - I have never rooted my evo - my phone is running Android 2.1 update 1 supersonic - and I did not try to do the "pre-release" update put out by HTC. Since late last night, I have been trying to install Froyo through system updates (settings, system updates, htc software update). I am able to download the upgrade, which is about 80 MB, but for some reason the update will not install. When I click install now, my phone restarts in the bootloader. If I click on fastboot, it searches for an image on my SD card but can't find one. If I hit recovery, it just returns me to the main bootloader screen. The only thing I can do is reboot or shut down my phone. When my phone boots back up, it says the update is downloaded and ready to be installed. I have tried redownloading the update but the same thing happens. Any help would be appreciated, preferable without losing contacts and apps. I'm trying to save a factory reset for a last resort.
Thanks,
Nick
Nick,
Please read the earlier posts, and follow the link from Cardiox... He said the following...
"I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-...urn-stock.html
This is the route I took and was just like you...I had no probs this way!"
Then read my posts, and you will see that I had the SAME problem you are having, and this worked for me... I posted the thread... It is pretty easy if you follow the instructions... Let me know if it works for you... Good luck !!!
wolverinexc said:
To start off - I have never rooted my evo - my phone is running Android 2.1 update 1 supersonic - and I did not try to do the "pre-release" update put out by HTC. Since late last night, I have been trying to install Froyo through system updates (settings, system updates, htc software update). I am able to download the upgrade, which is about 80 MB, but for some reason the update will not install. When I click install now, my phone restarts in the bootloader. If I click on fastboot, it searches for an image on my SD card but can't find one. If I hit recovery, it just returns me to the main bootloader screen. The only thing I can do is reboot or shut down my phone. When my phone boots back up, it says the update is downloaded and ready to be installed. I have tried redownloading the update but the same thing happens. Any help would be appreciated, preferable without losing contacts and apps. I'm trying to save a factory reset for a last resort.
Thanks,
Nick
Click to expand...
Click to collapse
I am not a genius by no means thus I am only sharing info that I have from personal trial and error. If you are going to a bootloader screen during this update process and your SD card is mounted then you most likely will need to bite the bullet and either do a factory reset or follow the link instructions so given. For some reason this update can not find the original factory code or RUU that it is trying to update. Sounds like your SD card is mounted but it can't find it...I would strongly consider just starting over with that link program. It does not root you it just puts you back square one with factory code. Then the update will have something to build off of...which you apparently don't have for whatever reason.
Ok, this is what I needed to know. I'm backing up my stuff with bitpim and will just do this. Thanks for all the help and the speedy responses!
-Nick

[Q] ITL41F OTA failed ... won't retry

Got the OTA today. Bog stock not rooted. update failed. After about 30 minutes a retry download button appeared. Pushing it doesn't do anything. Is there a minimum wait between update attempts? Any other ideas?
Same thing happened to me. I have waited 3 days for a repeat but to no avail. I rooted it and installed a custom ROM with the volume fix update in.
http://twitpic.com/7oody4 this?
Mine failed too... mine was just rooted; nothing else
I got the little Android logo with a !
Rebooted again, no update appears; so I decided to just put the update myself.
Twitpik link is broke. Didn't fail during reboot though. Error msg is right in the system update page. The dowload progress bar is grayed out and it says dowload failed instead a percent progress and there is Retry Download button lower right but it doesnt seem to do anything.
texiandave said:
Twitpik link is broke. Didn't fail during reboot though. Error msg is right in the system update page. The dowload progress bar is grayed out and it says dowload failed instead a percent progress and there is Retry Download button lower right but it doesnt seem to do anything.
Click to expand...
Click to collapse
Mine downloaded automatically over night, and asked if I wanted to apply it when I woke up at 6am. Twitpic should work btw, I just looked at it
Mine even said it was downloaded AND verified, but still failed
Rooted on stock rom with CWM.... Without the stock recovery it can't install. Just jumped to a new Rom with the update....I have always hated the auto updates..lol
Is there a way for me to apply this update by itself? Even if I don't have stock recovery? Is it possible to re-set recovery to original without wiping the entire device?
Mine is rooted, stock ROM, CWM recovery.
OTA re-set itself and installed correctly overnight without me doing anything. Not sure why it failed or how it resolved it but it's done.
If you're still having issues try this
http://www.coolsmartphone.com/2011/12/01/galaxy-nexus-ota-patch
Basically its links to the patch (OTA) and how to root/return to stock with a link to the guide on xda
Sent from my Galaxy Nexus using Tapatalk
I eventually received the update. It downloaded and asked for a reboot. I agreed and the phone counted down, then shutdown, but didn't startup. I waited and waited, the power button would not respond, so I removed the battery, and put it back in. It then started up, but still on the old ITL41D software. What did I do wrong? And what do I do now? Is it normal for it to fail to start up aftrr the reboot? Will I get another opportunity?
Sorry for all the questions, but I'm super frustrated
mirilo said:
I eventually received the update. It downloaded and asked for a reboot. I agreed and the phone counted down, then shutdown, but didn't startup. I waited and waited, the power button would not respond, so I removed the battery, and put it back in. It then started up, but still on the old ITL41D software. What did I do wrong? And what do I do now? Is it normal for it to fail to start up aftrr the reboot? Will I get another opportunity?
Sorry for all the questions, but I'm super frustrated
Click to expand...
Click to collapse
Is your phone rooted? If so, I would look at the comment above yours with the link to the patch (and instructions) to flash it manually. If it is not, it will likely allow you to retry in a day or two.
Hope it all works out for you.
EDIT: I just tried flashing the patch manually as per the prior instructions posted and it didn't work. It gave me "Error (Status 7)" and aborted the installation. Although, right when it rebooted back into the home screen, it came up with the official OTA update again. I'm hesitant on trying it again, since it's likely to fail due to whatever reason caused it to fail the first time.
Either way, this is getting aggravating. I really wish there was an easier way to get this patch without needing to lose root and having to re-do things all over again. I have done a TiBu batch run of all of the stuff I need, but still...oh well.
FlareHeart said:
Either way, this is getting aggravating. I really wish there was an easier way to get this patch without needing to lose root and having to re-do things all over again. I have done a TiBu batch run of all of the stuff I need, but still...oh well.
Click to expand...
Click to collapse
Don't think I've ever seen an OTA which left root intact. This occurs when the OTA sets the permissions recursive for the whole directory /system/bin to 755 removing the setuid attribute on the /system/bin/su binary.
The binary will still be there, but will have to have the setuid attribute added back, chdmod 4755, which will then return root.
Does seem odd Google allows the device to be unlocked, but yet unlocked devices get root access wiped. If they claim to want open source and open devices, perhaps they could script an exception for root access and not remove it with every OTA.
Normally, when Error status 7, or any other recovery error, we're in a custom recovery with adb access and can pull the log at /tmp/recovery.log or /cache/recovery.log and examine what caused the issue as more output is stored there than presented on the screen to the user.
Perhaps googling this recovery error code or grabbing the open source from AOSP will show generally what causes it.
Does seem odd the issues other users have had *automatically* cleared themselves after waiting a while.
First idea which comes to mind is perhaps the original OTA had a bug in the scripting and they were slowly replacing and pushing out the updated OTA.
Keep us updated! I'm on the samsung version of ics so I'll probably have to manually push over all the images...but good to keep up with the *official* route.
When trying to install my update, I get signature verification failed in recovery.
Any ideas?
EDIT: Flashed the recovery posted in the Image on Googles site.
Fixed the problem for me.
joeykrim said:
Keep us updated! I'm on the samsung version of ics so I'll probably have to manually push over all the images...but good to keep up with the *official* route.
Click to expand...
Click to collapse
Not technically official, but a MUCH easier way to get the patch and keep all of your settings and root can be done using the slightly modified stock ROM from bigxie (link: http://forum.xda-developers.com/showthread.php?t=1372376)
If you clear just the cache and dalvik, then flash this. You get the patch, SU, and busybox, without losing all of your settings or data.
Worked great for me. Hope that helps!

[Q] Quick question about stock recovery

Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
Yes you can go to software number to get the info you need. To do an OTA you need a stock sense ROM (NO CHANGES TO ANY SYSTEM APPS) you then need to flash the correct recovery for your software number and [IMPORTANT] relock the bootloader. You then can reboot into your system and take the OTA while still being able to unlock the bootloader and flash a custom recovery afterwards.
No need to relock the bootloader for an ota. People should stop spreading that info
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
ericksonline said:
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
Click to expand...
Click to collapse
Yup you're good ROM wise. Just flash the stock recovery and you should be good to go.
You can be unlock and have OTA.
You just need a stock recovery.
HTC ONE M8 fails to load up after failed software update
Hello guys, this is my first post. I really need your help as I'm at risk of loosing all my phone data. My phone internal memory had been exhausted and I bought an external SD card. I am unable to transfer data to the external SD card. I was doing a software update on my phone that failed to install, there was a warning sign on the phone screen for a few minutes then it try to power on but has failed, as it's seem to stuck on the screen that display htc powered by android. I tried the recovery holding down the power button and the column up button, the phone power off and back on but is still stuck on this screen (htc powered by android). I tried connecting the phone to my laptop to try and recover my data, but it's not mounting to the laptop. Please can someone help me. Thanks in advance.
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
jbarr3 said:
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
Click to expand...
Click to collapse
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
ericksonline said:
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
Click to expand...
Click to collapse
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
jbarr3 said:
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
Click to expand...
Click to collapse
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
ericksonline said:
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
Click to expand...
Click to collapse
Thanks erick but given what's happened I don't think I'll ever update from the playstore again. I'll load 2.16 using TWRP and report back. I can't stress enough how important it is to have a nandroid backup. I reckon its the best reason to load a custom recovery. Its got me out of trouble twice now and gives me piece of mind. I've actually gone overboard on this and I have two backups on my phone which I have copied to my PC..
vm54 said:
You can be unlock and have OTA.
You just need a stock recovery.
Click to expand...
Click to collapse
And stock ROM.
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
jbarr3 said:
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
Click to expand...
Click to collapse
Awesome! I'm glad to hear that it worked!

Trying to go from 4.4.4 to 5.0.2... NOT WORKING

OK, I have spent the last 2.5 hours reading/pushing buttons, and I'm going in circles. I had my N7 rooted with TWRP (using wugfresh), on 4.4.4.
As of right now. I believe I'm unrooted (using SuperSU), and then again using the WugFresh app. I downloaded the 5.0.2, tried booting into TWRP and installing, but it wouldn't see the zip. Read the forums, and came across people suggesting to extract the "system.img", still not working.
Because I believe i'm unrooted, I tried to let the OTA updater do its thing. After downloading, it says "rebooting", then it boots straight to TWRP. EVERYTIME. I'm sure I've tried a few other things, but at this point It's late, and I'm tired. I'm willing to just completely start from scratch. Yes, I'd be willing to set the boot system back, get rid of TWRP, and completely start with a "new system".
Please ask any questions you need to get more info, or point me to some tuts that will help, as i'm sure I misses a few that probably point out exactly what i'm looking for.
Thanks everyone!
DataGnome said:
OK, I have spent the last 2.5 hours reading/pushing buttons, and I'm going in circles. I had my N7 rooted with TWRP (using wugfresh), on 4.4.4.
As of right now. I believe I'm unrooted (using SuperSU), and then again using the WugFresh app. I downloaded the 5.0.2, tried booting into TWRP and installing, but it wouldn't see the zip. Read the forums, and came across people suggesting to extract the "system.img", still not working.
Because I believe i'm unrooted, I tried to let the OTA updater do its thing. After downloading, it says "rebooting", then it boots straight to TWRP. EVERYTIME. I'm sure I've tried a few other things, but at this point It's late, and I'm tired. I'm willing to just completely start from scratch. Yes, I'd be willing to set the boot system back, get rid of TWRP, and completely start with a "new system".
Please ask any questions you need to get more info, or point me to some tuts that will help, as i'm sure I misses a few that probably point out exactly what i'm looking for.
Thanks everyone!
Click to expand...
Click to collapse
UPDATE: I figured it out. I just did the "flash to stock", and told it to use 5.0.2, as the stock image. All good.

Help needed after upgrade to 51.1.5.0_515030720

So, the other day i have started on rooting the AFTV of a friend of mine. i rooted mine a while ago and was comfortable enough to do it for someone else.
was following the AFTVnews.com guide (very well organized site and i would say a wiki for all aftv users). the initial version on the box was 51.1.0.1. have succesfuly rooted it, installed customer recovery, busybox, bootmenu, etc, all as per the guide. have upgraded it to 51.1.4.0_514006420 updated succesfuly as well again using aftvnews.com after which have installed the busybox again. now here the strange things happen. have decided to keep upgrading it to the latest version 51.1.5.0_515030720, according to the description i could upgrade straight to this version from 51.1.4.0_514006420. followed the same upgrade procedure and after the reboot in CWM i get the Amazon Fire TV logo and doesnt do anything, left it for about 10 min - nothing. power cycled it still the coloured logo. which means somehow it got software bricked.
started to google the ways of unbrick it and followed the procedure with the USB keyboard, it worked well for me. i got in to CWM recovery and did factory reset after which reboot. no luck, still showing the coloured logo.
got back in to recovery using the same USB keyboard method and did again factory reset after which decided to install the 51.1.4.0_514006420 updated custom ROM again which was already on my sdcard.
installed successfully, rebooted and started to configure the brand new aftv box - language, network, register, etc. after all this got on home screen, system to find out that it has the stock 51.1.4.0 version (51.1.4.0_user_514006420). what is interesting that the supersu is already there but without the option to launch it, only force stop, clear data and cash.
tried towelroot but obviously no luck, it sais your phone is not supported. so i guess that's it, no more root for me.
where the hell i missed it? i followed every step carefully.
and why in the first place after upgrade from 51.1.4.0_514006420 to 51.1.5.0_515030720 i got bricked?
please tell me there's still hope to root it.
Update: despite the fact that towelroot cant root my box anymore i was able to install busybox and kernel boot menu succesfuly and granted super user permissions. the adb shell shows as [email protected] something is not right, looks like a partial root to me.
please advise.
have attached below a few screen shots.
http://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337
From the OP rbox:
"Starting with 51.1.4.1, these require FireTV Boot Menu. For the time being, you must update to 51.1.4.0 before updating to 51.1.4.1. Also, if you flashed 51.1.4.0, you must flash bootmenu afterwards. If you are already on 51.1.4.0, then you just need to flash bootmenu."
stutunaru said:
So, the other day i have started on rooting the AFTV of a friend of mine. i rooted mine a while ago and was comfortable enough to do it for someone else.
was following the AFTVnews.com guide (very well organized site and i would say a wiki for all aftv users). the initial version on the box was 51.1.0.1. have succesfuly rooted it, installed customer recovery, busybox, bootmenu, etc, all as per the guide. have upgraded it to 51.1.4.0_514006420 updated succesfuly as well again using aftvnews.com after which have installed the busybox again. now here the strange things happen. have decided to keep upgrading it to the latest version 51.1.5.0_515030720, according to the description i could upgrade straight to this version from 51.1.4.0_514006420. followed the same upgrade procedure and after the reboot in CWM i get the Amazon Fire TV logo and doesnt do anything, left it for about 10 min - nothing. power cycled it still the coloured logo. which means somehow it got software bricked.
started to google the ways of unbrick it and followed the procedure with the USB keyboard, it worked well for me. i got in to CWM recovery and did factory reset after which reboot. no luck, still showing the coloured logo.
got back in to recovery using the same USB keyboard method and did again factory reset after which decided to install the 51.1.4.0_514006420 updated custom ROM again which was already on my sdcard.
installed successfully, rebooted and started to configure the brand new aftv box - language, network, register, etc. after all this got on home screen, system to find out that it has the stock 51.1.4.0 version (51.1.4.0_user_514006420). what is interesting that the supersu is already there but without the option to launch it, only force stop, clear data and cash.
tried towelroot but obviously no luck, it sais your phone is not supported. so i guess that's it, no more root for me.
where the hell i missed it? i followed every step carefully.
and why in the first place after upgrade from 51.1.4.0_514006420 to 51.1.5.0_515030720 i got bricked?
please tell me there's still hope to root it.
Update: despite the fact that towelroot cant root my box anymore i was able to install busybox and kernel boot menu succesfuly and granted super user permissions. the adb shell shows as [email protected] something is not right, looks like a partial root to me.
please advise.
have attached below a few screen shots.
Click to expand...
Click to collapse
You kinda lost me there...but here's what I know
I'm almost certain its not possible for you to have boot menu and cwm without fully functional root privs
[email protected] is what it should say (does it go straight to that after inputting shell? Do you get the # sign?) That means bootloader is fully unlocked.
Supersu on aftv doesn't open and allow you to configure but it works. Not sure why but that's the way its been for a long time.
I think you're all set but sort of skimmed your post. Maybe someone else has insights.
stutunaru said:
So, the other day i have started on rooting the AFTV of a friend of mine. i rooted mine a while ago and was comfortable enough to do it for someone else.
was following the AFTVnews.com guide (very well organized site and i would say a wiki for all aftv users). the initial version on the box was 51.1.0.1. have succesfuly rooted it, installed customer recovery, busybox, bootmenu, etc, all as per the guide. have upgraded it to 51.1.4.0_514006420 updated succesfuly as well again using aftvnews.com after which have installed the busybox again. now here the strange things happen. have decided to keep upgrading it to the latest version 51.1.5.0_515030720, according to the description i could upgrade straight to this version from 51.1.4.0_514006420. followed the same upgrade procedure and after the reboot in CWM i get the Amazon Fire TV logo and doesnt do anything, left it for about 10 min - nothing. power cycled it still the coloured logo. which means somehow it got software bricked.
started to google the ways of unbrick it and followed the procedure with the USB keyboard, it worked well for me. i got in to CWM recovery and did factory reset after which reboot. no luck, still showing the coloured logo.
got back in to recovery using the same USB keyboard method and did again factory reset after which decided to install the 51.1.4.0_514006420 updated custom ROM again which was already on my sdcard.
installed successfully, rebooted and started to configure the brand new aftv box - language, network, register, etc. after all this got on home screen, system to find out that it has the stock 51.1.4.0 version (51.1.4.0_user_514006420). what is interesting that the supersu is already there but without the option to launch it, only force stop, clear data and cash.
tried towelroot but obviously no luck, it sais your phone is not supported. so i guess that's it, no more root for me.
where the hell i missed it? i followed every step carefully.
and why in the first place after upgrade from 51.1.4.0_514006420 to 51.1.5.0_515030720 i got bricked?
please tell me there's still hope to root it.
Update: despite the fact that towelroot cant root my box anymore i was able to install busybox and kernel boot menu succesfuly and granted super user permissions. the adb shell shows as [email protected] something is not right, looks like a partial root to me.
please advise.
have attached below a few screen shots.
Click to expand...
Click to collapse
Sounds like you installed 51.1.4.0 AFTER installing the bootmenu. You're supposed to install 51.1.4.0 first, then the boot menu, then the latest ROM. It's a simple enough fix. Just follow the "Resetting with Recovery Mode" portion of my guide here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
AFTVnews.com said:
Sounds like you installed 51.1.4.0 AFTER installing the bootmenu. You're supposed to install 51.1.4.0 first, then the boot menu, then the latest ROM. It's a simple enough fix. Just follow the "Resetting with Recovery Mode" portion of my guide here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Click to expand...
Click to collapse
@AFTVnews.com here are two separate issues im trying to find explanation:
1. why after installing rooted 51.1.5.0 i got brisked even i was following the same guide as for 51.1.4.0. i think i haven’t missed anything in there.
2. during the recovery the only missed step was nr.2 (missed to wipe cash partition). the question is why as a result of flashing the rooted 51.1.4.0 i got the stock one? (51.1.4.0_user_514006420)?
and the bootmenu i have installed only after applied 51.1.4.0->BusyBox->bootloader.
all works as should except the towelroot and partially supersu. why partially supersu because it still does what should, grants permissions to application but i cant open it, cant remove it, cant update it.
should i go ahead and apply the last rooted release (51.1.5.0_515030720)?
KLit75 said:
You kinda lost me there...but here's what I know
I'm almost certain its not possible for you to have boot menu and cwm without fully functional root privs
[email protected] is what it should say (does it go straight to that after inputting shell? Do you get the # sign?) That means bootloader is fully unlocked.
Supersu on aftv doesn't open and allow you to configure but it works. Not sure why but that's the way its been for a long time.
I think you're all set but sort of skimmed your post. Maybe someone else has insights.
Click to expand...
Click to collapse
according to AFTVnews.com the verification of unlocked bootloader was the adb shell. right after it i get [email protected]:/ #
http://www.aftvnews.com/how-to-check-if-your-fire-tvs-bootloader-is-unlocked/
cd2022 said:
http://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337
From the OP rbox:
"Starting with 51.1.4.1, these require FireTV Boot Menu. For the time being, you must update to 51.1.4.0 before updating to 51.1.4.1. Also, if you flashed 51.1.4.0, you must flash bootmenu afterwards. If you are already on 51.1.4.0, then you just need to flash bootmenu."
Click to expand...
Click to collapse
and i did flash the bootmenu after 51.1.4.0. the question is why after rooted 51.1.4.0 i got 51.1.4.0_user_514006420 which is stock ROM. also why if i have all tools mentioned for root on my aftv the towelroot says not supported?
is there anyway of starting allover again beeing on 51.1.4.0?
it's probably easier to do that then to troubleshoot why all these happened
stutunaru said:
and i did flash the bootmenu after 51.1.4.0. the question is why after rooted 51.1.4.0 i got 51.1.4.0_user_514006420 which is stock ROM. also why if i have all tools mentioned for root on my aftv the towelroot says not supported?
is there anyway of starting allover again beeing on 51.1.4.0?
it's probably easier to do that then to troubleshoot why all these happened
Click to expand...
Click to collapse
The rbox ROMs and the stock ROMs are named identically, as far as I know. As far as I know
Towel root probably sees the preroot fw as unsupported because the same version of stock is most definetly unsupported. I never tried because I am rooted so there was never a need.
You are rooted
You have unlocked the bootloader
Supersu is working
You have cwm
When I said you lost me there...I meant from reading your op I can't see anything that indicates you screwed up. In fact, I accidentally tried to flash a stock ROM when I was going through that long process but it won't flash. Rbox designed it to fail so we won't brick. So as far as I know there is no way to be running stock with a custom recovery and to have custom recovery you must be rooted. I could be missing something but I don't see what?
Have you tried flashing a more recent update?
***but don't just try it without ensuring prerequisites are met. Like many others I do things like root and unlocknjust once. There's a definite order to this that can't be overlooked.
Just grab the seeder.apk and try to enable it.
If it enables successfully,then you have root access.
stutunaru said:
and i did flash the bootmenu after 51.1.4.0. the question is why after rooted 51.1.4.0 i got 51.1.4.0_user_514006420 which is stock ROM. also why if i have all tools mentioned for root on my aftv the towelroot says not supported?
is there anyway of starting allover again beeing on 51.1.4.0?
it's probably easier to do that then to troubleshoot why all these happened
Click to expand...
Click to collapse
The pre-rooted ROM and the stock software update report the exact same software version number when you look in the Fire TV's about section. Saying "i got 51.1.4.0_user_514006420 which is stock ROM" is silly since the pre-rooted ROM will also say 51.1.4.0_user_514006420. Also, SuperUser not launching is a known issue. It is that way for everyone using the SuperUser app that is included in the pre-rooted ROMs.
You bricked because you either did not install the boot menu or you messed up the boot menu installation. Simple as that.
If you're running 51.1.4.0 right now, then:
Install BusyBox
CAREFULLY install the boot menu
Test that the boot menu is working by restarting your Fire TV and using the boot menu to enter recovery
Then finally, install the latest pre-rooted ROM
AFTVnews.com said:
The pre-rooted ROM and the stock software update report the exact same software version number when you look in the Fire TV's about section. Saying "i got 51.1.4.0_user_514006420 which is stock ROM" is silly since the pre-rooted ROM will also say 51.1.4.0_user_514006420. Also, SuperUser not launching is a known issue. It is that way for everyone using the SuperUser app that is included in the pre-rooted ROMs.
You bricked because you either did not install the boot menu or you messed up the boot menu installation. Simple as that.
If you're running 51.1.4.0 right now, then:
Install BusyBox
CAREFULLY install the boot menu
Test that the boot menu is working by restarting your Fire TV and using the boot menu to enter recovery
Then finally, install the latest pre-rooted ROM
Click to expand...
Click to collapse
Might be. i might've overlooked something during the process.
last night have applied the latest pre-rooted ROM and so far so good.
appreciate all your help folks.
:good::good::good:

Categories

Resources