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!
Related
Ok, so I've been working for a solid 2.5 days straight trying to repair an Eris I purchased on ebay.
I've flashed and re-flashed and done all sorts of crap and now it seems I'm in a pickle.
I was able to use RUU's just fine at the start of all this, additionally the phone's MIN showed up normally as well and also when I connected the phone to say QPST it showed up as a droid Eris.
Now the RUU's always give "error[130]: model id error," the MIN shows up as "0000009763" and the phone is recognized as a "FFA/SURF 7600 WinMob" phone of some sort.
My problem is that I'm trying to downgrade using an RUU to RUU_Hero_C_Sprint_2.27.651.5_R_signed_release in hopes that that will help me with the repair but I can't because of the RUU error.
Additionally, I feel like I may have just plain screwed up my phone with all this.
If anyone could please give some pointers or even just an encouraging word to lift my spirits I would be so appreciative as this is really starting to wear on me.
You guys are awesome even if there is no help for me..thanks for everything!
conradcliff said:
I was able to use RUU's just fine at the start of all this, additionally the phone's MIN showed up normally as well and also when I connected the phone to say QPST it showed up as a droid Eris.
Now the RUU's always give "error[130]: model id error," the MIN shows up as "0000009763" and the phone is recognized as a "FFA/SURF 7600 WinMob" phone of some sort.
My problem is that I'm trying to downgrade using an RUU to RUU_Hero_C_Sprint_2.27.651.5_R_signed_release in hopes that that will help me with the repair but I can't because of the RUU error.
Click to expand...
Click to collapse
I can not imagine even a single reason why you would ever attempt to flash firmware meant for one phone onto a different phone - especially if there was a bootloader replacement involved. The fact that the phone does anything at all after doing that is almost a miracle, frankly. (Yes, I realize that the Hero is a cousin of the Eris, but that doesn't also mean they share the same partitioning layouts, kernel load addresses, hardware interrupt structure, etc).
But, I suppose you are aware of that by now. It is probably also why no-one is offering any help - you are in territory where folks don't normally venture.
Personally, I would sell the phone on eBay described as a "for parts" unit and eat the difference between what was originally paid for the unit.
bftb0
Hmm, just following instructions I've gotten from several different sources.
I was leery as well, but after flashing that RUU a couple times prior with no ill effects it would seem that the information I received wasn't faulty.
Thanks for the input though.
If you did something meant for the hero and tried it on the eris then it is faulty. Just because something hasn't happened yet doesn't mean it won't
Sent from my FroyoEris using XDA App
I have since gotten back everything back pretty much to normal..though qpst still reads the phone as a SURF 7600 WinMob. I've got a 1.49.2000 S-OFF bootloader and eris radio and rom. Things are looking up from before but I stil haven't gotten it working on Metro..
Get it flashed over from a metro store then I can help you get the net on it
Sent from my FroyoEris using XDA App
Will a metro store flash this phone over? I thought they would flash data phones...
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
So, long story short, took the Phone into Sprint so they could look at my headphone jack (was cracked and left ear bud would constantly cut in and out) because its acting up.
Gave the Tech the phone without the battery in it (since he didn’t need to power up the device to clearly see the headphone jack has a huge crack in it) but I left my SD card installed. As he was walking away, I asked him if I could remove my SD card and he let me, then seen that I gave him the phone without a battery. So, I ended up giving it to him (praying he didn’t turn it on and see ViperBoys sick ass ROM booting up) and he accidently pressed the power button turning the phone on. Promptly short after, he removed the battery when the phone was on the HTC screen, didn’t even get the boot animation. I was like OHH $h!t, that gonna mess up my phone & sure as $h!t, it did… Just loops in and out of that screen resetting each time with a little vibrate then looping.
I can get into Fastboot and use ADB, I’ve flashed RUU’s, put Stock image on root of SD and let recovery restore (losing my CWM & my HBOOT 1.400), unlocked, relocked, wiped, thrown, and screamed at it with no luck.
I did do a CWM backup before even setting foot in the Store, so I do have a backup. The 1st thing I tried was restoring it through CWM recovery and that didn’t stop the looping. I can still get into fastboot via power + vol down and adb functionality is still there.
HBOOT is 1.50 and s-on is enabled..
Been reading through threads since lunch and tried many different solutions without success. It seems once a phone is this far gone, people stop responding.
Anyone have any ideas?
New phone will be here tomorrow (free of coarse courtesy of Sprint insurance) but I’ve been without a phone all day and most of yesterday. I’d like to get this one back to stock and booting before I trade it in for the replacement tomorrow
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
yousefak said:
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
Click to expand...
Click to collapse
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
lessegr said:
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
Click to expand...
Click to collapse
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
yousefak said:
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
Click to expand...
Click to collapse
BUMMER! In case the question comes up I ran "RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed" and it ran just fine.
Hmm, hardware issue. Dont see how I can check for that if it doesnt boot.
Guess I'll just have to wait for the new Phone
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
jdeoxys said:
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Click to expand...
Click to collapse
The HTC unlock went as expected. Followed the directions to the "T", then relocked, checked in fastboot (not that I could check anywhere else, LOL) and the phone says "*** RELOCKED***". Ran 2.17.651.5 RUU successfully to the finish. Still looping
WEIRD!
DarkManX4lf said:
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
Click to expand...
Click to collapse
Because I just want to know WTF happened!!! Had this Phone since release, abused\used the hell out of it by flashing ROMs constantly, restoring backups, tethering like crazy, emailing, texting, FBing...
No reason for it to crap out on me from a simple mistake, not even of my responsibility, lol!
The only issue I've had with this Phone is that damn headphone jack 1/2 way failing..
Got new phone, terrified to even think about trying to flash new ROM though
lessegr said:
Got new phone, terrified to even think about trying to flash new ROM though
Click to expand...
Click to collapse
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Threevo said:
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
DONT TEMPT ME DAMMIT! lol! Just been without a phone for almost 3 days. I'm also seeing a lot of new threads about people experiencing what I've gone through.
Woops, sprint\HTC! once again rooted, and running viperROM.... SWWWWWET!
HBOOT 1.5 and s-on is a *****!
Not to mention... But in Linux, I never got revo recovery to flash... You can do it in windows just do it via fastboot.
Took my Orig cwm bsckup "recovery" & "boot" .img and threw them @ the phone via command prompt.
After cwm was restored, I restored my 4\29\2012 backup that I made before I entered the Sprint store, now my phone is back to the exact same way
It was. Pretty Damn sweet!
So much info here!! I'm truly thankful!!!
Sent from my PG86100 using xda premium
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 **
Verizon ran a special last night, LG G2 for free. I have been pining over this phone since getting one in my hands in the store, was just impressed. My Rezound has been the longest phone I've owned, but it's time is done. Late Nov 2011 until now.......an impressive stretch. But it's developed some issues recently that make me believe it's a goner. So the new white G2 is ordered and will be picked up tomorrow.
As for my rezound......if anyone is reading this......here's the issues it's developed, mainly after a particularly hard fall about two weeks ago. It was initially fine, but about 3-4 days later, it started boot looping out of nowhere. If I replace the battery it's hit or miss if it does it or not now. If it does, it could be 1-2 times, it could take over 10 minutes to get into the OS. Then in my car last week, I turned on Bluetooth (Chrysler Pacifica, has that Uconnect through the stereo) but it never fully turned on. Then two days ago the wifi quit picking up ANYTHING even though it says it's on. Now I notice the speaker (both headset and external) have gone very crackly.
I'm doubting it's software related, I think it's just been dropped one too many times. I'm going to try to reflash a stock kernel and factory ruu to set it back to stock (it's S-On, unlocked bootloader) and see how things work, but what are your guys opinion on whether or not that's worth my time?
Fastbird said:
Verizon ran a special last night, LG G2 for free. I have been pining over this phone since getting one in my hands in the store, was just impressed. My Rezound has been the longest phone I've owned, but it's time is done. Late Nov 2011 until now.......an impressive stretch. But it's developed some issues recently that make me believe it's a goner. So the new white G2 is ordered and will be picked up tomorrow.
As for my rezound......if anyone is reading this......here's the issues it's developed, mainly after a particularly hard fall about two weeks ago. It was initially fine, but about 3-4 days later, it started boot looping out of nowhere. If I replace the battery it's hit or miss if it does it or not now. If it does, it could be 1-2 times, it could take over 10 minutes to get into the OS. Then in my car last week, I turned on Bluetooth (Chrysler Pacifica, has that Uconnect through the stereo) but it never fully turned on. Then two days ago the wifi quit picking up ANYTHING even though it says it's on. Now I notice the speaker (both headset and external) have gone very crackly.
I'm doubting it's software related, I think it's just been dropped one too many times. I'm going to try to reflash a stock kernel and factory ruu to set it back to stock (it's S-On, unlocked bootloader) and see how things work, but what are your guys opinion on whether or not that's worth my time?
Click to expand...
Click to collapse
Are they discounting the full price on it too? I need to keep my unlimited.
As for the phone, what would you intend to do with it? They aren't worth much to sell, specially if it's damaged, if the screen is good, someone might take it off your hands for parts.
mjones73 said:
Are they discounting the full price on it too? I need to keep my unlimited.
As for the phone, what would you intend to do with it? They aren't worth much to sell, specially if it's damaged, if the screen is good, someone might take it off your hands for parts.
Click to expand...
Click to collapse
I don't know yet. I think I've still got my OG Droid hiding somewhere too.
I'm going to wipe it all and do a full factory ruu reflash and see if that doesn't help things out. I want to swap the outer bezel out because I closed my toolbox on it and ended up with a nice dent in the black chrome bezel. The LCD is fine, but I don't know about the digitizer considering the soft keys are really REALLY slow to respond anymore. I was thinking of rebuilding it for the fun and then I don't know. By rebuild I mean new circuit board because I think mine is the root of the issue. Won't know until after a factory reset, but the crackly speakers doesn't give me high hopes.
I really loved this phone. My biggest complaint was always the horrendous battery life. I have three batteries and could easily kill them all in a day with it. Guess I'm not done tinkering with it yet.
Hmmm.....looks like it may be getting sold for parts. It was bootlooping again tonight after I deactivated it and officially went full time to the G2. So I went into recovery (Amon Ra) and wiped everything, and did a recovery of a backup of Clean Rom that I'd done immediately after in install and setup back in July of 2012. And it's still boot looping. I get into the phone for just a few seconds, the SD card stuff tried to load, but neither Wifi or Bluetooth turn on. My guess is that the last couple of hard drops it took did the mainboard in. Good news is that I just pulled the Zagg InvisibleShield and the screen itself is freaking immaculate.
So I'm thinking one of two things. I could invest about $70 for a mainboard and a new outer bezel, see if that fixes it, and keep it as a spare phone. Or, just sell it as parts. I'm leaning towards a mainboard and bezel and just holding on to it, but I gotta say that I need to know if this is truly a mainboard issue or not.
Fastbird said:
Hmmm.....looks like it may be getting sold for parts. It was bootlooping again tonight after I deactivated it and officially went full time to the G2. So I went into recovery (Amon Ra) and wiped everything, and did a recovery of a backup of Clean Rom that I'd done immediately after in install and setup back in July of 2012. And it's still boot looping. I get into the phone for just a few seconds, the SD card stuff tried to load, but neither Wifi or Bluetooth turn on. My guess is that the last couple of hard drops it took did the mainboard in. Good news is that I just pulled the Zagg InvisibleShield and the screen itself is freaking immaculate.
So I'm thinking one of two things. I could invest about $70 for a mainboard and a new outer bezel, see if that fixes it, and keep it as a spare phone. Or, just sell it as parts. I'm leaning towards a mainboard and bezel and just holding on to it, but I gotta say that I need to know if this is truly a mainboard issue or not.
Click to expand...
Click to collapse
if after a full clean flash or even full factory restore you still have issues id lean towards hardware issues myself...and i hear you on battery life...i too have 3 batteries and the phone will die by the end of the day with it....i sold my daily rez for a different android but i still have my developer rez...which has been lately used for just that
I also just retire the rebound for similar reasons. I went with the note 3. Just picked it up yesterday. I was going to get the moto x to keep unlimited but was able to keep it with the N3.
I liking it so far. Not reboots or freezes. I think that is what finally got me. For the last few months, I could not get the red to run smoothly on any roms dating back to bean stock and maybe before. Gummy had worked great but for blacks screens that also happen on kitkat. I'm still keeping the red for roms as I am not going to root the N3.
Sent from my SM-N900V using Tapatalk
REV3NT3CH said:
if after a full clean flash or even full factory restore you still have issues id lean towards hardware issues myself...and i hear you on battery life...i too have 3 batteries and the phone will die by the end of the day with it....i sold my daily rez for a different android but i still have my developer rez...which has been lately used for just that
Click to expand...
Click to collapse
Yeah, the nandroid restore I did was, I think, CleanRom 1.4. But it was a totally clean install as I had installed it, set it up, and backed it up immediately. And it still just boots, gets into the UI, and about 30 seconds later reboots. I can't even get USB Debugging disabled so I can use Fastboot to relock the bootloader and flash an RUU.
I guess once my taxes come back in that I'll get a new logic board since ALL the modules seem to come with it (wifi, BT, etc) and get a new centerboard/outer bezel combo. Cost me about $70, but if I can get it up and running it'll be a nice backup phone. If anything, something to tinker with, lol.
Holy crap. I left it sit all night, and just turned it on and it booted! However, I try to turn Wifi on, and it just sits at "Turning Wi-Fi on......" so looks like wifi is definitely buggered. As it bluetooth.....same thing.
Just went into Settings and under Wi-Fi is says Error. Yep.....that's fubar.
It's SlimRom 1.6, just checked.
But the good news is that I now have USB Debugging enabled, so I can use Fastboot and relock and put a factory RUU on it. One last try, lol.
Fastbird, I had bought a used Rezound for my daughter over Christmas and when we tried it the wifi said the same thing as you stated, "turning on wifi". It would stay like that forever. I then went and put on ViperRez rom and then the wifi was fine. Not saying this will work for you as well but just a thought I had when I saw your problem. Good luck, hope it all works out for you.
Bryon
Fastbird said:
Yeah, the nandroid restore I did was, I think, CleanRom 1.4. But it was a totally clean install as I had installed it, set it up, and backed it up immediately. And it still just boots, gets into the UI, and about 30 seconds later reboots. I can't even get USB Debugging disabled so I can use Fastboot to relock the bootloader and flash an RUU.
I guess once my taxes come back in that I'll get a new logic board since ALL the modules seem to come with it (wifi, BT, etc) and get a new centerboard/outer bezel combo. Cost me about $70, but if I can get it up and running it'll be a nice backup phone. If anything, something to tinker with, lol.
Click to expand...
Click to collapse
you dont need to worry about usb debugging for an ruu....just boot to hboot and select fastboot and plug it in.....in my downgrade upgrade guide it will show all you need to do....the only thing you have to worry about with that is gaining s-off...an ruu wipes and reinstalls android completely...so any setting you set in rom will be wiped anyway....if wifi and all that still fails than it shows that the CleanRom is your issue....although downgrading and using the ruu.exe files require a locked bootloader and to be s-off
Also, the "turning WiFi on" issue, if it just stays like that, is usually an issue of a kernel/module mismatch... Remember when flashing a ROM or restoring a Nandroid when S-On you must flash the boot.img manually.
Sent from my Nexus 4 using Tapatalk
REV3NT3CH said:
you dont need to worry about usb debugging for an ruu....just boot to hboot and select fastboot and plug it in.....in my downgrade upgrade guide it will show all you need to do....the only thing you have to worry about with that is gaining s-off...an ruu wipes and reinstalls android completely...so any setting you set in rom will be wiped anyway....if wifi and all that still fails than it shows that the CleanRom is your issue....although downgrading and using the ruu.exe files require a locked bootloader and to be s-off
Click to expand...
Click to collapse
Now....I thought you had to be S-ON to run the RUU file? That crap-can's that idea then. I'm not S-Off. CleanRom isn't the issue. I ran a later version of it for 1.5 years, and the version I tried the restore from was 100% functional for me too. I don't think I'm going to bother flashing the phone as it sits because of the hardware issues. I'm just going to wait until I get a new logic board and then probably S-Off and play with flashing until I find something I like to sit on as a backup. The Screen is just too pretty for me to part with, lol.
Fastbird said:
Now....I thought you had to be S-ON to run the RUU file? That crap-can's that idea then. I'm not S-Off. CleanRom isn't the issue. I ran a later version of it for 1.5 years, and the version I tried the restore from was 100% functional for me too. I don't think I'm going to bother flashing the phone as it sits because of the hardware issues. I'm just going to wait until I get a new logic board and then probably S-Off and play with flashing until I find something I like to sit on as a backup. The Screen is just too pretty for me to part with, lol.
Click to expand...
Click to collapse
all ruu.exe files and ota.zips require s-off for downgrading..... ie. say your on an older version like 3.14.605.12 you can be s-on and upgrade to higher if im not mistaken...going s-off and redoing the whole phone from first to finish on ruu and ota's would be your last chance for that board without having to spend cash....and no offense you can probably get a used perfectly working rezound alot cheaper than 70 as well...is there any chance you deleted the wrong system files....only factory ruu will it restore original files...some deletions can cause these issues as well
The getting stuck turning Wifi on started BEFORE I tried a restore.
Shouldn't be a kernel mismatch because I used the same kernel for the nandroid CleamRom 1.6 and the other version of CleanRom I was running (I believe 1.7).
Only wiped Data, Cache, and dalvik cache. Several times for each.
The phone is acting EXACTLY like it was prior to the nandroid restore which is why I'm so sure it's a hardware issue. And I do mean exactly. 85% of the time after rebooting it boot loops for a random amount of time. Once booted in it's fine, save for Wifi and Bluetooth not working.
I understand I could get a replacement phone for cheaper to slightly more than te $70, but that's not the point. I like to tinker. I learn by doing. Gives me something to do.
Ok, relocked and trying to upgrade to a higher RUU which by what I read is acceptable. I flashed one of the earliest ICS firmware's and rom's, and the last RUU I could find was about 3 months later so I'm hoping it's good.f
*Edit* RUU took, trying to boot, but it's boot looping like normal. I think it's safe to say hardware is jacked at this point. It's getting into the UI then dying again, just like before.
Nappyloxs said:
I also just retire the rebound for similar reasons. I went with the note 3. Just picked it up yesterday. I was going to get the moto x to keep unlimited but was able to keep it with the N3.
Click to expand...
Click to collapse
How were you able to keep unlimited? My contract is over with my Rezound and I want to purchase a Galaxy S4. The best Verizon would offer me to give up my unlimited data is 6gb of data for $30.
Sent from my ASUS Transformer Pad TF700T using XDA Premium 4 mobile app