Related
How to install new rom when I have only bootloader, mtty 4.12(it's black magic for me) and SD card (2gb). Could You help me?? I need step by step solution.
I have a very similar problem! I built a rom and flashed it using the Nordic ROM as my base image. Unfortunately something didnt quite work right and now all i get when i turn the phone on is the splash screen then nothing...
I can however go into the bootloader, but cant connect using MTTY??? I do have the ability to flash a rom from there using the rom utility, but as its the real SPL i cant flash a rom with only an OS.nb inside. Because i have previously flashed a rom with a different CID i can no longer flash an official HTC ROM.
Is it possible to re-sign an official HTC rom with a ModelID of: VOX010100 and a CID of: 11111111?
Please Help!!
Thanks,
iCEbeRg2403
Iceberg if your phone is CID unlocked have you tried to flash my rom from the bootloader, it should work. I've done it a hundred of times.
EDIT : Oooops, I didn't see you changed the CID. Same answer than the one I made to Luniople then, I don't know . You will have to wait for someone more experienced...
Luniople : Sorry I don't know how to flash a rom from sd card. I have nevere tried, but there should be some guides floating around on the forum.
odp
Ehhh....
Problem is done. I give my phone to servis and i have to pay them some cash. He told me that it takes him about 6 hours but i will have a working mobile again
So, i have updated my phone ota by htc so that now i have hboot 1.29 and ics installed with sense 3.6
I have no wifi/bluetooth anymore (MAC adres missing and bluetooth ID missing), so i was thinking in installing a custom rom/kernel whatever necessary to get my phone working properly again.
I think i read all the big guides and tutorials to be found in the sensation forum here. :good:
But that made me even more insecure.
What is it with the tools like the super utility from kgs1992, or the all-in-one toolkit.
i find threads about S-off, Super CID root, dev unlock and so on.
so, maybe someone here can give me one clear answer what i need to do in what order to exactly get my phone in a custom rom (let's say elegancia sense 4.1 themed?)
question one, what should i do first and what next?
first unlock over HTC dev (this i also a factory reset, isn't it?)
S-off (wire trick) (there are enough video's in youtube i guess)
then flash/install recovery (which one?)
Is this all correct?
at this point, am i rooted? and if not what comes next?
So what then? customrom? (how, what)? perm root? super cid? what do i need in what order?
in more than one place i read about rom as a file with the extension .img. But the elegancia download is a zip file.
what about the super tool, there they talk about a kernel, not a rom to flash.
And what about radio, is that a total different game? or is flashing a custom rom doing the interface, the kernel AND the radio in one go?
I hope i don't ask to much from anyone. I know there is a LOT of tutorials to be found already, but they are not all the same and often written to cover all versions and stuff. I can't see through all these things and hope to get some confidence by asking for my specific situation. :angel:
I'll try to explain stuff briefly ..hoping that it will solve other confusions too
well here it goes ...
1. First...Sensation by default is completely locked device (internal memory is locked )..so to either root the phone or run a custom rom ..you need to first unlock it.
2. Remember rooting the device and running custom rom are different
rooting: by doing this you will have complete control of the rom you are running be it stock or custom rom (its like administrative privileges in WIndows 7)
custom rom: this is changing the rom itself (like changing the OS From windows 7 to linux on PC )...and all custom roms comes pre rooted ..so once you flash/install a custom rom no need to root it again
3. Now The unlock procedure can be done in two different ways
3.1. HTC-DEV unlock : a process provided by HTC itself to support rooting of devices and running custom roms
(its a semi unlock...confused? will explain the difference later ..read on )
3.2. S-OFF: it means Security-off ..which implies unlocking the device completely (complete internal memory is unlocked)
S-OFF in turn has couple of ways to achieve it
3.2.1 S-OFF using revolutionary...It will only work on old bootloaders ..i.e. upto 1.18 HBOOT/BOOTLOADER (to put it simply it's for the sensation devices on gingerbread version of Android I.e. 2.3 version)
3.2.2 S-OFF using juopunutbear ..it will unlock even the current hboots (1.27/1.29 etc etc) (this method is primarily for sensation devices on ICS version of Android I.e. 4.0)
This juopunutbear inturn has two more ways
3.2.2.1. using juopunutbear after doing HTC-DEV unlock ..this process wipes the phone (because of HTC-DEV unlock) but the wire-trick (most imp step) is easier
(why juopunutbear ..if you already unlocked your device using HTC-DEV ? ..explained later ..read on )
3.2.2.2. using juopunutbear without HTC-DEV unlock required ..this process is harder at wire-trick part (comparatively)
4. Difference between HTC-DEV unlock and S-OFF:
to explain this ..I'll try to give a pictorial representation of Sensation Device
Sensation as a whole has different partitions (or blocks ) ..so the whole device can be divided like this
Recovery --------firmware--------ROM (or OS)
Recovery: its a recovery mode ..the name says it all ..we change/tweak/modify rom from here ..(remember only ROM ..not firmware)
eg: stock recovery, 4EXT recovery, CWM recovery, TWRP recovery etc etc (the later 3 are custom recoveries for flashing
custom roms
Firmware: all the lowest level stuff comes here ...typically bootloader, radio etc etc
we flash/install Recovery and stock ROMS from bootloader.
stock roms are ..called RUU's (Rom Update Utility) and are provided by HTC ...they are in .exe format and the actual stock ROMS are extracted from the RUU which will be in "img" format
ROMS: the actual custom/stock rom comes here ..this typically has three partitions/areas
1. data partition: all your apps/app data and all the phone data you eneter goes here
when you factory reset your device this partition is erased so that phone gets resetted to factory state
2. system partition: all the system apps and system stuff will lie here
(in case of carrier locked Sensation ..like T-Mobile all the T-Mobile junk apps reside here)
this area is locked in general ..rooting typically means getting this region unlocked ..so that you can change
anything in the rom
3. boot partition: your kernel lies here along with other stuff (this region is responsible for the phone to boot) Now it should be obvious that Radio aka a part of Firmware wont be there in a custom ROM and typical custom roms comes in zip format
Now HTC-DEV process only unlocks Recovery and ROM partitions (which are more than enough for installing custom roms or rooting)
This way of unlocking is safer as tinkering with Firmware is not really needed and if mistakes were made in changing the firmware the device can get bricked permanently.
but SOFF provides unlock on every partition of the Device ..thus complete unlock..thus more ease also more risks
Now the big question -> why SOFF needed if HTC-DEV is safer ?
Reasons:
1. Firmware and Rom partitions are dependent ..to be more clear
Ginger Bread (GB) firmware (1.17 firmware) ..supports only GB roms ...ICS or above roms wont boot
and
ICS firmware(3.32/3.33 firmware) ...supports only ICS and above ROMS (Jelly Bean(JB) roms are supported too )
thus if you do HTC-DEV unlock when on Ginger Bread you can only boot GB custom roms as you can't change/modify firmware over HTC-DEV unlock.
if you did HTC-DEV unlock over ICS rom..you are good to go with all the latest ICS/JB custom roms
2. Flashing/installing ROM from custom recovery with HTC-DEV unlock...requires an extra step...and if that extra step is not done ..phone wont boot (literally around 90% threads in Q&A section are about this problem as people didn't knew about the extra step )
3. some people require a change in radio ..to improve phone/data signal which isn't possible if you did just HTC-DEV unlock (as radio is part of firmware )
Another question that might come to your mind... What is the advantage of rooting the device on stock rom ..before installing a custom rom?
Answer:
people might say ..why root the device before installing custom rom when the custom rom comes pre-rooted
well here is the answer ..."to backup your phone and its data"
Remember this when installing a custom rom ..you need to wipe the phone(all the internal memory ..sdcard wiping is not needed) ..thus you will lose all data
but before wiping if you root the phone..you can backup all the user apps and its data ..also call logs, messages/MMS, wifi access points, bluetooth pairings. contatcs etc etc to your sdcard using a root app (an app which requires root permission to work ) ...and once you install the custom rom ..you can restore all the backup
..(makes things easier ..isn't it ? )
5. Miscellaneous terms:
Supercid:
CID -> carrier identification ..its a 8 characterterm used in the device to identify the proper Firmware or stock rom (RUU ..remember?)
as sensation is a global device ..there are different variants of firmware and stock Roms which are uniquely identified by this cid ..
eg: T-Mobile US locked sensation has CID: T-MOBO10, europe unbranded sensation has cid HTC__001 etc etc
so when flashing firmware/stock rom ..you need to find the proper one based on your phone cid ....
but if you do a supercid (i.e changing CID to 11111111) ..you can flash any firmware/stock rom (in form of RUU )
supercid can only be done ..over SOFF and wont/might not work over HTC-DEV unlock
also now there are Universal Firmwares ..aka Firmwares which can be flashed over ( SOFF) device having any CID ..thus Supercid is now kinda obsolete
hoping that things are clear now ..
few threads that are much detailed
1. "flashing roms while SON" by askickar in sensation general section ...(which explains flashing rom with just HTC-DEV unlock together with the extra step needed (remember ?) )..thread here
2. SOFF process threads ...for soff with HTC-DEV unlock ..thread here
3. SOFF without HTC-DEV unlock ...look in my signature for the thread
4. General way of flashing ROMS with Firmware flashing ..with ARHD Rom as reference...by joaquinf ..thread here
Happy flashing
Damn! now that is an explanation! Really really thanks for that! :victory:
I learned to always give feedback in your own words to check if you understood everything correctly.
If it is only for changing the 'interface'/running system part of the phone (that's called a ROM ), i can do with devunlock and flash a recovery, then flash a custom rom that is compatible for my version
(android 4.0.3 ICS/htc 3.6 sofware build 3.33.401.154/hboot 1.2900/kernel 3.0.16)
so any rom that has version 3.33 i can use it.
i don't need S-off per sé. (correct?)
doing above is already rooting, because i get (partially) access (or full access when S-off) to otherwise locked part of the system.
i have to flash a recovery to get influence when installing a new rom. so that means i NEED to flash a recovery to the phone before i flash a rom?
in short for my situation:
1. Do devunlock.
2. flash a recovery.
3. flash a custom rom to my phones specs as above.
so before or after step 1 i CAN do S-off using juopunutbear and the wiretrick
The easiest way to do all above is using the 'sensation all in one kit'
super CID i don't need, perm root is also optionally what can do as in the super tool kit is offered
But my fear is that the mac adres/wifi and bluetooth problems are from the 'lower level' of the system called firmware/kernel. (correct? or will flashing any custom rom already help me with solving my hardware part of the problems on the phone? besides giving me a much newer and cleaner installation with lot's of nice things, of course)
Main question still is? will a custom rom solve my wifi and bluetooth problems, or do i need more than above?
and ps, where does superswipe fit in all this? i read it's needed for instance at some versions of elegancia.
WOW Ganesh,what are you on?
@klimpetje
Wifi and bluetooth are on the "Radio" level.
Use an app from the market called "Getril"
This will show if you have the best radio/ril combination for your area.
Custom ROM MAY solve this problem.
Do not use "Superwipe" scripts.
Install 4 EXT recovery,and use the "Format all partitions (except sd card)"
doing above is already rooting, because i get (partially) access (or full access when S-off) to otherwise locked part of the system.
Click to expand...
Click to collapse
this ..is partially true ...once you do SOFF/HTC-DEV unlock ..the system partition can be unlocked ..and to actually make it unlock ..you need root
so that means i NEED to flash a recovery to the phone before i flash a rom?
Click to expand...
Click to collapse
yes
But my fear is that the mac adres/wifi and bluetooth problems are from the 'lower level' of the system called firmware/kernel. (correct? or will flashing any custom rom already help me with solving my hardware part of the problems on the phone? besides giving me a much newer and cleaner installation with lot's of nice things, of course)
Click to expand...
Click to collapse
the wifi and bluetooth modules are part of the ROM and drivers are part of radio ..so flashing CUSTOM ROM might/might not solve the issue
the chances of drivers getting corrupted are less ..as those areas are locked even when the OTA was applied...so custom ROM might solve your issue
superwipe -->as malybru said "not needed "..use the inbuilt wipe options present in recovery (this is done ..before flashing custom rom )
@malybru
WOW Ganesh,what are you on?
Click to expand...
Click to collapse
too much routine work/port im doing ...bored and came across this post
Nice guide ganeshp!
@ganeshp
Wow, that was really a nice and quick, yet thorough explanation! Cudos for being so helpful!
I was just wondering, is there any good reason to upgrade firmware after having S-OFF, custom recovery and flashed a working JB ROM?
Actually, I don't even know which firmware I have, but my last stock ROM before going custom was ICS.
My bootloader says:
Code:
=JuopunutBear=
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1111
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34
I can't really figure out which firmware it is - wasn't it supposed to be either 3.32 or 3.33?
PS: I'm currently on Paranoid v.21.
tachylatus said:
@ganeshp
Wow, that was really a nice and quick, yet thorough explanation! Cudos for being so helpful!
I was just wondering, is there any good reason to upgrade firmware after having S-OFF, custom recovery and flashed a working JB ROM?
Actually, I don't even know which firmware I have, but my last stock ROM before going custom was ICS.
My bootloader says:
Code:
=JuopunutBear=
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1111
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34
I can't really figure out which firmware it is - wasn't it supposed to be either 3.32 or 3.33?
PS: I'm currently on Paranoid v.21.
Click to expand...
Click to collapse
based on the radio ..you have i can safely say that the firmware is 3.32
but to confirm it ..the output of this command gives you the firmware
(the command should be typed in PC ..by opening the terminal where the adb/fastboot files are there ...with phone connected to PC from bootloader (phone says FASTBOOT USB if connected properly ))
fastboot getvar version-main
tachylatus said:
@ganeshp
Wow, that was really a nice and quick, yet thorough explanation! Cudos for being so helpful!
I was just wondering, is there any good reason to upgrade firmware after having S-OFF, custom recovery and flashed a working JB ROM?
Actually, I don't even know which firmware I have, but my last stock ROM before going custom was ICS.
My bootloader says:
Code:
=JuopunutBear=
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1111
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34
I can't really figure out which firmware it is - wasn't it supposed to be either 3.32 or 3.33?
PS: I'm currently on Paranoid v.21.
Click to expand...
Click to collapse
the only difference between 3.32fw and 3.33fw is radio upgrade
but you can check your fw version by doing this:
from bootloader connect your device to pc
open a command prompt and do
fastboot getvar version-main
then it will show you your firmware version
Thanks guys
My version is apparently 3.24.401.1.
I wonder if an upgrade will improve stability/performance.
Would you recommend following this guide, or should I just stay with the current version?
*edit*
I think I might give this a shot
Firmware information thread
The guy says something about most people reporting their devices to become noticeably faster after flashing.
tachylatus said:
Thanks guys
My version is apparently 3.24.401.1.
I wonder if an upgrade will improve stability/performance.
Would you recommend following this guide, or should I just stay with the current version?
*edit*
I think I might give this a shot
Firmware information thread
The guy says something about most people reporting their devices to become noticeably faster after flashing.
Click to expand...
Click to collapse
the only difference between 3.32fw and 3.33fw is radio ugrade
but in order to flash the latest ARHD rom probably requires 3.32 or 3.33(not so sure maybe it boots with 3.24 otherwise flash a higher fw version)
Great succes! :good:
I installed universal firmware 3.33.
Wouldn't boot ROM, so I used recovery to wipe cache, dalvik and battery stats, then reflash Paranoid v.21.
Works like a charm! Lightning fast
Sent from my HTC Sensation using xda app-developers app
ganeshp said:
I'll try to explain stuff briefly ..hoping that it will solve other confusions too
well here it goes ...
Click to expand...
Click to collapse
Really good stuff Ganeshp, wish I'd come across this earlier it's just what one needs when you enter this world fun trying to piece together all the terms being banded around. A huge time saver to have the 'glossary' and explanations in one place allowing the research time to go to the meat of the matter rather than sorting out the confusion that naturally occurs when starting up.
ganeshp said:
I'll try to explain stuff briefly ..hoping that it will solve other confusions too
well here it goes ...
Click to expand...
Click to collapse
Awesome Ganeshp, I am also new to this forum and this clears pretty much everything! I love how this Sensation forum is soo helpfull, thanks guys Im glad I bought my Sensation
cheers!
Status of my HTC:
Now it's RELOCKED
It has the original Recovery and Super CID (11111111)
BUT:
I can't flash any Stock rom! I always get the error 155! The bad thing is, I am not able to use a custom rom because, some of the Stock rom erased my flash!
but but but! the best thing is , I can't unlock the bootloader now! With the old unlock_boot.bin I will get an error and if I want to get a new Code from HTCDEV.com I also get an Error on the side, and they say, that the code is too long or not right (but I know how to copy and paste the text )
Why I want to go back to Stock?
First of all, I had an Wlan problem, which I solved but after that, i always got the Error (with Custom Roms) that the Android Keyboard (AOSP) will be closed, so I had no keyboard to work with
What can I do?
I only want to go back to my Custom Rom or the Stock ROM!!!!!
thesoldier16 said:
cheers!
Status of my HTC:
Now it's RELOCKED
It has the original Recovery and Super CID (11111111)
BUT:
I can't flash any Stock rom! I always get the error 155! The bad thing is, I am not able to use a custom rom because, some of the Stock rom erased my flash!
but but but! the best thing is , I can't unlock the bootloader now! With the old unlock_boot.bin I will get an error and if I want to get a new Code from HTCDEV.com I also get an Error on the side, and they say, that the code is too long or not right (but I know how to copy and paste the text )
Why I want to go back to Stock?
First of all, I had an Wlan problem, which I solved but after that, i always got the Error (with Custom Roms) that the Android Keyboard (AOSP) will be closed, so I had no keyboard to work with
What can I do?
I only want to go back to my Custom Rom or the Stock ROM!!!!!
Click to expand...
Click to collapse
Well, I imagine with the RUU you got back to a stock ROM... At any rate, you could try reflashing the RUU, or attempt to flash a different RUU (since you have SuperCID) and then see if your still having issues with getting a new unlock_boot.bin.
I imagine your 100% sure you know how to cut and paste? LOL I have to ask (even though you said it)... I was able to unlock my bootloader after flashing a newer RUU and didnt have this issue.
AKToronto
Well, I imagine with the RUU you got back to a stock ROM... At any rate, you could try reflashing the RUU, or attempt to flash a different RUU (since you have SuperCID) and then see if your still having issues with getting a new unlock_boot.bin.
Click to expand...
Click to collapse
Good aspect, but (now I love this word ) I tested nearly every Europe RUU and I always get the 155!
Some people said, that one of the latest RUU works with the CID :
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
At tis moment I found this rom, I will test it tomorrow!
I imagine your 100% sure you know how to cut and paste? LOL I have to ask (even though you said it)... I was able to unlock my bootloader after flashing a newer RUU and didnt have this issue.
Click to expand...
Click to collapse
Come on man! I unlocked the bootloader Soooo this is not the problem for me!
I read in some threads, that you can't generate a new .bin file with htcdev when you have on working Rom on your phone haha funny, yeah and I am not able to put a normal stock rom on the phone
This is a long shot, but if you still have a custom recovery, try loading it up and flashing this: http://www.mediafire.com/?l35x37414jhwual
That package will set your mainver to the lowest possible number, which combined with SuperCID will allow flashing of any RUU.
If that doesn't work, you'll have to keep trying the htcdev to get your unlock code. It's possible that the website could be having some temporary problems. If all else fails, shoot an e-mail to HTC Support with screenshots of the errors on the website, the fastboot errors, a picture of your phone's HBOOT, your old unlock_code.bin and your identifier token.
Edit: Oops, just read that you had the original recovery :/ Yeah, try the absolute latest RUU and if that doesn't work, you'll need a new unlock code to have any progress.
what is your hboot version?
thesoldier16 said:
I only want to go back to my Custom Rom or the Stock ROM!!!!!
Click to expand...
Click to collapse
The unlock_code.bin file you get from HTC is generated using fingerprints on your phone. When you changed your CID it's like changing a fingerprint. All you have to do is go through the unlocking process again and get a NEW unlock_code.bin from HTC Dev.
thesoldier16 said:
I always get the error 155! The bad thing is, I am not able to use a custom rom because, some of the Stock rom erased my flash!
Click to expand...
Click to collapse
Most likley you are trying to use a RUU that have a lower hboot then yours. You can only use an RUU that has the same version or a higher hboot.
thesoldier16 said:
It has the original Recovery and Super CID (11111111)
I can't flash any Stock rom!
Click to expand...
Click to collapse
If you have the original recovery you need to flash a custom recovery first. Find TWRP and flash that.
what is your hboot version?
Click to expand...
Click to collapse
It's the version 1.14.0002
Ok these roms don'tt work for me:
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed.exe -> I tried this rom with my old CID , it was H3G__106
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.exe
EDIT EDIT EDIT:
I got a new code from htcdev!
my problem was, I paste the text with the "info" . ok it was my fault, but now i have to try, to get my custom Recovery back!
One question, if I replace the SUPER CID with the HTC__001 one, can I flash the HTC Europe ones? (the 1.53 or the 1.78?)
Click to expand...
Click to collapse
thesoldier16 said:
It's the version 1.14.0002
Ok these roms don'tt work for me:
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed.exe -> I tried this rom with my old CID , it was H3G__106
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.exe
EDIT EDIT EDIT:
I got a new code from htcdev!
my problem was, I paste the text with the "info" . ok it was my fault, but now i have to try, to get my custom Recovery back!
One question, if I replace the SUPER CID with the HTC__001 one, can I flash the HTC Europe ones? (the 1.53 or the 1.78?)
Click to expand...
Click to collapse
The problem is that you trying to use RUU's with a lower Hboot then what you got it will never work without a downgrade. Its has to be the same or higher then what you got.
Hi there been a while since I've flashed stuff on htc devices and i'm trying to get dev edition 1.55.617.4 rooted odex rom on my device, i'm s-off and super cid rom installs but won't boot, i'm presuming its boot. Img or firmware related? Just after info if I extract boot. Img and firmware from the rom and flash separately will this solve the issue and will it remove twrp?
Currently on dev edition 1.12.617.6 CL639737
Thanks for any advice
Sent from my Lenovo YT3-X50F using Tapatalk
wakers said:
Hi there been a while since I've flashed stuff on htc devices and i'm trying to get dev edition 1.55.617.4 rooted odex rom on my device, i'm s-off and super cid rom installs but won't boot, i'm presuming its boot. Img or firmware related? Just after info if I extract boot. Img and firmware from the rom and flash separately will this solve the issue and will it remove twrp?
Currently on dev edition 1.12.617.6 CL639737
Thanks for any advice
Sent from my Lenovo YT3-X50F using Tapatalk
Click to expand...
Click to collapse
Change the SUPER CID to BS_0001, install the original RUU from: http://dl3.htc.com/application/RUU_HIA_AERO_UL_M60_SENSE7GP_ATT_MR_NA_Gen_Unlock_1.56.617.1.exe, then proceed to install the TWRP and Root with Windroid.
Hi there it won't let me change the CID to what you've stated above it says invalid, also the link i think is for the ATT version, i'm in europe so believe i need the GSM version ?
I can change the CID to HTC__001 for example but not what you've quoted...
Really struggling to get my phone updated to 6.0.1 i've only had it a few days tried numerous methods but not getting anywhere fast I thought if i was S-off and Super CID you could pretty much flash anything as long as it was for your correct phone model ?
Hence me presuming my issue was more boot.img and recovery.img related ?
I downloaded the official Dev edition RUU from the HTC Dev download section but that won't install either...
Getting confused i'm sure i'm probably missing a pretty easy step somewhere...
wakers said:
Hi there it won't let me change the CID to what you've stated above it says invalid, also the link i think is for the ATT version, i'm in europe so believe i need the GSM version ?
I can change the CID to HTC__001 for example but not what you've quoted...
Really struggling to get my phone updated to 6.0.1 i've only had it a few days tried numerous methods but not getting anywhere fast I thought if i was S-off and Super CID you could pretty much flash anything as long as it was for your correct phone model ?
Hence me presuming my issue was more boot.img and recovery.img related ?
I downloaded the official Dev edition RUU from the HTC Dev download section but that won't install either...
Getting confused i'm sure i'm probably missing a pretty easy step somewhere...
Click to expand...
Click to collapse
Try with Windroid http://forum.xda-developers.com/one-a9/development/tool-windroid-universal-android-toolkit-t3291251
Hey please can you tell me where I get cyanogenmod 12 for my device because it is not listed on cyanogenmod website or you can tell me how I install 5 lollipop ? in my device
malik ihtesham said:
Hey please can you tell me where I get cyanogenmod 12 for my device because it is not listed on cyanogenmod website or you can tell me how I install 5 lollipop in my device
Click to expand...
Click to collapse
I think you have the wrong forum ?
Got it sorted in the end, changed the info.txt file in the firmware to suit the phone, even though it said it failed when installing the firmware it had actually installed and then the 6.0.1 dev edition rooted rom installed... Happy days...
So i'm not sure if the Mid or Cid was the issue but either way when i changed the info.txt file to suit it worked...
Hey All,
Apologies if this is obvious but I couldn't figure it out myself looking at the FAQ's etc.
I just purchased a new HTC One A9 which was carrier unlocked by AT&T, and I want to convert from the RUU version they use (1.27.502.5) to the latest version that HTC has released on their website - 2.18.617.10 .
However, when I go to do this using that RUU, I get signature error 132. My phone is bootloader locked and S-ON, but from reading a little, I thought that shouldn't matter because I have a US phone, and you only need to change the CID/MID stuff (whatever those are) if you're in a different region?
How would I go about doing this? From reading through a bunch of posts, do I first need to switch to an unlocked version of Marshmallow, before then upgrading to Nougat?
Edit: Upon further reading, does the fact that the 502 in my current version does not match 617 in the one I wish to upgrade to mean that I can't do this with S-on? Do I need S-off? If so, how do I do that? Is it only by purchasing sunshine?
Thank you for your time!
Best,
-BBsmitz
bbsmitz said:
Hey All,
Apologies if this is obvious but I couldn't figure it out myself looking at the FAQ's etc.
I just purchased a new HTC One A9 which was carrier unlocked by AT&T, and I want to convert from the RUU version they use (1.27.502.5) to the latest version that HTC has released on their website - 2.18.617.10 .
However, when I go to do this using that RUU, I get signature error 132. My phone is bootloader locked and S-ON, but from reading a little, I thought that shouldn't matter because I have a US phone, and you only need to change the CID/MID stuff (whatever those are) if you're in a different region?
How would I go about doing this? From reading through a bunch of posts, do I first need to switch to an unlocked version of Marshmallow, before then upgrading to Nougat?
Edit: Upon further reading, does the fact that the 502 in my current version does not match 617 in the one I wish to upgrade to mean that I can't do this with S-on? Do I need S-off? If so, how do I do that? Is it only by purchasing sunshine?
Thank you for your time!
Best,
-BBsmitz
Click to expand...
Click to collapse
In order to convert to another carrier version, you must change your CID and MID to match the RUU version you want to flash. .617 uses the same MID as .502 so you'll need to change your CID only from CWS__001 to BS_US001. Changing CID does requires S-OFF (Sunshine is the best way unless you know someone with a XTC2Clip box).
You'll also need to update your firmware to Nougat before flashing the Nougat RUU because of the signature change implemented in Nougat.
Everything explained here:
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Read faq 1-2-3-4
alray said:
In order to convert to another carrier version, you must change your CID and MID to match the RUU version you want to flash. .617 uses the same MID as .502 so you'll need to change your CID only from CWS__001 to BS_US001. Changing CID does requires S-OFF (Sunshine is the best way unless you know someone with a XTC2Clip box).
You'll also need to update your firmware to Nougat before flashing the Nougat RUU because of the signature change implemented in Nougat.
Everything explained here:
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Read faq 1-2-3-4
Click to expand...
Click to collapse
Okay thanks so much Two more quick questions.
1) Does changing to S-off have any consequences in terms of a future update? I'm guessing it will void my warranty, but say I wanted to go back to using AT&T's version of android. Would the fact that my phone is now S-off prevent me from using their RUU (assuming I change the CID back.) I guess my question is, warranty aside, is there really any negative to turning S-off?
2) This is more out of curiosity. HTC One Phones that were sold unlocked/developer that are currently running Marshmallow can be upgraded to Nougat without flashing the firmware to 2.xx.xxx.x right? So if I was to change my current CID to that of a developer One A9, and install that Marshamallow RUU say (1.57.617.60), why wouldn't I be able to simply update from within the OS as they do?
Thanks again for your time.
Best,
Bbsmitz
bbsmitz said:
Okay thanks so much Two more quick questions.
1) Does changing to S-off have any consequences in terms of a future update?
Click to expand...
Click to collapse
No, after converting to another version, you'll receive ota updates for that version.
I'm guessing it will void my warranty,
Click to expand...
Click to collapse
Yes an no. There's always the possibility to revert back to your original version and hide everything you've done.
but say I wanted to go back to using AT&T's version of android. Would the fact that my phone is now S-off prevent me from using their RUU (assuming I change the CID back
Click to expand...
Click to collapse
You would simply have to revert your CID back to CWS__001 and flash the at&t ruu. Changing the cid is easily done.
I guess my question is, warranty aside, is there really any negative to turning S-off?
Click to expand...
Click to collapse
S-off gives you full control and access to all partitions which mean there is no more mechanism preventing you to flash incompatible software/firmware on your phone. Once s-off, be sure to understand what you're doing before flashing files. The risk is limited if you'll only be converting to another version or flashing custom roms but if you're going to explore a little deeper yeah it can be dangerous.
2) This is more out of curiosity. HTC One Phones that were sold unlocked/developer that are currently running Marshmallow can be upgraded to Nougat without flashing the firmware to 2.xx.xxx.x right? So if I was to change my current CID to that of a developer One A9, and install that Marshamallow RUU say (1.57.617.60), why wouldn't I be able to simply update from within the OS as they do?
Click to expand...
Click to collapse
All A9 can simply be updated from the OS, not only the unlocked/dev version. The reason why you need to flash the firmware first before flashing a RUU is that HTC changed their encryption signature in Nougat. That mean your phone need the new decryption key to be able to flash Nougat RUU. Flashing the firmware first will update your phone with the new key, making it able to flash Nougat RUU.
There is a firmware.zip file inside ota updates. When you install an ota update from the OS, the first thing that is flashed on your phone is that firmware.zip. So no you don't need to manually flash the firmware because it's done automatically in the ota process.
Yes you could flash the 1.57.617.30 ruu and do the ota update after. It's just faster to flash the Nougat firmware first and the Nougat RUU instead of flashing the Marshmallow RUU and downloading + installing 2 ota udpates, well that's my opinion. Both methods will give the same result.
alray said:
No, after converting to another version, you'll receive ota updates for that version.
Yes an no. There's always the possibility to revert back to your original version and hide everything you've done.
You would simply have to revert your CID back to CWS__001 and flash the at&t ruu. Changing the cid is easily done.
S-off gives you full control and access to all partitions which mean there is no more mechanism preventing you to flash incompatible software/firmware on your phone. Once s-off, be sure to understand what you're doing before flashing files. The risk is limited if you'll only be converting to another version or flashing custom roms but if you're going to explore a little deeper yeah it can be dangerous.
All A9 can simply be updated from the OS, not only the unlocked/dev version. The reason why you need to flash the firmware first before flashing a RUU is that HTC changed their encryption signature in Nougat. That mean your phone need the new decryption key to be able to flash Nougat RUU. Flashing the firmware first will update your phone with the new key, making it able to flash Nougat RUU.
There is a firmware.zip file inside ota updates. When you install an ota update from the OS, the first thing that is flashed on your phone is that firmware.zip. So no you don't need to manually flash the firmware because it's done automatically in the ota process.
Yes you could flash the 1.57.617.30 ruu and do the ota update after. It's just faster to flash the Nougat firmware first and the Nougat RUU instead of flashing the Marshmallow RUU and downloading + installing 2 ota udpates, well that's my opinion. Both methods will give the same result.
Click to expand...
Click to collapse
Edit2: I figured out the problem. I had to boot into the bootloader and then run
Code:
htc_fastboot oem rebootRUU
before I could run the RUU sucessfully. Am leaving the rest of this post up just so that other people googling this have a touch point.
Okay so I've used Sunshine to turn s-off and unlock my bootloader. I then changed my CID to BS_US001.
I then tried to install the HTC version of Marshmallow (maybe silly, but heard people having issues with Nougat and the battery) using the RUU.exe file. It started successfully, but then halfway though, after it had transferred the ROM over, it threw an ERROR155 and aborted, leaving my phone with an empty progress bar, and that circular green arrow icon in the middle. I used the command line to restart my device and had to factory wipe it, but otherwise not the worse for wear.
I tried googling it; do I need to relock my bootloader for the RUU.exe files to work? I think the Sunshine FAQ recommended against doing that. Is this a risky step?
Edit: Here are some instructions I found from the HTC One M8 firmware flashing thread. My error says "unknown" but I imagine its similar.
For “Error 155 relock bootloader" do:
- Since my thread works only with S-OFF phones anyway, this error can be read as: you need to S-OFF first!
- Error 155 can mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of a wrong region lock.
- Lately, Error 155 has occurred when a FUU was launched from within android. When encountering a FUU error 155 with the process stalling after the rebootRUU (stuck at black screen with silver HTC logo), please just restart the FUU and leave the phone in that mode, or reboot the phone, then reboot to bootloader, then do “htc_fastboot oem rebootRUU” and then launch the FUU again (thanks @anarchychris for pointing it out).
- run the fastboot command “htc_fastboot oem lock" - only applies to S-ON phones that want to update the firmware with a stock OTA package (not offered on this thread!!). Stock OTA files sometimes need a locked bootloader.
Click to expand...
Click to collapse
help
Is this guide convert AT&T bindings factory unlocked htc? I cant access wifi hotspot. also cant run RRU.
hiii i have htc one a9300 by mistak i wipe every thing including internal memory now my fon sows that no "os install are you sure wanto reboot " please tell me wat to do now
AT&T conversion
alray said:
In order to convert to another carrier version, you must change your CID and MID to match the RUU version you want to flash. .617 uses the same MID as .502 so you'll need to change your CID only from CWS__001 to BS_US001. Changing CID does requires S-OFF (Sunshine is the best way unless you know someone with a XTC2Clip box).
You'll also need to update your firmware to Nougat before flashing the Nougat RUU because of the signature change implemented in Nougat.
Everything explained here:
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Read faq 1-2-3-4
Click to expand...
Click to collapse
How do I get started to do this. How do I find out my mid Cid and if I need to change? How do I flash firmware first? I have android 6.0 software 1.27.502.5. I have done a run before but never changed from a carrier. I went to the link above but I don't know what some if this means and where to start and what steps to take in order.