I've been scouring XDA, looking for a way to get S-Off on my Unlocked/S-ON VZW HTC ONE. I was one of the few who managed to unlock the phone early using HTC DEV. Now I'm stuck with the antiquated firmware, modems, kernels, etc. Can anyone help with this? I'm kind of a noob when it comes to Fastboot....so you may need to steer me toward a walk-through. Thanks in advance
figaro1418 said:
I've been scouring XDA, looking for a way to get S-Off on my Unlocked/S-ON VZW HTC ONE. I was one of the few who managed to unlock the phone early using HTC DEV. Now I'm stuck with the antiquated firmware, modems, kernels, etc. Can anyone help with this? I'm kind of a noob when it comes to Fastboot....so you may need to steer me toward a walk-through. Thanks in advance
Click to expand...
Click to collapse
ok so what you'll need to do is make sure you have working ADB and Fastboot on you PC and make sure they can see the phone.
First you want to get:
http://forum.xda-developers.com/showthread.php?p=42407269
once you have this loaded on your pc we are going to want to make sure it works. for simplicity im going to this a certain way once you get the hang of paths and how this all works you can choose to do it a different way.
first make a folder on your c drive fastboot
once you have that folder place all the contents of ADB and Fastboot from the link above into the folder.
from windows open up a command prompt. (search CMD.exe)
once opened we want to get to that directory so we type this :
cd c:\
once that is done lets plug phone into the pc
run command
adb devices
(output should look something like this)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\>
this means no devices are seen by the pc. This is okay, for now.
with the phone you are going to need to enable develop mode. to do so go to
settings > about > software information > more > click the build number on the screen about 10 times in a row.
if done correctly it will call you a developer in a toast notification.
back all the way out to settings and go to the bottom. you should see developer options now. accept the warrning and get into the options. you will see the option for USB debugging, we want to have this enabled now.
once this is all done run this command from the CMD.exe you had to open above
adb kill-server
then run
adb devices
(output should look something like this)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
***device name here***
you are now talking to the phone via ADB congrats.
...next step
Perfect! I'm up and running in adb. Thanks for the great instructions Now what should I flash?
I'm running bonestock and it's amazing. Haven't found the need to change. It runs awesome, everything works, simply amazing.
Sent from my iPhone 5s using Tapatalk 4
figaro1418 said:
I've been scouring XDA, looking for a way to get S-Off on my Unlocked/S-ON VZW HTC ONE. I was one of the few who managed to unlock the phone early using HTC DEV. Now I'm stuck with the antiquated firmware, modems, kernels, etc. Can anyone help with this? I'm kind of a noob when it comes to Fastboot....so you may need to steer me toward a walk-through. Thanks in advance
Click to expand...
Click to collapse
Why do you say you're stuck with S-On? You can still S-Off, just so you know.
karn101 said:
Why do you say you're stuck with S-On? You can still S-Off, just so you know.
Click to expand...
Click to collapse
With Rumrunner? It won't work on my unlocked bootloader! I have ADB up and running on my computer, but my computer won't recognize the device in fastboot mode. I'm open to any ideas or advice. Again, I'm kind of a noob to HTC. I used to work with Samsung Phones. I've only recently learned how to work with HTC.
Lock your bootloader?
Sent from my iPhone 5s using Tapatalk 4
Look at the HTC one toolkit by squabbi on the HTC one general forum ,it helped me get root back after taking the ota
Sent from my GT-P3110 using xda app-developers app
I was in the same situation as you in regard to HTC Dev unlocked on day one but still had S-On. What I did was flashed the Odexed Full ROM version: 1.10.605.10 from santod040 (http://forum.xda-developers.com/showthread.php?t=2485319) and then flashed the stock boot.img and signed-recovery.
However, after doing that I had one hell of a time with rumrunner, even though I was using the download for 1.10.605.10. It turns out, even though I was on the stock ROM I flashed above with the correct version my OS was showing 1.10.605.02 because I had one of the weird phones that shipped with that version instead of .08. Luckily for me since I had the stock boot.img and signed-recovery, I just did the OTA update to 1.10.605.15 and then used rumrunner for that version.
Also, no you don't need to lock your bootloader before doing that. I didn't.
bloodiedwraith said:
I was in the same situation as you in regard to HTC Dev unlocked on day one but still had S-On. What I did was flashed the Odexed Full ROM version: 1.10.605.10 from santod040 (http://forum.xda-developers.com/showthread.php?t=2485319) and then flashed the stock boot.img and signed-recovery.
However, after doing that I had one hell of a time with rumrunner, even though I was using the download for 1.10.605.10. It turns out, even though I was on the stock ROM I flashed above with the correct version my OS was showing 1.10.605.02 because I had one of the weird phones that shipped with that version instead of .08. Luckily for me since I had the stock boot.img and signed-recovery, I just did the OTA update to 1.10.605.15 and then used rumrunner for that version.
Also, no you don't need to lock your bootloader before doing that. I didn't.
Click to expand...
Click to collapse
synisterwolf said:
Lock your bootloader?
Sent from my iPhone 5s using Tapatalk 4
Click to expand...
Click to collapse
figaro1418 said:
With Rumrunner? It won't work on my unlocked bootloader! I have ADB up and running on my computer, but my computer won't recognize the device in fastboot mode. I'm open to any ideas or advice. Again, I'm kind of a noob to HTC. I used to work with Samsung Phones. I've only recently learned how to work with HTC.
Click to expand...
Click to collapse
I had mine unlocked on day one as well. When RomRunner came out, I was able to run it just fine (unlocked).
Are you on a stock ROM? You can always make a backup, move those files to your computer, RUU to be completely stock, and then run RomRunner.
Once that's done, just bring over your backup and restore it in recovery.
figaro1418 said:
With Rumrunner? It won't work on my unlocked bootloader! I have ADB up and running on my computer, but my computer won't recognize the device in fastboot mode. I'm open to any ideas or advice. Again, I'm kind of a noob to HTC. I used to work with Samsung Phones. I've only recently learned how to work with HTC.
Click to expand...
Click to collapse
It won't recognize it because that's what fastboot is for in the folder your adb is in. Don't type adb devices. Type fastboot devices. Then you'll see your mistake
Sent from my One using Tapatalk
karn101 said:
I had mine unlocked on day one as well. When RomRunner came out, I was able to run it just fine (unlocked).
Are you on a stock ROM? You can always make a backup, move those files to your computer, RUU to be completely stock, and then run RomRunner.
Once that's done, just bring over your backup and restore it in recovery.
Click to expand...
Click to collapse
He can't run the RUU because you have to be S-OFF to do that, hence why I put what I needed to do since I was in the same situation.
bloodiedwraith said:
He can't run the RUU because you have to be S-OFF to do that, hence why I put what I needed to do since I was in the same situation.
Click to expand...
Click to collapse
You don't need to be S-Off to do it. The signed RUUs are up.
Here's a link.
http://flyhalf205.com/?dir=RUU
Regardless, flashing a stock ROM is most likely the easiest route to go. I was just throwing up an alternative.
Related
Hi guys!
Well, I'm new in what concerns to root, unlock, ROM's, kernels (no idea of what it is still), etc. I have a Xperia Arc, GB 2.3.4, branded for T-Mobile.
As I'm fed up with the bunch of bloatware, I wanted to root/debrand it, in order to get rid of it.
First I tried with this thread: http://forum.xda-developers.com/showthread.php?t=1035276 Post #2
Links for the ROM were dead, so I searched for some other thread. After a lot, I found this one: http://forum.xda-developers.com/showthread.php?t=1042978
I found it easy to lead, so i tried. I got so far, to even unlock my bootloader, but then, trying to root, I found the images link for the Global firmware was dead.
Then I realized, I wanted to change to the global versión for the mere reason of having ICS sooner (branded phones take longer to receive it, as far as I know). Then I saw, that actually I went in the full wrong direction when unlocking the bootloader.
I tried to relock thebootloader, by following the steps in this thread: http://forum.xda-developers.com/showthread.php?t=1324703
It appears to have worked well, but I'm not sure.
My questions are:
1) I want the SE ICS update, that is due to be available this month anytime. Since unlocking the bootloader might have turned my phone to brick (or not?) when upgrading, how can I be sure I did actually re-lock my bootloader? The guys from Android Soul Comnunity used a "Test" on their videos, which was running a program in fastboot mode, which apparently does something if the phone is unlocked, although it said "it needs to be rooted". Is there a way to know if I did it correctly relock whitout damaging my phone or flashing it by mistake in the process.
2) I really want to flash it to a global version and get rid of the bloatware (maybe rooted if posible), but also getting the official upgrade. Is there a way? I have the latest flashtool version and I downloaded the ftf file for the global version, but whenever I press flash in flashtool, it doesn't show anything (nor sin files or anything else). Maybe I will give it another try if someone else provides me with a functional link to the functional ROM (I really don't remember where I got the one I have).
I hope you guys can help me. I'm not a native english speaker, so forgive me for any mistake. Thanks in Advance
HerrJuancho
seems like you are new to this....so was I about 4 months ago.
if your bootloader is unlocked, good - keep it that way.
the best way to learn how to mess around is follow this thread step-by-step:
http://forum.xda-developers.com/showthread.php?t=1299729
I know that this thread is instructing you to flash cm7 - but dont worry, once you have done that, you will understand the basics and the processes involved.
if you really want ICS - then you can just us Arconium 2.2 as it is the closed custom rom to a stock ICS - it is tweaked and customized, so it will be better than any global rom you try to flash.
http://forum.xda-developers.com/showthread.php?t=1515148
kaatisu84 said:
seems like you are new to this....so was I about 4 months ago.
if your bootloader is unlocked, good - keep it that way.
the best way to learn how to mess around is follow this thread step-by-step:
http://forum.xda-developers.com/showthread.php?t=1299729
I know that this thread is instructing you to flash cm7 - but dont worry, once you have done that, you will understand the basics and the processes involved.
if you really want ICS - then you can just us Arconium 2.2 as it is the closed custom rom to a stock ICS - it is tweaked and customized, so it will be better than any global rom you try to flash.
http://forum.xda-developers.com/showthread.php?t=1515148
Click to expand...
Click to collapse
Thanks, I thought no one would answer.
I don't know if I actually still have a unlocked bootloader. How can I tell the difference? By doing what?
If it is really that good, the I would prefer it over the official. Thanks
HerrJuancho said:
Thanks, I thought no one would answer.
I don't know if I actually still have a unlocked bootloader. How can I tell the difference? By doing what?
If it is really that good, the I would prefer it over the official. Thanks
Click to expand...
Click to collapse
Do this
1)Connect your phone on fastboot mode.
2) open cmd prompt in the fastboot folder
3) type this in the command window
fastboot.exe -i 0x0fce get var version
4) if you get a value like 0.3 or something its unlocked
Sent from my LT26i using xda premium
king-iyokan said:
Do this
1)Connect your phone on fastboot mode.
2) open cmd prompt in the fastboot folder
3) type this in the command window
fastboot.exe -i 0x0fce get var version
4) if you get a value like 0.3 or something its unlocked
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
Well, that's actually one of the steps before unlocking, I thought it was just a sign that the device was well connected and that the drivers were up to date. My phone wasn't unlocked, and it did show 0.3 right before trying to unlock it.
HerrJuancho said:
Well, that's actually one of the steps before unlocking, I thought it was just a sign that the device was well connected and that the drivers were up to date. My phone wasn't unlocked, and it did show 0.3 right before trying to unlock it.
Click to expand...
Click to collapse
Ohh sorry. My bad. Try to boot a custom kernel via fastboot.
Fastboot.exe boot boot.IMG
If you get a notice "device not rooted" or similar the bootloader is loced.
If you are able to boot the kernel the bootloader is unlockd
Sent from my LT26i using xda premium
Ok, I bought a galaxy nexus SCH i515 off ebay. The phone was listed as verizon, all the information behind the battery came up as sch i515. However when I powered it on. The phone said activate samsung account. The phone matches verizon info on the back. I contacted verizon and they said most likely the phone was rooted and that the phone could not be switched back even after a hard reset (which i did). I have wifi so used that to get on play store and downloaded rootchecker.... it says phone is not rooted.. (did original owner just unroot phone) am I screwed or is there anything I can do to get verizon able to activate it?
1) wrong section
2) follow this: http://forum.xda-developers.com/showthread.php?t=1626895
after step 2, check in the phone status menu for the model number.
So i'm a noob and after running through all this I can still (and verizon saying that the imei number wasn't in their database) make this work with verizon... i dont want to get this into a boot loop or fry this thing.. sorry for bugging out... I just want to know if this will officially work... again my phone was verizon and was switched to a sprint phone (upon powering up it asked for sprint activation.)
loopers said:
So i'm a noob and after running through all this I can still (and verizon saying that the imei number wasn't in their database) make this work with verizon... i dont want to get this into a boot loop or fry this thing.. sorry for bugging out... I just want to know if this will officially work... again my phone was verizon and was switched to a sprint phone (upon powering up it asked for sprint activation.)
Click to expand...
Click to collapse
I appreciate your quick informative answer but if i've already called verizon and they have informed me that the imei is not in their data base.... if i do all these steps and flash back to complete stock the imei still will not be in there data base correct? I mean I'm still stuck on this.... if I need to start asking somewhere else please let me know. Thanks
Just flash the factory images from Google. And make sure the ESN is good you can check it just Google search
Sent from my Nexus 4 @1.72 GHz on Stock 4.2.2
where is the factory images from google? Sorry i've been back and forth with seller and verizon and DO NOT want to screw this up
I see nothing specific from google search that says from a google site to flash these files to phone with steps
loopers said:
I see nothing specific from google search that says from a google site to flash these files to phone with steps
Click to expand...
Click to collapse
sorry found files
well found everythhing i need and loaded into the bootloader.. can't get it unlocked because it won't recognize fastboot devices..... it recognizes nothing. tried multiple ports.usb ports that is.... comes up with error code 214dfddsf i can't remember.... googled error.. no one really knows a fix.. if anyone knows of a toolkit for 4.1.1 or similar for samsung galaxy nexus let me know.... i've been trying to get my wifes phone activated for 6 1/2 hours and i'm done with it less you guys have a clear cut alternative.. i don't expect anyone to jump up and say here ya go but if ya do i'd greatly appreciate it.... i've googled the error to death.. no clear cut fix.... and i'm not trying to load up a rom.. i neeed to get the phone completely factory reset so i can get it activated from verizon..
oh yeah... i found all the device drivers etc.. and they are working 100%.... also turned on debugging mode..... know nothing else to do to get it to recognize commands in command prompt... i'm typing the commands from the folder the files are in..... nothing with that error i'm not getting any further anyway....
loopers said:
oh yeah... i found all the device drivers etc.. and they are working 100%.... also turned on debugging mode..... know nothing else to do to get it to recognize commands in command prompt... i'm typing the commands from the folder the files are in..... nothing with that error i'm not getting any further anyway....
Click to expand...
Click to collapse
fastboot and adb are 2 completely different modes, and the commands are not interchangeable. usb debugging has nothing to do with fastboot whatsoever
Pirateghost said:
fastboot and adb are 2 completely different modes, and the commands are not interchangeable. usb debugging has nothing to do with fastboot whatsoever
Click to expand...
Click to collapse
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb
loopers said:
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb
Click to expand...
Click to collapse
Try wugs nexus root toolkit. More friendly for new users. Just Google the name and it'll come up.
Sent from my Galaxy Nexus using xda premium
loopers said:
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb
Click to expand...
Click to collapse
Just to make sure. You are in the bootloader on the phone and you are typing in the Fastboot devices and then OEM unlock command in Windows cmd? Try a different set of drivers. Uninstall the ones you have now and click the link below. Install those and do the "fastboot devices" command again. The naked divers seem to give people the least amount of problems.
Drivers: http://forum.xda-developers.com/showthread.php?t=1379875
Toro | Carbon | AK SKL
as is strewn throughout these forums....ADB and FASTBOOT use different drivers. just because you have adb working doesnt mean that fastboot is setup properly
Sandman-007 said:
Just to make sure. You are in the bootloader on the phone and you are typing in the Fastboot devices and then OEM unlock command in Windows cmd? Try a different set of drivers. Uninstall the ones you have now and click the link below. Install those and do the "fastboot devices" command again. The naked divers seem to give people the least amount of problems.
Drivers: http://forum.xda-developers.com/showthread.php?t=1379875
Toro | Carbon | AK SKL
Click to expand...
Click to collapse
those are the drivers i have installed i think someone completely fudged this phone
those are all google nexus don't say anything about samsung version :\
fudge it i'm gonna try that root tool kit.. i just gotta get this thing running on verizon for my wife.... don't want root.... just root and unroot like the toolkit says if it works magic... i hope
loopers said:
fudge it i'm gonna try that root tool kit.. i just gotta get this thing running on verizon for my wife.... don't want root.... just root and unroot like the toolkit says if it works magic... i hope
Click to expand...
Click to collapse
No need to root, just install drivers, unlock bootloader and flash stock image, then lock the bootloader up..
Got it fixed. Tool kit worked. Txx
Sent from my SCH-I535 using Tapatalk HD
A couple of months ago I asked if there was an upgrade path to the latest update for a non rooted completely stock Verizon HTC One. The phone belongs to my mom who uses it on Ultra Mobile. Is there anyway to upgrade it to Kitkat. Right not it's on 4.2 Jellybean.
Warbuff said:
A couple of months ago I asked if there was an upgrade path to the latest update for a non rooted completely stock Verizon HTC One. The phone belongs to my mom who uses it on Ultra Mobile. Is there anyway to upgrade it to Kitkat. Right not it's on 4.2 Jellybean.
Click to expand...
Click to collapse
Sure there is. Manually download the otapkg.zip and copy it to the phone. Reboot into stock recovery and chose apply update from phone storage.
dottat said:
Sure there is. Manually download the otapkg.zip and copy it to the phone. Reboot into stock recovery and chose apply update from phone storage.
Click to expand...
Click to collapse
Trying to do that. When I boot into recovery I get unable to access sd card for about 5 times and then it finally boots into recovery. When attempting to select apply from phone storage it states invalid operation and reboots the phone. Any suggestions?
Warbuff said:
Trying to do that. When I boot into recovery I get unable to access sd card for about 5 times and then it finally boots into recovery. When attempting to select apply from phone storage it states invalid operation and reboots the phone. Any suggestions?
Click to expand...
Click to collapse
Make sure fastboot is turned off, in the Rom settings before booting to recovery.
santod040 said:
Make sure fastboot is turned off, in the Rom settings before booting to recovery.
Click to expand...
Click to collapse
Thanks for getting back to me quickly. Fastboot is turned off in power settings and the same issue arises.
Warbuff said:
Thanks for getting back to me quickly. Fastboot is turned off in power settings and the same issue arises.
Click to expand...
Click to collapse
Well, this method used to work.
It may be that s-off is required to accomplish this now.
I can't really say for sure, as I haven't had a device that stayed s-on for more then a few days at most.
Wish I had a better answer for you.
santod040 said:
Well, this method used to work.
It may be that s-off is required to accomplish this now.
I can't really say for sure, as I haven't had a device that stayed s-on for more then a few days at most.
Wish I had a better answer for you.
Click to expand...
Click to collapse
Thanks for trying anyways. Greatly appreciated. I guess my mom will stay on 4.2.2 for the foreseeable future.
Just updating for any future users who may come across the thread. The solution to my initial issue is as follows:
For those not on Verizon you can still update by using HTC sync. After installing HTC Sync and connecting your phone, it will prompt you for an available upgrade. Follow the onscreen instructions and the phone will be updated to whatever the latest update is.
Warbuff said:
Just updating for any future users who may come across the thread. The solution to my initial issue is as follows:
For those not on Verizon you can still update by using HTC sync. After installing HTC Sync and connecting your phone, it will prompt you for an available upgrade. Follow the onscreen instructions and the phone will be updated to whatever the latest update is.
Click to expand...
Click to collapse
As long as you are stock I might add. If it reads a custom Rom you won't get offered an update. And btw, what the app knows HTC knows ?
dottat said:
As long as you are stock I might add. If it reads a custom Rom you won't get offered an update. And btw, what the app knows HTC knows ?
Click to expand...
Click to collapse
So HTC knew I went from 4.x.x.x (while unlocked and s-off with root) down to 2.x.x.x to update to the newest through the app before going s-off and they took my phone to swap out. Cracked screen replacement. Sometimes they know but don't check.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
So HTC knew I went from 4.x.x.x (while unlocked and s-off with root) down to 2.x.x.x to update to the newest through the app before going s-off and they took my phone to swap out. Cracked screen replacement. Sometimes they know but don't check.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Sorta depends on the case and who you get whether It pans out to be a problem. Just wanted to forewarn folks this app does check in
The fuu app does not.
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...
Hi All
having a problem here, windows 7 detect my phone, but in Hansoon 2000 and launch the cmd Getvar All, cmd unable to detect my phone
FYI my phone was already rooted and s-off, i totally forget how i did it
Reason to use Hansoon 2000 is because i had downloaded the official Lollipop update (1.44GB Asia) but have no means and ways to flash it even with twrp build in.
There is not supersu and does not seems root after i have **** up the OS.
Hope anyone here can guide me step by step, i getting confuse after looking for information on google and on XDA forums
Regards
Andy
cosmickiller said:
Hi All
having a problem here, windows 7 detect my phone, but in Hansoon 2000 and launch the cmd Getvar All, cmd unable to detect my phone
FYI my phone was already rooted and s-off, i totally forget how i did it
Reason to use Hansoon 2000 is because i had downloaded the official Lollipop update (1.44GB Asia) but have no means and ways to flash it even with twrp build in.
There is not supersu and does not seems root after i have **** up the OS.
Hope anyone here can guide me step by step, i getting confuse after looking for information on google and on XDA forums
Regards
Andy
Click to expand...
Click to collapse
i can help you over teamviewer just pm me.
cosmickiller said:
Hi All
having a problem here, windows 7 detect my phone, but in Hansoon 2000 and launch the cmd Getvar All, cmd unable to detect my phone
FYI my phone was already rooted and s-off, i totally forget how i did it
Reason to use Hansoon 2000 is because i had downloaded the official Lollipop update (1.44GB Asia) but have no means and ways to flash it even with twrp build in.
There is not supersu and does not seems root after i have **** up the OS.
Hope anyone here can guide me step by step, i getting confuse after looking for information on google and on XDA forums
Regards
Andy
Click to expand...
Click to collapse
You shouldn't use toolkits. Are you s-off?
Yes S-off
xunholyx said:
You shouldn't use toolkits.
Click to expand...
Click to collapse
Agreed. Why use a toolkit for what is accomplished with a single adb command? Toolkit just adds unnecessary complexity, and another point of potential failure.
Is the phone in recovery or booted into OS? getvar is an adb command, and adb only works under those conditions. Also, adb needs to be activated in the phone's settings.