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?
Related
Some people might want to get rid of the modified bootloader after running the revolutionary beta to get s-off. It is pretty easy.
Also if you run a RUU you will need to run this to get proper s-off.
1. Get s-off
1a. I recommend not useing clockwork mod and instead installing TeamWin Recovery Project2 .Download the eng bootloader and put it in the root of your sd-card
Link-> PG86IMG_eng-hboot.zip
Rename it to be PG86IMG.zip3. Disable quickboot in system power settings
Shutdown the phone, hold down the volume down button and hit the power/hold button4. Once in the bootloader hitting volume up will ask if you want to update, hit volume up again to accept and then reboot.5. Remove or rename the PG86IMG.zip in order to get into the bootloader again, as it will always try to apply the update.
ionstorm66 said:
Some people might want to get rid of the modified bootloader after running the revolutionary beta to get s-off. It is pretty easy.
1. Get s-off
1a. I recommend not useing clockwork mod and instead installing TeamWin Recovery Project2.Download the eng bootloader and put it in the root of your sd-card
Link-> PG86IMG_eng-hboot.zip
Rename it to be PG86IMG.zip
Click to expand...
Click to collapse
Whats the difference? Mine says eMMC H.Boot
The eng bootloader has s-off stock, and has more fastboot options. It also removes anything that revolutionary did in the bootloader to get s-off.
knowledge561 said:
Whats the difference? Mine says eMMC H.Boot
Click to expand...
Click to collapse
Thanks. I would have never known.
ionstorm66 said:
1. Get s-off
1a. I recommend not useing clockwork mod and instead installing TeamWin Recovery Project
Click to expand...
Click to collapse
When people make recommendations like this, I have to question why? Does CWM brick phones if you use this method? Is there a performance issue when trying this?
Not to be an ass or anything but you have 2 total post in 2 months. Please elaborate this recommendation before you have hundreds of thousands of people following your recommendation. Personal experiences as well as any confirmed bugs that others have experienced would be good.
I think that is more for Devs
Sent from my PG86100 using XDA Premium App
unknown_owner said:
When people make recommendations like this, I have to question why? Does CWM brick phones if you use this method? Is there a performance issue when trying this?
Not to be an ass or anything but you have 2 total post in 2 months. Please elaborate this recommendation before you have hundreds of thousands of people following your recommendation. Personal experiences as well as any confirmed bugs that others have experienced would be good.
Click to expand...
Click to collapse
If you have some basic knowledge and have used revolutionary you would know why he suggested it, so maybe you should read more and he can elaborate less? BTW his instructions are perfect.
TimidRat said:
If you have some basic knowledge and have used revolutionary you would know why he suggested it, so maybe you should read more and he can elaborate less? BTW his instructions are perfect.
Click to expand...
Click to collapse
Agreed
Locked & Loaded
unknown_owner said:
When people make recommendations like this, I have to question why? Does CWM brick phones if you use this method? Is there a performance issue when trying this?
Not to be an ass or anything but you have 2 total post in 2 months. Please elaborate this recommendation before you have hundreds of thousands of people following your recommendation. Personal experiences as well as any confirmed bugs that others have experienced would be good.
Click to expand...
Click to collapse
plus one dude sounded like a strait ****
ion thanks bro **** worked like a charm now im clean!!!!!!!!!!!!!!!!!!!!!
worked perfectly for me... thx OP
Worked awesome! Loving the look and being able to say I have the engineering bootloader, thanks OP.
hey +1 on the thanks, easy to do and kool eng boott
You know what f**k it, i'm not going to get into any internet wars for something that is not mine but never said anythuing was wrong with revolutionary, let's get that straight. I have used CWM for evolution, epic, e3d, and Asus TF. Never had anything go wrong. So if some says not to use it, I'd like to know if I need to seek an alternative for each device. No I'm not going to search/read any he said she said post on the internet to find an answer. If the answer has to do with people and not the actual programs themselves, then the recommendation is mute.
Thanks on the steps btw
And to clarify, revolutionary is the only method to get s-off right now. There are 2 recoveries available after the s-off: CWM and TWRP.
EEE Pad Transformer sent this
Also Sprint can't tell if your EVO is a dev unit or not because It's an official eng bootloader from HTC.
Sent from my PG86100 using XDA App
kpkimmel said:
Also Sprint can't tell if your EVO is a dev unit or not because It's an official eng bootloader from HTC.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Are you saying that Sprint can somehow poll our devices and deduce what bootloader is installed? Or do you mean a Sprint rep with hands-on access? If the latter, I'm fairly certain they would suspect something was up when they saw S-OFF and the ENG bootloader. Either one would be a sure sign that the phone was something other than stock.
unknown_owner said:
You know what f**k it, i'm not going to get into any internet wars for something that is not mine but never said anythuing was wrong with revolutionary, let's get that straight. I have used CWM for evolution, epic, e3d, and Asus TF. Never had anything go wrong. So if some says not to use it, I'd like to know if I need to seek an alternative for each device. No I'm not going to search/read any he said she said post on the internet to find an answer. If the answer has to do with people and not the actual programs themselves, then the recommendation is mute.
Thanks on the steps btw
And to clarify, revolutionary is the only method to get s-off right now. There are 2 recoveries available after the s-off: CWM and TWRP.
EEE Pad Transformer sent this
Click to expand...
Click to collapse
Well, most of us who got our E4G on release day and rooted immediately didn't like early versions of CWM because it wouldn't wipe properly or completely sometimes (giving rise to ridiculous multi-wipe scripts). That and all the associated wonkyness that would follow could be eliminated before it began by simply using Amon Ra and avoiding CWM like the plague...
...even though I've used CWM successfully on devices that have no Amon Ra given our collective early experiences with it (and absolute lack of problems with stable versions of Amon Ra) on the E4G we never used anything but Amon Ra and never had any problems....but we did with CWM at one point.
That's likely why he said it and is why you hear that a lot still. Lots of us E4G guys jumped to E3D immediately. Even though CWM fixed that problem I hear we wouldn't know, we used Amon Ra with nary a problem.
erikivy said:
Are you saying that Sprint can somehow poll our devices and deduce what bootloader is installed? Or do you mean a Sprint rep with hands-on access? If the latter, I'm fairly certain they would suspect something was up when they saw S-OFF and the ENG bootloader. Either one would be a sure sign that the phone was something other than stock.
Click to expand...
Click to collapse
A handful of them shipped S-OFF and some of those were probably eng hboots...that and it doesn't say "REVOLUTIONARY" in bright pink at the top...that's a definite giveaway.
If you're going to repost something you could at least link back to where you took everything from...
daneurysm said:
A handful of them shipped S-OFF and some of those were probably eng hboots...that and it doesn't say "REVOLUTIONARY" in bright pink at the top...that's a definite giveaway.
Click to expand...
Click to collapse
I forgot about the Revo branding at the top. And I didn't know any shipped s-off. I thought those were Sensations. Regardless, I happy we finally got what we've been waiting for.
Now I want to start from scratch again. I would like to root and use a cleanrom.
I know how to do all this. However, what exactly do I need to delete from my computer? I still have all the files on here from the last time I rooted my rezound. But I want to start completely from scratch.
Thanks is advance
first, go to htc dev.com and unlock the device.
then download amon ra recovery and install
through cmd or cleanflash 1.0 tool from scott.
after installing, get su from advanced menu in recovery.
now you've been unlocked and rooted.
download the rom and kernel you want to install
then install using recovery.
Disagree. First test the speaker and telephone call quality. Then do some downloading or program updates and make sure the phone does not get too hot. Once you are sure you didn't get a lemon, then decide if you want to void the warranty.
Sent from my ADR6425LVW using xda premium
jdmba said:
Disagree. First test the speaker and telephone call quality. Then do some downloading or program updates and make sure the phone does not get too hot. Once you are sure you didn't get a lemon, then decide if you want to void the warranty.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
yeah i'm on my 2nd replacement so far. i make sure to give phones at least a week of standard usage before i decide to unlock/root.
I found that alot of the phones have poor speakers/overheat or have dead pixels :x.
jdmba said:
Disagree. First test the speaker and telephone call quality. Then do some downloading or program updates and make sure the phone does not get too hot. Once you are sure you didn't get a lemon, then decide if you want to void the warranty.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
the question was how to get cleanrom on the phone..
read before writing..
don't you think testing the phone has been done already?
qudwis said:
the question was how to get cleanrom on the phone..
read before writing..
don't you think testing the phone has been done already?
Click to expand...
Click to collapse
Verizon doesn't really check their phones. There are a ton of POS phones sent out as refurbs/CLNR.
qudwis said:
the question was how to get cleanrom on the phone..
read before writing..
don't you think testing the phone has been done already?
Click to expand...
Click to collapse
Nope, he didn't say you were wrong by the way. Just trying to make sure someone who might be excited about the new phone tests out the phone first. Great logic, so don't get offended.
KORM via the beast known as the Rezound.
putney1477 said:
Now I want to start from scratch again. I would like to root and use a cleanrom.
I know how to do all this. However, what exactly do I need to delete from my computer? I still have all the files on here from the last time I rooted my rezound. But I want to start completely from scratch.
Thanks is advance
Click to expand...
Click to collapse
qudwis said:
the question was how to get cleanrom on the phone..
read before writing..
Click to expand...
Click to collapse
No, that was not the question. Take your own "advice". I quoted the original question as well to make it easy for you.
txkorm said:
Nope, he didn't say you were wrong by the way.
Click to expand...
Click to collapse
Even though s/he was wrong. But I said it so we're covered. lol.
Back to the question, which was ...what exactly do I need to delete from my computer?
I would probably not use the nands from your old set up on your new phone. I don't know if there's a way to access files in them other than from restoring them, but if there isn't I'd say get rid of them.
Also, you don't want to restore data from a Titanium backup if it's to a different ROM, don't know if it matters if it's to a different phone. So you can definitely use them to restore apps but might want to not restore data in case it causes any issues.
You'll need to get a new unlock code so you can delete that unlock_code.bin file you got last time.
Not sure what else you would have on there that you are wondering about. The folder you set up for using fastboot/adb can stay and be used again.
feralicious said:
No, that was not the question. Take your own "advice". I quoted the original question as well to make it easy for you.
Even though s/he was wrong. But I said it so we're covered. lol.
Back to the question, which was ...what exactly do I need to delete from my computer?
I would probably not use the nands from your old set up on your new phone. I don't know if there's a way to access files in them other than from restoring them, but if there isn't I'd say get rid of them.
Also, you don't want to restore data from a Titanium backup if it's to a different ROM, don't know if it matters if it's to a different phone. So you can definitely use them to restore apps but might want to not restore data in case it causes any issues.
You'll need to get a new unlock code so you can delete that unlock_code.bin file you got last time.
Not sure what else you would have on there that you are wondering about. The folder you set up for using fastboot/adb can stay and be used again.
Click to expand...
Click to collapse
Thank you all for your help. I have tested the phone for a week now. Seems to be ok.
that was my question, about the adb and fasboot etc that's already on my computer.
I have no idea on my computer where my old unlock code is haha. Im.sure I will find it.
I can use the same drivers correct?
Thanks afaik for everyone's help. I appreciate it.
Sent from my ADR6425LVW using Tapatalk
You do realize that even if you "void" your warranty, its easy to still return it for a replacement. Just put in the stock ROM and stock recovery and re-lock and you're good to go. You don't even need to re-lock, Verizon doesn't check.
engsoccerfan said:
You do realize that even if you "void" your warranty, its easy to still return it for a replacement. Just put in the stock ROM and stock recovery and re-lock and you're good to go. You don't even need to re-lock, Verizon doesn't check.
Click to expand...
Click to collapse
She's already done that, believe me... we went through it together. lol.
putney... you can keep all the drivers and the whole fastboot/adb folder you have set up. That's just for your computer and not phone specific. Well, the drivers are HTC but you got the same phone so you're set.
No big deal on the Unlock_code.bin. If you end up with the old one and it doesn't work you can always generate a new one any time from what I've heard. I just keep mine in the fastboot/adb folder so it's always available. I also do that with Amon Ra. Then I don't have to go looking for them.
feralicious said:
She's already done that, believe me... we went through it together. lol.
putney... you can keep all the drivers and the whole fastboot/adb folder you have set up. That's just for your computer and not phone specific. Well, the drivers are HTC but you got the same phone so you're set.
No big deal on the Unlock_code.bin. If you end up with the old one and it doesn't work you can always generate a new one any time from what I've heard. I just keep mine in the fastboot/adb folder so it's always available. I also do that with Amon Ra. Then I don't have to go looking for them.
Click to expand...
Click to collapse
Thanks so much, again lol. You are awesome!
Sent from my Kindle Fire using Tapatalk
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
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.
I just received a reconditioned rezound from Verizon's warranty department. I have 10 days with both (broken and reconditioned) phones. I want to root the new phone. I figure if I use a new SD card in the new phone and follow all of Nil's Business Sense instructions that should work. Then if I put in the old SD card I would have all of my settings and apps restored. I'm not sure if that really would work, that's why I am asking you guys & gals. I didn't have the guts to root the original phone, but now I am ready. Any help you can give would be greatly appreciated. Thank you!
Sad Noob said:
I just received a reconditioned rezound from Verizon's warranty department. I have 10 days with both (broken and reconditioned) phones. I want to root the new phone. I figure if I use a new SD card in the new phone and follow all of Nil's Business Sense instructions that should work. Then if I put in the old SD card I would have all of my settings and apps restored. I'm not sure if that really would work, that's why I am asking you guys & gals. I didn't have the guts to root the original phone, but now I am ready. Any help you can give would be greatly appreciated. Thank you!
Click to expand...
Click to collapse
SD card doesn't affect anything
Sent from my ADR6425LVW using xda app-developers app
As cslingerland stated, your SD card doesn't actually affect anything. You only use it to hold the roms and whatnot to install.
kirbfucius said:
As cslingerland stated, your SD card doesn't actually affect anything. You only use it to hold the roms and whatnot to install.
Click to expand...
Click to collapse
So if my SD card idea wont work, What is a good easy way to root my phone without bricking it. I thought my SD card idea was a good one, but I was off base it seems. Please help! :cyclops:
Easiest way to root the phone without bricking it? The same way everyone else does?
Unlocking Bootloader: http://forum.xda-developers.com/showthread.php?t=1415615
Root: http://forum.xda-developers.com/showpost.php?p=20776953&postcount=80
S-OFF: http://unlimited.io/juopunutbear.htm
Flash recovery: http://forum.xda-developers.com/showthread.php?t=1339679
Return to S-ON on whichever phone you're returning: http://forum.xda-developers.com/showthread.php?p=25167284#post25167284
Just a brief note that we're currently experiencing issues with the HTC Dev unlock. Their site isn't happy with us right now. Follow along here: http://forum.xda-developers.com/showthread.php?t=1475864&page=13
To root or not to root, that is the question
kirbfucius said:
Easiest way to root the phone without bricking it? The same way everyone else does?
Unlocking Bootloader: http://forum.xda-developers.com/showthread.php?t=1415615
Root: http://forum.xda-developers.com/showpost.php?p=20776953&postcount=80
S-OFF: http://unlimited.io/juopunutbear.htm
Flash recovery: http://forum.xda-developers.com/showthread.php?t=1339679
Return to S-ON on whichever phone you're returning: http://forum.xda-developers.com/showthread.php?p=25167284#post25167284
Just a brief note that we're currently experiencing issues with the HTC Dev unlock. Their site isn't happy with us right now. Follow along here: http://forum.xda-developers.com/showthread.php?t=1475864&page=13
Click to expand...
Click to collapse
You call that easy? you must be a M.I.T. graduate. I graduated from Nova South Eastern University, and let me tell you, It makes no sense to me. That's why I am asking for help!
Pro tip: If you don't S-OFF, you can't brick this phone. It's actually pretty much impossible to brick unless you S-OFF. You can "soft brick" it, but you can recover. Until you S-OFF, you don't have enough access to the important stuff to actually brick, and you can do everything even when you're S-ON...some of it takes a little more work, but if you're worried about bricking, it's safer to stay S-ON.
So, I recommend staying S-ON when you're starting out. It's a big time safety net.
Sad Noob said:
You call that easy? you must be a M.I.T. graduate. I graduated from Nova South Eastern University, and let me tell you, It makes no sense to me. That's why I am asking for help!
Click to expand...
Click to collapse
Which part are you having trouble with? Also, what is your ultimate goal with rooting? What are you wanting to do once rooted?
Sad Noob said:
You call that easy? you must be a M.I.T. graduate. I graduated from Nova South Eastern University, and let me tell you, It makes no sense to me. That's why I am asking for help!
Click to expand...
Click to collapse
I've helped a ton of people unlock and root their phones via teamviewer. I'm guessing that you're installing a new RUU to get the latest firmware. Or trying to s off because of the sdcard comment.
If you're having problems the sdcard that you normally use could just be copied to a folder on your computer and then use it like normal, for a regular root and unlock it shouldn't wipe your sdcard.
My gtalk is edit removed after 24 hours PM me if you need it
I'm A One Percenter... I did the wire trick
Amost ready to take the plunge
[/B]
CharliesTheMan said:
I've helped a ton of people unlock and root their phones via teamviewer. I'm guessing that you're installing a new RUU to get the latest firmware. Or trying to s off because of the sdcard comment.
If you're having problems the sdcard that you normally use could just be copied to a folder on your computer and then use it like normal, for a regular root and unlock it shouldn't wipe your sdcard.
My gtalk is edit removed after 24 hours PM me if you need it
I'm A One Percenter... I did the wire trick
Click to expand...
Click to collapse
I read a lot about the wire trick. Some people swear by it, others say it's a sure way to short out your phone. I've seen videos on You tube and the procedure looks pretty simple. I was nervous about voiding my warranty, but after just receiving my replacement (certified like new) Rezound, I think they just use the returned phone for parts for the next replacement, So wish me luck as I do the paper clip trick
One question... will my paid for apps live through the back-up to my sd card and back to the phone again
Sad Noob said:
[/B]
I read a lot about the wire trick. Some people swear by it, others say it's a sure way to short out your phone. I've seen videos on You tube and the procedure looks pretty simple. I was nervous about voiding my warranty, but after just receiving my replacement (certified like new) Rezound, I think they just use the returned phone for parts for the next replacement, So wish me luck as I do the paper clip trick
One question... will my paid for apps live through the back-up to my sd card and back to the phone again
Click to expand...
Click to collapse
If you bought them from Google play or have the apk then yeaa. Just back them up to your PC if you have the apk. And I really recommend you don't s-off.... Unless you know what you're doing. One wrong move after you s-off and you have a paper weight and not a phone any more.
cslingerland said:
If you bought them from Google play or have the apk then yeaa. Just back them up to your PC if you have the apk. And I really recommend you don't s-off.... Unless you know what you're doing. One wrong move after you s-off and you have a paper weight and not a phone any more.
Click to expand...
Click to collapse
I concur. And I'm glad you said that cslingerland. I've read so many posts from people saying "just s-off" to people who clearly aren't that well versed in all this stuff and I think that's bad advice.
I'm still s-on and I don't see a need for me to s-off since I rarely flash ROMs. I have know problem having to flash the kernel separately. And I've always liked using fastboot rather than the various tools and PH98IMG files since I like to know/be certain about what I'm doing and I don't want to end up with various PH98IMG files lying around not even knowing what they are. Turns out a lot of people don't know that a PH98IMG file can be anything, it's just a method to make things easier.
My take. If you don't plan on flashing a rom per day stay s on.
Sent from my ADR6425LVW using Xparent Green Tapatalk 2