Hey folks. I'm having a weird problem.
I was on ParanoidAndroid 3.10 march 18 and everything has been just fine (if you don't count occasional reboots) until earlier today I was going to take a picture.
Phone shuts down. No FC no nothing it just shuts down. Battery was almost full and so on.
I rebooted the phone again and went to camera and it shut down again.
Figured I'd might just as well update to the newest 3.15 march 26 version.
wipe data/factory reset, flashed rom + gapps, wiped cache+dalvik. Then rebooted. I get to the insert pin screen and then the phone shut down again.
Reboot again and it shuts down when I reach the insert pin. I download the rom again, wipe and flash and reboot and then the phone shuts down when the PA boot animation begins.
At this point I decided I'd try flashing the rooted stock JB rom by eybee1970. Flashed a CM10.1 kernel just to be sure, reboot recovery, wipe data/factory reset, format data/system/preload, flashed rom and it gives a really long error. Did the kernal and reboot again, wipes and flashed rom and now it went ok. Start booting and the phone won't boot past the white samsung gt-n7000 text.
At this point I start odin 3.07, dig the original N7000XBKK4_N7000OXXKK5_NEE from my archive, check the md5, put my phone in download mode, put the .tar in PDA and press Start. Everything goes fine, phone reboots and does some stuff and reboots and I hear the stock boot sound.
I enter my pin code and I'm welcomed with Welcome to GT-N7000 and boom phone shuts down.
I take out the sim card and sd card and reboot the phone. It boots fine and media scanning starts, it scans scans scans and "Media scanning complete" and boom it shuts down.
Please help? I do have warranty but I would prefer not to take my phone to repair as it would take weeks and weeks knowing SCF-Huolto's quality....
So to recap/TD;DR, I have KK4/KK5 stock GB rom, I have stock recovery, I have download mode, I have a booting phone, I have a phone which charges and USB works. But it just shuts down.
Edit: (11th April 2013 at 02:17 PM.) Reason: Device sent to repair)
Okay, I'll be taking my phone to the repair shop in an hour or so.
Thank you to ANYONE who bothered to read my thread and thank you to you who answered.
I will try and remember to update this when I get it back from the repair shop with what was done to it and so on.
Edit2: (17th April 2013 at 10:33 AM.) Reason: Device received at repair and repaired
So looks like it went to Optima instead. Didn't know that through Elisa Shopit the Samsung's go to Optima. Well I left it to the repair on 11th and it was sent to the repair shop on the 12th, it was received on 16th and today on the 17th I saw a message in the repair tracking service:
"piirikortti ja akku vaihdettu" which translates to circuit board and battery changed.
Probably can go get my Note on friday the 19th or on monday 22nd. I am sick and tired of this ZTE Blade III they gave to me LOL
How old is your battery? Did you try with another one?
It came with the phone so it's as old as the phone is, a year now maybe. But I can't imagine it would be the battery :/ Haven't had any problem with battery life and so on.
Checked the battery with my multimeter and it shows 3.98 volts right now.
Now I tried starting the phone again and it boots just fine. It finished the media scanning and then the screen sort of like vibrates the image and the phone shuts down. Took the battery out and the reading varied only 0.02v so margin of error if you ask me. If it was like very low voltage and then rising back up again like I see with my bigger 18650 IMR cells after they have been stressed with 10A+ loads then I would think about replacing the battery.
To get rid of the doubt on the battery, have you tried reboot and run your device while it is still connected to the charger ?
Put the phone on charger, booted it, the lock screen says Charging 47%, then "Media scanning completed" and it shuts down and then the big charging icon shows up with the circle in it and then it turns green and the bars move.
As it shutdowns after the message "Media scanning completed", have you tried to reboot and run without your external SD card ?
It can wrongly say "completed".
I have took the sd card out.
13 line first sentence "I take out the sim card and sd card and reboot the phone."
It starts and tries doing something so it's not a bootstrap problem, not problem on SD card. It remains doubt on RAM and on internal SD.
Anyone have any ideas what I still could try? I'll be leaving in maybe 2½ hours to Seinäjoki and take this thing to the repair shop. When I still had my HTC Desire and it went bonkers I tried and tried and did lots of things to try and get it working again. It was usb bricked and so on. Anyway, in the end I had spent like two or three months trying various methods but couldn't get it working again so I took it to the repair shop where it was like a month. If I would have taken it right away there it would have only been a month without a working Desire, instead of three to four months without a working Desire. So that's the reason I'll be taking it to the repair shop now. So if anyone comes up with please please do tell and I'll give it a go.
Well picked up my Note yesterday from the repair.
Info on what was done is "circuit board and battery changed"
It was updated to latest XXLRI stock rom 4.0.4.
It was working quite fine for a while but I'm now getting some random reboot every once in a while. Installed only few apps, Andchat/Tapatalk/Netflix/Facebook Messenger/Ebay and uninstalled some of them and didn't see any change in the random reboots.
I'm now downloading the 2.3.6 version, XBKK4 from sammobile. And will do a factory reset then, hopefully would resolve these random reboots. Did some searching and many people having this problem were suggested to go to GB and then reset. (well of course GB if wiping anything)
Guys, where can I find the MD5 for the stock rom on sammobile? I'd like to check the MD5 before I push it to my phone using Odin.
Here's the MD5 I got from the zip I downloaded (N7000XBKK4_N7000OXXKK5_NEE.zip) if any kind soul could bother to cross reference
7742E03F116957F3928BE9007F7A921E
E: Nevermind, I'm just being dense.
For MD5 check on stock ROM, I use Odin mobile. It always suggest to run MD5 check before flashing.
Well done with the flashing. Used Odin v1.85 and I'm running 2.3.6 now.
Code:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XBKK4_N7000OXXKK5_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> boot.bin
<ID:0/016> NAND Write Start!!
<ID:0/016> cache.img
<ID:0/016> factoryfs.img
<ID:0/016> hidden.img
<ID:0/016> modem.bin
<ID:0/016> param.lfs
<ID:0/016> Sbl.bin
<ID:0/016> zImage
<ID:0/016> RQT_CLOSE !!
<ID:0/016> RES OK !!
<ID:0/016> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/016> Removed!!
Phone booted just fine. I'm greeted with the Welcome message but couldn't access the setup wizard because of Google service framework and phone and so on force closing. Went to stock recovery, factory reset + wipe cache and rebooted. Now it's fine. Haven't had any random reboot, yet.
As far as this thread goes I see this is solved.
Congratulations ! Happy after hard experience.
No idea if it's related to your issue but I was having the same thing and it was driving me bonkers for a while but I found the culprit: my headphones (plugged into 3.5") we're a ghetto repair job (think gaffer tape ) where I'd joined the cord from one pair to another pair.
I don't know exactly what was happening but I'm assuming that everytime some wires touched from the volume control wires (which we're connected to anything on purpose) it somehow made the device shutdown. I don't know the exact ins and outs of how this might happen. But anyhow, I'm absolutely certain it was something to do with wires in the headphones because it's never happened since I got new headphones.
Just an idea, who knows.
Related
Beat with me guys, I am very very new to this board, and I apologize if I post this in the wrong area.
Lemme start from scratch.
My phone is not rooted or anything like that. BUT I wanted to update my software for the Captivate to 2.2 using samsung Kies.
Not sure what happened, I though I had the correct drivers installed and what not, but it gave me the screen with the phone, exlamation mark, and computer.
I can put my phone into download mode, and I installed odin3 one click downloader. The problem is, when it gets to the part 'file analysis' it gets stuck there.
I watched a video on youtube and his went automatically, so I'm not sure at ALL what to do. If I can fix this myself, I'd love to. If not, I will go through AT&T and see if I can get it replaced.
Any help would be greatly appreciated.
Not sure how to fix it, but if you have to send it into samsung say it got screwed up somehow while trying to update to KB1, in truth that is what happened, plus if you say that they will try to fix it fast
If you have access to another computer, download ODIN and try it on that one. Odin works on my laptop but not on my desktop.
CM7 Inspire 4G
What you have is a soft brick. Keep trying to get into download (try both 2 and 3 button methods) and then retry Odin. Look in Dev subforum for the "How to flash a ROM" sticky as there is good info on how to do this.
Samsung was absolutely no help lol.
Well.. I guess I can try this on another desktop.
Jeez I regret trying to upgrade man. Shoulda waited and learned more.
Has anyone had odin3 get stuck at file analysis before?
What model is your Cappy? You can find the model number underneath the battery (on the phone itself). It should have a number like 1006,1007,1008,1009,1010,etc.
Also, it'll be a good idea to try this alternate method in the mean time:
Make sure you know how to go to Download Mode, and that you have the drivers installed properly.
Windows 64bit
Windows 32bit
This is the manual (or "full") Odin, it's taken from a post by icezar1 in the Development Forum:
Do not use this if you want to send your phone back to ATT or Samsung for warranty!
Do not use this if you know you flashed a -LOW- ODIN package (when opening the PDA***.tar or CODE***.tar you will find inside boot.bin or sbl.bin)
Use this if you want to go back to stock before flashing a custom ROM.
Use this without worries if you changed your boot screen image or if you flashed the secondary boot loader which allows you to enter download/recovery with key combos.
Download the package from here
How to:
Remove sdcard and SIM card from the phone
Extract JF6_secure.zip somewhere.
Boot your phone in Download Mode
Run Odin3 v1.3.exe
Plug in your phone via USB
Click on the button PDA
Choose JF6_secure.tar.md5
Click start
Wait and do not unplug cable until it is finished
venomio said:
What model is your Cappy? You can find the model number underneath the battery (on the phone itself). It should have a number like 1006,1007,1008,1009,1010,etc.
Click to expand...
Click to collapse
Just for clarity sake, those are not the model numbers, they are build date (first two are year, second two are month). The model number of the Captivate is i896 or i897.
I know, I keep saying that they're model number though for some reason. Thanks anyway I guess.
Thank you venomio this 1.3 is working much better.
<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..
That's where I'm at right now. Fingers crossed!!
aftermaz said:
Beat with me guys, I am very very new to this board, and I apologize if I post this in the wrong area.
Lemme start from scratch.
My phone is not rooted or anything like that. BUT I wanted to update my software for the Captivate to 2.2 using samsung Kies.
Not sure what happened, I though I had the correct drivers installed and what not, but it gave me the screen with the phone, exlamation mark, and computer.
I can put my phone into download mode, and I installed odin3 one click downloader. The problem is, when it gets to the part 'file analysis' it gets stuck there.
I watched a video on youtube and his went automatically, so I'm not sure at ALL what to do. If I can fix this myself, I'd love to. If not, I will go through AT&T and see if I can get it replaced.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm in the same exact situation as the OP. I'll try the instructions posted below and report my findings.
check your build number first before you flash using odin. certain build may not work with odin one-click.
an usb jig will help you out if you cannot get into the download mode or just in case:
http://cgi.ebay.com/ws/eBayISAPI.dl...84198&ssPageName=STRK:MESELX:IT#ht_782wt_1139
The issue with mine is i have no history on this phone... its my co-workers who got it from a friend who is clueless about his own damn phone.... bought from a local guy.
anyways im in guam and i have no way of checking if this model was on a custom rom or what not or if the unit was pure stock all around i cant go into recovery mode at all only into ODIN which tells me to download a custom OS ... i myself am not a tech guy so im new to this just reading around but you all are well aware of what firmware and what not your unit was on but me i have no clue due to it not being able to fully start up and not charging only through my laptop port which at that wont even help cause my laptop tells me its not recognized but i have the drivers downloaded in already and have kies from my previous androids i had.
so my search is to find someone who can help me out here with me not knowing at all pretty much being blind to what the units firmware or ROM was even on and so forth.
further info
James Cortez671 said:
The issue with mine is i have no history on this phone... its my co-workers who got it from a friend who is clueless about his own damn phone.... bought from a local guy.
anyways im in guam and i have no way of checking if this model was on a custom rom or what not or if the unit was pure stock all around i cant go into recovery mode at all only into ODIN which tells me to download a custom OS ... i myself am not a tech guy so im new to this just reading around but you all are well aware of what firmware and what not your unit was on but me i have no clue due to it not being able to fully start up and not charging only through my laptop port which at that wont even help cause my laptop tells me its not recognized but i have the drivers downloaded in already and have kies from my previous androids i had.
so my search is to find someone who can help me out here with me not knowing at all pretty much being blind to what the units firmware or ROM was even on and so forth.
Click to expand...
Click to collapse
i downloaded a old ROM 2.3.5 i believe or somewhat and put it in my PC odin PDA put my phone into odin mode tab turned yellow. dowloaded as well the 16gb model PIT given by Dr.Ketan and also got emmsc brick PIT just in case now on my odin i just put in the PDA of the india version of an old rom for direct root accessability and so forth... the usual timing for the odin says 5-10 min. but mine is taking quite some time really....
more info
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK3_N7000ODDKK1_N7000DDKJ3_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> boot.bin
<ID:0/003> NAND Write Start!!
thats what my panel remains on
Do you know recovery mode?
Press volume up button, power button and home button together for 10 secs and release. Tell us what happens.
Also read drketan guide how to flash gb rom.
Sent from my GT-N7000 using xda premium
dsmas said:
Do you know recovery mode?
Press volume up button, power button and home button together for 10 secs and release. Tell us what happens.
Also read drketan guide how to flash gb rom.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i did Dr.Ketan guide im still awaiting response right now this is what it is stuck on right now
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK3_N7000ODDKK1_N7000DDKJ3_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> boot.bin
<ID:0/003> NAND Write Start!!
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
i cant get the phone into recovery mode...... it just reboots to the boot screen and just stays there......
i dont know the previous OS on this phone or ROM or KERNEL cause i got it dead and stuck like so .... right now im still waiting for a response from the odin
Maybe i could help you
1st : can you remove you phone battery and tell us your phone model ?
2nd : put the battery in and charge your phone without booting ,, is it turning into a battery icon ? if so continue charging at least to more than half the battery
3rd : if your device is surly a gt-n7000 try to download another rom and after that check its csc before flashing , jelly bean update seems awesome right now ! .... i could tell you to download this amazing stock - rom but i need to make sure of your phone model first !
sniper9911 said:
1st : can you remove you phone battery and tell us your phone model ?
2nd : put the battery in and charge your phone without booting ,, is it turning into a battery icon ? if so continue charging at least to more than half the battery
3rd : if your device is surly a gt-n7000 try to download another rom and after that check its csc before flashing , jelly bean update seems awesome right now ! .... i could tell you to download this amazing stock - rom but i need to make sure of your phone model first !
Click to expand...
Click to collapse
yes the device is surely a GT-N7000 ill charge the battery and yes it shows the charging icon and can charge......
no help
still its a fail
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK3_N7000ODDKK1_N7000DDKJ3_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> boot.bin
<ID:0/003> NAND Write Start!!
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
that is as far as i get then it just says fail...... my phone will only charge when connected to my laptop but not to my wall charger. my phone can enter download mode but not recovery mode.
when connected to my laptop the driver doesnt recognize it but it can be detected on odin but on kies it wont.
more help
okay ..... so its either the rom itself you are trying to flash or something else ....
first : what do you mean when you charge it from the plug it wont go ?? this is a real problem ... if you have another charger try it with first then if its not charging you'll need to service that mobile via samsung service center cause you cant do anything with an empty battery ....
if my guess is right then it a faulty charger and you need a new charger ... thats it , after checking this step you can try downloading another rom which i am sure it will be all right cause i am already using it :
try this link :
http://www.hotfile.com/dl/198300717/4646e97/N7000JPLSB_N7000OJPLSA_XSG.zip.html
download this version of odin too :
http://www.4shared.com/get/U6DTV0GA/gt-n7000_flasher__pit.html
you'll need to uninstall samsung kies , reboot you pc ,
and install samsung latest usb drivers :
http://forum.xda-developers.com/showthread.php?t=2038555
Note : DO NOT FLASH ANY FIRMWARE UNLESS YOU HAVE GOTTEN DEVICE IS READY TO USE AND ALL DRIVERS INSTALLED SUCCESSFULLY
afterwards you will extract odin and the firmware (md5 file + dll file "important" ) on you desktop in a folder and then you'll use odin in administrator mode then you make sure you note battery > 50% at least then make your note in odin mode ( vol down + home + power , then vol up to enter odin mode )
plug your note to usb and let the pc reapply drivers then youll put md5 file in pda bar and pit 16 gb in pit , also check your note internal capacity ... maybe you are lucky and have 32gb or even 64gb
okay then press start .... normally it would take less than 10 minutes to complete , 8 minutes 15 seconds of waiting then you have your note booting , unplug it from pc when odin says ok ( blue ) or pass ( green ) then here you go ... Jelly bean !!
teah man still no damn luck it keeps on failing and if it aint failed yet its like passed 30min. and still nothing changed.... do i put the PIT and the PDA or do i do it one by one.... do the GT7000 PIT first then the N7000 PDA after?!....
a step by step video would do more wonders than just reading.... cause i think my issue is way different cause i dont even know if this phone is unlocked or what or anything about it cause i got it bricked. stuck on boot logo and HARD RESET isnt accessible and im in GUAM.... ya know where GUAM is?!......
Me having same issue guys :crying: i am following this thread please experts help us !!
TRY booting in recovery or download mode.
recovery : volume up+home+power at the same time
download : volume down+home++power at the same time.
let us know if you can get into both or any of these modes
Mayank Chandwani said:
TRY booting in recovery or download mode.
recovery : volume up+home+power at the same time
download : volume down+home++power at the same time.
let us know if you can get into both or any of these modes
Click to expand...
Click to collapse
Not working mate
Sent from my GT-N7000 using xda premium
LucknowBoy said:
Not working mate
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
How long did you press/hold the buttons? In what order?
YEY!
thanks alot sniper9911 you're a live saver.., i follow the procedure that you've said then my problem solve
thanks again!
James Cortez671 said:
teah man still no damn luck it keeps on failing and if it aint failed yet its like passed 30min. and still nothing changed.... do i put the PIT and the PDA or do i do it one by one.... do the GT7000 PIT first then the N7000 PDA after?!....
a step by step video would do more wonders than just reading.... cause i think my issue is way different cause i dont even know if this phone is unlocked or what or anything about it cause i got it bricked. stuck on boot logo and HARD RESET isnt accessible and im in GUAM.... ya know where GUAM is?!......
Click to expand...
Click to collapse
Well, I´m with the same problem here on this side but i thinck this might work:
Check this link: http://forum.xda-developers.com/showthread.php?t=1901191 I dont know if this is going to work but i am going to run this in my samsung.
After that, I will reply you.
can someone help me...my n7000 just went off...i tried to start it,but loops on samsung logo. i used odin with stock rom...all went right it finished with Pass from the first try...but then again the phone didint want to start...i started updating apps and then looped again...every time it shows battery totaly empty...i tried a couple of times with odin and even pit file...even managed one time to start the phone,opened setting etc...battery indicator showed its full,and then suddenly phone just restarts and i cant do nothing?!
last time it rebooted automaticly opens android recovery and stays on that screen....? i cant do nothing....every time i plug it into charger he starts up and opens recovery ?
tried charging over computer usb,from a 220v,even from a dock....but he as soon as i plug it he opens recovery ?? any help...i think the main problem is battery....would it help to charge it in some other device or something ? or i screwed things big time ?
I had the same issue here.use odin still cant help
Anyone can help here
I stuck here.
<ID:0/003>NAND Write Start!!
3 things for I start 1 I'm bat in English because I'm dutch sorry for that if you don't understand a sentence just ask I will try to explain it 2 I'm also bad in making sentences that's why you don't see any dots Sorry for that to and the third thing is I'm not at bad at rooting or installing custom roms did it on my galaxy tab 3 no problems also on my cousins phone also no problems same as that from my mother.
I have for a long time my galaxy s1 like 3 years now I had it rooted and installed the Cyanogen mod (nightly form the 5th of April) and it was jut working fine I just update once in the moth or so always the lasts nightly but when I did updated for the newest nightly for that day (11th of may update) and when it restarted it was just stuck at the boot screen so I got the battery out waited 5 minutes and put it back in end reboot it did that like 3 times but every time it was stuck at the boot screen so I searched on Google but nothing works because Odin(3.0.7 also 3.0.9) fails to make connection or it was stuck at the nand write start
all what I tried was in the odin:
use an other cable
other pc / laptop
other usb ports (used always the back of the pc)
other packages for odin
other odin versions
I also tried using heimdall also no success
and after trying this all my phone even get worse when it was stuck i can only access download mode
recovery wasn't able any more so I also set the root package not on the pda from odin but on phone and when i booted the phone I get into an old recovery of cwm but he was not able to mount my storage or something else after just trying around with odin and a little heimdall no success now I can only access download mode and odin sees my phone but it doesn't matter where I put any package it just loads normal and when it needs to reboot it is just black screen it makes connection but it stops if I put the root package in the pda or a phone package in the phone sections then it stops at nand write start I tried to re-partition it with different pit files but also no success
*edit a friend said ty using odin 1.3.0 but now odin said this
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Can't open the specified file. (Line: 1455)
<OSM> All threads completed. (succeed 0 / failed 1)
if I do a root package in pda or phone
* edit
I fixed it just do this
http://forum.xda-developers.com/showthread.php?t=1583026
except for the voodoo kernel part its was stuck at boot screen hear only a women talking cant under stand it because my speaker in my phone is messed up
if you want to root it use this package http://download.chainfire.eu/132/CF...XA_JVU_2.3.6-v4.3-CWM3RFS.zip?retrieve_file=1
so maby you People can help me
Thanks for any help that comes
Background, Symptoms and Repair Attempts
My significant other's I9305 spontaneously died. The phone is fully stock, non-rooted. Was never custom-flashed.
It was working with no apparent problems, then one night we left it (turned on) to recharge overnight, as we usually do, and found it boot-looping in the morning.
"Boot-looping": repeatedly showing "Samsung Galaxy S3" screen for about 4 seconds, then restarts (screen goes black for about 3 seconds, then "Samsung Galaxy S3" screen shows again, infinitely repeating).
The boot-loop prevents access to recovery mode or to the main OS.
"Charge mode" is working - when phone is turned off, it shows charge animation when connected to power source (with battery level rising as charging progresses).
Download mode itself is accessible, and phone remains in it until I force it to end. Text shown on top of download mode screen:
Code:
ODIN MODE
PRODUCT NAME: GT-I9305
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
However, actual flashing is apparently impossible. I tried several times using Odin v3.09 to flash 2 different stock images:
I9305XXBME3_I9305DBTBMF1_I9305XXBME1 (Stock 4.1.2)
I9305XXUFNL1_I9305DBTFNL1_I9305XXUFOA1 (Stock 4.4.4)
In all my flashing attempts I had only "AP", "Auto Reboot" and "F. Reset Time" checkboxes checked, and the rest unchecked.
All attempts failed (with a red "FAIL!" on the top-left of the window) within 2-3 seconds after clicking the "Start" button. Odin's message log for such an attempt is as follows:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXBME3_I9305DBTBMF1_I9305XXBME1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/004> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried using Odin to flash 2 different custom recovery images:
openrecovery-twrp-3.0.2-1-i9305-F2FS
CWM_touch_6.0.4.7_i9305
Attempts to flash these failed in the exact same way as the stock images did (as described above).
Despite all my (failed) flashing attempts, all symptoms remained unchanged (boot loops, no recovery, only download mode and charge mode working).
Questions
I'd really appreciate any tips, advice, or answers to the following questions:
Are these symptoms indicating a problem with the eMMC chip?
Is there any possible repair other than replacing the eMMC chip? Is there any chance for repair using a dedicated JTAG/eMMC tool?
Am I supposed to be able to salvage at least part of the data on the eMMC chip using an SD reader and an SD adapter soldered to the motherboard (e.g. in a manner similar to the process described here)?
Am I supposed to be able to salvage at least part of the data on the eMMC chip using a dedicated JTAG/eMMC tool? Would I be able to extract more data with such a tool than I would be able to extract using the soldered SD adapter and reader?
Many thanks in advance for your time and help efforts!
EMMC Brickbug claims another i930x device. Unfortunately, all the partitions after a certain area are useless because some defects in a batch of EMMCs. i9300 has had it for some time, but i didn't know that i9305 could have a part of the faulty lot that kneeled the i9300. You may be lucky enough, depending in what country you live, to find and go to a very good smartphone repair shop and get the EMMC replaced by some people that actually know what they are doing. Or, if you have money, skills and time to spare, replace it yourself, but you'd need to take some precautions to not f it up. (i.e. place some thick metal piece over the modem to not heat it up, and to not apply too much temperature to the board to damage it.)
Trying to return previously rooted SM-T713 to stock. Downloaded the original ROM T713XXU1APD9_T713XAR1APD9_HOME.tar.md5 from here
https://forum.xda-developers.com/tab-s2/development/stock-official-t713-stock-firmware-t3392404
Also got Odin v3.10.7, and latest USB driver from Samsung. Device is correctly recognized on COM3. Per various instructions on web I load the .md5 file in the AP section of Odin and hit "Start". The process goes through mostly smoothly but fails at the very end
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> adspso.bin
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The device screen reads
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-T713
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: Off
WARRANTY VOID: 0x1 (2)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, GH1, R1, A2, P1
SECURE DOWNLOAD: ENABLE
download mode !!
SW REV CHECK FAIL: [aboot]Fused 2 > Binary 1
Click to expand...
Click to collapse
I have tried this a couple of time, Odin runs as admin. Any suggestions? At the moment I cannot boot to recovery (Pwr + Vol UP + Home does nothing) and if I try to boot to the OS I get
An error has occurred while updating the device software. Use the Emergency reovery function on the Smart Switch PC software
Click to expand...
Click to collapse
Update: while investigating the "FAIL! (Auth)" part of the message I read that Sammy does not let you install firmware that is older than the original firmware on the pad. So I tried XAR-T713XXU2BSA1-20190314170324 instead and it worked, but not the tab gets suck at the pulsating Sammy logo. The recommendation is to reboot to recovery and do a wipe/factory reset but I can't seem to get either the power button alone, or home + power + volume up to work. The only thing that seems to work is Power + home + volume down to get to fastboot. Argh!
After the firmware is flashed the Android logo and blue screen come up, it says "installing system update", gets to about 12%, then "erasing..." for a few seconds, then reboots to system, and gets stuck on the pulsating Samsung logo. Suggestions? I have tried re-flashing several times, and it is always the same song and dance.
Have tired half a dozen ROMs from various sources: XAR-T713XXU2APK6-20170109153313, SM-T713_1_20180216210827_n6ema2bn6h, XAR-T713XXU2BSA1-20190314170324, T713XXU2APJ1_T713XAR2APJ1_XAR, XAR-T713XXU1APD9-20160510111333. With the exception of the latter they all flash with Odin without issues but then the device goes into a bootloop. An initial blue screen appears that says "Installing system update", but that gets only till about 35% after which it switches to message "erasing" and the tab goes into a reboot only to get stuck on the pulsating "Samsung" screen. I have tried erasing NAND, flashing TWRN, and what not, to no avail. I can't get into recovery and the power button does not work either. Would be grateful any suggestions, otherwise this is going to the ewaste bin.
GroovyGeek said:
Have tired half a dozen ROMs from various sources: XAR-T713XXU2APK6-20170109153313, SM-T713_1_20180216210827_n6ema2bn6h, XAR-T713XXU2BSA1-20190314170324, T713XXU2APJ1_T713XAR2APJ1_XAR, XAR-T713XXU1APD9-20160510111333. With the exception of the latter they all flash with Odin without issues but then the device goes into a bootloop. An initial blue screen appears that says "Installing system update", but that gets only till about 35% after which it switches to message "erasing" and the tab goes into a reboot only to get stuck on the pulsating "Samsung" screen. I have tried erasing NAND, flashing TWRN, and what not, to no avail. I can't get into recovery and the power button does not work either. Would be grateful any suggestions, otherwise this is going to the ewaste bin.
Click to expand...
Click to collapse
The one I used the last few times I needed returned to stock has the same date as one of yours (20180206) but a different name both in the original XAR zip (XAR-T713XXU2BRB2_T713XAR2BRB2-20180206) and the extracted .tar (T713XXU2BRB2_T713XAR2BRB2_HOME.tar). I do not remember what site I got it from, but it took about a half day to download.. That was probably about a year ago. If you have somewhere that I can upload it to, I can put a copy of one or both there. Otherwise, you can at least search Google by name of a known working file.
sliding_billy said:
The one I used the last few times I needed returned to stock has the same date as one of yours (20180206) but a different name both in the original XAR zip (XAR-T713XXU2BRB2_T713XAR2BRB2-20180206) and the extracted .tar (T713XXU2BRB2_T713XAR2BRB2_HOME.tar). I do not remember what site I got it from, but it took about a half day to download.. That was probably about a year ago. If you have somewhere that I can upload it to, I can put a copy of one or both there. Otherwise, you can at least search Google by name of a known working file.
Click to expand...
Click to collapse
Thanks, I found the file on samsung-firmware.org. Says it will take 3 hrs to download. At this point I am not too hopeful, but will give it a go. Thank you for the tip!
P.S. For completeness sake, the link to this file is https://samsung-firmware.org/download/GALAXY__Tab__S2__/45bx/XAR/T713XXU2BRB2/T713XAR2BRB2/
GroovyGeek said:
Thanks, I found the file on samsung-firmware.org. Says it will take 3 hrs to download. At this point I am not too hopeful, but will give it a go. Thank you for the tip!
P.S. For completeness sake, the link to this file is https://samsung-firmware.org/download/GALAXY__Tab__S2__/45bx/XAR/T713XXU2BRB2/T713XAR2BRB2/
Click to expand...
Click to collapse
Good luck.
Alas the behavior of this known good ROM is identical to every other one I have tried - the system update proceeds till about the 35% mark, then it switches to a message "Erasing" after which the tab reboots and gets stuck on the pulsating Samsung logo. I guess it is going to the ewaste bin.
Edit: finally successful in getting past the Samsung logo. Per instructions from another thread got into recovery, wiped data and cache. That did not resolve the issue on the first try, but after a couple of cycles of flashing firmware and wiping data + cache things all of a sudden started working. Not sure why or how.
One important note that is far from clear online is the process of getting into recovery. It often stated as "press home /vol up/power" which does NOT work. The correct process is
1) press vol dn / power /home
2) as soon as the screen goes black release vol dn and press vol up while continuing to hold the other two buttons
GroovyGeek said:
Alas the behavior of this known good ROM is identical to every other one I have tried - the system update proceeds till about the 35% mark, then it switches to a message "Erasing" after which the tab reboots and gets stuck on the pulsating Samsung logo. I guess it is going to the ewaste bin.
Edit: finally successful in getting past the Samsung logo. Per instructions from another thread got into recovery, wiped data and cache. That did not resolve the issue on the first try, but after a couple of cycles of flashing firmware and wiping data + cache things all of a sudden started working. Not sure why or how.
One important note that is far from clear online is the process of getting into recovery. It often stated as "press home /vol up/power" which does NOT work. The correct process is
1) press vol dn / power /home
2) as soon as the screen goes black release vol dn and press vol up while continuing to hold the other two buttons
Click to expand...
Click to collapse
Glad you eventually got it working.
So there is no clean way of downgrading from Nugot 7.0 to Marshmellow 6.0?