Related
Below is the details of my phone, I am not able to S-Off the phone, require help. I tried couple of things however gives me error.
Phone Details.
Saga Pvt ship S-on RL
Hboot – 2.00.0002
Radio – 3822.10.08.04_M
eMMC-boot
Which guide did u follow and which part did u encounter an error?
Have u used the search bar?
Be specific. Show us ur error.
Sent from my Desire S
unlock your phone with htcdev and root it with superoneclick
worked perfect for me :good:
johnyomair said:
unlock your phone with htcdev and root it with superoneclick
worked perfect for me :good:
Click to expand...
Click to collapse
Using htcdev keeps the phone S-ON. You'll still be able to run custom roms, but can't flash a new radio.
rain987 said:
Which guide did u follow and which part did u encounter an error?
Have u used the search bar?
Be specific. Show us ur error.
Sent from my Desire S
Click to expand...
Click to collapse
I refered to a you tube video " How to S-off htc desire s" the first video that shows up. My phone is already rooted using the hdc dev kit, however when I am trying to do s-off the software gives just a message "Error". It also fails at signature.
do let me know what more information can I provide.
If you have a guide that I can try and share the results with you do send me that as well. I am new to rooting the phone, so sorry for not providing any info that is required.
You either htcdev unlock or you s-off
You'll now need to relock your phone to undo the htcdev and then downgrade you phone in order to properly s-off using revolutionary.
There are various downgrade guides in the index, see link on my signature
Sywepd form my DsereiS
ben_pyett said:
You either htcdev unlock or you s-off
You'll now need to relock your phone to undo the htcdev and then downgrade you phone in order to properly s-off using revolutionary.
There are various downgrade guides in the index, see link on my signature
Sywepd form my DsereiS
Click to expand...
Click to collapse
Thanks will try the suggestion and let you know the results
505dv said:
Using htcdev keeps the phone S-ON. You'll still be able to run custom roms, but can't flash a new radio.
Click to expand...
Click to collapse
My HTC is S-OFF because i rooted it with SuperOneClick afterwards
johnyomair said:
My HTC is S-OFF because i rooted it with SuperOneClick afterwards
Click to expand...
Click to collapse
No, it's S-ON, but writable on /system partition due to HTCDev unlock. It only means that you don't know the difference between S-OFF, rooting and HTCDev unlock - and misleading others.
Jack_R1 said:
It only means that you don't know the difference between S-OFF, rooting and HTCDev unlock - and misleading others.
Click to expand...
Click to collapse
Then please tell me why my Bootloader says:
*unlocked*
SAGA PUT SHIP S-OFF RL
S-OFF ... Security off
Rooting ... Grant root for the device, like su on linux
HTCDev unlock ... unlocks the bootloader
But its ok I just tried to help...
Then you can try to avoid confusion providing more detailed info, like:
"I have used XTC Clip to gain S-OFF, then used htcdev.com, without any particular reason, then got rooted by SuperOneClick"
Your previous post can mislead some non advanced users that SOC can provide S-OFF, without using additional tools.
Sent from my HTC Desire S
Ok..
I unlocked my HTC Desire S following the instructions on HTCDev.com. Afterwards I rooted the Phone,installed Busybox and installed ClockworkMod Recovery using the SuperOneClick tool for Windows 7.
And now I am able to flash Rom and Radios.
Nope to upgrade your Radio you have to be S-OFF
Maybe it was shipped with S-OFF because I had a brandig first.
I doubt that it was shipped S-OFF and even if, why would you unlock it with HTCdev ?
johnyomair said:
Ok..
I unlocked my HTC Desire S following the instructions on HTCDev.com. Afterwards I rooted the Phone,installed Busybox and installed ClockworkMod Recovery using the SuperOneClick tool for Windows 7.
And now I am able to flash Rom and Radios.
Click to expand...
Click to collapse
And you can flash radios only because you had a phone which already was S-OFF, either during manufacturing or by XTC-Clip, and you just didn't understand it and uselessly unlocked it while you could have done whatever you wanted with it. And S-OFF is the only reason you can flash radios, and HTCDev unlock didn't actually add anything and didn't allow you anything - just as it won't allow any non-S-OFF user to flash radios, and won't turn S-ON to S-OFF. But what do I know, I was just passing here.
c.m.b said:
I doubt that it was shipped S-OFF and even if, why would you unlock it with HTCdev ?
Click to expand...
Click to collapse
It is unlikely, but certainly possible. In the early days of Desire S development (back when we had to use the XTC-Clip hardware to obtain S-Off) there were some people who got their devices brand new already S-Off.
ok, back to the topic:
the simpliest way to gain s-off without xtc-clip is to downgrade the bootloader to HBOOT 0.98, and gain S-OFF with Revolutionary. After you did this you can run the latest ruu, which doesn't influence wether your s-off or s-on. Finally, you've got a device with hboot 2.02 and s-off.
After using revolutionary you are already S-OFF!
If you want to upgrade your HBOOT don't run a RUU AFAIK it could brick your device ... use this tutorial
http://forum.xda-developers.com/showthread.php?t=1679338
Do you know the differences between Radio HBOOT S-OFF root etc?
Sent from my Desire S using xda app-developers app
Jack_R1 said:
....you had a phone which already was S-OFF, either during manufacturing or by XTC-Clip, and you just didn't understand it and uselessly unlocked it
................and HTCDev unlock didn't actually add anything and didn't allow you anything...........
Click to expand...
Click to collapse
I have to disagree @Jack_R1 the unlock via htcdev wasn't completely useless as it managed to void his HTC warranty! :laugh: logging that fact with HTC in the process!
we can only try...........:silly:
Hi all, I had to re-install a stock rom from an HTC RUU. Prior to that I was HTC unlocked, HBOOT 1.27, firmware 3.33, rooted, custom ROMs.
Right now the bootloader is re-locked, HBOOT 1.29, european stock 3.33.401.106 with 11.76A.3504.00U_11.24A.3504.31_M radio.
The objective is to re-gain S-OFF and go trough all the way to custom ROM again.
I was thinking to execute fastboot oem writesecureflag 3
To my understanding this should clear off the relocked flag.
At this point to go to htcdev and proceed with that like I did already once.
Probably the above is too simple to work, but the whole JuopunutBear timing thing is a bit an issue having tried already in ther past.
Any help/feedback is greatly appreciated.
DiscreteTask said:
Hi all, I had to re-install a stock rom from an HTC RUU. Prior to that I was HTC unlocked, HBOOT 1.27, firmware 3.33, rooted, custom ROMs.
Right now the bootloader is re-locked, HBOOT 1.29, european stock 3.33.401.106 with 11.76A.3504.00U_11.24A.3504.31_M radio.
The objective is to re-gain S-OFF and go trough all the way to custom ROM again.
I was thinking to execute fastboot oem writesecureflag 3
To my understanding this should clear off the relocked flag.
At this point to go to htcdev and proceed with that like I did already once.
Probably the above is too simple to work, but the whole JuopunutBear timing thing is a bit an issue having tried already in ther past.
Any help/feedback is greatly appreciated.
Click to expand...
Click to collapse
fastboot oem writesecureflag 3 returns bootloader to S-ON, it wont help you.
The only way to S-OFF 1.2x.xxxx HBOOT versions is JuopunutBear S-OFF. Oh and did you know you dont have to be S-OFF to flash ROMs, search for the Flashing ROMs with S-ON guide and follow it.
Jonny, thank you for your input. To be honest I did not know that it was possible flashing with S-OFF, I will look into this.
From you answer I understand that JuopunutBear S-OFF can be used the same also in the case the device was already S-OFF and relocked.
Thanks again.
Jonny said:
fastboot oem writesecureflag 3 returns bootloader to S-ON, it wont help you.
The only way to S-OFF 1.2x.xxxx HBOOT versions is JuopunutBear S-OFF. Oh and did you know you dont have to be S-OFF to flash ROMs, search for the Flashing ROMs with S-ON guide and follow it.
Click to expand...
Click to collapse
DiscreteTask said:
Jonny, thank you for your input. To be honest I did not know that it was possible flashing with S-OFF, I will look into this.
From you answer I understand that JuopunutBear S-OFF can be used the same also in the case the device was already S-OFF and relocked.
Thanks again.
Click to expand...
Click to collapse
you have hboot version 1.29.0000 yes? This means that the easier revolutionary method wont work on your phone (revolutionary is GingerBread only), so the only possible way to S-OFF on your phone is with the JuopunutBear method.
To get rid of the relocked text on the bootloader you need to flash the JuopunutBear hboot (which you can only do after S-OFF) then run an RUU. This will make the text say "LOCKED" again
So, I have done a lot of research and I am hung up on one bit.
I have the stock RUU file on my PC.
I also have superCID . I am rooted with S-OFF
Think i used Revolutionary etc. Currently using ARHD 6.8.0
I want to return to Full Stock with S-ON. I looked at this guide: http://forum.xda-developers.com/showthread.php?t=1192300
But it doesn't say if I need to change my CID back to VODAP001 before or after (Or at all) I flash the Stock RUU. <hope that makes sense?
Could anyone help me?
I basically have the RUU. and need to know about the CID. Does it need to be changed?
Thanks
Just seen this actually
I can confirm SuperCID is successful as i just flashed a Tmous Rom (1.25.***) to my EU unbranded device to check. (added t-mobile tv and other carrier stuff to my apps list)
Does ^ this mean I can run the RUU with my SUPER CID?
Then just S-On once done??
thanks again.
pike0 said:
I can confirm SuperCID is successful as i just flashed a Tmous Rom (1.25.***) to my EU unbranded device to check. (added t-mobile tv and other carrier stuff to my apps list)
Does ^ this mean I can run the RUU with my SUPER CID?
Then just S-On once done??
thanks again.
Click to expand...
Click to collapse
Hi,
If you are returning your phone for warranty purposes,you need to return your SuperCID to normal.
This should be done after running your RUU,but before going back to s-on.
Look HERE for more information.
pike0 said:
I can confirm SuperCID is successful as i just flashed a Tmous Rom (1.25.***) to my EU unbranded device to check. (added t-mobile tv and other carrier stuff to my apps list)
Does ^ this mean I can run the RUU with my SUPER CID?
Then just S-On once done??
thanks again.
Click to expand...
Click to collapse
you can flash any ruu when you have supercid(that means S-OFF also)
this guide will help you more
http://forum.xda-developers.com/showthread.php?t=1672425
but read carefully about returning to S-ON
rzr86 said:
you can flash any ruu when you have supercid(that means S-OFF also)
this guide will help you more
http://forum.xda-developers.com/showthread.php?t=1672425
but read carefully about returning to S-ON
Click to expand...
Click to collapse
Cool, well the RUU I have will need the VODAP001 *** (I think it's that, will check before I attempt lol)
So I flash the RUU then I can use this:
Code:
fastboot oem writecid ******* Replacing the *'s with the CID I need.
Once done, can then return to S-ON
pike0 said:
Cool, well the RUU I have will need the VODAP001 *** (I think it's that, will check before I attempt lol)
So I flash the RUU then I can use this:
Code:
fastboot oem writecid ******* Replacing the *'s with the CID I need.
Once done, can then return to S-ON
Click to expand...
Click to collapse
also about S-ON read carefully what it is saying about bootloader
your bootloader must be LOCKED, RELOCKED or UNLOCKED otherwise don't do S-ON
rzr86 said:
also about S-ON read carefully what it is saying about bootloader
your bootloader must be LOCKED, RELOCKED or UNLOCKED otherwise don't do S-ON
Click to expand...
Click to collapse
Was just about to post. Successfully flashed the RUU and changed CID to VODAP001, phone boots and works fine!!!
But in bootloader it doesn't mention, locked, unlocked or relocked.
Previously to the Update, it said ***LOCKED***
Now I got just this:
Pyramid PVT Ship S-OFF RL
HBOOT-1.17.0006
RADIO-10.11.9007.09_M2
eMMC-boot
What do I need to do to S-ON???
Thanks
pike0 said:
Was just about to post. Successfully flashed the RUU and changed CID to VODAP001, phone boots and works fine!!!
But in bootloader it doesn't mention, locked, unlocked or relocked.
Previously to the Update, it said ***LOCKED***
Now I got just this:
Pyramid PVT Ship S-OFF RL
HBOOT-1.17.0006
RADIO-10.11.9007.09_M2
eMMC-boot
What do I need to do to S-ON???
Thanks
Click to expand...
Click to collapse
if your bootloader says locked now(as you are mentioning) then you can continue with S-ON
edit:what to do for S-ON?
from the same guide it has a tutorial for it
but i think it is a simple command and then you are done
rzr86 said:
if your bootloader says locked now(as you are mentioning) then you can continue with S-ON
edit:what to do for S-ON?
from the same guide it has a tutorial for it
but i think it is a simple command and then you are done
Click to expand...
Click to collapse
Sorry, I actually mean, before I restored the RUU it said locked. Now it doesnt mention anything.
It no longer says that, or unlocked / relocked.
So I haven't proceeded with the S-ON command.
pike0 said:
Sorry, I actually mean, before I restored the RUU it said locked. Now it doesnt mention anything.
It no longer says that, or unlocked / relocked.
So I haven't proceeded with the S-ON command.
Click to expand...
Click to collapse
hmm,
i don't know about that
it is better to ask for that in the ruu thread
someone will know
rzr86 said:
hmm,
i don't know about that
it is better to ask for that in the ruu thread
someone will know
Click to expand...
Click to collapse
Say I still have S-OFF but everything else is back to stock. What steps would I need to take to root, custom recovery & ROM again?
Thanks
pike0 said:
Say I still have S-OFF but everything else is back to stock. What steps would I need to take to root, custom recovery & ROM again?
Thanks
Click to expand...
Click to collapse
Hi,
Flash recovery of choice.
Flash root.
Flash custom ROM.
malybru said:
Hi,
Flash recovery of choice.
Flash root.
Flash custom ROM.
Click to expand...
Click to collapse
Recovery is the PMG...zip is that correct?
Thanks for all the help
pike0 said:
Recovery is the PMG...zip is that correct?
Thanks for all the help
Click to expand...
Click to collapse
Hi,
Look HERE
2. Flashing a recovery
4A. Flashing Root
malybru said:
Hi,
Look HERE
2. Flashing a recovery
4A. Flashing Root
Click to expand...
Click to collapse
Many thanks! Would it make a difference if my phone is already S-OFF??
pike0 said:
Many thanks! Would it make a difference if my phone is already S-OFF??
Click to expand...
Click to collapse
Hi,
No.
If you ran a RUU,then,everything would have returned to stock.
S-off is not affected.
So,to get back up and running,you will need to do all these things again.
Hey guys,
Where can I find the RUU for HBOOT 2.15.0000, RADIO 1.13.50.05.31 ?
I've looked all over and cannot find it.
Any help appreciated.
Seconded. I've looked for a RUU on and off for the last several months.
808phone said:
Hey guys,
Where can I find the RUU for HBOOT 2.15.0000, RADIO 1.13.50.05.31 ?
I've looked all over and cannot find it.
Any help appreciated.
Click to expand...
Click to collapse
What is your CID?
92lucio92 said:
what is your cid?
Click to expand...
Click to collapse
my cid:
TMOBO010
thanks!
808phone said:
my cid:
TMOBO010
thanks!
Click to expand...
Click to collapse
Why you need this specific ruu?
It may be this one: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
92Lucio92 said:
Why you need this specific ruu?
It may be this one: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
Click to expand...
Click to collapse
Thanks! I was told that I needed the same RUU as what I had on the phone or else I could not restore if I didn't have S-OFF.
Are you saying that I can install a _newer_ RUU at any time than what I have?
Thanks,
Aron
Yes, you can always install the same or newer version. To install older you need to be S-off.
Skickat från min One S via Tapatalk
WOW! OK, well that opens things up.
Here's my plan, please tell me if it makes sense.
1: I will try firewater s-off. Let's see if that works. Right now I am back to RELOCKED so we will see if the temporary root method works for firewater s-off.
2: Assuming the above works, I will them put in TWRP recovery (fastboot flash recovery xxxxx)
I would think that this would give me s-off, and finally a custom recovery software.
I am not sure at this point if I need SuperSU if I have s-off and TWRP installed and an unlocked boot loader.
Thanks!!!!
BTW: I had previously unlocked boot loader, installed TWRP, superSU. Tried to install CM11 and when I flashed the boot.img it screwed up my phone. Now I am back to RELOCKED and stock Jellybean.
808phone said:
WOW! OK, well that opens things up.
Here's my plan, please tell me if it makes sense.
1: I will try firewater s-off. Let's see if that works. Right now I am back to RELOCKED so we will see if the temporary root method works for firewater s-off.
2: Assuming the above works, I will them put in TWRP recovery (fastboot flash recovery xxxxx)
I would think that this would give me s-off, and finally a custom recovery software.
I am not sure at this point if I need SuperSU if I have s-off and TWRP installed and an unlocked boot loader.
Thanks!!!!
BTW: I had previously unlocked boot loader, installed TWRP, superSU. Tried to install CM11 and when I flashed the boot.img it screwed up my phone. Now I am back to RELOCKED and stock Jellybean.
Click to expand...
Click to collapse
I would look into moonshine s-off first. I've read of some people having problems with firewater.
Moonshine S-Off
You have to be patient with it, but it's completely foolproof. I've used it on two HTC One S models without fail.
OK, but with moonshine I need to go to HTC dev an unlock the boot loader again. Also I'm worried that it will change HBOOT. Seems spooky.
808phone said:
OK, but with moonshine I need to go to HTC dev an unlock the boot loader again. Also I'm worried that it will change HBOOT. Seems spooky.
Click to expand...
Click to collapse
It's not spooky at all. Even though it changes the hboot, the hboot is technically still listed as 2.15 and is compatible with any ROM in the dev section (except the ones that require 2.16, of course).
Thanks. I noticed another thing. With moonshine I have to update my ROM to :3.14.531.11
808phone said:
Thanks. I noticed another thing. With moonshine I have to update my ROM to :3.14.531.11
Click to expand...
Click to collapse
Yep. It has to be on the stock version of Jelly Bean 4.1 to work. Although I've read that it's also okay if you've upgraded to 3.14.531.17. It will work with that firmware upgrade too if you just use the same process as if it were on 3.14.531.11.
Brushstroke said:
Yep. It has to be on the stock version of Jelly Bean 4.1 to work. Although I've read that it's also okay if you've upgraded to 3.14.531.17. It will work with that firmware upgrade too if you just use the same process as if it were on 3.14.531.11.
Click to expand...
Click to collapse
OK I know my software number is 3.14.531.17
But when you look at something like HBOOT 2.15.0000, RADIO 1.13.50.05.31 how does that correlate to the software number? Is there a way to find out? Very confused by this.
Thanks!
808phone said:
OK I know my software number is 3.14.531.17
But when you look at something like HBOOT 2.15.0000, RADIO 1.13.50.05.31 how does that correlate to the software number? Is there a way to find out? Very confused by this.
Thanks!
Click to expand...
Click to collapse
Hboot version is the version of the bootloader. Radio is the version of the firmware for the equipment in the phone that controls your mobile data/WiFi connection. These usually are upgraded along with a major software update like 3.14.531.11.
Sent from my One S using xda app-developers app
Thanks! I was just wondering why the software version is not listed in the RUU number.
Something like:
HBOOT 2.15.0000, RADIO 1.13.50.05.31 Version 3.14.531.17 RUU
OK, never mind. I can't believe it was so easy to find the RUU. Right on HTC's site!
And HTC DOES list the software number:
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB.exe
OK, I am ready to try S-OFF.
Thanks for the help.
808phone said:
Thanks! I was just wondering why the software version is not listed in the RUU number.
Something like:
HBOOT 2.15.0000, RADIO 1.13.50.05.31 Version 3.14.531.17 RUU
Click to expand...
Click to collapse
The software version usually is in the RUU number, actually. The one for yours 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
It notes that it's for the Ville and not VilleC2, and that it is JB (Jelly Bean), that its for T-Mobile US, then the software number, then the radio version. They're all named pretty much in this order.
Sent from my Nexus 7 using xda app-developers app
Thanks for the help guys but moonshine and firewater s-off didn't work for me.
Moonshine gets stuck with a ton of .............. over and over.
Firewater crashes out of adb shell.
Another user has the same ROM etc... he tried all of the options (except all in one toolkit) and none work.
I thought I saw a manual way of getting s-off but I can't find the link now.
Ok, guys, i think that i made a big mistake, i was helping to restore to stock the HTC evita of a friend. We download the latest RUU from att, relocked and run. the problem was, that we didnt check it if there was super cid. and it have it. BUT, usually if there is a brick i cant enter to bootloader right? I can enter in bootloader, and show
Relocked
EVITA PVT SHIP S-ON RL
HBOOT- 2.18.0000
RADIO-1.35a.32.45.27
OPENDSP-v33.1.0.45.1127
eMMC-boot
Dec 3 2013,17,10,01:1
The phone has supecid: (bootloader) cid: 11111111
I know that usually is a brick, but i can enter the bootloader (i did a clearstorage but still bootloop) I dont want to make it worse. so any advice to fix it? I was thinking about unlocking again bootloader but probably it cause a brick? I read that the brick is unlocked bootloader + supercid +s-on, but the bootloader was relocket so maybe that save the device?. Any advice would be great
lorddavid said:
Ok, guys, i think that i made a big mistake, i was helping to restore to stock the HTC evita of a friend. We download the latest RUU from att, relocked and run. the problem was, that we didnt check it if there was super cid. and it have it. BUT, usually if there is a brick i cant enter to bootloader right? I can enter in bootloader, and show
Relocked
EVITA PVT SHIP S-ON RL
HBOOT- 2.18.0000
RADIO-1.35a.32.45.27
OPENDSP-v33.1.0.45.1127
eMMC-boot
Dec 3 2013,17,10,01:1
The phone has supecid: (bootloader) cid: 11111111
I know that usually is a brick, but i can enter the bootloader (i did a clearstorage but still bootloop) I dont want to make it worse. so any advice to fix it? I was thinking about unlocking again bootloader but probably it cause a brick? I read that the brick is unlocked bootloader + supercid +s-on, but the bootloader was relocket so maybe that save the device?. Any advice would be great
Click to expand...
Click to collapse
I think you need to unlock your bootloader and get S-off to proceed with RUU because you have superCid.
sathish804 said:
I think you need to unlock your bootloader and get S-off to proceed with RUU because you have superCid.
Click to expand...
Click to collapse
yes, the problem is that i cant load a rom, I mean, its bootloop. If i unlock bootloader and flash a recovery will be ok? I mean, i fear that unlocking bootloader brick my phone because I ran RUU with supercid
Unlock the bootloader again, flash TWRP recovery again, flash a custom ROM, get s-off, then you can run any RUU you want.
Sent from my Evita
ok, i unlock the bootloader, I'm trying to enter hboot again because the volumebutton ihave little damage. thanks If something happen i will report back.
PD: S-off can i do it with an aosp rom? Or need a sense rom?
It shouldn't really matter, I've done it on both.
Facepalm S-off
Sent from my Evita
Doesn't the Evita need to be s off to run a ruu, and with a locked bootloader?
Sent from my One X using Tapatalk
marknoll said:
Doesn't the Evita need to be s off to run a ruu, and with a locked bootloader?
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
No, but running any jb+ RUU with s-on and SuperCID causes a brick. Plus, if you have SuperCID, you need s-off to bypass the CID check that stops the RUU from running.
Sent from my Evita
timmaaa said:
No, but running any jb+ RUU with s-on and SuperCID causes a brick. Plus, if you have SuperCID, you need s-off to bypass the CID check that stops the RUU from running.
Sent from my Evita
Click to expand...
Click to collapse
Uff, finally, but TWPR is weird, flash a lot in splash screen :/ but after a while works. I was thinking that i had a brick because i was s-on and supercid. I had a aosp rom, so right now I will do s off. Thanks so much
PD: Right know is in the boot screen of PAC ROM. The hboot doesnt matter for an aosp rom right?
You probably need to read the Evita FAQ thread in my signature.
Sent from my Evita
timmaaa said:
You probably need to read the Evita FAQ thread in my signature.
Sent from my Evita
Click to expand...
Click to collapse
yes i did, is not the first time that i install a custom rom in a htc, i flash the boot.img and everything, but had some weird problems, I will try philz recovery now (TWPR sometimes flash a lot in the splash screen, or freeze or just works normal). and i will download another rom just to be sure.
Ok, its finnish, thanks so much. First the RUU close with an error, but i tried in another account of my pc and works (the same error was before when everything start, is funny, maybe thats save my phone from a brick because I was s-on with supercid :/ )
Thanks so much again for the help