[GT-I9020T] Nexus S the IMEI is unknown since flashing new ROM - Nexus S General

Bootloader version: I9020XXKA3
Baseband version: I9020XXKD1
Build number: GRJ22
Android version: 2.3.4
When i go into Settings in Android the IMEI number is unknown.
I'm trying to revert back to the Stock ROM, but i'm having problems, because when I try and boot in recovery, I get an error from the boatloader saying no boot or recovery img found.
is there a way to flash a full rom with fastboot? Or why can't I boot into recovery anymore?

If you don't have a copy of your EFS folder you are out of luck.
Besides that restoring an IMEI is mostlikely a punishable crime in your country (changing is in almost every country, restoring in most).

I'm trying to restore from stock via the one_click_method, but it fails trying to write the radio partition.
>$ fastboot-mac flash radio radio.img
sending 'radio' (15232 KB)... OKAY
writing 'radio'... FAILED (remote: Write Fail)
So I tried to erase the radio partition but I get this error:
>$ fastboot-mac erase radio
erasing 'radio'... FAILED (remote: No Allowance on This Partition)
I'm not sure what I'm doing wrong here.
Thanks,

@rentaric, I don't understand? Isn't the IMEI number just a number burned into the hardware like a mac address?
I thought maybe I flash the wrong radio or something and that is why the IMEI isn't showing up.
Well that's strange if I can't ever have a IMEI number...

You can have it jtag which will restore the imei. There's a guy on YouTube who does it many times. Mobile tech videos is the channel name.
Sent from my Nexus S using XDA App

djgerbavore said:
@rentaric, I don't understand? Isn't the IMEI number just a number burned into the hardware like a mac address?
Click to expand...
Click to collapse
Yes and no, it's what identifies your phone. Eg a criminal fakes your phone's IMEI, police gets hold of the criminal's IMEI, which is basically yours, checks with carriers who is the owner of that IMEI, you are in trouble initially. To prevent ppl from doing that in the first place it is illegal to change the IMEI of your device, some countries added more strict laws on top and also don't allow restoring of (your own) IMEI.
Also carrier blacklist phones via the IMEI, eg if the phone was stolen.

Related

[Q] How to restore my original Google Dev Phone Boot Loader?

I have a Google Dev Phone 1. I installed some mod image before, my flash screen is now showing 'T-Mobile G1'.
Now I try to put my Google Dev Phone 1 image(downloaded from HTC website) back. I load the radio image. When I try to install the system image, I got the following message:
Code:
ren:1.6 image ren$ ./fastboot-mac update signed-dream_devphone_userdebug-img-14721.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.33.2005
Baseband Version.....: 2.22.19.26I
Serial Number........: HT92RLZ00725
--------------------------------------------
checking product... OKAY
checking serialno... OKAY
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2005'.
Update requires '1.33.2004' or '1.33.0004' or '0.95.3000' or '0.95.0000'.
Looks like my phone doesn't have the GoogleDevPhone boot loader anymore. Is there a way to restore it?
You have an engineering SPL, so don't worry about that.
I'm not sure why it's failing, HTC documentation says you should use "$ fastboot update <imagepackage>.zip [-w]". That could be it, either way it's much easier to avoid fastboot.
Simply place the update.zip on the sdcard and flash from recovery
Now I managed to restore an T-mobile 1 image back. When I power on the phone I got T-Mobile splash screen and it ask me to setup Google Account.
I'm in Australia using a Vodafone sim card. So I need to modify APN setting before I can connect to Google server. However it doesn't seem to let me modify APN setting.
I think I still need to put my GoogleDevPhone image back. Does someone knows how?
Cheers
renshao said:
Now I managed to restore an T-mobile 1 image back. When I power on the phone I got T-Mobile splash screen and it ask me to setup Google Account.
I'm in Australia using a Vodafone sim card. So I need to modify APN setting before I can connect to Google server. However it doesn't seem to let me modify APN setting.
I think I still need to put my GoogleDevPhone image back. Does someone knows how?
Cheers
Click to expand...
Click to collapse
Which image on htc website did you download? There are several versions. I tried the "OTA" before, it worked well. I did that in the following steps:
1. I flashed the T-Mobile image ( .nth file ) in fastboot and then used telnet to root my device.
2. I downloaded the radio image and renamed it "update.zip", then flash it in recovery.
3. I downloaded the system image and renamed it "update.zip", then flash it in recovery.
4. All done.
There are two formats of system image available on developer.htc.com/adp.html.
1) the "ota-####" package -- flashed via recovery.
2) the "img-####" package -- flashed via FASTBOOT.
You have two options here.
1) modify the "ota-####" to eliminate the bootloader check.
2) use the "img-####" via fastboot as per the instructions on that website.

plz help p8 lite hang logo

i have p8 ale-l21 hang logo no recovery bootloader lock only go fastboot
cant flash with dload file any help plz
Use THIS instruction to extract the needed files from the UPDATE.APP file, and follow THIS instruction to flash them via fastboot.
Use your already downloaded UPDATE.APP file, and it should work fine, after flashing at least the BOOT, RECOVERY and SYSTEM partitions. If the UPDATE.APP has a CUST image, flash that too.
thx about quick reply
but how to flash recovery and boot with bootloader locked
sending 'boot' (22796 KB)...
FAILED (unknown status code)
finished. total time: 0.651s
mandolen said:
thx about quick reply
but how to flash recovery and boot with bootloader locked
sending 'boot' (22796 KB)...
FAILED (unknown status code)
finished. total time: 0.651s
Click to expand...
Click to collapse
Keep the phone in fastboot/bootloader mode and Try this command adb fastboot oem unlock.
Sent from my SM-J500F using XDA-Developers mobile app
im not have code unlock bootloader and product id and imie
Do you have the packaging of the phone? The box should have a label on the bottom, with your S/N and your IMEI.
If you send those two numbers to me in Private Message, I'll give you your bootloader unlock code in the reply.
If the S/N number is not present on the box itself, it still can be obtained. Connect the phone to your PC via fastboot, and type fastboot devices.
There should be only 1 list item, which is your phone, identified by it's S/N number.
The IMEI is often written on the invoice as well.
If you don't have these numbers, the only way you can get your phone back to life, is via repair.
If the phone got bricked while you was updating, the warranty should cover that. In this case, just return it, and you'll get a new one.
But if your phone was rooted without unlocking the bootloader, your warranty is void.
Note: please don't use colored, or formatted fonts if not necessary to do so. Thanks.
Note2: There should be a way to obtain all these information, even more, with fastboot, using the fastboot getvar all command, but seems like Huawei disabled this, for unkown reasons...
this my imie and s/n plz any one give me code unlock bootloader
imie1--869510020795934
imie2--869510020822670
s/n--W3D7N15B20006862

[XT1642][Baseband:EMEA][Channel:RETEU (Retail Europe)][dd images]

Hello everyone,
These are XT1642 Baseband EMEA Channel Retail Europe dd images.All 48 "by-name" partitions, including modem, modemst1 and modemst2.
I was unfortunately going by my own, trying to restore IMEI code and modem functionality of my first XT1642. I bought a typical phone and made dd images of all partitions.
I then engaged into trying to change IMEI code of my failed set. The best try was done by EFS_Professional_2.1.80_BETA, which I downloaded here from XDA, but I got the error NV_ERR_BAD_SECURITY_MODE.
I then resorted to flashing the dd images. Thinking out of focus as I did (I should have tested only modem images: modem, modemst1,modemst2 and fsg) I flashed images one by one in TWRP, until I felt something went wrong (sure it had to), so I rebooted to find I locked myself out at bootloader.
Bootloader says "oem_locked" and yet fails to boot in any mode: recovery, reset or other.
So this is the inevitable end: I was supposed to leave the phone set dead until a toolbox or a hardware hack come out, since I already tried at repair shops and non exist for Athene.
Now to the juicy parts: I promised myself I post these dd images, not just for modem issues, but for anyone wishing to manipulate XT1642 EMEA RETEU. Maybe these could just help.
The images are taken off MPJ24.23-4.
dd images: Google Drive and MediaFire
EFS Professional 2.1.80 Beta: Google Drive and MediaFire
"Manipulating" the IEMI is illegal.
And wrong because it will hurt another person's phone too, that has that IEMI.
SoNic67 said:
"Manipulating" the IEMI is illegal.
And wrong because it will hurt another person's phone too, that has that IEMI.
Click to expand...
Click to collapse
The partitions described don't contain an IMEI. I guess there is no problem here.

Bricked - Screen Not Turning On

If there is a thread that solves a problem like mine, please point me to it, thanks.
Basically, I had updated my phone to Nougat which resulted in the infamous test-keys build number, instead of the right one (my device is VNS-L31 and it was single-SIM, supposedly.) I was fine with it, but at some point SuperSU auto-updated through the play store and I lost root. So I tried rooting it, but couldn't boot into recovery. Even when I managed to, SuperSU would not flash properly. So I thought I should roll back and do it properly.
I tried the rollback packages through dload from the rollback to MM thread, they wouldn't work. I found another thread that seemed to be describing the 'good way' so I did as it said. Flashed the OEMinfo provided, but then it told me the data partition was damaged. I turned it off and updated through dload, which went to 100%, turned off. And that's that. Screen is not turning on, no tactile feeling from the power button. The only thing that I seem to access is fastboot and only on the pc, the phone shows nothing.
Now I have tried flashing the extracted system, boot and recovery.img from the update zip and even though it says okay, nothing happens. The bootlocker seems to be unlocked still, thankfully I kept the pass!
fastboot oem get-build-number gives 'VNS-C432B120'
Any help would be appreciated.
EDIT: Since flashing the separate images does not seem to work, and fastboot erase system -w results in:
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'system'...
FAILED (remote: Command not allowed)
I think that perhaps the partition table is messed up? Even though as I said the separate images seem to flash fine, without any errors... I tried to flash the whole update.zip or even a couple of ROMs, but it says that there is no android-info.txt. Is there any ROM which includes the android-info.txt or android-product.txt? Or does anyone perhaps know what the .txt should say inside? I have found some threads about HTC phones where they know the content of the .txt file, which is 4 tiny lines mentioning the model ID, main version and such information.

Bootloop redmi 7a vendor.img cant flash

so im trying this since yesterday
Please help me ive been trying to find solution everything flashes except when i try flashing vendor.img it says vendor error : buffer overreads occured due to invalid sparse header how can i fix this my device is redmi7A with unlocked bootloader using original cable on usb2 slot trying to unbrick it since yesterday using latest flashtool and drivers using this firmware eu version Xiaomi_Redmi_7A_V11.0.3.0.QCMEUXM_20200728.0000.00_EEA_10_XFT also would like to mention i unlocked bootloader installed twrp and formated all partitions (brave man i am) tryed using the default firmware upgrade tool also tryed manually installing vendor.img from the firmware but no success tryed formating the partition under twrp to ext2 and returned it to ext4 didnt try to change the size or anything ....this all because the default firmware couldnt install game me vendor error ... at this point im giving up on it ... if anyone knows what must be done hes welcome :fingers-crossed:
here is the msg :
fastboot flash vendor vendor.img
target reported max download size of 535821312 bytes
sending 'vendor' (290176 KB)...
OKAY [ 9.152s]
writing 'vendor'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 12.419s
....last time i ever buy a chinese device from 5-6 different firmwares i could test only 2 because the others didnt have all the files required in the images folder .....chinese piece of trash and thats it...no way of restoring my device even with the default firmware i still cannot understand did i do something wrong or what......
What says when you tried to flash the vendor with twrp?
first check if you using the newest fastboot version via: fastboot --version
are u sure that you have the EEA Hardware?
when u have access to twrp(recovery) try sideload via adb sideload
and here is a how to flash manually link:
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
How to flash a factory image | Return to stock | Unroot your Nexus 5 Hello Nexus 5 Users! I see many users that don't know how to restore their Nexus 5 to stock. It may come in handy, either when you want to RMA your phone, or you want to...
forum.xda-developers.com
plstanchev said:
....last time i ever buy a chinese device .....chinese piece of trash and thats it...
Click to expand...
Click to collapse
this could happen to you with any device! for me the 7A is a really great device. if you unlocked your bootloader you know that there is always a chance to brick your phone! so take responsibility for your actions and don't blame the manufacturer.
PS: if you use more dots and enter it would be much more better to read through your post if someone is trying to help :/
I am also not responsible if anything goes wrong.
May be your download file is corrupted, have you checked the integrity of that file, the extension (.tgz) fastboot firmware.
And flash them with mitool and always download from official site.

Categories

Resources