Related
Hello! Got DHD 2.50.405.2, downgraded it with fr3evo and misc_version to 1.32, and after this something happend with ?hboot? - powering up takes about 30 minutes - 20 minutes just black screen(so I thought phone completely broken), then HTC logo with approx 10 mins vibro, approx 5 mins silent, boot to android and then - working fast as usual. USB connection not recognizes, reboot to bootloader takes eternity and locks up in menu(maybe its just makes a move onse an hour, I dont tested so long)
Any advises?
... and you've flashed a new radio, flashed a 3rd party recovery, and a new rom as well?
.... or are you still running 1.32 since you didnt really understand why you were downgrading in the first place?
JSLEnterprises said:
... and you've flashed a new radio, flashed a 3rd party recovery, and a new rom as well?
.... or are you still running 1.32 since you didnt really understand why you were downgrading in the first place?
Click to expand...
Click to collapse
I am running unrooted 1.32 because bootloader freezes and usb connection not recognizes, just charging. This thing begins on the first reboot after 1.32 flashing, so I was unable to root, s-off etc. I have a plan to try root\s-off and manualy write hboot\radio in partitions area from terminal emulator, but want to gather some info before doing this, maybe there is another way? And what is so special in 2.50 stock rom phones so they acting so strange way on downgrade? Differs in hardware, deep fw versions or it was just corrupted 1.32 flashing?
Hello.
First sorry for my bad english.
I have exact the same problem after I tryed this new tool : Advanced Ace Hack Kit
But my phone is root and s-off
I can not boot to recovery. Not with buttons and not with my rom manager.
How can I flash new image?
Please can anyone help us.
Thanks a lot
Picture is not from my phone but almost like that
Now I can boot to Recover with 4ext Recovery Control.
I can flash any rom but it need 15 minutes to boot up
Need help to fix it.
slow boot
me too...downgraded...now taking lots of time to boot...what did u do to correct...am going to flash a gb rom to c how it goes...
Did anyone find a fix for this issue? I'm currently having the same problem!
Help!!! Does anyone know a solution to this??
Slow boot as in the bootloader part(white HTC)?is is followed by long vibrate?
markmmxtech said:
Slow boot as in the bootloader part(white HTC)?is is followed by long vibrate?
Click to expand...
Click to collapse
Yeah that's the one, once loaded it's fine so currently just hoping the battery doesn't run down or that I need a restart soon - but can't live like this forever
goldielocks said:
Yeah that's the one, once loaded it's fine so currently just hoping the battery doesn't run down or that I need a restart soon - but can't live like this forever
Click to expand...
Click to collapse
as ive said..after downgrading, update through OTA or install an RUU then root it with Ace advance kit..I was having the same issue before, the one I mentioned above solve that matter
markmmxtech said:
as ive said..after downgrading, update through OTA or install an RUU then root it with Ace advance kit..I was having the same issue before, the one I mentioned above solve that matter
Click to expand...
Click to collapse
It worked!! Now back to booting very quickly
Thanks for your help!!
cheers
It worked!! Verry thanks for your help!!
!!! After downgrading 1.32, i flash 2.50 used Advance Ace Kit. (copy "PD98IMG.zip" ver 2.50 into "aahk-29102011\PD98IMG\" ) It very very long time..... So be patient !!!
how much of time it takes please help ? because I need more info about this ?
Thanks
please help me
goldielocks said:
It worked!! Now back to booting very quickly
Thanks for your help!!
Click to expand...
Click to collapse
Hey ma., will u please help me, i have the same issue, my dhd not going to bootloader anymore, will u please tell me the steps u did in Ace Hack toolkit.
Thanks a lot
Hi,
My One X got the OTA update yesterday to go to 1.28
today I was flashing a ROM via recovery but something went wrong and afterwards the phone wouldn't boot up just got stuch at the HTC logo page.
Since then I've been trying to sort it out but with limited success.
I've essentially followed the advice given on this thread;
http://forum.xda-developers.com/showthread.php?t=1599748&page=4
However nothing has worked for me. I've tried flashing the RUU from here:
http://forum.xda-developers.com/showthread.php?t=1543604
But it won't install as I was already on 1.28.
After that I tried taking a boot_signed.img and system.img from the RUU. i was able to flash the boot_signed.img ok but when I try to flash the system.img I get an error as follows:
" FAILED (remote: (00000006))"
Does anyone know what this means? Is it something to do with the size of the system.img?
apart from getting this working there doesn't seem to be anything I can do other than wait for the 1.28 RUU to be released.
If anyone has any ideas I'd be really appreciative as I've got a pretty useless phone right now.
Thanks in advance.
Hi all
I have the same problem, i flashed the 3 dot fix from http://forum.xda-developers.com/showthread.php?t=1582506, not fully paying attention at the time that it was only for custom roms.
I am now stuck at the htc beats screen. Have done all the above and get the same error with system.img.
I have left it a few days without being able to use my phone in the hope that i could find a fix to very little success.
So please if anyone could help in any way would be much appreciated.
Thanks
- you need to have ruu of .28 (i don't think there is yet) and run the EXE file as you can't fastboot flash as of now
- you need to install htc software before you run ruu exe.
as for russel if you did not OTA read this
http://forum.xda-developers.com/showthread.php?t=1599748
same problem, waiting for a 1.28 ruu (chinese one didn't work (of course, but had to try anyway)). going to a Vodafone shop that has a technician on site, see if they can help (maybe they already have a 1.28 ruu).
noromamai said:
same problem, waiting for a 1.28 ruu (chinese one didn't work (of course, but had to try anyway)). going to a Vodafone shop that has a technician on site, see if they can help (maybe they already have a 1.28 ruu).
Click to expand...
Click to collapse
Where did you find the chinese version? We may be able to flash the system.img from that RUU
The moral of the story...always nandroid.
can't remember from which site it was, but there was a thread here about it (maybe in the dev section) with a link to a chinese site. took about 5 hours to download (i'm in europe).
was just in the vodafone shop, spoke to a technician, they don't have ruu 1.28, but he was going to ask around and told me to contact him in a week to see if he managed to get it.
A week? Hopefully someone will have posted it before then, hope so anyway, I need my phone back
If anyone could confirm what the fastboot error "remote:000000006" means I might be able to get around it.
Maybe it is because it is the wrong version.
"remote:000000006" = file too large. There is a way to by-pass it, but can't remember how exactly. There should be another fastboot? a "gray htc one"? Just my 2 cents.
disclaimer: (for all other readers) note that flashing boot.img and system.img is not recommended. use RUU's instead
riemervdzee said:
"remote:000000006" = file too large. There is a way to by-pass it, but can't remember how exactly. There should be another fastboot? a "gray htc one"? Just my 2 cents.
disclaimer: (for all other readers) note that flashing boot.img and system.img is not recommended. use RUU's instead
Click to expand...
Click to collapse
Thanks for this, I'll have a dig around and see if there is another fastboot available.
In work now so will have a play around later.
EDIT: If you remember what the workaround for that issue was please let me know.
jedi5diah said:
-
as for russel if you did not OTA read this
http://forum.xda-developers.com/showthread.php?t=1599748
Click to expand...
Click to collapse
I have try that method, but when it says "install RUU" how? i took the ROM.zip out and tried to flash the recovery.img that went fine and then when it came to the system.img says failed with the error from the 1st post.
I cannot run the RUU.exe as it say device cannot be found. (Have htc sync and drivers.)
Also tried differnt fastboots.
Lastly does the bootloader have to be locked or unlocked?
you have to flash back the original recovery, relock (fastboot oem lock) the phone, boot back into bootloader (power + volume down), make sure you have hts sync installed with the drivers, run ruu exe and follow onscreen instructions.
I think you need to be in fastboot then connect your phone to the pc and then run the exe and it should recognise your phone.
As mentioned above you also need to relock your bootloader before running the RUU.
When i run the RUU.exe and follow on screen instructions says device not found. I have htc sync installed and the drivers.
when i load back into bootload (the step before run RUU) do i enter back into FASTBOOT or stay in HBOOT?
EDIT: now got error battery below 30% so ill recharge and try again later. Thank you all for helping (wether this works or not) really appreciate it. (Sorry to the Op for deviating slightly from post. Didn't realize my issue was slightly differnt from yours.)
when this happen to me i just put the usb wyre en another usb port and restart my computer, this solve the problem
I finally got it to run the RUU, but now get the error 140: BOOTLOADER VERSION ERROR.
Have i downloaded the wrong RUU? as far as i have found there only 2 for Europe?
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.26.401.2_Radio_1.1204.90.13_release_251208_signed.exe
Thats the one i have. Im on contract (O2), live in south east england.
Thanks.
You may have the same issue as me. Did you update your firmware via an over the air update this week?
If yes you will have to wait for the 1.28 RUU to be released.
Sadly yes. Just minutes before applying the 3 dot fix. Was late at night wasnt paying attention.. So now its the waiting game. Thanks all.
russelblack said:
Sadly yes. Just minutes before applying the 3 dot fix. Was late at night wasnt paying attention.. So now its the waiting game. Thanks all.
Click to expand...
Click to collapse
Hopefully we won't have to wait too long. The OTA came out on Thursday I think so we should have the RUU in the next few days....
The new RUU should be available for download tonight:
http://forum.xda-developers.com/showpost.php?p=25125579&postcount=381
Hi guys,
This is my first thread here in XDA, so, forgive me by a possible mistake.
I recently bought a HOX, the seller said that is the international version.
I'm in 4.0.3, with software version 1.29.707.11 (already checked for updates, but phone says its up to date)
So, sometimes when i turn my wifi on, he doesn't connect in my network (already saved), i go to wifi settings, put to scan, and, aparently, the phone don't scan the networks and doesn't found my network too.
Obviously, im on the range of the network, and don't have that factory problem with bad wifi signal.
And, sometimes too, phone takes a lot of time to get carrier signal, so i turn on plane mode, then turn off, and finally get carrier signal.
My question is: is this normal? What can i try to fix it? (Thinked on a factory reset)
I don't tried anything yet.
If anyone could help, i'll appreciate and if the thread is on the wrong place, please move it
Just try flashing the RUU, which will delete everything and return it to stock.
BenPope said:
Just try flashing the RUU, which will delete everything and return it to stock.
Click to expand...
Click to collapse
Thanks for the help Pope!
I am VERY noob in HTC tools, can you say me what exactly is this "RUU", and where i can get it?
Its basically, a factory reset right? What is the difference from normal FR to this RUU tool?
lock! said:
Thanks for the help Pope!
I am VERY noob in HTC tools, can you say me what exactly is this "RUU", and where i can get it?
Its basically, a factory reset right? What is the difference from normal FR to this RUU tool?
Click to expand...
Click to collapse
The difference is that it will reflash the ROM from scratch, it's the first thing HTC do when you take your phone for repair. It's very safe (when flashed with decent remaining battery) and very thorough.
Check the Shipped ROM sticky in the development section.
I am searching about the Rom Update Utility, but i'm not finding a good tutorial to follow, explaining the whole process.
If anyone could help me in the process :laugh:
Edit:
Thanks again Pope! I'll look in dev section
You just have to charge the phone, put the phone in fastboot mode (hold down the volume down key when switching on the phone, then navigate from there), plug phone into Windows PC and double click RUU.
You may want to do an "adb backup" (you'll have search for this) beforehand, flash RUU, test and then restore.
BenPope said:
You just have to charge the phone, put the phone in fastboot mode (hold down the volume down key when switching on the phone, then navigate from there), plug phone into Windows PC and double click RUU.
You may want to do an "adb backup" (you'll have search for this) beforehand, flash RUU, test and then restore.
Click to expand...
Click to collapse
I'm not finding the correct RUU file for the One X, can you help me? Or just show me a place to search... (Some links here at job are blocked --') Basically finding the correct RUU file i'll do the rest without problem...
This "restore" you mean in the end, its the factory reset in the phone? Or another restore?
Don't need a backup, i got the phone 2 days ago hehehe
My HOX is totally clean.
No unlocked bootloader, no root.
This will not be a problem doing the flash with the stock RUU right?
lock! said:
My HOX is totally clean.
No unlocked bootloader, no root.
This will not be a problem doing the flash with the stock RUU right?
Click to expand...
Click to collapse
No, that's perfect, you don't need anything other than stock, and it will remain stock.
http://www.filefactory.com/file/5c0...Radio_1.1204.105.14_release_260743_signed.exe
BenPope said:
No, that's perfect, you don't need anything other than stock, and it will remain stock.
http://www.filefactory.com/file/5c0...Radio_1.1204.105.14_release_260743_signed.exe
Click to expand...
Click to collapse
Ben sorry for tons of questions hehe
I'm reading a tutorial, and on it said that i need my CID number, in order to download the correct RUU file for the correct region of my HOX. How can i know if this RUU you posted is the correct for my HOX?
I've tried to get my CID number (downloaded the fastboot flasher tool) but when i put the cid command he returns: CID > None lol
I Know that my HOX is from Shangai (has a SH in serial number) and got my MID number.
So, i just need to know which file i need to download, the right one of course hehehe
If i will need the CID to know, i'll ask for the files for fastboot commands (i don't found them)
If not, just confirm the link you posted ealier if its the correct RUU for my case.
PS.: This link posted is only for premium users, and i don't have a premium acc, can you provide in another mirror?
You can't flash the wrong RUU, the phone won't let you.
You don't need your CID as you are not unlocked, knowing that you are 1.29.707.x is enough. It's the right RUU.
I'm sure you don't need me to hold your hand whilst you use google to find that file somewhere else. The sticky dev thread I previously mentioned will likely have a ton of mirrors for the file.
So.. i'll look fot the file in other places.
Today, i've connected in my wifi network, and the phone says there's an update...
It's the same update announced days ago, but in my case with a different update number...
Phone has been upgraded to ICS 4.0.4 and Sense 4.1.
If the problems persist, i will flash the RUU anyway, but, because of this update, nothing changes right? The RUU file you posted still valid for my HOX?
Not any more, you've updated your hboot, so you'll need an updated RUU (you can't install on older hboot, packaged with an older RUU).
You're lucky:
http://www.filefactory.com/file/3rc...Radio_2.1204.135.20_release_278245_signed.exe
and
http://forum.xda-developers.com/showpost.php?p=30273253&postcount=1724
BenPope said:
Not any more, you've updated your hboot, so you'll need an updated RUU (you can't install on older hboot, packaged with an older RUU).
You're lucky:
http://www.filefactory.com/file/3rc...Radio_2.1204.135.20_release_278245_signed.exe
and
http://forum.xda-developers.com/showpost.php?p=30273253&postcount=1724
Click to expand...
Click to collapse
HELL YEAH!
I'll test for 2 ~ 3 days, if i note the same problem i'll flash it!
Thanks for all the help Pope!
With this 707 update I got better WiFi ..smooth, fast...amazing
Sent from my HTC One X using XDA Premium HD app
dragonesdenano said:
With this 707 update I got better WiFi ..smooth, fast...amazing
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Same here man...
In a network that once stood in 40% signal, now i'm getting almost 100%!
Apparently, carrier signal is working fine too.. i'll test for more 3 days...
here's the situation
i have recently bought refurbished htc one x
i wanted to update it with offical jelly bean update it showed me
th update downloaded and i proceed to install it, i was a long time on the installing icon so i left my phone, when i got back it wouldnt turn on like the batery was empty
before doing the update it showed around 50% so i wasnt thinking about it, but it seems i died during the update
now - i cannot turn my phone on, its stuck on htc logo, i can access bootloader mode, it says i have hboot 1,12
radio 5.1204.162,29
the bootloader is locked
could someone tell me in simple steps how to bring it alive? is it even possible?
I havent flashed my one x in a while, but try charge it as much as you can while in recovery or bootloader mode.
Then try unlocking the bootloader using htcdev and Hasoons all in one toolkit from the dev section.
That will help you get a custom recovery installed and allow you to reinstall another firmware.
Not sure how much you already know so I apologise if this is basic info haha.
Also dont forget to flash the boot.img if you go with a custom rom
Good luck
Sent from my GT-N7100 using xda premium
Return it for repair if you can. Unlocking bootloader is the hard way out if you ask me.
Sent from my HTC One X
A ruu might be a way out, but it's a long shot because the ruu doesn't need a unlocked bootloader.
Mr Hofs said:
A ruu might be a way out, but it's a long shot because the ruu doesn't need a unlocked bootloader.
Click to expand...
Click to collapse
Try this first.
I completely forgot about RUUs. You need to get the one that matches your CID
Sent from my GT-N7100 using xda premium
Sending it for repair isnt really an option as i bought the device and now im leaving the uk.
so they would send it back to me as ill be in another country.
also i opened it as i had the anthena problem but i solved it.
software speaking, as that is the problem, is it harf to fix?
i had couple of androids and customized all of them, but im new to htc and all that ruu,cids...
i dont mind custom rom, right now i just want to recover any functionality.
So if the ruu is the easiest way out is there a newbie tutorial? as i cant find it
and is unlocking the bootloader, flashing a custom recovery ans rom is so complicated to other devices?
i dont.know.what do you nean by flashing boot.img while flashing rom
When you run an ruu the computer end of it walks you through what to do. Make sure you have latest version of htc sync installed and do exactly what it says. Also returning it is the best option under normal circumstances. I did exactly that when ota wrecked my shift
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Webbage said:
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Click to expand...
Click to collapse
You don't provide much information so it's hard to help. So let's start at the bginning: What firmare version are you using? (It's stated in Download Mode in the line with "OS" at the beginning.)
You tried to flash a RUU? Which one? Have there been any error outputs? If yes, which ones? Since you're S-OFF flashing a RUU should not be a problem at all so these outputs are very important if you want any help.
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Webbage said:
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Click to expand...
Click to collapse
As far as I know Sneakyghost doesn't provide any RUUs. Those are only firmware packages that do not contain a rom. So it's no miracle that you're still booting ARHD.
You can download O2 RUUs from here, here or here. Any of the X.XX.206.X files will work since you are S-OFF. Do you have a SD card that is not bigger than 32gb? If yes, format it to fat32, copy one O2 RUU to its root directory and rename that file to "0PJAIMG.zip". If you then boot to Download Mode you will be asked to push the Volume Up button and the RUU will start flashing. If it reboots to system instead of rebooting to Download Mode you will have to power off your phone and boot to Download Mode manually. The RUU will continue then. At the end you will be asked to push the power button so that your phone gets shut down. If you now start your phone you will be back on a stock system.
Be aware that there is no RUU for your current firmware. Since you're S-OFF that doesn't matter but your phone will be downgraded at the end.
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Webbage said:
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Click to expand...
Click to collapse
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Agreed, use the s-off command to change back to "LOCKED" and leave it s-off. Too much of a risk otherwise.
If in the unlikely event they see it, you can play dumb, because a few rare people have gotten s-off phones from the factory and it doesn't prove you did anything.
Flippy498 said:
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Click to expand...
Click to collapse
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Webbage said:
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Click to expand...
Click to collapse
Didn't the RUU flash the corresponding stock recovery?
Flippy498 said:
Didn't the RUU flash the corresponding stock recovery?
Click to expand...
Click to collapse
My bad, I didn't check.
All sorted now, thanks again bud!