I've been asked by lots of folks on how to convert the HTC 10 unlocked US version into a full-featured Verizon version so I figured i'd write an all encompassing guide on how to complete the process.
After following this guide, your phone will effectively be a fully-functioning Verizon variant. IMS, advanced calling, wifi calling and all other Verizon features will work flawlessly!
Note: I am purely compiling this information. I had no part in discovering this process, I simply followed multiple guides and other random posts on XDA to accomplish this! Credits go to @jcase, @beaups, @dottat, and any others that were involved with testing this process. Please make sure to thank these guys for the work they've done.
Step 1: Unlock bootloader and acquire s-off
In order to modify the CID/MID and change the radio, we must first acquire s-off. The easiest way to do this is to follow jcase's well-written guide.
[FONT=Hind, sans-serif][Guide] Root (Optionally s-off) and Keep your radio working[/FONT]
Move on to step 2 after finishing the above guide to completion.
Step 2: Change CID and MID
2a) Download this link, and extract into your directory of choice
https://www.androidfilehost.com/?fid=24545065934258327
2b) Boot your phone into download mode via the button combo (down + power) or by using adb reboot-bootloader with USB debugging turned on and then selecting download mode
2c) Issue the following command while in download mode:
Code:
htc_fastboot oem writecid VZW__001
2d) Issue the following command while in download mode:
Code:
htc_fastboot oem writemid 2PS650000
2e) Reboot phone back into download mode and verify the CID and MID have changed and are correct.
Step 3: Flash Verizon RUU to phone
Now that we have s-off, unlocked bootloader and the proper CID/MID on our device, now we just need the Verizon stock ROM and radio on our device. The Verizon RUU will handle both of these for us in a relatively hassle-free manner.
3a) Download the following .exe file to your local machine (big thanks to @dottat!)
Verizon Stock RUU exe (dottat)
3b) Boot phone into download mode (or Android OS w/ USB debugging enabled) and run the executable file
3c) Follow onscreen instructions and wait for process to finish
3d) Reboot phone (it may take a while to boot so BE PATIENT! mine took about 4-5 minutes if I recall)
After your phone boots, it will be a fully functioning Verizon phone. At this point, you can go activate your phone and it will work. You will be able to take Verizon official OTAs and it will behave identically to the true Verizon variant due to the RUU re-flashing stock recovery and an unmodified system.
OPTIONAL -- Step 4: Re-root phone
The RUU that you deployed on your phone was an unrooted system image with stock recovery. In order to get root back, you will need to re-do steps 1-10 in jcases's Root/s-off guide from step 1.
Here's the link again in case you're too lazy to scroll back up
[FONT=Hind, sans-serif][Guide] Root (Optionally s-off) and Keep your radio working[/FONT]
Reminder: your phone already has s-off so you ONLY NEED TO DO STEPS 1-10! Running Sunshine again will likely just report that your phone already has s-off so no worries if you accidentally do the entire guide again.
Step 5: Activate your phone
This step can be very straightforward or a moderate pain the ass depending on what you have available to you.
There are two ways to activate the HTC 10 now that it's running stock Verizon firmware/software:
1) Pop an existing, activated nano-SIM with your current phone number on it in the device and reboot. Voila!
2) Take your device to a Verizon store and convince the employee that your phone is in fact, a true Verizon phone.
I would highly suggest using an already active nano-SIM if you have that available. I, unfortunately, did not as I was coming from the Verizon LG G4. I had to go three different Verizon stores to convince them to finally activate the device. Your IMEI on your unlocked 10 will not show up in Verizon's IMEI database. The store clerk actually had to pull an IMEI from a display model HTC 10 so that she could get the nano-SIM activated for my 10.
noahjk said:
Good post! I think you're looking for this link: http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
Click to expand...
Click to collapse
Good catch, thanks. I updated the links.
Tried this twice, both times my phone gets stuck on 'Preparing your phone...' after flashing and rebooting on the setup wizard.
edit: worked fine after removing SIM. Run through the setup without SIM for anybody having issues. I know this isn't explicitly stated in OP but if you're having issues, make sure you try this.
If anyone is having connection issues after putting in your SIM, you have to change your Preferred Network mode from Global to LTE/CDMA.
Other than that, everything's working great! Even comes with free VZW bloatware
anyone receiving "Htcdm has stopped" on their phone all of a sudden .... i just downloaded a few things, changed the bootanimation, setup my hotspot, and then bam - popups randomly.
codelinx said:
anyone receiving "Htcdm has stopped" on their phone all of a sudden .... i just downloaded a few things, changed the bootanimation, setup my hotspot, and then bam - popups randomly.
Click to expand...
Click to collapse
Haven't seen that before. What did you do to setup your Hotspot?
DoctorB0NG said:
Haven't seen that before. What did you do to setup your Hotspot?
Click to expand...
Click to collapse
That error would be the ota downloader.. what anything frozen I would ask the person who posted
Sent from my HTC6545LVW using Tapatalk
How would I revert back to the stock values and a stock unlocked RUU? Can you put that in the guide with a link to a stock RUU?
Zooks97 said:
How would I revert back to the stock values and a stock unlocked RUU? Can you put that in the guide with a link to a stock RUU?
Click to expand...
Click to collapse
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
andybones said:
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
Click to expand...
Click to collapse
Looks like all the stock information, RUUs, roms, and recoveries are here.
Has the MID/CID for stock there as well. Hope this makes it into the OP.
When I have access to a desktop/laptop I'll update the guide. Thanks for the suggestions.
After following all the instructions, I got to the end where the phone reboots and is supposed to be Verizon. When mine reboots, however, it comes up with the decryption screen asking for my password. Any ideas?
I think I might have figured it out. I did a factory reset/wipe and it looks like it's coming up now.
hunteditor said:
After following all the instructions, I got to the end where the phone reboots and is supposed to be Verizon. When mine reboots, however, it comes up with the decryption screen asking for my password. Any ideas?
I think I might have figured it out. I did a factory reset/wipe and it looks like it's coming up now.
Click to expand...
Click to collapse
Yep that's the fix. The vzw ruu does not wipe.
Sent from my HTC6545LVW using Tapatalk
andybones said:
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
Click to expand...
Click to collapse
Did you pick up a 10 yet?
aer0zer0 said:
Did you pick up a 10 yet?
Click to expand...
Click to collapse
I did.
It's prepared to be sent to Mr. @beaups when they are back doing devices again on May 22nd.
(In my signature below, in green are the devices I currently own, and the ones striked out are previous devices I had but are sold).
Just an FYI, I followed instructions on this guide, did everything without SIM card in and I do not have any advanced calling features. Signal drops to 1x when on a call and there is no Wi-Fi calling option in the advanced calling menu within Android. My guess on the cause is that I flashed TWRP and side loaded SuperSU before I put my SIM in the phone. I will try again from scratch and activate the phone prior to root and recovery and report back. Is anyone else having similar issues?
Light1984 said:
Just an FYI, I followed instructions on this guide, did everything without SIM card in and I do not have any advanced calling features. Signal drops to 1x when on a call and there is no Wi-Fi calling option in the advanced calling menu within Android. My guess on the cause is that I flashed TWRP and side loaded SuperSU before I put my SIM in the phone. I will try again from scratch and activate the phone prior to root and recovery and report back. Is anyone else having similar issues?
Click to expand...
Click to collapse
Did you activate those features on your account using the menu on the phone?
Sent from my HTC6545LVW using Tapatalk
dottat said:
Did you activate those features on your account using the menu on the phone?
Click to expand...
Click to collapse
What menu are you talking about? I went to take a screen shot of my advanced calling menu in settings and now Wi-Fi calling is showing up.. I didn't change a thing, very odd. However, my signal still drops to 1x when placing a call. And my device says non-VZW device when I login to my account online. I'm guessing that is part of the problem.
Light1984 said:
What menu are you talking about? I went to take a screen shot of my advanced calling menu in settings and now Wi-Fi calling is showing up.. I didn't change a thing, very odd. However, my signal still drops to 1x when placing a call. And my device says non-VZW device when I login to my account online. I'm guessing that is part of the problem.
Click to expand...
Click to collapse
Take some screen shots.
Sent from my HTC6545LVW using Tapatalk
Here is my advanced calling menu with Wi-Fi calling now showing up. Haven't tested, but it seemed to let me set it up. I have Wi-Fi tether enabled via default.xml edits. The one feature I'd really like is LTE on call. Had this without problem on my M7 but I think thats because it had multiple radios and didn't have to share a radio while on call. My noob guess anyways.
Maybe it's a setting in the hidden dialer menu *#*#4636#*#*? However, when I enter that into the dialer, nothing happens, the entered numbers just disappear and nothing happens. Thoughts?
Related
hey, i had a evo3d running synergy rom and half the screen broke so i had insurance send me a new one.
Keep in mind my old, broke, phone still works (only half the screen works).
once i got my new evo3d in i rooted it, updated the radio with PG86IMG-twrp-shooter-1.1.1.zip and then flashed the latest synergy 3d ROM. once it stated up, it ran the auto hands-free activation.
After a delay it came up and said connection failed 1 of 5, and asked if i wanted to activate or if i was on the phone with a sprint tech and wanted to do it manually. When i press "Activate" it crashes with this message "vDM client has crashed..." and i have to click Force quit. Then im at the normal setup your android screens.
If i skip ahead the phone is not activated (plus my old one is still live, but even still vDM should not be crashing i would assume). So i then called sprint tech *2 and had a very knowledgeable lady and we tried several things, the main issue being ##823834## not working or doing anything (prob bc of rom).
I can press ##3282# and get the View / Edit, but even on that page, using the password (it asks for a password if you press "Edit") give to me on the phone by the sprint tech, did not accept. She said i should bring it in to the store and she was going to make me an appointment. I clearly didn't mention it was rooted.
What can i do to get this new rooted phone activated? should i re-flash back to stock sprint? any why is vDM crashing (Google and xda search gave very very little on vdm)?
thanks alot.
1. Nandroid backup
2. RUU
3. Nandroid restore
4. ????
5. No profit, but working phone.
Just run a stock rooted ROM. The problem is you may have run into that error 16 issue. They warn of it in the thread on rooting. Basically it kills the data connection for the phone (Which is needed for hands free activation) and you need to call in to a department and have them reset it on their end. However, since the phone was never previously activated, it seems you don't have this option?
It doesn't happen every time you root, didn't happen to me at all. But perhaps read some of those issues and see if the tech team can push the fix your way. I think Product Fred posted about it specifically referencing the department to call. If all else fails, it seems like you may need to unroot and exchange for another device. Then activate that one before rooting.
Ok great i'll try the stock rooted rom and report back, im no to clear on what zadias was trying to say in his post however.
when you said "see if the tech team can push the fix your way." do you mean a push from sprint's tech team? bc if so then the lady from sprint i spoke with earlier did push some kind command when we were trying to troubleshoot activating it.
tks again!
hi,
I have tried the stock sprint rom and even on that the same thing happens, once it boots up and the "Hands free activation" screen comes up, after about 1 minute it comes up and says the connection has failed and do i want to retry? (it says if you are on the phone with a live sprint tech to click cancel.) i have the option of activate and cancel. if i click activate i get this:
The application vDM Client (process com.redbend.vdmc)) has stopped unexpectedly. please try again.
(then i must click force close)
Anyone have any input or ideas? im fully without a phone now as my others screen has stopped working fully.
thanks
jo2jo said:
hi,
I have tried the stock sprint rom and even on that the same thing happens, once it boots up and the "Hands free activation" screen comes up, after about 1 minute it comes up and says the connection has failed and do i want to retry? (it says if you are on the phone with a live sprint tech to click cancel.) i have the option of activate and cancel. if i click activate i get this:
The application vDM Client (process com.redbend.vdmc)) has stopped unexpectedly. please try again.
(then i must click force close)
Anyone have any input or ideas? im fully without a phone now as my others screen has stopped working fully.
thanks
Click to expand...
Click to collapse
Is the old phone still working..i mean can u make and get calls on the old phone?
Sent From My HTC EVO 3D ROOTED
Yes i can make calls on the old device, i have used it to call sprint *2 and we tried everything on the new phone, no luck she said i would have to bring it into the store.
Im trying to restore it to STOCK sprint using these directions, but the PIA file links dont work (on all 3 of the posts on return to stock ive found, none of the donwload links work so pls help.)
http://forum.xda-developers.com/showthread.php?t=1193540
It says download the stock rom zip which it links to a 400mb file, it then says:
In hboot mode the phone will scan the SD card with the image. Once it finds it will ask you if you want to update. Press "Power" to update.
(to me that sounds like how u flash a radio with a small 4mb zip file like team recovery file you rename to PG186.zip, so why are they linking to a 400mb rom file?)
to me that is how you flash a radio with a small PG186.zip file not a 300mb ROM file, so im confused on that, do i want to choose the zip to flash and flash that 300mb rom (which i have already done in the post 2 above this) or do i rename this 300mb file to PG186.zip so that the fastboot white screen AUTOMATICALY asks me if i want to update this file (flash a radio is what i understand this to be).
Please help guys, i have no phone and really stuck.
Don't restore a Nandroid backup before deleting wimax.img from the backup folder! If you don't, you'll overwrite the new Wimax keys with your old ones and the 4G won't work!
just to be clear this is the file im having issues with:
1. Download the stock ROM ZIP image from here: Sprint Stock ROM Image v 1.1.3.651.7
they say to flash it like PG186.zip but when i click on the link i see a 300MB rom file.
thanks
EDIT productRed, i just saw your reply ,i dont think any of that applies to me as im not using nandbackup nor have ever used that program or backup. tks
jo2jo said:
Yes i can make calls on the old device, i have used it to call sprint *2 and we tried everything on the new phone, no luck she said i would have to bring it into the store.
Im trying to restore it to STOCK sprint using these directions, but the PIA file links dont work (on all 3 of the posts on return to stock ive found, none of the donwload links work so pls help.)
http://forum.xda-developers.com/showthread.php?t=1193540
It says download the stock rom zip which it links to a 400mb file, it then says:
In hboot mode the phone will scan the SD card with the image. Once it finds it will ask you if you want to update. Press "Power" to update.
(to me that sounds like how u flash a radio with a small 4mb zip file like team recovery file you rename to PG186.zip, so why are they linking to a 400mb rom file?)
to me that is how you flash a radio with a small PG186.zip file not a 300mb ROM file, so im confused on that, do i want to choose the zip to flash and flash that 300mb rom (which i have already done in the post 2 above this) or do i rename this 300mb file to PG186.zip so that the fastboot white screen AUTOMATICALY asks me if i want to update this file (flash a radio is what i understand this to be).
Please help guys, i have no phone and really stuck.
Click to expand...
Click to collapse
Ok thats the problem if ur going to activate a phone with sprint u need to have the old phone and the new phone off and then call them from another phone so they can activate the new esn..thats why when they try the ##3282 the password didnt work on the new phone cause the password they have is for the old phobe so fisrt call them activate the new phone and then the handsfree is going to the rest....but remeber dont use either the old phone or new phone to call them.
Sent From My HTC EVO 3D ROOTED
it keeps crashing during activation, so i just need to bring it in to the store with both phones and have them activate it there.
Before i can do this i have to make the phone stock, can someone please post the stock Sprint evo3d radio link so i can flash it?
i have the stock sprint rom, but i need the stock radio as ive already flashed it to an aftermarket radio.
(all the posts with the links here have invalid download links)
tks
jo2jo said:
it keeps crashing during activation, so i just need to bring it in to the store with both phones and have them activate it there.
Before i can do this i have to make the phone stock, can someone please post the stock Sprint evo3d radio link so i can flash it?
i have the stock sprint rom, but i need the stock radio as ive already flashed it to an aftermarket radio.
(all the posts with the links here have invalid download links)
tks
Click to expand...
Click to collapse
WHAT ROM DO U HAVE?
Sent From My HTC EVO 3D ROOTED
ok i think i bricked my phone..
i did this: and now the phone will not power on or anything:
C:\adb>fastboot oem writesecureflag 3
...
OKAY [ 0.045s]
finished. total time: 0.048s
C:\adb>
anyone???? crap..
jo2jo said:
ok i think i bricked my phone..
i did this: and now the phone will not power on or anything:
C:\adb>fastboot oem writesecureflag 3
...
OKAY [ 0.045s]
finished. total time: 0.048s
C:\adb>
anyone???? crap..
Click to expand...
Click to collapse
If you were on the ENG bootloader, then yes, you just bricked your phone when you ran that adb command.
If i was on the ENG bootloader? english bootloader? versus a french or another language bootloader?
Can you please explain so i know what i did wrong.
tks
jo2jo said:
If i was on the ENG bootloader? english bootloader? versus a french or another language bootloader?
Can you please explain so i know what i did wrong.
tks
Click to expand...
Click to collapse
Eng bootloader is engineering bootloader.
Via My HTC Evo 3D On The Now Network From Sprint.
jo2jo said:
If i was on the ENG bootloader? english bootloader? versus a french or another language bootloader?
Can you please explain so i know what i did wrong.
tks
Click to expand...
Click to collapse
Engineering is ENG. SHIP is the stock bootloader. The ENG bootloader is hboot 1.04, SHIP (stock) is 1.30/1.40/1.50. When you go into the bootloader it says either SHIP or ENG by the bootloader version.
Please go here now: http://forum.xda-developers.com/showthread.php?t=1653777
Mods should unsticky mine and sticky that instead.
Go to the above link if your a victim of virgin mobile firmware.
since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?
hockey4life0099 said:
since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?
Click to expand...
Click to collapse
So you have no data at all? I'd try a ##data# reset first.
hockey4life0099 said:
since the other thread got shut down before i got a response, i will repost now.
I flashed the original fix that was posted a few days ago and it worked great until today. I got my first radio interface error since the pri downgrade. Does this mean if i want to fix my issues completely i should go through these new downgrade instructions? I don't really care about a banner (or even roaming at the moment), since i am assuming an official sprint firmware update will come very soon. The only thing that i need right now to work is my texting. Any suggestions on doing the bare minimum to hold me over till the official firmware is released?
Click to expand...
Click to collapse
Never assume. Just because VM has a different firmware, that doesn't mean that Sprint 3d's will too. We do not fully know what the differences are between the 2 devices.
Thus the reason for this and other fix threads. I would suggest trying this fix, and see if it helps, and hope that there is a firmware fix in the future.
I will tell you how I restored my data. I first downloaded the following stock rom.
Stock 2.08.651.2 With HTC/Sprint Spyware Removed
http://forum.xda-developers.com/showthread.php?t=1285975
After flashing to the stock rooted rom above I then went into my dialer and typed in ##my MSL number# (Example: ##000000#) To get your MSL number simply download MSL reader from the market. I then clicked on edit and then edited my MDN with all zeros and MSID with all zeros. I pressed the menu button and then pressed reset. After the phone rebooted the phone activation screen came up when I unlocked the phone and it was able to automatically activate it and I got 3G data.
jlechner said:
So you have no data at all? I'd try a ##data# reset first.
Click to expand...
Click to collapse
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.
hockey4life0099 said:
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.
Click to expand...
Click to collapse
This is the issue some are having. I would say it's because of the VM firmware we flashed. Did you try the PRI version downgrade that takes you back to 003 even though it shows 005? or does yours still say 004?
hockey4life0099 said:
no, i have data ussually. I have found though every once in a while my sms messages will not send (with a radio interface error). When this happens, my phone will show a signal, but calls, sms, and data will not work until i do a profile or a prl update. then my phone will work normally again until it decides it wants to crap out yet again.
Click to expand...
Click to collapse
Hockey, I have not seen this issue yet on my rom, PM me if you want to try mine, and let me know if you see any difference. I wonder if some of the SMS issues have to do with the ICS rom itself. BTW do not post my ROM anywhere as I do not release my stuff public, just want to help out a fellow hardcore flasher.
Cheers
jlechner said:
This is the issue some are having. I would say it's because of the VM firmware we flashed. Did you try the PRI version downgrade that takes you back to 003 even though it shows 005? or does yours still say 004?
Click to expand...
Click to collapse
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue
Freeza or Unknownforce, I have a guy getting a replacement phone tomorrow. He wants to help. I figured we could have him pull the partitions, please advise.
hockey4life0099 said:
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue
Click to expand...
Click to collapse
Touch base with Mikey.
hockey4life0099 said:
i flashed chads first firmware downgrade. My phone now shows that my PRI is 1.53_145. This worked for like 3 days, but here i am again with the same issue
Click to expand...
Click to collapse
Oh perhaps you need to be on PRI version 1.42_003? I never ran into issues on chad's downgrad PRI either though.
This thread can't be deleted. This has good info we need up.
I know it says Chad in it, but should we just take the name out?
Well, if we did, then we won't give credit where it's due.
Anyways,
Is there any general thought on the rough percentage of people this works 100% for?
Mikee4fun said:
Oh perhaps you need to be on PRI version 1.42_003? I never ran into issues on chad's downgrad PRI either though.
Click to expand...
Click to collapse
is there a way to get to 1.42_003?
Thank god there's another one of these!
Ok so I got back from sprint again and the were totally in awe and had no idea whatsoever was wrong with my phone They ordered me a new one and it'll be here on like tuesday or wednesday and i'll see if I can get it not activated already.
Btw the sprint people are totally dumb.... They were talking to a couple and saying yeah, the more storage a phone has the faster it'll be! He said that 32gb phones out performed 16gb phones.... I was like wtf man... Also he was trying to sell them the galaxy s 2's and was telling them that they're new phones. Wtf sprint salesman, wtf...
hockey4life0099 said:
is there a way to get to 1.42_003?
Click to expand...
Click to collapse
The 005 mod is actually 003, from my understanding.
Sent from my Sprint/Virgin Mobile hybrid.
jlechner said:
Freeza or Unknownforce, I have a guy getting a replacement phone tomorrow. He wants to help. I figured we could have him pull the partitions, please advise.
Click to expand...
Click to collapse
Thanks, but I think we have everything we need at this point. I'm writing code right now for the patching part of the process. Not that I have everything that I need just yet, but at least getting that part out of the way for when I do have the correct information.
I've located everything that I have to change in my own partition to fix it (All the differences) next I'm going to compare these offsets with those of the partitions that freeza gives me and see if they line up the same... there's going to be some major coding needed for this, because it did manipulate some of the "flow" I think in the way it lists out certain information in the file, like rom name, and phone number and stuff...
I'm not the fastest coder, but I have basically all I need at this point for my own device... I just want to verify that it's similar code on others' devices as well before I get too far ahead of myself here and have to backtrack. I'm actually going to re-code the downgrade tool to make it part of that, probably rename it to a "multitool" of some kind and simply put it into the already stickied thread, and have closeone update his cd with it so that people can do this with ease.
The best part of this all is that the bricking process isn't going to be a stupid timing thing like it is when downgrading... a single command can brick an already S-OFF phone the way we need it. So no confusing timing issues with this one! Just a nice easy set of instructions. Phew.
Short and sweet basic steps right now:
1.) Nand Backup
2.) Brick
3.) Run "multitool" Plug unplug, yadda yadda.
4.) Boot phone back up to 1.40 S-ON
5.) Run 1.13 RUU
6.) Revolutionary S-OFF
7.) Flash 2.17 Firmware
8.) Flash recovery
9.) Restore Backup
10.) Drink Beer
More details to follow.
hockey4life0099 said:
is there a way to get to 1.42_003?
Click to expand...
Click to collapse
Yes, you need to go through the adb push process stated in the OP. I can assist you if you want through team viewer if you don't want to tackle it.
Unknownforce said:
Thanks, but I think we have everything we need at this point. I'm writing code right now for the patching part of the process. Not that I have everything that I need just yet, but at least getting that part out of the way for when I do have the correct information.
I've located everything that I have to change in my own partition to fix it (All the differences) next I'm going to compare these offsets with those of the partitions that freeza gives me and see if they line up the same... there's going to be some major coding needed for this, because it did manipulate some of the "flow" I think in the way it lists out certain information in the file, like rom name, and phone number and stuff...
I'm not the fastest coder, but I have basically all I need at this point for my own device... I just want to verify that it's similar code on others' devices as well before I get too far ahead of myself here and have to backtrack. I'm actually going to re-code the downgrade tool to make it part of that, probably rename it to a "multitool" of some kind and simply put it into the already stickied thread, and have closeone update his cd with it so that people can do this with ease.
The best part of this all is that the bricking process isn't going to be a stupid timing thing like it is when downgrading... a single command can brick an already S-OFF phone the way we need it. So no confusing timing issues with this one! Just a nice easy set of instructions. Phew.
Short and sweet basic steps right now:
1.) Nand Backup
2.) Brick
3.) Run "multitool" Plug unplug, yadda yadda.
4.) Boot phone back up to 1.40 S-ON
5.) Run 1.13 RUU
6.) Revolutionary S-OFF
7.) Flash 2.17 Firmware
8.) Flash recovery
9.) Restore Backup
10.) Drink Beer
More details to follow.
Click to expand...
Click to collapse
Cool thanks!
Sent from my Sprint/Virgin Mobile hybrid.
Hi All,
I have been trying to get the FW update with extreme save mode for almost a week now.
I check for software updates daily and I get the NO UPDATE found message.
Called At&t and tech support is as useful as my 3 years old kid.
Does anyone have the same problem? Solutions?
Thanks
Unlock bootloader, install Android Revolution thats been updated with latest release and you are good to go. No reason to wait till they let it work for yea when you can do it yourself.
JayRolla said:
Unlock bootloader, install Android Revolution thats been updated with latest release and you are good to go. No reason to wait till they let it work for yea when you can do it yourself.
Click to expand...
Click to collapse
Thanks for the advice, but others are getting the update OTA, without root or downloading Android Rev.
Some M8 owners may see a delay in getting the OTA, as it rolls out sequentially, by some means (I've seen AT&T suggest its by IMEI number). A minority of folks will never get it, just by some random fluke or other (as happens on any OTA).
If you don't want to wait, the RUU is already posted. You can download to a PC, and run it with your phone connected. But it will wipe user data.
http://forum.xda-developers.com/showthread.php?t=2757462
redpoint73 said:
Some M8 owners may see a delay in getting the OTA, as it rolls out sequentially, by some means (I've seen AT&T suggest its by IMEI number). A minority of folks will never get it, just by some random fluke or other (as happens on any OTA).
If you don't want to wait, the RUU is already posted. You can download to a PC, and run it with your phone connected. But it will wipe user data.
http://forum.xda-developers.com/showthread.php?t=2757462
Click to expand...
Click to collapse
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Also, has everyone that attempted to download things manually received the update?
I would really appreciate the responses
sassij said:
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Also, has everyone that attempted to download things manually received the update?
I would really appreciate the responses
Click to expand...
Click to collapse
How did it not work? As long as you are completely stock with cid cws__001 it should work.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
sassij said:
Hi All,
I have been trying to get the FW update with extreme save mode for almost a week now.
I check for software updates daily and I get the NO UPDATE found message.
Called At&t and tech support is as useful as my 3 years old kid.
Does anyone have the same problem? Solutions?
Thanks
Click to expand...
Click to collapse
download ota package from here http://www.androidfilehost.com/?fid=23487008491963146
put it on your micro sd card
boot to recovery "vol up and power 10 sec, vol down and power until boot loader comes up and navigate to recovery"
once in recovery its either vol up and power or vol down and power for a few seconds for advanced options
choose install update from external sd.
sassij said:
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Click to expand...
Click to collapse
No, the phone does not need to be modded to run the RUU. Its a "official" update/recovery tool provided by HTC. If you phone is stock, it should work, as the above response also indicated.
If it "wouldn't work" it would be more helpful to give details, if you want proper help. Not just say it didn't work. What step did it fail at , any error message, etc. Also, the current state of your phone (root, unlocked bootloader, etc.), as we can only assume based on your comment about root, etc.
RUU failing on a stock device is usually a USB connectivity issue on the part of your computer (not a problem on the phone's side). Install or re-install the HTC drives, try a different USB port, or a different computer (if available). If on Windows 8.1, that version is a known issue and will not work with the HTC drivers. You can also try re-downloading the RUU to make sure it wasn't damaged/corrupted during download.
Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
homthtrnut said:
Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
Click to expand...
Click to collapse
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Just need to dig in and get it done!
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I can do anything that is new to me with good instructions. I WAS able to unlock, root, and flash a ROM with good success following the steps. What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk. Before I started anything , I backed it up using HTC SYNC on my laptop. Is that useful in returning it to stock? Or is that just for media and texts and such? Maybe what I should do is check the forum where the Revo users are and see what they say. Sorry if it sounds like Im thinking out loud but Im a noob at forums and flashing. And Im getting burnt out on having a phone that doesnt receive calls properly. Not to mention burnt out from working all day and coming home to try and solve this mystery. OK I wont mention it. Thanks to those who have attempted to give me input here to try to figure this thing out.
Just a lil something to think about...,youll not have dialer, vvm messages,contacts integrated,signal will probably be not as good,and no VoLTE when using euro ROM's. Stand alone vvm app may or may not install from playstore if you use it. My suggestion,flash back to stock,wait alil while and get an official Lollipop release from ATT.
Flash a twrp backup of latest 4.4.4
Flash stock recovery from latest 4.4.4
Steps above will put you back to as close to stock as possible,without relocking bootloader and reflashing the exe ruu file.
homthtrnut said:
What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk.
Click to expand...
Click to collapse
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Flashed firmware successfully.........darn .zip.zip tricksters!!!! Anyway!
redpoint73 said:
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Click to expand...
Click to collapse
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done. Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do. I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious. Now to see if I can receive calls again. Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
homthtrnut said:
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done.
I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious.
Click to expand...
Click to collapse
Do yourself a huge favor, and turn off the Windows option (if you haven't already) to hide known file extensions. The option is usually enabled by default. I suspect its mainly meant to prevent non-tech savvy PC users from deleting or modifying file extensions and rendering files unusable (or at least not associated with a program to open it).
For most folks who are going to be messing with things like modding phones, and even halfway familiar with the file extensions, the option to hide them is counter-productive and confusing.
The recommendation to rename the file to firmware.zip is valid. This is done since the files are often named things like 4.16.401 to differentiate the firmwares from each other (such as in firmware collections). Technically, you didn't rename the file to firmware.zip (although Windows make it look like you did), you actually named it firmware.zip.zip, even though Windows didn't display it that way.
homthtrnut said:
Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do.
Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
Click to expand...
Click to collapse
To unlock the bootloader again, simply go through the HTCDev.com process to get another unlock bin token, then run the fastboot command with that token again (like you did the first time).
On past devices, it was sometimes possible to reuse the original token (run the fastboot command with it). But an XDA user commented that doesn't work on this device (and that you need to get a new token). But you can always try it, if you want.
Flashed firmware and now stuck in HBOOT! I REALLY NEED HELP NOW
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258 and after numerous attempts to flash I finally got it to go by getting rid of the renamed .zip at the end. ( It was already a zip file) I think a lot of people have had that problem. Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again. Can anyone point me? I'll buy you a beer! or 12
homthtrnut said:
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258
Click to expand...
Click to collapse
401 firmware is Euro based firmware. AT&T is 501.
homthtrnut said:
Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again.
Click to expand...
Click to collapse
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
hboot and radio numbers currently on m8
redpoint73 said:
401 firmware is Euro based firmware. AT&T is 501.
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
Click to expand...
Click to collapse
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
That is the Android 4.4.4 radio. Meaning the 401 firmware you linked and tried to flash didn't take. And it won't with s-on, unless its signed and hacked to accept AT&T's CID (which I don't think there is any 401 firmware that meets those requirements).
Agree with the above response, in that the easiest way to get the phone up and running again is relock the bootloader and RUU to stock.
Since your device is hboot 3.19, you are stuck with s-on and that means you are stuck on KitKat firmware until AT&T releases Lollipop officially.
That also means you can only run ROMs that support 4.4.4 firmware (no LP based Sense ROMs), otherwise you will run into various serious bugs like the call issue on ARHD (or broken WiFi). There are some LP GPE and AOSP ROMs that support the 4.4.4 firmware, if you want to go that route.
Was just starting out, not enough experience.
bford152 said:
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
Click to expand...
Click to collapse
The above phone was eventually returned. Now I have an unlocked, s off M8. With help from PearlyMon I was able to do it all about a month ago. Now I'm just waiting to work up the nerve to flash a customer Rom and also add in the H/K sound feature. Really liked the HD Revolution Rom, I just didn't have the wherewithall to find and install the proper firmware. This time around will be better. On third M8 now. First one, brand new slipped out of workshirt pocket and faceplanted on a tile floor. First damn day! Didn't have the otter box defender case like I should've. 2nd and 3rd ones have been refurbs. So who knows how much use the battery saw before? So I'd like a nice Rom that has built in low battery drain. Every day it seems to drain off a little sooner. Went to black background today to help it out a little. Anyway, haven't been on this forum much since the above problem and thought I'd touch base with you and say thanks. Have a nice one.
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
jon145 said:
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
Click to expand...
Click to collapse
Some folks have been having issues with "international" based custom ROMs on AT&T's LTE network. It seems that AT&T has been making some changes to LTE, possibly in preparation for Voice over LTE (VoLTE, which AT&T calls "HD Voice"), that are messing up voice calls on "international" ROMs.
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
You might try WNC's ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Its based on the Lollipop Developer's Edition ROM, which is intended for use on AT&T's network. He's working on a version based on the AT&T 4.28 update, but its still in testing and not posted yet.
Yeah I've been running the SD 9.0 for several days and no love here in Dallas ... I could speculate for days since D is AT&T's home city.
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
jon145 said:
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
Click to expand...
Click to collapse
He has a beta in testing right now. Just ping him, and he will probably send you a link to the test build. Probably the only reason he would say "no" is if he is going to release soon anyway.
redpoint73 said:
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
Click to expand...
Click to collapse
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
rhughes93 said:
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
Click to expand...
Click to collapse
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
redpoint73 said:
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
Click to expand...
Click to collapse
So I re-flashed SkyDragon, and I think I was not understanding the difference between AROMA installer and the software itself. When I did it the first time, I think I did select T-mobile with wifi calling in AROMA, but AT&T within the software SIM setup. It did not work. Now after getting the stock ROM working, I re-flashed, chose the Other GSM/WWE/whatever option within AROMA, AT&T within the software, and all is right in the world. I may also try the same with Venom this weekend now that I have good restore options, though I don't recall if it had similar options in AROMA or not.
Honestly found it on XDA of all places after looking for it all night
What does 1.16 give us that 1.14 doesn't? Everything honestly. Could not get my Wing recognized to flash with 1.14. No 1.15 Patched exists either
We can downgrade with ChipErase (and restore IMEI), we can modify PDM, we can dump the entire phone (will do tomorrow), can upgrade.
See link here for link: https://forum.xda-developers.com/t/...er-w-fastboot-drivers-and-common_dll.4304181/
This was the only working LGUp_Tool that worked outside of LGUP CMD
I wanted this to try other countries firmware files to see if we get other weird results. This should also allow custom KDZ files? from my understanding
ADDED INFO Nov 8, 2021
How to use LGUp Tool From this Download
1.) Download the LGUp 1.16.03 Patched from the XDA Link above
2.) Run the EXE as admin so it can install Drivers and the software properly
3.) Go to the install directory and run the 2 Bat files that are in the folder as admin
Code:
Default: C:\Program Files(x86)\LG Electronics\LGUp
-- Running LGUP_UI-fixer.bat -- run as admin, follow instructions, run the software when it says to, then close it
-- Run LGUP_UI-Fixer-addon.bat -- run as admin, follow steps, then run LGUp.exe when patch complete
You now have a working LGUP Tool 1.16 Patched for the LG Wing
Explaining the functions of LGUP Tool
Code:
REFURBISH： You will lose all user data（KDZ or TOT）
UPGRADE: Keep data and update your phone（KDZ or TOT) - Select Upgrade to flash kdz firmware to unbrick/restore your phone back to stock.
Chip Erase: Dangerous, This will erase IMEI/efs, do not try this if you do not have a NV backup. - Chip Erase can also remove the Google FRP on many LG devices with Android 5.0, 6.0.
PARTITION DL：Flash the single Partition or selected partitions onto your phone. - This feature can solve “unknown model” issues. This feature can be used to bypass Google FRP by flashing specific tot firmware.
DUMP：Dump all partitions of your phone as backup. - Dump the stock firmware from a working phone as back up and use Partition DL to restore phones.
FOTA Upgrade: This can be used to flash OTA Update file that comes with dot up file extension.
PDM: Change imei, wifi address, bluetooth, mac address
video for how to use LGUP Tool to flash the Wing
Awesome! I just DL'ed.. don't know when I'll have time to mess around with it. Or if I have the skill set to help. But I would definitely try to help out if I can and be excited for rootable firmware.
kaluna00 said:
Awesome! I just DL'ed.. don't know when I'll have time to mess around with it. Or if I have the skill set to help. But I would definitely try to help out if I can and be excited for rootable firmware.
Click to expand...
Click to collapse
I plan on making a video I'll put on the post explaining the tool
KaptinBoxxi said:
I plan on making a video I'll put on the post explaining the tool
Click to expand...
Click to collapse
Holy cow I can’t believe it. You actually found the exact tool that we needed! I went ahead and did a chip erase on my demo model, which had previously been flashed with the Korean firmware from the previous tutorial, and flashed the T-Mobile Firmware. IT WORKED! To get rid of the error at that shows up every time you reboot it, I accessed the hidden menu and changed the TN number to the one associated with TMO_US, as shown in this post.
Thank you!
twocans said:
Holy cow I can’t believe it. You actually found the exact tool that we needed! I went ahead and did a chip erase on my demo model, which had previously been flashed with the Korean firmware from the previous tutorial, and flashed the T-Mobile Firmware. IT WORKED! To get rid of the error at that shows up every time you reboot it, I accessed the hidden menu and changed the TN number to the one associated with TMO_US, as shown in this post.
Thank you!
Click to expand...
Click to collapse
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
KaptinBoxxi said:
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
Click to expand...
Click to collapse
Where did you get the Verizon firmware?
kaluna00 said:
Where did you get the Verizon firmware?
Click to expand...
Click to collapse
I found a site that had a "KDZ Downloader" and used that to download it. I can upload it here for those who need it once i redownload it here at work
or you can yourself from this post. Just need the LG URL to the firmware
[LG TOOLS] LG-KDZ-dll-Tool/LGUP_UI-fixer/LG-Kdz-downloader
Please, do not share elsewhere as I want to be able to update if necessary ! LG-KDZ-dll-Tool/KDZ dll extractor (=old version) : this message actually, scroll down a bit... LGUP_UI-fixer LG-Kdz-downloader Share this thread or my blog instead...
forum.xda-developers.com
KaptinBoxxi said:
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
Click to expand...
Click to collapse
I bought a mint mobile trial sim from amazon and I’m getting calls, text, and 5G data.
twocans said:
I bought a mint mobile trial sim from amazon and I’m getting calls, text, and 5G data.
Click to expand...
Click to collapse
I get calls and text, no cell service at all. I had to manually program in an IMEI. My IMEI comes back as 0 if I just flash it without PDM. IMEI doesn't apply via the service menu either
KaptinBoxxi said:
I get calls and text, no cell service at all. I had to manually program in an IMEI. My IMEI comes back as 0 if I just flash it without PDM. IMEI doesn't apply via the service menu either
Click to expand...
Click to collapse
Interesting. I was able to generate an IMEI in the hidden menu after the chip erase and it worked fine. I did also have to re-add my CSN, because that was also removed, and then my phone did an unprompted factory reset and rebooted.
By the way, when you flashed it, did you use Refurbish? Because with my demo unit, it refused to let me do that and would only allow chip erase. I was reluctant, but it turned out fine. And, the only important thing I was unable to reprogram afterwords was the S/N, but it doesn’t really matter to me. (Too bad the fingerprint scanner still doesn’t work though. That’s the only thing left that still isn’t working after all of this.)
twocans said:
Interesting. I was able to generate an IMEI in the hidden menu after the chip erase and it worked fine. I did also have to re-add my CSN, because that was also removed, and then my phone did an unprompted factory reset and rebooted.
By the way, when you flashed it, did you use Refurbish? Because with my demo unit, it refused to let me do that and would only allow chip erase. I was reluctant, but it turned out fine. And, the only important thing I was unable to reprogram afterwords was the S/N, but it doesn’t really matter to me. (Too bad the fingerprint scanner still doesn’t work though. That’s the only thing left that still isn’t working after all of this.)
Click to expand...
Click to collapse
I plan on testing every function to document what happens, so far I've done Refurbish, Partition DL, Dump, PDM and ChipErase. only Dump didn't work
Nice work fellas!!! Exciting to see some movement towards being able to root/development.
kaluna00 said:
Nice work fellas!!! Exciting to see some movement towards being able to root/development.
Click to expand...
Click to collapse
@KaptinBoxxi
BTW... How do you get to the hidden menu on the Verizon Varient?
kaluna00 said:
@KaptinBoxxi
BTW... How do you get to the hidden menu on the Verizon Varient?
Click to expand...
Click to collapse
I think its the same dial code. I don't have the device in front of me at the moment to say
I tried this earlier...
Post in thread 'LG Wing 5G Network option activation' https://forum.xda-developers.com/t/lg-wing-5g-network-option-activation.4285275/post-85116977
Am I using the wrong dial code for Verizon?
kaluna00 said:
I tried this earlier...
Post in thread 'LG Wing 5G Network option activation' https://forum.xda-developers.com/t/lg-wing-5g-network-option-activation.4285275/post-85116977
Am I using the wrong dial code for Verizon?
Click to expand...
Click to collapse
I have yet to have network work on my demo device regardless of what firmware is on it because my Serial Number and IMEI always come back at 0 and even if I manually enter new ones, it doesn't acivate, although i was able to get to the menu just fine with the standard code in that post.
Interesting, I wonder if there's something different in your firmware or kdz...
looking at the software version. mine is on
F100VM10i
maybe they (Verizon) patched out the hidden menu. your KDZ is labeled
F100VM10d
???
kaluna00 said:
looking at the software version. mine is on
F100VM10i
maybe they (Verizon) patched out the hidden menu. your KDZ is labeled
F100VM10d
???
Click to expand...
Click to collapse
I'm not sure what the final letter signifies, but F100V is verizon, yeah
KaptinBoxxi said:
I'm not sure what the final letter signifies, but F100V is verizon, yeah
Click to expand...
Click to collapse
think that represents the SW iteration identifier between updates... bit of a guess, but i believe that character has changed with updates.