Hello,
I have noise on calls voip (whatsapp, skype, etc) i tried with any custom ROMs (4.4.2, 5.1.1, etc) and dont find solution.
Model: HTC 6435LVW
HBOOT-1.33.0001
RADIO-1.01.04.0801
Tnks
I had the same issue, flashing original RUU solved the problem. I cant recall where I read the explanation but it was described as a partition problem and flashing RUU solved it as it repartitions all the memory.
Warning: flashing RUU will replace your current rom and all your data. also will replace kernel, firmware, recovery... everything.
barantunc said:
I had the same issue, flashing original RUU solved the problem. I cant recall where I read the explanation but it was described as a partition problem and flashing RUU solved it as it repartitions all the memory.
Warning: flashing RUU will replace your current rom and all your data. also will replace kernel, firmware, recovery... everything.
Click to expand...
Click to collapse
Where I can find the original RUU and how flashing RUU?
You can find it by searching DNA section of the forum
barantunc said:
You can find it by searching DNA section of the forum
Click to expand...
Click to collapse
Is not there any rom that works with VoIP?
neb2567 said:
Is not there any rom that works with VoIP?
Click to expand...
Click to collapse
after flashing RUU and fix those partition problems, you can flash any other rom and VOIP will work fine.
Could you please help me with the thread to flash the RUU ?, I have searched and have not found.
Thanks
neb2567 said:
Could you please help me with the thread to flash the RUU ?, I have searched and have not found.
Thanks
Click to expand...
Click to collapse
This one should help you.
http://forum.xda-developers.com/droid-dna/general/official-exe-ruus-s-t2935556
barantunc said:
This one should help you.
http://forum.xda-developers.com/droid-dna/general/official-exe-ruus-s-t2935556
Click to expand...
Click to collapse
When I try to flash upgrade hboot I have this error, any solution?
sending 'zip' (558 KB)...
OKAY [ 0.205s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 0.424s
Click to expand...
Click to collapse
Related
I rooted my Droid Incredible 4G and everything went fine. I was able to use Hasoon2000's AI1K which worked great. However, I ended up trying to install a custom font through ROM Toolbox Pro, which ended up locking up the phone. After I rebooted, it just stuck on the eye logo and wouldn't actually load the OS. Being the idiot that I am, I wiped the OS through TWRP v2.1.8. I'm really not sure why I ever thought that would be a good idea in hindsight.
I can access the hboot menu and everything, I don't think this is beyond repair, I just have no idea what to do at this point. Also worth noting when I try to do anything in the Al1K program it says no device detected at this point. I found this thread but unfortunately I don't think it applies to the version of TWRP I've got.
BatmanJones said:
I rooted my Droid Incredible 4G and everything went fine. I was able to use Hasoon2000's AI1K which worked great. However, I ended up trying to install a custom font through ROM Toolbox Pro, which ended up locking up the phone. After I rebooted, it just stuck on the eye logo and wouldn't actually load the OS. Being the idiot that I am, I wiped the OS through TWRP v2.1.8. I'm really not sure why I ever thought that would be a good idea in hindsight.
I can access the hboot menu and everything, I don't think this is beyond repair, I just have no idea what to do at this point. Also worth noting when I try to do anything in the Al1K program it says no device detected at this point. I found this thread but unfortunately I don't think it applies to the version of TWRP I've got.
Click to expand...
Click to collapse
if you have a nandroid backup just restore it.
are you s-off or just unlocked
Aldo101t said:
if you have a nandroid backup just restore it.
are you s-off or just unlocked
Click to expand...
Click to collapse
Thanks for the quick response. I don't have a nandroid backup and I'm just unlocked as far as I know. I only used the AI1K from Hasoon.
BatmanJones said:
Thanks for the quick response. I don't have a nandroid backup and I'm just unlocked as far as I know. I only used the AI1K from Hasoon.
Click to expand...
Click to collapse
i didn't knw hasoon had a tool that worked for unlocking bootloader, unless he made a new one we all used the team fireballas fakecid method to unlock, but since then unlimited.io team has a s-off tool. at this point i don't know what to tell you except you may need to do an RUU and flash the original stock rom. i don't know what rom you are on. the first thing you should do after installing a custom recovery is make a nandroid backup to fall back on, so?
Aldo101t said:
i didn't knw hasoon had a tool that worked for unlocking bootloader, unless he made a new one we all used the team fireballas fakecid method to unlock, but since then unlimited.io team has a s-off tool. at this point i don't know what to tell you except you may need to do an RUU and flash the original stock rom. i don't know what rom you are on. the first thing you should do after installing a custom recovery is make a nandroid backup to fall back on, so?
Click to expand...
Click to collapse
Oh, right... I did use the fakecid method to unlock it originally.
Aldo101t said:
you may need to do an RUU and flash the original stock rom
Click to expand...
Click to collapse
Hopefully that would work.. could you point me in the right direction here? (how do I do that)
BatmanJones said:
Oh, right... I did use the fakecid method to unlock it originally.
Hopefully that would work.. could you point me in the right direction here? (how do I do that)
Click to expand...
Click to collapse
go to unlimited.io for the ruu and follow the directions there to ruu the stock rom
Aldo101t said:
go to unlimited.io for the ruu and follow the directions there to ruu the stock rom
Click to expand...
Click to collapse
Alright, thanks for the help again. I'm going to give this a go and come back to update.
BatmanJones said:
Alright, thanks for the help again. I'm going to give this a go and come back to update.
Click to expand...
Click to collapse
okey dokey
So I got this twice:
c:\Users\Aj\Desktop\rab>fastboot flash zip RUU.zip
sending 'zip' (583416 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image
INFOsignature checking...
FAILED (remote: 92 supercid! please flush image again immediately)
Click to expand...
Click to collapse
Third time I got this:
c:\Users\Aj\Desktop\rab>fastboot flash zip RUU.zip
sending 'zip' (583416 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFOsignature checking...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
INFO...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Click to expand...
Click to collapse
I'm going to try it again since that's what the site says.
BatmanJones said:
So I got this twice:
Third time I got this:
I'm going to try it again since that's what the site says.
Click to expand...
Click to collapse
when you get that error just retype the command:fastboot flash zip RUU.zip---immeadiately after in the same cmd prompt
OH, you need to relock bootloader TOO, sorry forgot this, unless you saw that in directions
And we're back in a working state again. Thanks so much, couldn't have had a better experience with my first thread on this forum. I'm so happy I didn't ruin my phone :laugh:
BatmanJones said:
And we're back in a working state again. Thanks so much, couldn't have had a better experience with my first thread on this forum. I'm so happy I didn't ruin my phone :laugh:
Click to expand...
Click to collapse
ME TOO, glad you got it goin!!
WELL, welcome to the GANG
Hello,
I have tried to flash a custom ROM to my htc desire x but unfortunetly I am a almost complete noob. I have been using Desire_X_All-In-One_Kit_v2.0 in order to complete the action. The problem is that i have never rooted the fone nor i have put in the recovery into it. So basically i unlocked the bootloader and thought it would all work.Well you know yourselfs it didn't.I have been looking all over the place for a way to get my phone fixed and i found one(ima Junior member can't post links yet ( Re-flash stock ROM (RUU) after bricking a rooted device)) .I have done all the steps but in step5 i get an error
C:\rec>fastboot flash recovery recovery_signed.img
sending 'recovery' (4266 KB)...
OKAY [ 0.795s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.323s
and in step 7 i get Error 140 bootloader error during RUU
Any help here would be greatly appreciated
Regards Kuba
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
nlooooo said:
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
Click to expand...
Click to collapse
How do you mean? do you mean whats written when i enter the bootloader or what have I written in in the terminal ( eg. fastboot flash recovery recovery_signed.img)
Thanks a lot for your quick reply
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
nlooooo said:
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
Click to expand...
Click to collapse
*****RELOCKED********
PROTO PVT SHIP S-ON RL
HBOOT-1.24.0000
RADIO-1.10.40.23
eMMC-boot
Oct 30 2012, 20:09:09
The most recent RUU i have downloaded is RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed
But i have read that FAILED <remote: signature verify fail> error that im getting is related to wrong ruu .I guess you know better
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
nlooooo said:
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
Click to expand...
Click to collapse
Great man!! thanks for help!! Could you just make it clear what i need in the folder with the ruu ?. its Adb.exe AdbWinAp.dll fastBoot.exe and the image file? is there anything else i would need? (as you see i know basically nothing about this)
It's not a folder its exe file, just run it from PC.
nlooooo said:
It's not a folder its exe file, just run it from PC.
Click to expand...
Click to collapse
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
hlick14 said:
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
Click to expand...
Click to collapse
That's why I'm here and that's what the thanks button stands for...
hi. my htc amaze is softbreaked and i need RUU to flash it . i don't know CID . How do I know which RUU i download ? i tested all i have file but did not answer.
pourya-man said:
hi. my htc amaze is softbreaked and i need RUU to flash it . i don't know CID . How do I know which RUU i download ? i tested all i have file but did not answer.
Click to expand...
Click to collapse
Maybe you can find your CID this way:
http://forum.xda-developers.com/showthread.php?t=1548090
pbergonzi said:
Maybe you can find your CID this way:
http://forum.xda-developers.com/showthread.php?t=1548090
Click to expand...
Click to collapse
thank's :laugh:
CID is HTC__044
Which RUU do I get?
pourya-man said:
thank's :laugh:
CID is HTC__044
Which RUU do I get?
Click to expand...
Click to collapse
If you are capable enough to flash your phone, you are capable of searching.
I searched, and without any certainty of what you did do or should do, found this link:
http://forum.xda-developers.com/showpost.php?p=41310223&postcount=135
If this link is helpful to you, be certain to use proper instructions for what you want to do.
Let me repeat that, "Be certain to use proper instructions for what you want to do."
thank my friend . problem fixed
Glad for you--you're getting pretty good at this.
Hello again . i s-off amaze and updated to ics but can't flash recovery
log :
---------------------------------------------------------------------------------------------------------------------------------
E:\Application\Android\Phone\HTC\01 Fastboot>"E:\Application\Android\Phone\HTC\0
1 Fastboot\Flash Recovery.bat"
E:\Application\Android\Phone\HTC\01 Fastboot>fastboot flash recovery recovery.im
g
sending 'recovery' (5502 KB)... OKAY [ 1.264s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.580s
---------------------------------------------------------------------------------------------------------------------------------
hboot is locked . i can't unlock it with Unlock_code.bin file.
What is the solution?
you need to get a new Unlock_code.bin file from htcdev.com, Something has changed older code won't work.
Hello all,
I'm having a problem with putting a new ROM on my device. Goiung back to backup ROm has failed to as it seems the Backup wasn't complete
I thought it had something to do with S-Off, but someone from another thread said I should make a new topic as this would probably be another problem.
I wanted to go to the SuperSense DX5 ROM, but then i need to upgrade my hboot version and boot.img.
At this moment my hboot version is 1.24.0000. Also the the device is still in S-On.
When I try to load boot.img i get the following message
flash boot boot.img
sending 'boot' (4452 KB)...
OKAY [ 0.811s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 0.811s
Click to expand...
Click to collapse
Fot the hboot i get following message:
flash hboot bravo_alphaspl-sense.img
sending 'hboot' (512 KB)...
OKAY [ 0.234s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.234s
Click to expand...
Click to collapse
When i looked these errors up I Always ended up about S-Off or get stock recovery.img. Already got the stockrecovery.img on device but still nothing works.
Is there anyone that could help me solve this problem please? I'm completly not sure why now I'm not able to put ROM's on it anymore.
With Kind Regards,
Günther
1. You're trying to flash hboot meant for Desire not Desire X
2. Your hboot is 1.24, you cannot flash boot.img or ROM meant for hboot 1.25
3. You should flash only ICS boot.img, ICS recovery and ICS ROM
So find any ICS ROM in dev section and follow instructions there on how to flash the ROM.
Or go to general section and look for how to restore to ICS stock and update your device to JellyBean.
Then you can install all those JB ROM that you wanted to.
Remember this ? It's the same problem and the same way that you need to do to solve your problem.
doninckg said:
Got it fixed, after some Stock rom install and then tried another ROM Shadow, and it seems to be working once again.
Sorry for my question. I might have done something wrong about the hboot version I think.
Click to expand...
Click to collapse
Good thing you still have S-On or else you would have a paperweight right now
Ohhh OK,
I just followed the guide on the SuperSense DX5 where they refered to hboot 1.25.
But I still don't get why i'm not able to flash a boot.img. Tried the ICS ROM I Always used before "Sense Revolution+ R2
But I'm not able to get this working anymore
But I actually wanted to upgrade because I had some difficulties with this ROM about my Mobile Data. Had high hopes that it could be fixed with a JB ROM for Desire X. The only boot.img and hboot i tried to install was meant for the Desire-X. I'm also using Hassoon 3.0 for Desire-X to have the right recovery flashed for ICS of JB.
Still I must be doing something wrong I guess now, but don't know what then.
So S-On is alright for this device then? I don't need to change annything for this device to try and put it in s-off?
Sorry if I lack a bit of knowledge to root. Thought I did everything that was needed, like I used to do before.
doninckg said:
But I actually wanted to upgrade......
Click to expand...
Click to collapse
1. If you have a backup of your ROM, restore that then update to JB with OTA.
2. Or use the RUU RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed.exe to restore your device then do OTA update.
Download : http://www.androidruu.com/?developer=Proto
3. Or for more advance user, follow this guide - http://forum.xda-developers.com/showthread.php?t=2212067 but not sure whether all links still active for the needed files.
Option 2 is the best for you.
How-to:
1- in fastboot mode - relock the bootloader : run command fastboot oem lock
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish
thanks ckpv5, I will try to do this now.
ckpv5, this fixed everything!!! Thanks a million times for helping me out this fast.
i have been trying to flash a new firmware to my htc one m8 but i get this error
C:\Users\kenny\Desktop\fastboot_adb>fastboot flash zip firmware.zip
sending 'zip' (30216 KB)...
OKAY [ 1.780s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.280s
i am s-off it the phone is relocked and the firmware is the 3.28.401.9 -firmware for the android L 5.0 rom
can some one tell me what im doing wrong ?
Wubzie said:
i have been trying to flash a new firmware to my htc one m8 but i get this error
C:\Users\kenny\Desktop\fastboot_adb>fastboot flash zip firmware.zip
sending 'zip' (30216 KB)...
OKAY [ 1.780s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.280s
i am s-off it the phone is relocked and the firmware is the 3.28.401.9 -firmware for the android L 5.0 rom
can some one tell me what im doing wrong ?
Click to expand...
Click to collapse
Which version on m8 do you have? It says model id check failed which means it's looking for a different cid
Sent from my HTC One_M8 using Tapatalk
Cannot flash anything with bootloader "relocked" and also whatever firmware your trying to flash,your MID model id is wrong for firmware your trying to flash. Figure out what model id is in the firmware and make sure yours is listed.
Wubzie said:
i have been trying to flash a new firmware to my htc one m8 but i get this error
C:\Users\kenny\Desktop\fastboot_adb>fastboot flash zip firmware.zip
sending 'zip' (30216 KB)...
OKAY [ 1.780s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.280s
i am s-off it the phone is relocked and the firmware is the 3.28.401.9 -firmware for the android L 5.0 rom
can some one tell me what im doing wrong ?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Cannot flash anything with bootloader "relocked" and also whatever firmware your trying to flash,your MID model id is wrong for firmware your trying to flash. Figure out what model id is in the firmware and make sure yours is listed.
Click to expand...
Click to collapse
ok ill unlock it , also i know the cid is CW__001. i know there is a thread of firmwares for the 5.0 android L rom that are compatible dose some one have the link?
if not its cool ill just troll around till i fined it
Are you not supposed to do fastboot oem rebootRUU and then do that?
Just wondering myself.
Sammy Eli said:
Are you not supposed to do fastboot oem rebootRUU and then do that?
Just wondering myself.
Click to expand...
Click to collapse
yes you are, but my prob i guess is that my cid is not matching up to my firmware. and the only one that i can fined that works with Android L 5.0 is the 3.28.401.9 and thats the one i have but it dose not work for me and im on cid : CW__001
i have been thinking about changing to super cid but idk if that would work.
Wubzie said:
ok ill unlock it , also i know the cid is CW__001. i know there is a thread of firmwares for the 5.0 android L rom that are compatible dose some one have the link?
Click to expand...
Click to collapse
Any 3.x firmware should work.
For AT&T's network, you will likely have the best results with 3.28.1540, which is found on Wonders_Never_Cease's ROM thread: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Since its the Dev Edition firmware (meant for use on AT&T) you won't even need to change CID/MID.
But be aware for any "international" based ROM (even on the proper firmware), there is a chance for some issues on AT&T's network (most commonly, broken Google services on LTE).
I'm having the same problem with my friends AT&T HTC One m8. I'm with verizon and had no issues whatsoever. However, he wanted to try SkyDragon's new Lollipop ROM, so he found the appropriate firmware, flashed it, flashed the 5.0 ROM, and everything was good. However, after finding several things about said ROM that he didn't like, he now wants to go back to a 4.4.4 Sense based ROM, but can't. We've tried flashing different firmwares, and kept getting error code 41. Then, after reading through this thread, I downloaded the 3.28.1504...(or something like that) firmware and attempted to flash. This time I got the error code 42. customer id check fail. What the heck is going on? He's tried flashing ViperOne 3.2.1, and after selecting all his preferences in Aroma, it fails, and will not flash. The only ROM other that 5.0 he's been able to flash is CM11. He's wanting to go back to Sense, but it's looking to be impossible. Has anyone had similar issues and found a way through this? Please Help!!!
blkhrt13 said:
I'm having the same problem with my friends AT&T HTC One m8. I'm with verizon and had no issues whatsoever. However, he wanted to try SkyDragon's new Lollipop ROM, so he found the appropriate firmware, flashed it, flashed the 5.0 ROM, and everything was good. However, after finding several things about said ROM that he didn't like, he now wants to go back to a 4.4.4 Sense based ROM, but can't. We've tried flashing different firmwares, and kept getting error code 41. Then, after reading through this thread, I downloaded the 3.28.1504...(or something like that) firmware and attempted to flash. This time I got the error code 42. customer id check fail. What the heck is going on? He's tried flashing ViperOne 3.2.1, and after selecting all his preferences in Aroma, it fails, and will not flash. The only ROM other that 5.0 he's been able to flash is CM11. He's wanting to go back to Sense, but it's looking to be impossible. Has anyone had similar issues and found a way through this? Please Help!!!
Click to expand...
Click to collapse
What does "appropriate firmware" mean exactly? It would be 3..28.401 firmware if you are going by the Skydragon thread. But you really need to be specific if you want us to help properly.
If the phone's CID was changed to flash the 3.28.401, then you need to change it back to AT&T's CID to flash 3.28.1540 firmware.
Failure to flash Viper is probably not related. Fastboot erase cache, and re-install TWRP by fastboot (update, if the present version is old) will clear up fail to flash issues a great majority of the time. Also, you can try another Sense software 3.x custom ROM.
redpoint73 said:
What does "appropriate firmware" mean exactly? It would be 3..28.401 firmware if you are going by the Skydragon thread. But you really need to be specific if you want us to help properly.
If the phone's CID was changed to flash the 3.28.401, then you need to change it back to AT&T's CID to flash 3.28.1540 firmware.
Failure to flash Viper is probably not related. Fastboot erase cache, and re-install TWRP by fastboot (update, if the present version is old) will clear up fail to flash issues a great majority of the time. Also, you can try another Sense software 3.x custom ROM.
Click to expand...
Click to collapse
He was actually able to fix it. He found firmware that cleared all his issues up...at least I think that's what he did. Anyway he can flash pretty much anything he wants now. Lol. But thank you for your reply.