Related
seems that someone has obtained to have s-off on desire ! have a look at this . maybe the n1 would be the next (i hope).
It's not needed on the N1, S-OFF for the Desire is the same as the N1 with an unlocked bootloader.
yeah, but with an s-off hboot we could relock the bootloader.
100% completely irrelevant on the N1.
Also, you can't re-lock the boot loader, it is permanent, per the warning you were given when you did it.
What if I want to reflash the unlocked splash screen with the locked one for cosmetic reasons (to hide the lock)? It is a little bit relevant.
G0belet said:
What if I want to reflash the unlocked splash screen with the locked one for cosmetic reasons (to hide the lock)? It is a little bit relevant.
Click to expand...
Click to collapse
That is something I had thought about doing, I must admit.
I didn't try it, but looked for it for completely another reasons (changing the splash screen). Looks like you can't flash "splash1" partition on Nexus, it fails. If you want - you can download splash1.img from any resolution-compatible device (EVO, for example), and try to flash.
Even with S-OFF:
Code:
C:\Users\Rusty\Desktop>fastboot flash splash1 evosplash1.rgb565
< waiting for device >
sending 'splash1' (750 KB)... OKAY [ 0.166s]
writing 'splash1'... FAILED (remote: not allowed)
finished. total time: 0.237s
That answers that then.
I never tried to downgrade my HBOOT but if I'm not mistaken, there's a way to flash mtd1 if my memory serves, and before upgrading you see the HTC logo instead of the Nexus One logo. Again I never had to downgrade my HBOOT but I think there might be a way to see how that img file works, and see if we can change the splash. That's a wild guess at this point.
EDIT: I mean mtd0. Can't we dump it to see what's in it?
The new G2 permroot procedure seems to involve running some sort of kernel module which then allows you to reflash HBOOT with an engineering bootloader and get S-OFF. If you subsequently restore to stock using PC10IMG.zip, the stock bootloader relocks to S-ON.
Would this not be theoretically possible with the N1? There are Nexus One units out there with an engineering bootloader that can go to S-OFF without a permanent watermark. If the ENG HBOOT can be flashed from inside the OS, it could be a way to get S-OFF reversibly.
The ENG HBOOT on the Nexus One is larger than the SHIP one, so apparently it's a no go.
G0belet said:
I never tried to downgrade my HBOOT but if I'm not mistaken, there's a way to flash mtd1 if my memory serves, and before upgrading you see the HTC logo instead of the Nexus One logo. Again I never had to downgrade my HBOOT but I think there might be a way to see how that img file works, and see if we can change the splash. That's a wild guess at this point.
EDIT: I mean mtd0. Can't we dump it to see what's in it?
Click to expand...
Click to collapse
You have HBOOT images (FRG83 and KO-KR FRF91 came with HBOOT 0.35 update, for example), so you don't need to try to dump them. Nobody invested time in hacking them, I believe, because it's not a priority work.
You can customize the partition sizes through command line, but it doesn't override things for fastboot itself - making it impossible to update HBOOT with Eng HBOOT, which is larger and doesn't fit on the HBOOT partition.
I'm not sure MTD0 flashed to MISC partition does anything to HBOOT itself. If it does - it might be possible to flash Desire S-OFF HBOOT on Nexus and deal with the differently partitioned ROM (or revert back to Nexus partitioning with command line override method). Anyway, it won't really bring Nexus back to stock, so it misses the point for all those that want to have their bootloader relocked. Even with substituted splash1 to match locked Nexus, going into bootloader will show a version Nexus doesn't have. Flashing back Nexus HBOOT will return the "unlocked" sign, since it wouldn't be locked.
And it looks like Desire HBOOT is still within the smaller partition size and doesn't enlarge it to fit Nexus Eng SPL.
Jack_R1 said:
I'm not sure MTD0 flashed to MISC partition does anything to HBOOT itself. If it does - it might be possible to flash Desire S-OFF HBOOT on Nexus and deal with the differently partitioned ROM (or revert back to Nexus partitioning with command line override method). Anyway, it won't really bring Nexus back to stock, so it misses the point for all those that want to have their bootloader relocked. Even with substituted splash1 to match locked Nexus, going into bootloader will show a version Nexus doesn't have. Flashing back Nexus HBOOT will return the "unlocked" sign, since it wouldn't be locked.
And it looks like Desire HBOOT is still within the smaller partition size and doesn't enlarge it to fit Nexus Eng SPL.
Click to expand...
Click to collapse
I checked, turns out mtd0 contains UART settings and the phone's CID... I can't see anything about logos and such.
Still, I think we could have a modified HBOOT with extended commands, making flashing splash0 and splash1 doable. And if we flash HBOOT back to the stock one through flash_image, it won't flash the splash screens again, so the splash change will stick. If you flash the one without a lock (splash0 I imagine) over splash1, and go back to stock HBOOT, won't it just stick?
This is just thinking here. Still, we need some kind of ENG HBOOT, or at least backport some functions of the ENG HBOOT to the SHIP one to allow splash screen flashing.
Also, the goal here is not necessarily to go back to stock and relock the bootloader in any way. It's mostly because the lock bugs me, and if there was a way to hide it, I'd gladly do it. I don't care about my bootloader not being the same anymore, or my phone not being stock I just like the clean look of the Nexus logo without the lock.
There is only one splash partition, there is no splash0 on those phones, AFAIK.
The thing is very simple: playing with HBOOT isn't safe - which means, if you flash a wrong one, your phone is done. Devs don't bother working on it, and rightfully so - when they have tasks of much higher priority, like G2's eMMC, they don't bother working on something that works already. I'm not going to be the one that tries flashing Desire HBOOT without certain knowledge, what will it do to Nexus - I don't live in Nexus-supported country. If you have a spare Nexus and are willing to exercise its warranty - flash Desire Eng HBOOT and see if it works.
I thought spcustom was basically splash1 with the lock, but turns out it's the screen that shows when you "fastboot oem unlock".
This is the bottom 768000 bytes of spcustom.img I found in a PASSIMG (most of you know that screen already though):
Maybe HBOOT actually adds the lock at the bottom of the screen. Or HBOOT composites the bottom part of spcustom and splash1. Can't say, I'm no engineer.
I actually know it's dangerous to do all this, and once again it's just a thinktank. I'm just trying to locate anything that could help more knowledgeable people to start working on this.
cmstlist said:
The new G2 permroot procedure seems to involve running some sort of kernel module which then allows you to reflash HBOOT with an engineering bootloader and get S-OFF. If you subsequently restore to stock using PC10IMG.zip, the stock bootloader relocks to S-ON.
Would this not be theoretically possible with the N1? There are Nexus One units out there with an engineering bootloader that can go to S-OFF without a permanent watermark. If the ENG HBOOT can be flashed from inside the OS, it could be a way to get S-OFF reversibly.
Click to expand...
Click to collapse
What it does is toggles power to the mmc and then force it to reinitialize as if suspended to disable the write-protect of the emmc. The N1 doesn't use emmc though so I think the protection of the hboot is done in some other way.
Rusty! said:
The ENG HBOOT on the Nexus One is larger than the SHIP one, so apparently it's a no go.
Click to expand...
Click to collapse
From what I've heard, the hboot partition on the retail N1s is actually the same size as the eng hboot. Open the eng hboot in a hex-editor and you'll see there is quite a lot of padding at the end and various other places. It might fit.
i read in general or q/a that someone did a warranty on there n1 and got it back a lock bootloader again, they had it unlocked. this was some ways back.. but there is a way to relock it, as there is some cases with ppl that have a unlock boot still get warranty and get it back with a lock boot...
Jack_R1 said:
There is only one splash partition, there is no splash0 on those phones, AFAIK.
The thing is very simple: playing with HBOOT isn't safe - which means, if you flash a wrong one, your phone is done. Devs don't bother working on it, and rightfully so - when they have tasks of much higher priority, like G2's eMMC, they don't bother working on something that works already. I'm not going to be the one that tries flashing Desire HBOOT without certain knowledge, what will it do to Nexus - I don't live in Nexus-supported country. If you have a spare Nexus and are willing to exercise its warranty - flash Desire Eng HBOOT and see if it works.
Click to expand...
Click to collapse
Yes, it isn't safe to muck around with HBOOT.
I bricked my desire by flashing a corrupt HBOOT patch, but it was my fault for not checking the md5.
And I would do it again. (But a checked file ;-))
so a couple of days ago i accidently flashed wrong radio and spl to my mytouch. I've created a gold card but everytime im in fastboot it never picks up the SAPPIMG.IMG it always says."Loading no Image." so what do i have to do get it back to stock everything? and yes i've googled multiple threads
Try to install new SPL, Radio and Hboot with Radio Switcher: http://forum.xda-developers.com/showthread.php?t=794450
Enter Fastboot, plug in USB, start the Radio Switcher and flash the files. Try couple of times and in different order if it doesn't work at first.
My Touch 3g 1.2/Fender
catracho713 said:
so a couple of days ago i accidently flashed wrong radio and spl to my mytouch. I've created a gold card but everytime im in fastboot it never picks up the SAPPIMG.IMG it always says."Loading no Image." so what do i have to do get it back to stock everything? and yes i've googled multiple threads
Click to expand...
Click to collapse
I have had similar problems before but when trying to un-root. I successfully fixed mine by using the ENG. SPL 1.33.2010. All attempts at using my Goldcard failed (the same goldcard I rooted the phone with I know it's good) so I flashed the ENG. SPL and everything worked. Hopefully your ENG SPL is functional your radio and original SPL will be restored when you fastboot the SAPPIMG.zip.
Look at your SAPPIMG you can't use the .nbh for the older magics.
PS- If you need help don't hesitate to E-mail me I do not want you to brick your device. If you need to go to Cyanogen Mod forums I'm in Dream/Magic Themes mostly my E-mail is there on my profile, GOOD LUCK.
First and foremost, this is the wrong section to be posting this topic.
Secondly, how are you guys telling him to flash stuff without even knowing what he's got right now?
With that being said, boot into fastboot holding back+power and post what you see there.
Sorry about that and it says 32B unknown eng-off
Sent from my SGH-T959 using XDA App
I must have missed the part where I only asked for the first line. I'm not trying to flame but come on dude. We need to know everything that shows up there.
Sent from my HTC Magic using Tapatalk
Ok again sorry i was at work
SAPPHIRE UNKNOWN 32B ENG S-OFF H
HBOOT-1.33.2010 (SAPP31000)
CPLD-13
RADIO-2.22.23.03
Jun 2 2009,17:27:03
Sent from my SGH-T959 using XDA App
Moving to General.
Start at step 4. I'm assuming you still have ADB installed.
Is there already a tool for Rooting the HTC Magic automatically?
I'm looking at making a tool that will do everything needed to get HTC Magic rooting with minimal knowledge needed by the user.
This was my first Android Phone and I rooted it no problems the 2nd time around. My first attempt resulted in a hard brick. I was lucky and the phone was replaced. My second attempt went better and I was able to sucessfully root, install Amon_RA recovery, flash Eng SPL, Custom ROM.
I was hoping to help make the process a little more "foolproof" for first timers.
I searched the forums here and have yet to find such a tool.
With help and suggestions I would like to make this program support multiple phone models both HTC and beyond.
Superoneclick. Roots in... well... one click
superoneclick seems to work pretty well, not sure if there others like it.
Yeah. SuperOneClick is the best and easy.
SuperOneClick is good for rooting but it doesn't flash an Engineering SPL or ROM.
SithLord2K said:
SuperOneClick is good for rooting but it doesn't flash an Engineering SPL or ROM.
Click to expand...
Click to collapse
Yeah, but MT3G, MT3G v1.2 and Magic 32B do not need ENG SPL...
Ok. Thank you for your feedback
Sent from my LG-P925g using XDA
Oh I see what you're talking about. A program that will root and flash a recovery in as few clicks as possible. that's a good idea. Make it easier for the noobs.
tvall said:
Oh I see what you're talking about. A program that will root and flash a recovery in as few clicks as possible. that's a good idea. Make it easier for the noobs.
Click to expand...
Click to collapse
Pretty much. Just trying to figure out how to get it to detect the phone type as well. Once I can get that I can make it useful for a broad range of phones.
Sent from my LG-P925g using XDA
SithLord2K said:
Pretty much. Just trying to figure out how to get it to detect the phone type as well. Once I can get that I can make it useful for a broad range of phones.
Sent from my LG-P925g using XDA
Click to expand...
Click to collapse
I would suggest a drop down menu where you select device at the beginning and then root and flash with proper files
Good idea. But I also want it to be able to detect the phone type to ensure someone isn't trying to flash the wrong things. Would hate to see brick posts because someone tried to flash the recovery for the wrong phone.
Sent from my LG-P925g using XDA
SithLord2K said:
Good idea. But I also want it to be able to detect the phone type to ensure someone isn't trying to flash the wrong things. Would hate to see brick posts because someone tried to flash the recovery for the wrong phone.
Sent from my LG-P925g using XDA
Click to expand...
Click to collapse
In theory there are following differences between types:
Magic 32A: hboot 1.33.xxxx / radio 3.22.xx.xx OR hboot: 1.76.xxxx / radio 6.35.xx.xx; MID: SAPPxxxxx
Magic 32B / MT3G: hboot 1.33.xxxx / radio 2.22.xx.xx; MID: SAPPxxxxx
MT3G v1.2: hboot 1.33.xxxx / radio 2.22.xx.xx; MID: SAPP31000 (only); 3.5" audiojack
You can query hboot, radio and modeild from fastboot commands:
Code:
fastboot getvar version-bootloader
fastboot getvar version-baseband
fastboot getvar modelid
But it is not enough. In some cases there are exceptions like this: http://forum.xda-developers.com/showpost.php?p=23595971&postcount=1
User wrote about Magic 32B, but device changed to 32A via inappropriate radio
Just note: it is a "brick" (half or full). If phone has 1.33.xxxx hboot, then it can not have radio 6.35.xx.xx - it will not work normally.
Case #2 - modelid can return sapp*****
http://forum.xda-developers.com/showpost.php?p=23314205&postcount=3
http://forum.xda-developers.com/showpost.php?p=14486530&postcount=3
http://forum.xda-developers.com/showpost.php?p=13186681&postcount=1
And there are some troubles to detect what is type...
Thank you so much I will be working on this. Will be a while but I will eventually get a release out
Sent from my LG-P925g using XDA
After many, many hours, i figured out i have a perfected SPL (None of the instructions actully said it, that was more hours searching till i figured it out). Cant flash a recovery to do it. Rom manager cant even install Clockwork, flashrec doent even work. Yes, i am rooted.
I have read every forum post, even searched on google. The instructions here are:
A. Wrong
B. Dead link
C. Just dont work
popetorak said:
After many, many hours, i figured out i have a perfected SPL (None of the instructions actully said it, that was more hours searching till i figured it out). Cant flash a recovery to do it. Rom manager cant even install Clockwork, flashrec doent even work. Yes, i am rooted.
I have read every forum post, even searched on google. The instructions here are:
A. Wrong
B. Dead link
C. Just dont work
Click to expand...
Click to collapse
whats your radio and spl?
blizard80 said:
whats your radio and spl?
Click to expand...
Click to collapse
Sapphire PVT 32B SHIP S-ON G
HBOOT-1.33.0013 (SAPP30000)
CPLD-10
RADIO-2.22.28.25
Oct 21 2009, 22:33:27
tried this?
http://forum.xda-developers.com/showthread.php?t=548218
" Write down the ‘Card:mmc2, Reverse CID’ value, making sure to use mmc2 and not mmc1"
There is no mm2. I read every post, there is no answer
My magix is on the activation screen
I made a goldcard using a free tool posted here on xda, I used a Galaxy Nexus to red the mmc CID, I created the .img and wrote it to the mmc.
I put SAPPIMG.zip from a thread where it is posted a ROM claiming to replace the PERFECTED SPL by an engineering one. after booting to HBOOT, the phone searches and says there are no any images or are wrong.
there is only one file in the card, SAPPIMG.zip
I dont know what to do.
yurais said:
My magix is on the activation screen
I made a goldcard using a free tool posted here on xda, I used a Galaxy Nexus to red the mmc CID, I created the .img and wrote it to the mmc.
I put SAPPIMG.zip from a thread where it is posted a ROM claiming to replace the PERFECTED SPL by an engineering one. after booting to HBOOT, the phone searches and says there are no any images or are wrong.
there is only one file in the card, SAPPIMG.zip
I dont know what to do.
Click to expand...
Click to collapse
That was absolutely no help
popetorak said:
That was absolutely no help
Click to expand...
Click to collapse
I was able to unlock first try. However, the most difficult thing was finding all the files as the hosts are all long dead by now and revskills is down so if you need a gold card let me know. I can still make them.
I'll walk you through step by step if you need.. Because I found it quite a bit trickier than "hacking" my lg nitro hd and I know how hard it was for me to find all the files.. However, my phone is the mt3g 1.2
Sapphire PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Click to expand...
Click to collapse
when I took on unlocking it a couple weeks ago.
I had to make a goldcard manually, then flash the 2010 engineering SPL so I could flash a custom recovery (I like cwm more than amon_ra's because it's missing several options and I'm just used to cwm from my main phone. After this its as simple as flashing any ROM you want.. And since you aren't stuck with a 3.5mm jack you don't have to worry about special kernels and such, so its even easier. Just find all files and read the entire guide to unlocking the perfected SPL before starting so you aren't stuck half way through with a bricked phone because you can't find that certain missing file.
Good luck.
Sent from my LG-P930 using Tapatalk 2
NFleck said:
I was able to unlock first try. However, the most difficult thing was finding all the files as the hosts are all long dead by now and revskills is down so if you need a gold card let me know. I can still make them.
I'll walk you through step by step if you need.. Because I found it quite a bit trickier than "hacking" my lg nitro hd and I know how hard it was for me to find all the files.. However, my phone is the mt3g 1.2
when I took on unlocking it a couple weeks ago.
I had to make a goldcard manually, then flash the 2010 engineering SPL so I could flash a custom recovery (I like cwm more than amon_ra's because it's missing several options and I'm just used to cwm from my main phone. After this its as simple as flashing any ROM you want.. And since you aren't stuck with a 3.5mm jack you don't have to worry about special kernels and such, so its even easier. Just find all files and read the entire guide to unlocking the perfected SPL before starting so you aren't stuck half way through with a bricked phone because you can't find that certain missing file.
Good luck.
Sent from my LG-P930 using Tapatalk 2
Click to expand...
Click to collapse
Im stuck at: " Write down the ‘Card:mmc2, Reverse CID’ value, making sure to use mmc2 and not mmc1" There is no mm2.
Like i said before. I want help, not repeating what i said
popetorak said:
Im stuck at: " Write down the ‘Card:mmc2, Reverse CID’ value, making sure to use mmc2 and not mmc1" There is no mm2.
Like i said before. I want help, not repeating what i said
Click to expand...
Click to collapse
Should be there. You have followed the instructions to a t?
Also if you have a different model it could be mmc1. Not sure
Sent from my LG-P930 using Tapatalk 2
NFleck said:
Should be there. You have followed the instructions to a t?
Also if you have a different model it could be mmc1. Not sure
Sent from my LG-P930 using Tapatalk 2
Click to expand...
Click to collapse
Instead of blaming me, why dont you help me?
I have unlocked and rooted MANY different phones, tablets and mp3 players. I dont this before
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