Related
Hello,
i have a T-Mobile flyer 3G 32gb with original HC
Build-number 3.55.111.1
baseband 20.4803.30.0822U_3822.11.08.07M2
HBoot 1.11.0011
Radio 3822.11.08.07M2
CID T-MOB101
I want to S-off and flash a custom rom but i don't know the best, the right, way to do this. So it's possible to have S-Off with this device?
I downloaded the T-Mobile RUU but with this RUU i can't downgrade to GB.
The RUU updater say Error 140 and stopped.
So what can i do for S-Off?
devil-77 said:
Hello,
i have a T-Mobile flyer 3G 32gb with original HC
Build-number 3.55.111.1
baseband 20.4803.30.0822U_3822.11.08.07M2
HBoot 1.11.0011
Radio 3822.11.08.07M2
CID T-MOB101
I want to S-off and flash a custom rom but i don't know the best, the right, way to do this. So it's possible to have S-Off with this device?
I downloaded the T-Mobile RUU but with this RUU i can't downgrade to GB.
The RUU updater say Error 140 and stopped.
So what can i do for S-Off?
Click to expand...
Click to collapse
Hey man...
I have the EXACT same flyer, everything the same... Did you manage to get it s-off and rooted back to Honeycomb?? I have read all the forums, but I actually can't find a clear solution! Lemme know please or if anybody can put it simple! Thanks!
custom rom for flyer with stock hc
These steps would help :
- unlock boot loader over htcdev
- flash cwm with fastboot
- with cwm you're able to flash any custom rom (zip files)
It worked at least on my htc evo 3D.
Hey,
I have somewhat of the same question - but remain puzzled... I unlocked the Flyer's bootloader yesterday through HTCdev, flashed a Revolutionary recovery (based on CWM) through fastboot and could then install SuperUser through an update.zip in the stock ROM.
I have mode some development on other devices, so I'm familiar with bootloaders and stuff. The forums are mostly talking about S-OFF and I don't really understand how that concerns me, because now that my stock ROM is rooted, I can do whatever I like (remove bloat etc.). I may not understand all implications of S-ON, but I know that my bootloader tells me my Flyer is S-ON.
Now, is there any problem to flash another ROM through CW Recovery? Will, for example, LeeDroid's ROM replace anything connected to 3G (I have the model running on AWS frequencies, which are quite unusual). Could I simply flash LeeDroid's ROM, then get back to my stock backup without any problem?
I guess the question is; since my bootloader is unlocked, does S-ON or OFF concern me in any way? Or is S-OFF only important for those who can't unlock their bootloaders through HTCdev?
Thanks!
(I do promise to write something up for the wiki if ever I understand
S-On means you can't flash a custom ROM through recovery or ROM Manager. You can only flash using fastboot.
Thanks!
So considering that I just tried to downgrade to Gingerbread in Windows and that I got Error 155 (which seems to be undocumented - the message was à la 'something went wrong - I don't know what'), can I restore CW recoveries through fastboot as well?
I wouldn't mind to plug the cable, and S-OFF seems like an unnecessary hassle to me... (I just want OpenVPN and from here I took as much time trying to figure that out than I would need to compile the module myself).
I guess what puzzles me is this (from the LeeDroid thread): "If you have acheived S-Off via HTCDev, you will need to extract the boot.img from the Kernel.zip and flash it via fastboot"
I don't have S-OFF. I have an unlocked bootloader.
Does that mean that if I want to switch to LeeDroid I first have to fastboot flash boot.img and then install the rest through CW recovery?
Similarly, if I want to get back to stock, I fastboot flash the boot.img from my backup and apply the rest through CW recovery?
Thus: S-ON actually only prevents the boot partition to be changed outside from fastboot?
Thanks again!
redpoint73 said:
S-On means you can't flash a custom ROM through recovery or ROM Manager. You can only flash using fastboot.
Click to expand...
Click to collapse
Hm. I just did full restore with CW recovery.
And I had already applied update.zip's with the recovery.
ADD: SOLVED. What I wrote in the post above was right. I can apply any zip file, but CW can't write boot.img. Solution: fastboot flash boot boot.img.
All the rest works. In order to get back to a backup I guess it's the same way - flash boot.img, apply the restore.
cid: TMOB010 and HBoot 1.11.0011 Please Help Soff this thing.
I have the exact same problem and I assume I need s-off to make this work like a phone. Yes? Has anybody figured this out yet?
bud.
I'm on 3.14 stock ruu, unlocked bootloader, amonra in the recovery
do I need to flash something like the "3.14 stock deodexxed root"
or can I just finally try to s-off?
thanks <3
Watercycle said:
I'm on 3.14 stock ruu, unlocked bootloader, amonra in the recovery
do I need to flash something like the "3.14 stock deodexxed root"
or can I just finally try to s-off?
thanks <3
Click to expand...
Click to collapse
the su binary MUST be present in the system for the S-OFF process to work correctly, so yes, you must root.
Since you have Amon ra installed, just boot into that, go to the developer menu and install the su binary, then do S-OFF
a.mcdear said:
the su binary MUST be present in the system for the S-OFF process to work correctly, so yes, you must root.
Since you have Amon ra installed, just boot into that, go to the developer menu and install the su binary, then do S-OFF
Click to expand...
Click to collapse
unguarded or super user? and thank you i didn't know about that =)
Watercycle said:
unguarded or super user? and thank you i didn't know about that =)
Click to expand...
Click to collapse
Sueperuser not unguarded
this is the most rediculous process ever! (currently trying to wire trick) I'VE USED 2 DARN TYPES OF WIRE AND A PAPERCLIP AND NONE OF THEM DO ANYTHING
oh god, whew... i was running around the house making a wire out of everything...
but after trying the paperclip for like the 8th time (which took a half hour to find) it seems to have worked
S-off is the most stressful android activity ever >XO
thanks you two <3
You did use the ics jb hboot right? Make sure you can see the sd card? And don't unlock your phone again. You would need to s-on then s-off again for it to say locked. I just woke up and saw your new posts, its been a long day but I see you got help. Welcome to the club, glad it finally worked.
sent from my Clean Rezound
I used the Hboot that came with 3.14 Ruu, if S-off took the "relocked" away then i'm happy, if it didn't, oh well, but I was unlocked when I started the process =o
As long as you don't unlock it after s-off, it will be locked again ( although it says "juopunutbear" instead of "locked" if you're using their modified boot. Just flash a stock one and it will say locked)
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Watercycle said:
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Click to expand...
Click to collapse
The patched hboot adds some advanced fast boot commands. However everything will work without the patched hboot. You don't need it its just nice to have
Watercycle said:
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Click to expand...
Click to collapse
The juoponut bear hboot is an eng hboot that allows for adb commands and other options most people will not need.
The h boot issue is thus......in the event you want your phone returned to stock (s on and locked in downloader), after gaining s off do NOT HTC unlock the phone.
If you don't unlock it and want to return to stock you basically run a ruu, and then write the secure flag back to s on (scotty123 has a thread how to do this). After which point you phone will be on stock Rom, recovery and h boot will say locked and s on. Just like the day you first got the phone.
If you unlock after s off (as an early adopter I did) your bootloader will only say unlocked or relocked. You can run ruus, and write secure flag to s on.....BUT your hboot will say relocked or unlocked. And to a trained eye, someone can tell you tampered with it (running Roma,etc)
In my case, I had to follow scottys thread, s on, and do the s off process all over again. Early on we thought flashing a ruu would change the hboot status from relocked to locked. However we were mistaken.
So, don't unlock after s off.
If you can't run adb commands with your h boot and don't want to flash an eng hboot, use the ph98img.zip method to flash things (ex recovery, hboots, radios).
Sent from my Rezound
ericsignals said:
The juoponut bear hboot is an eng hboot that allows for adb commands and other options most people will not need.
The h boot issue is thus......in the event you want your phone returned to stock (s on and locked in downloader), after gaining s off do NOT HTC unlock the phone.
If you don't unlock it and want to return to stock you basically run a ruu, and then write the secure flag back to s on (scotty123 has a thread how to do this). After which point you phone will be on stock Rom, recovery and h boot will say locked and s on. Just like the day you first got the phone.
If you unlock after s off (as an early adopter I did) your bootloader will only say unlocked or relocked. You can run ruus, and write secure flag to s on.....BUT your hboot will say relocked or unlocked. And to a trained eye, someone can tell you tampered with it (running Roma,etc)
In my case, I had to follow scottys thread, s on, and do the s off process all over again. Early on we thought flashing a ruu would change the hboot status from relocked to locked. However we were mistaken.
So, don't unlock after s off.
If you can't run adb commands with your h boot and don't want to flash an eng hboot, use the ph98img.zip method to flash things (ex recovery, hboots, radios).
Sent from my Rezound
Click to expand...
Click to collapse
Well everything is right but the first part, the modified hboot allows you to perform fastboot commands that would otherwise require you to unlock the bootloader
Fastboot flash, fastboot boot... Etc.
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Well everything is right but the first part, the modified hboot allows you to perform fastboot commands that would otherwise require you to unlock the bootloader
Fastboot flash, fastboot boot... Etc.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Forgot to add that part when I typed the adb part ....thanks for correcting me.:thumbup:
Sent from my Rezound
oh dear, so without that Hboot command prompt won't be able to fastboot into recovery and whatnot?
Watercycle said:
oh dear, so without that Hboot command prompt won't be able to fastboot into recovery and whatnot?
Click to expand...
Click to collapse
Yes, but there are ways around that
I personally just package my own ph98img.zips if I need to flash a kernel or recovery after doing something dumb
Sent from my ADR6425LVW using Tapatalk 2
If you want to add the JB Hboot, it is very simple. You can go to their site and just download the most recent hboot. You must know if you are ICS or GB. But go here: http://unlimited.io/hboot-downloads/ and download the right one, either vigor ics or vigor gb. Put that in the folder where you had put the original controlbear program and follow these instructions:
To flash the JuopunutBear hboots
Put the phone in fastboot mode, connected to the pc and enter the following commands
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
Thats all there is to it and you can now benefit from the JB Hboot.
I thought you needed to be unlocked with htc dev to gain s-off? Now I'm hearing that I should not unlock my phone before I s-off?
Yes you need to be unlocked. It's part of the prerequisites. Please read then reread the thread in general "s-off with instructions...it's official". Understand how to avoid problems and fix them if they arise. It's very easy but it's like people half ass reading the instructions recently. Don't be that person.
sent from my Clean Rezound
th3rapist said:
I thought you needed to be unlocked with htc dev to gain s-off? Now I'm hearing that I should not unlock my phone before I s-off?
Click to expand...
Click to collapse
You have to unlock befor you s off, afterwards it's redundant to do so. But some people have
Sent from my ADR6425LVW using Tapatalk 2
doubleshot, ruby ICS, vigor ICS, holiday ICS, pyramid ICS?
which one? haha
I don't mind don't 1 more small flash that will probably be necessary in the future as long as it doesn't screw my current rom up
It's been awhile since I've had a chance to get back to xda, so when I saw the htc dev bootloader unlock method, I jumped at the chance to unlock my version 1.5 bootloader and be able to get root without downgrading. However, just a few days later, the Ics ota was released. I had
1. unlocked my bootloader VIA HTC dev method,
2. Flashed twrp from command prompt, and
3. Flashed Su from twrp.
In a nutshell, I had root but was on a stock 2.17 ruu (latest gingerbread ruu) and had root. In order to try to revert to stock, I used the command "fastboot oem lock" to relock my EVO (cdma) so i could ota update, because when i tried to with root, I simply was booted into twrp.
So, after locking (and also removing the recovery.img from my sdcard) my bootloader, I tried to ota, which only put me into my bootloader with a message under "relocked"(at the top of the screen in bootloader) which said "security warning". I've tried to run the 2.17 ruu when in fastboot (because it would only give me security warning otherwise) but there was pretty much no visible effect on my phone. The ruu said it ran successfully, but after booting up I still had Su, and none of my app data had been deleted. I also couldn't do a factory reset from the OS or from bootloader. If anybody could help me get to ics anything, or at least back to stock w/o root (,so i can apply the ota and go from there) it would be greatly appreciated.
As a sidenote, I haven't used the ruu.zip method (PG86IMG.ZIP).
Ryoma Echizen said:
It's been awhile since I've had a chance to get back to xda, so when I saw the htc dev bootloader unlock method, I jumped at the chance to unlock my version 1.5 bootloader and be able to get root without downgrading. However, just a few days later, the Ics ota was released. I had
1. unlocked my bootloader VIA HTC dev method,
2. Flashed twrp from command prompt, and
3. Flashed Su from twrp.
In a nutshell, I had root but was on a stock 2.17 ruu (latest gingerbread ruu) and had root. In order to try to revert to stock, I used the command "fastboot oem lock" to relock my EVO (cdma) so i could ota update, because when i tried to with root, I simply was booted into twrp.
So, after locking (and also removing the recovery.img from my sdcard) my bootloader, I tried to ota, which only put me into my bootloader with a message under "relocked"(at the top of the screen in bootloader) which said "security warning". I've tried to run the 2.17 ruu when in fastboot (because it would only give me security warning otherwise) but there was pretty much no visible effect on my phone. The ruu said it ran successfully, but after booting up I still had Su, and none of my app data had been deleted. I also couldn't do a factory reset from the OS or from bootloader. If anybody could help me get to ics anything, or at least back to stock w/o root (,so i can apply the ota and go from there) it would be greatly appreciated.
As a sidenote, I haven't used the ruu.zip method (PG86IMG.ZIP).
Click to expand...
Click to collapse
You don't need to upgrade to ics to get a custom ics rom, if that's what your asking. Reunlock, and check out the development forums and find an ics rom that works with 2.17 (eg, cool sense, meanrom, homebrew, common sense [my rom lol]). Go ahead and flash one, and enjoy ics
Stay on 2.17 though, first rule: NEVER accept ota. It's kinda rule of thumb. I learned the hard way.
Sent from my EVO 3DMA with a little "common sense"
I assume you're s-on..
You said you tried the ota and it took you to the hboot. Did it upgrade your hboot to 1.58?
I think the security warning is due to having a custom recovery (i think)
Wikd said:
I assume you're s-on..
You said you tried the ota and it took you to the hboot. Did it upgrade your hboot to 1.58?
I think the security warning is due to having a custom recovery (i think)
Click to expand...
Click to collapse
Yeah I checked out some other threads (none for the 3d though) and they said pretty much that it did have to do with the custom recovery like you said. And you are right on the other two counts, but no, it didn't upgrade me to 1.58, I'm still on 1.5.
Alright, thanks! I'll try to re-unlock using the HTC method(I'm assuming ill need to get another unlock_code.bin since the one I used isn't working anymore for some reason). I'll post again and let you know how it goes.
I searched for this and could not find an easy way to get an answer.
So I recently achieved S-OFF. In doing so I reverted back to an ICS RUU(3.14.605.12) after relocking the phone. After I got the phone back up and running I then set things up to run the program needed for S-OFF. Got S-OFF. Then unlocked the phone and flashed a rom I wanted.
I am thinking I would like to install the latest RUU(4.03.605.2) to get the radios and everything up to date.
Main question. Would installing the newer RUU affect the S-OFF status at all? I would hope no, but I don't know.
Second question. Do I need to go through the process of relocking the phone?
Sax1031 said:
I searched for this and could not find an easy way to get an answer.
So I recently achieved S-OFF. In doing so I reverted back to an ICS RUU(3.14.605.12) after relocking the phone. After I got the phone back up and running I then set things up to run the program needed for S-OFF. Got S-OFF. Then unlocked the phone and flashed a rom I wanted.
I am thinking I would like to install the latest RUU(4.03.605.2) to get the radios and everything up to date.
Main question. Would installing the newer RUU affect the S-OFF status at all? I would hope no, but I don't know.
Second question. Do I need to go through the process of relocking the phone?
Click to expand...
Click to collapse
The newest RUU will not effect your s-off. It will relock the bootloader, however. The only thing that this changes is the fact that you won't be able to issue fastboot commands. You can unlock with Vinylfreak's method or through htc dev again, but I find either of these to be unnecessary with s-off. You will not need to re-lock with s-off to run the ruu. Just place it on your sd card, flash in hboot, and you're good to go. Make sure after you flash the RUU to find a zip of Amon-Ra 3.15 that you can flash via hboot. Good luck!
Just to be clear. You WILL retain s-off after flashing RUU.
iamwalterwhite said:
The newest RUU will not effect your s-off. It will relock the bootloader, however. The only thing that this changes is the fact that you won't be able to issue fastboot commands. You can unlock with Vinylfreak's method or through htc dev again, but I find either of these to be unnecessary with s-off. You will not need to re-lock with s-off to run the ruu. Just place it on your sd card, flash in hboot, and you're good to go. Make sure after you flash the RUU to find a zip of Amon-Ra 3.15 that you can flash via hboot. Good luck!
Click to expand...
Click to collapse
Yea I have Amon-Ra 3.15 ready to go. Will do later on today.
Thank you.
Sax1031 said:
Yea I have Amon-Ra 3.15 ready to go. Will do later on today.
Thank you.
Click to expand...
Click to collapse
You're welcome. The AR 3.15 that you flashed through fastboot when you were setting up your phone doesn't work in hboot (just so you're aware). I don't want to be a broken record, I just want to make sure that you have everything you need. In this thread: http://forum.xda-developers.com/showthread.php?t=1615969 there is an hboot flashable of AR 3.15 in the op. It may also be useful if you have any problems after s-off.
After you achieve s-off you don't need to unlock again, even though the boot loader says that it's locked you still have access to everything. Once you are S-off you no longer need to relock to flash RUUs. From what I've seen it's not recommended to unlock via htcdev if you are s-off, I'm not sure of the reason though. To regain access to fast boot commands all you have to do is flash an unlocked/modified hboot. There is a thread in the dev section called "hex edited hboots" just download the ph from there and flash it via hboot.
brando56894 said:
After you achieve s-off you don't need to unlock again, even though the boot loader says that it's locked you still have access to everything. Once you are S-off you no longer need to relock to flash RUUs. From what I've seen it's not recommended to unlock via htcdev if you are s-off, I'm not sure of the reason though. To regain access to fast boot commands all you have to do is flash an unlocked/modified hboot. There is a thread in the dev section called "hex edited hboots" just download the ph from there and flash it via hboot.
Click to expand...
Click to collapse
The reason it's not recommended is because if you do, you'll get the relocked message if you lock again. If you don't unlock again, you'll have "locked" just like stock.
Sent from my Rezound using Tapatalk 2
I bought Evo which was already upgraded to ICS (OTA I assume), and it was branded I think. I've unlocked it via HTCDev, flashed '4ext touch recovery' and then rooted. Then I flashed MIUI ICS ROM, and everything is OK for now.
I want to use BootManager to flash multiple ROMs. It requires s-off. I tried it already with s-on, because I've read that SmartFlash (from 4ext recovery) makes my phone like s-off, so ROM on SD card installed, but won't boot. I had many problems going back to my Phone ROM, I restored my backup, wiped many times, installed fresh ROM and still had a bootloop. Finally I got it working again by flashing boot.img via fastboot (glad I did nandroid backup before). I didn't try again with different ROM, because after 2 hours of trying to recover my base ROM I've had enough. So I'm pretty sure BootManager will work better if my phone will be s-off.
So my question is - what to do next? We have so many guides and different comments here, sometimes the same method works for one, and doesn't work for another one, and I'm really confused.
I assume I should follow the instructions here http://forum.xda-developers.com/showthread.php?t=1743466 but I don't understand few things:
friend.evil said:
flash an ICS ROM from recovery(Method B from 10 to 14)
open ICS ROM.zip and extract boot.img to a folder which contains adb, fastboot and AdbWinApi.dll
go to fastboot and type:
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Do I have to do this if I'm already have MIUI with root privileges? Do I still need that boot.img from MIUI, and put it together with fastboot.exe?
Or should I restore stock ICS? I'm pretty sure I did nandroid backup before flashing MIUI.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
Do I need to fix hboot after s-off? What hboot version I have after doing steps 1 to 4 from section E? There's a big zip file (PG86IMG.zip), is it another ROM or what?
And most important question - if method D doesn't work, method F is recommended, but:
elias17 said:
Hboot s on will only flash roms that are based on ics 3.28xx and sense 4 roms using a special boot.img ! U can never flash GB roms until u go s off like i did its a tricky process but it works and now i can flash any rom in the gsm section
Click to expand...
Click to collapse
friend.evil said:
2_flash Leedroid GB ROM from recovery http://leedroid.ftp.rshost.eu/Shoote....zip(Don't forget to wipe data/factory reset and wipe cache + dalvik)
Click to expand...
Click to collapse
I don't get it - can I flash GB ROM or not if I have hboot 1.53.0007 s-on? Can I use method F if method D fail?
Sorry for my english, I'm from Poland.
Thanks in advance for any tip.
You're confusing yourself, What you need to do my friend is.
1. Download RUU, Run RUU
2. HTC Unlock bootloader again
3. Do the Juopunutbear Wiretrick to get s-off
4. Download the 1.04 ENG hboot (There is one of those for the GSM I think... not sure though)
5. Flash a badass Android 4.2.1 rom. They work.
There's much more detailed guides on what to do, BUT This is a summary of what you want.
Be sure to hit thanks [= I'm almost to 100
Which RUU should I search for? GB or ICS?
But isn't the 1+2 the same as restoring my ICS Stock ROM from backup?
I think hboot 1.49.0007 would be enough, I've read that BootManager works well with that version.
1. Yes you can just restore your stock ics backup BUT you will have to root it using the file provided in method B.
2. Yes the 1.49.0007 hboot is best for gsm
3. You can flash a GB rom with your hboot no problem. It just dont think it will boot. so technically you should be able to do the wire trick with a GB rom flashed(not booted into). You'll be in fastboot mode for the wiretrick. There are different files for GB and ICS when doing the wiretrick
Your best bet is to run an ICS RUU, unlock bootloader, root rom, do the wire trick, change hboot to 1.49.0007 and then flash any rom you want
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
mars28 said:
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
Click to expand...
Click to collapse
That should work But unlocking again is really easy
You should still have you unlock token in the same place,
You just plug up to the computer hop into fastboot usb and type
Fastboot flash unlocktoken Unlock_Code.bin
to unlock and then
fastboot flash recovery recovery.img
for a recovery,
Then move SU to your sd card and flash it in recovery.
Then your all ready for the wire trick, The more you do these things the more experience you get at them and the better you get with fastboot. I suggest you go through the process opposed to just restoring (First off it's much much safer) and you'll know the ropes if you (or anyone else) has this problem.
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
The token and the unlock code are specific to the phone, And doesn't change until you get a new phone.
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
you can easily get a new token from htc dev web site
Sent from my HTC EVO 3D X515m using xda app-developers app
Can't_Live_Without_My_Evo said:
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
Click to expand...
Click to collapse
I know I use shooter_u, I asked because I've found another RUU which have "Rogers_WWE" in name of the file, and the rest of the file name is identical, and I remember that I had to choose "rogers" when I was unlocking via htcdev. That's why I wasn't 100% sure if I had to choose "HTC_Europe" or "Rogers_WWE".
Another thing which confuses me:
http://forum.xda-developers.com/showthread.php?t=1495358
mpgrimm2 said:
Note 3: If you previously did the HTC Unlock, you'd have to "RELOCK" BEFORE running the RUU.
To do this from fastboot type: fastboot oem lock
Click to expand...
Click to collapse
Should I do this or start directly with RUU.exe? My phone is currently "UNLOCKED, hboot 1.53.0007, s-on".
And what about CID? I've read somewhere that I have to change to supercid or something, to be able to flash zips via fastboot. How to check my current CID?
Search for cid getter on play store to get your cid
You certainly need to relock you hboot before running RUU. For the correct ruu you should check the box that your phone came in. It should have the details (atleast i think so)
P.S. you probably don't need to change cid. Infact i'd recommend you not to do that just yet
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
mars28 said:
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
Click to expand...
Click to collapse
I think yours might be an european model. i had the exact same cid as yours.
when you get to that step of corrupted hboot just follow the steps on this thread and flash hboot 1.49.0007
http://forum.xda-developers.com/showthread.php?t=1906172
Cant kive without my evis comments about the wire trick are bang on. It will fix everything. Having s-off is just much easier so do the wire trick. It will work. My wife and I both have an evo. I had to do the wire trick twice on hers for it to work and four times on mine for it to work. Be patient if it fails the first few times. And if the screen gets stuck on the jounuo whatever screen you can fix that.
If you are stuck at Juopunutbear screen and if you can go to bootloader you need to connect the phone to pc, go to fastboot ( should say fastboot usb)*Go to controlbear folder (from where you ran controlbear to begin withon you pc then open command window in it (hold shift and right click, that willopen command window rigjt there and then*when you get into it you need to enter:
"ControlBear.exe -f" no quotes or "ControlBear f" notice the space after the exe !
Lots of peopke forget to put it in and say it didnt work.
I presume this will fix the problem
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
My phone is now s-off. I didn't flash RUU, just restored stock rooted ROM from backup, did the wire trick (just one time, surprisingly) and everything went nice and smooth. Then I flashed hboot 1.49.0007 with no problems at all. Thanks guys for the tips.
One more thing - my phone state is now "LOCKED" - should I bother?
So I got what I wanted - I've installed ROM in BootManager (the one which doesn't boot before, while phone was 's-on') and this time it booted from SD. Today I'll try more ROMs in BootManager.
Locked doesn't matter as long as you are s-off. It only creates problems if you ever plan on using fastboot commands. Trust me, you dont need to bother with it
But if you really want to know heres a quote from ramjet where he explains it a bit.
ramjet73 said:
Once the RUU.exe is run and the stock bootloader is installed, the phone will be bootloader S-ON regardless of the radio S-OFF status. To run fastboot commands like "flash" and "erase" the stock bootloader needs to be unlocked by the htcdev method or a custom bootloader modified to support those commands needs to be flashed, which requires radio S-OFF.
Click to expand...
Click to collapse