Disclaimer: This is simply a thread to try and post viable solutions to help people struggling with 4G. I am not responsible for you bricking and/or damaging your phone. However I have personally tried all these methods (except the last one) successfully and have not had any ill effects from them.
Ok so I am going to post this thread as a solution thread for all the people that have been struggling with 4G (like myself) and have found solutions to restoring 4G permanently.
IMPORTANT: YOU MUST BE S-OFF TO ACCOMPLISH MOST IF NOT ALL OF THE SOLUTIONS LISTED HERE.
Update!!!!!!!
After starting the thread on possible solutions I found the simplest one that I have now tried multiple times on all ruus and the ics leak and it works on ALL OF THEM. Funny thing is that it is the simplest solution of all... It has been reported a couple of times now by different users I just tested it out intensively on all combinations. The steps are:
1. Relock your phone (Optional - I am in a habit of doing this step regardless due to an RUU failing on me while being unlocked)
2. Use a ruu to reformat your phone and restore
3. Then reboot into bootloader and DO A FACTORY RESET.
4. Reboot and enjoy full 4g
Have no idea why it never occurred to me to do this but I can verify no 4g drops on any combination of rom I have tried after those steps are completed... As long as you don't DOWN MIX AND MATCH FIRMWARE AND RADIOS. I have gone 6 hours straight no drop all 4g. Try and report back...
Thanks to whoever posted the find
___________________________________________________
Scenario # 1 - You have had perfect 4G service even after you performed s-off until you flashed this (http://forum.xda-developers.com/showthread.php?t=1614366) or this (http://forum.xda-developers.com/showthread.php?t=1612555) and now are losing 4G permanently and/or fluctuating. Here is two solutions that I have found worked so far... both have been tested to work on my phone however every phone is different so I cant speak for everyone.
Note: This solution is assuming that, like me, you have tried every RUU and hard flash method available and still are experiencing drops in your 4G
I re-locked my phone prior to performing any RUU's and/or starting any of these solutions
Solution # 1 - Download this GB RUU (http://www.mediafire.com/?v6d2kxspn9t14) and run the exe on a windows pc to perform a full restore (on a windows 7 64bit system I had to run it in compatibility mode to make it work - Windows XP service pack 2 & run as administrator). After this boot up the phone and verify that your 4G is still dropping. Proceed to unlock your boot-loader and flash a custom recovery (custom recovery is optional but it is a step i completed before continuing the process that worked for me). Then download this (http://forum.xda-developers.com/attachment.php?attachmentid=1017864&d=1335048263) and flash it in the Hboot. It will install the engineering version of Hboot for GB. Reboot phone back to bootloader and verify that the Hboot was flashed successively. After reboot your phone normally and verify that the 4G drops have been fixed.
On this solution I have been running 5 hours without a single drop so far. I feel that the Hboot directly related to s-off somehow affects the 4G radio. Just a hunch...
Solution # 2 - Same scenario as above but you want to go to the ICS leak instead of the GB RUU. I have found two different methods for this solution that works just as well as the one above.... so far.
Method a) Download GB RUU (http://www.mediafire.com/?v6d2kxspn9t14) and install like described above. Then download the ISC leak (http://bit.ly/IzGIFF) and flash it from Hboot. After these two things have been completed flash the official modded s-off Hboot (http://dl.dropbox.com/u/14779955/jb_hboot.zip) and reboot bootloader to verify that it is indeed the new Hboot. Then restart the phone and verify the 4G drops have been fixed. If 4G still drops then download the GB radios (posted below) and extract them into a folder containing your fastboot files on your computer. Boot into fastboot on your phone and type these commands from a command window ran from inside your folder :
fastboot erase mdm9k
fastboot erase radio
fastboot flash mdm9k mdm9k.img
fastboot flash radio radio.img
Verify that all four steps go successively and then reboot your phone. Verify 4G does not drop
Note: Using the last portion of this process I now have no drops on ICS.
THIS NEXT METHOD WAS TESTED BY ANOTHER PERSON AND VERIFIED THAT IT WORKED TO FIX 4G.
Method b) Download old GB RUU (http://www.mediafire.com/?24rwfff4nfe1j) and install like described above. Then download the ISC leak (http://bit.ly/IzGIFF) and flash it from Hboot. Then flash the 2.01.605.11 radios to replace the ICS ones (the links to the radio packages are listed below). Reboot to Hboot and verify that the radios are now the GB ones. Reboot and verify that 4G drops have been fixed.
These are all the solutions I have so far. Please let me know your results as well as any additional methods you find to fixing 4G drops and I will update the OP.
Happy 4G fixing
Here are the radio packages (thanks to flyhalf 205 for re-posting) to attempt solution 2 method b which is verified by him
GB Radio:http://www.mediafire.com/?6s86jwmers710o5
ICS Radio: http://www.mediafire.com/?xvu8g3ucfwzit48
Credits : graymonkey44 (s-off files), uToTMeH8 (RUU files), con247/jcase (engineering Hboot for GB), lllboredlll (used his link for the ICS leak), Flyhalf205 (for posting Solution 2 Method b and verifying), nolimitzr2 (for originally posting radio packages), jefffeely (for posting the hard erase & write method to this thread), and anyone else im forgetting.
If this helps in any way feel free to throw a thanks my way
Nice. Solution 2 Method b (aka the Flyhalf Method, ) is still working
GB Radio:http://www.mediafire.com/?6s86jwmers710o5
ICS Radio: http://www.mediafire.com/?xvu8g3ucfwzit48
Downloading everything again here at work and will give solution #1 a try and report back. None of the other solutions have worked for me. I have tried them already.
Thanks for posting this!
Flyhalf205 said:
Nice. Solution 2 Method b (aka the Flyhalf Method, ) is still working
GB Radio:http://www.mediafire.com/?6s86jwmers710o5
ICS Radio: http://www.mediafire.com/?xvu8g3ucfwzit48
Click to expand...
Click to collapse
Just added you to the credits bro... sorry i missed you the first time. And i threw a thanks at ya
dajmanjt said:
Just added you to the credits bro... sorry i missed you the first time. And i threw a thanks at ya
Click to expand...
Click to collapse
ha Thanks
I used solution #1, and I have 4G back, but it drops out every 4-5 minutes, but then comes back, and drops out again at 4-5 minutes.
jskolm said:
I used solution #1, and I have 4G back, but it drops out every 4-5 minutes, but then comes back, and drops out again at 4-5 minutes.
Click to expand...
Click to collapse
Thanks for the feedback... will you be attempting one of the other solutions?
dajmanjt said:
Thanks for the feedback... will you be attempting one of the other solutions?
Click to expand...
Click to collapse
Like you I have been trying for 2 days also. I have tried the other solutions already, and they didn't work for me either. This is the most stable I have gotten it so far though. I may have to just deal with it at this point.
I did:
Extract the files in the GB 2x radio zip into your fastboot directory.
fastboot erase mdm9k
fastboot erase radio
fastboot flash mdm9k mdm9k.img
fastboot flash radio radio.img
This was recommended in another thread and worked great for me
jskolm said:
Like you I have been trying for 2 days also. I have tried the other solutions already, and they didn't work for me either. This is the most stable I have gotten it so far though. I may have to just deal with it at this point.
Click to expand...
Click to collapse
You GB or ICS? Try doing the ICS way. Flash ICS leak and then the GB radios.
jefffeely said:
I did:
Extract the files in the GB 2x radio zip into your fastboot directory.
fastboot erase mdm9k
fastboot erase radio
fastboot flash mdm9k mdm9k.img
fastboot flash radio radio.img
This was recommended in another thread and worked great for me
Click to expand...
Click to collapse
Thanks for the feedback. I can add this to the OP... what were you on GB or ICS?
Flyhalf205 said:
You GB or ICS? Try doing the ICS way. Flash ICS leak and then the GB radios.
Click to expand...
Click to collapse
I have tried that. I get the similar results. I get 4G back and everything seems ok, but then it drops out for a while. But it will come back to 3G then eventually 4G, then start all over again for me.
dajmanjt. What solution are you on right now that has stable 4G and no drops?
Flyhalf205 said:
dajmanjt. What solution are you on right now that has stable 4G and no drops?
Click to expand...
Click to collapse
I was on solution a and was good as far as i could tell. But i want ICS. So now I am on solution b again and trying to verify the stable factor of it and/or how to improve stability. If i have more dropouts i will prob try to verify the hard erase of the radios and individually flash them back solution that was posted above....
Are you still golden on your solution?
dajmanjt said:
Are you still golden on your solution?
Click to expand...
Click to collapse
Yeah I am. So far I haven't had any drop outs so go for ICS man. Maybe my solution can be your solution haha
dajmanjt said:
I was on solution a and was good as far as i could tell. But i want ICS. So now I am on solution b again and trying to verify the stable factor of it and/or how to improve stability. If i have more dropouts i will prob try to verify the hard erase of the radios and individually flash them back solution that was posted above....
Are you still golden on your solution?
Click to expand...
Click to collapse
I'm on ICS, with ENG HBOOT 2.11, GB OTA Radios, and ICS 4.0.1 from the original ICS Leak. 4G works, 3G works, bluetooth works, wifi works, gps works, sms and mms work, etc. Zero problems here.
Flyhalf205 said:
Yeah I am. So far I haven't had any drop outs so go for ICS man. Maybe my solution can be your solution haha
Click to expand...
Click to collapse
I am flashing the ICS RUU right now to try your solution out again also.
Flyhalf205 said:
Yeah I am. So far I haven't had any drop outs so go for ICS man. Maybe my solution can be your solution haha
Click to expand...
Click to collapse
Ok so i have verified that i had some drops on solution 2a so i then booted into boot-loader and individually erased the lte and radio and manually flashed them back (GB lte & radio from latest OTA). And voila no more drops. As of the last 30 min that is.... so i will update that in the OP. I think basically it is doing the same thing as if i had done solution 2b but manually erasing to ensure the partition is totally erased. Cheers to progress
dajmanjt said:
Ok so i have verified that i had some drops on solution 2a so i then booted into boot-loader and individually erased the lte and radio and manually flashed them back (GB lte & radio from latest OTA). And voila no more drops. As of the last 30 min that is.... so i will update that in the OP. I think basically it is doing the same thing as if i had done solution 2b but manually erasing to ensure the partition is totally erased. Cheers to progress
Click to expand...
Click to collapse
Glad to hear. Which HBOOT you using. I have flashed both 2.21 and the modified 2.21 and both work with the GB Radio.
Flyhalf205 said:
Glad to hear. Which HBOOT you using. I have flashed both 2.21 and the modified 2.21 and both work with the GB Radio.
Click to expand...
Click to collapse
I am using the s-off modded one atm.... glad to hear they both work like a charm
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.
I've been (at least trying to) patiently wait for Deck to post full install instructions for CM10 but the CM10 op is still bare as bones. Has anyone else posted an install guide or instructions yet?
I'm currently rooted with RegawMod and running MeanRom 2.1 and it's really terribly laggy and frustrating, I can't wait any longer for CM10. Do I need S-off to install CM10 or do I just wipe, flash, and go?
Thanks for any help or links!
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Its been my daily for 3 weeks.
Sent from my EVO using Tapatalk 2
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Sent from my EVO using xda app-developers app
corcgaigh said:
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Click to expand...
Click to collapse
Dont use flash image gui unless you know how to do it manually through fastboot. You are just asking for issues
Instructions:
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Rxpert said:
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Click to expand...
Click to collapse
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Yes hboot 1.12 allows for access to the boot partition
Also luuuuucckkyyyyyy...
EdhyMonker said:
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Click to expand...
Click to collapse
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Bit off topic, anyone check to see if you can push a new splash, right now I'm too lazy to start my PC just to fastboot one measly splash
Rxpert said:
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Click to expand...
Click to collapse
The S-OFF guide was way over my head so I just let it be. If there's not a real good reason for doing it, and I can still run CM10, then I'd rather not.
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
om4 said:
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
Click to expand...
Click to collapse
No, S-ON people with 1.12 H-boot can flash radios and firmware from recovery. They can do whatever they please in recovery just like S-OFF. S-OFF users can flash things from bootloader and even change the appearance of their h-boot to read S-ON and **locked** even though they are S-OFF
To the OP, this is the best rooting guide I've seen. It really explains everything step by step. http://androidforums.com/evo-4g-lte...panda-s-htc-dev-ltevo-root-dummies-guide.html Its recommended to have Linux at least bootable, because in the small chance the phone gets bricked... the unbricker program requires linux.
I ran it in windows before the unbricker was available, no issues here
You basically just hook the phone up to it and run the program like you do for most other root programs. All 1-click
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
om4 said:
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
Click to expand...
Click to collapse
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
You don't have to flash any firmware updates. There are a few users with issues although they may be related to the ROM update and not necessarily the firmware included. I haven't really checked since I'm s on. If you want to update the radios there's an update zip here somewhere, be sure to read through everything carefully. Radios are more risky then every day flashing
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
EdhyMonker said:
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
Click to expand...
Click to collapse
ive only ever seen this issue with cyanogenmod and the old htc vogues, still great phones for what they were
EdhyMonker said:
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
Click to expand...
Click to collapse
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Rxpert said:
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Click to expand...
Click to collapse
Thanks, but I tried this and it says "no image or wrong image" when trying to flash the PJ75IMG.zip file.
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
joebarkho said:
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
Click to expand...
Click to collapse
I thought that might've been the issue so I tried it both ways, didn't work either way. I'll take another shot at it tomorrow.
Hello,
I installed the AOKP "adrenalized" ROM yesterday (http://forum.xda-developers.com/showthread.php?t=1884085), and while I initially had a great experience with it, it seems several things have started to go wrong for me.
The most pressing issue is that I can no longer make any phone calls... within the first 12 hours or so of having the ROM, this was not an issue (I received a phone call), but all of a sudden, I no longer have any mobile signal (either 4g or 3g) whatsoever, and if I try to make a call, it says "Mobile network not available." I tried searching online for help with this, but I could not find anything.
The other two issues (these are not as pressing as my inability to make/receive calls) are a persistent error that I have a "Damaged SD card" and I can't access my internal storage when I hook up my phone to my PC. I did find someone else on another phone having an issue with AOKP/damaged sd card, but the fix suggested (editing a file called vold.fstab) did not work (the line to edit in the file was not present in my file).
Sorry for the long post - I am fairly inexperienced when it comes to this stuff, but any help is greatly appreciated.
rocketman13 said:
Hello,
I installed the AOKP "adrenalized" ROM yesterday (http://forum.xda-developers.com/showthread.php?t=1884085), and while I initially had a great experience with it, it seems several things have started to go wrong for me.
The most pressing issue is that I can no longer make any phone calls... within the first 12 hours or so of having the ROM, this was not an issue (I received a phone call), but all of a sudden, I no longer have any mobile signal (either 4g or 3g) whatsoever, and if I try to make a call, it says "Mobile network not available." I tried searching online for help with this, but I could not find anything.
The other two issues (these are not as pressing as my inability to make/receive calls) are a persistent error that I have a "Damaged SD card" and I can't access my internal storage when I hook up my phone to my PC. I did find someone else on another phone having an issue with AOKP/damaged sd card, but the fix suggested (editing a file called vold.fstab) did not work (the line to edit in the file was not present in my file).
Sorry for the long post - I am fairly inexperienced when it comes to this stuff, but any help is greatly appreciated.
Click to expand...
Click to collapse
Need a little bit more info for me to be helpful. S-on or off? Did you verify MD5 before installing? What rom did you come from? Latest firmware? Anything you can provide about your setup would be useful. TBH, it sounds like you had a bad download, so I'd try to re-download and verify MD5 before you install.
iamwalterwhite said:
Need a little bit more info for me to be helpful. S-on or off? Did you verify MD5 before installing? What rom did you come from? Latest firmware? Anything you can provide about your setup would be useful. TBH, it sounds like you had a bad download, so I'd try to re-download and verify MD5 before you install.
Click to expand...
Click to collapse
Thanks for your reply, iamwalterwhite. Here is the relevant information:
S-On
Previous ROM before AOKP: Scott's CleanROM Pro 4.5
Firmware: Android Version 4.0.4
Baseband version: 0.95.00.1118r, 0.95.00.1223r
Unfortunately, I did not check the MD5 before I installed because I thought the risk of not doing it would be low. Apparently, I was wrong! Given that information, do you think it is still worth verifying MD5 and re-installing AOKP? Thanks.
You are still on gb firmware. Flashing the old firmware patch may help.
Sent from my Kindle Fire using Tapatalk 2
pwned3 said:
You are still on gb firmware. Flashing the old firmware patch may help.
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Wow, really? How can you tell? I thought Android version 4.0.4 was Ice Cream Sandwich, and I vaguely remember flashing a GB firmware patch when I first installed Scott's CleanROM 4.5, but my memory could be a bit fuzzy... should I just reboot to AmonRa recovery and flash it? Thanks for your help!
We can tell based off of your baseband version. Honestly, I think you should re-lock then flash the newest RUU. It will probably clear up your problem. If you'd still like, I can tell you how to check an MD5, but I think it's best if you flash that RUU. It's worth it, our radios have gone through multiple updates since the version that you have.
iamwalterwhite said:
We can tell based off of your baseband version. Honestly, I think you should re-lock then flash the newest RUU. It will probably clear up your problem. If you'd still like, I can tell you how to check an MD5, but I think it's best if you flash that RUU. It's worth it, our radios have gone through multiple updates since the version that you have.
Click to expand...
Click to collapse
Thanks, iamwalterwhite. I did some searching and found the latest RUU for the Rezound as 4.03.605.1 (I found it on Android Police, but I can't post the link since I'm a new user). However, it seems I am supposed to check the MD5 for that file as well.
Assuming that is the latest RUU though, then the steps I'd follow are: download the RUU/verify MD5, name it as PH98IMG.zip in my SDcard root, re-lock my bootloader, and finally reboot to AmonRa recovery to flash this RUU.
Are there any steps I am missing? Thanks again for your help... it is much appreciated.
You need to install in hboot not recovery. Running this will also write over your recovery. I suggest having the newest amon ra downloaded so you can unlock and flash it after the ruu
Sent from my Rezound using Xparent SkyBlue Tapatalk 2
rocketman13 said:
Thanks, iamwalterwhite. I did some searching and found the latest RUU for the Rezound as 4.03.605.1 (I found it on Android Police, but I can't post the link since I'm a new user). However, it seems I am supposed to check the MD5 for that file as well.
Assuming that is the latest RUU though, then the steps I'd follow are: download the RUU/verify MD5, name it as PH98IMG.zip in my SDcard root, re-lock my bootloader, and finally reboot to AmonRa recovery to flash this RUU.
Are there any steps I am missing? Thanks again for your help... it is much appreciated.
Click to expand...
Click to collapse
Have you set up an ADB folder? If so, place the RUU in your adb folder then execute this command in a command prompt:
cd c:\(your adb folder name)
You should then get a screen that looks like this:
c:\(your adb folder name)>
Then type: md5sums (ruu name).zip
Should look like this:
c:\(adb folder name)> md5sums (ruu name).zip
Your steps are mostly correct, however, you must flash the PH98IMG.zip via hboot. In fact, you won't be able to get to your recovery if you boot into your bootloader with the .zip on your sd card.
By the way, don't use the .1 RUU. Follow this link: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ This is the .2 (seems like a hopelessly miniscule difference), but it's the most current.
Edit: Since you are s-on, you will need to unlock via HTCDEV after the RUU. Then you can go about installing AR 3.15 the same way as you did before. If you plan on going s-off, you might want to consider doing that before running the RUU. I know it's a lot of information, and a lot to sift through (not to mention the many different ways to do do things) but going s-off makes it much more simple.
iamwalterwhite said:
Have you set up an ADB folder? If so, place the RUU in your adb folder then execute this command in a command prompt:
cd c:\(your adb folder name)
You should then get a screen that looks like this:
c:\(your adb folder name)>
Then type: md5sums (ruu name).zip
Should look like this:
c:\(adb folder name)> md5sums (ruu name).zip
Your steps are mostly correct, however, you must flash the PH98IMG.zip via hboot. In fact, you won't be able to get to your recovery if you boot into your bootloader with the .zip on your sd card.
By the way, don't use the .1 RUU. Follow this link: This is the .2 (seems like a hopelessly miniscule difference), but it's the most current.
Edit: Since you are s-on, you will need to unlock via HTCDEV after the RUU. Then you can go about installing AR 3.15 the same way as you did before. If you plan on going s-off, you might want to consider doing that before running the RUU. I know it's a lot of information, and a lot to sift through (not to mention the many different ways to do do things) but going s-off makes it much more simple.
Click to expand...
Click to collapse
A HUGE thank you to both of you!! I restored my phone to the .2 RUU, and I now have a working phone and proper access to my internal storage. Unfortunately iamwalterwhite, I didn't see your message until after I finished installing the RUU, so I am still on S-On, but I am rooted. Do you know if I could still get to S-Off from this point (i.e. after installing RUU on my phone)?
Also, do you think it is ok to try re-installing the AOKP ROM that previously gave me problems (I verified the MD5), or should I hold off/try another ROM?
Again, thanks to you both, iamwalterwhite and pwned3. I was pretty lost otherwise.
rocketman13 said:
A HUGE thank you to both of you!! I restored my phone to the .2 RUU, and I now have a working phone and proper access to my internal storage. Unfortunately iamwalterwhite, I didn't see your message until after I finished installing the RUU, so I am still on S-On, but I am rooted. Do you know if I could still get to S-Off from this point (i.e. after installing RUU on my phone)?
Also, do you think it is ok to try re-installing the AOKP ROM that previously gave me problems (I verified the MD5), or should I hold off/try another ROM?
Again, thanks to you both, iamwalterwhite and pwned3. I was pretty lost otherwise.
Click to expand...
Click to collapse
Sorry to post again, but I just had an issue arise that has been pestering me for a while. Anytime my GPS is on, my phone shuts off and reboots within a minute or so... I know Rezound folks had this problem a while back due to the Google Maps update, but I've been having this for a while, even when I was on Scott's CleanROM and with fixed Maps. Now that I am on RUU (rooted), I hoped this problem would go away because I use Navigation a lot... but unfortunately, it is still here. I currently have Maps 6.12.0.
Does anyone have any thoughts/suggestions? Thanks.
rocketman13 said:
A HUGE thank you to both of you!! I restored my phone to the .2 RUU, and I now have a working phone and proper access to my internal storage. Unfortunately iamwalterwhite, I didn't see your message until after I finished installing the RUU, so I am still on S-On, but I am rooted. Do you know if I could still get to S-Off from this point (i.e. after installing RUU on my phone)?
Also, do you think it is ok to try re-installing the AOKP ROM that previously gave me problems (I verified the MD5), or should I hold off/try another ROM?
Again, thanks to you both, iamwalterwhite and pwned3. I was pretty lost otherwise.
Click to expand...
Click to collapse
You're welcome, that's why they call this here a community. If I was you, I wouldn't try to s-off right now. The reason I say that is because the juopunutbear method to s-off uses a different hboot (I believe the jbear hboot is .25 while the RUU is .27). That hboot was compatible with the ICS ota pre-global. You may have to wait until they get an update do to it. At this point, you will only have to worry about extracting the boot.img for roms that aren't global based (aokp being an example), but that should be a small annoyance. Much smaller, than say, bricking your phone!
iamwalterwhite said:
You're welcome, that's why they call this here a community. If I was you, I wouldn't try to s-off right now. The reason I say that is because the juopunutbear method to s-off uses a different hboot (I believe the jbear hboot is .25 while the RUU is .27). That hboot was compatible with the ICS ota pre-global. You may have to wait until they get an update do to it. At this point, you will only have to worry about extracting the boot.img for roms that aren't global based (aokp being an example), but that should be a small annoyance. Much smaller, than say, bricking your phone!
Click to expand...
Click to collapse
A number of people have been successful with S-OFF on hboot 2.27 using the .5 ControlBear. There seem to be no issues with it at all.
shrike1978 said:
A number of people have been successful with S-OFF on hboot 2.27 using the .5 ControlBear. There seem to be no issues with it at all.
Click to expand...
Click to collapse
Just found this thread: http://forum.xda-developers.com/showthread.php?t=1883924&page=2 It looks like there have been a few successes wit s-off even after the .2 RUU. Thanks Shrike!
iamwalterwhite said:
Just found this thread: It looks like there have been a few successes wit s-off even after the .2 RUU. Thanks Shrike!
Click to expand...
Click to collapse
Oh man, I'm not sure I'm brave enough to do the infamous "wire trick" just yet... but I will keep that link as a reference once I feel more confident.
Also, sorry to bother you again, but did any of you happen to see my previous post about my GPS:
rocketman13 said:
Sorry to post again, but I just had an issue arise that has been pestering me for a while. Anytime my GPS is on, my phone shuts off and reboots within a minute or so... I know Rezound folks had this problem a while back due to the Google Maps update, but I've been having this for a while, even when I was on Scott's CleanROM and with fixed Maps. Now that I am on RUU (rooted), I hoped this problem would go away because I use Navigation a lot... but unfortunately, it is still here. I currently have Maps 6.12.0.
Does anyone have any thoughts/suggestions? Thanks.
Click to expand...
Click to collapse
As always, thank you very much!!
rocketman13 said:
Oh man, I'm not sure I'm brave enough to do the infamous "wire trick" just yet... but I will keep that link as a reference once I feel more confident.
Also, sorry to bother you again, but did any of you happen to see my previous post about my GPS:
As always, thank you very much!!
Click to expand...
Click to collapse
I saw that post abou GPS, but I'm not familiar with that at all. The only thing that I recall was the problem with the upgrade in google maps. Apophis has a thread over in General where he lists his g-talk (along with some other users). He might be able to help.
iamwalterwhite said:
I saw that post abou GPS, but I'm not familiar with that at all. The only thing that I recall was the problem with the upgrade in google maps. Apophis has a thread over in General where he lists his g-talk (along with some other users). He might be able to help.
Click to expand...
Click to collapse
Ok, great! I'll see if I can ask about the GPS. Thanks for your help!
I have been working on this phone for hours, and hours. and it has been one of the most frustrating phones i have ever worked with.
Okay so i can flash and change roms fantastically!
Im currently switching from verizon to T-Mobile and i heard there was a GSM capability. So on i went with research, I have tried so many different rom's, rom's with GSM that come with it.Nothing worked. No signal no nothing. one rom realized there was a sim card in but it said the sim card was full, which is definitely not full. I never got a good instruction and right files for the S-off function so i never made it S-off nor do i know what kind of wire to use. the most disappointing is that it can't get a signal and i flashed the RUU 4.0..... something and it did nothing to the radio on my phone when in bootloader. If anyone has some idea of what i can do with easy to follow instructions. I that much of a noob. I had successfully rooted and unloacked (sim by myself) and unlocked and flashed roms for the HTC Rezound. It's just this one thing that has been bother the crap out of me... nothing worked.
Did you go under network settings and select preferred network then select GSM?
Sent from my ADR6425LVW using Tapatalk 2
ruskimaster said:
I have been working on this phone for hours, and hours. and it has been one of the most frustrating phones i have ever worked with.
Okay so i can flash and change roms fantastically!
Im currently switching from verizon to T-Mobile and i heard there was a GSM capability. So on i went with research, I have tried so many different rom's, rom's with GSM that come with it.Nothing worked. No signal no nothing. one rom realized there was a sim card in but it said the sim card was full, which is definitely not full. I never got a good instruction and right files for the S-off function so i never made it S-off nor do i know what kind of wire to use. the most disappointing is that it can't get a signal and i flashed the RUU 4.0..... something and it did nothing to the radio on my phone when in bootloader. If anyone has some idea of what i can do with easy to follow instructions. I that much of a noob. I had successfully rooted and unloacked (sim by myself) and unlocked and flashed roms for the HTC Rezound. It's just this one thing that has been bother the crap out of me... nothing worked.
Click to expand...
Click to collapse
When you did the ruu, the second time it runs through the ruu (after first reboot) it will update the radios and system. Did you make sure when you did the ruu that you had to start it twice from hboot ? what version radios do you see listed in hboot ?
dottat said:
When you did the ruu, the second time it runs through the ruu (after first reboot) it will update the radios and system. Did you make sure when you did the ruu that you had to start it twice from hboot ? what version radios do you see listed in hboot ?
Click to expand...
Click to collapse
my radio is 1.22 and hboot is 2.25. when it went through and flashed/installed the ruu file it didn't reboot automatically as i've herd it should
ruskimaster said:
my radio is 1.22 and hboot is 2.25. when it went through and flashed/installed the ruu file it didn't reboot automatically as i've herd it should
Click to expand...
Click to collapse
Then you don't have global firmware yet. You need to ruu to 605.12 and then take the 6mb ota that will take you to 605.13. Then take one more ota @207mb which will give you full global radios and firmware.
Globals hboot is also 2.28 so you know what to look for.
Sent from my Nexus 7 using Tapatalk HD
dottat said:
Then you don't have global firmware yet. You need to ruu to 605.12 and then take the 6mb ota that will take you to 605.13. Then take one more ota @207mb which will give you full global
Click to expand...
Click to collapse
An alternative would be to install the global leak RUU first. From there you can follow the process for first installing the global update firmware (in the general discussion forum), then installing the global update itself (in the original android development forum).
Unfortunately, neither of the paths available to you is going to be totally painless...
Good luck,
John
So I haven't really found anyone with as specific a situation I'm in so I figured I'd make a new thread.
I was running a CM10.1 build from late July, which still had some bugs but was bearable. I upgraded to CM10.2 to try it out, but it was buggier than the CM10.1 build. I saw that the bugs were fixed in the latest build of CM10.1 so I flashed that. Since then I've been stuck in Roaming and can't activate my phone.
Each time I flashed I restored my 100% stock backup (I have a nandroid from the day I got the phone). Every flash was a clean install wiping data/cache/dalvik. Was first roaming when I reverted back to CM10.1, but restoring my backup and even flashing CM10.2 again I'm roaming still.
Basically, once I was roaming, I haven't stopped regardless of ROM.
And I'm sure someone will ask, I have S-off.
How do I go about fixing this?
EDIT: I've tried a clean flash of the same ROM with the sim card removed and tried changing the subscription type after like I've seen in another thread, but this did not work.
Bartikus said:
So I haven't really found anyone with as specific a situation I'm in so I figured I'd make a new thread.
I was running a CM10.1 build from late July, which still had some bugs but was bearable. I upgraded to CM10.2 to try it out, but it was buggier than the CM10.1 build. I saw that the bugs were fixed in the latest build of CM10.1 so I flashed that. Since then I've been stuck in Roaming and can't activate my phone.
Each time I flashed I restored my 100% stock backup (I have a nandroid from the day I got the phone). Every flash was a clean install wiping data/cache/dalvik. Was first roaming when I reverted back to CM10.1, but restoring my backup and even flashing CM10.2 again I'm roaming still.
Basically, once I was roaming, I haven't stopped regardless of ROM.
And I'm sure someone will ask, I have S-off.
How do I go about fixing this?
EDIT: I've tried a clean flash of the same ROM with the sim card removed and tried changing the subscription type after like I've seen in another thread, but this did not work.
Click to expand...
Click to collapse
This happened to me randomly. Only thing that works is RUU back to stock and go through the motions. You won't lose S-OFF, so you can then come back.
hurrrtin said:
This happened to me randomly. Only thing that works is RUU back to stock and go through the motions. You won't lose S-OFF, so you can then come back.
Click to expand...
Click to collapse
I need to RUU all the down to 1.15 correct? Then will I need to Moonshine again?
Bartikus said:
I need to RUU all the down to 1.15 correct? Then will I need to Moonshine again?
Click to expand...
Click to collapse
If you are S-OFF, then yes- RUU back down to 1.15. You won't need to moonshine again.
---------- Post added at 12:18 PM ---------- Previous post was at 12:13 PM ----------
hurrrtin said:
If you are S-OFF, then yes- RUU back down to 1.15. You won't need to moonshine again.
Click to expand...
Click to collapse
It might take a little while for it to change from roaming back to normal. Just give it time after you RUU.
Bartikus said:
So I haven't really found anyone with as specific a situation I'm in so I figured I'd make a new thread.
I was running a CM10.1 build from late July, which still had some bugs but was bearable. I upgraded to CM10.2 to try it out, but it was buggier than the CM10.1 build. I saw that the bugs were fixed in the latest build of CM10.1 so I flashed that. Since then I've been stuck in Roaming and can't activate my phone.
Each time I flashed I restored my 100% stock backup (I have a nandroid from the day I got the phone). Every flash was a clean install wiping data/cache/dalvik. Was first roaming when I reverted back to CM10.1, but restoring my backup and even flashing CM10.2 again I'm roaming still.
Basically, once I was roaming, I haven't stopped regardless of ROM.
And I'm sure someone will ask, I have S-off.
How do I go about fixing this?
EDIT: I've tried a clean flash of the same ROM with the sim card removed and tried changing the subscription type after like I've seen in another thread, but this did not work.
Click to expand...
Click to collapse
I'm having the exact same issue after doing the same thing you did, not sure where to go with it at this point, nothing is working
PhantomApollyon said:
I'm having the exact same issue after doing the same thing you did, not sure where to go with it at this point, nothing is working
Click to expand...
Click to collapse
Did you try to RUU back to 1.15? I just tried running it and it crashed, not sure if it's my computer or what
hurrrtin said:
If you are S-OFF, then yes- RUU back down to 1.15. You won't need to moonshine again.
Click to expand...
Click to collapse
I tried running the RUU from here http://forum.xda-developers.com/showthread.php?t=2017525
I ignored the first part about relocking since I assumed since I have s-off I don't need to, and I immediately tried to run the .exe as admin and it crashed.
UPDATE: I've relocked it now but the RUU still crashes before doing anything.
Bartikus said:
I tried running the RUU from here http://forum.xda-developers.com/showthread.php?t=2017525
I ignored the first part about relocking since I assumed since I have s-off I don't need to, and I immediately tried to run the .exe as admin and it crashed.
UPDATE: I've relocked it now but the RUU still crashes before doing anything.
Click to expand...
Click to collapse
try grabbing the RUU from the blue link in my sig
.torrented said:
try grabbing the RUU from the blue link in my sig
Click to expand...
Click to collapse
Downloading the RUU now. I've also tried flashing the 1.15 hboot and recovery, but they don't seem to have done anything. I'm still on 2.06... I unlocked my phone originally with moonshine, so my bootloader used to say moonshine s-off. now it says tampered/locked so I think hboot worked, but the recovery doesn't seem to have done anything.
UPDATE: The RUU ran it's course. Seems like the file for the other link was just bad (I had downloaded it twice). The phone is attempting to activate now, but it still can't get a signal. I know the signal at my house is usually pretty bad, but leaving it on the window sill usually does the trick. If worse comes to worse, could I at this point return it to Verizon without them knowing what's up?
Bartikus said:
Downloading the RUU now. I've also tried flashing the 1.15 hboot and recovery, but they don't seem to have done anything. I'm still on 2.06... I unlocked my phone originally with moonshine, so my bootloader used to say moonshine s-off. now it says tampered/locked so I think hboot worked, but the recovery doesn't seem to have done anything.
UPDATE: The RUU ran it's course. Seems like the file for the other link was just bad (I had downloaded it twice). The phone is attempting to activate now, but it still can't get a signal. I know the signal at my house is usually pretty bad, but leaving it on the window sill usually does the trick. If worse comes to worse, could I at this point return it to Verizon without them knowing what's up?
Click to expand...
Click to collapse
the point of the 1.15 hboot is so the RUU works... if you want to return to stock to take to vzw I would follow the restore guide, i believe its posted in the regular dev section and not the original dev section
edit* this one right here: http://forum.xda-developers.com/showthread.php?t=2293919
.torrented said:
the point of the 1.15 hboot is so the RUU works... if you want to return to stock to take to vzw I would follow the restore guide, i believe its posted in the regular dev section and not the original dev section
edit* this one right here: http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
Yeah the RUU seemed to work, I just still can't get a signal. Phone says no service and I can't get past the activation screen. I say "seemed" to work because I can't check in settings because I can't get past the activation... but the bootloader looks like stock again, whereas it said tampered before the RUU.
Thank you for the help by the way, I appreciate it.
RUU worked, I'm on 1.15. However, it didn't solve my no service problem. Could this be as trivial as a SIM problem? Is there anything else it might be?
Reset the Phone
Bartikus said:
RUU worked, I'm on 1.15. However, it didn't solve my no service problem. Could this be as trivial as a SIM problem? Is there anything else it might be?
Click to expand...
Click to collapse
After RUU you must Reset the phone from STOCK recovery,
finanandroid said:
After RUU you must Reset the phone from STOCK recovery,
Click to expand...
Click to collapse
Worked like a charm, thanks!
Bartikus said:
Worked like a charm, thanks!
Click to expand...
Click to collapse
U welcome! Glad you finally back on business :good:
finanandroid said:
U welcome! Glad you finally back on business :good:
Click to expand...
Click to collapse
Where can I find the STOCK recovery? I've been going crazy with this stock on roam thing.
RUU to get back to Stock Recovery
chipymunk said:
Where can I find the STOCK recovery? I've been going crazy with this stock on roam thing.
Click to expand...
Click to collapse
In order to recovery or restore the original phone factory setting you have to do RUU and Reset Phone*** is the way to get back
Stock recovery(= reset phone) to work properly. Even if you are on a Stock Rom it has a custom recovery so doing factory reset wont
work to restore the original phone setting.
after RUU you must do a phone reset either from setting>back up & reset or from the bootloader factory reset is the same Stock Recovery.
I read somewhere that flashing this Rom Stock rooted fix a roaming thing so you can give it a shot http://forum.xda-developers.com/showthread.php?t=2471836