Related
I've been reading many threads over the last 3 days, and I can't get back my SM-N9005 LTE 32Gb.
My N9005 (Portuguese TPH) bricked doing a firmware update from 4.4.2 N9005XXUGNG1 (Portuguese TPH) to 5.0 Lollipop N9005XXUGBOB6 (Poland XEO) with Odin 3.09. Odin said success (PASS), but phone never rebooted.
Solution #1: http://forum.xda-developers.com/showthread.php?t=2531224 Thanks @msmercy42 I learned a lot from it but none of the N9005 unbrick.img worked for me.
Solution #2: http://forum.xda-developers.com/showthread.php?t=2625332 Thanks @ValenteL finally my N9005 goes into ODIN/Download mode.
However, I belive that solution #2 isn't going as smooth as it should. This is what I get when I get the phone to start from SD card:
Code:
[COLOR="Lime"]BOOT RECOVERY MODE[/COLOR]
CHECK BOOT PARTITIONS. .
COPY FROM T-FLASH. .
BOOT RECOVERY. .
WRITE 163840 sectors. .
[COLOR="Red"]FLASH WRITE FAILURE[/COLOR]
ddi : mmc_read failed
[COLOR="red"]ODIN MODE[/COLOR]
PRODUCT NAME: SM-N9005
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
[COLOR="Gray"]QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
And then, Odin recognizes the phone.
Now I'm able to get Odin to recognize the phone, but I can't do anything with it. I've tried:
- flashing 4.4.2 N9005XXUGNG1 (Portuguese TPH) again - FAIL (see attachments) Phone outputs two lines, after UDC START:
Code:
[COLOR="Gray"](...)
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
MMC: mmc_read fail
[COLOR="Red"]ODIN : flash read failure[/COLOR]
- flashing N9005XXUGBOB6 (Poland XEO) again - FAIL
- flashing PIT files (tried 3 different ones) - FAIL Phone outputs another line, after UDC START:
Code:
[COLOR="Gray"](...)
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
MMC: mmc_read fail
I wasn't able to get any unbrick.img from a N9005 Lollipop yet. Is this the final solution for my problem? Since I'm able to get to odin mode, shouldn't this unbrick be enough? What does it mean "mmc_read fail"?? Any help?!?! I don't know what else to do...
Thanks!!
Skactus said:
I've been reading many threads over the last 3 days, and I can't get back my SM-N9005 LTE 32Gb.
My N9005 (Portuguese TPH) bricked doing a firmware update from 4.4.2 N9005XXUGNG1 (Portuguese TPH) to 5.0 Lollipop N9005XXUGBOB6 (Poland XEO) with Odin 3.09. Odin said success (PASS), but phone never rebooted.
Solution #1: http://forum.xda-developers.com/showthread.php?t=2531224 Thanks @msmercy42 I learned a lot from it but none of the N9005 unbrick.img worked for me.
Solution #2: http://forum.xda-developers.com/showthread.php?t=2625332 Thanks @ValenteL finally my N9005 goes into ODIN/Download mode.
However, I belive that solution #2 isn't going as smooth as it should. This is what I get when I get the phone to start from SD card:
Code:
[COLOR="Lime"]BOOT RECOVERY MODE[/COLOR]
CHECK BOOT PARTITIONS. .
COPY FROM T-FLASH. .
BOOT RECOVERY. .
WRITE 163840 sectors. .
[COLOR="Red"]FLASH WRITE FAILURE[/COLOR]
ddi : mmc_read failed
[COLOR="red"]ODIN MODE[/COLOR]
PRODUCT NAME: SM-N9005
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
[COLOR="Gray"]QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
And then, Odin recognizes the phone.
Now I'm able to get Odin to recognize the phone, but I can't do anything with it. I've tried:
- flashing 4.4.2 N9005XXUGNG1 (Portuguese TPH) again - FAIL (see attachments) Phone outputs two lines, after UDC START:
Code:
[COLOR="Gray"](...)
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
MMC: mmc_read fail
[COLOR="Red"]ODIN : flash read failure[/COLOR]
- flashing N9005XXUGBOB6 (Poland XEO) again - FAIL
- flashing PIT files (tried 3 different ones) - FAIL Phone outputs another line, after UDC START:
Code:
[COLOR="Gray"](...)
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
MMC: mmc_read fail
I wasn't able to get any unbrick.img from a N9005 Lollipop yet. Is this the final solution for my problem? Since I'm able to get to odin mode, shouldn't this unbrick be enough? What does it mean "mmc_read fail"?? Any help?!?! I don't know what else to do...
Thanks!!
Click to expand...
Click to collapse
I think you are actually doing everything correct, the reason is probably due to a corrupted MMC chip unfortunately.
That also explains why it failed during your first firmware update.
hallydamaster said:
I think you are actually doing everything correct, the reason is probably due to a corrupted MMC chip unfortunately.
That also explains why it failed during your first firmware update.
Click to expand...
Click to collapse
:/
No solution then?...
how should I solve this problem then? new motherboard? new MMC chip? ...
Assuming the chip is gone, is there anything else I can try before going to hardware repair?
Thanks for your response...
Is there any developer that can help me?
I'm also willing on trying to use a 5.0 PIT file or a 5.0 unbrick.img if someone can manage to get me one...
Skactus said:
:/
No solution then?...
how should I solve this problem then? new motherboard? new MMC chip? ...
Assuming the chip is gone, is there anything else I can try before going to hardware repair?
Thanks for your response...
Is there any developer that can help me?
I'm also willing on trying to use a 5.0 PIT file or a 5.0 unbrick.img if someone can manage to get me one...
Click to expand...
Click to collapse
AFAIK Lollipop ROMs boot on KK bootloaders, so that shouldn't be the problem.
Have you tried just to do a factory reset and see if anything happens?
If it doesn't work, what about installing a custom recovery from DL mode?
If that works try flashing a small AOSP rom.
EDIT:
Yes, if the MMC is corrupted, a new motherboard will be needed, unless ofcourse it's possible to do any HW repairs.
hallydamaster said:
AFAIK Lollipop ROMs boot on KK bootloaders, so that shouldn't be the problem.
Have you tried just to do a factory reset and see if anything happens?
If it doesn't work, what about installing a custom recovery from DL mode?
If that works try flashing a small AOSP rom.
EDIT:
Yes, if the MMC is corrupted, a new motherboard will be needed, unless ofcourse it's possible to do any HW repairs.
Click to expand...
Click to collapse
Can't get to recovery, so no factory reset for me...
I was wondering about installing a custom rom recovery from odin on last resort... I'm still hopeful for the miracle of unbrick.img from a 5.0 to work. Than I'll call my Note 3 by "Fenix 3" instead...
Skactus said:
Can't get to recovery, so no factory reset for me...
I was wondering about installing a custom rom recovery from odin on last resort... I'm still hopeful for the miracle of unbrick.img from a 5.0 to work. Than I'll call my Note 3 by "Fenix 3" instead...
Click to expand...
Click to collapse
There is no stock recovery when you try enter?
If I were you, I would try to install TWRP recovery through Odin, then install a custom AOSP ROM.
If that works you can try test the MMC with software.
hallydamaster said:
There is no stock recovery when you try enter?
If I were you, I would try to install TWRP recovery through Odin, then install a custom AOSP ROM.
If that works you can try test the MMC with software.
Click to expand...
Click to collapse
I can only get the phone to get alive using SD card with unbrick.img on it (see post #1). Then I can get access only to ODIN mode.
Tried to flash TWRP recovery through Odin right now: FAIL.
Odin 3.09:
Code:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone outputs two lines, after UDC START:
Code:
[COLOR="Gray"](...)
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
MMC: mmc_read fail
[COLOR="Red"]ODIN : flash read failure[/COLOR]
... it's a no go then...
Skactus said:
I can only get the phone to get alive using SD card with unbrick.img on it (see post #1). Then I can get access only to ODIN mode.
Tried to flash TWRP recovery through Odin right now: FAIL.
Odin 3.09:
Code:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone outputs two lines, after UDC START:
Code:
[COLOR="Gray"](...)
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
MMC: mmc_read fail
[COLOR="Red"]ODIN : flash read failure[/COLOR]
... it's a no go then...
Click to expand...
Click to collapse
I see, sorry about your phone. Does indeed seem like you have a dead MMC chip.
:/ thanks for your kind help anyway...
Should I expect someone else to confirm this, get a 5.0 PIT, maybe a 5.0 unbrick.img for the microSD card trick, or are you 100% sure of that and I should stop pursuing the utopia of getting my phone unbricked?
Sent from my RIDGE 4G using Tapatalk
Skactus said:
:/ thanks for your kind help anyway...
Should I expect someone else to confirm this, get a 5.0 PIT, maybe a 5.0 unbrick.img for the microSD card trick, or are you 100% sure of that and I should stop pursuing the utopia of getting my phone unbricked?
Sent from my RIDGE 4G using Tapatalk
Click to expand...
Click to collapse
I would probably not give up either, you can say there is no harm in trying what there is to try.
Using a debrick.img from a 5.0 Android should not make a difference, but if you can find one, why not give it a try?
I have found 2 pit files you might try, AFAIK they are both recent:
http://www.4shared.com/get/lrO_9qAoce/CSB_signed_HLTE_EUR_OPEN_32G_0.html
https://hostr.co/ndxkZa6KqRTF
You can also try use the "Nand erase all" feature in Odin 3.09, but I think I've read somewhere that it requires you to have a backup of your EFS to restore properly.
hallydamaster said:
I would probably not give up either, you can say there is no harm in trying what there is to try.
Using a debrick.img from a 5.0 Android should not make a difference, but if you can find one, why not give it a try?
I have found 2 pit files you might try, AFAIK they are both recent:
http://www.4shared.com/get/lrO_9qAoce/CSB_signed_HLTE_EUR_OPEN_32G_0.html
https://hostr.co/ndxkZa6KqRTF
You can also try use the "Nand erase all" feature in Odin 3.09, but I think I've read somewhere that it requires you to have a backup of your EFS to restore properly.
Click to expand...
Click to collapse
I belive I've already tried the first one. I'm downloading them right now. ´
Can you explain further on about "Nand erase all" feature? I don't really know nothing about it, but I confess I'm a scared to use it.
EDIT: Both failed. "Re-Partition operation failed."
Skactus said:
I belive I've already tried the first one. I'm downloading them right now. ´
Can you explain further on about "Nand erase all" feature? I don't really know nothing about it, but I confess I'm a scared to use it.
EDIT: Both failed. "Re-Partition operation failed."
Click to expand...
Click to collapse
Appareantly the "Nand erase alle" setting formats the MMC, but that means you have to have a backup of EFS, else you cannot restore your IMEI... Thats what I think it was about. Sorry, about the pits, that was all I got.
Yet I can't thank you enough, since you're the only one how even tried to assist me with my problem so far!
I have another question yet... is it too late to create a EFS backup?
I've speed read some threads about Nand erase and that could eventually solve my problem.
Skactus said:
I have another question yet... is it too late to create a EFS backup?
I've speed read some threads about Nand erase and that could eventually solve my problem.
Click to expand...
Click to collapse
Unfortunately I don't think it's possible to backup the EFS without recovery/working android. So if it's deleted, you will just have another bricked stated, not being able to use it with your provider.
Have you tried just to flash a bootloader through Odin, see if that works? Or does it just quit instantly?
You need to flash with a PIT file and repartition checked. At least that's what I gathered from looking at the issue.
hallydamaster said:
Unfortunately I don't think it's possible to backup the EFS without recovery/working android. So if it's deleted, you will just have another bricked stated, not being able to use it with your provider.
Have you tried just to flash a bootloader through Odin, see if that works? Or does it just quit instantly?
Click to expand...
Click to collapse
I don't tried yet flashing just the bootloader, but i've tried to flash a bootloader among with other files, Odin Failed. Can you sugest which bootloader to flash?
So far I couldn't flash anything without Odin failing...
BTW, adb doesn't find the device either...
toastido said:
You need to flash with a PIT file and repartition checked. At least that's what I gathered from looking at the issue.
Click to expand...
Click to collapse
Thanks for your reply. I've already flashed almost 6 diferent PIT files, with and without AP, nothing worked for me so far. I belive that's because I haven't got any 5.0 PIT file yet. Would you care to share one?
Skactus said:
Thanks for your reply. I've already flashed almost 6 diferent PIT files, with and without AP, nothing worked for me so far. I belive that's because I haven't got any 5.0 PIT file yet. Would you care to share one?
Click to expand...
Click to collapse
Unfortunately I don't have one, and I'm on am n900t, so even if I pulled one it probably wouldn't help. :/ best of luck, and please keep us apprised of any progress and outcomes!
toastido said:
Unfortunately I don't have one, and I'm on am n900t, so even if I pulled one it probably wouldn't help. :/ best of luck, and please keep us apprised of any progress and outcomes!
Click to expand...
Click to collapse
Sure, If I get to solve this I'll also make a tutorial about it (I've find some guys with similar problem [mmc_read fail], but no one got to solve it yet.).
I have the MCC_Read Failed. If I let the phone off for a while, and turn it on, I get to the Downloading Screen with that error... so I found that I need to flash .pit file to get Repartition. But When I try to do it, I get "Secure Check Fail: Pit" and I cant do repartition. What could it be? I can't find any help on internet..
Thanks!
takato23 said:
I have the MCC_Read Failed. If I let the phone off for a while, and turn it on, I get to the Downloading Screen with that error... so I found that I need to flash .pit file to get Repartition. But When I try to do it, I get "Secure Check Fail: Pit" and I cant do repartition. What could it be? I can't find any help on internet..
Thanks!
Click to expand...
Click to collapse
I have same mmc_read failed problem.
I found Note 4 pit files on http://forum.xda-developers.com/not...te-4-pit-files-repartiton-f-g-c-t-w8-t3282641
when I tried to flash it (repartition checked) with stock ROM (tried ANK4, COG2 & DOK2 .. none worked)
I got Secure check fail : pit
Please help!
Did either of you run auto root before this issue?
Nothing can be done against this mnc failure however try to flash E3(lollipop) repair firmware it will make u boot
Sent from my SM-N920G using XDA-Developers mobile app
Hello,
i got a device to repair. I am not so familiar with samsung devices so i would apreciate some advice/help.
I dont know how to flash correctly the n9005 firmware.
I cant go to recovery and when try to boot there is shown on the screen "kernel is not seandroid enforcing, set warranty bit : kernel" and the device is rebooting to this text over and over.
It Is N9005 (is written under the battery).
But when i go to download mode it is listed this:
Code:
Odin Mode
product name: SM-N900P
Current Binary: Samsung Official
System Status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
Qulcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A3, P1
Write Protection: Enable
I assume the owner accidentally flashed an n900P firmware to his n9005 device.
I tried many ODIN bversions (3.10.7,3.10.6,3.07,1.85) and stock 5.0, 4.4.2, 4.3 firmwares, various n9005 PIT files
when flashing a stock 4.4.2 firmware (only AP file from sammobile)
Code:
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> SingleDownload.
<ID:0/016> sbl1.mbn
<ID:0/016> NAND Write Start!!
<ID:0/016> FAIL! (Auth)
when flashing a stock 5.0 firmware (only AP file from sammobile)
Code:
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL! (Auth)
when flashing a 4.4.? csc file for n9005
Code:
<ID:0/015> Odin engine v(ID:3.1100)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Set PIT file..
<ID:0/015> DO NOT TURN OFF TARGET!!
<ID:0/015> FAIL!
<ID:0/015>
<ID:0/015> Re-Partition operation failed]
closest i got with this:
in ODIN 3.07 when flashing kitkat csc file i got
Code:
<ID:0/015> Firmware update start..
<ID:0/015> cache.img.ext4
<ID:0/015> NAND Write Start!!
<ID:0/015> hidden.img.ext4
<ID:0/015> FAIL
and on the device was shown:
Code:
secure check fail : PIT
Set warranty bit : cache
Unsupport dev_type
nobody?
I make a step further.
Now i can flash system (AP) or i can flash twrp recovery or root trough ODIN, but i cant flash the whole stock, because it will fail everytime on sbl1.img, aboot or hidden.image.ext4
So now i can boot the system, but with N900P modem, kernel and othe rpartitions, so wifi dont work ect.
Now it would be superb to have a zip file with stock modem,sbl,aboot,non-hlos to flash it trough TWRP.
please any advice?
Sorry for my English!!
Download your region firmware from sammobile and pit file for your device n9005 note 3 open europ from xda.
Open odin select pit then the rom on itch specific place flash everything...
Let me know if you've got a positive result.
Sent from my SM-N910F using XDA-Developers mobile app
tried this dozen times. It gives me error when Odin tries to write the sbl1 or aboot or modem partition (as i wrote in OP). It gives error because the pit file doesn't match.
Is it possible the phone's motherboard was swapped for a 900p?
don't know... maybe. so you suggest to imstall stock N900P firmware?
https://mega.nz/#!kQtGnCYZ!7jko1XT7fPc9mIGHE8JLZhOvaeGH6qQbaW7Y6RYBQjU
This is a pit file for n9005 Europe
I advice you to reflash the rom of your original specific model with the pit file with wipe partition checked
Let me know wen u did
Sent from my SM-N910F using XDA-Developers mobile app
I will try. I avoided to wipe partitions while users say here on xda that it is a one way ride. ?
Samsung seems to have pretty good security measures in place to prevent flashing incorrect ROMs via Odin.
The failure to flash the 9005 aboot file tells me the bootloader on the rom and the bootloader in the phone do not match.
so how it can be, that i have an n9005 device with n900p Firmware and all partitions?
Does the imei in the phone match the imei on the printed label under the battery?
And why not your device would be a N900P ? Remove battery and see...
Maybe your USB is bad (it happened to me : 4 cables, 3 not working, 1 working hopefully)
Or maybe your downloaded ROM can't been flashed (weird, but it happened also to me), so flash the same model, but other revision (exemple OD3 doesn't work, try with OJ3, in my case)
Good luck !
use kies to install firmware. from kies select tools then "Emergency firmware recovey".
Munawar Mehmood said:
use kies to install firmware. from kies select tools then "Emergency firmware recovey".
Click to expand...
Click to collapse
the kies dont see my device.
cedric3 said:
And why not your device would be a N900P ? Remove battery and see...
Maybe your USB is bad (it happened to me : 4 cables, 3 not working, 1 working hopefully)
Or maybe your downloaded ROM can't been flashed (weird, but it happened also to me), so flash the same model, but other revision (exemple OD3 doesn't work, try with OJ3, in my case)
Good luck !
Click to expand...
Click to collapse
as i wrote under thebbattery is written n9005. usb is good use it to flash other phones. tried to flash about 4 stock roms.
DallasCZ said:
as I wrote, under the battery is written N9005. USB is good : I use it to flash other phones. I tried to flash about 4 stock roms.
Click to expand...
Click to collapse
Install Kies ot SmartSwitch (Kies' replacement)
Go to Emergency
Enter N9005 in device model
Enter the S/N number (written under the battery)
Connect your phone (don't worry if it is not recognized)
Go !
It will download the right update and install it : be patient, don't disconnect the phone or internet...
Good luck
jemis1983 said:
https://mega.nz/#!9BtkxK4A!Gy7muVwEtYBQFtxktDfCFK3VfcMZanfOMdOP9Elrm1U
This is a pit file for n9005 Europe
I advice you to reflash the rom of your original specific model with the pit file with wipe partition checked
Let me know wen u did
Sent from my SM-N910F using XDA-Developers mobile app
Click to expand...
Click to collapse
this is only a bat file to store the pit from the device.There is no pit file inside.
cedric3 said:
Install Kies ot SmartSwitch (Kies' replacement)
Go to Emergency
Enter N9005 in device model
Enter the S/N number (written under the battery)
Connect your phone (don't worry if it is not recognized)
Go !
It will download the right update and install it : be patient, don't disconnect the phone or internet...
Good luck
Click to expand...
Click to collapse
smart switch sys that my device dont support iniciation (after i added the sn number and mobile number.
DallasCZ said:
smart switch sys that my device dont support iniciation (after i added the sn number and mobile number.
Click to expand...
Click to collapse
Ok, and have you found the PIT file for your device ?
cedric3 said:
Ok, and have you found the PIT file for your device ?
Click to expand...
Click to collapse
I have the pit file for N9005 i flashed it using ODIN ..it was all ok
When i try to flash the AP image of stock (that cotains all parts BL,AP,CSC, CP) the flash ends by starting with flashing BL partitions sbl1.img)
When try to flash BL (bootloader) there is error in flashing sbl1.img.
the same goe with CSC and CP images (always show some error in flashing aboot.img and other partitions and ODIN stops.
I can flash AP (the AP that is only the system,recovery,boot) it goes well, the device starts but has some errors (because of missing parts in CSC and CP?.). wifi dont work i see full signal but there is no simcard inserted
Now i can boot the device the imei that is shown in the android systme is other than the imei on the back (under the battery).
I think someone tried to flash a N900P firmware over the N9005.
Now i cant flash the rest of the partitions.
Hi,
my galaxy note have a problem.. it's doesn't boot correcly.
It says :
Odin mode (high speed)
product name: SM-N910F
current binary : Samsung official
system status : official
reactivation lock : off
knox warranty void : 0x0
qualcomm secureboot : enabled (csb)
app swrev: S1, T1, R1, A1, P1
secure download: enabled
VDC start
what can I do.. i tried with kies, and at 2% I have an error...
I tried with odin (flash last rom MM), nothing it doesn't work..
Maybe I have to flash the original rom (it's a GN4 branded by SFR) ?
Thanks a lot,
Cat
Catherine80 said:
Hi,
my galaxy note have a problem.. it's doesn't boot correcly.
It says :
Odin mode (high speed)
product name: SM-N910F
current binary : Samsung official
system status : official
reactivation lock : off
knox warranty void : 0x0
qualcomm secureboot : enabled (csb)
app swrev: S1, T1, R1, A1, P1
secure download: enabled
VDC start
what can I do.. i tried with kies, and at 2% I have an error...
I tried with odin (flash last rom MM), nothing it doesn't work..
Maybe I have to flash the original rom (it's a GN4 branded by SFR) ?
Thanks a lot,
Cat
Click to expand...
Click to collapse
Download this firmware link below. this is full repair firmware. After download extract file and flash in odin version 3.10 after flash go to recovery do wipe cache and factory reset otherwise you will face bootloops .this is 5.0.1 lollipop firmware but you can update to marshmallow later via ota update. And do let me know if it work for you
https://www.androidfilehost.com/?fid=24407100847294341
Trex888 said:
Download this firmware link below. this is full repair firmware. After download extract file and flash in odin version 3.10 after flash go to recovery do wipe cache and factory reset otherwise you will face bootloops .this is 5.0.1 lollipop firmware but you can update to marshmallow later via ota update. And do let me know if it work for you
https://www.androidfilehost.com/?fid=24407100847294341
Click to expand...
Click to collapse
Thanks
Meanwhile I have installed TWRP recovery via odin, and it worked (for the first time... i've tried before but no way...). The download of the firmware was not completed so I left the phone on in twrp mode... bad idea ! The battery was low... and now, I can't turn it on and I can't understand if it's charging or not.
So sad
Cat
Catherine80 said:
Thanks
Meanwhile I have installed TWRP recovery via odin, and it worked (for the first time... i've tried before but no way...). The download of the firmware was not completed so I left the phone on in twrp mode... bad idea ! The battery was low... and now, I can't turn it on and I can't understand if it's charging or not.
So sad
Cat
Click to expand...
Click to collapse
Charge your battery via other note 4 or desktop charger for few minutes and try again
Trex888 said:
Charge your battery via other note 4 or desktop charger for few minutes and try again
Click to expand...
Click to collapse
Unfortunately I don't have another GN4 nor a desktop charger (but maybe l'll buy it tomorrow...). So, wait and see...
By the way, thank you so much for your help I'll tell you tomorrow if it works or not
Cat
Hi Trex888,
here I am... but unfortunately it doesn't work:
Odin says :
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I put every file in the good case (AP in AP etc..) and even Pit file in pit case... On option tab i've selected re-partition and F-reset time.
On my phone I can see that :
UDC start
Odin: flash read failure
Error: there is no pit binary.
It's not good for me ?
Thanks
Cat
Another thing... it's not important but i've bought this phone on ebay. Today i've tried to check the imei of my GN4 (SM-N910F) and this is what i can see on imei.info :
G900P Galaxy S5 (Sprint) (SM-N910F)
it's strange... why it says G900P ? I know the differences between GN4 and S5... it's a GN4 for sure
Thanks,
Cat
I got this S7, wanted to flash 930U firmware to use T-Mobile but a failed flash has me in a boot loop. I fully updated before trying to flash, so it is I assume on the newest bootloader, etc.
I have attempted the newest firmware files that I can find (G930AUCS4BQL1) but am still getting the SW REV CHECK FAIL through Odin.
Are there files available that will fix this, do I just need to wait for them to come out, or have I bricked this thing?
Thanks for any help and have a great day!
Update:
- Using PrinceComsy Odin results in: FAIL! (Auth)
- USB Debugging is OFF and I am unable to boot to change that
- I am leaving the BL file blank in ODIN
perhaps you should try using offcial odin when flashing official images.
try version 3.12.3. whatever you do, don't use the princecomsy version unless for flashing engboot