Related
PLZ help me, while trying to upgrade my HERM I lost the Radio, there is a message (No GSM) appearing during the boot.
I've tried many unofficial ROMs, but still getting the same message!!!
And when I tried to use the official ROM, the upgrade stopped on 11%!!??
To solve the hangup problem, I used unofficial ROM again, and after the upgrade I found the same GSM problem again.
FirasKB said:
PLZ help me, while trying to upgrade my HERM I lost the Radio, there is a message (No GSM) appearing during the boot.
I've tried many unofficial ROMs, but still getting the same message!!!
And when I tried to use the official ROM, the upgrade stopped on 11%!!??
To solve the hangup problem, I used unofficial ROM again, and after the upgrade I found the same GSM problem again.
Click to expand...
Click to collapse
What "official" ROM? You've given absolutely NO info regarding anything friend...
Myself, I'd click the green link in my signature... but that's me
My problem is clear, there is No GSM in my HERM, I've tried WM 5, WM 6 and WM 6.1, but no way, I couldn't success??!!
Kindly, advice if you have any solution or ask for a specific info.
FirasKB said:
My problem is clear, there is No GSM in my HERM, I've tried WM 5, WM 6 and WM 6.1, but no way, I couldn't success??!!
Kindly, advice if you have any solution or ask for a specific info.
Click to expand...
Click to collapse
Yes your problem is clear, you have no GSM. I don't know where you hail from, which exact PDA you have, your provider, what ROM you last used before this happened, etc..
Dr Puttingham said:
Yes your problem is clear, you have no GSM. I don't know where you hail from, which exact PDA you have, your provider, what ROM you last used before this happened, etc..
Click to expand...
Click to collapse
Fine,,,
Device: at&t 8525
ROM: Original WM5 ROM, and while trying to upgrade it my device hanged up on the colored screen. To fix that, I've installed schap's 4.31 WM6 ROM using the MicroSD Card (HERMIMG). Now the device can boot but with No GSM at all (even there's no information about the GSM under Device Info).
The device now can accept any modified ROM (like schap's, faria, etc...) but unable to accept the official (original) ROMs. When I try to install any official ROM the upgrade process will stack on 11% every time.
So, the device still having no GSM.
Thank You....
FirasKB,
Most roms on her DO NOT come with a radio included. Usually only the manufacturer roms do.
There are 2 things you need to do:
- Consult the MrVanx guides which will help you understand what you are doing (google search for this).
- go to the wiki in this forum and search for a radio rom to upload.
In summary, reflash, say, Scahps rom then flash a radio rom from the wiki (I suggest radio 1.47, which is pretty reliable).
Hope this helps.
WB
FirasKB said:
Fine,,,
Device: at&t 8525
ROM: Original WM5 ROM, and while trying to upgrade it my device hanged up on the colored screen. To fix that, I've installed schap's 4.31 WM6 ROM using the MicroSD Card (HERMIMG). Now the device can boot but with No GSM at all (even there's no information about the GSM under Device Info).
The device now can accept any modified ROM (like schap's, faria, etc...) but unable to accept the official (original) ROMs. When I try to install any official ROM the upgrade process will stack on 11% every time.
So, the device still having no GSM.
Thank You....
Click to expand...
Click to collapse
Ahhh, a little info.
First download the official AT&T 3.62 ROM which includes the 1.54.07.00 radio.
Reboot the pc with the PDA disconnected.
(Oh, make sure that you have ActiveSync 4.5 insttalled of course)
Put the device into bootloader mode (hold power and OK button while pressing reset with stylus, nice tri color screen will appear)
Connect the PDA to the USB cable and run the RUU_Inside.exe file.
wacky.banana is correct, most chef's don't include a radio. You've got a corrupted ROM (due to the incomplete flash) The RUU_Inside.exe will typically talk directly to the hardware when nothing else can and fix. I've personally recovered around 10 or so 8525's that I've "bricked" with bad flashes and then repaired with this method.
I can't guarantee that this will work but it IS your best shot friend.
Good luck!
Dr Puttingham said:
Ahhh, a little info.
First download the official AT&T 3.62 ROM which includes the 1.54.07.00 radio.
Reboot the pc with the PDA disconnected.
(Oh, make sure that you have ActiveSync 4.5 insttalled of course)
Put the device into bootloader mode (hold power and OK button while pressing reset with stylus, nice tri color screen will appear)
Connect the PDA to the USB cable and run the RUU_Inside.exe file.
wacky.banana is correct, most chef's don't include a radio. You've got a corrupted ROM (due to the incomplete flash) The RUU_Inside.exe will typically talk directly to the hardware when nothing else can and fix. I've personally recovered around 10 or so 8525's that I've "bricked" with bad flashes and then repaired with this method.
I can't guarantee that this will work but it IS your best shot friend.
Good luck!
Click to expand...
Click to collapse
Thanks to your support friends,,
I've done as you mentioned, but the upgrade process stopped on 11% again and couldn't complete!!?? (the message ERROR [262]: UPDATE ERROR appeared on my P.C)!!??
Kindly, advice...
I can't remeber what error 262 is about; however is your device unlocked? If it is not then you need to address that issue first (its in the wiki)
Secondly have you installed hard spl to your device BEFORE attempting to upgrade your rom? If the answer to this question is no then that will confirm that you have not read up on this before jumping in, which is hugely dangerous.
WB
Stuck.... completely stuck
My fiances phone is stuck in the tri color bootloader screen. I am in the US and i have tried everything from flashing the original RUU to a hard reset and everthing, but nothing seems to work. the IPL is 4. 10. 0002 and the SPL is 4. 10. 0000. Can someone please help me. I know there has to be a way to fix this.
I had the same problem. After trying to fix it myself for about a week I gave up and sent it to AT&T Repair center. Got it back functional.
I haven't tried the Himalaya ROM method, though.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=372895
Good luck!
wacky.banana said:
I can't remeber what error 262 is about; however is your device unlocked? If it is not then you need to address that issue first (its in the wiki)
Secondly have you installed hard spl to your device BEFORE attempting to upgrade your rom? If the answer to this question is no then that will confirm that you have not read up on this before jumping in, which is hugely dangerous.
WB
Click to expand...
Click to collapse
Thanks again to your support,
The problem happened when I tried to unlock the device to upgrade it (it was fine befor), I don't know whether it was already locked or not, but usualy when I buy any Pocket P.C I'm preparing to unlock it first (I've done that many times on HERMES before, but this is the first time I'm facing such problem!!). So, while unlocking the device it's stucked on the tri color screen.
I've done many things after that to solve the problem (updating the hard SPL to v2.10 successfully, flashing many ROMs -not including Radio- successfully).
So, I can flash any ROM now but it must be without Radio, otherwise the flashing process will stuck on 11%.
try reading the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
More than 2 days and I couldn't success to bring the Radio back??!! I think I've really lost my device.
FirasKB,
What steps exactly have you taken to solve the problem? Try and outline them here; that will help people on here to identify what else you need to do to bring the device back to life.
WB
FirasKB said:
More than 2 days and I couldn't success to bring the Radio back??!! I think I've really lost my device.
Click to expand...
Click to collapse
Schap´s Rom has NO Radio. Flash this one BUT u must have HardSPL
http://forum.xda-developers.com/showthread.php?t=348435&highlight=Radio
wacky.banana said:
FirasKB,
What steps exactly have you taken to solve the problem? Try and outline them here; that will help people on here to identify what else you need to do to bring the device back to life.
WB
Click to expand...
Click to collapse
wacky.banana,
As I wrote above, my problem still not solved and my device still running with (No GSM).
I've done the following:
- Updating the ROM (O.S only as the device not accepting any Radio ROM)
- Updating the SPL to Version 7.
- Trying to update the radio (separately) but I didn't success??!!
It seems there is no solution to fix this problem???!!!
Abo Forat said:
Schap´s Rom has NO Radio. Flash this one BUT u must have HardSPL
http://forum.xda-developers.com/showthread.php?t=348435&highlight=Radio
Click to expand...
Click to collapse
No way, I tried it but my device can't accept any Radio version.
FirasKB said:
wacky.banana,
As I wrote above, my problem still not solved and my device still running with (No GSM).
I've done the following:
- Updating the ROM (O.S only as the device not accepting any Radio ROM)
- Updating the SPL to Version 7.
- Trying to update the radio (separately) but I didn't success??!!
It seems there is no solution to fix this problem???!!!
Click to expand...
Click to collapse
Frisk,
Read this thread and try the solutions metioned in it. It tells you what error 262 is all about....http://forum.xda-developers.com/archive/index.php/t-298516.html
Cheers
WB
wacky.banana said:
Frisk,
Read this thread and try the solutions metioned in it. It tells you what error 262 is all about....http://forum.xda-developers.com/archive/index.php/t-298516.html
Cheers
WB
Click to expand...
Click to collapse
Unfortunately, but that's also didn't help, because the main problem now is how to install the Radio on the device??!!
The device is not accepting the Radio installation at all, NO WAY....
Error Flashing: Unlocked T-Mobile Dash with all possible XDA 6.1 Downloads
I run into this same ERROR irrespective of which download I use. Any thoughts?
Image Version: 1.22.531.6
Upgrade To Versions tried with Ricky / Kavana etc Brazil Portuguese etc:
1.33.424.2
1.33.424.2
RESULT:
The phone shows the Red Green Blue Band with little white at bottom screen. Then phone and PC show 3%. Then it goes to the following:
Error [270]: Update Error
The image file is corrupted. Please check your update utility.
Need a little more info
Read the Stickies but you need to application unlock your phone
Probably going to have to put in bootloader mode first reflash to your official Rom then App Unlock then follow 6.1 upgrade guide.
http://wiki.xda-developers.com/index.php?pagename=HTC_Excalibur_WM61
Sim unlock is different than application unlocking
never heard of the problem. EVER. whats error 270?
gixxum said:
never heard of the problem. EVER. whats error 270?
Click to expand...
Click to collapse
Use the search
stylez said:
Use the search
Click to expand...
Click to collapse
all i could find was 100000000 posts about error 270. so, what do i do?
gixxum said:
all i could find was 100000000 posts about error 270. so, what do i do?
Click to expand...
Click to collapse
Whatever you do don't click the top one your dash will explode
I get the fundamentals of Simunlock v/s AppUnlock etc.
It was SimUnlocked using Unlock code I had got from T-Mobile.
1. It already has the latest Official ROM version on it (i.e. I tried doing it with the latest T-Mobile) and it shows the version I have is the same.
Do I need to reflash it with the ROM that is aleady present on my DASH? Is it worth trying that?
2. Now the step called AppUnlock? Which tool should I use given that I would have the T-Mobile Carrier 6.1 ROM on it (either already or reflash with T-Mobile 6.1 AGAIN)
3. After AppUnlock should I go for the FLASHing guide? Which one would that be?
if you search hard u can find it
sda unlock then put that file in your phone open it
then reboot
then just install it should be all center buttons if your using rickys rom
that's all
to add what are u talking about tmobile 6.1 there is none available from tmobile 6.1
crashnburnMDA said:
I get the fundamentals of Simunlock v/s AppUnlock etc.
It was SimUnlocked using Unlock code I had got from T-Mobile.
1. It already has the latest Official ROM version on it (i.e. I tried doing it with the latest T-Mobile) and it shows the version I have is the same.
Do I need to reflash it with the ROM that is aleady present on my DASH? Is it worth trying that?
2. Now the step called AppUnlock? Which tool should I use given that I would have the T-Mobile Carrier 6.1 ROM on it (either already or reflash with T-Mobile 6.1 AGAIN)
3. After AppUnlock should I go for the FLASHing guide? Which one would that be?
Click to expand...
Click to collapse
a. follow EXACTLY what the guide says. download the files it tells you to (and provides links to). thats why i put PICTURES so you wont have to ask. get the app unlocker from the guide....no need to install anything on the phone..just plug it in via activesync and run the app unlock...it will look like the pictures...then reboot and continue the install
b. tmobile has no 6.1 rom.
gixxum said:
a. follow EXACTLY what the guide says. download the files it tells you to (and provides links to). thats why i put PICTURES so you wont have to ask. get the app unlocker from the guide....no need to install anything on the phone..just plug it in via activesync and run the app unlock...it will look like the pictures...then reboot and continue the install
b. tmobile has no 6.1 rom.
Click to expand...
Click to collapse
Haha no I thought tmobile had the 7.1 rom... haha just messing...
The only thing I can access on my Dash is the Bootloader. It is the T-Mobile branded Excalibur.
ONBL and SPL say 1.22.0000
Which ROM do I need to flash to get my Dash back?
I have tried the original ROMs and I get ERROR[300]: INVALID UPDATE TOOL
This Update Utility cannot be used for your PDA Phone. Please get newer Update Utility.
I was told by someone having this similar problem that flashing the original ROM fixed it, but I have had no luck so far.
OxR said:
The only thing I can access on my Dash is the Bootloader. It is the T-Mobile branded Excalibur.
ONBL and SPL say 1.22.0000
Which ROM do I need to flash to get my Dash back?
I have tried the original ROMs and I get ERROR[300]: INVALID UPDATE TOOL
This Update Utility cannot be used for your PDA Phone. Please get newer Update Utility.
I was told by someone having this similar problem that flashing the original ROM fixed it, but I have had no luck so far.
Click to expand...
Click to collapse
Have a look here:
http://forum.xda-developers.com/showthread.php?t=415225
Then choose your desired ROM to upgrade or downgrade
Good luck,
I get the same error with those ROMs.
did you try the .exe upgrade, worked fine for me
skaroger867 said:
did you try the .exe upgrade, worked fine for me
Click to expand...
Click to collapse
If it is in the official ROMs thread then yes, I tried it.
If not, could you give me a link?
Since there is no resource thread for this variant, I decided to create this one for the little community using this on XDA.
First of all, some warnings:
- Custom ROM and kernel do not work so do not attempt to try, it would just be a waste of time. Even if the ROM work, you will not have signal and there will be bug. So if you are not a ROM developer looking to support this variant, I suggest staying away.
- Debranding to unlocked/international variant is not possible. At best you will only soft brick, at worst you could brick your device.
- Since there are no RUU and none will be available in the near future, always have a stock back up at the ready.
- Root is only achievable with Sunshine through temproot and S-Off. So if you are not prepare to pay or for the risk, stay away as well.
Now, on to the main disk
Here is the link to the most recent OTA:
http://fotadl-az.htc.com/secure/OTA...1.28.970.6_release_485495lwhgdc5g85j4uwwh.zip
Contain in here is the stock recovery and other image if you need.
Guide to root. As mention above, will S-off your phone.
Guide to receive OTA after root.
can i get the radio.img for this device on au? im trying to get my US unlocked edition to work on au, i flashed verizon radios, and it does work, but i only get 3g data.
Quadrider10 said:
can i get the radio.img for this device on au? im trying to get my US unlocked edition to work on au, i flashed verizon radios, and it does work, but i only get 3g data.
Click to expand...
Click to collapse
Extract from firmware.zip and see. Report back.
The problem is I can't find and firmware for the Japan variet.
If the first post is the au OTA, it has radio.img
andybones said:
If the first post is the au OTA, it has radio.img
Click to expand...
Click to collapse
i tried it, but for some reason, it did not work...
I think it can be converted to Unlocked one after s-off, you may try
Quadrider10 said:
i tried it, but for some reason, it did not work...
Click to expand...
Click to collapse
What was the error?
No signal, or unable to get the radio.img from post1
No signal or data. For some of reason, the only radio that works is Verizon's. but I only get 3G data and it registers as no signal even though I have data, make calls and texts.
thanks so much, im from japan and my phone was root, im looking for this.
Can you upload the stock room off AU or stock back up here?
Quadrider10 said:
No signal or data. For some of reason, the only radio that works is Verizon's. but I only get 3G data and it registers as no signal even though I have data, make calls and texts.
Click to expand...
Click to collapse
Did you try wiping modems?
In download mode using ADB issue the commands:
Fastboot erase modemst1
Fastboot erase modemst2
Fixed my 3g issue. But this was from a Different issue.
Won't hurt to try..
Thanks. I'll give that a shot
those ADB command will not work. says failed partition erase not supported
EDIT: nvm i ran it in the bootloader and they seemed to work, however i am still not receiving signal on my 10 with us unlocked. it seems the only way to receive the KDDI au signal at all is to flash verizon's radio.
au has a funky system authenticating the phone with an ID system which is embedded within the stock ROM. I don't know whether it is possible to have signal with an unlocked model. That's the only thing keeping me from flashing a custom ROM on the phone. Maybe some ROM developer could take a look into that?
I did notice that if u flash the Verizon radio, then install a ROM while choosing unlocked dev edition, as the provider, you get signal and bars, but this breaks my 5ghz wifi capability for some reason and I only received 3g at speeds of 1.5mpbs download. So not really worth it. Is there an ruu for the Japanese HTV32 out there that would flash in my 10?
Quadrider10 said:
I did notice that if u flash the Verizon radio, then install a ROM while choosing unlocked dev edition, as the provider, you get signal and bars, but this breaks my 5ghz wifi capability for some reason and I only received 3g at speeds of 1.5mpbs download. So not really worth it. Is there an ruu for the Japanese HTV32 out there that would flash in my 10?
Click to expand...
Click to collapse
There are no RUU yet, have you tried flashing the radio from the OTA?
nerodarknight said:
There are no RUU yet, have you tried flashing the radio from the OTA?
Click to expand...
Click to collapse
yes, it didnt work... lol
Can some one upload a stock or stock backup for HTC 10 Japan please!
http://hanpenblog.com/4640/
Good news guys, I just found this website with links to download the RUU for the original firmware and all OTA up to date if anyone needs them.
nerodarknight said:
http://hanpenblog.com/4640/
Good news guys, I just found this website with links to download the RUU for the original firmware and all OTA up to date if anyone needs them.
Click to expand...
Click to collapse
Did you in japan and did you success with it?
Anyway, check your inbox. thanks !
For starters, I have an AT&T HTC M9. I unlocked the bootloader, and after a while, got TWRP 3.0.2.0 installed as the custom recovery. I decided to flash ARHD, since that's my personal favorite that I've used on my M7 and M8. After flashing and clearing cache, the phone optimizes apps, reboots, and then stays at the HTC screen for a bit. Finally, the screen will turn off as if it's booted in. I could then wake the device and adjust volume and such, but I still had the HTC logo covering what would be the UI. After a bit more time, the setup menu finally came up. I couldn't set up wifi, as it got stuck on the "connecting" screen. Wiped, re-flashed ARHD. Same thing. Finally got through the setup, and I had no service. What am I doing wrong? Do I need to install a corresponding firmware or something? This happens to me every time. Also the M9 had Android 6.0 with Sense 7.0, for the record.
Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.
shivadow said:
Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.
Click to expand...
Click to collapse
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?
manlavi95 said:
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?
Click to expand...
Click to collapse
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Edit: I've got an RUU that I was thinking of using and then just rooting the stock ROM and then going about my day. I'd be ok with that if I knew for a fact that it wouldn't remove TWRP. That and I was looking forward to the ARHD battery life.
manlavi95 said:
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Click to expand...
Click to collapse
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).
Flippy498 said:
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).
Click to expand...
Click to collapse
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?
manlavi95 said:
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?
Click to expand...
Click to collapse
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.
Flippy498 said:
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.
Click to expand...
Click to collapse
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?
manlavi95 said:
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?
Click to expand...
Click to collapse
Based on my previous experiences with the M9 I'd say yes.
Flippy498 said:
Based on my previous experiences with the M9 I'd say yes.
Click to expand...
Click to collapse
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.
manlavi95 said:
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.
Click to expand...
Click to collapse
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.
Flippy498 said:
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.
Click to expand...
Click to collapse
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Another edit: I also don't see SuperSU anywhere, and that's confusing me just a bit.
manlavi95 said:
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Click to expand...
Click to collapse
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.
Flippy498 said:
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.
Click to expand...
Click to collapse
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.
manlavi95 said:
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.
Click to expand...
Click to collapse
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.
Flippy498 said:
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.
Click to expand...
Click to collapse
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.
manlavi95 said:
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.
Click to expand...
Click to collapse
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)
Flippy498 said:
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)
Click to expand...
Click to collapse
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.
manlavi95 said:
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.
Click to expand...
Click to collapse
Flash it like any other rom. The aroma installer is actually pretty straight forward. Choose default since there is nor AT&T specific installation.
Just make sure that you read what it wants you to do. Sometimes it asks which apps you want to install and sometimes which you want to uninstall.