Hey
I wanted to know is there anyway to downgrade hboot with Stock RUU
I have right now 3.28.401.1 but i got something like this: 1.20.401.8
Is it okay, or can it brick my device.
Other solutions dont work, i have done it all
amdgamer1992 said:
Hey
I wanted to know is there anyway to downgrade hboot with Stock RUU
I have right now 3.28.401.1 but i got something like this: 1.20.401.8
Is it okay, or can it brick my device.
Other solutions dont work, i have done it all
Click to expand...
Click to collapse
use my guide. You will have to re root and re flash recovery. if u us an ruu, No chance of bricking your device it's only flashing the pg86img. Zip
http://forum.xda-developers.com/showthread.php?t=1906172
I'm sorry, i forgot to tell you that i have a S-ON and cant unlocked via htcdev
amdgamer1992 said:
I'm sorry, i forgot to tell you that i have a S-ON and cant unlocked via htcdev
Click to expand...
Click to collapse
I also had S-ON and was still able to unlock via htc dev.
hmmm actually you could try using the wire trick but i dont remember how it was called.
and with the wire trick i achieved my HBOOT downgrade from 1.53 back to 1.49 and S-OFF also.
Sent from my Evo 3D GSM using XDA Premium 4 mobile app
gesange said:
I also had S-ON and was still able to unlock via htc dev.
hmmm actually you could try using the wire trick but i dont remember how it was called.
and with the wire trick i achieved my HBOOT downgrade from 1.53 back to 1.49 and S-OFF also.
Sent from my Evo 3D GSM using XDA Premium 4 mobile app
Click to expand...
Click to collapse
can it mess my phone up or something else?
amdgamer1992 said:
can it mess my phone up or something else?
Click to expand...
Click to collapse
No it wont but doing such thing always requires caution
Here is a very good tutorial step by step from our xda member rizozizo:
http://forum.xda-developers.com/showthread.php?t=2694007
I used it myself and worked well
But yeah you wont achieve it at first try cause you will need to repeat maybe 2-8 more times (it took me 20 btw xD) but it will work guaranteed
You can also google for evo 3D wire trick for a video that is online to give you better understanding what you need to do
Sent from my Evo 3D GSM using XDA Premium 4 mobile app
tried all options like 5 days now, NOTHING Happens
Joupunut failed,unlock failed, tried different radios, failed
everything i tried just failed
How can you flash different radios when you're s-on?
Sent from my INM805ND using XDA Free mobile app
i just tried everything, i know that radio changing is impossible but i wanted to try because i'm so desperate with this s*it birick
amdgamer1992 said:
i just tried everything, i know that radio changing is impossible but i wanted to try because i'm so desperate with this s*it birick
Click to expand...
Click to collapse
juopunutbear will work, stay on stock rooted rom for the procedure, then patience is all you need
So something finally changed. I Used UnknownForce method to brick my device
I got now 1.49.0007 but without a ruu, everytime i wanted to install with ruu, it says that Error 131
I also tried to change cid but didn't work
Also tried the fastboot mode to push stock GB PG86IMG.zip on it, then it says CID ERROR and tried to change supecid or HTC__001 mode but i doesn't work. Allways errors
Press power to exit and like that. i can be only in bootloader, fastboot mode and recovery mode
With hboot 1.49.0007 you should be able to s-off with revolutionary.io
Afterwards install recovery.img in fastboot mode (4ext recommendet).
Then you free to flash any rom in recovery.
and when you'll s-off with rivolutionary you'll be able to flash unsigned/incompatible ruu
i can't do the rev.io thing. it says to install drivers but adb/fastboot works
adb is acting weird too, when i switch off my phone then connect usb, pc says that htc is connected and adb says device is offline.
fastboot works in fastboot mode
i think when i did Ultimate recovery Tool thing, it sayed to install stock GB ROM but i cant install
Ah yes, I think I remember.
For revolutionary you need a running rom.
AFAIK ruu error 131 means you have the wrong ruu for your phone (cid error).
Run "fastboot oem getvar all" in fastboot mode to get the infos for the matching gb ruu (carrier, hboot version, baseband).
tom0769 said:
Ah yes, I think I remember.
For revolutionary you need a running rom.
AFAIK ruu error 131 means you have the wrong ruu for your phone (cid error).
Run "fastboot oem getvar all" in fastboot mode to get the infos for the matching gb ruu (carrier, hboot version, baseband).
Click to expand...
Click to collapse
and check that the ruu is for SHOOTER_U and not for SHOOTER (CDMA version)! maybe you have wrong version, and phone is just saving itself from bricking :fingers-crossed:
Related
hi s-off my phone when the hboot was 1.49.0007
but after the ics update i re(s-on) my phone for the new ics update
but now the hboot is 1.53.0007 and can't make it s-off(Update sucks nothing special)
1_tried using unlimited.io but didn't work made an error my guess because it's ics
2_tried using GB ROM(Leedroid) didn't work
used fastboot flash boot boot.img still no luck (restarts every 5 seconds)
3_PG86IMG.zip fails (Main version is Older)
4_last shooter ruu error 140
Any advice? thank you
If you accepted an official OTA update, then you are likely now stuck in Hboot1.5-Hell. (I made this mistake many moons ago.)
You can try one of the many methods to downgrade your HBoot, but I don't know how that works with the official ICS update.
Sorry.
thanks for answering
hope there will be a solution soon
not much of a problem still can flash any ICS ROM Unless Sense 4.0
but if there are any other ideas please help
friend.evil said:
hi s-off my phone when the hboot was 1.49.0007
but after the ics update i re(s-on) my phone for the new ics update
but now the hboot is 1.53.0007 and can't make it s-off(Update sucks nothing special)
1_tried using unlimited.io but didn't work made an error my guess because it's ics
2_tried using GB ROM(Leedroid) didn't work
used fastboot flash boot boot.img still no luck (restarts every 5 seconds)
3_PG86IMG.zip fails (Main version is Older)
4_last shooter ruu error 140
Any advice? thank you
Click to expand...
Click to collapse
What error code did you get?
Sent from my PG86100 using xda premium
error 140 Bootloader version error
This may sound dumb like a dumb question but do you see super user in your apps?
Sent from my PG86100 using xda premium
That error could mean the update put your bootloader to stock I'm not certain of what your capable of doing at the moment but I do know to unlock the bootloader for hboot 1.5 you had to use the HTC unlock method and maybe you'll have to use it. I'm not an expert so this may not be the case but keep in mind you said your hboot is at a different value than previous to me it would only make sense to use the HTC method to unlock reestablish root the use the wire trick to get s-off. If you try this I wish you success. Sorry if this seems lacking but if I find something out I'll make sure you know
Sent from my PG86100 using xda premium
sorry non of that works
anyways
thanks for trying to help
friend.evil said:
sorry non of that works
anyways
thanks for trying to help
Click to expand...
Click to collapse
Did u tried the pg86img gingerbread with goldcard ?
Or the official pg86img with changed older hboot ?
Sent from my HTC EVO 3D X515m using xda premium
friend.evil said:
hi s-off my phone when the hboot was 1.49.0007
but after the ics update i re(s-on) my phone for the new ics update
but now the hboot is 1.53.0007 and can't make it s-off(Update sucks nothing special)
1_tried using unlimited.io but didn't work made an error my guess because it's ics
2_tried using GB ROM(Leedroid) didn't work
used fastboot flash boot boot.img still no luck (restarts every 5 seconds)
3_PG86IMG.zip fails (Main version is Older)
4_last shooter ruu error 140
Any advice? thank you
Click to expand...
Click to collapse
1_ you tried unlimited.io and it didn't work? Thats surprising to me.
2_ have you tried booting recovery from fastboot and flashing a gb rom? Fastboot boot recovery yourrecovery.img
3_ You can run an older ruu if you change your main version, but it still won't lower your hboot, your phone says its version "x.x.x.x" and the ruu is lower so it won't flash.
4_ you will never be able to lower your hboot unless you use a downgrade method like unknownforces brick/downgrade. If you put a lower hboot in the newest ruu, it won't run because you've broken the HTC signature. Id try the wire trick again if I were you.
Question, why did you s-on? I've taken ota's with s-off and as soon as I see the new hboot I just reflash the engineering hboot.
I have ~ the same problem as friend.evil, although he says he can run roms with Sense < 4, (if i understood correctly) while i can not.
I did try the lastest GB (provided by anryl) PG86IMG, with no luck (device always stuck in boot loop), but i do not have any goldcard (nor could i find one for evo 3d, but i did not google for it that much)
I am not sure about what you (anryl) mean by « official pg86img with changed older hboot ? » ?
Would an ICS RUU solve the problem ? I will probably also try to downgrade hboot if no other suggestions pops up =S
(More context: http://forum.xda-developers.com/showpost.php?p=28076870&postcount=231 )
espace.ariane said:
I have ~ the same problem as friend.evil, although he says he can run roms with Sense < 4, (if i understood correctly) while i can not.
I did try the lastest GB (provided by anryl) PG86IMG, with no luck (device always stuck in boot loop), but i do not have any goldcard (nor could i find one for evo 3d, but i did not google for it that much)
I am not sure about what you (anryl) mean by « official pg86img with changed older hboot ? » ?
Would an ICS RUU solve the problem ? I will probably also try to downgrade hboot if no other suggestions pops up =S
(More context: http://forum.xda-developers.com/showpost.php?p=28076870&postcount=231 )
Click to expand...
Click to collapse
I don't mean to be insensitive but if you s-on'd and then took a new ota then youve got a problem on your hands. An older ruu with an older hboot will do you no good as it won't flash unless you change your main version, and even if you do that it won't flash an older hboot, just an older system (gb). You should go ahead and check in to downgrading.
wikdNoob said:
I don't mean to be insensitive but if you s-on'd […].
Click to expand...
Click to collapse
(It has always been s-on)
espace.ariane said:
(It has always been s-on)
Click to expand...
Click to collapse
Gotcha, well you should consider downgrading to get s-off. It's much more trouble free than s-on. Are you gsm or cdma?
NVM, dumb question, lol, if you took an ics ota then you're gsm
Edit... After reading your post in the link provided, is say that an ics ruu would fix u up. I'm cdma so I wouldn't know where to find it at.
Thanks for you suggestions… But still, i don't understand why downgrading should be necessary : why would flashing a rom, stock or not be a problem for the bootloader ? Can we not write to system or flash the boot partition anymore (from fastboot, using fastboot flash boot boot.img ?) in 1.53.0007 ?
(And indeed, gsm forgot to mention, sry)
espace.ariane said:
Thanks for you suggestions… But still, i don't understand why downgrading should be necessary : why would flashing a rom, stock or not be a problem for the bootloader ? Can we not write to system or flash the boot partition anymore (from fastboot, using fastboot flash boot boot.img ?) in 1.53.0007 ?
Click to expand...
Click to collapse
You might be on to something there, some hboots don't accept commands that others do. I would think that if you changed your main version and then ran a gb pg86img, it would get you back to gb but it won't change your hboot.
Have you tried booting a recovery from fastboot with fastboot boot recovery.img?
You can't use radios, ruu's, or the juop s-off method with 1.53. It's like having a locked/unlocked boatloader.
Sent from my extremely under rated EVO 3d with a shiny aluminum bezel like the EVO 4g LTE on, you guessed it, Sprint!
kiewee3 said:
You can't use radios, ruu's, or the juop s-off method with 1.53. It's like having a locked/unlocked boatloader.
Sent from my extremely under rated EVO 3d with a shiny aluminum bezel like the EVO 4g LTE on, you guessed it, Sprint!
Click to expand...
Click to collapse
Sent from my HTC EVO 3D X515m using xda premium
the problem in JuopunutBear is that it keeps waiting for the device
tells me to check if adb and fast drivers are installed but i am positive they are
Is there a possibility for a GB ROM to work on hboot 1.53.0007?
I'm lost as to where to begin. I'm currently looking for sprints ics ota zip to try and flash and can't find it.
My phone is currently on Hboot 1.58 with S-on and no Rom installed. I can't install any old roms because of the hboot. Any direction would be helpful
sailow said:
I'm lost as to where to begin. I'm currently looking for sprints ics ota zip to try and flash and can't find it.
My phone is currently on Hboot 1.58 with S-on and no Rom installed. I can't install any old roms because of the hboot. Any direction would be helpful
Click to expand...
Click to collapse
Sounds like you're in a pickle. I don't think the ruu is out yet.
I can only think of 1 thing that'll work, although their might be other options. Try to downgrade your hboot using unknownforces method. I don't think you have to be in the android system for it to work.
Not sure if it works on hboot 1.58 but I don't see why it wouldn't.
wikdNoob said:
Sounds like you're in a pickle. I don't think the ruu is out yet.
I can only think of 1 thing that'll work, although their might be other options. Try to downgrade your hboot using unknownforces method. I don't think you have to be in the android system for it to work.
Not sure if it works on hboot 1.58 but I don't see why it wouldn't.
Click to expand...
Click to collapse
i can't attempt unknownforces method because i can't flash a .zip. It'll give an error about older/newer hboot before it starts updating.
also i've already tried using HTC's dev unlock, but it gives another error regarding older/newer hboot
Just install one of the new ROMs and do the wire trick to S-Off. Then you can downgrade your Hboot. Virus has a stock rooted ROM in the dev section. I used that ROM when I did the wire trick. Now I'm back on Devil Toast with eng 1.04 Hboot.
Edit- Just noticed you said you tried to do HTC unlock but can't. So you're saying you are S-On Locked without a ROM? How is that even possible?
sailow said:
i can't attempt unknownforces method because i can't flash a .zip. It'll give an error about older/newer hboot before it starts updating.
also i've already tried using HTC's dev unlock, but it gives another error regarding older/newer hboot
Click to expand...
Click to collapse
I wonder if you could brick it with a pg86img of hboot 1.58
Use the wire,trick I was in the same,situation now I'm s-off with my own Rom
Sent from my PG86100 using XDA
Mr nerd said:
Use the wire,trick I was in the same,situation now I'm s-off with my own Rom
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
I can't use juopunutbear's controlbear because i don't have su
Go to your computer open cmd and type cd\rootevo3dnew put your phone on fastboot mode connected to ye computer and type this fastboot boot cwm-4.0.1.4-shooter.img then go to bootloader and hit recovery
olivera1208 said:
Go to your computer open cmd and type cd\rootevo3dnew put your phone on fastboot mode connected to ye computer and type this fastboot boot cwm-4.0.1.4-shooter.img then go to bootloader and hit recovery
Click to expand...
Click to collapse
I can't boot a custom recovery. The phones LOCKED, Security Warning, Hboot 1.58 and S-on
Probably going to just bring the phone to the repair center, see what they can do
ok so just flash the PG86IMG.zip
---------- Post added at 06:25 AM ---------- Previous post was at 06:22 AM ----------
sailow said:
I can't boot a custom recovery. The phones LOCKED, Security Warning, Hboot 1.58 and S-on
i was having the same problem so i just put the PG86IMG.zip to my sd card i volume down and power button automatic the phone detect the zip
Click to expand...
Click to collapse
olivera1208 said:
ok so just flash the PG86IMG.zip
---------- Post added at 06:25 AM ---------- Previous post was at 06:22 AM ----------
sailow said:
I can't boot a custom recovery. The phones LOCKED, Security Warning, Hboot 1.58 and S-on
i was having the same problem so i just put the PG86IMG.zip to my sd card i volume down and power button automatic the phone detect the zip
Click to expand...
Click to collapse
AFAIK, there isn't one with the current hboot, or i can't find it
Click to expand...
Click to collapse
You can't HTC devunlock?? Even if you cant you should be able to flash a recovery I was able to flash one after I ota updated
Sent from my PG86100 using XDA
sailow said:
I can't boot a custom recovery. The phones LOCKED, Security Warning, Hboot 1.58 and S-on
Probably going to just bring the phone to the repair center, see what they can do
Click to expand...
Click to collapse
As long as your LOCKED S-ON, and not RELOCKED S-ON, take that thing to a repair center. If they don't have the Sprint ICS RUU (which I doubt they do) to restore your phone, they'll give you a new one.
Sent from my PG86100 using Tapatalk 2
triscuit1983 said:
As long as your LOCKED S-ON, and not RELOCKED S-ON, take that thing to a repair center. If they don't have the Sprint ICS RUU (which I doubt they do) to restore your phone, they'll give you a new one.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Same situation but I am unlocked hboot, s-on, 1.58, 4ext recovery... tried PG86IMG.zip into sdcard: a) with twr 1.1, it says older version b) with newer zip, it boots to hboot then loads then it goes back to hboot with no "press power" option.
I achieved S-Off on my Evo 4g LTE by downgrading from HBOOT 1.19 to 1.12. After doing this I stupidly ran RUU to upgrade from 1.13 to 2.23. Now my bootloader is showing the following:
EVITA PVT SHIP S-OFF RL
CID-########
HBOOT-1.12.2222
RADIO-1.12.11.0809
OpenDSP-v29.1.0.45.0622
eMMC-boot
It also has an incorrect IMEI, but a correct SN, and don't know about the MB there. All of them have barcodes as well.
Evita HBOOT on a jewel? The phone now only sits on the HTC Splash with the Dev warning red text.
Am i screwed?
evilmm85 said:
I achieved S-Off on my Evo 4g LTE by downgrading from HBOOT 1.19 to 1.12. After doing this I stupidly ran RUU to upgrade from 1.13 to 2.23. Now my bootloader is showing the following:
EVITA PVT SHIP S-OFF RL
CID-########
HBOOT-1.12.2222
RADIO-1.12.11.0809
OpenDSP-v29.1.0.45.0622
eMMC-boot
It also has an incorrect IMEI, but a correct SN, and don't know about the MB there. All of them have barcodes as well.
Evita HBOOT on a jewel? The phone now only sits on the HTC Splash with the Dev warning red text.
Am i screwed?
Click to expand...
Click to collapse
if the phone still is on .. u should be good :good:
evo401 said:
if the phone still is on .. u should be good :good:
Click to expand...
Click to collapse
Any idea on steps? I ran a TWRP backup but I cant get into recovery, just fastboot. I have tried fastbooting recovery and it says okay but it doesnt work. I also tried the RUU again and it does not work.
Are you sure you have the correct ruu? There is no version 2.23, our latest version is 2.13.651.1. Just throwing ideas out there.
metalfan78 said:
Are you sure you have the correct ruu? There is no version 2.23, our latest version is 2.13.651.1. Just throwing ideas out there.
Click to expand...
Click to collapse
Sorry I meant 2.13, I was at work and didn't have it in front of me.
When I run the RUU it does go into RUU recovery and scrolls across and give me successful at the end. But still no good. When i plug it into my windows computer it shows up as "HTC Android Phone USB Device".
Have you tried to install the updated hboot on the lazy panda Site. If you out the pj75img.zip on your sdcard card and reboot into the bootloader it should install. Then install twrp 2.2.2 the same way and install the rom of your choosing.
Sent from my A500 using Tapatalk
cruise350 said:
Have you tried to install the updated hboot on the lazy panda Site. If you out the pj75img.zip on your sdcard card and reboot into the bootloader it should install. Then install twrp 2.2.2 the same way and install the rom of your choosing.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Since its the wrong model it looks for PJ83IMG.zip. When I do this it reverts the HBOOT to 1.12.2222. When I do the same for TWRP it flashes but still won't boot to it.
What ruu did you run after you got s-off?
RUU_JEWEL_CLICS_40_S_Sprint_WWE-2.13.651.1_Radio_1.12.11.0809_NV_SPCS-2.45_003_release_277028_signed
Nevermind. You could always try the downgrade. It seems like its the same process, especially if you ran the wrong ruu and it pushed a different hboot.
roids87 said:
Nevermind. You could always try the downgrade. It seems like its the same process, especially if you ran the wrong ruu and it pushed a different hboot.
Click to expand...
Click to collapse
I ran the 1.13 and it took, i got into adb but could not get root (not surprised) I installed SuperSU and still couldnt get root. It seems like it runs the system underneath the splash. Sometimes the volume keys even play sounds like its adjusting. I rebooted and havent got back into adb.
Could the HBOOT just be miscommunicating with the hardware?
evilmm85 said:
I ran the 1.13 and it took, i got into adb but could not get root (not surprised) I installed SuperSU and still couldnt get root. It seems like it runs the system underneath the splash. Sometimes the volume keys even play sounds like its adjusting. I rebooted and havent got back into adb.
Could the HBOOT just be miscommunicating with the hardware?
Click to expand...
Click to collapse
I was talking about the hboot downgrade in the Original Development section. It won't be much of a downgrade, since your on the same hboot, but the process seems like it would set you back on track with the jewel.
roids87 said:
I was talking about the hboot downgrade in the Original Development section. It won't be much of a downgrade, since your on the same hboot, but the process seems like it would set you back on track with the jewel.
Click to expand...
Click to collapse
I cant downgrade without getting into adb as root
evilmm85 said:
I cant downgrade without getting into adb as root
Click to expand...
Click to collapse
Touche, I really can't be much help, sorry bro.
roids87 said:
Touche, I really can't be much help, sorry bro.
Click to expand...
Click to collapse
Ok. I fastbooted flashed twrp into recovery. rebooted into recovery. now i can ADB, but i dont have root. I adb installed the SuperSU.apk and rebooted back into recovery but still cant root
evilmm85 said:
Ok. I fastbooted flashed twrp into recovery. rebooted into recovery. now i can ADB, but i dont have root. I adb installed the SuperSU.apk and rebooted back into recovery but still cant root
Click to expand...
Click to collapse
alright somehow when i was in recovery and noticed i had the # (root) in the adb shell so I rewrote my apparently broken block 4 with the backup i made after S-off.
SUCCESS!
Now im booting into my system and my recovery. although no network access right now although it might have to do with firmware bits, I'm gonna try to RUU with 2.13 again.
Somehow u kept the OneX downgrade files even after the RUU which seems odd. Have u tried asking the people working on the downgrade process?
I'm sure they would be more helpful to you.
evilmm85 said:
alright somehow when i was in recovery and noticed i had the # (root) in the adb shell so I rewrote my apparently broken block 4 with the backup i made after S-off.
SUCCESS!
Now im booting into my system and my recovery. although no network access right now although it might have to do with firmware bits, I'm gonna try to RUU with 2.13 again.
Click to expand...
Click to collapse
Good stuff!
roids87 said:
Good stuff!
Click to expand...
Click to collapse
No network because my MSL MEID, username, uicc id, imsi phone number are all wrecked...
And I dont have my MSL...ugh
evilmm85 said:
No network because my MSL MEID, username, uicc id, imsi phone number are all wrecked...
And I dont have my MSL...ugh
Click to expand...
Click to collapse
Do you have the bakp4 file you made when you did the downgrade? This has all of the correct information in it.
Does your bootloader still say Evita?
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
hello friends...
i try this all method http://forum.xda-developers.com/showthread.php?t=1743466
and als try http://unlimited.io/ wire trick
not work ... for me
i want to s-off . bcz i am going bore with official ics ..
plz help me
Are you on the stock rom, or did you flash a modified one? If you are still on the stock rom, unlock your bootloader via www.htcdev.com and then try the wire trick again. I had to do it a lot of times, but it eventually worked. Just keep trying and eventually you will succeed
thanks
posedatull said:
Are you on the stock rom, or did you flash a modified one? If you are still on the stock rom, unlock your bootloader via www.htcdev.com and then try the wire trick again. I had to do it a lot of times, but it eventually worked. Just keep trying and eventually you will succeed
Click to expand...
Click to collapse
thanks bro from last 3 days i try more then 20 time but not work ...
i always stuck on juopuntbear screen after that adb not work ...\i don't know what should i do
i try restart my pc and mobile both so many time but not work for me
it sucks .....
thsnks for reply
faizan950 said:
thanks bro from last 3 days i try more then 20 time but not work ...
i always stuck on juopuntbear screen after that adb not work ...\i don't know what should i do
i try restart my pc and mobile both so many time but not work for me
it sucks .....
thsnks for reply
Click to expand...
Click to collapse
Did you get s off or not? Tell me exactly what you have done so far. I can give you step by step instructions and guide you through the process.
MrJyrks said:
Did you get s off or not? Tell me exactly what you have done so far. I can give you step by step instructions and guide you through the process.
Click to expand...
Click to collapse
thanks bro ....
i try with control bear box
my mobile going junpuntbear after that my pc not dedect my htc .... adb fail always
my phone is unlocked recovery installed
i want s-off
i also attached one picture ... stuck there every time....
wait for you tips
thanks
First of all, you must be on stock rom. Every sense 3.6 based rom should work. Did you run ControlBear as administrator?
If you did, run murder.bat from the attached .rar as administrator, wait till it's done. Try again. Still not working? Extract all the files from the rar to a folder. Run controlbear from there (run as admin). Give me feedback if it worked!
Edit: I have to upload the file somewhere else, it's over 8 mb so cant upload here.
Here's the link: https://docs.google.com/file/d/0B-fWg2dqIcnRT0xSZUdnVFRHeVk/edit?usp=sharing
Also It's a good idea to disable antivirus. I always do it as a precaution so I don't screw up anything.
If you need to know, the bat file searces for processes that may be interfering with controlbear and kills them.
Also none of this is my work, so all the thanks go to unlimited team.
MrJyrks said:
First of all, you must be on stock rom. Every sense 3.6 based rom should work. Did you run ControlBear as administrator?
If you did, run murder.bat from the attached .rar as administrator, wait till it's done. Try again. Still not working? Extract all the files from the rar to a folder. Run controlbear from there (run as admin). Give me feedback if it worked!
Edit: I have to upload the file somewhere else, it's over 8 mb so cant upload here.
Here's the link: https://docs.google.com/file/d/0B-fWg2dqIcnRT0xSZUdnVFRHeVk/edit?usp=sharing
Also It's a good idea to disable antivirus. I always do it as a precaution so I don't screw up anything.
If you need to know, the bat file searces for processes that may be interfering with controlbear and kills them.
Also none of this is my work, so all the thanks go to unlimited team.
Click to expand...
Click to collapse
thank you very much ....
i just use samsumg galaxy s3 data cable and every think work fine and finlly i did s-off thanks for you reply ...
Hello, I tried this junpuntbear s-off tutorial, but I'm stuck on junpuntbear boot. My pc can't find my phone from adb and it just stays there.
I unlocked with htcdev my bootloader, 4ext recovery installed, rooted. "Still not found device" etc... Any suggestion? I installed all drivers, fastboot/adb works fine. I installed mwakious3Drom 16.0.150_BASE_FINAL_RELEASE rom on my phone, is this the problem?
mhnx said:
Hello, I tried this junpuntbear s-off tutorial, but I'm stuck on junpuntbear boot. My pc can't find my phone from adb and it just stays there.
I unlocked with htcdev my bootloader, 4ext recovery installed, rooted. "Still not found device" etc... Any suggestion? I installed all drivers, fastboot/adb works fine. I installed mwakious3Drom 16.0.150_BASE_FINAL_RELEASE rom on my phone, is this the problem?
Click to expand...
Click to collapse
You need to go stock ROM first and then try s-off
Sent from my Evo 3D GSM using xda premium
simran420 said:
You need to go stock ROM first and then try s-off
Sent from my Evo 3D GSM using xda premium
Click to expand...
Click to collapse
Thanks for your reply, how can I go to stock ICS? Which RUU I must pick to flash? I'm from Greece. (GSM Model)
If I keep a Nandroid, can I restore it after s-off with wiping the stock rom? Or I must start from the begining?
Well, in theory any sense 3.6 based roms should work. Not sure about mwakiousrom though. To go completely stock you must flash a ruu as far as im concerned. Just download the appropriate ics RUU. Link
Since you are s on, lock bootloader with"fastboot oem lock". Run RUU. It will take a long time to finish. After that you must unlock bootloader from htcdev. Flash recovery. And finally, do the wire trick. After wire trick flash hboot 1.49. Link. You need to format all partitions except sd card after hboot change.
You can get the correct Europe ICS RUU from here -> http://www.androidfiles.org/ruu/sec...00U_11.25.3504.06_M_release_262714_signed.exe
MrJyrks said:
Well, in theory any sense 3.6 based roms should work. Not sure about mwakiousrom though. To go completely stock you must flash a ruu as far as im concerned. Just download the appropriate ics RUU. Link
Since you are s on, lock bootloader with"fastboot oem lock". Run RUU. It will take a long time to finish. After that you must unlock bootloader from htcdev. Flash recovery. And finally, do the wire trick. After wire trick flash hboot 1.49. Link. You need to format all partitions except sd card after hboot change.
Click to expand...
Click to collapse
I will do it with revolutionary because I know how revolutionary works (old Desire Z user ) but I need to downgrade hboot. In theory can I get a nandroid and restore after all this? Or the rom should be unstable?
You can restore stuff from a nandroid using this app
It restores apps/data, wifi settings, sms etc. It will require you to have a rooted rom. So in theory after you have done the wire trick you can flash a rooted rom and restore important stuff with this app
---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------
https://play.google.com/store/apps/details?id=com.rerware.android.MyBackup&hl=en
Another backup option
And just a reminder, wire trick sometimes corrupts sdcards. so save your backups before doing wire trick
Oh, your on hboot 1.49? Revolutionary tools needs 1.49 afaik. If so, get the gb RUU.
MrJyrks said:
Oh, your on hboot 1.49? Revolutionary tools needs 1.49 afaik. If so, get the gb RUU.
Click to expand...
Click to collapse
I'm downloading the GB RUU, I think...
Code:
RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed.exe
is that right?
and one last thing, I think my mobile is vodafone branded, CID VODAP102.
then you should flash a vodafone ruu. And what hboot do you have? you cant run a GB ruu on a phone with the ics bootloader(1.53)
EM|NEM said:
then you should flash a vodafone ruu. And what hboot do you have? you cant run a GB ruu on a phone with the ics bootloader(1.53)
Click to expand...
Click to collapse
I have 1.53.0007 hboot. how I can downgrade the hboot? any suggestion?
mhnx said:
I have 1.53.0007 hboot. how I can downgrade the hboot? any suggestion?
Click to expand...
Click to collapse
Gosh. Maybe there is a way, but i am not aware of it. It is certainly a lot more easier to do the wire trick.
MrJyrks said:
Gosh. Maybe there is a way, but i am not aware of it. It is certainly a lot more easier to do the wire trick.
Click to expand...
Click to collapse
Then I'm going to make the wire trick, just hoping the ics ruu will work to get stock back. How much fool am I?
EDIT: The
Code:
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
RUU doesn't work, It reads the software info, I press start and nothing happens to my phone.