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.
Related
I'm hoping someone can help me, and I may need led thru steps.
I came from an x2, which I had managed to root, install recovery, and flashed and changed several ROMs, all successfully.
On my rezound however, I'm kinda stuck. I unlocked it, using the htc instructions and links, and rooted using zerg. I apparently don't have, and never have had recovery. Originally I just couldn't go any farther as far as gaining recovery or flashing roms, would get an error message and it would go to reboot. I don't know what I did 2 nights ago, but how whatever I do from the boot screen, I get an immediate haptic response, and it goes right to the white htc screen, where it is locked until I pull the battery. I've even tried to do factory resets, and it asks the prompt questions, but eventually it just reboots to the locked htc screen, until I pull the battery. Then it will reboot normally, but nothing was wiped.
I'm not totally inept, on the phone or the computer, but I'm definitely still a noob, but I really want to learn this stuff, the customization possibilities are the main reason I got the rezound.
I would appreciate some patient assistance from some of you knowledgeable folks!
Thanks in advance! Scott
Try using scott's cleanflash tool. It will flash recovery for you. It will also flash the boot.img (kernel) when you flash a custom ROM.
Sounds like you have fastboot checked in the settings.
If you really want to learn more about flashing, do yourself a huge favor and read up on ADB and fastboot. There's a few really good guides on them you can find by searching the forums, and knowing the basic commands will save you quite a bit of hassle vs. constantly doing battery pulls.
update..getting worse
thanks to the 3 of u who tried to help so far, i have tried some of your advice, but now my phone is basically non-functional, with constant reboots. it wont even allow me to do a hard reset. i tried it thru settings, when i could access them, and thru the "battery pull and buttons method". it confirms the reset, and goes thru the motions, but when i reboot it...everything is the same...including my problem. i need a functioning phone, does anyone know how i can go about putting my x2 back into service?
i know a lot of people on here probably figure i'm getting what i deserve, but if it comes down to it i will run over it with my car and get an insurance replacement. i really want to learn how to do this stuff, but without the background or any help, maybe i AM too "stoopid" Thanks Scott
Are you able to connect to your pc with it so you can use adb or RUU?
Not that I'm going to be the one with the answer to your problems, but maybe you can post exactly what you did that got you messed up in the first place because your post is a little confusing and it would help people who really know this stuff figure out what happened and how to fix it. Looks like you rooted and then did you ever flash a recovery?
ifyou would like hell free to shoot me your gtalk if you have one and I'll gladly help you out, got no plans tonight so I can help at whatever point you see this that also goes for anybody else having issues!
Sent from my sexy otterboxed ADR6425LVW using Tapatalk
i appreciate it!
pwnwolf117 said:
ifyou would like hell free to shoot me your gtalk if you have one and I'll gladly help you out, got no plans tonight so I can help at whatever point you see this that also goes for anybody else having issues!
Sent from my sexy otterboxed ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Ty wolf...and I very likely will take you up on your kind offer very soon! I was away all afternoon and evening today.
I did get out of the bootlooping mess I had earlier, I found a related post on droid forums, posted by malkavian under the title "continuous rebooting". The fix involved removing the sim card and typing in a code, and it fixed my most pressing problem.
I still have big problems though, I can't do anything from the boot/recovery screen, it goes right to the white htc screen and locks until I pull the battery. Also, I have tried several times to do hard resets, and those don't work either. I hope to talk to you soon...and thanks in advance! Scott
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
What's the likely hood that there will be a method for getting S-OFF without doing the wire trick in the somewhat near future? I really want to S-OFF but sticking wires into the back of my phone seems a little sketchy. I know that it would be hard to screw it up but still. Is it worth just biting the bullet and doing the wire trick or should I tough it out until there's another method?
magicnanners said:
What's the likely hood that there will be a method for getting S-OFF without doing the wire trick in the somewhat near future? I really want to S-OFF but sticking wires into the back of my phone seems a little sketchy. I know that it would be hard to screw it up but still. Is it worth just biting the bullet and doing the wire trick or should I tough it out until there's another method?
Click to expand...
Click to collapse
Just do it, it takes like 10min
It's doesn't hurt anything to do it, I've done it to 3 phones now with no Ill effects besides a sd card that needed to be reformatted
Now it can be tricky and a pain in the ass to do if you don't do it right but if you do get into a snag you could pm charliestheman or me and we will help you through it
Sent from my ADR6425LVW using Tapatalk 2
I finally s-off'd yesterday and I'm kinda disappointed I didn't do it earlier!!
It sounds way more intimidating than it really is. And honestly I'm not sure if a lot of people just can't read or what but as long as you follow the directions you'll be A-O.K.
Sent from my ADR6425LVW using Tapatalk 2
Alright I think I'll try it tomorrow, hopefully my parents leave because if they see me shoving a wire in the back of my phone they'll flip XD. And before anyone asks yes I live at home but that's only because I'm 16 and no I promise I'm not the stereotypical douche teenager. I am really ashamed of my generation, I go to school with some of the biggest idiots I've ever know. I know this isn't really XDA related but I always feel like I have to defend myself whenever I mention I'm in highschool.
s-0ff
Seriously, you'll be fine. Follow JBear's instructions to the "T",
do it in a well-lit place with no distractions, and touch ONLY the metal
contacts indicated. Takes 10 minutes....
magicnanners said:
Alright I think I'll try it tomorrow, hopefully my parents leave because if they see me shoving a wire in the back of my phone they'll flip XD. And before anyone asks yes I live at home but that's only because I'm 16 and no I promise I'm not the stereotypical douche teenager. I am really ashamed of my generation, I go to school with some of the biggest idiots I've ever know. I know this isn't really XDA related but I always feel like I have to defend myself whenever I mention I'm in highschool.
Click to expand...
Click to collapse
i know what you mean. im 15 and most people assume i know nothing about this stuff which is totally wrong.
Anyway the wire trick is pretty easy it just takes a few tries and its definitely worth it if you like to switch between GB and ICS nandroids like me
Before you start. I suggest doing a nandroid, transferring it to your PC, and make sure fastboot/adb works properly.
it's nothing you don't even have to unscrew anything.
magicnanners said:
Alright I think I'll try it tomorrow, hopefully my parents leave because if they see me shoving a wire in the back of my phone they'll flip XD. And before anyone asks yes I live at home but that's only because I'm 16 and no I promise I'm not the stereotypical douche teenager. I am really ashamed of my generation, I go to school with some of the biggest idiots I've ever know. I know this isn't really XDA related but I always feel like I have to defend myself whenever I mention I'm in highschool.
Click to expand...
Click to collapse
I am 67 yesterday i soffed and loaded the ics leak in about 20 min
Sent from my SCH-I905 using xda premium
Snuzzo said:
Before you start. I suggest doing a nandroid, transferring it to your PC, and make sure fastboot/adb works properly.
Click to expand...
Click to collapse
This is probably a dumb question. I'm itching to s off too, but a little scared. How do I make sure fastboot and adb works?
putney1477 said:
This is probably a dumb question. I'm itching to s off too, but a little scared. How do I make sure fastboot and adb works?
Click to expand...
Click to collapse
Just try adb devices and see if it spits out a serial number.
Po1soNNN said:
i know what you mean. im 15 and most people assume i know nothing about this stuff which is totally wrong.
Anyway the wire trick is pretty easy it just takes a few tries and its definitely worth it if you like to switch between GB and ICS nandroids like me
Click to expand...
Click to collapse
Yeah my problem is I don't know much about this stuff this is my first smartphone and I'm learning as I go, luckily I have a friend at school who's a total android guru who I go to before I bug you guy's XD. But I just want to thank all of you for your help I most likely will try to S-OFF tomorrow since it's getting late and I need my phone to work tonight and tomorrow morning. Again thanks you guys
Sent from my ADR6425LVW using XDA
magicnanners said:
What's the likely hood that there will be a method for getting S-OFF without doing the wire trick in the somewhat near future? I really want to S-OFF but sticking wires into the back of my phone seems a little sketchy. I know that it would be hard to screw it up but still. Is it worth just biting the bullet and doing the wire trick or should I tough it out until there's another method?
Click to expand...
Click to collapse
Seriously man just make sure you hit the right connectors and you will be fine it ain't hard and worse case scenario it bricks and you get a new one. It's easy man trust me.
Sent from my ADR6425LVW using XDA
recovery from failed s-off attempt
prior to attempting, I did a full nandroid backup with amonra recovery.
switched cards and ran the setup, it looked like all was working
but wire trick didn't for me. going to try again, with stiffer wire.
after battery pull, I rebooted to hboot fastboot and restored
the amon ra recovery with fastboot. I can reboot to amon ra now.
I tried normal boot and that failed to run. I thought the controlbear was
putting part software was part of itself in recovery, should it have written
on the real OS partitions?
hboot says unlocked, s-on, hboot-2.10.000
restore of the amon ra leaves me with juopunutbear in green in center of
screen on normal boot.
how do I recover?
the card contains boot.img, cache.img, data.img, recovery.img, system.img
do I need to fastboot flash parts of it? I'm unsure what it did?
fuzzynco said:
how do I recover?
Click to expand...
Click to collapse
After re-flashing Amon RA, use con's Nandroid helper or pull boot.img and "fastboot flash boot boot.mg" in hboot, in conjunction with a restore without the helper zip.
EDIT:
Once you gain s-off with the utility you won't need to do the above steps, as you will then be able to restore your boot.img without the assistance of either.
[Solved] Thanks... where can find the utility?
nandroid helper
So I need to boot to hboot / fastboot
then fastboot flash boot boot.img,
then restore the rest with amon ra?
Or were they already restored and just boot.img
needs manual loading?
next time I'll know to fastboot flash the boot.img
I guess that's due to s-on recovery can't restore
itself and boot?
==> resolved. Everything is back up from the backup.
fuzzynco said:
Or were they already restored and just boot.img
needs manual loading?
Click to expand...
Click to collapse
Already there. You can't restore a boot.img in recovery "natively" with s-on.
I was wondering about doing a backup, maybe somebody can point me in the right direction. I am on the ICS leak from a month or so ago. Everything works, so I don't even know why I'm thinking about this, but anyway, I'd like to do s-off because I love flashing different roms. My problem is I have a few apps that I use a lot, but they generate their own ID so to speak. They don't use a login and if I lose the data I already have, all my contacts on the apps are toast. I assume that the data for those apps must reside in the phone somewhere, but, I have no idea where, and I really would be hating life if I lost it.
/rant
App makers, please let us use email/password to effing identify ourselves instead of some randomly generated crap!
/end rant
So I guess the utility
makes the boot.img into an PH98IMG.zip for hboot to process?
Something like the ROM kernel modules are done?
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!