Radio zip flash Help - AT&T, Rogers HTC One X, Telstra One XL

I updated the firmware to 2.18, and eventually tried flashing other radios to try and better my reception...only making me want to return to the radio supplied with Firmware 2.18 (1.35a.32.45.27_10.144.32.34aL). I tried extracting the radio from the Firmware zip file and flashing using adb, but getting a "Failed (remote not allowed).
If someone would be so kind to create a flashable zip for this radio, it would be much appreciate (as i don't see it listed in the current Radio Thread).

Do you have a download link for just the radio.img file?
Sent from my Evita

timmaaa said:
Do you have a download link for just the radio.img file?
Sent from my Evita
Click to expand...
Click to collapse
Not for just the radio.img, but I extracted it from the 2.18 Firmware zip download: http://www.androidfilehost.com/?fid=23329332407573790

Are you s-off?
Sent from my Evita

timmaaa said:
Are you s-off?
Sent from my Evita
Click to expand...
Click to collapse
Yes...S-Off.

What method did you initially use on your attempt to flash the radio you extracted?
Sent from my Evita

timmaaa said:
What method did you initially use on your attempt to flash the radio you extracted?
Sent from my Evita
Click to expand...
Click to collapse
Placed the radio.img file into the adb/fastboot folder
Opened cmd
adb reboot bootloader
fastboot flash radio radio.img

timmaaa, do you think it be worthy of asking this request in the Radio/Ril thread? Wasn't sure which section it would be appropriate to request someone to create the 1.35 radio flashable zip file.

I'm doing some investigating, I haven't made one before so I'm a bit apprehensive. It wouldn't hurt to request it, just tag the thread owner. You'll need to provide him with a direct link to whatever he requests though, to make it as easy as possible for him.
Sent from my Evita

timmaaa said:
I'm doing some investigating, I haven't made one before so I'm a bit apprehensive. It wouldn't hurt to request it, just tag the thread owner. You'll need to provide him with a direct link to whatever he requests though, to make it as easy as possible for him.
Sent from my Evita
Click to expand...
Click to collapse
OK...I may do that.
I ended up just reflashing the 2.18 firmware, and got the radio back. I was a little apprehensive too in doing this, but it seemed to work. It would be nice to have the 1.35 radio zip file though.
Thanks for all your help/insight. Your definitely and asset to xda!

Related

[Q] Replacing files in signed RUU with S-OFF Hboot with ENG S-OFF

I'm sure this is a dumb question but couldn't we take a signed RUU update and pull the update zip from the RUU*.exe and extract the firmware.zip and replace the hboot* with an hboot from someone's phone that has ENG S-OFF then repackage it back into the update.zip and let RUU update it to the phone? Would the phone catch it when it did a MD5? Does the phone check the MD5 or does the computer? I have linux I'm sure I could make a hacked MD5 sum program that could give RUU the same MD5 value as the original? If this is dumb just tell me...
shootind5nukes said:
I'm sure this is a dumb question but couldn't we take a signed RUU update and pull the update zip from the RUU*.exe and extract the firmware.zip and replace the hboot* with an hboot from someone's phone that has ENG S-OFF then repackage it back into the update.zip and let RUU update it to the phone? Would the phone catch it when it did a MD5? Does the phone check the MD5 or does the computer? I have linux I'm sure I could make a hacked MD5 sum program that could give RUU the same MD5 value as the original? If this is dumb just tell me...
Click to expand...
Click to collapse
Once you repackage anything, signature is broken and can not be resigned without HTC's private keys. Not to be a nark but just post this in the fre3vo thread or another development thread or even the q and a section so we keep the dev section clean
Can s-off come out and play? You run but you can't hide
aray92 said:
Once you repackage anything, signature is broken and can not be resigned without HTC's private keys. Not to be a nark but just post this in the fre3vo thread or another development thread or even the q and a section so we keep the dev section clean
Can s-off come out and play? You run but you can't hide
Click to expand...
Click to collapse
Well thanks for answering, I didn't want to post in another thread and be accused of hijacking someone elses thread....Thanks for the help.
I think developers of xtc maybe know how to sign it.
Sent from my HTC Sensation Z710e using XDA App
jerrylzy said:
I think developers of xtc maybe know how to sign it.
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Even if they signed it, the signature would not match what the Sensation is expecting, so it wouldn't work.
Simple Answer is no. If raskall (XTC-Clip) would know the HTC´s key he could crack it in a couple of hours.
If anyone knew the key they could crack it instantly...
theres nothing easier than re-signing .zips
I went in this thread expecting flaming and sarcastic answers, but I was wrong. This forum is getting better!
I used xtc-clip to s-off my phone and it said cid incorrect..If it don't have signature it will show nothing,actually xtc shows cid incorrect.It proves xtc has the signature.
I noticed when I extracted the rom.zip and tried to flash it via fastboot that the signature error did come up, would it matter if somehow you could freeze the ruu and replace that rom.zip with the altered rom.zip(with eng hboot) and somehow get the ruu to push that file instead of the one just created by the ruu, would you still get a signature error?
shootind5nukes said:
I noticed when I extracted the rom.zip and tried to flash it via fastboot that the signature error did come up, would it matter if somehow you could freeze the ruu and replace that rom.zip with the altered rom.zip(with eng hboot) and somehow get the ruu to push that file instead of the one just created by the ruu, would you still get a signature error?
Click to expand...
Click to collapse
Yes because the phone is checking the signature...not the RUU.
Sent from my microwave.
NSider said:
I went in this thread expecting flaming and sarcastic answers, but I was wrong. This forum is getting better!
Click to expand...
Click to collapse
Depends on who you talk to.
Well as a test I tried to flash the rom.zip(unaltered). I just waited until RUU*.exe moved the rom.zip to temp files and then I just hit cancel on the RUU update. So the zip file was untouched and my phone still rejected it. That makes me think that maybe the RUU signs the zip file right before pushing it to the phone? Thoughts?

[Q] How do I flash a new radio?

I see the thread that showed the new 3.18 radio for AT&T is out. I have SCID, root, S-OFF, and viper XL installed - I've gotten that much, however, how do I upgrade the radio?
I see in the radio thread that there are 2 downloads, one that has RLL files and one that does not - which do I need? Thanks for the help!
use the 3.18 Radio from here:
http://forum.xda-developers.com/showthread.php?t=1694012
in youre case, you can Flash the zip in TWRP as you do with a ROM.
the RIL files maybe can make Problems.
Ghostrider said:
use the 3.18 Radio from here:
http://forum.xda-developers.com/showthread.php?t=1694012
in youre case, you can Flash the zip in TWRP as you do with a ROM.
the RIL files maybe can make Problems.
Click to expand...
Click to collapse
So download the zip to a location on the phone's memory, reboot into TWRP, select the file, and flash it?
yes, thats all it Needs
and only you are s-off.

[Q] HTC One XL - Reverting back to Stock Telstra

Hi Guys,
I have been having issues pretty much since I got my phone.
This has been to do with reception, it will say that it has full reception but just won't send messages, make calls or have any connectivity.
I was silly in thinking that maybe flashing a custom rom would help, I still have the issue.
I assume this is a hardware issue so I am at the point where I want to return the phone to Telstra.
I believe if it is a hardware fault I can return it no dramas, just have to flash it back to stock Rom?
Cheers for any help
Alex
Yeah I'd return it to Telstra and try your luck. But I'm not sure whether they'll replace/repair it under warranty though. I've worked at a mobile repair centre for one of the majors here in Australia, they do check whether the handset has been altered. Their excuse for not covering it under warranty will most likely be that the changes you made could have affected the handset, thus causing the issue you're having. It would have been best to send it back before rooting it, then they wouldn't really have a leg to stand on.
Sent from my One XL using XDA Premium
timmaaa said:
Yeah I'd return it to Telstra and try your luck. But I'm not sure whether they'll replace/repair it under warranty though. I've worked at a mobile repair centre for one of the majors here in Australia, they do check whether the handset has been altered. Their excuse for not covering it under warranty will most likely be that the changes you made could have affected the handset, thus causing the issue you're having. It would have been best to send it back before rooting it, then they wouldn't really have a leg to stand on.
Sent from my One XL using XDA Premium
Click to expand...
Click to collapse
Yeah, I was silly to think that I would be able to fix it with a root..
I have heard of people getting repairs after rooting though.
What's the best way to return it to stock?
Root wouldn't fix anything. Flashing a custom ROM wouldn't fix anything more than running an RUU would fix either.
If you didn't have to supercid to root you can just run the RUU. there's a few ruu threads linked in the resource compilation thread. There's a link in my signature.
Sent from my One X using xda app-developers app
exad said:
Root wouldn't fix anything. Flashing a custom ROM wouldn't fix anything more than running an RUU would fix either.
If you didn't have to supercid to root you can just run the RUU. there's a few ruu threads linked in the resource compilation thread. There's a link in my signature.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I've heard of it fixing peoples reception issues, but sadly not mine.
I've currently got Hboot 1.110000
Can I flash the stock Telstra 3.17 RUU on this hboot?
alexc2005 said:
I've heard of it fixing peoples reception issues, but sadly not mine.
I've currently got Hboot 1.110000
Can I flash the stock Telstra 3.17 RUU on this hboot?
Click to expand...
Click to collapse
Yes.
And rooting would not fix Radio reception, Flashing a new Radio might improve reception but for the most part I wouldn't say it would be a drastic change.
exad said:
Yes.
And rooting would not fix Radio reception, Flashing a new Radio might improve reception but for the most part I wouldn't say it would be a drastic change.
Click to expand...
Click to collapse
Thanks for that.
I appear to have my terminology mixed up.
By "rooting" I was referring to the installation of a custom rom and radio.
Hi Exad,
Thanks for your help so far.
I am planning to flash stock recovery and then the stock telstra RUU.
Do you know where I can get the stock recovery from?
Thanks
Alex
I suspect I have found it.
I will extract it from the stock RUU
Thanks!
alexc2005 said:
Hi Exad,
Thanks for your help so far.
I am planning to flash stock recovery and then the stock telstra RUU.
Do you know where I can get the stock recovery from?
Thanks
Alex
Click to expand...
Click to collapse
It included in the ruu just run the ruu it will flash everything for you
Sent from my HTC One X using Tapatalk 2
This might be a dumb question, but my RUU is a zip file...
How do I "run" it?
Note: I changed it from a .zip to a .exe, but apparently there was a file compatibility issue..seems to be an issue with windows, perhaps cause I run 64bit win 7?
alexc2005 said:
This might be a dumb question, but my RUU is a zip file...
How do I "run" it?
Note: I changed it from a .zip to a .exe, but apparently there was a file compatibility issue..seems to be an issue with windows, perhaps cause I run 64bit win 7?
Click to expand...
Click to collapse
If it's a .zip it's an OTA. Those need to be flashed using stock recovery. If you don't have a stock recovery image you can extract it from that zip file, it may be buried deep. It'll be called recovery.img or recovery_signed.img I believe.
You would need to fastboot flash the recovery, then boot to that stock recovery and install the zip file like you would flash a ROM. It could take a while too.
exad said:
If it's a .zip it's an OTA. Those need to be flashed using stock recovery. If you don't have a stock recovery image you can extract it from that zip file, it may be buried deep. It'll be called recovery.img or recovery_signed.img I believe.
You would need to fastboot flash the recovery, then boot to that stock recovery and install the zip file like you would flash a ROM. It could take a while too.
Click to expand...
Click to collapse
Hmm that's interesting.
I have downloaded 2 RUU's, based on filesize (one was 600mb, one was 90mb) both appear to be "OTA"
At this point I have extracted the recovery.img from the OTA zip (in firmware) and flashed that using fastboot and done the oem lock thing too. So it now says relocked.
The point I am up to I believe is flashing the full RUU to the phone, which I believe you have to do through fastboot?
Do I need to flash this via stock recovery? I tried to get into stock recovery last night but it just came up with a red triangle with a ! in it and a phone underneath.
EDIT: ok I got into stock recovery. I don't see a way of flashing it as it doesn't appear to be able to mount my SD Card.
Is there anywhere I can get the RUU and not the OTA? I got the OTA from a thread on here with all of the RUU links. They all seemed to be .zip for Telstra Aus..
I'm going to just use the 1.89 RUU and then upgrade as neccesary.
Can't find the 3.17 .exe.
Should be able to just OTA the newer updates when I boot into the rom.
alexc2005 said:
Hmm that's interesting.
I have downloaded 2 RUU's, based on filesize (one was 600mb, one was 90mb) both appear to be "OTA"
At this point I have extracted the recovery.img from the OTA zip (in firmware) and flashed that using fastboot and done the oem lock thing too. So it now says relocked.
The point I am up to I believe is flashing the full RUU to the phone, which I believe you have to do through fastboot?
Do I need to flash this via stock recovery? I tried to get into stock recovery last night but it just came up with a red triangle with a ! in it and a phone underneath.
EDIT: ok I got into stock recovery. I don't see a way of flashing it as it doesn't appear to be able to mount my SD Card.
Is there anywhere I can get the RUU and not the OTA? I got the OTA from a thread on here with all of the RUU links. They all seemed to be .zip for Telstra Aus..
Click to expand...
Click to collapse
The ruu is a .exe file
Sent from my HTC One X using xda app-developers app
It's possible they didn't release an RUU, I would download an older RUU and then update over the air.
Here's a link to the 1.89 ruu: http://bugsylawson.com/files/file/2...8c320901-1093a3220l-release-266699-signedexe/
Just check for updates after and let it update if you want to go to 3.18
exad said:
It's possible they didn't release an RUU, I would download an older RUU and then update over the air.
Here's a link to the 1.89 ruu: http://bugsylawson.com/files/file/2...8c320901-1093a3220l-release-266699-signedexe/
Just check for updates after and let it update if you want to go to 3.18
Click to expand...
Click to collapse
Yeah, that's my plan . Thanks for all the help mate!

[Q] Set Telstra HTC One XL to s-off

Hi guys, first time poster - I want to install the following custom rom...
http://forum.xda-developers.com/showthread.php?t=2442946
... and being new to android modding, do not want to brick it by doing something wrong.
I gather i need to set up superCID and then set to s-off - would anyone be able to point me in the right direction on how to do these correctly for a Telstra phone?
My phone is rooted with CWM, from whati gather (it says "ClockworkMod recovery" in recovery mode).
Thanks
jacen72 said:
Hi guys, first time poster - I want to install the following custom rom...
http://forum.xda-developers.com/showthread.php?t=2442946
... and being new to android modding, do not want to brick it by doing something wrong.
I gather i need to set up superCID and then set to s-off - would anyone be able to point me in the right direction on how to do these correctly for a Telstra phone?
My phone is rooted with CWM, from whati gather (it says "ClockworkMod recovery" in recovery mode).
Thanks
Click to expand...
Click to collapse
You might already have SuperCID, you can use a fastboot command to check. The command is:
Code:
fastboot oem readcid
If it comes back as anything other than 11111111 you can use this method to get SuperCID.
Once you have SuperCID you can use this method to get s-off.
Sent from my Evita
timmaaa said:
You might already have SuperCID, you can use a fastboot command to check. The command is:
Code:
fastboot oem readcid
If it comes back as anything other than 11111111 you can use this method to get SuperCID.
Once you have SuperCID you can use this method to get s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, i will take a closer look soon. Is it true that for Telstra phones the CID needs to be 22222222, or is 11111111 okay as well?
jacen72 said:
Thanks, i will take a closer look soon. Is it true that for Telstra phones the CID needs to be 22222222, or is 11111111 okay as well?
Click to expand...
Click to collapse
The 22222222 CID only applies to at&t phones trying to unlock their bootloader via htcdev, this is because at&t stock CID (cws__001) plus 11111111 CID have been blocked at htcdev. For your purposes 11111111 will be fine.
Sent from my Evita
timmaaa said:
The 22222222 CID only applies to at&t phones trying to unlock their bootloader via htcdev, this is because at&t stock CID (cws__001) plus 11111111 CID have been blocked at htcdev. For your purposes 11111111 will be fine.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the info - i know i need to superCID as i checked last night and CID was TELST001 (from memory). Will use 11111111.
No problems, did you use the fastboot command the check your CID? I only ask because there are apps available which claim to display your CID but they show the original CID, not the current one.
Sent from my Evita
timmaaa said:
No problems, did you use the fastboot command the check your CID? I only ask because there are apps available which claim to display your CID but they show the original CID, not the current one.
Sent from my Evita
Click to expand...
Click to collapse
I tried so many things last night i couldn't tell you exactly what i did, haha! Will try your way and see what it says.
A quick question - in regard to the facepalm link, it says "Download patcher and unzip it in your working directory" - can this be any folder on my phone (eg: Downloads)? I'm also guessing the other file (OneX.zip) goes in the same directory?
No you place the extracted patcher files and the PJ8312000-OneX.zip into your fastboot folder on your pc.
You need to have adb/fastboot and HTC drivers installed on your pc to do the s-off process.
Sent from my Evita
jacen72 said:
I tried so many things last night i couldn't tell you exactly what i did, haha
Click to expand...
Click to collapse
You should keep better track of things you are doing or you will end like NASA on Apollo 1 and not knowing what went wrong.
To repair something you need to know what you did to break it.
Big thanks timmaaa, have upgraded successfully!
twistedddx, you're not wrong - i should have kept an eye on what i was doing. Luckily for me, all went well!
Thanks again.
Glad to see you got it all sorted mate.
Sent from my Evita
Hi guys, since updating Android, i seem to find my service connection (no service) is being lost fairly easily - is there something i need to do in regard to this, or is it just me?!
Cheers
Which ROM are you on?
Sent from my Evita
timmaaa said:
Which ROM are you on?
Sent from my Evita
Click to expand...
Click to collapse
the one from the following link:
http://forum.xda-developers.com/showthread.php?t=2442946
You either need to update your firmware to 2.15 or just flash the Beastmode kernel.
Sent from my Evita
timmaaa said:
You either need to update your firmware to 2.15 or just flash the Beastmode kernel.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, when you talk about beastmode, is the following link what you are referring to?
http://forum.xda-developers.com/showthread.php?t=1797251
Also, with firmware 2.15 - i would actually like to keep it as stock as possible, so perhaps the firmware upgrade would be the better option? I have found a link that looks like it goes to the correct download:
http://forum.xda-developers.com/showthread.php?p=45646878 - (see last post)
Would i be right in saying the instructions for updating the kernel would be the same as at the following link:
http://forum.xda-developers.com/showthread.php?t=2423735 - (OPTIONAL: Installing the Firmware)
Thanks again for your help.
The first link is incorrect, you can find the Beastmode kernel in our development section. The kernel you just install in recovery.
The last link you quoted is where you'll find the 2.15 firmware, and the install instructions see in the first post on that thread (it's a manual install using fastboot).
Sent from my Evita
timmaaa said:
The first link is incorrect, you can find the Beastmode kernel in our development section. The kernel you just install in recovery.
The last link you quoted is where you'll find the 2.15 firmware, and the install instructions see in the first post on that thread (it's a manual install using fastboot).
Sent from my Evita
Click to expand...
Click to collapse
Thanks - looks easy enough. Can i ask what why i would install Beastmode instead of the firmware upgrade? From what i gather, it is to overclock the CPU?
You can leave the Beastmode settings stock, it's just an easier and safer fix rather than upgrading firmware. You can OC if you wish to of course. There's always a small risk involved with anything that touches your hboot.
Sent from my Evita
timmaaa said:
You can leave the Beastmode settings stock, it's just an easier and safer fix rather than upgrading firmware. You can OC if you wish to of course. There's always a small risk involved with anything that touches your hboot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, maybe i will install beastmode instead then if it will help fix my connection issues. Sorry, but would you be able to point in the direction of where it is in the development section, i cannot seem to find it.
I promise if this works you wont have to hear my noob questions anymore!!

[Q] How to Update to OTA_K2_UL_JB422_SENSE50_MR_hTC_Asia_WWE_3.12.707.2

Hi Guys,
Good day!
Have received a system update notification on my One SV and downloaded the file:
OTA_K2_UL_JB422_SENSE50_MR_hTC_Asia_WWE_3.12.707.2-2.14.707.5_release_3445776pznn0vdk5c0jhzu
However, my phone is rooted, with CWM Recovery v6.0.3.2.
Please help on how will I able to install the update.
Thanks!
My bootloader info:
TAMPERED
UNLOCKED
K2_UL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40a.00.07
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 7 2013, 22:41:40:-1
You must restore your stock recovery. Also the boot.img and system partition (System apps) must be stock and nothing deleted!
old.splatterhand said:
You must restore your stock recovery. Also the boot.img and system partition (System apps) must be stock and nothing deleted!
Click to expand...
Click to collapse
Thanks for the reply!
Can you please teach me how to restore everything?
I have read your guide but I think it will not be applicable(?) in my case since my phone is Asia WWE and there is no available RUU for K2_UL.
Thanks!
I think, the best for you is, read and follow this thread.
@russellvone did a good job in building things for asian phones
old.splatterhand said:
I think, the best for you is, read and follow this thread.
@russellvone did a good job in building things for asian phones
Click to expand...
Click to collapse
Thanks again for the reply.
During downgrade of hboot, I have received the ff. error:
Model ID incorrect! Update Fail!
When I run the command on Terminal Emulator, I got 2 model IDs:
PL8010000, PL8015000
Please help.
Thanks!
The hboot downgrade is only for european phones. There is no RUU for your asia model. You have another radio.img.
old.splatterhand said:
The hboot downgrade is only for european phones. There is no RUU for your asia model. You have another radio.img.
Click to expand...
Click to collapse
That's sad news..
I think the problem is that my hboot cannot be downgraded, since the RUU issue can be solved using @russellvone 's method.
Anyway, thanks a lot!
You can update with a special firmware.zip. You need to backup your radio.img first, and replace it with the one inside the firmware.zip. Then you need to edit the model id in the android-info.txt of firmware.zip.
This must be flashed and then you can restore a european backup/rom.
Maybe @renanski still has his radio.img and can share it with us. He has also asia k2ul.
I've got a copy if needed @old.splatterhand @palamanTM
russellvone said:
I've got a copy if needed @old.splatterhand @palamanTM
Click to expand...
Click to collapse
K2ul Asia radio.img? Share it with us
And also already a firmware.zip for it?
old.splatterhand said:
K2ul Asia radio.img? Share it with us
And also already a firmware.zip for it?
Click to expand...
Click to collapse
uploading now
---------- Post added at 02:49 PM ---------- Previous post was at 02:47 PM ----------
K2_UL_Asia_Radio.img_PL80IMG.zip
@old.splatterhand
Thanks, @russellvone for this!
Have replaced the android-info.txt in the original PL80IMG.zip file and tried again to downgrade the hboot.
But I got "CID Incorrect!" error.
after moonshine S-OFF, my phone's info is now:
K2_UL PVT SHIP S-OFF RL
CID-HTC_044
HBOOT-2.00.4444
RADIO-1.15.40a.00.07
OpenDSP-v9.2.0268.1214
eMMC-boot
Thanks again for the assistance!
You need to get Supercid first. Use this fastboot cmd:
fastboot oem writecid 11111111
Click to expand...
Click to collapse
old.splatterhand said:
You need to get Supercid first. Use this fastboot cmd:
Click to expand...
Click to collapse
Thanks! My hboot was successfully downgraded!
But when I run the RUU, I'm getting an "MODEL ID ERROR."
I tried to extract the rom from temp files (as instructed by @russellvone in the other thread) but I am always getting a corrupted zip.
There was another method mentioned in that thread, using an extractor, but unfortunately, I have no linux pc to run the program.
Maybe @wilson3q or any of you guys can share the rom file.
And please enumerate again the correct procedure in flashing, as I was not able to get it clearly on the other thread.
Please help.
Thanks again.
palamanTM said:
Thanks! My hboot was successfully downgraded!
But when I run the RUU, I'm getting an "MODEL ID ERROR."
I tried to extract the rom from temp files (as instructed by @russellvone in the other thread) but I am always getting a corrupted zip.
There was another method mentioned in that thread, using an extractor, but unfortunately, I have no linux pc to run the program.
Maybe @wilson3q or any of you guys can share the rom file.
And please enumerate again the correct procedure in flashing, as I was not able to get it clearly on the other thread.
Please help.
Thanks again.
Click to expand...
Click to collapse
This way is only for a model with existing RUU!
Lets try another way:
Download this firmware.zip: http://d-h.st/69V
Make sure, the android-info.txt is correct for your model id. Replace the radio.img inside, with the one from russel, the rename the firmware.zip to PL80IMG.zip and put it on your sdcard. Boot into bootloader, confirm to flash. After that, install twrp recovery and flash my stock odexed rom.
old.splatterhand said:
This way is only for a model with existing RUU!
Lets try another way:
Download this firmware.zip: http://d-h.st/69V
Make sure, the android-info.txt is correct for your model id. Replace the radio.img inside, with the one from russel, the rename the firmware.zip to PL80IMG.zip and put it on your sdcard. Boot into bootloader, confirm to flash. After that, install twrp recovery and flash my stock odexed rom.
Click to expand...
Click to collapse
I was hoping I can get my phone back to stock to receive the "official" update.
But since there is still no RUU available, I'll go with your stock odexed rom.
Thanks a lot for the assistance, @old.splatterhand and @russellvone! my phone is now 4.2.2!
old.splatterhand said:
This way is only for a model with existing RUU!
Lets try another way:
Download this firmware.zip: http://d-h.st/69V
Make sure, the android-info.txt is correct for your model id. Replace the radio.img inside, with the one from russel, the rename the firmware.zip to PL80IMG.zip and put it on your sdcard. Boot into bootloader, confirm to flash. After that, install twrp recovery and flash my stock odexed rom.
Click to expand...
Click to collapse
What if I flash the firmware.zip inside the OTA file for 4.2.2 and flash your 4.2.2 stock odexed ROM,will it work?
Fysiks said:
What if I flash the firmware.zip inside the OTA file for 4.2.2 and flash your 4.2.2 stock odexed ROM,will it work?
Click to expand...
Click to collapse
Yes, if for your K2 variant.
Sent from my C525c using Tapatalk
Modding.MyMind said:
Yes, if for your K2 variant.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Am I required to flash the boot.img inside the ROM?
Fysiks said:
Am I required to flash the boot.img inside the ROM?
Click to expand...
Click to collapse
If you are S-On, then:
flash Rom via custom recovery after you have conducted a factory reset wipe from within your custom recovery, to include the system partition which can be found in the advance options if using TWRP.
Then, wipe dalvik cache and cache after it finishes
Then, reboot your bootloader, and via fastboot, flash the boot.img which would require you to extract it from the Rom and placing it where your proper adb/fastboot files are on your PC. Use this command:
Code:
fastboot flash boot boot.img
If you are S-Off, then just flash the Rom via custom recovery as explained above. You will not need to flash the boot.img via fastboot. Just wipe dalvik cache and cache after it finishes, and reboot your device.

Categories

Resources