Related
Does anyone have a stock Cincinnati Bell 2.2 froyo ROM for this phone, the Huawei U9000 Ideos X6?
Need to do a restore after trying a few alternate ROMs... thanks
olm3ca said:
Does anyone have a stock Cincinnati Bell 2.2 froyo ROM for this phone, the Huawei U9000 Ideos X6?
Need to do a restore after trying a few alternate ROMs... thanks
Click to expand...
Click to collapse
go to this web page http://www.huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=3781&tb=2 and click on software and its a stock upgrade that Huawei put out for our phone
cowsgo said:
go to this web page http://www.huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=3781&tb=2 and click on software and its a stock upgrade that Huawei put out for our phone
Click to expand...
Click to collapse
Thanks - will try that. I found a WellCom A99 ROM. Do you know what the difference is?
The reason I'm asking is I am trying to unlock via a code I paid for (as Cincinnati Bell refuses to give their customers the codes, bad policy) and it isn't working. I'm wondering if it is the ROM or if the code just doesn't work. I will try the Huawei ROM and see if I have a different result but I fear this code is not good.
cowsgo said:
go to this web page http://www.huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=3781&tb=2 and click on software and its a stock upgrade that Huawei put out for our phone
Click to expand...
Click to collapse
hi
will this ROM work on my Spice Mi410 just wanted to try it see if their is any improvement over the other Roms
olm3ca said:
Thanks - will try that. I found a WellCom A99 ROM. Do you know what the difference is?
The reason I'm asking is I am trying to unlock via a code I paid for (as Cincinnati Bell refuses to give their customers the codes, bad policy) and it isn't working. I'm wondering if it is the ROM or if the code just doesn't work. I will try the Huawei ROM and see if I have a different result but I fear this code is not good.
Click to expand...
Click to collapse
I assume you mean sim card unlock. Please report success or failure on this.
Sent from my CSL-MI410 using xda premium
Sergekarol said:
I assume you mean sim card unlock. Please report success or failure on this.
Sent from my CSL-MI410 using xda premium
Click to expand...
Click to collapse
I am now on the stock Huawei ROM and the phone is requesting a block unblock key. That only happens when your unlock code attempts fail too many times. Apparently, this company can get the key, and is working on that now. If / when I get the key and a correct code, that should solve it and I'm going directly to the CM7 build.
I'll post again if successful.
olm3ca said:
I am now on the stock Huawei ROM and the phone is requesting a block unblock key. That only happens when your unlock code attempts fail too many times. Apparently, this company can get the key, and is working on that now. If / when I get the key and a correct code, that should solve it and I'm going directly to the CM7 build.
I'll post again if successful.
Click to expand...
Click to collapse
Just out out of curiosity, are you trying to use a t-mobile sim?
haree said:
hi
will this ROM work on my Spice Mi410 just wanted to try it see if their is any improvement over the other Roms
Click to expand...
Click to collapse
hari,
not sure if this will work on your phone or not. I was not able to flash any wellcom or magnum roms on my phone. Create a nandroid back up and give it a try.
cowsgo said:
hari,
not sure if this will work on your phone or not. I was not able to flash any wellcom or magnum roms on my phone. Create a nandroid back up and give it a try.
Click to expand...
Click to collapse
hi
i dont think this can be flashed via CWM
and for ur info if u tried both the roms u mentioned via CWM it wont happen u have to flash it via stock recovery only or u can use Napstar new CWM which has the option to also boot via stock
u also need to rename them to firmware.nb0 put it on root of ur SD and then try flashing via Stock recovery only
Success! I am in no way promoting these guys, but unlocksolution[dot]com came through. They got me the SIM block reset key, I entered it (as it was blocked from too many failed unlocks) and the phone is now registered.
Sergekarol said:
Just out out of curiosity, are you trying to use a t-mobile sim?
Click to expand...
Click to collapse
I'm actually overseas for work, so I'm using Orange now. This is great for those of us who, contrary to Cincinnati Bell's stupid rules, want to use our phones overseas and still use CB in the states. T-mo and AT&T give out unlock codes after 90 days, I wish CB would wake up and have a decent policy.
One other thing for those talking about using different ROMs... I'm on CM7 now (the kang version, top of the list in the Dev forum for this phone) and it's working great. Not sure why anyone wants to stay with different stock ROMs, the only thing they have is a FM radio, and I can live without that.
If anyone needs help with any of this just PM me. Thanks!
olm3ca said:
Success! I am in no way promoting these guys, but unlocksolution[dot]com came through. They got me the SIM block reset key, I entered it (as it was blocked from too many failed unlocks) and the phone is now registered.
I'm actually overseas for work, so I'm using Orange now. This is great for those of us who, contrary to Cincinnati Bell's stupid rules, want to use our phones overseas and still use CB in the states. T-mo and AT&T give out unlock codes after 90 days, I wish CB would wake up and have a decent policy.
One other thing for those talking about using different ROMs... I'm on CM7 now (the kang version, top of the list in the Dev forum for this phone) and it's working great. Not sure why anyone wants to stay with different stock ROMs, the only thing they have is a FM radio, and I can live without that.
If anyone needs help with any of this just PM me. Thanks!
Click to expand...
Click to collapse
Yea my last stent with Cincinnati Bell. As soon as my contract (or they change the TOS) is up I am moving to another carrier. They really suck when it comes to user support and willingness to work with customers. Their customer support has been absolutely rude with me in certain of their stores. On top of that they used to be price competative but not anymore. they have went up on their prices to where other carriers can really be competitive (except Verizon and ATT).
olm3ca said:
Success! I am in no way promoting these guys, but unlocksolution[dot]com came through. They got me the SIM block reset key, I entered it (as it was blocked from too many failed unlocks) and the phone is now registered.
I'm actually overseas for work, so I'm using Orange now. This is great for those of us who, contrary to Cincinnati Bell's stupid rules, want to use our phones overseas and still use CB in the states. T-mo and AT&T give out unlock codes after 90 days, I wish CB would wake up and have a decent policy.
One other thing for those talking about using different ROMs... I'm on CM7 now (the kang version, top of the list in the Dev forum for this phone) and it's working great. Not sure why anyone wants to stay with different stock ROMs, the only thing they have is a FM radio, and I can live without that.
If anyone needs help with any of this just PM me. Thanks!
Click to expand...
Click to collapse
Since you have rooted to CM7, have you had the "Incoming Download Mode
polling, get oemsbl_mode =" problem where you have to take the battery out of the phone to reboot because the screen is black and that message just keeps going and going? That seems to be inherent on the Ascend X for Cincy Bell customers. I know 4 other people besides myself that have the issue consistently. Also, a lot of random reboots.
mnwilkinson said:
Since you have rooted to CM7, have you had the "Incoming Download Mode
polling, get oemsbl_mode =" problem where you have to take the battery out of the phone to reboot because the screen is black and that message just keeps going and going? That seems to be inherent on the Ascend X for Cincy Bell customers. I know 4 other people besides myself that have the issue consistently. Also, a lot of random reboots.
Click to expand...
Click to collapse
Only reason for this to happen if that somehow you are holding the vol up key when starting. If you have a case on it perhaps the case is holding the vol up button or that button is somehow stuck.
mnwilkinson said:
Since you have rooted to CM7, have you had the "Incoming Download Mode
polling, get oemsbl_mode =" problem where you have to take the battery out of the phone to reboot because the screen is black and that message just keeps going and going? That seems to be inherent on the Ascend X for Cincy Bell customers. I know 4 other people besides myself that have the issue consistently. Also, a lot of random reboots.
Click to expand...
Click to collapse
hi the thing u reported about is the download mode usually used to update software or call it firmware of the phone ....
check out this thread i updated how to use software update tool
in the middle of the video on this link i had explained how to go to download mode too ... u would easily understand it
go check Here click on this link
Hi everyone!
I bought recently a new galaxy s advanced and for some weird reason i can't make calls, can't text and can't receive anything. But i can unlock my sim without any problem and i can use mobile internet.
I had first the original gingerbread rom (i9070XXLK2), rupgraded it to 4.1.2 jelly bean(i9070XXLQE), rooted it, upgraded the kernel to this one: http://forum.xda-developers.com/showthread.php?t=2140597 and after that tried a cyanogen rom(this one => http://forum.xda-developers.com/showthread.php?t=2497660 ), went after the cyanogen back to the 4.1.2 but nothing works.
atm it is running original 4.1.2 rooted and cwm.
I also tried galaxSim but it doesn't support the galaxy s advanced, also the *#simlock# thing does not work. I am not sure there is a simlock on the phone because mobile internet works.
If you need more info just ask! Not really sure what information you need to know.
I have no idea what to do now, i hope some1 can help me.
samcool55 said:
Hi everyone!
I bought recently a new galaxy s advanced and for some weird reason i can't make calls, can't text and can't receive anything. But i can unlock my sim without any problem and i can use mobile internet.
I had first the original gingerbread rom, upgraded it to 4.1.2 jelly bean and after that tried a cyanogen rom, but none of them works.
I also rried galaxSim but it doesn't support the galaxy s advanced, also the *#simlock# thing does not work. I am not sure there is a simlock on the phone because mobile internet works.
I have no idea what to do now, i hope some1 can help me.
Click to expand...
Click to collapse
You must do Factory reset when you change ROM. Do it now.
Do you have I9070 or I9070P? On CM you do not have network unless you change tee folder if your phone is I9070P.
shut_down said:
You must do Factory reset when you change ROM. Do it now.
Do you have I9070 or I9070P? On CM you do not have network unless you change tee folder if your phone is I9070P.
Click to expand...
Click to collapse
I have factory resetted it 3 or 4 times (after every rom flash).
It's an I9070, not the P one.
If some1 tries to call me they hear an automated message tape thing that says my number is blocked and i need to call my provider.
I did call my provider and there is nothing blocking my number or the phone.
When i put my sim in another phone everything works fine so the issue must be in the phone itself.
Thanks for trying to help :highfive:
samcool55 said:
I have factory resetted it 3 or 4 times (after every rom flash).
It's an I9070, not the P one.
If some1 tries to call me they hear an automated message tape thing that says my number is blocked and i need to call my provider.
I did call my provider and there is nothing blocking my number or the phone.
When i put my sim in another phone everything works fine so the issue must be in the phone itself.
Thanks for trying to help :highfive:
Click to expand...
Click to collapse
Try to put some other SIM in phone. See what happens then. And did you wipe dalvik cache too? Try that.
Sent from my GT-I9070 using Tapatalk
shut_down said:
Try to put some other SIM in phone. See what happens then. And did you wipe dalvik cache too? Try that.
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
I tried 3 different SIM's but all from the same provider, i am going to visit a friend tomorrow to lend his SIM (he has another provider). I wiped dalvik cache every time i factory resetted it (after every rom flash)
Is it possible there is a piece of hardware in the phone blocking the calls and the messages?
Found out something new, if i do phone (the app) => call settings => additional settings, i get a message saying "network or sim card error".
I am searching for an hour now for a fix but i can't find anything. I will keep searching for another couple of hours, i really want to fix this.
samcool55 said:
I tried 3 different SIM's but all from the same provider, i am going to visit a friend tomorrow to lend his SIM (he has another provider). I wiped dalvik cache every time i factory resetted it (after every rom flash)
Is it possible there is a piece of hardware in the phone blocking the calls and the messages?
Found out something new, if i do phone (the app) => call settings => additional settings, i get a message saying "network or sim card error".
I am searching for an hour now for a fix but i can't find anything. I will keep searching for another couple of hours, i really want to fix this.
Click to expand...
Click to collapse
Are you sure it is not locked to some provider?
shut_down said:
Are you sure it is not locked to some provider?
Click to expand...
Click to collapse
I don't know, as far i can see there is no sign of a provider/region lock. During boot no logo from a provider, sim can be unlocked when it asks for my PIN.
I tried to figure out if there is a simlock with *#SIMLOCK# but the code does not work. Any idea how i can see if there is a sim-lock?
samcool55 said:
I don't know, as far i can see there is no sign of a provider/region lock. During boot no logo from a provider, sim can be unlocked when it asks for my PIN.
I tried to figure out if there is a simlock with *#SIMLOCK# but the code does not work. Any idea how i can see if there is a sim-lock?
Click to expand...
Click to collapse
I am not sure where you can look for that. And you bought from store or? You can go there and ask them maybe what is the problem. You have warranty?
shut_down said:
I am not sure where you can look for that. And you bought from store or? You can go there and ask them maybe what is the problem. You have warranty?
Click to expand...
Click to collapse
I bought it from an auction, a phone shop went bust and they sold thousands of phones. They had over 20 shops and they were not promoting a provider.
it was brand new in a sealed box and as far as i know i don't have warranty.
Is there a place to check if there is still a warranty on the phone?
EDIT: just checked and i have still warranry (produced at oktober 2012) but the problem i have now is, i flashed it a couple of times, isn't my warranty ruined now?
samcool55 said:
I bought it from an auction, a phone shop went bust and they sold thousands of phones. They had over 20 shops and they were not promoting a provider.
it was brand new in a sealed box and as far as i know i don't have warranty.
Is there a place to check if there is still a warranty on the phone?
Click to expand...
Click to collapse
I am not sure how is it in your country about that. You can go to some service center to see if the phone is locked to some carrier.
I just tried to check the binary counter, but as far as i can see it didn't move during the flashes and looks original
When i go in download mode i get this:
Odin mode
Product name: GT-I9070
Custom binary download: no
current binary: samsung official
I think this means it got still warranty?
If it is, i'm going to put back jelly bean on it and try to send it back to samsung, is there a chance they will fix it and won't find out i messed with it?
samcool55 said:
I just tried to check the binary counter, but as far as i can see it didn't move during the flashes and looks original
When i go in download mode i get this:
Odin mode
Product name: GT-I9070
Custom binary download: no
current binary: samsung official
I think this means it got still warranty?
If it is, i'm going to put back jelly bean on it and try to send it back to samsung, is there a chance they will fix it and won't find out i messed with it?
Click to expand...
Click to collapse
Yes, just go back to JB and you are good to go. And you can uninstall app that need root if you have any.
shut_down said:
Yes, just go back to JB and you are good to go. And you can uninstall app that need root if you have any.
Click to expand...
Click to collapse
Thanks for the help, just switched back to JB (stock version of course) checked the download screen again and it's still good,
No root stuff on the phone anymore, eveything looks how it's suppose to i think
requested to rma the phone and it will be sent tomorrow.
i hope they fix it! Again thanks for the help! :highfive:
Sad news, the phone is back from RMA and there is a simlock on it, but the problem is i can't find a method to remove it 4 free (don't want to pay even more for the damn thing). I am going to a shop from the original carrier over a couple of days(i know which carrier simlocked the crap out of it and they have shops not really far from here) but i am not sure they unlock it for free, and tbh the people that work there probably have no clue how to do it, so i don't have a lot of hope for that so i want to try it first myself if that's possible, but i tried already a couple of things and none of them works. Anyone an idea how i can remove it?
samcool55 said:
Sad news, the phone is back from RMA and there is a simlock on it, but the problem is i can't find a method to remove it 4 free (don't want to pay even more for the damn thing). I am going to a shop from the original carrier over a couple of days(i know which carrier simlocked the crap out of it and they have shops not really far from here) but i am not sure they unlock it for free, and tbh the people that work there probably have no clue how to do it, so i don't have a lot of hope for that so i want to try it first myself if that's possible, but i tried already a couple of things and none of them works. Anyone an idea how i can remove it?
Click to expand...
Click to collapse
I did not see anyone that unlocked sgsa here on the forum… And I did not see any guide about it for our device.
Sent from my GT-I9070 using Tapatalk
shut_down said:
I did not see anyone that unlocked sgsa here on the forum… And I did not see any guide about it for our device.
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
I was afraid of that, thanks to confirm. Went to the carrier which locked the phone and they said it is illegal to unlock it, which isn't true of course (checked it everywhere and it is legal) I will find a way to fix it with the carrier, thanks for the help.
Hi guys, I'm trying to unlock my S3 Mini and I'm having no luck so far. I've managed to root the phone using the iRoot (former Vroot) program and it worked nicely. At least it seems it did, now it does ask me to give su eprmissions to allpications and busybox is installed.
As for the unlocking itself, I tried several methods. Firstly, there was some service menu, accessible by a long string of numbers on the dialer, then going to network lock menu and setting something there, but the menu isn't there. Or better said, when I come to the Network Lock, it says only Not Active and no further options available. Then I tried the GalaxSim Unlock just to see, but as it said in the notes, this version of phone is not supported and so it didn't work. Same with another app, Galaxy S Unlock, or something like that. That one needs busybox, so I installed the 1.22 I think, but it says that there is a problem with busybox or something. It does say in the notes, that recommended is 1.17 busybox, so I keep that as a backup hope but it seems again, that the phone is not supported...
So basically, I have a rooted S3 Mini, that is still locked to T-mobile. I'm not sure, whether the country of origin matters here, but I think it was purchased in Austria (I am not the first owner) and need to unlock it for slovak O2. So far I am actually very happy with it's stock ROM, so I'm not planning to flash it completely, just sim unlock. So if anyone has any idea, what I can do to avoid going to a phone service and have it done for money, I'd appreciate it.
GT-I8910
stock Android 4.1.2
I8910XXAME1
Seriously noone has any idea how to unlock one of these machines? I've seen so many people talking about unlocking this and none of the methods mentioned worked. So please, pretty please, if you have any info on this, share it...
Lolll
fariz haikal said:
Lolll
Click to expand...
Click to collapse
Wow. Seriously? This is all you write? Why did you even bother?
Magicnet2 said:
Wow. Seriously? This is all you write? Why did you even bother?
Click to expand...
Click to collapse
Good luck dude...
need help too its currently locked to 02 UK and I want it unlocked to accept an EE sim. Cheers
Symptoms
-No IMEI and no Baseband
Both say unknown.
-No signal bars
-No sim detected (with or without sim card)
-Top right gets very hot hot at times
-Battery drains pretty fast
What I've tried
-Downgrade to 4.4
- Different play-store apps
- Different modems and radios
- IMEI writers etc
-Custom roms
-Same as above with no avail
-Stock roms
-4.4 stock
-5.0 stock
-Youtube
-All types of things in videos except octoplus or whatever its called.
Please help
You have an n900a? If yes, where did you get the 4.4 and 5.0 stock ROMs? They were never released by AT&T.
audit13 said:
You have an n900a? If yes, where did you get the 4.4 and 5.0 stock ROMs? They were never released by AT&T.
Click to expand...
Click to collapse
I used custom roms off XDA hoping it would somehow recover missing IMEI
Is the phone an n900a?
Yes SM-n900a
Made in China
If the stock roms don't restore imei and baseband, the efs folder may be damaged. A completely stock flash may be done via JTAG.
audit13 said:
If the stock roms don't restore imei and baseband, the efs folder may be damaged. A completely stock flash may be done via JTAG.
Click to expand...
Click to collapse
JTAG
Long time since I've heard that.
Wish there was something I could do on my own. I was hoping maybe just a modem flash.
I'll standby for a few more days then if nothing I'll start looking into what they could do.
Where did you get the stock 4.4 and 5.0 ROMs?
Here on XDA
audit13 said:
Where did you get the stock 4.4 and 5.0 ROMs?
Click to expand...
Click to collapse
I believe they were both from the unified threads.
you can find 4.4.2 stock on here
then 4.4.4 and 5.0 were based on official release.
Update
Still have no clue whats wrong
Either something is really wrong on the software side of the phone beyond Odin (maybe JTAG)
OR
The Sim card slot on the phone is damaged.
The phone was given to me because the old owner was never ever to get it working and gave up.
I have the IMEI on a sticker located on the back.
(Yes I know discussion about changing IMEI etc is banned that's not what I'm here for)
My main question is what can be done if I don't have an EFS back up? Is the phone just a softbrick/parts
If so plan forward is just to use as a car dock lol.
I am in the same boat man. I do not know what to do, to get my imei back and baseband. i posted a thread as well similar to yours hopefully one of us gets a success story!!!!!!
jjta said:
Still have no clue whats wrong
Either something is really wrong on the software side of the phone beyond Odin (maybe JTAG)
OR
The Sim card slot on the phone is damaged.
The phone was given to me because the old owner was never ever to get it working and gave up.
I have the IMEI on a sticker located on the back.
(Yes I know discussion about changing IMEI etc is banned that's not what I'm here for)
My main question is what can be done if I don't have an EFS back up? Is the phone just a softbrick/parts
If so plan forward is just to use as a car dock lol.
Click to expand...
Click to collapse
Willcruz82 said:
I am in the same boat man. I do not know what to do, to get my imei back and baseband. i posted a thread as well similar to yours hopefully one of us gets a success story!!!!!!
Click to expand...
Click to collapse
The first step would be to try to find the proper basebands. Dont know where any of the firms are located. Im trying to dig them all up. And reupload them but may take some days. I am hoping to temperarelly revive this device as i have gotton one myself.
Best of luck
TheMadScientist said:
The first step would be to try to find the proper basebands. Dont know where any of the firms are located. Im trying to dig them all up. And reupload them but may take some days. I am hoping to temperarelly revive this device as i have gotton one myself.
Click to expand...
Click to collapse
My goal as of now is to find a t mobile 1 with a broken screen and switch boards. Done with the boot loader being locked.
I was instructed to do 1 of 2 things... 1st like you said buy a busted up phone with a good logic board and swap. OR 2- buy that same junk Note3 and copy the efs files and install them into your phone and switch the imei to yours. etc... I gave up on trying to revive mine so I no longer can tell you if it works or not but it seems to be the best 2 options friend... good luck let me know if you get it with one of the options....
Hello all, been a little while with LG V40 as my second device, and loved it so much but tried to follow the crossflash procedures as mentioned here:
https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and I succeeded with it, only few notes wanted to share as experience/question about them:
- wifi, 3G and 4G are working as it should and no other problem found.
1. after flashing, phone booted successfully to Android 10, giving strange error message :
"WARNING!
Current version is not available for user. Can't find matched carrier. Check NT-Code: 310410310150 310170,311180,310560,310030,3 10280,310950,313100,312670: FF,FF,FF,FF,FF,FF,FF,FF,FF,FF
2. there's no SN for the phone in the settings!
- attached some screenshots for errors, looking forward to seeing some feedback or help if possible with how to fix those problems.
thanks in advance for all for such great efforts done here.
Hi, possible remove simlock after crossflash? Thanks.
P.S.
To remove message "WARNING!
Current version is not available for user. Can't find matched carrier......"
You must have root and edit file cust_path_mapping.cfg
77an said:
Hi, possible remove simlock after crossflash? Thanks.
P.S.
To remove message "WARNING!
Current version is not available for user. Can't find matched carrier......"
You must have root and edit file cust_path_mapping.cfg
Click to expand...
Click to collapse
thank you so much, i overcome it by crossflashing the latest EU Android 10.
and, about sim lock, it can't be done with cross flashing.
abokamel said:
thank you so much, i overcome it by crossflashing the latest EU Android 10.
and, about sim lock, it can't be done with cross flashing.
Click to expand...
Click to collapse
Can you share the rom that you use?
Also, were you root?
oscarillo said:
Can you share the rom that you use?
Also, were you root?
Click to expand...
Click to collapse
no, it's stock, not rooted.
the current rom i use now is here
abokamel said:
no, it's stock, not rooted.
the current rom i use now is here
Click to expand...
Click to collapse
Thanks a lot for your reply.
One more question.
Did you do a Refurbish or Upgrade option?
oscarillo said:
Thanks a lot for your reply.
One more question.
Did you do a Refurbish or Upgrade option?
Click to expand...
Click to collapse
used the command line, i think it's making refurbish
This is a bit of an older thread, but just recently did the same crossflash from pie on att device to korean open Q.
Decided on the KR instead of EBW because KR, I thought, had more of the t-mo LTE bands I needed. Unfortunately, the different sites with firmware specs aren't always accurate (which LTE bands supported). One site has EBW supporting every LTE band of every LG phone! Def inaccurate.
So I tested both EBW and KR Q versions. Use LTE Discovery (from playstore) to view LTE bands in your current location. One thing to note about that, the LTE bands it shows u are going to be the nearest towers it's using. Which means that another tower, a little farther away, won't show up.
So to verify a particular band, that you think the phone might be capable of, but you aren't sure, you have to go into the svc menu and select 'field test' and enable only that LTE band you're searching for. Then use LTE Discovery and see if it's connected with that band. If it isn't connected with it (usually it will default to a 3G band if that one u selected isn't available), that means 2 things; 1) either that band isn't used in your area 2) Your device doesn't support that band (or both 1 and 2).
But in my case, I know band 71 works in my area (from previous testing), but I have to select enable for only that band for it to show up, because other nearby towers with band 66 will 'drown it out'.
Thus, the point here, the KR firmware Band 71 **DOES WORK**. And, btw, no site indicates it included in supported bands. The following screenshot shows it connected to 71 and the KR 409 at the bottom.
Cheers
abokamel said:
Hello all, been a little while with LG V40 as my second device, and loved it so much but tried to follow the crossflash procedures as mentioned here:
https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and I succeeded with it, only few notes wanted to share as experience/question about them:
- wifi, 3G and 4G are working as it should and no other problem found.
1. after flashing, phone booted successfully to Android 10, giving strange error message :
"WARNING!
Current version is not available for user. Can't find matched carrier. Check NT-Code: 310410310150 310170,311180,310560,310030,3 10280,310950,313100,312670: FF,FF,FF,FF,FF,FF,FF,FF,FF,FF
2. there's no SN for the phone in the settings!
- attached some screenshots for errors, looking forward to seeing some feedback or help if possible with how to fix those problems.
thanks in advance for all for such great efforts done here.
Click to expand...
Click to collapse
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
You need to have root access to so you can open your /oem/OP/cust_path_mapping.cfg and a hex editor. I use HxD.
Write down the number you have in the beginning, in my case "FFFFFF,60"
Reboot into 9008, open QFil and backup your FTM by choosing "READ" option
File will be stored at C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_9
Rename file to FTM_original.bin and open in HxD
Press ctrl + G to go to offset 14000
and replace first section with number you wrote down from cust_path_mapping earlier while deleting everything after
Also, if you're missing a serial number you can add that in as well, located at offset 12000 in the FTM file
Replace the red FFFFFFFFFFFFFF with your serial #
Once done, hit "SAVE AS" so you have a backup of the original if things go wrong and rename to FTM_fixed.bin
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
advancedtekniqs said:
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
<snip brevity>
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
Click to expand...
Click to collapse
Wow thanks for that. First I've seen this idea to fix that issue. Other methods didn't work. Will try soon.
There are some other values you can change in cust.prop that can help also. Get's rid of most of the KR language in unexpected places. Will jot them down and add them here shortly.
cheers
AsItLies said:
Wow thanks for that. First I've seen this idea to fix that issue. Other methods didn't work. Will try soon.
There are some other values you can change in cust.prop that can help also. Get's rid of most of the KR language in unexpected places. Will jot them down and add them here shortly.
cheers
Click to expand...
Click to collapse
I've only been using this rom for about 6 hours. I haven't really noticed any KR except on the phone dialer. Doesn't really bother me, but if you have a way to set that to ENG, I'd like to know as well.
advancedtekniqs said:
I've only been using this rom for about 6 hours. I haven't really noticed any KR except on the phone dialer. Doesn't really bother me, but if you have a way to set that to ENG, I'd like to know as well.
Click to expand...
Click to collapse
Yes u need to change the cust.prop in OP. Change the target region country to US (from KR) and same for target country. Change language prop to en_US.
Additionally, change featureset prop to OPENUS from OPENKR.
these changes disable most KR elements in firmware, most noticeably dual clock and call recording in dialer. They **may** also enable volte if supported by carrier.
This is from nice guy Neo on tele group who's played with this much more than I have
Cheers
Oh yeah, lol, just remembered, the main reason I was asking for the info above was to get the 'field test' selection (so you can select LTE bands) in the SVC Menu from dialer. By default, it doesn't show up, but above changes fixes that also.
advancedtekniqs said:
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
You need to have root access to so you can open your /oem/OP/cust_path_mapping.cfg and a hex editor. I use HxD.
Write down the number you have in the beginning, in my case "FFFFFF,60"
Reboot into 9008, open QFil and backup your FTM by choosing "READ" option
File will be stored at C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_9
Rename file to FTM_original.bin and open in HxD
Press ctrl + G to go to offset 14000
and replace first section with number you wrote down from cust_path_mapping earlier while deleting everything after
Also, if you're missing a serial number you can add that in as well, located at offset 12000 in the FTM file
Replace the red FFFFFFFFFFFFFF with your serial #
Once done, hit "SAVE AS" so you have a backup of the original if things go wrong and rename to FTM_fixed.bin
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
Click to expand...
Click to collapse
thank you so much for sharing such detailed fix for that strange problem., as a work around, I managed to flash OPEN US kdz, then reflashed the open KR, then it's gone now, but i can't find mt phone's serial number when showing it on settings.
thanks again for such amazing tutorial. keep up
AsItLies said:
Yes u need to change the cust.prop in OP. Change the target region country to US (from KR) and same for target country. Change language prop to en_US.
Additionally, change featureset prop to OPENUS from OPENKR.
these changes disable most KR elements in firmware, most noticeably dual clock and call recording in dialer. They **may** also enable volte if supported by carrier.
This is from nice guy Neo on tele group who's played with this much more than I have
Cheers
Oh yeah, lol, just remembered, the main reason I was asking for the info above was to get the 'field test' selection (so you can select LTE bands) in the SVC Menu from dialer. By default, it doesn't show up, but above changes fixes that also.
Click to expand...
Click to collapse
that's terrific and brilliant to be honest! thank you so much for information you shared.
So, just found something additional that works on open 409N. The 'buffer fix' can be a bit of a pain. Tried a magisk module supposedly for v40 Q but that didn't work. So did what I've done before and just copy the .so fix to the appropriate directory, but that didn't work, even the oem camera stopped working after that.
So, even though this says it's for 'custom roms' tried it, and boom, works in magisk and does what's needed to fix buffer.
cheers
abokamel said:
thank you so much for sharing such detailed fix for that strange problem., as a work around, I managed to flash OPEN US kdz, then reflashed the open KR, then it's gone now, but i can't find mt phone's serial number when showing it on settings.
thanks again for such amazing tutorial. keep up
Click to expand...
Click to collapse
Try this website to find your seriel# by IMEI
So, interesting updates, for anyone using this Rom.
I went back to my AT&T rom, android 9. Then, just a few hours later... decided to go back to KR Open Don't ask, it's too confusing
But, the point, this time, when flashing the KR rom, I did part DL, and then after booting did Refurbish. Had read on tele that doing that fixes some of the issues crossflashing causes. Sure enough, my NT-code issue went away (couldn't fix that even with hexedit of ftm)!
So, that was cool. But now, my S/N disappeared! IMEI was still okay though. So tried the hexedit ftm and added S/N, boom, now it's fine also. But the funny thing was, with the refurbish and no NT-code problem, I looked at what was in the newer ftm at that address, and it had nothing, no info at that address at all.
One thing to be aware of, attesting to why this is difficult to deal with, these values (IMEI, S/N - and others) get propagated from one partition to another, I don't know the chain of events or criteria involved, but it adds to the difficulty of trying to fix issues. Which specific place it looks for something is confusing also, and if it's doing compares of 2 or more places is a mystery.
But anyway, do a Part DL to crossflash, then do a Refurb and it appears to fix some of the issues.
cheers
Awesome work, fellas!
What program and files do you all have success with during the flashing? Perhaps share a link to it?
Also, is a serial number necessary? For using the phone and having service? Seems you guys are taking the blank serial number very seriously. Thanks!
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
AsItLies said:
But anyway, do a Part DL to crossflash, then do a Refurb and it appears to fix some of the issues.
cheers
Click to expand...
Click to collapse
So for an old sprint v40 running oreo, Just crossflash to the korean Q rom via partition DL, then again, with Refurb option? Or swap between different roms? Haven't done any crossflashing yet..hoping to avoid errors. Serial number loss won't stop the phone from working, right?
fireblade20 said:
Awesome work, fellas!
What program and files do you all have success with during the flashing? Perhaps share a link to it?
Also, is a serial number necessary? For using the phone and having service? Seems you guys are taking the blank serial number very seriously. Thanks!
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
So for an old sprint v40 running oreo, Just crossflash to the korean Q rom via partition DL, then again, with Refurb option? Or swap between different roms? Haven't done any crossflashing yet..hoping to avoid errors. Serial number loss won't stop the phone from working, right?
Click to expand...
Click to collapse
Mine is an AT&T, but afaik, Sprint should be the same. Yes, do the part DL, let it reboot as normal, then shut off and do refurb. Is S/N a big deal? no, everything works, and the S/N is still in the phone, just not displaying properly. It's an individual thing how much effort you put into fixing that. Some people have lost either / or IMEI or dual IMEI (some roms have that), when cross flashing. That's a problem because they get no cell signal, but that's on a different rom.
Look in this thread for how to LGUP / crossflash.
cheers
Thanks man!