Related
Basically I have the preview build of Jelly Bean (JRN84D) but it keeps alerting me to install the OTA version which fails, I know there are lots of threads about this but I can't seem to find the answer in them, I tried flashing the stock recovery but when I try to boot into it I get the Red exclamation mark and can't do anything with the volume or power keys, this is the same exclamation mark I get when trying to install the update.
I think the recovery file may be corrupt, is this the key to getting OTA update? Also my radio is XXLF1 if that helps. Thanks for any help offered, I watched the video and everybody hates noobs but I tried the solutions in other posts and it seems to have got worse.
EDIT: I can access recovery now, but the update still fails.
Sgtpanda said:
Basically I have the preview build of Jelly Bean (JRN84D) but it keeps alerting me to install the OTA version which fails, I know there are lots of threads about this but I can't seem to find the answer in them, I tried flashing the stock recovery but when I try to boot into it I get the Red exclamation mark and can't do anything with the volume or power keys, this is the same exclamation mark I get when trying to install the update.
I think the recovery file may be corrupt, is this the key to getting OTA update? Also my radio is XXLF1 if that helps. Thanks for any help offered, I watched the video and everybody hates noobs but I tried the solutions in other posts and it seems to have got worse.
EDIT: I can access recovery now, but the update still fails.
Click to expand...
Click to collapse
Flash the Stock Recovery/Radio/Bootloader for Takju from the hosted Google Factory Images through Fastboot. It won't erase your data/apps. For the Recovery, you will need to extract it manually from the image while the bootloader and radio should be standalone.
dnlsmy said:
Flash the Stock Recovery/Radio/Bootloader for Takju from the hosted Google Factory Images through Fastboot. It won't erase your data/apps. For the Recovery, you will need to extract it manually from the image while the bootloader and radio should be standalone.
Click to expand...
Click to collapse
When you say the Takju Google Factory Image do you mean the 4.0.4 takju image? as that's the only one I can find on their site.
Thanks.
Sgtpanda said:
When you say the Takju Google Factory Image do you mean the 4.0.4 takju image? as that's the only one I can find on their site.
Thanks.
Click to expand...
Click to collapse
Yes.
Sent from my Galaxy Nexus using xda app-developers app
wilsonlam97 said:
Yes.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Flashed the radio, bootloader and recovery from it and it still doesn't work, if I press up and power button after it fails it gives me a status 7 error, might just flash stock and unroot if there's no other way.
Sgtpanda said:
Flashed the radio, bootloader and recovery from it and it still doesn't work, if I press up and power button after it fails it gives me a status 7 error, might just flash stock and unroot if there's no other way.
Click to expand...
Click to collapse
What is the error?
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
What is the error?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Any ideas or am I screwed and should go ahead and try flash stock rom and unroot? Will that even help?
Sgtpanda said:
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
What's the FULL error.
Also, are you using a recovery that is different from CWM 5.5.0.2 or 5.5.0.4? If so, get rid of it, and use one of those.
efrant said:
What's the FULL error.
Also, are you using a recovery that is different from CWM 5.5.0.2 or 5.5.0.4? If so, get rid of it, and use one of those.
Click to expand...
Click to collapse
I'm using stock recovery because everything I've read says to use stock if you want to accept OTA updates, the full error is:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk","08db09578758c61cf5c8ec895b1331a5fa4cc349","512784ba869d55f3cf2d291baaa5f6a0aa90b960")
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Sgtpanda said:
I'm using stock recovery because everything I've read says to use stock if you want to accept OTA updates, the full error is:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk","08db09578758c61cf5c8ec895b1331a5fa4cc349","512784ba869d55f3cf2d291baaa5f6a0aa90b960")
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Where did you get the preview build? Based on that error, it would seem to me like you flashed a non-stock version of JB 4.1 like bigxie's ROM. If that is the case, you need to flash a stock ROM before any update can be applied...
efrant said:
Where did you get the preview build? Based on that error, it would seem to me like you flashed a non-stock version of JB 4.1 like bigxie's ROM. If that is the case, you need to flash a stock ROM before any update can be applied...
Click to expand...
Click to collapse
Now that you've mentioned that name, yes that's the ROM I got, I'm gonna go ahead and guess there's no way to return to stock without wiping data is there?
Sgtpanda said:
Now that you've mentioned that name, yes that's the ROM I got, I'm gonna go ahead and guess there's no way to return to stock without wiping data is there?
Click to expand...
Click to collapse
Maybe. You can try this without wiping and see if it works. Then apply the JRO03C-from-JRN84D update form here.
efrant said:
Maybe. You can try this without wiping and see if it works. Then apply the JRO03C-from-JRN84D update form here.
Click to expand...
Click to collapse
And if I do that then will I be able to accept any future OTA updates through android and have it update automatically without having to flash the updates myself?
Sgtpanda said:
And if I do that then will I be able to accept any future OTA updates through android and have it update automatically without having to flash the updates myself?
Click to expand...
Click to collapse
If you follow method 2, then yes, you will be able to automatically accept OTA updates and have it install automatically. BUT, you MAY need to do the first one (i.e., to JRO03C) manually (if you don't get it shortly after you flash JRN84D). After that, you will be all set for the next update.
efrant said:
If you follow method 2, then yes, you will be able to automatically accept OTA updates and have it install automatically. BUT, you MAY need to do the first one (i.e., to JRO03C) manually (if you don't get it shortly after you flash JRN84D). After that, you will be all set for the next update.
Click to expand...
Click to collapse
I'll try it, thanks for the help.
EDIT: It worked! Did it without wiping and it accepted the OTA without needing to do it manually, once again thanks so much for helping!
I just flashed CM10.1 on my Sprint S3.
I am trying to flash the latest nightly and I am getting the following error in both CWM and TWRP
Assert failed: getprop("ro.bootloader" == "l710vpbLj7" ... and it repeats that line specific to other versions (L710VPBMA6 etc)
I had an older version of CWM ... but still a 6+ when I flashed it. I since installed (via goomanager) TWRP as it looked cool. I started getting this error. Next, I used CWM to install the latest 6.0.3.1 version of CWM. It's still not wokring.
I seem to be able to download the goomanager latest DL and that's what I used to get the initial flashable zip.
Any ideas? I'm kinda at a loss. I'd do a full wipe but I'm afraid that if I do that I'll be SOL - as I have a current functional ROM right now.
Thoughts???
Sent from my SPH-L710 using xda app-developers app
Ha ha. You're still in the same, incorrect (international GT-i9300) forum. Try here:
http://forum.xda-developers.com/forumdisplay.php?f=1707
gregory15 said:
I just flashed CM10.1 on my Sprint S3.
I am trying to flash the latest nightly and I am getting the following error in both CWM and TWRP
Assert failed: getprop("ro.bootloader" == "l710vpbLj7" ... and it repeats that line specific to other versions (L710VPBMA6 etc)
I had an older version of CWM ... but still a 6+ when I flashed it. I since installed (via goomanager) TWRP as it looked cool. I started getting this error. Next, I used CWM to install the latest 6.0.3.1 version of CWM. It's still not wokring.
I seem to be able to download the goomanager latest DL and that's what I used to get the initial flashable zip.
Any ideas? I'm kinda at a loss. I'd do a full wipe but I'm afraid that if I do that I'll be SOL - as I have a current functional ROM right now.
Thoughts???
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I have the same problem on the spring gs3 and I can't figure it out.
Whew, someone else with the Asset faled: getprop error
Have you learned anything more about this? I have found I was able to install CM10.1 up to nightly 0511 but nothing after that.
gregory15 said:
I just flashed CM10.1 on my Sprint S3.
I am trying to flash the latest nightly and I am getting the following error in both CWM and TWRP
Assert failed: getprop("ro.bootloader" == "l710vpbLj7" ... and it repeats that line specific to other versions (L710VPBMA6 etc)
I had an older version of CWM ... but still a 6+ when I flashed it. I since installed (via goomanager) TWRP as it looked cool. I started getting this error. Next, I used CWM to install the latest 6.0.3.1 version of CWM. It's still not wokring.
I seem to be able to download the goomanager latest DL and that's what I used to get the initial flashable zip.
Any ideas? I'm kinda at a loss. I'd do a full wipe but I'm afraid that if I do that I'll be SOL - as I have a current functional ROM right now.
Thoughts???
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
FlagPonder said:
Have you learned anything more about this? I have found I was able to install CM10.1 up to nightly 0511 but nothing after that.
Click to expand...
Click to collapse
**** UPDATE *****
****THIS SOLUTION and LINKS ARE ONLY APPLICABLE TO SPRINT GALAXY S3 PHONES ... FYI FYI FYI******
yes. I have. The problem is that we have an old version of the FIRMWARE. If you flash the following to update your firmware to MD4:
http://forum.xda-developers.com/showthread.php?t=1910947 and install Galaxy-S-fre3-MD4FirmwareModemAIO.zip from CWM.
There are some new checks that happen that require the MD4 stuff. For more information about that - you can check https://plus.google.com/app/basic/stream/z13cdxpafunnexghb04cc5q4knbyjh4hprg0k
Also, clear cache/dalvik - not that it matters - but I did that - and i found things working. So, after flash, go into /cmupdate folder and flash the latest - it should work (unless i'm just lucky)
_G
gregory15 said:
**** UPDATE *****
****THIS SOLUTION and LINKS ARE ONLY APPLICABLE TO SPRINT GALAXY S3 PHONES ... FYI FYI FYI******
yes. I have. The problem is that we have an old version of the FIRMWARE. If you flash the following to update your firmware to MD4:
http://forum.xda-developers.com/showthread.php?t=1910947 and install Galaxy-S-fre3-MD4FirmwareModemAIO.zip from CWM.
There are some new checks that happen that require the MD4 stuff. For more information about that - you can check https://plus.google.com/app/basic/stream/z13cdxpafunnexghb04cc5q4knbyjh4hprg0k
Also, clear cache/dalvik - not that it matters - but I did that - and i found things working. So, after flash, go into /cmupdate folder and flash the latest - it should work (unless i'm just lucky)
_G
Click to expand...
Click to collapse
Thank you so much. Fixed my issue as well. One thing I have to add is that you should do Advanced > Reboot Recovery if you still cannot flash the ROM that gave you the assert problems.
I remember reading that from now on CM10.1 will need the MD4 bootloader or else you get that assert error.
Sent from my SPH-L710 using Tapatalk 2
anyone know if the sprint md4 firmware update will work with c spire's galaxy s3?
You should not flash firmware not intended for your exact device.
CNexus said:
You should not flash firmware not intended for your exact device.
Click to expand...
Click to collapse
What he said. Flashing modems is about the most dangerous thing you can do to your phone
Sent from my SPH-L710 using xda app-developers app
k good to know how would I be able to successfully flash cm10.1 on my c spire gs3?
Fazzl86 said:
k good to know how would I be able to successfully flash cm10.1 on my c spire gs3?
Click to expand...
Click to collapse
Shoot me a pm. I'll set ya straight
Virgin Mobile?
Anyone know if this will work for the Sph-l710 for Virgin Mobile? I'm trying to flash a 4.4 Rom and I'm wanting to try this but it sounds too risky.... Thoughts?
Ok, so I'm getting the same error as OP, trying to flash the CM10.2 Stable (via TWRP) and I understand that I may need to update my firmware or bootloader (are these different?). The only problem is, I may have accidentally installed the OTA 4.3 rom with Knox. I ended up reflashing right away after I realized what I'd done, and the rom I have now (4.3 stock w/ root) doesn't have any knox apps, nothing about knox in device manager, and root/superuser is working just fine.
That said, I'm a bit scared to update my firmware as I've heard stories about Knox working in the background and bricking. Is there a way I can be sure updating my firmware wont brick me? Can someone point me to the latest file I should be flashing here?
Thing in "About Device":
Model:SPH-L710
Version 4.3
Baseband: L710VPUCMK3
Kernel:[email protected] #1
Build: JSS15J.L710VPUCMK3
SE: Permissive
Hardware:L710.14
Thanks in advance. I've gotta get off the stock 4.3, battery life and sluggish behavior are killing me.
DC
I was able to successfuly root and flash a custom ROM onto my phone a few months back using CWM. However, when I try to install a new ROM after all this time, I have come to the realization that my bootloader is outdated.
I've followed the steps in the "if you are unable to install CM10.1" thread, but I still receive the same error (Status 7).
According to the error I get on my phone in CWM, it looks like I need either I747UCDLK3 & I747MVLDLK4. I am sure I will be able to find those on my own, however, going about installing those or updating my current bootloader onto my phone through a Mac computer, I am not positive.
I just need someone to point me in the right direction.
tl;dr Rooted S3 months ago, installed ROM, looking to install CM10.1, error 7, need to update bootloader, not sure how to using Mac.
Correct me if I'm wrong but I think status 7 error means out of date recovery. What version of cwm recovery are you running? The latest one is 6.0.3.1
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
You probably do need to update CWM.
How to do a bootloader: http://forum.xda-developers.com/showthread.php?p=41771519
Remember this is the most difficult thing to do on your phone and you could bork it!
Here are bootloaders: http://forum.xda-developers.com/showthread.php?p=41503727
AGAIN REMEMBER THIS IS SOMETHING THAT CAN BORK YOUR PHONE....
Domoo said:
Correct me if I'm wrong but I think status 7 error means out of date recovery. What version of cwm recovery are you running? The latest one is 6.0.3.1
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nope, I have an up to date CWM (version 6.0.3.1)
oldbbman said:
You probably do need to update CWM.
How to do a bootloader: http://forum.xda-developers.com/showthread.php?p=41771519
Remember this is the most difficult thing to do on your phone and you could bork it!
Here are bootloaders: http://forum.xda-developers.com/showthread.php?p=41503727
AGAIN REMEMBER THIS IS SOMETHING THAT CAN BORK YOUR PHONE....
Click to expand...
Click to collapse
So I just used CWM to update my bootloader to the one that CyanogenMod said you needed for 10.1 (d2att: I747UCDLK3 & I747MVLDLK4) and I still get the same error.
Edit: So, I downloaded Rootchecker, while my "About Phone" says I have the new bootloader I installed, Rootchecker says I have the old one. I believe it is still an issue of the bootloader being out of date but I'm not sure how to update it without Odin.
Edit 2: This (http://d-h.st/yqV) is what I need to update my bootloader to, without using Odin. Is this possible?
kercmerk said:
Nope, I have an up to date CWM (version 6.0.3.1)
So I just used CWM to update my bootloader to the one that CyanogenMod said you needed for 10.1 (d2att: I747UCDLK3 & I747MVLDLK4) and I still get the same error.
Edit: So, I downloaded Rootchecker, while my "About Phone" says I have the new bootloader I installed, Rootchecker says I have the old one. I believe it is still an issue of the bootloader being out of date but I'm not sure how to update it without Odin.
Click to expand...
Click to collapse
See if this thread can help you: http://www.google.com/url?sa=t&rct=j&q=status%207%20installation%20aborted%20galaxy%20s3&source=web&cd=1&cad=rja&ved=0CCsQtwIwAA&url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQW1znjDLe-k&ei=OJLgUdOBO9LKqQHybQ&usg=AFQjCNHgYodJ06avMnRIFYOxGshpLssfIw&bvm=bv.48705608,d.aWM
kercmerk said:
Nope, I have an up to date CWM (version 6.0.3.1)
So I just used CWM to update my bootloader to the one that CyanogenMod said you needed for 10.1 (d2att: I747UCDLK3 & I747MVLDLK4) and I still get the same error.
Edit: So, I downloaded Rootchecker, while my "About Phone" says I have the new bootloader I installed, Rootchecker says I have the old one. I believe it is still an issue of the bootloader being out of date but I'm not sure how to update it without Odin.
Edit 2: This (http://d-h.st/yqV) is what I need to update my bootloader to, without using Odin. Is this possible?
Click to expand...
Click to collapse
You are confusing bootloaders and baseband. Baseband is the modem.
http://forum.xda-developers.com/showthread.php?t=2321310
This week help you update your bootloader
mrhaley30705 said:
You are confusing bootloaders and baseband. Baseband is the modem.
http://forum.xda-developers.com/showthread.php?t=2321310
This week help you update your bootloader
Click to expand...
Click to collapse
Thanks! I actually found that link before I read your post but I'm glad you posted it so others with the same problem have the solution right here.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Here is my dilemma, I recently unlocked and rooted my HTC One M7 for Verizon. I may not have performed a backup but I am oblivious to what the problem may be. I am a newb to rooting and unlocking so please spare me any negative feedback. S-off was successful using firewater. Phone is unlocked in bootloader. Phone was rooted through TWRP v2.7.0.0 and SU. After root was successful I did a factory reset then flashed CM11 with TWRP. CM11 installation was successful except for one problem. My mobile network is not available and a message appears on the screen(You need to refer to the SIM card instruction that came with your phone.) The CM11 file that I installed is: cm-11-20140407-NIGHTLY-m7.zip and after reading that the "Nightly" roms are not the most stable, I then flashed this one: cm-11-20140405-SNAPSHOT-M5-m7.zip. Here is what the Installation looked like in Recovery:
Updating partition details...
Full SELinux support is present.
Formatting Cache using make_ext4fs function.
Wiping data without wiping /data/media ...
Done.
Updating partition details...
Installing ' /sdcard/Download/cm-11-20140405-SN
APSHOT-M5-m7.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Updating partition details..
Successful.
Following the successful flash, I then installed gapps-kk-20131208. Please be detailed in how I can fix this issue. Thanks so much in advance.
Have you ever updated to kk firmware? If your using a kk based rom, you also need kk firmware.
KK firmware
cmlusco said:
Have you ever updated to kk firmware? If your using a kk based rom, you also need kk firmware.
Click to expand...
Click to collapse
I don't understand. What is KK firmware? This may seem like a stupid question but I really don't know.
kk
I am going to feel really stupid if you meant kit kat and if you did then yes I have installed the version for kit kat 4.4.2
Zacb01 said:
I am going to feel really stupid if you meant kit kat and if you did then yes I have installed the version for kit kat 4.4.2
Click to expand...
Click to collapse
No he doesn't mean it has to do with the rom. Firmware is flashed separate from roms. Once you flash it, you don't have to worry about it unless a newer firmware gets released. Go to this thread: http://forum.xda-developers.com/showthread.php?t=2485319 and follow the instructions on the 2nd post. Use 3.11.605.1 NO Boot.img firmware.zip since you'll be doing custom roms.
Mobile service
Crawshayi said:
No he doesn't mean it has to do with the rom. Firmware is flashed separate from roms. Once you flash it, you don't have to worry about it unless a newer firmware gets released. Go to this thread: http://forum.xda-developers.com/showthread.php?t=2485319 and follow the instructions on the 2nd post. Use 3.11.605.1 NO Boot.img firmware.zip since you'll be doing custom roms.
Click to expand...
Click to collapse
I installed this successfully but I still can't make or receive calls. I am wondering if the version of cyanogenmod that I flashed might not be compatible but I did not get a status 7 error when installing. I am also wondering why I got the sim card message when first installing cm11. The version that I installed is stated above on my first post but cyanogenmod has m7 and m7vzw, I can install m7, which I believe is for GSM but I have a Verizon HTC One. When I try to flash the m7vzw version I get the status 7 error code. I tried to do a fix for it but I may have done this incorrectly since I got a status 6 error code. Plz help. I need this phone for work.
You want the m7vzw, the regular m7 is gsm. Status 7 refers to an error in the update script or an incompatible update binary. Does it give a specific error with that status 7? You should also update your twrp to version 2.7.0.4b-santod. http://www.androidfilehost.com/?fid=23329332407584851
Last i heard cm11 is only in preview and data and calls do not work. That may have changed though.
Error
I updated the twrp to v2.7.0.4b-santod, did a factory reset and tried to flash cm11 for m7vzw and was given this mssg...E:Error executing updater binary in zip ' /sdcard/Download/cm-11-20140124-NIGHTLY-M7VZW.ZIP' Setting performance mode OFF. Error flashing zip....etc.....
Why are you flashing an old nightly, and not the one from yesterday? http://download.cyanogenmod.org/?device=m7vzw&type=nightly
I think your issue is that your trying to flash an older nightly with a newer recovery. The newer recoveries have updated binaries that older roms arent compatie with. So either flash a newer nightly, or and older recovery.
If you want a stable rom, i would not use cm11, i would go with cm10.2.
Compatible
The twrp version you recommended and the yesterday's nightly don't work together. Do you have a recovery and a cm11 that are compatible that you can recommend?
Recommendation
cmlusco said:
Why are you flashing an old nightly, and not the one from yesterday? http://download.cyanogenmod.org/?device=m7vzw&type=nightly
I think your issue is that your trying to flash an older nightly with a newer recovery. The newer recoveries have updated binaries that older roms arent compatie with. So either flash a newer nightly, or and older recovery.
If you want a stable rom, i would not use cm11, i would go with cm10.2.
Click to expand...
Click to collapse
I decided to go with cm 10.2.1. Thanks for everything!
Zacb01 said:
The twrp version you recommended and the yesterday's nightly don't work together. Do you have a recovery and a cm11 that are compatible that you can recommend?
Click to expand...
Click to collapse
Hmm thats strange, mabey cm11 just dosent like twrp or something. Glad you got something figured out.
Upgrading to lollipop
Someone should please help on how to upgrade to lollipop 5.0 on HTC m7 complaining of md5 file not found
Hi. I've been trying to install the latest OTA update on my phone. I get the notification on my screen saying it is available to download (The message says: Android 2.3.5 update and system enhancement 5.07.651.1 13.46 MB This new software…) but whenever I accept and choose "Install Now", it restarts and tries to install through the ClockworkMod Recovery v3.0.0.5 then immediately fails displaying the following message:
Finding update package…
Opening update package…
Verifying update package…
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
Any help would be appreciated. Thanks.
Also, here is some information about my phone if it make any difference:
EVT2-3 SHIP S-OFF
HBOOT-2.1.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
Android version:
2.3.5
Baseband version:
2.15.00.11.19
Kernel version:
2.6.35.10-g4b48446
[email protected]#1
Wed Dec 21 16:37:11
Build number:
4.67.651.3 CL2339674 release-keys
Software number:
4.67.651.3
You'll have to install the stock Android system recovery to take the OTA. The best thing to do in your case would be to update your firmware, since it's a version or two behind. If you're happy with the ROM you're using I wouldn't bother with the OTA.
Sent from my HTC device
Magnum_Enforcer said:
You'll have to install the stock Android system recovery to take the OTA. The best thing to do in your case would be to update your firmware, since it's a version or two behind. If you're happy with the ROM you're using I wouldn't bother with the OTA.
Sent from my HTC device
Click to expand...
Click to collapse
Yeah ... umm, I'm not using a ROM. Also, how do I go about updating the firmware? I tried doing so by going into settings under system updates but everything is grayed out.
Xactot said:
Yeah ... umm, I'm not using a ROM. Also, how do I go about updating the firmware? I tried doing so by going into settings under system updates but everything is grayed out.
Click to expand...
Click to collapse
Look at post #2 in the link below. The latest firmware is the first link in that post. Follow the directions in the first post to install via bootloader:
http://themikmik.com/showthread.php?8477-Radio-Update-2-15-00-01-15-2-16-13
Sent from my HTC device
Magnum_Enforcer said:
Look at post #2 in the link below. The latest firmware is the first link in that post. Follow the directions in the first post to install via bootloader:
(Wasn't allowed to quote URL since I'm still a new user LOL)
Sent from my HTC device
Click to expand...
Click to collapse
Ok, so I followed the instructions in the first post to the letter and I'm not sure why but it failed, of course . Specifically speaking, it said:
Installing: /sdcard/PC36IMG_Supersonic_Radio_2.15.00.01.15.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Xactot said:
Ok, so I followed the instructions in the first post to the letter and I'm not sure why but it failed, of course . Specifically speaking, it said:
Installing: /sdcard/PC36IMG_Supersonic_Radio_2.15.00.01.15.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Click to expand...
Click to collapse
You should be following the instructions in the post with the file. That file gets installed through the bootloader, not recovery.
Captain_Throwback said:
You should be following the instructions in the post with the file. That file gets installed through the bootloader, not recovery.
Click to expand...
Click to collapse
Yep, I followed the wrong instructions Woops It worked and now the firmware/baseband is 2.15.00.015. Thanks Captain! So, now that I've updated to the new firmware, how do I update to the newest OTA?
Xactot said:
Yep, I followed the wrong instructions Woops It worked and now the firmware/baseband is 2.15.00.015. Thanks Captain! So, now that I've updated to the new firmware, how do I update to the newest OTA?
Click to expand...
Click to collapse
Flash the 5.07.651.6 stock rooted ROM.
Captain_Throwback said:
Flash the 5.07.651.6 stock rooted ROM.
Click to expand...
Click to collapse
But my phone isn't rooted...
Xactot said:
But my phone isn't rooted...
Click to expand...
Click to collapse
Are you saying you don't have a custom recovery installed? All that's needed to be rooted is to install a custom recovery and then flash a rooted ROM.
Since you already updated your firmware, that's the easiest way to make sure you're on the latest stock ROM.
P.S. You mention having a custom recovery installed (ClockworkMod), which means that while you are in recovery, you have root access (i.e. you are rooted). All you have to do is flash a ROM (though I do recommend upgrading your recovery to smelkusMOD or TWRP).
Captain_Throwback said:
Are you saying you don't have a custom recovery installed? All that's needed to be rooted is to install a custom recovery and then flash a rooted ROM.
Since you already updated your firmware, that's the easiest way to make sure you're on the latest stock ROM.
Click to expand...
Click to collapse
Oh ok thank you. I guess so since I have Clockwork lol. I'm downloading the ROM now. Sorry for not knowing much.
Xactot said:
Oh ok thank you. I guess so since I have Clockwork lol. I'm downloading the ROM now. Sorry for not knowing much.
Click to expand...
Click to collapse
Check out my P.S.
Captain_Throwback said:
Are you saying you don't have a custom recovery installed? All that's needed to be rooted is to install a custom recovery and then flash a rooted ROM.
Since you already updated your firmware, that's the easiest way to make sure you're on the latest stock ROM.
P.S. You mention having a custom recovery installed (ClockworkMod), which means that while you are in recovery, you have root access (i.e. you are rooted). All you have to do is flash a ROM (though I do recommend upgrading your recovery to smelkusMOD or TWRP).
Click to expand...
Click to collapse
I will definitely do so now. Just wondering, with which am I less likely to risk bricking my phone if I ever wanted to flash a custom ROM. Also, I realize that there are quite a few custom ROM's to choose from. Are there any that you'd suggest?
Xactot said:
I will definitely do so now. Just wondering, with which am I less likely to risk bricking my phone if I ever wanted to flash a custom ROM. Also, I realize that there are quite a few custom ROM's to choose from. Are there any that you'd suggest?
Click to expand...
Click to collapse
Neither of those recoveries will brick your phone, and technically the stock rooted ROM is a "custom" ROM.
I don't have a recommendation for you as far as a ROM goes, because everyone is different. The only way to figure out what suits you is to try them all and see what you prefer. The biggest thing to know is that only Gingerbread and Froyo ROMs will be fully functional on this device. While there are ICS, Jellybean and KitKat ROMs for this device, they all suffer similar shortcomings, i.e. no HDMI, no FFC & no WiMAX.
Captain_Throwback said:
Neither of those recoveries will brick your phone, and technically the stock rooted ROM is a "custom" ROM.
I don't have a recommendation for you as far as a ROM goes, because everyone is different. The only way to figure out what suits you is to try them all and see what you prefer. The biggest thing to know is that only Gingerbread and Froyo ROMs will be fully functional on this device. While there are ICS, Jellybean and KitKat ROMs for this device, they all suffer similar shortcomings, i.e. no HDMI, no FFC & no WiMAX.
Click to expand...
Click to collapse
I'll be sticking to Gingerbread ROMs then. Its not worth giving up functions. And I just updated to one of smelkus' Recovery's now. I guess all that's left is flashing the rooted stock ROM. And thank you for suggesting that I switch. Using smelkusMOD is by far so much better and simplistic :laugh: