Database Info

[Q] Can I use Fastboot to change my Serial Number

(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.

Understanding S1 Service mode

Can anyone help to understand S1 Service mode (not a fastboot) ?
For example, Sony device [ vid: 0FCE ; pid: ADDE ] also like [ SOMC Flash Device ]
Where I can get more information about this ? from what to start ? something about structure / commands etc. Would be great to see anything without sniffing and debugging usb traffic <_<
Can I, for example, push bootloader into RAM then access to its commands such as loading something into addrX then to start evaluation from that addrX and so on. How about without emmc (CPU + RAM only) ? How about u-boot?
I started from problem here (I also have trim-area (TA) backup, but...):
https://forum.xda-developers.com/showpost.php?p=76505189&postcount=714 (phone is not mine)
Mainly I can't think of how I can inspect emmc on hardware problems without soldering at all because I have no Z3X or something else. So I can programming only via USB and some other related things if it's not so hard to prepare at home manually.
Anyway, would be great to solve or at least understand this problem in details.
So any suggestions for more understanding this bug or S1 Service are very welcomed!

Well, looks like emmc is dead. Don't know why ( Samsung KLMAG2GEAC-B001 ).
Unfortunately, but I still have no any information about mentioned S1 mode. Thus I can't understand is it possible to redirect most common requests for emmc to sd card.
That is, something like to use preloader for allocating in upper range of RAM the our modified loader. Then writing and running at this address which will provide information about emmc from another way. +TA/Boot/...
hmm, I think I will not spend my time for this device today anymore However, any info about S1 still is actual of course.

ah yes, don't know the good place for writing about the following tips below (move it if you need). Just my bonus for everyone when I was checking mentioned device above:
[ Sony Xperia Z Ultra C6833 ]
* Found UART:
1. RX
2. TX
3. GND
4. VCC is not required.
{
"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"
}
Click to expand...
Click to collapse
* Solution to charge the Xperia Z ultra battery with very low voltage (less than 2.6v etc) without phone but still through battery controller:
! Strictly observe the polarity of the connection. Otherwise it will be corrupted. !
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
3.8+ it's okay now:
Click to expand...
Click to collapse
* About Test-point you should already know where it placed from other topics otherwise, find the red dot from first image above

Impossible to reinstall a rom after root

Hello guys,
I'm new here, I've read a lot about your different topics and I'm admirative for some level god members with their answers :good: :laugh:
Indeed I'm a dev, but for websites so it's a bit different with phones for me, and I will try to explain as detailed as I can.
I have a samsung SM G965F, bought in Poland (I work here for the moment); And indeed tried to root it for private purposes.
I followed a tutorial; I was on Pie 9 (****tiest ever update for me); from there OEM in DEV tools was activated, and the TWRP was installed.
the phone wasn't root, but I had the TWRP options (when push Volume up+bixby+lock) so thought I'm on the good way, but only after, and there is my mistake, I understood by reading something that I should make faster an operation when enabled the OEM (before it start to delete all my infos) that I should switch to recovery mode (or installation) and if not there was a story with 7 days to wait.
So the phone was just reseted with only memory card datas not deleted, and the phone was working, just the OEM always disabled, and when you select to enable it it says "ok we reboot the phone you will loose all your files etcc..." and anyway after many attempts, it says always the same after the reboots, and never is enabled after. So I tried to install a new rom, and then I thought I had a problem, in the installation it was written "Secure Check Fail : PIT".
So I tried to found the right rom, with the number "6" inside as per this screen :
{
"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"
}
Then the Secure Check Fail : PIT dissapeared and now its just Fail in Odin.
Also, I tried to reboot normally but it says that there was an error and I need to reinstall with smart view or smart touch, I don't really remember, so I just reinstalled the first TWRP and now the screen of my phone is looping on Samsung, and rebooting.
I'm lost, I spent from 3pm to 4 am yesterday in the internet to found a solution, so my final option is write to ask your help guys.
Hope you can help me, thank you in advance
PS: Sorry for the big picture, there is no acceptance unfortunately for resizing codes, or maybe I just still don't have access to this option cuz I have less than 10 messages, if need delete it or explain me if you need pictures, I did it 10 min ago, even if there is not a lot to do because i'm limited with my phone now

Question Pixel 7 Pro stuck on "usb serial device" with no screen

Hey all,
after trying to flash images from a private build
[
1) REPO: repo init -u https://android.googlesource.com/platform/manifest -b android-13.0.0_r11
2) LUNCH: aosp_cheetah-userdebug
3) fastboot flashall -w for the out directory
]
the Pixel was stuck on a boot loop, showing the google screen but nothing more.
after battery drained, tried to put it on fastboot mode, unsucessfully
right now, the device is in this state, with black screen showing nothing.
{
"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"
}
Does someone know what tools are needed to save the device and guide to do it?
and second question - something in the process I described above is wrong about the flashing that caused it to fail?

Wow...where to begin...?!
I completely don't know to what end you were attempting to get to or how you were trying to get there, but looking at such an unconventional method of flashing and unconventional "private build" (so I assume not the full factory images Google publishes on their dev page), I wouldn't be surprised if you didn't permanently brick your device -- especially considering the outcome is a weird "USB Serial Device" and black screen/no fastboot mode...
But what I suggest is powering on using the button combination (I believe it is PWR & VOL+Down), sometimes it takes 1-2+ minutes holding it down.
I would suggest correcting the driver, but I'm unsure if that will lead anywhere if you cannot get into fastboot mode and/or the screen stays black. But, if you think it will help; download the Google USB Drivers (can be found HERE), unzip it, uninstall (and MOST IMPORTANTLY tick the box that says delete the driver software if it pops up) the "USB Serial Device", Scan for New Hardware, if the new driver does not identify as "Android Bootloader Interface" then -- right click the new driver -- click update driver -- and either Browse to the folder where you unzipped the Google USB Drivers or manually "Let Me Pick from available drivers" and manually select the .inf file to install the driver as. That should correct your driver issue, though I don't know how helpful it will be without the screen or being able to get into fastboot mode...
And, if you don't want to risk breaking your P7P, I would suggest from now on sticking with traditional methods of flashing (platform tools or recovery mode) and Google Full Factory Images or established ROMs....
Or maybe research considerably more in the unconventional method you are trying to attempt...
Good luck to you, seems you will need it...

it's basically flashing from here
Pixel Phones as Development Platforms | Android Open Source Project
source.android.com
which I assumed will be no problems
I have tried the combinations to fastboot, but unsuccessfully, all I see is black screen.
thanks for reply.

[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