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...
Please forgive me if this has been answered elsewhere, i searched but what little i found didnt seem to helpful (maybe im just confused) i want to flash the new Viper rom but it says i need 4.4.4 firmware, my rooted htc only has 4.4.2. How do i update it? I am scared of bricking my new phone so could someone please explain it to me like i am stupid? I used the all_in_one_toolkit (wonderful program!) If it matters..... also i flashed twrp cause there was no OTA att update found (checked twice)
Dragonmaster0430 said:
Please forgive me if this has been answered elsewhere, i searched but what little i found didnt seem to helpful (maybe im just confused) i want to flash the new Viper rom but it says i need 4.4.4 firmware, my rooted htc only has 4.4.2. How do i update it? I am scared of bricking my new phone so could someone please explain it to me like i am stupid? I used the all_in_one_toolkit (wonderful program!) If it matters.....
Click to expand...
Click to collapse
1) Mods won't like you posting a question in the Dev thread... there are specific sections (general, firmware, etc) where you can post it...
2)Considering that your phone is practically new, if you only rooted it and haven't installed a custom recovery, you will be able to update your firmare (OTA) through the built in upgrade process on your phone. Once, that is done, root your phone and install a custom recovery like TWRP.
good luck
Deathsting_50cal said:
1) Mods won't like you posting a question in the Dev thread... there are specific sections (general, firmware, etc) where you can post it...
2)Considering that your phone is practically new, if you only rooted it and haven't installed a custom recovery, you will be able to update your firmare (OTA) through the built in upgrade process on your phone. Once, that is done, root your phone and install a custom recovery like TWRP.
good luck
Click to expand...
Click to collapse
1. SH!t sorry! I didn't realize ?
2. ...i already flashed TWRP,cause i checked twice for a OTA before hand and therr was no update found
Anyone got any ideas?
Dragonmaster0430 said:
Please forgive me if this has been answered elsewhere, i searched but what little i found didnt seem to helpful (maybe im just confused) i want to flash the new Viper rom but it says i need 4.4.4 firmware, my rooted htc only has 4.4.2. How do i update it? I am scared of bricking my new phone so could someone please explain it to me like i am stupid? I used the all_in_one_toolkit (wonderful program!) If it matters..... also i flashed twrp cause there was no OTA att update found (checked twice)
Click to expand...
Click to collapse
Yes, I sure do.
First of all, if you want the newest ViperOne, you'll want 5.0.1 firmware, at least.
Hook up to you PC. Get into ADB/fastboot, and issue the command fastboot getvar all.
Post the readout here, and I, or someone else, will point you in the proper direction to update your firmware.
Please make sure to delete the serial# and IMEI from the readout. Never post those in a public forum.
xunholyx said:
Yes, I sure do.
First of all, if you want the newest ViperOne, you'll want 5.0.1 firmware, at least.
Hook up to you PC. Get into ADB/fastboot, and issue the command fastboot getvar all.
Post the readout here, and I, or someone else, will point you in the proper direction to update your firmware.
Please make sure to delete the serial# and IMEI from the readout. Never post those in a public forum.
Click to expand...
Click to collapse
Ok sure!....how do I issue a command?
Dragonmaster0430 said:
Ok sure!....how do I issue a command?
Click to expand...
Click to collapse
Have you never used ADB or fastboot before?
Okay. This will update your firmware. Backup anything important to you, because this will wipe your phone.
Go here: http://www.htc.com/us/support/htc-one-att/news/
Scroll down to where it says "Manual system update instructions". Read what it says, then click the download link at the bottom.
xunholyx said:
Have you never used ADB or fastboot before?
Okay. This will update your firmware. Backup anything important to you, because this will wipe your phone.
Go here: http://www.htc.com/us/support/htc-one-att/news/
Scroll down to where it says "Manual system update instructions". Read what it says, then click the download link at the bottom.
Click to expand...
Click to collapse
Not by itself, i dont think so anyways... I just followed a youtube vid on how to use the all-in-one-tool kit program... I figured less room for error risk?
Thank you for the link! Will have to reroot and unlock it after the update and stuff like that?
Dragonmaster0430 said:
Not by itself, i dont think so anyways... I just followed a youtube vid on how to use the all-in-one-tool kit program... I figured less room for error risk?
Thank you for the link! Will have to reroot and unlock it after the update and stuff like that?
Click to expand...
Click to collapse
Yes, but that's easy. Unlock your bootloader, flash TWRP, and flash a rooted ROM, such as ViperOne.
Also, I recommend not using one click toolkit methods. They often cause problems, plus doing it manually is easy and gives you an introduction to ADB and fastboot, making it less intimidating.
I don't know how to do it manually =( last time I tried I hard bricked my m7
Dragonmaster0430 said:
Not by itself, i dont think so anyways... I just followed a youtube vid on how to use the all-in-one-tool kit program... I figured less room for error risk?
Thank you for the link! Will have to reroot and unlock it after the update and stuff like that?
Click to expand...
Click to collapse
I get this when running the RUU from the link you sent...
Dragonmaster0430 said:
I get this when running the RUU from the link you sent...
Click to expand...
Click to collapse
what should i do now?
Dragonmaster0430 said:
I get this when running the RUU from the link you sent...
Click to expand...
Click to collapse
You need to re-lock your bootloader first if you are not S-Off.
Get back into fastboot and do fastboot oem lock, then leave your phone connected, and run the RUU again.
xunholyx said:
You need to re-lock your bootloader first if you are not S-Off.
Get back into fastboot and do fastboot oem lock, then leave your phone connected, and run the RUU again.
Click to expand...
Click to collapse
ok I did that my bootloader now shows
"*** TAMPERED***
*** RELOCKED ***
and i still am get the same error message that I posted the screenshot of before
Dragonmaster0430 said:
ok I did that my bootloader now shows
"*** TAMPERED***
*** RELOCKED ***
and i still am get the same error message that I posted the screenshot of before
Click to expand...
Click to collapse
You have an AT&T phone, right? That's what it says in the title. And that download link I gave you is from HTC's official website for the latest AT&T RUU.
xunholyx said:
You have an AT&T phone, right? That's what it says in the title. And that download link I gave you is from HTC's official website for the latest AT&T RUU.
Click to expand...
Click to collapse
Yup It is at&t
Dragonmaster0430 said:
Yup It is at&t
Click to expand...
Click to collapse
I don't know.
Maybe you don't have the drivers installed on your PC.
Go to Device Manager with your phone connected. You should see that your M8 is connected.
If you don't see it in Device Manager, download HTC Sync Manager and run it to install the drivers. After that, uninstall HTC Sync. It doesn't play nice with ADB and fastboot. The drivers will remain.
Then go to Device Manager and confirm that your phone is listed there when connected..
xunholyx said:
I don't know.
Maybe you don't have the drivers installed on your PC.
Go to Device Manager with your phone connected. You should see that your M8 is connected.
If you don't see it in Device Manager, download HTC Sync Manager and run it to install the drivers. After that, uninstall HTC Sync. It doesn't play nice with ADB and fastboot. The drivers will remain.
Then go to Device Manager and confirm that your phone is listed there when connected..
Click to expand...
Click to collapse
mine shows up under device manager as "MTP"
Dragonmaster0430 said:
mine shows up under device manager as "MTP"
Click to expand...
Click to collapse
I really don't know what's going on here.
I do know that if you were to go S-Off, updating your firmware is a piece of cake. You just need to find the firmware.zip and flash it.
xunholyx said:
I really don't know what's going on here.
I do know that if you were to go S-Off, updating your firmware is a piece of cake. You just need to find the firmware.zip and flash it.
Click to expand...
Click to collapse
how do i do all that?
Made a series of mistakes that led me to only have access to fastboot and recovery. It appears I'm capable of flashing things in fastboot. I can't access download mode at all (gives me an error saying it's unable to boot into download mode), which I believe you need in order to flash RUUs in the first place.
If anybody has a TWRP backup of system and boot that'd be awesome, but really need an img of download mode or a RUU or something to help me recover everything to normal. I am S-OFF and bootloader is unlocked.
Checked HTCdev and nothing was there for this device. All help appreciated.
How do you have fastboot when fastboot comands are done from download mode? Dont you have a stock system image that you made?
He means bootloader mode, the white screen. I think OP is SOL. That's why it's important to make backups, especially for exotic devices. I'm not sure if it's possible, but since he's s-off his best bet would be to convert to an unlocked or Verizon device if at all possible just to get the device working again and wait for either an ruu or backup.
If he is soffed he can flash an international ruu
Sent from my HTC 10 using XDA-Developers mobile app
Android The Greek said:
If he is soffed he can flash an international ruu
Click to expand...
Click to collapse
Cid and mid still needs to match
How did you go with this, OP? I just got the HTV32 (HTC10) here in Japan, and unlike previous HTC's I have owned here (Desire, M7), there seems to be no RUUs for Japan anywhere (or am I not looking hard enough...). Website HTCsoku seems very short on info on this model, and the former repository for all things HTC in Japan for modders and tinkerers, 'Scottish Vinegar', has disappeared. Will be getting Sunshine then flashing TWRP and SuperSU soon, but I always like to have the option of stock images, etc., handy, just in case things go tits up.
I remembered the case of failure to entering Download Mode in M9 which solution is flashing the hosd image (extract from firmware), you can give it a try
androg said:
How did you go with this, OP? I just got the HTV32 (HTC10) here in Japan, and unlike previous HTC's I have owned here (Desire, M7), there seems to be no RUUs for Japan anywhere (or am I not looking hard enough...). Website HTCsoku seems very short on info on this model, and the former repository for all things HTC in Japan for modders and tinkerers, 'Scottish Vinegar', has disappeared. Will be getting Sunshine then flashing TWRP and SuperSU soon, but I always like to have the option of stock images, etc., handy, just in case things go tits up.
Click to expand...
Click to collapse
Unfortunately was not able to get a hold of the stock RUU. I took my phone to my carrier and they gave me a new one free of charge despite the unlocked bootloader, S-OFF and TWRP being installed. Was just more careful on the replacement phone.
I actually am still looking for a stock RUU though.
Personally I made a TWRP backup before installing SuperSU. That way I can update with OTAs later on. (once we get an OTA we'll be able to pull the stock recovery img from it and update without issue).
Trying to convert this model to an international model was a terrible mistake. Au KDDI does not play well with these types of things. My Butterfly 3 is permanently SIM locked on AU's network for attempting the same thing (was trying to get Marshmallow at the time, which coincidentally is being released for the device next week).
I have been running Xposed and SuperSU with no issues at all though. If you get any "device encrypted" error after S-OFFing, just factory reset the data in TWRP.
Many domo's, DarkRazorZ!
I read that twrp-3.0.2-6-pme.img is the one to go for - that what you used?
Good you had no grief from HTC Japan. I actually sent back my M7 for the purple camera issue a few years back and did very little to disguise the fact it was unlocked and S-Offed. I think they are all fellow modders there and don't give a damn what we do. One reason why HTC is awesome.
I am now waiting for Nougat on the HTC10 (they (AU) just did a press release that it will be pushed soon), and as soon as that is on my phone, I shall be going the Sunshine route and installing aforementioned TWRP and so on. Getting fidgety, though... Xposed, Amplify, ad blocking... lemme at 'em.
DarkRazorZ said:
Unfortunately was not able to get a hold of the stock RUU. I took my phone to my carrier and they gave me a new one free of charge despite the unlocked bootloader, S-OFF and TWRP being installed. Was just more careful on the replacement phone.
I actually am still looking for a stock RUU though.
Personally I made a TWRP backup before installing SuperSU. That way I can update with OTAs later on. (once we get an OTA we'll be able to pull the stock recovery img from it and update without issue).
Trying to convert this model to an international model was a terrible mistake. Au KDDI does not play well with these types of things. My Butterfly 3 is permanently SIM locked on AU's network for attempting the same thing (was trying to get Marshmallow at the time, which coincidentally is being released for the device next week).
I have been running Xposed and SuperSU with no issues at all though. If you get any "device encrypted" error after S-OFFing, just factory reset the data in TWRP.
Click to expand...
Click to collapse
Hey I was wondering if you could help me on how to get a replacement device, I ran into the same problem as you did. Thanks
Hello DarkRazorZ.
I'm curious about your attempt to convert HTV32 to international.
It couldn't be done because of hardware compatibility issue among HTV32 and international?
Or because of just your own mistake in the process?
Did you try a method like this?
http://forum.xda-developers.com/htc-10/help/convert-htc-10-to-unlocked-t3384460
I'm in Japan and considering to buy HTV32, and I want to use it with international firmware.
I know this is your thread, but I can't find any information about this on web.
So could you share me your knowledge. Thanks.
the us unlocked version can be used on KDDI Au but the verizon radio has to be flashed for it to work and even then, you will only get 2g speeds.
Quadrider10 said:
the us unlocked version can be used on KDDI Au but the verizon radio has to be flashed for it to work and even then, you will only get 2g speeds.
Click to expand...
Click to collapse
No, I'm considering to buy HTV32(= HTC10 for Japan region), not other.
Well I'll make a new thread about this issue.
Thanks for replying Quadrider10, and sorry for disturbing DarkRazorZ.
Made a series of mistakes that led me to only have access to fastboot and recovery. It appears I'm capable of flashing things in fastboot. , which I believe you need in order to flash a stock or RUUs in the first place.
If anybody has a TWRP backup of system and boot that'd be awesome, but really need an img of download mode or a RUU or something to help me recover everything to normal. I am S-OFF and bootloader is unlocked.
DarkRazorZ said:
Made a series of mistakes that led me to only have access to fastboot and recovery. It appears I'm capable of flashing things in fastboot. I can't access download mode at all (gives me an error saying it's unable to boot into download mode), which I believe you need in order to flash RUUs in the first place.
If anybody has a TWRP backup of system and boot that'd be awesome, but really need an img of download mode or a RUU or something to help me recover everything to normal. I am S-OFF and bootloader is unlocked.
Checked HTCdev and nothing was there for this device. All help appreciated.
Click to expand...
Click to collapse
hii can u help me how to unlock bootloader on HTC 10 AU version
aSSikn said:
hii can u help me how to unlock bootloader on HTC 10 AU version
Click to expand...
Click to collapse
follow this tut:
https://www.htcdev.com/bootloader/
s2kaka said:
follow this tut:
htcdev
Click to expand...
Click to collapse
i already follow that tutor yesterday.. but when i insert token number the site always says error 170 "CID not allowed"
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.
If you mess up your device I'm not responsible, it works for me, and for others. I will help as much as i can, but it is on YOU, the user to follow the prerequisites and read carefully. This zip was created in collaboration with @TxanMoe and myself
This zip can be used to return to the stock rom(for the most part, you'll still have fastboot,root,twrp) as long as you can get into TWRP recovery on the device. It also flashes the modem bands needed for working Sprint LTE(bands 25,26,41, ect.."all the Sprint bands")
Prerequisites:
1. Activate with Sprint first if you intend to use the converted US998 on Sprint!
2. You already crossflashed to US998 if not follow the guide here "Frankenstein method" [https://forum.xda-developers.com/lg...sflashing-t3780969/post76510671#post76510671]
3. You followed the bootloader unlock, root, TWRP "WTF" thread here https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
(US998 to LS998) Downloads: (Sprint LS998 system,boot,modem)* MAKE SURE TO FLASH MAGISK, NO-VERITY OPT ENCRYPT, AND RCD DISABLER BEFORE LEAVING RECOVERY!!*
Sprint 20b
https://drive.google.com/file/d/1aQojUcchnEruHwnecfaVGToxZbmj-UX3/view?usp=drivesdk
Sprint 21a(may security patch)
https://drive.google.com/file/d/1JCalyu7mt8DW6wMWbgGViqj0oi9eUSr7/view?usp=drivesdk
*Instructions*:
a. Make a backup in TWRP of system,boot,and data before proceeding!
b. Reboot to TWRP and wipe data (factory data reset)
c. Install the SPRINTLS998.zip (20b or 21a)from TWRP (Do NOT leave recovery yet)
d. Flash Magisk, no verity encrypt, and RCD disabler(you should already have these files if you followed the WTF thread)
e. Reboot
d. Once booted up you need to connect to WiFi. go to settings, update profile and prl. Reboot
quantemplation said:
For anyone who flashes back to Sprint but needs to edit the APNs still, you can type this in command prompt(from PC)
Code:
adb shell
su
am start -n com.lge.hiddenmenu/com.lge.hiddenmenu.ModemProtocol.ModemProtocolMain
Then go to PDP Setting
Then go to APN setting
Click to expand...
Click to collapse
be sure to thank his post here
https://forum.xda-developers.com/showpost.php?p=76633700&postcount=45
JonnyTrulove said:
@JWnSC thanks to the help of some of you great people in this thread I have had the chance to do this conversion twice now. Both times it worked great but I did have to update the APN settings before getting mobile data to work for me. I know you were kind enough to include screenshots of the right APN settings but I just wanted to share that both times I used the ##SCRTN## dialer code to force OTA provisioning and it worked, so I thought you may want to add that option to your first post. Might be a good option for someone that's in hurry to get connected.
Only negative I can think of is that you would not have tethering unless you were subscribed or you manually added the "Dun" provision to the APN later.
Just wanted to share in case you thought it was worth adding to your original post. If not, no biggie. Thanks
Click to expand...
Click to collapse
Special thanks:
@TxanMoe for finding the bootloader exploit and helping me along the way
@ChazzMatt for his in depth Guides and help in this forum
@SGCMarkus for TWRP recovery for this device and all the roms he provides
@quantemplation
@JonnyTrulove
and to any others I may have missed..
Here is a zip for warranty exchange ect...*NOT Recommended* (you will lose root, TWRP)
https://drive.google.com/file/d/19FHVNn6TS5ybdNIziL1nyKPWcIc_RN0t/view?usp=drivesdk
From TWRP(wipe data) install the FACTORYSPRINT.zip reboot device, update prl and profile, reboot, do a system update
It works. I tested it
I'll give this a real-world run-through tomorrow when my new LS998 arrives.
SilverZero said:
I'll give this a real-world run-through tomorrow when my new LS998 arrives.
Click to expand...
Click to collapse
I tested it myself to make sure it works. Working on creating a full back to stock zip for warranty exchange ect.. Will post that after I test and know all is well.
JWnSC said:
I tested it myself to make sure it works. Working on creating a full back to stock zip for warranty exchange ect.. Will post that after I test and know all is well.
Click to expand...
Click to collapse
Yeah...it sucks we need this...sprint not allowing access to kdz is a load of bs...it is much appreciated that we have you helping to support us sprint users...i am looking back at my past lg phones now to see if i can find the process of creating a working kdz...one of the people i think in the g2 or g3 forums actually created a kdz using the untouched signed lg files and it was fully flashable to get back to 100% stock...i don't know if too much has changed since then to do this again...but it would be nice to have for some...me...i won't be doing anything that removes my bootloader unlock and root...but those with warranty may want to have that ability...thanks to all that have contributed to making this a great device...i missed root on a level people outside these forums may never understand
Could you tell me if i could switch out your LS998 bins for h933 ones? also on my dump from lgup can i just change _com6 to .bin ?
cre4per said:
Could you tell me if i could switch out your LS998 bins for h933 ones? also on my dump from lgup can i just change _com6 to .bin ?
Click to expand...
Click to collapse
Right. change "_COM#" to ".bin" should be fine as long as the rsa keys match for the devices you are flashing. Don't flash nougat to Oreo or vice versa
JWnSC said:
Right. change "_ whatever com #" to ".bin" should be fine as long as the rsa keys match for the devices you are flashing. Don't flash nougat to Oreo or vice versa
Click to expand...
Click to collapse
perfect will give it a try, hoping this will let me get volte back on mydevice
JWnSC said:
Here is a zip for warranty exchange ect...*NOT Recommended* (you will lose root, TWRP)
https://drive.google.com/file/d/19FHVNn6TS5ybdNIziL1nyKPWcIc_RN0t/view?usp=drivesdk
From TWRP install the FACTORYSPRINT.zip reboot device, update prl and profile, reboot, do a system update
It works. I tested it
Click to expand...
Click to collapse
Could you lock the bootloader after this? Or will it show an error?
guapinoy said:
Could you lock the bootloader after this? Or will it show an error?
Click to expand...
Click to collapse
Bootloader would still be unlocked but the message after every boot would disappear and you won't be able to enter fastboot. (After you do the system update)
I thought after installing the latest update it would lock the bootloader...it didn't, but it did remove the text after every boot saying to lock bootloader and you won't be able to enter fastboot after. Activating developer options will show the boot is still unlocked. It does change the software info to LS99821a instead of US99820a
To lock the bootloader, you could probably flash the other Sprint zip(without flashing magisk ect..) and just sprint recovery or the factory zip. Reboot to bootloader from twrp and lock it that way. Then do the Sprint system update *I have to do more testing tho I don't recommend doing this until it's tested*
I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.
Omatter4 said:
I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.
Click to expand...
Click to collapse
You can't update profile/ prl on US998 firmware(or at least I couldn't). Backup your setup and try DotOS if you already have working lte. This thread is mainly for users to get lte back. I'm not running the stock Sprint firmware. I switched to stock firmware first to get lte working and switched back to us998 rom.
If you wipe data and flash the SprintLS998.zip you won't have any issues. It already contains the Sprint modem, system, and boot. No need to flash the modem from the other thread.
Will flashing the sprint zip only have bands 25,26 &41?? I'm in an area with band 13 also.. Thanks.
Lurien said:
Will flashing the sprint zip only have bands 25,26 &41?? I'm in an area with band 13 also.. Thanks.
Click to expand...
Click to collapse
???
If you flash the Sprint modem you'll have all the Sprint bands.
It's just the US998 does not have LTE bands 26 & 41. So you have to flash the Sprint modem to get them. If the LS998 normally has LTE band 13, then you'll have that.
Have any of our few sprint users taken latest update and tried to bootloader unlock and root their devices?...just wondering if they actually managed to patch it yet...
jamesd1085 said:
Have any of our few sprint users taken latest update and tried to bootloader unlock and root their devices?...just wondering if they actually managed to patch it yet...
Click to expand...
Click to collapse
I tested the latest update, it installed. I dumped the modem, system and boot from it. I can make a zip from it later. My bootloader was still unlocked tho. I plan to lock it and test..been putting it off, don't want to get stuck on stock haha. I need my phone this week. I'll test this weekend. After the latest update it removed the bootloader warning and I couldn't enter fastboot but the bootloader still showed unlocked under developer options.
JWnSC said:
I tested the latest update, it installed. I dumped the modem, system and boot from it. I can make a zip from it later. My bootloader was still unlocked tho. I plan to lock it and test..been putting it off, don't want to get stuck on stock haha. I need my phone this week. I'll test this weekend. After the latest update it removed the bootloader warning and I couldn't enter fastboot but the bootloader still showed unlocked under developer options.
Click to expand...
Click to collapse
How did you install? Because twrp is there it failed on mine
jamesd1085 said:
How did you install? Because twrp is there it failed on mine
Click to expand...
Click to collapse
I flashed the factory back to stock.zip and went to settings, system update.
Not worth it imo...I was testing the factorysprint.zip to make sure it worked. I can make a flashable zip later(to only include system, modem,boot)..I don't think much changed. Looks like it was just an update to disable fastboot and access to recovery
Omatter4 said:
I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.
Click to expand...
Click to collapse
The first time I tried the profile and PRL updates they took a while to actually launch. Not sure if yours would if you just waited a bit longer (like a minute). I would try that and then the Sprint zip (that's actually more likely to fix your issue).
SilverZero said:
The first time I tried the profile and PRL updates they took a while to actually launch. Not sure if yours would if you just waited a bit longer (like a minute). I would try that and then the Sprint zip (that's actually more likely to fix your issue).
Click to expand...
Click to collapse
I had to connect to wifi when i updated profile...it kept telling me to contact carrier when i tried to update through data connection