Related
i was trying to install cm7 after seeing it everywhere,i was on gingerbread. tried to install it it didn't work just went to recovery screen every time, then i read i had to be using froyo so i downgraded to froyo , successfully downgraded, i noticed i didnt have recovery nor download, so i installed rom manager so i can install recovery, didnt work so installed cm7 from the app, phone powered on then vibrated,went to random repair shop(Somalian) they said he can fix it, then he said i damaged the boot sector so he said he can do it, left it to him, couldnt do it, after he tried fixing it, phone didn't power on (worse) he did say samsung will fix it because he repaired the boot sector and they will fix it. phone was rooted with froyo software.
WILL SAMSUNG FIX THIS ISSUE, TOLD THEM IT WAS AN ISSUE AFTER UPDATING THROUGH THE KIES SOFTWARE . HAS ANYONE ELSE HAD THIS ISSUE
(IN THE UK) URGENT SENT IT TO THEM WAITING FOR IT
whlzibos said:
i was trying to install cm7 after seeing it everywhere,i was on gingerbread. tried to install it it didn't work just went to recovery screen every time, then i read i had to be using froyo so i downgraded to froyo , successfully downgraded, i noticed i didnt have recovery nor download, so i installed rom manager so i can install recovery, didnt work so installed cm7 from the app, phone powered on then vibrated,went to random repair shop(Somalian) they said he can fix it, then he said i damaged the boot sector so he said he can do it, left it to him, couldnt do it, after he tried fixing it, phone didn't power on (worse) he did say samsung will fix it because he repaired the boot sector and they will fix it. phone was rooted with froyo software.
WILL SAMSUNG FIX THIS ISSUE, TOLD THEM IT WAS AN ISSUE AFTER UPDATING THROUGH THE KIES SOFTWARE . HAS ANYONE ELSE HAD THIS ISSUE
(IN THE UK) URGENT SENT IT TO THEM WAITING FOR IT
Click to expand...
Click to collapse
I think, therefore fail to understand, that might even fix it yourself. Could enter download mode?
You should have bought the USB jig to force boot into download mode. Less hassle.
Nevertheless Samsung will fix it for you.
no download mode
i wasn't able to go into download mode i tried many things, i thought of getting the jig but its for semi bricked i think mine was fully bricked.
you said they will fix it, have you tried it before and how do you know (no offence)
Hi,
Yes samsung will fix it, i did it once !
It's when i tried to flash my first ROM, i used ODIN and during the flashing, it failed, and i did not have the 3-button-combo to go back into download mode...
Result : Phone bricked...
I sent it back to samsung saying that my computer turned off during an upgrade using Samsung Kies.
They gave it back to me after 2 weeks!
if you're newly flashing the CM7, then after the installation, it goes bootloop then go to recovery, over and over. remove the battery, then go to recovery(volume up+homebutton+powerkey) then flash it again. try that.
price
Skiess said:
Hi,
Yes samsung will fix it, i did it once !
It's when i tried to flash my first ROM, i used ODIN and during the flashing, it failed, and i did not have the 3-button-combo to go back into download mode...
Result : Phone bricked...
I sent it back to samsung saying that my computer turned off during an upgrade using Samsung Kies.
They gave it back to me after 2 weeks!
Click to expand...
Click to collapse
how much was it for samsung to fix it ?
not trying cm7 again
nieohl said:
if you're newly flashing the CM7, then after the installation, it goes bootloop then go to recovery, over and over. remove the battery, then go to recovery(volume up+homebutton+powerkey) then flash it again. try that.
Click to expand...
Click to collapse
never trying cm7 again
whlzibos said:
i wasn't able to go into download mode i tried many things, i thought of getting the jig but its for semi bricked i think mine was fully bricked.
you said they will fix it, have you tried it before and how do you know (no offence)
Click to expand...
Click to collapse
That it can be repaired there is no doubt because it is a software problem and not hardware. I've seen in forums that if you can not enter the download mode, you can force hardware, you put a resistor in the USB cable, but in the end for a normal user is a bit complicated, my advice would carry it to the Service Center. And the price can be from free to relatively inexpensive because it does not have to replace any parts.
phone is back
they fixed the phone free of charge and the bonus is my phone was 8gb now is 16gb for some reason
thanks for the replies
whlzibos said:
they fixed the phone free of charge and the bonus is my phone was 8gb now is 16gb for some reason
Click to expand...
Click to collapse
Then they didn't bother fixing it and just sent you another handset...
[CONSPIRACYMODE] Or Samasung only made 16gb versions and crippled some to only 8gb... [/CONSPIRACYMODE]
Some people have all the luck. Glad for you whizibos your small mishap had fringe benefits.
I was trying to fix my microsd card and came across this guide
http://forum.xda-developers.com/showthread.php?t=907436
I used the dd command at first for mmcblk0 which unfortunately was internal SD card. I found it out when I used the fdisk command in 2nd step. Then I exited and tried again with mmcblk1 which is external SD and at the end I tried to reboot. Now I the phone doesn't get turned on at all. No recovery or download mode too. Please someone point me to the right direction...
Sent from my JellyBean using XDA
PS as far as I have understood I have erased some blocks from internal SD and there seems no way of formatting it again since device won't turn on. I still have it under warranty. What should I do? Go to Samsung and try to play dumb? Like I was upgrading my phone to ics and now phones not working?? Plz help..
Sent from my JellyBean using XDA
Can you still get into recovery!?
If yes, you should flash the original pit file for your n7000 either the 16gb or 32gb. It will automatically re-partition your internal sd to its original state.
Please read more on this from the link below:
http://forum.xda-developers.com/showthread.php?t=1667886
Sent from my GT-N7000
Thanks for your reply...
No it doesn't go into recovery. It just has a black screen.
Sent from my JellyBean using XDA
Try holding power button+home+volume up key for about 30 secs. Open odin, plug in your phone, try to check odin detects your phone. Sometimes the screen just goes black but it in fact enters recovery. If your phone gets detected flash the pit file and flash any safe kernels just tobe sure then flash any rom you want. Hope you get it sort out.
Sent from my GT-N7000
SuperMane said:
I was trying to fix my microsd card and came across this guide
http://forum.xda-developers.com/showthread.php?t=907436
I used the dd command at first for mmcblk0 which unfortunately was internal SD card. I found it out when I used the fdisk command in 2nd step. Then I exited and tried again with mmcblk1 which is external SD and at the end I tried to reboot. Now I the phone doesn't get turned on at all. No recovery or download mode too. Please someone point me to the right direction...
Sent from my JellyBean using XDA
Click to expand...
Click to collapse
There are few things can try:
1. check/recharge battery
2. SS service
2. an usb Jig to get the phone in download mode
3. jtag riff box. It can fix bootloader and get the phone work again from hard brick. They have service in many countries.
GL!
@vlxdxmxr
I tried both download and recovery and connected but nothing happens. Is there any other way to make sure whether the device turns on? I remember that on lcd the devices turns black. But on amoled there is no sign of life...
@forest1971
Battery is working. It gets heated up when charged it for 3 hours. Are you sure this is just a soft brick which a jig can solve ? I mean I have changed some mmcblks. Is there any chance that download mode is gone? Then if I m not wrong a jig can't solve this since it just forces to download mode. SS is last option since I have lost my bill...
And another reason I am afraid to go to SS is because I was running a custom ROM. They might not even accept it for repairs.
Sent from my JellyBean using XDA
Sometime a usb jig can help to get the phone in download mode. From there you can flash orig pit file and then flash bootloader (from dr.ketan toolbox). Jig is cheap so should order online and try it. If not work then try jtag. It is more expensive but almost sure will work and will fix your phone. The service may cost around 1/4 of the motherboard. If you need to buy the box itself it cost more and do it yourself with the box is not easy at all.
Sent from my phone
@forest1971 And how much would that be? I have ordered a jig already will get it by Saturday.
Sent from my JellyBean using XDA
I gave it to ssc and told them it hung during ics update and now they are changing its motherboard...
Sent from my JellyBean using XDA
Howdy there.
First off, this is not "just another bricked Note thread".
I got this thing from a friend who did not have a clue what he did with it, but he told me he tried to "root it or something" He didn't have any files left, or any memory what he used.
I have for weeks tried every single trick in the book, followed every tutorial, and it shows no sign of coming to life any time soon.
When I got it, it just got stuck on the Samsung flash screen. I couldn't get into any sort of recovery, but I got into download mode, so I tried reflashing the stock firmware with ODIN, but it got stuck on NAND WRITE START for 2 hours, and then failed. All Kies processes were killed, I double checked.
After that, it only shows the "Firmware update failed, start emergency recovery mode in kies"
Kies does not support initialization for N7000, doubted it would have worked anyways.
After this, I went on to read about the brick bug for N7000
Since then I have tried repartitioning the device with all kinds of pit files, I have tried installing about 20 different firmwares, I have tried installing just a kernel, both stock and others, and NOTHING works.
Some pit files get stuck in DO NOT TURN OFF DEVICE for 6-24 hours, until I have disconnected or battery has run out, and some fail by themselves after 20 minutes.
Firmwares get stuck at NAND WRITE START, and fail after about an hour
Kernels fill up the bar with the green dots showing it's doing something but as soon as the log says "NAND Write Start" it gets stuck.
Is there ANYTHING still worth testing, before throwing it in the well? I will not go to a service center and pay to fix a spare phone that will lay in a box until I MIGHT need it some day.
It doesn't matter if my storage space goes down to only 500mb space with some sort of repartitioning, nothing matters. I just want it to run.
I do not have any recovery, and I haven't successfully installed any,
Basically the only thing I can do, is get to Download mode, and the only program so far finding it is ODIN.
I am very thankful for any help, and don't hesitate checking if I forgot something very basic, I might just as well have forgot something very important, but I feel I have tried everything.
Thank you!
-Jimi
It is exactly this: just another bricked Note thread.
ThaiDai said:
It is exactly this: just another bricked Note thread.
Click to expand...
Click to collapse
Well, okay then. Thanks for clearing that up.
I just figured that it's something worse since NOTHING works, hence the "not just another" meaning "not just the same as the others". Atleast I thought it meant that. Perhaps my English isn't so good. Oh well.
I have read dozens of other threads about this where people have been able to get into recovery mode, repartition, or flash a new kernel, or at least SOMETHING, but mine just blocks everything.
-Jimi
Okay then, let's simplify the question/request.
Is there ANY way at all to scan or/and repartition my emmc?
WITHOUT a recovery.
WITHOUT it accepting anything through ODIN, not even the standard pit file, or any of the custom ones I have tried from another thread.
WITHOUT adb.
I can only get to Download Mode.
Heimdall seemed to understand my phone a bit, but couldn't flash anything.
Kernels got stuck at 100%
Factoryfs got stuck at 4%
Recovery got an error "finishing the packet" or something.
Could I use Heimdall to scan or repartition my emmc maybe?
If you are unable to Odin flash a recovery or stock rom then there's no other way. If you found other methods but is still unsuccessful then your phone is dead anyways.
I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.
nokiamodeln91 said:
I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.
Click to expand...
Click to collapse
Nah, I think the memory is broken.
I have only tested with odin 1.75, but on 3 different PCs
My laptop with Win 8.1
My old computer with XP
And my work computer with Win 7 home
Still, I do not want to give up!
In my frustration I started to flash everything and anything that just had a N7000 tag on it, and somehow somewhere something happened.
I do not have the "firmware failed, use kies recovery" message anymore.
I am instead getting the Samsung splash screen, but it freezes there, I can't do anything.
And also, if my device is off, I can charge it! The battery shows up, but then it freezes with the circle in it before it fills with green to show how much it is charged, but now it atleast accepts charge. Before it didn't.
But I still wonder if I could not scan and repartition my phone with anything else than recovery mode? Perhaps I could flash a repartitioned custom Pit file with Odin if I could just scan it somehow?
I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.
froyoguy said:
I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.
Click to expand...
Click to collapse
Which rom was this?
AutumQueen92 said:
Which rom was this?
Click to expand...
Click to collapse
Thanks for your reply. Couldn't check it until last night. I was running NightOwl when this happened. Last night, I thought something and flashed the same Philz recovery through Odin and some how it worked.
I have started realizing that it is a hardware issue, since the device does not start without being connected to a power source. 1 out of 20 tries take me into recovery (of course while the device is connected to the charger, or else the screen is always black).
However, the recovery doesn't stay too long. I tried flashing a newer version of NightOwl, but while the recovery is still opening the package, the phone restarts .
One weird thing is that the phone doesn't starts without being connected to the PC or the charger. But when connected, within seconds, the offline charging screen says 100%, which is making me believe something is wrong with the hardware.
Part of the "hardware" is your battery...
I recently did the latest update to my T-mobile Note 4 upon updating the phone, the phone was in a constant boot loop and finally installed the update to the device. Upon installing the new software update to the phone it began the reboot loop and eventually started up I received one text message and it began to loop again and now it will not turn on. None of the button combinations will turn the phone on it is not accepting a charge either. I put the battery in another note 4 and it works fine and shows 79 percent of the battery is charged. What can be done to get the phone to wake up out of it's current state most of the pictures were salvaged with drop box, but it did not update from a family funeral yesterday with several pictures and those are important. Has anyone had this issue before and what was done to fix it?
nigafied45 said:
I recently did the latest update to my T-mobile Note 4 upon updating the phone, the phone was in a constant boot loop and finally installed the update to the device. Upon installing the new software update to the phone it began the reboot loop and eventually started up I received one text message and it began to loop again and now it will not turn on. None of the button combinations will turn the phone on it is not accepting a charge either. I put the battery in another note 4 and it works fine and shows 79 percent of the battery is charged. What can be done to get the phone to wake up out of it's current state most of the pictures were salvaged with drop box, but it did not update from a family funeral yesterday with several pictures and those are important. Has anyone had this issue before and what was done to fix it?
Click to expand...
Click to collapse
A few questions I would ask to be able to help would be:
Which baseband/bootloader/version were you on and which upgrade was your Note IV attempting to install?
Are you rooted or stock?
When you say that it bootlooped a bunch and then "finally installed the update", was that with no user interaction at all? seems odd to me for a bootloop to repeat and then randomly work.
If I were you and after pulling battery for 30 seconds doesnt work and holding down home+power+volume up, then try plugging it into a USB port on your computer and see if it recognizes it. Make sure your PC has latest samsung usb drivers.
Modzilla44 said:
A few questions I would ask to be able to help would be:
Which baseband/bootloader/version were you on and which upgrade was your Note IV attempting to install?
Are you rooted or stock?
When you say that it bootlooped a bunch and then "finally installed the update", was that with no user interaction at all? seems odd to me for a bootloop to repeat and then randomly work.
If I were you and after pulling battery for 30 seconds doesnt work and holding down home+power+volume up, then try plugging it into a USB port on your computer and see if it recognizes it. Make sure your PC has latest samsung usb drivers.
Click to expand...
Click to collapse
All stock the last update performed was for that security hole android had on the android 5.1.1. What I mean is that during the install the phone kept restarting and restarting and then it installed the updates and went to the home screen. When it reached the home screen it showed me one text and I went on charging the phone thinking it was normal woke up this morning the phone was off yet the battery still has 79 percent when placed in another note 4 phone. I tried plugging into the pc the phone isn't recognized because it does not turned on it says unrecognizable usb device and I installed the latest samsung drivers as well I've tried those button combinations as well as pulling the battery. I'm wondering if the update corrupted something prohibiting it from booting it doesn't take a charge either when connected to the wall it's almost like the phone is in a stale state.
nigafied45 said:
All stock the last update performed was for that security hole android had on the android 5.1.1. What I mean is that during the install the phone kept restarting and restarting and then it installed the updates and went to the home screen. When it reached the home screen it showed me one text and I went on charging the phone thinking it was normal woke up this morning the phone was off yet the battery still has 79 percent when placed in another note 4 phone. I tried plugging into the pc the phone isn't recognized because it does not turned on it says unrecognizable usb device and I installed the latest samsung drivers as well I've tried those button combinations as well as pulling the battery. I'm wondering if the update corrupted something prohibiting it from booting it doesn't take a charge either when connected to the wall it's almost like the phone is in a stale state.
Click to expand...
Click to collapse
Have you tried installing Kies on your PC to see if it can detect it? I believe it has a couple special options for detecting and repairing corrupted stock updates. http://www.samsung.com/us/support/owners/app/kies
Modzilla44 said:
Have you tried installing Kies on your PC to see if it can detect it? I believe it has a couple special options for detecting and repairing corrupted stock updates. http://www.samsung.com/us/support/owners/app/kies
Click to expand...
Click to collapse
I haven't tried kies I tried smart switch though and the phone wasn't detected I'll try kies as well. I'll be back with an update appreciate the help.
Kies didn't work because the phone can't be recognize by the program the computer makes a noise knowing when the phone is connected but the screen on phone doesn't turn on I can't even get it to boot up or accept a charge and the battery is nearly full given that I put it in another phone to check. I've tried even starting the phone up with no battery using direct charger as primary source but it didn't work. I'm not sure how the update fried my phone, but I'm going to be losing some important pics drop box didn't sync yesterday during a family funeral.
That is just really ****ty luck. They say there is always a small chance that flashing anything can cause epic partition disasters. If kies is detecting it but saying it's unable to connect then I'd say the phone is toast. You might be able to get Odin to recognize it and reflash the entire ROM, but that would obviously destroy any data you had on the device previously. Might look into doing an adb pull or backup but being realistic with expectations, I'd say the chances of them working considering what you've done is minimal.
Since you're on stock anyways I'd just go warranty exchange it if you can. Not worth dicking around with Odin if you are stock.
Sorry I couldn't be more help but I would take this opportunity to seriously get yourself a cloud based automatic backup so you don't have to worry about these things anymore. I had something similar happen to me and I lost all my data and now it all syncs to my ex_sdcard and Dropbox haha..can never be too sure
Sent from my SM-N910T using Tapatalk
Yeah I never flashed anything it was an over the air update basically that went bad. The last time I flashed software using odin I didn't lose any of my information it stayed on the internal memory and was there still. It truly is sad they roll out an update over air and it bricks your phone makes no sense.
Modzilla44 said:
A few questions I would ask to be able to help would be:
Which baseband/bootloader/version were you on and which upgrade was your Note IV attempting to install?
Are you rooted or stock?
When you say that it bootlooped a bunch and then "finally installed the update", was that with no user interaction at all? seems odd to me for a bootloop to repeat and then randomly work.
If I were you and after pulling battery for 30 seconds doesnt work and holding down home+power+volume up, then try plugging it into a USB port on your computer and see if it recognizes it. Make sure your PC has latest samsung usb drivers.
Click to expand...
Click to collapse
I have gotten the phone to turn on randomly it turned on and is now regularly turning on however it is still in a bootloop will not allow me to enter recovery I can enter custom OS have tried to root but it flashes and does not stick with phone for the custom recovery I'm not sure what I can do now that the phone turns on any suggestions?
When trying to root or enter recovery I get recovery is not Seandroid enforcing set warranty bit recovery and boot loop
Have you tried connecting it to kies again to see if it will repair the corrupted flash? If not, Google your bootloader and Odin flash the full stock firmware
Sent from my SM-N910T using Tapatalk
Modzilla44 said:
Have you tried connecting it to kies again to see if it will repair the corrupted flash? If not, Google your bootloader and Odin flash the full stock firmware
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I have a t-mobile 910T note 4. I will try kies again not sure what my bootloader is or was I'm just trying to do what ever i can to preserve the data on phone will flashing stock again delete the internal I know with root with my other note 4 it didn't. This phone was never rooted the over the air update boot looped the phone
I would definitely try using kies or even adb from command to see if you can pull the data from it. Flashing a full firmware will wipe all data Yeah so I'd use that as a last resort
Sent from my SM-N910T using Tapatalk
Not to sound stupid what's an adb command
Modzilla44 said:
Have you tried connecting it to kies again to see if it will repair the corrupted flash? If not, Google your bootloader and Odin flash the full stock firmware
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
On this forum I have found just the bootloader available to down load if I download the full rom is it going to wipe the internal memory here is the link I'm referring to http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
I think I might have it figured out just need clarity on if flashing just the bootloader will do the trick I also got a set warranty kernel on boot last time as well.
If it were me I'd install the following:
Twrp custom recovery : https://www.androidfilehost.com/?fid=24052804347792887
Make sure you have latest drivers from Samsung. Flash twrp and see if you can boot into recovery and then either wipe cache or flash a bootloader zip from there. At the very least you could pull files from it once in recovery
Sent from my SM-N910T using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:10 AM ----------
If that doesn't work then I'd read this guide on adb setup and commands. It seems daunting at first but incredibly useful
http://forum.xda-developers.com/showthread.php?t=2225405
Sorry I'm a bit short on explanation I'm just short on time. If you need anything more specific in terms of clarification don't hesitate to ask.
Sent from my SM-N910T using Tapatalk
I would visit your local tmobile store and have them look at it. Besides smartswitch they have a program they can run and possibly restore your phone before it gets totally borked up.
This could help justify rma with Samsung.
Pp.
My phone was dead. I used the original note 4 cable and it worked like a charme was able to odin to stock (new firmware) and root. I dont see any way out other than loosing all data
Sent from my SM-N910T using Tapatalk
This is what I see when I flash the root or recovery every single time. I know if I can get the recovery on the phone I can get the pictures on to my pc because I had a phone that was android locked that I did myself and rooted recovery and was able to get the pc to see and transfer files to pc so why is it showing this image am I doing something wrong?
PanchoPlanet said:
I would visit your local tmobile store and have them look at it. Besides smartswitch they have a program they can run and possibly restore your phone before it gets totally borked up.
This could help justify rma with Samsung.
Pp.
Click to expand...
Click to collapse
They don't have that machine any more I use to work at t mobile that machine was a joke by the way I'll be able to get a replacement it's the funeral pictured that are most important to me they didn't sync to drop box for some reason and that's my main reason for trying to get the phone working. I've flashed everything I've been told to flash I still get the boot loop and the stupid se android reinforcing set recovery or set kernel etc currently it's recovery if I try to initiate recovery via the buttons it just boot loops
Save your dead/bricked device! Overall a straightforward process. Simple recovery using SD card to load correct bootloader and be able to ODIN stock firmware.
Successfully performed on a locked bootloader Note 4 from Verizon, using another locked bootloader Note 4 from Verizon. Should be equally possible with other devices as well as the T Flash function does not check the device model, and writes the entire firmware, according to the included or specified PIT file into the SD card.
Requirements:
Secondary Samsung device with working download mode and microSD slot
Odin version appropriate to the firmware version you are trying to install
16+ GB microSD card
Samsung drivers installed on your PC
Steps:
1) Find and download the correct FULL firmware for your device, of the same or newer version than was on the device previously. These are frequently available from AFH, amongst other sites. A "repair firmware" may be sufficient ONLY IF IT INCLUDES ABOOT and BOOT partitions.
2) Download the correct version of Odin for your firmware
3) Open Odin, set up your full firmware into the AP/PDA slot.
4) Tick the T Flash option in the settings.
5) Insert a 16+ GB card into the SD slot on your working Samsung device
6) Boot into download mode, and connect to computer. Ensure the device shows up in Odin. If not, check drivers and restart (and reconfigure) Odin.
7) Start flash. It may fail at a certain point but this is OKAY. As long as the ABOOT and BOOT partitions have flashed, the procedure will work.
8) Remove SD from the working device and insert it into the bricked device.
9) Hold VOLUME DOWN + HOME + POWER, or use a USB jig to enter into download mode on the dead device. It will now magically work, as it reads the partitions from the SD card.
10) Reflash the correct firmware in Odin to the bricked device.
Hope I was able to help. Do note that this will NOT solve issues with your device if it has PHYSICAL eMMC issues (cracked solder balls, bad chip, bad connections, etc, etc).
The "magic" SD card will only work on the device it was intended for. Don't attempt "miracles" by say, trying to boot firmware intended for a different model on your device. That may cause permanent damage, for which I will not be held responsible.
This tutorial should be equally acceptable for other devices. I am posting it here because it worked successfully on my Note 4, and I'm assuming other people here may have the same issue. Originally I tried this on an S5 with heavy motherboard damage, which would only render a download mode screen, but would not flash anything to the device.
Anyone with an interest in making a donation, please contact me for donation info or donate to your charity of choice
Most information presented here is publicly available but there was no simple/accurate way detailing the process, so I assumed it would be nice to have all info aggregated in one place.
Please, please, please - I have a hard bricked N910F (no recovery, no download, no power). Can you send me the files to unbrick it?
Thanks in advance
These guides are all well and good
The problem is most people don't have a secondary note 4.
It'd be best if people w/ different models of this phone (SM-N910W8 , SM-N910F, Etc.) could upload image files here & form a directory. There isn't a definitive hard brick solution guide on this site because people won't do that.
Exactly. If only someone with a working Note 4 could create a SDCard restore image and share it. The procedure is simple, safe and would take 30 minutes. It would help a LOT of people.
✔ Auto Reboot
✔ F.Reset Time
✔ T Flash
So I need to Tick those 3 or ONLY T Flash on Odin3 v3.09?
2 of my colleagues had hard brick their Note 4 SM-N910G and they have zero knowledge about rooting. The phone cannot :
➡ Switched ON
➡ No Red LED light while charging
➡ No battery icon when changing
➡ QHSUSB_BULK when connected to PC
Can your method solve the problem? I do have a few friends who are using Note 4 so I guess if this works, I can borrow one of the working phones to do the 'MAGIC' SD Card..
bietoff0728 said:
Auto Reboot
F.Reset Time
T Flash
So I need to Tick those 3 or ONLY T Flash on Odin3 v3.09?
2 of my colleagues had hard brick their Note 4 SM-N910G and they have zero knowledge about rooting. The phone cannot :
Switched ON
No Red LED light while charging
No battery icon when changing
QHSUSB_BULK when connected to PC
Can your method solve the problem? I do have a few friends who are using Note 4 so I guess if this works, I can borrow one of the working phones to do the 'MAGIC' SD Card..
Click to expand...
Click to collapse
Leave everything checked the way it is when Odin first opens. Then check off T Flash. Don't change anything else.
Symptoms sound identical to this Note 4. It should be possible to save it.
dwegiel said:
Save your dead/bricked device! Overall a straightforward process. Simple recovery using SD card to load correct bootloader and be able to ODIN stock firmware.
Successfully performed on a locked bootloader Note 4 from Verizon, using another locked bootloader Note 4 from Verizon. Should be equally possible with other devices as well as the T Flash function does not check the device model, and writes the entire firmware, according to the included or specified PIT file into the SD card.
Requirements:
Secondary Samsung device with working download mode and microSD slot
Odin version appropriate to the firmware version you are trying to install
16+ GB microSD card
Samsung drivers installed on your PC
Steps:
1) Find and download the correct FULL firmware for your device, of the same or newer version than was on the device previously. These are frequently available from AFH, amongst other sites. A "repair firmware" may be sufficient ONLY IF IT INCLUDES ABOOT and BOOT partitions.
2) Download the correct version of Odin for your firmware
3) Open Odin, set up your full firmware into the AP/PDA slot.
4) Tick the T Flash option in the settings.
5) Insert a 16+ GB card into the SD slot on your working Samsung device
6) Boot into download mode, and connect to computer. Ensure the device shows up in Odin. If not, check drivers and restart (and reconfigure) Odin.
7) Start flash. It may fail at a certain point but this is OKAY. As long as the ABOOT and BOOT partitions have flashed, the procedure will work.
8) Remove SD from the working device and insert it into the bricked device.
9) Hold VOLUME DOWN + HOME + POWER, or use a USB jig to enter into download mode on the dead device. It will now magically work, as it reads the partitions from the SD card.
10) Reflash the correct firmware in Odin to the bricked device.
Hope I was able to help. Do note that this will NOT solve issues with your device if it has PHYSICAL eMMC issues (cracked solder balls, bad chip, bad connections, etc, etc).
The "magic" SD card will only work on the device it was intended for. Don't attempt "miracles" by say, trying to boot firmware intended for a different model on your device. That may cause permanent damage, for which I will not be held responsible.
This tutorial should be equally acceptable for other devices. I am posting it here because it worked successfully on my Note 4, and I'm assuming other people here may have the same issue. Originally I tried this on an S5 with heavy motherboard damage, which would only render a download mode screen, but would not flash anything to the device.
Anyone with an interest in making a donation, please contact me for donation info or donate to your charity of choice
Most information presented here is publicly available but there was no simple/accurate way detailing the process, so I assumed it would be nice to have all info aggregated in one place.
Click to expand...
Click to collapse
did this method work
Wow this is very useful info, If it works.
So @dwegiel, your stating that by ticking T-flash, that tells Odin to flash the bootloader over to the sd card. Which you can then use to boot any note 4 of the model you flashed.
If this is so, then we should be able to make a disk image file to share for each model. That would be great!
Thanks for the info!
Samsung SM-G910S HArd Bricked
Samsung SM-G910S HArd Bricked
@dwegiel i can successfully say that your method work on my Note edge N915V @aaron74 you are also correct that can be done....................but we would of to create the debrick image for all the "OS" version are else it wont work an you cant do it with any Samsung phone it as to be done with the same phone.................meaning if you want to create one for a Note 5 you of to use a note 5 (carrier doesn't matter)
I'm in this situation with my N910G, I have a working one but I don't want to change it, will this alter the working device in any way?
no i wont
Is it possible to recover a hard bricked Note 4 when it won't stay on for more than a few minutes and/or freezes.? I got most of the way through rooting it but it shut down before completion. Reason I wanted to root it was because it got stuck in a bootloop following a recent OTA security upgrade. Running Marshmallow 6.0.1. Incidentally sometimes when it boots up it gets stuck at the Samsung screen but there is a yellow message top left - Set Warranty Bit Kernel. When I read up on this it said knox was tripped, but this was before I had even tried to root it. Thx
bietoff0728 said:
Auto Reboot
F.Reset Time
T Flash
So I need to Tick those 3 or ONLY T Flash on Odin3 v3.09?
2 of my colleagues had hard brick their Note 4 SM-N910G and they have zero knowledge about rooting. The phone cannot :
Switched ON
No Red LED light while charging
No battery icon when changing
QHSUSB_BULK when connected to PC
Can your method solve the problem? I do have a few friends who are using Note 4 so I guess if this works, I can borrow one of the working phones to do the 'MAGIC' SD Card..
Click to expand...
Click to collapse
My 910G is also in the same situation no download mode nothing complete dead phone
Have ypu found the solution plz let me know
I have an F variant (see screenshot for info) . If of any use dont mind uploading an SD backup if anyone up to say the steps needed to be taken..
Hi, i have the sm-n915fy, can anyone just send me a sd image of a stock rom for my phone
Bonez355555 said:
@dwegiel i can successfully say that your method work on my Note edge N915V @aaron74 you are also correct that can be done....................but we would of to create the debrick image for all the "OS" version are else it wont work an you cant do it with any Samsung phone it as to be done with the same phone.................meaning if you want to create one for a Note 5 you of to use a note 5 (carrier doesn't matter)
Click to expand...
Click to collapse
Is there anyway you could send me your image? I can't find anyone else with the Note edge, and I have family photos I want to restore
Has anything else been done with this? Is there a thread for downloading this SD card files?
"It will now magically work,"
As said it really worked for me today for my samsung galaxy note edge(SCL24 SM-915J) dead for 10 months.
At first it didn't worked because my current SCL24 has updated android version . Then I bought another SCL24(now,I have yes 3 working SCL24.)
What I did before trying this thread.
I tried Freeze method for 5 mins, 10 mins, 20,30 , 1 hr, 2,4,.....12 hours, 1 day too. But, it didn't work.(Last year like 5, 10, 20 min was workind for me)
Then I used the cardboard method to attach to my emmc for solving my error reading emmc yesterday, it didn't work either.
But, today this thread worked.Wow thank you so much.