Now that we are S-OFF, time to start having some fun with our phones.
Directions:
Must be S-OFF, MUST KNOW HOW TO USE ADB
download a .zip
rename it to splash.zip
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip splash.zip
Make sure that there are no error messages when flashing
fastboot reboot
Downloads:
STOCK
Click the images to download
/
Standard Disclaimer: I am not responsible for any damages to your phone.
User Requests/Contributions
User Requests
/
Contributions - jmotyka
/
/
FAQ
FAQ
I'm getting the following error...
sending 'zip' (28 KB)...
OKAY [ 0.228s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.270s
I am S-OFF and Unlocked. USB debugging is ticked. Any ideas?
TheRedmonian said:
I'm getting the following error...
sending 'zip' (28 KB)...
OKAY [ 0.228s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.270s
I am S-OFF and Unlocked. USB debugging is ticked. Any ideas?
Click to expand...
Click to collapse
going to take a guess and say you didnt rename it to splash.zip..?
andybones said:
going to take a guess and say you didnt rename it to splash.zip..?
Click to expand...
Click to collapse
I wish it was something that simple but I did rename it and put it in the same folder as adb. I've never had a problem with fastboot commands on any other phone. I can fastboot flash a recovery no problem, but for some reason a zip keeps throwing that error.
Edit: Nm, I figured it out.
TheRedmonian said:
I wish it was something that simple but I did rename it and put it in the same folder as adb. I've never had a problem with fastboot commands on any other phone. I can fastboot flash a recovery no problem, but for some reason a zip keeps throwing that error.
Edit: Nm, I figured it out.
Click to expand...
Click to collapse
mind sharing what the problem was in-case others come across doing the same.
Glad you got it
Skimming your instructions vs reading them, lol. I didn't fastboot oem rebootRUU.
Sent from my M7 using XDA Premium 4 mobile app
TheRedmonian said:
Skimming your instructions vs reading them, lol. I didn't fastboot oem rebootRUU.
Sent from my M7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Andy, does it matter what hboot you are running? and it might be worth adding to the OP that ADB doesn't work on Windows 8.1...
Edit... also, thanks for starting this thread !!!!
dspcap said:
Andy, does it matter what hboot you are running? and it might be worth adding to the OP that ADB doesn't work on Windows 8.1...
Edit... also, thanks for starting this thread !!!!
Click to expand...
Click to collapse
very welcome, I didn't make this thread though for lessons on ADB. This is S-OFF. playing with the big boys, if they can't ADB.. I don't suggest they mess around flashing these personally.
Not saying they don't know how, but this just isn't the thread to talk about anything besides splash screens. Not how to use ADB.
This is a friendly post, idk how it reads on the internet but no disrespect was meant to be said if you find any.
oh as for hboot, flash at your own risk if not on stock.
andybones said:
as I answered the first time.
Flash at your own risk if you are NOT on the stock hboot.
Click to expand...
Click to collapse
I don't understand what stock hboot means. Is that what I have from htcdev or somewhere else?
Sent from my HTC6500LVW using Tapatalk 4
dspcap said:
I don't understand what stock hboot means. Is that what I have from htcdev or somewhere else?
Sent from my HTC6500LVW using Tapatalk 4
Click to expand...
Click to collapse
Stock, the one that comes with the phone.
1.54.0000
I have NO idea what you have.
check your bootloader
also if you don't know what or how to find the stock hboot I suggest NOT messing with the splash screens.
andybones said:
Stock, the one that comes with the phone.
1.54.
I have NO idea what you have.
check your bootloader
also if you don't know what or how to find the stock hboot I suggest NOT messing with the splash screens.
Click to expand...
Click to collapse
Thank you kind sir, now I can enjoy splash screens also. :good:
thread cleaned. lets stay on topic. and OP id say chill a little. I know you dont like off topic but all of you need to take a break from the keyboard. Makes xda no fun to see everyone act like this
Can you do this one, Andy? Thanks in advance!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jaydubbs said:
Can you do this one, Andy? Thanks in advance!
View attachment 2277524
Click to expand...
Click to collapse
Added to 2nd OP
Hey Andy, another request!
Looking for something simple like those first two, but instead of "quietly brilliant" something like "quietly unlocked" or "quietly rooted"
Thanks in advance!
PizzaSauce said:
Hey Andy, another request!
Looking for something simple like those first two, but instead of "quietly brilliant" something like "quietly unlocked" or "quietly rooted"
Thanks in advance!
Click to expand...
Click to collapse
that would be more for a themer, u find me a pic and ill make it , though.
Rename the downloads to splash.zip
Click to download
Also had this on my original DInc so I remade it for the One
Click to download:
fader01 said:
I made this as a splash zip but until my phone is back cannt test it so I wont post it but here is the image if Andy wants to convert it.
Also had this on my original DInc so I remade it for the One when I get it back
Click to expand...
Click to collapse
just a warning for soem reason (even on sprint) the green logo shows at yellow?
Related
Okay, I know there are a bunch of threads on how to unroot, but I'm not sure which way I should do it.
There's the ruu way or there's the upload the pc(something.com).zip and just flash that and it will unroot.
I have 003 hardware(I think, I got the evo when it first came out)
I rooted via the three step windows program and have s-off
I'm running cm7 rls1
How should I got about unrooting?
When I tried the ruu way, the ruu would not find my evo connected to the computer..
Flashing the pc(something).zip would be easy but idk where to find the latest version of it.
Thank you.
http://forum.xda-developers.com/showthread.php?t=884060
There's a whole list of them. The second one down is what you're looking for. Name it "PC36IMG.zip" without quotes.
http://www.shipped-roms.com/shipped/Supersonic/
Download the 3.70 version, then boot your phone into fastboot, connect to pc, run RUU exe, and follow the instructions.
teh roxxorz said:
http://www.shipped-roms.com/shipped/Supersonic/
Download the 3.70 version, then boot your phone into fastboot, connect to pc, run RUU exe, and follow the instructions.
Click to expand...
Click to collapse
I downloaded the above... what is the point of booting into fastboot if the ruu instructs to turn the phone on normally?
I tried running the ruu while the phone was in fastboot and the ruu couldn't find the phone connected to the computer.
Should I try it with the phone on as stated in the ruu?
Are you sure this is the correct ruu?
I used simple root to root btw.
firebird0 said:
http://forum.xda-developers.com/showthread.php?t=884060
There's a whole list of them. The second one down is what you're looking for. Name it "PC36IMG.zip" without quotes.
Click to expand...
Click to collapse
I did that.. but when I boot into the bootloader, it goes through the imgs but it doesn't find the one that it needs...
make sure the pc36img.zip is named exactly pc36img.zip and doenst have .zip.zip extention or something because of hidden extensions or some other glitch. BTW IF YOU HAVE EVER FLASHED UNREVOKED FOREVER MAKE SURE YOU FLASH THE S-ON TOOL BEFORE UNROOTING. S-OFF IS THE MOST OBVIOUS SIGN OF ROOT SO MAKE SURE TO TURN IT BACK ON.
dkdude36 said:
make sure the pc36img.zip is named exactly pc36img.zip and doenst have .zip.zip extention or something because of hidden extensions or some other glitch. BTW IF YOU HAVE EVER FLASHED UNREVOKED FOREVER MAKE SURE YOU FLASH THE S-ON TOOL BEFORE UNROOTING. S-OFF IS THE MOST OBVIOUS SIGN OF ROOT SO MAKE SURE TO TURN IT BACK ON.
Click to expand...
Click to collapse
s-on is on... but i'll double check the name. thanks
Let us know how it turns out. I was never interested in unrooting until today when I noticed a big white splotch on my screen and serious light leakage which started all of the sudden out of nowhere. Guess I'll be following your lead and heading to the Sprint store on Monday Ugh!!!
here's what happens when I try and do it via boot loader...
http://www.youtube.com/watch?v=E3nmsg9eWBA
and when I try and do it via the ruu either in fastboot or whent he phone is on.. I get this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bump..... does anyone know why? Or how?
That is what should happen if there is no pc36img.zip. Make sure it is named exactly pc36img.zip and not pc36img.zip.zip because extensions are hidden or something.
Sent from my PC36100 using XDA App
dkdude36 said:
That is what should happen if there is no pc36img.zip. Make sure it is named exactly pc36img.zip and not pc36img.zip.zip because extensions are hidden or something.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm sure that is named correctly. I copied right off of your message... I have show known extensions... I don't get it..
Well there is no way it wouldn't even verify the zip if it was named correctly. Name is the only thing I can think of. Re check the name. Pc36img.zip
Sent from my PC36100 using XDA App
dkdude36 said:
Well there is no way it wouldn't even verify the zip if it was named correctly. Name is the only thing I can think of. Re check the name. Pc36img.zip
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'll double check man... but I swear its right...
It should at the very least say checking zip. You can manually flash the zip in ruu mode if you want and then you don't have to worry about names.
Sent from my PC36100 using XDA App
Try following this guide, I used this when I was unrooting.
http://forum.xda-developers.com/showthread.php?t=780141
dkdude36 said:
It should at the very least say checking zip. You can manually flash the zip in ruu mode if you want and then you don't have to worry about names.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
how do you do it manually?
He probably means doing it using the RUU (Application on your computer). If you're having the same problem that I'm having, that won't work. But it's worth a try.
firebird0 said:
He probably means doing it using the RUU (Application on your computer). If you're having the same problem that I'm having, that won't work. But it's worth a try.
Click to expand...
Click to collapse
Yeah, I stated before the the ruu would not find my phone. When its in fastboot, normal boot loader or when the phone is just on...
Im selling the phone on eBay and the auction is done in 8 hours, so that's why I need to unroot it...
Thank you for your help.
Sorry for late reply. No ruu Is not what I mean. Try setting up adb and fast boot commands. boot phone into fast boot usb mode. Then in the comp type.
Fastboot oem rebootRUU
You should see a black screen with silver htc letters. Type.
Fastboot flash zip /path/to/pc36img.zip
Keep in mind the zip us on your computer in this case. You should see a bunch of lines. When it completes, type.
Fastboot reboot
this should unroot you.
Sent from my PC36100 using XDA App
Alright, ill try it that way. Thank you for your help my friend.
HTC just released a step-by-step guide and unlock mechanism for couple of their phones include HTC Wildfire S (mine is S-ON and I was able to unlock the bootloader successfully).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enjoy
http://www.htcdev.com/bootloader/
Very good, Can you flash my custom rom and test it?
m1ndh4x8r said:
Very good, Can you flash my custom rom and test it?
Click to expand...
Click to collapse
Why don't you do it on your own? It's really easy
Good luck.
I mean can you test and flash this one here http://forum.xda-developers.com/showthread.php?t=1432259 and do the data2sd installation. Report to me if it works for you. only if you have an sim card wildfire s.
m1ndh4x8r said:
I mean can you test and flash this one here http://forum.xda-developers.com/showthread.php?t=1432259 and do the data2sd installation. Report to me if it works for you. only if you have an sim card wildfire s.
Click to expand...
Click to collapse
Yes, I may give it a try. But what does it mean "sim card Wildfire S"? You mean if I use any SIM card in it?
Umpal said:
Yes, I may give it a try. But what does it mean "sim card Wildfire S"? You mean if I use any SIM card in it?
Click to expand...
Click to collapse
Wildfire S A510e is the one with a sim card as it is GSM.
The other like the A510c or whatever are CDMA and dont use a sim.
willmcquillin said:
Wildfire S A510e is the one with a sim card as it is GSM.
The other like the A510c or whatever are CDMA and dont use a sim.
Click to expand...
Click to collapse
I assume then that mine is A510c ;-)
PS I'm preparing my microSD card for operation. Be at my hand just in case I need you
rom is for Marvel A510e only sim card phone. If you flash some things won't work not sure but you can try and report if it works.
In your step 2 guide is:
In CWM recovery
Wipe Factory, Data, Cache and Wipe Dalvik Cache
Click to expand...
Click to collapse
Where (or how) I can find/turn it?
Ok, found it here, but... I get an error "CID incorrect, Update fail!".
So I followed this instrucction and it seems it's updated (see the attached screenshot) but my bootloader hasn't changed a bit.
What wrong I'm doing? Any help please.
[Update]
It seems I have to look more carefully, it is a change but I can see it when I go to Recovery option. I'm now in CWM Recovery. Doin' an update with your custom ROM...
[Update 2]
Done. Wasn't that hard after all. What do you wanna know? (Apart that my Wildfire is A501e not 'c')
I get this?
C:\android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
??????
What can I do?
schlex2010 said:
I get this?
C:\android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
??????
What can I do?
Click to expand...
Click to collapse
I had the same, but had to do an update before any proceeding. On the very beginning you have a list of available carriers (try this link, but probably you will have to log in first: http://www.htcdev.com/bootloader/ruu-downloads). Mine Wilfire S is in T-Mobile D, so I chose TMO DE link (http://www.htcdev.com/ruu/PG7610000_Marvel_hboot_1.08.0099_20111216.exe).
After this update everything went smooth.
Good luck!
Umpal said:
I had the same, but had to do an update before any proceeding. On the very beginning you have a list of available carriers (try this link, but probably you will have to log in first: http://www.htcdev.com/bootloader/ruu-downloads). Mine Wilfire S is in T-Mobile D, so I chose TMO DE link (http://www.htcdev.com/ruu/PG7610000_Marvel_hboot_1.08.0099_20111216.exe).
After this update everything went smooth.
Good luck!
Click to expand...
Click to collapse
I thought about that, see that on HTCdev, but T-Mobile is not my carrier. Will try now with the file you postet.
Danke!
---------- Post added at 06:41 AM ---------- Previous post was at 06:15 AM ----------
yes!!!!!
With the Hboot Update it works all smooth as you told me
Unlocked bootloader, permroot and custom recovery... Very very smooth.
Now will test a custom ROM to make WFS fast
schlex2010 said:
I thought about that, see that on HTCdev, but T-Mobile is not my carrier. Will try now with the file you postet.
Danke!
---------- Post added at 06:41 AM ---------- Previous post was at 06:15 AM ----------
yes!!!!!
With the Hboot Update it works all smooth as you told me
Unlocked bootloader, permroot and custom recovery... Very very smooth.
Now will test a custom ROM to make WFS fast
Click to expand...
Click to collapse
I'm glad I could help
I've flashed this custom ROM and I'm now testing it.
Apart from that I also downloaded this and this. We'll see. Maybe after some time I'll test them also (unless there is an ICS fully working, stable and fast ).
Great stuff, gonna do the wifes when shes not looking
bradmax57 said:
Great stuff, gonna do the wifes when shes not looking
Click to expand...
Click to collapse
it will wipe all her user data to be careful in case she make you sleep on the sofa lol
eoghan2t7 said:
it will wipe all her user data to be careful in case she make you sleep on the sofa lol
Click to expand...
Click to collapse
haha yeah! got her contents of sd card backed up and also use smsbackup+ so there all safe, all her contacts are tied to her gmail account so it should just be a few apps to reinstall
Hi!
i want to unlock my friend's WFS.
This WFS Carrier German Vodafone.
Download the carrier ruu from htcdev.com and update. See error on the first picture.
I tipe in command prompt: fastboot oem get_identifier_token and the error see in secund picture.
The phone SN: HT153TR03430
PN: 99HMM084-00
How can i solve this problem. I want to unlock boot loader and install custom rom. Help me please!
Umpal said:
HTC just released a step-by-step guide and unlock mechanism for couple of their phones include HTC Wildfire S
Click to expand...
Click to collapse
Hello.
Sorry but I cannot find this guide on http://www.htcdev.com/bootloader.
Where can I find it ?
I'm trying to root a Wildfire S A510e (so, Marvel if I've well understood).
Provider: SFR
Android 2.3.3
Rom version: 1.33.163.2
I don't know the version of the bootloader.
I'm able to gain root shell using zergRush but I cannot fully root the phone because of the bootloader (I guess).
So, how can I S-Off it safely please ? (it's not my phone, I don't want to break it)
tuxfamily said:
Hello.
Sorry but I cannot find this guide on http://www.htcdev.com/bootloader.
Where can I find it ?
Click to expand...
Click to collapse
Did you registered and log in? I mentioned about it in my post.
Here you have a copy of the guide that still exists on the link you posted above:
BEFORE beginning the Unlock Bootloader process your product requires that you update the ROM to the version listed in the table below first, then download the RUU next to it to enable the unlocking capability.
To install the RUU, simply follow these instructions:
1. On your phone, enable USB debugging. (From the Home screen, MENU > Settings > Applications > Development > Check USB debugging)
2. Connect your phone to the computer using the USB cable that came with your phone. Wait a moment for your computer to identify your phone, this may take a few minutes.
a. If your computer cannot find your phone, you may need to install HTC You can download HTC Sync here.
3. After your computer has found your phone, double click on the RUU to start the process.
4. Follow the on screen instructions to finish flashing the RUU on your phone.
NOTE: If you encounter an error while flashing your phone, it’s possible that the connection to your phone was interrupted. Simply exit the program, disconnect your phone and start over.
a. Fully exit the RUU to ensure there is no conflict of multiple instances of the program running.
b. Disconnect the USB cable from both the phone and the computer.
c. After a few moments, reconnect the USB to the computer and phone. See above if your phone or computer cannot find each other.
d. Run the RUU.
Disclaimer: You may not be able to get further FOTA updates once the RUU was applied to your device.
Umpal said:
Did you registered and log in? I mentioned about it in my post.
Here you have a copy of the guide that still exists on the link you posted above
Click to expand...
Click to collapse
Ha, this is the guide ... I was expecting a "commands line" guide working on all OS.
I'm on Linux (and sometime Mac), so HTCSync and *.exe are not very useful for me.
Well, I will do it with the zip to put on the sdcard and I hope that it will not break this device ... :/
Thanks for your reply anyway
Hi everyone,
I hope I can get some kind hearted people to help me with my problem! :crying: I am selling my One X and have followed a step by step guide to Unroot the device. It now shows as Relocked on the bootloader. However, the phone wont boot up the OS and just reboots to the bootloader again. Here are some pics:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would really appreciate any help!
Yep, you need to flash RUU to return it to stock, just by relocking the bootloader it doesn't unroot
xl VipeR lx said:
Yep, you need to flash RUU to return it to stock, just by relocking the bootloader it doesn't unroot
Click to expand...
Click to collapse
Do I need to download it from this thread? http://forum.xda-developers.com/showthread.php?t=1543604
Should it boot up as stock after flashing it?
Khy50 said:
Do I need to download it from this thread? http://forum.xda-developers.com/showthread.php?t=1543604
Should it boot up as stock after flashing it?
Click to expand...
Click to collapse
yep, what network were you on, was yours a branded handset or unbranded, can you run fastboot commands from your pc on the phone, try running fastboot oem getvar cid
that will tell you what brand your one x is and help you flash the right RUU
My Sensation had the same thing happen to it when i first relocked the bootloader, i almost cried because it wouldn't boot, but thankfully i fixed it by flashing the RUU. you learn from your mistakes :good:
xl VipeR lx said:
yep, what network were you on, was yours a branded handset or unbranded, can you run fastboot commands from your pc on the phone, try running fastboot oem getvar cid
that will tell you what brand your one x is and help you flash the right RUU
My Sensation had the same thing happen to it when i first relocked the bootloader, i almost cried because it wouldn't boot, but thankfully i fixed it by flashing the RUU. you learn from your mistakes :good:
Click to expand...
Click to collapse
Thanks for the helpful info mate. Yes I am pulling my hair out thinking my phone is bricked!
I am on UK Tmobile, it was branded (tmob splash screen). I am downloading the RUU: RUU_ENDEAVOR_U_ICS_40_TMO_UK_1.28.110.7_R2_Radio_1.1204.103.14_release_256500_signed.exe
I assume this one will work. I am using a mac but have a PC to use the exe file. Download speed is at 50kb/s though
Khy50 said:
Thanks for the helpful info mate. Yes I am pulling my hair out thinking my phone is bricked!
I am on UK Tmobile, it was branded (tmob splash screen). I am downloading the RUU: RUU_ENDEAVOR_U_ICS_40_TMO_UK_1.28.110.7_R2_Radio_1.1204.103.14_release_256500_signed.exe
I assume this one will work. I am using a mac but have a PC to use the exe file.
Click to expand...
Click to collapse
brilliant, that should work then, definitely run it on PC not mac
its not exactly bricked, its just that you relocked the bootloader, so in simple terms the security warning is there because the phone is now locked, it checks the whole phone when it boots, and its recognizing something isn't stock, so goes into bootloader with a warning. Flashing RUU returns everything to stock so that should in wipe off whatever is causing the security warning.
Post back how it goes and good luck !
xl VipeR lx said:
brilliant, that should work then, definitely run it on PC.
its not exactly bricked, its just that you relocked the bootloader, so in simple terms the security warning is there because the phone is now locked, it checks the whole phone when it boots, and its recognizing something isn't stock, so goes into bootloader with a warning. Flashing RUU returns everything to stock so that should in wipe off whatever is causing the security warning
Click to expand...
Click to collapse
Alright, just have to wait 3 hours for download to finish.. think ill do it in the morning lol. Thanks for your help mate :good:
Khy50 said:
Alright, just have to wait 3 hours for download to finish.. think ill do it in the morning lol. Thanks for your help mate :good:
Click to expand...
Click to collapse
No probs. anytime
Yes it worked a treat. Live and learn eh! :good:
Khy50 said:
Yes it worked a treat. Live and learn eh! :good:
Click to expand...
Click to collapse
No problem
try flashing RUU:fingers-crossed:
Hi everyone,
First of all thank you for taking the time to read my problem, and maybe trying to help.
I will try to describe with as many data and images what I have done, that led me to my problem, I hope it's not the end of my M9.
My original goal was to revert my M9 back to stock.
The M9 state before trying to achieve this was:
Root
S-OFF
TWRP Recovery installed
Unlocked Bootloader
cid 11111111
Custom Rom- Viperone M9 version 4.3.0
To revert to stock, I first tried RUU.EXE method.
This procedure always resulted in ERROR 155. After searching the forums, I understood that this sometimes happens because of the unlocked bootloader.
So using the Fastboot I relocked the bootloader. Unfortunately, that didn't help.
After that, I tried flashing RUU.ZIP via Fastboot.
I did several Fastboot commands after searching all forums. Everytime Fastboot command resulted in another error.
Unfortunately, during this process I did S-ON, and I this that because of that, I am currently stuck.
At the moment, the device doesn't manage to execute any command I try.
Also, it doesn't boot into the firmware, so I can't S-OFF again.
I'm afraid already (hope it's not too late) to continue other actions without assistance.
At the end of OP, you will find screenshots of
The current Bootloader Screen
The current Download screen
Result info of Fastboot command: "fastboot getvar all"
A link to the RUU.EXE I tried using
A link to the RUU.ZIP I tried using
To keep thing clear, any other image of actions will be uploaded to OP.
I would very very much appreciate help and advice.
I hope it's not too late, even if this whole thing doesn't succeed, I look forward learning more to prevent this from happening in the future.
Thank you.
Bootloader Screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download Screen:
Fastboot getvar all:
RUU.EXE: https://www.dropbox.com/s/9kjf0u8h5iy8rdc/RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.12.exe?dl=0
RUU.ZIP: https://www.dropbox.com/s/edzwftny23ldsiq/0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.12_Radio_01.01_U11440792_97.00.51203G_F_release_signed.zip?dl=0
Actions done according to information from this thread:
You have to be "official" to go to stock or the ruu fails.
I dont think supercid helps either.. S-off shouldn't make a difference.
I think it's flash a stock backup, flash stock recovery,?? lock bootloader?? Flash stock ruu.
There are a few threads. I recommend flippy's thread.
Sent from my HTC One M9 using Tapatalk
You have to be "official" to go to stock or the ruu fails.
I dont think supercid helps either.. S-off shouldn't make a difference.
I think it's flash a stock backup, flash stock recovery,?? lock bootloader?? Flash stock ruu.
There are a few threads. I recommend flippy's thread.
Click to expand...
Click to collapse
Hi, and thank you for your reply.
Can you please past a link to the thread so that I can be sure I'm following the correct one?
I tried flashing recovery, locking bootloader and flashing stock RUU, all resulting in error.
If you could be more specific about what exactly I should do, I would give you the respected result.
I'm not looking for someone to do the searching or work for me. I just want to be accurate about the actions I need to do and their results so that you I and other helpers would now the exact actions made and their results.
Thank you
http://forum.xda-developers.com/showthread.php?t=3132698
Sent from my HTC One M9 using Tapatalk
shivadow said:
You have to be "official" to go to stock or the ruu fails.
I dont think supercid helps either.. S-off shouldn't make a difference.
I think it's flash a stock backup, flash stock recovery,?? lock bootloader?? Flash stock ruu.
There are a few threads. I recommend flippy's thread.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
shivadow said:
http://forum.xda-developers.com/showthread.php?t=3132698
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
There are no instructions there. Only all sorts of files.
I have already been to that thread. The files are tried to flash are also from there.
Maybe I flashed the wrong files, or maybe I didn't do the steps properly, but in any case, I can't know from that thread since it is not described there.
Again, please be more specific about what are the steps, or anything else that I need to do.
Thank you
Did you even bother reading the OP of my thread? If you had you would have known where to find the instructions.
Sent from my HTC One S using XDA Labs
Flippy498 said:
Did you even bother reading the OP of my thread? If you had you would have known where to find the instructions.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
Lol, I read every letter in the first post.
post 1: Opening post (no instructions)
post 2: TWRP backups (not relevant to me because I can't flash the recovery, again no instructions. Only files)
post 3: OTA Updates (again no instructions. Only files)
post 4: Stock Recoveries (again no instructions. Only files)
post 5: General Info (again no instructions. Only links to other threads regarding the info)
post 6: Useful links to downloads
Did I miss something?:laugh:
henengel said:
Did I miss something?:laugh:
Click to expand...
Click to collapse
Well, obviously you did.
From the OP:
Flippy498 said:
Please take a look at my google sheet if you want to get back to stock and don't know how to flash a RUU or how to correctly restore a TWRP backup. Although the sheet doesn't contain files for every existing firmware version the instructions can be used for every other RUU and TWRP backups that contain at least a Boot Image, the Stock Recovery and a System Image, too.
[...]
RUUs and useful links (e.g. instructions) can be found in the 6th Post.
Click to expand...
Click to collapse
From Post #6:
Flippy498 said:
Flippy498's Google Sheet
Contains download links for all Back-to-Stock files he collected/created (RUUs, OTAs, official Firmware Packs, Stock Recoveries, Boot Images and TWRP Backups) and some instructions how to flash RUUs or how to Restore a TWRP Backup correctly, too
Click to expand...
Click to collapse
Edit: Btw, if you don't want others to use your IMEI for scam you should remove it from your OP.
Flippy498 said:
Well, obviously you did.
From the OP:
From Post #6:
Click to expand...
Click to collapse
First of all thank you for pointing out the instructions.
Obviously, I did...
Just a suggestion, it would be very helpful if you could make the section stand out more, and be clearer that all steps and instructions are placed there.
I personally didn't understand that all of that is located there... again only my opinion.
I'll start right away and be back with all results and images...:good:
I actually prefer it the way it is now. That wasn't my thread from the beginning and I don't want to change too much of the original OP. Besides I don't like the tl;dr attitude (aka "OP? I see no reason why I should waste my time and read it!"-attitude) more and more user seem to have here on xda. You can do a lot of mistakes and ruin your phone in so many ways if you don't know what you're doing (this especially applies to S-OFF users) and this way people are forced to read the OP if they need help. (And maybe one or another user starts reading the basic information in post #5.)
Oh and for your own safety: Please take a look at the edit of my last post.
Flippy498 said:
I actually prefer it the way it is now. That wasn't my thread from the beginning and I don't want to change too much of the original OP. Besides I don't like the tl;dr attitude (aka "OP? I see no reason why I should waste my time and read it!"-attitude) more and more user seem to have here on xda. You can do a lot of mistakes and ruin your phone in so many ways if you don't know what you're doing (this especially applies to S-OFF users) and this way people are forced to read the OP if they need help. (And maybe one or another user starts reading the basic information in post #5.)
Oh and for your own safety: Please take a look at the edit of my last post.
Click to expand...
Click to collapse
I totally understand you...
That is indeed the common attitude...but if it doesn't stand out a bit, it is really easy to miss like I did.
There is a lot of information here, and it's very easy to miss 1 sentence, as I did.
But you are the creator, or in this situation the of the maintainer of the post, so obviously your opinion is what counts.
As far as one is concerned, I'm just appreciate very much and thank you for your help.:good:
Well after doing as the guide said (very easy), my M9 is up and running as normal.
Thank you so very much for your help and guidance.
Hi,
Yesterday I started trying to root my phone, needless to say it didn't go too well. As the title says, I'm unable to access recovery mode, and this morning when I tried to update to andriod 6.0, that wouldn't work either.
I successfully unlocked the bootloader, I think. It says unlocked in bootloader anyway. I have now relocked it to see if it will update with a locked bootloader.
Okay, so to describe what happens when I try to boot into recovery: The HTC logo shows up for a second or so, then the screen goes black and I have to boot it up from start. Also, I noticed, don't know if this is relevant, but in order for me to get into bootloader I have to hold vol down and power for at least 20 seconds, that does't seem normal to me.
I have downloaded a RUU from an HTC site(can't link, first post), but of course that wont install because im S-ON, which I don't know what it means. Anyway, the RUU wizard tells me to get the corret one, even though im fairly sure I am using the correct one.
my CID is HTC__Y13, do't know if that is going to help.
When trying to root I followed the htconeroot websites guide. again can't link :/
I have no idea what to do from here, if anyone who actually knows how these things work could help me, I would apreciate it greatly.
Thanks in advance!
Post fastboot getvar all result without serial & imei no.
Then we'll see what you need to do.
You may need these drivers installed : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Hey, thanks for replying!
Here is my getvar stats. If you don't mind me asking, why should I not post serial or ime no.?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh, also my battery is almost fully charged, still says 0mv... Don't know why, maybe somehow my phone incorrectly detects that my battery is too low when trying to run recover/update and quits because of low battery level?
You don't post serial and imei so you don't get your phone stolen. Those numbers can let someone report the phone as stolen, and have it become rejected by the carriers and such. As for the main issue you have, I'm S-OFF personally, so I flash everything manually. I haven't dealt with much of anything with S-ON aside from pure stock which does everything on it's own.
Trauken said:
Hey, thanks for replying!
Here is my getvar stats. If you don't mind me asking, why should I not post serial or ime no.?
Oh, also my battery is almost fully charged, still says 0mv... Don't know why, maybe somehow my phone incorrectly detects that my battery is too low when trying to run recover/update and quits because of low battery level?
Click to expand...
Click to collapse
Because those are personal info .. bad people can use the data to hack or something. So it's best not to post them.
The battery show as 0 on getvar result is normal ...
back to your problem ....
Your device is not a M8 but a different device called M8s
So the custom recovery that you installed most probably for M8 and definitely won't work on M8s.
And be frank with you, I am not familiar with your kind of device. There is a separate thread for M8s - http://forum.xda-developers.com/htc-one-m8/one-m8s-general
You can ask help here : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
or here : http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
maybe someone with your device version will help you
Wow! I feel so stupid now...
Thanks alot for your help guys!
I'll try using the correct stuff instead and see if I can solve things, thanks again!
By the way, what would be the easiest way to go about this?
My bootloader is locked and I can't unlock it again since I have used the wrong recovery mod... So I can't just flash the recovery mode now, can I?
Could I use the RUU to somehow restore my recovery mode ? That would be great.
You can unlock the bootloader again with the same unlock_code.bin that you applied to HtcDev.
This time use correct TWRP meant for M8s to root it. You can find it in that M8s thread.
I don't know whether there is RUU for your software version. As I mentioned above, those people in M8s thread know better.
Since your device is not rooted (most probably), why don't you do the update from 1.21.401.1 to Marshmallow 2.10.401.1 ?
You just need to reflash the stock recovery but you need to find either 1.21.401.1 0r 2.10.401.1 stock recovery.img
Well the problem is I can't reflash since my bootloader is locked, and I can't unlock my bootloader because whenever I go into the "do you really want to unlock bootloader" screen and say yes, it shows the HTC logo and then turns off again... Very frustrating.
I know I'm currently in the wrong section, but since I already have your attention and the fact that you seem to know your stuff, what do you think I should do?
Trauken said:
Well the problem is I can't reflash since my bootloader is locked, and I can't unlock my bootloader because whenever I go into the "do you really want to unlock bootloader" screen and say yes, it shows the HTC logo and then turns off again... Very frustrating.
I know I'm in the wrong section currently, but since I already have your attention and the fact that you seem to know your stuff, what do you think I should do?
Click to expand...
Click to collapse
OK .. you need to flash 1.21.401.1 signed firmware.zip
I'll try to find one (hopefully is available) but I'll do this tomorrow. It's already 1.45 am here .. I need to rest soon.
Meantime try to search/google 1.21.401.1 OTA.zip or firmware.zip. If you can find one (but make sure it is for M8s not M9 or any other device) .. you just need to run these command to flash it.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
you'll see error
fastboot flash zip firmware.zip (one more time)
fastboot reboot-bootloader
this should fix your problem . your problem now is wrong recovery installed but unable to reinstall correct recovery alone because bootloader is relocked.
Thanks man!
If only the world was made up of people like you!
Get some rest, I'm not in any hurry!
I'll try to get the RUU version that I fits my phone, I'm guessing I can't use a newer one because I'm S-ON? Anyway, you don't have to answer now.
Thanks alot again, really appreiciate your help!
Trauken said:
I'll try to get the RUU version that I fits my phone, I'm guessing I can't use a newer one because I'm S-ON? Anyway, you don't have to answer now.
Click to expand...
Click to collapse
If there is a newer one 2.10.401.1 yes you can use, you can't use older version than 1.21.401.1 like 1.11.401.1 or 1.11.401.10 , higher version is ok.
Good night.
Hey, hopefully I don't wake you up somehow.
I found what I think is the right file, it was named the same thing you told me to flash.
When using the commands you told me I get this:
I can't understand any of it really, I'll google around some more and see if I can find what is wrong.
It happened that I woke up for a drink.
Just wait for tomorrow, I already have the correct firmware.zip for you.
Edit : try this - https://drive.google.com/file/d/0B4jGj3SfskzMVElpa0MxTlpCRGM/view?usp=sharing
See whether you can download it, posted on mobile.
I'll check your progress tomorrow
The last command to exit that cmd prompt screen is fastboot reboot-bootloader
Have to get some sleep, saw your answer just now lying in bed...
Will continue as soon as I wake up
EDIT- Okay so I couldn't wait lol.
Did as you said but I get this:
Am I supposed to put the firmware.zip in the fastboot folder. I did that, I'm guessing that's right...
Here is a picture of my fastboot folder in case it is somehow useful:
Trauken said:
Did as you said but I get this:
Am I supposed to put the firmware.zip in the fastboot folder. I did that, I'm guessing that's right...
Here is a picture of my fastboot folder in case it is somehow useful:
Click to expand...
Click to collapse
It seems like the generic fastboot.exe is not working for this. You should try using the htc_fastboot.exe
https://ruu.lalleman.net/HTC_M8S(QL_UL)/Tools/Fastboot/
put the htc_fastboot.exe in your fastboot folder, then try again with commands
fastboot oem rebootRUU
htc_fastboot flash zip firmware.zip
error...
repeat htc_fastboot flash zip firmware.zip
fastboot reboot-bootloader
If this also fails, the last thing that you can do (you need microSD) ...
rename the firmware.zip to 0PKVIMG.zip (that's a zero not "O")
put 0PKVIMG.zip on your microSD (not in any folder)
on bootloader select hboot
it will scan the file and ask whether to update
volume up to update
once completed reboot
(remember to remove this 0PKVIMG.zip from microSD after reboot)
Thank you once again.
My phone now propely works thanks to you.
The htc_fastboot.exe seems to have done the trick. What is it that it actually does?
I can't stress enough how grateful I am!
Trauken said:
Thank you once again.
My phone now propely works thanks to you.
The htc_fastboot.exe seems to have done the trick. What is it that it actually does?
I can't stress enough how grateful I am!
Click to expand...
Click to collapse
Most probably the HTC encryption on the htc signed firmware.zip only can be read by htc_fastboot.exe
Great that you solved your problem .. you should update to the latest Marshmallow 2.10.401.1
As this is M8s device matter, I requested moderator to move this thread to M8s section
when i type "htc_fastboo oem rebootRUU" it restarting normally and bootloop