Flashing Between Models SM-M3070 SM-M30F - Samsung Galaxy M30s Questions & Answers

Can you flash firmware between the M30s models?
I have a SM-M3070 and want to try flash SM-M307F from India for example. However when I use Odin to flash the new firmware, it says:
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
I'm guessing that I have to turn on Re-partion in the options tab. Does anyone know if this is fine to do? Most flashing tutorials says to not have that option ticked.

Related

Need help recovering Samsung S5 SM-G900A

Hi, my brother-in-law tried to root his phone but probably didn't know what he was doing with Odin and Kies. I tried to restore the phone with Kies3 but the phone is not recognized and I can't get a recovery code. I've tried the default option of booting into recovery mode and flashing with Odin as Administrator. I'm flashing following a guide on this forum using [Auto Reboot] [F. Reset Time] checked in the options and loading [AP] [CP] [CSC] first. Others have commented not to use the [BL] file. The problem is when I try to flash it fails and I get this message:
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the screen of the phone it says:
UDC START
SYS REV CHECK FAIL : Refer 3 > Binary 1
SECURE CHECK FAIL : system
Click to expand...
Click to collapse
I've tried everything I could flashing each one by one [BL] [AP] [CP] and [CSC]. Apparently the only one that successfully flashed through was [CP]. The phone can boot into recovery mode fine, when I start the phone normally it just hangs on the Samsung Galaxy S5 screen. Any help in the right direction would be appreciated. I have pretty much GoogledFu'd all the information I can and am using the stock Samsung Galaxy S5 SM-G900A firmware. I have tried different USB ports, the stock Samsung USB cable, and an LG USB cable and that didn't help either.
To flash the firmware using Odin you need to put the phone in Download mode (Power + home + volume down) and not recovery mode. Select PDA/AP in Odin, select the firmware and then click start.
DigitalBeating said:
Hi, my brother-in-law tried to root his phone but probably didn't know what he was doing with Odin and Kies. I tried to restore the phone with Kies3 but the phone is not recognized and I can't get a recovery code. I've tried the default option of booting into recovery mode and flashing with Odin as Administrator. I'm flashing following a guide on this forum using [Auto Reboot] [F. Reset Time] checked in the options and loading [AP] [CP] [CSC] first. Others have commented not to use the [BL] file. The problem is when I try to flash it fails and I get this message:
On the screen of the phone it says:
I've tried everything I could flashing each one by one [BL] [AP] [CP] and [CSC]. Apparently the only one that successfully flashed through was [CP]. The phone can boot into recovery mode fine, when I start the phone normally it just hangs on the Samsung Galaxy S5 screen. Any help in the right direction would be appreciated. I have pretty much GoogledFu'd all the information I can and am using the stock Samsung Galaxy S5 SM-G900A firmware. I have tried different USB ports, the stock Samsung USB cable, and an LG USB cable and that didn't help either.
Click to expand...
Click to collapse
Yes, I already have done that and the only thing that writes successfully is the [CP] file. It fails to write to the NAND and does a FAIL! (Auth). Not sure what else I can do.
Alright I think I figured exactly what he did to the phone. Apparently AT&T locked the bootloader on Lollipop and his phone got upgraded to Lollipop while he was sleeping. So he tried to use Odin to flash the AP for the older KitKat back onto the S5 and this softbricked the phone. As far as I have read there is no way to downgrade back currently to KitKat to get root access. I'm trying to look for stock firmware for Lollipop but I can't find anything for this model. I assume if I flash it back to the latest Lollipop version functionality will be restored. Someone said something about flashing a kernel but I don't know. Not really sure what to do now since I can't find official Samsung S5 SM-G900A firmware to flash back either through the recovery or through Odin.
DigitalBeating said:
Alright I think I figured exactly what he did to the phone. Apparently AT&T locked the bootloader on Lollipop and his phone got upgraded to Lollipop while he was sleeping. So he tried to use Odin to flash the AP for the older KitKat back onto the S5 and this softbricked the phone. As far as I have read there is no way to downgrade back currently to KitKat to get root access. I'm trying to look for stock firmware for Lollipop but I can't find anything for this model. I assume if I flash it back to the latest Lollipop version functionality will be restored. Someone said something about flashing a kernel but I don't know. Not really sure what to do now since I can't find official Samsung S5 SM-G900A firmware to flash back either through the recovery or through Odin.
Click to expand...
Click to collapse
I am currently in the same boat. Please tell me you found a fix for this and if so, what was it? Any help is greatly appreciated.
@DigitalBeating and @Theamazingcorey
Here is an AT&T lollipop firmware.....
https://www.androidfilehost.com/?fid=24591000424940454
G900AUCU4COI5_ATT4COI5_v5.1.1_Repair_Firmware
I found it (by chance) on a Russian hosting site. They say it's a 'repair' firmware which means it is more than likely going to be more than one file (it'll probably be bootloader, modem and OS) So you'll have to load each file into it's respective Odin 'slot'.
If I understand how repair firmwares work, it should wipe and format the data partitions (instead of simply overwriting them) as it flashes. This will give the best chance of a successful flash.....
http://i.imgur.com/rVnFwJM.jpg
I cannot thank you enough, that seems to have fixed my problem. I though I was going to be stuck with a paperweight, lol.
Would you happen to know if there is a way to root the the AT&T S5 with 5.1.1?
Glad it worked fella.....
With regards to rooting, everything I've read on XDA indicates AT&T Lollipop can't be rooted....and the possibility of downgrading to achieve root is non existent.......
But there's a LOT if information on XDA, and I'll be the first to admit that I haven't read it all........
http://i.imgur.com/rVnFwJM.jpg
@Theamazingcorey just out of interest, can you confirm what files were inside the zip?
http://i.imgur.com/rVnFwJM.jpg
Thanks for the info. Sorry I was not able to get back to you sooner, I've been slammed these last couple of days. Have family coming into town this evening and between work and getting ready for their visit, I haven't had time to think straight, lol.

There is no PIT partition.

Hello people,
I have tried a lot of things since two hours, but I just cannot go past it. I installed the stock firmware on my i9505 from CM12. And it worked fine. However it got unrooted by itself. Now I want to root it back and install a custom rom.
Firstly, odin never turned yellow. Now when it did, it says There is no PIT partition. I am trying to install a recovery, so that the phone gets rooted first.
I am putting the phone in download mode, connecting the USB cable, and then adding the recovery file in the PDA section. And the same result keeps coming. I have tried switching F.Reset time on and off just to check if that is working, but both don't.
I've read the suggestions on xda, and I have changed USB ports, restarted phone, laptop, changed the laptop and tried again. It also says Write protection: enable.
Here's the log as well.
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> Added!!
Please help me out on this. Thanks!
And now the phone is bricked! It says firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
thehtmldev said:
And now the phone is bricked! It says firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Click to expand...
Click to collapse
Use a different usb port / different usb cable.
thehtmldev said:
And now the phone is bricked! It says firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Click to expand...
Click to collapse
If you can't flash anymore, then install kies and select recovery mode. The recovery mode will work only if you have an active internet connection, required for downloading the system files.
Rooting is not required to install a custom rom.
Looks for a pit file for your phone and flash it together with twrp. Once you have twrp working, you can wipe the system, cache, data, etc. and flash a custom rom.
audit13 said:
Rooting is not required to install a custom rom.
Looks for a pit file for your phone and flash it together with twrp. Once you have twrp working, you can wipe the system, cache, data, etc. and flash a custom rom.
Click to expand...
Click to collapse
You can't flash pit file via twrp. He needs to reflash all, to back to the stock rom. But, odin gets error. I suggest to him to use kies to recover his phone.
Giovix92 said:
You can't flash pit file via twrp. He needs to reflash all, to back to the stock rom. But, odin gets error. I suggest to him to use kies to recover his phone.
Click to expand...
Click to collapse
You are correct in the part that Odin can't flash a .pit file. But that's not what Audit13 is saying. He is saying that when flashing TWRP through Odin he also uses the .pit file.
The .pit error in 99% of the cases is solved by using a different usb port and different cable.
Lennyz1988 said:
You are correct in the part that Odin can't flash a .pit file. But that's not what Audit13 is saying. He is saying that when flashing TWRP through Odin he also uses the .pit file.
The .pit error in 99% of the cases is solved by using a different usb port and different cable.
Click to expand...
Click to collapse
In 1% of case the .pit file is damaged. Yes, you're right about TWRP, but he can't flash the stock firmware by TWRP.
Deleted, posted message in wrong forum. Sorry.
Obtain a pit file and flash it together with your desired firmware via ODIN. I'm afraid that your pit is damaged. (Like others said if any)
Sent from my GT-I9500
Try flashing the last official firmware you used on Sammobile and let it do a full boot and then try flashing again the custom recovery...

ODIN is unable to flash stock firmware for Galaxy S4 SC-04E

Hi,
I need some assistance. I have an S4 (SC-04E) and it has TWRP custom recovery loaded in it. My colleague accidentally clicked wipe system from TWRP and it wasn't able to boot at all. So I thought I'd flash the stock firmware in order to resolve the problem. However, when I flash stock firmware on ODIN, it fails and gives me an error:
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
How do I resolve this? The original firmware was 5.0.1 and I tried flashing both 4.4.4 as well as 5.0.1, but both have failed. I googled the error and I was unable to get relevant results. I downloaded the stock firmware from sammobile. Any idea what I can do for this issue?
Your phone doesn't boot because your friend wiped the Operating System from it. The recovery should boot and flashing any custom ROM through it should make it work again.
Regarding your Odin problem, make sure you have done the following:
Used a different USB cable
Used a different USB port
Used a different Odin version
Tried another Windows
Tried a completely different PC.
All of the above can affect the outcome of flashing with Odin.

Cant flash stock firmware.

Hi Everyone
Samsung S7 Edge
Hope someone can help me.
I try flash the stock firmware on odin, but then it says there no pit partition, I download the pit file then when i try to flash it again it says pit file partition failed or something, i try different firmwares from sammobile.
When i installed smart switch it ask for recovery code,
Product Name is SM-G935F
Current Binary is Samsung Official
System Status is Custom
FAP LOCK on
Is there anyone that can help me please i would appreciate it
What error do you get on the phones download mode screen?
Sent from my SM-G935FD using Tapatalk
TOmwbb said:
Hi Everyone
Samsung S7 Edge
Hope someone can help me.
I try flash the stock firmware on odin, but then it says there no pit partition, I download the pit file then when i try to flash it again it says pit file partition failed or something, i try different firmwares from sammobile.
When i installed smart switch it ask for recovery code,
Product Name is SM-G935F
Current Binary is Samsung Official
System Status is Custom
FAP LOCK on
Is there anyone that can help me please i would appreciate it
Click to expand...
Click to collapse
You may have to flash back to the original ROM your device came with, then work your way back up to whichever version you want.
This has worked for me a few times. An example would be I was on N, so had to flash "down" to Marshmallow since nothing N and up (Oreo, Pie) would flash. And the FRP lock will be removed using this method.
If you can get into download mode you can always recover your device, it may take several attempts.
Thanks SteveMurphy,
I will try that but i dont know what rom it was the orginal one, I dont get any error message on my download screen only message i got was in odin was re-partition and then cant not find pit
when add the pit it says set pit file
:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1207)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
SteveMurphy said:
You may have to flash back to the original ROM your device came with, then work your way back up to whichever version you want.
This has worked for me a few times. An example would be I was on N, so had to flash "down" to Marshmallow since nothing N and up (Oreo, Pie) would flash. And the FRP lock will be removed using this method.
If you can get into download mode you can always recover your device, it may take several attempts.
Click to expand...
Click to collapse
TOmwbb said:
Thanks SteveMurphy,
I will try that but i dont know what rom it was the orginal one, I dont get any error message on my download screen only message i got was in odin was re-partition and then cant not find pit
when add the pit it says set pit file
:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1207)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Click to expand...
Click to collapse
I just download latest firmware now, and when i just put in the csc
I get this
ID:0/004> Odin engine v(ID:3.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 301 M
<ID:0/004> SetupConnection..
<ID:0/004> Removed!!
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Can't open the specified file. (Line: 2057)
<OSM> All threads completed. (succeed 0 / failed 1)
I would advise you download a ROM older than what you currently have and try that. I had this same issue, with the fail notification, and was able to fix not just that but also the FRP lock by flashing an old ROM (in my case it was a stock Marshmallow ROM from Sammobile).
So put all the files inside the zip (BL, AP, CSC) into their respective slots in Odin and flash it.
If you don't remember what you had, go to Sammobile and download/flash the oldest ROM they have. Latest firmwares will not work while you have FRP lock on.
SteveMurphy said:
I would advise you download a ROM older than what you currently have and try that. I had this same issue, with the fail notification, and was able to fix not just that but also the FRP lock by flashing an old ROM (in my case it was a stock Marshmallow ROM from Sammobile).
So put all the files inside the zip (BL, AP, CSC) into their respective slots in Odin and flash it.
If you don't remember what you had go to Sammobile and download/flash the oldest ROM they have. Latest firmwares will not work while you have FRP lock on.
Click to expand...
Click to collapse
Will try just now.
My windows 10 installed the driver as SAMSUNG MOBILE USB CDC COMPOSITVE DEVICE is that correct
Hi Steve do you maybe perhaps or link how installed TWRP, i still dont come right, Maybe if i installed TWRP in download mode
Thank you
TOmwbb said:
Hi Steve do you maybe perhaps or link how installed TWRP, i still dont come right, Maybe if i installed TWRP in download mode
Thank you
Click to expand...
Click to collapse
Just put the twrp file in AP slot of odin and flash.
Sent from my SM-G935FD using Tapatalk
Reason why i asked i took my phone into service center and they say on the samsung software they use the machine gives SIMRA error i dont know what that is, can it be couse the phone was rooted.
So hope if i use TWRP and go from there should work
TOmwbb said:
Reason why i asked i took my phone into service center and they say on the samsung software they use the machine gives SIMRA error i dont know what that is, can it be couse the phone was rooted.
So hope if i use TWRP and go from there should work
Click to expand...
Click to collapse
No idea what Simra error is. Twrp should work just fine.
Sent from my SM-G935FD using Tapatalk
Yeah thanks everyone for being so kind to me and trying to help me i think the error they say is fimbriae or something they saying they cant load the firmware on. So i think that could be reason maybe the phone is rooted and they cant even load the software
CAn anyone maybe link me the correct TWRP for samsung s7 edge. I see there so many but dont wanna download incorrect one.
Would appreciate it
Is it possible anyone have a Pit file for SM-G935F South africa vodafone
TOmwbb said:
CAn anyone maybe link me the correct TWRP for samsung s7 edge. I see there so many but dont wanna download incorrect one.
Would appreciate it
Click to expand...
Click to collapse
https://eu.dl.twrp.me/hero2lte/twrp-3.3.0-1-hero2lte.img.tar.html
Flash via odin.
Hi Karachi,
I tried TWRP the thing is only thing that stoppig me is odin keep saying set pit partition ive downloaded so many SM-G935F Pit files none of them are working
TOmwbb said:
Hi Karachi,
I tried TWRP the thing is only thing that stoppig me is odin keep saying set pit partition ive downloaded so many SM-G935F Pit files none of them are working
Click to expand...
Click to collapse
My name is Mustafa not Karachi[emoji23]
I live in karachi.
As for your problem, your binary in locked since odin detected an unauthorized download. I'll let you know one I find a solution.
Sent from my SM-G935FD using Tapatalk
Sorry about that thanks would appreciate it very much thank thanks
Anyone can maybe link me I need to download - G935FXXU2ERG2 XFV South Africa vodafone sammobile free download is currently off would appreacite it
HI Mustafa, I downloaded the stock rom Nougar, i tried flash it my phone says SW REV CHECK FAIL(BOOTLOADER) DEVICE 4 BINARY 2

Help with sm-a205yn

Hi, good afternoon, I have an SM-A205YN imported from vodafone and I want to unlock it for use in my country so I want to use a SM-A205G rom, I'm trying to flash a SM-A205G rom by odin3 v3.14.4 and I'm getting the following error: re-partition operation failed I'm on Windows 10, AMD c 60 processor with 8gb ram I've tried flashing with the "re-partition" box checked and also with the "re-partition" box unchecked, if anyone can help me I'll be forever grateful
Wendellsilva2408 said:
Hi, good afternoon, I have an SM-A205YN imported from vodafone and I want to unlock it for use in my country so I want to use a SM-A205G rom, I'm trying to flash a SM-A205G rom by odin3 v3.14.4 and I'm getting the following error: re-partition operation failed I'm on Windows 10, AMD c 60 processor with 8gb ram I've tried flashing with the "re-partition" box checked and also with the "re-partition" box unchecked, if anyone can help me I'll be forever grateful
Click to expand...
Click to collapse
First, before using Odin and doing other stuff, including flashing, you should unlock the bootloader. Have you followed any guide to do so, but it did not work?
The first steps are to click build number 10 times, open developer options, select OEM unlock and USB debugging, restart the phone and go to recovery mode and see if you have a bootloader unlock option...
If this does not work, you can try using the Magisk app. For this: download the app, download the firmware for you phone on the pc (which will be a .zip file), extract boot.img from it, copy that on the phone, use that file in Magisk and let the app patch it and flash with Odin (AP) the resulting patched Magisk file.
But in order to receive any help, you need to tell us exactly what step did not work for you...
By the way, unlocking the bootloader erases all data on the phone, so do a back-up beforehand.
Hi, my bootloader is already unlocked and USB debugging is enabled,I try to flash the system through odin3 but I get this error:
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 5605 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
No, do not flash the custom rom using Odin. Flash with Odin only the TWRP (TeamWin Custom Recovery Project) on the AP. If I am not mistake, there is an official version for A20. If not, there is certainly an unofficial version. TWRP is device specific. Do not install TWRP for another device or you risk bricking your device.
After flashing TWRP, go to recovery (TWRP) and see if you can see the custom recovery file before installing anything. Also, having the device connected by usb to a pc running windows and having all samsung drivers installed, you should see on your pc the contents of your phone.
Only then, wipe dalvik, cache, data and system (=also called clean flash).
If you see a bunch of encripted folders and files in TWRP, you need to first format data, then wipe, than move the custom recovery file from pc to phone, find it in twrp and flash.
Then restart to system.
If anything happends wrong, you should have on your pc the stock rom firmaware for your specific phone. Go to bootloader and flash it with Odin to save your phone.

Categories

Resources