samsung note 1 N7000 do not boot - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Hello,
I have read many posts, very interesting but no solution of my trouble.
My phone does not boot.
I have tried a factory recovery, nothing.
I have installed the USB driver, the ODIN. I tried to communicate through ODIN with different stock ROM, different ODIN versions, USB drivers and computer, nothing.
Maybe the reason is that the settings of the phone is not set to accept downloading through USB port.
What is your opinion?
Thanks
for information the configuration is
phone samsung galaxy N7000GSMH,
windows8,
USB_Drivers_1.5.27.0,
odin V3.09, V3.10, V3.12
ROM N7000XXLRI_

Se
Pleaze, does anyone have an idea?
I read that I should enable the usb debug in my device, but the phone is stuck in the boot....
Please help

Can you enter the recovery mode ?

I have the same sort of issue. My current phone just bricked itself, so I reached into the closet and pulled out my old GT-N7000, only to find it won't boot. Only the initial boot screen is displayed.
Charging mode works, and I can get it into download mode , - but not recovery. Odin recognises the phone, though not consistently. When I try to flash a stock ROM via Odin, with or without repartitioning (PIT file), Odin begins the operation and just stalls indefinitely.
Does this indicate hardware failure?

Related

[Q] Semi-bricked, USB not recognized, doesn't even charge

Hi!
After searching the forums for a while I did not find a thread exactly matching my problem, so if I've overseen it, please just point me there.
To my problem:
I did a very stupid mistake, flashing a new custom ROM with a different kernel (as usual, cooked in Docs Kitchen) without converting back the lagfix. So I ended up with a non-booting phone - so far, so bad. Note to myself: Never flash a phone during the carnival weekend again.
So I booted into download mode and tried to recover it via Odin, but here I got my really bad surprise: USB device is not recognized, thus I Odin does not see the phone.
I tried 4 different PCs with Win7 or XP, a Linux desktop and a Macbook. I also tried 5 different USB cables (they all work with other smartphones like the Desire and the HD2). Wherever I stick the phone in, it is not recognized (code 10/code 43 in Win7). I used the stand-alone-drivers from the sticky forum thread here, and also most recent Kies versions, always the same: USB device not recognized.
Does anybody have an idea how to revive the USB connectivity? I'm almost at the point to send it in for repairs...
Or can someone elaborate how I could have killed USB with corrupting the ROM? I've to admit I do not really understand how these two are connected.
--Jens
Hi Amokbunny
You get into download mode but the PC won't recognize the phone?
That's messy and I can think of nothing that could have done that. you did not change the bootloader did you (flashed a full samsung ROM containing a bootloader, for example VJ1)?
If not I guess it's a hardware issue.
formatted to ext4 without any backup
I did a very stupid mistake too. Got darky's rom 9.3., installed i, everything worked great(really awesome thing), then i wnt to recovry mode and entered tthe speedmod and it showed mr that my phone has rtf files system not EXT4 as it should be, thou i installed the speed mode. then i chose to repartition it to ext4 but i didn't choose the backup. Just clicked to format the sd. It did formatted to EXT4, rebooted, i saw the darky's rom logo and the the phone vibrated and the logog of the droid just flashed. I tried to enter recovery mode-didn't load. Started the download mode connexted to pc used ODIN 1.7 with PDA I9000XXJPY.tar, MODEM I9000XXJPY.tar, GT-I9000-CSC-MULTI-OXAJPY-LITE.tar s1_odin_20100512.pit.
The phone has started, appeared teh stok galaxy s logo and it's just flashing. Help needed. Don,t know what to do know. I have galayx s i9000 european version.
somehow i've managed to install new firmare 2.2.1 /I9000XXJPY-baseband /2.6.32.9 [email protected] #1-kernel version, but z4root isn't working. When i start permanent root the programm ends on aquiring root shell, the debug mode is on
Got it all running, installed Darky's rom 9.3. Thanks anyway.
theduckking said:
Hi Amokbunny
You get into download mode but the PC won't recognize the phone?
That's messy and I can think of nothing that could have done that. you did not change the bootloader did you (flashed a full samsung ROM containing a bootloader, for example VJ1)?
If not I guess it's a hardware issue.
Click to expand...
Click to collapse
Yep, I can boot into download and recovery modes, but that's it.
The only apparent change in the new custom ROM was the kernel.
I also cannot really access my external SD card (it shows me some phantom files, but not the actual content of the SD), otherwise I'd try to recover it this way.
I agree with the hardware issue, if it wouldn't have coincided with the flash procedure...anyway, I think I'll send it in for repairs if I don't get it to run on this sunday.
I have the exact same problem, except that I can access my external SD. I got the problem after upgrading to Darkys Rom 9.3 the usual way, but switched from Speedmod to Voodoo. After that update, my USB didn't work anymore.
I can't get neither Xp or Win 7 to recognize my phone. USB device not recognized, and tried all the tricks. Reinstalling Kies and drivers, switching between the different modes (storage, kies media, ask, debug...) But still no USB connection.
I updated to darkys 9.5 (transferring the rom using bluetooth, and updating using CWM), but still it doesn't work.
Can get it into download mode, but still can't connect using USB and Odin.
HELP!
Did anybody ever find a solution for this?
European version of I9000, bought in Denmark. No Simlock
Same thing here after installing JV1 + Ultibread Rom 1.4... Still no solution
*shameless push*
Any solution here? I dont have that problem, but it sounds too scary to not have a working solution :S
Same prob here! Any news?
Any solution? I have the same problem.
same problem my phone is bricked while flashing a stock rom the windows disconnected the phone while flashing
ended with device not recognized even in download mode
bassem8246 said:
same problem my phone is bricked while flashing a stock rom the windows disconnected the phone while flashing
ended with device not recognized even in download mode
Click to expand...
Click to collapse
But if you are in download mode on your fone you'd rather should have a look at your configuration on the computer. Because the fone still can be flashed if the symbol for download still appears.
- Kies is shut down while ODIN is active?
- latest Samsung USB driver installed?
- Odin started with Admin?
Btw. did you try to get into recovery mode? Maybe this also still is working as the partition is quite small and chance high that it was flashed w/o faults. So you may be able to flash a zipped ROM rather than a tarball for Odin.
USB Not working when Phone plugged in... try these..
Unplug Device from PC..
Windows go to Device Manager...
Scroll down to Universal serial bus Controllers
Start with the top one and work your way down ..uninstall them all..
When done reboot Computer and let it install them all.. then try again
2.Settings --> USB Setings (under wireless & network may differ depending on Rom used) --> Try other settings Mass storage
3.Different USB ports on PC
4.Uninstall KIES from PC (reboot PC to take effect) and Reboot and just install samsung USB drivers....
5.Using windows type in msconfig in Start>Run box... windows will pop up and untick KIES from STARTUP TAB
Apply to take effect and restart machine.. try using ODIN to Flash ROM
I myself only use the Samsung USB drivers and ODIN never use KIES
or ...Check my signature and try SD formatter

[Q] Bricked Galaxy S : Download mode corrupted?

Hi everyone
So here it is : No program is able to recognize/detect my Galaxy S i9000M (Bell Vibrant) when it's in download mode, so I can't flash any ROM. My phone is currently fully bricked and unusable. I cannot access to the recovery mode with the three-button thingy or by "adb reboot recovery"
I bricked using Odin 1.8, trying to flash a 2.2 froyo stock ROM from Samfirmware. The flashing went ok, but it failed to reboot. Actually, the screen was turned off and nothing was happening. I figured out it was fully bricked so I made a USB JIG, it worked. I can access my download mode.
I connected the phone to my Windows 7 computer and used Odin to flash back to 2.1 Eclair, with a stock ROM from Samfirmware. It failed (I don't remember the error message, it was a couple days ago...).
I tried with Heimdall Frontened. It had a problem uploading the .pit file, so the flashing didn't work.
Now each time i connect the phone to my computer, Windows (and Heimdall frontened and Odin) doesn't detect it,which means that I can't flash anything on it even though it is in download mode.
I have tried reinstalling like every driver on earth, still not responding.
I tried on another Windows 7 machine and on Ubuntu, the device is not detected.
I tried with different USB cables, nothing happens.
This is my hypothesis (maybe silly) : Could the problem be the Download mode being corrupted?
Whatever... I could use some help from you guys.
Thank you,
Sam
I had/have the same problem.
I installed the Samsung Kies and now my computer recognize my phone again.
But I have still no idea what I need to flash to make my phone working.
goldsage said:
I had/have the same problem.
I installed the Samsung Kies and now my computer recognize my phone again.
But I have still no idea what I need to flash to make my phone working.
Click to expand...
Click to collapse
That is strange... I tried installing Kies and it didn't detect the phone. And you could just flash any 2.3 stock ROM with Odin I guess.

Galaxy TAB P1000 NOT Detecting in ODIN

Hello xda users,
I need HELP !
I have a galaxy tab P1000
currently froyo 2.2
wanted to upgrade to GB
Tried the Odin way from another link on this site (MANUAL updation for galaxy tab(p1000) into 2.3.3 gingerbread ), it failed and the Tab got soft bricked,
somehow managed to unbrick it, now its back to its original fw, but it keeps restarting in a loop until i switchd the damn thing off completely
I have tried to go in download mode to flash but odin doesnt recognise it , tried differnt computers too, no use.
I have gone in recovery mode, hard reset, wipe cache , still when i switch it on, it goes in a reboot loop.
tried to use heimdall. cant get sucess as i might not understand how to use it properly
Please help.
Sincere thanks to you if you can help me get my tab up and running., if not in GB atleast back in froyo.
(PS- i im not worried about my data , and i have not backed up the rom etc before doing any of these)
Try to reinstall or install a usb driver from samsung
tried that before , didnt work
anyway now i managed to get it detected on ODIN and flashed it to GB
Libon
Yeah, happened to me too, nearly had a sh*t my pants when Odin didn't recognise my Tab.
I would recommend -
charge the Tab fully using wall adapter (4 hrs+)
plug it in with Odin open and using USB cable
don't expect Odin to recognise the Tab immediately
check back after 5 mins or so (I don't know, does Odin refresh?)
I was able to restore my Tab from the PC - ! - Marvin screen.
I don't want to go back there again though!
yea dude.. same here
i kept it on charge for a couple of hours and then tried.. bam it conencts..
Libon
Tab not turning on
HI Guys I have Galaxy 1000 .I was updating it by using kies in between the process my computer shut down and when I am trying to connect my tab again its not turning on .can some one help me please ?
Waiting no charge baterry 2 3 j
Run odin
Connect tab . Wait Long time 20 30min
Tab is. Détect go flashing
Sorry for my english
I m.. French
Envoyé depuis mon GT-P1000
GT P1000 Odin wont detect
hi guys can you help me on my GT P1000 odin wont detect it even after 2-3hrs. tried everything but odin wont detect my device.
thanks in advance...
iamkakers said:
hi guys can you help me on my GT P1000 odin wont detect it even after 2-3hrs. tried everything but odin wont detect my device.
thanks in advance...
Click to expand...
Click to collapse
do u have samsung kies installed in your pc? if does, kill the kies process (Ctrl+Alt+Del). close, and open odin3, put your tab into download mode, and then plug it into usb port. try to change different ports.
i always had this problems.. if all if that didn't work, i'll format my pc
Sent from my GT-P1000
odin3
hi
i also have a gt p1000 and odin3 doesnt detect the tab. i've been trying to root my tab for a while, tried odin and it doesnt detect, tried doomlord and it doesnt even get past the first step. i tried uninstalling kies on my windows 8 laptop and still no luck im not too sure what to do. is there something that i might be doing wrong because i follow all the info thati get from here.
is there another rooting app i can try that doesnt brick my device? and or is there an app that i can get that i am able to use a ps3 controller on my device that does not require a rooted device. please help
thanks
My Galaxy tab also doesn't connect to usb after cache wiped humber os flash
Thanks in advance guys!..
Earlier I was using Cyanogen mode 10 Custom ROM but has few issues like recognize SD card.
later I flashed to Humber OS caused real problem.
It was clock work recovery installed but my tab tab boots stays on screen humber OS.
It goes to recovery mode, and also to some unknown recovery mode.
Either the way not recognized by computer. I tried all options like heimtal an Odin. No help.
Friends any help, would be highly appreciated.
BUMP
Any solution to this given the fact that usb drivers have been installed?
Are you sure it is recognised by the computer before trying Odin or Heimdall?
I seen this in a post:
#################################################################################
4 Reasons Why Odin is Not Detecting Your Android Device:
Reason 1: No drivers installed for your phone
Most of the time Odin is not able to detect your phone, simply because you haven’t installed the drivers for your phone. Normally windows would automatically download the respective drivers for your phone from the internet and install it. But in case it isn’t able to do so, you need to download the drivers from your phone manufacturer’s website.
Reason 2: Inferior quality or damaged USB cable
Odin is very sensitive to low quality or damaged USB cables, which is a major reason why odin will detect your android phone in file transfer mode but fail to detect it in download mode. You might have a genuine USB cable that came with your Android phone but with time its quality will depreciate, which is why you might have to get a new USB cable.
Reason 3: Odin is corrupted
This happened once with a reader on my blog, we tried everything to solve his problem, but in the end using a different version of Odin worked out for him.
Reason 4: USB port is defective
Defective USB ports can also be a reason for Odin not detecting your Android phone. This was a problem faced by one of my readers and plugging the USB cable in another USB port worked out for him.
#######################################################################
and I need install cwm recovery on a twrp recovery and just do that with this app:
ROM Manager
if you want do same job; you can download it from google play easily!
and install recovery,rom or restore backup with it.
farza(db)astany said:
I seen this in a post:
#################################################################################
4 Reasons Why Odin is Not Detecting Your Android Device:
Reason 1: No drivers installed for your phone
Most of the time Odin is not able to detect your phone, simply because you haven’t installed the drivers for your phone. Normally windows would automatically download the respective drivers for your phone from the internet and install it. But in case it isn’t able to do so, you need to download the drivers from your phone manufacturer’s website.
Reason 2: Inferior quality or damaged USB cable
Odin is very sensitive to low quality or damaged USB cables, which is a major reason why odin will detect your android phone in file transfer mode but fail to detect it in download mode. You might have a genuine USB cable that came with your Android phone but with time its quality will depreciate, which is why you might have to get a new USB cable.
Reason 3: Odin is corrupted
This happened once with a reader on my blog, we tried everything to solve his problem, but in the end using a different version of Odin worked out for him.
Reason 4: USB port is defective
Defective USB ports can also be a reason for Odin not detecting your Android phone. This was a problem faced by one of my readers and plugging the USB cable in another USB port worked out for him.
#######################################################################
and I need install cwm recovery on a twrp recovery and just do that with this app:
ROM Manager
if you want do same job; you can download it from google play easily!
and install recovery,rom or restore backup with it.
Click to expand...
Click to collapse
reason 1: my phone is samsung and it's detected by ODIN, kies and I transfer files from and to my computer without problems. also tried reinstalling just in case but nothing, so I guess this is not the answer for my problem
reason 2: tried with original cable, but as I didn't use the tablet for a long time I also thought it could be the cable, so I asked a friend of mine if he could lend me one cable, but that didn't work. pity. :/
reason 3: tried 3 different versions of ODIN, and in every version my phone (mentioned above) is detected. shame. :S
reason 4: tried the 3 different USB ports in my laptop. two 2.0 USB ports and one 3.0 USB port, so again I doubt this is the reason of my problem.
extra reason: ~~~ maybe it's the OS version ~~~ // this laptop came with windows 8 preinstalled. nothing. then, I updated to win 8.1. again nothing. now I'm running windows 10 and the same, nothing is detected neither by ODIN nor the computer. also tried in 4 different computers running win xp, win 7 and other with win 8.1.
btw, thank you anyway for your apportation; this may help other people, but unfortunately, it's not my case, so can anybody else join me to think about a new reason and a way to solve it? thank you very much :good: :highfive: :fingers-crossed:
~~~~~~~~~~~~ EDIT ~~~~~~~~~~~~
I have continued researching and found a software. it didn't work for me, but maybe it works for other people.
-first, you have to make sure you have java installed on your computer.
-second, extract the oneclick.rar file on an easy-access directory.
-third, put your tab on download mode (while charging icon when tab is turned off, press power + volume down until a yellow triangle appears).
-fourth, click start unsoft-brick and let the magic begin! 8)
note: if a warning error pops up, trust the software and click on resolution center and follow the instructions of one of the three "alternative ways".
download: https://www.dropbox.com/s/8ix6yygu23a1kjn/OneClick.rar?dl=0
good luck!!
help
blizzard_boy said:
tried that before , didnt work
anyway now i managed to get it detected on ODIN and flashed it to GB
Libon
Click to expand...
Click to collapse
hi can you plz help me out with the processess you followed to as im suffring the same problum only CWM working and even it shows sd card mount error also not installing any rom via SD card showing error and odin not detecting it nothing happening only CWM and blank screen
blizzard_boy said:
tried that before , didnt work
anyway now i managed to get it detected on ODIN and flashed it to GB
Libon
Click to expand...
Click to collapse
How did you did it im having the same error???
i did the same thing with my tab exactly like yours plzzzz help me recover it

[Q] N7000 not recognized by windows.

Hello all,
My mother has a GT-N7000 running complete stock.
It updated something according to ehr saying and afterwards it rebooted.
After the reboot it rebooted again and now its bootlooping, it shows samsung and plays the sound.
The bleu glaze comes up and the the device reboots.
I cant get into recovery with vol up+home+power button combo.
It boots to it and it shows the droid with the sort of cubic icon spinning in its belly and after 3 sec the device reboots.
I cant do a factory reset there so i read about Odin and reflash stock image.
I downloaded the proper file and Odin 3.0.9 and installed samsung drivers.
I dont have Kies installed as i read it could give problems.
The device does go i ndownlaod mode but my PC running w7 ultimate 64bit doesnt recognize the device.
I tried 3 different USB ports from the Mobo, and i tried a couple of diferent USB cables.
One of the cables is original Samung U2 cable.
Everyt time i connect the device winodws shows the message: the USB device isnt recognized.
Odin doesnt register anything so i cant flash a thing with it to restore.
Does this mean the device is bricked?
Does the N7000 has some sort of unbrick JTAG mode or something or would linux help to rewrite all partitions?
Thx for any tips.
With best ergards,
Mister_mini
Edit: thinking back it could be possible USB debuuging has been turned on but im not sure on this part.

I9001 stuck in bootloop twrp

Guys i have S Plus i9001. i just factory restored the custom rom 5.1.1 now phone is stuck in recory loop of twrp recovery. i tried connected to odin but in download mode it says. unrecognized device. but my vibrant T959 in connecting to same odin using same cable in download mode. i tried almost every thing on internet but no progress. reinstall drivers. even all drivers of computer. updated them. tried three cables and two versions of odin.
P.S: Odin is detecting it in RAMDUMP mode.
Guys please help if anybody knows
I posted the guide

Categories

Resources