Related
Hi folks.
You'll have to excuse me, as I know next to nothing about putting roms and whatnot into my phone - but I am super excited about being able to learn how, etc.
I'm currently using a totally stock and normal HTC Sensation 4G and have been since roughly the time it came out with my carrier. The phone has started being... weird, so I'm looking to change things around with it.
Anyways - I've been looking around the site and trying to find what exactly is the best starting point for somebody with absolutely no experience.
I've seen some noob threads here and there, but I'm not sure if they're leading me to readying my phone to throw no a new rom. Is there just some sort of state to put my phone into and then be able to flash whatever rom is available for it?
This is what I started looking at but I'm not sure if this a good jump off or not to ready my phone for fun changes.
Thanks for being patient with me on this.
Read this guide: http://forum.xda-developers.com/showthread.php?t=1192300
Basically, you need to S-OFF your phone, and install a new recovery. Then you can flash new roms from your new recovery.
Use the Revolutionary method in the guide to unlock your phone. Install the Clockworkmod Recovery, and Super CID if you want. That just means that you'll be able to flash a rom meant for *any* carrier, not just your own.
That's it.
59seconds said:
Read this guide: http://forum.xda-developers.com/showthread.php?t=1192300
Basically, you need to S-OFF your phone, and install a new recovery. Then you can flash new roms from your new recovery.
Use the Revolutionary method in the guide to unlock your phone. Install the Clockworkmod Recovery, and Super CID if you want. That just means that you'll be able to flash a rom meant for *any* carrier, not just your own.
That's it.
Click to expand...
Click to collapse
Thanks!
That's exactly what I needed. I plan on digging around when I get home.
Good luck. Just remember to read everything all the way through before you do anything, and make sure that you understand all of the steps. Most of the problems that people have is because they just don't read the information/guides.
59seconds said:
Good luck. Just remember to read everything all the way through before you do anything, and make sure that you understand all of the steps. Most of the problems that people have is because they just don't read the information/guides.
Click to expand...
Click to collapse
Fair advice for nearly anything!
Question about doing all this...
Do I have to have my phone connected to my computer? Or is this done primarily through the phone?
You'll need to transfer over some files. Super CID requires you to run commands to your phone from your computer, but that's it. It's definitely worth it to have fastboot and adb running on your computer in case you need it.
59seconds said:
You'll need to transfer over some files. Super CID requires you to run commands to your phone from your computer, but that's it. It's definitely worth it to have fastboot and adb running on your computer in case you need it.
Click to expand...
Click to collapse
Great! I will keep that in mind for when I'm there!
Is this generally a long winded process?
Nah The first time is a bit of work since you have to S-OFF your phone and install a recovery. But it's a breeze after that. So many people have done it and the xda forums are very helpful. I followed that guide the first time and had zero problems.
So, hopefully somebody will have a bit of an idea what to do here...
First things first. I'm doing this all through a bootcamp-esque program from my Macbook - and currently on Windows 7, as there's only Windows and Linux available for the Revolutionary method.
I've downloaded the program. Opened it into a folder, etc. Turned on USB debugging and done everything else the tutorial has mentioned.
Has anybody had similar issues before?
speps said:
Hi folks.
You'll have to excuse me, as I know next to nothing about putting roms and whatnot into my phone - but I am super excited about being able to learn how, etc.
I'm currently using a totally stock and normal HTC Sensation 4G and have been since roughly the time it came out with my carrier. The phone has started being... weird, so I'm looking to change things around with it.
Anyways - I've been looking around the site and trying to find what exactly is the best starting point for somebody with absolutely no experience.
I've seen some noob threads here and there, but I'm not sure if they're leading me to readying my phone to throw no a new rom. Is there just some sort of state to put my phone into and then be able to flash whatever rom is available for it?
This is what I started looking at but I'm not sure if this a good jump off or not to ready my phone for fun changes.
Thanks for being patient with me on this.
Click to expand...
Click to collapse
You mentioned the phone being "weird", in what way is it weird? If this turns out to be a hardware issue or something that requires you to send the phone back to the manufacturer, rooting the phone can void your warranty (if you have any warranty left).
Please keep this in mind prior to rooting your phone. There is a way to flash your phone back to stock and return S-ON but from what I hear it is a little risky and there is a chance of bricking your phone while doing it (as with any part of the rooting process).
When following directions for rooting, I would advise you to read the whole instructions list first to ensure you have an understanding of the whole process, so you don't get stuck at any steps. Make sure you follow the guides exactly as well.
Never heard of anyone doing this through bootcamp on a MAC, but as with any compatability issues, if you have any strange issues with any of the steps it is best to use a native Windows or Linux machine to perform the rooting process.
I have never had any issues with any rooting process, for my SGS and Sensation XE using a Windows 7 64bit computer.
rickadlee said:
You mentioned the phone being "weird", in what way is it weird? If this turns out to be a hardware issue or something that requires you to send the phone back to the manufacturer, rooting the phone can void your warranty (if you have any warranty left).
Please keep this in mind prior to rooting your phone. There is a way to flash your phone back to stock and return S-ON but from what I hear it is a little risky and there is a chance of bricking your phone while doing it (as with any part of the rooting process).
When following directions for rooting, I would advise you to read the whole instructions list first to ensure you have an understanding of the whole process, so you don't get stuck at any steps. Make sure you follow the guides exactly as well.
Never heard of anyone doing this through bootcamp on a MAC, but as with any compatability issues, if you have any strange issues with any of the steps it is best to use a native Windows or Linux machine to perform the rooting process.
I have never had any issues with any rooting process, for my SGS and Sensation XE using a Windows 7 64bit computer.
Click to expand...
Click to collapse
It's been doing a lot of the issues listed here - plus, the battery life is just absolute crap. I've ordered new batteries for it (the 1900mAh Anker ones people here discussed before) and taken a few other steps to try and make it work in my favour a bit more.
I was able to almost complete the S-Off process last night, although I hit a brick wall as it just continued on the "Zerging root" while using Revolutionary. Damn.
I may try again when I get home.
One thing NO ONE ever points you to do but is, in my mind, the most important thing is to try a make sure there is an RUU available for your current ROM.
An RUU (ROM Upgrade Utility) is a complete ROM from HTC which will restore your phone to stock should you need to send it back for a warranty claim.
To check for an RUU, you first need to know your current ROM version that your phone came with. Go to Settings>About phone>Software information and make a note of the 'Software version' e.g. 1.50.401.3
Once you have that, go here and try to find a file name matching the version:
http://forum.xda-developers.com/showthread.php?t=1074559
If you find one, download it and keep it safe
EddyOS said:
One thing NO ONE ever points you to do but is, in my mind, the most important thing is to try a make sure there is an RUU available for your current ROM.
An RUU (ROM Upgrade Utility) is a complete ROM from HTC which will restore your phone to stock should you need to send it back for a warranty claim.
To check for an RUU, you first need to know your current ROM version that your phone came with. Go to Settings>About phone>Software information and make a note of the 'Software version' e.g. 1.50.401.3
Once you have that, go here and try to find a file name matching the version:
http://forum.xda-developers.com/showthread.php?t=1074559
If you find one, download it and keep it safe
Click to expand...
Click to collapse
I'll be sure to do that. Thanks!
Would anybody know why I keep getting stuck at the "zerging root.." portion?
Unless it usually takes a few minutes, it seems to just... hang.
As far as I can tell, everything else is set up correctly for this to work.
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.
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
So, i was here back when the phone came out, unlocked the bootloader and got a few Roms in the start, and ended up with Paranoid Android V2.54 i believe, and never really cared about looking for anything new since i thought it was pretty good, and i enjoy as close to stock as possible. But now my phone is getting really slow, and i need a change. And getting back onto the forums here im just really intimidated by the amount of Roms, the term S-OFF and Kernel. I generally know the basics i suppose, but when i was installing Roms back in the early days of the HTC one S it was as easy as getting the rom on the SD card an flashing it. Im probably coming off as a bit stupid here, but i dont wanna brick this phone just because i did one thing wrong.
So where im getting at is, what Rom should i go for? I just need something easy to install, and nothing super flashy. As said earlier, i enjoy the stock android, and i wouldnt mind getting the newer version of android aswell. So give me some pointers, and feel free to give me the details on how to flash it as i havent done this in a while
Jahrern said:
So, i was here back when the phone came out, unlocked the bootloader and got a few Roms in the start, and ended up with Paranoid Android V2.54 i believe, and never really cared about looking for anything new since i thought it was pretty good, and i enjoy as close to stock as possible. But now my phone is getting really slow, and i need a change. And getting back onto the forums here im just really intimidated by the amount of Roms, the term S-OFF and Kernel. I generally know the basics i suppose, but when i was installing Roms back in the early days of the HTC one S it was as easy as getting the rom on the SD card an flashing it. Im probably coming off as a bit stupid here, but i dont wanna brick this phone just because i did one thing wrong.
So where im getting at is, what Rom should i go for? I just need something easy to install, and nothing super flashy. As said earlier, i enjoy the stock android, and i wouldnt mind getting the newer version of android aswell. So give me some pointers, and feel free to give me the details on how to flash it as i havent done this in a while
Click to expand...
Click to collapse
First thing you should tell us some more info about your phone, just to know better what guides and adices we should give you:
1. Phone model: S4 or S3 (is it with dual core krait 1.5 Ghz or with older dual core 1.7 Ghz processor?)
2. What hboot/firmware do you have, what radio, are your bootloader locked or not (at HTC Dev site)...in fact we need all the info that you have on your bootloader screen (power off phone then keep pressed VOLUME DOWN while pressing POWER)
3. What recovery do you use (CWM or TWRP) and what version?
4. Finally but not least....WHAT DO YOU WANT? A Sense ROM, an AOSP ROM, do you want latest Android version (4.4.2 KitKat) or it doesn't matter to you...things like this. You said something about this but maybe give more details
Then we might have some guides for you and some advices and you could choose among them based on your pers preference :good:
Rapier said:
First thing you should tell us some more info about your phone, just to know better what guides and adices we should give you:
1. Phone model: S4 or S3 (is it with dual core krait 1.5 Ghz or with older dual core 1.7 Ghz processor?)
2. What hboot/firmware do you have, what radio, are your bootloader locked or not (at HTC Dev site)...in fact we need all the info that you have on your bootloader screen (power off phone then keep pressed VOLUME DOWN while pressing POWER)
3. What recovery do you use (CWM or TWRP) and what version?
4. Finally but not least....WHAT DO YOU WANT? A Sense ROM, an AOSP ROM, do you want latest Android version (4.4.2 KitKat) or it doesn't matter to you...things like this. You said something about this but maybe give more details
Then we might have some guides for you and some advices and you could choose among them based on your pers preference :good:
Click to expand...
Click to collapse
1. According to Quadrant i have a CPU Frequency of 1512MHz, so by definition that should make it a S4
2. For recovery, im almost 100 percent sure its SuperSU, and heres the details from my bootloader:
VLE PVT SHIP S-ON RL
HBOOT-1.06.0000
RADIO-0.15.315018.19
OpenDSP-v21.1.0.32.0314
eMMC boot
Mar 15 2012.23:37;23
And yes i used HTC Dev website to unlock it. got some sort of key and everything.
3. The recovery i use atm is CWM 5.8.3.1 the none touch version. Tried the touch version a few times, but it doesnt seem to work for me.
4. For ROM as i mentioned i really like AOSP, and can't really see myself going for a Sense ROM unless there's something really awesome out there. Ive used CM 9 and 10, AOKP, ParanoidAndroid and one of those Pac-man ROMs before, and they have all been decent. But now i want something newer. Preferably something over 4.1.2 as ive had that for probably a year now, and i need SOMETHING new. I dont particularly want anything that isn't as complete as possible. The ROM im rocking now reboots my phone ATLEAST 1-2 times a day, and have some minor Wi-Fi issues. (not really that bad anymore after buying an expensive new ASUS Router)
So those are like my only things when it comes to ROMs. Doesnt need to be as flashy as coming with a completly themed interface and that sorts
I like CM11. It seems to running ok, but better check the latest in the thread.
http://forum.xda-developers.com/showthread.php?t=2528113&page=367
Jahrern said:
1. According to Quadrant i have a CPU Frequency of 1512MHz, so by definition that should make it a S4
2. For recovery, im almost 100 percent sure its SuperSU, and heres the details from my bootloader:
VLE PVT SHIP S-ON RL
HBOOT-1.06.0000
RADIO-0.15.315018.19
OpenDSP-v21.1.0.32.0314
eMMC boot
Mar 15 2012.23:37;23
And yes i used HTC Dev website to unlock it. got some sort of key and everything.
3. The recovery i use atm is CWM 5.8.3.1 the none touch version. Tried the touch version a few times, but it doesnt seem to work for me.
4. For ROM as i mentioned i really like AOSP, and can't really see myself going for a Sense ROM unless there's something really awesome out there. Ive used CM 9 and 10, AOKP, ParanoidAndroid and one of those Pac-man ROMs before, and they have all been decent. But now i want something newer. Preferably something over 4.1.2 as ive had that for probably a year now, and i need SOMETHING new. I dont particularly want anything that isn't as complete as possible. The ROM im rocking now reboots my phone ATLEAST 1-2 times a day, and have some minor Wi-Fi issues. (not really that bad anymore after buying an expensive new ASUS Router)
So those are like my only things when it comes to ROMs. Doesnt need to be as flashy as coming with a completly themed interface and that sorts
Click to expand...
Click to collapse
OK, I got more info now, maybe some others will step in and give you their opinions and advices. What I can tell
1. SuperSU is not a recovery (you already said you're using CWM)...it's the root program.
2. You have hboot 1.06 the same I had on my device some time ago (not too long ago). It has some advantages and some disadvantages. I'll try to be brief and prsent you all and you can decide what you wanna do.
First some background: S-Of basically means you are able to write to certain partitions on your device, partitions that are normally locked. Most important are the firmware/hboot partition, radio partition and kernel partition. If you are S-On, you cannot write/flash radio or firmware and you MUST flash any kernel via a separate command in fastboot.
Now what makes 1.06 hboot so special...it is behaving like a partial S-Off device even if you are not S-Off. What does this mean? You will be able to flash radios and kernels as any other S-Off user. Only thing you won't be able to flash is the firmware/hboot. On the other hand, all new ROMs require hboot 2.13/2.15 or the leaked 2.16. That means that IF your current hboot allows you to run such a ROM, you won't be able to flash it unless you're editting EVERY TIME the updater-script in the ROM ZIP you're flashing to bypass the hboot check. So things will become little bit complicated.
To avoid all these you should first S-Off then you should upgrade to hboot 2.15. This is the last official firmware and it is supported by all new KitKat ROMs. DO NOT flash 2.16 firmware unless you would like to flash and use Sense based ROMs like MaximusHD.
I made S-Off by using Rummrunner because I found it the simplest way to do it...it's like a one-press-S-Off. If that doesn't work for you, you can try other methods like Facepalm or Moonshine. You can find separate threads for each in Dev section and I'll also link them below
Rummrunner
Facepalm
Moonshine
After you made S-Off, next step will be to upgrade your hboot/firmware to 2.15. You can use the flashable ZIP from THIS thread and you'll find info on how to do it in the thread. I would suggest you to choose the Unbranded 2.15 hboot and that has also the red warning gone (the one you see when start up the device with "This device is for development purposes only...bla bla bla")
For all the above you might also want to check/try a tool that incorporates most of them. You can find it in THIS thread.
Now that you have S-Off and upgraded your hboot, you might want to flash a newer radio. Hint:If you're satisfied with your current signal strength, mobile data and so on, don't flash another radio. Even if in a ROM thread it is recommended or mandatory a certain radio, my advice is to first try the ROM with your current one and only if performance is not satisfactory, flash another radio.You can find radios in tecardo's thread HERE or if you want the newer radios you can find radio 1.20 HERE or 1.35a HERE. One more note regarding tecardo's thread with the radio collection...that thread is old and some info is not updated. Just remember that you must flash ONLY the V6 Sense Radio installer for any ROM you'll be using, being it sense based or AOSP. Also ignore that warning that the procedure is only for hboots below 1.3...at that time there was no S-Off (remember what I've said about the particularities of 1.06 hboot earlier). Now things are different, you're S-Off so you will just need to flash it
Before flashing, you might consider upgrading to a newer recovery. I would recommend you the latest official TWRP 2.7.0.0 that will support flashing anything made for hboot 2.15. If and only if you decide to try sense ROMs based on hboot 2.16, you'll need a different recovery specific for 2.16 and that you'll get from that specific ROM thread. Official TWRP downloads for Ville S4 are HERE
Now youre almost done. You just need to pick your ROM and flash it...pretty difficult task considering how many they are. I tested most of AOSP ones and also some Sense based ones (not the ones for hboot 2.16 tho). I don't want to advice too much here since it could be considered I favour one or another...the truth is I do and that's normal, but I'd like to be objective
First, all KitKat ROMs are pretty stable. On CM11 there are regular nightlies and there are also less stable or bugged builds but this is expected. So you might try several ROMs to see which suits you most and you can decide by reading each ROM's thread. I'll list some ROMs (not all), the ones that are updated most often and I've tested, in no particular order...in fact I'll list them alphabetically to avoid interpretations
AOSP based
Beanstalk
CandyKat
CM11
Infamous (IOAP)
PAC-Man
TwistedKat
Vanir
Sense based
Viper ROM 3.1.3
Liberty ROM
Sorry for the long post but I wanted to get most in a single place and if you'll have more questions we'll detail them later. Just try something... READ READ READ...each thread contains valuable info about each procedure and step and also the experience of the users. I know it is easier to ask but don't forget it's YOUR PHONE and YOUR INTEREST to see things working on it. So you should make some effort to read and search also
Good luck
I've read the entirety of your post now, and it's definetly helpful!
As it's pretty late here atm, i will come back to the tread tomorrow and S-Off and all that jazz. Im not a complete moron on this area, allthough thats what it probably seemed like Im glad i asked before i did anything, cause this was alot more complicated then when i was flashing ROMs when the phone came out.
I will definetly try to hold on to my current Radio as i have had no complaints ever on connection and service. So thanks for telling me about that, otherwise i would probably have flashed a new one each time.
Ill be sure to keep you posted on my progress tomorrow, just incase i totally **** up or something, or just cant get myself to understand something. If it is as easy to flash ROMs as it used to be once im ready to flash again, ill figure out my Next ROM, so im grateful that you listed a few of them that i can try out.
Again i wanna thank you for taking the time to explain a total Noob how to go about doing this, i really appreciate it!
rapier's post just about expresses all the basic info you need, couldnt have been put better!!
as far as going on to the newer sense based roms i'd suggest not to take that road yet as they require hboot 2.16 and it can get fairly tricky to go back to the previous hboot.
also for hboot 2.15 also you have more choice for roms available... just a point of view!!
happy flashing!!
So, now im totally lost. did the S-off, and now im trying to do the firmware, but im clueless here as i cant find the folder adb/fastboot in my platfomr-tools sdk folder or whatever you wanna call it. It wants me to place the firmware inside the adb folder, and i cant find any folder with that name.
I followed a guide on how to get adb working on my computer as i did not have that anymore on my PC, so had to redo it.
was following the guide, and did not see this "2. Now place the Firmware_named_something.zip into your adb/fastboot folder" at first, and tried to flash and was welcomed with cannot open "named file here" for obvious reasons when i saw step 2.
but this step 2 is what is confusing me, as ive mentioned, there is no adb/fastboot folder. is this a folder i make somewhere in my sdk? or what am i missing here. to give you the full info, i used this guide:
http://forum.xda-developers.com/showthread.php?t=1752270
the second post.
i remember having fastboot in that sdk folder on my old PC, but did not get it this time around when following these instructions, maybe thats what im missing
Jahrern said:
So, now im totally lost. did the S-off, and now im trying to do the firmware, but im clueless here as i cant find the folder adb/fastboot in my platfomr-tools sdk folder or whatever you wanna call it. It wants me to place the firmware inside the adb folder, and i cant find any folder with that name.
I followed a guide on how to get adb working on my computer as i did not have that anymore on my PC, so had to redo it.
was following the guide, and did not see this "2. Now place the Firmware_named_something.zip into your adb/fastboot folder" at first, and tried to flash and was welcomed with cannot open "named file here" for obvious reasons when i saw step 2.
but this step 2 is what is confusing me, as ive mentioned, there is no adb/fastboot folder. is this a folder i make somewhere in my sdk? or what am i missing here. to give you the full info, i used this guide:
http://forum.xda-developers.com/showthread.php?t=1752270
the second post.
i remember having fastboot in that sdk folder on my old PC, but did not get it this time around when following these instructions, maybe thats what im missing
Click to expand...
Click to collapse
ADB/fastboot are not folders, are commands. What that instruction meant was to place the firmware zip in the same folder where your ADB/fastboot executable is. Usually this is in "android-sdk/platform-tools". You'll notice there the ADB and fastboot executables
Rapier said:
ADB/fastboot are not folders, are commands. What that instruction meant was to place the firmware zip in the same folder where your ADB/fastboot executable is. Usually this is in "android-sdk/platform-tools". You'll notice there the ADB and fastboot executables
Click to expand...
Click to collapse
OMG! That makes more sense, still that sentence he used in the guide was pretty misleading though. literally tried making a fastboot folder with the .exe in alot of different folders xD
Will try that one out and see if it works! Thanks, AGAIN!
EDIT:
Just tried to put the firmware inside C:/android/sdk/platform-tools/ folder, but still i got
"Error: Can not open 'Fuu_Downgrade2.15_Unbranded.zip'
EDIT:
Turns out there was a program instead of a .exe :s just tried though, and it failed.
"FAILED (rempote: 99 unknown fail)
EDIT:
Apparently the S-OFF didnt work. Tried Rumrunner, as i didnt understand jack **** about the alternatives
EDIT:
Tried Facepalm aswell, not 100 percent sure if i did it right though, as there was no confirmation anywhere, but still no S-OFF
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.