Hi guys, I am desperate and in need of help ...apparently my Note decided to die on me and I think I just made it worse. Please whoever has any suggestions please help me.
For a good while now I had been running Paranoid Android without any problems whatsoever until last friday my phone woke up stuck on the start screen (the one that says GT-N7000). Please note that NO changes were made to the system nor were any new apps installed. Rebooting the phone resulted in the same situation.
After noticing that it was stuck, I figured I would go into recovery and try clearing cache as that sometimes will help, to my surprise the phone was unable to go into recovery, it would just present a blank screen.
I could still go into download mode, so I thought I would go back to stock through ODIN eand re-root and re-flash, when i tried this ODIN hanged at this point:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLA4_N7000OXALA4_N7000XXLA4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> factoryfs.img
<ID:0/007> NAND Write Start!!
I tried several GB and two JB stock ROMs, both ended up with the same results. I also tried flashing this through ODIN 1.83, 1.85 and 3.07 with no luck.
Then I got worried that my phone had somehow gotten bricked (overnight with no change which I know does not make sense), and I found forest1971 thread on how to revive a bricked Note. Following this thread I tried all PIT files from 2.0 up to 2.5 and ODIN hanged at this point:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
After this I got really desperate, so I went ahead and tried the manual method, and tried flashing Speedmod kernel in order to be able to access recovery again as is instructed in the thread. ODIN hangs during this process as well, thus not installing the Kernel but it did give me the yellow triangle and increased my binary flash count. I had managed to avoid this throughout my whole 10 months of owning the phone by doing things correctly, and now I cannot send it to Samsung even though I would still have 2 months worth of warranty eliminating the possibility of sending it back to them.
So in summary I can't access recovery, I can't flash a stock ROM, I can't flash kernels and now I have the yellow triangle. Please also note that I have tried with several USB cables, updated drivers and several PCs.
What can I do about this? Is there still some sort of hope for my phone? Can the triangle be somehow removed without access to recovery or the ROM? and finally how on earth could my phone do this from one night to the other without me installing or doing anything to it?
Thank you very much, any ideas will be greatly appreciated.
Related
Hey all,
I've softbricked my Captivate and back to download mode using a JIG. It took me awhile to get it there as well. Anyhow, my phone is connected to the PC and is recognized by the OS and Odin3 3 Button Fix v1.81. It is not detected by Odin 1 click. When I attempt to flash back to stock, Odin REALLY enjoys to "setupconnection" with my phone. So much so it stays there for 10+ mins. I've heard people say that the PDA check box causes this issue. I've flashed to stock before and it hasn't been an issue until now. I was wondering if I can leave out the PDA.zip just to get back to stock 2.1. Would there be many ill effects? Especially if I'm just going to flash to a custom ROM?
I was on CM7 Nightly build 14. I attempted to recover back to Phoenix Ultimate using CWM. It failed when installing something that had to do with boot. Should I also add a bootloader file to the Odin install?
Thanks!
Just restart your PC and try one click odin...if Odin 1.8 is detecting then one click odin should also detect IMO...
I am not 100% sure but you do need PDA to flash to stock...try Icezar's package, its safest way to flash to stock..
Not really an answer to your question, but did you have repartition checked when you used odin? To return stock?
Sent from my GT-I9000 using XDA App
I did have re-partition clicked. I got the same results with and without it clicked. I had it showing up in Odin 1 click, but that got stuck with file analysis or the like. Now I have the Phone ! PC screen and I'm not sure how to proceed.
EDIT: Sorry for lying, back in download.
EDIT: Using Icezar's Package
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Enter CS for MD5..
<ID:0/003> Check MD5.. Do not unplug the cable..
<ID:0/003> Please wait..
<ID:0/003> Checking MD5 finished Sucessfully..
<ID:0/003> Leave CS..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So, Odin was flashing and the battery fell out. /cry
JIG now opens Phone ! PC screen and the Odin won't recognize it. I've had Odin opened first and loaded all information before hand. No luck so far.
Any tips?
EDIT: New Captivate coming from ATT. Thanks for the help everyone!
Hi,
my girlfriend just came back from China with a P1000 from her friend. As the whole device was running on chinese language and for some strange reason it was not possible to enter System Setting to change the language, I decided to flash her the latest firmware and just make a fresh start. (i'm a flash veteran on my SGS since 2 years, so I know how to use Odin)
I downloaded the P1000XWJQ8 from Sammobile, fired up Odin and flashed the new ROM with repartition enabled.
The procedure went through without errors:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P1000XWJQ8_P1000XXJPZ_P1000DBTJQ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> cache.rfs
<ID:0/003> hidden.rfs
<ID:0/003> modem.bin
<ID:0/003> factoryfs.rfs
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/003> Added!!
At the end of it the device didn't auto-boot as expected, it just stayed there with a black screen!!!!!!
Disconnecting and reconnecting it triggers in Odin the REMOVED and the ADDED lines but nothing happens.
I cannot switch on, cannot go into download nor recovery, the device just seems to stay dead :-(
My next idea was trying to pull the battery but apparently the battery is glued to the casing, so before I do more damage, I better start asking here.
Hope someone can help, my girlfriend will kill me if I can't repair this damn thing...
EDIT: after having closed Odin on the PC I tried to connect the device again and it started to play the startup song and Win7 started to install the new drivers from the new firmware. 7 out of 9 found drivers installed correctly, 2 instead failed.
But nothing changed to the vegetarian state of the P1000
EDIT 2: now, after 12 hours wait, the device doesn't do anything anymore when I connect it to the PC, no USB connect, no sign of adding it in Odin. It seems like the charging mechanism doesn't work anymore either. The deivce appears totally dead.
Did you see my thread http://forum.xda-developers.com/showthread.php?t=1769144? This problem is totally the same as mine.
Is yours rooted? Coz it says here http://www.teamovercome.net/p1000/?page_id=17 that :
[REQUIRED FOR FROYO-BASED TABS ONLY:] Your Tab must be rooted. (Please look for SuperOneClick root method as it’s usually the safe bet! But for more information on rooting, please refer here: http://forum.xda-developers.com/showthread.php?t=812367)
Click to expand...
Click to collapse
I hope someone can help us, or else, no choice but to bring this to service center.
itenos said:
Hi,
my girlfriend just came back from China with a P1000 from her friend. As the whole device was running on chinese language and for some strange reason it was not possible to enter System Setting to change the language, I decided to flash her the latest firmware and just make a fresh start. (i'm a flash veteran on my SGS since 2 years, so I know how to use Odin)
I downloaded the P1000XWJQ8 from Sammobile, fired up Odin and flashed the new ROM with repartition enabled.
The procedure went through without errors:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P1000XWJQ8_P1000XXJPZ_P1000DBTJQ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> cache.rfs
<ID:0/003> hidden.rfs
<ID:0/003> modem.bin
<ID:0/003> factoryfs.rfs
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/003> Added!!
At the end of it the device didn't auto-boot as expected, it just stayed there with a black screen!!!!!!
Disconnecting and reconnecting it triggers in Odin the REMOVED and the ADDED lines but nothing happens.
I cannot switch on, cannot go into download nor recovery, the device just seems to stay dead :-(
My next idea was trying to pull the battery but apparently the battery is glued to the casing, so before I do more damage, I better start asking here.
Hope someone can help, my girlfriend will kill me if I can't repair this damn thing...
EDIT: after having closed Odin on the PC I tried to connect the device again and it started to play the startup song and Win7 started to install the new drivers from the new firmware. 7 out of 9 found drivers installed correctly, 2 instead failed.
But nothing changed to the vegetarian state of the P1000
Click to expand...
Click to collapse
MarlX said:
Did you see my thread http://forum.xda-developers.com/showthread.php?t=1769144? This problem is totally the same as mine.
Is yours rooted? Coz it says here http://www.teamovercome.net/p1000/?page_id=17 that :
I hope someone can help us, or else, no choice but to bring this to service center.
Click to expand...
Click to collapse
hey guys, are sure your gtab is P1000??
see the back cover, and chek your gtab model to make sure.
qm4n76 said:
hey guys, are sure your gtab is P1000??
see the back cover, and chek your gtab model to make sure.
Click to expand...
Click to collapse
Yes, 100% sure, my one is a P1000. As wrote in EDIT2 my device now seems to be totally dead
Hello people.
This started couble of weeks ago when my phone suddendly went to factory mode. it wasent rooted and i was running 4.3 so i took it to the repair center. They told me that the phones circuit board needed to be replaced and it would cost 281€. Since the same phone new was only 299€ i declined their repair. then i went on a search for way to repair the phone my self. I wound some ways but they needed a root acces. So i tried to downgrade my phone back to 4.1.2 but for some reason Odin started to give me this error...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXBMI3_I9305NEEBMH1_I9305XXBMH3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
And then when i restarted my phone it keeps giving me yet another error saying that "Firmware upgrade encountered an issue. please select recovery mode in Kies & try again. In kies the phone wont connect to it. it just keeps loading. Now im asking for some help if some1 has an idea or a way to fix this.
I can give more info if needed.
it fails cause you are trying to flash 4.1.2...once you got 4.3 you can't go back...i'm guessing that you get that error when it tries to install the old bootloader(without knox counter)....
spiderman07 said:
it fails cause you are trying to flash 4.1.2...once you got 4.3 you can't go back...i'm guessing that you get that error when it tries to install the old bootloader(without knox counter)....
Click to expand...
Click to collapse
yeah i figured that out. tryed to follow a guide but it dident work... but flashed to 4.3 and that worked and auto rooted my phone and factory mode gone and everything is back to normal
Hi Everyone, i have searched through the forums and tried what has been said, but still no luck. I have a galaxy Gear V700
I tried numerous times on kies to update and it just would not play ball at all.Even leaving it over night, thinking maybe it is downloading something.
Today i have used Odin today, and flashed with V700XXUCNF1_V700OXACNF1_BTU
Within Odin it does the following
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
then it freezes. Because it had froze for about 25 minutes, i unpluged the Gear, to try again. All of a sudden Odin jumped up and said failed, and the Gear now is stuck with "Firmware Upgrade encountered an issue, please select recovery mode in kies and try again"
Problem is Kies 2 and 3 do not recognise the watch anymore. Odin seems to recognise it but wont allow me to do anything . I have tried using Odin to flash an original stock image, and have even tried the earlier Tizan.
I am still stuck...
I am a complete newbie on here and do not really know much about the phones and watches, but got so frustrated at not being able to upgrade the traditional way.
Any help would be greatly appreciated..
Many thanks
I am now getting this in Odin 3.09, so it seems to be going a little further, but still fails at the end
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> V700XXUCNF1_V700OXACNF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> zImage
You have to update to Tizen version NE9 first through ODIN 3.09, then update to NF1. Do not skip this step.
It has already been talked about here:
http://forum.xda-developers.com/showthread.php?t=2794780
bballengphd said:
You have to update to Tizen version NE9 first through ODIN 3.09, then update to NF1. Do not skip this step.
It has already been talked about here:
http://forum.xda-developers.com/showthread.php?t=2794780
Click to expand...
Click to collapse
Sorry being a pain in the backside, but where do i get the NE9 as all the update files i have downloaded none have NE9 or the NF1 in there names... How do i know which is the right one..
Thanks
Go here to get the NE9 for your region.
http://samsung-updates.com/device/?id=SM-V700
Many thanks
That has fixed it..... SO basically what i was doing i think, was flashing it with an update to Tizan, not the update from android to Tizan. DOH
Thanks to all that helped
.,
note 5 N920T
Successfully flashed Sick/Flu ROM about 2-weeks ago and it was (is) excellent. It was like getting an entirely new phone in battery life and speed. Long story short, tried to add fingerprint scans and bricked it--only to find out this was the one caveat to the ROM. So proceeded to reflash ROM while talking with family during Thanksgiving--I had really prepared the first time and felt pretty comfortable doing it again--but not being focused I ended up deleting the wrong information and soft bricking it.
At this juncture the only item still visible on the internal drive is TWRP. I AM able to boot into ODIN mode and the software does recognize my phone and I am also able to boot into TWRP. Other than that I do not have any OS on the phone at this time. I've downloaded the original firmware, but multiple attempts at flashing it have failed. Hours and hours of reading it seems that I may be missing a PIT file (?), but I haven't been able to confirm that is the actual problem or locate the specific N920T PIT file anyways. Seems like many of the discussion strings died in 2015
I can provide more details about the failure messages I read on ODIN and my phone during reflash attempts if anyone has the patience and time to help me. I spent essentially 13 hours straight all over the internet with no success and am reaching the point of throwing it into a fire
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Attempts at flashing stock ROM.
Please does anyone have suggestions? I have scoured all prior threads in this regard and had no success
Wyattthomas said:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Attempts at flashing stock ROM.
Please does anyone have suggestions? I have scoured all prior threads in this regard and had no success
Click to expand...
Click to collapse
If you need the PIT file you can get it here but you'll have to create an account in order to see the download links.
http://www.sammobile.com/forum/showthread.php?t=30106
By the way don't use an old firmware, you have to use the very last firmware you were using before ever doing anything to it.
I did find the PIT file several hours ago and it doesn't appear to have been the problem. Its actually the only file that will "successfully" flash on the phone.
I've tried flashing the original android firmware that was on device originally as well as the most recent android firmware. Between each attempt the computer and phone were reset. No dice.
Wyattthomas said:
I did find the PIT file several hours ago and it doesn't appear to have been the problem. Its actually the only file that will "successfully" flash on the phone.
I've tried flashing the original android firmware that was on device originally as well as the most recent android firmware. Between each attempt the computer and phone were reset. No dice.
Click to expand...
Click to collapse
Have you tried booting into recovery and flashing a downloaded rom? You should be able to get into twrp and then flash from there... If you can't get into twrp then reflash twrp and try again.
MrMike2182 said:
Have you tried booting into recovery and flashing a downloaded rom? You should be able to get into twrp and then flash from there... If you can't get into twrp then reflash twrp and try again.
Click to expand...
Click to collapse
WELL-------IT flippin' worked!!!!!!!!!!!!!1
So I HAD also tried flashing the new ROMs with TWRP several times before but that wasn't working either. Later on I realized that I was off by a couple months on the latest Android 6.1.1. update and repeated ODIN flashes with new bootloaders/PIT files etc all continued to fail. Didn't think about trying the TWRP flash again
I am going out for a drink. This phone ruined my Thanksgiving, but for the records I'm immediately flashing the Sick as Hell ROM again. I know exactly how to do it in my sleep now. AVOID USING FINGERPRINT lock and it is otherwise an amazing ROM. Fast, Fast, Fast, and battery goes all damn day. Spotify hack is wonderful too.
Wyattthomas said:
WELL-------IT flippin' worked!!!!!!!!!!!!!1
So I HAD also tried flashing the new ROMs with TWRP several times before but that wasn't working either. Later on I realized that I was off by a couple months on the latest Android 6.1.1. update and repeated ODIN flashes with new bootloaders/PIT files etc all continued to fail. Didn't think about trying the TWRP flash again
I am going out for a drink. This phone ruined my Thanksgiving, but for the records I'm immediately flashing the Sick as Hell ROM again. I know exactly how to do it in my sleep now. AVOID USING FINGERPRINT lock and it is otherwise an amazing ROM. Fast, Fast, Fast, and battery goes all damn day. Spotify hack is wonderful too.
Click to expand...
Click to collapse
Create a full backup first so you have something to fall back on and restore if anything goes wrong again.
MrMike2182 said:
Create a full backup first so you have something to fall back on and restore if anything goes wrong again.
Click to expand...
Click to collapse
First thing I did. I've since backed it up about 3 more times...never again will I make that fatal error.