Related
Hi.
I heard from someone that there is an app that enables a danish Magic to fully access the android market thereby bypassing the region restriction. Is that true?
I´ve done a search. Nothing found.
yes, google for marketenabler
Thanks. Cheers.
You must root your phone for that to work.
maedox said:
You must root your phone for that to work.
Click to expand...
Click to collapse
I´ve just rooted the phone and the enabler tells me that everything is ok. But I still only get the free apps in market..
How do I check to see it my phone really is rooted? Might be that I´ve messed up ?
Did you remember to kill your market process and clear its cache before trying to go in again?
Did it and it works.. thanks..
Tuco Benidicto Pacifico Juan Maria Ramirez?
I've been having problems with this app. My phone IS rooted yet whenever I try to choose a source in the list I get the "we got a problem houston " error message! Can someone please help?
BTW, I'm a Rogers customer.
rickytenzer said:
I've been having problems with this app. My phone IS rooted yet whenever I try to choose a source in the list I get the "we got a problem houston " error message! Can someone please help?
BTW, I'm a Rogers customer.
Click to expand...
Click to collapse
use the new 3.0.1 beta version. works for me when the older one doesnt.
nmesisca said:
use the new 3.0.1 beta version. works for me when the older one doesnt.
Click to expand...
Click to collapse
Could you explain your steps to me? No matter what version I try, I ALWAYS get the "we got a problem Houston " error message. This is what I did:
Downloaded MarketEnabler_v3.0.1-beta.apk
Put it in C:\AndroidSDK\
Opened cmd from run
Went to C:\AndroidSDK\
adb install MarketEnabler_v3.0.1-beta.apk
Completed successfully
Went to applications in my Magic and force stopped Market as well as cleared the cache
Opened Market Enabler and tried the German source
Error message comes up!
Thanks for the help
And yes, my phone IS rooted.
EDIT: Didn't have Superuser installed! It works fine now although ATM it doesn't show any paid apps...
rickytenzer said:
Could you explain your steps to me? No matter what version I try, I ALWAYS get the "we got a problem Houston " error message. This is what I did:
Downloaded MarketEnabler_v3.0.1-beta.apk
Put it in C:\AndroidSDK\
Opened cmd from run
Went to C:\AndroidSDK\
adb install MarketEnabler_v3.0.1-beta.apk
Completed successfully
Went to applications in my Magic and force stopped Market as well as cleared the cache
Opened Market Enabler and tried the German source
Error message comes up!
Thanks for the help
And yes, my phone IS rooted.
EDIT: Didn't have Superuser installed! It works fine now although ATM it doesn't show any paid apps...
Click to expand...
Click to collapse
try clearing the cache again. it definitely works every time for me.
hey guys can u please help me out i need to root my phone but am unable to do so.. I am from india .and i guess have regional restrictions on...I do not have the market ...??:-( i tried to use the instructions on
http://forum.xda-developers.com/showthread.php?p=4335330#post4335330
but i get stuck on point 6, am unable to get the command prompt it.. i get a message saying " this path does not exist "??/ wt am i doing wrong?? have i typed something wrong in step 3?
can anyone please tell me wt to do???
aamodr said:
hey guys can u please help me out i need to root my phone but am unable to do so.. I am from india .and i guess have regional restrictions on...I do not have the market ...??:-( i tried to use the instructions on
http://forum.xda-developers.com/showthread.php?p=4335330#post4335330
but i get stuck on point 6, am unable to get the command prompt it.. i get a message saying " this path does not exist "??/ wt am i doing wrong?? have i typed something wrong in step 3?
can anyone please tell me wt to do???
Click to expand...
Click to collapse
step 3 is enabling debug mode, so i dont know what you could have typed wrong.
point 6 is just to open a command prompt. have you tried with the Command Prompt icon in Windows?
aamodr said:
hey guys can u please help me out i need to root my phone but am unable to do so.. I am from india .and i guess have regional restrictions on...I do not have the market ...??:-( i tried to use the instructions on
http://forum.xda-developers.com/showthread.php?p=4335330#post4335330
but i get stuck on point 6, am unable to get the command prompt it.. i get a message saying " this path does not exist "??/ wt am i doing wrong?? have i typed something wrong in step 3?
can anyone please tell me wt to do???
Click to expand...
Click to collapse
You can try to use the method ekindangen is showing in this thread:
[ROM] Change the perfected SPL HBOOT 1.33.0010 to 1.33.0009
And after that you can choose to use flashrec to get recovery-RAv1.2.1H.img on your device or just use adb fastboot method. And then flash the rom you desire into your mobile.
But before you do so please confirm that you got a 32A with the perfect SPL 1.33.0010 for your own sake You should have, and method worked for me and was really easy!
Hello,
My 510 x64 phone received a new update from HTC.
OTA_A11_UL_K443_DESIRE_SENSE60_HTC_Europe_1.51.401.2-1.51.401.1_release_4271720d6aeagtsc88zjb1
Is a 30 Mb file that should contain some fixes.
The issue is that the phone re-boots in recovery and at 30 % of the green bar the installation fails. A red download icon shows in the middle of the screen and nothing happens.
In the past i flash some different recovery files but i returned to stock ( stock files that i found online for x64 - 16.0 MB (16,777,216 bytes) )
Can someone please advise if this could be related to my recovery image ?
mzqaddicted said:
Hello,
My 510 x64 phone received a new update from HTC.
OTA_A11_UL_K443_DESIRE_SENSE60_HTC_Europe_1.51.401.2-1.51.401.1_release_4271720d6aeagtsc88zjb1
Is a 30 Mb file that should contain some fixes.
The issue is that the phone re-boots in recovery and at 30 % of the green bar the installation fails. A red download icon shows in the middle of the screen and nothing happens.
In the past i flash some different recovery files but i returned to stock ( stock files that i found online for x64 - 16.0 MB (16,777,216 bytes) )
Can someone please advise if this could be related to my recovery image ?
Click to expand...
Click to collapse
I flashed stock recovery and update installed successfully, you can give me update file?
Uploaded the file
https://drive.google.com/file/d/0B_bbXjxfqWaeMEFjUmE1ZlhFMmM/view?usp=sharing
can you please share your stock boot & recovery files ?
mzqaddicted said:
Uploaded the file
https://drive.google.com/file/d/0B_bbXjxfqWaeMEFjUmE1ZlhFMmM/view?usp=sharing
can you please share your stock boot & recovery files ?
Click to expand...
Click to collapse
With this recovery I flashed update.
https://drive.google.com/open?id=0B3-NJk0QRfxXaG5sWDc1NG5tbzg&authuser=0
EDIT: Try this recovery, is extracted from update.
https://drive.google.com/file/d/0B3-NJk0QRfxXNzBZbFFiRk5HclE/view?usp=sharing
tried both of them and i have the same issue.
https://drive.google.com/file/d/0B_bbXjxfqWaeVXJqZFBIaTZySGc/view?usp=sharing
mzqaddicted said:
tried both of them and i have the same issue.
https://drive.google.com/file/d/0B_bbXjxfqWaeVXJqZFBIaTZySGc/view?usp=sharing
Click to expand...
Click to collapse
Lock bootloader => run this RUU => update
lucyr03 said:
Lock bootloader => run this RUU => update
Click to expand...
Click to collapse
the RUU installer doesn't work.. somehow.. after i accept the licence agreement nothing happens and the installation shield application disappears.
Thried on 2 dif computer, both W7 x64, latest drivers via HTC sync manager
updated Visual C++ Redistributable for Visual Studio 2012 Update 4
mzqaddicted said:
the RUU installer doesn't work.. somehow.. after i accept the licence agreement nothing happens and the installation shield application disappears.
Thried on 2 dif computer, both W7 x64, latest drivers via HTC sync manager
updated Visual C++ Redistributable for Visual Studio 2012 Update 4
Click to expand...
Click to collapse
Work for me, but take more time to open and you have to wait after accept license...
How i can lock bootloader? I am looking instruction and i can't find :/
Ok i find command "fastboot oem lock" lock bootloader. Now I install RUU from link on post lucyr03 but this version is Europe_1.51.401 .1. Today my phone first time find new update to version Europe_1.51.401 .2-1.51.401.2. What is a diffrent of this version?
Misarus said:
How i can lock bootloader? I am looking instruction and i can't find :/
Ok i find command "fastboot oem lock" lock bootloader. Now I install RUU from link on post lucyr03 but this version is Europe_1.51.401 .1. Today my phone first time find new update to version Europe_1.51.401 .2-1.51.401.2. What is a diffrent of this version?
Click to expand...
Click to collapse
Install RUU from my post and update with OTA.
mzqaddicted said:
Hello,
My 510 x64 phone received a new update from HTC.
OTA_A11_UL_K443_DESIRE_SENSE60_HTC_Europe_1.51.401.2-1.51.401.1_release_4271720d6aeagtsc88zjb1
Is a 30 Mb file that should contain some fixes.
The issue is that the phone re-boots in recovery and at 30 % of the green bar the installation fails. A red download icon shows in the middle of the screen and nothing happens.
In the past i flash some different recovery files but i returned to stock ( stock files that i found online for x64 - 16.0 MB (16,777,216 bytes) )
Can someone please advise if this could be related to my recovery image ?
Click to expand...
Click to collapse
I forgot you posted this already. I just received a 30MB update from Boost Mobile on the 32 bit version and it fails the same exact way yours does. I contacted HTC and Boost Mobile and it seems if it doesn't update properly we have to wait for HTC to release it in the form of a RUU, which I believe they will just wait for Lollipop and bundle this little fix in with the Lollipop update. I searched on their site to see if there was anyway we could manually update and it doesn't exist. There are only old ROMs. I tried some tricks to manually update and it failed every time. I am completely stock on the Boost Mobile RUU and I totally deleted everything before the install so there aren't any problems on my end. There is simply a problem with the way they are attempting to update our phones.
Pretty sure you cant update if unlocked and rooted. Has to be like out of the box running. I couldnt but I did update on my wifes locked/unrooted phone no problem. Took 10 minutes. Checking it out, couldnt really see much, if any, difference. 30mb is pretty small.
CSP III said:
Pretty sure you cant update if unlocked and rooted. Has to be like out of the box running. I couldnt but I did update on my wifes locked/unrooted phone no problem. Took 10 minutes. Checking it out, couldnt really see much, if any, difference. 30mb is pretty small.
Click to expand...
Click to collapse
I am on the Boost Mobile stock RUU, locked, and unrooted.
I just noticed the error message in the stock recovery:
htc/sprint_wwe_vm/htc_a11chl:4.4.2/KOT49H/373881.1:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "htc/sprint_wwe_vm/htc_a11chl:4.4.2/KOT49H/373881.2:user/release-keys"
Installation aborted.
Write host_mode:0 done
I did
adb shell
getprop ro.build.fingerprint on my phone and I got:
htc/sprint_wwe_vm/htc_a11chl:4.4.2/KOT49H/433600.1:user/release-keys
This is on the stock Boost RUU, locked, and unrooted.
There are some other items in build.prop that are different than what the update is looking for.
I am going to change them to what is in my phone and try again.
I don't expect it to work, but it can't hurt.
If it doesn't work, I'll try a stock Rom backup from this site, then try the update again.
Sounds good man. Check back in with the results, I'd like to see how it turns out for you. IMO though, I really think the update isn't worth all the hassle but I totally get it if you are/want to just get it to work. I'd probably do the same. good luck.
CSP III said:
Sounds good man. Check back in with the results, I'd like to see how it turns out for you. IMO though, I really think the update isn't worth all the hassle but I totally get it if you are/want to just get it to work. I'd probably do the same. good luck.
Click to expand...
Click to collapse
Thanks. I know it's not really worth the hassle, but I'm learning a lot by messing with it. It's not working, still. I may be wrong but I think they made a mistake with the build.prop when sending the updates to some of our phones. I think some of us just have to wait for Lollipop.
Hi. I am in the UK and have the first gen moto x. i was dicking around with roms etc and i ended up accidentally erasing internal storage. I managed to the get the phone back to how it was apart from the fact that it cannot make calls, text, get 3g signal. it is essentially a small tablet. when i use the dialler code to show the imei number it is 0. i tried reinstalling modems etc and none have worked. i have tried differnet roms and even flashing lollipop. I am wondering if the modems files i am using are not working because they are US files and I need some kind of EU file? Idk.
I had my imei written down so i was going to try and change it to that on the phone but engineer tools does not open or even seem to exist on the phone. i cant try using the stock rom etc because it is on a site (something like sbf developers ) that says it is forbidden. i literally have tried everything. can anyone help? :crying:
azerouz said:
Hi. I am in the UK and have the first gen moto x. i was dicking around with roms etc and i ended up accidentally erasing internal storage. I managed to the get the phone back to how it was apart from the fact that it cannot make calls, text, get 3g signal. it is essentially a small tablet. when i use the dialler code to show the imei number it is 0. i tried reinstalling modems etc and none have worked. i have tried differnet roms and even flashing lollipop. I am wondering if the modems files i am using are not working because they are US files and I need some kind of EU file? Idk.
I had my imei written down so i was going to try and change it to that on the phone but engineer tools does not open or even seem to exist on the phone. i cant try using the stock rom etc because it is on a site (something like sbf developers ) that says it is forbidden. i literally have tried everything. can anyone help? :crying:
Click to expand...
Click to collapse
Hey! If you've installed a US ROM, you are using the wrong baseband files to access your service provider network ( XT1053- US ; XT1052- UK)
Try installing an XT1052 based rom and report back . Also, be careful while flashing your new chosen ROM. Ensure that it does not downgrade / modify your current bootloader as you may end up bricking your phone (since you've upgraded to LP)
Best of luck mate .
Bhargav4591 said:
Hey! If you've installed a US ROM, you are using the wrong baseband files to access your service provider network ( XT1053- US ; XT1052- UK)
Try installing an XT1052 based rom and report back . Also, be careful while flashing your new chosen ROM. Ensure that it does not downgrade / modify your current bootloader as you may end up bricking your phone (since you've upgraded to LP)
Best of luck mate .
Click to expand...
Click to collapse
Ty for the reply. I just tried flashing a rom for the 52 instead of the 53 and twrp gives an error message of "This package is for the device: xt1052 ghost, xt1052 ghost etc.. this device is ." the etc is just a couple more models but the device doesnt seem to know what it is? its saying becuase it is for the 52 it cannot install even though the device is the 52.
azerouz said:
Ty for the reply. I just tried flashing a rom for the 52 instead of the 53 and twrp gives an error message of "This package is for the device: xt1052 ghost, xt1052 ghost etc.. this device is ." the etc is just a couple more models but the device doesnt seem to know what it is? its saying becuase it is for the 52 it cannot install even though the device is the 52.
Click to expand...
Click to collapse
Strange . Do elaborate as to what rom you are flashing and which rom you are currently using (The one that has a problem).
Also, are you wiping the system before flashing ?
Bhargav4591 said:
Strange . Do elaborate as to what rom you are flashing and which rom you are currently using (The one that has a problem).
Also, are you wiping the system before flashing ?
Click to expand...
Click to collapse
Hi again. i googled xt1052 rom and found a few. the one i tried was cyanhacker(obviously based on cm). after i got that error i tried editing the updater script to skip over the process in which it checks what device it is on. after that it appeared to flash successfully but when i tried to boot it showed the bootloader unlocked screen, vibrated then restarted and just kept doing that bootloop.
azerouz said:
Hi again. i googled xt1052 rom and found a few. the one i tried was cyanhacker(obviously based on cm). after i got that error i tried editing the updater script to skip over the process in which it checks what device it is on. after that it appeared to flash successfully but when i tried to boot it showed the bootloader unlocked screen, vibrated then restarted and just kept doing that bootloop.
Click to expand...
Click to collapse
1. Please download the correct ROM for your device from here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
2. Head over here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 and follow the Instructions. CAUTION: If you decide yourself for manual flashing DO NOT PASTE THIS CODE:
Code:
fastboot oem config carrier vzw
Or you'll end up, like me: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
In case I could help you with some guidance, I would be happy, if you could help me, in my thread.
//EDIT: Your battery should be on 70% or more, before you try to do anything! Keep this in mind, else flashing could be interrupted!
Kind regards
Xanthales said:
1. Please download the correct ROM for your device from here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
2. Head over here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 and follow the Instructions. CAUTION: If you decide yourself for manual flashing DO NOT PASTE THIS CODE:
Code:
fastboot oem config carrier vzw
Or you'll end up, like me: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
In case I could help you with some guidance, I would be happy, if you could help me, in my thread.
//EDIT: Your battery should be on 70% or more, before you try to do anything! Keep this in mind, else flashing could be interrupted!
Kind regards
Click to expand...
Click to collapse
Thankyou so much. did what you said. tinkered in twrp. flashed a lollipop rom and made a call. My man right here <3
azerouz said:
Thankyou so much. did what you said. tinkered in twrp. flashed a lollipop rom and made a call. My man right here <3
Click to expand...
Click to collapse
No problem, im glad to hear, that I could help you!
Maybe you can help me here?: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
This would be awesome, if you got a retail device!
Hello, guys! After installing the latest update on my Galaxy A6 (A600FN) the touch screen stopped working. I tried flashing all 3 ROMs for my region that had the version 5 bootloader with Odin and none of them fixed the issue. One of them was Android 10 and 2 were Android 9. ROMs with an older version of the bootloader would fail the flash because apparently you can't downgrade it. It shows this error: Sw rev. Check fail. Device: 5, binary 3. I'm certain it's not a hardware issue because I had this happen on 2 A6 devices right after the update. I thought of trying a custom ROM but I can't find one for A6, only A6+. What can I do here? Can I trick it somehow to downgrade it? Is there some command I can send through adb shell to fix the touchscreen? Any help would be greatly appreciated!
BTW, I can access the device via a USB OTG mouse and it works perfectly fine.
Bump. Please, any help is appreciated!
Do you tried factory reset from recovery?
Zevnor said:
Do you tried factory reset from recovery?
Click to expand...
Click to collapse
That was the first thing I tried. Didn't help.
robert335 said:
That was the first thing I tried. Didn't help.
Click to expand...
Click to collapse
Is your phone carrier-branded? If yes, try to flash unbranded firmware.
I managed to fix it, will update this post soon with how I did it.
robert335 said:
I managed to fix it, will update this post soon with how I did it.
Click to expand...
Click to collapse
HI, if you have a solution to this problem can you share it please? I have the same phone with the same issue .
barthab said:
HI, if you have a solution to this problem can you share it please? I have the same phone with the same issue .
Click to expand...
Click to collapse
First make sure you aren't RMM locked: https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Then get yourself TWRP: https://forum.xda-developers.com/galaxy-a6/development/recovery-twrp-3-2-2-0-galaxy-a6-t3819741
Afterwards, I installed this custom ROM which is pretty close to stock Pie: https://forum.xda-developers.com/galaxy-a6/development/rom-pa6-rom-a6-t3943573
Maybe you can try this one too, I haven't tried it: https://forum.xda-developers.com/galaxy-a6/development/phonezippy-microrom-t4083579
After installing the ROM, make sure to install "no-verity-opt-encrypt" and "RMM Bypass v3". This is VERY IMPORTANT, otherwise your device will become RMM locked and brick itself until you flash stock firmware again.
I fixed both of my phones but looks like I messed up on one and after I restarted it had RMM state Prenormal. Does anyone know how to fix this? OEM is unlocked in developer settings but flashing twrp from Odin yields "only official binaries are allowed"...
Hi there,
after flashing an ebw version (since there seems to be no androind 10 ua version) on my v405ua i get this error/warning message everytime i boot up the phone, which says "current Version is not available for user. Can't find matched carrier. Check NT-Code ....."
How do i fix this Warning ? Since basically everything seems to work as usual, my lte wifi 5 etc. all work just fine. Except for when im in the NL i cant get an internet connection through the mobile network, is says something is wrong with my apn settings.
Help is much appreciated, and thanks in advance.
Gurkenbeat said:
Hi there,
after flashing an ebw version (since there seems to be no androind 10 ua version) on my v405ua i get this error/warning message everytime i boot up the phone, which says "current Version is not available for user. Can't find matched carrier. Check NT-Code ....."
How do i fix this Warning ? Since basically everything seems to work as usual, my lte wifi 5 etc. all work just fine. Except for when im in the NL i cant get an internet connection through the mobile network, is says something is wrong with my apn settings.
Help is much appreciated, and thanks in advance.
Click to expand...
Click to collapse
The NT-Error code thing has been discussed quite a bit, as it's very common to anyone that has cross-flashed. There are various things people have done and some have worked for some, but not others.
First, it's not a problem, it's just something that shows up when u boot up, after that it's inconsequential. *But*, I found that if I did a Lgup partition DL of the rom (that I wanted to cross flash to), let it boot up, then shut it off. Then do a 'Refurbish' with the exact same rom. Then I'd no longer have the NT-Error code show up.
As far as the mobile data goes, just verify what the apn settings should be, it may be as simple as that.
cheers
Would a "reflash" to an ua version solve the problem ?
for example there seems to be a verizon version of the 405ua available, would that solve the nt warning ?
Gurkenbeat said:
Would a "reflash" to an ua version solve the problem ?
for example there seems to be a verizon version of the 405ua available, would that solve the nt warning ?
Click to expand...
Click to collapse
No
AsItLies said:
The NT-Error code thing has been discussed quite a bit, as it's very common to anyone that has cross-flashed. There are various things people have done and some have worked for some, but not others.
First, it's not a problem, it's just something that shows up when u boot up, after that it's inconsequential. *But*, I found that if I did a Lgup partition DL of the rom (that I wanted to cross flash to), let it boot up, then shut it off. Then do a 'Refurbish' with the exact same rom. Then I'd no longer have the NT-Error code show up.
As far as the mobile data goes, just verify what the apn settings should be, it may be as simple as that.
cheers
Click to expand...
Click to collapse
Unfortunatley, this didn't work for me but I'm planning on LOS where the error goes away. I just wonder if this causes my SafetyNet to fail?
FreeSoftwareServers said:
Unfortunatley, this didn't work for me but I'm planning on LOS where the error goes away. I just wonder if this causes my SafetyNet to fail?
Click to expand...
Click to collapse
No, it doesn't cause safetynet to fail, they are completely different things.
AsItLies said:
The NT-Error code thing has been discussed quite a bit, as it's very common to anyone that has cross-flashed. There are various things people have done and some have worked for some, but not others.
First, it's not a problem, it's just something that shows up when u boot up, after that it's inconsequential. *But*, I found that if I did a Lgup partition DL of the rom (that I wanted to cross flash to), let it boot up, then shut it off. Then do a 'Refurbish' with the exact same rom. Then I'd no longer have the NT-Error code show up.
As far as the mobile data goes, just verify what the apn settings should be, it may be as simple as that.
cheers
Click to expand...
Click to collapse
What partitions do I select?
blowtorchhonor said:
What partitions do I select?
Click to expand...
Click to collapse
If you're doing a part D/L select all but ftm. After it reboots, go to Lgup mode again and do a 'refurbish' with the same kdz.
Most of the time that gets rid of the nt code thing.
cheers
AsItLies said:
If you're doing a part D/L select all but ftm. After it reboots, go to Lgup mode again and do a 'refurbish' with the same kdz.
Most of the time that gets rid of the nt code thing.
cheers
Click to expand...
Click to collapse
Thank you so much for the quick reply! I flashed to the latest OPEN_EU ROM and now I can't flash back to anything else, hopefully I don't have to if the NT message can be removed.
blowtorchhonor said:
Thank you so much for the quick reply! I flashed to the latest OPEN_EU ROM and now I can't flash back to anything else, hopefully I don't have to if the NT message can be removed.
Click to expand...
Click to collapse
I was unable to do a refurbish after the DL. It said unable to cross flash V405UA to V405. Message is still present.
blowtorchhonor said:
I was unable to do a refurbish after the DL. It said unable to cross flash V405UA to V405. Message is still present.
Click to expand...
Click to collapse
When u get that crossflash issue u have to use a different version of lgup. If you look in the 'guides' forum, there will be links to (I believe it's) ver 1.16, a newer version that will work with newer versions of the roms.
cheers
AsItLies said:
When u get that crossflash issue u have to use a different version of lgup. If you look in the 'guides' forum, there will be links to (I believe it's) ver 1.16, a newer version that will work with newer versions of the roms.
cheers
Click to expand...
Click to collapse
I was using an outdated common DLL, thanks for helping me! Let's see if this works!
blowtorchhonor said:
I was using an outdated common DLL, thanks for helping me! Let's see if this works!
Click to expand...
Click to collapse
Nope
I have this message that pops up on my V450VM. I assume it was related to Navigation Gestures that I used, and loved, on my V405QA7. When activating and setting it up, my V50 downloaded Nav Gestures from backup and when the phone updated to A11 I found the app was incompatible. I deleted the app and key. Ever since, rebooting has brought up the notification and I assume something didn't delete from the app. Guess I may have been wrong. I'm living with it and it doesn't seem to cause any issues but my OCD flares everytime :/