i have a Galaxy 10.1v ( P7100) that won't start.
it only start up to booting recovery kernel image, it showns the android logo with a box but then it goes in the exclamation mark and the android logo...
Started like this i can find it in device manager but i cannot install any drivers for MTP usb device and for P7100 =, so i cannot use odin..
I have tried to rewrite the bootloaders and reflash it in nvflash (adx mode) and i did managed to put it in download mode, odin see it but when i try to send a new firmware to it it get stuck at setupconnection.
Does anybody have any advices?
nobody knows nothing about it?
vcosmin said:
i have a Galaxy 10.1v ( P7100) that won't start.
it only start up to booting recovery kernel image, it showns the android logo with a box but then it goes in the exclamation mark and the android logo...
Started like this i can find it in device manager but i cannot install any drivers for MTP usb device and for P7100 =, so i cannot use odin..
I have tried to rewrite the bootloaders and reflash it in nvflash (adx mode) and i did managed to put it in download mode, odin see it but when i try to send a new firmware to it it get stuck at setupconnection.
Does anybody have any advices?
Click to expand...
Click to collapse
Saw the getting stuck at "setupconnection" a while back with a IO tab and it was due to the version of Odin being used...which version are you on?
SO, in nvflash i did:
C:\NVFlash>nvflash --bl bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x027c1049423f2157
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 1473840/1473840 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
C:\NVFlash>nvflash --resume --download 8 stockIOrecovery.img
Nvflash started
[resume mode]
sending file: stockIOrecovery.img
/ 5242880/5242880 bytes sent
stockIOrecovery.img sent successfully
C:\NVFlash>
Is the only procedure that's is taking me to upload mode.
on the tablet's creen i have:
Entering nvflash recovery mode / nv3p server
============================
Entering upload mode...
Upload_cause: undervined
============================
I am using Odin 3 v1.85.
I am trying to write P7100 VDF P7100BUKC8
The status is :
<ID:0/027> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_SIGNED_HRI83_BUKDF.tar.md5 is valid.
<OSM> MODEM_HRI83_BUKDF_REV_03.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/027> Odin v.3 engine (ID:27)..
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
vcosmin said:
SO, in nvflash i did:
C:\NVFlash>nvflash --bl bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x027c1049423f2157
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 1473840/1473840 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
C:\NVFlash>nvflash --resume --download 8 stockIOrecovery.img
Nvflash started
[resume mode]
sending file: stockIOrecovery.img
/ 5242880/5242880 bytes sent
stockIOrecovery.img sent successfully
C:\NVFlash>
Is the only procedure that's is taking me to upload mode.
on the tablet's creen i have:
Entering nvflash recovery mode / nv3p server
============================
Entering upload mode...
Upload_cause: undervined
============================
I am using Odin 3 v1.85.
I am trying to write P7100 VDF P7100BUKC8
The status is :
<ID:0/027> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_SIGNED_HRI83_BUKDF.tar.md5 is valid.
<OSM> MODEM_HRI83_BUKDF_REV_03.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/027> Odin v.3 engine (ID:27)..
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
Click to expand...
Click to collapse
Looks like you've uploaded recovery ok and I assume you have used the correct partition (n°8) tho as I don't have info on P7100 let's hope that is correct.
Upload mode (Entering upload mode...Upload_cause: undefined) is entered by a very long press on the power button....this WON'T get you to odin DOWNLOAD mode...
Do you know the button combinations for the tab? I think you are confused with the modes. To get to download (for odin)
1) Power off your Tab and power it back on, while holding down both the VOLUME DOWN and POWER buttons.
2) When the DOWNLOAD / FASTBOOT icons appear, press just the button VOLUME DOWN to select DOWNLOAD icon - it will be flashing (the one with the "Android and the roadworks sign")
then press VOLUME UP to confirm selection.
It might give a warning, just press the appropriate volume up or down to continue, then try again with odin
starting with volume down and then power it's sending it to booting recovery kernel and it's ending with an exclamation mark not with the options to go to recovery or download
Never thought to ask before but how did you get into this state in the first place? Faulty flash of something?
You seem to be describing the loss/corruption of the boot image here (hopefully just that and not BCT as well)
As you have succeeded in using nvflash I think you should try using it to send a boot image to the tab then try the steps you have previously tried to get into download mode as I described.
You have a boot image that works as you have used it to run nvflash...make a copy somewhere(another directory) of the "bootloader.bin" from your nvflash directory...rename it "boot.img" put it back into nvflash directory and use the commands in nvflash that you used before to send recovery to the tab but send to partition 4 for the boot partition...
If you prefer I have attached a rar of the original 10.1 IO tab boot image below, just unrar it and push it to partition 4 using nvflash
Let us know how you get on
actually i don't know how it happened because i recieved in this state from a friend
vcosmin said:
actually i don't know how it happened because i recieved in this state from a friend
Click to expand...
Click to collapse
hope you didn't pay too much if that is the case...
i did not pay a thing. But the display is brand new )
i will let it charge for a bit and try to write down the boot image
Have you tried it yet?
Sent from my GT-P7510 using xda premium
i did but now i can't even write the bootloader. after it is done writing the bootloader to the tablet, when it needs to reinitalise it it is getting an errot x0x writting on the usb device, it restarts the tablet and it apears in the device manager as an unknown device...
I think that a new motherboard is the best solution for it.
Think you might be right
Sent from my GT-P7510 using xda premium
hi,
hi, i have one p7100, write ok with odin 3 firmwares but stuck in logo.
hi everyone i have a p7100 i flased the modem and now its stuck on startup logo how do i get past this , i tried to wipe cache etc but still same thing
Related
Good evening,
for unknown reasons my phone (Unbranded Samsung Galaxy S4) started to show weird signs of system failures. It kept restarting and hanging on the boot screen; often rapidly changed the battery percentages and then crashed. A day after these weird errors appeared the phone suddenly refused to boot at all. The boot process stopped at the Samsung logo and completely froze.
So I tried booting into recovery... But it didnt work? Sometimes it simply rebooted after showing "Recovery booting..." in the top left side of the screen and sometimes it displayed an red error showing "No command". On the 15th try or so it suddenly showed a kernel error instead:
"SET WARRENTY BIT: KERNEL"
Instead of using recovery mode I instead booted into Odin mode, where to my surprise I found that the current binary was no longer the official Samsung one, but a custom one. I decided on downloading stock firmware from the Samsung database and flashing it with Odin v3.11.
Name of the used firmware pack: " I9505XXUHOJ2 [5.0.1]"
I put it into Odin mode and then applied the firmware md5 file under AP in Odin 3.11 and it started working. Flashing the image was successful until half through the system.img.ext4 part where after half of the operation it suddenly failed and disconnected. Recovery.img and so on, however, was flashed successfully. I rebooted it into Odin mode, where the binary was now "Samsung Official" and retried the procedure.
This time it failed instantly. Shortly after starting the operation Odin said it could not open the specified file and the operation was aborted. The phone is now stuck in a "Firmware Update Failed - Use Kies Recovery" bootloop that remains even when I turn the phone off. (It simply turns back on again)
Is the phone screwed now? Re-Partioning was unchecked so I don't know if the partition table was ruined or not.
Does anyone have an idea?
Info shown after operation in Odin mode:
PRODUCT NAME: GT-I9505
CURRENT BINARY: SAMSUNG OFFICIAL [CUSTOM before operation]
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0x0
KNOX WARRENTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: ENABLED
eMMC BURST MODE: ENABLED
I can't even turn off the phone now :victory:
No customization has occured on this phone. I have never used any custom roms or custom kernels. It simply started doing weird stuff on its own.
maybe hardware faulty? NAND corrupt?
Perhaps try flashing TWRP until it's successful, and then use it to flash the framework file(s) you've placed on the SD (use another phone for this end, or an mSDcard adapter that comes with the SD (most laptops have a slot for this). This does away with many underlying assumptions, like the soundness of the cable, port, laptop/pc, and flashing software.
First just charge the battery until it's full.
KNOX WARRENTY VOID: 0x1
Click to expand...
Click to collapse
Seems like a potential security threat. Are you sure you haven't rooted your phone somehow?
Btw, if the partition is indeed ruined, use TWRP to make a backup of the phone (even if there's nothing to backup). It'll restore the partition table. Then proceed to flash the framework from the SD via TWRP.
ThePrick said:
Perhaps try flashing TWRP until it's successful, and then use it to flash the framework file(s) you've placed on the SD (use another phone for this end, or an mSDcard adapter that comes with the SD (most laptops have a slot for this). This does away with many underlying assumptions, like the soundness of the cable, port, laptop/pc, and flashing software.
First just charge the battery until it's full.
Seems like a potential security threat. Are you sure you haven't rooted your phone somehow?
Btw, if the partition is indeed ruined, use TWRP to make a backup of the phone (even if there's nothing to backup). It'll restore the partition table. Then proceed to flash the framework from the SD via TWRP.
Click to expand...
Click to collapse
Before I read your post I tried flashing a 4.X software for GT-I9505, which was successful with ODIN.
Recovery still wont work, as it crashes the phone instantly. Booting normally got to the Samsung logo part and then froze.
Sometimes the phone shows very weird graphical glitches. It boots up with a green dotted screen and slowly turns brightness up to max. I think this might mean its hardware faulty.
Concerning the KNOX issue: The phone was never rooted nor modified. I have no idea how the system picked up a rooting process when there was none.
I'll try flashing TWRP... Atleast download mode still works even though everything else doesnt.
Thanks for your reply
EDIT: Flashed TWRP successfully but S4 is refusing to boot into recovery
following error is dísplayed:
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRENTY BIT: RECOVERY
Noroxuz said:
Before I read your post I tried flashing a 4.X software for GT-I9505, which was successful with ODIN.
Recovery still wont work, as it crashes the phone instantly. Booting normally got to the Samsung logo part and then froze.
Sometimes the phone shows very weird graphical glitches. It boots up with a green dotted screen and slowly turns brightness up to max. I think this might mean its hardware faulty.
Concerning the KNOX issue: The phone was never rooted nor modified. I have no idea how the system picked up a rooting process when there was none.
I'll try flashing TWRP... Atleast download mode still works even though everything else doesnt.
Thanks for your reply
Click to expand...
Click to collapse
I LITERALLY had the EXACT same problem.
See the thread here for some ideas: http://forum.xda-developers.com/gal...oft-bricked-s4-gt-i9505-t3430921/post68024954
I didn't mention the green screen and glitching because I didn't see it as relevant.
Just happenstance that it worked eventually.
I flashed the framework and it was successfully, but the system still didn't boot. I tried flashing the framework after a couple of days of persistent failure as a last ditch effort, and it worked, surprisingly, and I cannot explain it fully. I had planned to put the framework on an SD card and use TWRP i.e. recovery to flash it. That's still the best method imo. Try flashing TWRP and doing just that! It should work if there isn't any hardware damage. By the way, I tried older versions of Odin (3.07) when the newer versions didn't work. Additionally, perhaps flashing more recent ROMs would be a better idea (5.0.1, 5.1.1 (if Samsung has bothered updating it to that point)).
Once TWRP ((((or CWM )))) is flashed successfully, boot into recovery mode and do a backup. This should automatically restore the partition table. Then flash the framework file/tar and reboot. If it doesn't work, try flashing different firmware versions (5.0.1, 5.1.1) using the older versions of Odin, say, if TWRP was flashed successfully but the phone still won't boot into recovery.
Alternately, maybe the battery is dying, but I doubt it. Be ABSOLUTELY sure the power button is in perfect condition. The Galaxy S3, S4, Note 4, have a terrible history with defective power buttons causing all sorts of problems.
ThePrick said:
if TWRP was flashed successfully but the phone still won't boot into recovery.
Click to expand...
Click to collapse
Yeah... I flashed TWRP but got the
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRENTY BIT: RECOVERY
stuff instead. Last time I tried flashing a 5.X rom ODIN failed halfwax through so
Then I flashed stock ROM again and it got to the Samsung logo with the jingle but it goddamn crashed again.
Booted into recovery (which suddenly worked) and deleted user data/ cache.
Now it doesnt do anything anymore lol?
Probably broken GPU or NAND corrupting itself every 2 sec.
I dunno.
Samsung should really fix their stuff.
HELP ME IM NOT ABLE TO FLASH STOCK ROM ON GT I9505 <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CP_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_OXA_I9505OXAHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
abdulkareemsid said:
HELP ME IM NOT ABLE TO FLASH STOCK ROM ON GT I9505 <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CP_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_OXA_I9505OXAHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Click to expand...
Click to collapse
Try a different USB port and/or cable.
Odin failures can happen when using incompatible USB cables and ports so try everything available.
My phone was acting slow 2 days ago and then locked up on the Samsung logo . This is the third time this year it has happened. The previous two times I flashed the same firmware and good to go. This time it failed and I received the message "Samsung firmware upgrade encountered an issue" error with associated images. If I boot into recovery mode I am confronted with the same message. However, I can boot into download mode.
The phone is a US Cellular Galaxy S4 SCH-R970. It is rooted and running a stock 4.2.2 firmware.
Things I have tried.
1) Flashing the identical firmware with Odin.
2) Tried several original cables, several USB ports on my computer, different versions of Odin and even KIES.
3) Flashing 4.4.2 that I had used successfully on another identical device.
When I flash 4.4.2 with ODIN everything works until the write process and then it fails. Here is what is displayed by ODIN. I tried 4.2.2 again but it gives me a SW Check Fail because I had tried to flash a newer firmware.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> R970TYUFNK1_R970USCFNK1_R970TYUFNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The following is displayed on the screen above the error message.
PRODUCT NAME: SCH-R970
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL : 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0X30
Write Protection: Enable
eMMC BURST MODE: enabled
START [224,1440]
Click to expand...
Click to collapse
This brings me to a 2 part question.
1) Is this a hardware issue like the motherboard failing?
2) Is there a way to revive the phone and stop this cycle of soft bricks?
apel69 said:
My phone was acting slow 2 days ago and then locked up on the Samsung logo . This is the third time this year it has happened. The previous two times I flashed the same firmware and good to go. This time it failed and I received the message "Samsung firmware upgrade encountered an issue" error with associated images. If I boot into recovery mode I am confronted with the same message. However, I can boot into download mode.
The phone is a US Cellular Galaxy S4 SCH-R970. It is rooted and running a stock 4.2.2 firmware.
Things I have tried.
1) Flashing the identical firmware with Odin.
2) Tried several original cables, several USB ports on my computer, different versions of Odin and even KIES.
3) Flashing 4.4.2 that I had used successfully on another identical device.
When I flash 4.4.2 with ODIN everything works until the write process and then it fails. Here is what is displayed by ODIN. I tried 4.2.2 again but it gives me a SW Check Fail because I had tried to flash a newer firmware.
The following is displayed on the screen above the error message.
This brings me to a 2 part question.
1) Is this a hardware issue like the motherboard failing?
2) Is there a way to revive the phone and stop this cycle of soft bricks?
Click to expand...
Click to collapse
Hi @apel69 ,
Have you tried installing a custom recovery and a custom rom?
I already had cwm installed and I can't boot to it. I had thought about reflashing it but wasn't sure there would be anything to recover since the newer firmware update had started and failed.
You mean the phone started a stock firmware upgrade from 4.2.2?
No update. I was flashing the existing version because it soft bricked.
Bought a new cable and successfully installed 4.4.2. All three original cables were bad including the one reserved for flashing. Grr!!
Hi,
I am unable to bring my Samsung Galaxy Tab 4 (SM-T231) in "Download mode". With ADB i was able to bring it in "Manual Mode" but not in "Download mode". I have downloaded the latest Samsung USB drivers, installed different versions of ODIN but ODIN doesn't seem to recognize my mobile (ID:COM not hightligthed), though my Windows 10 system is able to do so.
I came across someone's post here who mentioned Samsung 300k that can put my mobile into "Download mode". But it doesn't seem to work with Windows 10 and it's zip gives a CRC error.
I get the following screen on my mobile:
HTML:
Android System Recovery <3e>
KOT49H T231XXU8A0I2
Volume up/down to move highlight:
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
<Android logo with Red triangle having exclamation mark!>
No command.
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : XSG
Successfully applied multi-CSC.
Then in ODIN i get the following when i click AP and select Recovery.img.md5 file:
HTML:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
If i click Start, then this line shows up:
HTML:
<OSM> All threads completed. (succeed 0 / failed 0)
Any help would be most appreciated asap.
You got into the wrong mode bro.
That's why your phone shows "Android system recovery"
You are trying to enter "download mode" right?
On my tab 4 7" LTE you enter download mode by these steps:
1)Shutdown your phone
2)Hold PWR+VOLDOWN+HOME at the same time
3)Stop pressing power button but continue to hold VOLDOWN+HOME once Samsung logo appears
4)The screen will show a big triangle warning icon saying that "installing a custom OS will harm your device blablabla"
5)Now press VOLUP button to enter download mode
(Blue box in Odin should appear)
You're ready to flash stuff in ODIN now.
Please help.
my s7 edge (G935A) suddenly stops working and showing this message.
custom binary blocked by secure boot (recovery. fmg)
system software not authorized by AT&T has been found on your phone. please turn off your phone and go to nearest AT&T store for help.
at ODIN downloading mode the following details are showing
ODIN mode (high speed)
product name ; sm-G935A
current binary ; custom
system status ; official
FRP lock : on
warranty void; 0*0
Qualcomm secureboot ; enable
RP swrew; B10( 2,1,1,1,1) K10 S10
Secure download ; enable
sw rev check fail; aboot fued 10> binary 4
at ODIN following status showing
<OSM> ; checking MD5 finished successfully...
; leave CS
; enter cs for md5
; check md5.. do not unpluge cable..
; please wait..
; checking md5 finished successfully..
; leave cs
<ID;0/003> odin engine v ( ID: 3,1301)..
file analysis
total binary size 4819M
setup connection..
initialization..
set PIT file..
Do not turn off target..
get pit for mapping..
firmware update start..
NAND write start..
single download..
emmc_eppsboot.wbn
Fail ( Auth)
complete ( write) failed
xcess2adil said:
Please help.
my s7 edge (G935A) suddenly stops working and showing this message.
custom binary blocked by secure boot (recovery. fmg)
system software not authorized by AT&T has been found on your phone. please turn off your phone and go to nearest AT&T store for help.
at ODIN downloading mode the following details are showing
ODIN mode (high speed)
product name ; sm-G935A
current binary ; custom
system status ; official
FRP lock : on
warranty void; 0*0
Qualcomm secureboot ; enable
RP swrew; B10( 2,1,1,1,1) K10 S10
Secure download ; enable
sw rev check fail; aboot fued 10> binary 4
at ODIN following status showing
<OSM> ; checking MD5 finished successfully...
; leave CS
; enter cs for md5
; check md5.. do not unpluge cable..
; please wait..
; checking md5 finished successfully..
; leave cs
<ID;0/003> odin engine v ( ID: 3,1301)..
file analysis
total binary size 4819M
setup connection..
initialization..
set PIT file..
Do not turn off target..
get pit for mapping..
firmware update start..
NAND write start..
single download..
emmc_eppsboot.wbn
Fail ( Auth)
complete ( write) failed
Click to expand...
Click to collapse
Did yoy try to flash ATT firmware?
UsmaniMustafa said:
Did yoy try to flash ATT firmware?
Click to expand...
Click to collapse
initially when the phone stopped working we took it to nearby mobile repair shop. he said this is software issue and i will intall its software. he tried software installation and failed to install. then he said i will change its motherboard if you want. i refused and took it back to home. than i tried to install firmware by using odin by myself and the results i have posted in my subject problem. after posting this issue in xda forum i waited for 4,5 days for someones reply. yesterday i took it back to some other mobile repair shop. some how this new technician was able to intall its software and phone starts. but a new problem shown. it keeps on restarting again and again. he removed battery, reboot, facory reset every thing tried. now he is saying its hardware issue. he want to replace its power IC.
im not sure what i should do. will replacing IC solve problem ?
my s7 edge (G935A) suddenly stops working and showing this message.
custom binary blocked by secure boot (recovery. fmg)
system software not authorized by AT&T has been found on your phone. please turn off your phone and go to nearest AT&T store for help.
at ODIN downloading mode the following details are showing
ODIN mode (high speed)
product name ; sm-G935A
current binary ; custom
system status ; official
FRP lock : on
warranty void; 0*0
Qualcomm secureboot ; enable
RP swrew; B10( 2,1,1,1,1) K10 S10
Secure download ; enable
sw rev check fail; aboot fued 10> binary 4
at ODIN following status showing
<OSM> ; checking MD5 finished successfully...
; leave CS
; enter cs for md5
; check md5.. do not unpluge cable..
; please wait..
; checking md5 finished successfully..
; leave cs
<ID;0/003> odin engine v ( ID: 3,1301)..
file analysis
total binary size 4819M
setup connection..
initialization..
set PIT file..
Do not turn off target..
get pit for mapping..
firmware update start..
NAND write start..
single download..
emmc_eppsboot.wbn
Fail ( Auth)
complete ( write) failed
FRP lock : on
xcess2adil said:
my s7 edge (G935A) suddenly stops working and showing this message.
custom binary blocked by secure boot (recovery. fmg)
system software not authorized by AT&T has been found on your phone. please turn off your phone and go to nearest AT&T store for help.
at ODIN downloading mode the following details are showing
ODIN mode (high speed)
product name ; sm-G935A
current binary ; custom
system status ; official
FRP lock : on
warranty void; 0*0
Qualcomm secureboot ; enable
RP swrew; B10( 2,1,1,1,1) K10 S10
Secure download ; enable
sw rev check fail; aboot fued 10> binary 4
at ODIN following status showing
<OSM> ; checking MD5 finished successfully...
; leave CS
; enter cs for md5
; check md5.. do not unpluge cable..
; please wait..
; checking md5 finished successfully..
; leave cs
<ID;0/003> odin engine v ( ID: 3,1301)..
file analysis
total binary size 4819M
setup connection..
initialization..
set PIT file..
Do not turn off target..
get pit for mapping..
firmware update start..
NAND write start..
single download..
emmc_eppsboot.wbn
Fail ( Auth)
complete ( write) failed
Click to expand...
Click to collapse
you need to turn off frp lock