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.
Related
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
Here is the radio from the leak on 5/2 for those of you who would like to try it.
http://www.mediafire.com/?93i6ppvasdpetet
MD5: cd59d504b81aa2ac7e8aaf5f5fd017d4
As has been stated, these radios are not updated from the 3.11 RUU leak. If you are already on that RUU you will not see a difference.
If you flash to the 3.13 RUU then you will most likely see an improvement due to the following files in the RUU being updated:
Boot.img
hboot
initramfs
Aside from those those the RUU appears to be pretty much exactly the same as the 3.11 release.
Warning: I am not responsible for any damage you do to your phone. Flashing radios can leave your phone inoperable if something goes wrong.
Installation:
REQUIRES S-OFF
1. Rename zip to PH98IMG.zip and put it on an SD card.
2. Unplug any USB cables from your phone, Open the phone, and remove the battery.
3. Insert the SD card with the zip file on it into your phone and reinsert your battery.
4. Hold down the VOL-DOWN and POWER buttons until your phone turns on and enters hboot.
5. Hboot will scan for the file. Once it finds it, press the VOL-UP key to flash.
6. Wait for the process to complete.
7. Press power once hboot prompts you.
8. Enjoy the speed (hopefully)
I am seeing a vast improvement running the 3.13 RUU with this radio. I have not tried it in other ROM or RUU versions.
On 3.13 RUU I am getting 10+mb down / 2+mb up in my lead paint coated apartment.
On 3.11 RUU I was lucky to even get an LTE signal.
Please check out superchilpil's post if you want the whole leak: http://forum.xda-developers.com/showthread.php?t=1614366
Have a link?
jefffeely said:
Here is the radio from the leak on 5/2 for those of you who would like to try it.
I am seeing a vast improvement running the 3.13 RUU with this radio. I have not tried it in other settings.
Click to expand...
Click to collapse
a link would help and maybe noob instructions
Changing radios in the passed caused 4G issues. So be warned!!
Yeah, but folks were going back to GB right?
jefffeely said:
Here is the radio from the leak on 5/2 for those of you who would like to try it.
I am seeing a vast improvement running the 3.13 RUU with this radio. I have not tried it in other settings.
Click to expand...
Click to collapse
Can ya share a ruu link?
Sent from my ADR6425LVW using xda premium
My thread has the new leak with the hboot and radios, I've upgraded from the gb firmware with no issues
If you do try it and encounter issues I've attatched the stock recovery, use it and factory reset
The hboot doesnt have the extra fastboot commands so if you need them then down flash it
Sent from my ADR6425LVW using Tapatalk 2
Irieone said:
Have a link?
Click to expand...
Click to collapse
I has talent.
Flyhalf205 said:
Changing radios in the passed caused 4G issues. So be warned!!
Click to expand...
Click to collapse
Flashing the entire 3.13 ICS leak RUU fixed the radio issues I was having. I hadn't had a good connection since the original stock.
Definitely have no idea how the new radios will work with other builds though.
Do we need to be s-off for this? Or can we just set this up as a ph98img?
Sent from my ADR6425LVW using Tapatalk 2
nhugh406 said:
Do we need to be s-off for this? Or can we just set this up as a ph98img?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
s-off
Ahh. Ty sirs!
Sent from my ADR6425LVW using Tapatalk 2
so this will work with this right?
http://www.scottsroms.com/downloads.php?do=file&id=111
Is this the full radio set now?
When 1st posted it mentioned that it lacked the lte piece.
QBall45 said:
Is this the full radio set now?
When 1st posted it mentioned that it lacked the lte piece.
Click to expand...
Click to collapse
Yup it is the whole thing now.
Can you post the MD5 for the download. I always check. Not checking is like not using protection.
jm700wx said:
Can you post the MD5 for the download. I always check. Not checking is like not using protection.
Click to expand...
Click to collapse
cd59d504b81aa2ac7e8aaf5f5fd017d4 there ya go.
Thank You Sir!!! Time to flash!!!
I don't think that it has been mentioned yet being that radio flashing is a new thing for the Rezound. But on the Dinc one way that people were able to brick their devices was flashing the same radio on top of itself. What would happen is someone would flash their PH*.zip file, then not delete it off the root of the SD Card and then the next time they went in to their bootloader it would still be there and prompt them to update. They would say Yes and then get bricked.
Not sure if that is the same for the Rezound, but I would hate to hear about someone bricking their phone because of this. So remember to immediately remove your PH98IMG.zip after flashing your radios guys.
Let me know if y'all experience data issues
Sent from my ADR6425LVW using Tapatalk 2
My phone screen will freeze, the buttons will not respond, the bluetooth input buttons will not respond, in fact I though the phone was completely locking until I found it would still respond to adb. Sometimes this when this happens it eventually reboots on it's own, but will often bootloop until I pull the battery. I am 1.58 hboot s-off with meanrom ics, but it also happened with 1.5 s-on stock. I have tried clean wipes and setting things up from completely scratch. (not using google or titanium at all to restore)
Any suggestions?
Hey rob. Maybe I can help. I'm running meanrom ics v2.6 right now. With hboot 1.58 s-off as well. I have had this problem in the past. Usually I had to do a full clean wipe and reflash the Rom to get it to work again. There could be a couple reasons this is happening. What kernel are you using? I am using the one that the Rom provided which is the hboot 1.58 one. Also have you flashed any mods on top of the Rom? Certain mods don't play well with certain roms. If so try reflashing the Rom without them and see what happens. If you are using a different kernel please use the hboot 1.58 one and see what happens.
---------- Post added at 09:24 AM ---------- Previous post was at 09:22 AM ----------
Also have you had this problem with other roms or just this one?
To clarify it happens about every other day. Yes it happened on the stock rom, but I did not verify if it was a full device freeze or just the interface freezing.
There are no mods installed.
I am using the 1.58 kernel as required by the 1.58 hboot.
My suggestion to you is flash the ruu file. Check through the cdma dev section for PG86IMG Ics 2
35 s 2.89 added in the thread title. It's the very first download link. Once you download the file rename it to PG86IMG in all caps and place it on the root of your sdcard. then boot into bootloader and let your phone pick up the update. Ruu files tend to fix problems like that. if it don't work then my next suggestion is to take it to a sprint repair shop to fix it. Your phone will be in a state where they can fix it because they won't touch your phone if it has a custom Rom installed. killing two birds with one stone if the update fails to fix your problem.
thanks for the effort. the stock rom from the ruu did the same thing, even more then meanrom does.
Just hoping for other options as the problem is not repeatable on demand so taking to the store will take forever before they replace the device.
robtheslob said:
thanks for the effort. the stock rom from the ruu did the same thing, even more then meanrom does.
Just hoping for other options as the problem is not repeatable on demand so taking to the store will take forever before they replace the device.
Click to expand...
Click to collapse
I'm sorry I couldn't be more of assistance. It's starting to sound like a hardware issue. Usually these solutions would fix the problem. Hopefully you can get it fixed. Best wishes
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!
Ok, I give up. I've tried everything I can think of, but I can't get 4G to stick on, and trying to run the 3.06 RUU gives me error 170.
Here's what happened. Yesterday I flashed Kickdroid 2.0 with the CDMA patch from: http://forum.xda-developers.com/showthread.php?t=2634126
- Everything seemed to install fine, and initially 4G was up. But within about a minute 4G disconnected and I no longer had any mobile data.
- So then I did a full complete wipe via TWRP - doing the factory reset, then using the advanced wipe on everything except internal storage - then restored my backup of BadSeed's Tranquil rom. It came up fine initially but then within about a minute 4G disconnected and I was put back at 3G.
- Re-wiped everything same as before, then flashed the Tranquil Rom from scratch. - Same problem. 4G connects initially then drops to 3G.
- Updated TWRP to the beta .6 version as suggested by the Kickdroid dev and re-flashed and did all those same steps again and still having same problem
- At one point last night I left the phone alone and after a long time with the kickdroid Rom re-flashed it asked me which carrier I had. I chose Verizon and then 4G stuck on for a while. Then, it lost it's connection again to 4G. This Rom never gave me any 'Service'. The lockscreen always said 'no service'
- This morning, I flashed the latest Viper and it too initially gives me 4G then about a minute later that drops and I'm stuck on 3G.
- I thought maybe it was my SIM card, so I put it in my rezound and it works just fine in that phone.
- I've been trying to RUU using the 3.06.605.4 RUU from: http://forum.xda-developers.com/showthread.php?t=2612740 but I keep getting error 170 saying that the device wasn't found and to plug in my usb cable.
I suspect that there is something in the CDMA patch that has done this. I say that in hopes to help narrow the problem down not to blame anyone, as I do accept the responsibility to what I have flashed on my phone, so please don't take it that way. I don't know what could remain after wiping and re-flashing but it seems as thought something has.
Anyhoo, I'm getting a little desperate at this point and hoping someone can help me out. Much appreciated...
Try flashing the recovery flashable radio?
Something could have borked the radio partition.
Sent from my DNA using my mind.
Uzephi said:
Try flashing the recovery flashable radio?
Something could have borked the radio partition.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Lol, of course the one thing I forgot to mention that I did. I flashed the radio from .torrented's thread as well.
I think at this point I'd like to just RUU it anyway. Could it be that my bootloader is still unlocked and I have TWPR as my recovery?
Thanks a lot guys...
badogg said:
Ok, I give up. I've tried everything I can think of, but I can't get 4G to stick on, and trying to run the 3.06 RUU gives me error 170.
Here's what happened. Yesterday I flashed Kickdroid 2.0 with the CDMA patch from: http://forum.xda-developers.com/showthread.php?t=2634126
- Everything seemed to install fine, and initially 4G was up. But within about a minute 4G disconnected and I no longer had any mobile data.
- So then I did a full complete wipe via TWRP - doing the factory reset, then using the advanced wipe on everything except internal storage - then restored my backup of BadSeed's Tranquil rom. It came up fine initially but then within about a minute 4G disconnected and I was put back at 3G.
- Re-wiped everything same as before, then flashed the Tranquil Rom from scratch. - Same problem. 4G connects initially then drops to 3G.
- Updated TWRP to the beta .6 version as suggested by the Kickdroid dev and re-flashed and did all those same steps again and still having same problem
- At one point last night I left the phone alone and after a long time with the kickdroid Rom re-flashed it asked me which carrier I had. I chose Verizon and then 4G stuck on for a while. Then, it lost it's connection again to 4G. This Rom never gave me any 'Service'. The lockscreen always said 'no service'
- This morning, I flashed the latest Viper and it too initially gives me 4G then about a minute later that drops and I'm stuck on 3G.
- I thought maybe it was my SIM card, so I put it in my rezound and it works just fine in that phone.
- I've been trying to RUU using the 3.06.605.4 RUU from: http://forum.xda-developers.com/showthread.php?t=2612740 but I keep getting error 170 saying that the device wasn't found and to plug in my usb cable.
I suspect that there is something in the CDMA patch that has done this. I say that in hopes to help narrow the problem down not to blame anyone, as I do accept the responsibility to what I have flashed on my phone, so please don't take it that way. I don't know what could remain after wiping and re-flashing but it seems as thought something has.
Anyhoo, I'm getting a little desperate at this point and hoping someone can help me out. Much appreciated...
Click to expand...
Click to collapse
Did you update HTC driver? then trying to RUU from bootloader, Fastboot usb, with the latest Hboot updated* (1.54.0000)= 3.06.605.4 version.
---------- Post added at 01:34 PM ---------- Previous post was at 01:23 PM ----------
badogg said:
Lol, of course the one thing I forgot to mention that I did. I flashed the radio from .torrented's thread as well.
I think at this point I'd like to just RUU it anyway. Could it be that my bootloader is still unlocked and I have TWPR as my recovery?
Thanks a lot guys...
Click to expand...
Click to collapse
Bootloader unlocked matter to RUU , TWRP nope.
finanandroid said:
Did you update HTC driver? then trying to RUU from bootloader, Fastboot usb, with the latest Hboot updated* (1.54.0000)= 3.06.605.4 version.
---------- Post added at 01:34 PM ---------- Previous post was at 01:23 PM ----------
Bootloader unlocked matter to RUU , TWRP nope.
Click to expand...
Click to collapse
I would expect a problem later on if it were the bootloader being locked still, not int he beginning and then saying that the device isn't found. Or am I totally wrong and should just re-lock the bootloader and try again?
badogg said:
I would expect a problem later on if it were the bootloader being locked still, not int he beginning and then saying that the device isn't found. Or am I totally wrong and should just re-lock the bootloader and try again?
Click to expand...
Click to collapse
Well you mention error 170, usually its HTC Driver outdated, thats the reason that I suggest Driver update.
thought first have a working ADB/fastboot to see your phone. usb 2
you need to lock the Bootloader in order to run Ruu 3.06.exe (no problem because after RUU is done, Rumrunner unlock and S-Off Thanks to beaups
you need to update the Stock Hboot version to 3.06. thanks to Torrented
Here the link updated thanks to Phaded http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
finanandroid said:
Well you mention error 170, usually its HTC Driver outdated, thats the reason that I suggest Driver update.
thought first have a working ADB/fastboot to see your phone. usb 2
you need to lock the Bootloader in order to run Ruu 3.06.exe (no problem because after RUU is done, Rumrunner unlock and S-Off
you need to update the Stock Hboot version to 3.06. thanks to Torrented
Here the link updated thanks to Phaded http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Click to expand...
Click to collapse
I tried the updated drivers earlier and still get the error 170. I'm wondering if there is just something wonky with my work computer that isn't working right. I'll try locking bootloader and running RUU from a laptop and see what happens. Thanks for the assist! :highfive:
badogg said:
I tried the updated drivers earlier and still get the error 170. I'm wondering if there is just something wonky with my work computer that isn't working right. I'll try locking bootloader and running RUU from a laptop and see what happens. Thanks for the assist! :highfive:
Click to expand...
Click to collapse
a pleasure
Any other android devices hooked up to that PC? I had 170 error when having both Rezound and DNA plugged in. The program may be trying to look at the other device port instead of the DNA port.
Try with locked boot loader and stock recovery. After I got rid of error 170 I got an error in the 150's (not the one mentioned in the ruu thread). It was because of custom splash image and custom recovery.
Sent from my DNA using my mind.
Uzephi said:
Any other android devices hooked up to that PC? I had 170 error when having both Rezound and DNA plugged in. The program may be trying to look at the other device port instead of the DNA port.
Try with locked boot loader and stock recovery. After I got rid of error 170 I got an error in the 150's (not the one mentioned in the ruu thread). It was because of custom splash image and custom recovery.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Interesting, I don't have anything connected, but I'm sure I have drivers loaded for my nexus 7
Which drivers for HTC are you using? The ones from HTC sync or the ones from pdanet? I found the pdanet ones work better for everything but HTC sync (which, who honestly uses? Lol)
Sent from my DNA using my mind.
Well, I let htcsync update the usb drivers and now the RUU is updating the image now.
Ok, this persisted through the RUU. Rom booted up, got 4G initially, then went to 3G.
badogg said:
Ok, this persisted through the RUU. Rom booted up, got 4G initially, then went to 3G.
Click to expand...
Click to collapse
after Ruu you most do a factory reset* from stock recovery
All that is usually needed is to restore the NV partitions on the device.
To do this, flash a stock rom and stock recovery.
Perform a factory reset in stock recovery.
Your radio should then function normally again.
No need to RUU or any of that, just a stock rooted rom and stock recovery are sufficient.
The key factor is the factory reset in stock recovery.
So if you did the RUU already, and did not do the factory reset in stock recovery, then that's why you still have an issue.
finanandroid said:
after Ruu you most do a factory reset* from stock recovery
Click to expand...
Click to collapse
omg, duh!! I knew that, just forgot to do it.
That seems to have fixed it. +150,000 internets to you!!
badogg said:
omg, duh!! I knew that, just forgot to do it.
That seems to have fixed it. +150,000 internets to you!!
Click to expand...
Click to collapse
glad :good: you got it !
@santod040 which stock rom do I need to flash and what is stock recovery? Do I have to do this with adb comands or use twarp like normal flash so I can get my radio working correctly again and 4g back? Any one that can point me to what I need to do here is greatly appreciated. Thank you!
Sent from my HTC6435LVW using Tapatalk
Sutko82 said:
@santod040 which stock rom do I need to flash and what is stock recovery? Do I have to do this with adb comands or use twarp like normal flash so I can get my radio working correctly again and 4g back? Any one that can point me to what I need to do here is greatly appreciated. Thank you!
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
My full odex stock Rom in the dev section is sufficient.
If there isn't a stock recovery posted anywhere I'll locate one for you.
Then you flash the Rom in your current recovery.
After you boot, reboot to hboot.
Then fastboot flash recovery nameoffile.img.
Then either factory reset from Recovery or from the roms settings option.
Sent from my HTC6500LVW using Tapatalk
Pls locate stock recovery as I am not sure which one to use. I am downloading your odexed stock rom as we speak. I appreciate this very much! @santod040
Sent from my HTC6435LVW using Tapatalk
---------- Post added at 11:48 PM ---------- Previous post was at 11:43 PM ----------
After boot type in command prompt reboot to hboot or can I just type adb devices and then flash recovery
Sent from my HTC6435LVW using Tapatalk