Database Info

PLEASE Help - I think i bricked my phone. [SOLVED]

Hi,
My phone was working fine till i tried to revert to old radio and spl to use the superD rom. Ive used many roms and all works fine. When i did the revert my recovery stopped working, so i tried going back to the higher radio and spl and still my recovery doesnt work, i press home and end call and insteasd of going to recovery it just sits there with the htc magic logo for 5 mins then reboots and loops. I have no OS on the phone now so I cant boot into O/S or recovery so I thought id try to install an RUU that I know lets me change the SPL and radio. I thought the only way would be in fastboot so I went into fastboot and loaded the RUU in windows and get the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". Now my fastboot has a little picture of a processor(I think) with a red cross through it and now I cant even change the SPL or radio as I keep getting the error "FAILED (remote: signature verify fail)" this is so frustrating and I really need my phone . I am not smart enough to fix this so if someone could PLEASE help i would be greatly appreciative, thanks.
In fasboot I have the little processor photo with a red cross and the following info.
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.008(SAPP10000)
CPLD-12
RADIO-6.35.08.29
Nov 3 2009, 15:56:29
***Update***
Now I can only get into fastboot, even when I just turn the phone on. Please view this link of the photo of my phone to see what I mean, thanks.
http://i43.tinypic.com/2n1ylwk.jpg

I dont think you bricked it as long as you can enter fastboot..
Actually I dont know what you should do.. hopefully someone can help you.
Good luck

Screwing around with different radio versions almost guarantees a bricking if you don't know what you're doing.
I got your fastboot info, but what exact phone is it?

MicroMina said:
I dont think you bricked it as long as you can enter fastboot..
Actually I dont know what you should do.. hopefully someone can help you.
Good luck
Click to expand...
Click to collapse
Hi MicroMina,
Thanks for the reply. I hope someone can help me too im really stuck here. I have attached a photo in my first post, not sure its even fastboot anymore I can access

kbeezie said:
Screwing around with different radio versions almost guarantees a bricking if you don't know what you're doing.
I got your fastboot info, but what exact phone is it?
Click to expand...
Click to collapse
Hi kbeezie,
Its a HTC Magic 32A. I got it on a plan from Three(hutchinson) Australia.
My phone was working fine up until I used the radio and SPL for this topic
http://forum.xda-developers.com/showthread.php?t=605239
I was trying to downgrade(revert) when the problem happend. Updating/reverting had the same outcome which is where I am at now, thanks

ddmmh said:
Hi kbeezie,
Its a HTC Magic 32A. I got it on a plan from Three(hutchinson) Australia.
My phone was working fine up until I used the radio and SPL for this topic
http://forum.xda-developers.com/showthread.php?t=605239
I was trying to downgrade(revert) when the problem happend. Updating/reverting had the same outcome which is where I am at now, thanks
Click to expand...
Click to collapse
Well you can probably try to revert the phone back to it's original RUU:
http://forum.xda-developers.com/showthread.php?t=659403
There's a Hutchinson, Au one on the list.

kbeezie said:
Well you can probably try to revert the phone back to it's original RUU:
http://forum.xda-developers.com/showthread.php?t=659403
There's a Hutchinson, Au one on the list.
Click to expand...
Click to collapse
Hi kbeezie,
Thanks for the reply but I already tried to do that but i keep getting the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". . Long story short up until 3 days ago I was using the Aus hutching RUU from that post. It was unhackable up until 2 days ago when there was a solution for the spl.0009-0010. I applied the method to revert to a non perfected SPL( i believe its called) i had root/recovery.. i even played around with a few roms but ultimatley i wanted to use the superD rom so I had to revert back to an old radio and SPL and thats when all this nightmare began, any other suggestions?? or any other info I can provide for you? Thanks.

ddmmh said:
Hi kbeezie,
Thanks for the reply but I already tried to do that but i keep getting the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". . Long story short up until 3 days ago I was using the Aus hutching RUU from that post. It was unhackable up until 2 days ago when there was a solution for the spl.0009-0010. I applied the method to revert to a non perfected SPL( i believe its called) i had root/recovery.. i even played around with a few roms but ultimatley i wanted to use the superD rom so I had to revert back to an old radio and SPL and thats when all this nightmare began, any other suggestions?? or any other info I can provide for you? Thanks.
Click to expand...
Click to collapse
If you had it working... why did you bother to flash the radio?

kbeezie said:
If you had it working... why did you bother to flash the radio?
Click to expand...
Click to collapse
Because to run the superD rom you need to have old radio and spl. As soon as I went to revert i started having the problems of not getting into recovery and the phone hanging on the htc magic and rebooting in a loop. At that point in time the fastboot didnt have a lock on it(see picture in first post) When i tried to use the RUU is when I REALLY started having big problems and the fastboot had that little lock image and now the only thing the phone does is go into fastboot no matter if i power on or hold home and power or volume and power... hope this sheds a bit more light on the situation thanks

ddmmh said:
Because to run the superD rom you need to have old radio and spl. As soon as I went to revert i started having the problems of not getting into recovery and the phone hanging on the htc magic and rebooting in a loop. At that point in time the fastboot didnt have a lock on it(see picture in first post) When i tried to use the RUU is when I REALLY started having big problems and the fastboot had that little lock image and now the only thing the phone does is go into fastboot no matter if i power on or hold home and power or volume and power... hope this sheds a bit more light on the situation thanks
Click to expand...
Click to collapse
I never had to deal with the RUU screen, and googling isn't revealing any new info. There's a good chance you effectively bricked the phone. The only other thing I can think of in regards to RUU images, is if perhaps the phone wasn't originally intended for Australia (as such would be a different RUU image).

kbeezie said:
I never had to deal with the RUU screen, and googling isn't revealing any new info. There's a good chance you effectively bricked the phone. The only other thing I can think of in regards to RUU images, is if perhaps the phone wasn't originally intended for Australia (as such would be a different RUU image).
Click to expand...
Click to collapse
Hmm i see, does the SPL or radio determine this? Because like i said earlier I was using the latest RUU for hutchinson AUS which installed fine so I believe thats not the issue, the only problem was the perfected SPL which was finally cracked a few days ago. I never thought id actually brick my phone. Do you think theres nothing I can do? I tried googling a locked fastboot with no results either, is this the first problem of its kind that you know of?

While in fastboot; can you see the device from adb devices?
The safest thing to do would be to go back to the provider's code... just make sure it is the one for your model.

Carlos1970 said:
While in fastboot; can you see the device from adb devices?
The safest thing to do would be to go back to the provider's code... just make sure it is the one for your model.
Click to expand...
Click to collapse
Hi Carlos,
No I cannot see any devices when i CMD adb devices
When you say go back to the providers code do you mean the RUU? If so then ive tried this without success(last one not original). If not can you explain what you mean? thanks

...and you have the SDK and USB drivers installed; correct? I run WinXP and the ADB driver was not automatically installed; had to be installed manually.
"fastboot devices" should work; does that one show anything?

Wow, amazing. Don't try to help when you yourself are not completely sure about what you are saying.
ADB will NEVER recognize your phone in fastboot mode - hence FASTBOOT commands were created!
do "fastboot devices" while in fastboot , not "adb devices"

eyegor said:
Wow, amazing. Don't try to help when you yourself are not completely sure about what you are saying.
ADB will NEVER recognize your phone in fastboot mode - hence FASTBOOT commands were created!
do "fastboot devices" while in fastboot , not "adb devices"
Click to expand...
Click to collapse
The problem of course is those who don't know what they're talking bout wouldn't know that?

And yet they talk. (not directed at Carlos, he did in fact tell the OP to try fastboot devices as well, only later)

OK so I mispoke... The point I was trying to make was that the USB drivers had to be properly installed to get any output out of ADB.
Either through adb devices or fastboot devices it would be good to know if there is any comm over the usb port. If so; the best thing to do might be to reflash the provider's code.
So back to the issue. I found this thread from earlier in the year; I didn't go through all the messages but it is your same problem.
"My HTC Magic Stuck in RUU Screen after failed ROM upgrade"
Search for thread 625604
Hope it helps.

Carlos1970 said:
OK so I mispoke... The point I was trying to make was that the USB drivers had to be properly installed to get any output out of ADB.
Either through adb devices or fastboot devices it would be good to know if there is any comm over the usb port. If so; the best thing to do might be to reflash the provider's code.
So back to the issue. I found this thread from earlier in the year; I didn't go through all the messages but it is your same problem.
"My HTC Magic Stuck in RUU Screen after failed ROM upgrade"
Search for thread 625604
Hope it helps.
Click to expand...
Click to collapse
Hi Carlos and everyone thanks for your input.
I read through that post and all related posts but there wasnt really much of a solution.
I CAN access fastboot devices so i tried to flash a recovery via fastboot it starts to write then I get an error "FAILED (remote: 12 signature verify fail).
I think because I have S-ON? So i was thinking if there was a way to turn S-OFF would I be able to flash a custom recovery via fastboot??? Cheers

BUMP ^ ^
$20 into paypal account for anyone can give me a solution to fix this 100%.

Help needed please.... got into a dead end with my One X

Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster

sunster00 said:
Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
Click to expand...
Click to collapse
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout

jags_the1 said:
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
Click to expand...
Click to collapse
Hi mate thanks for offering advice and help. I have not had to use your method as I decided to give the HTC bootloader unlock code one final try before proceeding to your rescue plan and all of a sudden it was successful again. I got into recovery and did a nandroid restore so am back online again, but have nevertheless made note of your method in case I become stuck again in the future. Thanks anyway for your reply! :good:

Go back to stock, full stock!

Hi all again, another noobish question
i am facing some Wi-Fi issues (wifi dont turn on..i tried new roms, kernels, stock ones either, wiping etc...), so i decided go back to stock and i mean STOCK with S-ON, unroot, stock radio, stock hboot etc. > also because of warranty, coz new motherboard cost almost like whole new phone, and thats not acceptable for me but i want restore all the goodies, when phone returns from service!!! (ViperS 1.2.0 is so fraggin awesome!)
So my question is: Can somebody post some tutorial or help me with this? my laptop i so slow right now, word i write appears about 15 seconds later, so i can´t search
Thans in advance!!
Lord5619

http://forum.xda-developers.com/showthread.php?t=1672425
Sent from my HTC Sensation 4G using xda app-developers app

Do a nandroid backup of your current ROM.
Change CID to the one you're meant to have. You'll need to boot into fastboot mode and run the command "fastboot oem writecid xxx" where xxx is your correct cid.
Run the correct RUU for your phone to install the stock ROM. You'll need to run it from a windows PC with the HTC drivers installed but without HTC sync. If it won't work, put the phone into bootloader mode and try it again.
Once the RUU has successfully flashed, boot into fastboot mode and issue the command "fastboot oem writesecureflag 3" to return to S-on. Make sure that step is done last else you'll end up with a brick.
I recently did the above for a friend's phone to return for warranty repair. It was successful

So i flashed complete RUU ICS, get S-ON...and the wi-fi still doesn't work, I tried it for maybe half an hour...So i leaved it on the table and went play with my little son for an hour or so. Than a returned to my damn phone and wi-fi actually works!!! Quite strange, but great
Thx for help guys!

Looking for updated info on OTA update 2.35

I received a new replacement 1S a week ago. Three days ago—after I rooted it (though no SuperCID or S=off yet)—I got the notification for the 2.35 update. I searched here about this update and it seems overall that it it helpful. However, some people were concerned about an upgrade to hboot.
Since it seems that we have the ability to get s=off, a worry over an upgraded hboot would now be irrelevant, correct? I would rather not go through the whole process of unrooting, flashing stock recovery, etc. then dissembling the update, changing updating script, signing & rezipping, etc., etc. and instead just install the update and if it unroots, just re-flash TWRP and flash SuperSU.
Is it OK just to install the update and re-root?
Thank you...

syntropic said:
I received a new replacement 1S a week ago. Three days ago—after I rooted it (though no SuperCID or S=off yet)—I got the notification for the 2.35 update. I searched here about this update and it seems overall that it it helpful. However, some people were concerned about an upgrade to hboot.
Since it seems that we have the ability to get s=off, a worry over an upgraded hboot would now be irrelevant, correct? I would rather not go through the whole process of unrooting, flashing stock recovery, etc. then dissembling the update, changing updating script, signing & rezipping, etc., etc. and instead just install the update and if it unroots, just re-flash TWRP and flash SuperSU.
Is it OK just to install the update and re-root?
Thank you...
Click to expand...
Click to collapse
If you're talking about the One S, you're in the wrong forum.

My apologies... Where did that get posted originally...? Oh well.
Edit: Apparently I was looking at the HTC One forum and forgot I was still there when I posted the above question.
But if anyone thinks I should have no problem flashing that update and re-rooting, let me know. It appears some improvements to WiFi were made, and I would like to install it without stressing about it.
Sent from my HTC VLE_U using xda premium

OK... well I figured out that I cannot install the update with TWRP as my current recovery. I didn't know that. I figured the update would just install its own recovery.
So.... I am reflashing stock recovery. I have it on my SD card... I did adb fasboot. The phone is in fastboot mode and fastboot devices shows my device.
So...(and this is driving me nuts), what is the path to the sdcard??? It always was /sdcard/. When did this change?????
In a fit of research I again tried other paths found around the web: /mnt/sdcard, /storage/sdcard/, /mnt/sdcard0/, /storage/sdcard0/ and just /sdcard0/, but adb tells me it cannot find my recovery .img.
I know that the name of the file is correct.... Can someone please tell me how I can do a listing of the filesystem through adb???
Thank you,
irritated but grateful for any help

Here are some commands in fastboot just to assure myself that everything is correct...
C:\HTCOne>fastboot devices
FA2CKW400117 fastboot
C:\HTCOne>fastboot getvar version-main
version-main: <-------------------- I don't know why I didn't get a version here...But I am guessing it is because I have TWRP as recovery.
finished. total time: 0.003s
C:\HTCOne>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.010s]
finished. total time: 0.011s
C:\HTCOne>
[EDIT]I downloaded another copy and installed it from my laptop... I guess this has all been a waste since I was going to go to S=off next and I guess I didn't realize you could flash partitions independently (or that the update was in that format). But anyway... I still am wondering if there is a way to use ADB to list the partitions... so I can determine the path to my SDCard..
I am running stock...it is still rooted, but that shouldn't matter. I might have disabled some bloatware but I never got around to uninstalling it before I decided to back up and quickly install this update.
I will try to look for a stock recovery and download it to my PC...I know that is a solution, but I don't really like not being able to access my SDcard from ADB. This has never been a problem in the past. Also... I see people talking about needing a "jellybean recovery"... Is this true??? Has the recovery changed (I presume this is an international 1S upgrade since stock is still ICS in the US). But does it matter???

Did you ever get this working? I have an issue with 2.35 that is driving me nuts, and like you, people are reading my post but not replying for some reason. 2.35 makes fixing the App Associations idiocy much more difficult, if not impossible.

[s-off] hboot 2.15 htc one s flawless

So there are many tutorials out there for obtaining S-OFF for the HTC ONE S for all kinds of HBOOTS. But what about those of us with the newest model and HBOOT 2.15 and so on? Well it's been solved after months of trying.
1) First thing you're going to need is an appropriate RUU for your device. Mine is "RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2"
There is a thread for obtaining the proper RUU and how to distinguish which one you need. If you're here, you probably already have the appropriate RUU.
2) Second, youre going to need THE CORRECT VERSION of Moonshine. If your device is like mine, it will look like this: HTC One S T-MOB Windows 3.14.531.11 moonshine_ville_3.14.531.11.zip. If you have a different ROM version, get that one. Same goes for the carrier. Use your RUU name for a cheat sheet if you have to. Note the similarities??
3) Probably one of the most important steps is making sure that you have FASTBOOT AND ADB both installed and running AND detecting your device!!! I can not stress enough how important these are! Without them, you're gonna have a bad time. MAKE SURE USB DEBUGGING IS ON AT ALL TIMES! Snoop05 made a fantastic tool called 15 SECONDS ADB INSTALLER 1.1. Here's the link for that http://forum.xda-developers.com/showthread.php?t=2588979
Follow his instructions in the OP for a how to if you run into a problem, which you shouldn't if you can read.
Use the terminal command " adb devices " and you should get something like this
C:\Users\C***********\Desktop>adb devices
List of devices attached
HT26TW407378 device
This means your phone is being recognized as an adb device, which is fantastic! If not, try disabling and re-enabling USB DEBUGGING.
Boot into BOOTLOADER and go back to your command prompt and enter " fastboot devices ". You should get a reply that looks something like this:
C:\Users\C***********\Desktop>fastboot devices
HT26TW407378 fastboot
CONGRATULATIONS, you're almost there!
4) Once you have ADB and FASTBOOT both running properly, it is ALMOST time to run your RUU. First we have to relock our BOOTLOADER! It is very simple. Go into your Bootloader and make sure you have FASTBOOT USB on your screen. Once you see that, open a command terminal on your PC where fastboot is located, or anywhere if you used the 15 file I have above, as it makes sets fastboot machine wide! (exciting, huh?) In the command window type in " fastboot oem lock ". Now your bootloader is relocked and you are ready to run the RUU.
Run the RUU and allow it to finish. Reboot your device. HERE IS WHERE STUFF CHANGES!! Other people would have you ROOT. All you need to do is this:
-RE-ENABLE USB debugging and set your screen to NEVER TURN OFF. Trust me, you want this for now.
-Unlock your BOOTLOADER again
-DO NOT root
-DO NOT install SU or busybox
-DO NOT flash a custom recovery
-ONLY RUN MOONSHINE, follow the prompts, answer Yes twice and let it do its magic. My phone took 4 tries to get it done, but it worked!
If you followed my instruction to the T you should be moonshine S-OFF. Your device will be turned off when it finishes. Reboot your phone into Bootloader and profit, because you are S-OFF!

>My phone took 4 tries to get it done, but it worked!
What do you mean by this? You had to run the moonshine 4 times before it worked? Why would this be?

Misconception, sorry pal
808phone said:
>My phone took 4 tries to get it done, but it worked!
What do you mean by this? You had to run the moonshine 4 times before it worked? Why would this be?
Click to expand...
Click to collapse
Allow me to clarify.
When Moonshine is running it sends your phone into bootloader and restarts the phone.
After it checked to see that ADB and fastboot were working properly, it started doing that.
It went into fastboot to adb to fastboot to adb and had a running line of "moonshining<1,2,3,4>.........." after each time.
It did this four times before moonshine actually gained S-OFF.
It went something like this:
Waiting for device..........................................................................
Device found
Moonshining<1>.........................................................
Moonshining<2>..................................................
Moonshining<3>...........................................
Moonshining<4>......................................
Waiting for ADB Device
Waiting for device
Powering off device. Unplug and reboot device (or something of that nature)
Hope you enjoyed the moonshine.
Keep in mind this is off of my memory of what the terminal said. I did NOT have to restart moonshine 4 times. I ran it once, and was done.
It took about 10-15 minutes all together.

What do I need to know about RUU to use Moonshine
Thanks for this tutorial. I have had a million problems trying to get S-Off but I'm hopeful that your technique will work since it seems like we both have the One S from Tmobile.
Can you please point me to some info about RUU? I've heard of them but not sure exactly what they are. If you have a link to a good tutorial it would be much appreciated.
p.s. Here is the link to my current thread documenting my difficulties getting s-off: http://forum.xda-developers.com/showthread.php?t=2658650

fonnae said:
Thanks for this tutorial. I have had a million problems trying to get S-Off but I'm hopeful that your technique will work since it seems like we both have the One S from Tmobile.
Can you please point me to some info about RUU? I've heard of them but not sure exactly what they are. If you have a link to a good tutorial it would be much appreciated.
p.s. Here is the link to my current thread documenting my difficulties getting s-off: http://forum.xda-developers.com/showthread.php?t=2658650
Click to expand...
Click to collapse
An RUU (recovery update utility, I believe) can be used to upgrade your device OR (in our case) return your phone to stock. There is a sticky in the development area that has a page with an RUU repository. That page should tell our exactly how to match the correct RUU with your phone. I'm sorry I don't have the link handy, I'm not on my laptop right meow.
Sent from my One S using Tapatalk

Thanks. Just a couple more quick questions. After I do moonshine:
Will I be root?
Can I simply flash cwm recovery and then restore my current nandroid backup?

fonnae said:
Thanks. Just a couple more quick questions. After I do moonshine:
Will I be root?
Can I simply flash cwm recovery and then restore my current nandroid backup?
Click to expand...
Click to collapse
You should be able to! Right after I moonshined, I went right into flashing a recovery and then flashed my ROM. It was so exciting not having to boot into bootloader and the use fastboot to flash the kernel. It was instantaneous!
Flash a recovery (I've noted having trouble with old recoveries meow)
Restore your nandroid and report back here?
I'm sure there will be another user with your question. I'll add it to the OP if all goes well. And it should go perfectly. The recovery should fix root, it'll ask you before you reboot the device.
Sent from my One S using Tapatalk