Related
So I flashed one of those no sound AOSP roms, I instantly nandroided back to my Synergy #318. When I did it told me "System not responding" "Force Close" I figured bad nandroid. Super wipe and reflashed 318, I went through set up and then I get no 3G no Phone, here is a screeny of my about phone.
Do I reflash the radio???
EDIT...re-flashed radio and still get the same sh#t
I have a backup of my WiMax in clockwork form, flashed over to clockwork recovery, creating a backup to replace current WiMax with the one I have saved (Original).
EDIT...That broke the MD5 and would not allow a restore of WiMax
Trying a RUU now
Looks like the RUU made me a shiny new BRICK!!!
Bootloader is stuck here, its been like this for over 8 minutes.
WTF is really going on here
I followed this return to stock thread HERE
Well after 15 minutes I said F it and pulled the battery. Apparently it didnt do anything as far as the RUU goes because it booted back into my ROM. It stills says "Process System is not responding" Force Close or Wait.
I flashed synergy once and I had the Samething your showing... Everyother ROM I flashed all the info would show up. Sometimes on synergy it was just blank. So are you able to flash any roms?
Sent from my PG86100 using xda premium
neopolotin75 said:
I flashed synergy once and I had the Samething your showing... Everyother ROM I flashed all the info would show up. Sometimes on synergy it was just blank. So are you able to flash any roms?
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Yes, it happens with all roms though. It never gives me signal, phone signal or 3G/1X signal. It says looking for service, but service never comes.
I installed aosp again, it offers better info in about phone. this is what I see, not looking good for the home team
In the aosp rom I flashed I found a update-binary, I will upload below. This is what F'ed me up! Can someone tell me how to open this, so I can correct what is wrong and re-flash? I ran aosp through rom kitchen and mustve hit convert to update-binary. Now I am F'ed!
I know you can't connect to data but Can you connect to wifi? Are you on 2.3.3 or 2.3.4? Hausx (sure I didn't spell it right) posted in CDMA the individual components..... Try flashing each one and see if that helps and maybe try going to 2.3.4 if not there. I'd stay away from hboot 1.5 or you will have to do htcs method to unlock which I'm thinking should definitely work.
Sent from my PG86100 using xda premium
neopolotin75 said:
I know you can't connect to data but Can you connect to wifi? Are you on 2.3.3 or 2.3.4? Hausx (sure I didn't spell it right) posted in CDMA the individual components..... Try flashing each one and see if that helps and maybe try going to 2.3.4 if not there. I'd stay away from hboot 1.5 or you will have to do htcs method to unlock which I'm thinking should definitely work.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I can connect to WiFi, I also tried the radio already. I also tried 2.3.4 and 2.3.3 this sucks ares!
EDIT...I found the thread, gonna try flashing them now! What about the factory reset within the rom, using dialer ##778# I think? Would that maybe help, get the hands free activation going maybe? Thing is if you look at that picture it is not even reading PRL
New radio/PRI did not help, what could keep phone from reading this info off of it? I just did a reset from within rom, that didnt help either.
OPST does not read my phone anymore either
OK, I tried RUU again and it went through! I had 2 things labeled TP and it bypassed the first one, and updated the second. I am rebooting now so we will see if I get signal back. If not at least I am at stock for warranty!
And NO GO! Same Process System is Not Responding! If I wait the phone reboots. What the hell can be happening here?
Now I did a factory reset and the phone boots, then re-boots during the set up process.
Sort of sounding like you may need to give Sprint a call and see if they can have you manually re program it over the phone or something. I'm not sure how you'd go about un-doing whatever it is that you updated that caused this. It sounds like something you'd need to mess with using EPST ## codes.
Did you just try the radio and PRI and not the full RUU? if the forced factory data reset through ## doesn't work and the radio didn't..... I'm wondering if trying to root it via htc website wouldn't fix it. Very wierd situation you have here
Sent from my PG86100 using xda premium
Tell me about it! I got a replacement coming. I tried all I could, somewhere I F'ed something up with the partitions is my guess. Something in the Update-Binary changed a location of partition, or the size. For now I got my back up Optimus S online, really missing my 3D already! lol
anyone have any DEV stuff they need a tester on that may brick, hit me up.
Alright i need help badly. I consider myself an advanced noob in installing roms and kernals on a phone. I have the rezound. I unlocked it about a week about and went through the step by step instructions. I installed ziggys kernal. I was getting some bootloops but not to many until this morning. My phone kept bootlooping. I would take the battery out and put it back and it would do it again. I tried wiping the date cache and dalvik. Nothing. I then formatted all to ext3. After i did that it said i need to install a rom. I try to restart my phone and it just stays on the HTC screen. I tried to do the factory restore. Nothing. I have to put my sd card in after i get into recovery because when i go to the bootloader screen the HBOOT does something and then asks me if i want to do an update. I tried and hit yes and it did it then reboots but nothing. When i hit no it just wants me to reboot my phone, which does nothing for me. As it is right now my phone wont load. it just stays on the HTC screen. HELP please
http://forum.xda-developers.com/showthread.php?t=1394659
Try this, but you should really search first.
I would try that but my phone will not boot. it will not go past the HTC start up screen
Evo4gLI said:
http://forum.xda-developers.com/showthread.php?t=1394659
Try this, but you should really search first.
Click to expand...
Click to collapse
The other half of the problem is that it sounds like he formatted ext3 and wiped his ROM. So, he'd have to reboot back into recovery and restore a backup or drop a new ROM on the phone via USB.
Grab the RUU and start all fresh again.
MrSmith317 said:
The other half of the problem is that it sounds like he formatted ext3 and wiped his ROM. So, he'd have to reboot back into recovery and restore a backup or drop a new ROM on the phone via USB.
Grab the RUU and start all fresh again.
Click to expand...
Click to collapse
Good point. I'm in class, so I just read it quickly. RUU sounds like the way to go.....start with a clean slate.
how do i get to the RUU
See "shipped Rom collection" sticky in dev section
Sent from my ADR6425LVW using XDA App
Good Luck
This is one of the reasons I have not tried to hack this device. Although I may unlock/root my Rezound I'm not in a hurry to. It's really a great device. Just too expensive for me to maybe mess up. Especially since its our own fault if we do. Can't blame the carrier/manufacturer for not paying to fix/replace either. Hopefully you get it fixed soon. I know I wouldn't want to have to go through all that either.
i just installed the CleanRom. Ill let you know if this works
installed cleanrom but now my wifi says error and wont connect
Abead84 said:
installed cleanrom but now my wifi says error and wont connect
Click to expand...
Click to collapse
You need to reflash the kernel in order to get wifi to work.
Abead84 said:
installed cleanrom but now my wifi says error and wont connect
Click to expand...
Click to collapse
The answer should be in the CleanRom thread but as far as I know if you flashed Ziggy's Kernel, you should reflash it and that should solve the problem.
Oops, just noticed this was already answered.
i flashed a kernel and its all good now
Abead84 said:
i flashed a kernel and its all good now
Click to expand...
Click to collapse
Glad you got it all back. That would scare the sh*t out of me
WasabiWa83 said:
Glad you got it all back. That would scare the sh*t out of me
Click to expand...
Click to collapse
It shouldn't. You can't brick with unlock S-On. If you can get to HBOOT, you are fine. And there is no way to overwrite HBOOT yet.
con247 said:
It shouldn't. You can't brick with unlock S-On. If you can get to HBOOT, you are fine. And there is no way to overwrite HBOOT yet.
Click to expand...
Click to collapse
And does it need to be said that this phone has been out for less than a month? Maybe we should give the devs a chance to work out the kinks before we start flashing.
I *really* miss WiFi tethering that I used to do with my DInc, but I am not about to root in the first two weeks of ownership before I see good, dependable feedback from the community.
I love this phone too much.
Sent from my ADR6425LVW using Tapatalk
con247 said:
It shouldn't. You can't brick with unlock S-On. If you can get to HBOOT, you are fine. And there is no way to overwrite HBOOT yet.
Click to expand...
Click to collapse
That's damn good to know
WasabiWa83 said:
That's damn good to know
Click to expand...
Click to collapse
Actually you might be able to mess up the partitions or something, but HTC limits our ability to **** up the phone pretty well
WookieFan said:
And does it need to be said that this phone has been out for less than a month? Maybe we should give the devs a chance to work out the kinks before we start flashing.
I *really* miss WiFi tethering that I used to do with my DInc, but I am not about to root in the first two weeks of ownership before I see good, dependable feedback from the community.
I love this phone too much.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Not trying to knock you but I don't see the point in waiting. Flashing a rom is fairly straightforward and even flashing kernels is for the most part. I had an Incredible prior to this and I am absolutely in love with my phone...that's why I read how to do things properly and learn from others mistakes.
Take the plunge! It's great on the otherside
WookieFan said:
I *really* miss WiFi tethering that I used to do with my DInc
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
There is a wifi tether app that doesn't require root. Koush is the dev. I tried it and it worked. That was the only thing I would have needed root for also. You should be able to find it if you search for it. If not, I'll find the link.
Edit: I found the link
https://plus.google.com/u/0/103583939320326217147/posts/1Yy1jb9z4TA
Sent from my ADR6425LVW using Tapatalk
Ok, I looked around and cannot find an answer that works for me for this issue. I am wondering if it has to do with my phone having S-Off? I am most likely wrong, but i have to know whats going on. No matter what I try, I cannot get My Rezound to go from GB to ICS, ANY ICS BASED ROM for that matter. I checked MD5, Tried with battery door both removed and attached, with or without the SIM card inserted into the phone. The phone boots up almost 100%. I get a message saying "Updating Android" and it says its updating or doing something to 160 apps, the system then reboots, when it gets past the 4G screen again, It says that the boot was completed, I have no signal, i checked on the service type and its correct, tried a factory reset, and still nothing, the system just continues to boot loop over and over again, and when it boots up i cannot get past the Activation screen where it says that the phone is trying to contact Verizon to Auto Activate. I can go back to GB easily, and that works %100. Any and all information would be useful, Only reason why i think this might have to do with S-Off is because my first Rezound was S-On and worked just fine going to ICS, while this new one has S-Off and is just not cutting it.
If you have s-off the rom image could contain a radio update. That could be getting you...also data is off by default in some ICS ROMs.
Sent from my ADR6425LVW using Tapatalk
Sent from my ADR6425LVW using Tapatalk
MrSmith317 said:
If you have s-off the rom image could contain a radio update. That could be getting you...also data is off by default in some ICS ROMs.
Sent from my ADR6425LVW using Tapatalk
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
so what would be recommended in this type of situation? I know its not the data being off thats causing the issue, because when i boot up i dont have a signal at all, and the lock screen instead of showing VZW banner it says No Signal. Would the Radio being an issue also cause boot loop issues?
Did you put the battery cover on the phone ?
Edit saw that u did sorry ...
Sent from my Dinc... I mean Rezound
Only thing i can think of is that the ICS rom you flashed has data off automatically, and requires you to keep pressing the home button until it passes the activation screen.
Also make sure your battery cover is on like yojoe600 said, your antenna is connected to the cover and without it you will have no signal.
who_mike_d said:
Only thing i can think of is that the ICS rom you flashed has data off automatically, and requires you to keep pressing the home button until it passes the activation screen.
Also make sure your battery cover is on like yojoe600 said, your antenna is connected to the cover and without it you will have no signal.
Click to expand...
Click to collapse
this is just sooooooooo irritating. all that i have tried, this is kinda depressing. One interesting thing that i did come across though. When i flashed the BAMF GB, and tried to go from rom to rom to rom, i didnt get any MainVer error.... Dont know if thats just because S-Off allows you to go from one to another freely, or if its just not taking these updates.....
S-off has no mainvar issues. Try putting the gb radio into a PB zip or whatever the resound uses and flash that and boot to see of you get data then
Sent from my ADR6425LVW using XDA App
hey guys, its not just data, the phone is bootlooping on him.
I know several people have s-off devices. You might try looking over on rootzwiki as well. Maybe a dev with s-off can help.
I am one of those people with an s-off and I have had no issues with it but I also updated to the ICS radio AMD have no issues so I'm not totally sure what not working with yours
Sent from my ADR6425LVW using XDA App
werdna87 said:
I am one of those people with an s-off and I have had no issues with it but I also updated to the ICS radio AMD have no issues so I'm not totally sure what not working with yours
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Not sure what is going on with mine that is making it so different. This is just frustrating, last thing that im going to try is going to be flashing th kernel through adb, know that whould not matter too much, but i'll give it a shot, not like it would hurt at all.
dalvear88 said:
Not sure what is going on with mine that is making it so different. This is just frustrating, last thing that im going to try is going to be flashing th kernel through adb, know that whould not matter too much, but i'll give it a shot, not like it would hurt at all.
Click to expand...
Click to collapse
Ok , so i tried this, and as i thought not much happened, more of the same. No real help at Rootz either sadly. I need to find me an S-Off Dev.... lol
On a side note, how would one go about flashing a different recovery.img on an S-Off device, do i have to adb it, or can i do it on the fly? If so, how?
Last thought...did you try the bootloop fix? ##whatever after booting without the battery covery etc...?? There' s a full thread on it.
MrSmith317 said:
Last thought...did you try the bootloop fix? ##whatever after booting without the battery covery etc...?? There' s a full thread on it.
Click to expand...
Click to collapse
yeah was about to give that a go, but the system seems to shut down before i get to the phone portion. I'm having to use the Emergency Call option to get to the dialer since the phone sits on the Self Activation Page.
Before anyone can help you fully and properly, more information needed!
What ROM are you trying to install?
angryPirate12 said:
Before anyone can help you fully and properly, more information needed!
What ROM are you trying to install?
Click to expand...
Click to collapse
what you mean more info, my original post was pretty clear, dont mean to be snappy or anything, i could try to give more info maybe. I've tried all the "fixes" and so far nothing works. ALL AND ANY ICS BASED ROMS are not staying stable on my phone. They get stuck in what i think is the data bootloop, but i cannot access the dial pad other than through the Emergency dial pad, i input the *#*#4636#*#* and nothing comes up, i try without the battery cover, and without the SIM card as well (Also have tried Various combinations of SIM and Battery Cover removals and inclusions). The device has S-Off, and is Unlocked with DevUnlock, and has Perm Root.
Like I stated in my initial post, the leak may contain a radio update that your phone(and the network) isn't ready for. We wouldn't get that update because our radios are locked and only a signed update from HTC would install it. I'd say back down to GB and wait it out...or post in the thread of the ROM maker and ask them about the radio.
dalvear88 said:
what you mean more info, my original post was pretty clear, dont mean to be snappy or anything, i could try to give more info maybe. I've tried all the "fixes" and so far nothing works. ALL AND ANY ICS BASED ROMS are not staying stable on my phone. They get stuck in what i think is the data bootloop, but i cannot access the dial pad other than through the Emergency dial pad, i input the *#*#4636#*#* and nothing comes up, i try without the battery cover, and without the SIM card as well (Also have tried Various combinations of SIM and Battery Cover removals and inclusions). The device has S-Off, and is Unlocked with DevUnlock, and has Perm Root.
Click to expand...
Click to collapse
When I say more info, I mean don't describe every symptom... tell us specifically what you did. Every ICS ROM is unique, like for example I last installed newtoroot's Senseless 4.0.3 ROM. In order to use it, I had to flash a ICS Kernel, I used the fastboot method. Then I could flash the ROM using AmonRa Recovery, and it would boot and operate effectively.
That's the kind of specifics we need, so we can follow your steps and identify possible error points, if any.
angryPirate12 said:
When I say more info, I mean don't describe every symptom... tell us specifically what you did. Every ICS ROM is unique, like for example I last installed newtoroot's Senseless 4.0.3 ROM. In order to use it, I had to flash a ICS Kernel, I used the fastboot method. Then I could flash the ROM using AmonRa Recovery, and it would boot and operate effectively.
That's the kind of specifics we need, so we can follow your steps and identify possible error points, if any.
Click to expand...
Click to collapse
Definetly more descriptive lol thank you for the breakdown infact. In that case, last one i tried what the ICS Sense Redefined, and I tried to use the fastboot method for the Included Kernel as well, but that didnt work at all, what ICS Kernel did you flash to get it to work? a Pre-Packaged one? When installing, I did a full wipe (Both the Amon Ra Factory Reset option and the SuperWipe that is in the Dev Forum) installed the Rom, went into the Bootloader and did ADB CMD of fastboot flash boot boot.img and thats about it.
dalvear88 said:
Definetly more descriptive lol thank you for the breakdown infact. In that case, last one i tried what the ICS Sense Redefined, and I tried to use the fastboot method for the Included Kernel as well, but that didnt work at all, what ICS Kernel did you flash to get it to work? a Pre-Packaged one? When installing, I did a full wipe (Both the Amon Ra Factory Reset option and the SuperWipe that is in the Dev Forum) installed the Rom, went into the Bootloader and did ADB CMD of fastboot flash boot boot.img and thats about it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22203549&postcount=40
That is the one I used. If you're having issues with fastboot flashing the kernel, you may want to throw the PH98IMG.zip onto your external sd-card and boot into HBOOT then hit vol up to install it that way
angryPirate12 said:
http://forum.xda-developers.com/showpost.php?p=22203549&postcount=40
That is the one I used. If you're having issues with fastboot flashing the kernel, you may want to throw the PH98IMG.zip onto your external sd-card and boot into HBOOT then hit vol up to install it that way
Click to expand...
Click to collapse
ok, i'll give this a shot really quick and do through ext. sd. thanks for the link btw, you've been extremely helpful. let ya know how this goes for me.
I was rooted on MeanROM, and from TWRP I cleared the cache and delvic cache and did a factory wipe, then tried to install the cm10 nightly build, but it said failed, so I cleared and wiped again and tried installing the FreshEVO ROM that I had on it before the MeanROM, it never finished installing, just froze after a while. then TWRP restarted then went into the white HTC "quietly brilliant" screen with the red disclaimer and stuck there. When i hold the power down, it just reboots back to this screen. I cant get it into recovery or bootloader or anywhere but this. My computer isn't recognizing the phone, I tried to adb to it from cmd but its not showing up. I don't think i had the latest hboot or whatever on it, it's been probably two months since i first rooted it. any help would be great, please and thank you. I'm heading to work but i'll check this on my breaks and answer any questions i can about what ive done. I was about to trade the phone for an s3 this saturday, but im sure he wont want it like this! THANK YOU.
I'm just gonna say this and don't take it offensively... That is the risk you took rooting your phone.. if you can get into bootloader, try loading a current ruu on there and see If that works.
Sent from my EVO using Tapatalk 2
thlinx said:
I'm just gonna say this and don't take it offensively... That is the risk you took rooting your phone.. if you can get into bootloader, try loading a current ruu on there and see If that works.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
No offense taken, I understood the risks, and I accept the consequences, which is why I'm fairly calm and not freaking out. I'm going to read more into RUU's on my break, as I'm not completely sure how to do that. Does the computer have to recognize my device for that? I would think so. Is there a trick to getting from this white HTC screen back to TWRP other than trying to reboot or pwr+vol down? Everything just keeps going back here. It wont even turn off without the battery draining.. I'll keep reading on my break, any other helpful comments are definitely welcome. Thanks.
Hold down the power button for 10 seconds and the lights on the capacitive buttons will blink. As soon as the screen goes black wait about half a second then hold volume down and power to get into bootloader then go into recovery.
Hope that helps you. That's how I've always gotten back into recovery when I have a bad flash.
Sent from my EVO using xda premium
BrianBaker said:
Hold down the power button for 10 seconds and the lights on the capacitive buttons will blink. As soon as the screen goes black wait about half a second then hold volume down and power to get into bootloader then go into recovery.
Click to expand...
Click to collapse
This is correct and works. Couldn't boot after trying to install Chainfie 3D drivers but got to recovery this way.
Sent from my EVO 4g LTE on my 3g network.
Happened to me. You have to flash the boot image for cm10 if I recall correctly.
Sent from my EVO
themorningsleeve said:
I was rooted on MeanROM, and from TWRP I cleared the cache and delvic cache and did a factory wipe, then tried to install the cm10 nightly build, but it said failed, so I cleared and wiped again and tried installing the FreshEVO ROM that I had on it before the MeanROM, it never finished installing, just froze after a while. then TWRP restarted then went into the white HTC "quietly brilliant" screen with the red disclaimer and stuck there. When i hold the power down, it just reboots back to this screen. I cant get it into recovery or bootloader or anywhere but this. My computer isn't recognizing the phone, I tried to adb to it from cmd but its not showing up. I don't think i had the latest hboot or whatever on it, it's been probably two months since i first rooted it. any help would be great, please and thank you. I'm heading to work but i'll check this on my breaks and answer any questions i can about what ive done. I was about to trade the phone for an s3 this saturday, but im sure he wont want it like this! THANK YOU.
Click to expand...
Click to collapse
did you ever get this going? Sounds like from what i was seeing you got into your BL finally. I would try reinstalling TWRP like the second part of the OP http://forum.xda-developers.com/showthread.php?t=1794867 and then select reboot to recovery from the bootloader ot the button method. If you get back into twrp restore the last working rom setup you had which sounds like meanrom. If it works come back and let us know.
motcher41 said:
did you ever get this going? Sounds like from what i was seeing you got into your BL finally. I would try reinstalling TWRP like the second part of the OP http://forum.xda-developers.com/showthread.php?t=1794867 and then select reboot to recovery from the bootloader ot the button method. If you get back into twrp restore the last working rom setup you had which sounds like meanrom. If it works come back and let us know.
Click to expand...
Click to collapse
Hey guys, on my lunch break, i got it working! I couldn't get it to go into recovery last night for the life of me, but i tried this morning on my way to work and it worked just fine like it should. For some reason none of my roms would install though other than the jewel stock of the latest update with root that i had on here. It worked and I'm good to go. Thanks for the help though! Anyone know why the roms that i installed before are falling Everette i try to install them now? I always wipe and restore first..
themorningsleeve said:
Hey guys, on my lunch break, i got it working! I couldn't get it to go into recovery last night for the life of me, but i tried this morning on my way to work and it worked just fine like it should. For some reason none of my roms would install though other than the jewel stock of the latest update with root that i had on here. It worked and I'm good to go. Thanks for the help though! Anyone know why the roms that i installed before are falling Everette i try to install them now? I always wipe and restore first..
Click to expand...
Click to collapse
I'm willing to bet that you are not S-OFF, and on Hboot 1.15 or higher, and that was the issue when you tried to install CM10. Make sure you read the instructions for flashing CM10, because you have to do something special to flash a kernel when you are S-ON. Now, as far as the old roms not being able to flash, it may be that they were based on the original 1.13 software version with the 1.13 kernel, and it won't let you flash over your current kernel because the version is older. Essentially, if you are S-ON, you can't flash a kernel unless it matches or is a newer version than the one you have. Of course, you can follow one of the many guides on how to flash boot (kernel) with S-ON to get around this.
timtlm said:
I'm willing to bet that you are not S-OFF, and on Hboot 1.15 or higher, and that was the issue when you tried to install CM10. Make sure you read the instructions for flashing CM10, because you have to do something special to flash a kernel when you are S-ON. Now, as far as the old roms not being able to flash, it may be that they were based on the original 1.13 software version with the 1.13 kernel, and it won't let you flash over your current kernel because the version is older. Essentially, if you are S-ON, you can't flash a kernel unless it matches or is a newer version than the one you have. Of course, you can follow one of the many guides on how to flash boot (kernel) with S-ON to get around this.
Click to expand...
Click to collapse
Wow yes this all made perfect sense! I didn't think about my old roms not being compatible, and i also didn't realize i needed s-off for cm10. I have a bad habit of thinking i can just throw a zip on my card and flash it and it will magically work perfectly lol.. This kind of thinking is what gets me into trouble! Where can i read about turning s-off for installing cm10? Are there links on the download page?
themorningsleeve said:
Wow yes this all made perfect sense! I didn't think about my old roms not being compatible, and i also didn't realize i needed s-off for cm10. I have a bad habit of thinking i can just throw a zip on my card and flash it and it will magically work perfectly lol.. This kind of thinking is what gets me into trouble! Where can i read about turning s-off for installing cm10? Are there links on the download page?
Click to expand...
Click to collapse
S-OFF info is here, but because you are having this issue, you probably have HBoot 1.15 or higher, which means you can't achieve S-OFF until a new exploit is found.
http://forum.xda-developers.com/showthread.php?t=1737123
There are methods for flashing kernels here with S-ON here:
http://forum.xda-developers.com/showthread.php?t=1794867
Also, there's the newer twrp dumlock method if you install the latest version ot TWRP (2.2.1). http://teamw.in/project/htcdumlock
timtlm said:
S-OFF info is here, but because you are having this issue, you probably have HBoot 1.15 or higher, which means you can't achieve S-OFF until a new exploit is found.
http://forum.xda-developers.com/showthread.php?t=1737123
There are methods for flashing kernels here with S-ON here:
http://forum.xda-developers.com/showthread.php?t=1794867
Also, there's the newer twrp dumlock method if you install the latest version ot TWRP (2.2.1). http://teamw.in/project/htcdumlock
Click to expand...
Click to collapse
Ok thanks. My main goal is to not screw this phone up before Saturday when i trade it for an S3 so i may not bother, but i will definitely give it a look!
themorningsleeve said:
Wow yes this all made perfect sense! I didn't think about my old roms not being compatible, and i also didn't realize i needed s-off for cm10. I have a bad habit of thinking i can just throw a zip on my card and flash it and it will magically work perfectly lol.. This kind of thinking is what gets me into trouble! Where can i read about turning s-off for installing cm10? Are there links on the download page?
Click to expand...
Click to collapse
You dont have to have s-off though like he said for cm-10 you just need an extra step or two. I dont blame you for trading it in I did the same. Except I am going back to the Gnex.
motcher41 said:
You dont have to have s-off though like he said for cm-10 you just need an extra step or two. I dont blame you for trading it in I did the same. Except I am going back to the Gnex.
Click to expand...
Click to collapse
I had the gnex before this, why did you go back to that out of the other 2?
themorningsleeve said:
I had the gnex before this, why did you go back to that out of the other 2?
Click to expand...
Click to collapse
Well I'm going back cuz of the non htc clustscrew and the openess of the platform. No bs no s on or s off dev unlocks etc...its how a phone should be. Better camera functionality and I know the sammy platform. Imho it may be older but its a far superior device. Could afford any device out there and to me its hands down gnex
Sent from my SPH-M900 using Tapatalk 2
motcher41 said:
Well I'm going back cuz of the non htc clustscrew and the openess of the platform. No bs no s on or s off dev unlocks etc...its how a phone should be. Better camera functionality and I know the sammy platform. Imho it may be older but its a far superior device. Could afford any device out there and to me its hands down gnex
Sent from my SPH-M900 using Tapatalk 2
Click to expand...
Click to collapse
right on. I did enjoy that phone. I LOVE the camera on my EVO LTE though, that's the one thing ill miss about this one. I did just find out that the ass that was supposed to trade me on saturday already traded someone, so i'm stuck with the LTE for a while now, so i might venture into putting cm10 on it, but then again i might wait til a more stable version hits, just depends on how long that may take..
themorningsleeve said:
right on. I did enjoy that phone. I LOVE the camera on my EVO LTE though, that's the one thing ill miss about this one. I did just find out that the ass that was supposed to trade me on saturday already traded someone, so i'm stuck with the LTE for a while now, so i might venture into putting cm10 on it, but then again i might wait til a more stable version hits, just depends on how long that may take..
Click to expand...
Click to collapse
Ruu it back to stock locked and ebay it. Should get enough for nib sealed gnex. I found one for 319.00. Saw a couple s3 on swappa for about 430-440 nib sealed. Saw a bad esn one going for 290ish so yours should be 350ish or more
Sent from my SPH-M900 using Tapatalk 2
CM10 should be going completely open source with the camera very soon. Expect good things.
To the people complaining about HTC and leaving/trading for new phones.... cya.
That isnt helpful here... we dont need an announcement. Just go please.
Rxpert said:
CM10 should be going completely open source with the camera very soon. Expect good things.
To the people complaining about HTC and leaving/trading for new phones.... cya.
That isnt helpful here... we dont need an announcement. Just go please.
Click to expand...
Click to collapse
Me and the op are having a good clean conversation in his thread so.... cya
Sent from my SPH-M900 using Tapatalk 2
motcher41 said:
Me and the op are having a good clean conversation in his thread so.... cya
Sent from my SPH-M900 using Tapatalk 2
Click to expand...
Click to collapse
Take your private conversation to PM?
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Try reflashing a kernel. Might try stock first, then maybe Elkay's or dsb's writeable.
In case you're doing it a different way, try flashing it this way: flash the boot.img using the Flash Image GUI app. Then flash the corresponding modules for that specific boot.img kernel (can't mix and match) in Recovery.
If that doesn't help the situation, you may need to flash a different radio.
HTH!
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
have you tried a completly different rom?
.torrented said:
have you tried a completly different rom?
Click to expand...
Click to collapse
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
saabguy93 said:
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
Click to expand...
Click to collapse
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Perhaps you accidentally flashed your radio partition? Reflash your radio and you'll probably be good to go. Either that or like someone else said try a different sim card.
Bigandrewgold said:
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I put the SIM in my Nexus and I dont have any problems at all.
saabguy93 said:
I put the SIM in my Nexus and I dont have any problems at all.
Click to expand...
Click to collapse
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Run the RUU again but this time try and just booting into android from the RUU and trying to use your phone
saabguy93 said:
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Click to expand...
Click to collapse
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yeah so it was a rom issue then
Sent from my HTC6435LVW using XDA Premium HD app
Not a Rom issue, I've had the problem on viper and hatka, both before and after soff and new radio. New kernel, old kernel.
I'm getting ready to try stock 1.15 before I ruu.. will report back.
Edit: Fresh off RUU, with the old radios flashed before the RUU. Still no change. Tried turning phone off, remove sim card, phone on, try to use cell connection (obvious failure), phone off, insert sim card and boot. Still no good. About to try above method using CWM and Digital Dream, as soon as it downloads.
Edit 2: Still no such luck. After digging through system logs, there's quite a few errors pertaining to the radio, IccCard, and RIL. One that particularly caught my eye was an error that there stated Ril_get_icc_status returned an error, and it should never return an error. Unfortunately, I didn't get a capture on the time I saw that, the radio reset which Su to reset which caused catlog to reset. Still have quite a few errors pertaining to SIM problems as well. I am way over my head after this point. I can interpret java, and linux.. but not so much understand when they're mixed together in Android.
http://www.pastebin.ca/2317800 This is logcat capture I got of the radio log. Unknown technology doesn't sound good to me....
http://db.tt/nbYfqEkb A full system log as soon as I could save after the force close. Couple things here and there.
I suppose if I can't get it fixed in a day or two.. off Verizon for a replacement. What's the purpose of a phone if I can't make phone calls on it?
Sent from my HTC6435LVW using xda premium
Unless an error loops continually, its okay.
Have you tried to manually select a different network? I'm not quite sure how to do it on a sense rom, but I do know that when I was messing around within my CM10 build and changed to the wrong network type, I lost 4G data in sense. I reflashed CM10, selected a different network and then flashed back and it was working.
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
CharliesTheMan said:
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
Click to expand...
Click to collapse
Any luck figuring this out? I have the same issue and have tried radios, kernels, ROMs, RUU, and am still getting the same error message.
jc332986 said:
I was having "com.android.phone" issues. I relocked then ran the RUU. It didn't fix the error. I unlocked, tried to go Into recovery and there was no recovery. I flashed cwm recovery, flashed busy box/superuser, and rebooted. I flashed cubed kernel. The fix for the phone was to fix permissions with system write capabilities. I'm not sure why the RUU didn't put the phone all the way back to stock.
Click to expand...
Click to collapse
spjoneser said:
I had this problem with my first DNA, warrantied it out after trying all the same things, flashing different roms, RUUing. After replacement I came across a thread somewhere and found that someone had fixed the same problem by simply fixing permissions before doing anything else, sounds like once you flash something else you're screwed.
Anyone try that first?
Click to expand...
Click to collapse
Anyone have an idea about the permissions described here?
same issue
dragonstalker said:
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Click to expand...
Click to collapse
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
jimmydee62 said:
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
Click to expand...
Click to collapse
I'm in the same boat with you my friend :crying:...Can someone please help us. PLEASE!!!