T-Mobile Note 4 MODEL NUMBER: SM-N910TZKETMB - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

I have a T-Mobile Note 4 MODEL NUMBER: SM-N910TZKETMB and I tried to root it using the the steps showed on the forum but I couldn't I only have a Fail message in ODIM every time I tried. Any one have a clue on how to root it. I tried different methods XModegame and nothing seems to work always have the same error it start and ones it goes by half or more on the process I have the fail message in red in ODIM

This has happened to me a couple of times before ,and the fix was either a different cable or a different pc. Try a different cable first

Thanks I will check and let you know if I have luck
Sent from my SM-N910T using XDA Free mobile app

No Luck
ctrlaltdeln said:
This has happened to me a couple of times before ,and the fix was either a different cable or a different pc. Try a different cable first
Click to expand...
Click to collapse
I tried with 4 different cables and two PC's, 3 different versions of ODIM and no luck I always get this message in ODIM:
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img.ext4
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ariosvelez said:
I tried with 4 different cables and two PC's, 3 different versions of ODIM and no luck I always get this message in ODIM:
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img.ext4
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If you used the original Samsung charging cable that came with the phone and you tried all of your USB ports on your computer then it is most likely your phone's charging port. In which case you're going to have move the charging cable until you have a connection and then keep the phone still while doing the upload.
Only use the original Samsung charging cable that came with the Note 4 and lay the phone and cable on the table completely still until the upload is complete. You might try wiggling the charging plug while it is inserted into the phone to see if that is causing the issue. Be gentle, if it is already partly broken contorting it more will make it much worse.

Also, run odin as an administrator.
Pull out both SD card and sim card.
Turn Knox off if enabled

I tried with the original cable and with 3 other cables, I have conection but it fails and is not the cable or the port because I try it with the original .tar and it worked in odim.
Sent from my SM-N910T using XDA Free mobile app

Download the samsung usb phone drivers, install it (even if you installed it before), and only use that odin for that phone/device. I've noticed for whatever reason, Odin is very device specific (or so it seems for me) and because of that is very finicky. Make sure that your Odin has a Tmobile DLL in it also. Try different usb ports. My laptop has 4 ports, 2 of which are 3.0, I tend to have better luck on the 3.0 ports than the 2.0 ports, don't know why. Also best to make sure that the battery is above 70% when doing it, that seems to help also. In odin load the file first, then plug in your device to the pc, and finally run. I seem to have the best luck with that order. It tends to fail if I have my device plugged in ahead of times.

dcoke said:
Download the samsung usb phone drivers, install it (even if you installed it before), and only use that odin for that phone/device. I've noticed for whatever reason, Odin is very device specific (or so it seems for me) and because of that is very finicky. Make sure that your Odin has a Tmobile DLL in it also. Try different usb ports. My laptop has 4 ports, 2 of which are 3.0, I tend to have better luck on the 3.0 ports than the 2.0 ports, don't know why. Also best to make sure that the battery is above 70% when doing it, that seems to help also. In odin load the file first, then plug in your device to the pc, and finally run. I seem to have the best luck with that order. It tends to fail if I have my device plugged in ahead of times.
Click to expand...
Click to collapse
ariosvelez... were you able to root it after all that advice and do you still have this model
---------- Post added at 02:20 AM ---------- Previous post was at 02:17 AM ----------
ariosvelez said:
I have a T-Mobile Note 4 MODEL NUMBER: SM-N910TZKETMB and I tried to root it using the the steps showed on the forum but I couldn't I only have a Fail message in ODIM every time I tried. Any one have a clue on how to root it. I tried different methods XModegame and nothing seems to work always have the same error it start and ones it goes by half or more on the process I have the fail message in red in ODIM
Click to expand...
Click to collapse
ariosvelez......sorry I meant to reply to you
were you able to root it after all that advice and do you still have this model

ariosvelez said:
I tried with the original cable and with 3 other cables, I have conection but it fails and is not the cable or the port because I try it with the original .tar and it worked in odim.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
I always get this error for some reason. I can't flash any firmware with an extension .tar.MD5 If you remove the .MD5 from the filename it works everytime

Related

[Q] So frustrated... can't flash back to stock 2.1!

I've been trying for the past couple of hours to flash back to stock 2.1 so I can load Serendipity onto my phone which will hopefully solve some of the hardware problems I've been having on stock 2.2 (rooted). My Captivate is an At&t phone that I use on the Canadian Rogers network.
Problems:
- Battery Life
- Nobody Can hear me during voice calls or I sound far away
- Random Shutdowns (Captivate keep alive helps but drains battery even more)
I have tried several methods to flash back to stock, with varying results.... none of them successful.
Using AIO Captivate Toolbox it hangs on file analysis
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
Using Odin v1.3-1.7 flashing to JF6_secure.tar.md5 it hangs on SetupConnection
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Check MD5.. Do not unplug the cable..
<ID:0/004> Please wait..
<ID:0/004> Checking MD5 finished Sucessfully..
<ID:0/004> Leave CS..
<ID:0/004> SetupConnection..
I have removed the battery, restarted the phone, restarted the programs, restarted the computer, removed sim and sd cards numerous times in different orders...
I've reinstalled the Samsung USB drivers (which solved the problem when I was trying to root 2.2 on my phone)
I apologize if my problem has been solved on another thread but I've tried searching everywhere online to no avail. I really want to try Serendipity but things are not looking good!!
If you have a Captivate, try using DesignGears One Click Odin http://forum.xda-developers.com/showthread.php?t=731989. Make sure that you are in Download mode before trying to flash and make sure that Odin is open before you plug in your phone. Also, you might have a bad cable or you might want to try to plug in your USB cable into a different port. Make sure the USB port on your computer you are using is a USB port directly on the computer. The ones on the back of a desktop work really well.
Good luck!!
I tried the One Click Odin but it was a no go... it hung at file analysis. So I thought I would try Heimdall but even after installing the drivers it said "failed to detect compatible device". Installing the right drivers was how I originally managed to get the root for 2.2 working, but it doesn't seem to have any effect on what I'm doing now.
I've been at this for a few hours now, and I'm not sure what else to do. I can live with crappy battery life but it's a pain when nobody can hear me.
BTW I'm using an iMac and when I plug the Captivate directly into the back Odin doesn't recognize it but if I plug it into the USB hub it does... weird. I don't think there is a problem with the cable because I've used it to root as well as when I updated to 2.2 via Kies.
Any more suggestions? I really appreciate the help!!
estefana said:
I tried the One Click Odin but it was a no go... it hung at file analysis. So I thought I would try Heimdall but even after installing the drivers it said "failed to detect compatible device". Installing the right drivers was how I originally managed to get the root for 2.2 working, but it doesn't seem to have any effect on what I'm doing now.
I've been at this for a few hours now, and I'm not sure what else to do. I can live with crappy battery life but it's a pain when nobody can hear me.
BTW I'm using an iMac and when I plug the Captivate directly into the back Odin doesn't recognize it but if I plug it into the USB hub it does... weird. I don't think there is a problem with the cable because I've used it to root as well as when I updated to 2.2 via Kies.
Any more suggestions? I really appreciate the help!!
Click to expand...
Click to collapse
There's your problem.. Odin doesn't work on Mac. You'll need to find a MS pc
BWolf56 said:
There's your problem.. Odin doesn't work on Mac. You'll need to find a MS pc
Click to expand...
Click to collapse
+1 odin is a windows tool.
Oh I have Boot Camp running Win 7 and Odin works fine on that. I simply tried Heimdall on both platforms to see if I could get it to work but no cigar.
Okay I've tried both Heimdall and Odin on two other computers, one running Win 7 and the other Vista. I managed to get the drivers to install on Zadig for Heimdall (the device wasn't even showing up on either of the Win 7 computers), but Heimdall still stated "failed to detect compatible device". Maybe time to start looking for an alternative to Heimdall and Odin? I'll keep my progress posted!
From Win7, did you happen to Right-click Odin and select "Run as administrator?" This is a simple thing, but Odin always gets stuck at that point if I forget to do it. Also, Odin should be up and running before placing the phone in d/l mode.
Weirdly odin will not detect my captivate even with drivers installed normally. The only way i get it to work is to reinstall drivers that come with AIO captivate toolbox each time i need to use odin...almost as if the drivers disappear every so often. Running win7 x64 btw
Sent from my SCH-I800 using XDA App
I tried running it as Administrator but still gets stuck at SetupConnection...

Issue with bricked phone and going back to stock...

I have a friend that bricked his phone by trying to install Cognition 5 v2.
Basically it would only boot loop the ATT logo. I purchased a jig and got it into download mode.
I have downloaded Odin 3 one click and Odin 3 1.81. From what I read I should use One Click, so I fired it up. I plugged in the phone and at first the pc would not recognize it, but by plugging and unplugging it found it. It showed 0:[com:9} in yellow in the box, so I clicked Start, and it ran its start processes:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
So here is where I stand, after multiple attempts it just sits at this point. I have waited up to 30 min for it, and it just sits there. Do I need to wait longer? or is there something else to try?
Odin never turns green and shows a blue bar, plus the phone never shows a blue loading bar either.
Are you running ODIN in ADMIN. Are you using a USB hub thats from the Mother Board (if desktop)
prbassplayer said:
Are you running ODIN in ADMIN. Are you using a USB hub thats from the Mother Board (if desktop)
Click to expand...
Click to collapse
Running as admin: Yes
USB Hub: No, plugged into back USB port on tower
I know this is going to sound dumb, but the exact steps you are doing? You should run ODIN in admin then plug your phone in download mode to the pc. It should appear and work.
Start Odin3 1.00 as an admin
Put battery into phone, plug in jig, unit goes into download mode
Plug phone into Micro USB PC cable (sometimes may take multiple plugins for it to recognize.
Once recognized in odin, I click start
Wait.....nothing.....
From what I see it looks like it is having issues with the repartitioning of it.
I also tried to use Odin 1.81 with aJH2 pit and tar file, and it just sits on Set Partition.
It shouldn't take multiple plugins. It could be a faulty cable. Also try another computer as well.
Ya, think I am going to try a diff comp, mine has had odin and stuff before, could cause issues. I will let you know what I find out.
Tried second coputer and a no go with it as well.
i downloaded heimdall just to try and I get it installed and connected, but when I go to flash it says this:
Ready for flash.Repartition was requested but bootloaders are not to be flashed.
IBL+PBL SBL PARAM KERNEL FACTORYFS DBDATAFS CACHE MODEM
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Beginning session...
Handshaking with Loke...
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
KERNEL upload failed!
Ending session...
So it seems there is something deeply wrong with it. Any ideas folks?
Don't think its the phone. It could be a faulty cable.
Ok, will try a different cable.
It definately was the cable. I tried a basic universal from Walmart and it worked.
So now I know not to use my wife's LG cable for anything but her phone.
Thank you for all of the help.
No problem glad you got it running ^^

[Q] interesting brick?

My phone was acting a bit erratic (running CM7 with Glitch v12).. I tried to Odin 1 click it back and start from scratch and now I get this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Key items:
-Phone does not power on by itself.
-3-button mode doesnt work, I get in by plugging the phone into PC w/ USB cable.
- I can get Odin One click to see the cappy & gets stuck on:
<ID:0/003> DO NOT TURN OFF TARGET!!
Anyone have a clue how to fix?
Please help. I miss my cappy. Thanks.
That is definitely download mode if it's pulling up on odin. I would give different ports and a different computer a try this issue has happened to me before sometimes you have to get it into dl mode before or after you start odin.
Hope this helps!
this has been covered in pretty much every thread that involves odin in any way...
reboot pc, swap usb ports to one in the back, if already in the back swaitch to another. right click on odin run as admin BEFORE you plug the phone in.
if you still get the issue try another usb cable, a different pc, or use heimdall instead of odin.
tried on 3 PCs on different ports. 2 different USB cables and both Odin & Heimdall.
no avail.
olebear1969 said:
tried on 3 PCs on different ports. 2 different USB cables and both Odin & Heimdall.
no avail.
Click to expand...
Click to collapse
Did you take your SIM card out? I know some people say it doesn't matter, but my phone will not flash with the SIM card in.
Try Heimdall on a Linux machine.
Bricked
Hello, I've installed Odin one click and i tried to start Odin. Once i started it, my captivate was going fine until it suddenly stopped like 2 minutes later. The screen turned read. I tried this 5 times and it kept doing the same thing, except it was red, green, and pink screens. Now my phone won't turn on. I think it's bricked, but i can still get on download mode. Can anyone please help me?
I'm sorry if i sound like a really big noob
studacris said:
this has been covered in pretty much every thread that involves odin in any way...
reboot pc, swap usb ports to one in the back, if already in the back swaitch to another. right click on odin run as admin BEFORE you plug the phone in.
if you still get the issue try another usb cable, a different pc, or use heimdall instead of odin.
Click to expand...
Click to collapse
This advice should help you out. I've saw the multi color thing when I didn't have my USB cable plugged into a port on the back of myPC.
benboy221 said:
Hello, I've installed Odin one click and i tried to start Odin. Once i started it, my captivate was going fine until it suddenly stopped like 2 minutes later. The screen turned read. I tried this 5 times and it kept doing the same thing, except it was red, green, and pink screens. Now my phone won't turn on. I think it's bricked, but i can still get on download mode. Can anyone please help me?
I'm sorry if i sound like a really big noob
Click to expand...
Click to collapse
1. Your phone is not hard bricked, yet. Don't panic. Read more and do as people are suggesting you.
2. Like studacris suggested, try other PCs, another USB cable etc. And Make sure to use the USB port which is directly on motherboard (not using some sort of USB extension or hub). Try another USB cable. Make sure it is in good contact with Phone as well as PC.
3. Download the Odin 1-click again to make sure you dont have the corrupt file.
thanks, i tried to do it on a mac and pc and it still wont work. My mac wont even recognize my phone. I left it overnight and i think the battery is drained. I dont think it's charging too. Is there an easier solution, or should I just send it back to atnt?
---------- Post added at 09:44 AM ---------- Previous post was at 09:19 AM ----------
IlluminatedOne said:
1. Your phone is not hard bricked, yet. Don't panic. Read more and do as people are suggesting you.
2. Like studacris suggested, try other PCs, another USB cable etc. And Make sure to use the USB port which is directly on motherboard (not using some sort of USB extension or hub). Try another USB cable. Make sure it is in good contact with Phone as well as PC.
3. Download the Odin 1-click again to make sure you dont have the corrupt file.
Click to expand...
Click to collapse
dude thank you so much. I've really thought it was bricked but the next morning i decided to try one last time, AND IT WORKED!!! you're a life saver
Tried linux over the weekend. Again, I can see the cappy, but no files get pushed.
My main concern is the grey box on the screen in DL mode.
olebear1969 said:
My phone was acting a bit erratic (running CM7 with Glitch v12).. I tried to Odin 1 click it back and start from scratch and now I get this...
View attachment 772593
Click to expand...
Click to collapse
Dude, that's the same HP laptop I have, come to think of it that's the same phone I have too. I call dopelganger.
Anyway on a serious note, I have always used the SATA/USB port one back from the USB port you had it plugged in to, and I have never had a problem during while flashing. Hope it helps.
apbthe3 said:
Did you take your SIM card out? I know some people say it doesn't matter, but my phone will not flash with the SIM card in.
Click to expand...
Click to collapse
(back after a long hiatus)
Yes, I always remove Sim Card & External Memory when flashing.

USB not working but system is alive - how to flash?

Hey guys,
I got a SGS I9000 here from a friend of mine who got it from egay (stupid, but nvm) and I try to fix the device but till now I was not lucky.
I want to upgrade to a newer / higher version but the "faulty" USB makes it very difficult.
Here are the facts:
- The device is running 2.3.3 Gingerbread
- Device Information: GT-I9000HKYDBT + PDA: I9000XWJVI , PHONE: I9000XXJVO, CSC: I9000DBTJV2
- Charging via USB does work, data connection does not work
- Entering Recovery Mode works
- CWM is not installed
- Samsung Kies is installed
- Entering Download Mode works
- External micro-SD Cards are being recognized at Android
- If I connect the device in Windows or Download Mode, the message "USB-Device was not recognized" comes up
What I`ve tried till now:
- three different micro-USB cables (original Samsung, HTC and Motorola)
- two different PCs with Kies installed and not installed
- Tried to flash via Recovery Mode but nothing is shown on the "external SD", even after renaming to update.zip
- Managed to copy files into internal flash but since the "original" Recovery Mode seems to have a verification, the flash process aborts either with
"E:signature verification failed" or "E:failed to verify whole-file signature"
- Odin of course but USB data does not work unfortunately so Odin as well
So the big question for me is:
Is there ANY chance to root/flash the device with the actual difficulties?
Any help or hints are highly appreciated.
Cheers
FaCeOff said:
So the big question for me is:
Is there ANY chance to root/flash the device with the actual difficulties?
Any help or hints are highly appreciated. Cheers
Click to expand...
Click to collapse
you may have to try all these http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571 But first break that cycle by removing battery and reinsert after a few min and check phone connection or Mobile Odin is another option
email the recovery file to yourself or upload to dropbox. then download to your phone and flash away!
Don't forget to thoroughly clean your micro usb connector. I once had the same issue with my sgs. Different cables or drivers didn't work. I was about to give up on it, but then fixed it by cleaning it with rubbing alcohol and very tiny dentaid toothbrushes.
Afterwards it worked like a charm. Worth giving a shot, since these connectors collect a lot of dust/dirt over time.
xsenman said:
you may have to try all these http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571 But first break that cycle by removing battery and reinsert after a few min and check phone connection or Mobile Odin is another option
Click to expand...
Click to collapse
Thanks for your fast reply.
I did mention this thread yesterday but after installing all different drivers, switching of the PC completely and disconnecting all devices, turning BT ON/OFF, switching between Dev Mode and MSD I'm at the same position as before.
Doesn't matter which cable I use, I just get always the same fking message about Device is not being recognized.
In the meantime, I got a 2nd SGS from a friend of mine which works perfectly after connecting the device with my PC.
It starts immediately with the driver installation and is ready in couple of seconds.
I also tried to put the cable carefully into the USB but it doesn't help either.
Any other suggestions?
FaCeOff said:
Any other suggestions?
Click to expand...
Click to collapse
That would mean, its your USB slot on the phone, that needs a solution, either you have to examine it very closely for damage to resolve it or its internal and you may have to change it.
hey
can u do to download mode??
if u can then upgrade using Odin...
And the uUSB issues cam with my SGS too,but after flashing the firwmare via odin there was no issues...i flashed 2.3.6 ValuePack..
U too can give it a shot..
xsenman said:
That would mean, its your USB slot on the phone, that needs a solution, either you have to examine it very closely for damage to resolve it or its internal and you may have to change it.
Click to expand...
Click to collapse
Yep, doesn't look good and now I'm quite sure this cannot be solved easily.
tchindalia said:
hey
can u do to download mode??
if u can then upgrade using Odin...
And the uUSB issues cam with my SGS too,but after flashing the firwmare via odin there was no issues...i flashed 2.3.6 ValuePack..
U too can give it a shot..
Click to expand...
Click to collapse
Well, as told above, I can enter download mode but USB DATA connection does not work!
So from my understanding, Odin only works if there's a valid connection, otherwise I could flash anything and would not have the problem
Mobile Odin does not work due to the root restriction.
Is there any way to flash another ROM or get the the device rooted with these restrictions?
Stuck on First Screen
Well this is not an answer to the problem. Well am having the same problem as you, just mine is more complicated.
I managed to root using Z4root by copying the APK file on external sd .
I got cmw and entered recovery.
I updated using the CM10-unofficial rom that is in the development forum
I restored the nand that i did in recovery and now the phone is frozen (Stuck) on the first boot screen (Galaxy S GT-i9000 SCREEN)
Now I can go to Download mode but I can't go to recovery mode.
Let me remind you that my USB data connection is not working.
So now I am looking for a solution that would permit me to flash without USB or allow me to go to recovery mode.
Or a tutorial on how to change the usb port myself.
Thanks in advance.
kigordid said:
Now I can go to Download mode but I can't go to recovery mode.
Let me remind you that my USB data connection is not working.
Click to expand...
Click to collapse
As long as you can get to download mode, flashing should solve your problem after you resolve the USB problem , which can be due a number of issues.
Somehow ROM changes and bad flashes, may have pin configuration changes on the phone, (just like changes in combo key functions when you use different ROM) ...so driver changes works for some
So you may have to try all these http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571 options to get your USB connection back. But first break that cycle by removing battery and reinsert after a few min and check phone connection , and try those options.
FaCeOff said:
Thanks for your fast reply.
I did mention this thread yesterday but after installing all different drivers, switching of the PC completely and disconnecting all devices, turning BT ON/OFF, switching between Dev Mode and MSD I'm at the same position as before.
Doesn't matter which cable I use, I just get always the same fking message about Device is not being recognized.
In the meantime, I got a 2nd SGS from a friend of mine which works perfectly after connecting the device with my PC.
It starts immediately with the driver installation and is ready in couple of seconds.
I also tried to put the cable carefully into the USB but it doesn't help either.
Any other suggestions?
Click to expand...
Click to collapse
Sorry to repeat my comment again, but if all these drivers aren't working for you, you should check your micro-usb connector. I'm pretty sure the connector is the issue here.
Have you tried cleaning the micro-usb connector on your phone? Don't just blow the dust out or clean it a bit with some paper, but go for a complete and thorough cleaning solution.
Get yourself some dentaid toothbrushes. Get a few sizes. You can get these at your local pharmacy.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Get some Cleaning / Rubbing Alcohol. You can find this at a handyman store or your local pharmacy should have this as well.
Dip the toothbrush with some rubbing alcohol. The toothbrush should be a bit moist but not dripping wet.
Start cleaning the connector. You can apply some pressure to clean everything.
If this doesn't work, no harm done. These things are quite cheap and rubbing alcohol and these dentaid toothbrushes come in handy when other electronics go bust.
Honestly, just try it! People always dismiss this solution attempt as a last resort but it's usually the problem fixer.
I fixed mine that had the same problem with a similar technique
Sent from my GT-I9000 using Tapatalk 2
Trying using mobile Odin.
Establish best recowery mod fix and adb on your computer.
without root and probably will not even cwm mobile Odin.

[Q] Bootloop, no Recovery Mode, phone not detected in Download Mode

Hello,
First: I know these problems have been reported before, but to no avail AFAIK...
So, here's my problem:
My girlfriend's SGS 9000 (International Version) got stuck in a boot loop after randomingly crashing (running CM 9).
The recovery-mode key combination does not work, but I can enter Download Mode.
The problem is now: KIES (latest version) and ODIN won't detect the phone (tried v 1.85 and 1.83) at all. Heimdall Frontend (v 1.3.2) says "Device Detected" but if I try flashing it aborts with
Uploading PIT
ERROR: Failed to send file part packet!
PIT upload failed!
Ending session...
ERROR: Failed to send end session packet!
Heimdall crashed!
(see screenshot attached)
In the utilities section when I try to download a PIT it gives this Output:
Initialising connection...
Detecting device...
ERROR: Failed to retrieve config descriptor
(see screenshot attached)
I've reinstalled the Windows drivers (I'm on Windows 7) several times. I've tried having the latest KIES installed (but not running in the background, of course), I've tried just installing the "naked" driver (from the Samsung website). All to the same result:
Windows detects the device (as "Gadget Serial", driver by "Samsung Electronics Co Ltd), it won't show up as a mass storage device though.
ODIN and KIES do not detect the device at all, Heimdall "detects" the device but can not upload anything or "retrieve config descriptor" for PIT Download.
I've tried several USB-cables (including the original Samsung one) and USB-ports. They all work perfectly fine with my Nexus 4 and Nexus 7.
So, please, am I just missing something very obvious here or is there really no help for this semi-bricked thing?
Thanks in Advance!
Jakob
got stuck in a boot loop after randomingly crashing
Click to expand...
Click to collapse
Can't remember, which one ICS ROM I used before, but I got this problem too. To solve it I used old Heimdall v1.1 + zadig to install the latest stock firmware
diotallevisheir said:
So, please, am I just missing something very obvious here or is there really no help for this semi-bricked thing?
Click to expand...
Click to collapse
most solutions listed here and heimdal 1.3.2 had some issues, so try earlier versions . best would be to test on another PC or better still lap top and odin3 for flashing , preferably not win 7, 64 bit or win 8
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​
@diotallevisheir in Odin is rule-of-thumb that you must flash PIT file if you have checked re-partition. Use now your Odin 1.83 and flash again the stock ROM under PDA, but download also PIT file for i9000 and choose it under PIT (Odin will check re-partition then by default) file name ends with 512.tar
It should unbrick it.
And @xsenman is right, the flashing would have more chances to be successful if you would use a laptop with WinXP 32-bit
thank you very much, sir!
DumF0rGaming said:
Can't remember, which one ICS ROM I used before, but I got this problem too. To solve it I used old Heimdall v1.1 + zadig to install the latest stock firmware
Click to expand...
Click to collapse
What can I say, apart from thank you a 1000 times! :good::good::good:
This one actually worked!
Used the "restore.bat" and "Flash without repartition" and it just worked! And nothing else did!
You just saved me from a lot of trouble and my gf says thanks as well

Categories

Resources