Related
Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant
Tritan84 said:
Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant
Click to expand...
Click to collapse
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.
xunholyx said:
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.
Click to expand...
Click to collapse
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?
Tritan84 said:
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?
Click to expand...
Click to collapse
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
The ARHD thread does recommend a full wipe with the non-matching firmware/ROM base though.
xunholyx said:
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
Click to expand...
Click to collapse
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?
Tritan84 said:
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?
Click to expand...
Click to collapse
Probably because of the conversion from Verizon to T-Mo.
xunholyx said:
Probably because of the conversion from Verizon to T-Mo.
Click to expand...
Click to collapse
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help
Tritan84 said:
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help
Click to expand...
Click to collapse
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.
xunholyx said:
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.
Click to expand...
Click to collapse
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up
Tritan84 said:
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up
Click to expand...
Click to collapse
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?
possible progress?? I wasn't in the correct file to fastboot flash files. I moved the unlock code download to the correct file as flashboot, then flashed it. It says "unlock token check successfully." but now it seems the phone is stuck in white htc screen. Is it ok to power down the phone when in this screen? maybe loading the software from new ROM?
so I went ahead and powered down the phone. Still S-off. Now has UNLOCKED banner, but behaving the same. Stuck in bootloader loop. Won't allow me to get into recovery
Tritan84 said:
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?
Click to expand...
Click to collapse
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.
where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do
xunholyx said:
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.
Click to expand...
Click to collapse
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.
nitephlight said:
where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do
Click to expand...
Click to collapse
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.
Tritan84 said:
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.
Click to expand...
Click to collapse
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
Tritan84 said:
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.
Click to expand...
Click to collapse
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.
xunholyx said:
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.
Click to expand...
Click to collapse
I think you're right. I've tried to search how to change modelid via fastboot since I can't boot the phone to run adb, but all the tutorials seem to be based on using adb. Is their a way to change via fastboot only?
SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.
Tritan84 said:
SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.
Click to expand...
Click to collapse
Cool. I glad you got everything sorted. :good:
Yeah and the guy from Germany doesn't have the time to look into this anyway...
When I first got my HTC LTE was working fine then it suddenly stopped. I called T-Mobile who was clueless, so I popped the sim back into my S7 Edge and Nexus 6P age LTE worked perfectly. I decided to try unlocking s-off etc to flash a more current firmware since mine was on a really old one. I flagged 1.30xx stock then LeeDroid rom being sure to not decrypt data during the process. LTE still won't won't, I'm only getting HSPA+ which sucks. I have another sim card I could activate, but I want to know if there's another way to fix this? My APN seems fine, as does the preferred radio mode. Any suggestions/additional troubleshooting that I can do before sending the phone back
Update:
Here are some videos I made showing the issue:
Part 1
Part 2
I will add another one using the stock ROM to further prove the issue exists on both the unlocked firmware, and T-Mobile one.
You root your phone, mess it up and then send it back? Kinda messed up.
Did you try flashing the latest modem?
iamtimmah said:
You root your phone, mess it up and then send it back? Kinda messed up.
Click to expand...
Click to collapse
He said this happened before, and he tried rooted and flashing a ROM to see if it made a difference.
iamtimmah said:
You root your phone, mess it up and then send it back? Kinda messed up.
Click to expand...
Click to collapse
No, I stated the issue was there before then. I only unlocked it and flashed updated firmware in an attempt to fix the issue which it didn't. Clearly we all need to read thoroughly before responding to an OP so we don't look arrogant in the end.
Now, on another note I mentioned this issue was already present from the moment I started using the phone 100% stock. It will sometimes still get LTE, but it only sticks for 10-30 seconds then drops to H/H+ immediately. My S7 Edge and Nexus 6P do not have this issue whatsoever therefore I'm certain something with the firmware is not right.
geoff5093 said:
Did you try flashing the latest modem?
He said this happened before, and he tried rooted and flashing a ROM to see if it made a difference.
Click to expand...
Click to collapse
Thank you, for reading the OP , and no I don't have just the modem files, although I do have the RUU so I know it's in there
Pilz said:
When I first got my HTC LTE was working fine then it suddenly stopped. I called T-Mobile who was clueless, so I popped the sim back into my S7 Edge and Nexus 6P age LTE worked perfectly. I decided to try unlocking s-off etc to flash a more current firmware since mine was on a really old one. I flagged 1.30xx stock then LeeDroid rom being sure to not decrypt data during the process. LTE still won't won't, I'm only getting HSPA+ which sucks. I have another sim card I could activate, but I want to know if there's another way to fix this? My APN seems fine, as does the preferred radio mode. Any suggestions/additional troubleshooting that I can do before sending the phone back
Click to expand...
Click to collapse
Did you try 1.53 us unlocked ruu that's worth a try
bbell101584 said:
Did you try 1.53 us unlocked ruu that's worth a try
Click to expand...
Click to collapse
No, I can't get it to flash, but I'm going to try another method for updating it to that version
Mine has been extremely inconsistent in sticking to LTE. Sometimes I have to force it to LTE only and then when I switch back to GSM/WCDMA/LTE auto, it ****s the bed for a few minutes before correcting itself.
Pilz said:
No, I can't get it to flash, but I'm going to try another method for updating it to that version
Click to expand...
Click to collapse
Did you try downloading the ruu.exe on the computer and then running it as administrator also make sure you have either changed your cid to the US unlocked one or to supercid I used the exe version of the ruu it went fine on my end I hope you get your situation worked out
I don't know your phone model, but since you are in the US. I would suggest you run US unlocked RUU for eliminating any software issues.
If you have an unlocked device, then you can simply download from @Behold's thread about us unlocked RUU.
If you have a T-mobile device, I would suggest you to get s-off and then run RUU.
Send back your modified phone is likely the least preferred option to do/recommend.
bbell101584 said:
Did you try downloading the ruu.exe on the computer and then running it as administrator also make sure you have either changed your cid to the US unlocked one or to supercid I used the exe version of the ruu it went fine on my end I hope you get your situation worked out
Click to expand...
Click to collapse
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
frankcck said:
I don't know your phone model, but since you are in the US. I would suggest you run US unlocked RUU for eliminating any software issues.
If you have an unlocked device, then you can simply download from @Behold's thread about us unlocked RUU.
If you have a T-mobile device, I would suggest you to get s-off and then run RUU.
Send back your modified phone is likely the least preferred option to do/recommend.
Click to expand...
Click to collapse
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.
Pilz said:
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.
Click to expand...
Click to collapse
Boot into download mode and run RUU again.
frankcck said:
Boot into download mode and run RUU again.
Click to expand...
Click to collapse
That's exactly what I did, and I just confirmed the error code was "155 unknown error"
Pilz said:
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.
Click to expand...
Click to collapse
Did you right click the ruu.exe and choose to run as administrative that's the only thing else I can say maybe a more experienced person can help you further sorry
---------- Post added at 02:10 PM ---------- Previous post was at 02:09 PM ----------
Redownload the ruu or just try from a whole different computer if you have access to one
bbell101584 said:
Did you right click the ruu.exe and choose to run as administrative that's the only thing else I can say maybe a more experienced person can help you further sorry
Click to expand...
Click to collapse
Yep, following the instructions to the t (so to speak), it ran fine, booted into whatever that weird screen is with the % on it then after about 15 seconds gave me the error
I just gave the extSD method again, now it is saying
Code:
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 22 RU_HEADER_ERROR
Pilz said:
That's exactly what I did, and I just confirmed the error code was "155 unknown error"
Click to expand...
Click to collapse
I did not boot into download mode. Left it on the home screen, Just made sure USB debugging was on. The RUU handled everything after that.
Quick update:
I changed my CID to 111111 and it flashed via the RUU .exe file (surprisingly). I still cannot get LTE other than a ran moment where it might connect for a second before dropping back to H+. I even made a new APN (copied from my S7 Edge) and it still won't get LTE. Could this be some bizarre sim issue despite it working on every other phone I own (4 other phones work fine with LTE and my sim)?
Pilz said:
Quick update:
I changed my CID to 111111 and it flashed via the RUU .exe file (surprisingly). I still cannot get LTE other than a ran moment where it might connect for a second before dropping back to H+. I even made a new APN (copied from my S7 Edge) and it still won't get LTE. Could this be some bizarre sim issue despite it working on every other phone I own (4 other phones work fine with LTE and my sim)?
Click to expand...
Click to collapse
Have them re register the device on the network? The US unlocked base should work fine on TMOUS, I know as I have used it and both LTE, VoLTE, and WiFi calling fully work.
Mikee4fun said:
Looks like a sim issue. Try re seating the sim and if that does not work have TMO give you another sim from the store.
Click to expand...
Click to collapse
I have another sim, and I've reinserted it s few times now without success. I might call them and activate the other sim. It's just odd how it works flawlessly with LTE on every phone but this one.
old m9 ended up kicking the bucket sorta (usb died, so no way to charge the phone) so i bought a used one from swappa. it came with the latest ruu flashed, but i decided to reflash again to make sure it was totally clean (RUU_HIMA_UL_M60_SENSE70_ATT_MR_Cingular_US_3.38.502.12.exe). it went fine and so i began the process of unlocking it and flashing recovery (twrp 3.0.2.0) and flashing a rom (arhd 20 which is marshmallow) and titanium backuping back into shape. it unlocked and flashed recovery fine, however when i flashed the rom and did the first boot, i noticed i had no signal even though the stock rom had 4 bars of lte. it was also very laggy and had issues with crashing apps and for some reason still had at&t bloatware even though i did a dalvik/cache/system/data wipe beforehand and then a data wipe during the install and was missing inbuilt htc apps like internet. in the settings it shows that the imei, baseband, and other things related are all "unknown". i researched and came across a fix where you flash back your stock boot image, and it worked, except it would fail to boot after the first reboot. so that was useless.
i decided to try flashing arhd 14 (lollipop) because its what my old m9 had since forever and never gave me an issue. surprisingly, it actually installed and ran just fine even though the phone is on marshmallow firmware, as well as much quicker and smoother than arhd 20. however, i have the same issue. no signal, and imei and stuff "unknown". it does show my imei in download mode so i know the phone itself didnt forget it somehow. i have no idea what is going on here because ive literally never had this problem with any phone, even with my old m9 and i absolutely refuse to use a stock rom and have to manually deal with all of the bloatware especially with selinux making anything remotely "dangerous" an excessive hassle. can someone help me figure out this unnecessary pita?
this is what is shown in the download mode screen:
*** UNLOCKED ***
HTC_HIMAULATT PVT S-ON
LK-1.0.0.0000
RADIO-01.01_U11440801_96.01.51207A_F
OPENDSP-15.6.1.00522.8994_1026
OS-3.38.502.12
Did You Get Any Solutions ? :crying:
nope.
daktah said:
nope.
Click to expand...
Click to collapse
Can you please give me the link of stock img which helped you to get signal at first boot ? i am running on viper marshmallow rom.advance thanks to you
---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------
and yes exact same problem is also happening with me It shows imei in fastboot,but In the settings and phone info,Imei shows unknown and no cell signals .I Just Bought THe phone 2 Days ago Happened after flashing the Ar Hd Rom
i used the boot from the nandroid i made of the stock ruu image before i tried to install arhd
I know I sound stupid, but actually I did'nt take any backup before flashing would you please upload it to somewhere and give me a link. It would mean a lot to me, thanks
daktah said:
i used the boot from the nandroid i made of the stock ruu image before i tried to install arhd
Click to expand...
Click to collapse
Are you S-OFF? if so, are you sure that you used the correct firmware. Never had this issue myself, but am remembering from the days on the M9 that such an issue could occur if a wrong firmware is flashed.
Another chance could be the following one: if your RUU didn't download correctly it might be damaged and thus have caused the problem. This may be the case as you're missing stock Apps after flash. Have you checked if the md5 of the downloaded file is correct.
Edit: report back if it helped.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
Are you S-OFF? if so, are you sure that you used the correct firmware. Never had this issue myself, but am remembering from the days on the M9 that such an issue could occur if a wrong firmware is flashed.
Another chance could be the following one: if your RUU didn't download correctly it might be damaged and thus have caused the problem. This may be the case as you're missing stock Apps after flash. Have you checked if the md5 of the downloaded file is correct.
Edit: report back if it helped.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
Yeah turns out the latest arhd is made for 3.35 and I'm on 3.38, so that's why it's all jacked up. And of course there is no way to "downgrade" (see: upgrade) to a lower firmware without $25 s off. Pretty ridiculous I have to pay just to s off so I can put my phone on an older software that works better because of "security" (see: money).
daktah said:
Yeah turns out the latest arhd is made for 3.35 and I'm on 3.38, so that's why it's all jacked up. And of course there is no way to "downgrade" (see: upgrade) to a lower firmware without $25 s off. Pretty ridiculous I have to pay just to s off so I can put my phone on an older software that works better because of "security" (see: money).
Click to expand...
Click to collapse
I still think something went wrong when flashing RUU. A 3.35 based ROM shouldn't jack up anything, as long as your firmware is even a later one than the ROM base. Btw 25 bucks are well invested regarding all the work they do, but it's the wrong place to discuss. Did you check if the RUU downloaded correctly and the md5 after download still is the same as given in the dl link. Missing stock Apps after flashing an RUU are a major indicator for a bad download, and if firmware parts where missing in this download as well, you'll end up just as you'd described in your opening post.
Sent from my htc_pmeuhl using XDA Labs
I used the ruu 2 or 3 times and it worked fine every time and the stock rom runs just fine. It's when trying to flash the rom it doesn't work, and I used one I downloaded from my computer, from my phone, and one I already had on my SD and they all ended up with the same result.
5m4r7ph0n36uru said:
A 3.35 based ROM shouldn't jack up anything, as long as your firmware is even a later one than the ROM base.
Click to expand...
Click to collapse
It actually does. That's why thicklizard made his custom kernel. The 3.3x firmware versions for SKUs which skipped the 3.35 version are not compatible with 3.35 roms unless that kernel gets flashed.
Edit: I just read that the mono-revisited kernel is only for AOSP roms. I'm sorry but it seems like I don't have a solution for sense roms.
5m4r7ph0n36uru said:
Missing stock Apps after flashing an RUU are a major indicator for a bad download, and if firmware parts where missing in this download as well, you'll end up just as you'd described in your opening post.
Click to expand...
Click to collapse
Doesn't daktah say in the OP that he was missing those apps after flashing ARHD20? I never used that rom but it sounds like they got uninstalled during the installation. Does ARHD have an aroma installer like the Viper rom does where you can select which apps to install or not to install?
Sent from my HTC One S using XDA Labs
Flippy498 said:
Doesn't daktah say in the OP that he was missing those apps after flashing ARHD20? I never used that rom but it sounds like they got uninstalled during the installation. Does ARHD have an aroma installer like the Viper rom does where you can select which apps to install or not to install?
Click to expand...
Click to collapse
Thanks for the clarification mate.
Didn't remember this one.. guess it's already to long since I used my M9. I'm not sure if he tried to state exactly what I quoted from your post, cause he jumps from RUUing right to the flash of ARHD. never used it myself, this I don't know if it comes with an Aroma Installer at all. Either way it would be interesting to know what happens if he just boots into his stock ROM, to make sure the cause isn't a bad download of the RUU. Feel free to correct me if I'm mistaken
Sent from my htc_pmeuhl using XDA Labs
In theory you're right but I guess we both missed the post located directly above mine.
Sent from my HTC One S using XDA Labs
We did indeed. Blind I've become, as Yoda would state now.
Sent from my htc_pmeuhl using XDA Labs
So I managed to fix it... By replacing the USB/aux board in my phone. Only cost 10 bucks for a new one . However now i have a problem where my phone will not charge at full speed and will actually give me the "using too much power to charge" message when doing a titanium backup even on the stock charger. The battery was at dead flat 0 for like 5 days before I fixed it, so do I need to replace it or is there something else I can do to fix it? When it's full it holds a charge for as long as it did before, just charging is not working correctly it seems.
i have nandroid backup of 3.38.841.6 let me know if i can be any help, i"ll upload it on mediafire and give you link,
btw i had the same problem yesterday, i flashed my nandroid backup and things went smooth
i got no imei no network after flash AEHD20, so i flash back boot img from backup, everything fine but without root. i down load twrp backup from http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698, select the correct CID match your phone. my CID is HTC__044 with 3.42.708.3. After download backup unzip the file, done once backup boot file, copy the file from download overwrite your backup, then restore the file from backup. good luck. don't wipe!!!!!!
17/09/16
I install Viber one still no imei, restore back up boot, imei back but no root, install super su 2.65 everything fine got root and imei.
Install twrp 2.8.5.0 first then update to twrp 3.0.2.0
Hey arcslt18,
arcslt18 said:
i have nandroid backup of 3.38.841.6 let me know if i can be any help, i"ll upload it on mediafire and give you link,
btw i had the same problem yesterday, i flashed my nandroid backup and things went smooth
Click to expand...
Click to collapse
Do you still have that nandroid backup handy?
I think i do, Currently at work. i'll contact you as soon as i get my hands on it.
I've had this quite a lot of times but flashing a different kernel usually sorts of out right away
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 !
After successfully converted to US Unlocked, Nougat, I tried to revert back by flashing firmware.zip and TWRP backup. But after the first time flashing the firmware.zip, I tried to reboot to download mode to complete the 2nd flashing but the phone just shut down. Now I cannot turn it on anymore and it does not even register charge from the charger. Have I bricked it? My is Japan variant, S-Off, bootloader relocked
nerodarknight said:
After successfully converted to US Unlocked, Nougat, I tried to revert back by flashing firmware.zip and TWRP backup. But after the first time flashing the firmware.zip, I tried to reboot to download mode to complete the 2nd flashing but the phone just shut down. Now I cannot turn it on anymore and it does not even register charge from the charger. Have I bricked it? My is Japan variant, S-Off, bootloader relocked
Click to expand...
Click to collapse
The correct way to revert would be to change the CID back then flashing the corresponding firmware etc. If you tried flashing the firmware for Japan but still had the CID set to us unlocked then yes you possibly bricked the phone.
I changed the cid back to Japan variant already, if the CID was not correct it wouldn't flash anyway. The problem is that the phone isn't receiving charge from the charger. I believe the phone would still hold a charge even if brick.
nerodarknight said:
I changed the cid back to Japan variant already, if the CID was not correct it wouldn't flash anyway. The problem is that the phone isn't receiving charge from the charger. I believe the phone would still hold a charge even if brick.
Click to expand...
Click to collapse
Sounds like a big hairy nasty brick alright.
comstockload said:
Sounds like a big hairy nasty brick alright.
Click to expand...
Click to collapse
Gonna bring it to the carrier, gonna see what they are going to do, hopefully can have it replaced
Same happened to me. Had to replace using insurance
nerodarknight said:
Gonna bring it to the carrier, gonna see what they are going to do, hopefully can have it replaced
Click to expand...
Click to collapse
may I ask what firmware you flashed to revert back?
If you flash an incremental one it will brick. need to flash a full/combined firmware from @Sneakyghosts thread
Same thing happened to me this morning, went to flash a FW and boom, brick. Not sure what I did wrong but will not do it anymore lol.
I've sent it away to HTC for repair. Has anyone else went this route and know what to expect?
I'm worried they will get it back on and see that it's S-OFF and a different CID than what it should be. I have a Sprint variant.
FlowingAway said:
Same thing happened to me this morning, went to flash a FW and boom, brick. Not sure what I did wrong but will not do it anymore lol.
I've sent it away to HTC for repair. Has anyone else went this route and know what to expect?
I'm worried they will get it back on and see that it's S-OFF and a different CID than what it should be. I have a Sprint variant.
Click to expand...
Click to collapse
theres no sprint nougat firmware, so you flashed an GSM firmware on your CDMA sprint? Not good.
This is why I take as few risks as possible when flashing. I'm still on a MM rom and will be until we get an official TWRP. And I only flash firmware/roms made for my device. Just my $0.02. Keep the change.
.
j to the 4n said:
theres no sprint nougat firmware, so you flashed an GSM firmware on your CDMA sprint? Not good.
Click to expand...
Click to collapse
I did it once before. I removed all radio img files and any other img files that the Sprint firmware doesn't contain. I think what did me in was flashing it while on an official Sprint Marshmallow ROM. The other time I did it I was already on a Nougat ROM. Might've been Viper or CM 14 a few days ago.
Learned my lessons haha. One question tho, what if I were to flash a RUU, matching CID and MID, would it be ok?
nerodarknight said:
Learned my lessons haha. One question tho, what if I were to flash a RUU, matching CID and MID, would it be ok?
Click to expand...
Click to collapse
I am only going to tell you the safest way because I don't want you to brick another phone. Assuming you're already on a custom rom:
1. Download the N ruu.exe for your device from HTC. Right now all they have is N for the US unlocked. The rest should be available in Jan. It won't kill anyone to wait that long.
2. Run the executable on your computer and follow the easy prompts. This will perfectly install the stock N rom.
3. Flash the official TWRP via fastboot command.
4. Use TWRP to format your data partition then flash the custom N rom of your choice. SuperSu should be included with the rom.
Finished. Yes, there are all kinds of things you can do instead. I use my phone for work too so I ain't going there.