Hello,
I'm S-on HTC Unlocked and running Mean Rom. I know Sprint's data network is atrocious right now but I wonder if my phone and/or the radio is making it worse.
I'm in a major metropolitan area and 60% of the time my phone is running on 1g data. Four or five times a day it randomly goes into roaming mode and I have to reboot it to get it out of roaming. Data speeds are like .3 mbps download when I do get 3g service with pings as high as 1400 ms.
I can seem to find out what radio I should be using or which is the most recent. Can I even update the radio without s-off? I did the firmware update when I got the phone so I cant get s-off. My old Evo 4G seemed to do better than this new one.
Any suggestions?
Oh, btw, I'm currently on Radio 1.05.11.0606.. H-boot 1.15 if it matters.
Thanks for the help.
Flash back to stock ROM and recovery, relock bootloader loader and take the ota or alternatively you can use an ruu.
om4 said:
Flash back to stock ROM and recovery, relock bootloader loader and take the ota or alternatively you can use an ruu.
Click to expand...
Click to collapse
Thanks.. I tried the RUU and I get errors. How exactly do I flash back to stock ROM? Just find a ROM in the development thread that says it stock?
Thanks again.
Yeah it should be in development. Flash stock ROM, recovery, then lock the boot loader (fastboot oem lock) and accept the ota
om4 said:
Yeah it should be in development. Flash stock ROM, recovery, then lock the boot loader (fastboot oem lock) and accept the ota
Click to expand...
Click to collapse
Where do you get stock recovery from? Do you can you fast boot unlock boot loader?
You need the unlock_code.bin to unlock bootloader again. Stock recovery should be in development somewhere
Related
Hello i currently am on GB Rom but when i turn on the phone it goes to the bootloader and says "TAMPERED". When I go to reboot option, it turns on the phone. How can I flash the RUU or return it to complete stock, since I have to send it into VZW. Thanks!
http://forum.xda-developers.com/showpost.php?p=24517103&postcount=5
I *think* this is the best you can do. Maybe even reflash stock recovery and re-lock but unsure if that rom will boot in a re-locked state.
jackpot08 said:
Hello i currently am on GB Rom but when i turn on the phone it goes to the bootloader and says "TAMPERED". When I go to reboot option, it turns on the phone. How can I flash the RUU or return it to complete stock, since I have to send it into VZW. Thanks!
Click to expand...
Click to collapse
you need to HTC dec relock run the new Ruu twice
im used to flashing ROMs on my galaxy SII. so my girl wanted me to upgrade her EVO to android 4.0. i forgot that i needed to use adb and fastboot to install ROMs on her device. I booted into TWRP via the power menu and proceeded to flash a ROM. i am now stuck in a bootloop. i can get into the bootloader menu, but nothing i do seems to fix the problem. ive been searching for a while and found some info im still reading about on how to get S-off and whatnot. anyone got any advice for me?
since you were able to get into TWRP, Imma assume that you went to HTCDev,
since you can get to the bootloader, i assume you can also set it to fastboot?
my suggestion would be to downgrade your h-boot (procedures are different for GSM and CDMA if I'm not mistaken) and get S-off, as some roms can have problems with higher hboot versions regardless of S-off.
From there you have pretty much free reign to do whatever you like to the phone.
My guess would be that since the phone is not S-off it's not playing nice with the ROM/Kernel you installed.
Links to Downgrading threads:
GSM:
http://forum.xda-developers.com/showthread.php?t=1471246
CDMA:
http://forum.xda-developers.com/showthread.php?t=1563342
Got it sorted. From fastboot I was able to relock the bootloader with advt. Then run the latest RUU and go back to stock. Now to unlock the bootloader again.
Question, if I downgrade the hboot and get s-off, can I just flash from recovery instead of booting recovery through fastboot and adb then flashing?
Sent from my SPH-D710 using xda app-developers app
yep, when you downgrade hboot and get S-off, you can flash all manner of roms and kernels without hooking the phone up to a pc at all
I successfully installed Fresh Evo LTE 5.3.1 on my phone.
One of the suggestions is to update the Radio but I'm having a tough time doing that.
Here are my specs:
HBOOT 1.15.0000
S-ON
FreshEVO 5.3.1 ROM
I went to the link from the FreshEVO LTE 5.3.1 page to update the radio and have tried the following to install the Radio:
Attempt 1
Downloaded the Full Firmware zip file
Rename it "PJ75IMG"
Place it in the root of my SD card
Reboot into Bootloader
The PJ75IMG.zip file is detect but I only get 'Parsing PJ75IMG.zip' and then the Fastboot, Recovery, etc. options are displayed.
Attempt 2
From the same page where I downloaded the Full Firmware zip file, I also tried:
Download the Boot.img Only (signed) file
Flash it through the command prompt while in Fastboot ("fastboot flash boot boot.img")
Go into Bootloader
The PJ75IMG.zip is detected but still get the "Parsing..." message and nothing else happens.
Attempt 3
I have also tried going into my TWRP recovery and installing the Full Firmware zip AND the Radio 1.12.11.0809 Only.zip file but the installation fails.
Any pointers or a link to a video or a post would be much appreciated.
Thanks and sorry if this is a duplicate post but I really couldn't find any post that showed step-by-step process.
revert to stock and accept the ota, you can then fastboot recovery again and reflash. hboot 1.15 can not directly flash any firmware
edit: you may have to relock your hboot but ive seen users state they didnt. if you decide to relock the phone you will have to unlock the bootloader again to enable fastboot
om4 said:
The easiest way to update your firmware is to revert to stock and accept the ota, you can then fastboot recovery again and reflash
Click to expand...
Click to collapse
I don't have my stock backup anymore.
I've heard stuff about using RUU or something like that. Any quick guide on how to revert back to stock?
DO NOT UNROOT TO ACCEPT THE OTA OR RUU
I'd highly suggest just staying with your current radios and waiting for S-OFF before trying to update the radios. You can still flash the new ROMS in the meantime
You cannot update radios or firmware with Hboot 1.15 or 1.19------->Thats why it is suggested and not required
Rxpert said:
DO NOT UNROOT TO ACCEPT THE OTA OR RUU
I'd highly suggest just staying with your current radios and waiting for S-OFF before trying to update the radios. You can still flash the new ROMS in the meantime
You cannot update radios or firmware with Hboot 1.15 or 1.19------->Thats why it is suggested and not required
Click to expand...
Click to collapse
Thanks for the warning.
Since I'm pretty new to all this, I'll play it safe and stick to what I have.
sorry guys internet crapped out and i got stuck trying to post lol. rxpert has a point but with so much negativity about s-off never coming I'm starting to consider taking the OTA.
also you should always have a back up, its your go to solution when nothing else seems to be working since its a back up of when everything was new and working be it stock or custom
The new radios aren't worth losing the possibility, no matter how small
Sent from my EVO using Tapatalk 2
True...
om4 said:
sorry guys internet crapped out and i got stuck trying to post lol. rxpert has a point but with so much negativity about s-off never coming I'm starting to consider taking the OTA.
also you should always have a back up, its your go to solution when nothing else seems to be working since its a back up of when everything was new and working be it stock or custom
Click to expand...
Click to collapse
Just so I am clear, I too am 1.5 so if have my orginal rom, (the one after I unlocked my bootloader) i can restore it and accept the OTA without having to relock my phone? (it wont brick):good: Or do i have some other steps to take, I read the don't panic instructions, but it only mentioned what the OTA does ( relocks with a new rom) but nothing about what happens if I don't relock before I accept the OTA, I know i seem a bit slow, 4g lte isn't as interesting as OG 4g without S-off.
RamesisX said:
Just so I am clear, I too am 1.5 so if have my orginal rom, (the one after I unlocked my bootloader) i can restore it and accept the OTA without having to relock my phone? (it wont brick):good: Or do i have some other steps to take, I read the don't panic instructions, but it only mentioned what the OTA does ( relocks with a new rom) but nothing about what happens if I don't relock before I accept the OTA, I know i seem a bit slow, 4g lte isn't as interesting as OG 4g without S-off.
Click to expand...
Click to collapse
I havent yet done it myself but users have said they didnt need to relock, how ever as captain said there is no real need to update right now. If you decide to go ahead it would be a good idea to relock ( fastboot oem lock ) just to make sure, you can unlock afterwards. I neglect to mention this in my guide because most phones now are on 1.19 anyway and those still on 1.15 are holding out for soff
You will want to have the stock recovery to take the ota. Most people do this by relocking and running the ruu
Once again, I'm providing the info but I don't recommend it
Sent from my EVO using Tapatalk 2
Rxpert said:
You will want to have the stock recovery to take the ota. Most people do this by relocking and running the ruu
Once again, I'm providing the info but I don't recommend it
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I am still researching how to relock without issues. I have my orginal rom but still leary about the entire relocking process. I was hoping i could restore to orginal sense rom, then take the OTA. otherwise I am looking for the simplest way to accompish the relocking task, but frankly nothing is easy when i comes to playing around with 4g lte, except it is rather difficult to brick. With my luck i might succeed in that LMAO
:good::laugh:
RamesisX said:
I am still researching how to relock without issues. I have my orginal rom but still leary about the entire relocking process. I was hoping i could restore to orginal sense rom, then take the OTA. otherwise I am looking for the simplest way to accompish the relocking task, but frankly nothing is easy when i comes to playing around with 4g lte, except it is rather difficult to brick. With my luck i might succeed in that LMAO
:good::laugh:
Click to expand...
Click to collapse
there is no simpler method for relocking hboot, simply fastboot oem lock
om4 said:
there is no simpler method for relocking hboot, simply fastboot oem lock
Click to expand...
Click to collapse
Used that and it worked great.
Evo 4G LTE
h-boot 1.19, s-on, HTCDev unlocked
Hi I need to take my phone in for repair and want to revert to Sprint's stock ICS, however I am on the engineering hboot 1.04 and don't want to lose that. I have flashed the OTA ROM from here (http://forum.xda-developers.com/showthread.php?t=1808150) but I am boot looping due to the kernel. Can anyone point me to a compatible flashable kernel?
And as a follow up, if I were to flash directly to Sprints current OTA, is it possible to downgrade all the way back to HBOOT 1.04?
daviderickson said:
Hi I need to take my phone in for repair and want to revert to Sprint's stock ICS, however I am on the engineering hboot 1.04 and don't want to lose that. I have flashed the OTA ROM from here (http://forum.xda-developers.com/showthread.php?t=1808150) but I am boot looping due to the kernel. Can anyone point me to a compatible flashable kernel?
Click to expand...
Click to collapse
The reason you are boot looping is because that ROM requires bootloader (hboot) 1.58, which is part of the updated 2.89.651.2 firmware. You can either flash the firmware from the OP of that thread, or reset everything to 100% stock by downloading the Sprint ICS RUU from here and flashing it from Windows.
Your radio status will stay S-OFF, and you can easily flash any bootloader you want from the stock bootloader once you get your phone back.
ramjet73
ramjet73 said:
The reason you are boot looping is because that ROM requires bootloader (hboot) 1.58, which is part of the updated 2.89.651.2 firmware. You can either flash the firmware from the OP of that thread, or reset everything to 100% stock by downloading the Sprint ICS RUU from here and flashing it from Windows.
Your radio status will stay S-OFF, and you can easily flash any bootloader you want from the stock bootloader once you get your phone back.
ramjet73
Click to expand...
Click to collapse
Thanks ramjet- And this won't require me having to go through HTC's unlock procedure right?
daviderickson said:
Thanks ramjet- And this won't require me having to go through HTC's unlock procedure right?
Click to expand...
Click to collapse
That's correct.
As long as you are S-OFF now and don't set S-ON before bringing the phone in for service, you can flash whatever bootloader you want after you get your phone back and then flash any ROM/kernel combination that works with that hboot.
Of course, S-ON could be set by whoever works on your phone, but I've never heard of that happening and the wire trick is pretty easy if you should need to get S-OFF again.
ramjet73
Hey ramjet-
I just got my phone back from repair, it is still listed as S-OFF, but is listed as locked. Since this seems to be a somewhat unique starting point compared to other threads, what is the procedure to go from S-OFF/locked to another hboot? Do I just pick an arbitrary RUU and flash with it?
daviderickson said:
Hey ramjet-
I just got my phone back from repair, it is still listed as S-OFF, but is listed as locked. Since this seems to be a somewhat unique starting point compared to other threads, what is the procedure to go from S-OFF/locked to another hboot? Do I just pick an arbitrary RUU and flash with it?
Click to expand...
Click to collapse
It's good that it has the bootloader locked because that's the stock status and you don't need it unlocked if you have S-OFF. However, if you want to run fastboot commands like "flash", "erase" and "boot" from a PC you need to flash a custom bootloader, then you can flash a custom recovery after that using the "fastboot flash recovery recovery.img" command. Your bootloader status will still be "locked" but the custom hboots ignore that status and run the fastboot commands anyway.
This post explains how to select and flash a different hboot when you are S-OFF.
ramjet73
Thanks for the pointer, I was able to flash back to 1.04 ENG, and get 4ext back installed. Is there any particular reason to run a newer hboot like Jbear's 1.58 other than if needed for kernel/ROM compatibility?
daviderickson said:
Thanks for the pointer, I was able to flash back to 1.04 ENG, and get 4ext back installed. Is there any particular reason to run a newer hboot like Jbear's 1.58 other than if needed for kernel/ROM compatibility?
Click to expand...
Click to collapse
No. Only if you want to run the ROM's that require it like coolexe's Cool ICS and Virus's Viper3D. The thread I linked on bootloaders gives a lot more detail on compatibility with different types of ROM's.
ramjet73
Hi All,
I'm not sure if i messed up my phone or not by updating to ARHD 11.1
I had to flash something on the phone as I was going overseas. I unlocked the phone from network but the APN was still attached to ATT cell towers
Current Problems:
- No Vibrations few weeks after flashing ARHD (checked/unchecked and restarted the haptic feedback or when it rings)
- Slow Startup when restarting (power ON/OFF is fine)
- Restarting phone will have red text that says "This version is for Developing Purposes only...."
- No Music on Google Play Music or Music application
The procedure I took goes as follows:
1. Unlocked bootloader
2. Flashed TWRP recovery
3. Flashed ARHD 11.1 ROM
4. Originally ATT phone but selected International Generic ROM
***didn't flash a new firmware before flashing ROM?***
I flashed from ATT Stock 4.2 > 4.4.3
Currently I am:
Android: 4.4.3 S-ON
Baseband: 1.16.21331931
Build Number: 2.22.401.5
Can someone show me step by step of how I should revert the process and get ARHD working on my phone again?
Slow boot is a known issue if you didn't update the firmware and using a 2.x Sense ROM.
Since you are s-on, one way to update is to relock the bootloader and RUU to 2.23. You will then need to unlock the bootloader again and re-install custom recovery (and your desire custom ROM).
No sound in some apps is known issue if you picked the Harmon Kardon mod, and do not have the corresponding firmware. Easiest way around this is to just re-flash the ROM and do not pick the HK mod. If you didn't pick HK, it might be another symptom of the outdated firmware issue described above.
The red text on the boot screen is normal on a modded phone. It will appear once you have a custom recovery installed. You can either just live with it; or s-off an flash a modified hboot to get rid if the red text.
redpoint73 said:
Slow boot is a known issue if you didn't update the firmware and using a 2.x Sense ROM.
Since you are s-on, one way to update is to relock the bootloader and RUU to 2.23. You will then need to unlock the bootloader again and re-install custom recovery (and your desire custom ROM).
No sound in some apps is known issue if you picked the Harmon Kardon mod, and do not have the corresponding firmware. Easiest way around this is to just re-flash the ROM and do not pick the HK mod. If you didn't pick HK, it might be another symptom of the outdated firmware issue described above.
The red text on the boot screen is normal on a modded phone. It will appear once you have a custom recovery installed. You can either just live with it; or s-off an flash a modified hboot to get rid if the red text.
Click to expand...
Click to collapse
Thanks for the help. My vibration came back....dont exactly know how but I just kept tapping on the bottom part of the phone
So, I can relock bootloader and use RUU even if I am S-ON?
Is there a guide I should be following?
@oogierule
Google search,Google Now is one option you can use to find guides with the right key words
fastboot oem lock will relock your bootloader.
oogierule said:
Thanks for the help. My vibration came back....dont exactly know how but I just kept tapping on the bottom part of the phone
So, I can relock bootloader and use RUU even if I am S-ON?
Is there a guide I should be following?
Click to expand...
Click to collapse
oogierule said:
So, I can relock bootloader and use RUU even if I am S-ON?
Click to expand...
Click to collapse
Of course, why else would I have stated exactly that in my previous post?
In fact, s-on is the only thing that makes this a requirement. With s-on, you don't need to relock to RUU.
redpoint73 said:
Slow boot is a known issue if you didn't update the firmware and using a 2.x Sense ROM.
Since you are s-on, one way to update is to relock the bootloader and RUU to 2.23. You will then need to unlock the bootloader again and re-install custom recovery (and your desire custom ROM).
No sound in some apps is known issue if you picked the Harmon Kardon mod, and do not have the corresponding firmware. Easiest way around this is to just re-flash the ROM and do not pick the HK mod. If you didn't pick HK, it might be another symptom of the outdated firmware issue described above.
The red text on the boot screen is normal on a modded phone. It will appear once you have a custom recovery installed. You can either just live with it; or s-off an flash a modified hboot to get rid if the red text.
Click to expand...
Click to collapse
Would i need to RUU back to 1.58 first and then RUU to 2.23? or would i be able to RUU to 2.23 directly from my custom ROM?
oogierule said:
Would i need to RUU back to 1.58 first and then RUU to 2.23? or would i be able to RUU to 2.23 directly from my custom ROM?
Click to expand...
Click to collapse
You can just run the 2.23 RUU. RUU is a complete image, and therefore they do not need to be installed "sequentially".
This is in direct contrast to OTAs, which are not always a complete image, and typically need to be installed in proper sequence.