Related
The tutorial is for 1.33.00010 but I have 09: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
Am I stuck?
did you try?
bengrulz said:
did you try?
Click to expand...
Click to collapse
If I try and flash an SPL I don't think will work then my device will be bricked.
"In order to replace the SPL on your phone and install CyanogenMod on the system, you will need a customized recovery utility. Ordinarily, fastboot would be the easiest means of installing the utility but Rogers is now distributing phones with v1.33.0010 and higher SPL versions (aka: "Perfect" SPL) which prevent fastboot from flashing image"
it seems to me that youd be okay.
also in the future this is not the correct section for these sorts of questions
bengrulz said:
"In order to replace the SPL on your phone and install CyanogenMod on the system, you will need a customized recovery utility. Ordinarily, fastboot would be the easiest means of installing the utility but Rogers is now distributing phones with v1.33.0010 and higher SPL versions (aka: "Perfect" SPL) which prevent fastboot from flashing image"
it seems to me that youd be okay.
also in the future this is not the correct section for these sorts of questions
Click to expand...
Click to collapse
Apologies, I'm not sure what I'm supposed to do now as to how to root my phone, and if it's going to break because of this
my phone had that for hboot too and i followed that same tutorial and now my phone is bricked. could this be why?
I started with the same SPL as you and just rooted my phone today by following that guide.
That being said, I had to deviate from the guide in order to install an SPL.
The guide tells you to use flashrec from google code, but that older version didn't work on my phone. Write down the URL the old one tries to use, then use it with a new one from here:
http://zenthought.org/content/project/flashrec
And all should work out just fine.
Hi all,
I foolishly flashed the Korean FRF91 onto my N1 and now I have SPL 0.35.0017 instead of the normal 0.33.0012 version.
To downgrade, I have tried:
- repacking the 0.33.0012 HBOOT into an update.zip (Looks like it worked, but it didn't)
- Flashing 0.33.0012 through FASTBOOT (Verification failed)
- Applying an older Google update (Main version is older)
Any ideas?
Thanks!
http://android.modaco.com/content/htc-desire-desire-modaco-com/310970/how-to-downgrade-hboot/
OK, I think that worked...
But now my N1 has an HTC logo on the screen for FASTBOOT.
can you explain how do you have made .
i don't understand the tutorial. (i m french :s)
if you can link the file you have apply.
thank's
cursordroid said:
OK, I think that worked...
But now my N1 has an HTC logo on the screen for FASTBOOT.
Click to expand...
Click to collapse
Probably because the link given by baseballkyle is in the "HTC Desire" section of the modaco forum, not nexus one.
Yes,
I would also appreciate an explanation on how you did it.
I tried it but it didn't work for me.
The hboot.img doesn't work. If I try a zip version it seems that the device accepts it and flash it but i keep having the wrong version installed.
Could you explain how you made the mtd0.img (with which numbers) and provide a link to the hboot version that worked for you?
PLs Help Also
Pls tell us also how u did it, thanks..
http://forum.xda-developers.com/showthread.php?t=726258
I have posted instructions here.
Great!!!
The key was applying the hboot file through the PASSIMG.ZIP and not just alone.
Fantastic.
Thanks a lot
nexus Hboot
What happen if I install the korean hboot. Because everybody is complaining about it. They want to return back to stock Hboot.
Though that hboot is newer currently all the signed firmwares (original ones, CM6, and whoever provide signed builds) check that the hboot version installed in the phone is 0.33.2012.
If you don't have that one then you will not be able to install any of this firmwares directly.
With some manual work you can make it happened but forget about OTA updates (stock OTA updates, CM-updater OTA updates, Rom Manager OTA updates).
If you don't care about that then you are fine.
help
i cant install any ota update can someone please help i went to erd 79 hoping that would fix everything
So what is the correct hboot version to use? I currently have 0.33.0012
Sent from my Nexus One using XDA App
Edited in blue font on 3/24/2012 @ 9:11PM
FYI:
WARNING!
Several people have had serious issues in updating to ICS while using a custom rom/recovery. I hate seeing bricked devices & if you were an early user of the custom recovery, there was an overwrite flaw that can cause serious issues when updating using ruu's & other factory firmware such as OTA's.
While this has been used by many & is the safest way to update, I do not know what changes you have made to your device/firmware. As always, anything custom is used at your own risk, that said I believe this is the safest way to update to ICS particularly for those that have not changed their recovery since the first release or two. Theire are detailed instructions to help you minimize the risk involved with updating an unlocked device.
Before updating to ICS, make sure you have a newer version of Recovery. One of the first recoveries released could not be overwritten without first flashing another moddified factory recovery first. Updating your device firmware with the older non-writable recovery will stop the device from reflashing the needed files after the first reboot & may cause other issues for some users.
If you try to update to ICS using this recovery you will get BSOD, boot loop or worse, qshsub_dload. All of these are fixable, but the last is still being worked on & as of this time requires jtag/riff to recover from.
If you're using a custom recovery that is older, take note of version & try to flash newer recovery. If recovery fails to be updated, then you are using a flawed recovery & need to flash two files before updating to ICS.
I highly recommend fastboot flashing to the attached recovery before updating your device. This recovery has many features & is more current than the release in the thread. You will have to re-install the recovery again after using the PH39img ICS update, which changes your SBL, Radio & other component firmware required to run ICS.
If you want to use the stock OTA, it is recommended that you return to stock recovery & relock your device using ADB/Fastboot. To flash stock ruu or OTA, you must relock your device. It can be unlcoked using the unlock bin file again from HTCDev.
The command to relock you device is "fastboot oem lock"
This info is in particular for AT&T customers.
The absolute safest way to update to ICS is to relock your device & return it to as close to stock as you can get it. Relocked you can flash the leaked GB AT&T rom in football's thread. Once complete, you can now download a final RUU from the HTC website at: http://dl3.htc.com/application/htc_vivid_att_RUU_3.26.502.56_US.exe
Using the stock GB recovery & firmware in conjunction with the new RUU is probably the best way to ensure a safe flash since you are then using firmware tested by HTC on devices & made to work together. We have know for some time that locking the device is temporary & unlocking it again can be acheived in many cases with your original unlock_code.bin, or by simply obtaining a new unlock_code.bin after registering/logging in to the htcdev.com website.
The next safest way to update is to return to GB & the stock recovery, relock your device & receive the OTA update. But for those that want to live in the fast lane, lol, this is the method that I & several hundred others have used without incident.
I am posting a link that includes many tools & a custom recovery that I highly recommend. Take note of the information in the Instructions.txt to have a safe ICS upgrade experience.
The recovery included is CWM based recovery. The only difference is it adds some touch support & correct Nand backup abilitiy as well as some nice tools available in newer versions. If you are NOT familiar with flashing via fastboot, all you have to do is extract the zip to the any folder & double click the batch (.bat) files & they will automatically write the recovery or whatever boot.img you select. The recovery script is only for the WCX version of CWM though. Just make sure you extract the files to a folder on your PC that does not have any spaces in the naming. That means if your pc is named Joe Smith-PC, you cannot use the Documents folder or any library folders, so I suggest using C: or create a new folder in c: without space, i.e. C:/Android
The wcxrecovery is CWM based, just more recent, updated with full nand backup support & capacitive button support. All of the files have been safely used & tested extensively by WCX, his rom team & his beta testers. The recovery is also compatible with all of the custom roms (GB & ICS) that I have played with. These items are for users & not to be cooked into public roms without permission of Wild Child. I posted it here due to all of the requests for help I have gotten over the last several days & the amount of time it was costing with one on one support.
If you choose to use the All-In-One tool located Here: http://forum.xda-developers.com/showthread.php?t=1498003 to unlock your device again & still want to use the newer wcx recovery in my zip, you can simply navigate to the /data/recovery folder for the all-in-one kit & replace the recovery included there with the wcxrecovery.img & then copy the existing recovery name (should be recovery-cwm-vivid-5.5.0.4B2.img) delete the file recovery-cwm-vivid-5.5.0.4B2.img, & rename the wcxrecovery.img to recovery-cwm-vivid-5.5.0.4B2.img. You can then use the all in one tool to unlock & flash the new recovery, albeit a few more steps than just using the batch file I included.
Thank you to the developers & owners of the included firmware/tools for allowing users to safely update custom roms to ICS. Please do not Donate to me for any of these items, I merely packaged together the work of others & wrote a pair of scripts to make things easier.
http://www.mediafire.com/?n4x2pcn1jw0g206
Hey can you include a cwm recovery image as well
Sent from my HTC PH39100 using XDA
The wcxrecovery in the zip is CWM based. It is just updated & it includes capacitive button support.
We have two videos...one is for those who have already unlocked their bootloader and one for those with a brand new phone wanting to unlock the bootloader from being locked from the factory. They will probably be updated again but here are the beginning videos
Already Unlocked Phone Video ccb101
Locked Phone From the Factory New Video Randong
WC
Just got a error when trying to download.
Third try it worked.... Sorry false alarm.
Sent from my HTC PH39100 using XDA
GSLEON3 is great! Good advice. I was on gingerbread but had an unlocked boot loader and rooted. Did exactly as he said, relocked boot loader, reinstalled gb to factory standards, accepted ics ota, installed and unlocked my phone. No need to rush into getting ics. It is not worth messing up your phone to save a couple of minutes. It took very little time, maybe an hour in all. Just make sure to have your phone charged up as well.
The videos run through everything from flashing hboot to finally flashing the roms
Dropbox suspended my account for 3 days due to high traffic I am uploading it now for wildchild and he will upload it to his YouTube page. Sorry for any inconvenience. Eta is about 2 hours from now.
Sent from my HTC PH39100 using xda premium
ccb101 said:
Dropbox suspended my account for 3 days due to high traffic I am uploading it now for wildchild and he will upload it to his YouTube page. Sorry for any inconvenience. Eta is about 2 hours from now.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Thanks for you work on the video! I really learn so much by watching someone else do the steps. That is not cool how they suspended your account.
megatronisabeast said:
Thanks for you work on the video! I really learn so much by watching someone else do the steps. That is not cool how they suspended your account.
Click to expand...
Click to collapse
Your welcome glad I could help
Sent from my HTC PH39100 using xda premium
Video finally edited and uploaded to youtube channel
WC
My toolkit has been updated with this new recovery.
http://forum.xda-developers.com/showthread.php?t=1498003
Wild Child said:
Video finally edited and uploaded to youtube channel
WC
Click to expand...
Click to collapse
Just curious... as I don't own the AT&T version.
where about is that recovery flash-able AT&T ICS file shown on the video ??
all I see available are the RUU and the Velocity version..etc
BTW... I have the Rogers version but SIM unlocked it to use with Bell ( and other carriers ).... for future reference... I can only flash Rogers released version...correct ??
Or when DEV released a universal version... then all bets are off ?? LOL
Thanks
UnicornKaz said:
Just curious... as I don't own the AT&T version.
where about is that recovery flash-able AT&T ICS file shown on the video ??
all I see available are the RUU and the Velocity version..etc
BTW... I have the Rogers version but SIM unlocked it to use with Bell ( and other carriers ).... for future reference... I can only flash Rogers released version...correct ??
Or when DEV released a universal version... then all bets are off ?? LOL
Thanks
Click to expand...
Click to collapse
http://www.wcxxperia-nce.com/index.php
Here you go. Several versions available. You have to sign up to see the vivid forum. This is wild child's site. Just follow all directions and you won't be disappointed.
You don't want to use the ruu to flash the att ics if you are on rogers. It would change the radio and you wouldn't be able to use your phone.
megatronisabeast said:
http://www.wcxxperia-nce.com/index.php
Here you go. Several versions available. You have to sign up to see the vivid forum. This is wild child's site. Just follow all directions and you won't be disappointed.
You don't want to use the ruu to flash the att ics if you are on rogers. It would change the radio and you wouldn't be able to use your phone.
Click to expand...
Click to collapse
There's no love there for us Bell & Rogers owners ?
I thought ... by SIM unlocked + Bootloader unlocked & rooted roms & everything... I now have a world phone that can adapt to the spec Freq. , that I can take anywhere ?...etc. ( provided that the country uses one of the compatible freq. )
how does this radio part of thing come into play ?
I've been able to use my past devices flashing different radios on them and have used them oversea successfully 3G+ ...etc
actually... AT&T freq. bands are compatible with BELL & ROGERS up here in north.... it's T-Mobile that uses the incompatible freq.
There is no changing radios on these phones,only boot.img,recovery.img and a rom....no s-off no radios flashing
Wild Child said:
There is no changing radios on these phones,only boot.img,recovery.img and a rom....no s-off no radios flashing
Click to expand...
Click to collapse
my original Nexus One can flash custom radios with S-ON intact. why is that so ?
UnicornKaz said:
my original Nexus One can flash custom radios with S-ON intact. why is that so ?
Click to expand...
Click to collapse
Well I can tell you the raider/vivid is not able to flash radios with S-0n. if we could i would have ICS already.
You may find the answer as to why you can flash the radio with S-on in the nexus One thread.
Just a thought.
Ahh...Technically not true. The RUU & PH39IMG files have.....New Hboot & radios in them as well as SBL files. So, as long as the signaturre is correct, you can flash radios. You just can't use CWM to flash radios, but why would you want to anyway? There are not many compatible LTE radios out there yet, so it is pointless.
As for the NEXUS One...It is a Nexus line & is you are flashing radios from anything other than OEM PHxxIM.zip or RUU, then the radio secu_flags most certainly are off, regardless of S-Off Hboot status.
But whomever started the "you can't flash radios on S-On devices" was misinterpreted or misunderstood. With correct signature & byte typing you can flash modem, misc, hboot, sbl, & radio files. Just nobody has packaged all the tools & written the scripts that are needed to make it feasible & simple enough for average users.
Getting the phone to say S-Off is just a matter of two bytes in the image, however, to truly be S-Off (Even many S-Off devices are not truly S-Off in the strict sense) you need the radio, hboot/spl & kernel to all agree.
do we have to be locked to do the ics ruu update?
I know these questions have largely been answered in bits and pieces spread over hundreds of threads, however, as a newcomer to the forum I can safely say understanding everything fully is a very daunting task. I'm having trouble grasping the relevance of RUUs, CID numbers.
I bought an HTC One from the carrier 'TIM' in Italy. It came with Hboot 1.54. I unlocked the bootloader, I installed a custom ROM, I rooted it, I tried out a custom kernel. I do not have S-off. I am confused.
1. The /boot partition on the file system contains both the bootloader(hboot) and the kernel, is this correct ?
1.a. If so, updating the kernel (by flashing it from recovery) is only affecting the /kernel subdirectory of the boot partition ?
2. An RUU functions as a 'stock restore' from what I understood, however it cannot be used to downgrade. I am uncertain about what this means. If an RUU is a 'stock restore package' from HTC- it includes stock kernel, rom, and recovery.
2.a. Will I be unable to use an Android 4.2.2 RUU to return my HTC One (currently running Maximus HD 14.0 (base 3.22)) to stock 4.2.2 then use OTA updates to get to stock 4.3 ?
2.b. Will the previously mentioned stock HTC OTA updates update my firmware to the latest version?
2.c. From past experience, when I talk about firmware I'm used to considering as the software running at the lowest level abstraction in the computer, aka hardware level. However, I have read posts on the forum where the firmware version IS the build number (in my case 3.22.1540.1 CL252721 release-keys) and that it describes the version of android that is running. Which is it ?
2.d. What is the deal with needing to have S-Off to update the firmware if it apparently updated with me normally? I went from build no. 3.17 in MaximusHD 13.0, to 3.22 in Maximus 14.0
3. On the HTCDev website there is a section called "Kernel Source Code, Binaries and Updates for HTC Android Phones", filtering for my TIM HTC One I get two hits one running Android 4.1, the other 4.2.2
4.1:
Type: CRC Kernel: 3.1.1 Description: 1.29.901.2_R
4.2.2:
Type: MR Kernel:3.4.1 Description: 2.24.901.1
What does the type designate ?
What does the number in the description represent ?
I know that the '901' references my carrier (TIM italy) what does the rest of that number mean? I have seen RUUs with number 2.29.x.x and cannot understand if they are more recent or older than RUUs with numbers 2.24.x.x or 3.x.x.x, for example on http://www.htc1guru.com it is mentioned that restoring to a 2.24 nandroid backup is reccomended as it will be compatible with the updated firmware, unlike a 2.29 backup. It is implied that 2.29 is OLDER. I am confused.
FINALLY, what is the relevance of the CID? Baseband version is the 'radio' firmware am I right ? How does this get updated?
Again I apologize for making such a long post, however it is hard to find a post containing all this information while making it clear how all these things are relevant to EACH other, I hope there are other people who share the same problem and that this may be of some help to them
answers
definitely not an expert but I will try to answer some of them.... In case I am wrong I am sure someone senior will rectify...
1. The /boot partition on the file system contains both the bootloader(hboot) and the kernel, is this correct ? As far as I know, YES, def Kernel not sure whether hboot is always there or not.
1.a. If so, updating the kernel (by flashing it from recovery) is only affecting the /kernel subdirectory of the boot partition ? As far as I know, YES
2. An RUU functions as a 'stock restore' from what I understood, however it cannot be used to downgrade. I am uncertain about what this means. If an RUU is a 'stock restore package' from HTC- it includes stock kernel, rom, and recovery. You can use it to downgrade. You make sure you have got the right hboot installed though, some RUUs require old hboots.
2.a. Will I be unable to use an Android 4.2.2 RUU to return my HTC One (currently running Maximus HD 14.0 (base 3.22)) to stock 4.2.2 then use OTA updates to get to stock 4.3 ? YES you can use Android 422 RUU t ogo back and get the OTAs. I have done it multiple times.
2.b. Will the previously mentioned stock HTC OTA updates update my firmware to the latest version? Updates firmware. YES.
2.c. From past experience, when I talk about firmware I'm used to considering as the software running at the lowest level abstraction in the computer, aka hardware level. However, I have read posts on the forum where the firmware version IS the build number (in my case 3.22.1540.1 CL252721 release-keys) and that it describes the version of android that is running. Which is it ? rRight with the first sentence. Version of not the Android but the update of the HTC
2.d. What is the deal with needing to have S-Off to update the firmware if it apparently updated with me normally? I went from build no. 3.17 in MaximusHD 13.0, to 3.22 in Maximus 14.0 ... sorry dont get the question?
3. On the HTCDev website there is a section called "Kernel Source Code, Binaries and Updates for HTC Android Phones", filtering for my TIM HTC One I get two hits one running Android 4.1, the other 4.2.2
4.1:
Type: CRC Kernel: 3.1.1 Description: 1.29.901.2_R
4.2.2:
Type: MR Kernel:3.4.1 Description: 2.24.901.1
What does the type designate ? Dont know this sorry,
What does the number in the description represent ? Dont know this sorry.
I know that the '901' references my carrier (TIM italy) what does the rest of that number mean? I have seen RUUs with number 2.29.x.x and cannot understand if they are more recent or older than RUUs with numbers 2.24.x.x or 3.x.x.x, for example on htc1guru it is mentioned that restoring to a 2.24 nandroid backup is reccomended as it will be compatible with the updated firmware, unlike a 2.29 backup. It is implied that 2.29 is OLDER. I am confused.
FINALLY, what is the relevance of the CID? this is a kind of an id number for your phone to be recognised eg. what region it belongs to etc.
Baseband version is the 'radio' firmware am I right ? RIGHT
How does this get updated? THERE IS A LINK SOMEWHERE IN THR FORUMS
First of all thanks for taking the time to read and reply, you're awesome.
What I meant about how the radio firmware is updated is, if upgrading my rom to base 3.22 from 3.17 updated the firmware accordingly why have I read EVERYWHERE that updating firmware requires s-off and that it must be done through fastboot having downloaded the according files that are linked on the forums. Additionally, why is the radio not updated as part of the firmware and what is the relevance of the carrier id? Does the radio firmware change according the carrier for optimal performance on whatever bands they operate on?
I'm sorry for all the questions haha today I thought my firmware would be stuck on an old version so I was trying to find out how to return to stock to update it, and understood that I couldn't because a) can't find RUUs for my carrier x.x.901.x and b) I have s-on w/ hboot 1.54. Which by the way didn't update and is still 1.54
Again, you are awesome
Sent from my HTC One using xda app-developers app
Radio are updated almost always including with OTA
Sent from my HTC 802w
1. As @bcan13 said, as far as I know also, yes,
1a. Flashing a custom kernel will also effect modules and add certain mods. Some will make changes to /system so that the mods will be effective. They can also effect libs for things like camera improvements.
2. An RUU is an .exe program file from HTC, it rewrites everything one the phone; firmware, hboot, kernel, rom, recovery. Before starting the flashing process it checks your current firmware version, it will not run if it is not installing a newer version. It also checks CID and MID.
2a. I don't believe so, the current RUU has the same firmware version as your phone is currently running. You would need to wait until the 4.3 RUU comes out. Also, it would need to match your CID and MID.
2b. Official updates will upgrade your firmware version.
2c. Firmware usually contains; Hboot, radio, recoveries, and drivers, as far as I know.
2.d S-off is security off, without security off you can not flash unsigned .zip's in fastboot or ruu mode. This means the only way to update firmware is through an official HTC OTA or RUU, which is signed. S-off also disables many other system checks, but more on that later. What you see in Settings - About Phone - Software is not always accurate, it is just displaying what the build.prop says it should be, this does not mean that's what it really is. To see accurate information boot into bootloader - "fasboot getvar all"
3. These are Kernel source code. It's required under the GPL (General Public License) that all distributed software based off the linux kernel (which Android is) release the source codes. This is just HTC following that mandate, they mean nothing unless you plan on compiling a kernel from source.
The CID and MID are Carrier ID and Model ID. RUU's and OTA's and other official software are device specific. To flash a RUU the CID and MID must match. They are also used to control OTA's. (AT&T phones wont receive Developer's Edition OTA's and vice versa, because they have different CID's. When HTC pushes an update they only push it to phones with XXX__XXX CID. HTC Pushes out an update for the GPe phones, other phones wont get it because having a CID of GOOGL001 is required.)
Also, radio's are flashable via recovery.
Let me know if you need help with anything, or have any other questions. Also, more knowledgeable users feel free to correct anything I missed or got wrong.
I found a twrp backup that I believe I made just after unlocking and rooting my phone, I also believe I did an OTA update to 4.2.2, but otherwise it should be stock.
I use CWM now, how would I use this backup? I can install twrp but would this backup even show up? Would I also then have to flash the stock recovery after restoring from the backup?
Assuming the backup works, can I flash any stock recovery or is it also cid specific?
Finally, can I flash radio without s-off? If so, will any radio work or is it carrier specific!?
Thanks for your help!!
Sent from my HTC One using xda app-developers app
Flash TWRP. Restore backup. Download a 4.2.2 OTA and open it up. Pull out the recovery.IMG and flash it. That should work?
There are recovery flashable radio.zip's (not to be confused with fastboot flashable zips).
Everyone's experience with radios is different, so you'll have to try them. I have good reception with the latest GPe radio.
Sent from my HTC One using XDA Premium 4 mobile app
But there isn't an issue with flashing a radio from a US base to an EU phone?
The backup I have is probably 4.2.2 so I shouldn't be able to download the ota from my phone, and I can't find ANYTHING for my cid on the forums, or through Google. Is the recovery image cid specific?
Sent from my HTC One using xda app-developers app
Firstly, thank you for reading this post. I appreciate that there are a number of posts already covering a lot of what I will be asking (I have already checked and Googled) but in much the same way you end up watching a video of a cat rescuing a child from Narnia on YouTube when you originally started with videos about the political stability in the Middle East, the tedious link between start and finish is now well and truly blurred!
With the above in mind, the aim of this post is to try and collate answers to my questions in one place. I will try and be as clear as possible.
It is also worth mentioning I am not completely new to this. I previously owned an HTC Sensation which I rooted myself (even used the paper clip technique) but the world of ROMs and “Framework” etc seems to be totally different to what is was a few years ago.
I suppose I will start with the basics, the custom recovery.
I have used both CWM and 4EXT in the past and am wondering which is favourable for the HTC One? A lot of posts I have read use CWM but an advantage I found with 4EXT was the ability to flash Kernels without having to go through the whole Super CID route I had to with my Sensation. Am I concerned about an issue that no longer exists or are the benefits of using 4EXT still relevant for the HTC One?
Secondly….and sort of thirdly, kernels and ROMs. Obviously I am wanting to OC the HTC One and I have found a number of kernels which allow this. I have also found a number of custom ROMS which include kernels that allow for over clocking….fine, except the “thirdly” part of this question is the difference between custom ROMs and the “Xposed” framework I have been reading about.
If I flash a custom ROM will Xposed still work or is it a case of one or the other?
To me, it seems the Xposed framework is the preferred option by a number of people for the very detailed level of customisable options it provides without (almost) any of the unwanted parts.
I appreciate the above might be a bit tongue tied so here is a simpler way of what I am asking:
• Custom ROM + Kernel + Xposed – Possible? And or necessary?
• Kernel + Xposed – Possible?
• Custom ROM + Kernel – I know this is possible.
Now, if the first bullet point is possible, I would like to know of a few 4.3 ROMs I can use. Please remember I am on the international UK version. A number of posts have US 4.3 ROMs but every time I look for international compatible ROMs it only ever states 4.2.2.
Is there a 4.3 ROM available for the UK HTC SIM Free One?
Note* The ROMs do not have to include kernels, I can find a compatible one easy enough.
Lastly, S-OFF.
If the original question about recovery images is negative, do I have to S-Off the device and S-CID etc?
If you got this far, thanks for reading and hopefully you can make things a little clearer than mud!
First thing I'd do is check the HBOOT on the phone as if you're on 1.44 I'd S-OFF it NOW! Even if you never do anything else it gives you the option in future
I'd then just use the phone as normal as this is the first phone I've not had to root...
If you DO want to go down the rooting route, then I'd look at Android Revolution HD which is currently running the latest leaked build for the EU handsets and works 100% fine on the unbranded EU/UK handset
EddyOS said:
First thing I'd do is check the HBOOT on the phone as if you're on 1.44 I'd S-OFF it NOW! Even if you never do anything else it gives you the option in future
I'd then just use the phone as normal as this is the first phone I've not had to root...
If you DO want to go down the rooting route, then I'd look at Android Revolution HD which is currently running the latest leaked build for the EU handsets and works 100% fine on the unbranded EU/UK handset
Click to expand...
Click to collapse
Thanks Eddy,
I would like to go down the rooting path due to the OC and customisable options.
I will check the HBOOT though when I get it in a few days....
Thanks.
Anyone else with any other comments on OP?
http://forum.xda-developers.com/showthread.php?t=2365506
Sent from my HTC One using Tapatalk
r1tesh said:
http://forum.xda-developers.com/showthread.php?t=2365506
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks for the link.
I did already find this and have it saved as a point of reference for when I figure out what I need to do.
I think my questions above still require guidance though as I am already aware updating firmware will require S-Off and S-CID but when I rooted my second Sensation, 4EXT allowed for the flashing of certain things without the requirement to S-OFF or S-CID (paper clip trick).
Furthermore, this doesnt touch on the ROM vs Xposed query but as mentioned, thanks for the link.
WOW long post
ssjghost said:
Lastly, S-OFF.
If the original question about recovery images is negative, do I have to S-Off the device and S-CID etc?
Click to expand...
Click to collapse
Actually, this should be firstly, S-Off if you can (at the moment that's only for hboot 1.44 pre June 2013, or using a JavaCard); use vomer's guide posted above.
Things have changed since Sensation, S-Off is good to change CID (IF needed), but a must for flashing unsigned firmware. (not to mention running a downgrade RUU)
However, even with S-On, you can still flash custom ROM, kernel, recovery, and even radio, using HTCdev to get an unlock token for your phone.
ssjghost said:
I suppose I will start with the basics, the custom recovery.
I have used both CWM and 4EXT in the past and am wondering which is favourable for the HTC One? A lot of posts I have read use CWM but an advantage I found with 4EXT was the ability to flash Kernels without having to go through the whole Super CID route I had to with my Sensation. Am I concerned about an issue that no longer exists or are the benefits of using 4EXT still relevant for the HTC One?
Click to expand...
Click to collapse
You'll need to use either CWM or TWRP, I believe 4EXT is not (yet) compatible with HTC One M7. As mentioned above both these recoveries are able to flash ROM, kernel and radio. S-Off and SuperCID not needed. Download those from the threads in xda, not the official web site as the ones in the thread are more up to date.
ssjghost said:
• Custom ROM + Kernel + Xposed – Possible? And or necessary?
• Kernel + Xposed – Possible?
• Custom ROM + Kernel – I know this is possible.
Click to expand...
Click to collapse
All three possible. :good::good:
ssjghost said:
Now, if the first bullet point is possible, I would like to know of a few 4.3 ROMs I can use. Please remember I am on the international UK version. A number of posts have US 4.3 ROMs but every time I look for international compatible ROMs it only ever states 4.2.2.
Is there a 4.3 ROM available for the UK HTC SIM Free One?
Click to expand...
Click to collapse
I can't say for all ROMs, but many of them are/were based on the US Developer edition, which was one of the first to receive 4.3, but were recoded to be WWE editions, that would work for UK.
Just remember to stay away from Sprint and Verizon editions, as these are completely different.
ssjghost said:
Note* The ROMs do not have to include kernels, I can find a compatible one easy enough.
Click to expand...
Click to collapse
The ROMs do include a kernel, but you can flash any other kernel after having flashed the ROM; so by extension every time you flash a ROM, you would need to reflash your custom kernel (making sure it's compatible with the ROM base obviously).
Hope that helps out a little, and remember to hit the thanks button for all that helped
nkk71 said:
WOW long post
Actually, this should be firstly, S-Off if you can (at the moment that's only for hboot 1.44 pre June 2013, or using a JavaCard); use vomer's guide posted above.
Things have changed since Sensation, S-Off is good to change CID (IF needed), but a must for flashing unsigned firmware. (not to mention running a downgrade RUU)
However, even with S-On, you can still flash custom ROM, kernel, recovery, and even radio, using HTCdev to get an unlock token for your phone.
You'll need to use either CWM or TWRP, I believe 4EXT is not (yet) compatible with HTC One M7. As mentioned above both these recoveries are able to flash ROM, kernel and radio. S-Off and SuperCID not needed. Download those from the threads in xda, not the official web site as the ones in the thread are more up to date.
All three possible. :good::good:
I can't say for all ROMs, but many of them are/were based on the US Developer edition, which was one of the first to receive 4.3, but were recoded to be WWE editions, that would work for UK.
Just remember to stay away from Sprint and Verizon editions, as these are completely different.
The ROMs do include a kernel, but you can flash any other kernel after having flashed the ROM; so by extension every time you flash a ROM, you would need to reflash your custom kernel (making sure it's compatible with the ROM base obviously).
Hope that helps out a little, and remember to hit the thanks button for all that helped
Click to expand...
Click to collapse
Perfect! Thats the answer I was "rooting" for.......
Although, your detailed answer has prompted another question.
Given that I can flash ROMS, Xposed and kernels without the need to S-Off or Super CID and the only benefit to S-Off and S-CID is the ability to flash new firmware and radios, this begs the question, for the not so hard core rooting user, do I even need to?
Agreed the posts say to S-Off straight away so I will heed this advice but in honesty, am I required to?
Am I likely to encounter any problems by flashing 4.3 ROMs without upgrading to the latest firmware?
S-OFF gives you a 'get out of jail' option should you ever need it as you can flash an RUU to return the phone to stock. What software build are you running on at present?
It's always best to match firmware to the ROM
EddyOS said:
S-OFF gives you a 'get out of jail' option should you ever need it as you can flash an RUU to return the phone to stock. What software build are you running on at present?
It's always best to match firmware to the ROM
Click to expand...
Click to collapse
Sorry, excuse my ignorance.
When you say "software build" do you mean firmware version or android build? Or something else completely!?
ssjghost said:
Perfect! Thats the answer I was "rooting" for.......
Although, your detailed answer has prompted another question.
Given that I can flash ROMS, Xposed and kernels without the need to S-Off or Super CID and the only benefit to S-Off and S-CID is the ability to flash new firmware and radios, this begs the question, for the not so hard core rooting user, do I even need to?
Agreed the posts say to S-Off straight away so I will heed this advice but in honesty, am I required to?
Am I likely to encounter any problems by flashing 4.3 ROMs without upgrading to the latest firmware?
Click to expand...
Click to collapse
SuperCID is not needed anyway (I believe) for flashing unsigned firmware, S-Off should suffice. On the other hand, finding signed firmware, is quite difficult, I haven't seen but a few around (and pretty old). You could still receive them using OTAs, but that would force you to flash stock ROM, stock recovery, and maybe even relock the bootloader, then having to go through the bootloader unlocking procedure again (which also wipes your phone completely, including sdcard/internal storage)
That bring one thing to mind, the first thing you should do once you install a custom recovery, is do a complete nandroid backup of your phone, should you need to get back to it at some later point in time (including for example, receiving OTAs)
As for "needing" to upgrade firmware, there are people still running 1.xx firmware (from Android 4.1.2) with 4.3 ROMs. Everything from 4.1.2 to 4.2.2 was pretty much OK with any firmware.
However, I've recently read a few posts on ARHD, where some issues (on ARHD 30.0) were actually only resolved with an update to the latest firmware. I cannot confirm these were actually issues due to different firmware and base versions, but it may very well be case.
If you are able to achieve s-off (I personally did it with revone, as it doesn't use a custom hboot, just get's rid of the security ON), I highly recommend it. Even if you never need it, having it is better as it will allow you to downgrade/upgrade, etc.etc.
One last thing, when you use HTCdev to unlock your bootloader and flash custom stuff, the bootloader will show "UNLOCKED" and "TAMPERED", even if you lock it again, it will only show as "RELOCKED", whereas with revone, you can remove the "TAMPERED" sign, and even return it to "LOCKED".
PS: Since you're in the UK, at worst, you can use the FunFoneShop (or whatever they're called), because they have JavaCards which can achieve S-Off even for 1.54 hboot (I think they charge something like 20 or 30 pounds, if I'm not mistaken)
Also, some people are saying that s-off for 1.54 "is around the corner" (by beaups), but can't confirm that either.
---------- Post added at 06:24 PM ---------- Previous post was at 06:20 PM ----------
ssjghost said:
Sorry, excuse my ignorance.
When you say "software build" do you mean firmware version or android build? Or something else completely!?
Click to expand...
Click to collapse
Software build is the HTC version, ie ARHD 30.0 is "latest official HTC One 3.57.401.500 - Android 4.3", and firmware would be the firmware in that release. You can use different firmware version with different base version, but it's always best (if you can) to have both the same.
ssjghost said:
Sorry, excuse my ignorance.
When you say "software build" do you mean firmware version or android build? Or something else completely!?
Click to expand...
Click to collapse
As in the build shown in Settings>About phone>Software information, e.g. 2.24.401.8
nkk71 said:
SuperCID is not needed anyway (I believe) for flashing unsigned firmware, S-Off should suffice. On the other hand, finding signed firmware, is quite difficult, I haven't seen but a few around (and pretty old). You could still receive them using OTAs, but that would force you to flash stock ROM, stock recovery, and maybe even relock the bootloader, then having to go through the bootloader unlocking procedure again (which also wipes your phone completely, including sdcard/internal storage)
That bring one thing to mind, the first thing you should do once you install a custom recovery, is do a complete nandroid backup of your phone, should you need to get back to it at some later point in time (including for example, receiving OTAs)
As for "needing" to upgrade firmware, there are people still running 1.xx firmware (from Android 4.1.2) with 4.3 ROMs. Everything from 4.1.2 to 4.2.2 was pretty much OK with any firmware.
However, I've recently read a few posts on ARHD, where some issues (on ARHD 30.0) were actually only resolved with an update to the latest firmware. I cannot confirm these were actually issues due to different firmware and base versions, but it may very well be case.
If you are able to achieve s-off (I personally did it with revone, as it doesn't use a custom hboot, just get's rid of the security ON), I highly recommend it. Even if you never need it, having it is better as it will allow you to downgrade/upgrade, etc.etc.
One last thing, when you use HTCdev to unlock your bootloader and flash custom stuff, the bootloader will show "UNLOCKED" and "TAMPERED", even if you lock it again, it will only show as "RELOCKED", whereas with revone, you can remove the "TAMPERED" sign, and even return it to "LOCKED".
PS: Since you're in the UK, at worst, you can use the FunFoneShop (or whatever they're called), because they have JavaCards which can achieve S-Off even for 1.54 hboot (I think they charge something like 20 or 30 pounds, if I'm not mistaken)
Also, some people are saying that s-off for 1.54 "is around the corner" (by beaups), but can't confirm that either.
---------- Post added at 06:24 PM ---------- Previous post was at 06:20 PM ----------
Software build is the HTC version, ie ARHD 30.0 is "latest official HTC One 3.57.401.500 - Android 4.3", and firmware would be the firmware in that release. You can use different firmware version with different base version, but it's always best (if you can) to have both the same.
Click to expand...
Click to collapse
OK, so asuming I will be flashing a 4.3 ROM or 4.2.2 at the latest, my software version will be 3.57.401.500?
Therefore find the appropriate firmware for this software build?
The build is linked to the ROM you flash. ARHD is currently based on the recent 3.57.401.500 leak which is Android 4.3 and you'd ideally need the FW to match it but you have to be S-OFF to flash the FW
Going back to my previous question, what build are you currently on? It's more to direct you for backups/recovery options more than anything as before you jump head long into the rooting world it's ALWAYS the best to know how to revert to stock if required
EddyOS said:
As in the build shown in Settings>About phone>Software information, e.g. 2.24.401.8
Click to expand...
Click to collapse
Just to confirm, I am yet to obtain the phone.
Once I have it I and I have flashed a 4.3 ROM, I asume I will need to find the compantable firmware and also flash this.
ssjghost said:
Just to confirm, I am yet to obtain the phone.
Once I have it I and I have flashed a 4.3 ROM, I asume I will need to find the compantable firmware and also flash this.
Click to expand...
Click to collapse
Recommended YES, needed not always necessary. (and you need s-off for that)
Firmware can be found in @vomer's guide here: http://forum.xda-developers.com/showthread.php?t=2365506 (in section 2)
EddyOS said:
The build is linked to the ROM you flash. ARHD is currently based on the recent 3.57.401.500 leak which is Android 4.3 and you'd ideally need the FW to match it but you have to be S-OFF to flash the FW
Going back to my previous question, what build are you currently on? It's more to direct you for backups/recovery options more than anything as before you jump head long into the rooting world it's ALWAYS the best to know how to revert to stock if required
Click to expand...
Click to collapse
Gotcha,
So, what's needed is:
Root device
Install Custom Recovery
S-Off and S-CID
Flash Custom Rom
Find and Flash matching FW to ROM
Flash GApps
Flash Xposed Framework
Excluding the obligatory back-ups along the way....Happy days?
ssjghost said:
Gotcha,
So, what's needed is:
Root device
Install Custom Recovery
S-Off and S-CID
Flash Custom Rom
Find and Flash matching FW to ROM
Flash GApps
Flash Xposed Framework
Excluding the obligatory back-ups along the way....Happy days?
Click to expand...
Click to collapse
No. First thing is:
1. Find build version
2. Find RUU for backup purposes and download if available for your build
3. S-OFF (if possible) and unlock bootloader at the same time
4. Flash custom recovery (through fastboot)
5. Backup current ROM
6. Flash new ROM
7. Flash GAPPs (only if using CyanogenMod/AOSP - they're included in Sense-based ROMs)
8. Flash FW (through fastboot, not recovery)
9. Do anything else you want
ssjghost said:
Gotcha,
So, what's needed is:
Root device
Install Custom Recovery
S-Off and S-CID
Flash Custom Rom
Find and Flash matching FW to ROM
Flash GApps
Flash Xposed Framework
Excluding the obligatory back-ups along the way....Happy days?
Click to expand...
Click to collapse
If you get it with hboot 1.44 (pre June 2013), you can first S-Off and unlock bootloader without using HTCdev.
EddyOS said:
No. First thing is:
1. Find build version
2. Find RUU for backup purposes and download if available for your build
3. S-OFF (if possible) and unlock bootloader at the same time
4. Flash custom recovery (through fastboot)
5. Backup current ROM
6. Flash new ROM
7. Flash GAPPs (only if using CyanogenMod/AOSP - they're included in Sense-based ROMs)
8. Flash FW (through fastboot, not recovery)
9. Do anything else you want
Click to expand...
Click to collapse
Thanks, and thanks eveyone else. You can probably see from the number of posts Ive made I try and find out stuff before posting so its appreciated not getting flammed when I do!
Thanks for all your help with this and no doubt youll hear from me again when I follow the step by step guides "to the letter" and end up on boot-loop!
Didn't think it would take long before I posted again.
Spent the evening trawling the forum and the CM page but cant seem to find a CM ROM for the international M7? Even a link to the CM site from another site returned a page on CM website but no files? Am I mistaken? Example: http://www.get.cm/?device=m7&type=
So...after yet more searching Im guessing the Pac-Man ROM here http://forum.xda-developers.com/showthread.php?t=2348415 and kernel here http://forum.xda-developers.com/showthread.php?t=2301543 are compatible although it doesn't look like the kernel allows for middle HTC button to become menu. Does anyone know where I can find the firmware?
IGNORE HERE: PRE EDIT - If not, then can anyone advise a lightweight,non-sense ROM (offering 4.2.2 or 4.3), a compatible overclocking and HTC menu button converting kernel and the applicable firmware?