Hello guys,
I'm trying to find a way to fix the unknown serial issue, or at least see if it's gonna be fixable when Asus unlock the bootloader (which hopefully will help rooting the device with unknown serial number...).
2 things would be really great on this thing :
_ Having people with a valid serial number to help, by providing some informations on their working device.
_ Keeping the thread development oriented and clean (which means no whining about the issue, no talking about returning the device or how much Asus suck etc....).
Let's just gather all of our knowledge and work together on the issue with a technical PoV.
What I tried so far :
Device ID: It is different from the Serial Number, so nothing to do with it. Good thing is that a lot of applications and games use it for different things (as a "unique" id for push or other stuff).
build.prop and default.prop : couldn't find anything interesting. Maybe it has something to do with my TP not having a serial number, would be nice if someone could publish their files (preferably from a 3.2 prime with valid serial...)
Build.SERIAL : Main reason why I created this thread, so people with a valid serial number could try this APK and publish what the Build.SERIAL shows. On my TP, it shows unknown, so I'm guessing asus makes the same call in the system settings. Basically, if a proper TP shows up the right serial with this APK, we can probably find out where exactly the problem comes from, and hopefully fix it.
So please, if you have a Transformer Prime with a valid serial in the settings, please try this apk and report if the Serial Number that shows up in the app matches the one on the sticker
kouray said:
Hello guys,
I'm trying to find a way to fix the unknown serial issue, or at least see if it's gonna be fixable when Asus unlock the bootloader (which hopefully will help rooting the device with unknown serial number...).
2 things would be really great on this thing :
_ Having people with a valid serial number to help, by providing some informations on their working device.
_ Keeping the thread development oriented and clean (which means no whining about the issue, no talking about returning the device or how much Asus suck etc....).
Let's just gather all of our knowledge and work together on the issue with a technical PoV.
What I tried so far :
Device ID: It is different from the Serial Number, so nothing to do with it. Good thing is that a lot of applications and games use it for different things (as a "unique" id for push or other stuff).
build.prop and default.prop : couldn't find anything interesting. Maybe it has something to do with my TP not having a serial number, would be nice if someone could publish their files (preferably from a 3.2 prime with valid serial...)
Build.SERIAL : Main reason why I created this thread, so people with a valid serial number could try this APK and publish what the Build.SERIAL shows. On my TP, it shows unknown, so I'm guessing asus makes the same call in the system settings. Basically, if a proper TP shows up the right serial with this APK, we can probably find out where exactly the problem comes from, and hopefully fix it.
So please, if you have a Transformer Prime with a valid serial in the settings, please try this apk and report if the Serial Number that shows up in the app matches the one on the sticker
Click to expand...
Click to collapse
Wrong section ?
Should prove usefull though.
As per your request - yes, the provided apk does display my right serialnumber.
Thanks for getting this started!
I'm not savvy enough with Linux or android from a programming perspective to do this, but I too have the unknown serial issue. I'll help in any way I can before I have to return my prime.
Sent from my MB860 using XDA App
Danny-B- said:
Wrong section ?
Should prove usefull though.
Click to expand...
Click to collapse
I don't really know, look like development section needs work already done.
Diamondback said:
As per your request - yes, the provided apk does display my right serialnumber.
Click to expand...
Click to collapse
Thanks a lot for this information, this is very useful to know. Can you pull your build.prop too please ?
PHP:
adb pull /system/build.prop .
kouray said:
I don't really know, look like development section needs work already done.
Thanks a lot for this information, this is very useful to know. Can you pull your build.prop too please ?
PHP:
adb pull /system/build.prop .
Click to expand...
Click to collapse
Sure, just wait some minutes, doing a complete pull right now.
Here we go: build.prop of a DE ICS Prime
http://dl.dropbox.com/u/10460451/build.prop
Diamondback said:
As per your request - yes, the provided apk does display my right serialnumber.
Click to expand...
Click to collapse
That is useful because people with the Serial Number Unknown problem are showing a different serial than the one on the box of the tablet. So someone is on to something.
Great work, great work, and thanks to you all for trying to help us.
3rdamention said:
That is useful because people with the Serial Number Unknown problem are showing a different serial than the one on the box of the tablet. So someone is on to something.
Great work, great work, and thanks to you all for trying to help us.
Click to expand...
Click to collapse
How do u know we (people with unknown serials) are showing a different serial # from the one on the box?
Although if u mean "unknown" is different than an actual serial, then I agree, but kind of a weird statement to make?
Thanks a lot once again !
I'm gonna keep looking where the serial number could be saved in the system (and if it actually is requesting the system and not some hardware), it is not in the build.prop
ramtripper said:
How do u know we (people with unknown serials) are showing a different serial # from the one on the box?
Although if u mean "unknown" is different than an actual serial, then I agree, but kind of a weird statement to make?
Click to expand...
Click to collapse
Because two People alone with Unknown Serial Number ran that APK yesterday and the serial it returned was different than the one on the sticker. Here is a link to page 14 of the "Serial Number Unknown" thread. 2 people said the serial number his APK returned were different.
http://forum.xda-developers.com/showthread.php?t=1426881&highlight=apk&page=14
I wasn't making anything up. He has been working hard on this since yesterday, before this thread was created. Why would I be in here making crazy statements? I want to find a break in this bug before I take mine back, which is going back this evening.
Asus isn't helping, so it is nice to find someone, such as Kouray, that is trying to help.
3rdamention said:
Because two People alone with Unknown Serial Number ran that APK yesterday and the serial it returned was different than the one on the sticker. Here is a link to page 14 of the "Serial Number Unknown" thread. 2 people said the serial number his APK returned were different.
http://forum.xda-developers.com/showthread.php?t=1426881&highlight=apk&page=14
I wasn't making anything up. He has been working hard on this since yesterday, before this thread was created. Why would I be in here making crazy statements? I want to find a break in this bug before I take mine back, which is going back this evening.
Asus isn't helping, so it is nice to find someone, such as Kouray, that is trying to help.
Click to expand...
Click to collapse
This is a different APK than the one from yesterday, this one makes a different call to get the serial instead of the id device
Thanks for the support
kernel update?
ah sorry about that 3rdamention, i did read that actually.
well, i see on the Asus support site that you can download the Eee Pad Kernel Code for Android 3.2.1 OS (V8.8.3.23) from November 24.
It could be our kernel that's f'd up thus preventing the device from reading our serials and not allowing us to root (as a possibility to the whole problem, although 2 diff serials is a whole different problem).
If we can downgrade to this firmware version from our versions (most commonly 8.8.3.27), may this fix our kernel?
hxxp://support(dot)asus(dot)com /Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
under "Source Code (1)"
Also, has there been any known single person whos been able to update to ICS manually (by downloading the file and placing it in the correct location for the TP to recognize) whether or not they have a serial number?
On the TF101 the serial in Settings>About Tablet->Status was different, fwiw.
Sent from my Transformer Prime TF201 using Tapatalk
ramtripper said:
ah sorry about that 3rdamention, i did read that actually.
well, i see on the Asus support site that you can download the Eee Pad Kernel Code for Android 3.2.1 OS (V8.8.3.23) from November 24.
It could be our kernel that's f'd up thus preventing the device from reading our serials and not allowing us to root (as a possibility to the whole problem, although 2 diff serials is a whole different problem).
If we can downgrade to this firmware version from our versions (most commonly 8.8.3.27), may this fix our kernel?
hxxp://support(dot)asus(dot)com /Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
under "Source Code (1)"
Also, has there been any known single person whos been able to update to ICS manually (by downloading the file and placing it in the correct location for the TP to recognize) whether or not they have a serial number?
Click to expand...
Click to collapse
I would love to know as well. Or more specifically, if anyone has been able to run a manual ICS Update when they have the Serial Number Unknown and whether it fixed the lack of Serial Number.
3rdamention said:
I would love to know as well. Or more specifically, if anyone has been able to run a manual ICS Update when they have the Serial Number Unknown and whether it fixed the lack of Serial Number.
Click to expand...
Click to collapse
That especially lol. I heard some people did factory resets and the serial # came back... Don't know if it's true though and don't really wanna delete everything off my TP for a 1% chance of it working...
What do you think? Prob wont do anything right?
I was not able to get the serial number to return with factory resets, and I was unable to install the ICS update file from AndroidPolice. The system would begin, but it would eventually just reboot back into Honeycomb and give an Unknown System Error (2).
kouray said:
Thanks a lot once again !
I'm gonna keep looking where the serial number could be saved in the system (and if it actually is requesting the system and not some hardware), it is not in the build.prop
Click to expand...
Click to collapse
Looking at some source I think it might be coming from /proc/cmdline. Also, the source seems to indicate that it will only be readable by root.
If I'm correct, the cmdline contents are read and parsed with one result being a property for androidboot.serialno being set.
note: might be nice for a more knowledgeable dev to take a look at import_kernel_nv in {ANDROID_SRC}/system/core/init/init.c
KDLMaj said:
I was not able to get the serial number to return with factory resets, and I was unable to install the ICS update file from AndroidPolice. The system would begin, but it would eventually just reboot back into Honeycomb and give an Unknown System Error (2).
Click to expand...
Click to collapse
Where did you place the file for it to be read by the TP and even begin an update to ICS?
KDLMaj said:
I was not able to get the serial number to return with factory resets, and I was unable to install the ICS update file from AndroidPolice. The system would begin, but it would eventually just reboot back into Honeycomb and give an Unknown System Error (2).
Click to expand...
Click to collapse
factory reset worked for me to allow OTA updates,, got ICS OTA, installed fine but still no serial number.....
s/n is a bcokas02xxxx flavour if you gaf
screen shot for fun, also does everyone have this dev. option tool bar?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I got my TP yesterday... I charged it, played with it a bit, but want to update to ICS before spending a ton of time setting it up. When I check for an update under the system firmware update menu I get "There is no update available for your device currently" message. Does anyone know if ASUS has halted the OTA in order to get some of the ICS kinks worked out?
There is a known bug where the serial number for some of the units is listed as Unknown. If you have this problem then the automatic updates won't work. Check that your prime has its serial number in Settings > About Tablet,
aragorn182 said:
There is a known bug where the serial number for some of the units is listed as Unknown. If you have this problem then the automatic updates won't work. Check that your prime has its serial number in Settings > About Tablet,
Click to expand...
Click to collapse
Thank you, that is my problem. I had thought that the serial number issue was occurring after the update. Will do my research and try and fix problem. Again thank you.
Check out this post: http://forum.xda-developers.com/showpost.php?p=22035109&postcount=302
I used ratchet to enter a serialnr, beacause im a guy withe the serial unknown issue.
I RMA my first TFP, a new DE mainboard was in, bevor it was a WW. Since my prime is back, i had the serial issue. I tried ratchet with a DE and a WW Firmware.
This step i cant find in my settings:
" After that, you should be able to head into Settings/About Tablet/ Status and vertify your serial. Once you confirm that the serial is in correct, update away!!"
the question is: How do i confirm the serial?
The serialnr is there but no option to confirm....
I tried the rooted and the non-Rooted way....nothing
sry, my english is not the best^^
thx in advanced
If there is no way to recive OTA, my baby is going back to Asus
Ratchet's method gives you a serial number you can see but it doesn't allow OTA updates.
I read a lot of threads in diffrent forums, there are a lot of peobles they can receive
ota after using ratchet.....
I Unbricked my Nook using AdamOutlers Post and when I when't to setup menu and I entered where you Sign In to BN and when I signed in it said "Error we're having trouble seting up your nook. Please Shutdown the Device and try Again" At the bottom theres a Error number and the Number is D-AD1202 The Device is also running 1.4.0 Software. Thanks in Advance.
Try updating, you might have been on a higher firmware when you registered, and that might be the problem (I know its far fetched)
Or try setting up with a new.account.
Also check if your account is active by logging in.on a PC.
Hit Thanks if I helped you!
As I understand it this particular method wipes the serial number that is needed for registration. That's why this method should be used with extreme caution after trying "everything" else without success.
Anyway, it's done now, and if I'm right about the serial niumber there are a couple of topics about serial number retrieval as well. Try the search function and Google.
asawi said:
As I understand it this particular method wipes the serial number that is needed for registration. That's why this method should be used with extreme caution after trying "everything" else without success.
Anyway, it's done now, and if I'm right about the serial niumber there are a couple of topics about serial number retrieval as well. Try the search function and Google.
Click to expand...
Click to collapse
It Has the Serial Number but I Fixed it now.
SpeedyFeed said:
It Has the Serial Number but I Fixed it now.
Click to expand...
Click to collapse
Great news! One thing to remember with BN devices is that it has to be unregistered by a use before it can be registered to someone else. A completey wipe/reste doesn't deregister it from BN database.
hi Team.
My phone is Not Showing Update Notification After I copied Update File in root Folder.
I Tried Too Many Files bus Still There is No Notification.
I need A Frimware File Of Android 12 To install it from PC.Can u do that?
To update you need to be on WW-18.0410.2203.201
Then download A12 firmware from asus website
Shreyash_drogon said:
To update you need to be on WW-18.0410.2203.201
Then download A12 firmware from asus website
Click to expand...
Click to collapse
I'm Already on it..but There is No Update Notification For Android 12
lvl0rde said:
I'm Already on it..but There is No Update Notification For Android 12
Click to expand...
Click to collapse
Then, you just have to download and install the last rog phone 3 firmware from asus website!
ROG Phone 3 | ROG Phone 3 | Gaming Phones｜ROG - Republic of Gamers｜ROG Global
ROG Phone 3 sets the new standard for mobile gaming! Absolute Power. Absolute Visuals. Absolute Control.
rog.asus.com
You download it, put it in the root folder of your internal storage space, reboot your phone and process to an update search, you'll get a notification to install it!
I did it this way yesterday, working like a charm!
You have the Asus flag off. There will be no automatic updates anymore. Only manual programming remains.
Once you copy the latest update from the Asus website to the root directory, this should work.
If it doesn't work, your phone doesn't have a serial number or an IMEI. Or the serial number of the phone does not match the assigned IMEI number. Or vice versa. This is an old number of fake sellers.
Either way you have a problem.
IrCio36 said:
You have the Asus flag off. There will be no automatic updates anymore. Only manual programming remains.
Once you copy the latest update from the Asus website to the root directory, this should work.
If it doesn't work, your phone doesn't have a serial number or an IMEI. Or the serial number of the phone does not match the assigned IMEI number. Or vice versa. This is an old number of fake sellers.
Either way you have a problem.
Click to expand...
Click to collapse
It could also mean the option to detect software update after restart from developer options is turned off (ensure you are a developer)