[Q] USSD Code for AP/CSC not working? - Galaxy Note 3 Q&A, Help & Troubleshooting

Hi all, I'm attempting to root my note 3 with the new root de la vega method. Unfortunately it asks you to input a USSD code of #1234# (*#1234#) on the phone to identify the correct AP and CSC files to download. When I input this code my phone prompts me with this error: Unable to Process Request. I'm a bit frustrated, is there a workaround or another way to find out this information reliably? Would greatly be appreciated! Thanks!

MidniteKitten said:
Hi all, I'm attempting to root my note 3 with the new root de la vega method. Unfortunately it asks you to input a USSD code of #1234# (*#1234#) on the phone to identify the correct AP and CSC files to download. When I input this code my phone prompts me with this error: Unable to Process Request. I'm a bit frustrated, is there a workaround or another way to find out this information reliably? Would greatly be appreciated! Thanks!
Click to expand...
Click to collapse
bump. i'm having the same issue on tmobile version note 3.

teknowiz23 said:
bump. i'm having the same issue on tmobile version note 3.
Click to expand...
Click to collapse
This thread had been temporarily deleted, it is now active again? Either way, my question was solved at the thread below:
http://forum.xda-developers.com/showthread.php?t=2493514
The codes ended up being AP - N900TUVUBM17 & CSC - M17

Related

[Q] Whats the CSC access code now? (ICS)

Hi Guys!
Anyone got any idea what the new dialler codes are for this baby? Old CSC access code doesn't work...
try the anycut app in play store, choose all activites-->custom activity, there should be a long list, find service mode, or personilization(to change CSC).
or are you referring to *#1234# ? that info should be accessible as well from service mode.
Also BE CAREFUL in there, try not to press anything you are not sure of.
Hmm. Nope. neither method works...
The *#1234# does not work
Sent from my GT-P6800 using xda premium
have a look at this post.. http://forum.xda-developers.com/showpost.php?p=27179257&postcount=12
enter *#*# (code) #*#* into dialer.
for example.. *#*#197328640#*#*, should enter service mode.
remember be careful.
Still no joy guys!
Tried everything you have said, but nada. Nothings happening... anyone figure out the new codes yet?
Thanks for the help people!
if your handy with adb commands you can run the command from that post should list something. I know where to find them in .smali code.
perhaps they did change things.
does the standard mmi codes work? *#06#?

Discover SPC/MLS for Defy XT on Republic Wireless

Hey Folks,
So over in the republic, we are working to root our phone so that we can enjoy the life of a rooted user, but unfortunately RW has not provided us with the SPC and sadly it is not 000000. We have tried many methods of recovering the SPC, like parsing logcat logs while accessing ##DATA# ##SVN#, etc. We have tried getprop with zero luck also.
I wanted to know, if there is a way to validate the SPC via adb cli. For instance, I was thinking of attempting to change a setting on the phone by passing through an SPC code and either getting a success or error. This way I could create a script to attempt all possible SPC codes until it hits success.
Any advice or insight would be much appreciated.
Want to be on this thread.
Also looking for any suggestions about how to get the Defy XT 557 into DIAG mode so COM port can be opened for connection to QPST, QXDM, RadioComm, CDMA workshop, etc.
Thanks in advance.
Diagnostic COM port (COM13) opens on Defy XT557 (Republic Wireless) using SUT LR 1.82, but without the MSL/SPC, not able to finish the process to obtain root.
cmm324 said:
Hey Folks,
So over in the republic, we are working to root our phone so that we can enjoy the life of a rooted user, but unfortunately RW has not provided us with the SPC and sadly it is not 000000. We have tried many methods of recovering the SPC, like parsing logcat logs while accessing ##DATA# ##SVN#, etc. We have tried getprop with zero luck also.
I wanted to know, if there is a way to validate the SPC via adb cli. For instance, I was thinking of attempting to change a setting on the phone by passing through an SPC code and either getting a success or error. This way I could create a script to attempt all possible SPC codes until it hits success.
Any advice or insight would be much appreciated.
Click to expand...
Click to collapse
Bump, still need help with this issue.
cmm324 said:
Bump, still need help with this issue.
Click to expand...
Click to collapse
+1
Sent from my XT557 using xda premium
Moved to Q&A. Please ask all questions there, thanks.

E footer is wrong, e signature verification failed when installing OTA update?

Hi folks!
Just bought myself an S5, have successfully rooted the phone, and decide to install the Alliance Rom with no issues.
I then downloaded the Black Glass OTA Theme, went into recovery mode and tried to unzip the file (Using Philz touch) - I received the following two error messages: "e footer is wrong, e signature verification failed"
I'm on android v4.4.2 - I backed up prior to this so I've just restored back to factory settings for the meantime, but I'd like to know why I'm getting those two errors if possible?
Many thanks!
ggiiaann91 said:
decide to install the Alliance Rom with no issues.
I then downloaded the Black Glass OTA Theme, went into recovery mode and tried to unzip the file (Using Philz touch) - I received the following two error messages: "e footer is wrong, e signature verification failed"
Click to expand...
Click to collapse
Could be many reasons, you don't have enough information yet to know. Crucially, you failed to paste the verbatim error and the context surrounding it here. Or even link to the theme you refer to. So we don't have much to go on.
As it is labeled as an OTA theme, it will be specifically formatted for that custom ROM. So wouldn't it make more sense to seek help in the custom ROM support thread?
The actual error could be anything from a corrupt download (did you verify the md5 checksum or try downloading the theme again?) to a marginal USB cable (did you try a different USB cable and port?). Or many other things. Did you search the support thread to see if anyone else was troubleshooting similar issues?
.
Sorry, I'm completely new to the forum so don't know my way about.
How would I go about obtaining/providing the verbatim error?
ggiiaann91 said:
How would I go about obtaining/providing the verbatim error?
Click to expand...
Click to collapse
You can copy and what you see on screen from the log that Odin or Kies makes. Or alternately make a screenshot.
Most questions could be expediently answered by a search of the forum too. But for some reason, most people don't try that.
.
fffft said:
You can copy and what you see on screen from the log that Odin or Kies makes. Or alternately make a screenshot.
Most questions could be expediently answered by a search of the forum too. But for some reason, most people don't try that.
.
Click to expand...
Click to collapse
I appreciate that, I did try looking via the forum before asking but didn't find any mention of 'verbatim'...
I also searched for the errors I am experiencing and whilst I found several other threads, none are a similar scenario to mine.
I am not using Odin or Kies, I was able to root my phone successfully, and installed the Alliance Rom with no issues.
My issue occurs after downloading an the OTA update/theme and then going into recovery mode > Install Zip > Choose zip from /sdcard > OtaDownloads/ > Install Black_Glass_S5
I ticked to check the MD5 sum, it came back with with 'MD5 check: error'
Signature verification causes the 'E: footer is wrong and E: signature verification failed' errors.
ggiiaann91 said:
I did try looking via the forum before asking but didn't find any mention of 'verbatim'...
Click to expand...
Click to collapse
Your search technique needs polishing. If some particular keyword doesn't work in a search, then use a synonym or reword your search query.
ggiiaann91 said:
I ticked to check the MD5 sum, it came back with with 'MD5 check: error'
Signature verification causes the 'E: footer is wrong and E: signature verification failed' errors.
Click to expand...
Click to collapse
And there is crucial information that you didn't provide earlier. The very reason why I wanted the verbatim context. We are't psychic and can't help you effectively if you don't provide a detailed account.
Adding those details is a huge improvement. You selected a feature (check md5) without understanding how it worked. That caused an error. You then asked us what the error meant without telling us that you had done that and not providing any context or details for us to work with.
The error message, in context, tells us that you either tried to check md5 on a file that doesn't have a md5 - therefore a spurious error. Or the file was profoundly corrupt.
.
It's not my intention to be vague, I simply do not know what information is relevant/beneficial to you.
I deleted the file and then re-downloaded a new copy but it still won't unzip the file, the issue also occurs for another OTA file.
If there's specific info I can provide then by all means let me know and I'll provide it.
Appreciate the help and patience - evidently I'm still a noob when it comes to all the features/tools.
ggiiaann91 said:
If there's specific info I can provide then by all means let me know and I'll provide it.
Click to expand...
Click to collapse
If you were already an expert, you could pare down the details in your post to the minimum amount needed. But when seeking help in an area that is new to you, you should provide the maximum amount of information. If in doubt post more, rather than exclude something when troubleshooting.
Nothing impairs someone from providing effective help as much as missing crucial details. The only things you should withhold are personally identifying info e.g. serial numbers.
Someone knowledgeable trying to help you can easily sift through too much info. Not the reverse.
.
fffft said:
If you were already an expert, you could pare down the details in your post to the minimum amount needed. But when seeking help in an area that is new to you, you should provide the maximum amount of information. If in doubt post more, rather than exclude something when troubleshooting.
Nothing impairs someone from providing effective help as much as missing crucial details. The only things you should withhold are personally identifying info e.g. serial numbers.
Someone knowledgeable trying to help you can easily sift through too much info. Not the reverse.
.
Click to expand...
Click to collapse
I wasn't disagreeing - I've not got any other information to provide currently.
Will try searching the forum more to see if I can find anything else in the meantime.
g935f stuck on logo
hi i tried to remove pattern lock of my s7 edge with z3x but phone just stuck on logo now im trying to take it to download mode but can not boot , just i can go to recovery mode , can anyone help me , is this possible i can flash by sd card.
fffft said:
Your search technique needs polishing. If some particular keyword doesn't work in a search, then use a synonym or reword your search query.
And there is crucial information that you didn't provide earlier. The very reason why I wanted the verbatim context. We are't psychic and can't help you effectively if you don't provide a detailed account.
Adding those details is a huge improvement. You selected a feature (check md5) without understanding how it worked. That caused an error. You then asked us what the error meant without telling us that you had done that and not providing any context or details for us to work with.
The error message, in context, tells us that you either tried to check md5 on a file that doesn't have a md5 - therefore a spurious error. Or the file was profoundly corrupt.
.
Click to expand...
Click to collapse
You should be nicer. That was just plain rude.
guau pues buscais el update.img lo meteis y listo
"read only"?
ggiiaann91 said:
Hi folks!
Just bought myself an S5, have successfully rooted the phone, and decide to install the Alliance Rom with no issues.
I then downloaded the Black Glass OTA Theme, went into recovery mode and tried to unzip the file (Using Philz touch) - I received the following two error messages: "e footer is wrong, e signature verification failed"
I'm on android v4.4.2 - I backed up prior to this so I've just restored back to factory settings for the meantime, but I'd like to know why I'm getting those two errors if possible?
Many thanks!
Click to expand...
Click to collapse
Do you mount your SD card into a USB card reader and then use in a USB port on your desktop or laptop?
because if you accidentally made the "E" port into "read only" on one file, or anything on the drive it could have locked the entire drive down, which to me is exactly
what it sounds like,
put the card back into your desktop, right click as if you were ejecting drive. select properties> preferences> share file settings and set to "Everyone"
yes i know its old, but its not a bad thing to bring up to answer for other newbies right on front page.
thanks this helped me a lot
Greggofaster said:
Do you mount your SD card into a USB card reader and then use in a USB port on your desktop or laptop?
because if you accidentally made the "E" port into "read only" on one file, or anything on the drive it could have locked the entire drive down, which to me is exactly
what it sounds like,
put the card back into your desktop, right click as if you were ejecting drive. select properties> preferences> share file settings and set to "Everyone"
yes i know its old, but its not a bad thing to bring up to answer for other newbies right on front page.
Click to expand...
Click to collapse
I realised I couldn't boot from sd card because I was creating the boot card through a card reader from this post so that really helped me thanks
"Hey i'd rather you do the work for me" kinda thang is a bit annoying. People are so silly sometimes.

[Q] nvram/imei ?

So my nexus 4 /data/nvram/blahblahblah is gone which means that in turn my imei is also gone. I used this as a reference guide:
- http://hackershandbook.org/forum/hacking-discussion/nexus-5-imei-change
I successfully extracted my friends nvram using QPST. However I cant seem to push the nvram (qcn file) to my phone, every time I try to do so I get this error message:
Exception Thrown!!
NvManager::writeToPhone( const string comPort) - QpstServer::sendSynclmpl - Bad response from phone (DM packet commands 19-24)
Im kind of stuck at this point I also get the error message from nv items reader/writer (after I generate the IMEI file for my phone using nv_gen.exe):
'$-9' is not a valid integer value
So im stuck at this point and phone less. Anyone got anything for me? Thanks in advance!
Note:
- I'm on Cyanogenmod 4.2.2 (4.2.2 only firmware that boots without imei)
- Friend was on stock 4.4.4 when I extracted nvram from their phone
- Any other methods that you guys have that may work for my imei please share, im all ears.
The reason it failed in the first place could be a hardware fault, which means this wouldn't fix it. But the guide you are following is for a samsung s3, I think you might need a box to do the n4.

Zenfone AR (Verizon) WiFi not working: INVALID_COUNTRY_CODE_DISABLE_WIFI

I purchased an Asus Zenfone AR from Verizon a month ago on New York. I used the phone as my main phone for a couple of weeks there and it worked perfectly (both cellular network and wifi worked just fine). Then a went to Latin America and the wifi stopped working. What this means is: I cannot turn the wifi ON, when I try to turn it ON, there is a toast saying "Error" and it shows back OFF.
I've went back to the States a week ago and I took the phone with me. On California the wifi started working (being able to turn it ON) again, so when I asked for help on a Verizon shop, the people there told me there was nothing they could do because the phone was working just fine.
Now I'm on Latin America again and the wifi does not turn on, I debugged the phone with Android Studio and I get this error on the console:
Code:
10-07 01:02:18.998 1201-2738/? E/ActivityManager: Sending non-protected broadcast android.net.wifi.INVALID_COUNTRY_CODE_DISABLE_WIFI from system 1201:system/1000 pkg android
java.lang.Throwable
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:20117)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:20687)
at android.app.ContextImpl.sendStickyBroadcastAsUser(ContextImpl.java:1239)
at com.android.server.wifi.WifiServiceImpl.notifyInvalidCountryDisableWifi(WifiServiceImpl.java:1556)
at com.android.server.wifi.WifiServiceImpl.setWifiEnabled(WifiServiceImpl.java:960)
at android.net.wifi.IWifiManager$Stub.onTransact(IWifiManager.java:317)
at android.os.Binder.execTransact(Binder.java:565)
A quick google search did not show any results on this error code.
I did a factory reset a couple times and tried it with and without the Verizon SIM card.
Does anyone know what this error means exaclty?
I'll keep debugging it and updating the post with my results.
Update 1:
Looks like the Country I'm in (Argentina) does not have a valid country code... which does not make any sense, but here is the error:
Code:
10-07 01:33:02.691 1201-1930/? D/WifiService: setWifiEnabled: true pid=8209, uid=10124
10-07 01:33:02.693 1201-1930/? D/WifiService: checkCountryCode: 'AR' is invalid
10-07 01:33:02.694 1201-1930/? D/WifiService: notifyInvalidCountryDisableWifi
Update 2:
I'm able to get an internet connection using Bluetooth tethering.
Update 3:
Looks like something like this would help, but would require a rooted device:
https://forum.xda-developers.com/pixel/themes/mod-wifi-country-code-fix-root-required-t3558044
Update 4:
Ok, so, from what I understand now, the local SIM I used changed the country code to AR. But I still don't see why that would disallow me to turn wifi ON. I do know that this could hide some networks from me due to the country code, but I should be able to turn it ON anyway.
A simple
Code:
adb shell setprop gsm.operator.iso-country us
should fix this issue, but root would still be needed.
logain42 said:
Ok, so, from what I understand now, the local SIM I used changed the country code to AR. But I still don't see why that would disallow me to turn wifi ON. I do know that this could hide some networks from me due to the country code, but I should be able to turn it ON anyway.
A simple
Code:
adb shell setprop gsm.operator.iso-country us
should fix this issue, but root would still be needed.
Click to expand...
Click to collapse
Hi.
Did you solved?
Have same problem?
But I have wrong MAC address of wifi adapter... Is it hardware problem or ?
Similar issue here...
Bought a Samsung A5 2017 in US, everything was working fine until I updated via OTA to Nougat and started using an Argentinian simcard.
Country code changed and wifi does not turn on at all. I tried everything but rooting and using the method you mentioned... I'll try it as soon as i get the time to do it and post here the result.
As far as I got investigating the issue, the problem seems to be caused by the wifi driver not loading properly because of "incorrect" country code.
I get the message "Wifi driver unloaded" in logcat
I had the silly idea of doing factory reset once more (I wasn't thinking properly), and now I'm not even able to use the device, because I need internet connection in order to log-in with a google account, and the bluetooth trick does not work on this step.
I'm basically bricked until I get back to the States.
anybody tried to install bootloader unlock app from ASUS site?
I did, but can not install, it says: "app not installed the package conflicts with an existing package by the same name"
same exactly problem, any solve this?
Hi.
Is there a solution to the problem with Wi-Fi idle from ASUS ZenFone AR V570KL (A002A) (Verizon)?
nick_fc said:
anybody tried to install bootloader unlock app from ASUS site?
I did, but can not install, it says: "app not installed the package conflicts with an existing package by the same name"
Click to expand...
Click to collapse
I wasn't able to make it work either.
Funny thing is, I bought this phone because I wanted to develop stuff for Google Tango, but now that google killed that project, I don't have any other reason for using it any more.
Unless someone comes out with a fix or some way of rooting it, I'll sell it as a used phone on the States and at least get part of my money back.
logain42 said:
I purchased an Asus Zenfone AR from Verizon a month ago on New York. I used the phone as my main phone for a couple of weeks there and it worked perfectly (both cellular network and wifi worked just fine). Then a went to Latin America and the wifi stopped working. What this means is: I cannot turn the wifi ON, when I try to turn it ON, there is a toast saying "Error" and it shows back OFF.
I've went back to the States a week ago and I took the phone with me. On California the wifi started working (being able to turn it ON) again, so when I asked for help on a Verizon shop, the people there told me there was nothing they could do because the phone was working just fine.
Now I'm on Latin America again and the wifi does not turn on, I debugged the phone with Android Studio and I get this error on the console:
Code:
10-07 01:02:18.998 1201-2738/? E/ActivityManager: Sending non-protected broadcast android.net.wifi.INVALID_COUNTRY_CODE_DISABLE_WIFI from system 1201:system/1000 pkg android
java.lang.Throwable
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:20117)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:20687)
at android.app.ContextImpl.sendStickyBroadcastAsUser(ContextImpl.java:1239)
at com.android.server.wifi.WifiServiceImpl.notifyInvalidCountryDisableWifi(WifiServiceImpl.java:1556)
at com.android.server.wifi.WifiServiceImpl.setWifiEnabled(WifiServiceImpl.java:960)
at android.net.wifi.IWifiManager$Stub.onTransact(IWifiManager.java:317)
at android.os.Binder.execTransact(Binder.java:565)
A quick google search did not show any results on this error code.
I did a factory reset a couple times and tried it with and without the Verizon SIM card.
Does anyone know what this error means exaclty?
I'll keep debugging it and updating the post with my results.
Update 1:
Looks like the Country I'm in (Argentina) does not have a valid country code... which does not make any sense, but here is the error:
Code:
10-07 01:33:02.691 1201-1930/? D/WifiService: setWifiEnabled: true pid=8209, uid=10124
10-07 01:33:02.693 1201-1930/? D/WifiService: checkCountryCode: 'AR' is invalid
10-07 01:33:02.694 1201-1930/? D/WifiService: notifyInvalidCountryDisableWifi
Update 2:
I'm able to get an internet connection using Bluetooth tethering.
Update 3:
Looks like something like this would help, but would require a rooted device:
https://forum.xda-developers.com/pixel/themes/mod-wifi-country-code-fix-root-required-t3558044
Update 4:
Ok, so, from what I understand now, the local SIM I used changed the country code to AR. But I still don't see why that would disallow me to turn wifi ON. I do know that this could hide some networks from me due to the country code, but I should be able to turn it ON anyway.
A simple
Code:
adb shell setprop gsm.operator.iso-country us
should fix this issue, but root would still be needed.
Click to expand...
Click to collapse
I have the same problem and have solved it by downloading CSC_V520KL_T3.3.15_all_eng.zip rom
But the rom is very primitive and impractical and there is no package Asus and google in it
What is important is that it can be used Wi-Fi files from it to Verizon rom
just we need root to fix it
Please, share flasher and software
If you have.ô
ArtSima said:
Please, share flasher and software
If you have.ô
Click to expand...
Click to collapse
Asus Zenfone V (V520KL)
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
i can't post link sorry
give ur mail
qaqen said:
Asus Zenfone V (V520KL)
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
i can't post link sorry
give ur mail
Click to expand...
Click to collapse
[email protected] and thank you
qaqen said:
Asus Zenfone V (V520KL)
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
i can't post link sorry
give ur mail
Click to expand...
Click to collapse
can you send me flash tool too with some info? thanks
[email protected]
I just had the same thing while traveling to Europe. In both Scotland and Iceland, I was not able to use wi-fi but once we got back to USA, all is good. Very annoying. I'd like to be able to find an official fix.
some solution to activate WiFi for Asus_A002A
Having exactly the same problem - can you share the link with me too please?
qaqen said:
Asus Zenfone V (V520KL)
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
i can't post link sorry
give ur mail
Click to expand...
Click to collapse
can you help me with the files please
I give you my e-mail address [email protected]
tomelich said:
can you help me with the files please
I give you my e-mail address [email protected]
Click to expand...
Click to collapse
just google it
"Asus CSC Image Collection"
you will find new links
:good:
qaqen said:
just google it
"Asus CSC Image Collection"
you will find new links
:good:
Click to expand...
Click to collapse
only flashing "Asus CSC Imag" = WW_V570KL_T3.0.6_all_eng
With that, WiFi will work and my software will work normally?
could you say the right steps please
I flashed by Software Upgrade Assistant (ASUS) from verizon wireless
When you connect your phone to the USB cable with pc and choose the repair option from the phone, the program will automatically run in Windows
When you make a repair option from pc , the program will download the latest version of the ROM into a new folder at drive D & compressed file. The program will automatically unzip and install. the zip rom in your phone
I flash CSC rom by
replacing CSC rom with original rom file. at D drive and change its name with the same name as the "xxxxxxx.raw" , do not delete or change name of the original compressed file . Only change the raw file and change name as the original name rom. after make repair option from pc again you will flash CSC rom
In any case you need the fownload original ROM if you want to return to original
If you change the size or the name of the compressed file in the folder created by the program, it will delete everything and download the ROM again,so copy zip rom before the change it
sorry for my language

Categories

Resources