[Q] Can I use Fastboot to change my Serial Number - General Questions and Answers

(let me preface this by saying I hope this is the right forum for this, since it's about non-device-specific boot commands. if this is the wrong place, a mod can feel free to move it.)
Phone: Motorola Photon 4g
Provider: Sprint
OS: Android 4.0.4
A few days ago, I began having occasional 3g issues. I looked under the Information tab in Settings, and it listed my Network as Unknown, so I decided to use the RSD Lite to restore everything to factory settings.
First, here is the command prompt output from the day I first unlocked my phone, 2/11/12. I've censored device specific numbers because I'm not really sure what could be used to compromise my account. But here is the first time I see my "Device ID"
Code:
moto-fastboot oem unlock
... INFOUnlocking your device can permanently VOID
your warranty.
INFOThis process cannot be reversed. If you wish to proceed,
INFOreissue the unlock OEM command containing the unique ID
INFOof your device: 042801________
OKAY [ 0.000s]
Here is a picture of one of my barcodes under my battery showing my serial number:
{
"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"
}
Here is a screenshot I took for a rom I was having issues with (the ro.telephony.default_network= line in build.prop had been commented out). As you can see, my serial number is still the one starting with TA2, the same serial number printed on the barcode outside my phone.
Now here is where **** hit the fan: After I flashed the SBF file from RSD Lite, when I rebooted it just stayed at "Connecting to Network" when I tried to update Profile or PRL. Assuming at the time it was just a network issue and my radio had been set correctly anyways, I reboot into recovery, wiped data, cache, and system, and installed a CM9 rom. When it booted, it prompted me to activate my phone, which didn't work. When I went to the same information tab as before, I saw this:
My Serial Number was now the same 042801__ number that I received as my Device ID when I first unlocked my phone. I tried restoring nandroid backups, but not only did they not fix anything, I had to move them from a folder that was named the previous TA2__ number to the new 042801__ number. At this point I decided to wipe everything I could in CWM, and reflash the SBF, but that just came back up with the infinite Connecting to Network screen.
So at this point, as far as I can tell, I have two options:
1) Find some way to change my Serial Number back to what it should be. Fastboot has a setserial command for this, but I keep getting an error message when I try. I've spent about 6 hours today trying to find more command line options for this, but I've found nothing.
2) Flash the SBF one last time and bring it in to Sprint and hope they can reconnect me.

Ok I fixed it. Turns out I had managed to erase my PDS partition, and the recovery I was using wasn't restoring it. I reinstalled an older recovery that I had used to back up my factory rom before my first wipe and restored that and everything worked great.

Related

Guide: A50 (Garminfone). How to reset to 10 tries to enter unlock code

I bought a ebay Garminfone (it's my second) and it came with 1 attempt left to enter the code. I've ordered the code, but I wanted better odds than 1 try.
Hold D-Pad left while powering on. Hold D-Pad LEFT until the next line appears:
"Wipe userdata" appears on the screen. It can take a few minutes to run its course.
{
"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"
}
It wipes EVERYTHING off the phone. Just be warned.
I did a Master Clear when it restarted, just for good measure. I have no idea if I needed to or not. I had a T-Mo SIM card (unregistered) to be able to access the Master Clear section. It may work without doing the Master Clear.
But it does reset the counter to 10 tries!
This process may even work on a HARD LOCKED phone that shows 0 attempts left, but I have not had cause to try that. This method wipes everything on the phone and restores it with the hidden/secure recovery image. Hard Lock seems to be a software issue, which can probably be changed with this method.
After I did this, I changed the .update file to the Canadian one for Videotron. The 10 tries stuck!
I am just waiting for my unlock code to give it a try.
I think it's pretty safe to buy used phones that claim not to read the SIM card etc now. Updating the old 1.6 version to 2.1 fixes that. D-Pad left + power fixes almost everything else.
This process should be able to recover from anything except if you've screwed up the bootloader or the hidden recovery image.
this method does not work on my hardlock phone, i try to update but no sucess, it hang up after rebooting in the first line until i remove battery pls any one know solution to this
segun4u said:
this method does not work on my hardlock phone, i try to update but no sucess, it hang up after rebooting in the first line until i remove battery pls any one know solution to this
Click to expand...
Click to collapse
pls someone help me here, i have code to unlock but phone is hardlock,

Can't recover IMEI using Tutty/Putty/Hyperterminal

Hi there!
I bricked my p920 a week ago while trying to flash the ported 3D-ICS rom from xbsall. I don't really know what I did wrong, but somehow I destroyed my bootloader.
However, using the "p920 resurrection guide" (http://forum.xda-developers.com/showthread.php?t=1942836), I was able to boot my phone again and to restore my nandroid backup, so that I'm back to stock-GB now (rooted, CWM installed).
Everything works fine, except that my phone does not find any network and has no IMEI anymore (yes, I know, these two symptoms are connected )
I tried to recover my IMEI using this guide here (http://forum.xda-developers.com/showthread.php?t=1734330), but I always get stuck at point 9 of the instructions (trying to type in the original IMEI using Tutty).
So far, everything goes according to the guide. I connected Tutty with my phone using COM-port 3 (the only port available in Tutty) and when I type "AT" in Tutty, the expected "OK" comes as a response.
But when I try to type "at%imei", the only response I get is "ERROR" and no dummy-IMEI shows up.
By accident I also typed "atimei" one time, the response I got was "56000 56000 OK".
...later today I'll add a screenshot with my latest Tutty-session...
{
"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"
}
So, what am I doing wrong? So far I tried all that with two different Win7(64bit) PCs and via a virtual PC running on WinXP (32bit). All drivers for my phone, Omap and Infineon are installed (Edit: at my last try yesterday, the Infineon-driver didn't seem to work. After starting CP-download mode my PC gave an error, stating it wasn't able to install drivers.)
I also tried to use Putty and Hyperterminal instead of Tutty, but with the exact same results.
Any ideas?
Bye
a noob with an O3D
I was in the same boat as you but i flashed v10k kdz file with lg b2capp and my Imei was restored.
Hope this helps
Sent from my LG-P920 using xda app-developers app
Yup..just flash kdz file and your problem will gone
Use This Tuts
Fixed it!
Good news!
I fixed my problem.
Thanks for your suggestions about flashing a kdz, but I fixed it another way, because I wasn't able to find a functional download link for any kdz-file. o,O
So here is my solution:
I think my problem was, that I backed up my system with my original nandroid-backup too early.
I repeated the whole "resurrection guide"-procedure and let the V21E stock OS installed, in this OS I had no problems fixing my IMEI using Tutty,
Afterwards I then just booted into CWM and flashed my nandroid-backup from before this whole s**t.
I thank all of you on this wonderful forum, special thanks to all the devs for their life-saving guides!

Lollipop factory image problem

I just recently followed the manual way of flashing each .img individually like I usually do. Every fastboot flash was successful I followed instructions to a T and tried it several times. The phone boots and goes through the android is-upgrading its apps then after that I get a black screen with only the time, battery ad signal in the status bar and the back arrow in the navigation aarea, ant ideas what i grg wgon"
{
"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"
}
======
Sent from my Tablet
@Jonnyredcorn Did you restore from a backup? If so try from a new device
Why nt make a clean flash and see if it persists or not?
I had this exact same problem, and assuming that you did a dirty flash (did not erase your data), this is why it's being caused
After flashing Android L onto your device it is attempting to run the "First installation" screen but is in conflict with booting up normally as you have already completed the setup.
To confirm this = Try "unlocking and locking" your phone with the power button, you should see the install menu flash up briefly, for a second or less, if that's the case then you're in the exact same situation I was in
There was an old fix for this, but isn't very reliable now, it's worth a shot anyway
"adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity"
This will force the installation overlay on top of the black screen allowing you to "setup" your phone again despite already doing it.
If this fails then your only hope is a fresh reinstall
I don't believe I did a dirty flash. I was under the understanding if I flash the factory images it did to clean white I didn't do a clean wipe and recovery prior to booting into the bootloader and flashing the factory images. I did not restore from a backup this is my first time going from KitKat to lollipop I do not see the installation screen pop up when unlocking and locking my phone
Sent from my Nexus 7
Ah okay then,
I'd suggest attempting a reinstall
If you modify the flash-all.bat removing the "-w" command, which wipes your phone, you'll be able to retain any data currently on the phone.
But as you've said you think you've wiped over it anyway, just complete another wipe over the device and flash it again, better yet download a fresh ROM first
OK so my issue was I forgot to flash the userdata.img which caused me to dirty flash. I just redid the whole thing and it's working it's working perfectly now thanks for all your help guys
Sent from my Nexus 5 running lollipop!

Trying to backup a locked Android Phone

So I have a small problem that has giving me a headache the past few days. I got an old Nokia 6.1 from my mom & was asked to get the pictures & documents from it. I removed her pattern lock, because I was annoyed to use it all the time. A couple of days later, the phone has out of the blue a security pin. Which obviously no one knows, because no one configured it...
I spent hours looking different ways to extract the data or to bypass the lock & sofar I think I ran out of all the options.
Here is my current state & I would really appreciate some advice how to proceed.
1. Find my device:
The phone is on the list. But it shows that the last activity was on the 10th january & can't be reached it even though it's connected to the internet via my mobile data. Furthermore it seems that I wouldn't be able to unlock it anyways because it only gives me two options "Call the Phone" & "Set up secure & delete".
2. Installing Aroma to extract the data/remove lock files:
I can't do that because there is no custom recovery installed on the phone. Just the stock.
3. Installing a custom recovery:
I can't install/flash anything on the phone because the developer options, usb debugging & bootloader are not unlocked/enabled.
I came as far as being able to see my dive with adb on my pc, but I couldn't flash anything of it, because the signature fails.
I'm now posting this threar, to see if anybody has some advice for me, how I could get the pictures from the phone.
Thank you all in advance~
Push
The door to any Android device is ADB.
You say
came as far as being able to see my dive with adb on my pc,
Click to expand...
Click to collapse
hence ADB obviously is fullly working, means it should be possible to pull out the data in question by means of ADB.
Hi, thank you for your answer, I have expressed myself wrong/mixed adb & fastboot up. What I wanted to say, is that I can see the device via fastboot. Unfortunately not over adb.
{
"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"
}
as you can also see in the screen
If I understood what I read, there is no way to access the phone like this, is that correct?
Is there anything else I can do?
The Phone itself gives me an option to "Apply Update from ADB". My knowledge about this stuff is barely anything. But is there a way for example I could install/update an android version/new system without losing the internal data? At that point I don't care about the phone working properly, as I would like to get the pictures from it & root + wipe everything from it.
push
As "Apply Update from ADB" implies this option is used to flash an OS's update provided by OEM/carrier: updating an OS doesn't affect user data stored on phone.
Have you ever tried to exit phone's fastboot mode by running Fastboot commands
Code:
fastboot devices
fastboot reboot
I ended up factory resetting the phone. This Thread can be closed
If you have usb debugging on. Then you can use ADB. You can try to mount user partition and you can copy that partition.

[Help] Why does my phone's boot screen look like this?

I got a pixel4a phone, but the startup screen looks like a factory mode screen. how can i remove this screen, thanks a lot
{
"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"
}
that's not a lot of info to go by. what did you do prior to getting this screen? since when has this screen been showing? is it rooted? did you do low level stuff with it, and if so, did you do it through a computer or on the phone directly?
the first thing you would want to do is to check if you can enter recovery mode (stock will do if you don't have an aftermarket) and see if you can do something with that, like, say; factory reset.
the next thing you could try is to first backup your flash, and I mean from sector 0 to EOF, and a second backup per partition, then flash a stock rom you could get online.
I WOULD preffer to just diagnose the problem and fix it non-destructively but phones and their OSes are not built to accomodate repair beyond changing the screen/batery and resetting/flasing the ROM
P.S. throw in the chipset type while you're at it I.E. MTK or QLM
Thank you for your response, bro! This phone is a second-hand phone. When I received it, it only had the factory mode. I flashed Android 11 through the website flash.android.com, but every time I boot up the phone, the screen will display for a few seconds before entering the system. I searched online and it seems that the phone is still in factory mode and needs to be activated to normal mode, but I haven't found a way to switch to normal mode.
1. Enable ADB ( AKA USB Debugging ) on phone
2. Connect computer and phone via USB-cable
3. On computer run ADB command
Code:
adb reboot
oldmaize said:
Thank you for your response, bro! This phone is a second-hand phone. When I received it, it only had the factory mode. I flashed Android 11 through the website flash.android.com, but every time I boot up the phone, the screen will display for a few seconds before entering the system. I searched online and it seems that the phone is still in factory mode and needs to be activated to normal mode, but I haven't found a way to switch to normal mode.
Click to expand...
Click to collapse
well, taht just sounds like the ROM didn't come with a boot animation/logo so I suggest if you want one you can well... there's not much you can do without tripping tamper triggers I.E. install rootkit & modify system partition (can't be done post pie) or unpack system image, insert the animation/logo and repack, but then you have an orange state device and that's not much better than that factory logo, or you lock it without image verification enabled and hope that something doesn't rely on it
android isn't built to be moded, so you have to mod it before building an hoo boy is that a wild ride
P.S. on second read, the ROM might be in eng mode instead of userdebug or user
you could check it by either terminal emulator, issueing the command `getprop` and search for build variant or do so through adb

Categories

Resources