Android M Code Name: Macadamia Nut Cookie

While the official name for the latest iteration of Android has yet to be revealed, the code … more

XDA Recap: This Week In Android (May 17 – 23)

Another week, another recap. The Sunday tradition marches on this week with a fresh … more

Huawei To Sell Honor Smartphones Via Indian Retail Outlets

World’s fourth largest smartphone maker Huawei plans to now sell its … more

Sunday Debate: Are Smaller Bezels Better or Worth It?

Bezels have been getting smaller and smaller as the years go by, and while devices … more
Post Reply Subscribe to Thread Email Thread

[Q] Is my phone bricked?

1st June 2014, 03:50 AM |#1  
OP Junior Member
Thanks Meter: 1
Hello xda,
New to Android here.
My co-worker talked me into getting and Android phone. I decided to go with the note 3. After leaning about ROMs and all that I wanted to test some out. I tested some out then wanted to make Hyperdrive my stock ROM. I was very stupid and kept the ROM file in my system. Well when I whipped the system folder, the ROM file went with it. So I followed the steps for the bricking tutorial and when I put my phone in download mode and launch Odin, its not found by Odin. Also I do have the drivers and I was not sure if I enabled USB debugging mode.
Could someone be able to assist me?

Able to access E3
Able to access phone in download mode through Odin
SECURE CHECK FAIL : PIT When using Heimdall Frontend to create partion
Not able to be detected by Odin in download mode but is able to when stuck on boot logo


So, after starting this thread. I was thinking about being a good trouble shooter and retracing my steps.
After sitting down for a good 5 hours ( been working on this even before starting the thread ) and reading through the steps, learning ADB and just learning how Odin works in general, I found the stickler.
What it turned out to be is that when you have to change the driver with Zadig, it caused the phone to stop being found in Odin.
How I fixed this is going into Device Manager > Ticking the tab that says Show hidden devices > Finding the device "MSM8960" > Unplug the phone > Uninstall the driver > Plug the phone in again > Let Windows handle the drivers.
Then I followed the tutorial once again and boom. My phone worked.
Last edited by 8BitHayden; 1st June 2014 at 06:25 AM.
The Following User Says Thank You to 8BitHayden For This Useful Post: [ View ]
1st June 2014, 04:48 AM |#2  
Virus1x's Avatar
Senior Member
Flag Scottsdale, Arizona
Thanks Meter: 147
Donate to Me
I walked him as far through it as I could since I only Dev for my nexus 5 and a little for my note3

Sent from my SM-N900V using Tapatalk
The Following User Says Thank You to Virus1x For This Useful Post: [ View ]
2nd June 2014, 02:14 AM |#3  
badler6545's Avatar
Senior Member
Flag Los Angeles
Thanks Meter: 32
Glad you figured it all out, and I am particularly happy that you included your fix for other users. This is why I love this place!
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Top Threads in AT&T Galaxy Note 3 Q&A, Help & Troubleshooting by ThreadRank