Database Develop

[Q] Flashing always stops at data.img/datafs

I made a wipe data/factory reset while on CWM Touch (I didn't know about the issues yet) and, of course, it didn't work. So now, everytime I try and flash an Odin ROM (because it doesn't work with the recovery), it gets stuck at data.img/datafs so there's no way I can boot my phone although it does have recovery, download and it gets to the Samsung bootscreen (I flashed a stock ROM).
Has anyone got any ideas on how to fix this? Thanks

Tried clearing cache and data while on recovery? Which rom/kernel are you on?
Sent from my GT-N7000 using XDA

praetorius said:
Tried clearing cache and data while on recovery? Which rom/kernel are you on?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I was on AOSP ICS v04 with the infamous AbyssNote 1.2 kernel (but I don't have the same factoryfs problem as the others) with Touch CWM (that's where the problem comes from I believe) and the only problem is that neither Odin nor CWM can access the /data partition. So a wipe doesn't work.

I fear the nearest Samsung service is the way to go for you, mate. Your data partition is corrupted beyond repair.
Believe me, the guys affected with Angelom 1.2 had tried everything, including jigging, jtagging and nothing helped unbrick their phones. It looks like replacing the motherboard is the only solution.
Sorry to have to tell you this.

chasmodo said:
I fear the nearest Samsung service is the way to go for you, mate. Your data partition is corrupted beyond repair.
Believe me, the guys affected with Angelom 1.2 had tried everything, including jigging, jtagging and nothing helped unbrick their phones. It looks like replacing the motherboard is the only solution.
Sorry to have to tell you this.
Click to expand...
Click to collapse
Are you sure? Even though it's never stuck at factoryfs and it only bootloops? Because the problem is I have no service center I can go to so sending it via La Poste (in France) isn't exactly what I'd call safe... Or is there a way to send iut directly to Samsung and get a new one?

Up.............

Since it looks like a partition problem - have you tried using stock .pit file and repartition with ODIN ?

Akiainavas said:
Since it looks like a partition problem - have you tried using stock .pit file and repartition with ODIN ?
Click to expand...
Click to collapse
Yes I did. Well I think imma have to send it to a samsung repair center. How long does it take to get a new Note?

Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.

nico53laval said:
Yes I did. Well I think imma have to send it to a samsung repair center. How long does it take to get a new Note?
Click to expand...
Click to collapse
According to warranty agreement:
"Repairs are done as fast as possible, but within 14 days time."

no id agree with what the guys have told you, looks like a service center job, did you just flash this recently or were you one of the users who flashed it weeks back, and youve only just attempted a wipe now??
Just out of curiosity, if people have this kernel installed, can they flash to a diff kernel b4 trying a wipe, or will that not work.

graemeg said:
Just out of curiosity, if people have this kernel installed, can they flash to a diff kernel b4 trying a wipe, or will that not work.
Click to expand...
Click to collapse
You're fine if you don't do any wipes prior to flashing another kernel. However, wipe anything and it's curtains.

chasmodo said:
You're fine if you don't do any wipes prior to flashing another kernel. However, wipe anything and it's curtains.
Click to expand...
Click to collapse
Exactly :/ I was fine for weeks then I wiped before installign another ROM and boom...

dirk271 said:
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
Click to expand...
Click to collapse
Too late ^^ I sent it to a repair center.. But I don't think it would have worked. I already did a wipe on a tock rom with stock recovery and it worked but the phone still couldn't boot.

Akiainavas said:
According to warranty agreement:
"Repairs are done as fast as possible, but within 14 days time."
Click to expand...
Click to collapse
The problem is that in France the repair centers have an agreement with Samsung but they're not directly related to Samsung so do you think it'll only be 14 days (even though I might neeed a new mobo or a new phone)?

Not sure how youre postal system works there but make sure you get recorded delivery or france similar so you have proof of posting etc.
Also considering the issue ive read most times lads have had a quick turn around, but who knows, depends how fast samsung receive it, i would suggest UP TO 2 weeks, more likely a week, but then it me be 2 week, depends what they have to do to repair it.
I recently took a phone to the o2 shop to be repaired, i received it back via post 4 days later, that was really fast, and im quite lucky here that theres an abundance of walk in repair centres around the uk, it just made me wonder if there one close to you and would it be economical to take it in person, samsung repair shop where i live if ya take your phone in by hand theyll usually say come back in a couple of hours and then they fix it there and then, that would be better for you because you arent messing around with posting then, i know a lot of countries guys dont have that option but i would have thought france and germany would be similar to the uk as they are both quite large mobile manufacturing countries so my fingers are crossed for you that you can find a quick solution.

No idea mate, but you shouldn't wait more than 2 weeks. The repair will take one hour probably, the rest is testing, posting, filling papers etc.
You'll probably have it back after 1 week or so. So let's hope you'll received it fixed as soon as possible.

nico53laval said:
Exactly :/ I was fine for weeks then I wiped before installign another ROM and boom...
Click to expand...
Click to collapse
Oh, I see. Should've read angelom 1.2 thread first.... sorry
Good luck with service.

dirk271 said:
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
Click to expand...
Click to collapse
what stock rom? which version you used?

[Q] Trying to rescue a bricked Note, help is appreciated!

I have a note here...its bricked, the owner tried flashing angelrom ICS, and bricked it.
It gets stuck when it starts writing factoryfs.img.
I have tried properly repartitioning it, installed a stock bootloader from a gt-n7000 stock rom, and that at least allowed me to get back into android system recovery. I wiped the data and cache and tried again.
I tried a stock rom that had multiple parts, and one that had the individual parts. I can flash all of the individual parts successfully but the PDA.
Anybody encounter this, and know a fix? I would really appreciate any tips or suggestions.

Just wanted to give some more information. I followed Ketan's guide to flash to stock rom, and tried multiple stock roms with the same results.
So I also tried repartioning with the proper pit file (the 16gb n7000) and that didn't work.
The only bootloader I could seem to find (because that was the next logical step to me) was "KERNEL_N7000XXKJ1_CL627135_REV02_eng_mid_ship.tar.md5" , would that be compatible with all stock roms or just a specific one?

I am sorry bro. You fried your flash drive, there is no way to revive it. The motherboard has to be replaced.
There isn't anything one can do if you flashed that kernel. If you have warranty head to Samsung service.

Yep, anilisanil is right. People who had found themselves in the same predicament tried absolutely everything, but there was no cure whatsoever. Data partition corrupted beyond repair, not even JTAG could help.
Motherboard replacement is the only thing that can be done.

anilisanil said:
I am sorry bro. You fried your flash drive, there is no way to revive it. The motherboard has to be replaced.
Click to expand...
Click to collapse
chasmodo said:
Motherboard replacement is the only thing that can be done.
Click to expand...
Click to collapse
+1
Sorry, it seems You have no option but to go service centre.

chasmodo said:
Yep, anilisanil is right. People who had found themselves in the same predicament tried absolutely everything, but there was no cure whatsoever. Data partition corrupted beyond repair, not even JTAG could help.
Motherboard replacement is the only thing that can be done.
Click to expand...
Click to collapse
How the duck is that physically possible? What an enormous embarrassment for angelom. I doubt hell ever post another kernel again...
Sent from my superior GT-N7000 using Tapatalk

Yeah...I figured it was beyond hope after reading through a lot of the threads....
I did reset the counter with a jig, and took away the yellow triangle...but I was told samsung won't warranty this model in the USA.
Thanks for your replies!

Just a little query. Whats the actual physics behind this? Like how can some software fry the drive? Just a little interested and wondered how it actually physically happened. Because my assumption before all this was that it cant be truly completely bricked (obviously i was wrong). but wondering how!
Sent from my GT-N7000 using Tapatalk

[Q] Super Bricked Gnote Revived But Lost Memory

Hello Dear friends,
This is Alvina Snow, a nooby nooby noob girl, who once liked to play with phones and would make fun of her buddies, carrying the stereo-typed GB versions on thier Note. I am no more interested in flashing Roms and not because i blame developers. They have always been great in thier job and i owe them for their coolest roms, but i blame myself and my hastiness in everything. Cutting the crap, let me come to the point.....
Last night, tired of the mediocre looks of Official ICS, i downloaded Paranoid Android 0.4a along with goodies and following the instructions, I opened Odin to downgrade to GB so i can install PA 0.4a safely. To my surprise, once the GB Rom installed successfully, it got stuck at bootloader, i rebooted it a few times, then i went to recovery and reset factory/ format, wiped cache and rebooted. Note stuck this time on the first screen. :fingers-crossed:
Presuming that Odin install may have been faulty, i redid the Odin method and this time, the install stuck at "factoryfs.rfs". From then on, i tried for hours to make it happen, swapped roms, used kernels, wiped everything... and ultimately i got a nice super brick on my hands. the notorious mobile-cum-triangle-cum-PC sign, asking me to use recovery through kies.
researched XDA all night and finally landed on Dr. Forest's "Easy guide for repartition workaround to fix super-brick Note"
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Did everything as directed. I used "standard 16 GB pit" and stable GB rom to resurrect my Note and we both came to life to my surprise, only to discover that now i have an 8.24 GB emmc space available, instead of previously held 11.4 GB something. :victory:
I have been praying for Dr. Forest and all esteemed developers and i will always be thankful to them. My questions to my learned seniors is that:-
- Is there any method, adopting which the missing 3 GB should be regained?
- Will I ever be able to regain the missing 3GB space?
- Having this notion in mind that now i have caged 3 GB of voracious malfunctioning space in my emmc, should i expect any further stability issues after revival of Note or it should work just fine.
Once again hats off to Dr. Forest and all other developers for thier compassionate assistance for us noobs. My thanks in advance for help. :angel:
-

alvinasnow said:
Hello Dear friends,
This is Alvina Snow, a nooby nooby noob girl, who once liked to play with phones and would make fun of her buddies, carrying the stereo-typed GB versions on thier Note.
Did everything as directed. I used "standard 16 GB pit" and stable GB rom to resurrect my Note and we both came to life to my surprise, only to discover that now i have an 8.24 GB emmc space available, instead of previously held 11.4 GB something. :victory:
I have been praying for Dr. Forest and all esteemed developers and i will always be thankful to them. My questions to my learned seniors is that:-
- Is there any method, adopting which the missing 3 GB should be regained?
- Will I ever be able to regain the missing 3GB space?
- Having this notion in mind that now i have caged 3 GB of voracious malfunctioning space in my emmc, should i expect any further stability issues after revival of Note or it should work just fine.
Once again hats off to Dr. Forest and all other developers for thier compassionate assistance for us noobs. My thanks in advance for help. :angel:
-
Click to expand...
Click to collapse
Thanks for the kind words which is a lovely reward to the people who contribute time and knowledge to the guides to help revive brick G-Note, including me :victory:!
I will try to answer some of the questions:
1- So far there has not been a known method to fix the faulty areas in the partition caused by the buggy ICS kernel yet. There seem to be some encouraging news from some senior developers who are in contact with Samsung developers and it is hope that there may be a Jtag method release. If the method is available then your device can also benefit from it since the re-partition is fully reversible. Let's just hope they can make it.
2- Will the phone be stable or not: for most people it seems to work well and stable. For some people who have a large damaged areas of space in former sdcard region due to the bug, there seem to be some problem of unstable system. In those cases it is likely that there are still some faulty blocks somewhere in cache or data partitions that has not been eliminated yet.
3- If you are comfortable with using adb method you can try again to explore the lost areas and in some cases can regain 1 or 2 GB of space. There is a free app call "eMMC Brickbug Check" from Gplay which can help to scan the whole chip and report the beginning of faulty blocks. Then you can use parted to make partitions in different areas within the lost range (from 281mb to 3322mb) while try to avoid the faulty blocks.
Hope it helps in some ways. cheers.

Thanx a Ton
Ex expected you came to my rescue and encouragement Sir Forest. . Thanx a million for taking time to answer my queries. I hope that Samsung will soon come up with some remedy. As advised by you, i will also try to use the regain method. Though am not sure
Thank you

forest1971 said:
3- If you are comfortable with using adb method you can try again to explore the lost areas and in some cases can regain 1 or 2 GB of space. There is a free app call "eMMC Brickbug Check" from Gplay which can help to scan the whole chip and report the beginning of faulty blocks. Then you can use parted to make partitions in different areas within the lost range (from 281mb to 3322mb) while try to avoid the faulty blocks.
Click to expand...
Click to collapse
Forest Sir, as you advised i used eMMC Brickbug Check", which says that:
Phone Model: Samsung GT-N7000
eMMC Chip
type: VYLOOM
Date: 03/2012
CID:15010056594c30304d19b9c9013c3fdd
FwRev: 0x19
Brick Bug? : YES. Insane Chip
Now when i check memory.. it started checking and showing something similar to seconds counting and the phone restarted after reaching 671 seconds..
Now pardon my noobness, but i am not clear if how am i gonna get help in determing defected areas out of this.
Help please. God Bless You

alvinasnow said:
Forest Sir, as you advised i used eMMC Brickbug Check", which says that:
Phone Model: Samsung GT-N7000
eMMC Chip
type: VYLOOM
Date: 03/2012
CID:15010056594c30304d19b9c9013c3fdd
FwRev: 0x19
Brick Bug? : YES. Insane Chip
Now when i check memory.. it started checking and showing something similar to seconds counting and the phone restarted after reaching 671 seconds..
Now pardon my noobness, but i am not clear if how am i gonna get help in determing defected areas out of this.
Help please. God Bless You
Click to expand...
Click to collapse
No, not yet all. In this case it does not allow to see where the faulty block is.
If you are confident and like to play again with adb then can explore using parted to create new partitions again in different ranges, with part 9 starting from 1174mb, and then move up by 300mb each time until parted is happy with the new area for part 9. with that approach you will probably save more space.
Otherwise, a external sdcard can also compensate more than all the loss of space in the internal sdcard . cheers.

Thank You Sir Forest for ur guidance. I think its time to get me a 32 GB micro sd

Amen !! I only use my internal SD to hold my Mods and ROMs, all the precious stuff is on the external, Just incase.
Plus i have dropbox and google drive to keep my stuff regularly backed up

azzledazzle said:
Amen !! I only use my internal SD to hold my Mods and ROMs, all the precious stuff is on the external, Just incase.
Plus i have dropbox and google drive to keep my stuff regularly backed up
Click to expand...
Click to collapse
Yea Sir, after getting bricked, I know realize its the best way to handle the unseen
Long Live my Seniors... Owe you people very much.:good:

alvinasnow said:
Thank You Sir Forest for ur guidance. I think its time to get me a 32 GB micro sd
Click to expand...
Click to collapse
If you get that 32GB micro-SD, you can use it as your phone's internal SD card with an easy vold.fstab swap. Your reduced capacity internal storage would then become your "external" SD card.
Sent from my GT-I9300 using XDA Premium HD app

Mister_Mxyzptlk said:
If you get that 32GB micro-SD, you can use it as your phone's internal SD card with an easy vold.fstab swap. Your reduced capacity internal storage would then become your "external" SD card.
Click to expand...
Click to collapse
:victory: Ahaa. Another good news after being delved in miseries for a full day. Let's google the Vold.fstab Swap.
Thank you Mister Mxyzptlk

My Options.
Considering my options, I got few questions in my mind...
a. My Note is International version and purchased from KSA, whereas I am in Pakistan now. So can I claim my warranty here with Samsung Service Centres?
b. If yes, I obviously need to reset my binary counter, which is 4 or 5 at the moment. I also need to restore my Note to stock rom and stock kernel. Is there any safe way except Angelo's kernel and USB Jig to reset binary counter? i was looking for "Triangle Away" in the market, but i somehow couldn't find it.
Help my seniors please. If with your help I can go to Samsung and my warranty is validated, all credits with be to you guys for saving me from big troubles. To be honest I had been a poor kinda girl and managed barely to pull off my Note. I can't afford to manage a board replace night now

Hi: I do not have answers to all questions, but for triangleaway.
you can file a free and paid version of your choice:
http://forum.xda-developers.com/showthread.php?p=22463153#post22463153
https://play.google.com/store/search?q=triangleaway&c=apps
cheers,

Thank You Sir, Forest. Hope this would work

Of you've repartitioned the note that will void your warranty I imagine.
What you really need is an untouched superbrick as Samsung won't be able to tell if it has any hits on the binary counter or if its ever been rooted or custom firmwares flashed...
So brick it again if you are able to claim warranty in Pakistan.
Sent from my GT-N7000 using xda premium

SpyderTracks said:
Of you've repartitioned the note that will void your warranty I imagine.
What you really need is an untouched superbrick as Samsung won't be able to tell if it has any hits on the binary counter or if its ever been rooted or custom firmwares flashed...
So brick it again if you are able to claim warranty in Pakistan.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
So, bricking its again seems a potentially dangerous job :fingers-crossed: besides what do you suggest, i should tell Samsung guys, how it happened. Coz i believe they are gonna ask me if how come the phone went dead and i have also learnt that they have ways to check binary count, even if the phone is Superbricked. I am in a fix, coz after investing 500$ on a Note, living without a 3GB phone space is pain in the a*s.
Help please

alvinasnow said:
So, bricking its again seems a potentially dangerous job :fingers-crossed: besides what do you suggest, i should tell Samsung guys, how it happened. Coz i believe they are gonna ask me if how come the phone went dead and i have also learnt that they have ways to check binary count, even if the phone is Superbricked. I am in a fix, coz after investing 500$ on a Note, living without a 3GB phone space is pain in the a*s.
Help please
Click to expand...
Click to collapse
The brick has been acknowledged by samsung, they've admitted it can happen on fully stock uprooted firmware update over kies. That's all you say, you were updating through kies, it failed and you're bricked. They can't check binary count under super brick because it's not possible to enter download mode therefor impossible to get any data or connection off the device. Simple.
Sent from my GT-N7000 using xda premium

SpyderTracks said:
The brick has been acknowledged by samsung, they've admitted it can happen on fully stock uprooted firmware update over kies. That's all you say, you were updating through kies, it failed and you're bricked. They can't check binary count under super brick because it's not possible to enter download mode therefor impossible to get any data or connection off the device. Simple.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Well Dear spyderTracks, it confuses me further to think whether i was superbricked at all? coz i could go to recovery and could also go to download mode. as far as i know, u r super bricked if ur phone does not installs any rom and through odin, the rom installation stucks at factoryfs. please correct me if am wrong.
thanx for ur time.

alvinasnow said:
Well Dear spyderTracks, it confuses me further to think whether i was superbricked at all? coz i could go to recovery and could also go to download mode. as far as i know, u r super bricked if ur phone does not installs any rom and through odin, the rom installation stucks at factoryfs. please correct me if am wrong.
thanx for ur time.
Click to expand...
Click to collapse
No, that's correct. Usually it disables download mode also, my apologies.
Sent from my GT-N7000 using xda premium

[Q] Formatted Note internal SD - Wont boot

Hi.
Firstly, i should start by apologizing for my stupidity and complete failure to be less... useless, when it comes to my phone.
I am selling my Galaxy note, which is rooted and has ICS Stunner 2 on it, with 'cwm-based recovery v6.0.2.7 (if that helps)
My issue is, Before selling my phone I took out my 'external SD' card and decided to reformat/nuke my internal SD, thinking that the firmware would remain intact and the thing would still be useable if i repartitioned it or whatever.. Again, a bit new to this..
Anyhow, half way through formatting the internal SD the process was interrupted. I can boot the phone, but when I do anything that requires use of the internal SD (saving photos, downloading apps... and in cwm recovery, even factory reset) it wont work
In fact, when I try a factory reset it says 'Error mounting /sdcard/.android_secure
I would love to know what I am meant to do to fix this, and of course am willing to provide any info you may need to help me out here..
As i was typing this the phone got sold and I am now running against the clock to make this work...
please, help!
Thank you so much and I again apologize.
AceS
Quick edit: Kernel version -cm-enhanced+
[email protected] #1
Stunner version 2.2.4
Baseband N7000XXLR1

AceSLive12 said:
Hi.
Firstly, i should start by apologizing for my stupidity and complete failure to be less... useless, when it comes to my phone.
I am selling my Galaxy note, which is rooted and has ICS Stunner 2 on it, with 'cwm-based recovery v6.0.2.7 (if that helps)
My issue is, Before selling my phone I took out my 'external SD' card and decided to reformat/nuke my internal SD, thinking that the firmware would remain intact and the thing would still be useable if i repartitioned it or whatever.. Again, a bit new to this..
Anyhow, half way through formatting the internal SD the process was interrupted. I can boot the phone, but when I do anything that requires use of the internal SD (saving photos, downloading apps... and in cwm recovery, even factory reset) it wont work
In fact, when I try a factory reset it says 'Error mounting /sdcard/.android_secure
I would love to know what I am meant to do to fix this, and of course am willing to provide any info you may need to help me out here..
As i was typing this the phone got sold and I am now running against the clock to make this work...
please, help!
Thank you so much and I again apologize.
AceS
Quick edit: Kernel version -cm-enhanced+
[email protected] #1
Stunner version 2.2.4
Baseband N7000XXLR1
Click to expand...
Click to collapse
If you are selling your note, maybe the best thing you can do is flash stock rom for you region and thats it.
It will solve your problems at once.

djoni_gitara said:
If you are selling your note, maybe the best thing you can do is flash stock rom for you region and thats it.
It will solve your problems at once.
Click to expand...
Click to collapse
I appreciate this, however I have advised the buyer that I am selling it Rooted.
I don't want to let him/her down at all.
Other than this the phone is perfect.. As soon as this is fixed all will be good

Flash a Philz ICS kernel (zip version in recovery) Reboot back into recovery and /Format emmc.
Sent from my GT-N7000 using xda app-developers app

shoey63 said:
Flash a Philz ICS kernel (zip version in recovery) Reboot back into recovery and /Format emmc.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
+1
Forgot about that, that would do the trick:good:

djoni_gitara said:
+1
Forgot about that, that would do the trick:good:
Click to expand...
Click to collapse
You guys are both lifesavers; thanks to you both.
Mods/admins? Delete/lock thread?

AceSLive12 said:
You guys are both lifesavers; thanks to you both.
Mods/admins? Delete/lock thread?
Click to expand...
Click to collapse
Think they won't it will be open for people which have similar problems like you

TheNoticer said:
Think they won't it will be open for people which have similar problems like you
Click to expand...
Click to collapse
Ah of course - Thank you again everyone
I can get some sleep now

[Q] Whoops... Wiped System. Mayday!

Good Evening XDA Note 4 Devs/Users,
The Bad News;
I seem to have gotten myself into a pickle. and, Hopefully.. one that isn't permanent.
So, I was planning on reinstalling Firekat 4.4.4 after being on CM12 (Lolipop) Remix. everything went super till I went to wipe my data/cache. In the process of being yelled at by two people and in the stress of it all I accidentally wiped the system data too. Which, seems to have deleted just about everything.. including the original backup of my device, the two ROMS and the system OS. The phone is also claiming not to be rooted now and TWRP seems to have been deleted too. The only thing I can really do is boot into download mode which ODIN keeps refusing to detect. and, Windows 8.1 keeps thinking the phone is a Banana.
The Good News;
I May have a Backup of the Original Unrooted TMO KitKat stored on my Laptop from ODIN.
I May Be able to push the Unrooted ROM by ADB / ODIN
I can boot into Download mode.
So, knowing my predicament and knowing I screwed up. Any advice or help from here to get the device working again?
Also, I promise not to try and turn the phone into a brick again. :good:
Thank you in Advance! :highfive:

Odin

follow this http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733

I'm on FK, I always wipe everything. As long as my Zip (for install) is on the external SD card, I'm good. So what's wrong?
As for not having TWRP, I would also just Odin to stock, reinstall it. Should be an easy fix.

madmike23 said:
I'm on FK, I always wipe everything. As long as my Zip (for install) is on the external SD card, I'm good. So what's wrong?
As for not having TWRP, I would also just Odin to stock, reinstall it. Should be an easy fix.
Click to expand...
Click to collapse
I came from a phone that if you end up deleting everything like this. You bricked the device completely with it not even turning on. (Older android phone). So, Naturally. I thought I had screwed myself with it. lol
I did fix it though right after I posted the thread. I managed to get one of the rom's to flash through odin. (so, I guess I did not accidentally unroot it). I think I Love Samsung phones now that I can accidentally brick it and then still get myself out of trouble with the help of you all

I dont know anyone who has bricked a samsung in a while. Odin is great. Only mess up would be if you delete pit file

BACARDILIMON said:
I dont know anyone who has bricked a samsung in a while. Odin is great. Only mess up would be if you delete pit file
Click to expand...
Click to collapse
I regret to say this is my first Samsung device.. was a Motorola and HTC fanboy before both which I bricked one way or the other..

BACARDILIMON said:
I dont know anyone who has bricked a samsung in a while.
Click to expand...
Click to collapse
I would still be careful. I managed to brick my Note 3 so hard that JTAG couldn't bring it back to life. They are easy to recover from soft bricks, but they aren't invincible...

Face_Plant said:
I would still be careful. I managed to brick my Note 3 so hard that JTAG couldn't bring it back to life. They are easy to recover from soft bricks, but they aren't invincible...
Click to expand...
Click to collapse
Really. I was working on 3 phones and flashed the wrong rom on my note 3. It was from a totally different phone. Took 6 hours to bring back to life. Odin would install a part then fail so just kept pushing and wiping and finally went in. I was mad as hell since i qas going on vacation the next day. Lol.

BACARDILIMON said:
Really. I was working on 3 phones and flashed the wrong rom on my note 3. It was from a totally different phone. Took 6 hours to bring back to life. Odin would install a part then fail so just kept pushing and wiping and finally went in. I was mad as hell since i qas going on vacation the next day. Lol.
Click to expand...
Click to collapse
I couldn't get into download mode. The phone was completely unresponsive to all button combos and my laptop. I tried a USB jig, an unbrick image flashed on an SD card, yelling at it, and sending it off for JTAG but nothing could bring it back. I was quite sad because I had a lot of good memories with that phone, but my Note 4 fills the void nicely.

Hi
I managed to get in trouble with note 3...I have listed my entire trial & error here, can someone please help me bring this phone back to life.
http://forum.xda-developers.com/gal...ed-samsung-note-3-n9005-t3058408/post59580154