Verizon is sending out replacement phone and need to restore this to stock.
This also started prior to flashing the new ICS leak and after dling ~600mb's via wireless tether.
Not sure if something burned up.
Phone is stuck on 1X only. Tried everything and can't get 3g or reliable 4g.
It get's 4G but only a minute at a time.
I tried doing the various "Fix network bootloop 1x issue threads" but still a no go.
Phone doesn't take the CDMA only option under Mobile networks, it resets back to to lte/cdma.
It never drops to 3g.
I dled the RUU but it does not update nor recover.
Any ideas?
Thanks!
Flash the stock Rom from scrosler's website.
www.scottsroms.com
Droidel said:
Verizon is sending out replacement phone and need to restore this to stock.
This also started prior to flashing the new ICS leak and after dling ~600mb's via wireless tether.
Not sure if something burned up.
Phone is stuck on 1X only. Tried everything and can't get 3g or reliable 4g.
It get's 4G but only a minute at a time.
I tried doing the various "Fix network bootloop 1x issue threads" but still a no go.
Phone doesn't take the CDMA only option under Mobile networks, it resets back to to lte/cdma.
It never drops to 3g.
I dled the RUU but it does not update nor recover.
Any ideas?
Thanks!
Click to expand...
Click to collapse
First thing I'm thinking is you can't RUU back in your situation because the version number is higher than the old RUU. My suggestion is to ROM it, and then flash back to stock RUU, because most ROMs set the version number to 1.0.0.0, therefore all RUU's are a higher version number. Then when you go to flash it, it will recognize, read and flash.
On a side note form this, you're pretty much screwed if you're trying to go to stock from something ripped, since your bootloader will show relocked or tampered, or something other than 'locked' as it shows when completely stock out of the box. This is of course unless you never unlocked it, which means you cant change version numbers, which means you're screwed either way.
Verizon will be able to look at your bootloader and know that it isnt factory stock, so chances are, they are going to charge you for your phone. I'm just trying to be honest and upfront, since I'm kind of a realist when it comes to getting screwed by big corporations like Verizon.
Good luck getting it back to an older version though.
p.s. on the note of your signal issue... the back is on the phone, right? Did you check the contacts inside the cover?
poppajules said:
First thing I'm thinking is you can't RUU back in your situation because the version number is higher than the old RUU. My suggestion is to ROM it, and then flash back to stock RUU, because most ROMs set the version number to 1.0.0.0, therefore all RUU's are a higher version number. Then when you go to flash it, it will recognize, read and flash.
On a side note form this, you're pretty much screwed if you're trying to go to stock from something ripped, since your bootloader will show relocked or tampered, or something other than 'locked' as it shows when completely stock out of the box. This is of course unless you never unlocked it, which means you cant change version numbers, which means you're screwed either way.
Verizon will be able to look at your bootloader and know that it isnt factory stock, so chances are, they are going to charge you for your phone. I'm just trying to be honest and upfront, since I'm kind of a realist when it comes to getting screwed by big corporations like Verizon.
Good luck getting it back to an older version though.
p.s. on the note of your signal issue... the back is on the phone, right? Did you check the contacts inside the cover?
Click to expand...
Click to collapse
The contacts are fine. what if the phone bricked during a software update in hboot? Can they still see relocked and tampered?
Some say that vz doesnt care as long as it has no physical damage.
I don't know about Verizon not caring, but I highly doubt they would take back all of our rooted phones..
I doubt the phone bricked if it booted up. I would flash the ICS RUU and see if the radios fix your signal issue.
Like I said before, I am running Scott's CleamROM and it sets the software versions to 1.0.0.0, so any RUU will flash over it. This is your best bet.
If VZW doesn't care about the bootloader, then you're golden, but don't count on that.
If I may pry, why are you sending it back for the replacement? If it's because of the radios, then I really doubt they are going to just take the phone back, since you could have messed up software to cause the issue.
Just try flashing some stuff before you call it busted. I would go with the ICS leak, Scott's CleanROM, and then back to your old RUU if you want. There's also a patch you have to install to downgrade from CleanROM and ICS leak back to GB, so you might want to do research, also. If you need help finding stuff, just send me a PM.
p.s. Anyone can boot your phone to bootloader (unless of course your phone is in little tiny pieces all over the street), and see that the bootloader is unlocked, possibly tampered for the custom recovery installed, and even if you lock it again, it will say relocked, indicating to everyone that it has been unlocked at one point. 'Unlocked', 'Relocked', 'Tampered', and 'Security Warning' void certain parts of your warranty (in the words of HTC dev.com). The only thing that doesn't void it is if it reads 'Locked'. Period.
Some say that vz doesnt care as long as it has no physical damage.[/QUOTE] Dude I sent two Dinc2 back completed rooted with no problems. Most times the tech at big V. couldn't care less. Most don't wouldn't know what rooting is and the ones that do, more than likely are rooted themselves. The question is if they send it to HTC? And will it meet their requirment now that they have a record that you are rooted as I'm sure if you're had to go thru HTC to unlock. However in reading alot of cases noone have posted a problem with returning a rooted or relocked phone at lease none I've read about. Good luck tho as there's always that first time.
ghostt021 said:
Dude I sent two Dinc2 back completed rooted with no problems. Most times the tech at big V. couldn't care less. Most don't wouldn't know what rooting is and the ones that do, more than likely are rooted themselves. The question is if they send it to HTC? And will it meet their requirment now that they have a record that you are rooted as I'm sure if you're had to go thru HTC to unlock. However in reading alot of cases noone have posted a problem with returning a rooted or relocked phone at lease none I've read about. Good luck tho as there's always that first time.
Click to expand...
Click to collapse
Yeah, I've never tried to send a rooted phone back, personally, but I've never asked anyone at VZW about it. (I'm paranoid that SWAT will descend from the roof and take me down if they knew my phone was rooted)
Good luck dude, just box it up and ship it off then. 'F' 'em.
No go, reflashed ICS leak, the tamper and security warning are gone.
I don't understand why it's not letting me switch to CDMA only. It goes back to CDMA/LTE. Could a bad SIM card cause 3g issues?
I doubt the SIM card would cause 3G issues, but hey, anything is possible I guess. I would say that you wouldn't get ANY signal if the SIM card were bad. Do you have another SIM card phone to test with, perhaps? Just an idea...
Did you go to a ROM instead of just the leak? Hell, you might just have signal issues where you are.. Maybe?
Maybe the antenna did burn up.. never heard of it, but that's not saying it can't happen.
I think tracing your steps back is going to be the best at figuring out the issue. When you flashed the ICS leak, you relocked and flashed, right? no errors? the install went straight down the list with no skipping around? After the install, you went through full HTC/Verizon setup? Have you tried the phone in other locations, i.e. work, groceiry store, gas station, interstate, etc.? Even outside the house will give a different strength... Forgive these sugestions as 'elementary' or 'duh' type suggestions, but something just doesn't sound right.
Also, go to your network settings and try changing the network type from automatic to home only. See what happens.
poppajules said:
I doubt the SIM card would cause 3G issues, but hey, anything is possible I guess. I would say that you wouldn't get ANY signal if the SIM card were bad. Do you have another SIM card phone to test with, perhaps? Just an idea...
Did you go to a ROM instead of just the leak? Hell, you might just have signal issues where you are.. Maybe?
Maybe the antenna did burn up.. never heard of it, but that's not saying it can't happen.
I think tracing your steps back is going to be the best at figuring out the issue. When you flashed the ICS leak, you relocked and flashed, right? no errors? the install went straight down the list with no skipping around? After the install, you went through full HTC/Verizon setup? Have you tried the phone in other locations, i.e. work, groceiry store, gas station, interstate, etc.? Even outside the house will give a different strength... Forgive these sugestions as 'elementary' or 'duh' type suggestions, but something just doesn't sound right.
Also, go to your network settings and try changing the network type from automatic to home only. See what happens.
Click to expand...
Click to collapse
I noticed this happeneng a day prior to flashing the ICS leak. I was using wifi tether do download about 600mb's and notice a couple of hours later that it dropped to 1x. Restarted phone and it went to 4g. I usually switch to 3g to save battery, that's when i notice the problem.
The ics leak flash didn't show any errors.
I am trying to flash GB to this new firmware but i'm having a hard time flashing the PH98IMG RUU from scott's site. It reads and checks it but doesnt flash it.
RUU.exe errored out with "Unknown Error"
Droidel said:
I am trying to flash GB to this new firmware but i'm having a hard time flashing the PH98IMG RUU from scott's site. It reads and checks it but doesnt flash it.
RUU.exe errored out with "Unknown Error"
Click to expand...
Click to collapse
Make SURE you are pulling the PH98IMG for the stock RUU from the android police website, NOT Scott. He didn't post up the new leak. The RUU that Scott has will NOT flash over the old ICS stuff he's put out before.
Go here to get the leaked RUU.
In this process, relock your bootloader, flash the file from A.P.(TWICE, this is important), unlock your bootloader with your unlock token from htcdev, and THEN flash what scott has. It's a time consuming process. It's up to you though. The directions are out there on A.P., Scott's website, all over Scott's thread around the 400-page range for the 4.0.1 release... and my abbreviated directions here.
Grab one of the top three selections, not the pre-rooted version.
also, try going back and re-downloading your ROM file, maybe you got a bad download.
If you upgraded to ics, you can't ruu to gingerbread at all because of the older hboot. But you can flash a gb kernel then a Rom or nandroid+ scrosler sdcard fix
Sent from my ADR6425LVW using xda premium
Related
So one of the 5 pins in the mini-usb connection is missing. This disables any sort of data connection through usb, however I'm still able to charge the phone. Now I think I can get my phone replaced by Verizon but as it is right now I have dcd's 3.2.0 rom and the 3.42.30 radio. I have no problem flashing through my sd card as far as roms and radios go, but can the bootloader be relocked in the same fashion? I know the procedure for relocking is in the wiki but it relies on an activesync connection, which I cannot make. Am I proper f*cked or can I do this relocking?
So one of the 5 pins in the mini-usb connection is missing. This disables any sort of data connection through usb, however I'm still able to charge the phone. Now I think I can get my phone replaced by Verizon but as it is right now I have dcd's 3.2.0 rom and the 3.42.30 radio. I have no problem flashing through my sd card as far as roms and radios go, but can the bootloader be relocked in the same fashion? I know the procedure for relocking is in the wiki but it relies on an activesync connection, which I cannot make. Am I proper f*cked or can I do this relocking?
Click to expand...
Click to collapse
You can't relock unless you have an activesync connection. You can relock using nuespl, but it will relock to 2.07 which is the GPS rom stock bootloader...something that doesn't exist yet for Verizon.
I think ImCoKeMaN @ PPCGeeks has a relocker for the 1.06 bootloader that can be run from SD. It's not recommended for use after running a GPS ROM/Radio, but I've heard of a few success stories. Of course, I've also heard of a number of devices becoming completely and utterly useless after trying this. I don't think he made the version that can run from SD publicly available, but you could try shooting him a PM. He'd be able to give you all the details as well. Might be worth a shot as a last resort.
I might give that a try. If I recall, I can set up an activesync through bluetooth, which is what I'm goin to try first. If that's impossible I'll be pming ImCoKeMaN. Thanks
If you have the insurance it would be unfournate when it takes a trip in to the Shower or Tub.
Big Dawg 23 said:
If you have the insurance it would be unfournate when it takes a trip in to the Shower or Tub.
Click to expand...
Click to collapse
Or even better, falls down into the toilet. Chances are the people at Verizon won't want to poke around with it in that case.
Before I go through relocking or flushing my phone I thought I'd try to bluetooth connect it to try activesync. Well, it seems that the only connect I can make is to use it as a dial-up modem, a serial connection isn't possible. Has anyone else with dcd's rom tried to connect to a pc for file transfers and succeeded?
Honestly, I think the flashing / locking software relies on the USB connection. If I remember correctly, once the connection is made through Activesync... it disconnect Activesync. I'm not sure if this connection stays available for the flashing / locking. I personally don't want to try and brick my phone. LOL
Nitro is correct. The unlockers/relockers that run from your PC place your phone in bootloader mode, and at that point your bluetooth connection would drop.
The real issue isn't the broken USB port. There are ways to relock from SD. Your main problem is that going from a GPS ROM/Radio/SPL to a non-GPS version has been known to brick devices. You could always try and hold out until VZW releases an official GPS ROM, then you wouldn't have to worry about going back to a 1.x SPL. From what I've seen, gc14 may have some insight into when that ROM will actually be released.
I had a similar issue happen to my sprint mogul, I was able to charge but the mini-usb connector was messed up so I could not get a data connection.
I re-flashed the latest stock rom and radio from the sd card and took it in. Both the service reps and the technicians did not notice the bootloader version, and I got a replacement for free within 30 minutes or so. I would think that with all the devices they work with, the vast majority of people do not have unsupported software versions and the techs most likely do not check every time (or just do not care all that much).
Just my thoughts and experience though, yours with Verizon could obviously differ.
EDIT:
Ahh yeah I forgot that Verizon has not released their gps radio yet and that downgrading can be problematic... Best of luck to you.
VerusMaya said:
I had a similar issue happen to my sprint mogul, I was able to charge but the mini-usb connector was messed up so I could not get a data connection.
I re-flashed the latest stock rom and radio from the sd card and took it in. Both the service reps and the technicians did not notice the bootloader version, and I got a replacement for free within 30 minutes or so. I would think that with all the devices they work with, the vast majority of people do not have unsupported software versions and the techs most likely do not check every time (or just do not care all that much).
Just my thoughts and experience though, yours with Verizon could obviously differ.
Click to expand...
Click to collapse
Same exact issue here, except I did go ahead and put the 2.07 SPL back on. They are wanting to charge me $35 though. How long ago did you get your phone? I might try a few other shops and see if they'll swap me a new phone for free.
I'm going to try and make it as stock as possible and go for the return. I've found what seems to be a lot of conflicting procedures for returning to Verizon stock roms and radios, is there a 'best' one?
egrzelak said:
I'm going to try and make it as stock as possible and go for the return. I've found what seems to be a lot of conflicting procedures for returning to Verizon stock roms and radios, is there a 'best' one?
Click to expand...
Click to collapse
Yeah, this one here.
bedoig said:
Same exact issue here, except I did go ahead and put the 2.07 SPL back on. They are wanting to charge me $35 though. How long ago did you get your phone? I might try a few other shops and see if they'll swap me a new phone for free.
Click to expand...
Click to collapse
I got the original one in late December and got them swapped about two months ago. I was actually rather surprised I got it so hassle-free and without paying anything, I expected to have to pay some warranty fee or something.
I ran into this situation about a month ago, except the data port was hosed enough I couldn't charge or sync. After stressing about it I contacted a major contributor to the board and he said not to worry about it.
So I took the phone in (@ 3 mos. old) and the vzw sales guy was pretty cool about it (I didn't mention anything about flashing the software). He got on the phone with someone else at vzw tech and did some kind of exchange program. A few days later I had a new 6800 and instructions to send the old phone back.
I probably should have secured the phone better in the box when returning, but oh well. I seriously doubt anyone even looked at the rom, since it was a hardware issue.
why not just get a new cable?
deeznuts2 said:
why not just get a new cable?
Click to expand...
Click to collapse
The cable isn't the problem as the pin is missing from the phone.
Alright, so the only way to relock back to Verizon's original SPL is with a working USB. Over on ppcgeeks there seem to be some people who've flashed back to the stock radio and rom without relocking the phone. They only problem they've experienced is it being unable to wake up when it's been put in sleep mode. I think this is what I'm going to do to do the return.
egrzelak said:
I'm going to try and make it as stock as possible and go for the return. I've found what seems to be a lot of conflicting procedures for returning to Verizon stock roms and radios, is there a 'best' one?
Click to expand...
Click to collapse
Look at it this way if you brick it who cares....you are trying to get it replaced.....
I've recently rooted and had some issues with my personal phone, which I've cleared up with help from this board and members, and have actually enjoyed messing with my phone, its been fun learning about android and the possibilities with these phones. But with a bit of hesitation on going at it again with my phone, and how screwed I was when I couldn't get it going for a while, I thought I'd browse for a spare phone, anything, something old to screw around with and really practice on.
well, don't I find a 'bricked' amaze in my local classifieds! so $50 later I have myself a spare amaze to mess with! This phone powers on and goes straight to hboot, and I thought sweet, a factory rom upgrade and away we go. but it wasn't so easy.
this phone is a telus, and was relocked, but the one thing I noticed on this one that I didn't on mine when I flashed the telus rom is that this one has a 'security warning' under the relocked banner at the top of hboot. For the life of me I can't seem to get an oem rom to upgrade this phone. I've tried 3 different sd's, formatting etc. downloading the telus ruu zip from lots of different sites, trying with sd out then installing it when hboot loads, with and without usb plugged in, you name it I've tried it, and I cant' seem to get a stock rom to load.
hboot checks for ph85diag, then ph85img, finds it, checks it, then checks it again and back to hboot. No matter what I do, it won't ask to upgrade, and even trying out other ruu's it'll at least tell me that its the wrong file. Funny thing is in all of this I've already done this on my fully working amaze, and it worked right away, the only thing I'm thinking is that security warning banner, if that's in any way preventing the install.
any thoughts?
andy55 said:
I've recently rooted and had some issues with my personal phone, which I've cleared up with help from this board and members, and have actually enjoyed messing with my phone, its been fun learning about android and the possibilities with these phones. But with a bit of hesitation on going at it again with my phone, and how screwed I was when I couldn't get it going for a while, I thought I'd browse for a spare phone, anything, something old to screw around with and really practice on.
well, don't I find a 'bricked' amaze in my local classifieds! so $50 later I have myself a spare amaze to mess with! This phone powers on and goes straight to hboot, and I thought sweet, a factory rom upgrade and away we go. but it wasn't so easy.
this phone is a telus, and was relocked, but the one thing I noticed on this one that I didn't on mine when I flashed the telus rom is that this one has a 'security warning' under the relocked banner at the top of hboot. For the life of me I can't seem to get an oem rom to upgrade this phone. I've tried 3 different sd's, formatting etc. downloading the telus ruu zip from lots of different sites, trying with sd out then installing it when hboot loads, with and without usb plugged in, you name it I've tried it, and I cant' seem to get a stock rom to load.
hboot checks for ph85diag, then ph85img, finds it, checks it, then checks it again and back to hboot. No matter what I do, it won't ask to upgrade, and even trying out other ruu's it'll at least tell me that its the wrong file. Funny thing is in all of this I've already done this on my fully working amaze, and it worked right away, the only thing I'm thinking is that security warning banner, if that's in any way preventing the install.
any thoughts?
Click to expand...
Click to collapse
unlock it done
you're kidding, its that easy? I thought about it too and didn't try that. First thing I'll be doing when I get home
what I was screwed by was I did the exact same thing to my good phone, I re-locked it, and loaded the telus rom and it went easy, no problems, and I tried the same with this phone, and no dice
did the unlock trick work
I'll let you know in a couple hours, the dud's at home and I'm stuck at work with computers that encrypt everything connected to them no screwing around (to a certain degree) at work
yup worked, had issues with wifi/bluetooth but bulletproof fixed that issue, all is working again, thanks, I can't believe I didn't think that would work before!
So I was on SOS Rom with Chad's linux 3 kernel and did the wire trick. I got s off, yay!!!!
So, now my wifi stinks, 3g stinks, my touch screen was affected, I have slight dead areas. I can't flash kernels, but I can flash boot screens. Totally not worth the trade off, lol. I have tried CWM, 4Ext, fastboot and flash image GUI. None work
Anyone have any ideas WTF is going on? Or what I need to do? I was thinking about using google to find out how to get s on and try the wire trick again, or just stay s on.
Would I need to flash a firmware from Frieza to possibly fix the kernel issues? I have no idea how that would help at all, lol.
If anyone else has had issues like this,.what did you do?
XDA senior techs, any ideas?
Not saying the wire trick stinks, just saying I ran into an issue I cant figure out
Sent from my PG86100 using XDA
Well I'm deeply sorry for your issues but I also believe that the issues your experiencing is not totally related to the "wire trick".
The effects of the wire tricks can't do much damage because the voltage going out of the pin#1 is not enough to cause massive effects with the small amount of time you make contact with ground.
Questions :
what kind of wire did you use?
How long did you place the wires in full contact?
I would say as well that disclaimers are posted and there are risks with following any prodcedures written in this site.
Try flashing a RUU and see what happens, perhaps that could be a way out?
Sent from my PG86100 using Tapatalk 2
Nametaken said:
So I was on SOS Rom with Chad's linux 3 kernel and did the wire trick. I got s off, yay!!!!
So, now my wifi stinks, 3g stinks, my touch screen was affected, I have slight dead areas. I can't flash kernels, but I can flash boot screens. Totally not worth the trade off, lol. I have tried CWM, 4Ext, fastboot and flash image GUI. None work
Anyone have any ideas WTF is going on? Or what I need to do? I was thinking about using google to find out how to get s on and try the wire trick again, or just stay s on.
Would I need to flash a firmware from Frieza to possibly fix the kernel issues? I have no idea how that would help at all, lol.
If anyone else has had issues like this,.what did you do?
XDA senior techs, any ideas?
Not saying the wire trick stinks, just saying I ran into an issue I cant figure out
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Oouch! I hope there is a fix for you, I'm sure you are going to try everything.
I don't know how to fix this but I do know a little bit about electronics. Actually quite a bit. Sounds like this trick shorted out or caused a voltage spike internally. Generally when an electronic component is damaged, there is no fix.
When you let out that factory installed smoke, you can't get the Genie back in the bottle.
I had a laptop once where the fan stopped working. I bought a new one. New one was not getting any voltage. A friend of mine was sitting at the bench with me. He decides lets just find another spot with same voltage and tap in there. Starts jumping wires around on the mother board and poof -- $1,000 dollar laptop on sale for parts on Ebay. Took me a long time to get over that one.
I was just looking around and found a problem similar to yours, in the "wire trick" thread. http://forum.xda-developers.com/showthread.php?p=26390751
Yeah... I totally noob bombed that dev thread so o started up a qna here lol
Sent from my PG86100 using XDA
Just a little more info. I can flash other kernels, but on sense Roms, it just shows up as the same name as the other stock kernel. I was able to fully flash other roms, like AOSP. Once I flash AOSP, I can see the other kernels I flash.
Flashing AOSP:
While I can flash it and other kernels, I get stuck on being able to activate my phone on the device. It gets stuck saying airplane mode is on. Totally sucks. Haven't tried activating online or by calling sprint. I have been busy with family stuff.
If anyone else has issues, post em up! Perhaps we can all help each other out
Sent from my PG86100 using XDA
So Here's what I ended up doing. After wire trick got me the S-Off, I had that ICS HBoot and thought hey, maybe this has something to do with my weird AOSP issues (for background please see my post in the CDMA developers section in the JBear thread), so I flashed my 2.17 RUU that I had handy. After that, I updated PRL and Profile (hoping this would do something). Then to my surprise, everything was stock again, bootloader read hboot 1.5.0 again instead of the 1.57 one, however no root because it's an RUU! Anyway, I kept reading through the thread like some of these folks told me, however I didn't find much, I did see that most people with success were using the JBear GB version. So, I flashed the jb_hboot from the GB version (I actually took another guy's advices and simply renamed the jb_hboot.zip file to PG86IMG.zip, this worked! Got me the Jbead modified GB bootloader on 1.50. SO I guess since we're S-Off, I was able to go back to hboot 1.50 and then did a fastboot flash recovery recovery.img and flashed the Ext4 recovery image I had. From there, I restored the nandroid I had (Nocturnal ICS Xi36 r105) and it all booted up fine. Later I will try flashing back to CM9 and see what happens, perhaps I'll be able to get out of this "sort of Airplane mode" that isn't really airplane mode (where the phone htinks it's deactivated.)
The key here is that while I was on GB RUU, I updated PRL and Profile, then went to the 1.5 hboot hoping that would be enough for the CM 9 rom and other AOSP ICS roms to activate upon install. I'll keep you posted.
Thanks for starting this thread man, we need a place to sort all this out. With all the info that floods the OPs of development threads, it's hard to really find what is even relevant. So, glad to see one in the Q and A that we can ask questions.
Well what i can say is that after trying the wire trick my device would randomly turn off and stop working. No charge, No light. Nada. Completely dead then it would randomly come back to life. Anyways. I took my phone to sprint today and ill be going back in two hours to see what the problem with my phone is.
I personally think its a hardware issue. Maybe i used a bad wire? Or i touched the wire during the process which is known to mess up your device.
Thinking about it . I don't see why people don't downgrade instead of the wire trick.
Update- Sprint told me my device had hardware issues and will send me a new phone within 4 days.
There is a possibility that, as someone else has pointed out, that we are indeed hurting our phones. Not so insulated wires, paperclip with tape etc, is the culprit. Too much static getting in and possibly hurting our phones. Something to think about.
To RUU Paul, lol,
I was thinking of uprooting using a similar method like you and gaining root again to ensure it isn't permanent. While it seems you could make it back, this could mean it is a software issue then, but it is too early to tell. Hopefully we cab get enough of the anomalies in to pin point this.
Sent from my PG86100 using XDA
cmbaughman said:
Anyway, I kept reading through the thread like some of these folks told me, however I didn't find much, I did see that most people with success were using the JBear GB version. So, I flashed the jb_hboot from the GB version (I actually took another guy's advices and simply renamed the jb_hboot.zip file to PG86IMG.zip, this worked! Got me the Jbead modified GB bootloader on 1.50. SO I guess since we're S-Off, I was able to go back to hboot 1.50 and then did a fastboot flash recovery recovery.img and flashed the Ext4 recovery image I had.
The key here is that while I was on GB RUU, I updated PRL and Profile, then went to the 1.5 hboot hoping that would be enough for the CM 9 rom and other AOSP ICS roms to activate upon install. I'll keep you posted.
Thanks for starting this thread man, we need a place to sort all this out. With all the info that floods the OPs of development threads, it's hard to really find what is even relevant. So, glad to see one in the Q and A that we can ask questions.
Click to expand...
Click to collapse
Thanks for pointing this all out! I can confirm that doing this allows us to flash back to AOSP with Airplane mode off and get it all up and going.
Once in there, you can change out your kernel and see that it is changed under About Phone! I loves you so much!
Now, if anyone has a way to verify if a kernel was changed or not, we can see if my idea was right about it flashing the kernel, just not showing the correct name of the kernel that was flashed
Thank you all the effort you guys have put into this. I too ran into this issue, and simply flashing the GB hboot resolved my issue. Just so everyone knows, that it is not necessary to revert to stock first. Just simply flash the other hboot, and you should be good to go.
Hey, guys. I'm having a heating issue with my Rezound. It's on Newt's OneXxX RLS3 right now, 3.14.605.5 and his kernel, S-On, just flashed it this morning in the hopes it would fix my overheating issues, but no luck.
Last night, and from May 30th, I was on BAMF ICS 2.1, 3.11 firmware. I made a 15 minute call to my Mom, and went from 100% to 87%, and up to 123 degrees with alternating amber/green light.
Just a few minutes ago, spent about 10 minutes on the phone and playing on the net, and it was up to 110 degrees, and in 10 more minutes, went from 69% battery to 25%, so looks like Newt's didn't fix it either.
I need to know what I need to do to get it into a returnable condition. Do I need to re-lock the bootloader? If so (I assume so) will that be enough to get past Verizon, or do I need to return it to stock? Do they look at software numbers and stuff? I really don't want to have to S-Off the damn thing just to get it back to GB to return it.
I tried to call Verizon and have them send me a replacement, but the tech lady said I'd need to take it to a brick and mortar store to have them check it out. She said they would want to check out the battery, the charger, and the phone.
Ok, didn't get an answer so I went ahead and S-Off'd. Now where are the directions for reverting to GB....
First, please confirm you didn't run HTCDev Unlock again after S-off, at least tell me you kept stock bootloader or flashed the JB hboot lol. If you did, you'll need to redo the S-off process to get the "Unlocked/Relocked" flag to change back to "Locked". If you are worried about full stock appearance for warranty purposes.
Download the 2.01.605.11 GB RUU, preferably the PC .exe version since it can wipe stuff easier remotely.
http://forum.xda-developers.com/showthread.php?p=19756694
Glad you were able to accomplish S-off quickly, since you don't have much technical trouble you'll probably want to follow this guide to reset the S-on flag too: http://forum.xda-developers.com/showthread.php?p=25165453
Ah, crap. No, I forgot to install the jb_hboot. I've already installed this Rom: http://forum.xda-developers.com/showthread.php?t=1467329 but I still have Amon Ra. I'm locked, but still S-Off. Can I install the 2.01 over top of what I have already? And will it overwrite the recovery?
Danariel said:
Ah, crap. No, I forgot to install the jb_hboot. I've already installed this Rom: http://forum.xda-developers.com/showthread.php?t=1467329 but I still have Amon Ra. I'm locked, but still S-Off. Can I install the 2.01 over top of what I have already? And will it overwrite the recovery?
Click to expand...
Click to collapse
Well the point is actually that once you run HTCDev Unlock on the bootloader, only S-off magic can make the flag a stock "Locked" message. Relocking normally shows "Relocked" which still indicates tampering lol. Sounds like you are good if it is still "Locked" that is what you want.:thumbup:
Yes, run the RUU and it overwrites the ROM, the recovery, bootloader, radios, and factory resets the data. What it does not affect are the flags in the bootloader (i.e. Locked/Unlocked/Relocked and S-on/S-off) That RUU covers all warranty issues except S-off flag. To toggle to S-on, all your accessing past this point will be from the adb commands you have from HTCDev/S-off process if that is what you're wondering.
So yeah, from where you are just run the RUU, do Scotty's guide for the S-on flag. Just remember on Scotty's guide you must boot into the ROM after the RUU to toggle USB debugging in the settings. So go back into the bootloader after the guide and do a factory reset to cover those tracks lol.
Well, I managed to install the jb_hboot, but now there's no Recovery at all. And since I'm already on 2.01, the .exe is failing. I think I need to set Mainversion Low, but since I don't have a recovery...looks like I'll have to use the other file to flash it in the bootloader. I'll let you know how this goes.
Edit: Ok, I am now Locked, and S-On. However, it won't boot. When I go to turn it on, it boots to a black screen with a circle arrow and one in the middle pointing down over the picture of a phone. I managed to brick it, didn't I?
Edit 2: Ok, it's rebooting now...and we have Stock! I rebooted into the bootloader to verify LOCKED, S-ON, but there's still nothing when I try to go to recovery. IDC, that's good enough for me dammit. I'm through with it for the night!
(And thank the gods I remembered to uninstall my Blizzard Authenticator before I did all this crap...)
Danariel said:
Well, I managed to install the jb_hboot, but now there's no Recovery at all. And since I'm already on 2.01, the .exe is failing. I think I need to set Mainversion Low, but since I don't have a recovery...looks like I'll have to use the other file to flash it in the bootloader. I'll let you know how this goes.
Ok, I am now Locked, and S-On. However, it won't boot. When I go to turn it on, it boots to a black screen with a circle arrow and one in the middle pointing down over the picture of a phone. I managed to brick it, didn't I?
Click to expand...
Click to collapse
Soft brick. That is the stock recovery... Did you do S-on with the JB hboot and/or custom ROM? That could cause that per the warnings in Scotty's thread.
Edit 2: haha good deal, congrats. Yes, that is what stock recovery looks like, no alarm needed.
PhantasmRezound said:
Soft brick. That is the stock recovery... Did you do S-on with the JB hboot and/or custom ROM? That could cause that per the warnings in Scotty's thread.
Edit 2: haha good deal, congrats. Yes, that is what stock recovery looks like, no alarm needed.
Click to expand...
Click to collapse
Thank you so much for all your help!
The temp on this ***** is 121 Degrees Fahrenheit right now. She's going BACK tomorrow! Absolutely unbelievable. You know, come to think about it, my Thunderbolt had overheating/rebooting issues until I rooted it and got a custom ROM. I really hope I get a good one, this time, I'd hate to go through all this **** again.
Danariel said:
Thank you so much for all your help!
The temp on this ***** is 121 Degrees Fahrenheit right now. She's going BACK tomorrow! Absolutely unbelievable. You know, come to think about it, my Thunderbolt had overheating/rebooting issues until I rooted it and got a custom ROM. I really hope I get a good one, this time, I'd hate to go through all this **** again.
Click to expand...
Click to collapse
All phones are different, depends on how a person uses it. But the radio, charginig method, running apps, and likely hardware are all factors. http://forum.xda-developers.com/showthread.php?p=20138465 Worth skimming through. Some now have newer XE and unmarked hardware models which may have better temperature performance, time will tell. Could be worse... Just don't know if these hardware revisions address quality issues with heat, or are meant to reduce production cost. Probably both. Perhaps inconsistent from revision to revision; maybe a middle-aged model got cheaper but unexpectedly ran hotter. Need to be an HTC insider or get plenty of feedback to isolate the effect hardware revision has in the overall heat equation.
Edited for TL;DR-ness of anecdotal info. Good luck with the replacement.
PhantasmRezound said:
All phones are different, depends on how a person uses it. But the radio, charginig method, running apps, and likely hardware are all factors. http://forum.xda-developers.com/showthread.php?p=20138465 Worth skimming through. Some now have newer XE and unmarked hardware models which may have better temperature performance, time will tell. Could be worse... Just don't know if these hardware revisions address quality issues with heat, or are meant to reduce production cost. Probably both. Perhaps inconsistent from revision to revision; maybe a middle-aged model got cheaper but unexpectedly ran hotter. Need to be an HTC insider or get plenty of feedback to isolate the effect hardware revision has in the overall heat equation.
Edited for TL;DR-ness of anecdotal info. Good luck with the replacement.
Click to expand...
Click to collapse
LOL, Bacon Mode! Yep, that's my phone to a Tee. However, i'm not going to LET it get to 135 or 152 before I take it back. That's Extra Crispy bacon right there!
Hello all!
My bro just got the rezound and I was able to root it and slap on a recovery and get a custom rom. Well, the rom wouldn't boot so I tried different boot.img options and finally just did the s-off procedure (scary much) now it will boot just fine. I get to the rom and no data/voice but wifi works. I have downloaded the newest radio package, flashed it in hboot and still no avail. I went back into hboot, went to clear storage, wiped cache, dalvik, rebooted and now the same. I'm going to try and flash an AOKP rom to see if anything changes but this is way frustrating me. Any words of advice? Thanks in advance :fingers-crossed:
Well don't I feel like a newb. I was browsing on another forum and I saw a post that had "HTC Rezound Fun Facts" and it said that the radio is inside the battery cover....this is awesome because I had the case off this whole time since I had to do sooooo many battery pulls (plus I have never had an issue like that before). I put the cover back on, and whaddya know, I have radio again! Fun learning experience. :ashamed:
Yep. That's one reason this phone gets such great reception...the antennas aren't covered by a bunch of metal and plastic...just what's in the back cover.
pogibry said:
Well don't I feel like a newb. I was browsing on another forum and I saw a post that had "HTC Rezound Fun Facts" and it said that the radio is inside the battery cover....this is awesome because I had the case off this whole time since I had to do sooooo many battery pulls (plus I have never had an issue like that before). I put the cover back on, and whaddya know, I have radio again! Fun learning experience. :ashamed:
Click to expand...
Click to collapse
Don't feel bad about it, Verzion couldn't figure out what you did. When I first got my Rezound, my SIM had trouble activating after a friend tried out their SIM in it first.
Was sitting in a Verizon cellular center for over an hour, talking with customer support on the store phone. They told me to remove the back cover and keep it off while removing and reinserting the battery and SIM a bajillion times, checking for the network signal. They fixed my account info, but the phone strangely was not picking up still.
Only turned on, of course, once I put the cover back on as I was leaving for a Verizon store next county over to get a whole new replacement phone. You'd think one of the dozen or so Verizon reps I interacted with that day would've identified the issue, especially with two other Rezounds in the store and two being worked with on the other end of the phone.
4g Not Working
Now that you guys mention that, I got it working but 4g is still a nogo :crying: Is there any other way I can get it to work aside from re-locking my bootloader and flashing a stock RUU? I'd really hate to have to go through that ordeal again.
I found this awesome thread so let's see how it goes!
http://rootzwiki.com/topic/25841-firmware-icsgb-firmware-combos/
pogibry said:
I found this awesome thread so let's see how it goes!
http://rootzwiki.com/topic/25841-firmware-icsgb-firmware-combos/
Click to expand...
Click to collapse
I don't know if this helps, but I was on hboot 2.25 and after that link, I am at hboot 2.27 and I'm running the AOKP rom.
Still no dice, my friends. Any ideas?
Mercifully the RUU worked and I am back on factory ICS, unlocked with s-off, rooted and with working 4g! Since I was unlocked AND s-off, I didn't have to relock my phone (praise the Lord!). I reflashed TWRP and now will try to install just a rom with nothing else. We'll see how it goes. :fingers-crossed:
4g works and it's still rooted! Wow that was a *fun* 9 hours of fiddling. Let's see how long it lasts. But until then, the AOKP ROM for the Rezound is pretty slick and smooth, FYI.
***Please hit thank you if my sacrifice has helped you in anyway **