Related
Hey all!
I rooted my phone quite a while ago and have been running das_bamf_remix_1.7 and am thinking of switching to a different rom, the only thing is that I see all these requirements for mr2 or 2.5... and my question is, do these usually come with the rom? If not, what are the best steps for flashing these radios and what exactly do they do?
Thanks guys.
Hi, that is exactly what I was trying to figure out too.
Can the radios be updated independent to ROMs?
I am currently at rooted stock rom.
Should I install the radio to, say MR2, and the install the custom ROM?
Thanks for your help!
The radios do not normally come with the ROM's and would need to be updated separate using the HBOOT process. GB would need the MR2 or MR2.5, Froyo would use the MR1 radios. I don't have the links right now to point to the radios but if you search here you will find them pretty quickly.
Here is a link for some info on the radio's.
http://forum.xda-developers.com/showthread.php?t=1045081&highlight=radio
Thanks alot! I think I was able to install both the custom rom and the radio (in that order).
I wish if someone could help a bit more...
Regarding the 'Gingerbread Related Bricking'
http://forum.xda-developers.com/showthread.php?t=1096104
Could this apply to Das BAMF Remix v2.1 + MR2.5?
This is the combination I have tried...
Here is another link to the Radio's.
http://forum.xda-developers.com/showthread.php?t=1154010
fooooo - Yes you are correct with the rom then the radio flash. As far as the bricking, did you brick or are you just curious about it bricking?
I am completely stock but flashed the mr2 update.. reboots have completely stopped but my signal and 3g (currently not in 4g area) are extremely slow.. although they appear to be slower while pdanet v3.0 tethering.. any info or advice?
Also can anyone point me to a thread that lets me go back to completely stock
Thanks
The bricking issues seem to have subsided since the release of the MR2 radio. I think it was suspected that the original leaked GB radio initiated the bricks.
krime - As far as running MR2 on stock I would imagine that the problem is that MR2 & 2.5 are for the GB-based ROMs (and das bamf 1.8.6) and as such won't work with stock froyo. But I haven't been on stock for a while so maybe somebody else knows for sure.
krime922 said:
Also can anyone point me to a thread that lets me go back to completely stock
Thanks
Click to expand...
Click to collapse
Last link under REF|Guides
http://forum.xda-developers.com/showpost.php?p=12481600&postcount=1
"Next, push exploits.zip and misc.img."
Ok so basically download the stock firmware and exploits, when it gets to the adb commands (from the above on) im lost... Do I download the sdk starter package on android sdk website or? A complete guide-for-dummies would be appreciated
I am coming from 1-click DroidX so my rooting ability is negligible.. however because MR2 apparently does not belong on stock froyo.. I kinda have to in order to go back to complete stock.
I would of posted in the dev forum but I havent met the minimum required posts lol
Thanks for your responses
ksmitchell said:
Here is another link to the Radio's.
http://forum.xda-developers.com/showthread.php?t=1154010
fooooo - Yes you are correct with the rom then the radio flash. As far as the bricking, did you brick or are you just curious about it bricking?
Click to expand...
Click to collapse
It looks like it's working fine!
I just wanted to make sure I wasn't on the bad combination of ROM and radio that could brick the phone.
Glad it seems fine. Thnx!
krime922 said:
"Next, push exploits.zip and misc.img."
Ok so basically download the stock firmware and exploits, when it gets to the adb commands (from the above on) im lost... Do I download the sdk starter package on android sdk website or? A complete guide-for-dummies would be appreciated
I am coming from 1-click DroidX so my rooting ability is negligible.. however because MR2 apparently does not belong on stock froyo.. I kinda have to in order to go back to complete stock.
I would of posted in the dev forum but I havent met the minimum required posts lol
Thanks for your responses
Click to expand...
Click to collapse
First: Don't post questions in the dev forum. I know you didn't, but you said you would have if you had enough posts. Only development of hacks and ROMS and such belong there just FYI. As to your question, J-Case's root tutorial that is stickied in the dev forum has an easy ADB installer. Use that it's the easiest way to get ADB up and running. Search XDA and Google for tutorials on how to use ADB. I don't have links, but its pretty easy to find the info. Once you have done that go to the dev forum and look for J-Case's sticky thread on how to properly return to stock. This should get you back on totally stock unrooted MR1.
Sent from my HTC Thunderbolt
I am thinking about flashing the leaked GB but was wondering if I flash one of them would I be able to flash back to stock sense froyo?
Sent from my ADR6400L using XDA Premium App
i actually skipped a step ahead and flashed the leaked gb rom.. i thought it was just the radio because because you have to rename it in bootloader.. funny thing is i flashed the debloated version minutes before. now im stuck with a stock unrooted s-on device. im trying to reroot to flash back myself but im getting 'failed to set prot mask'... im still searching for answers. my conclusion just dl the debloated one.
alluzzion2o9 said:
i actually skipped a step ahead and flashed the leaked gb rom.. i thought it was just the radio because because you have to rename it in bootloader.. funny thing is i flashed the debloated version minutes before. now im stuck with a stock unrooted s-on device. im trying to reroot to flash back myself but im getting 'failed to set prot mask'... im still searching for answers. my conclusion just dl the debloated one.
Click to expand...
Click to collapse
I'm gonna say you should probably read my noob qANDa thread. You NEVER flash ROMs through hboot. You don't even have to rename your ROM. You, my friend, flash an RUU, which you should only do if you want a bone stock device. RUUs are put out there for devs to play with, generally speaking. The only thing you ever flash in hboot is the radio, and maybe a couple other things if you really know what you're doing. As for fixing your root situation, the process can be done exactly as it's laid out in jcase's guide, except you need to use a different exploit tool instead of the one supplied in that thread. A quick search for rooting the GB rom should locate that exploit. I can't speak for AlphaRevX yet. Last time I looked they were out of commission.
loonatik78 said:
I'm gonna say you should probably read my noob qANDa thread. You NEVER flash ROMs through hboot. You don't even have to rename your ROM. You, my friend, flash an RUU, which you should only do if you want a bone stock device. RUUs are put out there for devs to play with, generally speaking. The only thing you ever flash in hboot is the radio, and maybe a couple other things if you really know what you're doing. As for fixing your root situation, the process can be done exactly as it's laid out in jcase's guide, except you need to use a different exploit tool instead of the one supplied in that thread. A quick search for rooting the GB rom should locate that exploit. I can't speak for AlphaRevX yet. Last time I looked they were out of commission.
Click to expand...
Click to collapse
Guess I used the wrong choice of words there. I am aware that RUUs, radios are all that you flash from HBoot, and ROMs are flashed from the recovery. I just remember reading one post on here that someone asked if we flash GB can we get back to stock sense froyo and was told no. After taking a step back and thinking of what I was asking and how ROMs actually work I could have answered my own question.
jmc2543 said:
Guess I used the wrong choice of words there. I am aware that RUUs, radios are all that you flash from HBoot, and ROMs are flashed from the recovery. I just remember reading one post on here that someone asked if we flash GB can we get back to stock sense froyo and was told no. After taking a step back and thinking of what I was asking and how ROMs actually work I could have answered my own question.
Click to expand...
Click to collapse
I think "no" might have been true for a short time, but it wasn't long before I saw the exploit to root GB floating around. That one guy did seem a bit confused on the matter though.
loonatik78 said:
I think "no" might have been true for a short time, but it wasn't long before I saw the exploit to root GB floating around. That one guy did seem a bit confused on the matter though.
Click to expand...
Click to collapse
What is the new exploit? Fr3vo?
Sent from my HTC Thunderbolt
This is beginning to get out of control with all of the thread jacking and such with mainver issues. Anyway, read on.
NEW INFO: FLASH THIS: http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4\
PROBLEM SOLVED!
Old info if you care:
Q. What is MainVer?
A. MainVer is a string that HBOOT keeps track of that keeps the latest version of the RUU or PH98IMG.zip that has been flashed.
Q. Why does HTC have this?
A. In order to prevent downgrading with an RUU.
Q. I haven't run an RUU. How was my MainVer updated?
A. There are 2 reasons your MainVer could have been updated at this point.
The Original ICS Leak
DSB's new BAMF Rom (downloaded 1/17/2012 or later)
The original ICS leak that some of you flashed was still in RUU image form. Unfortunately, this was distributed with an updated MainVer string in the android-info.txt. When this was flashed, the new MainVer string was recorded into your device. DSB for some reason also included this new android-info.txt in his kernel PH98IMG.zip that is packed with his rom. I am not quite sure why he did that.
Q. What does this mean for me?
A. See new text at the top
Q. Why won't devs just add the new mainver to their roms to make my life easier?
A. They could, but then they would be forcing everyone to have this problem, not just you. It would also prevent everyone from using an RUU to repair their phones until a new one came out.
More Info:
No matter if you are going GB->GB or GB->ICS or ICS->GB you will need to have the correct mainver for your device. If you aren't having trouble going from rom to rom right now, you shouldn't even be looking at this guide. But if you got your mainver updated, you need to replace the android-info.txt for every single rom forever (until a new RUU comes out and it is safe to unify everyone's mainver)
Click to expand...
Click to collapse
That was quick! Nice work, Con. Hopefully this will help everyone out having these issues. I'll make sure I bookmark this page to link to if anyone should have issues. Thanks!
WasabiWa83 said:
That was quick! Nice work, Con. Hopefully this will help everyone out having these issues. I'll make sure I bookmark this page to link to if anyone should have issues. Thanks!
Click to expand...
Click to collapse
Thanks! That is a good idea about the bookmark. Ill do that too.
Yeah I had to answer this question a few times... this Q/A should make it easier.
I want to be sure I understand this correctly. If I flash an ICS rom I need to use the android-info mainver source 3.10.605.7 and if I want to revert back to a stock rom I need to use the android-info mainver source 1.02.605.6?
I have not installed any ICS roms yet, waiting for some more of the bugs to get worked out. I've been reading where many people are having issues with installing ICS roms and struggling with reverting back to stock.
I will try to make that more clear. Hold on.
I make a motion to sticky this thread. Anyone 2nd this motion?
Sent from my ADR6425LVW using xda premium
con247 said:
I will try to make that more clear. Hold on.
Click to expand...
Click to collapse
Thanks Con for the quick reply! I like to look over these forums and make sure I'm understanding some of the issues that are currently going on. I've been flashing roms for awhile but still consider myself a noob. Thanks again!
trickster2369 said:
I make a motion to sticky this thread. Anyone 2nd this motion?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yeah, definitely a 2nd for very this useful post. Especially since a lot of the ROM threads are getting off topic because of this. I saw Scott posted a link to this thread in his release posts. Good idea for the Devs to link back here too
Yeah this needs to be stickied...
Con... here is a post I did explaining Mainver... It is a bit more simplified, might be easier to follow for the new guys. (it also explains what RUU files are and what they do)
Marine6680 said:
RUU files are the official software releases from HTC.
RUU files are signed. (They give proper "official" codes to hboot to get past the s=on security)
This means that they can flash all parts of the device, even the bootloader and radio firmware, which we can not normally flash because it is write locked. (do to s=on we can't flash them even with root)
Sometimes people have issues and need to get the phone back to pure stock so they use the RUU.
Mainver is data on the software version number of the kernel (I believe... it may be for some other part, either way it is version info)
Think V1... V1.2... V1.5... V1.5.5
Because of s=on we are not allowed to "downgrade/revert" to older software versions.
The leaked ICS build has a newer Mainver, some people flashed the leak unmodified, and that changed the Mainver info. Now they need to use a special trick to trick the s=on security to allow flashing of older kernels. The ICS ROMs we have now, have been modified so they do not change the Mainver. This makes it easier to go back to GB or switch to other ROMs.
Click to expand...
Click to collapse
I am sorry but I am trying to make sense of all this. I am on Scott's CleanRom 2.1 will I need to use these instructions to go back to my stock room? This is my first HTC, I've only had Motorola phones up till now and I hate to admit it but this is all a bit over my head. I have been studying these forums for the last 2 days and I really have no clue how to use the backup I made of my stock GB Rom or even what kernel to use. I do regret not waiting to mess with this phone. Any help is greatly appriciated and I love all the work you have all put into this phone. Thanks in advance.
Sent from my ADR6425LVW using XDA App
snowride20 said:
I am sorry but I am trying to make sense of all this. I am on Scott's CleanRom 2.1 will I need to use these instructions to go back to my stock room? This is my first HTC, I've only had Motorola phones up till now and I hate to admit it but this is all a bit over my head. I have been studying these forums for the last 2 days and I really have no clue how to use the backup I made of my stock GB Rom or even what kernel to use. I do regret not waiting to mess with this phone. Any help is greatly appriciated and I love all the work you have all put into this phone. Thanks in advance.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
You're pretty much good because Scott's ROM does not update your MainVer. This is only for those ROMs that updated the MainVer. All you will need to do is restore your nand and flash the stock rooted kernel with Scott's Clean Flash tool. It's really more simple than you would think. You can find the Clean Flash tool and the stock rooted kernel in the dev forum. Just make sure that there is no PH98IMG.img on your ext sd card before you try to revert to your nandroid. Once you have restored your nand, you need to get to HBoot using the clean flash tool to make sure that you flash the stock rooted kernel. If you have the PH98IMG on your ext SD card, you would be kind of boned. Hope this helps a little.
So I flashed BAMF once, but it was weeks ago and I've since been using GingerSense without any issues, and that flashed fine after I tossed his boot.img back on, and then again after I did a full wipe a few nights ago. Is there any way to easily tell which mainver we're currently on? I'm assuming I'm ok since I haven't had to do anything else while flashing his ROM, guess I just wanna make sure.
rboddy said:
So I flashed BAMF once, but it was weeks ago and I've since been using GingerSense without any issues, and that flashed fine after I tossed his boot.img back on, and then again after I did a full wipe a few nights ago. Is there any way to easily tell which mainver we're currently on? I'm assuming I'm ok since I haven't had to do anything else while flashing his ROM, guess I just wanna make sure.
Click to expand...
Click to collapse
I believe mainver only changed if you flashed rezound cubed 1.0.2. If you didn't flash that, like I did, you should be fine.
Sent from my ADR6425LVW using xda premium
Well if that's true then yeah I'm ok, I see 1.0.2 is from 1/17 and I know I flashed it well before that, so I guess that explains why I haven't had any issues. Thanks!
rboddy said:
Well if that's true then yeah I'm ok, I see 1.0.2 is from 1/17 and I know I flashed it well before that, so I guess that explains why I haven't had any issues. Thanks!
Click to expand...
Click to collapse
Thanks, I added that date to the OP
It worked
Wasabi, I appriciate you giving me the little extra i needed to get back to stock. Thanks for the help.
So, is the MainVer stuck at the higher version number even if you manually flash the older boot.img from the PC?
The boot.img is independent of the mainver. Once you have it set higher, it can never go back. Possibly on an S-OFF device, but that would be pointless.
Oh thrill. So no ICS for us who flashed the dsb kernel? I hope the real HTC ICS is out soon then.....
ok i downloaded the factory telus PH85IMG.zip file i relocked the bootloader then i flashed the file when i hit reboot it goes to htc logo then back to bootloader why?
avenged_sevenfold27 said:
ok i downloaded the factory telus PH85IMG.zip file i relocked the bootloader then i flashed the file when i hit reboot it goes to htc logo then back to bootloader why?
Click to expand...
Click to collapse
unlock your bootloader using hasoon aio kit here
http://forum.xda-developers.com/showthread.php?t=1493905
relock your bootloader again.
format you externel sd card.
download a different copy of PH85IMG.
you know the rest..
so i format the sdcard after i relock thebootloader? because it wont let me into recovery once my bootloader is locked the only place it allows me to go is inside the bootloader
avenged_sevenfold27 said:
so i format the sdcard after i relock thebootloader? because it wont let me into recovery once my bootloader is locked the only place it allows me to go is inside the bootloader
Click to expand...
Click to collapse
No,formatting the sd card is a different issue,its for clear all the possible bad sectors and files....put your PH85IMG file after formatting the sd card...and you do not need recovery while you returning to stock...right
If i,ve helped you,then don't forget to hit the thanks button
avenged_sevenfold27 said:
because it wont let me into recovery once my bootloader is locked the only place it allows me to go is inside the bootloader
Click to expand...
Click to collapse
you do not need recovery to flash a stock ROM,because the fastboot automatically detects your PH85IMG from your ext sd card.
avenged_sevenfold27 said:
so i format the sdcard after i relock thebootloader? because it wont let me into recovery once my bootloader is locked the only place it allows me to go is inside the bootloader
Click to expand...
Click to collapse
relock the bootloader then flash your ruu once it's done flash the jbear hboot (or else you'll have trouble flashing the recovery) plus since you already have an ics firmware why are you messing your phone up :S just flash some rom and enjoy it? you keep flashing stuff more than using your phone as a phone :/
I unlocked and installed cm 10 before I s-off. Could not run s-off successfully without stock.
So... I asked similar questions a month or so back about Telus.
I can't successfully rollback to the gb ruu or the ics ruu. The ics ruu is an ota which appears to need an gb install.
Pure stock tmous ruu check for tmous cid and fails when it finds the Telus cid.
Finally installed arhd 4 and s-off tool ran without error. I could then flash radio and hboot
Sent from my HTC_Amaze_4G using xda premium
bhtm said:
I unlocked and installed cm 10 before I s-off. Could not run s-off successfully without stock.
So... I asked similar questions a month or so back about Telus.
I can't successfully rollback to the gb ruu or the ics ruu. The ics ruu is an ota which appears to need an gb install.
Pure stock tmous ruu check for tmous cid and fails when it finds the Telus cid.
Finally installed arhd 4 and s-off tool ran without error. I could then flash radio and hboot
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
what is arhd4 wher can i find it can u upload it for me? im amaze 4g mobilicity
Alimataei said:
what is arhd4 wher can i find it can u upload it for me? im amaze 4g mobilicity
Click to expand...
Click to collapse
ARHD4 is short for Android Revolution HD version 4 which has recently been updated to version 5. It's a ROM that's very close to stock T-Mobile OTA from March of 2013, it's deodexed, with minor tweaks and slight debloating, and addons which are done through the Aroma installer. It can be found in the dev section of this board.
Odysseus1962 said:
ARHD4 is short for Android Revolution HD version 4 which has recently been updated to version 5. It's a ROM that's very close to stock T-Mobile OTA from March of 2013, it's deodexed, with minor tweaks and slight debloating, and addons which are done through the Aroma installer. It can be found in the dev section of this board.
Click to expand...
Click to collapse
ty
i installed arhd5 but when tried to s-off gives me error that u are not on stock rom
and i searched forum and google no arhd4 found
can anyone upload it for me?
Alimataei said:
ty
i installed arhd5 but when tried to s-off gives me error that u are not on stock rom
and i searched forum and google no arhd4 found
can anyone upload it for me?
Click to expand...
Click to collapse
I don't believe you can s-off with any non-stock ROM (though I may be mistaken). I think you need to be on the latest factory image from your carrier before you can run the s-off hack or it won't work. Reread through the instructions carefully and I think you'll find what I'm saying is correct.
+1
Sent from my HTC_Amaze_4G using Tapatalk
bhtm said:
I unlocked and installed cm 10 before I s-off. Could not run s-off successfully without stock.
So... I asked similar questions a month or so back about Telus.
I can't successfully rollback to the gb ruu or the ics ruu. The ics ruu is an ota which appears to need an gb install.
Pure stock tmous ruu check for tmous cid and fails when it finds the Telus cid.
Finally installed arhd 4 and s-off tool ran without error. I could then flash radio and hboot
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Odysseus1962 said:
I don't believe you can s-off with any non-stock ROM (though I may be mistaken). I think you need to be on the latest factory image from your carrier before you can run the s-off hack or it won't work. Reread through the instructions carefully and I think you'll find what I'm saying is correct.
Click to expand...
Click to collapse
this is my wxact problem and he fixed it with arhd4
Alimataei said:
this is my wxact problem and he fixed it with arhd4
Click to expand...
Click to collapse
ARHD won't help you for several reasons. First, it isn't a stock ROM, it's been rooted, deodexed, and some apps removed from stock. Second, it's based on a T-Mobile ruu and you don't have the T-Mobile version of this handset. There are several threads which detail how you can get back to stock, please read them, use the search function, and do some research for yourself rather than spamming the board requesting help.
Odysseus1962 said:
ARHD won't help you for several reasons. First, it isn't a stock ROM, it's been rooted, deodexed, and some apps removed from stock. Second, it's based on a T-Mobile ruu and you don't have the T-Mobile version of this handset. There are several threads which detail how you can get back to stock, please read them, use the search function, and do some research for yourself rather than spamming the board requesting help.
Click to expand...
Click to collapse
i searched 1 week this is the remaining answer and i have arhd5 installed and working so it doesnt mean i cant flash custom t-mob roms
Odysseus1962 said:
I don't believe you can s-off with any non-stock ROM (though I may be mistaken). I think you need to be on the latest factory image from your carrier before you can run the s-off hack or it won't work. Reread through the instructions carefully and I think you'll find what I'm saying is correct.
Click to expand...
Click to collapse
NEW PROB :
i have installed RMS_Quick-sense_v7.0_signed.zip and tried to s-off my phone:
it gave me no error and i successfully get to wire trick step but my phone dont have the pin!!!!!!
here is picture:
Alimataei said:
i searched 1 week this is the remaining answer and i have arhd5 installed and working so it doesnt mean i cant flash custom t-mob roms
Click to expand...
Click to collapse
Reread my post. I didn't say you couldn't flash it, I said you couldn't attain s-off with it, because it isn't a stock ROM for your device. In order to attain s-off the CID of the ROM has to match the CID of your handset. The vast majority of ROMs for the Amaze are made from a T-Mobile base so they are incompatible for your purposes because of this mismatch. What about this fact do you not understand? There have been many threads written about this, and the solutions have been given to you by several folks here in the forum.
Regardless, please discontinue spamming the board, especially when you have been told how to resolve your issue. You were the one who didn't initially follow directions and are now stuck, not any of us. If you're incapable of following basic directions or searching for the answers yourself then you shouldn't be modding your phone in the first place.
Odysseus1962 said:
Reread my post. I didn't say you couldn't flash it, I said you couldn't attain s-off with it, because it isn't a stock ROM for your device. In order to attain s-off the CID of the ROM has to match the CID of your handset. The vast majority of ROMs for the Amaze are made from a T-Mobile base so they are incompatible for your purposes because of this mismatch. What about this fact do you not understand? There have been many threads written about this, and the solutions have been given to you by several folks here in the forum.
Regardless, please discontinue spamming the board, especially when you have been told how to resolve your issue. You were the one who didn't initially follow directions and are now stuck, not any of us. If you're incapable of following basic directions or searching for the answers yourself then you shouldn't be modding your phone in the first place.
Click to expand...
Click to collapse
plz dont spam forum with ur useless answers
Hahahahaha you are the one whos spaming bro and then getting mad over it.....
Sent from my HTC_Amaze_4G using Tapatalk
Muneeb Saeed said:
Hahahahaha you are the one whos spaming bro and then getting mad over it.....
Sent from my HTC_Amaze_4G using Tapatalk
Click to expand...
Click to collapse
im s-off now by speed rom so u 2 plz dont help anyone else
wished to can unthanks u!
Can some one direct me to where the most up to date radio is for the HTC EVO LTE. And if you can be specific in your explanation to which file or files I need to flash, that would be great. I am S-off, so I have no concerns there.
NoClemency said:
Can some one direct me to where the most up to date radio is for the HTC EVO LTE. And if you can be specific in your explanation to which file or files I need to flash, that would be great. I am S-off, so I have no concerns there.
Click to expand...
Click to collapse
Click the radio in my signature.
Captain_Throwback said:
Click the radio in my signature.
Click to expand...
Click to collapse
I already found this, but these files look different than what I'm used to seeing. Which file or files for Jewel do I need to flash? Basically what I'm trying to ask is which one or ones are the radios that I need to flash in recovery?
NoClemency said:
I already found this, but these files look different than what I'm used to seeing. Which file or files for Jewel do I need to flash? Basically what I'm trying to ask is which one or ones are the radios that I need to flash in recovery?
Click to expand...
Click to collapse
You don't flash them in recovery. There should be instructions in that thread, which would also be the best place to post your question about it.
Captain_Throwback said:
You don't flash them in recovery. There should be instructions in that thread, which would also be the best place to post your question about it.
Click to expand...
Click to collapse
Thanks, I will take a look at it and message you if I don't figure it out. Thanks.
Captain_Throwback said:
You don't flash them in recovery. There should be instructions in that thread, which would also be the best place to post your question about it.
Click to expand...
Click to collapse
From my understanding, I simply need to download this file http://api.viglink.com/api/click?format=go&jsonp=vglnk_jsonp_14038262922359&key=24636c05045fe31f69f1eb3e4d641948&libId=004339bf-8139-4787-8c79-40bea463038c&loc=http%3A%2F%2Fthemikmik.com%2Fshowthread.php%3F13192-RADIOS-RECOVERY-FLASHABLE-Jewel-Radio-Collection%26p%3D220556%26viewfull%3D1%23post220556&v=1&out=http%3A%2F%2Fd-h.st%2FRbT&title=%5BFIRMWARE%5D%5BS-OFF%5D%20Jewel%20Firmware%20Collection%20-%20Latest%3A%203.17.651.4%20OTA%20-%20theMikMik&txt=%3Cfont%20size%3D%223%22%3E%22Full%22%20Firmware%20zip%3C%2Ffont%3E and flash it in recovery, and I should be good to go. Is that correct, and is this the most up to date version, because I noticed it doesn't match the version in your signature?
That's not the newest radios, and no, they are not flashed through recovery. They are flashed through the bootloader. If you aren't planning on updating to Android 4.3, however, those are the newest and will work fine. For more info, click the top link in my sig and read the section regarding firmware updates.
Sent from my HTC device
Magnum_Enforcer said:
That's not the newest radios, and no, they are not flashed through recovery. They are flashed through the bootloader. If you aren't planning on updating to Android 4.3, however, those are the newest and will work fine. For more info, click the top link in my sig and read the section regarding firmware updates.
Sent from my HTC device
Click to expand...
Click to collapse
You are right, I forgot you do flash them in the boot loader. My question now is that I'm currently on 4.1.1 but may in the future update to 4.3. As a result, can you point me specifically to the file that I need to flash in the boot loader. Is the file I need to flash in the boot loader called 4.13.651.4 Sense 5 Android 4.3 - Odex or is it something else. Sorry for asking such stupid questions, but I'm getting confused.
If you want to update to 4.3 you should run the RUU. That will make sure everything gets updated. The RUU will also change how the internal storage is set up. In that same link I mentioned above, there is a link to all the applicable RUU's for this device.
Sent from my HTC device
Magnum_Enforcer said:
If you want to update to 4.3 you should run the RUU. That will make sure everything gets updated. The RUU will also change how the internal storage is set up. In that same link I mentioned above, there is a link to all the applicable RUU's for this device.
Sent from my HTC device
Click to expand...
Click to collapse
Thanks for the information. I decided to simply use the older radio link that I linked you that you said is the most up to date version if I'm not switching over to 4.3. I'm planning on getting a new phone soon, so I didn't want to take the time to switch to 4.3 right now. I already flashed the radios and everything looks to be working fine. Thanks for your help.
NoClemency said:
Thanks for the information. I decided to simply use the older radio link that I linked you that you said is the most up to date version if I'm not switching over to 4.3. I'm planning on getting a new phone soon, so I didn't want to take the time to switch to 4.3 right now. I already flashed the radios and everything looks to be working fine. Thanks for your help.
Click to expand...
Click to collapse
Glad to help:good: