SM-N910A Baseband unknown/Bootloop after *#9090# - GSM-Forum

md.kishor23 · 08-27-2015, 10:34

SM-N910A Baseband unknown/Bootloop after pressing *#9090# . Set was received for unlock, 5.0.1 android version was there and as it was not detecting usb for unlock I pressed *#9090# and selected HS-USB then it rebooted. After reboot it boot looped so I checked baseband and BANG there was no Baseband. Then I tried like flashing and wiping Data/Cache from support but still baseband unknown.
I flashed with both files:
Firstly, N910AUCU1BNK3_N910AATT1BNK3_ATT_Android_4.4.4.rar nothing was wrong till here
But after flashing with N910AUCU1ANIE_N910AATT1ANIE.oct efs was too corrupt. E:failed to mount /efs (Invalid Argument) while putting in reovery.

Now the problem is I found solution for unknown baseband http://forum.gsmhosting.com/vbb/f684...-step-1961415/ but I was unable to enter *#0808# and while looking for problem I found that there was no efs I mean while putting on recovery it says "E:failed to mount /efs (Invalid Argument)"

How to revive this set now? I found that many users have same problem, but how to solve this??

Octopus box · 08-27-2015, 11:10

Hello.

Please, install the latest Software version and re-flash the phone with firmware from the Support Area, then perform "Repair EFS" operation.

md.kishor23 · 08-27-2015, 11:29

well I forgot to check repair efs, diag is now activated thanks

md.kishor23 · 08-28-2015, 08:28

Well I managed to repair baseband, now I have a different problem. I can't write Cert file on this phone.

This is error when I tried with c3303k cable.

This is error when I tried with usb cable.

P.S I have tried flashing with both files available on support and also tried wiping cache/data. And I already tried with latest oct version 2.0.4 , Actually someone has successed writing cert with 2.0.2 version so I installed and tried with this version but failed.

Octopus box · 08-28-2015, 08:39

Please, make sure that You block one pin on a battery, accordingly to Software manual, before connect phone via UART cable, to read Software manual press "Help" button in software and read carefully, repeat "Write Cert' operation again and post here results.

md.kishor23 · 08-28-2015, 08:41

Without blocking pin Software won't say Phone found. I have already blocked one pin and write certificate but same problem,

Platform: Samsung Android
Selected port: COM18
Selected model: SM-N910A
Selected file: C:\Documents and Settings\fuzion\My Documents\Downloads\Cert-SM-N910A_355694060163020.cert
Perform the following steps:
1. Connect phone via UART cable to the Box.
2. Note: phone screen must be active
Connecting to phone, please wait...
Found phone on COM18
Phone connected successfully
Checking Certificate file...
and then stops.

Octopus box · 08-28-2015, 08:47

Please contact us to Skype, or Yahoo! Messenger, we will check where can be the problem. Our contacts You can find in our profile.

andrew.xardas · 10-26-2015, 14:19

I have a problem with bootloop n910a after *#9090#. I have already installed all the firmwares from the support page - it does not help me. How can I solve this problem? Octopus team, please help me.

Octopus box · 10-26-2015, 14:24

Re-flash the phone with firmware from the Support Area, then perform "Repair EFS" operation.
Also look here: http://forum.gsmhosting.com/vbb/f684...-step-1961415/

Unfortunately currently no other solutions for this issue.

08-27-2015, 10:34	#1 (permalink)
md.kishor23 Freak Poster Join Date: Feb 2012 Location: Kathmandu Age: 33 Posts: 285 Member: 1721729 Status: Offline Sonork: 100.1623685 Thanks Meter: 28	*SM-N910A Baseband unknown/Bootloop after #9090#** SM-N910A Baseband unknown/Bootloop after pressing #9090# . Set was received for unlock, 5.0.1 android version was there and as it was not detecting usb for unlock I pressed #9090# and selected HS-USB then it rebooted. After reboot it boot looped so I checked baseband and BANG there was no Baseband. Then I tried like flashing and wiping Data/Cache from support but still baseband unknown. I flashed with both files: Firstly, N910AUCU1BNK3_N910AATT1BNK3_ATT_Android_4.4.4.rar nothing was wrong till here But after flashing with N910AUCU1ANIE_N910AATT1ANIE.oct efs was too corrupt. E:failed to mount /efs (Invalid Argument) while putting in reovery. Now the problem is I found solution for unknown baseband http://forum.gsmhosting.com/vbb/f684...-step-1961415/ but I was unable to enter *#0808# and while looking for problem I found that there was no efs I mean while putting on recovery it says "E:failed to mount /efs (Invalid Argument)" How to revive this set now? I found that many users have same problem, but how to solve this??

08-27-2015, 11:10	#2 (permalink)
Octopus box Product Supporter Join Date: Oct 2009 Location: Romania, Bucharest Posts: 99,827 Member: 1146942 Status: Offline Sonork: 100.1587278 Thanks Meter: 27,409	Hello. Please, install the latest Software version and re-flash the phone with firmware from the Support Area, then perform "Repair EFS" operation.

08-27-2015, 11:29	#3 (permalink)
md.kishor23 Freak Poster Join Date: Feb 2012 Location: Kathmandu Age: 33 Posts: 285 Member: 1721729 Status: Offline Sonork: 100.1623685 Thanks Meter: 28	well I forgot to check repair efs, diag is now activated thanks

08-28-2015, 08:28	#4 (permalink)
md.kishor23 Freak Poster Join Date: Feb 2012 Location: Kathmandu Age: 33 Posts: 285 Member: 1721729 Status: Offline Sonork: 100.1623685 Thanks Meter: 28	Well I managed to repair baseband, now I have a different problem. I can't write Cert file on this phone. This is error when I tried with c3303k cable. This is error when I tried with usb cable. P.S I have tried flashing with both files available on support and also tried wiping cache/data. And I already tried with latest oct version 2.0.4 , Actually someone has successed writing cert with 2.0.2 version so I installed and tried with this version but failed.

08-28-2015, 08:39	#5 (permalink)
Octopus box Product Supporter Join Date: Oct 2009 Location: Romania, Bucharest Posts: 99,827 Member: 1146942 Status: Offline Sonork: 100.1587278 Thanks Meter: 27,409	Please, make sure that You block one pin on a battery, accordingly to Software manual, before connect phone via UART cable, to read Software manual press "Help" button in software and read carefully, repeat "Write Cert' operation again and post here results.

08-28-2015, 08:41	#6 (permalink)
md.kishor23 Freak Poster Join Date: Feb 2012 Location: Kathmandu Age: 33 Posts: 285 Member: 1721729 Status: Offline Sonork: 100.1623685 Thanks Meter: 28	Without blocking pin Software won't say Phone found. I have already blocked one pin and write certificate but same problem, Platform: Samsung Android Selected port: COM18 Selected model: SM-N910A Selected file: C:\Documents and Settings\fuzion\My Documents\Downloads\Cert-SM-N910A_355694060163020.cert Perform the following steps: 1. Connect phone via UART cable to the Box. 2. Note: phone screen must be active Connecting to phone, please wait... Found phone on COM18 Phone connected successfully Checking Certificate file... and then stops.

08-28-2015, 08:47	#7 (permalink)
Octopus box Product Supporter Join Date: Oct 2009 Location: Romania, Bucharest Posts: 99,827 Member: 1146942 Status: Offline Sonork: 100.1587278 Thanks Meter: 27,409	Please contact us to Skype, or Yahoo! Messenger, we will check where can be the problem. Our contacts You can find in our profile.

10-26-2015, 14:19	#8 (permalink)
andrew.xardas Junior Member Join Date: Apr 2012 Location: Kiev Posts: 6 Member: 1743802 Status: Offline Thanks Meter: 1	I have a problem with bootloop n910a after *#9090#. I have already installed all the firmwares from the support page - it does not help me. How can I solve this problem? Octopus team, please help me.

10-26-2015, 14:24	#9 (permalink)
Octopus box Product Supporter Join Date: Oct 2009 Location: Romania, Bucharest Posts: 99,827 Member: 1146942 Status: Offline Sonork: 100.1587278 Thanks Meter: 27,409	Re-flash the phone with firmware from the Support Area, then perform "Repair EFS" operation. Also look here: http://forum.gsmhosting.com/vbb/f684...-step-1961415/ Unfortunately currently no other solutions for this issue.