Related
Hi guys!
It was a stupid move for me to check Nand erase all option, but i did it!
At first i was not able to go in to recovery menu, only in to donwload mode.
I flashed only a.pit file via Odin 3.09 and then i was able to get in to the Recovery mode - ClockworkMod Recovery v6.0.4.7.
When i tried to wipe data/factory reset or to install zip i am gettinf error messages "Error mounting /data" or "Error mounting /sdcard/.android_secure"
Then i tried to flash the stock 4.4.2 firmware via Odin, but i am getting FAIL message on the NAND WRITE step.
What i have to do now, to get back my phone in working order ?
Thank you in advance!
If it was me I would just flashed 4.2.2 firmware MDM (which have no bootloader files)
then 4.4.2
But this is just my opinion
so many times I fix my phone with this
but Knox on my phone was tripped
Currently Knox is 0x0 on my phone and all official and do not bother with custom ROMs because it makes no sense (they do not offer anything except headaches)
gsmconn said:
If it was me I would just flashed 4.2.2 firmware MDM (which have no bootloader files)
then 4.4.2
But this is just my opinion
so many times I fix my phone with this
but Knox on my phone was tripped
Currently Knox is 0x0 on my phone and all official and do not bother with custom ROMs because it makes no sense (they do not offer anything except headaches)
Click to expand...
Click to collapse
I can't flash it, because i am getting only:
Code:
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
UPDATE!!!!
I have managed to flash new rom. I just checked again Nand erase option, this time with PIT and firmware in odin and it got passed!
But now i am in bootloop! The device is loading to the Samsung logo and it is freezing on it for a minute or two, then it is turning off.
Also i can't access the recovery!
UPDATE 2!!!
Finally, everything is fine runing!
I have flashed a stock recovery and i was able to get in to it and to wipe /data and /cache and i've got out of the bootloop!
So to summ it:
1. You have to download a propriet PIT file and firmware.
2. In Odin you have to load both of them and to check this options: Autoreboot, F.Reset Time and NAND ERASE ALL! Yes, you have to check Nand erase all, again!
3. If you got stuck in bootloop after the above steps, you have to get in to recovery and delete /data and /cache!
Hi All
I have the Hong Kong Note 4 N910U
PDA N910UXXU1AOC3
CSC N910UZZH1AOC3
As you may know, lollipop 5 is not out yet for this particular version. As I am experiencing some issues with the phone, I thought I'll just do a factory reset. However I've read somewhere here that I can use the other stock roms of the N910U eg; Taiwan 5.01 or New Zealand 5.0.1. So I thought I might aswell update to lollipop and then do a fresh factory reset.
So I downloaded this Taiwan one
PDA N910UXXU1BOD4
CSC N910UZZT1BOD4
However it keeps failing in ODIN.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910UXXU1BOD4_N910UZZT1BOD4_N910UXXU1BOD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did use all different versions of ODIN, tried on different usb ports, re-installed installed new drivers, used a different computer etc.. Still same outcome. I am using the original usb cable that came with the phone. What am I missing, any help will be much appreciated ?
gokhan04uk said:
Hi All
I have the Hong Kong Note 4 N910U
PDA N910UXXU1AOC3
CSC N910UZZH1AOC3
As you may know, lollipop 5 is not out yet for this particular version. As I am experiencing some issues with the phone, I thought I'll just do a factory reset. However I've read somewhere here that I can use the other stock roms of the N910U eg; Taiwan 5.01 or New Zealand 5.0.1. So I thought I might aswell update to lollipop and then do a fresh factory reset.
So I downloaded this Taiwan one
PDA N910UXXU1BOD4
CSC N910UZZT1BOD4
However it keeps failing in ODIN.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910UXXU1BOD4_N910UZZT1BOD4_N910UXXU1BOD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did use all different versions of ODIN, tried on different usb ports, re-installed installed new drivers, used a different computer etc.. Still same outcome. I am using the original usb cable that came with the phone. What am I missing, any help will be much appreciated ?
Click to expand...
Click to collapse
I have identical problem. Same device, same stock firmware. Trying to update to BOD4
Dancing around:
I've installed last TWRP (https://twrp.me/devices/samsunggalaxynote4exynos.html) from Odin after multiple failed attempts with N910UXXU1BOD4
Device booted normally (long boot with "updating applications")
TA-DA!
it booted to 5.0.1
It's creepy magic, but it works.
BTW, sammobile has newer version (N910UXXU1BOE3_N910UZZT1BOE3_BRI.zip)
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
stari4ek said:
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
Click to expand...
Click to collapse
Thanks for that mate. Will try it when i get home. Im not familiar with using odin or this TWRP thing. So do i download the TWRP tar file and load it to odin, then what? Can you give me the full nstructions please. Im quite confused especially the last bit under odin install method ,
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery"
gokhan04uk said:
Thanks for that mate. Will try it when i get home. Im not familiar with using odin or this TWRP thing. So do i download the TWRP tar file and load it to odin, then what? Can you give me the full nstructions please. Im quite confused especially the last bit under odin install method ,
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery"
Click to expand...
Click to collapse
My device booted to TWRP by itself without any problem, so no need to force it with keys or fastboot.
I forgot to mention, since TWRP is custom recovery You will trigger "knox void warranty 0x1", so if it's important to you - you need another way.
Does Your device boot to system after error with N910UXXU1BOD4? Cause my didn't.
Probably flashing original recovery will fix it also and will not trigger knox
I just want to clarify this just to be clear.
So after it fails you turn off, pull battery, turn on to download mode and install TWRP and then it will boot into TWRP and you just reboot and the BOE3 Taiwan firmware will just boot up? Sounds like magic, like you mentioned before.
stari4ek said:
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
Click to expand...
Click to collapse
stari4ek said:
My device booted to TWRP by itself without any problem, so no need to force it with keys or fastboot.
I forgot to mention, since TWRP is custom recovery You will trigger "knox void warranty 0x1", so if it's important to you - you need another way.
Does Your device boot to system after error with N910UXXU1BOD4? Cause my didn't.
Probably flashing original recovery will fix it also and will not trigger knox
Click to expand...
Click to collapse
Well after the error that odin gave me, i managed to recover my device using kies so my phones back on its original firmware all working. So, what is the method you used to install the latest taiwan update? Did you just go through the normal odin method or ? I dont really want to root the device, i just want to install the original stock 5.1 firmware.
a_ballads said:
I just want to clarify this just to be clear.
So after it fails you turn off, pull battery, turn on to download mode and install TWRP and then it will boot into TWRP and you just reboot and the BOE3 Taiwan firmware will just boot up? Sounds like magic, like you mentioned before.
Click to expand...
Click to collapse
yes. after error.
i "reboot" device to download mode (disconnect from usb, take out battery, put it back. volume-down+home+power).
in download mode I install TWRP.
if "auto reboot" is ticked in odin - it will reboot to new recovery (twrp) automatically. it (twrp) will perform some patching and will reboot device automatically. device will boot to system.
first boot can take a while.
---------- Post added at 10:12 AM ---------- Previous post was at 10:05 AM ----------
gokhan04uk said:
Well after the error that odin gave me, i managed to recover my device using kies so my phones back on its original firmware all working. So, what is the method you used to install the latest taiwan update? Did you just go through the normal odin method or ? I dont really want to root the device, i just want to install the original stock 5.1 firmware.
Click to expand...
Click to collapse
it.s 5.0.1 btw. There is no 5.1 yet
Yes I went through normal odin with last taiwan firmware.
it did fail with error above.
reboot to download mode.
I flashed TWRP on top of it.
when twrp is installed - system boots to new 5.0.1
KNOX is triggered!
some hours device is alive and fully working. no issues... yet =)
As usual. No responsibility here, Do it on Your own risk
stari4ek said:
yes. after error.
i "reboot" device to download mode (disconnect from usb, take out battery, put it back. volume-down+home+power).
in download mode I install TWRP.
if "auto reboot" is ticked in odin - it will reboot to new recovery (twrp) automatically. it (twrp) will perform some patching and will reboot device automatically. device will boot to system.
first boot can take a while.
---------- Post added at 10:12 AM ---------- Previous post was at 10:05 AM ----------
it.s 5.0.1 btw. There is no 5.1 yet
Yes I went through normal odin with last taiwan firmware.
it did fail with error above.
reboot to download mode.
I flashed TWRP on top of it.
when twrp is installed - system boots to new 5.0.1
KNOX is triggered!
some hours device is alive and fully working. no issues... yet =)
As usual. No responsibility here, Do it on Your own risk
Click to expand...
Click to collapse
I see. Well there should be a way of getting this installed without having to root/trigger the knox. I dont see how others are doing it through odin and our ones are failing. There should be a reason. Or it might be that this specific taiwan one fails for everyone? I did see some who flashed the new zealand one without issues..
gokhan04uk said:
I see. Well there should be a way of getting this installed without having to root/trigger the knox. I dont see how others are doing it through odin and our ones are failing. There should be a reason. Or it might be that this specific taiwan one fails for everyone? I did see some who flashed the new zealand one without issues..
Click to expand...
Click to collapse
probably it doesn't like that we're flashing different CSC.
the last image flashed is hidden.img, which if I'm not mistaken has CSC stuff
I'd expect that flashing this TAR without hidden.img or flashing original recovery instead of TWRP - will keep KNOX 0. But this homework is for someone else =)
stari4ek said:
probably it doesn't like that we're flashing different CSC.
the last image flashed is hidden.img, which if I'm not mistaken has CSC stuff
I'd expect that flashing this TAR without hidden.img or flashing original recovery instead of TWRP - will keep KNOX 0. But this homework is for someone else =)
Click to expand...
Click to collapse
Ok, Well if i do it the way you done it, will i get future ota updates or not ? i dont mind voiding warranty because the device is from hong kong, even if something goes wrong it will be a headache to send it back there and wait for it to come back. If I can get future updates wirelessly then i dont mind rooting it.
Nope. It rejects to check OTA. Manual update via Odin is still an option.
Probably, if flash original recovery and reset device, so it switches to new CSC - OTA will work. Probably.
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Salim.Keady said:
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Click to expand...
Click to collapse
This sounds interesting, can you please expand on the inductions as I am I little confused about when to flash hidden.img.
Thanks[emoji1]
Salim.Keady said:
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Click to expand...
Click to collapse
Can you give us full instructions please. I downloaded N910UXXU1BOE3_N910UZZT1BOE3_N910UXXU1BOE3_HOME
After I rename the md5 file to tar and extract. What do I do with the hidden.img file ?
Do I need to use only odin? or anything else
gokhan04uk said:
Can you give us full instructions please. I downloaded N910UXXU1BOE3_N910UZZT1BOE3_N910UXXU1BOE3_HOME
After I rename the md5 file to tar and extract. What do I do with the hidden.img file ?
Do I need to use only odin? or anything else
Click to expand...
Click to collapse
Flash firmware
Hidden fails
Extract hidden.img and flash it as pda
Simple as that
And remeber am not responsible even if it worked for me and another user
Salim.Keady said:
Flash firmware
Hidden fails
Extract hidden.img and flash it as pda
Simple as that
And remeber am not responsible even if it worked for me and another user
Click to expand...
Click to collapse
So I have to go through the normal odin process. Once it fails. I have to flash hidden.img through odin?
gokhan04uk said:
So I have to go through the normal odin process. Once it fails. I have to flash hidden.img through odin?
Click to expand...
Click to collapse
Yes
How do you even flash the hidden.img,ext4 files through odin?
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.
Hi, when trying to flash my Verizon S7 back to stock (with the correct verizon files) I got this odin log
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When trying to exit I got the "Software Update Failed" and when trying to flash again it's just a stuck bar on my screen. Not sure what to do and I'm kinda of new to this but I'd appreciate any help. Since then my phone has been stuck on the green screen since and whenever I press anything it just returns to the screen.
Any fast help would really be appreciated, it's been like this for hours and I'm not sure what to do ):
I'm gonna take a quick stab at this and say use the other CSC file, whichever one you haven't tried (either csc_vzw or home_csc_vzw).
Do not use the HOME_CSC file. Use the CSC and be sure that all of the images are in the correct spots in ODIN.
Was the device rooted? If so, you may not have gotten rid of all the root files, so it detects modified and won't flash.
Which firmware are you trying to flash? Were you on Nougat? We need more information.
Are you going from U firmware? I had to check repartition when I did.
ironbesterer said:
Do not use the HOME_CSC file. Use the CSC and be sure that all of the images are in the correct spots in ODIN.
Was the device rooted? If so, you may not have gotten rid of all the root files, so it detects modified and won't flash.
Which firmware are you trying to flash? Were you on Nougat? We need more information.
Click to expand...
Click to collapse
I was rooted through the steps found here
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I tried to flash back to stock and got the error after that. My phone's battery died and it's just sitting on my desk now );
Sayunoi said:
I was rooted through the steps found here
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I tried to flash back to stock and got the error after that. My phone's battery died and it's just sitting on my desk now );
Click to expand...
Click to collapse
Same thing here. I can only get into stock recovery with the error "dm-verity verification failed" (most options are disabled), and into bootloader, but unable to flash stock ROM; it just fails every time.
I'd be glad for a solution!
Don't forget the bootloader file too. I believe the root thread doesn't include the BL file in the instructions, but the error disappeared when I included the Bootloader.
azoller1 said:
Don't forget the bootloader file too. I believe the root thread doesn't include the BL file in the instructions, but the error disappeared when I included the Bootloader.
Click to expand...
Click to collapse
Mine still has the error when I included the bootloader file.
Another thing I should mention is in the top right it says "SW REV CHECK FAIL : [system] Fused 3 > Binary 1
I tried changing the wire, using the boot loader file, and changing usb ports. Lost here );
Sayunoi said:
When trying to exit I got the "Software Update Failed"
Click to expand...
Click to collapse
I tried going back to stock as well and am stuck on this screen. It says to use the Verizon Software Repair Assistant on a computer to repair it. I've only ever rooted a kindle fire so I don't know too much. Any way I can just get my phone back to normal?
JaffXsMan said:
I tried going back to stock as well and am stuck on this screen. It says to use the Verizon Software Repair Assistant on a computer to repair it. I've only ever rooted a kindle fire so I don't know too much. Any way I can just get my phone back to normal?
Click to expand...
Click to collapse
Really wondering the same thing =/
I think maybe I'm trying to flash back to an older version. Does anyone have a link for the latest Galaxy S7 stock rom?
Sayunoi said:
I think maybe I'm trying to flash back to an older version. Does anyone have a link for the latest Galaxy S7 stock rom?
Click to expand...
Click to collapse
You cannot flash a stock rom with an older bootloader than what ever you currently have on your phone. You can only Odin flash a stock rom with same or newer bootloader. So usually you cannot go to an older rom only newer.
Can I try flashing stock rom while in the Software update failed screen, or do I need to be in download mode?
Sayunoi said:
I tried changing the wire, using the boot loader file, and changing usb ports. Lost here );
Click to expand...
Click to collapse
Try re-downloading the firmware. Are you sure you had the right firmware downloaded? The error seems to be caused by some kind of mismatch between the software trying to be flashed and what software you currently have on your phone
Also, make sure you are using the non princecosmy Odin 3.12
When ever I try to flash stock onto my phone, i'm getting the error "SW REV CHECK FAILED : [aboot] fused 4 > binary 2" I don't know what any of this means. Could someone explain this? Also when trying to flash stock i'm in "System Update Failed" screen and a little bar appears at the bottom. Does this mean it is still able to download the stock rom at all? One last thing, if I were to try and flash G935U instead of G935V could that help? Any help would be nice
go to samfirm and download the latest firmware for the S7 that you have, try flashing with that. I had to put everything in it's place in odin and select reformat to unroot my phone. I ran into the dm_verification failed and the only option was to download the latest firmware and flash that.
JerseyDubbin said:
go to samfirm and download the latest firmware for the S7 that you have, try flashing with that. I had to put everything in it's place in odin and select reformat to unroot my phone.
Click to expand...
Click to collapse
Do you mean sammobile? https://www.sammobile.com/firmwares/database/SM-G935F/
That or http://samfirm.net/I believe.
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.