Database Develop

[Q] Signed samsung zip

Hi. I have been trying to find an solution to my problem for 3 days. I have looked all over here and the rest of the internet. I believe what I need is an update zip file that will pass the standard e3 recovery.
I have downloaded several zips already(a couple from here), that say they are the stock samsung firmwares, but everytime I put it on an sd, then try to apply the update with it, in the e3 recovey I get E: signature verification failed.
I got to this point by trying to apply the OTA update. ( ok, you can all throw rotten food at me now). I thought I was safe as I didn't have any custom firmware on there. I had, however gained root access. The update went fine and seemed to work, then it finished and tried to reboot, only to get stuck on the samsung logo for over an hour before I decided it had gone wrong and panicked.
The usual ways of fixing I know about are odin, heimdall, adb. None of these are working. I think it's my computer being too old. Odin doesn't detect, Heimdall sees there is a device there but has problems connecting to it. adb will only see it in the e3 recovery mode and not in odin mode and even then because it doesn't seem to be root anymore it can't really do much.
I am open to suggestions on how to get something to work. My thoughts are that I just need a gingerbread rom that has some samsung siigning on that I can put on an sd and use that in E3 to flash from there. I can then work from there if that works. Feel free to laugh and point and tell me that's not gonna work, but if you know a way that will work I would be very grateful.
Thank you for listening and I hope someone can help.

Open kies, do the connection troubleshooting to reinstall device drivers.
Then follow path of flashing stock with PC Odin with pit file. See dr Ketans thread in sticky section of development for path.
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
Open kies, do the connection troubleshooting to reinstall device drivers.
Then follow path of flashing stock with PC Odin with pit file. See dr Ketans thread in sticky section of development for path.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
thanks for getting back so soon. I have had kies up on the screen actually. It's been trying to connect for about 3 hours now lol.
I did the troubleshoot thing earlier where it reinstalled drivers. Restarted pc but same. Won't actually connect in either odin mode or recovery.I'm pretty sure it's a pc issue, at least partly anyway, but don't have anything else to try it on.
Is the signed zip idea a definite no go?

Not sure about zip,
Close Kies, open pc odin,
Gp into download mode, connect phone, confirm downloadmode with volume up and try tp flash
Let me know how that goes
Sent from my GT-N7000 using Tapatalk 2

No Odin pc refuses to recognise there is anything attached. I'mgiving up for the night now anyway. thank you for looking in. I'll try again in the morning. I might have to buy a new pc before I can get this thing to work.

Connect the usb to back port, sometimes helps with connection. Use stock usb cable.
please hit thanks if i helped

thanks but I've tried all the basics, but if it would help I'd stick a wire up my nose, so it's all helpful. It could be something simple I just forgot.

PC specs? Is it a Mac maybe? Reboot phone and PC and use another cable. Download latest kies and update it restart PC and then connect the phone.
Sent from my GT-N7000 using Tapatalk 2

Umm, did you wipe after the flash?
1. A data wipe will, in all probability, solve the bootloop after the upgrade from GB to ICS.
2. A data wipe on an ICS kernel CAN result in a hardbrick, as I'm sure you must have noticed, on the forums.
I'd say wipe it. The bricks are not all that common. Just this once. I faced a similar situation, and I KNEW the thing would boot after a wipe, so I just crossed my fingers and did it. All went well.

By they way, what do you mean by e3 recovery? I've been assuming stock.
Sent from my GT-N7000 using xda premium

the PC is a 7-8 year old laptop. Our desktop died a few months ago and we've not really had the spare cash to replace it yet. The desktop was even older and was a real pain. The technical gremlins have really infested my house.
I don't really want to wipe the data, as I could just send off to samsung repair as a last resort. I really want my pictures and data back. Got some of my 2 and half month old daughter on there that I haven't got backed up anywhere else. (yes I'm looking dumber with every post). My next thing to try I guess is see if I can borrow my sister in laws PC for a few hours or something. That is if if cannot find a rom that the recovery will accept to put on my sd.
yes -the e3 recovery s the stock one.

Feel for ya.... if you can enter stock recovery then the connection problem most likely lies either with the cable and port or drivers being out of date
Sent from my GT-N7000 using xda premium

almost positive it's my knackered computer that won't let me do anything. Still can't believe that a rom doesn't exist with samsung signing, somewhere in the world. What is the point of having a standard recovery at all if you can't use it to recover stuff?
I need to be borrow or steal the use of someones computer now I think. I'll keep an eye on this thread incase someone knows of a signed zip file, and I will report of any news incase someone else has the same problems and wants to fix it without sending to Samsung so they can keep their data.

kyllerbuzcut said:
I don't really want to wipe the data, as I could just send off to samsung repair as a last resort. I really want my pictures and data back. Got some of my 2 and half month old daughter on there that I haven't got backed up anywhere else.
Click to expand...
Click to collapse
I understand the reluctance.
Although, the pictures would survive the wipe, as they would be in /sdcard/DCIM/Camera. A wipe wouldn't affect anything in /sdcard, although, you'd lose your contacts if they aren't backed up. Your best bet would be to borrow someone's computer for a while.

thanks for all the advice.
Finally found a zip that the e3 recovery thinks is signed.
It was the 2.3.6 gingerbread, uk cpw one.
It seems to pass the signing check and then it looks like it's doing domething for a few minutes, then nothing seems to happen afterwards. just stays in recovery. If I do it a few times in a row it will sometimes think for longer, then reboot itself like it has all worked, but then get stuck at the samsung logo again.
Can I ask, what exactly is getting wiped then? Just the main android folders and not the sdcard folder? Is that for definite?

Yes. Just the android partition should get wiped, internal SD should remain intact.
Try taking out the battery for five minutes or so before powering on again. Sometimes after flashing the rom needs a breather to "settle".
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!

Just an update on my situation. I finally managed to get use of another computer and got it to work properly, so managed to flash the stock ICS rom through odin.
Thanks a lot Samsung for forcing me to put the yellow triangle on my device. At least there are people willing to help with fixing mobile phones' software, even if the manufacturers themselves don't care about you losing all your data. I managed to get everything back. Nothing was lost. If only they allowed you to flash the stock rom from their stock recovery. It's ridiculous that it doesn't.
Anyway there is the triangle away app for that I suppose and now I might try some new roms out to see which I prefer.

Yeah you would have to make a flashable zip. Not sure how to do that.
Good you are back
Sent from my GT-N7000 using Tapatalk 2

Does warranty accept my Gnote after emmc brick?

Hi,
I have got my Gnote super bricked and I used pit file method to revive it but now these freezes are killing me. I have bought it 9 months ago from mediamarkt in Germany.
Do you think they will accept it now? I mean it is working but every several hours it freezes. What should I tell them about the problem?

I revived my note using the pit files but it isn't giving me problems as you say

I really have no idea where these freezes are coming from. I think sooner or later I should give it for warranty

have you tried already doing the 3 wipes on your phone in CWMR?
if you have tried it already and still getting the hangups on it.. my reasonable suggestion is.... just BORK it more. I mean what have you got to lose if Samsung can't boot your phone anymore right? No more explanations to them other than your phone got toasted when you tried to update via KIES....
end of discussion.

ashkan_mc said:
I really have no idea where these freezes are coming from. I think sooner or later I should give it for warranty
Click to expand...
Click to collapse
As long as the binary counter is set to 0 and there's no yellow triangle you should be able to take it to warranty. Of course unroot it first and leave no trace of any customization.

So I'd they ask you what's the problem with your note what shall you say?

letters_to_cleo said:
have you tried already doing the 3 wipes on your phone in CWMR?
if you have tried it already and still getting the hangups on it.. my reasonable suggestion is.... just BORK it more. I mean what have you got to lose if Samsung can't boot your phone anymore right? No more explanations to them other than your phone got toasted when you tried to update via KIES....
end of discussion.
Click to expand...
Click to collapse
You mean again I try to make it bricked? Just like the last time or with another method? Can they find out I did it deliberately?
The problem is now my internal sd is showing 9.33 GB and if they dig in more, they will find out what I have done to it.
Of course samsung is responsible for this matter cause it is they fault not mine.
Now my phone is unroot and has official LRQ on it.

ashkan_mc said:
You mean again I try to make it bricked? Just like the last time or with another method? Can they find out I did it deliberately?
The problem is now my internal sd is showing 9.33 GB and if they dig in more, they will find out what I have done to it.
Of course samsung is responsible for this matter cause it is they fault not mine.
Now my phone is unroot and has official LRQ on it.
Click to expand...
Click to collapse
Yeah sure why not... I mean it may seem ridiculous to advice you this but bricked it back until you can't turn it back on again. I know most other users before who have bricked their phone big time (can't boot up their phone anymore) and they've return it back to Sammy to have the mobo replace. No questions asked. If they try to ask you what you did.. just give them an innocent smuck and say.. "My phone's not turning ON after I tried to update it thru Kies. I dunno what's the problem with it." Give them a casual after stupid innocent look. Most likely they won't drill you anymore.

letters_to_cleo said:
Yeah sure why not... I mean it may seem ridiculous to advice you this but bricked it back until you can't turn it back on again. I know most other users before who have bricked their phone big time (can't boot up their phone anymore) and they've return it back to Sammy to have the mobo replace. No questions asked. If they try to ask you what you did.. just give them an innocent smuck and say.. "My phone's not turning ON after I tried to update it thru Kies. I dunno what's the problem with it." Give them a casual after stupid innocent look. Most likely they won't drill you anymore.
Click to expand...
Click to collapse
Do they give a new phone or just replace its motherboard?
And btw what did you mean by 3 wipes? I did not wipe the whole internal and external sd though
Thanks alot

ashkan_mc said:
Do they give a new phone or just replace its motherboard?
And btw what did you mean by 3 wipes? I did not wipe the whole internal and external sd though
Thanks alot
Click to expand...
Click to collapse
No, they're just going to replace your motherboard.
3 wipes is Wipe DATA, Wipe Cache Partition and Wipe Dalvik... all of these are in CWMR (if your still able to boot in recovery).
hmm, on a lighter point, before you begin the steps above(if you would like to try though), try to format your external SD card and try to place it back again to your phone. See if you still have the hangups.. If you do have it still, then go with the 3 wipes I mentioned above.

letters_to_cleo said:
No, they're just going to replace your motherboard.
3 wipes is Wipe DATA, Wipe Cache Partition and Wipe Dalvik... all of these are in CWMR (if your still able to boot in recovery).
hmm, on a lighter point, before you begin the steps above(if you would like to try though), try to format your external SD card and try to place it back again to your phone. See if you still have the hangups.. If you do have it still, then go with the 3 wipes I mentioned above.
Click to expand...
Click to collapse
If I try to get it bricked and mediamarkt in germany won't accept it, is it possible that I revive it with pit file method again?

Like I've said..skip the 3 wipes for now and just format first your SD card and see if the hangups wouldn't be there after.
If it's not there anymore then GOOD.. if it's still there, then you do the 3 wipes. I would assume your already using a safe kernel already right?

letters_to_cleo said:
Like I've said..skip the 3 wipes for now and just format first your SD card and see if the hangups wouldn't be there after.
If it's not there anymore then GOOD.. if it's still there, then you do the 3 wipes. I would assume your already using a safe kernel already right?
Click to expand...
Click to collapse
I did use hydracore kernel for a while but with that I had freeze more. Now I am in unroot condition with stock kernel. So I can not do the 3 wipes now.
I will try to remove my external sd card and see without that what is gonna be ...

sure, just post back later on your results.

I did all kinds of wipes and formats but again freeze don't know what to do

Well, it's apparent that your phone's boot partition has some bad sectors on it still. That's why everytime your phone reads those particular bad sectors.. it freezes itself up.
try to repartition your phone back to remove those bad sectors or you can try the link here http://www.alliance-rom.com/communi...-superbricked-stage-from-ics-kernel-bug.8018/ , as your reference to remove those bad sectors and scan for possible partition errors as well.

letters_to_cleo said:
Well, it's apparent that your phone's boot partition has some bad sectors on it still. That's why everytime your phone reads those particular bad sectors.. it freezes itself up.
try to repartition your phone back to remove those bad sectors or you can try the link here http://www.alliance-rom.com/communi...-superbricked-stage-from-ics-kernel-bug.8018/ , as your reference to remove those bad sectors and scan for possible partition errors as well.
Click to expand...
Click to collapse
I have tried this thread before ... The one which belongs to forest1971 ... Again nothing ...

Mate best thing is return to gb stock with counter 0... ensure everything is stock... give the mobile to ur girlfriend and ask her to take it to sammy center...
Ull get the replacement for sure... tell them updating from kies did this...

Why GB? If it would be ICS it has problem? I mean I want to tell them that I was on LRK and I updated it to LRQ via Kies and then my phone got bricked. Do you think it is ok? GF idea is perfect

ashkan_mc said:
Why GB? If it would be ICS it has problem? I mean I want to tell them that I was on LRK and I updated it to LRQ via Kies and then my phone got bricked. Do you think it is ok? GF idea is perfect
Click to expand...
Click to collapse
Bro u have already revived ur mobile... so best thing to do is take it sammy and tell them that ur mobile lags a lot and u have some lost space on ur memory card... (play innocent).... they'll check it and replace ur mobo if needed... so doesnt matter if u r on gb or ics

[Q] Recovering from Hard Brick

Okay, so essentially I'm fixing my friends Galaxy Note. He had ICS on it, it was rooted, and then he thought installing Cyanogen 10 was a good idea on the default samsung unsafe kernal, and ICS, also the "unsafe for use" CM10. He's not very bright.
Being the kind friend I am, I said I'd fix it. It was stuck on the "plug into kies for recovery" screen, and when I plugged it into kies, it asked for a recovery password... which he obviously forgot. So I tried flashing it with a stock ICS rom, but it got stuck on factoryfs.img.
From there I could flash a new kernel using a USB jig, which was the default samsung one, and get it into the ClockWorkMod recovery which was thankfully installed. But he didn't backup his stock rom beforehand *facewall*
I still can't flash roms using odin or CWM. And I looked up the factoryfs.img and said it was a partition error.
Is it worth trying to fix the partition error using ADB and command, or is it possible for someone nice to give me their backup to get it working again?
Thanks,
Aaron

If you are getting a factoryfs.img or NAND write start hang up in Odin, more than likely it is superbricked. There's a thread in General (I think) that you can look at at possibly reviving it the "hard" way but who knows if it will work fully again without taking it to the samsung service centre.

You can revive using this method :
http://forum.xda-developers.com/showthread.php?t=1667886
U will loose few GB on Ur usb internal storage.
But if u don't want to loose anything, u can only bring to Samsung.
I choose to revive, and I lost 2GB. Now my phone working well.
Sent from my GT-N7000 at the corner of this rounded earth.

He contacted Samsung about it and they say because it was bought outside Europe it's not their problem...
I'm going for the partition fix guide now, not using the PIT files but manually doing it with command
Thanks guys

arono7342 said:
He contacted Samsung about it and they say because it was bought outside Europe it's not their problem...
I'm going for the partition fix guide now, not using the PIT files but manually doing it with command
Thanks guys
Click to expand...
Click to collapse
If u know other way to do, perhaps u can share as well once u succeed. :thumbup:
Sent from my GT-N7000 at the corner of this rounded earth.

[Q] flashing wth Odin stucks at Factoryfs.img step...tried everything,what to do now?

I had battery issues with my Note GT-N7000. I purchased the original battery from samsung service center. Phone did restarted several times due to low battery. After one such incident it was not accepting my correct pattern. After some time it just stopped getting start up.
Then i tried to enter into recovery mode. It got stucked at android green logo, wheel spinning every single time.
But download mode is still working. I tried to re-flash it with stock firmware as i was running it before this problem occurred (stock with root).
I followed flashing instructions extremely carefully and as they instruct. When i put my phone into download mode, it got successfully recognized by my computer, But while flashing it got stucks at flashing factoryfs.img, ""NAND write start"" and followed by ""complete write operation failed"".
I did changed my original usb cable to another original cable. My antivirus and firewall are turned off permanently. I did tried it on another computer but same result. Downloaded my firmware from sammobile twice. Did tried different Odin versions from 1.83 to 3.07. But no luck at all. I am attaching my screenshots so that you can have a look.
Please help me out in any way you can. Any links or help will be highly appreciated from the bottom of my heart. Thanks in advance for your reply.

Did you have a ROM on it that required you to change the PIT file? If there is a different partition scheme that could cause an issue. Also try unchecking f reset time.
Sent from my SM-G900T using XDA Premium HD app

zombieplanalpha said:
Did you have a ROM on it that required you to change the PIT file? If there is a different partition scheme that could cause an issue. Also try unchecking f reset time.
Sent from my SM-G900T using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for your quick response. I do not have a ROM that require me to change PIT information. I was on pure stock with root before this issue came up. I did unchecked reset time but same error came up.
Different partition scheme...? As far as i know, i didnt do anything to my partitions.

You bricked your device. Search for threads with "factoryfs.img" and you'll find answers (repartition, replace MB or follow hg42's thread).
And you'll might find your post from Nov 2012 when you had a problem like this before but "solved" it.

ThaiDai said:
You bricked your device. Search for threads with "factoryfs.img" and you'll find answers (repartition, replace MB or follow hg42's thread).
And you'll might find your post from Nov 2012 when you had a problem like this before but "solved" it.
Click to expand...
Click to collapse
So is there any possibility of restoring the data?

Negative. Custom recovery and frequent backups along with an app like titanium backup would have been good to have before this happened
Sent from my SM-G900T using XDA Premium HD app

zombieplanalpha said:
Negative. Custom recovery and frequent backups along with an app like titanium backup would have been good to have before this happened
Sent from my SM-G900T using XDA Premium HD app
Click to expand...
Click to collapse
I do have the backup but its more than 2 months old...but i cannot go into stock recovery....i should have installed cutom recovery. Any links to follow or any proper guides to come out from it?

http://forum.xda-developers.com/showthread.php?t=1667886

ThaiDai said:
http://forum.xda-developers.com/showthread.php?t=1667886
Click to expand...
Click to collapse
As per the article and since i cannot enter into recovery mode, i tried all the PIT files provided with stock rom. But nothing has worked. Every time Odin is failing. I am attaching the screenshot of the same. I did tried to flash speedmod kernel but didnt got success message from Odin. Kindly help me.

i have used custom PIT files due to which my binary counter has increased(i dont care as its out of warranty). My phone shows a yellow warning sign on bootup and now it just dont even start the recovery mode and shows that yellow warning sign when i try to enter recovery.
Download mode is still working but i am unable to perform any write operation. NAND operation is failing everytime. When i used PIT files, it says re-partition operation failed. I can only try things mentioned in the above posts only when i can enter recovery.
Will someone be kind enough to help me out on this one as i really need urgent help? Please help me out guys.

I think you didn't read hg42's thread and didn't follow his big bold red warnings.
Brute Force experiments with different pit files made it only more difficult or impossible.
In his thread there is a link to another thread related to the problem
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
forest describes a manual method to check for errors including a repair option by scanning the device with e2fsck in chapter 4.2.
I remember some users who solved the brick with factorfs.img with this method (at least I remember one where nokiamode gave that hint).
Try this and follow forest`s instructions carefully.

You tried flashing PhilZ-cwm6-DDLSC kernel tar file fusing odin?

ThaiDai said:
I think you didn't read hg42's thread and didn't follow his big bold red warnings.
Brute Force experiments with different pit files made it only more difficult or impossible.
In his thread there is a link to another thread related to the problem
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
forest describes a manual method to check for errors including a repair option by scanning the device with e2fsck in chapter 4.2.
I remember some users who solved the brick with factorfs.img with this method (at least I remember one where nokiamode gave that hint).
Try this and follow forest`s instructions carefully.
Click to expand...
Click to collapse
Thanks for replying. I did read that article carefully but all steps and troubleshooting is valid only and only when your phone's recovery mode is working. In my phone, only download mode is working. So all those steps are not applicable to me.
However i went for case B where he has described solution if we are unable to access recovery mode and suggested to use blind method to use custom pit files. I followed him but it didn't worked out for me. None of the pit files worked for me and i just ended up raising my binary counter to 2 now.
I am not receiving any replies from people(Only 2 or 3 kind people like you have replied, i appreciate it). I am not getting support. Its reallly sad just because my phone is little old now.
Even if i didn't find any solution and my phone becomes a brick( i guess it has become by now) it is still fine for me But the most sad thing is no one cares to reply on a community which was built to help each others. I am continuosly searching for solutions now. Lets see how far i can go. Thanks for your time. Do let me know if you come across any thing or i am ready to try any solution/troubleshooting steps.

nokiamodeln91 said:
You tried flashing PhilZ-cwm6-DDLSC kernel tar file fusing odin?
Click to expand...
Click to collapse
I have downloaded Philz-cwm6-DDLSC tar file....I'll be flashing it soon and'll let you know for sure

vinay28761 said:
I have downloaded Philz-cwm6-DDLSC tar file....I'll be flashing it soon and'll let you know for sure
Click to expand...
Click to collapse
No progress...it just got failed again.....I will get the motherboard replaced by samsung...It'll cost me 170+ USD, original motherboard and a new original battery as well.

vinay28761 said:
No progress...it just got failed again.....I will get the motherboard replaced by samsung...It'll cost me 170+ USD, original motherboard and a new original battery as well.
Click to expand...
Click to collapse
Have you tried another pc, and genuine USB cable by Samsung?

nokiamodeln91 said:
Have you tried another pc, and genuine USB cable by Samsung?
Click to expand...
Click to collapse
Yes i tried on different pc, different cables(all are genuine)

[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