[Q] radio stopping - HTC Rezound

I have read several posts/threads and don't see the problem I am having addressed. My rezound radio drops out all too often and I am not sure if there is a software or kernel that will correct my problem. I am rooted, S-on, have flashed two of Scotts Roms and am now on ViperRez 1.0.3. Kernel version is 3.0.16-gd0049f1. When I loose 3g/4g sometimes I can turn off and on the mobile network and it will come on but most of the time I have to do a batter pull. Sure would like to know if there are any answers out there or if its the hardware.
Thanks!

What's your baseband version? It sounds like you didn't do a clean enough wipe. Also being on the updated firmware will help your signal from dropping out..
Sent from my ADR6425LVW using xda app-developers app

famouscollin said:
What's your baseband version? It sounds like you didn't do a clean enough wipe. Also being on the updated firmware will help your signal from dropping out..
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Baseband is 0.95.00.1118r, 0.95.00.1223r.
The rom instructions were pretty straight forward and I did a data wipe and factory reset prior to flashing. Should there be more?
thanks.

dmar1224 said:
Baseband is 0.95.00.1118r, 0.95.00.1223r.
The rom instructions were pretty straight forward and I did a data wipe and factory reset prior to flashing. Should there be more?
thanks.
Click to expand...
Click to collapse
Well your still on gb radios you could run the latest ruu to get up to date.. and as a personally rule when flashing a new Rom I always:
Factory wipe x2
Wipe data x2
Wipe cache x2
Wipe dalvik cache x2
Wipe system
Then I flash the Rom.. I do extra wipes to always ensure a clean instal.
Sent from my ADR6425LVW using xda app-developers app

famouscollin said:
Well your still on gb radios you could run the latest ruu to get up to date.. and as a personally rule when flashing a new Rom I always:
Factory wipe x2
Wipe data x2
Wipe cache x2
Wipe dalvik cache x2
Wipe system
Then I flash the Rom.. I do extra wipes to always ensure a clean instal.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Great information!
Do you have a radio suggestion for this phone and rom? I would love to re-wipe and re-install everything today to see if it's time to put this in the junk pile and head to Verizon.
Appreciate your help.

Here's the latest ruu http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ if your s-on relock your bootloader with command "fastboot oem lock" the rename the zip file to PH98IMG put it on your sd, boot your phone to bootloader and let it run tje update.. you'll then have to unlock and flash amonRa again..
Sent from my ADR6425LVW using xda app-developers app

Try re-seating your SIM card. Mine was acting the same way. I removed the SIM, then put it back in. The problem immediately disappeared. I can't guarantee this will work for you but it's worth a try.
Sent from my HTC Rezound, rooted with S-OFF on Verizon's periodically blazing fast and mostly reliable 4G LTE Network

Related

1% battery steps for 2.3.5 firmware (the one dumped from Electrify)

Edit: Link is broken and I don't have this on my hard drive anymore. Anyone who have this, please share with others.
Cwm installable zip.
This was made by Olegfusion and me.
Thanks.worked great
Sent from my Motorola Electrify using Tapatalk
Bootstrap?
Sent from my MB855 using xda premium
jguevara4854 said:
Bootstrap?
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Sure
Sent from my Motorola Photon using xda premium
tried bootstrap on a 2.3.5 and i got 70% in the battery icon but never went in ones
Hmm, that's interesting. I am unlocked, with jokers kernel, but if it makes any difference in 1% steps? Try to wipe cache and dalvik cache.
Anyone get this to work with bootstrap?
Sent from my Motorola Electrify using Tapatalk
Worked for me. 2.3.5 locked with bootstrap
Sent from my Motorola Electrify using Tapatalk
dosnt work on my mopho
Cleared cache and dalvik cache and flashed in bootstrap, works on my locked 2.3.5! This was the only thing missing from rocko!
Sent from my Motorola Electrify using Tapatalk
Running Jokers special-club-0.0.1-cm-9.0.0-RC0-Sunfire-KANG-signed + JokerGappsV9 + Droid Razr BootAnimation + a few other little tweaks and flashing from CWM based 5.0.2.7 caused me to get stuck in boot screen before and after wiping Cache + wipe Cache Partition nd Fix Perm. Going to wipe and flash since I have to wipe anyway and see what happens. Bummer
[edit] wipe battery stats, no-go
[edit] wipe data was a no-go as well, had to format system, wipe and reflash
FanBoy_Hunter said:
Running Jokers special-club-0.0.1-cm-9.0.0-RC0-Sunfire-KANG-signed + JokerGappsV9 + Droid Razr BootAnimation + a few other little tweaks and flashing from CWM based 5.0.2.7 caused me to get stuck in boot screen before and after wiping Cache + wipe Cache Partition nd Fix Perm. Going to wipe and flash since I have to wipe anyway and see what happens. Bummer
[edit] wipe battery stats, no-go
[edit] wipe data was a no-go as well, had to format system, wipe and reflash
Click to expand...
Click to collapse
you're funny. it'll not work in cm9 OF COURSE!
olegfusion said:
you're funny. it'll not work in cm9 OF COURSE!
Click to expand...
Click to collapse
Worth a test, people on the cm9 forum were asking about it so I gave it a shot, that was a long time ago.
Sent from my MB855 using xda premium
FanBoy_Hunter said:
Worth a test, people on the cm9 forum were asking about it so I gave it a shot, that was a long time ago.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Ok, Ill look on it later
update
http://forum.xda-developers.com/showthread.php?p=22747523#post22747523
1% for cm9
Sent from my MB855 using xda premium
How did you get the 1%. I flashed the zip in bootstrap and formatted cache and dalvik. I am only gettting 10% still? Any Ideas? I had no percentage before and now I get percentages but in 10%. Thanks
anyone have this? link is dead
Link updated
Thank you very much! Works perfect.
peetr_ said:
Link updated
Click to expand...
Click to collapse
Is this works with 2.3.4 locked.
Sent from my MB855
Worked like a champ on...
ROCKO 3.5 unlocked 2.3.5 ROM
thanks so much..
No how do you get rid of that US Cellular Banner?????

Running seraphim and keep getting wifi errors

Hello,
First and foremost, I'm loving this rom. I'm a noob and getting my hands dirty figuring all this out.
Now with that said:
When I try to connect to my wifi network it keeps saying authentication error occurred. I have tried everything and the only thing that fixes it is restoring my backup to my stock rom.
Please help!!!!
Sent from my SAMSUNG-SGH-I717 using xda premium
Smerleau said:
Hello,
First and foremost, I'm loving this rom. I'm a noob and getting my hands dirty figuring all this out.
Now with that said:
When I try to connect to my wifi network it keeps saying authentication error occurred. I have tried everything and the only thing that fixes it is restoring my backup to my stock rom.
Please help!!!!
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I will say 90% of the people in here will say it is not the rom. just because theres seems to work. and i tend to agree. what have you tried to fix it? besides going back (to Stock). i have not had any issues with WiFi on Serephim yet, so i can not say what a fix would be. maybe wipe your cache's. when i had that issue on GB i had to reinstall the kernel and boom it worked. but seeing as though we do not have one yet for ICS. i would say wipe and worst case reinstall the from after a very Thurough Wiping Process.
the2rrell said:
I will say 90% of the people in here will say it is not the rom. just because theres seems to work. and i tend to agree. what have you tried to fix it? besides going back (to Stock). i have not had any issues with WiFi on Serephim yet, so i can not say what a fix would be. maybe wipe your cache's. when i had that issue on GB i had to reinstall the kernel and boom it worked. but seeing as though we do not have one yet for ICS. i would say wipe and worst case reinstall the from after a very Thurough Wiping Process.
Click to expand...
Click to collapse
I have wiped cache a few times and I just downloaded another rom and got the same issue.. The only time it works is on stock GB
Sent from my SAMSUNG-SGH-I717 using xda premium
Smerleau said:
I have wiped cache a few times and I just downloaded another rom and got the same issue.. The only time it works is on stock GB
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Then if your into flashing right now, just try either the superwipe.
Or this is how i wipe.
I factory default/format usb from inside the rom.
I wipe factory/data from cwm
i wipe cache partition from cwm
i wipe delvik from cwm
then i flash "Rom" and reboot.
this leaves nothing from previous roms and or Gingerbreak roms.
try that and see if it works. if not then i am out of ideas until a kernel source is released.
Ok i will try that and see if it works...
Thank you!!!
Sent from my SAMSUNG-SGH-I717 using xda premium
the2rrell said:
Then if your into flashing right now, just try either the superwipe.
Or this is how i wipe.
I factory default/format usb from inside the rom.
I wipe factory/data from cwm
i wipe cache partition from cwm
i wipe delvik from cwm
then i flash "Rom" and reboot.
this leaves nothing from previous roms and or Gingerbreak roms.
try that and see if it works. if not then i am out of ideas until a kernel source is released.
Click to expand...
Click to collapse
I fixed it.... USER ERROR.. I Don't want to admit this but I was entering the wrong password and my old Rom had the password saved so I never had to enter it...
Sent from my SAMSUNG-SGH-I717 using xda premium

Which super wipe do you guys prefer?

So, there is nothing magical about super wipe scripts, but this one seems to have had some serious thought put into it.
http://forum.xda-developers.com/showthread.php?t=834812
I usually wipe manually but was curious what you guys do...
Sent from my EVO using xda app-developers app
adma84 said:
So, there is nothing magical about super wipe scripts, but this one seems to have had some serious thought put into it.
http://forum.xda-developers.com/showthread.php?t=834812
I usually wipe manually but was curious what you guys do...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
There is only one superwipe for our phone. There is nothing to compare it to, and no need as it works fine. The link you posted has nothing to do with our device.
http://forum.xda-developers.com/showthread.php?p=27166189
Ta da!
I've never understood super wipes. I just do it manually.
No need for a superwipe. Just Factory Reset and wipe System and you're ready to flash. That's never once given me a problem.
I use superwipe mod all the time after a manual wipe. Reason because TWRP does not have option to wipe/format the BOOT partition.
Sent from my EVO using xda premium
theoner1 said:
I use superwipe mod all the time after a manual wipe. Reason because TWRP does not have option to wipe/format the BOOT partition.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
You shouldn't have to wipe boot.
SoraX64 said:
You shouldn't have to wipe boot.
Click to expand...
Click to collapse
Exactly I never even heard of a Superwipe until the 3d came out. Never had to flash one since I had my g1 and i'm not going g to start now
Sent from my EVO using xda premium
SoraX64 said:
You shouldn't have to wipe boot.
Click to expand...
Click to collapse
Install any aosp rom, example deck cm10 8-31-12. The Rom have force close issue with the phone process at the beginning. Now if you want to go back to latest sense Rom, without wiping boot img, you will continue to have the same phone process force close issue even if you're on sense Rom. It just happen to me a couple nights ago. So wiping boot partition is my way of completely getting rid of previous issue on the last install Rom.
Sent from my EVO using xda premium
theoner1 said:
Install any aosp rom, example deck cm10 8-31-12. The Rom have force close issue with the phone process at the beginning. Now if you want to go back to latest sense Rom, without wiping boot img, you will continue to have the same phone process force close issue even if you're on sense Rom. It just happen to me a couple nights ago. So wiping boot partition is my way of completely getting rid of previous issue on the last install Rom.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I can flash between CM and Sense all I want without the error persisting, maybe you're doing something else wrong?
SoraX64 said:
I can flash between CM and Sense all I want without the error persisting, maybe you're doing something else wrong?
Click to expand...
Click to collapse
I was doing something wrong at the time, I forgot to flash the superwipe. When I first booted into meanrom 3.6 the same phone process force close still there. After realizing I forgot to flash superwipe, went back to recovery, wipe completely manually follow by superwipe then install meanrom 3.6, which booted fine without phone process error. Every time I flash a New Rom I always wipe everything at least twice.
Sent from my EVO using xda premium
theoner1 said:
I was doing something wrong at the time, I forgot to flash the superwipe. When I first booted into meanrom 3.6 the same phone process force close still there. After realizing I forgot to flash superwipe, went back to recovery, wipe completely manually follow by superwipe then install meanrom 3.6, which booted fine without phone process error. Every time I flash a New Rom I always wipe everything at least twice.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Are you by any chance 1.15 S-ON?
Because not a week ago I left CM10 for Viper 4G because I needed the camera to work stably, and I did not receive the force close once.
SoraX64 said:
Are you by any chance 1.15 S-ON?
Because not a week ago I left CM10 for Viper 4G because I needed the camera to work stably, and I did not receive the force close once.
Click to expand...
Click to collapse
Nope orginal hboot 1.12 and s-off
Sent from my EVO using xda premium
theoner1 said:
Nope orginal hboot 1.12 and s-off
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hmm, interesting because I have gone back and forth between CM10 and MeanRom. I have never had an issue. I love the speed and fluidity of CM10 but the Sense camera is just to good at this point.
I have then same issue...if I don't use sw I have issues bouncing between sense and cmx nands.. can't make calls on sense without it..with it I have no issues
firmbiz94 said:
I have then same issue...if I don't use sw I have issues bouncing between sense and cmx nands.. can't make calls on sense without it..with it I have no issues
Click to expand...
Click to collapse
See what I mean, I'm not the only with this issue. Superwipe work wonders for me too.
Sent from my EVO using xda premium
I think a lot of people got used to using these from the og evo. CWM was thought to have trouble wiping so most would wipe two or three times to make sure it didn't miss anything. I haven't heard of that being an issue for a long, long time though.
One thing that it may help with though is if the ROM doesn't format the system partition. I've spent hours trying to track down bugs only to realize leftover system files were wreaking havoc with the new ROM.
theoner1 said:
See what I mean, I'm not the only with this issue. Superwipe work wonders for me too.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hmm that's interesting, i remember i flashed tranquility rom and was working great! then tested cmx and at the same time tranquility was updated and that error was still present on the new tranquility rom, but i thought it was the rom so i flashed another sense rom but, this time i used superwipe after manually wiping all and no error anymore, since then i didnt use tranquility thinking it was the new update. now i always use superwipe.
time to go back to tranquility :fingers-crossed::fingers-crossed:

Tips for someone new to flashing ROMs?

Im currently running Viper4g on my evolte but ive been checking out CM10 and i want to try it out. What would be the usual steps to take when flashing a new rom?
I would do a full NAND backup with whatever recovery you have in case you want to revert back. Then do a full wipe (system, data, cache, dalvik) and flash the new ROM.
Read the guide in my sig lol, explains just about anything you could think of and has a list of basic trouble shooting scenarios that some users are likely to encounter
Come on guys you tell me what a great write up I have and never recommend it?
Edit: I feel like I'm trying to sell myself and I am not a wh***
*runs away in tears*
Of course it's great
However, you said yourself: it's a great reference guide, but not a step-by-step for anything.
The OP asked for steps to take when changing ROMs
Yes but the title of his thread says tips for someone new....ahaaaa.. *cue classic black and white cinema fiend music*
I so wrote it to avoid all these brick and corrupt card threads
Touche...
*bows in defeat*
Make sure you check out om4's AWESOME guide, "DON'T PANIC", here: http://forum.xda-developers.com/showthread.php?t=1869377
*runs off to bed*
bilbo524 said:
Touche...
*bows in defeat*
Make sure you check out om4's AWESOME guide, "DON'T PANIC", here: http://forum.xda-developers.com/showthread.php?t=1869377
*runs off to bed*
Click to expand...
Click to collapse
Suck up
Sent from the depths of hell
Quiet let me have my moment lol
Absolutely not lol
Sent from the depths of hell
Dude, check out the last 2 scenarios, went to the head and the gf added them. I laughed so hard
Well it looks like i did something wrong cause my phone is stuck in a constant boot loop. I followed the instructions on http://forum.xda-developers.com/showthread.php?t=1794867
for
How to flash a boot image if S-ON Dev Unlocked 1.15 HBOOT:
I was trying to install CM10 btw. I did a backup using twrp tried restoring but that didnt work. What can i do now to fix it?
Maybe the cmx was a bad download or bad flash. If you fasboot flashed the aosp boot IMG you might have problems trying to restore a sense backup. I would download cmx again redo all the steps.
I'm not sure if you have to flash a sense boot IMG when restoring a backup , I would try it tho to be safe.
Hey man. The instructions work, so start over and make sure you follow every step including wiping.
Sent from my EVO using xda app-developers app
Did you do a full factory reset and wipe system, data, cache, and dalvik before flashing the ROM?
Sent from my LTEvo powered by CM10 using XDA Premium
bilbo524 said:
Did you do a full factory reset and wipe system, data, cache, and dalvik before flashing the ROM?
Sent from my LTEvo powered by CM10 using XDA Premium
Click to expand...
Click to collapse
No i didnt. Right now i just want to get my phone working again since i have work in an hour. What should i do to get it working again?
Start the process over just make sure you wipe fully before flashing anything. Cache, dalvik, factory reset and system.
Sent from my EVO using xda app-developers app
To restore your existing backup, you will need to reflash your old viper4g kernel (boot.IMG) first with fastboot.
Sent from my LTEvo powered by CM10 using XDA Premium
bilbo524 said:
To restore your existing backup, you will need to reflash your old viper4g kernel (boot.IMG) first with fastboot.
Sent from my LTEvo powered by CM10 using XDA Premium
Click to expand...
Click to collapse
So just follow the steps from the link i posted using the boot.img from the viper4g download?
Yes, follow the same steps you used to flash the CM10 kernel to reflash the viper4g kernel. Your exisiting viper4g backup should then boot OK.
Sent from my LTEVO powered by CM10 using XDA Premium
bilbo524 said:
Yes, follow the same steps you used to flash the CM10 kernel to reflash the viper4g kernel. Your exisiting viper4g backup should then boot OK.
Sent from my LTEVO powered by CM10 using XDA Premium
Click to expand...
Click to collapse
ok im trying to restore again, hopefully it works. i have work in 45 minutes and being without my phone would suck.
It worked! Thanks for the help guys. Im gonna leave CM10 alone until the weekend when im off.

[Q] Thunderbolt failing to boot after custom ROM

I recently attempted to root my HTC thunderbolt, and to do so I used the htc dev unlocker and then this "HTC Thunderbolt Tool'
rootzwiki.com/topic/27310-all-in-one-the-htc-thunderbolt-tool
After that I downloaded a rom and installed it through the 4ext recovery, it all install fine and I did do a factory/data reset but whenever I reboot after the rom install, I get the HTC white bootloader and then the screen become black with a back light to it.
I have tried a number of times to re-install the rom and have tried to use other roms but all of them seem to end the same way.
I have used:
BAMF FOREVER 1.1
BAMF MECHA ICS
AIRBORNE GOUI
Killsense 3.7.19
Lightning501
few more
My phone is a HTC Thunderbolt and when I attempted to root the phone it had a hboot version of 1.0.8 and had a stock version of ICS installed.
Sadly I have a phone without a working rom and I had forgot to make a backup so if anyone can help it would be greatly appreciated. Preferably I would like to keep the phone rooted but its not necessary.
Thank You
I'm a total xda-developor noob, so I hope I didn't mis a thread with a the solution all ready on it.
Make sure you do the factory reset, wipe dalvik and cache. Flash the ROM and reboot. Sounds like your missing a step somewhere 8)
Sent from my ADR6400L using xda app-developers app
tburns said:
Make sure you do the factory reset, wipe dalvik and cache. Flash the ROM and reboot. Sounds like your missing a step somewhere 8)
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
I have tried clearing everything but still doesn't seem to work.
One thing I forgot to mention is sometimes if I wait long enough on the blank screen It boots me back into the 4ext recovery, don't know if that makes much of a difference.
The way I have been installing the rom
Load ROM onto the SD
Do a "wipe data/factory reset"
Go into install sd and choose the Rom which is in a .zip file
I think this is how its supposed to be done, but not sure.
aplysenko said:
I have tried clearing everything but still doesn't seem to work.
One thing I forgot to mention is sometimes if I wait long enough on the blank screen It boots me back into the 4ext recovery, don't know if that makes much of a difference.
The way I have been installing the rom
Load ROM onto the SD
Do a "wipe data/factory reset"
Go into install sd and choose the Rom which is in a .zip file
I think this is how its supposed to be done, but not sure.
Click to expand...
Click to collapse
You need to wipe cache and dalvik cache too.
Sent from my Nexus 7 using Tapatalk 2
disconnecktie said:
You need to wipe cache and dalvik cache too.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I have done that.
Problem is you were coming from the ICS OTA.
The All In One Tool alone will not get you rooted after taking the OTA.
In order to fully root and s-off after having the OTA loaded, you would need to follow the steps outlined HERE
santod040 said:
Problem is you were coming from the ICS OTA.
The All In One Tool alone will not get you rooted after taking the OTA.
In order to fully root and s-off after having the OTA loaded, you would need to follow the steps outlined HERE.
Click to expand...
Click to collapse
Your link dont work for me, id assume you were pointing to this wonderful thread
Milimbar said:
Your link dont work for me, id assume you were pointing to this wonderful thread
Click to expand...
Click to collapse
Correct Thanks I fixed the link in my first post.
I am using the thread and so far its working, just one last question. Do I have to install and use 4ext, or can I just use clockwork mod?
aplysenko said:
I am using the thread and so far its working, just one last question. Do I have to install and use 4ext, or can I just use clockwork mod?
Click to expand...
Click to collapse
You can use whatever Recovery you want, Clockwork Mod is old and not really suggested to use, especially with newer roms.
I miss the RA recovery I had on my first bolt. I use the ext4 recovery now. Glad Santod was able to help you out!!
Sent from my ADR6400L using xda app-developers app

Categories

Resources