Database Users

Acer_A500_1.105.01_EMEA_GEN3 boot.img, flexrom.img, system.img and update.zip

Ok, I extracted the boot system and flexrom from my brothers A500 which has Acer_A500_1.105.01_EMEA_GEN3 (unzip to see the update.zip, flexrom.img, boot.img and system.img).
Download here.
Let me explain what I did to restore mine to stock.
I bricked my device but thanks to the update.zip from this thread I was able to recover it.
Next I flashed the system.img and flexrom.img with the following commands in ADB (you need root obviously)
Important: in this order!
ADB shell
su
dd if=/sdcard/flexrom.img of=/dev/block/mmcblk0p6
(takes about 30 secs, 100 MB)
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
(takes a couple minutes, it's 600 MB)
First I tried to flash the boot.img also but this resulted in an LNX checksum error during start-up and had to re-apply the update.zip. So don't do this.
After the flexrom.img and system.img were flashed I rebooted the A500. Note: the A500 will be unresponsive after flashing system.img so you have to reboot manually (holding power button).
I was able to select the proper language (Dutch in my case). But wifi wasn't working so I had to make this working again using these files (depending on your kernel). You can restore wifi using this post. You might need to run gingerbreak again for root.
After that was working I was given the option to update . I tried the update but it failed due to the boot.img. I rebooted the A500 and flashed the boot.img using ADB with this command.
ADB shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p2
(takes a couple seconds, only 8 MB)
After it is finished do not reboot!! as this will result in a LNX checksum error.
Then I ran the update and it was successful. Tadaa stock A500 with firmware Acer_A500_1.141.01_EMEA_GEN3.
In any case your device doesn't offer you the update I included it with the download. The update.zip came from this post. In that case I would think you first flash boot.img and then reboot with the vol - button pressed while update.zip on your EXT_SD.
I hope this will help some people.
I redid the whole guide to check for errors and I found non.

What's new? Thanks for sharing

Nothing's new but this a way to restore your A500 back to Acer_A500_1.141.01_EMEA_GEN3 if you had to restore the tablet with an foreign update.zip.

i c. thank you.

Always keep a backup of the following partitions for any firmware version you want to restore to. (ie. i have these for my original 1.104.02 and 1.141.07).
mmcblk0p1 (recovery)
mmcblk0p2 (boot)
mmcblk0p3 (system)
mmcblk0p5 (misc)
mmcblk0p6 (flexrom)
mmcblk0p7 (??)
If bricked, use any of the base update.zips to get back to a bootable tablet.
Then to restore to your given version:
1. Push all your backup files to your device with the DD command EXCEPT mmcblk0p3 (system).
2. Run itsmagic to update the checksums
3. Push the mmcblk0p3 file last (this will cause the tab to lock up).
4. Reboot
If running the dd command from adb shell, you'll see when it finishes the push. If running it from a terminal emulator, give step 3 at least 5 full minutes to complete before rebooting.
I did this last night with my original 1.104.02 backup and then took the OTA to 1.141.07. worked perfectly.
Edit: I'm gonna update my rom flasher app to do this whole procedure

spaanplaat said:
Ok, I extracted the boot system and flexrom from my brothers A500 which has Acer_A500_1.105.01_EMEA_GEN3 (unzip to see the update.zip, flexrom.img, boot.img and system.img).
Download here.
Let me explain what I did to restore mine to stock.
I bricked my device but thanks to the update.zip from this thread I was able to recover it.
Next I flashed the system.img and flexrom.img with the following commands in ADB (you need root obviously)
Important: in this order!
ADB shell
su
dd if=/sdcard/flexrom.img of=/dev/block/mmcblk0p6
(takes about 30 secs, 100 MB)
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
(takes a couple minutes, it's 600 MB)
First I tried to flash the boot.img also but this resulted in an LNX checksum error during start-up and had to re-apply the update.zip. So don't do this.
After the flexrom.img and system.img were flashed I rebooted the A500. Note: the A500 will be unresponsive after flashing system.img so you have to reboot manually (holding power button).
I was able to select the proper language (Dutch in my case). But wifi wasn't working so I had to make this working again using these files (depending on your kernel). You can restore wifi using this post. You might need to run gingerbreak again for root.
After that was working I was given the option to update . I tried the update but it failed due to the boot.img. I rebooted the A500 and flashed the boot.img using ADB with this command.
ADB shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p2
(takes a couple seconds, only 8 MB)
After it is finished do not reboot!! as this will result in a LNX checksum error.
Then I ran the update and it was successful. Tadaa stock A500 with firmware Acer_A500_1.141.01_EMEA_GEN3.
In any case your device doesn't offer you the update I included it with the download. The update.zip came from this post. In that case I would think you first flash boot.img and then reboot with the vol - button pressed while update.zip on your EXT_SD.
I hope this will help some people.
I redid the whole guide to check for errors and I found non.
Click to expand...
Click to collapse
"Then I ran the update and it was successful. Tadaa stock A500 with firmware Acer_A500_1.141.01_EMEA_GEN3."
how you run the update if cannot reboot, i need to be clear the step before can proceed. thanks.

Euclid's Brother said:
Always keep a backup of the following partitions for any firmware version you want to restore to. (ie. i have these for my original 1.104.02 and 1.141.07).
mmcblk0p1 (recovery)
mmcblk0p2 (boot)
mmcblk0p3 (system)
mmcblk0p5 (misc)
mmcblk0p6 (flexrom)
mmcblk0p7 (??)
If bricked, use any of the base update.zips to get back to a bootable tablet.
Then to restore to your given version:
1. Push all your backup files to your device with the DD command EXCEPT mmcblk0p3 (system).
2. Run itsmagic to update the checksums
3. Push the mmcblk0p3 file last (this will cause the tab to lock up).
4. Reboot
If running the dd command from adb shell, you'll see when it finishes the push. If running it from a terminal emulator, give step 3 at least 5 full minutes to complete before rebooting.
I did this last night with my original 1.104.02 backup and then took the OTA to 1.141.07. worked perfectly.
Edit: I'm gonna update my rom flasher app to do this whole procedure
Click to expand...
Click to collapse
Thanks for sharing. I will make a backup just in case.
mrlonely78 said:
"Then I ran the update and it was successful. Tadaa stock A500 with firmware Acer_A500_1.141.01_EMEA_GEN3."
how you run the update if cannot reboot, i need to be clear the step before can proceed. thanks.
Click to expand...
Click to collapse
First you flash the boot.img but do not reboot (if you manually reboot you will get the LNX checksum error). Then check for the update. Once the update is downloaded it will automatically reboot to install the update. This is no problem as it will first check if there is a proper boot.img and then flash the update (it goes into recovery instead of just booting).

MDL -> MF4 in heimdall

Has anyone done a MDL to MF9 update in Heimdall? All of the threads I have found have been for Odin, and my preference is to use either a Linux or Mac laptop.
I am running stock firmware +root +TWRP, no other customizations.

Been searching forums for hours trying to get something to work... nothing.. I'm beginning to think it's impossible.

egyptianbman said:
Been searching forums for hours trying to get something to work... nothing.. I'm beginning to think it's impossible.
Click to expand...
Click to collapse
I gave up, booted Windows to run Odin.

You could've also dd'd the system.img after extracting the tar.md5 file.
(In recovery)
Code:
adb push system.img /tmp
adb shell /sbin/umount -a
adb shell dd if=/tmp/system.img of=/dev/block/<system partition>

I upgraded through heimdall awhile back
Sent from my SPH-L720

Tell me please usb jig work hard brick N900V

My N900V Hard Brick Can Recover USB jig

On a working SM-N900V plugging the USB jig in to the USB port with the phone off causes it to boot into Download mode. (I just tried it last night)
Except it is slightly different: at the top of the screen the first line says "Factory Mode" instead of "Odin Mode".
But I don't really know what other any other differences are. Note though that I said working SM-N900V, not hard-bricked. I seriously doubt that the USB jig is going to make your phone spring to life if you can't get into Download mode the usual way.
My guess is that your best bet is going to be finding someone who is on your same firmware release (OB6? OF1? ) and is rooted **but not unlocked** and get them to build a debrick image for you:
create debrick image
Code:
su
dd if=/dev/block/mmcblk0 bs=16384 count=16384 of=/sdcard/of1debrick.img
Someone with a bootable SM-N900V would then do this:
raw write of debrick image to *spare* SDcard
Code:
su
mkdir /data/local/tmp
cp /sdcard/of1debrick.img /data/local/tmp/of1debrick.img
umount /sdcard
echo eject your good SDCard now and put a spare in there
echo IMPORTANT NOTE "mmcblk1" BELOW, NOT ...blk0
umount /sdcard
dd of=/dev/block/mmcblk1 if=/data/local/tmp/of1debrick.img
Because your phone is not booting, you are going to have to do the raw image write onto the "spare" microSD card in an equivalent way but with some other means. (I suggest you avoid using Windows.)
I would make one for you but my phone has never been on OF1.

N900V Hard Brick Lollipop Debrick.img?

GALAXY 12345 said:
N900V Hard Brick Lollipop Debrick.img?
Click to expand...
Click to collapse
Anybody on OF1 want to help this guy out? I think he wants a OF1 debrick image.
dd if=/dev/block/mmcblk0 bs=16384 count=11776 of=/sdcard/of1debrick.img
will produce a 184 MB image file "of1debrick.img" on your SD card (slack space before p1 and p1-p22). Or you could use @hsbadr 's recovery-flashable debrick generator.
I cant generate it myself, I'm currently on MJE firmware (and won't be rolling forward in the near future). I suppose it would be better if this came from a rooted OF1 phone with a locked bootloader, but the stock aboot.mbn image could be written into place with the right incantation of dd (seek=, conv=notrunc options). I can provide those instructions.
@hsbadr didn't put up debrick images for ob6 or of1 in his file share for his unbricking thread. That's certainly not a poke at hsbadr; I'm just describing why yet another person is in an utter panic due to lack of planning.
.

Galaxy On5 - TMO G5500T - IMEI Unknown

We got a handful of free On5's when we signed up with TMO (from VZW) last year. No one really liked them much, so they have been mostly replaced by better phones. We do have two in use, however. Once was for my daughter, who was just using it on WiFi. I had loaded TWRP 3.0.2.0 on it and rooted it, but had all sorts of problems with the com.android.phone error messages. Since she is starting middle school next year, we thought it was time to add a line for her. I got the SIM via next-day air, but noticed that whenever it was in, the IMEI and IMEISV would show up as "Unknown". If I removed the SIM and rebooted, it would show a proper IMEI number.
I did a full wipe (including the internal SD card) and restored from some downloaded md5/tar files to quote-unquote "start over". Now the incessant com.android.phone messages are gone (thank God), but the IMEI is still showing "unknown", except now, it's even showing unknown when the SIM slot is empty. I also tried throwing my SIM in to see if it was an issue with her SIM, but it still shows unknown and SIM not inserted in the status bar.
From what I understand, the EFS partition contains the IMEI info. I tried a dd command to rebuild the EFS, which actually worked on my Axon 7 when I had a similar issue (no radio functions to speak of), but it didn't help. The phone is exactly the way it was.
Here are the commands I ran. Maybe they are different for the Galaxy On5?
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384
While I didn't save the output, it was very similar to this (including the "no space left" messages) output from my Axon 7.
Can anyone help?
Code:
/dev/block/platform/soc/624000.ufshc/by-name # dd if=/dev/zero of=/dev/block/boo
tdevice/by-name/modemst1 bs=16384
dd: writing '/dev/block/bootdevice/by-name/modemst1': No space left on device
129+0 records in
128+0 records out
2097152 bytes (2.0MB) copied, 0.001917 seconds, 1.0GB/s
/dev/block/platform/soc/624000.ufshc/by-name # dd if=/dev/zero of=/dev/block/boo
tdevice/by-name/modemst2 bs=16384
dd: writing '/dev/block/bootdevice/by-name/modemst2': No space left on device
129+0 records in
128+0 records out
2097152 bytes (2.0MB) copied, 0.001829 seconds, 1.1GB/s
/dev/block/platform/soc/624000.ufshc/by-name #
c:\Users\chris\Desktop\Chris Phone\Axon\modem_a2017u>

Bump.

You may give a try to z3x box.
It is good tool to repair null/unknown imei or baseband..

@ßh! said:
You may give a try to z3x box.
It is good tool to repair null/unknown imei or baseband..
Click to expand...
Click to collapse
I ended up picking up a Moto G4 to unlock and use instead, but I still would like to fix this and sell the phone. I will try z3x box tonight.

I have a issue with Efs. I cannot boot into the OS, have no root, or a custom recovery. In the stock recovery, I get an efs invalid argument message. Any ideas?

Trying the first method on this page
https://www.technobezz.com/fix-samsung-galaxy-unknown-baseband-version/

vtinoc said:
Trying the first method on this page
https://www.technobezz.com/fix-samsung-galaxy-unknown-baseband-version/
Click to expand...
Click to collapse
That was one of the first things I tried. I tried both methods. I don't remember how they failed, but they did. I'll try again, hopefully this weekend.

Try
in TWRP select "Mount" then tick efs, go back then select "Advanced" "File Manager" open efs folder select the check mark icon on lower right delete, then reboot phone.
If this works and you get network reboot into TWRP and backup efs.

vtinoc said:
Try
in TWRP select "Mount" then tick efs, go back then select "Advanced" "File Manager" open efs folder select the check mark icon on lower right delete, then reboot phone.
If this works and you get network reboot into TWRP and backup efs.
Click to expand...
Click to collapse
That was easy enough to try... but it didn't work. The folder won't delete. Here's the error I get:
Code:
rm -rf "/efs" process ended with ERROR: 1

Did the process look like this?
Or can you just clear out the folder from a root browser. Then reboot.
Have you recovered from Kies by input of your model name and S/N

Yup. It looked just like that. I also tried via terminal and root browser. Both of those actually deleted the folder. They were back after a reboot, but were still empty.
I did try Kies. It seemed to work,but after it was done, I still had no radio/imei.

Steps I have taken
Have a good rom that you can Flash from TWRP via zip On ext SD, One I use is Superstarz On5.
Steps:
Recovered from Kies from S/N let boot into setup but dont setup
Turn off, boot into Download mode flash TWRP via Odin(untick auto reboot), remove battery
Place back battery boot into phone boot into recovery. Select Wipe and tick all but Ext SD.
Then install Rom Zip. If Superstarz in Aroma choose Hard Format, once done reboot let sit to install rom.

vtinoc said:
Steps I have taken
Have a good rom that you can Flash from TWRP via zip On ext SD, One I use is Superstarz On5.
Steps:
Recovered from Kies from S/N let boot into setup but dont setup
Turn off, boot into Download mode flash TWRP via Odin(untick auto reboot), remove battery
Place back battery boot into phone boot into recovery. Select Wipe and tick all but Ext SD.
Then install Rom Zip. If Superstarz in Aroma choose Hard Format, once done reboot let sit to install rom.
Click to expand...
Click to collapse
You think that will restore the IMEI?

Its how I got mine back atlest
Odin has a Clear ESR tick, try reading on what that does

vtinoc said:
Its how I got mine back atlest
Odin has a Clear ESR tick, try reading on what that does
Click to expand...
Click to collapse
Cool. I will try that tonight.
Trying to resist not shooting the damn thing with my .308.

You can go to
https://firmwarefile.com/samsung-sm-g550t
Download file for Odin
Unzip
Run odin untick auto reboot click CP look for download CP file from Unzipped Odin files
Flash.
CP is the Baseband firmware

vtinoc said:
You can go to
https://firmwarefile.com/samsung-sm-g550t
Download file for Odin
Unzip
Run odin untick auto reboot click CP look for download CP file from Unzipped Odin files
Flash.
CP is the Baseband firmware
Click to expand...
Click to collapse
So if I do that, I don't need to do the recovery from Kies?

I would try the odin 1st its the fastest and seems like the best way

vtinoc said:
I would try the odin 1st its the fastest and seems like the best way
Click to expand...
Click to collapse
I'll try that first then. Hopefully I get some time tonight to mess with it.

Both of those say "Thailand". I would need the US-based ROM. Or does it matter... since I'll probably be putting something else on it anyway? If I'm stopping at the setup screen, it doesn't even need to be in English, I suppose.

No baseband, no Imei (N5120) Can someone help me?

Hello, I need your help, if possible.
I have a Galaxy Note 8.0 N5120 (LTE Model), which was running rooted stock rom 4.4.2.
Then, I wanted to update it to a newer Android version, and I found RR (=Resurrection Remix) , which is 7.1.2. I updated Recovery to TWRP and started testing (RR 5.8.4 and 5.8.5).
During testing, I changed versions of TWRP, too.
The main reason for testing is that in the beginning, USB OTG was not working, and with 5.8.5 usb otg was working and I was happy!! However, at some time later, USB OTG started not working, So, I thought it must be a harware issue. Then I noticed I had no baseband, no IMEI!! (I must have lost it sometime in the process of testing, because with 4.4.2 everything was working!!)
SO, I did a lot of search, and I tried the following.
First, I flashed back to original stock rom (4.4.2)
As I had "efs.img" (which I probably made with Philz Touch many years ago). I changed recovery to Philz Touch, but could not restore. So, I searched and I found a way to flash it with Philz Touch. (Before flashing I deleted all the folders and files in efs dirtory, and after flashing, I checked that the folders and files were there.)
But, still no baseband, no IMEI....
So, I searched again and I found out that erasing modemst1 and modemst2 could solve the issue.
First, I tried in TWRP (advanced - Terminal)
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
gives "no such file or directory"
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
gives "no such file or directory"
So, I setup adb in my PC (Windows 7 64bit), and started testing.
1) adb devices
gives "xxxxxx unauthorrized"
On the phone, I authorized and, then it gives "xxxxxx device"
So, I presume the connection is establed with the phone.
2) adb reboot bootloader
The phone reboots but in normal android mode (4.4.2)
I searched again, and I found out Samsung phones don't support fastboot...(I can not use fastboot commands...)
Just to check, I put the phone in Download mode (home + volume up and power on). Then I connected it to my PC, but the phone is not detected.
As adb seems to work, I tried the following.
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
gives "cannot open for write: No such file or directory"
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
gives "cannot open for write: No such file or directory"
(So, it does seem like adb works, but maybe modemst1 and 2 are in a different location...)
I have no more idea...
Is there anything I can try?