Hi,
I am facing boot loop issue on my N7100 from the time since I updated software.
My Note II motherboard went dead a long time ago so I thought to buy a new motherboard(International Version) from China which I received yesterday. I was able to install the board successfully, phone started working in normal condition, I was really Happy. Very soon, new software update popups started appearing which I decided to install one by one. Initial were some patches, then a big update came for around 800Mb which was for addition of KNOX and other features. The download was completed successfully & and I tried to Install it.
After the installation my phone went into boot loop. The Samsung logo comes and disappears and the cycle goes on.
> I am not able to get phone in recovery mode ( Vol Up+Home+Power).
> Yes, I am able to get phone in download mode (Vol Down+Home+Power).
Following is the status in download mode:
Product Name: GT-N7100
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Knox Warranty Void: 0
AP SWREV: A2
I did try to re-install ROM using ODIN but failed.
ROM Link : https://www.needrom.com/server/download.php?name=/2017/09/KSA-N7100XXUFNL1-20150518112800.zip
Currently,
a) I don't know the details of motherboard ( S/N, Country Origin, PDA Number, CSC Number ).
b) Developer options were not enabled while phone was in working condition.
c) Tried my best to restore ROM but failed.
I need support to make this phone functional again. I need to know whether the board has gone faulty or can be repaired using software stuff?
Earliest response will be highly appreciated.
Thankyou so much!
Regards
Nikhil
Did you try to flash any non-Samsung software via Odin? I ask because I see the word "custom" in download mode.
What happens when you try to boot into recovery? What happens when you try to flash a stock ROM?
Try flashing a stock recovery from sammobile.com or updato.com.
Related
I have a Sprint Samsung Galaxy s3 (Pebble Blue).
I downloaded Odin and tried to root it to CF-Root-SGS3, but using this tutorial video: youtube com watch?v=mndQZqom3Ac
Yes, I am a complete noob, therefore it failed. When I tried to turn it back on, it showed me this:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I did perform a full back up of my phone on Kies before starting, thankfully, but when I tried performing the emergency firmware recovery, it won't show my device in the list of devices requiring emergency recovery. I also don't know what the recovery code would be.
I also tried performing the firmware upgrade and initialization process, but it required my IMEI number, and I don't know how to find that without my phone working properly.
This is the other info my phone is showing:
ODIN MODE
PRODUCT NAME: SPH-L710
CUSTOM BINARY DOWNLOAD: Yes (4 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER RP SWREV: 1
Please help. Thank you so much in advance!
Did you get this taken care of? Hopefully you havent been phoneless for the past few days. Can you still boot into download mode? if you can you should try to Odin the stock tar file for the latest firmware/system update (ND8). It's in a thread here http://forum.xda-developers.com/showthread.php?t=2738533 You should be able try rooting again after this gets your phone up and running again. The only thing to worry about is that YOU CAN NOT DOWNGRADE FIRMWARE after MK3 or ND8 without bricking your phone.
Thank you!
I replied to your message, thanks again!
Hello,
I'm semi-new to flashing/rooting/custom roms, etc. I say "semi-new" because I used to know what I was doing - but it's been quite awhile. Here's my situation.
I was doing some Spring cleaning the other day and found my old T-Mobile Samsung Galaxy S3 lying around. I upgraded to the S5 awhile back, and forgot about the S3.
So I figured, "I'll sell this on eBay and make some cash!". Reasonable thought, right? I went into Security and started a Factory Reset to wipe all the data off the phone before I sold it.
Oops! Guess what? I had a Custom Recovery on the phone. Completely forgot I had rooted the device and put CWM on it.
No worries, I thought to myself - I'll use ODIN and flash the Stock Rom back on it.
So I did some research on the web and then went to Sammobile and downloaded the 4.3 firmware for SGH-T999 (March 2014). The file is: T999UVUENC2
I connected my phone to Odin, made sure re-partition was NOT checked, and attached the T999UVUENC2 file to PDA and hit Start.
So that went through successfully, according to Odin, HOWEVER, upon reboot, the phone froze on "Samsung" with the blue glow, and the LED slowly pulsated a blue light.
*** At this point I probably should have stopped what I was doing and contacted the forum ***
But I didn't.
After doing some more research, I tried to downgrade to an older version of the Stock Firmware, but I couldn't.
I then installed CWM Recovery (successfully) and tried to install Cyanogenmod 11, with the hope of installing a custom ROM, and then going back to Stock. However, I kept getting ASSERT (ro.bootloader) errors when I tried to flash CM 10.2 and CM 11 (using an SD Card from Recovery).
Now, the phone won't boot up past the initial Samsung Galaxy SIII logo.
When I boot into Download mode, this is what I see
ODIN MODE
Product Name: SGH-T999
Custom Binary Download: Yes (5 counts)
Current Binary: Custom
System Status: Official
Qualcomm Secureboot: Enable
Warranty Bit: 1
Bootloader AP SWREV: 1
I should mention, Kies does not recognize my phone. So there's that. I was hoping to do the Emergency Firmware Initialization/Upgrade using my Serial Number but the phone won't recognize my phone when I go into Recovery Mode. Do I need to re-install the stock recovery?
So, anyway, yes, I messed up, and I am for many of you, you may be rolling your eyes going, "What did you do?!??!" As someone who works in IT, I know that feeling all too well. But, if anyone in the forum will have mercy on me, I would be much obliged!!
Is my phone savable without having to send it in somewhere and paying $50 to have them un-brick it?
Thank for taking the time to read, and I look forward to your replies.
[SOLVED]
This fixed my issue:
http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
Hi, so I recently rooted, flashed TWRP, and put SlimKat on my phone, and it worked great for a few days, but then all of a sudden it would freeze on the lockscreen. To fix this I would need to pull out the battery or do the hard reboot. Then, today, after doing that once again, when I tried to boot normally or into recovery, it showed static (I'll include an image). It does, however, boot into download mode.
So then, I thought I would try and put a new recovery on it through Odin to see if that would fix anything, but upon pushing start in Odin it says no PIT partition and fails.
I have a Nandroid backup made through TWRP (I'm not sure if the one on hand is from stock or right after flashing SlimKat).
In case you need this info, here is what it says when download mode is booted:
ODIN MODE
PRODUCT NAME: SGH-T889
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 0
AP SWREV:
I'm hoping it isn't a hardware issue and that I can, if anything, put it back to stock.
Any help is greatly appreciated! Thank you!
Any update? I have read that when it loses model number it is one of the IC's. I still have model number when linked to odin.
Flashing in Odin may require the original Samsung USB cable in order to read the phone'a partition information.
Hello all,
I rooted my G925T device 1-2 weeks ago (SUPERSu?) and haven't had any major problems. Yesterday my phone died and while charging, I turned it back on only to get stuck on the T-mobile screen. I tried most everything including using Odin to reset to stock 5.1.1 firmware but I am getting a FAILED response (can't open the serial(com) port).
Some notes (not sure if relevant):
-90% sure my SuperSU was not enabled when my phone died and this started happening
-Pretty sure I unchecked the USB Debugging right after I rooted
-I wiped all my data from the recovery mode
Any help, tips, suggestions? THANKS!
bodef said:
Hello all,
I rooted my G925T device 1-2 weeks ago (SUPERSu?) and haven't had any major problems. Yesterday my phone died and while charging, I turned it back on only to get stuck on the T-mobile screen. I tried most everything including using Odin to reset to stock 5.1.1 firmware but I am getting a FAILED response (can't open the serial(com) port).
Some notes (not sure if relevant):
-90% sure my SuperSU was not enabled when my phone died and this started happening
-Pretty sure I unchecked the USB Debugging right after I rooted
-I wiped all my data from the recovery mode
Any help, tips, suggestions? THANKS!
Click to expand...
Click to collapse
Try this. Smart Switch usually can fix your boot loops. Be warned though you will lose everything on the phone. It will be reset to like you got it from the store. Except with the latest firmware.
can be deleted
jmc302005 said:
Try this. Smart Switch usually can fix your boot loops. Be warned though you will lose everything on the phone. It will be reset to like you got it from the store. Except with the latest firmware.
Click to expand...
Click to collapse
Hey, thanks for the reply.
Problem is, when I am in download mode it only tells me the following:
ODIN MODE (in red)
Product Name: SM-G925T
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download: Enabled (in blue)
KNOX WARRANT VOID: 1
RP SWREV: Letter:Number Letter:Number Letter:Number
And then Downloading... Do not turn off target
Flash Latest Stock ROM
bodef said:
Hey, thanks for the reply.
Problem is, when I am in download mode it only tells me the following:
ODIN MODE (in red)
Product Name: SM-G925T
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download: Enabled (in blue)
KNOX WARRANT VOID: 1
RP SWREV: Letter:Number Letter:Number Letter:Number
And then Downloading... Do not turn off target
Click to expand...
Click to collapse
FIrst Flash Full Stock Firmware than See if work .
1.If not work flash Unikernel V8-002 in odin.. ( it must work )
2.If both not work download firmware in 4 parts ...(BL,AP,CP,& CSC)
Just Flash only BL and AP (it work 100% Tested )
These must work ..
try and post result
The Emergency Recovery Smart Switch method worked!
I was able to find my s/n when I selected to view the barcode before going into download mode.
I thought s/n would be IMEI but its not.
bodef said:
The Emergency Recovery Smart Switch method worked!
I was able to find my s/n when I selected to view the barcode before going into download mode.
I thought s/n would be IMEI but its not.
Click to expand...
Click to collapse
I was just about to tell you that you need to press Home button to see S/N before you press Vol-Up. Glad you got it worked out. Please hit the thanks button if I helped you out.
Hi all!
I've got a bricked Samsung S4 mini.
It's stuck in a bootloop and I've got no recovery mode (No command with dead droid). Kies doesn't recognize it.
I've tried:
- flashing CWM and TWRP to get recovery mode up and running but no luck. Odin completes fine and it restarts (tried to enter on first reboot as described) but still "No command".
- flashing stock firmware from sammobile.com. I completes fine but when i restart its no difference (bootloop and no recovery)
- flashing stock firmware (all files with pit file) https://forum.xda-developers.com/showthread.php?t=2751224. This gets error in Odin and "SW REV CHECK FAIL: FUSED 2 > BINARY 0" in on the phone. I suspect its the wrong firmware.
In download mode:
Code:
CURRENT BINARY: Samsung Official
SYSTEM STATYS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
I'm all out of ideas and would love some help. I've found some similar threads on this but no solution.
How do i find out exactly what model number I've got. The back says GT-I9195 and the Samsung Warrany site says "cant find product". I guess its because its a Scandinavian phone.
Any help much appreciated.
/Daniel
Reply.
What was the last thing you did that caused the boot loop and made recovery inaccessible?
Exanneon said:
What was the last thing you did that caused the boot loop and made recovery inaccessible?
Click to expand...
Click to collapse
I got it from a friend and he said that it started to behave strange. So he decided to try flashing a custom rom.
It seems to have been a little bit to custom for this device Maybe he flashed the wrong version.
Reply.
Flashing a "wrong version" can be fatal to an android device, this has happened to 2 of my phones to my younger, more inexperienced self (around 4 years ago), for one of the phones recovery and download mode became corrupted (inaccessible), and the other phone became a complete and utter "brick" (useless), it was unable to even be turned on!
My point is that if he had flashed a rom, or even worse; a stock firmware for his phone this can seriously kill it, I suggest asking him what rom and what model the rom was built for.
Update me once you find out.
Exanneon said:
Flashing a "wrong version" can be fatal to an android device, this has happened to 2 of my phones to my younger, more inexperienced self (around 4 years ago), for one of the phones recovery and download mode became corrupted (inaccessible), and the other phone became a complete and utter "brick" (useless), it was unable to even be turned on!
My point is that if he had flashed a rom, or even worse; a stock firmware for his phone this can seriously kill it, I suggest asking him what rom and what model the rom was built for.
Update me once you find out.
Click to expand...
Click to collapse
He said that he doesn't know exactly. He tried a few but all should have been for the GT-I9195.
Reply.
If all of them were for the GT-I9195, then please list them for me, or at least the last one that was flashed, as I can't help you if I'm told that everything was done correctly.
Sure
- I9195XXUCPE1 (https://www.sammobile.com/firmwares/galaxy-s4-mini/GT-I9195/NEE/download/I9195XXUCPE1/78908/)
- I9195XXSCQA3
- I9195XXUBML4-D-BT (4 files + PIT-file CSB_signed_SERRANOLTE_ONEPIT_OPEN_130523)
Reply.
So you haven't been flashing roms, but rather stock firmwares, what odin were you using?
Exanneon said:
So you haven't been flashing roms, but rather stock firmwares, what odin were you using?
Click to expand...
Click to collapse
My friend said that he initially flashed a Cyanogenmod rom and it worked but he didin't like it and the troubles started when he tried to revert to stock.
Odin version: 3.09
Thanks.
Reply.
That's unusual, flashing stock firmware is very unlikely to cause any problems but fix everything...Could you please give me the link to the stock firmware your friend was flashing? (If you have it)
standarggbg said:
Hi all!
I've got a bricked Samsung S4 mini.
It's stuck in a bootloop and I've got no recovery mode (No command with dead droid). Kies doesn't recognize it.
I've tried:
- flashing CWM and TWRP to get recovery mode up and running but no luck. Odin completes fine and it restarts (tried to enter on first reboot as described) but still "No command".
- flashing stock firmware from sammobile.com. I completes fine but when i restart its no difference (bootloop and no recovery)
- flashing stock firmware (all files with pit file) https://forum.xda-developers.com/showthread.php?t=2751224. This gets error in Odin and "SW REV CHECK FAIL: FUSED 2 > BINARY 0" in on the phone. I suspect its the wrong firmware.
In download mode:
Code:
CURRENT BINARY: Samsung Official
SYSTEM STATYS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
I'm all out of ideas and would love some help. I've found some similar threads on this but no solution.
How do i find out exactly what model number I've got. The back says GT-I9195 and the Samsung Warrany site says "cant find product". I guess its because its a Scandinavian phone.
Any help much appreciated.
/Daniel
Click to expand...
Click to collapse
same problem. did you find any luck fixing your phone? wanna try it too if so :good:
He doesn't remember but think it was I9195XXSCQA3.
ddikere said:
same problem. did you find any luck fixing your phone? wanna try it too if so :good:
Click to expand...
Click to collapse
Nope. Not yet.