I have a 80 G9 (16GB) . It came with 3.2.79, I updated to 3.2.80 when it came out.
I successfully rooted 3.2.80 using information from this site.
This weekend I tried to update to the new 4.0.4. The update seemed to "hang", and I ended up forcing a power-off.
I subsequently used the recovery menu to do a full system format, and then tried to reinstall the 4.0.4 firmware - I've tried this a few times and each time it *seems* to be successful. After copying the AOS file to the device over USB, and selecting "ok", it says to leave the USB connected, a progress bar winds its way across the bottom of the screen, and then it reboots.
However, each time when it tries to boot, it just sits at the animated boot logo and never proceeds further. I've even tried letting it sit overnight - when I checked it in the morning after allowing it 6+ hours, it was STILL just sitting there rolling that bright bar across the "ARCHOS" logo..
I've tried to go back to 3.2.80, it gives an "update failed" on that every time I try.
I did the "remove developer edition" in the recovery menu, thinking perhaps the official firmware was balking on a 'rooted' device. Reformat, recopy AOS file, reboot, still no cigar..
I tried downloading the AOS file again, no luck..
Am I now the not-so-proud owner of a flat shiny brick? Is there some other procedure I can try? Has anyone else experienced this?
ANY advice or suggestions will be greatly appreciated.
If anyone needs more details or other info just let me know.
1. Download update .aos again (just to be sure)
2. Boot to recovery
3. Select Reset Android option
4. Install update
I hope this helps
gen_scheisskopf said:
1. Download update .aos again (just to be sure)
2. Boot to recovery
3. Select Reset Android option
4. Install update
I hope this helps
Click to expand...
Click to collapse
I've already done 2,3,4 several times. I managed to get a hold of someone at Archos that said that the file gets validated when it goes to update, and I'd get an error if it was corrupt. It doesnt give me an error there, it accepts the file.
As I'm currently on a slow hotel Internet connection, does anyone have an md5sum or sha1sum of their ICS .aos file I can use to validate mine against? (Annoying that Archos doesnt include a hash on their site)
Update .aos file is digitally signed (this also includes checksums of contents). If signature check fails recovery will not flash it.
My guess is that you'll have to give tablet to service unfortunately
tapatalked from Desire
In case anyone cares, I did in fact end up sending it back, and they sent me a replacement.
The replacement had ICS on it, and has in fact since OTA's another update without any problem.
Megadave123 said:
In case anyone cares, I did in fact end up sending it back, and they sent me a replacement.
The replacement had ICS on it, and has in fact since OTA's another update without any problem.
Click to expand...
Click to collapse
I cant believe you got through to support. I have been trying for the best part of 3 months and got no reply. I am new to XDA since I recently got a HTC Sensation. Saw that we have this section here for Archos G9s. Got my ''broken'' one out of storage and rooted and flashed it with a custom ROM. And it works again. Surprised since I had the exact same issue you got but I was not rooted when updating.
Related
I did the OTA for .14 where upon my Prime immediately started an infinite bootloop. I tried re installing .14 with the manual sd card method, but it changed nothing. I'd like to try again with .15 but ASUS hasn't updated their page with .15, nor have they responded to my help request within 48 business hours. Does anyone have a link for .15 I can try? Or .11 for that matter so I can downgrade?
Edit: Just realized I posted to the wrong section. I am dumb. Sorry Mods! Go ahead and move it.
If your unlocked then Here you go.
I saw that. I'm not and don't plan to. 8\
Thanks though
I have the exact same problem, and seems like ASUS is not really worried about us ... what are they waiting to finally put online the complete firmware, it's been 4 days since the last OTA ...
Still no firmware and still no response on my support request. Time to take it to Twitter I guess. Got me help when my ISP was trying to screw me.
TheMan876 said:
Still no firmware and still no response on my support request. Time to take it to Twitter I guess. Got me help when my ISP was trying to screw me.
Click to expand...
Click to collapse
It's been over a week that my device is a deluxe paperweight, they're really starting to piss me off ...
Finally !!
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/WW_epaduser9_4_2_15UpdateLauncher.zip
Did it work for you? I'm downloading it now
anthonyalberto said:
Finally !!
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/WW_epaduser9_4_2_15UpdateLauncher.zip
Click to expand...
Click to collapse
I downloaded the US version. How do you install it? it's just a zip file with no instructions or executables. There is no instructions listed on the support site either. Thanks.
Finally, my prime is back to life!
Method known as the EP201_SDUPDATE.zip method :
Download the firmware or your choice on the asus download page. It has to be the same version or an upgrade of your current version. You can't downgrade using this method.
Once downloaded, extract the zip. Inside, there's another file file.
Rename this one into EP201_SDUPDATE.zip and put it in the root of a microSD card.
Put the microSD card into the tf201.
As soon as your device boots (or reboots), hold the Volume Down key until some text shows up on the top left of the screen. Then, press Volume Up once within 5 seconds.
Some more text will be displayed. Wait a bit and ... there's three scenario here :
A) A droid with a blue diamond and a progress bar is showed on the screen for a while, then the device reboots and a long progress bar is upgrading or changing firmware zone. You Win.
B) The device reboots like nothing happened. It means you have a very bad reboot problem. I had it myself using .14. The device reboots so frequently that there's not enough time for it to load the rescue upgrade program. Solution : try again, repeat the steps to enter rescue mode. Eventually, you'll get it (took me 15 tries or so to get it)
C) You see the same thing as A) but then there's a dead droid with a red "!" symbol. It means your microSD card is not inside or the file you've put at the root of it is not valid (no downgrade!!)
So using this method, I was able to upgrade to .15 and my prime is back to life right, syncing all the programs right now, that's great
Yeah, I used that method too. Unfortunatly while trying to fix it the other day I wiped it. 8(
It's running, but now I have another problem. I have no wifi. >_<
Yep, that did the trick. Thanks!
Hello! I have scenario you don't have on your list. My TF201 just keeps repeating the ASUS screen over and over and when I try to go into recovery all I get is the GREEN Android with and GREEN Triangle and Exclamation mark. Have you heard of anyone with this type of symptom?
JuNyA8971 said:
Hello! I have scenario you don't have on your list. My TF201 just keeps repeating the ASUS screen over and over and when I try to go into recovery all I get is the GREEN Android with and GREEN Triangle and Exclamation mark. Have you heard of anyone with this type of symptom?
Click to expand...
Click to collapse
Have you put the right file at the root of your microSD? It's the zip file that is in the zip file you downloaded from ASUS.
Must be renamed EP201_SDUPDATE.zip
And you can't downgrade using this method. Use a different SKU or an upgrade.
It's supposed to work if done properly, give me more details on what you're trying to do (version and sku of firmware you have on tf201 and sku and version of firmware you're trying to use)
anthonyalberto said:
Have you put the right file at the root of your microSD? It's the zip file that is in the zip file you downloaded from ASUS.
Must be renamed EP201_SDUPDATE.zip
And you can't downgrade using this method. Use a different SKU or an upgrade.
It's supposed to work if done properly, give me more details on what you're trying to do (version and sku of firmware you have on tf201 and sku and version of firmware you're trying to use)
Click to expand...
Click to collapse
Thank you for your reply. Here is what I did:
My TF201 is a JP version and originally had HC on it. I read through XDA to find that I am able to use the ICS update from a different SKU so I updated to ICS US Version and all was great except that I could not use my Keyboard Dock since it a JP version Keyboard. Then I noticed we were able to put CWM on the TF201 so I went ahead and did that (I think this may be the reason why I can`t revive my prime.). I wanted to go back to HC so that I can use my Keyboard Dock again (I had already backed my Blob from the time it was still on HC JP Version). I googled the HC US Version and did the downgrade as posted on this site, all went well as it was showing the progress bar of the downgrade. But when I rebooted all I got was the ASUS Logo loop and when I try to access recovery I would see the Android Robot and a progress bar at the bottom then it would suddenly give me the green exclamation mark. I asked around here and was shown your thread so I gave it try using the latest ICS update for US version since that was the SKU of the HC I tried to downgrade to. I followed the instructions on this thread and to no avail will my Prime revive. I have tried about 10 times over and over but would still get the same Android Robot with Exclamation mark. Shall I keep trying your method or is there a possibility my Prime is bricked for good. Any assistance would be great and I am willing to try anything to get my Prime revived again, don`t want to go out buy a new one if I can revive my Prime.
Hmmm that's weird, maybe its because you unlocked your bootloader ... maybe ask to people who also did unlockthe bootloader ...
anthonyalberto said:
Hmmm that's weird, maybe its because you unlocked your bootloader ... maybe ask to people who also did unlockthe bootloader ...
Click to expand...
Click to collapse
Yes it is very wierd. I get no errors like most people do. I think it is the bootloader that is causing the problem. I am going to try to run ADB logcat to see if anything pops out. If I can only pin point the problem I may be able to figure it out or .... not. I am going to ask around some more and keep trying your method. Thanks for trying to help me out! Greatly appreciated!!!
EDIT: I have tried everything to revive my Prime, I pretty much give up. I have asked ASUS for assistance in getting it repaired but have no reply from them yet.
I had a similar issue (stuck at the Eee Pad screen) and used this method to resolve it.
It is worth noting that the Micro SD Card must be formatted as FAT32, not FAT as suggested on some sites. I wasted a day or more on this using a FAT formatted card.
Hi everyone, i have a problem with my Sony Tablet S, suddenly it's freezing and when i try to turned it back on it stuck on booting screen (with sony logo ).
then i checked to the internet and i found that i have to hard reset it, by holding down the + volume button and power button in order to get to the Android System Recovery. But then again no clue, i have tried reset to factory setting and keep stuck on boot screen. its frustating.
Prompt on my screen :
E: Fail to read boot logo flag
E: Cant Open / Dev/block/mmcblk0p5
(No Such file or directory)
E: Failed to Mount /cache (No such file or directory)
E: Cant mpunt/ cache/recovery/command
E: failed to mount /cache (No such file or directory)
E: failed to mount /cache (No such file or directory)
On the Android System Recovery there is Update System from SD Card, is there any possible ways that i can put Honeycomb virtual image on to the SD Card then make it as a bootable device, so i can boot from my SD Card.
Please help! thanks a lot !
If it was previously on Honeycomb, and you could find someone with a rooted Tablet running ICS from the same region and same version (WiFi vs 3G etc) then you might be able to recover it.
You would need to get them to install the rescue-bcakdoor on their device, allowing them to download the OTA update file. You could then try and ABD push that file onto your device's storage and install from the Recovery menu.
Just a thought! Otherwise, you could try sending it back under Warranty or something..
Disclaimer: This is by no means a tested solution and you may want to check on a few things before trying this. I take no responsibility for anything that happens as a result of this procedure. As always, I recommend trying Sony's Warranty and Repairs department for an official, warranty-valid repair.
Same problem here
I have the same problem with my Sony tablet s, i udated it to 4.0.3, it was working fine till yesterday when it would not start, its stuck at the logo, ive tried factory reset, but nothing changed, i did not have a recovery data either.
i would appreciate if some one would guide me how to fix it, either upload the ota update file, can i root it some how or flash it by using an UPDATE.Zip on memory card and try system recovery using android 3.2.1 ota file. please help
help me too
I got the same problem yesterday(29. May), it might be google did something via OTA. I'm using China version, changed region to US and upgraded it to ICS, but unfortunatlly, can't root in ICS now. Yesterday, it suddenly stuck and can't reboot any more. always stuck on Starting Screen. I called Sony Customer Center, and follow their struture to reset the tablet, but not help. Can any one help me to fix it....
InMyEyes said:
I got the same problem yesterday(29. May), it might be google did something via OTA. I'm using China version, changed region to US and upgraded it to ICS, but unfortunatlly, can't root in ICS now. Yesterday, it suddenly stuck and can't reboot any more. always stuck on Starting Screen. I called Sony Customer Center, and follow their struture to reset the tablet, but not help. Can any one help me to fix it....
Click to expand...
Click to collapse
I'm not too sure about easy fixes (I'd have to work through it a lot more, which is tricky without the error), but I know that it can't be Google. Google neither could nor would release an OTA package that aggressively downloaded to the device, installed and then broke something at system boot-level. Doesn't really work like that.
arso123 said:
I have the same problem with my Sony tablet s, i udated it to 4.0.3, it was working fine till yesterday when it would not start, its stuck at the logo, ive tried factory reset, but nothing changed, i did not have a recovery data either.
i would appreciate if some one would guide me how to fix it, either upload the ota update file, can i root it some how or flash it by using an UPDATE.Zip on memory card and try system recovery using android 3.2.1 ota file. please help
Click to expand...
Click to collapse
If you have this problem and you don't have a rooted tablet, you won't be able to downgrade. you must send it back for repair, since it can't reboot normally, sony won't detect any self bricking tracks, so warranty is still in the game, had the same problem to with Region Changer somewhere in V2.1 or something.
Goodluck.!
I have the same problem too, and I can't send it to sony service because it's not on sale in my country. I look forward to deal with it through sd card. Can't use USB connection. (not rooted too).
I have a similar issue, but mine seems to be stuck on the bootscreen animation (with the swirly yellow lines traveling from one side to the other). Haven't tried the power + volume up yet, will try that to see if I can hard reset. I was rooted on HC, but decided to take the ICS update so I believe that I'm unrooted at this point--still unsure though.
Regions - guarantee
Same problem here
Have tried all of the tips in this post...Still stucked with the Sony logo..
I bought my in Krakow, Poland, but lives in Norway... it has the /P on the back instead of the /N.
Do you know if the guarantee is worldwide? If I can drop this to a Sony shop in Norway?
I dont have the receipt anymore, because I claimed a refound from the company I work in...
Thanks
Rune
What color is on the tabblet?
Is it green or red?
I think if its green, there is no fix.
If its red, use the battery completely then recharge it until green light.
Try after that. Mine was fixed whit same problem.
Well, I've tried everything that I've found on the forums/internet to no avail. Just contacted Sony support and am having them send me a box to ship it back for repairs (luckily I only bought it last December). The operator on the phone says that it's most likely a hardware issue if it doesn't get pass the "Sony" logo. This leaves me a bad taste with Sony, won't be buying a tab or phone from them again.
I have had the same issue, so will be going back to Sony soon for a repair. Disappointed as I've only had it 6 weeks, but as long as the repair service is good I'll be ok.
Same problem here tonight. Unreal. Purchased last August. Won't buy another Sony again. First it was the constant soft resets in order to power on. Now this.
I got the same problem on my sony tablet s device too model SGPT111US/S anykne fixed this erorr yet?
Now i can't do any things because it stoped at logo SONY, please help, any flasher or rom support this device from pc ?
Just got off the phone with tech support. Couldn't even get it to do a factory reset. Stuck on system restore screen. Sending it in for repair. Very disappointing. Paid $500 for this thing. Didn't last a year. A few more weeks and I would have been out of luck on the warranty.
SCIONTX said:
Just got off the phone with tech support. Couldn't even get it to do a factory reset. Stuck on system restore screen. Sending it in for repair. Very disappointing. Paid $500 for this thing. Didn't last a year. A few more weeks and I would have been out of luck on the warranty.
Click to expand...
Click to collapse
I Have no money for this, and i'm in vietnam, can't contact with any one.
No way to fix this ?
update, when i'm enter recovery mode, i enter ADB, run via cmd, adb can send reboot comand: adb reboot :cyclops:
then the tablet reboot, but still loop at sony, and i see windows is try to install MTP USB Device but un successful.
Any ideas ?
goldenfish said:
update, when i'm enter recovery mode, i enter ADB, run via cmd, adb can send reboot comand: adb reboot :cyclops:
then the tablet reboot, but still loop at sony, and i see windows is try to install MTP USB Device but un successful.
Any ideas ?
Click to expand...
Click to collapse
What version did you have before boot loop? 3.2.1, 4.0.3?? Try to flash a us rom from recovery. You can find in my signature link.
Good luck
Chur
stifilz said:
What version did you have before boot loop? 3.2.1, 4.0.3?? Try to flash a us rom from recovery. You can find in my signature link.
Good luck
Chur
Click to expand...
Click to collapse
it's 4.0.3,
custom rom from your link is zip file, i don't know how to flash this file, because the tablet can't mount sdcard ????
goldenfish said:
it's 4.0.3,
custom rom from your link is zip file, i don't know how to flash this file, because the tablet can't mount sdcard ????
Click to expand...
Click to collapse
Oh didn't realise you can't mount, that is an issue then. Sorry you may be soft-bricked
Hope you can find something
Chur
Some of you might have seen my earlier thread, my ReZound is rooted. HTC sent out the ICS update my phone attempted to install it and afterwards it would not advance past the white HTC screen. After many hours of playing around with it (being semi-noobish to all things rooting, but decently knowledable with technology) I realized that on the H-boot screen it was telling me that the Image was missing. I assumed that the HTC update deleted it? After thinking about it, I thought that maybe installing a custom ROM would fix this, so I grabbed Scotts Clean ROM. Sure enough I did and I was finally able to advance past the white HTC screen. It looks as if everything is working fine with the phone now EXCEPT I have no data and no calling connection. Im assuming that my phone is just that messed up from the attempted upgrade this morning that im missing files needed for the connection.
My next thought was to just say heck with it and do a factory reset hoping to get back to a bone stock phone that at least functioned, but when I try the factory reset it doesnt work....
Any ideas of what I should do next? Ive spent 5-6 hrs trying to fix this phone today, I really hope to get something figured out. Thank you everyone for your help!
EDIT: I feel like an idiot... Because of putting the battery in and out for resets I left the back off the phone. I now have service. Main issue now is that when I try to call out, as soon as I type a number on the dialer it freezes up and restarts itself....
The phone still tries to look for the old image on the restart and gives me issues every time on startup still also. Id like to be able to get this back to not needing a ROM....
If it were me, I would download the official RUU for ICS found here: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/ IIRC, mirror #3 was the fastest. Then follow the directions from that site:
After downloading the file, rename it to "PH98IMG.zip" (no quotes)
Place the renamed file onto the root of the SD Card
Power down your device
Reboot into the bootloader by holding VOL DOWN + Power
The flashing process should begin automatically
Let the device reboot, and you should be done.
That will get you up and running. Then you can go about rooting it again if you like.
I got a gen 8 101IT from a friend. Problem with the device is that it boots automatically in recovery and it won't install any update I've tried.
From what my friend can remember is that he first installed SDE and UrukDroid after that. The device worked fine but later he wanted to revert back to android. So he tried to install an original Archos firmware and the install failed.
I'm not entirely sure what exactly did he do at this point, but it seems that the device no longer has SDE. It boots straight to recovery, where I have the options "ok", "update firmware", "repair system", "format system". What I have tried so far is installing the newest firmware, some older firmwares and the SDE, running "format system" between each try ofcourse. Every update fails with "Update failed: (207)" message. I also tried formatting the internal storage to Ext2 and got the same error. I have redownloaded the firmwares multiple times, and I'm quite certain that I have downloaded the correct versions and have the correct filename.
Has anyone got any ideas what might have gone wrong. I'm wondering if it is possible to brick the recovery in a way that it boots but doesn't flash the rom? Also I was wondering if it's normal that after formatting the device and mounting the internal storage on my pc it's totally empty except for the empty folders "Music", "System" and "Video".
Code 207 is displayed when the .aos upgrade file doesn't pass the signature check.
drain the battery and wait before next try
Thanks for the reply mrbelou, I thought it must have something to do with the signature check. Still it seems a bit weird that it wouldn't pass the check, unless the stored signatures are corrupt. I'll try draining the battery and see if it helps, might even disconnect it for a while so I don't have to wait for it to drain by itself.
Draining the battery and even disconnecting it for an hour or so didn't have any effect. I'll have to start researching and hacking a bit more. Already found some of the reverse-engineered stuff, I'll have to keep researching it more. I already started wondering that if the signature check keys for the .aos verification are in the same keystore as the recovery kernel verification key, yet it still boots the recovery kernel...
ARCHOS 101it Android OS anyone???
kugge said:
I got a gen 8 101IT from a friend. Problem with the device is that it boots automatically in recovery and it won't install any update I've tried.
From what my friend can remember is that he first installed SDE and UrukDroid after that. The device worked fine but later he wanted to revert back to android. So he tried to install an original Archos firmware and the install failed.
I'm not entirely sure what exactly did he do at this point, but it seems that the device no longer has SDE. It boots straight to recovery, where I have the options "ok", "update firmware", "repair system", "format system". What I have tried so far is installing the newest firmware, some older firmwares and the SDE, running "format system" between each try ofcourse. Every update fails with "Update failed: (207)" message. I also tried formatting the internal storage to Ext2 and got the same error. I have redownloaded the firmwares multiple times, and I'm quite certain that I have downloaded the correct versions and have the correct filename.
Has anyone got any ideas what might have gone wrong. I'm wondering if it is possible to brick the recovery in a way that it boots but doesn't flash the rom? Also I was wondering if it's normal that after formatting the device and mounting the internal storage on my pc it's totally empty except for the empty folders "Music", "System" and "Video".
Click to expand...
Click to collapse
I have the EXACT same problem. I made the mistake of leaving my ARCHOS 101it on near a hot wi-fi connection with third party downloads switched on. It downloaded something that totally wiped out all my apps...got an error message "Sorry! the application Archos (app)(process+com.archos.archoswidget)has stopped...etc"
soooo, I copied my files onto my laptop and re-formatted. Now all I see are those three stinking folders just like you mentioned. I was able to install the SDE and get a workable desktop, but can't access the internet. When I followed with trying to update the firmware I got "Update failed: (1)"
I am by no means programming literate, so I have no idea how to find the root /) file or copy the upgrade to the black screen with little tiny white letters in it (I told you I was STUPID). I don't know what "flash" the drive means (tried googling it and got things about flash players) ...so whoever helps me (PLEASE) will have to be quite specific as to what to do. I also don't know what "brick the recovery" means I believe mounting means hooking the usb cable to my pc. What is "flash the ROM" mean and how do you do it.
Am I asking too much??? Jeanie
UPDATE!!!!! After applying sde versions and trying numerous times to re-download firmware, I finally got my aos back!!! Seems I downloaded the newest version using Chrome and it wasn't copying right, so I followed another forum's advice and used Internet Explorer...it worked!!! Now after a week, I now have a "Like New" Archos 101it. What a learning experience!!!
Nice to hear you fixed your problem jeanuhlik.
I haven't gotten anywhere with mine. Can't remember if I tried downloading the firmware with different browser. I've just been researching omap bootloaders and stuff if I get the time to start hacking together something to unbrick the device. It's not worth the time but it's always interesting to learn new stuff.
maybe some help...
kugge said:
Nice to hear you fixed your problem jeanuhlik.
I haven't gotten anywhere with mine. Can't remember if I tried downloading the firmware with different browser. I've just been researching omap bootloaders and stuff if I get the time to start hacking together something to unbrick the device. It's not worth the time but it's always interesting to learn new stuff.
Click to expand...
Click to collapse
I found that if there were several versions of ( firmware_archos_android_gen8.(2)aos)...you HAVE to delete the (2)...then download it into your archos....that's what finally worked for me! I've been playing on it for almost a whole day now!! Be sure and format and delete any SDE firmware you have in there, a format will not get rid of the SDE, but when you open the white screen it should give you Developers tools (or something like that) then you have the option of deleting the SDE.
I hope I have helped, like I said, I know NOTHING about hacking or anything like that, but I guess I just got lucky, I was ready to ship it off to a computer repair shop (we live about 50 miles away from any town that has anything in it)
Best wishes, Jeanie
Hello. I have a Sprint M9. It had been acting flaking lately (I would try to install the latest update, and it would reboot without installing and report that the phone had recovered from an error and ask if I wanted to send to HTC). Tonight, I was trying to use DLNA to play video from my phone to my TV, I was in settings and gave DLNA permission to access my storage. As soon as I did that the phone rebooted without warning and continues in a loop of displaying the HTC logo, then restarting over and over.
I can get into bootloader, download, and recovery mode by holding down the volume down key. I have tried Wipe Cache Partition and Wipe Data, but the phone still will not get out of the loop.
Phone is stock. I have never tried to root or disable S-on or load my own recovery.
What, if anything, can I do to get my phone working again?
Just tried doing what I think is called RUU? I downloaded the .exe from this site:
http://www.htc.com/us/support/htc-one-m9-sprint/news/
It found my phone, and rebooted into download mode. It tried to flash my rom, but shortly after trying to send the file (progress bar jumped from 0% to 100% in 1/2 second). The utility gives me a Error [155]: Unknown Error. I've tried a couple times and get the same problem each time.
The utility reports I have version 3.41.651.21 and tries to flash to 3.41.651.31
Great, now it is telling me my software has been modified. (it hasn't) The only things I've done is run the RUU and reboot into recover to clear cache/data. Bad NAND?
Well, found out why RUU wouldn't work. Low battery. Apparently it ate a lot more battery than I realized while it was in the reboot cycle. Tried manually flashing the firmware and fastboot told me the reason it was failing. C'mon HTC, if the CLI can tell me there's not enough battery to proceed, your GUI utility should be able to as well.
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
shawndoc said:
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
Click to expand...
Click to collapse
Same thing happened to me. The update that Sprint pushed last Wednesday completely bricked my HTC One M9. Same failure mode that you experienced. Sprint technical center was unable to do anything with it, so they are replacing it, allegedly ( been waiting a week for said replacement ).
I talked to a few other people who had the same problem, by the way. Someone in Sprint's QA team completely dropped the ball on this update.
Well, even after RUU it says my system has been modified and the phone will no longer boot into recovery. Just errors back to Download with the message that recovery couldn't launch.
I've also now got intermittent problems with the com.android.settings crashing. So I've thrown in the towel and purchased my first non HTC phone since the original Windows Mobile days.
Hello there. The same problem has come to my mind and the phone has been off for almost a month. Did you solve your problem? If you could solve it, how did you do it? I sent you above the original stock rom set. Nothing changed. The phone developer rum works. but the original 0pja200 rom is starting again.
my phone soft bricked, unlocked bootloader and S-off. Whether it is possible without blocking bootloader flashed RUU rom?