so i recently got a note 3 from a friend to fix for her. it boots to the samsung logo then vibrates and reboots over and over, recovery just says "booting recovery" then it goes blank and reboots to the same booting recovery screen, shes doesnt know what version it had prior to bricking. she said one day it was working then turned off and never back on again, the odin mode screen had a2, a3 on it ill post a pic later anyway i can get into download mode so i figured id just flash with odin and be good, i tried to narrow down the proper firmware with the a3, but after flashing nc2, nl1, oc1, im still stuck odin says everything passed, i tried flashing the big main file, tried flashing them in each box at the same time, even tried it with the pit file, tried flashing with odin 3.9 and 3.10.7. same result odin says passed still cant access recovery or os. any help would be greatly appreciated. thanks
Open Odin, uncheck everything except f reset time, flash rom. When you see reset on the statutes window, remove USB cable from the phone, remove battery, wait 5 seconds, replace battery, boot directly into recovery, perform a factory wipe, reboot.
does it matter what version i flash? since im not really sure what version it had prior?
I can't figure out how to upload a photo I have xda 4.0, and can't post outside links yet. Anyway
It says
Product name:N900A
Current binary: Samsung official
System status official
Knox void status 0x0
Qualcomm Secureboot enabled(csb)
Ap swrev s2 t2 a2 a3 p2
Secure download enable
Udc start
Hope that helps
Ran Odin again with the settings you said, after the battery pull the phone says recovery booting, then turned off vibrated twice then same screen again and again. Thanks for the suggestion though any our ideas? I was searching and thought I seen somewhere that to unbrick it it needs to be the same firmware it had before, but I don't know what that was.
ghost5825 said:
Ran Odin again with the settings you said, after the battery pull the phone says recovery booting, then turned off vibrated twice then same screen again and again. Thanks for the suggestion though any our ideas? I was searching and thought I seen somewhere that to unbrick it it needs to be the same firmware it had before, but I don't know what that was.
Click to expand...
Click to collapse
You should probably ask her if she had Lollipop. If she did then that narrows it down to OC1 or OC2.
She doesn't know, not very phone literate as far as software, any ideas? I read in another thread to flash a modified version of nc2 but can't seem to find that version, this is the thread http://forum.xda-developers.com/showthread.php?t=2703006
Don't know if I can't find it, kinda confusing as far as what I need, like I said I've tried everything except oc2 cant find a link I've tried googling, and that thread says Odin files but can't find a full one for oc2, there's ones for safestrap but can't find Odin
Related
This WAS the situation before the problems:
Rooted Gingerbread rom, all working fine. Decided to unroot and install the full version of the official German ICS rom by using PC Odin. All went fine and used my Note for over two days. Because of the lags en slow responses I decided to reflash the ICS rom. From that moment on I messed it up. I've been reading and searching hundreds of posts for almost a day but didn't find a solution.
This IS the current situation:
I can get into download mode
I can get in recovery mode
However, in recovery mode I can not install a rom, every flash (CWM, both ICS and GB - even using chainfire's rom needed for rooting) stops on a random moment...but never gets it to the end, even if I wait several hours. Installing is very...very....very slow.
In recovery mode i can not restore a Nandroid backup, both ICS and GB. Every backup stops when /system has te be installed. errormessage.
In download mode I can connect my Note to PC Odin. I can select a rom and start flashing. However, after appr. 80% installation halts during "nand write start", no error message. The flashing does not finish, even after hours.
Funny is, i can install a kernel like Abyss.
So, I can't restore, i can't flash using cwm in recovery and I can't flash using PC Odin. My device seems not fully bricked. The max I get when rebooting (knowing that the process has not finished) is the triangle screen.
Any advise is appreciated.
Do not flash thru CWM... Flash a good GB kernel like "franco.Kernel" but thru PC Odin then u can flash whatever u want from franco's CWM... Good luck
Don't need help anymore
Note is officially bricked. After several attempts to recover from a softbrick the screen of my Note didn't turn on anymore. No button or button combination works, no recovery and no download mode, just a black screen.
Ce said:
Don't need help anymore
Note is officially bricked. After several attempts to recover from a softbrick the screen of my Note didn't turn on anymore. No button or button combination works, no recovery and no download mode, just a black screen.
Click to expand...
Click to collapse
Flat battery? It's also possible that it's just the screen that's not working. Try entering download mode "blind". So hold power+home+vol down for ~10 seconds, then press vol up. Hook it up via usb and see if Odin can recognize it.
Thanks, didn't think of that. But unfortunately no response from the device.
So now that it looks like your phone is officially bricked, I think you should just take it to Samsung and make up a story. Like you were updating your software with Kies and something happened and the phone is just not booting up.
I am sorry you bricked your note though..
try AMORA Filemanager.. flash via recovery and you have a file manager,,, take a look on your partitions
just my idea, you got nothing to lose
musashiro said:
try AMORA Filemanager.. flash via recovery and you have a file manager,,, take a look on your partitions
just my idea, you got nothing to lose
Click to expand...
Click to collapse
I would like to but it's very hard when you can't see anything on the screen...
Maybe it's just the battery, try to charge it externally and try a JIG also
Sent from my GT-N7000 using XDA
Just a quick, final, update.
My Note was superbricked. Had to send it to a Samsung Service Center. No additional questions were asked. Samsung replaced the mainboard. Didn't have to pay anything.
Great service!!!
try this out buddy, do it on your own risk!!! anyways you have messed it up.
Ce said:
This WAS the situation before the problems:
Rooted Gingerbread rom, all working fine. Decided to unroot and install the full version of the official German ICS rom by using PC Odin. All went fine and used my Note for over two days. Because of the lags en slow responses I decided to reflash the ICS rom. From that moment on I messed it up. I've been reading and searching hundreds of posts for almost a day but didn't find a solution.
This IS the current situation:
I can get into download mode
I can get in recovery mode
However, in recovery mode I can not install a rom, every flash (CWM, both ICS and GB - even using chainfire's rom needed for rooting) stops on a random moment...but never gets it to the end, even if I wait several hours. Installing is very...very....very slow.
In recovery mode i can not restore a Nandroid backup, both ICS and GB. Every backup stops when /system has te be installed. errormessage.
In download mode I can connect my Note to PC Odin. I can select a rom and start flashing. However, after appr. 80% installation halts during "nand write start", no error message. The flashing does not finish, even after hours.
Funny is, i can install a kernel like Abyss.
So, I can't restore, i can't flash using cwm in recovery and I can't flash using PC Odin. My device seems not fully bricked. The max I get when rebooting (knowing that the process has not finished) is the triangle screen.
Any advise is appreciated.
Click to expand...
Click to collapse
i was not a member when i commited this mistake. but then big thanks to this community it helped me back from softbrick.
first you do is install a stock kernel of ics on your note go into recovery and just clear cache partition, thats it no wipe/data factory reset.
then,
install the pit file from this thread, also read it completely before proceeding. http://forum.xda-developers.com/show....php?t=1667886 , hoping yours is 16gb version and also read this thread for additional info but its quite complicated for me so im just telling you the direct method and hopefully itll get your note back to work. so once you download the 16gb pit file unzip it and in the unzip folder you will find a separately lying pit of 16gb stating patched-standard thats the one you want.
then,
goto samfirmware and download the latest ics firmware(i downloaded the indian one as it is in file .tar),
unzip it till you get .tar file.
open odin- click pit-select 16gb patched standard pit- check wether repartion is ticked- click pda-select the .tar file you extracted connect your phone and start. this time i wont stop at factory.fs.....
NOTE THAT AFTER THIS PROCEDURE IS COMPLETED SUCCESSFULLY YOUR INTERNAL STORAGE WOULD BE ONLY 8GB INSTEAD OF 11 GB STOCK WHICH YOU WERE GETTING.
I REVIVED MY NOTE THROUGH THIS PROCEDURE. PROCEES AT YOUR OWN RISK.
one your phone is working you'll be able to reset the counter with a jig and get your phone under warranty and get your motherboard changed by teliing at the Samsung Service that you are getting only 8gb instead of 11gb you used to get earlier(warranty only if you had any).
hope this helps mate.
BEST OF LUCK!!
A BIG HUGE THANKS TO hg42.....
I bricked my SM-T900 Wifi while attempting to root it. Can anyone help me get it un-bricked?
Here's a step by step list of what I did and what happened:
1. Turned on USB debugging mode
2. Downloaded and installed Samsung kies
3. Downloaded the file for SM-T900 from autoroot [dot] chainfire [dot] eu/ (it won't let me post outside links)
4. Turn off tablet, get into custom firmware installation mode by holding power, volume-, and home, then confirm the warning
5. run Odin (v3.07, came in the zip file)
6. plug in tablet, tablet showed up as a com port but did NOT show any other information. I don't know if it was supposed to show anything else but I hadn't though about that at the time.
7. Clicked on PDA and selected the file CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5
8. Clicked start
9. Waited, it said it was doing something with cache, I don't recall exactly what it said
10. after about 3 minutes the screen looked wrong, all the pixels were different colors, (rainbow static?)
11. Waited about 10 minutes just in case that was not a sign of failure, then Odin reported that it failed.
Now when I press the power button, I get the screen that says "Firmware upgrade encountered and issue. Please select recovery mode in Kies and try again"
I tried using that in Kies but Kies can't connect to my tablet any more. When I try to use Odin using the recovery with power, vol-, home, it detects that I plugged it in but when I try to click start it fails and nothing happens.
I have exact the same problem.
I have read many articles, who said it was easy to root.
That's not true !!!!.
Maybe because the tablet became an update today ?
What I did to recover the tablet: (phew !!!)
Download this bootloader:
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
Connect to Odin and flash it.
A few seconds, it says OK, reboots and voila: there's your tablet again revived !!!!.
rumaro said:
I have exact the same problem.
I have read many articles, who said it was easy to root.
That's not true !!!!.
Maybe because the tablet became an update today ?
What I did to recover the tablet: (phew !!!)
Download this bootloader:
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
Connect to Odin and flash it.
A few seconds, it says OK, reboots and voila: there's your tablet again revived !!!!.
Click to expand...
Click to collapse
Unfortunately Odin fails before it manages to even connect to my tablet so I'm not sure it will work for me but I'll give it a try. It managed to connect before when I tried to flash the root files but now it fails every time. I'll update this when I get home and try flashing that.
Edit:
Got home, tried your fix. I am happy to report it worked and it only took a few seconds. Thanks!
Edit:
To anyone reading this thread, if you tried rooting your SM-T900 using the SM-T900 files for rooting, try using the SM-P900 files instead! I just tried that and it seems to be working fine.
I'm glad I could help. :good:
It's bad for your heart when you see that your expensive tablet is bricked.
Hello everyone. Where do I flash the bootloader in odin? Do I use PDA or Bootloader and do I need to check the bootloader update box? Just wanted to confirm before further messing up my tablet. Thanks!
Edit: Never mind, figured it out. Thanks for the help!
This method just worked for me. Flashed the bootloader with Odin after getting "stuck" and it booted right up.
Jim
sizedlemming65 said:
Hello everyone. Where do I flash the bootloader in odin? Do I use PDA or Bootloader and do I need to check the bootloader update box? Just wanted to confirm before further messing up my tablet. Thanks!
Edit: Never mind, figured it out. Thanks for the help!
Click to expand...
Click to collapse
What did you do exactly to fix it? I'm having the same issue. Just sits at screen and says:
ODIN MODE
Product Name: SM-T900
Current Binary: Custom
System Status: Official
KNOX Warranty Void: 1
RP SWREV: A1
How do you use that recovery.img file?
For the top most problem flash cwm or TWRP recovery through Odin or through recovery mode then boot into cwm or TWRP recovery delete all files and install a supported rom.
If u want full explained steps mail me
- [email protected]
Sent from my SM-J500F using XDA Forums
it's 2022 & my T900 finally went into bootloop in model logo, does anyone know the real reason for this? is it hardware or software problem?
- I can flash any version via odin but still bootloops
- TWRP worked once after that can't get in anymore
- the only button working is for the download mode PWR + Vol Down
- before all this LED Stayed on until batt drained then bootloops
it's a good tab to watch movie while on a treadmill
Hi so I was trying to use CF to root my phone and ended up screwing it somehow and bricked. I thought I'd followed the instructions well enough but I obviously did something wrong. Now my phone is stuck saying it needs to recover with Kies. This is my first Samsung phone but I'm not new to Android.
I tried installing the stock firmware through ODIN but everytime I flash it gets to installing the system ext4 and fails. I also wasn't able to recover using Kies(not even sure how you use it tbh).
If anyone could help me it would be mucho appreciated. I'm pretty pissed at myself right now.
re: not bricked
cronos1388 said:
Hi so I was trying to use CF to root my phone and ended up screwing it somehow and bricked. I thought I'd followed the instructions well enough but I obviously did something wrong. Now my phone is stuck saying it needs to recover with Kies. This is my first Samsung phone but I'm not new to Android.
I tried installing the stock firmware through ODIN but everytime I flash it gets to installing the system ext4 and fails. I also wasn't able to recover using Kies(not even sure how you use it tbh).
If anyone could help me it would be mucho appreciated. I'm pretty pissed at myself right now.
Click to expand...
Click to collapse
Your phone is NOT bricked. If it was the screen would not even go on.
Have you tried going into recovery mode (VolumeUP/VolDown/PowerButton)
and once in Recovery Mode do a factory reset or Data Reset forgot what the
exact wording is in the stock recovery.
If you flashed twrp recovery it's ok too, just select "factory reset".
After doing that the phone should no longer display anything about Kies.
If you get to the twrp recovery screen you should be able to flash a stock
rooted rom without any issues.
If all you get is the stock recovery screen then you should be able to odin
flash the official Samsung Note 4 kitkat 4.4.4 NJ7 firmware which you may
need to download the firmware from http://SamMobile.com if you don't
already have it. (be sure you have the correct firmware for the Note 4 N910T).
Be 100% sure that the phone is FULLY POWERED DOWN before going
into Download Mode to avoid odin errors and issues.
Good luck!
Thanks man. I had tried Odin at my office and nothing doing.
Got home took my time and was real calm about things and voila. May have been an md5 issue with the firmware file. Just relieved I didn't have to RMA it.
cronos1388 said:
Thanks man. I had tried Odin at my office and nothing doing.
Got home took my time and was real calm about things and voila. May have been an md5 issue with the firmware file. Just relieved I didn't have to RMA it.
Click to expand...
Click to collapse
Can you check for the file with md5 before you flash from your phone? I forgot where to dig for this info.
All I I have done before is on my cook rom file, I just open it with WinRAR and test for error. If no error, then its good.
On my Home PC I have a program that will put a check mark next to a file if it matches the md5. I also have Winrar at home.
I was just using the default Windows zip program and I have had problems with that and installers/roms in the past.
The only other things I did different were I removed the SD card and installed the drivers before plugging my phone in instead of letting Windows download them automatically.
I also removed the battery after I left work so it was out of the phone for a couple of hours.
The final thing I did was calm down lol after the initial shock of seeing a softbricked screen on my brand new phone.
I'm all rooted now with TWRP and running Hyperdrive so it's all smooth sailing from this point forward.
You should check md5 on phone once you done transferred to phone from PC
BAD ASS NOTE 4
I've searched around the forum and haven't hit a solution, so sorry if it's out there.
So, I have a Galaxy S4 Active (i537) ATT. I was given to me in a bootlooping state, and if I fix it I can keep the device.
What I have done to the moment:
Flashed every stock rom found in the forum with Odin (No luck on the device booting)
What the device does:
It shows the samsung splash, and restarts over and over, sometimes it doesn't even manage to get to the samsung splash.
Attempting to boot into recover mode produces the same result, it says booting recovery and it restarts.
Info on Download mode:
Product name: SGH-i537
Current Binary: Samsung official
System Status: Official
Knox kernel lock: 0xfffffffc
Knox kernel warranty void: 0xfffffffc
CSB-CONFIG-LSB: 0x30
Write protection: enable
emmc burst mode enabled
I'm new to samsung devices, so I hope someone can help me out here.
Thanks in advanced!
rguilamo said:
I've searched around the forum and haven't hit a solution, so sorry if it's out there.
So, I have a Galaxy S4 Active (i537) ATT. I was given to me in a bootlooping state, and if I fix it I can keep the device.
What I have done to the moment:
Flashed every stock rom found in the forum with Odin (No luck on the device booting)
What the device does:
It shows the samsung splash, and restarts over and over, sometimes it doesn't even manage to get to the samsung splash.
Attempting to boot into recover mode produces the same result, it says booting recovery and it restarts.
Info on Download mode:
Product name: SGH-i537
Current Binary: Samsung official
System Status: Official
Knox kernel lock: 0xfffffffc
Knox kernel warranty void: 0xfffffffc
CSB-CONFIG-LSB: 0x30
Write protection: enable
emmc burst mode enabled
I'm new to samsung devices, so I hope someone can help me out here.
Thanks in advanced!
Click to expand...
Click to collapse
It's hard to say what is wrong, but it sounds like you definitely need to flash stock firmware. One question, is it definitely the AT&T version (with the AT&T logo on the back cover) or could it be the Mexican version?
If it's the AT&T version, then flash the NE3 firmware by following the instructions in i537 Firmware Install Guide. The OP of the guide will ask you which firmware you're currently on, but for NE3 it doesn't matter which one you select because all the instructions will be the same. Make sure you don't have a corrupted download by checking the MD5 of the file you downloaded against the MD5 posted in the i537 Firmware Thread.
If you have the Mexican/Uruguayan version, you need to download the latest version of the firmware from sammobile and flash that. Flashing AT&T firmware on a Mexican/Uruguayan phone could result in the bootloops you are experiencing.
Devo7v said:
It's hard to say what is wrong, but it sounds like you definitely need to flash stock firmware. One question, is it definitely the AT&T version (with the AT&T logo on the back cover) or could it be the Mexican version?
If it's the AT&T version, then flash the NE3 firmware by following the instructions in i537 Firmware Install Guide. The OP of the guide will ask you which firmware you're currently on, but for NE3 it doesn't matter which one you select because all the instructions will be the same. Make sure you don't have a corrupted download by checking the MD5 of the file you downloaded against the MD5 posted in the i537 Firmware Thread.
If you have the Mexican/Uruguayan version, you need to download the latest version of the firmware from sammobile and flash that. Flashing AT&T firmware on a Mexican/Uruguayan phone could result in the bootloops you are experiencing.
Click to expand...
Click to collapse
Yes I'm sure It's AT&T. I had already tried NE3, as I said, I've flashed as many stock firmwares as I have been able to lay hands on. I did notice that when I tried NE3 again, knox kernel lock and knox kernel warranty changed from my previous posted states to these:
Knox kernel lock: 0x0
Knox kernel warranty void: 0x1
I cand add that exactly when Odin sends the reboot the phone tries to boot but into recovery mode, instead of just booting normally.
The only thing I can think of now, is that the device must have a hrdware issue.
rguilamo said:
Yes I'm sure It's AT&T. I had already tried NE3, as I said, I've flashed as many stock firmwares as I have been able to lay hands on. I did notice that when I tried NE3 again, knox kernel lock and knox kernel warranty changed from my previous posted states to these:
Knox kernel lock: 0x0
Knox kernel warranty void: 0x1
I cand add that exactly when Odin sends the reboot the phone tries to boot but into recovery mode, instead of just booting normally.
The only thing I can think of now, is that the device must have a hrdware issue.
Click to expand...
Click to collapse
It's supposed to try to reboot into recovery mode when you first Odin back to stock NE3. I just recovered from a soft brick myself where I couldn't boot at all. Flashed NE3 through Odin and the first time it rebooted, it went to stock recovery (I assume to finish installing the stock rom), did what it needed, and eventually rebooted normally. Plus (sorry, I just have to ask), you are using download mode for Odin (not recovery mode), correct?
thisisapoorusernamechoice said:
It's supposed to try to reboot into recovery mode when you first Odin back to stock NE3. I just recovered from a soft brick myself where I couldn't boot at all. Flashed NE3 through Odin and the first time it rebooted, it went to stock recovery (I assume to finish installing the stock rom), did what it needed, and eventually rebooted normally. Plus (sorry, I just have to ask), you are using download mode for Odin (not recovery mode), correct?
Click to expand...
Click to collapse
Yes I'm using Download mode for ODIN, the thing is, when it tries to boot to recovery mode after flashing with ODIN, and the reboot command is sent, the recovery never boots, the screen goes off, and then it just starts restarting itself
rguilamo said:
Yes I'm using Download mode for ODIN, the thing is, when it tries to boot to recovery mode after flashing with ODIN, and the reboot command is sent, the recovery never boots, the screen goes off, and then it just starts restarting itself
Click to expand...
Click to collapse
And you definitely don't have a corrupted download, and you've tried different usb cables, different usb ports, and different computers?
Devo7v said:
And you definitely don't have a corrupted download, and you've tried different usb cables, different usb ports, and different computers?
Click to expand...
Click to collapse
Checked MD5's, used original Samsung cable, Asus Nexus 7 Cable, tried Windows 7 (Desktop), and windows 8.1 on two different laptops.
Curiously I said to myself, let me try and charge it, since all this flashing might have taken out the battery. When I plugged in the USB cable the device showed the Samsung splash, and turned off, yet I let it be and didn't disconnect it, after an hour or so, I came back and saw him charging the battery, with the red light indicator on, about 20 minutes later it tried to boot, got to the ATT logo, and after I while with the ATT logo (I assume since it has to compile the dalvik, because it's the first boot) it just turned off again, and back to ATT logo, and it was bootlooping like this until I unplugged it and gave up.
Hello everyone- I hope someone can give me some advice i haven't tried yet on my issue. This is my first post and i searched through a million forums for ideas, my apologies if i missed anything or if anything below is unclear. I tried to list everything out that i have tried in case i missed anything.
Note 9 - SM-N960U (TMB) went into a boot loop randomly (possible after a Samsung update as it happened overnight).
Steps I've taken so far:
- Tried the normal steps first as instructed by Samsung, clear cache-partition, factory reset device etc - still stuck in boot loop.
- Took phone to authorized Samsung service center, they could not fix. phone now on blue screen "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC Software"
- Smart switch recovery software would not recognize the phone, updated drivers multiple times, still no detection.
-Downloaded stock TMB firmware from SamMobile (N960USQS9FUG2) - Tried to flash with Odin (versions 3.13 and 3.14 - patched and unpatched) kept getting stuck at vendor.img.ext4 in CSC file or system.img.ext4 in the AP file.
-Tried to Re-Partition without Pit file and with the pit file - PIT file name: CROWNQLTE_USA_SINGLE.pit - Odin would get stuck on same files.
-Tried to re-partition with Nand Erase selected and Pit file attached - Odin would freeze at setting the partition.
Is there anything else i can try or is this phone officially a paper weight?
You are able to flash firmware from the emergency screen. When one of my devices did this I was able to get things up and running with Odin flash from that screen. I can't remember what partition was broken when it happened on my Note 8, but the only way to fix was putting in new mother board. I'm not saying go this route. Might try combination firmware. I'm sure someone will chime in if I am wrong. I tried to flash stock on my SM-N950U after being rooted. It would show pass in Odin but would never boot..just bootloader. As I said above my only option was new motherboard. I wish I could find the message from a developer that helps me a ton, and which partition it was that was the issue. If I find it I will let you know.
butchieboy said:
You are able to flash firmware from the emergency screen. When one of my devices did this I was able to get things up and running with Odin flash from that screen. I can't remember what partition was broken when it happened on my Note 8, but the only way to fix was putting in new mother board. I'm not saying go this route. Might try combination firmware. I'm sure someone will chime in if I am wrong. I tried to flash stock on my SM-N950U after being rooted. It would show pass in Odin but would never boot..just bootloader. As I said above my only option was new motherboard. I wish I could find the message from a developer that helps me a ton, and which partition it was that was the issue. If I find it I will let you know.
Click to expand...
Click to collapse
Thanks for the reply @butchieboy, If you find those messages i would definitely appreciate it! I should have specified that i was able to run the Odin flash from the recovery page. That's a good idea to try combination firmware, never done it before though. Would i just try an older AP or CSC with the up to date other files? or just a combination of old and new and see if something happens?
Overall i think i may be in the boat you were in with your Note 8- something seems seriously wrong with the memory partitions that seem like it may be unfixable via flash. i'll have to see if i can find a motherboard that's worth the price to see if it's worth it at this point.
Combo firmware needs be on same bootloader that you are currently on