hello,
i am trying to get my htc one mini to S-OFF and to do that, after reading most of the forums in XDA for htc one mini, i was told to use the "revone" file, unfortunately the website revolutionary.io/revone is broke and i cannot find the revone file anywhere on the net. Can any body please upload the file which will be much appreciated and one more question, i have bought my HTC ONE MINI @dubai, which stock rom or RUU or Firmware should i try if in case i have wiped my storage and lost my original OS.
Hi I have it somewhere but it doesn't work anymore. Which ROM do you have and which HBOOT? Are you rooted ?
If you have HBOOT 2.22 and 4.4.2 Android simply flash xXminiWHOOPERxX kernel V6 , then try rumrunner. It worked yesterday for me after whole day of trying with all sorts of methods. Hope that helps.
Thank you , my bad, i managed to work on RUMRUNNER, everything went fine but it seems RUMRUNNER does not work on 4.4.2. My HBOOT is 2.22 and yes i am rooted.
I really appreciate your reply, i stopped looking at XDA because none bothered replying me. I would try xXminiWHOOPERxX Kernel V6 and will update you. Thank you so much. :good:
Also i am not a geek in android, but can you please, if you don't mind, tell me how to flash the kernel? Sorry if i am being Dumb Here
EjđiSixo said:
Hi I have it somewhere but it doesn't work anymore. Which ROM do you have and which HBOOT? Are you rooted ?
If you have HBOOT 2.22 and 4.4.2 Android simply flash xXminiWHOOPERxX kernel V6 , then try rumrunner. It worked yesterday for me after whole day of trying with all sorts of methods. Hope that helps.
Click to expand...
Click to collapse
Sorry, typing response for 10 minutes with instructions, then stupid forum decides to sabotage me, really don't want to type all again. You have to flash it through fastboot (adb binaries).
Or rename it to boot.img, put in archive of rom you will flash and replace with current boot.img in archive. If you need any help , i'll try.
Hi, Thank you. I tried downloading all the 3 versions of the kernel and it pissed me off. It was a zip file and when extracted the file was an .exe which led me to viruses in my laptop. i had to format:crying: i tried searching the the whooper kernel v6 but all in vain. i don't want to risk it all again.
EjđiSixo said:
Sorry, typing response for 10 minutes with instructions, then stupid forum decides to sabotage me, really don't want to type all again. You have to flash it through fastboot (adb binaries).
Or rename it to boot.img, put in archive of rom you will flash and replace with current boot.img in archive. If you need any help , i'll try.
Click to expand...
Click to collapse
Oh man,you never ever open exe file except when you expect it to be exe file. Blue button is to download real kernel. I wish people used more friendly hosting sites tho.. Anyway here you go in the attachment.
I really really really appreciate your effort for helping me. Thanks a lot. Let me Flash it and update you. Thanks a Tons my Friend.:good:
EjđiSixo said:
Oh man,you never ever open exe file except when you expect it to be exe file. Blue button is to download real kernel. I wish people used more friendly hosting sites tho.. Anyway here you go in the attachment.
Click to expand...
Click to collapse
No problem, just make sure to post reply if everything went good, so if somebody searchs for it in the future can find this useful.
I can confirm it works however the rumrunner froze on a few occasions but it seemed to pick up from when It stopped.
I can confirm that rumrunner with the "BootV6.img" supplied above worked like a charm on KK 4.4.2, HBoot 2.22. The only downside to revone is that you can't remove the "TAMPERED" on the bootloader, but I can live with that!
EjđiSixo said:
Oh man,you never ever open exe file except when you expect it to be exe file. Blue button is to download real kernel. I wish people used more friendly hosting sites tho.. Anyway here you go in the attachment.
Click to expand...
Click to collapse
I was almost ready to give up on this site. In the dev section it looks like there might not be a single link left that's functional.
Just flashed the kernel and used rumrunner to S-OFF my mini with 2.22 HBOOT.
I almost had a mini heart attack when i started realizing that people might really be buying into newer devices and abandoning older ones at an ever increasing rate. My old HTC Desire made in 2010 lasted me until now and still mostly works with a custom ROM... I hope this mini will last me just as long although that might require opening it up to change the "non removable" battery at some point.
Bottom line, this previously used thing cost me 65eur (+10 for shipping) and it only had very minor scratches. Please don't forget those who recycle that which gets discarded by walking bags of money.
Related
Okay, here goes the story-
1.Got an Inspire
2.Did the Hack Kit and then installed the Rooted Stock ROM (Discontinued), everything went okay but when trying to reboot into CWM, I got the HTC Screen for a few seconds then blackness, I later determined it was working I just couldn't see it for whatever reason.
3.Okay, I thought I'd try Bubby's One Click and see if that would fix it, it went great too, but CWM still no workie, getting frustated now.
4.I thought I'd try flashing a non-AT&T ROM, since so many have been having issue running one and getting the working, but black screened CWM, I chose CoreDroid's.
5.I put CoreDroid's ZIP on my SD Card, went into ROM Manager and installed it, making sure clear memory and backup current ROM were checked.
6.It rebooted into CWM, which of course I couldn't see, then about 10 minutes later it rebooted, and the beautiful CoreDroid Animation came up, and a few minutes after that I had CoreDroid up and running.
7.Well, I thought, CWM should work fine now, EHHHHH Sorry Johnny (which sounded weird, since my name is Mike ), wrong answer, I rebooted into CWM and there it was again, total blackness.
8.Okay, I noticed in CoreDroid that to be able to flash new Radio's, you had to have Eng S-OFF, so I ran the One Click Eng S-Off Tool found here http://forum.xda-developers.com/showthread.php?t=855403 , making sure to check the box saying I already have S-Off.
9.It ran, and said it was successful, and I now had Eng S-Off, so I rebooted into Hboot to check, and at the top sure enough, it said Eng S-Off, I then hit PowerDown, which it did, but then....well, go to 10
10.It rebooted into...yep, CWM! Clear and beautiful, it looked wonderful! So booted back up, went into ROM Manager and told it to boot into CWM, it did so and it came up again, no problems! I did it again to make sure it wasn't a fluke, nope, all was well now in CWM Land!
So, how's that for a saga? Ahh, now I can kick back, it's Miller Time, or Dr.Pepper Time in my world, I don't drink
Use this at YOUR OWN RISK! I take no responsibility for bricked or ruined phones, I just posted this in hopes it might help out people having CWM issues. DO NOT send me hate mail because this didn't work for you
Good job bro!! I don't personally have the problem, but I've been following tons who have. Well done!
i did step 8 throu 10 and it works great thanks a mill!
No prob, I'm glad I could help you guys out!
congrads!!! i'm gonna try it out, i really wanna try some of these awesome roms available
Thanks Epic, let me know how it goes for you! I can't figure out what it did, other than maybe some files were corrupted or missing, and doing the Eng S-Off pushed and refreshed whatever was corruped or missing, either way I am glad to have it working again
Very nice discovery, I will in cooperate this into the next version of my program. Thanks a ton.
bubby323 said:
Very nice discovery, I will in cooperate this into the next version of my program. Thanks a ton.
Click to expand...
Click to collapse
No Prob Bubby, I'm glad I could help and give something back! I am in full support of you by the way, I think it's pretty slimy how they ganged up on you like that, when all you did was try and make things easier for the community. If I can help out in any way, let me know!
californiarailroader said:
No Prob Bubby, I'm glad I could help and give something back! I am in full support of you by the way, I think it's pretty slimy how they ganged up on you like that, when all you did was try and make things easier for the community. If I can help out in any way, let me know!
Click to expand...
Click to collapse
Will do.
I believe (if I'm not mistaken) that ENG S-OFF is the Engineering bootloader... it's not the best way to S-Off, because it puts the Engineer's Test HBOOT onto your phone, which causes some problems for other things. Also, to get back to complete stock, you'll now need to flash a stock HBOOT as well, if I remember correctly.
For that very reason, I would *NOT* incorporate this into your one-click, bubby... it worked for me perfectly the way it is, WITHOUT an Engineering HBOOT. I'd leave this as a possible solution for the ones that actually have the problem.
ClearD said:
I believe (if I'm not mistaken) that ENG S-OFF is the Engineering bootloader... it's not the best way to S-Off, because it puts the Engineer's Test HBOOT onto your phone, which causes some problems for other things. Also, to get back to complete stock, you'll now need to flash a stock HBOOT as well, if I remember correctly.
Click to expand...
Click to collapse
I haven't had any issues yet, so hopefully I'm good I wouldn't have even ran it except for the fact that to flash other radios, you need to have it on there. I don't mind doing whatever I have to do to go back to Stock, which I don't plan on doing unless I have to send it in for warranty or insurance.
That said, I just posted it so that it might be of help to others, so I guess try it if you are having problems with CWM showing up properly, otherwise leave it alone
californiarailroader said:
I haven't had any issues yet, so hopefully I'm good I wouldn't have even ran it except for the fact that to flash other radios, you need to have it on there. I don't mind doing whatever I have to do to go back to Stock, which I don't plan on doing unless I have to send it in for warranty or insurance.
Click to expand...
Click to collapse
No doubt. I hope I never have to, either... I just remember that with an engineer hboot on the desire, it was a LOT harder to get it back to stock, and had several other issues, and that's why they did away with it in favor of non-ENG HBOOT options. I like how it opens up the phone, though. This is indeed a great find that it works with ours!
EDIT: Ahh, I found it. It's in the G2 Wiki here.
"INSTALLING ENGINEERING HBOOT (DZ/G2/DHD) - OPTIONAL and UNNECESSARY!
Assuming you've backed up your phone with Clockwork's nandroid, you can install the engineering HBOOT (bootloader), which among other things allows you to use fastboot flash (or flashing-over-usb from your computer). This is unnecessary for most users but provides additional functionality for developers.
This is totally optional and dangerous - if the write to the phone partition fails the phone will be bricked. At the moment there is no cure for a phone that has been bricked by a failed hboot install."
That very last line is why Bubby should NOT include this in his one click... you think problems are bad now, wait till someone bricks a device and we can't unbrick it! D:
ClearD said:
No doubt. I hope I never have to, either... I just remember that with an engineer hboot on the desire, it was a LOT harder to get it back to stock, and had several other issues, and that's why they did away with it in favor of non-ENG HBOOT options. I like how it opens up the phone, though. This is indeed a great find that it works with ours!
EDIT: Ahh, I found it. It's in the G2 Wiki here.
"INSTALLING ENGINEERING HBOOT (DZ/G2/DHD) - OPTIONAL and UNNECESSARY!
Assuming you've backed up your phone with Clockwork's nandroid, you can install the engineering HBOOT (bootloader), which among other things allows you to use fastboot flash (or flashing-over-usb from your computer). This is unnecessary for most users but provides additional functionality for developers.
This is totally optional and dangerous - if the write to the phone partition fails the phone will be bricked. At the moment there is no cure for a phone that has been bricked by a failed hboot install."
That very last line is why Bubby should NOT include this in his one click... you think problems are bad now, wait till someone bricks a device and we can't unbrick it! D:
Click to expand...
Click to collapse
Thanks for posting that. I was just going by what they said to do in the CoreDroid thread, and it worked for me, thankfully
"
FAQ:
Again, it's recommended that you flash radio 26.04.02.17_M2 (Orange ES 1.75.75.2 / HTC WWE 1.72.405.3) or radio_26.06.03.24_M2 (TELUS WWE 1.84.661.1) or Radio 26.05.05.27_M3 - (Orange UK 1.84.61.2)
How do I flash a new radio?
In order to flash other radios you need to have ENG S-OFF. Once your device has that read this thread to learn how to flash a radio.img
How to get ENG S-OFF:
Download the attached "easy S-OFF.zip" at the botton of this FAQ.
Extract to a folder of your choice.
Connect your phone to a computer (make sure you have USB Debugging enabled. Connect charge only!)
Open my "Desire HD easy s-off.exe", click "S-OFF it"! Allow possible SuperUser request on your phone.
There could be force closes after the process, just reboot and everything will be fine.
Done. (in bootloader it should now show ENG S-OFF)"
http://forum.xda-developers.com/showthread.php?t=965207
No doubt, still a great find. It's definitely a temp cwm fix, so use as necessary, just be careful and DO NOT unplug your phone while it's flashing!
ClearD said:
No doubt, still a great find. It's definitely a temp cwm fix, so use as necessary, just be careful and DO NOT unplug your phone while it's flashing!
Click to expand...
Click to collapse
For me, it was a permanent CWM fix
Use this at YOUR OWN RISK! I take no responsibility for bricked or ruined phones, I just posted this in hopes it might help out people having CWM issues.
I just put that in my first post, hopefully it will do it's job
I could get into cwm, no black-screen for me though. Still couldnt do radios. Used this and bam new radio....Thanks for the info.
Lol Cali, remind me to "thank" you tomorrow I've been trying all night, but I'm at the 24 hr limit for "thanks". I appreciate the post update, and this really is a great find. I can't stress that enough lol. In the right hands, an engineering HBOOT is great.
btdt13 said:
I could get into cwm, no black-screen for me though. Still couldnt do radios. Used this and bam new radio....Thanks for the info.
Click to expand...
Click to collapse
You are very welcome!
ClearD said:
Lol Cali, remind me to "thank" you tomorrow I've been trying all night, but I'm at the 24 hr limit for "thanks". I appreciate the post update, and this really is a great find. I can't stress that enough lol. In the right hands, an engineering HBOOT is great.
Click to expand...
Click to collapse
No problemo, as the Terminator would say
Sry for bad English.
this work for all Desire HD devices such as branded device and ect
Now a downgrade method has arrived! After this process, you can use any root (+ S-OFF) method you want. Basically your device will be just like any other Desire HD with older build version.
1- Get stock 1.32 PD98IMG.zip ROM
2- format microSD as FAT32 (I suggest that the mirror can format with Memory Reader)
3- Download the attached file and extract it
4- Put PD98IMG.zip and attached file to your SD card
5- take the phone to boot loader (I suggested at the first turn off the phone battery click here again, in memory instead of its own And hold volume down button and turn on phone) and wait to be installed ROM.
What is this? That text has been copied almost completely from my downgrade guide.
pls put link
It is a sticky here in XDA. http://forum.xda-developers.com/showthread.php?t=905003
) this works diffrently and you don't need to any goldcard or pc conection.
The link is copied from the original thread.
Don't you need to trick the phone a lower version number if you have 1.72 installed in order to Update to a lower version number? eg. Cable connected from Phone to PC and the steps in the original thread?
That is right, this guide is fake, troll or something like that.
Jenxie said:
The link is copied from the original thread.
Don't you need to trick the phone a lower version number if you have 1.72 installed in order to Update to a lower version number? eg. Cable connected from Phone to PC and the steps in the original thread?
Click to expand...
Click to collapse
No. if you have 1.72 or highier you can downgrade easily.
jkoljo said:
That is right, this guide is fake, troll or something like that.
Click to expand...
Click to collapse
Why fake?? it's Work very well and it's better than your way. try it
it work great, thanks
WOWWWWW!
You're the man!!!
Incredible, worked like a charm.
So easy, so quick, so perfect..... I don't know why people speak without know about.
Thanks guy!!!
PD: can it be implemented like a new method to flash radio and roms? <- maybe a noob question....
kaotiko said:
You're the man!!!
Incredible, worked like a charm.
So easy, so quick, so perfect..... I don't know why people speak without know about.
Thanks guy!!!
PD: can it be implemented like a new method to flash radio and roms? <- maybe a noob question....
Click to expand...
Click to collapse
Haha clearly OP, wow this thread is funny.
may be speaking out of term here, but can anyone else confirm as the only ones to "confirm" this method works all write in the same "style" of english
If i'm on gingerbread (CM7) can I flash this and it'll be me back to stock firmware? (first version released?)
andywright1982 said:
may be speaking out of term here, but can anyone else confirm as the only ones to "confirm" this method works all write in the same "style" of english
Click to expand...
Click to collapse
Sorry for my english, I'm from spain ....
I see that you did not tried this method... then .... Why would discredit the work of another person without knowing?
I've tried it and it has worked perfect for me.
I'm not used to write much in the forums, but when i do it i try to know what I'm talking about.
I hope you can understand my poor and maybe ridiculous english.
Alright, I stand corrected, it seems to work for some people. The question is, does it work for people without S-OFF. Because that is what the downgrade is for, and people here just seem to be interested in going from higher custom builds to stock.
So, can someone with branded stock phone confirm this?
Thread close while this gets investigated....
@jkoljo...would you mind PMing this member and try to sort it out? I would get involved if you need me too
Cheers,
M_T_M
Your peaceful Mod
I've been on 3.24 firmware for a while, but wanted to revert as ICS has some minor issues. Good fun trying it though.
Anyway, I'm bootlooping like grandma's butt on a barstool.
I have crawled the forum and tried just about any/everything.
All I did was trying to run an incompatible ROM (gb) on the 3.24 firmware. Fair enough.. it doenst work. So I flashed 3.12. Nothing still... then I flashed 1.17 and the radio. Now no rom, ICS nor GB, will boot eithout looping. (Even when going back to 3.24 and ICS) I've tried downgrading hboot from 27 to 17. And yes, for every try I completely wipe (4ext, format all excpt fat32) and superwipe and also wipe cache and Dalvik. I've reinstalled every rom I have on my sd as well as trying to restore a couple of backups I have.
Nothing. Nada. Zilch. Still the same bootloop.
EDIT: 4Ext Recovey seems unaffected and works
Try starting again. What I recommend is you try downgrading the firmware and install a Stock RRU.
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
Why do people try to flash everything they can even remotely think of when something doesn't go as planned?
Probably the worst thing you can do... you're quite lucky you didn't brick your phone in the process.
If you want to use a GB ROM - flash a 1.17 Firmware from this link.
Superwipe
Install GB Rom.
Once you have that sorted and it's actually running (let it boot up completely at least ONCE!), you can flash the appropriate radio. (and please actually follow the instructons that came with it....!!!)
Just to confirm, I wasn't actually saying flash anything possible.. I basically wanted him to do what you just gave him the link to, however I'm not on my computer at the moment so it's a little hard to multi-task and source a thread that has what they need in it. He could've found the answer to his question pretty easy anyway.
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
jaaystott was right on the money. I downloaded the stock RUU package and I extracted the rom.zip. Renamed it to PG58IMG, threw it on the sd and voila. This rom package contains everything to downgrade bootloader, radio and all the other components.
anazei...don't get cheeky until you've actually READ my post. Lol! But still big ups for all suggestions. Yours was absolutely on my list of plausible remedies and would probably have done the trick, had the circumstances been different. :-D
Thanks guys! Always prompt help and response on XDA! :-D
Now, let's get down to brass tax: Why wouldnt anazeis solution work? I did do exactly what he/she suggests. Which is flashing back down to 1.17. I can clearly see that the stock rom.zip flashes heaps of stuff. And the 3.24 as well. But trying to revert there was quite obviously a component still un-downgraded when flashing fw and radios separately. What am I missing out on?
Anyone?
Glad that I helped solved your problem
I have no idea why that didn't work, but all I can possibly think is maybe the firmware or HBOOT didn't downgrade or something like that..
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
cyb0rgb0rg said:
jaaystott was right on the money. I downloaded the stock RUU package and I extracted the rom.zip. Renamed it to PG58IMG, threw it on the sd and voila. This rom package contains everything to downgrade bootloader, radio and all the other components.
anazei...don't get cheeky until you've actually READ my post. Lol! But still big ups for all suggestions. Yours was absolutely on my list of plausible remedies and would probably have done the trick, had the circumstances been different. :-D
Thanks guys! Always prompt help and response on XDA! :-D
Now, let's get down to brass tax: Why wouldnt anazeis solution work? I did do exactly what he/she suggests. Which is flashing back down to 1.17. I can clearly see that the stock rom.zip flashes heaps of stuff. And the 3.24 as well. But trying to revert there was quite obviously a component still un-downgraded when flashing fw and radios separately. What am I missing out on?
Anyone?
Click to expand...
Click to collapse
Hi
Could you tell me how to extract the rom.zip from the RUU.exe ?
Thanks
You simply:
- start the exe file and just leave it running
- go to your user profile's temp folder. Something like C:\Users\YourName\AppData\Temp
- sort the folder by date and enter the most recent directory with a guid as name
- drop down to the next guid folder as well and voila. There it is.
- rename it and put it in the root of the sd and the bootloader will start sanitizing the Sensation gone sour.
Here's a method for Linux/MacOSX as well:
http://www.kennynet.co.uk/2010/06/24/extract-rom-zip-from-ruu-in-linux/
An easier way to extract it is to use something like 7zip or win rar and simply right click on the exe and extract
GhostXSeries said:
An easier way to extract it is to use something like 7zip or win rar and simply right click on the exe and extract
Click to expand...
Click to collapse
True that! Totally forgot but thats a really smooth way to do it as well. Thanks!
First, I just wanted to send a huge shout-out to cyb0rgb0rg and jaaystott for helping me solve a similar problem I had found myself all yesterday evening. THANK YOU! I am very new to installing custom ROMs on my phone. Rooted the phone yesterday, and I realize I must have, right off the bat, installed some firmware with my original rooting instructions that for whatever reason rendered the phone unable to boot. It specifically had to do with the audio output, since as the phone was booting (in any ROM I would attempt), the output of "adb logcat" would cycle over and over and over again through the loading the audio drivers.
It took me a second to find the stock RUUs, but a link is here: http://forum.xda-developers.com/showthread.php?t=1074559
I was able to find the rom.zip in the Temp directory, as suggested, and although I was a little hesitant because the file was so huge, I flashed it with HBOOT. Success. Then, I loaded in the bootloader I started getting the hang of (teamwin 2.0). Flashed in the Virtuous Inquisition firmware, the Virtuous Inquisition ROM, and amazingly, the whole thing works. I'm going to try to retrace my steps to try to find out exactly which firmware caused this problem, but I suspect that many of the very similar problems I encountered while searching for a solution can be solved with this method.
So, thank you very much! You helped make a tired and desperate man very happy.
So here is the story.
I'm more of a linux user than anything else. I use Ubuntu Studio and Linux Mint on my home computer, and when I heard about the developers preview of Ubuntu Touch, I got excited.
Following the instructions in one thread here, I found it fairly simple to install Ubuntu Touch, and it looked perfect. However, it was much too early in development for use. Everything was kind of a placeholder, there was no network connectivity, phone capabilities, etc. So I went back and installed the rom I had used previously.
Here's where the problem happened. After successfully flashing the Rom to my phone and booting up into the GUI, if I clicked on anything it would reboot. Seems kinda funny, so I had tried about 5 other working roms, and they all did the same thing.
So I assume that when I installed ubuntu touch, it had actually removed a lot of the drivers for my Sensation.
HTC has been NO help at all in obtaining the correct software so I can fix my phone. Additionally, they don't even answer back my emails with comprehensible responses. I've explained this problem to them in great detail, and the extent of their responses are "if u can not find the softwares on htcdevs.com you will have to send your device in for repairs. If the damage is not covered under warranty we will let you know how much repair will cost, if you dont want repair you pay for shipping of unrepair device back to you."
Like, really?
I would like to do a fresh installation of the kernel, drivers, OS, etc so that I can use my phone again.
If you need more information don't hesitate to ask.
I hope someone has had a similar scenario, or at least know what I'm talking about and might be able to help me a bit.
What you probably need to do is flash (is it flash?) a RUU (Rom Update Utility). You can find them here.
EDIT:
Hmm.. You probably can't run .exes on Linux, can you? Maybe with Wine?
ridder215215 said:
What you probably need to do is flash (is it flash?) a RUU (Rom Update Utility). You can find them here.
EDIT:
Hmm.. You probably can't run .exes on Linux, can you? Maybe with Wine?
Click to expand...
Click to collapse
he can extract the rom.zip from ruu and flash it from bootloader
see here for that
http://forum.xda-developers.com/showthread.php?t=1672425 (step 4)
rzr86 said:
he can extract the rom.zip from ruu and flash it from bootloader
see here for that
http://forum.xda-developers.com/showthread.php?t=1672425 (step 4)
Click to expand...
Click to collapse
Oh thank you, I will check that, because I had just downloaded a RUU and booted into my windows partition, and attempted to run it. Since I can really only boot into recovery, it was only mounting my SD card, not my internal storage (i seem to recall it used to mount the device itself). So, the RUU for pyramid wouldn't run. If I can flash it, that would be best, I will have a look at that thread, thank you.
I think what happened is Ubuntu Touch stripped down android on my phone... I'm not sure if roms run as a replacement for that, or on top of it, I'm really still a beginner when it comes to phones, but usually I can manage to find the information I need to fix a problem... This is the most difficult problem I've had. Thanks again for the link.
rzr86 said:
he can extract the rom.zip from ruu and flash it from bootloader
see here for that
http://forum.xda-developers.com/showthread.php?t=1672425 (step 4)
Click to expand...
Click to collapse
Thank you again. You pointed me in the right direction and I got my phone working once again. Re-rooted and s-offd and now installed CM9. Thanks again for your help.
Hi,
First of all, I'm new to this Forum, but i've been following it for quite a while now since almost everything Android related you can find here. And People around here seem really knowledgeable.
I've trying to update my One SV K2_UL, and i seem to got it messed up.
I was able to flash the update, and everything went smoothely, until i got to the firmware files, a cannot get them to flash.
I guess the problem is my phone is S-ON, and i cannot change it's CID, although a tried several ways of doing it.
And i cannot guet my phone to be S-OFF, i tried Moonshine but it gets stuck on second test. - "Waiting for ADB".
My phone is exactly the same as leegreenaway refers in this post:
http://forum.xda-developers.com/showthread.php?t=2512742&page=9
so i guess, it's not an equipment problem, it was really my order of doing things that screwed this.
Can someone please help me? What can I do?
I tried to revert to old version but with no luck.
Thank you in advance.
Rui
Yes, as long you are S-On, you can't flash the firmware files.
If moonshine don't work for you, you can try the new rumrunner S-Off (which is made from the same people).
Take care on the instructions on the page there, as it is new, i can not really tell you how it will work.
I have tried rumrunner also, it behaved a little different from moonshine since it passed the second test, and found the device, but than nothing, it didn't go further it just said - "Press Enter to Exit.".
Thanks for the fast reply btw.
Then maybe this post, can give you a helping hand.
If you have Norton Antivirus, disable it. Make sure, you have a sdcard in the phone.
I did had Norton in the beginning of my day, but i already uninstalled it, just to make sure,.
I do have a sdcard on my phone.
So i tried running rumrunners once again, and took a ps of what is happening.
View attachment 2398349
When i see it right, you are on windows 8?
Windows 8 is known as not "driver-friendly" related to android/adb.
Maybe you have a chance to use a Windows 7 PC or even Linux.
Maybe @beaups knows whats the problem is...
Yes you're right,
i'm on windows 8.
unfortunately i do not own any PC with win7, althought ADB looks to be working right since i was able to use the shell and other adb stuff, i might as well give it a try tomorrow at work. I just hope i can turn this around, the phone is working great appart from that fantastic noise the speaker makes.
Thank you.
Well, today I tried to use both moonshine and rumrunner at work, but with no luck. The pc at work is running win7, althought the problem persisted exactly the same in rumrunner, in moonshine it was a bit different because it only stopped the second time it was waiting for adb. I was wondering if someone with the orange phone from UK could provide the firmware from that update, and if this souls male a difference.
Thanks again,
Sent from my HTC One SV using xda app-developers app
Last idea on my side:
You wrote in first post, you flashed everything except firmware. That means, you have the Sense 5 software already installed?
I think you should try then with the stock software, moonshine is made for.
Maybe its checking the version (HTC One SV (k2_ul) 2.14.401.6) and fails, because it is wrong.
Well, actually I got that same conclusion in my mind yesterday, just when I arrived at home from work. So I used the 2.14 odexed stock you provided in a thread, and from there I was able to run moonshine, it completed successfully, and after I just had to re-flash the 3.22 odexed, change the cid and flash the firmware. Voila, problems solved everything is in order now.
So the problem was only, the boot img moonshine was trying to flash would never work on my sys version.
Thank you very much for your help, this was a great learning experience.
Cheers,
Rui
Sent from my HTC One SV using xda app-developers app
Glad you got it sorted out.
old.splatterhand said:
Yes, as long you are S-On, you can't flash the firmware files.
If moonshine don't work for you, you can try the new rumrunner S-Off (which is made from the same people).
Take care on the instructions on the page there, as it is new, i can not really tell you how it will work.
Click to expand...
Click to collapse
Thankyou thiese s-off utility helped me to take s-off