yashsingh1/xdaforums huggingface dataset:
[Sony Xperia T, TL, TX, V] danial-mach1:
hello guys

how i can find out my Xperia T is for which country?

i bought it in my country but its imported from another country and i want to find it out which coutry
[Sony Xperia T, TL, TX, V] WhiteNeo:
Are you still on complete stock firmware?
[Sony Xperia T, TL, TX, V] danial-mach1:
Yep its stock
[Sony Xperia T, TL, TX, V] superricky89:
You can find out which country is for your firmware by searching your Customization Number.

You must enter in the Service Menu by pressing "*#*#7378423#*#*" (*#*#SERVICE#*#*) in the phone dialer, and after tapping "Service Info" - "Software Info".

After that, you can download from this topic: http://xdaforums.com/showthread.php?t=2608983 "Xperia update Checker".

With that software, you can check the last firmware for a specified Customization number, but also check which country and which carrier your firmware is for!

Hope it helps! :)
[Sony Xperia T, TL, TX, V] danial-mach1:
thanks friend it works

that phone is from UK

and a spicial thanks for *#*#SERVISE#*#*:D
[Galaxy S 4 Q&A, Help & Troubleshooting] mrsharif:
Hi

I was previously using version 4.3.

I had no problems with 3g

But when I installed version 4.4 3g does not work.

Internet working via mobile data but not connect 3gand intenet very slowly.

I can not do video call

please help me
[Galaxy S 4 Q&A, Help & Troubleshooting] qtwrk:
Try flash different modem
[Galaxy S 4 Q&A, Help & Troubleshooting] mrsharif:
please tell me another way

i flashed but not work
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
Dial *#1234# and make a screenshot pls :highfive:
[Galaxy S 4 Q&A, Help & Troubleshooting] mrsharif:
ok
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
Wipe all, open ODIN and flash this FIRMWARE again :)
[Galaxy S 4 Q&A, Help & Troubleshooting] mrsharif:
ok but i now use VJUFNB2

|ROM| |★GOLDENEYE★| |I9505| |M919| |►VJUFNB2◄ please help this rom
[Galaxy S 4 Q&A, Help & Troubleshooting] mrsharif:
ok now i downloading

thanks bro
[Galaxy S 4 Q&A, Help & Troubleshooting] mrsharif:
i install VJUFNB2 and flashing modem .

But the modem does not change

please help me for change cp - modem.

i flashing via odin and my modem I9505VJUFNB2_MODEM

but do not change
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
Repeat the process but:

Reboot into Download Mode and use Odin

Untick Autoreboot

Flash modem

Take off the battery 1 minute and put it in again

Turn it on into Download Mode

Untick Autoreboot in Odin

Flash Modem once more

Once done, unplug then reboot device manually (like step 4)

Turn on the phone normally

If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
[Galaxy S 4 Q&A, Help & Troubleshooting] mrsharif:
yes now my modem nb2 and baseband and csc nb3

thanks bro

now testing 3g and tell you bro
[Galaxy S 4 Q&A, Help & Troubleshooting] mrsharif:
hello i now use nb2 but not connect 3g

my simcart dont have a problam and tested

mobiledata worked but not connect 3g
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
Go to Apps - Settings - Connections - More networks - Mobile networks - Click in Network mode and make a screenshot pls :fingers-crossed:
[Galaxy S 4 Q&A, Help & Troubleshooting] mrsharif:
Kk
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
It isn't there :silly:
[Galaxy S 4 Q&A, Help & Troubleshooting] mrsharif:
what?
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
Go to Apps - Settings - Connections - More networks - Mobile networks - Click in Network mode and make a screenshot pls :fingers-crossed:

*EDIT: If u dont find it, put ur phone for a second in english :)
[Galaxy S 4 Q&A, Help & Troubleshooting] mrsharif:
Go ahead
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
Where is the problem then? I see all correct :)
[Moto G Themes and Apps] rzac:
I am looking for a nice ad-free compass app for my Moto G running CM11 latest nightly (03-12). Just tried "nice compass" from f droid and market but both installs crash right at the start. Did anybody have the same issue? Just like to figure out if it is the app or a CM11 bug.
[Moto G Themes and Apps] kellerman40:
Use adaway.
[Moto G Themes and Apps] matiasrey:
I use Holo compass, simple, beatiful and efficient.
[Moto G Themes and Apps] rzac:
way .. holo is nice. i'll keep it.
[Moto G Themes and Apps] reversegear:
Ulyss gizmos..

Pls search it in play store

Features: compass,spirit level, magnet sensor, GPS

Though it is updated very very long back
[JAM, MDA Compact, S100 General] Slightlysane:
Is there any way of making my magician play my normal message tone, but shutup when I open it? (I have a long message tone - and I want to keep it) also would like to know if there is a fix for stopping full message alerts when in a call, and maybe change for a discreet tone.
[JAM, MDA Compact, S100 General] mark190977:
message alert tone

Soory to other you but nobody is answering my blog, and you seem to have solved my problem. When i try to change my message alert tone ,hte only options i am given are the default message alerts, ive tried copying tones into the windows ring folder but still only get default tonesthe previuos process works fine for my ring tone, can you help?
[JAM, MDA Compact, S100 General] doctorhcna:
Your notifications have to be in wav format. Or they will not work.

-This goes into the /windows folder

Ringtones can be in midi/wav or mp3 format

-This goes to the /windows/ringtones

Here are some wav files I made which you can try out

Free Female Voice Wav Alerts

http://docfiles.blogspot.com/2006/08/female-voice-alert-wavs.html#links
[JAM, MDA Compact, S100 General] mark190977:
Thanx for your speedy reply, cant look at link till work unblocks internet at break time but i`ll check them out, is there any way of converting my current message alert tones that i cant use to wav
[HTC Sensation] v.konvict:
i noticed most people are using hboot 1.27 and i am on hboot 1.29. Does hboot affect custom rom api or normal function because i have been having some problems with accessiblity settings in viper s 5.1.0
[HTC Sensation] rzr86:
no it doesn't affect

AFAIK sensation XE devices come with 1.29 hboot
[HTC Sensation] migui0401:
It doesn't affect any custom rom you install, settings problem may be caused by a problem in the rom.
[HTC Sensation] Far_SighT:
Hboot 1.29 doesn't have any performance upgrades over 1.27.

Firmwares 3.32/3.33 both support (AFAIK) all android 4.0+ ROMS.

However you won't find any unlocked versions of 1.29. Just 1.27 mods only.

Happy to help.
[HTC Sensation] touristas0:
With 1.29 on pyramid z710e I start getting some robotic sound distortion on some phone calls I make (is getting fixed by enabling/disabling speaker), should I go back to 1.27? :confused:
[HTC Sensation] v.konvict:
I dont think the hboot has anything to do with sounds ....its probably something to do with rom you are on

sent by v.konvict
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
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
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Azeazezar:
Can you boot into recovery?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
I unfortunately can't get it to do anything.. I am hoping there's something I can do that i haven't tried.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
What the PDA and bootloader task? How did you do it?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
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
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Azeazezar:
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.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
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.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
Why did you even flash those files? Go to www.sammobile.com and download a firmware. Then flash it using Odin. Just use the PDA tab to flash the rom.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
It failed, can i try to flash with an older rom?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Azeazezar:
You can flash any rom from that site. i recommend avoiding the ICS roms though.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
How where why?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
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..
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
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.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
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:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
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.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
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 :o
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
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.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
Odin successful - but can't boot into recovery..
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
Why not? Power off the device. In fact remove the battery for a couple of seconds.. Then put it back. Press volume up home and power together till you see the N7000 logo and let go..
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
Tried it.. Nothing happens - but i can touch the screen and it'll vibrate?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
Any other thoughts as to how to move this thread along?

I'm really happy that there's people out there helping me with this situation.. :good:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
Can anything else be done in Odin?

Bootloader - Dunno what it does?

Phone ?

CSC ?

And what is a PIT file ?

:eek:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
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..
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
Sorry.. But I think it Fooked :crying:

Came back with this..

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> CODE_N7000XXLSA_549786_REV02_user_low_ship.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> boot.bin

<ID:0/004> NAND Write Start!!

<ID:0/004> data.img

<ID:0/004> factoryfs.img

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
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.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
have got to this stage o.k

Can you explain in simple terms what i should be typing please as I have never done this sort of thing before - thanks :eek:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
Type what's written.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
Microsoft Windows [Version 6.1.7600]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Stev>adb devices

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

List of devices attached

304D19FE9230A03F recovery

C:\Users\Stev>adb shell

~ # unmount/system

unmount/system

/sbin/sh: unmount/system: not found

~ # unmount /system

unmount /system

/sbin/sh: unmount: not found

~ # umount /system

umount /system

umount: can't umount /system: Invalid argument

~ # umount/system

umount/system

/sbin/sh: umount/system: not found

~ # umount system

umount system

umount: can't umount system: Invalid argument

~ # umount /system

umount /system

umount: can't umount /system: Invalid argument

~ # umount/system

umount/system

/sbin/sh: umount/system: not found

~ # umount data

umount data

umount: can't umount data: Invalid argument

~ # umount cache

umount cache

umount: can't umount cache: Invalid argument

~ # e2fsck -f -c -y /dev/block/mmcblk0p9

e2fsck -f -c -y /dev/block/mmcblk0p9

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: Superblock invalid, trying backup blocks...

e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p

9

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

~ # e2fsck -f -c -y /dev/block/mmcblk0p10

e2fsck -f -c -y /dev/block/mmcblk0p10

e2fsck 1.41.14 (22-Dec-2010)

/dev/block/mmcblk0p10: Updating bad block inode.

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

/lost+found not found. Create? yes

Pass 4: Checking reference counts

Pass 5: Checking group summary information

/dev/block/mmcblk0p10: ***** FILE SYSTEM WAS MODIFIED *****

/dev/block/mmcblk0p10: 20/131072 files (0.0% non-contiguous), 17230/524288 block

s

~ # e2fsck -f -c -y /dev/block/mmcblk0p7

e2fsck -f -c -y /dev/block/mmcblk0p7

e2fsck 1.41.14 (22-Dec-2010)

The filesystem size (according to the superblock) is 51200 blocks

The physical size of the device is 25600 blocks

Either the superblock or the partition table is likely to be corrupt!

Abort? yes

~ # reboot download

reboot download

C:\Users\Stev>

That's everything..
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
Looks like your system and cache partitions are damaged.. Try to format them blindly in recovery. Button series is as follows

volume down
volume down
power
volume down
power
volume down
volume down
power

So what you need to do is..

- power off and boot into recovery. Make sure you are on recovery by using adb devices command and it should show recovery.

- then use the above button series. This should blindly take you to formatting all the partitions except int and ext sd. Wait for about 30 sec and use abd command e2fsck on system and check whats the output..

Using the correct buttons is important ..else you might end up in a different menu.

PS: the button sequence is as per kernel XXLTA Philz.. There could be difference in other versions of kernel so if you didnot flash XXLTA version, first flash it.

Other command is

umount data
umount system
umount cache
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
Use umount cache and then run the command for mmcblk0p7 again.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
C:\Users\Stev>adb devices

List of devices attached

304D19FE9230A03F recovery

C:\Users\Stev>adb shell

~ # umount cache

umount cache

~ # e2fsck -f -c -y /dev/block/mmcblk0p7

e2fsck -f -c -y /dev/block/mmcblk0p7

e2fsck 1.41.14 (22-Dec-2010)

/dev/block/mmcblk0p7: Updating bad block inode.

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

/dev/block/mmcblk0p7: ***** FILE SYSTEM WAS MODIFIED *****

/dev/block/mmcblk0p7: 15/6400 files (6.7% non-contiguous), 1448/25600 blocks

~ #
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
OK.. Now in command window type reboot download.. Then open Odin and flash the XXLSA rom.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
Still failed I'm afraid..

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> CODE_N7000XXLSA_549786_REV02_user_low_ship.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> boot.bin

<ID:0/004> NAND Write Start!!

<ID:0/004> data.img

<ID:0/004> factoryfs.img

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
Download the attached file. boot into recovery.. same procedure you followed and this time use the below mentioned sequence.

volume down
power
volume down
volume down
volume down
power

once done.. in command window .. use

adb sideload "path of the downloaded file" (enter)

reboot recovery.

Check if you get the display in recovery.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
After the adb sideload command... There will a % transfer... After it reaches 100.. Wait for about 15 seconds before giving the reboot recovery command.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
Hi, I can't seem to add the write terminology into the command prompt to access the downloaded file - can you help please..

Thanks
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
write in command prompt

adb sideload

then a space and drag the downloaded file to the command window. This will put the path.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
it says error: closed
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
Did you use the button series ... use reboot recovery command and then follow ...

volume down

power

volume down

volume down

volume down

power

this activates sideload in recovery..

then use sideload..
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
I have followed your instructions (I think)..

They are as follows -

Remove battery-

press volume up + power + home buttons for approx. 15 sec?

check if screen vibrates?

follow button commands-

go into command prompt-

type adb devices-

it shows phone is in recovery-

type adb sideload & drag zip file into window and press enter?

Says error: closed?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
may be sideload is not getting activated or you are getting to a different menu..The kernel you installed was it, XXLTA v5.15.0 ? anyways...try this

remove the ext SD... and empty it.. place the downloaded file in it so that there is just 1 file... then boot into recovery... make sure it is recovery by using adb devices,

then

volume down

power -

power -

power -

volume down

volume down

power

---------- Post added at 05:33 PM ---------- Previous post was at 05:01 PM ----------

Or go to http://www.sammobile.com/firmwares/3/?download=4510 and download the firmware and extract the zip and check if there is a "N7000_APBOOT_N7000ZSLPF_CL558430_REV02_user_low_sh ip.tar.md5" file in it.. if yes this is the boot loader to be flashed using odin.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] marmyte:
I've used PhilZ-cwm6-XXLTA-ATL-5.15.0.tar.md5
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
Did you try the other method? If not try the new firmware and extract the boot loader..