[Q] Galaxy note Help.. I think it's Bricked!!

Search This thread

marmyte

Member
Mar 7, 2014
41
1
I have a Note N7000, It is rooted with Philz Touch 5. I had issues with it last friday where it would restart when trying to start any random app.
Thought it weird, maybe it's the last app to be put on - but no. Went into the phone and cleared the cache in Philz Touch 5. After this the phone would not start again.. much to my disappointment.

I have downloaded Odin3 v1.87 and have downloaded the attachment from this thread. http://xdaforums.com/showthread.php?t=1354888

i have also purchased a JIG from this Ebay ad. http://www.ebay.co.uk/itm/141209048811?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649

The JIG doesn't work, ODIN can read my phone when it's plugged in - and has successfully done the PDA & BOOTLOADER tasks.

I hope & feel that I can bring my phone back to life - I would someone to help me to understand what next steps I can take to do this.

Thanks for all your help in advance..:D
 

marmyte

Member
Mar 7, 2014
41
1
What the PDA and bootloader task? How did you do it?

Used C:\Users\Stev\Downloads\removeyellowtriangleNEW\2-ZSLPF.tar for BOOTLOADER

And C:\Users\Stev\Downloads\removeyellowtriangleNEW\1.tar for the PDA

All went well -

<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> Sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> Sbl.bin
<ID:0/004> param.lfs
<ID:0/004> Sbl.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!

Used Odin3 v1.87
 

Azeazezar

Senior Member
Aug 5, 2011
380
187
ಠ_ಠ
EDIT
I just noticed those files are from triangleaway. NOT the stock rom. What you flashed is to remove the big yellow triangle at boot.
Download Stock GB or Jellybean, and flash those with odin. That should fix your phone.
 
Last edited:

marmyte

Member
Mar 7, 2014
41
1
Can you put me in the right direction for the stock roms, I've tried a download for uk vodafone but it goes to hotfile with a warning message :confused:
Thanks.
 

marmyte

Member
Mar 7, 2014
41
1
Using Odin3 v1.85

It gets to this stage and... How long does it take?

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000VODLT4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
 

nokiamodeln91

Senior Member
Jun 6, 2012
7,389
2,634
Using Odin3 v1.85

It gets to this stage and... How long does it take?

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000VODLT4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
There is some connection problem with phone and PC.. so kill all kies processes.. run odin as admin.. reboot into download mode and try again.
 

marmyte

Member
Mar 7, 2014
41
1
killed all kies processes.. run odin as admin.

Got this..

<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000VODLT4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Help please:crying:
 

nokiamodeln91

Senior Member
Jun 6, 2012
7,389
2,634
killed all kies processes.. run odin as admin.
Help please:crying:

Flash a tar version of Philz kernel like XXLTA or DDLSC. using odin. The power off the device and boot into recovery. This should get you into CWM. Format system, data, cache and preload. Then reboot into download mode and flash this rom again OR you can flash any custom TW or CM rom.
 

marmyte

Member
Mar 7, 2014
41
1
I'm really sorry, but I don't understand what you've just said - can you make it any easier for a novice like me :eek:
 

nokiamodeln91

Senior Member
Jun 6, 2012
7,389
2,634
I'm really sorry, but I don't understand what you've just said - can you make it any easier for a novice like me :eek:
go to this link and in post 3.. there is download for TW kernels. download the latest tar version.
boot the phone to download mode and select the tar kernel in PDA and flash it. Odin will say KERNEL.. If it completes. power off the device and try to boot into recovery.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Update..

    Installed cm-10.1.3-n7000 & gapps-jb-20130812-signed..
    All works excellent :)

    I think I've got my phone back :fingers-crossed:

    Big Big Thank you to nokiamodeln91 & forest1971 for all your help!! :good:

    :good:


    Thought so.. May be issue was with the hidden partition... Anyhow.. Good to know. .. Later dont go flashing unknown bootloaders....:p
    1
    Can anything else be done in Odin?

    Bootloader - Dunno what it does?
    Phone ?
    CSC ?

    And what is a PIT file ?

    :eek:
    This is based on the fact that you get a blank screen on recovery... issue might be with the bootloader you flashed earlier.. Search for N7000XXLSA_N7000OXALSA_DBT.zip in sammobile.com and download the firmware..(if not found on that site, use Google).
    Unzip it. here will be 3 files
    Open odin.
    Use the CODE_ file in PDA
    MODEM_ in PHONE
    CSC_ in CSC
    Flash again..
    1
    Sorry.. But I think it Fooked :crying:
    Came back with this..

    May be...
    Lets try a different approach..
    Flash the previously download Philz kernel again. Once you get a success message, power off the device and remove the battery. Now put the battery back and press and hold the three button combo for recovery till you see the GT-N7000 screen. After that wait for 5 seconds.
    Last time you did this, you said the screen vibrates but is blank.. If its the same, then connect the phone to PC.
    If you are aware of adb then go ahead.. Drivers can be found here (http://xdaforums.com/showthread.php?t=2588979)

    - Open command prompt.
    - type adb devices (output should be the device ID and recovery)
    - adb shell (output should be #)
    - now type umount /system (enter)
    umount data (enter)
    umount cache (enter)
    then
    - type e2fsck -f -c -y /dev/block/mmcblk0p9 (enter and let it do its thing)
    e2fsck -f -c -y /dev/block/mmcblk0p10 (enter and let it do its thing)
    e2fsck -f -c -y /dev/block/mmcblk0p7 (enter and let it do its thing)
    -type reboot download
    - kill adb from task manager
    - open odin and flash the XXLSA rom again.
    1
    After the adb sideload command... There will a % transfer... After it reaches 100.. Wait for about 15 seconds before giving the reboot recovery command.
    1
    I already have this zip file on my sd card (PhilZ-cwm6-XXLT9-ORA-5.08.5-signed).. do I delete it off the card and then put on sweet rom and install that?

    no need to delete that. just put on sweet rom. From Philz recovery you can choose which zip to flash. But before flash should go in to wipe/factory reset menu, then choose "clean to install rom". this is to make sure partitions are clean to avoid bootloop.