Related
This may be a lame post, but I keep seeing people talk about how roms will not work if you used unrevoked. I don't understand why there would be a difference. If you root, install a Engineering SPL and a recovery image....after that you flash with whatever you want. Why on earth would it matter? Once you have an Engineering SPL, and your system partition is writable, you can wipe the whole phone and put what ever you want on...why on earth would it matter if you used unrevoked??
Am I missing something? Are people just assuming that you aren't fully rooted?? If so they should really be more clear.
root yes but unrevoked doesnt unlock nand
Maybe I misunderstood, I thought NAND was locked by the HBOOT and I thought that by replacing your SPL with the Engineering SPL you were changing the HBOOT version, thus unlocking NAND.
I don't think Toast's root process does this. I thought it was the same as unrevoked and simply gave your root access to user space on the os via su. I thought that regardless of which version you used to gain your root, you still had to use Toast's unlock nand process to load the Engineering SPL and gain full nand r/w and load a permanent recovery image.
I think this is just a misunderstanding from most people about os level root vs engineering SPL/nand unlocking. If so, I wish people would just start referring to it in their ROM posts as "you must have unlocked nand or be running the engineering SPL" vs tying that in with root, as it's pretty confusing. Maybe I'm wrong though, I haven't had my evo long and alot of my knowledge about root/SPL is from my previous experience with my mt3g.
Thanks
if you just run unrevoked you don't get unlocked nand, so you flash the engineering spl and you get unlocked nand so your not running "just" unrevoked, lots of people run unrevoked and never flash the engineering spl but they think they can run anything and everything, then they are surprised when they can't ... try just running unrevoked without unlocking nand and see what happens. if everything works properly let us know. Unrevoked just opens a hole while in HBOOT as soon as HBOOt is closed poof no more hole. so yes you can flash while the whole is open then try to read write to the /system and see what happens. Sorry this was a jumble ....
I had so many issues after running Unrevoked and even Simpleroot. It was my first experience with flashing new ROMs on any Android phone so I wanted to do it the "easy" way to save time.
The funny part is that I wasted so much time trying to get things working that the 20 minutes I spent doing it all from scratch were no big deal. Wish I had done it that way from the start.
Once I went through the 2 part method posted on this forum I have had no issues that weren't just related to unsupported features.
neodorian said:
I had so many issues after running Unrevoked and even Simpleroot. It was my first experience with flashing new ROMs on any Android phone so I wanted to do it the "easy" way to save time.
The funny part is that I wasted so much time trying to get things working that the 20 minutes I spent doing it all from scratch were no big deal. Wish I had done it that way from the start.
Once I went through the 2 part method posted on this forum I have had no issues that weren't just related to unsupported features.
Click to expand...
Click to collapse
Toasts?
I am pretty sure I want Amon-Ra...and not clockwork though. Hmm.
Sorry, yes it was Toast's method. All of the simplified versions gave me issues where certain things weren't done properly and since I hadn't done it manually with any kind of real feedback it caused issues down the line. I had to start over from the beginning to get things all working properly. Not sure where I screwed up but Toast's method fixed it.
I also use Amon RA's recovery. Only thing about that is that ROM updater that comes with Fresh's ROM doesn't want to work without Clockwork. I'll probably just delete it.
How do I COMPLETELY unroot EVO to send back to Sprint
Like s-off s-on plz help
If you rooted using Unrevoked 3.21 there is a thread listed in Android Development explaining the process as well as the needed links to download the needed zip files to turn S-On and the zip file to restore back to Stock Froyo 2.2
SouthernEvo said:
If you rooted using Unrevoked 3.21 there is a thread listed in Android Development explaining the process as well as the needed links to download the needed zip files to turn S-On and the zip file to restore back to Stock Froyo 2.2
Click to expand...
Click to collapse
Tbd but I used toast.method to root that used a lot of adb
mccurt29 said:
Tbd but I used toast.method to root that used a lot of adb
Click to expand...
Click to collapse
Ok but there are still methods in the forum for unrooting just like how you rooted. I would just do a search for them and choose which one you feel is the easiest for you to understand. Also if you are getting another EVO unrevoked 3.21 is as many in here have said easy peasy for rooting.
Good luck
playya said:
Ok but there are still methods in the forum for unrooting just like how you rooted. I would just do a search for them and choose which one you feel is the easiest for you to understand. Also if you are getting another EVO unrevoked 3.21 is as many in here have said easy peasy for rooting.
Good luck
Click to expand...
Click to collapse
Thanks!......
You need to run the RUU.exe found in the Dev section. It will do the trick.
Sent from my PC36100 using XDA App
novanosis85 said:
You need to run the RUU.exe found in the Dev section. It will do the trick.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Precisely. It can be found here:
*OFFICIAL* RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15. 00.09.01_NV_1.77_CNV_rel.
One thing to check first: do you have S-OFF? This would be the case if you ever ran Unrevoked Forever or Unrevoked 3.21. If so, you'll need to flash the Unrevoked Forever S-ON tool from recovery before running the RUU.
Noxious Ninja said:
Precisely. It can be found here:
*OFFICIAL* RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15. 00.09.01_NV_1.77_CNV_rel.
One thing to check first: do you have S-OFF? This would be the case if you ever ran Unrevoked Forever or Unrevoked 3.21. If so, you'll need to flash the Unrevoked Forever S-ON tool from recovery before running the RUU.
Click to expand...
Click to collapse
Thx guys I never used unrevok just toast methods but how do u check the A-on thing & should it be on or off
Also this 1 guy on this forum said he used the ruu & had s-on/off but Sprint still found out he rooted so should I wipe that ex--- >#366# stuff too?
mccurt29 said:
Thx guys I never used unrevok just toast methods but how do u check the A-on thing & should it be on or off
Also this 1 guy on this forum said he used the ruu & had s-on/off but Sprint still found out he rooted so should I wipe that ex--- >#366# stuff too?
Click to expand...
Click to collapse
Reboot into the bootloader (turn phone off, then hold power+volume down until it comes on). Then look at the end of the first line.
If it says SHIP S-ON, you're good.
If it says SHIP S-OFF, you need to run the Unrevoked tool.
If it says ENG S-OFF (which should be the case if you used Toast's method), it is indeterminate.
However, if you never used Unrevoked at all, you shouldn't have to worry about it. You can check after you run the RUU, which will reset it to the SHIP bootloader.
I believe the 3.29 RUU resets everything, including the PRI. Toast's method downgraded the PRI, and it was difficult to get it back before the current update, so this used to be a sure-fire way of telling whether you had rooted. Unless you had a bad Wimax flash and broke your 4G, I *think* you should be OK. But I don't know for sure.
Noxious Ninja said:
Reboot into the bootloader (turn phone off, then hold power+volume down until it comes on). Then look at the end of the first line.
If it says SHIP S-ON, you're good.
If it says SHIP S-OFF, you need to run the Unrevoked tool.
If it says ENG S-OFF (which should be the case if you used Toast's method), it is indeterminate.
However, if you never used Unrevoked at all, you shouldn't have to worry about it. You can check after you run the RUU, which will reset it to the SHIP bootloader.
I believe the 3.29 RUU resets everything, including the PRI. Toast's method downgraded the PRI, and it was difficult to get it back before the current update, so this used to be a sure-fire way of telling whether you had rooted. Unless you had a bad Wimax flash and broke your 4G, I *think* you should be OK. But I don't know for sure.
Click to expand...
Click to collapse
thanx that did the trick now to the sprint store tomorrow wish me luck
If your still having trouble then try this:
http://forum.xda-developers.com/showthread.php?t=780141&highlight=unroot
I just unrooted mine last night and it only took me 5 mins, just flash the unrevoked and then do the update on the PC36IMG and thats it.
Posting this to get it out in the community for anyone who wants it. This is the shipping hboot 1.04 patched to give s-off identical to the current ENG hboot everyone is using as well as including the ENG commands and fastboot flash/erase support. Obviously if you have a perfectly running device there might be no reason to flash this. For those who are yet to flash a hboot you might choose this instead since it's newer and we don't know what flaws could have been fixed from the older ENG release.
This will likely accompany our official root release for the device when we finish it.
I have tested this to be working on my phone, as well as another developers device so it should be safe. You however take full responsibility for anything that goes wrong with this flash as with any aftermarket mod.
IMPORTANT NOTE:
For those not aware, the thunderbolt is not a true s-off device. The ENG hboot or this patched hboot give you fake s-off while the radio is screaming s-on... This doesn't mean much, but DO NOT flash a hboot that isn't patched or you'll be stuck.
UPDATE 8/1/2011: This has been updated to now block normal hboot flashing to make it much safer. It's still wise to not arbitrarily flash things but you should rest a little more at ease now.
Thread update (not a new version):
Here is the commands to re-flash hboot after installing this:
"fastboot oem mw 8d08ac54 1 31302E30"
"fastboot flash hboot whateverhbootfile.nb0"
where whateverhbootfile.nb0 is in your path, you can get this file by unzipping the PG05IMG.zip with a hboot in it
(BE CAREFUL WITH THIS, YOUR PHONE WILL FLASH TETRIS.EXE AS A BOOTLOADER IF YOU ASK IT TO)
Enjoy.
Sweet thanks
Sent from my ADR6400L using XDA Premium App
Thank you sir, I shall try this soon.
This is not newer than the ENG, its actually the same version number. The ENG one came from a 1.12.605.6 eng ruu (same as shipping)
Will this block hboot flashing like the alpharevx one (please say yes)
Shadowmite said:
Posting this to get it out in the community for anyone who wants it. This is the shipping hboot 1.04 patched to give s-off identical to the current ENG hboot everyone is using as well as including the ENG commands and fastboot flash/erase support. Obviously if you have a perfectly running device there might be no reason to flash this. For those who are yet to flash a hboot you might choose this instead since it's newer and we don't know what flaws could have been fixed from the older ENG release.
This will likely accompany our official root release for the device when we finish it.
I have tested this to be working on my phone, as well as another developers device so it should be safe. You however take full responsibility for anything that goes wrong with this flash as with any aftermarket mod.
IMPORTANT NOTE:
For those not aware, the thunderbolt is not a true s-off device. The ENG hboot or this patched hboot give you fake s-off while the radio is screaming s-on... This doesn't mean much, but DO NOT flash a hboot that isn't patched or you'll be stuck.
Enjoy.
Click to expand...
Click to collapse
Ah, I guess I was under the impression it was older from what I was told. Regardless I never ran that one. Currently it doesnt block hboot flash, but I'll look into that patch next. I guess we'd want to block hboot from zip files but not from fastboot flash in order to protect soff while still having a way to return to stock.
Shadowmite said:
Ah, I guess I was under the impression it was older from what I was told. Regardless I never ran that one. Currently it doesnt block hboot flash, but I'll look into that patch next. I guess we'd want to block hboot from zip files but not from fastboot flash in order to protect soff while still having a way to return to stock.
Click to expand...
Click to collapse
I ended up not releasing the older one, as I had both (im not sure if joshua was given both or not).
Once you add blocking hboot flash (artificially high version number does it i think??) would it be ok to place in my guide until (if/when) yall release a package? (I intend to remove mine once a reliable "auto" is out).
Flashed for fun and it works great.
Having another method of root may not mean much to Tbolt owners now but it will once devices start shipping with GB.
Great to have you guys working on this.
so this a a way to root in the future for GB owners? just want to make sure so i dont flash if i dont need to because i am already rooted
Shadowmite said:
Ah, I guess I was under the impression it was older from what I was told. Regardless I never ran that one. Currently it doesnt block hboot flash, but I'll look into that patch next. I guess we'd want to block hboot from zip files but not from fastboot flash in order to protect soff while still having a way to return to stock.
Click to expand...
Click to collapse
excellent! i personally would love a permanent s-off patch. ill be watching this thread,thank you kind sir.
thanks,Shadowmite
Shadowmite said:
Posting this to get it out in the community for anyone who wants it. This is the shipping hboot 1.04 patched to give s-off identical to the current ENG hboot everyone is using as well as including the ENG commands and fastboot flash/erase support. Obviously if you have a perfectly running device there might be no reason to flash this. For those who are yet to flash a hboot you might choose this instead since it's newer and we don't know what flaws could have been fixed from the older ENG release.
This will likely accompany our official root release for the device when we finish it.
I have tested this to be working on my phone, as well as another developers device so it should be safe. You however take full responsibility for anything that goes wrong with this flash as with any aftermarket mod.
IMPORTANT NOTE:
For those not aware, the thunderbolt is not a true s-off device. The ENG hboot or this patched hboot give you fake s-off while the radio is screaming s-on... This doesn't mean much, but DO NOT flash a hboot that isn't patched or you'll be stuck.
Enjoy.
Click to expand...
Click to collapse
Hey,
Might you guys post your IDB of this hboot? or send it to me via PM? or somehow. Id love to see the breakdown of the file you guys reversed.
and what patches. Thanks!
Thanks shadowmite. I followed your work way back in the 6600 days...
Sent from my ADR6400L using Tapatalk
running it now,no issues. used it to flash a recovery,and change my radios. also verified it has the same available fastboot commands.
feel free let me know if you need any kind of feedback,or help with testing. id be more thaN happy to help test a permanent patch
Ok, updated main post with new updated hboot. Now patched to block normal hboot flashes which should make it a lot safer. To test, flash the update, then try flashing it again. The second one should not take.
yes! thank you kind sir. so,if im understanding correctly,it will prevent the flash of any other hboot,including the original engineering one?
downloaded and about to flash
scotty1223 said:
yes! thank you kind sir. so,if im understanding correctly,it will prevent the flash of any other hboot,including the original engineering one?
downloaded and about to flash
Click to expand...
Click to collapse
Correct. I figure eventually someone might need to flash back to a original and ill eventually toss up instructions how to do this. For now, this should block everything we've seen for the device to date.
Is revolutionary working on root for the thunderbolt? Will it give us true s-off?
from the first post,no it will not give us true s-off. im running it now,tried flashing the stock s-on hboot and the old eng hboot and it blocked them both
next question: if one installed a stock recovery,and accepted an OTA... would this prevent hboot from being overwritten there as well?
Yes it should always block hboot unless they do something purposeful to overcome the block method. I'll post a command in the first post sometime next week that will allow you to overwrite hboot should you want to.
NO LONGER TAKING Q'S. HAVE MOVED TO X8 FORUM!! HI everyone. i have started this thread as i didnt know what to do when i first had to send my wildfire back for repairs. first download the attatched zip. unzip to desktop and make sure u have got the drivers for your bootloader interface already installed. to do this you will need just two things. the zip you have just downloaded and the HBOOT which i included inside the ziped file. once extracted run the java file named S-ON.jar and plug your phone in and turn on fastboot. once connected make sure you click on check connection. once you have done that you should see your serial number appear. okay your ready to go. look for the first tab and click on it. then click on HBOOT/SPL. locate the HBOOT file you inzipped with the S-ON tool and then click it. once done just click on flash HBOOT/SPL. once done you will see it says FLASH HBOOT/SPL/SUCCESS. thanks for takuing time to look at my GUIDE and i hope it helps you. just remember one thing only flash the new HBOOT after you have installed the RUU which is android 2.2.1 so you can root again. and remember you can also get S-OFF again the exact same way
BEFORE you attempt to flash new HBOOT to gain s-on. please click start on your pc then goto run then in the dialog box type CMD. then you will have a pop-up it will be your command promt. in the command promt type
C:\fastboot>fastboot oem mb 9C068490 1 30 then hit enter. then open the s-on tool and flash the new HBOOT. then it will flash without FAIL. sorry for not realising this earlyer. and happy flashing.
comment if you need the bootloader drivers and i will upload them if requested thanks again everyone. and i would like to thank the acctuall creator of the programme thanks again briliant work on all sides.
i wil try it my Wildfire
here are the bootloader interface drivers..
enjoy thank me if this method helped you in your Quest to gain s-on
Did it worked for someone? I need to S-ON my wildfire, because i want to sell it
Edit: The WinRun.bat and LinuxRun.sh are wrong. They call the FastbootCommanderV.1.5.jar file, but they should call S-ON.jar
Question: What is eng hboot in your warning when the programm starts? I have the AlphaRev hboot 6.01.1002, will it work?
yesw i have done it on 5 diff wildfires i GUARENTEE it works mate hit me up on my thanks button
like i said this is not my programme i just found it very usefull to gain s-on. the only other way apart from this is to do it via the command promt on windows. which sucks as only a few people acctually know how to use this method. you dont need any of the linux stuff or win.bat. this method is for windows users only
For windows users only !!
this will only work on windows. wilol not work on linux. i am trying to get the programme to work on linux but to no avail. i will keep on trying but its just not capable of doing it. also please do NOT rename the HBOOT.NbO file if you do rename it then it will not flash and will not work.
i tried it, but when i will flash the hboot, i get this error:
Flashing "hboot" - PLEASE WAIT.
"hboot" flash FAILURE.
The device shows me: not roll back hboot version
DO NOT rename the file.
if you rename the file you will get a error. also make sure u have put your phone back to the stock RUU that is android 2.2.1 BEFORE you try this method
These are the RUU you need
go to this site and download the RUU that is used for your phone okay. go to this link and download the one for your phone. http://shipped-roms.com/index.php?category=android&model=Buzz
i have done this. my phone has 2.2.1 stock and i did not rename the file.
I think, i cant flash the hboot, because the alpharevx hbootversion is higher than the stock hboot...i think i read it somewhere...
no thats wrong the other way it to push it to the phone using fastboot and windows command prompt. this is the only 2 ways of gaining s-on again. trust me i have done it on my wildfire and 5 others and worked 1st time everytime
i will be shortly taking a video of me using this programme to gain s-on then you will all be able to see it working. it will not be untill my partner gets home but asoon as its uploaded i will share the url and let you all see that this way works 100% it is maybe somthing you are doing wrong ???? have you unzipped it to a sub fol;der on your desktop ????? and did you run it as admin ?? and if yes to them both. did you 1.rename the HBOOT file ?? or 2. did you move it out of the unzipped folder ???/
i trust you, but it get an error xD
edit: yes...i am an informatic specialist..i should know, what i should do and not..
lol. i dont know what to suggest then. it is odd because it has work flawlessly everythime i have flashed HBOOT/SPL. hmm i dont know then. i have done this method over 15 times to my own wildfire just to make sure it work 100% and could be used by other people. it has worked with alpharevx HBOOT and revelutionarys HBOOT which are both 6.01.1002 so its really weird it never worked for you :S
Strange...
An idea: I have the hboot from alpharevx from a very early closed irc beta. maybe this hboot is in some way locked. Can i flash the hboot with revolutionary again and use your tool? maybe the revolutionary hboot is different to the early closed irc beta :/
aslong as you know what your doing yes. it is possible. if you can get the revelutionary HBOOT then it will flash. then you should be able to flash the s-on HBOOT no problem
revolutionary dont let me flash their hboot -.- they say, i already s-off, so no flash needed -.-
ah i see, you said "if i can get the revolutionary hboot"...yep, i dont think, i can get the hboot
do you know the commands for flash the hboot manually?
do you know how to use command promt in windows ????
IMPORTANT INFORMATION!
READ THIS BEFORE GOING TO THE S-OFF THREADS
This simple guide is aimed at giving you the best chance at achieving S-OFF on your device. Although not all of the steps listed below are 100% necessary if you are failing to achieve S-OFF or still receiving errors of any sort then you either cannot S-OFF your phone or you haven't followed the guide. In my opinion your best hope for S-OFF is by using RUMRUNNER. It supports the largest amounts of firmware and the support is great.
You should only use MOONSHINE/REVONE to S-Off if......
1. You are on or flash a STOCK Sense 5, Android 4.1 ROM! (NOTE: 4.2 Software may be OK however for your best chances use the oldest you possibly can!!)
2. Have an old un-patched 1.44 HBoot or If on T-Mob or AT&T and on Patched 1.44 HBoot you have downgraded using one of the guides provided at the bottom of this post. (NOTE: To my knowledge patched 1.44 HBoot's are most likely those dated from June 2013 onwards, to check this reboot to bootloader and find the date there.)
3. Use the up to date 0.2.1 revone (the older ones give false successes)
4. Are Rooted (Not necessary but seems to improve chances of success)
5. Have the correct Moonshine package for your exact firmware and software version! If your firmware is not on the site and there is no way of you getting a matching firmware then you can't use it!
6. Are not on stock 4.2 software upgraded via OTA. (NOTE: Custom 4.2 Software may be OK as long as your HBoot is still 1.44)
7. Are not using a GE ROM, 4.3 Rom or on stock 4.3 software
8. Are not on HBoot 1.54 or higher
9. Are NOT on HBoot 1.54 or higher
10. ARE NOT ON HBOOT 1.54 OR HIGHER
11. Are not an Idiot! (Most important of all)
Before you try RUMRUNNER you must.....
1. Ensure you are on 100% Stock firmware/software that is supported. (note:you may be rooted or have custom recovery they should not effect success)
2. Ensure that if your device is carrier branded you are running stock firmware/software for your carrier (i.e H3G = 2.24.771.3)
3. Have your bootloader unlocked!
4. Use the correct RumRunner package for your device firmware. If you are not then flash Stock software matching your correct carrier firmware before starting.
5. Have HTC Sync removed from your computer!
6. Have firewalls, antivirus and anything else turned off or un-installed! (Ensure to turn back on after completion )
7. Have read the RumRunner thread and Site HERE and know you can email them with your firmware version so maybe they can S-OFF your phone! But DO NOT pester them on their IRC channel, that is for support only!!
8. Have more then 40% battery life.....
9. Not be an idiot! (Always the most important point!)
Notes:
1. If it still isn't working try a different stock rom and re-flash your correct stock firmware and try RumRunner again
2. If RumRunner gets to pouring (5)... Or higher it's more then likely failed already.
3. Some branded firmware's might work with the international package i.e 2.24.111.3 works with the 2.24.401.1 rumrunner package.
Again as I stated earlier some of these may not apply but if you want to guarantee revone or moonshine to work then you should follow these rules! Also in addition to this. READ THE OP of the threads in question (and POST 2 of revone!) They are your bible and will tell you what to do.
If you aren't sure what S-OFF is, does, why you might need it or how to achieve it safely then you DO NOT NEED S-OFF. You could ruin your phone and you really should start with more basic things first!!
WARNING Going back to S-ON isn't necessary for warranty, just lock the bootloader and go back to a stock rom/recovery if you do decide to be crazy and go S-ON again you may receive back a non-s-offable device that isn't supported by any of the above methods... YOU HAVE BEEN WARNED
Error codes and what they mean (from my experience, and what I've read!) ;-
Error Code -1 = Potentially you need to try a different ROM or it could just be random and after a few tries and reboots it might work. A few people have reported that rebooting and using -p rather than -P has worked but I'm not convinced as -p isn't built as a command but you're free to try whatever you wish.
Error Code -2 = I've seen people report this but revone has actually worked so should you see this try and reboot and carry on, if not then try changing ROMs and try again.
Error Code -6 = More then likely you're on either a patched or a 1.54 HBoot and you're not going to be able to S-Off. If you reboot to bootloader and you're on 1.44 then you might be able to downgrade using one of the guides on xda. Xboarder's guide on rootzwiki for TMob is a good one. In addition you may be on the right 1.44 HBoot but the software/ROM you're running could be the issue. In any case run a stock RUU for your CID and you should be sorted.
Error Code 1 = I've had this myself and this basically means it's not ever going to work. I think it's a variant on the -6 Error. If you see this, you're out of luck IMO.
Link for T-Mobile Device HBoot Downgrade to enable S-OFF HERE
Link for AT&T Device HBoot Downgrade to enable S-OFF HERE
Additional Info (On Downgrading HBoot from 1.54 with S-ON)
If after reading this guide you're thinking OK so I need to downgrade my HBoot, then to clear things up here is a list of methods that categorically do not and will not work to downgrade your 1.54 HBoot to 1.44 HBoot if your device is S-ON regardless of how much you think it should work because it did on your old phone.
Note these methods WILL NOT WORK to downgrade HBoot from 1.54 to 1.44 while S-ON!
1. Running an old RUU for your device with a lower HBoot inside
2. Writing directly to any of the board or hboot partitions mmcblk0p4, mmcblk0p5, mmcblk0p12. This includes:-
a) dd'ing your hboot/board image, editing the version then dd'ing it back
b) dd'ing any other hboot/board image to your hboot partition mmcblk0p12
c) dd'ing anything to anything!! HBoot and board are WP from low boot and cannot be written to or modified at all unless S-OFF
d) chmodding mmcblk0p12, deleting it, editing it, or anything else you might thing could work
e) using recovery to flash to mmcblk0p12 using busybox and dd command.
f) anything else I missed (I hope you're getting the picture here anyway) Oh and note, if you try to dd and it says it worked.... It didn't!
3. Modifying and flashing an encrypted or decrypted rom.zip, firmware.zip, PN07IMG.zip or RUU.zip from recovery, fastboot or RUU mode
4. Flashing an old encrypted or decrypted rom.zip, firmware.zip, PN07IMG.zip or RUU.zip from recovery, fastboot or RUU mode
5. Using a Y-Cable with or without a goldcard to flash an old PN07IMG.zip
6. Using a Y-Cable with or without a goldcard to flash a modified PN07IMG.zip
7. Running a modified RUU with old or editied HBoot version
8. *Not totally proven yet* Trying to brick the phone by shutting it off during RUU.zip install at the HBoot writing stage. (This has only been tried once so far and didn't pay off, I would not advise trying this unless you are a "VERY" confident/crazy android user/dev)
I hope this helps clear things up, have a nice day and happy flashing
The War Horse said:
OK so following my post of pretty much exactly this on the revone thread it seems that a lot of people still aren't sure what's going on so here is my simple guide to follow BEFORE you try to S-OFF your phone or post in the Revone or Moonshine threads.
You should/can only use revone or Moonshine(potentially different as I am not as familiar but I'm pretty sure the same rule apply) to S-Off if;-
1. You are on or flash a STOCK Sense 5, Android 4.1 ROM before you try!
2. Have an old un-patched 1.44 HBoot or If on T-Mob or AT&T and on Patched 1.44 HBoot you have downgraded using one of the easy to find guides provided.
3. Use the up to date 0.2.1 revone (the older ones give false successes) <revone only>
4. Are Rooted (Not necessary but seems to improve chances of success) <revone only>
5. Have the correct Moonshine package for your exact firmware and software version! If your firmware is not on the site guess what..... You can't use it! <moonshine only>
6. Are not using a 4.2 ROM
7. Are not using a GE ROM
8. Are not on HBoot 1.54
9. Are not on HBoot 1.54
10. ARE NOT ON HBOOT 1.54
11. Are not an Idiot! (Most important of all)
Some of these may not apply but if you want to garuntee revone or moonshine to work then you should follow these rules! Also in addition to this. READ THE OP of the threads in question (and POST 2 of revone!) They are your bible and will tell you what to do.
Notes on Error codes (from my experience, and what I've read!) <revone only>;-
Error Code -1 = Potentially you need to try a different ROM or it could just be random and after a few tries and reboots it might work. A few people have reported that rebooting and using -p rather than -P has worked but I'm not convinced as -p isn't built as a command but you're free to try whatever you wish.
Error Code -2 = I've seen people report this but revone has actually worked so should you see this try and reboot and carry on, if not then try changing ROMs and try again.
Error Code -6 = More then likely you're on either a patched or a 1.54 HBoot and you're not going to be able to S-Off. If you reboot to bootloader and you're on 1.44 then you might be able to downgrade using one of the guides on xda. Xboarder's guide on rootzwiki for TMob is a good one.
Error Code 1 = I've had this myself and this basically means it's not ever going to work. I think it's a variant on the -6 Error. If you see this, you're out of luck IMO.
I hope this clears things up. Please feel free to post your error code findings should they be any different from what I have stated. Also anyone familiar with moonshine please feel free to add anything I might have missed. Cheers.
Sent by homing dragon......
Click to expand...
Click to collapse
Can I get s-off with HBOOT 1.54???????? (joking BTW lol)
cheers for this should stop certain muppets asking silly things
Aditional Information - SuperCID
On a separate note If you are on an updated HBoot but SuperCID (11111111) Then the above rules may not apply. If this is the case for you and you are SuperCID, S-ON on HBoot 1.54 or Higher then you may have to try a few different routes as SuperCID bypasses some things on occasions. You may well be able to downgrade your HBoot and S-OFF.
exocetdj said:
Can I get s-off with HBOOT 1.54???????? (joking BTW lol)
cheers for this should stop certain muppets asking silly things
Click to expand...
Click to collapse
Lets hope so. Mods moved it from the Origional Dev forum though and I have a feeling a lot of Muppets will totally bypass this forum and go there and still crack on blindly...... Maybe if this was a sticky then it would be missed less.... I dunno..... MODS?
The War Horse said:
Lets hope so. Mods moved it from the Origional Dev forum though and I have a feeling a lot of Muppets will totally bypass this forum and go there and still crack on blindly...... Maybe if this was a sticky then it would be missed less.... I dunno..... MODS?
Click to expand...
Click to collapse
Think maybe you should put the title of the thread entirely in capitals and surround it with *********s or ###s so not even the dumbest noob will miss it lol!
exocetdj said:
Think maybe you should put the title of the thread entirely in capitals and surround it with *********s or ###s so not even the dumbest noob will miss it lol!
Click to expand...
Click to collapse
HAHA, I did actually try this but it converted the lot to lowercase randomly.... I assume you're not allowed all capitals? lol
The War Horse said:
HAHA, I did actually try this but it converted the lot to lowercase randomly.... I assume you're not allowed all capitals? lol
Click to expand...
Click to collapse
damn i assume so!!!! anyway soz for clogging up ur thraed mate! Try the symbols ~~~ *** (it will look like you are swearing at em hahaha!)
exocetdj said:
damn i assume so!!!! anyway soz for clogging up ur thraed mate! Try the symbols ~~~ *** (it will look like you are swearing at em hahaha!)
Click to expand...
Click to collapse
No worries man. Just spread the word. I've asked a mod if it can be stickied so we'll see.
posted a friendly link to this thread in the soff ones lol!
just have a look:laugh:
The War Horse said:
No worries man. Just spread the word. I've asked a mod if it can be stickied so we'll see.
Click to expand...
Click to collapse
the noobs dont even notice the stickies, they will still answer questions
IINexusII said:
the noobs dont even notice the stickies, they will still answer questions
Click to expand...
Click to collapse
I know. I'm thinking that at least from now on noone has to answer the questions though. they can simply send them to this thread lol.
I'd be better if this was in the Orig Android Dev forum imo, that way when they jump in there head first they might see it!
The War Horse said:
I know. I'm thinking that at least from now on noone has to answer the questions though. they can simply send them to this thread lol.
I'd be better if this was in the Orig Android Dev forum imo, that way when they jump in there head first they might see it!
Click to expand...
Click to collapse
the ONLY way is for XDA to automatically redirect the noobs to this thread whenever they click on a S-OFF thread. otherwise they wont see it
IINexusII said:
the ONLY way is for XDA to automatically redirect the noobs to this thread whenever they click on a S-OFF thread. otherwise they wont see it
Click to expand...
Click to collapse
Now that would be something!!
1.54 s off
just go my phone s-off on 1.54 h boot,check fone fun shop.was only achieved today.
doohdah said:
just go my phone s-off on 1.54 h boot,check fone fun shop.was only achieved today.
Click to expand...
Click to collapse
S-Off via jtag or by an external paid source is completely different to revone or moonshine. For one they're a lot cheaper!
Also the company you mention has been offering S-Off on the one for while now.
Sent from my HTC One using Tapatalk 4
good!:good:
1.54.s off
The War Horse said:
S-Off via jtag or by an external paid source is completely different to revone or moonshine. Fit's the onlone they're a lot cheaper!
Also the company you mention has been offering S-Off on the one for while now.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
For your information the 1.54.s-off was only achieved yesterday and is.by java card,it my be more expensive than revone but its the only solution at this time.
doohdah said:
For your information the 1.54.s-off was only achieved yesterday and is.by java card,it my be more expensive than revone but its the only solution at this time.
Click to expand...
Click to collapse
But by java card it is always possible, that's how htc does it, even on for the one x some shops offer it....
doohdah said:
For your information the 1.54.s-off was only achieved yesterday and is.by java card,it my be more expensive than revone but its the only solution at this time.
Click to expand...
Click to collapse
It was achieved by java card the day the phone was made. Lol.... Java card isn't an exploit.
Sent from my HTC One using Tapatalk 4