Related
Ok so, this is my first android phone and after being prompted to install the 2.2 update on my European htc desire, i downloaded and started it installing. It gets to about 23% and says process system unavailible and after reading what people said i cleared the phone and tried to install the update manually from the SD card. This didn't work
My phone currently does this
Will boot into what it says is 2.2 but with no wifi, no service, and no SD card showing up
then after about 5 minutes it will reboot.
I have no idea what i can do to fix this? could someone please help me, i'm a noob with android so a clear step by step would be much appreciated
anyone
I am having the same issue... Anyone some help please...
I had a symetrical experience.. I can't post links yet, but you if you look at my posts you should be able to find what worked for me.
Futurian said:
I had a symetrical experience.. I can't post links yet, but you if you look at my posts you should be able to find what worked for me.
Click to expand...
Click to collapse
how did you create a blank goldcard, i can't access my SD card on my phone while it's in the phone so how did you do it
Do you have a WIFI connection? I do, and did the OTA 2.2 upgrade over WiFi with no problems, on my Unbranded European HTC Desire.
If youre phone won't boot properly, there are a few answers; 1) Return in to HTC, they're getit working and back to you, 2) Return it to th place of purchase, 3) Root/reflash (but sounds like it might not be an option).
Dale
F3L1X1 said:
how did you create a blank goldcard, i can't access my SD card on my phone while it's in the phone so how did you do it
Click to expand...
Click to collapse
I followed the instuctions in the "[TUT]Complete upgrading guide(root, unroot, flashing ROM & updates)" thread within Desire Android Development. (Post #3)
dedlite said:
Do you have a WIFI connection? I do, and did the OTA 2.2 upgrade over WiFi with no problems, on my Unbranded European HTC Desire.
If youre phone won't boot properly, there are a few answers; 1) Return in to HTC, they're getit working and back to you, 2) Return it to th place of purchase, 3) Root/reflash (but sounds like it might not be an option).
Dale
Click to expand...
Click to collapse
When I got in touch with HTC they wanted £50 to do a reflash, falsely accusing me of rooting my device..
was that 50$ to send it to them? or can they do it without having it there. Because if THEIR update screwed up my phone i don't see why i should have to pay for a fix
maybe a silly question but did you try a factory reset?
http://www.htc.com/www/howto.aspx?id=805&type=1&p_id=312
HugoTouchHD said:
maybe a silly question but did you try a factory reset?
http://www.htc.com/www/howto.aspx?id=805&type=1&p_id=312
Click to expand...
Click to collapse
yeah i did that, about the only advice the australian HTC support guy gave me -____-
F3L1X1 said:
was that 50$ to send it to them? or can they do it without having it there. Because if THEIR update screwed up my phone i don't see why i should have to pay for a fix
Click to expand...
Click to collapse
Tell me about it, so thankful I managed to fix it myself!
It sounds like you are alll applying an OTA update for the standard ROM to what was a branded device. There are lots of explanations as to how to fix this if this is the case
In summary
Download update from mentioned here
Copy this to root of your goldcard and rename to update.zip
Turn off phone
Turn on holding down vol down
Select Bootloader then Recovery (an image of device should appear with exclamation mark over)
In menu (sorry forgot how you get in, if it does not appear then try power+vol down or power + back). From there choose apply update.zip
Wait while update applied
After update select reboot and wait for device to boot
Video of it here
jameson_uk said:
It sounds like you are alll applying an OTA update for the standard ROM to what was a branded device. There are lots of explanations as to how to fix this if this is the case
In summary
Download update from mentioned here
Copy this to root of your goldcard and rename to update.zip
Turn off phone
Turn on holding down vol down
Select Bootloader then Recovery (an image of device should appear with exclamation mark over)
In menu (sorry forgot how you get in, if it does not appear then try power+vol down or power + back). From there choose apply update.zip
Wait while update applied
After update select reboot and wait for device to boot
Video of it here
Click to expand...
Click to collapse
I've just tried this again, installation looked like it went through ok, rebooted and relaoded into sense, then it shows me a status bar counting, normally this gets to about 10% then says ?Sorry process system is not responing, so i can either click wait or force close, then in continues upto about 97% then reboots and reloads only to load a white screen showing htc and continues counting in percentages, gets to about 15% then says force close, then onto about 91% then reboots this goes on for a while until it just shows me a sorta bricked phone with no wifi, gsm or any real functionailty and it continues to reboot every 5 mins, back to where I started showing 2.2 as installed
One strange thing I have noticed is that my CID is
CID: 00000000000000000049E917D100A69E
Reversing CID
CID: 00A600D117E949000000000000000000
Can't find update.zip on SD card during recovery
Tried all this, thanks. Goldcard created using Gold Card Tool 0.0.5 (awesome job Klutsh) . I get the error message:
"E:failed to open /sdcard/update.zip (No such file or directory)" even though it is in the root dir when I look at the card on my PC.
Should it be in a directory called /sdcard ?
chessmaster82 said:
I've just tried this again, installation looked like it went through ok, rebooted and relaoded into sense, then it shows me a status bar counting, normally this gets to about 10% then says ?Sorry process system is not responing, so i can either click wait or force close, then in continues upto about 97% then reboots and reloads only to load a white screen showing htc and continues counting in percentages, gets to about 15% then says force close, then onto about 91% then reboots this goes on for a while until it just shows me a sorta bricked phone with no wifi, gsm or any real functionailty and it continues to reboot every 5 mins, back to where I started showing 2.2 as installed
One strange thing I have noticed is that my CID is
CID: 00000000000000000049E917D100A69E
Reversing CID
CID: 00A600D117E949000000000000000000
Click to expand...
Click to collapse
i get this same problem. How do i create a gold card if when i plug in my phone to my pc it won't recognise it and when i put the SD in the phone the bricked 2.2 won't recognise it
F3L1X1 said:
i get this same problem. How do i create a gold card if when i plug in my phone to my pc it won't recognise it and when i put the SD in the phone the bricked 2.2 won't recognise it
Click to expand...
Click to collapse
I had to format the card in a card reader in my PC, then use the Gold Card Creator mentioned elsewhere in the thread. You have to install HTC Sync because enough drivers are in there to at least allow the apps to 'see' the card at physical level, even if the bricked Android doesn't. Set the phone to USB debug mode in Settings/Applications - the phone stays 'on' long enough between reboots to do that and get a CID out of it! Then Gold Card Creator works well enough to get the CID from the SD.
I'm trying this again with a 2GB card to see if makes any difference.
Check folder settings when using windows
bearMedicine said:
Tried all this, thanks. Goldcard created using Gold Card Tool 0.0.5 (awesome job Klutsh) . I get the error message:
"E:failed to open /sdcard/update.zip (No such file or directory)" even though it is in the root dir when I look at the card on my PC.
Should it be in a directory called /sdcard ?
Click to expand...
Click to collapse
Quick update to this. Make sure you have extensions of known file types SHOWING in your folder settings. I was naming the file update.zip.zip!!
Thanks to ALL in this forum for get apps and assistance. I unbricked my phone tonight thanks to you all
well i phoned the shop here in australia that i bought it from and they said they've had alot of desires being returned because they've been bricked by the update and to just send it back and they'll fix it and update to 2.2 for me
Would appreciate your help on the following issue (amoled display):
- phone doesnt boot up, it is stuck to a screen showing htc in the middle and 4 small triangles in the corners; if I unplug the pc cable it goes to a RUU menu
- no access to recovery or bootloader menus (by holding power + vol down/back)
- installing stock RUUs dont work; there is a 110 error saying that the RUU is not complete (tried 5-6 RUUs, both 2.1 and 2.2). there is a progress bar on the phone's screen that is normally green, but turns red when the radio is being written (as per the install wizard on the pc) and there is another triangle showing up at the end of the progress bar
- fastboot oem boot restarts the phone, but then it gets stuck to the white screen having htc in the middle (like when you start up the phone and after this quietly brilliant shows under htc, for me it doesnt go beyond this initial point)
- fastboot reboot-bootloader restarts the phone into the same 4triangles screen with htc in the middle
- adb doesnt work as it doesnt show my device
- any power + vol down/back combination brings the phone to the 4triangles screen
- if I run the stock RUU after fastboot oem boot (white screen with htc in the middle) there is a menu showing up on top of the white screen showing up the progress (1-bootloader, 2-radio_v2, 3-radio, then system, recovery, user data, etc.); bootloader is updated ok but then it gets stuck when updating radio_v2 and doesnt move further from that point)
- after the RUU install fails, I plug out the pc cable and see the RUU menu; depending on the RUU that I try to flash the hboot version changes up and even goes down after, but the firmware (what the RUU installer "sees" on the phone) and radio (seen on the RUU menu) remains the same: 1.21.405.1 and 4.06xx; the date on the RUU menu also changes depending on the RUU that I try to flash
Any suggestions to get my desire unbricked?
Bit of a background to the problem:
- rooted (unlockr) and was having Paul's r3 rom (2.1)
- updated the radio to 5.10xx
- got into silly restarts when using gps and thought to reflash a new rom and went for Paul's r8
- restarts were there also when using the phone normally
- thought to re-do all the rooting, wiping out everything from the phone, etc; so having r8 as the rom (pre-baked version) I started the rooting process with creating again the goldcard, etc etc
- error message at some point saying partition update fail (following the steps from theunlockr as I did the first time when rooting) and then the phone got to this triangles screen with htc in the middle
- strange though that this screen is different than the one when I first rooted when there was just one big triangle in the middle
Thanks a ton guys!
I've seen a few posts about this screen with the 4 triangles, but never seen the result of any potential fixes, or if it was ever actually fixed.
Just an idea, but it was maybe a bad radio flash if you are saying it started playing up after that? Unfortunately a bad radio flash is fairly terminal so I hope that's not your problem.
Good luck with this one and if you get it fixed then post the result here if you don't mind!
Will definitely post the solution when found; so far though nobody has any thoughts around what might be the reason behind this problem and how to get around it. I dropped a few PMs to the people that had this problem in the past and contacted Paul at Modaco, but so far no replies...
You can fix this with an RUU, I've had the same issue when I unplugged too early after flashing, but you are asking for help in the wrong section.
thought that the dev's section is where the best knowledge exists...
about the RUU process, I am trying to flash stock RUU.exe files, but there is a problem when the radio is being written and then I get a 110 error from the RUU install wizard saying that the RUU is incomplete.
for you the RUU install worked smoothly?
If you get a write error during an RUU flash (i.e. while the flashing is taking place, not before) it probably means there's a hardware fault.
Could be hardware, but I find it hard to believe as the phone is new and it is network locked, hence I didnt even use it for real, apart from some wifi and gps activities. Besides, the phone worked very well when I first rooted with Paul's r3 and the whole mess with restarts when using gps started after I upgraded the radio to 5.10xx having a 2.1 OS.
I feel that the problem started when I tried to root the phone being on Paul's r8 2.2 OS (tried to root with a 2.1 system and then it got messed up in the process).
I am not saying that it is not hardware as it is a possibility, but still think that it might be a messy software aspect, as if the radio is messed up from a hardware perspective, then at least the system should boot up and then wifi, gps, gsm and the things that are controlled by the radio shouldnt work...but somehow the OS should start-up.
Basically I dont get a write error, it's just that the error comes up when the radio is being written, hence I think that there is something wrong with the radio set-up that I have now on the phone...
Maybe somebody knows how to flash the system from scratch using only fastboot in cmd (having the right zip or img files properly signed), or maybe just the radio to start with.
This is not a Development question and thus should not be posted in the Development forum.
Thread reported.
have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.
acolwill said:
This is not a Development question and thus should not be posted in the Development forum.
Thread reported.
Click to expand...
Click to collapse
Well, I thought that as various solutions to root the phone, to get past different restrictions in the OS, etc. were discussed here, it might be a good thing to develop a way to bring back to life a OS being in this situation like mine...come on...
mariosraptor said:
have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.
Click to expand...
Click to collapse
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days
I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.
but to get adb you need to download and install android sdk. look here http://developer.android.com/sdk/index.html system dependands download.
install it here are instructions on how to use if you aren't familiar with.
http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
for anything else just use google.
i'm pretty sure that your device is fixable and you can fix it without any service center. cheers and post what ever happens.
popepope said:
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days
Click to expand...
Click to collapse
I know how to use adb commands...pretty new to android and everything, but lately I roamed a lot through various things about it and learned a lot.
The problem is that adb doesnt list my phone when I run adb devices, it shows only when I run fastboot devices, I am sure you know what I mean...hence I cannot push any files to the phone, etc., at least not using adb in cmd.
That's actually the problem, that I cannot get adb to work, I only have fastboot commands. At least the way I see it now the question is how can I work with the phone to fix it just by having fastboot access in cmd.
I searched quite a lot various forums, etc, but I never came across a solution that will get things going just by having fastboot in cmd (without adb working). Maybe somebody here will come up with some magic trick...
Nerten said:
I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.
Click to expand...
Click to collapse
How did you end up having this problem, just like that or after some update, flash, etc?
Thanks!
have a look here mate http://forum.androidcentral.com/htc...9-bricked-my-evo-but-there-away-un-brick.html
same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!
sorry idf i don't underdstand, but if you have fastboot working in your device and sdcard also then you should be able to push files to device via fastboot making as clean installs as possible.so if your device is picked up by command line type fastboot to see command list. i'am a bit comfused. pretty sure you should fix it through fastboot though.
popepope said:
same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!
Click to expand...
Click to collapse
right, I can run 2 things with fastboot in cmd: (name of the files just an example)
1. fastboot update update.zip
here I get that the archive doesnt contain android-info.txt or android-product.txt
2. fastboot flash update.img
here i get signature verify fail
for example, fastboot erase radio says FAILED, remote: not allowed
there are some fastboot commands related to the kernel and some others, but dont know how to make use of them for my problem.
sd card is accesible for sure and it is a goldcard.
I saw some linux/ubuntu methods to simulate adb usage in cmd, but I dont think it will work...will try to find an ubuntu image and mount it under windows, but dont have time now...
anyways, thanks to everybody for the suggestions and interest, maybe we'll crack it some day
You need to use an official RUU zip image - i.e. a PB99IMG.zip. Not an update.zip.
Hi,
I need to retrieve my 1) contacts, 2) Messages. If someone could help i would be really grateful and appreciative.
My HTC One X is standard with no mods (software/hardware).
Ive never updated firmware from 4.0.2 i believe.
Recently i downloaded a few programs from Play store.
I dont know if that was what caused the problems but i started getting problems with the apps closing/crashing.
Long story short spoke to O2 whom im with who were no help just wanted me to factory reset. Spoke to Dialaphone who said factory reset. And tried a couple times with HTC with the second time the girl advisor suddenly saying she will terminate calls while i was talking of options and hwen i stated i had done nothing wrong ie did not raise voice, did not say anything bad/derogatory etc and why she was doing that she cut the call off. I was understandably very angry, and i feel i will not be buying a HTC again with that kind of treatment.
As i couldnt get into play store due to crashing apps. I rang HTC. When i first rang HTC they said backup and do factory reset. I asked how they said use HTC SYnc Manager. Dl'ed and connected phone. No phone coming up. The phone at the time was again crashing all the apps now inc the android core something app.
I uninstalled the recent apps i had installed. Two sound meter apps, two lightmeter apps.
And i restarted phone. Phone then restarted but has to date not gone past the HTC bootup animation screen.
I have used soft reset by using power button. Recovery mode by way of pressing volume button and power button and then selecting recovery. When i do do recovery it shows its doing something and then i get a red triangle with an exclamation mark.
Please i need help to retrieve the data contacts and mesages on the phone. Asi never had problems with the phone before i didnt get round to making a backup. Normally i used to do this but have had a lot of other things going on and have become somewhat lazy.
Many thanks
MazzaUK said:
Hi,
I need to retrieve my 1) contacts, 2) Messages. If someone could help i would be really grateful and appreciative.
My HTC One X is standard with no mods (software/hardware).
Ive never updated firmware from 4.0.2 i believe.
Recently i downloaded a few programs from Play store.
I dont know if that was what caused the problems but i started getting problems with the apps closing/crashing.
Long story short spoke to O2 whom im with who were no help just wanted me to factory reset. Spoke to Dialaphone who said factory reset. And tried a couple times with HTC with the second time the girl advisor suddenly saying she will terminate calls while i was talking of options and hwen i stated i had done nothing wrong ie did not raise voice, did not say anything bad/derogatory etc and why she was doing that she cut the call off. I was understandably very angry, and i feel i will not be buying a HTC again with that kind of treatment.
As i couldnt get into play store due to crashing apps. I rang HTC. When i first rang HTC they said backup and do factory reset. I asked how they said use HTC SYnc Manager. Dl'ed and connected phone. No phone coming up. The phone at the time was again crashing all the apps now inc the android core something app.
I uninstalled the recent apps i had installed. Two sound meter apps, two lightmeter apps.
And i restarted phone. Phone then restarted but has to date not gone past the HTC bootup animation screen.
I have used soft reset by using power button. Recovery mode by way of pressing volume button and power button and then selecting recovery. When i do do recovery it shows its doing something and then i get a red triangle with an exclamation mark.
Please i need help to retrieve the data contacts and mesages on the phone. Asi never had problems with the phone before i didnt get round to making a backup. Normally i used to do this but have had a lot of other things going on and have become somewhat lazy.
Many thanks
Click to expand...
Click to collapse
Maybe you will not be able to restore anything on your phone because of the factory reset but maybe you will have working phone. Go in bootloader and after this connect the phone to a computer you must see fastboot USB download fastboot and adb extract it to c:\fastboot open cmd and type cd\ after this cd fastboot and run the command fastboot getvar version-main and post the result here
Hi Thant,
Thanks for the help. To clarify i have not done any type of factory reset and do need the data. I have done a Recovery which showed the red triangle with exclamation mark.
If i do bootloader thing as you have specificed will it flash over the data?
Please let me know.
Many thanks
Thant said:
Maybe you will not be able to restore anything on your phone because of the factory reset but maybe you will have working phone. Go in bootloader and after this connect the phone to a computer you must see fastboot USB download fastboot and adb extract it to c:\fastboot open cmd and type cd\ after this cd fastboot and run the command fastboot getvar version-main and post the result here
Click to expand...
Click to collapse
Connected the phone to PC but PC says it doesnt recognise usb connection
Thant said:
Maybe you will not be able to restore anything on your phone because of the factory reset but maybe you will have working phone. Go in bootloader and after this connect the phone to a computer you must see fastboot USB download fastboot and adb extract it to c:\fastboot open cmd and type cd\ after this cd fastboot and run the command fastboot getvar version-main and post the result here
Click to expand...
Click to collapse
MazzaUK said:
Connected the phone to PC but PC says it doesnt recognise usb connection
Click to expand...
Click to collapse
You must to go in bootloader and choice fastboot after this connect the phone to computer. Then you must download fastboot files and paste in c:\fastboot. Then run cmd and navigate to this folder and run the command fastboot devices and you must to your S/N. If you didmn't see the phone install latest HTC drivers and post the result from command fastboot getvar all and delete your S/N and IMEI from the info
Thats perfect. It worked. Thank you.
I Have attached an image with the results.
Thant said:
You must to go in bootloader and choice fastboot after this connect the phone to computer. Then you must download fastboot files and paste in c:\fastboot. Then run cmd and navigate to this folder and run the command fastboot devices and you must to your S/N. If you didmn't see the phone install latest HTC drivers and post the result from command fastboot getvar all and delete your S/N and IMEI from the info
Click to expand...
Click to collapse
MazzaUK said:
Thats perfect. It worked. Thank you.
I Have attached an image with the results.
Click to expand...
Click to collapse
Download THIS and run as Administrator and fallow the instruction. To hope you will not lose any data because if you unlock your bootloader have big chance to wipe everything
MazzaUK said:
Thats perfect. It worked. Thank you.
I Have attached an image with the results.
Click to expand...
Click to collapse
Any news with the RUU?
I followed the instuctructions and the phoe rebooted and started working and booted into Android. But messages and contacts seem to have been erased in the process as nothing is showing.
Thant said:
Any news with the RUU?
Click to expand...
Click to collapse
Yeah that's what a ruu does, it deletes everything and put the phone back to factory stock
MazzaUK said:
I followed the instuctructions and the phoe rebooted and started working and booted into Android. But messages and contacts seem to have been erased in the process as nothing is showing.
Click to expand...
Click to collapse
Yes but you have your pictures you must to use google acount for future to not lose your contacts. sorry but I say in my first post maybe you will not restore your data but you will have working phone. Sorry again for the contacts and for future use google account
For me the phone didnt matter but i needed the messages and contacts. My fault for not backing them up but they were all very important to me. If there was a glitch/hack that allowedrooting without wipe i think that would have been a way around it. Even HTC didnt want to help which i think is silly for situations where it is vitally important info and for fee as well not a freebie.
Thank you for your help anyways in getting the phone past bootloop.
Thanks
Thant said:
Yes but you have your pictures you must to use google acount for future to not lose your contacts. sorry but I say in my first post maybe you will not restore your data but you will have working phone. Sorry again for the contacts and for future use google account
Click to expand...
Click to collapse
MazzaUK said:
For me the phone didnt matter but i needed the messages and contacts. My fault for not backing them up but they were all very important to me. If there was a glitch/hack that allowedrooting without wipe i think that would have been a way around it. Even HTC didnt want to help which i think is silly for situations where it is vitally important info and for fee as well not a freebie.
Thank you for your help anyways in getting the phone past bootloop.
Thanks
Click to expand...
Click to collapse
No way to restore contact or message from broken phone sorry. If you unlock the bootloader have big chance to lose your picture but with RUU you keep them and lose only data,system and cache partition on the phone
Thant said:
No way to restore contact or message from broken phone sorry. If you unlock the bootloader have big chance to lose your picture but with RUU you keep them and lose only data,system and cache partition on the phone
Click to expand...
Click to collapse
I have latest firmware and phone constantly restarts and more recently screen freezes. Mainly restarts all the time. Fed up of htc and their problems
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Did your phone just reboot in the middle of doing something innocuous then start bootlooping? Were/Are you on total stock with bootloader locked? If both yes, it is probably hardware issue you are encountering.
Regarding sideloading, did you place your Android recovery in sideload mode?
Did you verify adb can "see" your device using "adb devices"?
SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Well luckily I made this post today.
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
SomewhatIrked said:
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
Click to expand...
Click to collapse
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
bardhi92 said:
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
Click to expand...
Click to collapse
In short:
OTA rescue failed during adb sideload,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue claims to have failed at 47% during adb sideload- still booted into android. However briefly. Went back to bootloop,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue completed via adb sideload,
Turned on dev options (usb debug, oem unlock),
Booted to fastboot - unlocked bootloader. Now back to bootlooping
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
SomewhatIrked said:
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
Click to expand...
Click to collapse
IMO you shouldn't flash the TOT file. If you end up bootlooping again, your phone will be stuck in bootloader locked mode with no ability to unlock it.
If you were able to get your phone to boot into android once, there is really nothing the TOT file will do for you that you can't do from TWRP or bootloader, whereas once it locks your bootloader, there are problems you can no longer fix like EFS corruption (which likely isn't your problem).
In the end, you probably do have eMMC that is slowly starting to fail. There is usually error correction on the eMMC that can lock out bad blocks but if it gets to serious, it'll fail. This is why reflashing stuff over and over sometimes works.
HTC One M9
Android 6
Bootloader Locked
S=On
USB debugging disable
today I found my phone stock on decryption screen! I did not enable encryption mode. now my phone says: your phone is encrypted. to decrypt your phone, enter your Screen lock password.
it does not matter what number I enter! every number I enter, it says: Decryption unsuccessful. the password you entered is correct, but unfortunately, your data is corrupt. to resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
But nothing happened when I press the "reset phone" button. I waited 4 hours but it remains on a window named "Factory data reset, Rebooting..." but it can not proceed to reboot.
when I power off and go to bootloader, I can not go to recovery mode. on recovery mode, there is only a triangle with a red exclamation mark.
I download a stock ROM so I can flash it to my phone from download mode, but at the beginning of flashing process it comes with this error
12 RU_ZIP_ERROR
please help me
sjmahmoudi said:
HTC One M9
Android 6
Bootloader Locked
S=On
USB debugging disable
today I found my phone stock on decryption screen! I did not enable encryption mode. now my phone says: your phone is encrypted. to decrypt your phone, enter your Screen lock password.
it does not matter what number I enter! every number I enter, it says: Decryption unsuccessful. the password you entered is correct, but unfortunately, your data is corrupt. to resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
But nothing happened when I press the "reset phone" button. I waited 4 hours but it remains on a window named "Factory data reset, Rebooting..." but it can not proceed to reboot.
when I power off and go to bootloader, I can not go to recovery mode. on recovery mode, there is only a triangle with a red exclamation mark.
I download a stock ROM so I can flash it to my phone from download mode, but at the beginning of flashing process it comes with this error
12 RU_ZIP_ERROR
please help me
Click to expand...
Click to collapse
This problem has been posted from time to time by other users - it often indicates a corrupt chip in the motherboard.
Depending on your SKU and whether or not there really is a hardware issue or not, it may be possible to apply a RUU, which would effectively restore your phone to factory state (though it will wipe your internal memory).
Please post your OS version, which will help us determine your phone's SKU.
If you put the phone in download mode and plug it into a pc then run fastboot.exe with the cli command 'fastboot getvar all' you will get a lot of important information.
If you are absolutely sure your phone has never been modified and it shows on the fastboot output "status modified" then you can assume your phone has hardbricked from a faulty nand. Only HTC can fix it in the case.
Beamed in by telepathy.
computerslayer said:
this problem has been posted from time to time by other users - it often indicates a corrupt chip in the motherboard.
Depending on your sku and whether or not there really is a hardware issue or not, it may be possible to apply a ruu, which would effectively restore your phone to factory state (though it will wipe your internal memory).
Please post your os version, which will help us determine your phone's sku.
Click to expand...
Click to collapse
os: 3.35.401.32
shivadow said:
If you put the phone in download mode and plug it into a pc then run fastboot.exe with the cli command 'fastboot getvar all' you will get a lot of important information.
If you are absolutely sure your phone has never been modified and it shows on the fastboot output "status modified" then you can assume your phone has hardbricked from a faulty nand. Only HTC can fix it in the case.
Beamed in by telepathy.
Click to expand...
Click to collapse
I rooted this phone when I first bought it. but 4 months ago I unroot it so I could update it's android to marshmallow. after unrooting, i receive the android update and everything was as normal as a fresh unrooted phone.
I was able to go to download mode when first my phone faced this problem. but now the download mode is not available
it says: failed to boot to download mode
press volume up or down to back to menu
this build is for
development purposes only
do not distribute outside of HTC
without HTC's written permission.
Failure to comply may
lead to legal action.
computerslayer said:
This problem has been posted from time to time by other users - it often indicates a corrupt chip in the motherboard.
Depending on your SKU and whether or not there really is a hardware issue or not, it may be possible to apply an RUU, which would effectively restore your phone to factory state (though it will wipe your internal memory).
Please post your OS version, which will help us determine your phone's SKU.
Click to expand...
Click to collapse
I took my m9 to HTC service center. he said that main chip must be replaced. after replacing the chip, he said that I need a dump.bin file and I do not have it. now after 3 months, my dear m9 is still on the service center . I search all over the net for the dump.bin file but there is nothing at all.
I do not even know what the hell is the dump.bin file. he said that your phone can boot but it will not have antenna without relevant dump file. I'm confused please help me
my phone model ID: 0PJA100
Did you give your phone to an official HTC service center? HTC should have the needed file so the fact that you should provide it to the service center confuses me a bit.
It's impossible to get that file (from a working phone) without a JTAG device and I doubt that many M9 owners have one since they're quite expensive. Sorry for the bad news.