yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] TheBr0ken:
when you s-off and do not load jb's hboot your bootloader will say "locked". Installing the juopunutbear hboot will display =Juopunutbear=. Doesnt matter what it says now, to go back to just "locked" for warranty here's what you need to do, and in this order or you could possibly brick! I'll explain after the steps, read

everything

first!

Run latest official RUU

1. to s-on first open a command window on your pc. plug in your phone,charge only mode, w/usb debugging on. type the commands as follows

2. adb devices (to make sure your pc can communicate with your device)

3. adb reboot bootloader

4. fastboot devices (to make sure your pc can communicate with your device in bootloader)

5. fastboot oem writesecureflag 3 (S-ON, If your bootloader says locked, skip to step 9 , if not go to step 6)

6. fastboot reboot bootloader

7. S-off again using the juopunutbear s-off method but do not install the custom hboot (changes your bootloader from relocked or tampered or whatever to just plain locked)

8. repeat step 5 to go back to s-on

9. fastboot reboot

10. Done

Now the warning. Doing the s-on procedure (step 5) while on a custom hboot like juopunutbear hboot or an Engineering hboot WILL brick your device, you could check out this thread (http://xdaforums.com/showthread.php?t=1833530) incase this happens, but I wouldn't chance it. If you dont know if you are on juopunutbear's hboot, ruu first, If you dont know if you are on an engineering hboot, ruu first. I guess what I'm trying to say is RUU FIRST!

note: the command fastboot oem lock also locks the bootloader, but then it will say relocked - Tampered. If you unlocked after you did the s-off procedure (really, really unnecessary) going back to s-on then going s-off again without loading juopunutbear hboot will do what fastboot oem lock does, but will now just say locked vs relocked - Tampered
[HTC Rezound] dashbored:
Hey bloodymurderlive, I think I might be your best "test subject" since I basically just went through the process using mostly your guides. I ended up using an insulated wire instead of paperclip because it turns out I could NOT find a coated paperclip around the house, but in my search found an old piece of wire that did the job haha

I was about to unlock my bootloader at my last post. I had just finished the S-off step and had a locked bootloader. I googled around and in the process found an interesting post using ph98img.zip for amon ra 3.15 to flash with locked bootloader. Sadly the link was dead. I eventually stumbled upon many of Scotty's old posts on the topic, and figured out how to make my own ph98img.zip, at least for amon ra purposes. So that actually worked for me. I currently have Amon ra 3.15 as my recovery on the locked bootloader with S-off. I know it's mostly a moot point (might be good for future references), but do you remember the error message from the failed flash attempt? I ran into similar problems in my trial and error, and I realized my text file accompanying the zip file was off.

So I have one follow up question to all this. At this point, the only reason to get s-on is for warranty purposes. I am just curious about that process... and also, if you wanted to get S-off again, do you just repeat the wire trick? Hopefully, this is just an academic question and will never be in use *knock on wood*

EDIT: I didn't see TheBr0ken's post - guess that answers my question!
[HTC Rezound] dashbored:
Appreciate the reply. I think I will make a nandroid backup asap.

Also, I can confirm that the latest update to wifi tether has a Rezound profile and it works great :)
[HTC Rezound] topgun1953:
Regarding comment #10.. AmonRA recovery should be flashed after taking the ics update AND it should be flashed using the ph98img.zip being flashed when booting into bootloader.

Bloody..I think it was you that couldn't flash amon without unlocking the bootloader....what exactly were you trying to flash and how. That was never disclosed to my knowledge. There are plenty of ph98img.zip links out there.

https://docs.google.com/open?id=0B28uLCcMCyfRZDZVOWNXbE90eWc is one of them. ctrl-s to download
[HTC Rezound] agapedisciple:
fyi ... here's what i found works if you end up in a bootloop

http://xdaforums.com/showthread.php?p=30543700#post30543700
[HTC Rezound] bloodymurderlive:
The first thing I tried was using the ph98img.zip from the bootloader. When that didn't work, I tried fastboot... which supposedly doesn't work after S-OFF without a custom bootloader. Anyway, that didn't work either.

Then somebody in the forums suggested that maybe I needed be unlocked. So I went through the unlock process again.

Then, I tried flashing ph98img.zip from the bootloader, again. Didn't work, again. Tried fast boot commands to flash it, again, but mysteriously... it worked!

Basically, it seems that my experience is one giant anomaly. I was definitely locked, S-OFF, stock hboot, and ICS when I first tried flashing ph98img.zip through the bootloader. Maybe it was the zip, but I used the same zip the entire time, and got it to work. :confused:

I guess since nobody else seems to have had the same experience as me, I should update my instructions... It's just that I didn't want to include instructions that didn't actually work for me. :eek:

---------- Post added at 03:07 PM ---------- Previous post was at 02:58 PM ----------

Here is more information on what happened during the process for me: http://xdaforums.com/showthread.php?t=1827263

The two conclusions from this discussion seemed to be that I had to either (a) unlock after s-off, or (b) flash jb hboot and use fastboot commands.

And yet, the solution for me was to use the command console to flash the zip... despite having stock hboot and s-off.
[HTC Rezound] topgun1953:
Thanks for the info. One more thing, if you still have the same ph98img.zip file, can you open it up and tell me what files are in it? If all you have is the one recovery name.img file, then it wouldn't have worked as a ph98img.zip file in bootloader.

You said you used the command console to flash the zip... Was this fastboot flash recovery (name of file).img ?

thanks..i'm trying to get an understanding what happened hmmm....were you getting a "main version error" way back when this started...I think you would have if you used the same GB zip with ICS...
[HTC Rezound] bloodymurderlive:
I'll have to wait until I'm home to play with the files and recap what specifically I did. I don't believe I got a "main version error" at any point.

I'll update once I can consolidate more info for you.
[HTC Rezound] scwtech:
Hi all, I'm curious if item #2 above has been figured out. I'd like to explain the details of my situation and I really hope the awesome rezound community can help me get this sorted. I've read literally hundreds of posts on no less than 6 sites, and I hope this is the right place to post my questions.

I have owned the eris, incredible 2, and recently bought a 'mint condition' rezound on ebay. physically, it's flawless and I'm happy with my purchase. it came with the OTA stock ICS (which means to me that it isn't really 'mint' and that it was likely used a little, enough to go through with the OTA update). I have successfully rooted and flashed custom roms to both my eris and inc2, and I'm eager to do the same with my rezound. I am a serious tinkerer and rather fearless when it comes to using the terminal (I'm on a mac) and I can follow instructions well.

But now I'm at a dead end. I have unlocked and relocked my rz using htcdev, and flashed amonra recovery, and am s-on. I'm running vigor360, which is nice, but I'd like to achieve s-off and get the rz to where the eris and inc2 were, which is that I can freely do nandroid backups and flash custom ROMs at will. I specifically want to run tonked, and try others.

here's the weird situation: it seems that my current rz did not require flashing a kernel after I flashed vigor360. here's the procedure I used to get to where I am now:

- stock ICS OTA, s-on

- relocked bootloader

- flash stock RUU from http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/

- unlock bootloader using htcdev

- flash amonra

- flash vigor360

- do NOT flash kernel

...and it runs fine. I'm still s-on and I want to be s-off. when I've tried other ROMs that require a kernel, they launch ok but freeze on the ROM boot screen. so, I try flashing the kernel and I get the dreaded 'main version is older' error. bottom line is, I need to be s-off.

what I've read about gaining s-off with the OTA ICS is that I must be rooted and have SU installed, and be running the stock RUU. I can get my rz to locked or unlocked, with the stock RUU, but I will likely not be rooted unless I can find a stock RUU that's got root built-in.

any advice will be hugely appreciated. if my research failed to uncover an existing post on this topic, please provide the link and I'll continue over there. Thanks!
[HTC Rezound] shrike1978:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip

Flash it in recovery and you're rooted.
[HTC Rezound] cwarnick726:
I'm more confused then ever, last weekend I tried this whole root procedure .

I'm on a stock ics rezound, don't think I had to update this one.

I used htcdev to unlock bootloader properly...

I believe the guide I followed had me flash a custom recovery image, and I believe I attempted to flash a stock recovery (Ruu?) Because I did not want to alter anything yet...

I have the developer options screen, but I tried installing Su/superuser and nothing...

Now my bootloader screen is s-on, unlocked, and tampered.

Idk what to do at this point. I want to be able to use wifitether and other root required apps

I have no need for custom roms, but I would think about getting rid of bloatware.

Can someone help me out?

I used my gfs windows vista laptop 64bit, after installing all theprereqs I needed like JRE and the other adb files

I own a ubuntu laptop, 12.04 64bit hp dv9000, would that be easier to use

Do I need s-off for this, or only root? Or is it the same thing?

---------- Post added at 03:15 PM ---------- Previous post was at 03:11 PM ----------

I've only used the adb fastboot thru command in the SDK folder I made with the phone apps. Sorry to sound like a newb but I want to learn and I've searched now every day since I started and spent 7 hours pulling up links and threads to try to solve this. I need lamens terms, not sure what flashing is exactly, so written out commands and links would be golden

I have installed a lot of updates and apps on my linux laptop thru terminal so I understand the procedures somewhat
[HTC Rezound] CharliesTheMan:
I can help you get it straightened out, if you want. Send me a PM and I'll send you my google talk username. I'll help you get it going. You're on the right track but we can make it easier.
[HTC Rezound] CharliesTheMan:
Just an update guys, cwarnick726 is good to go, we fixed the issues that he was having and got him all squared away with his precious new rezound.
[HTC Rezound] jtayag:
What is stock RUU?

I received the OTA update. I wanted to debloat so I unlocked and rooted and flashed SuperUser, SU, and AmonRa recovery and then installed zone23's ZoneROM Stock ODEX 8.16.12 v3. In its description, it is stock, ODEXed, and has RUU 3.14.605.12 built by Android Police. I'm looking at Settings > About Phone > Software Information and under Software Number, it reads 3.14.605.12 710RD.

Now I read that one of the prerequisites for running JuopunutBear's S-off is that I'm running a stock RUU and stock ROM. With everything I've done thus far, am I clear to attempt S-off? I haven't attempted anything else besides what I've mentioned above. Thanks!
[HTC Rezound] Snuzzo:
The prerequisites are for the exploit itself. I know that rom very well you should be ok to run it

Sent from my ADR6425LVW using Xparent Green Tapatalk 2
[HTC Rezound] jtayag:
"temporary brick" duration

Thanks, Snuzzo! According to the JuopunutBear program, I performed the wire trick successfully. Instructions say your phone becomes "temporarily bricked." Right now, my phone is sitting at the HTC boot screen, it's still plugged into my computer, and the back cover is still off. I haven't pushed any buttons or anything. Any idea how long the temporary brick state lasts? Can I reattach the back cover? Can I unplug it? The charging light isn't even on.

I'm getting worried!!! It's been about 7 minutes I think... haha I hope this scary waiting is just all part of the master plan! Please tell me this is normal!
[HTC Rezound] Snuzzo:
OK you ran through and did the wire trick correct I presume and hboot shows s-off?
[HTC Rezound] jtayag:
Still stuck

After a few hours, my phone is still stuck at the HTC screen. The entire time it was doing its JuopunutBear thing, it was upside-down on my desk, so I don't know if the phone ever said I achieved S-off. The phone is still plugged into the computer and the back cover is off. I actually tried removing the battery so I could attempt to reboot, but the HTC screen never went away! Any suggestions on what my next step should be?
[HTC Rezound] Snuzzo:
OK do you still have any windows or cmd prompts showing on the PC?

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] jtayag:
I got past the HTC screen after removing the battery and unplugging and rebooting. I do have S-off, locked, and a bar across the top that says "Tampered." I'm looking up how to fix the internal memory but I'm having trouble locating and verifying the necessary files.
[HTC Rezound] Snuzzo:
At this point, re-flash a recovery through fastboot (fastboot flash recovery **filename of recovery**.img) and re-flash ZoneRom. Will figure out from there on the SD card. Just want to get you back to booting for now. Will get you a patched hboot later also.
[HTC Rezound] Snuzzo:
Any updates jtayag?
[HTC Rezound] cwarnick726:
Thanks for the help, great guys here. Rooted s-on, custom Rom, debloated. Loving this phone again.
[HTC Rezound] matsod78:
Charles, I am having a very similar problem. I apparently did everything to root my phone I achieved the superuser app with eye patch after installing it from amon ra. Root necessary apps say I am not rooted. When I try to update the binary superuser goes through everything until gaining root access and it fails.
[HTC Rezound] Snuzzo:
Install busybox by stericson from play store. Use smart install after pressing install on the left.

Sent from my ADR6425LVW using Xparent Green Tapatalk 2
[HTC Rezound] matsod78:
I can't use it. It says my phone is not properly rooted.
[HTC Rezound] Snuzzo:
Ok google SuperSU. You would need the recovery flashable zip.

Sent from my ADR6425LVW using Xparent Green Tapatalk 2
[HTC Rezound] matsod78:
So installing it from the play store want work? Because I have tried that to no avail.
[HTC Rezound] Snuzzo:
Nope won't work. Gotta give it a flash. Alternatively if you have a custom recovery you could just wipe data/system and flash a custom rom.

Sent from my ADR6425LVW using Xparent Green Tapatalk 2
[HTC Rezound] matsod78:
Big thanks to all who helped. Big thanks to CharliesTheMan. Got me up and running
[Samsung Galaxy Nexus] maliceomalice:
Does anyone have any other methods to avoid enabling data to send/receive MMS?

I came from the xperia x8 and arc and both can receive and send mms without enabling data. I googled and some ppl said that samsung devices are different from sony's and that data must be enabled to use MMS. I find this very depressing coz i dont have any data plan and if i enabled data, my prepaid will be deduced alot. Anyone have any workaround regarding this problm?

-plz help if there are ppl from malaysia...
[Samsung Galaxy Nexus] patruns:
Have you asked your carrier to actually block data instead of charging you if you use it?

I have to ask, why would you buy a phone such as this and not have a data plan? You are missing most of the advantages of the phone.
[Samsung Galaxy Nexus] adrynalyne:
I'm not understanding your request. MMS requires data. So blocking data = blocking MMS.
[Samsung Galaxy Nexus] efrant:
Different carriers use different methods for allowing MMS. For example, Rogers sends all MMS through a different APN than regular data. That way it charges a fixed rate for each MMS, instead of it coming out of your data plan. MMS works without a data plan, so it would lead me to believe that you do not have the MMS APN set up for your carrier.
[Samsung Galaxy Nexus] adrynalyne:
Interesting. Verizon does the same, but it still sends over data.
[Samsung Galaxy Nexus] efrant:
The way Rogers does it, you can still ask for data to be blocked, but are still able to send MMS. All MMS data goes through one APN and is charged per MMS; All other data goes through another APN, and is charged per kb.
[Samsung Galaxy Nexus] adrynalyne:
Nice.
[Samsung Galaxy Nexus] patruns:
T-Mobile in the US separates it as well so you can send MMS without a data plan.
[Samsung Galaxy Nexus] LNJ:
For Rogers, you can just delete the data apn. There is a second apn just for mms anyway.
[Samsung Galaxy Nexus] DarkBanHammer:
You should be able.to disable data on your account or you could call support to disable it. Allways worked for me
[Samsung Epic 4G Touch] rovar:
Id like to make a ODIN version of my current phone setup, and I'm wondering if this thread: http://xdaforums.com/showthread.php?t=1082288 information works/will work with the E4GT.

I'm not comfortable restoring from a nandroid and prefer to flash my stuff using ODIN or Mobile ODIN instead.

Any input is appreciated.
[Samsung Epic 4G Touch] rovar:
Bump 1/2 thanks in advance.

Edit: Oh well for starters its /dev/block/mmcblk# structure on this phone, now if anybody got a guide of what is ok to dump, that'd be great.
[Samsung Epic 4G Touch] Ravaged Pheonix:
There is no danger in using any recovery unless you use factory reset. Get yourself a copy of calks wipe all zip and use that instead of FR. Nandroids are completely safe. I haven't used Odin in months and I flash different roms and Nandroids for testing at least 5 times a week.
[Defy Themes and Apps] rabe3ab:
Hello,

as the title says, here the original Defy Wallpapers. I really missed them since I moved to CM10.

If anyone knows how to create apk using these wallapers to appear in settings, please do this and post the apk here.

http://www.mediafire.com/?4w2wsy8u1z3coac about 13 MB
[Defy Themes and Apps] drone99:
Thanks mister !
[Defy Themes and Apps] rabe3ab:
you're welcome
[Defy Themes and Apps] krkdesigns:
I tried customizing a wallpaper with beats audio.
[Defy Themes and Apps] vedhasd:
Here you go guys, download it from my play store account

https://play.google.com/store/apps/details?id=com.vedhasd.mb525wp
[Defy Themes and Apps] AnTerNoZ:
for me it don't work on latest Epsylon CM10 build

Jelly powered.Defy
[Defy Themes and Apps] vedhasd:
Download vm tool and set vm to 64, I am having some bitmap mem problem...its using very large vm
[Defy Themes and Apps] AnTerNoZ:
the normal size from my vm

heapsize 256

heapstartsize 8

heapgrowthlimit 64

and it don't work

Jelly powered.Defy
[Defy Themes and Apps] vedhasd:
Can you give details on what error are you getting? (If any)? Or is it a random fc? I have tested it on gb only! But it should work on cm10 also... if possible can you print stack trace or logcat?
[Defy Themes and Apps] AnTerNoZ:
i send a crash report true PlayStore, with my logcat program i don't get anything

Jelly powered.Defy
[Verizon Samsung Galaxy S III] Krog216:
Hey all, first time posting here,

So, I rooted my phone a few days ago and flashed Invisiblek's CM10(Running the August 10th build), using the instructions found here. Haven't had any problems at all until now. I had to reboot my phone, and now it's stuck in a boot loop. The CWMR screen is missing the background, and it won't let me boot into ODIN mode. What do I do?

Thank you for any help!
[Verizon Samsung Galaxy S III] Neverendingxsin:
You should be able to boot into odin by taking the battery out, and then putting it back in while holding Volume Down + Home + Power at the same time. And then just flash a stock or stock rooted image in odin.
[Verizon Samsung Galaxy S III] Krog216:
There we go. :) Thank you very much!
[Verizon Samsung Galaxy S III] Krog216:
Flashed the ROM linked from here. Now I'm stuck on the 4G LTE screen. Suggestions?
[Verizon Samsung Galaxy S III] Krog216:
Flashed it again. Still nothing. Did I brick it?
[Verizon Samsung Galaxy S III] cbrehob:
If you can get into Odin mode, I suggest flashing back go stock and starting over. If you can't get Odin to work, or even enter download mode then you might have other problems.
[Verizon Samsung Galaxy S III] Krog216:
I am (thankfully) able to get into odin mode. Where can I get the stock ROM for the US VZW version? I haven't been able to find that anywhere, and the thread on here only has dead links.
[Verizon Samsung Galaxy S III] Krog216:
Flashed again, still nothing. I get stuck at the 4G LTE loading screen.
[Verizon Samsung Galaxy S III] Krog216:
Found a stock ROM and flashed back to it. Still stuck at that screen. Did I brick it?
[Verizon Samsung Galaxy S III] vega04:
dont forget to wipe data/cache...

it happens :D

you can do this by booting into stock recovery

Volume UP + Home + power.
[Verizon Samsung Galaxy S III] Krog216:
Oh my god I love you.

It works!!! :)
[Verizon Samsung Galaxy S III] vega04:
i love you too.. lol ive been there..
[Verizon Samsung Galaxy S III] Krog216:
So, I've got it worked out so that I have a recovery image made of a rooted version of the stock ROM. However, I SWEAR a kitten dies every time I look at the TouchPiss interface, but whenever I try to flash Invisiblek's CM10 I get stuck in a boot loop. Any ideas as to what's causing it? I've tried clearing data/cache/davlik cache before flashing the ROM, after flashing the ROM...
[Verizon Samsung Galaxy S III] Krog216:
Would there be any way at all that I could flash it through ODIN?
[XPERIA X8 Q&A, Help & Troubleshooting] Cheshire-Cat:
So, I was using MiniCM7 2.2.1 (kernel nAa-13) but it seemingly was too hard on my battery, therefore I decided to give a try to a few other ROMs in order to find out which provided the best battery life. So I tried a few on the same kernel and then flashed the Alfs v08a-CM7 kernel and the GingerZaraki ROM. Then the problem began.

As soon as it booted I noticed that the touchscreen was acting weird. I assumed it to be a GingerZaraki or Alfs bug so I flashed back to nAa-13 and MiniCM7 2.2.1, but it persisted, then I flashed nAa-ics-04 and MiniCM9 3.0.4, and finally stock 2.1 -- and it's still there. In all cases factory resets were done and the SD card was cleared as I've seen on other touchscreen bug threads.

I don't know what happened, or what to do. It is like, from time to time, an invisible finger repeatedly touched the right edge of the screen. That results on options being activated in portrait mode (in settings it can go down to third or fourth level in each of the "bursts") or the notification center being activated in landscape mode.

Any ideas?
[XPERIA X8 Q&A, Help & Troubleshooting] Bejjo:
try in stock rom/eclair about a week ,I think it is about nAa issue !!
[XPERIA X8 Q&A, Help & Troubleshooting] binhari:
just full wipe and flash stock rom..........using flash tools......or try using song update service........
[XPERIA X8 Q&A, Help & Troubleshooting] Cheshire-Cat:
I did, as I stated before. Still not working properly.

What I don't understand is how flashing a new kernel/ROM can break it in a way that not even flashing back stock Eclair solves the problem. I can only think of hardware failure but... it would be akin to a computer failing because you installed a different version of Windows. :confused: