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
Related
Was trying to flash to 2.3.3 from my Phoenix ROM. It froze at setup connection for about 30mins so I battery pulled and read about the disabled 3 button users should go back to stock 2.1 before flashing to GB, so I attempted to use OneClick Odin. It was stuck at sbl.bin(bootload file if im not mistaken). I waited and battery pulled again. When I press power nothing happens, however I can still get into DL mode. Should I keep trying to use oneclick, or is the phone shot?
Holy poop! You can get into download mode! That's, well not lucky I guess, cause its all F'ed up atm, but you are not bricked.
Make sure the chord is good, and its plugged into the back of the pc, if it already is switch ports, reboot and try again.
Use this package http://forum.xda-developers.com/showthread.php?t=995143 it doesn't have any bootloaders so bricking is very very difficult.
Good luck.
Downloading it now, if it works, you're a genius. If it doesn't work...well, lets be serious, you're a member of Phoenix: you're still a genius
Will update in a bit.
jabarri1 said:
Downloading it now, if it works, you're a genius. If it doesn't work...well, lets be serious, you're a member of Phoenix: you're still a genius
Will update in a bit.
Click to expand...
Click to collapse
Awww ... Warm and fuzzies! Thanks man, but I'm really nothing special learned everything by reading xda.
Ok back on topic. You got really lucky you're right sbl.bin is a bootloader your risk of brick was pretty high ... But you got into download mode after ... Any sign of life is not a brick. I'm 99% certain this will work. Only reason it won't is, your connection is faulty somewhere in the chain. But with that package it can't get any worse than it is.
Thank you very much! Got it to actually boot into recovery. I assume I can now insert my SD and apply the stock update.zip? Since it wont actually boot to the phone menu screen?
I'm not sure what's in the update.zip you still have the gb bootloaders if it has just one froyo bootloader and not both, you will brick the phone. Look in the update folder of that zip, if you see only boot.bin or only sbl.bin don't flash it. If you see both or neither its ok. Although I would just use that odin package I linked you to.
I did use the Odin package you linked. Thats how it was able to boot into recovery and also clockwork recovery, but it just wont full boot. I cant view anything thats on the internal memory card, so I cant see the update.zip files. Ive heard you can access the memory card from recovery by mounting it through CWM and accessing it through ADB however I have yet to be able to get my computer to recognize my phone during recovery mode.
Edit: After playing around a bit with uninstalling/reinstalling drivers, got odin to work and its back to stock! thanks again stud
Now to try to 2.3 it again lol
Hey guys,
I tried to update my girlfriends Galaxy S today from Darky's rom to Miui, I tried to remove the lagfix by following the instructions through recovery.
However, after the phone rebooted it now displays the Galaxy S logo, then simply vibrates periodically (every 5 seconds, than every 12 - not that I think this matters).
Does anybody have a clue what I've inadvertently done and how to recover the device - preferable without wiping the data on-board.
Thanks in advance guys.
Just an update, it's clearly a soft brick. I can still get into download mode and recovery, it did a backup before it rebooted however I've tried to restore this backup and still no joy - although I do now get the old rom's boot animation back which is stuck on an endless loop with the phone vibrating in the background.
You probably won't be able to fix it without a wipe. You should still be able to get into download mode, so you can flash a full ROM with Odin. You need to use a .PIT file and make sure repartition is checked as the file system is probably broken.
DrFredPhD said:
You probably won't be able to fix it without a wipe. You should still be able to get into download mode, so you can flash a full ROM with Odin. You need to use a .PIT file and make sure repartition is checked as the file system is probably broken.
Click to expand...
Click to collapse
Yeah miui uses a different file system so you have to undo that as described above. Then you may be able to restore the backup.
Sent from my GT-I9000M using XDA Premium App
After you guys pointed me in the right direction and a little more digging I ended up stumbled across galnet's Miui thread and his instructions through there.
To cut a long story short the phone's now running Miui and I'm not in the dog house, thanks for the help guys.
Where would I get a JTAG repair?
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 tired rooting my t-mobile s6 [SM-G920T] running on 5.1.1 last night with the method outlined by the following thread:
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002
it took me a few attempts, but i thought i finally got root... it turns out my digitizer's x-axis somehow got messed up during some process [when i touch the right side of the screen, it selects left, and vise-versa]
now i can't even turn on my phone... when i try, the splash screen simply tells me "kernel is not seandroid enforcing" and "custom binary blocked by FRP lock"
i tried taking it back to the t-mo store since i just got the phone yesterday, but "no exchanges on rooted devices...":crying:
is there any way for me to fix my problem? please advise, thank you.
Try Odin my friend or smart switch..
Sent from my SM-G920T using XDA Free mobile app
since i upgraded to 5.1.1 before i attempted all this, i need the G920TUVU2COF6 md5 file... i was using the 5.0.2 version: G920TUVU1AOCG
maybe that is why it kept failing... i am downloading the right version right now and will give it a try.
i really hope it works... if not, i don't know what else i can try
You flashed twrp recovery for the G925T edge.
Try this before doing anything else. If it works, thank edgarf28.
The next time you flash something, double check that it is correct for your phone before flashing :good:
sublimaze said:
You flashed twrp recovery for the G925T edge.
Try this before doing anything else. If it works, thank edgarf28.
The next time you flash something, double check that it is correct for your phone before flashing :good:
Click to expand...
Click to collapse
i tried that, but no success...
i was able to odin the 5.1.1 file, but the digitizer was still messed up.
but now with a bootable stock rom, i took the phone into the store and they exchanged it for me in 15 minutes.
Was it booting into odin? These situations are weird because if odin reads and the phone at least boots to Samsung screen I try and have succeeded on all occasions at un-soft-bricking.
i was able to put the phone into download mode... since i updated to 5.1.1 before i began the root process, i had to use the G920TUVU2COF6 md5 file instead of the G920TUVU1AOCG in odin to restore.
dnaL0R said:
i was able to put the phone into download mode... since i updated to 5.1.1 before i began the root process, i had to use the G920TUVU2COF6 md5 file instead of the G920TUVU1AOCG in odin to restore.
Click to expand...
Click to collapse
you can recover your phone using stock G920TUVU2COF6, i recovered my phone from same issue.
Anyone please help. I am fairly new too the whole Android scheme of things and everywhere I look I see gibberish all talk about Roms and flashes and I don't know what to do. I have a Galaxy Note 4 in a rebbot loop, I tried to root with this thing called kingo root. And I rebooted my phone and it doesn't turn on it goes to the T-Mobile screen then powers off and repeats the process. I need to know how to factory reset the phone. I already tried to wipe the phone in recovery and same problem. I don't want a root or custom OS I just want to get the phone working. And as dumb down as possible. I'm so used to the one click jailbreak on iPhone and not the complexity of rooting and it screwed me over. I just want to know how to reset the phone and get it working.
Thanks
Lollipop 5.1.1 was what it was running and I have an SD Card if I need to reset from external since ik that's an option.
Nicholasgh said:
Anyone please help. I am fairly new too the whole Android scheme of things and everywhere I look I see gibberish all talk about Roms and flashes and I don't know what to do. I have a Galaxy Note 4 in a rebbot loop, I tried to root with this thing called kingo root. And I rebooted my phone and it doesn't turn on it goes to the T-Mobile screen then powers off and repeats the process. I need to know how to factory reset the phone. I already tried to wipe the phone in recovery and same problem. I don't want a root or custom OS I just want to get the phone working. And as dumb down as possible. I'm so used to the one click jailbreak on iPhone and not the complexity of rooting and it screwed me over. I just want to know how to reset the phone and get it working.
Thanks
Lollipop 5.1.1 was what it was running and I have an SD Card if I need to reset from external since ik that's an option.
Click to expand...
Click to collapse
Look on here how to Odin 5.1.1. Thatll give you a fresh start. I suggest staying away from kingoroot or king root. Use cf-autoroot.
Sent from my SM-N910T using XDA Free mobile app
This could help you also - you could try to re-root and flash the kernel in this video that should get you going.
https://www.youtube.com/watch?v=nDCTQtCaUig
Look for a program called odin 3.10 and dl it to deaktop. Then dl 5.1.1 firmware . Also dl twrp 2.8 or higher . Once you have everything put phone into dl mode by holding power ,home and volume down. Once in dl open up odin and connect your phone to computer. Click pda and look for the twrp and flash it. Once done put phone into recovery by pressing power,home and up volume. Once in recovery wipe to factory reset. Now put phone back into dl mode and do the same with the firmware you dl. Make sure you extract the 5.1.1 file and it's a tar so you can flash it. Once it's ready flash the tar and you should be back to stock with no problem.
Sent from my SM-N910T using Tapatalk