I unbricked my 16 gm tablet using parted and ubuntu wipe. Now I can't register with B&N. I notice the serial # in the info screen is different. I believe I somehow have Adam Outlers old serial # in my machine. Is there a way to edit this in ADB ? Currently have cm7 internal with ADB working. I'd like to option of returning to stock if need be Thanks Again
sailerph said:
I unbricked my 16 gm tablet using parted and ubuntu wipe. Now I can't register with B&N. I notice the serial # in the info screen is different. I believe I somehow have Adam Outlers old serial # in my machine. Is there a way to edit this in ADB ? Currently have cm7 internal with ADB working. I'd like to option of returning to stock if need be Thanks Again
Click to expand...
Click to collapse
according to adamoutler's thread, his total wipe ubuntu flash doesn't affect the rom partition which contains your serial information. so that shouldn't be the problem...
ShinnAsuka said:
according to adamoutler's thread, his total wipe ubuntu flash doesn't affect the rom partition which contains your serial information. so that shouldn't be the problem...
Click to expand...
Click to collapse
Well, I don't know what I did, but I definitely have a wrong serial # in my device. Is it possible to edit the serial # and how Thanks
sailerph said:
Well, I don't know what I did, but I definitely have a wrong serial # in my device. Is it possible to edit the serial # and how Thanks
Click to expand...
Click to collapse
Try this link. http://forum.xda-developers.com/showthread.php?t=1610069&highlight=serial
Good Luck!
tobdaryl said:
Try this link. http://forum.xda-developers.com/showthread.php?t=1610069&highlight=serial
Good Luck!
Click to expand...
Click to collapse
Would anyone be able to simplify/expand this tutorial ? ADB is working. Confused after serial # Recovery
what do I do with Veronica's mmcblk0p5 image ? Are we copying/pulling/editing/pushing ? basically ? Thanks
Related
Hello.
I used the ubuntu restore from AdamOutler. It worked like a charm to restore my borked Nook tablet. But for what ever reason it picked up a serial number that doesnt match the one that is registered to me and my tablet. Is there a adb command or something along those lines that i can restore my serial with? I changed the serials via root explorer but it always defaults back to the wrong serial. I know it must be something I did along the line of trying to fix it but it bothers me it doesnt match to my account. It wont let me register it again. Thank you for any help...
markbird1 said:
Hello.
I used the ubuntu restore from AdamOutler. It worked like a charm to restore my borked Nook tablet. But for what ever reason it picked up a serial number that doesnt match the one that is registered to me and my tablet. Is there a adb command or something along those lines that i can restore my serial with? I changed the serials via root explorer but it always defaults back to the wrong serial. I know it must be something I did along the line of trying to fix it but it bothers me it doesnt match to my account. It wont let me register it again. Thank you for any help...
Click to expand...
Click to collapse
Since no one has answered I'll give it a try. The place I find the serial number is
/rom/devconf/SerialNumber it is 16 bytes and permissions are r--r----- or
440. Since you didn't say where you were making the change this may not help.
also for info you will find /system/xbin/setserial hope this limited info may help.
Good luck!
Forgot something. I believe you can register multiple devices with google and use the same account. Mine is registered two different ways. I am registered as
Bn Nook Tablet
and
Barnes&Noble BNTV250
both are the same unit just different builds.
I'm glad im not the only one that this happen to there nook.
i sent Adam a PM last week about it and he told me that he will be making an app for that so let's hope he didn't forget.
In the mean time any help will be greatly appreciated.
Hello again,
I found two places where the serial is stored both in the rom folder. One is the "Serialnumber" file and the other is label "deviceID". Changing both will not outlast a system reset. There must be a hidden backup file where this number is stored also.
markbird1 said:
Hello again,
I found two places where the serial is stored both in the rom folder. One is the "Serialnumber" file and the other is label "deviceID". Changing both will not outlast a system reset. There must be a hidden backup file where this number is stored also.
Click to expand...
Click to collapse
Interesting!
serial number change
The same thing happened to me. Please prod Adam to make that app or post any other solution that is found!
no news yet =/
Any solution yet ??
sailerph said:
Any solution yet ??
Click to expand...
Click to collapse
Try this link.
http://forum.xda-developers.com/showthread.php?t=1610069&highlight=serial
Good Luck!
tobdaryl said:
Try this link.
http://forum.xda-developers.com/showthread.php?t=1610069&highlight=serial
Good Luck!
Click to expand...
Click to collapse
I tried this method, but for some reason, I kept getting errors when trying to write from the unmounted SD card with DD, and, when trying with the device mounted, it would continue to write the .img file, (3-4 gig before I realized why it was taking so long.)
However, once I had the "ROM" sd card, and modified the files as necessary, I booted a CM7 SD card with my nook, installed one of the many "Root" filesystem managers, and replaced the edited DeviceID and SerialNumber files on my Nook's internal ROM.
This worked -- to an extent. B&N's default software now shows my proper Serial #, however, my B&N will still not pass registration.
I'm thinking that perhaps there's something more to the registration process, MAC address perhaps?
((UPDATE))
So, I took the plunge, cracked open the back of the nook, and found the MAC address on a sticker inside, handy that, eh?
However - This still will not pass B&N registration, so there's something that I've managed to mess up beyond that. I'm guessing this particular NT will never be able to use stock ROM's again. Oh, well, not a huge loss IMHO.
((END UPDATE))
I'm probably not going to poke at it further, as I dont acutally plan on using B&N's default software, I purchased my NT with the express intention of rooting. My only worry is warranty, however, I purchased the Best Buy "Accidental Damage" warrenty, so, if it does break. I just need to "drop" it so the screen cracks! LOL!
Nook Tablet Serial Number Restore & MAC Address restore
Thanks to all for the help with repartitioning/rebuilding Nook Tablet. Here's my input to help others on their way.
Serial Number and MAC Address restore.
You will need to install a hex editor to your laptop - one like "Free Hex Editor Neo".
We will find every instance of the serial Number and of the Mac Address in Partition 5 and change them to the correct values.
This also will automatically correct the DeviceID.
Write down your incorrect values and your correct values for Serial Number and MAC Address
Now we will modify an existing rom image for Partition 5
-if you have an existing image for Partition 5 in your laptop make a copy of it and put it in C:/download.
. -skip to step 9
-otherwise do the following:
Get the image for partition 5 from your Nook Tablet and copy it to your laptop.
1. adb shell
2. ~# mount sdcard
3. ~# dd if=/dev/block/mmcblk0p5 of=/sdcard/blk/mmcblk0p5.img
..-this copied the rom image to the sd card. It is about 48MB.
4. ~# exit
5. cd /
6. adb pull /sdcard/blk/mmcblk0p5.img /download/mmcblk0p5.img
..-this copies the image file from the SD card to your laptop. Places it in the C:/download subdirectory.
7. adb shell
8. rm /sdcard/blk/mmcblk0p5.img
..-this deletes the image file from the SD card
Edit the image file
9. Open Free Hex Editor Neo
.......-file, open file, C:\download\mmcblk0p5.img
10. Search for the old incorrect value for the serial number
11. click on the right side of the hex editor (on the ansi script)
.......-do a replace
...............-type in correct serial number
...............-replace every instance of the serial number in the file
12. Do the same operation to find/replace the MAC address
13. save the file. remove the “.img” file extension from it.
14. put it on the sd card in the root directory (either push it or place the SD card in your laptop)
15. adb shell
16. ~# mount sdcard
17. ~# dd if=/sdcard/mmcblk0p5 of=/dev/block/mmcblk0p5
18. ~# exit
19. remove sdcard, reboot internal.
Cheers.
markbird1 said:
Hello.
I used the ubuntu restore from AdamOutler. It worked like a charm to restore my borked Nook tablet. But for what ever reason it picked up a serial number that doesnt match the one that is registered to me and my tablet. Is there a adb command or something along those lines that i can restore my serial with? I changed the serials via root explorer but it always defaults back to the wrong serial. I know it must be something I did along the line of trying to fix it but it bothers me it doesnt match to my account. It wont let me register it again. Thank you for any help...
Click to expand...
Click to collapse
Do you have the serial number, and mac address that it changed yours to?
I was doing a factory reset to clean install one of the CM10.1 release candidates and I went into Mounts and Storage and I accidentally formatted ROM instead of System. Now Cyanoboot keeps going into CWM and won't boot my rom. I flashed a different rom and I also restored from backup but neither did the trick. Any tricks that can get my dear old Nook booted? Any help would be greatly appreciated. (My last resort is one of those lengthy unbrick posts if there's no way to fix it. I've done these before but if there is an easier solution I'd like to try that first.)
I am familiar with adb (and ubuntu if need be).
Do you know the serial number? Like when you use adb, and you type adb devices, it shows a serial number. Did you write it down? I have a backup of the ROM partition and it includes a few files in there containing serial and mac address, etc. The serial number is important for it to boot AFAIK, so I hope you have that somewhere.
sagirfahmid3 said:
Do you know the serial number? Like when you use adb, and you type adb devices, it shows a serial number. Did you write it down? I have a backup of the ROM partition and it includes a few files in there containing serial and mac address, etc. The serial number is important for it to boot AFAIK, so I hope you have that somewhere.
Click to expand...
Click to collapse
I have the serial number (behind the microsd card slot)..but not the mac address
Also, I only wiped the ROM and system partitions. The factory partition is still there untouched and I've read somewhere that it contains a backup of the information in the ROM partition.
adb devices shows a serial number of abcdef123456789.
Not exactly a good sign...Should I try so****e's serial number recovery thing through ubuntu?
If what you had re-formatted by mistake is /rom but your /factory is still intact then not all was lost, as /factory holds romdata.zip which is a backup archive of data files in /rom (see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more elaboration).
What you can try is to flash stock recovery (e.g., flash_stock_recovery.zip from Succulent's repo https://github.com/succulent/acclaim_recovery_sdcard), then do the "8 failed reboots" to trigger a "factory reset to stock".
Can you try to use adb from CWM? Try "adb pull /factory" and see if it copies over the factory folder to your computer.
digixmax said:
If what you had re-formatted by mistake is /rom but your /factory is still intact then not all was lost, as /factory holds romdata.zip which is a backup archive of data files in /rom (see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more elaboration).
What you can try is to flash stock recovery (e.g., flash_stock_recovery.zip from Succulent's repo https://github.com/succulent/acclaim_recovery_sdcard), then do the "8 failed reboots" to trigger a "factory reset to stock".
Click to expand...
Click to collapse
Factory is definitely in tact; only rom was formatted (I figured factory was important so I didn't want to format it.) I'll try this after and let you know. I'm going to manually flash partition 5 onto my nook through adb and see if that can get me up and running.
sagirfahmid3 said:
Can you try to use adb from CWM? Try "adb pull /factory" and see if it copies over the factory folder to your computer.
Click to expand...
Click to collapse
pull: building file list...
0 files pulled. 0 files skipped.
This was through command prompt/adb in Windows 7. Should I try Ubuntu?
topdawg7793 said:
pull: building file list...
0 files pulled. 0 files skipped.
This was through command prompt/adb in Windows 7. Should I try Ubuntu?
Click to expand...
Click to collapse
You need to mount the /factory partition before you can access it.
Why not do it the easy way: just flash stock recovery and let it restore the missing data as part of the "8 failed boots" factory reset process?
digixmax said:
You need to mount the /factory partition before you can access it.
Why not do it the easy way: just flash stock recovery and let it restore the missing data as part of the "8 failed boots" factory reset process?
Click to expand...
Click to collapse
I had no clue it fixed the missing data! Just did it and I'm back to a working nook. Appreciate the help everybody!
So what did you do to finally get it fixed? Flash stock recovery and do the 8 failed reboots method?
sagirfahmid3 said:
So what did you do to finally get it fixed? Flash stock recovery and do the 8 failed reboots method?
Click to expand...
Click to collapse
I know I'm slightly late on this, but I figure I should at least respond so any poor soul who gets into the same situation and sees this thread can have some go-to solution. I never got to do the partition thing through adb (use somebody's ROM partition and change the serial number and mac address to that of my Nook) so I booted an SDcard version of some CM10 nightly and then used the touchscreen firmware flasher to restore to the factory firmware. Then I took out the SDcard and did the 8 reboots thing and that finally fixed it.
NOTE: NEVER GO BACK TO STOCK WHILE ON THE 10-TOUCH FIRMWARE. YOUR TOUCHSCREEN WILL NOT WORK AND YOU WILL EFFECTIVELY BE STUCK UNTIL YOU BOOT OFF AN SDCARD AND RESTORE THE FACTORY TOUCHSCREEN FIRMWARE.
topdawg7793 said:
I had no clue it fixed the missing data! Just did it and I'm back to a working nook. Appreciate the help everybody!
Click to expand...
Click to collapse
lol well now i know wut to do if i accidentally format rom. cheers every1 who helped topdawg :highfive:
So I am stuck in a bootloop and no obvious way out.
US Galaxy Player 4.0
Rooted and been on custom roms for a year now. Problem started after upgraded to latest CM. Tried going back to stock but no luck in resolution. I am able to get into recovery and download mode and flash with odin. I can run adb shell. Just won't boot. The error message I get is as follows:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
In my adb shell I can see that there is no "mmcblk0..." files at all.
I have tried to go through the full stock recovery and used the PIT files and the stock rom through odin. I get the same boot loop and cant get the data to wipe due to the same error. I can flash anything through Odin easily without fail but everything is stuck in boot loop. I just don't seem to have /data to wipe.
There are some other posts around which indicate the Partition may be screwed but I am not sure what it is supposed to look like or the command line syntax to use to correct.
http://forum.xda-developers.com/showthread.php?t=1468213&highlight=wipe+data+shell
I have several nandroid backups on an external location but now I can't get the external card to recognize in CWM so haven't been able to try to revert backwards that way. I have backup of efs and all other stuff just can't seem to get to it.
Anybody with Ideas or direct help are greatly appreciated
map1122 said:
So I am stuck in a bootloop and no obvious way out.
US Galaxy Player 4.0
Rooted and been on custom roms for a year now. Problem started after upgraded to latest CM. Tried going back to stock but no luck in resolution. I am able to get into recovery and download mode and flash with odin. I can run adb shell. Just won't boot. The error message I get is as follows:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
In my adb shell I can see that there is no "mmcblk0..." files at all.
I have tried to go through the full stock recovery and used the PIT files and the stock rom through odin. I get the same boot loop and cant get the data to wipe due to the same error. I can flash anything through Odin easily without fail but everything is stuck in boot loop. I just don't seem to have /data to wipe.
There are some other posts around which indicate the Partition may be screwed but I am not sure what it is supposed to look like or the command line syntax to use to correct.
http://forum.xda-developers.com/showthread.php?t=1468213&highlight=wipe+data+shell
I have several nandroid backups on an external location but now I can't get the external card to recognize in CWM so haven't been able to try to revert backwards that way. I have backup of efs and all other stuff just can't seem to get to it.
Anybody with Ideas or direct help are greatly appreciated
Click to expand...
Click to collapse
This is how we fix that with the Player 5 : http://forum.xda-developers.com/showthread.php?t=2398120&page=4 (read the whole thread from page 4 on)
You'll need to do pretty much the same thing but you need an image from the Player 4.:good:
recrtora above
Thank you Meticulus. I see that you were involved in the thread I referenced too and this is where I figured I needed to go. However this is where I get tripped up. The main issue being that I don't have an image from a 4.0 US player. The thread I linked to had the Intl Player shown... There were even a few requests for the US version later on in the thread.
So- Anyone want to share their US player working partition table?
Is this information contained in the .PIT files somehow?
anyway to retrieve this?
map1122 said:
Thank you Meticulus. I see that you were involved in the thread I referenced too and this is where I figured I needed to go. However this is where I get tripped up. The main issue being that I don't have an image from a 4.0 US player. The thread I linked to had the Intl Player shown... There were even a few requests for the US version later on in the thread.
So- Anyone want to share their US player working partition table?
Is this information contained in the .PIT files somehow?
anyway to retrieve this?
Click to expand...
Click to collapse
As far as I know that's the only way to do it is with the picture.... Be patient, I'm sure someone will post an image...
@zaclimon ???
Needed: out put of fdisk on mmcblk0
Code:
adb root
adb shell
fdisk -l /dev/block/mmcblk0
Then post a screenshot, or just the output.:highfive:
Meticulus said:
As far as I know that's the only way to do it is with the picture.... Be patient, I'm sure someone will post an image...
@zaclimon ???
Needed: out put of fdisk on mmcblk0
Code:
adb root
adb shell
fdisk -l /dev/block/mmcblk0
Then post a screenshot, or just the output.:highfive:
Click to expand...
Click to collapse
Here it is, do note that it's a intl device though too.
zaclimon said:
Here it is, do note that it's a intl device though too.
Click to expand...
Click to collapse
That's definately not what I expected... to see from the 4.0's partition table...
Meticulus said:
That's definately not what I expected... to see from the 4.0's partition table...
Click to expand...
Click to collapse
We only have mmc blocks for the actual storage of the device. The system partition and others are pure raw nand (which is why we use mtd and yaffs2)
Envoyé depuis mon Nexus 7 avec Tapatalk 4
zaclimon said:
We only have mmc blocks for the actual storage of the device. The system partition and others are pure raw nand (which is why we use mtd and yaffs2)
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Click to expand...
Click to collapse
So then, will recreating these partitions solve the OP problem?
Meticulus said:
So then, will recreating these partitions solve the OP problem?
Click to expand...
Click to collapse
Most probably because it will only touch /data and internal storage. Actually this is the first time I see a problem like this for the 4.0.
Envoyé depuis mon Nexus 7 avec Tapatalk 4
So any confidence in the international vs the US version being the same?
Now the next thing is I used the command fdisk to start trying to recreate the partitions using the post instructions you recommended. I did not get an option for "new". I attached the output from the shell command. Tried looking up shell command references on fdisk but is not helping me here. Is it because there is not mmcblk0 at all? I don't seem to be getting into the command mode of the fdisk command.
If I use fdisk -l /dev/block/mmcblk0 I get "no such file or directory"
map1122 said:
So any confidence in the international vs the US version being the same?
Now the next thing is I used the command fdisk to start trying to recreate the partitions using the post instructions you recommended. I did not get an option for "new". I attached the output from the shell command. Tried looking up shell command references on fdisk but is not helping me here. Is it because there is not mmcblk0 at all? I don't seem to be getting into the command mode of the fdisk command.
If I use fdisk -l /dev/block/mmcblk0 I get "no such file or directory"
Click to expand...
Click to collapse
Hmm... Can post a list of /dev/block ?
Code:
adb shell
ls /dev/block
Here you go.
map1122 said:
Here you go.
Click to expand...
Click to collapse
Hmmmmm .... see if you can get here: /sys/bus/platform/devices/s3c-sdhci.0 and post the output
Like so?
map1122 said:
Like so?
Click to expand...
Click to collapse
yes.... I'm not sure what's wrong but id recommend installing a full odin flashable rom...
Not sure what that would be for the 4.0..
Here is another place you can check /sys/bus/platform/devices/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0
Here is the output of that. No further.
I am already on fresh Odin flash. Several attempts actually. I have been able to flash back to Stock (and use PIT) files, access stock recovery. I did this first to think I could restore to OEM. Then flash the Terra-Silent kernel to obtain CWM and the IcyFusion Rom (did this again this morning so I could get adb to link). These are the only Odin flashable that I am aware of for the 4.0. Obviously nothing boots because the issues discussed here.
Thank you.
what does "partition SD Card" in the Advanced and Debugging menu in CWM do?
map1122 said:
Here is the output of that. No further.
I am already on fresh Odin flash. Several attempts actually. I have been able to flash back to Stock (and use PIT) files, access stock recovery. I did this first to think I could restore to OEM. Then flash the Terra-Silent kernel to obtain CWM and the IcyFusion Rom (did this again this morning so I could get adb to link). These are the only Odin flashable that I am aware of for the 4.0. Obviously nothing boots because the issues discussed here.
Thank you.
Click to expand...
Click to collapse
I don't know if those are "full" odin flashable roms.
Try here: http://forum.xda-developers.com/showthread.php?t=1531850
Yes, that is the one I am using to revert to stock and additional PIT. I checked MD5 sums too.
Would this kind of thing be backed up in a nandroid?
map1122 said:
Yes, that is the one I am using to revert to stock and additional PIT. I checked MD5 sums too.
Would this kind of thing be backed up in a nandroid?
Click to expand...
Click to collapse
No, It wouldn't be backed up in android...
I'm betting that the U.S. Odin ROM on that page is not a "full" recovery rom either... I'm downloading right now to check. If it isn't, we need to find out how safe it is to flash an INT version first then flash a USA over it.
On the 5.0, we can do that... and everything is OK but don't know about 4.0...
EDIT: Seem like the only difference is that INT has bootloaders and USA does not. That doesn't help us...
I have an App called simple recovery switcher and currently it does not support Intel CPU's. I've never even played with a Intel android device.
Can someone check the by-name path for recovery?
it would be in /dev/block/platform/SOME FOLDER NAME HERE/by-name/recovery (or sometimes on terga devices will be SOS, not sure what they name it on Intel based devices)
What I need is the folder name after platform and then whatever the recovery name is called. Also in the build/prop can you tell me the values for ro.product.board and ro.board.platform?Thanks in advance
that?
that?
graffixnyc said:
I have an App called simple recovery switcher and currently it does not support Intel CPU's. I've never even played with a Intel android device.
Can someone check the by-name path for recovery?
it would be in /dev/block/platform/SOME FOLDER NAME HERE/by-name/recovery (or sometimes on terga devices will be SOS, not sure what they name it on Intel based devices)
What I need is the folder name after platform and then whatever the recovery name is called. Also in the build/prop can you tell me the values for ro.product.board and ro.board.platform?Thanks in advance
Click to expand...
Click to collapse
solaresmty said:
that?
Click to expand...
Click to collapse
Ok look in platform/Intel/by-label it should be in there is it called recovery? RECOVERY? Or something else?
Also what are the entries in the build.prop?
Thanks
graffixnyc said:
Ok look in platform/Intel/by-label it should be in there is it called recovery? RECOVERY? Or something else?
Also what are the entries in the build.prop?
Thanks
Click to expand...
Click to collapse
so under /dev/block/platform/intel/by-label
cache
config
data
factory
logs
panic
reserved
spare
system
there isnt a specific recovery partition
ro.product.board=clovertrail
ro.board.platform=clovertrail
A few more details:
On the Venue 8 7000, here is the output (very similar to the results you already have)
Code:
[email protected]:/dev/block/platform/intel/by-label # ls
ls
cache
config
data
factory
logs
misc
panic
reserved
system
ro.product.board=moorefield
ro.board.platform=moorefield
There is no recovery partition, or boot partition, or fastboot partition, as these are all handled in some special dumb Intel Android way.
However! Here is the Nexus Player output, which runs the same SoC, but has Android 5.0, and likely more strict input from Google on how they were allowed to arrange their boot images:
Code:
[email protected]:/dev/block/by-name # ls
ls
boot
cache
factory
fastboot
misc
panic
recovery
splashscreen
system
temp
userdata
ro.product.board=fugu
ro.board.platform=moorefield
As you can see, it has a recovery partition. Hopefully, when the Venue gets updated to Lollipop, it will have the same new set of partitions.
Hello,
Following erasure of all data in recovery mode ( wipe date / cache / system) , I finally managed to reinstall a origin ROM .
Unfortunately , I did not know I had deleted all of my data.
I managed to get the IMEI code with SN_Writer_Tool_v1.1632.00 : Working
Unfortunately data remains that I can not change .
my serial number (SN ) is: 0123456789ABCDEF . I do not know from where it comes but it has nothing to do with the original number.
Can you give me the manipulation that allows me to restore this No. ??
I also noticed that the SNID / NS were "invalid" on the phone.
NVRAM is not present ?? I do not think I have a bootloader too.
HELP !!!
thank you
jblefou62 said:
Hello,
Following erasure of all data in recovery mode ( wipe date / cache / system) , I finally managed to reinstall a origin ROM .
Unfortunately , I did not know I had deleted all of my data.
I managed to get the IMEI code with SN_Writer_Tool_v1.1632.00 : Working
Unfortunately data remains that I can not change .
my serial number (SN ) is: 0123456789ABCDEF . I do not know from where it comes but it has nothing to do with the original number.
Can you give me the manipulation that allows me to restore this No. ??
I also noticed that the SNID / NS were "invalid" on the phone.
NVRAM is not present ?? I do not think I have a bootloader too.
HELP !!!
thank you
Click to expand...
Click to collapse
Help please. I did find any answer in the forum.
what phone is that?
My mediatek soc phablet came stock with the same serial number.
It is very possible your problem with imea number is unrelated to your serial number. I suggest finding a stock complete rom and start again from fresh.
OLderDan said:
It is very possible your problem with imea number is unrelated to your serial number. I suggest finding a stock complete rom and start again from fresh.
Click to expand...
Click to collapse
Hello,
my phone is a Acer Z410.
I use a recovery rom from acer to format it.
i think the problem is link with the NVRAM because is missing too.
I try to change barecode with MAIU but i don't have file et i don't know where i car download a NVRAM datebase for it....
This works for me on Oukitel K6000 Plus:
https://stackoverflow.com/questions...o-phone-are-connected-on-a-pc-can-i-change-th
echo -n "XXXXXXXXXXXXXXXX" > /sys/class/android_usb/android0/iSerial
Untill reboot, but it's a starting point.
jblefou62 said:
Help please. I did find any answer in the forum.
Click to expand...
Click to collapse
same happen to my celpon . my unit is Blu Grand Max - G110Q
How to change serial number ?
0123456789ABCDEF looks like a emulator or AOSP serial number
Check your default.prop or build.prop serial number
Code:
adb shell getprop | grep serial
[ril.serialnumber]: [0123456789ABCDEF ]
[ro.boot.serialno]: [0123456789ABCDEF ]
[ro.serialno]: [0123456789ABCDEF ]
and change it to yours
Code:
adb shell setprop ro.serialno YOURSERIALNUMBER
Edit build.prop or default.prop for persistent
Yablio said:
0123456789ABCDEF looks like a emulator or AOSP serial number
Check your default.prop or build.prop serial number
and change it to yours
Edit build.prop or default.prop for persistent
Click to expand...
Click to collapse
I already checked it in build.prop but the serial number is not there.
France Mari said:
I already checked it in build.prop but the serial number is not there.
Click to expand...
Click to collapse
not much info about this, sadly. Got this generic serial number issue right now on a Blackview Max 1, MT6763
Yablio said:
adb shell setprop ro.serialno YOURSERIALNUMBER
Click to expand...
Click to collapse
adb shell (even under su) doesn't give permission, is there a way to get permission to write
Code:
ro.boot.serialno
ro.serialno
Global_V12.0.7.0 (redmi note 9)