Anybody can help me find ROM 3.32.708.12. ? My phone is breaked and it is so important.
Thank for your help
marco1962 said:
Anybody can help me find ROM 3.32.708.12. ? My phone is breaked and it is so important.
Thank for your help
Click to expand...
Click to collapse
Do you mean stoc ROM? We need your CID to get it. to find it boot to bootloader and use the following fastboot command:
fastboot getvar cid
If you are unlocked and just want a ROM to flash, all ICS and JB ROMs are compatible.
astar26 said:
Do you mean stoc ROM? We need your CID to get it. to find it boot to bootloader and use the following fastboot command:
fastboot getvar cid
If you are unlocked and just want a ROM to flash, all ICS and JB ROMs are compatible.
Click to expand...
Click to collapse
RUU official ROM, with CID HTC_622
marco1962 said:
RUU official ROM, with CID HTC_622
Click to expand...
Click to collapse
Couldn't find exact ROM for you, but try this:
http://www.androidruu.com/getdownlo...0U_11.24A.3504.31_M_release_266490_signed.exe
astar26 said:
Couldn't find exact ROM for you, but try this:
http://www.androidruu.com/getdownlo...0U_11.24A.3504.31_M_release_266490_signed.exe
Click to expand...
Click to collapse
Dear Astra, so thanks for your help. But again I received ERROR [131]: ....
This is my boot loader screenshot. Hope this will help to solve my problem.
marco1962 said:
Dear Astra, so thanks for your help. But again I received ERROR [131]: ....
This is my boot loader screenshot. Hope this will help to solve my problem.
Click to expand...
Click to collapse
It seems that you re-locked your bootloader. Can you try to unlock it? it may help restore your phone without using an RUU. Use th following command:
fastboot oem unlock
Edit: also, how did you get to this situation? It might help solving it.
astar26 said:
It seems that you re-locked your bootloader. Can you try to unlock it? it may help restore your phone without using an RUU. Use th following command:
fastboot oem unlock
Edit: also, how did you get to this situation? It might help solving it.
Click to expand...
Click to collapse
The attached is result of command fastboot oem lock
and how was this this.
i was using Cygen ROM 4.2.2 for several months. one day stoped on boot screen. I tried to install ROM again but can not.
Final i tried to lock and use from official RUU, but all type of RUU give the erroe 131.
this is my story
To unlock ur bootloader again u will need to use the Unlock token again from htc dev.
jmcclue said:
To unlock ur bootloader again u will need to use the Unlock token again from htc dev.
Click to expand...
Click to collapse
now again Unlocked phone, even wrote CWM and installed stock ROM.
But after reboot stop on HTC logo, and don't do anything more.
i am going to became crazy.
marco1962 said:
now again Unlocked phone, even wrote CWM and installed stock ROM.
But after reboot stop on HTC logo, and don't do anything more.
i am going to became crazy.
Click to expand...
Click to collapse
Because you are on S-ON you need to flash the boot.img of the Rom via fastboot command or
flash 4ext recovery
Enable smartflash from it
Flash the Rom
Sent from my HTC Sensation Z710e using xda premium
Related
Hi all,
Lately I've dropped my phone a few times so now the screen is pretty messed up, but because I've got insurance I can make them repare it. I just wanted to make my phone completely stock again only i found out to late that I have to flash the stock RUU first and I ran the command "fastboot oem writesecureflag 3" (don't do this to your sensation!!) and as a result I can't flash the stock RUU and I also can't flash any other firmware, right now I'm on 1.23. I've also tried "fastboot oem writesecureflag 0" but it doesn't help.
Does anyone know what I can do?
Thanks in advance!!
Dutch-Guy said:
Hi all,
Lately I've dropped my phone a few times so now the screen is pretty messed up, but because I've got insurance I can make them repare it. I just wanted to make my phone completely stock again only i found out to late that I have to flash the stock RUU first and I ran the command "fastboot oem writesecureflag 3" (don't do this to your sensation!!) and as a result I can't flash the stock RUU and I also can't flash any other firmware, right now I'm on 1.23. I've also tried "fastboot oem writesecureflag 0" but it doesn't help.
Does anyone know what I can do?
Thanks in advance!!
Click to expand...
Click to collapse
why cant you flash stock RUU ? ..if you find a upgradable/incremental one ..you can happily flash it
go to this guide find your corresponding RUU and flash it
EDIT: consider yourself lucky that you didnt got a brick
ganeshp said:
why cant you flash stock RUU ? ..if you find a upgradable/incremental one ..you can happily flash it
go to this guide find your corresponding RUU and flash it
EDIT: consider yourself lucky that you didnt got a brick
Click to expand...
Click to collapse
Thanks for your guide but I've already tried flashing it and I can't flash anything via Hboot, that's why I'm stuck at 1.23. When I flash a RUU from my home screen I get error 171 after it tries to reboot the bootloader and when I try it from fastboot I get error 155, maybe that's because I'm on a AOSP ROM? I haven't been able to flash a sense ROM yet, I've tried 2.3.4 sense 3.0 and 3.5 4.0.3 sense 3.6 and 4.0 no positive results yet, it keeps looping the bootscreen of the ROM itself.
Dutch-Guy said:
Thanks for your guide but I've already tried flashing it and I can't flash anything via Hboot, that's why I'm stuck at 1.23. When I flash a RUU from my home screen I get error 171 after it tries to reboot the bootloader and when I try it from fastboot I get error 155, maybe that's because I'm on a AOSP ROM? I haven't been able to flash a sense ROM yet, I've tried 2.3.4 sense 3.0 and 3.5 4.0.3 sense 3.6 and 4.0 no positive results yet, it keeps looping the bootscreen of the ROM itself.
Click to expand...
Click to collapse
You should run the ruu from fastboot.. That's what guide says isn't it?
Also error 155 means either you ran ruu from normal screen or you have unlocked bootloader
So in your case.. You need to re lock bootloader if you did unlock using htcdev (to re lock fastboot oem lock)
Try the above and let me know
Also did you got the correct ruu based on your cid? If you followed the guide you would
Sent from my Sensation 4G using xda premium
Oh damn! You are my new hero and the best person out there! I was superCID and just flashed a RUU from fastboot and it finally worked!! Thank you so much for helping me fix my phone!!!!
Dutch-Guy said:
Oh damn! You are my new hero and the best person out there! I was superCID and just flashed a RUU from fastboot and it finally worked!! Thank you so much for helping me fix my phone!!!!
Click to expand...
Click to collapse
Glad it got worked
Anyways there is a way to say thanks in xda
Sent from my pyramid.. Through blazing fast sonic waves
Hi, I tried to install via RUU the new ICS ugrade released yesterday.
My Desire S is:
Unlocked bootloader
S-ON
hboot 2.00.0002
radio 3822.10.08.04_m
Recovery 4EXT touch v.1.0.0.5 RC5
Device Rooted
ROM Stock (Gingerbread)
The installation of the new ICS via RUU fails with error 155.
After removing battery and reboot all my data are still there, nothing has been removed.
Thanks for every helping suggestion....
Relock your bootloader using fastboot:
fastboot oem lock
chninkel said:
Relock your bootloader using fastboot:
fastboot oem lock
Click to expand...
Click to collapse
Many thanks.
Upgrade finished ok.
ICS RUU
Was on Stock GB Rom, downloaded the exe via the xda-link, connected, inatalled less tha 10 mins.
Not sure I like Sense 3.6 any better than 3.0???? Now for CM10 nightlies!
Thanks, XDA! (Because I have no idea what I'm doing, I research so much that eventually I don't know where exactly I got it or who specifically to thank).
romassi said:
Many thanks.
Upgrade finished ok.
Click to expand...
Click to collapse
What happened if I setup this RUU EU on my ARA ROM.
Will I be able to write in Arabic language?
Sent from my HTC Desire S using xda app-developers app
help
romassi said:
Many thanks.
Upgrade finished ok.
Click to expand...
Click to collapse
how i do fastboot oem lock?
cesar.villamizar said:
how i do fastboot oem lock?
Click to expand...
Click to collapse
fastboot oem lock
is the command you send to your mobile device
via terminal on pc...
look in to the index thread of our forum to find
all how to`s...
How to fix bootloader tempered...plz
ouadah77 said:
How to fix bootloader tempered...plz
Click to expand...
Click to collapse
S-OFF. RUU.
There's nothing really broken about it saying tampered. It just means you unlocked the bootloader.
exad said:
S-OFF. RUU.
There's nothing really broken about it saying tampered. It just means you unlocked the bootloader.
Click to expand...
Click to collapse
TNX exad .......But how do I install the Recovery with a new I in htc ... and also there is no fastboot and hboot How do I find
ouadah77 said:
TNX exad .......But how do I install the Recovery with a new I in htc ... and also there is no fastboot and hboot How do I find
Click to expand...
Click to collapse
It says fastboot USB in your picture. THat means it's in fasboot mode and connected to your PC.
fastboot flash recovery recoveryfilename.img
You are going to brick this phone if you don't read more my friend. It's quirky and bricking is more than a possibility if you don't know what you're doing.
My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you
jiteshgawali said:
My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you
Click to expand...
Click to collapse
if you are completely stock then i think you only option is to use a ruu.exe
http://forum.xda-developers.com/showthread.php?t=1672425
find the one which corresponds with your region and cid
rzr86 said:
if you are completely stock then i think you only option is to use a ruu.exe
http://forum.xda-developers.com/showthread.php?t=1672425
find the one which corresponds with your region and cid
Click to expand...
Click to collapse
Thanks rzr86
I looked into the thread you suggested. For my region and CID, I was not able to get the RUU from the thread. What I could get was this - an OTA zip file that matches my software version exactly (3.33.720.106) from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
How do I proceed further with this zip file, since I don't have an executable RUU file?
I am hoping you can be of help -)
(The zip file contains -- META-INF, patch, system, firmware.zip, fotaBoot, version.txt)
Get s off
Install custom recovery(4ext)
and flash any ics / jelly bean custom Rom
Itsakash said:
Get s off
Install custom recovery(4ext)
and flash any ics / jelly bean custom Rom
Click to expand...
Click to collapse
I was of the same opinion itsakash, but I am not sure if I can SOFF from the bootloader screen because I have only that option available with me. Can you please refer to me a good guide on this forum where I can SOFF from bootloader?
jiteshgawali said:
I was of the same opinion itsakash, but I am not sure if I can SOFF from the bootloader screen because I have only that option available with me. Can you please refer to me a good guide on this forum where I can SOFF from bootloader?
Click to expand...
Click to collapse
Yes u can s off from bootloader
Use KGS utility or ganeshp one click root. ,s off method Check general section in sensation forum
Connect mobile to pc on bootloader screen( mobile should say fastboot USB )
And follow instruction carefully
:thumbup:
Itsakash said:
Yes u can s off from bootloader
Use KGS utility or ganeshp one click root. ,s off method Check general section in sensation forum
Connect mobile to pc on bootloader screen( mobile should say fastboot USB )
And follow instruction carefully
:thumbup:
Click to expand...
Click to collapse
When I try and do SOFF using KGS utility, it restarts my phone because my phone is not HTC dev unlocked. (My phone's motherboard was replaced some time ago, and so I cannot unlock my phone.)
ganeshp's one click root requires SOFF. I can't SOFF using his technique because temp_root.bat doesn't work in bootloader screen.
I am in trouble, and don't look like getting out of it
jiteshgawali said:
When I try and do SOFF using KGS utility, it restarts my phone because my phone is not HTC dev unlocked. (My phone's motherboard was replaced some time ago, and so I cannot unlock my phone.)
ganeshp's one click root requires SOFF. I can't SOFF using his technique because temp_root.bat doesn't work in bootloader screen.
I am in trouble, and don't look like getting out of it
Click to expand...
Click to collapse
@ganeshp's one click root doesn't require htc dev unlock (meaning no prequisite permanent root; the guide has steps for temproot).
You just need one boot.
Do this: get the boot.img of your current (stock rom) and type fastboot boot boot.img.
jiteshgawali said:
My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you
Click to expand...
Click to collapse
I know its a long shot, but you should try doing a factory-reset from the bootloader, just in case it works.
Otherwise run an RUU from the bootloader.
firstly Itsakash he can't S-OFF because the device must be booted to the OS
secondly Far_SighT the command is fastboot flash boot boot.img
thirdly as raz0rf1sh suggested factory reset is a good idea and
fourthly jiteshgawali can you post your bootloader details?
It really is great to see your input guys.
@Far_SighT: I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
@raz0rf1sh: I have done factory reset several times from bootloader, doesn't help friend. I don't have an RUU for my region/CID, all I have is an OTA zip file for my phone from the link I have specified right above this. Can't seem to get an RUU for firmware base 3.33, and CID HTC__038.
@rzr86: Posting all the details I am aware of currently:
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
CID - HTC__038
Software version - 3.33.720.106
rzr86 said:
firstly Itsakash he can't S-OFF because the device must be booted to the OS
secondly Far_SighT the command is fastboot flash boot boot.img
thirdly as raz0rf1sh suggested factory reset is a good idea and
fourthly jiteshgawali can you post your bootloader details?
Click to expand...
Click to collapse
Nope
Not necessary to boot into os for s off
Itsakash said:
Nope
Not necessary to boot into os for s off
Click to expand...
Click to collapse
It would help if you can tell me how to do this or direct me to any specific guide
jiteshgawali said:
I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
Click to expand...
Click to collapse
Did u connected mobile to pc from bootloader??
If yes then I'm helpless may b rzr was right
But in s off section I read somewhere that it doesn't require boot into android
Anyway do PM to Ganeshp he is good guy. I'm damn sure he will help u
jiteshgawali said:
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
Click to expand...
Click to collapse
For stock rom go http://forum.xda-developers.com/showthread.php?t=1923629.
Get the rom and extract boot.img.
Then use the earlier command I posted.
Yes I haven't seen Indian version ruu until now ..so ruu is out of question AFAIK
Now the factory reset over boot loader should help if you have software problems but as per your replies it didn't work it seems
Tried HTC Dev unlock ? Even if the motherboard is replaced its worth a try
If htcdev unlock failed
Then try to go to recovery first ..from boot loader and if you went to recovery properly let me know
The other solution I propose is try to do change the cid ..even on locked bootloader sometimes it works
Try these commands one by one
fastboot oem writecid HTC__001
Then
fastboot reboot-bootloader
Then check cid using this command
fastboot getvar cid
If cid changed that's a good sign
Sent from my Nexus 7 using XDA Premium 4 mobile app
rzr86 said:
secondly Far_SighT the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
I said fastboot boot boot.im instead of fastboot flash boot booti.img as the previous one boots the rom with with the new image but doesn't attempt to write that to the boot partition. Hence it might get him a much needed boot to s-off.
jiteshgawali said:
It really is great to see your input guys.
@Far_SighT: I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
@raz0rf1sh: I have done factory reset several times from bootloader, doesn't help friend. I don't have an RUU for my region/CID, all I have is an OTA zip file for my phone from the link I have specified right above this. Can't seem to get an RUU for firmware base 3.33, and CID HTC__038.
@rzr86: Posting all the details I am aware of currently:
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
CID - HTC__038
Software version - 3.33.720.106
Click to expand...
Click to collapse
as you stated your current is 3.33.720.106 so the OTA update is unnecessary
do as ganeshp suggested
Itsakash said:
Did u connected mobile to pc from bootloader??
If yes then I'm helpless may b rzr was right
But in s off section I read somewhere that it doesn't require boot into android
Anyway do PM to Ganeshp he is good guy. I'm damn sure he will help u
Click to expand...
Click to collapse
both S-OFF guides say that stock rom is required in order to follow the S-OFF procedure
ganeshp said:
Yes I haven't seen Indian version ruu until now ..so ruu is out of question AFAIK
Now the factory reset over boot loader should help if you have software problems but as per your replies it didn't work it seems
Tried HTC Dev unlock ? Even if the motherboard is replaced its worth a try
If htcdev unlock failed
Then try to go to recovery first ..from boot loader and if you went to recovery properly let me know
The other solution I propose is try to do change the cid ..even on locked bootloader sometimes it works
Try these commands one by one
fastboot oem writecid HTC__001
Then
fastboot reboot-bootloader
Then check cid using this command
fastboot getvar cid
If cid changed that's a good sign
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for responding Ganesh. HTC Dev Unlock never worked for me post change of motherboard, but thanks for the suggestion.
I am able to browse the recovery option from bootloader properly.
And it gives me a little satisfaction to let you know that I was able to change the CID to HTC__001 following your steps. Can you suggest what I should be doing next?
jiteshgawali said:
Thanks for responding Ganesh. HTC Dev Unlock never worked for me post change of motherboard, but thanks for the suggestion.
I am able to browse the recovery option from bootloader properly.
And it gives me a little satisfaction to let you know that I was able to change the CID to HTC__001 following your steps. Can you suggest what I should be doing next?
Click to expand...
Click to collapse
Great now just download the HTC wwe ruu and install it... I'll link it up in a second.. Watch this space
Here is the link
http://htc.vi8.info/Sensation-XE/RU...0U-11.24A.3504.31-M-release-281004-signed.exe
Sent from my HTC Sensation 4G using XDA Premium 4 mobile app
Hello,
I have a HTC sensation, that i started rooting and install a custom rom - Kitkat from sultanxda.
All worked perfectly, only that one day i wanted to make a sim unlock, because it was locked in Vodafone Romania.
By mistake, i am not an expert, i've used the comand: fastboot oem writesecureflag 3
After this i've got my phone bricked...
I've found Unbriking projet on xda, and with a Linux I have managed on unbriking.
The problem is that now i have S-ON, and i cannot install another ROM, it works only with the ROM that wass installed before bricking.
I cannot get S-off, i have tried Juopunutbear method, but its not working, says to connect the device, and install drivers...
I have tried a lot of method's, i've tried installing a stock RUU, without luck...
I guess that i have to modify my firmware or hboot version, but as I was saying, i am no expert.
I can provide more information, if anyone can help me.
thanks
florinbv23 said:
Hello,
I have a HTC sensation, that i started rooting and install a custom rom - Kitkat from sultanxda.
All worked perfectly, only that one day i wanted to make a sim unlock, because it was locked in Vodafone Romania.
By mistake, i am not an expert, i've used the comand: fastboot oem writesecureflag 3
After this i've got my phone bricked...
I've found Unbriking projet on xda, and with a Linux I have managed on unbriking.
The problem is that now i have S-ON, and i cannot install another ROM, it works only with the ROM that wass installed before bricking.
I cannot get S-off, i have tried Juopunutbear method, but its not working, says to connect the device, and install drivers...
I have tried a lot of method's, i've tried installing a stock RUU, without luck...
I guess that i have to modify my firmware or hboot version, but as I was saying, i am no expert.
I can provide more information, if anyone can help me.
thanks
Click to expand...
Click to collapse
post now your bootloader details
rzr86 said:
post now your bootloader details
Click to expand...
Click to collapse
I made a print screen to be sure that i dont give u false information, hope its OK.
florinbv23 said:
I made a print screen to be sure that i dont give u false information, hope its OK.
Click to expand...
Click to collapse
does your bootloader says unlock/locked?
use these ruu.exe and see how it goes
http://fileom.com/gjssrzfjd7c6/RUU_....24A.3504.31_M_release_280871_signed.exe.html
http://fileom.com/m9b0o83qmnpv/RUU_....24A.3504.31_M_release_266171_signed.exe.html
it says unlocked, i am online now, and trying to find answers
thanks for the help, i will donwnload the ruu u provided me to see if i have luck
florinbv23 said:
it says unlocked, i am online now, and trying to find answers
thanks for the help, i will donwnload the ruu u provided me to see if i have luck
Click to expand...
Click to collapse
since it is unlocked you can still flash kitkat rom
just follow step 2 from this guide(flashing a recovery)
http://forum.xda-developers.com/showthread.php?t=1631861
then from 4ext format all partitions except sdcard
enable smartflash(because now you are on S-ON)
flash the rom
but if you still want to use the ruu.exe you must have to relock your bootloader first
then from 4ext format all partitions except sdcard
enable smartflash(because now you are on S-ON)
flash the rom
but if you still want to use the ruu.exe you must have to relock your bootloader first[/QUOTE]
i've relocked the bootloader, and now i try tu use the ruu.exe, hope it works...
florinbv23 said:
then from 4ext format all partitions except sdcard
enable smartflash(because now you are on S-ON)
flash the rom
but if you still want to use the ruu.exe you must have to relock your bootloader first
Click to expand...
Click to collapse
i've relocked the bootloader, and now i try tu use the ruu.exe, hope it works...[/QUOTE]
post results
rzr86 said:
i've relocked the bootloader, and now i try tu use the ruu.exe, hope it works...
Click to expand...
Click to collapse
post results[/QUOTE]
this error occured when the ruu,exe was updating signature, put an attachement...
could be because i have 3.24.401.1 firmware???
florinbv23 said:
could be because i have 3.24.401.1 firmware???
Click to expand...
Click to collapse
nope i gave you a ruu with higher firmware but the same region as yours
i don't know what is wrong
did you try both of them ?
edit: unlock the bootloader again and try flashing a rom from recovery
rzr86 said:
nope i gave you a ruu with higher firmware but the same region as yours
i don't know what is wrong
did you try both of them ?
edit: unlock the bootloader again and try flashing a rom from recovery
Click to expand...
Click to collapse
the second one didnt got... invalid link...
florinbv23 said:
the second one didnt got... invalid link...
Click to expand...
Click to collapse
are you syre?
i can download it fine
florinbv23 said:
the second one didnt got... invalid link...
Click to expand...
Click to collapse
i think i made a mistake first time, i used a ruu.exe with same firmware 3.24, it was an older one i had in downloads
now i try with the first one u gave me... hope it works
finally, i managed installing the ruu.exe u gave me, i hope that now i can get s-off... and make simunlock..
i will use this thread http://forum.xda-developers.com/showthread.php?t=1870233
thx you for helping me
i made a big mistake, as i was trying with the ruu.exe with the same firmware as i had, that is why i got that signature error.
the ruu.exe u gave me, made the upgrade and it works now )
i am so happy... i've tryed for 2 weeks on solving the problem.
florinbv23 said:
i think i made a mistake first time, i used a ruu.exe with same firmware 3.24, it was an older one i had in downloads
now i try with the first one u gave me... hope it works
Click to expand...
Click to collapse
that makes sense about signature error
florinbv23 said:
finally, i managed installing the ruu.exe u gave me, i hope that now i can get s-off... and make simunlock..
i will use this thread http://forum.xda-developers.com/showthread.php?t=1870233
Click to expand...
Click to collapse
why don't you try with this S-OFF guide?
http://forum.xda-developers.com/showthread.php?t=1661631
there is no need to unlock the bootloader again
rzr86 said:
why don't you try with this S-OFF guide?
http://forum.xda-developers.com/showthread.php?t=1661631
there is no need to unlock the bootloader again
Click to expand...
Click to collapse
I will try it tomorow
thx again