S-OFF is gone, CyanogenMod is installed -> How to S-OFF? SunShine ain't working!

redpoint73

Recognized Contributor
Oct 24, 2007
15,259
6,946
113
Failed.
FAILED (remote: signature verify fail)

Tried:
stock 6.12.401.4 International
Strange, I believe the "Full stock, Wipe" fw zips for Sneakyghost's thread should be signed. Try the fw advised by ckpv5 in the previous response.


Also tried:
M8_6.12.1540.4_DevEd_FullStock
This won't work on your device. the version number needs to have "401" not "1540". 1540 means its for the Developer's Edition, which is a different CID and MID.

---------- Post added at 01:26 PM ---------- Previous post was at 01:21 PM ----------

http://imgur.com/a/BvaYN

Console locked up.
I don't have the balls to CTRL+C it...
If you wait for a long time, and still no response, there isn't much else you can do but kill the process.

It looks like it stalled before sending (much less installing) so it should be safe to kill it. But as with everything else on XDA, at your own risk.
 
  • Like
Reactions: BloodySword

BloodySword

Member
Nov 26, 2014
39
2
0
IT WORKED!!

ckpv5's method was the goal!

You're right, it somehow locked itself up before fastboot could pass any data!

The log:
Code:
C:\adb>fastboot flash zip fw_6.12.401.4.zip
target reported max download size of 1830612992 bytes
sending 'zip' (53847 KB)...
OKAY [  2.382s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) total_image_number=8

(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0

(bootloader) current_image_number=1

(bootloader) current_image_number=2

(bootloader) current_image_number=3

(bootloader) current_image_number=4

(bootloader) current_image_number=5

(bootloader) current_image_number=6

(bootloader) current_image_number=7

FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 6.675s

C:\adb>fastboot flash zip fw_6.12.401.4.zip
target reported max download size of 1826418688 bytes
sending 'zip' (53847 KB)...
OKAY [  2.615s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) total_image_number=13

(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,10
(bootloader) [RUU]UZ,adsp,21
(bootloader) [RUU]UZ,adsp,33
(bootloader) [RUU]UZ,adsp,43
(bootloader) [RUU]UZ,adsp,54
(bootloader) [RUU]UZ,adsp,65
(bootloader) [RUU]UZ,adsp,76
(bootloader) [RUU]UZ,adsp,88
(bootloader) [RUU]UZ,adsp,98
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) current_image_number=0

(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,5
(bootloader) [RUU]UZ,boot,10
(bootloader) [RUU]UZ,boot,15
(bootloader) [RUU]UZ,boot,20
(bootloader) [RUU]UZ,boot,25
(bootloader) [RUU]UZ,boot,30
(bootloader) [RUU]UZ,boot,35
(bootloader) [RUU]UZ,boot,40
(bootloader) [RUU]UZ,boot,50
(bootloader) [RUU]UZ,boot,55
(bootloader) [RUU]UZ,boot,65
(bootloader) [RUU]UZ,boot,70
(bootloader) [RUU]UZ,boot,80
(bootloader) [RUU]UZ,boot,86
(bootloader) [RUU]UZ,boot,95
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) current_image_number=1

(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,5
(bootloader) [RUU]UZ,recovery,11
(bootloader) [RUU]UZ,recovery,17
(bootloader) [RUU]UZ,recovery,22
(bootloader) [RUU]UZ,recovery,28
(bootloader) [RUU]UZ,recovery,33
(bootloader) [RUU]UZ,recovery,39
(bootloader) [RUU]UZ,recovery,44
(bootloader) [RUU]UZ,recovery,56
(bootloader) [RUU]UZ,recovery,61
(bootloader) [RUU]UZ,recovery,66
(bootloader) [RUU]UZ,recovery,72
(bootloader) [RUU]UZ,recovery,79
(bootloader) [RUU]UZ,recovery,89
(bootloader) [RUU]UZ,recovery,95
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,89
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=2

(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) current_image_number=3

(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=4

(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) current_image_number=5

(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=6

(bootloader) start image[sensor_hub] unzipping & flushing...
(bootloader) [RUU]UZ,sensor_hub,0
(bootloader) [RUU]UZ,sensor_hub,100
(bootloader) [RUU]WP,sensor_hub,0
(bootloader) [RUU]WP,sensor_hub,4
(bootloader) [RUU]WP,sensor_hub,8
(bootloader) [RUU]WP,sensor_hub,12
(bootloader) [RUU]WP,sensor_hub,16
(bootloader) [RUU]WP,sensor_hub,20
(bootloader) [RUU]WP,sensor_hub,24
(bootloader) [RUU]WP,sensor_hub,28
(bootloader) [RUU]WP,sensor_hub,32
(bootloader) [RUU]WP,sensor_hub,36
(bootloader) [RUU]WP,sensor_hub,40
(bootloader) [RUU]WP,sensor_hub,44
(bootloader) [RUU]WP,sensor_hub,48
(bootloader) [RUU]WP,sensor_hub,52
(bootloader) [RUU]WP,sensor_hub,56
(bootloader) [RUU]WP,sensor_hub,60
(bootloader) [RUU]WP,sensor_hub,64
(bootloader) [RUU]WP,sensor_hub,68
(bootloader) [RUU]WP,sensor_hub,72
(bootloader) [RUU]WP,sensor_hub,76
(bootloader) [RUU]WP,sensor_hub,80
(bootloader) [RUU]WP,sensor_hub,84
(bootloader) [RUU]WP,sensor_hub,88
(bootloader) [RUU]WP,sensor_hub,92
(bootloader) [RUU]WP,sensor_hub,96
(bootloader) [RUU]WP,sensor_hub,100
(bootloader) ...... Successful
(bootloader) current_image_number=7

(bootloader) start image[sp1] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=8

(bootloader) start image[tz] unzipping & flushing...
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) current_image_number=9

(bootloader) start image[wcnss] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=10

(bootloader) start image[radio] unzipping & flushing...
(bootloader) trying to rename MBA
(bootloader) ...... Successful
(bootloader) current_image_number=11

(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=12

OKAY [ 64.004s]
finished. total time: 66.622s
I want to thank you all guys. I mashed the button on EVERY post.
Kindest regards from Germany!

But the journey doesn't stop there!
When I want to S-OFF, should I first unlock the bootloader or should I just SunShine?

Edit: WTF...
It now boots into ... CyanogenMOD.. oO

Edit2:
The volume rocker often bounces, so I selected the wrong menu entry. It is now showing the CyanogenMOD robo animation but nothing happens.
 
Last edited:

ckpv5

Recognized Contributor
Feb 11, 2008
14,359
18,290
0
Kuala Lumpur
Reading all your posts .. the best route for you is option 2 because option 1 require you to do more to accomplish your goal.. to S-Off

I put the link again for option 2 : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

After you completed the process, unlock bootloader, install latest TWRP and install SuperSU 2.76, then Sunshine process.

Option 1 was meant for you to update your hboot, once updated, unlock bootloader, install latest TWRP then install CM 13.
 
  • Like
Reactions: redpoint73

redpoint73

Recognized Contributor
Oct 24, 2007
15,259
6,946
113
But the journey doesn't stop there!
When I want to S-OFF, should I first unlock the bootloader or should I just SunShine?
You need the stock ROM (but with root) to use sunshine.

You only flashed firmware (50 MB), which does not contain a ROM. If you want the stock ROM in order to s-off, the quickest way to do that is RUU (over 1 GB), as I already mentioned (2nd method we discussed). Then unlock bootloader, flash TWRP 3.0.2, flash SuperSU 2.76.


Edit2:
The volume rocker often bounces, so I selected the wrong menu entry. It is now showing the CyanogenMOD robo animation but nothing happens.
The phone won't boot into OS after flashing stock firmware, by definition. Its just firmware, not a full ROM.

From there, to get back to bootloader, reboot the phone by holding power+vol up (may need to hold for a minute or more). Then once the screen goes black to reboot, slide your finger from vol up to vol down. Don't let go of vol down, until the bootloader screen appears.

From there, continue the process. If you were doing method 1: unlock bootloader, flash TWRP, then CM13.
 
Last edited:

BloodySword

Member
Nov 26, 2014
39
2
0
Things in your link done, look posts above.
Unlock also done!
Next step is TWRP...
Wish me luck!
Edit: TWRP flashed successfully.

So now, for S-OFF, lock again, then flash HTC firmware?
Or does it work unlocked?
 
Last edited:

ckpv5

Recognized Contributor
Feb 11, 2008
14,359
18,290
0
Kuala Lumpur
Strange, I believe the "Full stock, Wipe" fw zips for Sneakyghost's thread should be signed.
AFAIK.. they are modded firmware. Some signed firmware are partial (especially the incremental updates) so the full stock has additional files added .. it is unsigned.

---------- Post added at 01:51 AM ---------- Previous post was at 01:43 AM ----------

Things in your link done, look posts above.
Unlock also done!
Next step is TWRP...
Wish me luck!
That's firmware not RUU.

Since you unlocked bootloader and installed TWRP .. you can restore 6.12.601.4 backup then install SuperSU 2.76 then Sunshine process to S-Off.

Or .. you can install almost stock custom ROM like MaximusHD, then S-Off process.

Both method .. leave the bootloader unlocked.
 
Last edited:

ckpv5

Recognized Contributor
Feb 11, 2008
14,359
18,290
0
Kuala Lumpur
Edit: Does SunShine still cost? I can download and start the app for free. But it didn't work because of CyanogenMOD ROM obviously.
You can start the app for free.. it will check your system for free and when it says it can S-Off your device it will ask $25 to proceed.


Good luck & good night
 

BloodySword

Member
Nov 26, 2014
39
2
0
Wow, I don't even know if the person would benefit from S-OFF, if it would be free, I would be doing it. But yeah, I think I just flash the current CyanogenMOD.
Thank you guys and have a nice day/night whereever you live. :)
Kudos are given!
Best regards from Germany!
 

redpoint73

Recognized Contributor
Oct 24, 2007
15,259
6,946
113
Wow, I don't even know if the person would benefit from S-OFF, if it would be free, I would be doing it. But yeah, I think I just flash the current CyanogenMOD.
I advised early on, that s-off costs $25 US. S-off can be valuable for some purposes, and some folks.

But its not needed for flashing ROMs, updating firmware, root, and a great many other mods. Whether s-off is worth it or not, is subjective. Many will say yes. But my opinion, most folks don't need it.
 

redpoint73

Recognized Contributor
Oct 24, 2007
15,259
6,946
113
Mhh... Boot after SuperSU takes ages. Root ist activated in DEV for both Apps and ADB.
You flashed CM13, right? Then just go to Settings>Dev Options and select root. That's it. No need to flash SuperSU. If you did flash SuperSU, you may have messed it up. If it doesn't boot, just wipe (default TWRP wipe) and re-flash CM13 and gapps, nothing else. Then boot, go into settings, and activate root, that's it.
 

BloodySword

Member
Nov 26, 2014
39
2
0
NOW I understand...
I am so stupid.
I did that but I thought I still need tat SuperSU app...
And this app prompts me to install the su binaries...
Totally unneccessary?

Edit: Back with CM12, SuperSU was mandatory I guess.
But current CM builds do not need that.
 

redpoint73

Recognized Contributor
Oct 24, 2007
15,259
6,946
113
I did that but I thought I still need tat SuperSU app...
And this app prompts me to install the su binaries...
Totally unneccessary?

Edit: Back with CM12, SuperSU was mandatory I guess.
But current CM builds do not need that.
If your intent is to replace the built-in SU with SuperSU (which I think you did by flashing SuperSU) then I would think you want to keep the binary updated.

I was on CM12 on my tablet (Samsung Tab Pro 8.4) and it worked the same way. You didn't have to flash SuperSU, but simply enable root in Settings.
 

BloodySword

Member
Nov 26, 2014
39
2
0
Yeah, it seems that CM13 has a kind of SuperSU-App (I really mean the apk, not the zip!) built-in where you can manage your apps that can get root or not.
I didn't know that. But I remember back then when I flashed the first KitKat CM, this feature was not present at all.
 

BloodySword

Member
Nov 26, 2014
39
2
0
Well again:
Many many thanks for clarifying these things.
Device is packaged together with my old bill and ready to be handed over. :)

Perhaps we meet again when I try it with my OPO3. ;)
 

redpoint73

Recognized Contributor
Oct 24, 2007
15,259
6,946
113
You're quite welcome. Happy to be of help.

Perhaps we meet again when I try it with my OPO3. ;)
Perhaps, indeed. OPO3 looks very interesting. I'm a bit torn with my loyalty to HTC. The 10 looks nice, although I'm not sure nice enough to justify the added expense. But also, the Nexus devices should be coming out in the next couple months, and I want to see what those look like.
 

jshamlet

Senior Member
Aug 25, 2014
997
313
0
You're quite welcome. Happy to be of help.



Perhaps, indeed. OPO3 looks very interesting. I'm a bit torn with my loyalty to HTC. The 10 looks nice, although I'm not sure nice enough to justify the added expense. But also, the Nexus devices should be coming out in the next couple months, and I want to see what those look like.
I feel the same way, as the M8 has been the best Android device I've ever owned. However, the new Nexus devices are going to be made by HTC, and rumor has it the larger of the two, the Marlin, will be based on the 10's body. I'm holding off until the release to see the particulars, but it looks awfully promising.
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone