I can't update my radio on my HTC Evo 3D CMDA. So far I'm on S-on and unlocked with Meanrom 0.8 andbuild number 2.17.651.5 baseband radio 0.97.10.0808.
I have tried RUU back to original stock and no luck.
This has cause dropping of calls alot.
What can i do to fix this issue?
so if am understanding this correctly you are trying to manually update from your settings, correct?
yes but nothing is working.
your ROM probably has the updater function removed from it...
this is for good reason... because you should never accept OTA updates, nor apply them.
if you are looking to update your radio hit the dev section because it has been nicely package in a flashable zip, and you can just flash the radio.
i haven't accept any ota's my rom doesn't have the updater either.
where in the dev section in the flashable radio because i have tried the bootloader way too.
search for a thread created by Freeza.. you'll find it
http://forum.xda-developers.com/showthread.php?t=1443592
If this it i have tried this nothing works. Tried locking the bootloader too.
yes i apologize, TrevE's thread, freeza's post.
post # 131 of that thread bro. should be all set.
okay tried that through the bootloader method didn't work.
i just noticed your first post says you are s-on... are you on Hboot 1.5?
yes hboot 1.50 with s-on and unlocked running meanrom.
pretty sure you have to put a COMPLETELY stock ROM on it first...
the updater package does a number of checks throughout the system to verify it is compatible. runs through /system/app directory, **** like that. so if there are inconsistencies or if something is missing (like bloatware), it will abort the update.
i don't think being rooted will matter, however, but you WILL need to be on a completely stock ROM (pre-update)
what would be the right stock rom pre update?
Thx for all this help
no problem... and i am positive there are some completely stock RUU threads in the dev section. i know xhausx has posted one or two before... look around i know you will find one.
okay i think i found where i need to be. just which one?
http://forum.xda-developers.com/showthread.php?t=1223979&highlight=xhausx
Completely Stock 2.08.651.2 ROM - As is from using the OTA update
Shooter_2.08.651.2_odexed_rooted-signed.zip (MD5: 662790FC8DAF4B86CAFD27AE29E02CFC)Shooter_2.08.651.2_deodexed_rooted-signed.zip (MD5: 77D088F46CC37BF2C2CE9227CED4AC94)
Click to expand...
Click to collapse
that's the one you want. flash that, then try your update again. should do the trick.
okay successfully did the stock rom but when it does the radio update through the bootloader way it does nothing.
I put the PG86IMG.zip on the root of the sdcard and boot to the bootloader and reads it but does nothing to the radio.
mediaman65 said:
okay successfully did the stock rom but when it does the radio update through the bootloader way it does nothing.
I put the PG86IMG.zip on the root of the sdcard and boot to the bootloader and reads it but does nothing to the radio.
Click to expand...
Click to collapse
I'm not quite sure what you mean by it does nothing to the radio?
Sent from EVO 3D using XDA premium
after rebooting and back up it didn't change the radio. Does the phone need to have stock kernel?
everything needs to be stock before you do it.
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
i am almost positive you can do it while rooted, but maybe somebody else can chime in here and verify that.
---------- Post added at 04:13 PM ---------- Previous post was at 04:12 PM ----------
i can't imagine the update script would check for su binaries...
Related
The problem:
-My evo 3d keeps restarting at random times and when it restarts it sometimes dies during the booting up process, and i have to put in a new battery because when it boots up with the old battery it just says its at 10% or less.
this has happened a lot. PLEASE HELP
The specs:
Hboot 1.4
rom: http://forum.xda-developers.com/showthread.php?t=1620318 (Newts one)
please help. this is really irritating me.
I had the very same problem (on RC3). I later remembered that I just upgraded the radio to the latest version. Downgrading back to the radio in the 1.13 RUU (v0530) resolved the issue. My battery life dropped tremendously on the new radio as well.
On a side note, have you tried other ROMs since then? If it's happening in all ROMs it could be an issue there as well.
thefsfempire said:
I had the very same problem (on RC3). I later remembered that I just upgraded the radio to the latest version. Downgrading back to the radio in the 1.13 RUU (v0530) resolved the issue. My battery life dropped tremendously on the new radio as well.
On a side note, have you tried other ROMs since then? If it's happening in all ROMs it could be an issue there as well.
Click to expand...
Click to collapse
it has also done it on Meanrom 4.3,
where do i find the radio you placed that fixed the issue?
jlopez512 said:
it has also done it on Meanrom 4.3,
where do i find the radio you placed that fixed the issue?
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/showthread.php?t=1193101
Under downloads you'll see this: From the 1.13.651.7 OTA/RUU. Click the CDMA link (for 0.97.10.0530). Place this file on the root of your SD card (must be PG86IMG.zip - case sensitive!) and power on phone into bootloader mode (vol down + power). It'll verify and ask you to flash.
Be very careful doing this because you can potentially brick your phone if you don't know what you're doing. There are more detailed instructions at the thread at the beginning of this post. Post back here if you have any issues so I can help you out!
Good luck!
EDIT: If you have access to a computer, follow the "How To Flash" instructions at the link so you can verify the MD5 to make sure the download isn't corrupted.
thefsfempire said:
Here: http://forum.xda-developers.com/showthread.php?t=1193101
Under downloads you'll see this: From the 1.13.651.7 OTA/RUU. Click the CDMA link (for 0.97.10.0530). Place this file on the root of your SD card (must be PG86IMG.zip - case sensitive!) and power on phone into bootloader mode (vol down + power). It'll verify and ask you to flash.
Be very careful doing this because you can potentially brick your phone if you don't know what you're doing. There are more detailed instructions at the thread at the beginning of this post. Post back here if you have any issues so I can help you out!
Good luck!
EDIT: If you have access to a computer, follow the "How To Flash" instructions at the link so you can verify the MD5 to make sure the download isn't corrupted.
Click to expand...
Click to collapse
i have the current radio 0.97.00.0518, flashing this will be safe, right?
also, will it erase my phone data?
The radio version you have is from RUU 1.11 which is one of the oldest ones for this device. I'm curious to know how it's still there unless you've never done an OTA/Hboot downgrade.
It will not erase your handset, only updates the radio software which is a completely separate part of your phone. Just follow the instructions and read through them a few times. I've upgraded/downgraded my radio several times following those instructions.
thefsfempire said:
The radio version you have is from RUU 1.11 which is one of the oldest ones for this device. I'm curious to know how it's still there unless you've never done an OTA/Hboot downgrade.
It will not erase your handset, only updates the radio software which is a completely separate part of your phone. Just follow the instructions and read through them a few times. I've upgraded/downgraded my radio several times following those instructions.
Click to expand...
Click to collapse
my phone was hboot 1.3 when i got it so i used Revolutionary.io method lol
i hope this works, thank you so much!!
jlopez512 said:
my phone was hboot 1.3 when i got it so i used Revolutionary.io method lol
i hope this works, thank you so much!!
Click to expand...
Click to collapse
Good luck to you! Like I said, if you have an issue let me know! *Thread subscribed
thefsfempire said:
Good luck to you! Like I said, if you have an issue let me know! *Thread subscribed
Click to expand...
Click to collapse
my phone just restarted :/
jlopez512 said:
my phone just restarted :/
Click to expand...
Click to collapse
If it restarted after the radio update: flash the 2.17 RUU then downgrade hboot to 1.4 -OR- flash the 2.17 zip and remove the hboot file.
If it restarted during the radio update: (this is bad). The problem could be with a faulty battery. But that is the least of your problems now.
I'll get the link the 2.17 downloads for you. just a sec..
EDIT#1: Here is a link to the PG86IMG.zip for 2.17 containing the latest software and firmware. Delete the HBOOT file from the zip using WinRAR, 7Zip, etc. and rename zip file to PG86IMG.zip, move to root of SD and flash.
http://goo.im/stock/shooter/ruu/PG8...216_NV_NV_spcs_1.42_release_233304_signed.zip
EDIT#2: Here is the link to the actual RUU (run in Windows then do HBOOT downgrade): http://goo.im/stock/shooter/ruu/RUU...216_NV_NV_spcs_1.42_release_233304_signed.exe
---------- Post added at 09:08 PM ---------- Previous post was at 08:43 PM ----------
Just found this while helping someone else. Freeza posted an all-in-one firmware update package for those on Hboot 1.4. This updates you to all the firmware from the 2.17 package without losing root or S-OFF. This does NOT flash a ROM, just updates the firmware.
http://forum.xda-developers.com/showpost.php?p=21374142&postcount=131
thefsfempire said:
If it restarted after the radio update: flash the 2.17 RUU then downgrade hboot to 1.4 -OR- flash the 2.17 zip and remove the hboot file.
If it restarted during the radio update: (this is bad). The problem could be with a faulty battery. But that is the least of your problems now.
I'll get the link the 2.17 downloads for you. just a sec..
EDIT#1: Here is a link to the PG86IMG.zip for 2.17 containing the latest software and firmware. Delete the HBOOT file from the zip using WinRAR, 7Zip, etc. and rename zip file to PG86IMG.zip, move to root of SD and flash.
http://goo.im/stock/shooter/ruu/PG8...216_NV_NV_spcs_1.42_release_233304_signed.zip
EDIT#2: Here is the link to the actual RUU (run in Windows then do HBOOT downgrade): http://goo.im/stock/shooter/ruu/RUU...216_NV_NV_spcs_1.42_release_233304_signed.exe
---------- Post added at 09:08 PM ---------- Previous post was at 08:43 PM ----------
Just found this while helping someone else. Freeza posted an all-in-one firmware update package for those on Hboot 1.4. This updates you to all the firmware from the 2.17 package without losing root or S-OFF. This does NOT flash a ROM, just updates the firmware.
http://forum.xda-developers.com/showpost.php?p=21374142&postcount=131
Click to expand...
Click to collapse
i have another issue. my internet. i used to get error code 67, called sprint, and they refreshed my line and stuff. when i try to turn it on it goes as follows from the settings; "Turning on.." then after a few seconds it says "disconnected"
Ok where are you at right now? Are you still S-OFF? Are you on stock RUU or are you on Newts?
thefsfempire said:
Ok where are you at right now? Are you still S-OFF? Are you on stock RUU or are you on Newts?
Click to expand...
Click to collapse
Same, Newts, S-off
by the way, i flashed what you told me from the second edit. hasnt restarted since :')
I had a similar issue that turned out to be a hardware problem. Had to have sprint get me a new phone. The restarts kept happening more often and the phone was slightly hot. Then it just wouldn't turn on anymore.
Sent from my PG86100 using XDA
jlopez512 said:
Same, Newts, S-off
by the way, i flashed what you told me from the second edit. hasnt restarted since :')
Click to expand...
Click to collapse
Glad to hear your restarts have stopped. As far as internet, that was a known issue with earlier kernels. I have Chad's RLS5 kernel; PM me if you'd like it. It fixes lots of issues with WiFi, 3G connectivity, animations, etc.
Sometimes the random reboots are a hardware problem or a radio problem. I used to get them every once in a while but they stopped ever since I updated the radio and firmware to the 2.17 Fw. Freeza had posted an all-in-one radio/fw update that removed the hboot that could possibly work..
Sent from my PG86100 using XDA
thefsfempire said:
Glad to hear your restarts have stopped. As far as internet, that was a known issue with earlier kernels. I have Chad's RLS5 kernel; PM me if you'd like it. It fixes lots of issues with WiFi, 3G connectivity, animations, etc.
Click to expand...
Click to collapse
yeah sure, hopefully that is all it just needs
mreyesems said:
Sometimes the random reboots are a hardware problem or a radio problem. I used to get them every once in a while but they stopped ever since I updated the radio and firmware to the 2.17 Fw. Freeza had posted an all-in-one radio/fw update that removed the hboot that could possibly work..
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
isn't it the same one form page one, edit two?
I had this problem and the solution was much simpler -- pull your memory card out and see if the reboots stop.
If that's the problem, back up the card to a computer and long format it.
mreyesems said:
Sometimes the random reboots are a hardware problem or a radio problem. I used to get them every once in a while but they stopped ever since I updated the radio and firmware to the 2.17 Fw. Freeza had posted an all-in-one radio/fw update that removed the hboot that could possibly work..
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
I was also having issues with random reboots on my phone. These seemed to only be occurring while the phone was asleep (in my pocket, on a desk, etc...). I had somewhere on the order of 7-8 reboots in a 48 hour period. I also flashed the all-in-one radio/fw update that Freeza posted, and have had zero reboots while sleeping in the 72 hours since. I highly recommend flashing this all-in-one update if you are having issues with reboots while sleeping.
Hey guys,
I was running the latest Viper rom. Every great once in a while the phone would just turn off. I could get it back fine and this happened about 5-6 times. Today the phone got stuck in a boot loop. I figured something went wrong.
I attempted to restore the phone to stock using the RUU thread found here: http://forum.xda-developers.com/showthread.php?t=2152993
I restored it once fine, said it was good. Phone only rebooted over and over. The HTC logo came up 3-4 times then screen went blank. So I flashed again. Same thing, nothing.
Now I had been playing around and think I updated my radio. Now the RUU from that thread above says it cannot upgrade my phone. I can get to fastbook and lock and unlock the bootloader. I did install latest TWRP but it never enters recovery. I had hoped to just install a basic rom from the 2.04 update and be done. But I cannot get into recovery.
I'm stuck and don't know what else to do. Is there and RUU file like the one above for the new 2.04?
I still think something else is wrong with this phone. Somehow doubt VZW will take it back and exchange.
S-ON
Phone displays HBOOT-1.33.0001
RADIO-1.01.01.0110
Any ideas what I can do next please?
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Tersanyus said:
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Click to expand...
Click to collapse
Did you take the verizon update as you mentioned 2.04? If you did you will have to wait a bit yet to root again. Your only option would be stock verizon. Their software update basically closed the previously open window. If not...You HAVE updated radio per the # you posted, not sure if that really matters with regard to recovery. It seems like you have compounded many issues. I would try relocking bootloader and flash stock RUU again. Try to get back to stock verizon. If that's a no go, would try reflashing old radio and try stock ruu. How are you getting to try bootloader/recovery, turning on phone holding down vol button? Last ditch if it's says s-on and locked, I think you would be ok to try for a new phone.
I did not take the OTA from Verizon. I never got any prompt for an update. I did the updates for Viper that turned I think just turned that off.
Getting to bootloader is fine. I can lock it and unlock it fine. I know the RUU only loads if locked. I know recovery can only be installed if unlocked I believe. And yes I do that from vol down plus power button.
If I use newest TWRP recovery just gives a whole bunch of colored lines. If I try 2.4.0.0 I can see TWRP come up briefly then the phone reboots again.
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Tersanyus said:
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Click to expand...
Click to collapse
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
---------- Post added at 10:39 AM ---------- Previous post was at 09:48 AM ----------
rootntootn said:
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
Click to expand...
Click to collapse
Can you get to fastboot? adb can communicate with the phone? Says in red fastboot usb? Also how are you doing RUU, assuming your using executable from your pc? Forgot to ask..
Yes I can get to fastboot fine. I do a "fastboot devices" and it is read. adb doesn't seem to do anything though. The RUU is the .exe I found.
For the cid I did the old one so mine reads all 1's. I didn't think I could so the new cid as I cannot boot into Android at all.
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
rootntootn said:
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Click to expand...
Click to collapse
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
BTW There was nothing wrong with your phone, it's just that when you restored, you needed to flash the boot.img from your rom that you restored. It was most likely a kernel issue that we could correct with viper.
It sounds like you just need to install the matching rom and boot.img. If you're s off, just fastboot flash the boot.img for whatever rom you currently have installed. For the OTA update, you can install the radios without an RUU if you're s off.
I ran for several hours and several reboots on the RUU .exe file. When I downloaded a custom rom from http://forum.xda-developers.com/showthread.php?t=2150262 - That fan fine for an hour or so. Then boot loop over and over again. Thankfully I made a backup in twrp. I restored that and all is well.
I can't stand this factory rom, the part that really annoys me, besides the VZW bloat, is the recent apps button. For over a year with other HTC's I am used to making that the menu button. Had that in the custom rom.
So it looks like that rebooting loop just means I need to fastboot the boot.img?
I go back to the rom I linked about and fastboot the boot.img. I really liked viper rom but am going to stick to stock that is rooted and debloated.
My cid is all 1's since I did that before all this OTA came out. I did that about 3 weeks ago the day I got the phone.
Thanks for the tips. I'll let you know what happens when I go back to the rom above.
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Sorry about the 2's info but read that the older cid apk would no longer work (from thread below) and myself put on the new one which yields the all 2's. Bottom line, glad you made progress, hopefully problem resolved
http://forum.xda-developers.com/showthread.php?t=2109862
I have all the above, can I do the OTA and still get root? I just want to have the latest stock version for a while, but didn't know if I can just do the OTA. Thanks for the help.
GHII said:
I have all the above, can I do the OTA and still get root? I just want to have the latest stock version for a while, but didn't know if I can just do the OTA. Thanks for the help.
Click to expand...
Click to collapse
If you are S-Off like you say you are then you can flash the ENG-Hboot then restore with the RUU take the update and reflash the recovery. Then I just flash a superuser.zip and your all set. Make sure you backup you files to a PC.
Edit:
You have to have the stock recovery to take the OTA and the only way I know to get that is installing the RUU.
---------- Post added at 09:04 AM ---------- Previous post was at 09:02 AM ----------
Be SURE you are S-Off because if you aren't you WILL be screwed.
If you are s-off, with a custom recovery, you can also just flash the radios in fastboot, and flash a 2.04 rom that is stock, except for having root. Delete the root if you don't like it
http://forum.xda-developers.com/showpost.php?p=38015322&postcount=1
GHII said:
I have all the above, can I do the OTA and still get root? I just want to have the latest stock version for a while, but didn't know if I can just do the OTA. Thanks for the help.
Click to expand...
Click to collapse
Same and this is what I did. Read through the whole thread http://forum.xda-developers.com/showthread.php?t=2149951
Ok i am running a stock tmobile rom 1.27.531.11 with s-off , rooted and custom recovery.
I flash the stock recovery and try to install the update it says
finding update package
opening update package
virifying update
installing update
waring: no file_contextsVerifying current system
assert failed: apply_patch_check(/system/bin/app_process",
after the , is to long numbers looks like a checksum mismatch to me but im unsure. I would like to know how to i fix this?
xile6 said:
Ok i am running a stock tmobile rom 1.27.531.11 with s-off , rooted and custom recovery.
I flash the stock recovery and try to install the update it says
finding update package
opening update package
virifying update
installing update
waring: no file_contextsVerifying current system
assert failed: apply_patch_check(/system/bin/app_process",
after the , is to long numbers looks like a checksum mismatch to me but im unsure. I would like to know how to i fix this?
Click to expand...
Click to collapse
I was running a custom ROM with custom recovery, s-off, rooted and my cid was 11111111(? how many 1's is that) . anyways what i did i just flashed a stock RUU and it went through fine then from there i just did a normal update through the phone settings.
---------- Post added at 07:58 PM ---------- Previous post was at 07:55 PM ----------
i might wanna add that after the update i'm still s-off with super cid but it did update my hboot to 1.55.
---------- Post added at 08:01 PM ---------- Previous post was at 07:58 PM ----------
i might wanna add that after the update i'm still s-off with super cid but it did update my hboot to 1.55.
compta5 said:
I was running a custom ROM with custom recovery, s-off, rooted and my cid was 11111111(? how many 1's is that) . anyways what i did i just flashed a stock RUU and it went through fine then from there i just did a normal update through the phone settings.
---------- Post added at 07:58 PM ---------- Previous post was at 07:55 PM ----------
i might wanna add that after the update i'm still s-off with super cid but it did update my hboot to 1.55.
---------- Post added at 08:01 PM ---------- Previous post was at 07:58 PM ----------
i might wanna add that after the update i'm still s-off with super cid but it did update my hboot to 1.55.
Click to expand...
Click to collapse
thanx for the help.
It probably dont mater anymore now tho. I ended up soft brciking the phone, (son was jumpping around and i eneded up hiting factory reset)
I think im going to im going to end up losing all me stuff :crying:
but im doing the ruu now and i will see what happens. Hopefully i can recover some of my pictures and stuff.
And i did do a nano backup but like a dumba.. i didnt transfer it to the laptop. Also forgot that the data/system is one and no sd card
I give from now on ill do weekly data backups.
I have same problem.
Flashed stock recovery , but still same...
I have unlocked bootloader and s-off (with t-mob cid, ect)
What to do? S-on? Don't really think it causes problem
tried S-on , but still same
"warning no file_contexts verifying current system" ...
jkjambo said:
I have same problem.
Flashed stock recovery , but still same...
I have unlocked bootloader and s-off (with t-mob cid, ect)
What to do? S-on? Don't really think it causes problem
Click to expand...
Click to collapse
Dont flash stock recovery. You have to flash the 1.27 RUU which will flash stock hboot, recovery, and ROM.
blackangst said:
Dont flash stock recovery. You have to flash the 1.27 RUU which will flash stock hboot, recovery, and ROM.
Click to expand...
Click to collapse
i have stock recovery and stock rom , so i'll flash now just hboot . if this will not help me , then i'll try whole Ruu (i'm too lazy to download and install that )
don't know why , but i couldn't install htboot , so donwloading 1.27.531.8 (Downgreader) ...
I have an s-off'd / unlocked / rooted / TWRP (recovery) rezound that is working.
Want to sell it and buyer requests factory reset. I can't find the RUU files anywhere.
the posted articles point to androidpolice.com and that source return's a 404 not found?
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
Click to expand...
Click to collapse
Does anyone have an RUU I can use to reset to stock and then reset the flag to be s-on?
Thanks
I found: http://forum.xda-developers.com/showthread.php?t=2509770
which pointed me to 2 PH98IMG.zip files (which I hoped were the ICS and
global radio ones).
Can anyone confirm for that I just need to apply the zips with fastboot RUUmode &
fastboot flash zip, then reset the s-off flag?
I never tested the procedure with the Rezound but I once did it with an EVO 3D that was Unlocked and S-OFF, and it worked juste fine (after flashing it said Locked & S-OFF). However in the end I wasn't able to sell it so I didn't set it back to S-ON, I don't know how to do that.
The official Global update was only available as an OTA patch so you have to apply the official ICS RUU (3.14.605.12, radios 1.22) and then the official Global OTA (4.05.605.14, radios 2.23).
There was a v4.03 RUU with Global radios 2.22 floating around for a long time before the 4.05 was released but it was unofficial so I wouldn't flash that one.
Here are some more. http://androidruu.com/?developer=Vigor
My question would be, why bother? This device will never get another firmware update, just go to the Dev section and find the latest stock/rooted image and flash... GTG
---------- Post added at 10:42 AM ---------- Previous post was at 10:31 AM ----------
acejavelin said:
My question would be, why bother? This device will never get another firmware update, just go to the Dev section and find the latest stock/rooted image and flash... GTG
Click to expand...
Click to collapse
Maybe the buyer wants pure stock without root?
I also find that ridiculous, ICS is so old now that it would be better to put something like CM10.2 on it (so the camcorder works) and unroot it if the buyer doesn't want root (some people dislike it because they don't want to have to deal with apps asking su rights and the like).