http://androidroot.mobi/2012/01/31/introducing-ratchet-the-unknown-serial-fix/
If your device is not rooted beforehand.
* Unzip the archive.
* Make sure the USB drivers for the Transformer Prime are installed, as well as ADB (Android SDK).
* adb push mempodroid /data/local/
* adb push ratchet /data/local/
* adb shell (You’ll now see a [email protected]:/ $ prompt)
* chmod 755 /data/local/mempodroid /data/local/ratchet
* /data/local/mempodroid 0xd9ec 0xaf47 /data/local/ratchet
This is where the magic happens. Make sure you enter your serial number correctly, all in caps!
* Reboot your device.
* Done!
If your device is already rooted (su/Superuser installed).
* Unzip the archive.
* Make sure the USB drivers for the Transformer Prime are installed, as well as ADB (Android SDK).
* adb push ratchet /data/local/
* adb shell (You’ll now see a [email protected]:/ $ prompt)
* su (You should now see a [email protected]:/ # prompt)
* chmod 755 /data/local/ratchet
* /data/local/ratchet
This is where the magic happens. Make sure you enter your serial number correctly, all in caps!
* Reboot your device.
* Done!
Afterwards, verify if ‘About tablet’ in Settings shows your Serial Number.
You can, alternatively, check by ‘getprop ro.serialno’ in an adb shell.
https://github.com/downloads/AndroidRoot/Ratchet/ratchet.zip
Post all of this in Gary's sticky thread up top also. For unknown serial numbers. Good looking out as this should help out alot of folks.
will asus want this information in an "official" thread since it has info for rooting the device?
I'm not being a traffic cop, just asking a question
Sent from my MB855 using Tapatalk
I'd say go for it. Plus its already posted in there. Asus doesn't have a better solution so mad props to Apache aka BumbleBee and the Androidmobi team. I hope he can come out with someone fixes and upgrades for the prime. Glad to know he owns a prime also n looked out for owners of prime.
As I predicted several weeks ago, the Development Community would find a fix before Asus would.
Good job to the Devs. Heck, it took Asus 18 Days just to tell me how to update my Prime OTA, even though I told them the Serial Number Unknown wouldnt allow me (yes, they simply ignored my Tech Inquiry, and gave me a copy and paste answer that didn't even answer my questions/issues).
I wonder how long Asus is going to be with their Fix? Supposedly, by Gary Key's Accounts, it is in testing right now.
Good find. Also Asus is trying to find a fix that doesn't require a rooted device.
Can you undo the fix
So... how does one undo this process?
In case you want to RMA the unit and have it display the dreaded "Unknown" in the Serial number field.
Should one just re-do the process and type "Unknown" instead of the actual serial number?
thanks.
Can i hear from people who actually done that fix? Just want to understand if their OTA updates work after that fix...
predo said:
Can i hear from people who actually done that fix? Just want to understand if their OTA updates work after that fix...
Click to expand...
Click to collapse
I did it myself and made no difference for the OTA, was still unable to get them automatically.
After I applied the "fix" I had the s/n populated in the about/tablet menu, that is all.
I got sick of that and sent it to the local service support.
Hopefully my attempt to fix it via this fix won't cause an issue with the warranty ...
Will post again once I get it back (it's been 2 weeks).
julien.me said:
I did it myself and made no difference for the OTA, was still unable to get them automatically.
After I applied the "fix" I had the s/n populated in the about/tablet menu, that is all.
I got sick of that and sent it to the local service support.
Hopefully my attempt to fix it via this fix won't cause an issue with the warranty ...
Will post again once I get it back (it's been 2 weeks).
Click to expand...
Click to collapse
Right, me too. I want to RMA mine and want to revert what the tool patched before sending it back.
and "predo"... NO... OTA doesn't work after applying this fix.
shame so it really isn't a fix, just change in how ATP displays serial but this doesn't fix reason why it is displayed as unknown in the first place....
I guess I'll just hang on to mine until there's more stock to replace it/fix is available.
julien.me said:
I did it myself and made no difference for the OTA, was still unable to get them automatically.
After I applied the "fix" I had the s/n populated in the about/tablet menu, that is all.
I got sick of that and sent it to the local service support.
Hopefully my attempt to fix it via this fix won't cause an issue with the warranty ...
Will post again once I get it back (it's been 2 weeks).
Click to expand...
Click to collapse
predo said:
shame so it really isn't a fix, just change in how ATP displays serial but this doesn't fix reason why it is displayed as unknown in the first place....
I guess I'll just hang on to mine until there's more stock to replace it/fix is available.
Click to expand...
Click to collapse
Well... in a way the tool is a fix to help you ROOT your prime
I got my tablet back from RMA and they "fixed" the s/n apparently, the s/n shows correctly now, will see next time there is an update
They have change the main board and the only thing I can see that has changed is the MAC address of the wireless interface which mean they will have change the motherboard ...
Related
Has anyone found a method for restoring Serial Number and DeviceID after recovering a bricked NT? I've recovered, but I can't re-register with B&N due to missing SN/ID? Not really finding any answers in the forums so far. If you have some info or can point me in the right direction, I'd be greatful. (yes I have been trying to look through the forums, just not seeing an answer, though it seems many have asked).
shawnshine2 said:
Has anyone found a method for restoring Serial Number and DeviceID after recovering a bricked NT? I've recovered, but I can't re-register with B&N due to missing SN/ID? Not really finding any answers in the forums so far. If you have some info or can point me in the right direction, I'd be greatful. (yes I have been trying to look through the forums, just not seeing an answer, though it seems many have asked).
Click to expand...
Click to collapse
I would have expected a deregister and reset would have restored your sn.
Beyond that I have found the sn at two locations.
/rom/devconf/SerialNumber
/rom/devconf/DeviceID
these are both text files; there may be others but this is what I found
your sn is located where your sdcard plugs in if you don't have it otherwise
I have not tried to edit these files so I can't suggest you do.
Sorry not much help but that's all I have.
I lost mine once but it returned after I replaced the restore partition and did a reset.
added info:
I pulled both files listed above and checked them with a hex editor and they contain the sn and only the sn - no extra characters of any kind (16 bytes only) permissions on are 440 and 440.
Thanks for the bit o' info. Unfortunately it's not as simple as that. The entire partition table had been deleted thus removing all of the data for the NT. I was able to recreate the partitions, and using meghd00t's & CRE's recovery method got v.1.4.0 B&N reinstalled. Now I'm not able to re-register the device with B&N due to missing DeviceID/Serial. I'm still looking around seeing if I can find a way to re-enter the info. I haven't had much luck in finding an easy way to do it, much less a hard way.
Serial number resolved / Now need Model Number & MAC location
It looks like I only had one file "/rom/devconf/DeviceID" that was only 8 zeros. I pulled the file with ADB, added my SN, saved and pushed it back. I took the saved file, renamed it to SerialNumber and did a push to rom as well.
C:\android-sdk-windows\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
0000000000000000 recovery
C:\android-sdk-windows\platform-tools>adb pull /rom/devconf/DeviceID
1 KB/s (8 bytes in 0.007s)
(here I pulled the file: notice it's only 8bytes instead of 16. Once I had the file my pc, I edited it with Notepad and added my 16digit serial, then saved)
C:\android-sdk-windows\platform-tools>adb push DeviceID /rom/devconf
2 KB/s (16 bytes in 0.007s)
(here I pushed the file back to the nook. notice it is now 16bytes)
C:\android-sdk-windows\platform-tools>adb push SerialNumber /rom/devconf
3 KB/s (16 bytes in 0.004s)
(here I renamed the file on my pc as SerialNumber then pushed it to the rom)
C:\android-sdk-windows\platform-tools>adb shell
~ # ls
ls
boot etc sd-ext
bootdata init sdcard
cache init.rc sys
data proc system
datadata res tmp
default.prop rom ueventd.acclaim.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # cd rom
cd rom
/rom # cd devconf
cd devconf
/rom/devconf # ls
ls
DeviceID SerialNumber
/rom/devconf # cat DeviceID
cat DeviceID
20202400########/rom/devconf #
/rom/devconf # cat SerialNumber
cat SerialNumber
20202400########/rom/devconf #
/rom/devconf # exit
exit
C:\android-sdk-windows\platform-tools>adb kill-server
C:\android-sdk-windows\platform-tools>
Now the Nook registers the Serial Number. What I need now is to find out where the MAC address and Model number should be listed (located). If I can get that added, I think I'll be good to go. At least I'm now half way there!
shawnshine2 said:
It looks like I only had one file "/rom/devconf/DeviceID" that was only 8 zeros. I pulled the file with ADB, added my SN, saved and pushed it back. I took the saved file, renamed it to SerialNumber and did a push to rom as well.
C:\android-sdk-windows\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
0000000000000000 recovery
C:\android-sdk-windows\platform-tools>adb pull /rom/devconf/DeviceID
1 KB/s (8 bytes in 0.007s)
(here I pulled the file: notice it's only 8bytes instead of 16. Once I had the file my pc, I edited it with Notepad and added my 16digit serial, then saved)
C:\android-sdk-windows\platform-tools>adb push DeviceID /rom/devconf
2 KB/s (16 bytes in 0.007s)
(here I pushed the file back to the nook. notice it is now 16bytes)
C:\android-sdk-windows\platform-tools>adb push SerialNumber /rom/devconf
3 KB/s (16 bytes in 0.004s)
(here I renamed the file on my pc as SerialNumber then pushed it to the rom)
C:\android-sdk-windows\platform-tools>adb shell
~ # ls
ls
boot etc sd-ext
bootdata init sdcard
cache init.rc sys
data proc system
datadata res tmp
default.prop rom ueventd.acclaim.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # cd rom
cd rom
/rom # cd devconf
cd devconf
/rom/devconf # ls
ls
DeviceID SerialNumber
/rom/devconf # cat DeviceID
cat DeviceID
20202400########/rom/devconf #
/rom/devconf # cat SerialNumber
cat SerialNumber
20202400########/rom/devconf #
/rom/devconf # exit
exit
C:\android-sdk-windows\platform-tools>adb kill-server
C:\android-sdk-windows\platform-tools>
Now the Nook registers the Serial Number. What I need now is to find out where the MAC address and Model number should be listed (located). If I can get that added, I think I'll be good to go. At least I'm now half way there!
Click to expand...
Click to collapse
Hang in there, this can be done. With cwm I formatted everything including rom and I was able to recover. I'll check on mac and get back so just remain positive.
How to find your Original B&N Nook Tablet MAC Address
I don't know if there is a way to find the Nook Tablet's original MAC address using ADB, but as far as I could find, IF you had ever flashed a version of CM7 onto your device the MAC address is given as 08:00:28:12:03:58. So unless you wrote down your original MAC address before flashing, you will end up with this one. I however do remember a little trick with pc's. When you have a bad nic card in a pc and your dealing with Firewalls and Routers (as I do for work) you can open the system and find the MAC address either printed directly on the board or listed on a sticker that's attached. So I did a little bit of rummaging through some YouTube videos and found a tear down of the NT. Lo and behold, right inside the back cover is a sticker with the NT's serial number AND MAC address. The video for cracking open your nook is here: http://www.youtube.com/watch?v=3SVO2JCgqPM And the website for the tear down is here: http://www.ifixit.com/Teardown/Nook-Tablet-Teardown/7121/1
But, if you don't have a T5 torq's screwdriver to remove the two screws at the SDcard door, if you are very very very careful and gentle, you can still use a tiny (and I mean tiny) flat head and gently insert at the bottom of the back panel right at the middle point and gently pry the back off working your screwdriver in a clockwise direction. Just don't try to pop that lower right hand corner open, you will break the case. (you been warned). Once you have about 3 quarters of the back popped off gently lift up the back cover and peer inside, you should see the SN & MAC address label. Copy the numbers. Replacing the cover back you need to be just as gentle and you want to work it back in going in a counterclockwise motion and only use the screwdriver to help work the last one or two tabs back in. If you are careful enough you won't even know that it was ever open. NOTE: There are two tiny gray paper stickers over the two screws at the SDcard door. If you remove the two papers, and expose the screws, you may have a hard time getting warrenty work done. So just know that before you start futzing with it.
Now if I can just find out where the heck the MAC address is located in the B&N v.1.4.0 software.
shawnshine2 said:
It looks like I only had one file "/rom/devconf/DeviceID" that was only 8 zeros. I pulled the file with ADB, added my SN, saved and pushed it back. I took the saved file, renamed it to SerialNumber and did a push to rom as well.
C:\android-sdk-windows\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
0000000000000000 recovery
C:\android-sdk-windows\platform-tools>adb pull /rom/devconf/DeviceID
1 KB/s (8 bytes in 0.007s)
(here I pulled the file: notice it's only 8bytes instead of 16. Once I had the file my pc, I edited it with Notepad and added my 16digit serial, then saved)
C:\android-sdk-windows\platform-tools>adb push DeviceID /rom/devconf
2 KB/s (16 bytes in 0.007s)
(here I pushed the file back to the nook. notice it is now 16bytes)
C:\android-sdk-windows\platform-tools>adb push SerialNumber /rom/devconf
3 KB/s (16 bytes in 0.004s)
(here I renamed the file on my pc as SerialNumber then pushed it to the rom)
C:\android-sdk-windows\platform-tools>adb shell
~ # ls
ls
boot etc sd-ext
bootdata init sdcard
cache init.rc sys
data proc system
datadata res tmp
default.prop rom ueventd.acclaim.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # cd rom
cd rom
/rom # cd devconf
cd devconf
/rom/devconf # ls
ls
DeviceID SerialNumber
/rom/devconf # cat DeviceID
cat DeviceID
20202400########/rom/devconf #
/rom/devconf # cat SerialNumber
cat SerialNumber
20202400########/rom/devconf #
/rom/devconf # exit
exit
C:\android-sdk-windows\platform-tools>adb kill-server
C:\android-sdk-windows\platform-tools>
Now the Nook registers the Serial Number. What I need now is to find out where the MAC address and Model number should be listed (located). If I can get that added, I think I'll be good to go. At least I'm now half way there!
Click to expand...
Click to collapse
I'm only finding the mac at one location (seems to easy) but that may be all.
/rom/devconf/MACAddress 12 bytes 440 permissions no colons used in this file just the address all typed together.
We must have been typing together. I run cm7 internal final and have my mac as from the factory. What you mentioned may have related to the first version.
I must have been asleep earlier. Model no
/rom/devconf/ModelNuumber 7 bytes permissions 440 - (BNTV250)
One more step done, another one pops up.
Add the files and I got that knocked out but still having an issue. My devconf directory only had the one original file. I've added the ones you listed and now I have the Serial, Model, and MAC all showing on the Device Info tab. I think there has to be a second MAC location as when I get the Wifi page of the setup screens, it's still listing the old bad MAC address. But It does let me connect to my router. But when it goes to register I still get the error screen. When I click Device Info button, it shows all my info in Green now, but shows Battery: ! 100% in red. I reset battery stats, but nothing changed. I'll keep cracking away at it.
shawnshine2 said:
Add the files and I got that knocked out but still having an issue. My devconf directory only had the one original file. I've added the ones you listed and now I have the Serial, Model, and MAC all showing on the Device Info tab. I think there has to be a second MAC location as when I get the Wifi page of the setup screens, it's still listing the old bad MAC address. But It does let me connect to my router. But when it goes to register I still get the error screen. When I click Device Info button, it shows all my info in Green now, but shows Battery: ! 100% in red. I reset battery stats, but nothing changed. I'll keep cracking away at it.
Click to expand...
Click to collapse
I'm getting a different sense of where we began than I was in the beginning. Are you running CM7 and if so is it from the sdcard?
As a note /rom/devconf includes seventeen files total in my configuration (cm7 alpha final internal - flashed from 1.4.0). If you are running cm7 from sdcard I'll restore to 1.4.0 and see if I can help from there.
Restored all the info / but I think it's a fruitless quest
Whole story long........ I started out with a Nook Tablet that had no partitions, I acquired it that way. It had nothing, wouldn't even boot up. So I have been playing with it for two weeks trying to get it unbricked. After many tries and countless hours, using adamoutler, veronica, and meghd00t & EMR's forum posts I was able to get it running with the SDcard (CM7). I had to recreate the partitions in ADB. I struggled with the whole boot w/wo usb cable & sdcard for a long time. Finally on Friday I used EMR's recovery image and got it where I could finally make some headway and was finally able to boot normally. I used the internal restore image that Veronica posted but was unable to register with B&N. Thus began the search for Serial Numbers & MAC Addresses. The funny thing about that image (and I don't know if it's just because I never had the files to begin with) when you had told me about all the files in /rom/devconf I was confused cause I had only the one empty file. I recreated the files you suggested but still couldn't register. So I went back to one of Veronica's other posts about restoring partition images using the dd command. I copied partition 5, 6, 7, 8, and 9 using her partition images and all of the missing information was restored. I just had to edit the SerialNumber, DeviceID, MACAddress file and I used xvi32 hex editor to add my original MAC address back into the WiFiBackupCalibration file. After all of that, I re-flashed the original recovery software and did a complete restore of the B&N software back to version 1.0.0 . I am sad to report that I am still unable to register it back with B&N. Not a really a big deal, I just wanted to see if I could get it back to as close to original as I could. Using the bypass registration technique shows that there are several additional individual "keys" (hash private key and public key)that are locked to the device from the factory (most likely to keep people from doing what we are doing) and if what is on the device doesn't match what they have in the system from the factory then it refuses the registration. (my theory anyway). So unless someone knows something I don't, that's what I'm going with. One thing I have noticed is that on the Registration Error page, just below the Device Info button is a code B-CM1004. I'm curious if that is an error code and if it is what it might mean? If I find anything else I'll post back. Moral of the story is that I've since flashed CM7 internally and I now have my original MAC address. (always a silver lining).
shawnshine2 said:
Whole story long........ I started out with a Nook Tablet that had no partitions, I acquired it that way. It had nothing, wouldn't even boot up. So I have been playing with it for two weeks trying to get it unbricked. After many tries and countless hours, using adamoutler, veronica, and meghd00t & EMR's forum posts I was able to get it running with the SDcard (CM7). I had to recreate the partitions in ADB. I struggled with the whole boot w/wo usb cable & sdcard for a long time. Finally on Friday I used EMR's recovery image and got it where I could finally make some headway and was finally able to boot normally. I used the internal restore image that Veronica posted but was unable to register with B&N. Thus began the search for Serial Numbers & MAC Addresses. The funny thing about that image (and I don't know if it's just because I never had the files to begin with) when you had told me about all the files in /rom/devconf I was confused cause I had only the one empty file. I recreated the files you suggested but still couldn't register. So I went back to one of Veronica's other posts about restoring partition images using the dd command. I copied partition 5, 6, 7, 8, and 9 using her partition images and all of the missing information was restored. I just had to edit the SerialNumber, DeviceID, MACAddress file and I used xvi32 hex editor to add my original MAC address back into the WiFiBackupCalibration file. After all of that, I re-flashed the original recovery software and did a complete restore of the B&N software back to version 1.0.0 . I am sad to report that I am still unable to register it back with B&N. Not a really a big deal, I just wanted to see if I could get it back to as close to original as I could. Using the bypass registration technique shows that there are several additional individual "keys" (hash private key and public key)that are locked to the device from the factory (most likely to keep people from doing what we are doing) and if what is on the device doesn't match what they have in the system from the factory then it refuses the registration. (my theory anyway). So unless someone knows something I don't, that's what I'm going with. One thing I have noticed is that on the Registration Error page, just below the Device Info button is a code B-CM1004. I'm curious if that is an error code and if it is what it might mean? If I find anything else I'll post back. Moral of the story is that I've since flashed CM7 internally and I now have my original MAC address. (always a silver lining).
Click to expand...
Click to collapse
I haven't abandoned your problem but from here it will be much slower to find a path unless someone with prior knowledge comments. In the meantime you may be able to register B&N from CM7 with NOOK for Android by B&N. https://play.google.com/store/search?q=nook&c=apps
I haven't made any progress toward clearing your problem. If it were mine I would think seriously about doing a CWM backup, doing this recovery “[UnBrick]TOTAL WIPE and reflash back to 1.4.0 via Ubuntu Recovery --Now Easier!!!!”.http://forum.xda-developers.com/showthread.php?t=1470910
Once that is completed reboot into recovery and allow stock 1.4.0 recovery. You could always restore your backup if this failed. If reluctant to try this then you can try NOOK for Android by B&N from Google Play(Android Market) and maybe get registered with your current setup.https://play.google.com/store/search?q=nook+for+android
I'm sorry but this is all I can formulate now.
You guys are way more knowledgeable than me, but, is it possible that you can't register your Tablet, shawnshine2, because the last owner didn't deregister it?
smarcin said:
You guys are way more knowledgeable than me, but, is it possible that you can't register your Tablet, shawnshine2, because the last owner didn't deregister it?
Click to expand...
Click to collapse
Of course it is possible. Thanks for replying 3 heads are better than 2.
I have a theory that I use to help keep me grounded so I can't agree that we know more.
Want to hear my theory? Well I'll tell you either way! I may know more about some subject but you will know more about others; it takes all of us to make the world a better place.
Thanks for your input and I'm throwing a thanks your way.
And finally the saga ends ...for better or worse.
So to give a final ( ? ) update here, after going through every forum post I could find and even trying a few things not covered I finally gave in and called customer support. Since I bought this used and completely wiped out, I didn't expect that they would be much help. I was surprised. The CSR asked a few questions about what the problem was and I give it to him straight. He was surprisingly understanding. He looked up the serial number and said it was still registered to the previous owner, but it was also still under warranty. Here he was little cautious with me, but I give him all of my buddies information, name, address, phone number, email. With that, he was a little more comfortable. He said that he needed to De-register it on their servers and then for me to try again in 15 minutes. Unfortunately, this did not fix it. I called him back and he passed me to the technical desk. They in-turn had me try to do a "hard reset" (as if I hadn't done that 100 times already). When that failed, he said that the only thing they could do was to swap it out. I figured they'd say no since I wasn't the original owner, but they actually went ahead and sent the email with the return voucher to my buddy. He was gracious enough to print it out for me. Went to the store later in the afternoon and they switched it out no questions asked with a cert. pre-owned. But in true sales-people style, they talked me into buying a new case! So, I am at a loss to say what the problem was but B&N really didn't seem to care. They just wanted to make sure I was happy with their customer service, which, at the end of the day, I am really grateful for. I'm sorry I don't have the answer that can solve this problem for others, but honesty with B&N at least got me a replacement with almost no hassle. So, if nothing else, you can always give that a shot.
shawnshine2 said:
So to give a final ( ? ) update here, after going through every forum post I could find and even trying a few things not covered I finally gave in and called customer support. Since I bought this used and completely wiped out, I didn't expect that they would be much help. I was surprised. The CSR asked a few questions about what the problem was and I give it to him straight. He was surprisingly understanding. He looked up the serial number and said it was still registered to the previous owner, but it was also still under warranty. Here he was little cautious with me, but I give him all of my buddies information, name, address, phone number, email. With that, he was a little more comfortable. He said that he needed to De-register it on their servers and then for me to try again in 15 minutes. Unfortunately, this did not fix it. I called him back and he passed me to the technical desk. They in-turn had me try to do a "hard reset" (as if I hadn't done that 100 times already). When that failed, he said that the only thing they could do was to swap it out. I figured they'd say no since I wasn't the original owner, but they actually went ahead and sent the email with the return voucher to my buddy. He was gracious enough to print it out for me. Went to the store later in the afternoon and they switched it out no questions asked with a cert. pre-owned. But in true sales-people style, they talked me into buying a new case! So, I am at a loss to say what the problem was but B&N really didn't seem to care. They just wanted to make sure I was happy with their customer service, which, at the end of the day, I am really grateful for. I'm sorry I don't have the answer that can solve this problem for others, but honesty with B&N at least got me a replacement with almost no hassle. So, if nothing else, you can always give that a shot.
Click to expand...
Click to collapse
Great! I'm glad you didn't wait any longer on me as I was stumped.
Happy computing.
Not wanting to give up but may have to
After hours and hours of searching and reading, I must say this post makes me kind of sad. I haven't taken the time to reset my serial number and MAC, but this post makes me think "why bother". I really love my Nook & I was trying to unRoot and just go back to stock. Somewhere along the way I must've clicked something wrong and hosed it all up. AdamOutler's Total Wipe method was the only thing I could find to get me out of a CWM bootloop. Mine is right at a year old (Christmas gift last year), so I seriously doubt B&N will be as forgiving with me.
Just adding to this thread in case someone has figured out anything since April. I also messaged Adam to see if he had any thoughts. Sadness is setting in.
Vol4Ever said:
After hours and hours of searching and reading, I must say this post makes me kind of sad. I haven't taken the time to reset my serial number and MAC, but this post makes me think "why bother". I really love my Nook & I was trying to unRoot and just go back to stock. Somewhere along the way I must've clicked something wrong and hosed it all up. AdamOutler's Total Wipe method was the only thing I could find to get me out of a CWM bootloop. Mine is right at a year old (Christmas gift last year), so I seriously doubt B&N will be as forgiving with me.
Just adding to this thread in case someone has figured out anything since April. I also messaged Adam to see if he had any thoughts. Sadness is setting in.
Click to expand...
Click to collapse
Have you looked at this thread?
Yes. Read in detail. It tells you how to retrieve serial number, but that apparently doesn't get you past the B&N checks that occur when setting up the tablet. It still locks up and gives the number to tech support. Without completing the activation step, you can't access the B&N store or your previously purchased content.
Vol4Ever said:
Yes. Read in detail. It tells you how to retrieve serial number, but that apparently doesn't get you past the B&N checks that occur when setting up the tablet. It still locks up and gives the number to tech support. Without completing the activation step, you can't access the B&N store or your previously purchased content.
Click to expand...
Click to collapse
My reading of that thread's first post is it's about how to put tablet's serial number (which can be found on the back of the micro-SD card slot cover) back into the NT's relevant system info files. The "Retrieve" word in the OP's thread title is, unfortunately, misleading.
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
duuude im baked said:
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
Click to expand...
Click to collapse
Thought I would share some info I found when I ran into the wifi problem on my daughter's nabi. I did some searches on the internet and the typical answer I found for solving the wifi issue was "reset the device" or "unroot and return to stock rom - flash all updates and reroot". Being a glutton for punishment, and the fact I didn't want to reset the device, I searched and searched and was able to fix my daughter's wifi without doing a reset or unroot/reroot. Before I get into it I wanted to mention that wifi failures can happen for a number of reasons so while this worked for myself, it may not work for you.
Some prerequisites:
Most importantly; you need a rooted device. If you do not have root access you will not be able to write files or access the commands to fix the issue I am about to outline.
Some knowledge of linux would be helpful, but not necessarily required.
Lets get started:
Warning! It goes without saying but I will say it anyways - you can mess up your nabi by rooting it. Some of the commands below could mess up your nabi bad. If this scares you then you probably should not proceed any further. I am not responsible for any damage you do to your nabi.
Commands are listed between ' and ' - do not use the ' when inputing the commands.
Note: The first two/three steps are not necessary but they do give you insight as to how I was able to determine my problem. If following this doesn't fix the problem for you the logcat output may give you some important info that you can google that may help you fix your particular problem.
Note: Steps 5 and on can be skipped if you have a text editor (vi or nano) on your device. If you have a text editor loaded simply edit the conf file directly.
1. You will need to run the command 'adb logcat' in a command-line window and in your appropriate directory. Adb is available as part of the android sdk but can also be found stand alone since most people do not need the sdk.
2. Try to turn on the wifi. You should see the output of your adb logcat window scroll some data. If the wifi is not attempting to turn on at all sometimes you can move between the settings options then go back to the wifi settings and move the slider. If you cannot get your wifi to turn on you can scroll the window up and attmept to find the data from when the device started up. In the output you should see lines that talk about wlan0 and probably something that says "failed" somewhere. In my case I could see where the wlan0 enabled but then a few lines down it said something about "Line: 25 failed" and "failed to parse file".
3. The file is actually a configuration file used by the wifi kernal module/driver. In my case this file had become corrupted.
4. Set adb in root mode (won't work if the device does not have root access) by running 'adb root' at the command-line. You may need to click on an "allow root permission" window on the actual device after running this command.
5. Run 'adb pull /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb shell' from command line.
b. 'su'
c. 'cat /data/misc/wifi/wpa_supplicant.conf' - copy the output from the command and paste into a text editor (see note in step 6 on why NOT to use notepad).
d. Save the file as wpa_supplicant.conf, preferrably in the same diretory as adb.
e. 'exit' twice should exit you from the adb shell and return you to your command-line. If all else failes a "ctrl-c" should drop you out of adb.
6. Use a text editor to open wpa_supplicant.conf. The file should be located int he same directory as adb. If you are using Windows I would strongly suggest you NOT use notepad. Notepad will typically change all the EOLs (End Of Line) from \n to \r\n which will really mess things up worse.
7. In the file you should see "network={" entries. There maybe one entry, there maybe many entries. You can remove all lines between "network={" and "}" including the latter themselves. If you see your 'home' network listed you can leave it as the only entry and make sure its priority is set to 1 but it maybe better to remove it as well just in case it contains part of the corrupted data.
8. Save the file.
9. Do 'adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb push wpa_supplicant.conf /sdcard/wpa_supplicant.conf' from command-line.
b. Run 'adb shell'
c. 'su'
d. 'dd if=/sdcard/wpa_supplicant.conf of=/data/misc/wifi/wpa_supplicant.conf'
e. Do 'exit' twice to exit the adb shell. If all else fails then a "ctrl-c" should drop you ot of adb.
10. If the wpa_supplicant file was corrupted then the wifi should now be able to enable and you should now be able to connect to a network.
I hope this is helpful to at least a few people.
So I bricked my Kinde Fire HDX by changing the build.prop and not fixing permissions. I have adb access but no root (I don't know why :S). Would a factory reset work? If not, how can I get to fix the build.prop or replace it with the old one? thank very much, I've been a couple hours looking for solution but I couldn't find any.
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
r3pwn said:
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I used the HDX ToolKit v0.92 to check the root access, and it said "Please grant root on your device"
I've also tried "adb shell", and then "su", but it just returns "su" again. I am new with adb commands so I don't really know what it should show.
Thank you very much for your help
May I ask what version you were on before you bricked?
Sent from my Amazon Tate using Tapatalk
14.3.2.3.2, last update I think.
?
peter_b93 said:
14.3.2.3.2, last update I think.
Click to expand...
Click to collapse
Fixed?
jimyv said:
Fixed?
Click to expand...
Click to collapse
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
well
peter_b93 said:
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
Click to expand...
Click to collapse
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
jimyv said:
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
Click to expand...
Click to collapse
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
well
peter_b93 said:
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
Click to expand...
Click to collapse
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
jimyv said:
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
Click to expand...
Click to collapse
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
peter_b93 said:
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
Click to expand...
Click to collapse
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
jimyv said:
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
Click to expand...
Click to collapse
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
sweet
GSLEON3 said:
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
Click to expand...
Click to collapse
I'm not sure either that's why when I used it I was on a blacklisted unit and I kept the PC and the tablet and airplane mode at all times. Until I was certain I got all the files off of both before I let them go to Wi-Fi Chinese files that is.. But one thing I was very curious about is if you open that tool up the Chinese tool that is an you go to the same page you would hit the anchor to root to your device just below that it says fastboot I'm wondering if they have a fastboot working for also too bad nobody here know Chinese..
This thread has been deleted.
This thread has been deleted.
This thread has been deleted.
***** really really really reserved*****
Working w/ Root on a Mac (OSX Yosemite)
CONFIRMED: This works using AT&T (SM-R750A), OSX (Yosemite), VirtualBox and Windows XP. See this link for the driver setup I used on my Mac.
http://www.onebadkid.com/?p=6930
I also find that after factory reset, I still have root! Great job!
---
Also, I haven't been able to get the scripts to work in the virtual machine so I've just been "pushing" the files manually. I did open up the scripts to get the destinations for the various files, so thank you OP. Also, you have to have the Tizen Wearables SDK installed and then use SDB commands in the terminal.
Remember, when using SDB on a Mac, it's: ./sdb [command] (you have to use the "dot-slash")
./sdb devices (to show whether or not your device is connected)
./sdb root on
./sdb shell (puts you into the device's shell so you can navigate the device in a Darwin/Linux terminal)
./sdb push [/full path of the file you want to upload to the device] [/full path of the desination]
I usually open up three Darwin/Linux Terminals on my Mac. One to use to navigate my watch in shell, the other to run the ./sdb command (just like in Windows, you have to run SDB on the mac from within it's home location: "/Users/[you]/tizen-wearable-sdk/tools"), and a third to drop files into so I can quickly see their full file path/location.
"PWD" = print working directory so you can use that in the Darwin/Linux Terminal so you don't get lost.
I'm using Windows 8.1 (don't know if it matters) but after updating to this driver my PC no longer recognized my Gear S. Had to roll back to previous driver.
Ohhhhh!!!
ohh SO installing these and getting it ready for the rest
Edit: got rootfs.img odin'd in so now i wait lmao
Wondering
Good write up so far. I had already gotten root from the previous thread with horrible direcions. LoL After I got my replacement gear s (ALWAYS CHECK YOUR SIM COVER), I rooted it using the bad direction method again (luckily I already know how to do these things), but your directions are very clear cut and noob friendly. You're doing a huge favor to new comers who come looking to root their gear. Hopefully they don't brick them before they find this.
cipherswitch said:
Got any request for certain alarms, notification sounds or ringtones? Shoot me a PM and I will get through them as fast as I can and repost here.
No themes as of yet, but I will definitely be working on custom clock faces apart from everything else
Click to expand...
Click to collapse
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Megaflop666 said:
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Click to expand...
Click to collapse
Do this
sdb root on
sdb shell
chmod +x /bin/setup-folder.sh
./bin/setup-folder.sh
Megaflop666 said:
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Click to expand...
Click to collapse
Color me embarrassed. It seems in the final uploads, I nabbed the rootfs file that wasn't done yet. Uploading the new file now,sorry for the delay.
I reset, flashed the wrong one to confirm the issue then flashed the correct rootfs and confirmed it working. That was the issue, Im waiting for the new one to upload to mediafire now.
and yeah, I couldnt type this morning, totally freaking out.
cipherswitch said:
Color me embarrassed. It seems in the final uploads, I nabbed the rootfs file that wasn't done yet. Uploading the new file now,sorry for the delay.
I reset, flashed the wrong one to confirm the issue then flashed the correct rootfs and confirmed it working. That was the issue, Im waiting for the new one to upload to mediafire now.
and yeah, I couldnt type this morning, totally freaking out.
Click to expand...
Click to collapse
Its all good, I decided to tear into some things and bricked the damn thing, so I am sitting here waiting (forever) for the original firmware to download so I can factory restore it. I was not even able to get into recovery, just download mode. LoL
Oh well, if flashing the original firmware doesn't fix it, i'll take it up to Tmo at 10am and get a new one.
new rootfs uploaded as of 12/17/14 8:42 am est, I also updated the link in the writeup.
::::::Just a quick dirty write-up of how to load sounds with your newly rooted Samsung Gear S::::::
Since most folks are rooting their Gear S for the ability of adding Ringtones (which can be done via a pay app) and adding Notifications, Wallpapers, Watch Faces, you get it......
Once you have followed the awesome rooting guide contained here and you want to load some stuff:
Path for Ringtones:
/opt/share/settings/Ringtones/
Path for Notifications:
/opt/share/settings/Alerts/
Path for Wallpapers:
/opt/share/settings/Wallpapers/
Path for Alarm Sounds:
/opt/share/settings/Alarms/
I have placed both mp3 and off files and they both work fine. Sometimes when setting your applicable Alert/Notification/Ringtone and the file is a mp3, the sound will not play, no worries, it will when the Alert/Notification/Ringtone is invoked.
To load files (Choose appropriate folder listed above)
sdb root on
sdb shell ls /opt/share/settings/Alerts/ (Shows directory listing for /opt/share/settings/Alerts/ on the Gear 2)
sdb push NAMEOFFILE /opt/share/settings/NOTIFICATION_TYPE_FOLDER (ie /Alerts or /Ringtones)
Megaflop666 said:
Its all good, I decided to tear into some things and bricked the damn thing, so I am sitting here waiting (forever) for the original firmware to download so I can factory restore it. I was not even able to get into recovery, just download mode. LoL
Oh well, if flashing the original firmware doesn't fix it, i'll take it up to Tmo at 10am and get a new one.
Click to expand...
Click to collapse
It is SO hard to brick this device so you will be fine! If you get into the firmware failed to install screen you're still good to go. Like I said, I got to bootloops and thought it was dead but stock fixed everything.
No worries you're fine!
You'll be fine!
You will be fine. I've been able to restore from this screen using stock.
Um actually..... its easier. Connect your gear, drop your content into the right folders (eg; ringtones, alerts and such) and run the update script. done and done.
ipstack said:
::::::Just a quick dirty write-up of how to load sounds with your newly rooted Samsung Gear S::::::
Since most folks are rooting their Gear S for the ability of adding Ringtones (which can be done via a pay app) and adding Notifications, Wallpapers, Watch Faces, you get it......
Once you have followed the awesome rooting guide contained here and you want to load some stuff:
Path for Ringtones:
/opt/share/settings/Ringtones/
Path for Notifications:
/opt/share/settings/Alerts/
Path for Wallpapers:
/opt/share/settings/Wallpapers/
Path for Alarm Sounds:
/opt/share/settings/Alarms/
I have placed both mp3 and off files and they both work fine. Sometimes when setting your applicable Alert/Notification/Ringtone and the file is a mp3, the sound will not play, no worries, it will when the Alert/Notification/Ringtone is invoked.
To load files (Choose appropriate folder listed above)
sdb root on
sdb shell ls /opt/share/settings/Alerts/ (Shows directory listing for /opt/share/settings/Alerts/ on the Gear 2)
sdb push NAMEOFFILE /opt/share/settings/NOTIFICATION_TYPE_FOLDER (ie /Alerts or /Ringtones)
Click to expand...
Click to collapse
sbrownla said:
It is SO hard to brick this device so you will be fine! If you get into the firmware failed to install screen you're still good to go. Like I said, I got to bootloops and thought it was dead but stock fixed everything.
No worries you're fine!
Click to expand...
Click to collapse
I wasn't worried to begin with. It's dead, stock firmware flash didn't even fix it. New one will be here tomorrow afternoon. It'll be my third one since I first bought it done my kids drowned the first one. Lmao
Megaflop666 said:
I wasn't worried to begin with. It's dead, stock firmware flash didn't even fix it. New one will be here tomorrow afternoon. It'll be my third one since I first bought it done my kids drowned the first one. Lmao
Click to expand...
Click to collapse
Hm ... what was it doing when you tried to flash?!
I was working on changing some permissions, rebooted it and it never came back, don't even have recovery. From what tmo said, this has happened to other people on this watch
So, after I finally managed to unbrick my phone, I am still left with the problem of the IMEIs being 111111111111111 and 222222222222222.
There are countless threads on this topic on these forums, but I could not get anything to work. Either they use tools with links which aren't available anymore or their solutions just plain don't work.
Something I tried more than others is generating an MP0B_001 file and pushing it over to /data/nvram/md/NVRAM/NVB_IMEI/ (Not entirely sure about the last folder name. I just tab-completed...)
However, using the generated file, changing owner and group to radio:radio and setting permissions to 660, I get no valid IMEI. *#06# is simply blank and the phone info screen says "Unknown".
Now, here's the best thing: Even after moving the original file and fixing ownership and permissions, it still does not restore the IMEI. I'm really not sure what is going on here.
What else can I do? I tried rooting my phone and installing mobile uncle, but that didn't seem to work at all. Engineering mode is missing CDS Information, so that is a no-go. Mtk Droid Tools I haven't found a working download yet. (It's also windows-only. No clue how well that is going to work with wine. I'm on Linux.)
I'm really at a loss. As far as I know, changing your IMEI is illegal in Germany. Using such an obviously fake one is just asking for trouble.
I finally figured it out! I had been at this for hours when I posted this thread and, of course, right after I post it, I manage to fix it. (Well, two hours after posting. In the grand scheme of things, right after.)
On https://www.leakite.com/2016/04/how-to-change-modify-of-fix-null-imei.html method #2 finally worked. However, the pttycmd1 is not in /dev directly, but in /dev/radio. I also had to reflash since /dev/radio was empty. (Probably due to various other attempts to change the IMEI, which made it disappear entirely)
If somebody stumbles upon this with the same problem, here's what you do:
- root your phone
- enable usb debugging
- enter an adb shell (alternatively, you can use a local root terminal)
- Execute:
su
echo 'AT+EGMR=1,7,"IMEI1"' >/dev/radio/pttycmd1
echo 'AT+EGMR=1,10,"IMEI2"' >/dev/radio/pttycmd1
- reboot
This is by far the easiest method I have found so far and ended up being the only one that worked. Why is this not recommended more often?
I agree, these methods should be more widely available on web forums etc. At moment I have tried IMEI changer but the trouble is on a dual sim phone, it seems to change both IMEIs to the same number! So far from ideal.
Just curious on method above, does one not actually put in the "" marks and just enters the actual two IMEIs?
---------- Post added at 11:32 AM ---------- Previous post was at 11:20 AM ----------
I agree, these methods should be more widely available on web forums etc. At moment I have tried IMEI changer but the trouble is on a dual sim phone, it seems to change both IMEIs to the same number! So far from ideal.
Just curious on method above, does one not actually put in the "" marks and just enters the actual two IMEIs?
Very useful I have a umi plus and I have to do A complete reset (download only) losing IMEI now I have the solution ... thank you so much
Xandaros said:
I finally figured it out! I had been at this for hours when I posted this thread and, of course, right after I post it, I manage to fix it. (Well, two hours after posting. In the grand scheme of things, right after.)
On https://www.leakite.com/2016/04/how-to-change-modify-of-fix-null-imei.html method #2 finally worked. However, the pttycmd1 is not in /dev directly, but in /dev/radio. I also had to reflash since /dev/radio was empty. (Probably due to various other attempts to change the IMEI, which made it disappear entirely)
If somebody stumbles upon this with the same problem, here's what you do:
- root your phone
- enable usb debugging
- enter an adb shell (alternatively, you can use a local root terminal)
- Execute:
su
echo 'AT+EGMR=1,7,"IMEI1"' >/dev/radio/pttycmd1
echo 'AT+EGMR=1,10,"IMEI2"' >/dev/radio/pttycmd1
- reboot
This is by far the easiest method I have found so far and ended up being the only one that worked. Why is this not recommended more often?
Click to expand...
Click to collapse
I completely agree, this is the easiest method and it just works, no software needed (if made via terminal software on the phone itself). But the commands you posted are slightly wrong. there should be a space between the AT+ and the EGMR:
Code:
su
echo 'AT+ EGMR=1,7,"IMEI1"' >/dev/radio/pttycmd1
echo 'AT+ EGMR=1,10,"IMEI2"' >/dev/radio/pttycmd1
uuzi said:
I completely agree, this is the easiest method and it just works, no software needed (if made via terminal software on the phone itself). But the commands you posted are slightly wrong. there should be a space between the AT+ and the EGMR:
Code:
su
echo 'AT+ EGMR=1,7,"IMEI1"' >/dev/radio/pttycmd1
echo 'AT+ EGMR=1,10,"IMEI2"' >/dev/radio/pttycmd1
Click to expand...
Click to collapse
Good night, I did the twrp and I think I deleted some files from the DEV folder, because my IMEI does not appear anymore. I'm with the TWRP and rooted device. Some tip to reset my IMEI. My handset is a power 3 ulefone
Thank you!
I lost IMEI after flashing stock ROM on my Elephone S8 and there was no option to set in Engineering Mode.
100% the easiest way to fix
I have a Acer Liquid E700 E39 that has /dev/radio empty too.
This happened after i flashed a stock rom.
What can i do?
Thanks in advance.
Great share for restoring IMEI, thank you!