Related
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
Hi,
I just noticed this was ready to download on my phone today. I downloaded and went to install, but the ClockWordMod Recovery doesn't let me install the update saying, "Image Verification Failed". I assume the problem is that the phone is rooted, and searching through the forums I heard this update isn't really anything big, just removing some German apps or something.
Is there anyway I can stop this update from notifying me? Or anyway to install? My phone is rooted but I'm not bothered about keeping it rooted as at the moment, there is nothing I need the phone to be rooted for. So, either way is fine for me.
Thanks!
If you want to unroot it, just flash generic ruu, more info here http://theunlockr.com/2010/06/07/how-to-unroot-the-htc-desire/
Than simply check for updates and update it
Or wait for few hours for rooted version of this rom
Hi!
I have a branded Desire and installed the update via Recovery. I had to disable the verification to do that (Goldcard inside). But all I got was a boot loop and my phone was derooted. I tried much (e.g. delete my data) and after a couple of hours I found the simple solution: Simply install the update again. Then I rooted my phone and restored the NANDROID Backup I made before I started the update because all of my data was gone.
Then I installed the Update again and this time it worked at the first time. All data was still there. I rooted it again and everything is fine. Don't know why my phone got a boot loop after first try but second try was perfect!
My suggestion: copy the zip from the download folder to the SDcard (made to a Goldcard!!!!) root and to the PC. Just if you need it more than once. Then make a Backup in the Bootloader. Then Install the update via Recovery. If anything goes wrong install the update again!
TL;DR Trying to get my phone to stock to accept OTA, running this rom http://forum.xda-developers.com/showthread.php?t=2485319 and unlocked bootloader/s-off with stock recovery flashed via Flashify. Anything else I should do?
So, let me preface this by saying that I am very, very new to this. I have a rooted tablet that I use, and that was a simple process. No adb commands or anything. But, when I rooted my phone using sunshine, I had no clue the world of **** I was about to get into. I rooted the phone, got a custom recovery on it, and all was going well. Until I accidentally wiped system, and was left without an OS. So, after the quick process of learning how to sideload, I got ViperOne installed on the phone and had it working. Yay for XDA help!
Not over yet though. Soon, over time, I was unable to accept calls. The phone would ring, and I would be able to answer, but no audio output and the mic wasn't picking anything up either. So, I found some fixes regarding google now voice detection, and all went well for about half an hour. Then it stopped working again. Frustrated, I bought another phone (galaxy s4), and decided I'd just get my HTC back to stock as possible.
Now for the question. I'm running this rom http://forum.xda-developers.com/showthread.php?t=2485319 , and I have the stock recovery (I flashed the recovery using Flashify, then rebooted the phone). All seems to be running well, despite the recovery flash wiping everything from the phone. My question is, seeing as I'm on that ROM, the latest firmware/radio/hboot, and stock recovery, and unlocked/s-off, could I accept and safely install the OTA when it rolls out? Thanks for any help, and sorry for writing so much!
Hey, check your Reddit post I gave you some info there.
Hi Guys,
so this morning my SW3 told me there was a system update, cool, so i said yes to the update and let it do its thing.
on coming back, the os version was still the same (LDZ22D) which i thought was odd.
I then did a search and found that there was indeed a new version out (LCA43) and thought something sus was afoot.
I got the twrp from this post http://forum.xda-developers.com/smartwatch-3/development/lwx49k-rooting-easy-t3107501 and booted from twrp
i then pushed the rom i downloaded form here http://www.xperiablog.net/2015/08/2...-update-lca43-intros-interactive-watch-faces/ and promptly tried to flash it like i would any custom rom i would normally flash on any of my other android devices.
I got an error, saying it was expecting "test keys" from a LAZ22D device or a LWX49K device, and that I had LRX22G test keys.
I also tried an ADB sideload which also didn't work.
Am i doing something wrong? Has anyone else ever encountered this?
Full disclosure, I also installed supersu a few months ago, but have had many factory resets since then (new roms on the paired fone) which i wouldn't have thought was an issue?
Cheers for any help you can give
That update only works on stock recovery. Go to my rollback thread and install the complete system of 5.0.1. I put links and directions to all the files. Then roll forward.
Thanks for that @lekofraggle, but I found an easier option, install Sony companion software, reflash "latest" firmware (apparently LAZ22D) then sideload the original update zip. Worked just fine. Just to clarify, I never flashed twrp, just hot booted from it, wondering if root did break ota...
Sent from my Nexus 7 WIFI using Tapatalk
Yes, root breaks most otas, but adb sideload usually works. Glad it was simpler than my doomsday thoughts.
I had a strange and new issue for me today. Went to sideload the OTA update (2nd February 2022 update). I have been doing it this way for the last few, with no issues. All seemed fine, but got an error when trying to flash the new magisk boot.img. Tried again and seemed to go thru. Rebooted then to bootloop. Keep trying and nothing, tried to get back in and flash again, also tried flashing stock boot to all slots, nothing.
So I had to resort to using the flash tool (in chrome). I assumed I would lose all and had made backups prior, so I would make it work. Using the flash tool, got in, got device connected. Then I selected the .004 build and unchecked all options. I can't remember for sure but I think I also unchecked the force flash all partitions/slots (I think that is what it was called). The flash tool did its thing and came back online, and seemed like no data loss, which was great. I then re-downloaded platform tools, factory image and OTA, got fresh boot.img, patched in magisk, flashed it and all good. After that, I did the direct install too, just in case, but I don't think that is needed, but doing so didn't mess anything up.
Not sure if this is normal, or helpful to anyone, but in my frantic searching, I didn't see a ton on this, so thought I would share it in case it happens to anyone else.
I have a feeling I should do what I normally do, reboot my pc and then download all items needed and flash away. I usually do that and haven't had issues to date. All ended up being good. If anyone runs into this, hope this helps you out.
Thanks for all the info on this forum, it is a great help to keeping my phone updated and running.
I had same problem
I had no issues. Same process... Recovery, ota sideload, reboot, let it finish setting up, patch boot.img extracted from full image, reboot into bootloader and flashed boot sector. All is fine.
I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.
DirtyPISTOLA said:
I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.
Click to expand...
Click to collapse
I think you can just use the flash tool. Check the appropriate options and it should wipe everything and return it to stock. It looks like you can even use it to lock bootloader again, if you wanted to. This was my first time using it. I may play around with it on one of my old pixels. Never had a use for it before, but came in very handy this week. Probably good for me if I know a bit more about it and how to use it.
DirtyPISTOLA said:
I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.
Click to expand...
Click to collapse
Within the guide is this post and I'm sure many other posts.
[GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST! ⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Here's the guide: https://forum.xda-developers.com/t/guide-root-pixel-6-oriole-with-magisk.4356233/
Thank you all, I figured out that online flash tool is a thing. I got it now.
hpower1 said:
I had a strange and new issue for me today. Went to sideload the OTA update (2nd February 2022 update). I have been doing it this way for the last few, with no issues. All seemed fine, but got an error when trying to flash the new magisk boot.img. Tried again and seemed to go thru. Rebooted then to bootloop. Keep trying and nothing, tried to get back in and flash again, also tried flashing stock boot to all slots, nothing.
So I had to resort to using the flash tool (in chrome). I assumed I would lose all and had made backups prior, so I would make it work. Using the flash tool, got in, got device connected. Then I selected the .004 build and unchecked all options. I can't remember for sure but I think I also unchecked the force flash all partitions/slots (I think that is what it was called). The flash tool did its thing and came back online, and seemed like no data loss, which was great. I then re-downloaded platform tools, factory image and OTA, got fresh boot.img, patched in magisk, flashed it and all good. After that, I did the direct install too, just in case, but I don't think that is needed, but doing so didn't mess anything up.
Not sure if this is normal, or helpful to anyone, but in my frantic searching, I didn't see a ton on this, so thought I would share it in case it happens to anyone else.
I have a feeling I should do what I normally do, reboot my pc and then download all items needed and flash away. I usually do that and haven't had issues to date. All ended up being good. If anyone runs into this, hope this helps you out.
Thanks for all the info on this forum, it is a great help to keeping my phone updated and running.
Click to expand...
Click to collapse
Did you check the downloaded files via checksum?
If you update via OTA, whether via delta or sideload, you CANNOT interrupt the boot process, otherwise the device assumes the update has failed.
Additionally, if you try to use an older boot image, you'll get the same result.
The recommended means of update is either delta OTA + install to inactive slot in Magisk, or factory image + patch new boot image in Magisk.