Related
I was attempting to get root access to my galaxy tab 2 10.1 running android 10.2.1 (or whatever the latest Samsung update was it is 10.2 on my phone but am sure it was 10.2.1 on the tablet.
I was following this guide that someone here recommended
http://www.ibtimes.co.uk/articles/4...-p5113-android41-jellybean-android404-ics.htm
I set usb debug and made sure the drivers were on my pc and made sure KIES was completely not running
Followed the instructions to the letter but should have worried when I found the instructions to get to download were wrong - I found on videos that it was reboot using power and right volume key. That was successful
It connected to ODIN fine and the yellow box came up
I made sure the two boxes were ticked and then searched for the file
CF-Auto-Root-espresso10wifi-espresso10wifibby-gtp5113.zip and started ODIN
it seemed to be going fine until suddenly a red box came up with update failed
Now all I can get on the device is "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
No matter how I try to restart this I get the same screen and imagine I couldn't connect to kies even if I should
Can anyone help as I am worried that I have bricked my device - I was looking for a simple way to get root without flashing a whole rom - or is that what I was doing anyway?
Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:
Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again
n0is said:
Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:
Click to expand...
Click to collapse
I will take a look but so far the only thing I get is the message to connect to KIES and it wont of course connect - cant get into any other modes - you would think they would have some kind of hard boot recovery button that gets you to basic screen to download the latest firmware.
And I did start here and believe that this led from a post here - I was trying to find the least complicated method of getting root access without changing what I already had too much - the only other process that I found on here seemed to have lots of people reporting problems if it wasn't a 3g model
It is beginning to look like I may have found out what bricking is - thanks for the reply anyway
would like to do that
mjrshark said:
Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again
Click to expand...
Click to collapse
In fact the instructions do say if it doesn't work first time, to run it again with the boxes unticked - the problem is that I cant get back to download mode, or any mode other than the message to connect to kies, so have no way of doing this. So looks like it may have bricked - is there any way of unbricking a tablet?:crying:
It's going to be an expensive mistake especially as I haven't even had the £50 cash back from Samsung yet and I would have to pay full price now to replace it,
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
not optamistic but will try!
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I will try but I don't think it is going to work. Whenever I connect the tablet by USB I get the usb connecting sound followed immediately by the USB disconnect sound - this just continues to happen every 4 seconds or so all the time that the device is connected. At the moment I have it on charge as once the error screen comes on it doesnt seem to go off for a very long time and then it wont start unless I charge it first. After a few minutes on charge - The firmware upgrade encountered an issue message comes up. I am going to leave it a while until I am sure it is fully charged and then try what you suggest - not optamistic though since I now realise that it is not even connecting properly. I just have a bad feeling about this. I had to disconnect it from the power yesterday because the error screen stays on continuously and the device starts to get warm
Assuming that I ever manage to get a stock image installed will this mean I can go back to normal kies updates - all I really wanted was the standard samsung android O/S but with super user added.
Unfortunately I had read the linked article a while back and what made me more confident was the statement that said it was "virtually impossible to brick this device"
Since it's still going into Charging mode and spitting out error messages, it's not completely bricked. It's just in a reboot loop (a.k.a. soft brick).
Keep trying to get it into Download mode. Sometimes the timing is a little tricky if it's in a boot loop.
1. Disconnect it before trying to get it into Download Mode. If it's plugged in (charger or PC), the device will go into Charging mode instead.
2. Hold the Power button for 10 seconds to make it reboot.
3. When you see the screen turn off, let go of Power and then press and hold Power and Volume Right/Up.
4. If done correctly, it will immediately go into Download Mode. If you see the Samsung logo instead, repeat from Step 2.
some progress but still stuck - any more ideas please
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Hi well thanks -
when I connected Odin it did show up yellow and so I downloaded the P5110 stock from from the other thread - all went well and it reported all OK and re-booted - saw the animated sequence but now it has stalled on the samsung logo and still wont connect to kies
So still stuck but at least it has moved on - The instructions on the other page were a little unclear about one stage
It said if there was pit file included to set something and tick repartition - this was all in one line and so I assumed part of the pit instruction - as there was no pit file I did not tick re-partition - I wonder if I should have done?
I have just reconnected to ODIN and the ID Com is still lit up yellow so presumably I could try running it again, or should I look on here for another stock rom - I am wondering if I have somehpw scewed up the bootloader and if so how I go about restoring it
ODIN is the only thing it connects to right now
OK, Ive been without my note for a whole day and been researching wht to do nonstop
What happened to me was that, since i had updated to official kitkat, i soon developed a taste for lollipop, and went on to try out different ROMs and finally settled on to crDroid
So it was one of those days where everything was going well until the note stopped opening apps for like a minute then showd a black screen and then all of a sudden restarted
Since this was a Sammy i thought it would get back up again.... But no, even a 5 minute didnt wake this beast up, it remained stuck at the boot logo, i.e, Samasung Galaxy Note 10.1
Im like ok ill go on do a factory reset and wipe cache and all, upon trying to accesss the recovery after the boot logo the recovery kinda opens then gets back at boot logo, a black screen shows up then turns on to be a full brightness black screen for a sec then goes back
I can access the download mode and can odin things but they fail every single time.
I have tried to odin a recovery and a stock recovery so far and they show a nand write error
i also have tried to PIT but they get stuck at get PIT for mapping
I have also tried all versions of odin tried changing a USB Port and the wire with no success
So is there any hope for my NOTE??
Please i need help its urgent
Osama Abedin said:
OK, Ive been without my note for a whole day and been researching wht to do nonstop
What happened to me was that, since i had updated to official kitkat, i soon developed a taste for lollipop, and went on to try out different ROMs and finally settled on to crDroid
So it was one of those days where everything was going well until the note stopped opening apps for like a minute then showd a black screen and then all of a sudden restarted
Since this was a Sammy i thought it would get back up again.... But no, even a 5 minute didnt wake this beast up, it remained stuck at the boot logo, i.e, Samasung Galaxy Note 10.1
Im like ok ill go on do a factory reset and wipe cache and all, upon trying to accesss the recovery after the boot logo the recovery kinda opens then gets back at boot logo, a black screen shows up then turns on to be a full brightness black screen for a sec then goes back
I can access the download mode and can odin things but they fail every single time.
I have tried to odin a recovery and a stock recovery so far and they show a nand write error
i also have tried to PIT but they get stuck at get PIT for mapping
I have also tried all versions of odin tried changing a USB Port and the wire with no success
So is there any hope for my NOTE??
Please i need help its urgent
Click to expand...
Click to collapse
is it rooted ?
i have the same problem from 2 months and i am finally got that i must replace the motherboard
Sounds like its written its last, flash is dead.
Since you are able to enter in download mode there is hope. Trying to flash recovery which doesn't match the firmware version will always fail. So, try flashing some of the base firmwares which will return everything to stock. I was in your situation few months ago and managed to flash Android Revolution HD 4.4.2 after first flashing stock firmware via odin. I got my 4.4.2 base firmware from "sammobile.com", firmware section (sorry i don't have enough posts for using links).
I remember i tried flashing TWRP for GT N8000 and i also tried Philz then CWM all for GT N8000
I also tried flashing base rom but it gives NAND write fail
Nand write fail can mean damaged PIT or the actual nand memory is damaged and needs a new motherboard .
flash with pit file
found these pit files for the device.
you can flash the pit file for GT-N8000 in odin
don't forget to repartition, it's a very delicate situation, you don't want to mess it up, before going to this, you should confirm if the size are same. you wont like to flash a 16gb to 32gb partition.
http://forum.xda-developers.com/showthread.php?p=41158546#post41158546
good luck and please share your fix if its done
billysam said:
found these pit files for the device.
you can flash the pit file for GT-N8000 in odin
don't forget to repartition, it's a very delicate situation, you don't want to mess it up, before going to this, you should confirm if the size are same. you wont like to flash a 16gb to 32gb partition.
http://forum.xda-developers.com/showthread.php?p=41158546#post41158546
good luck and please share your fix if its done
Click to expand...
Click to collapse
thx for telling me... im trying out a new wire so will try it out nxt week
Sorry for the late reply tho
Osama Abedin said:
thx for telling me... im trying out a new wire so will try it out nxt week
Sorry for the late reply tho
Click to expand...
Click to collapse
same problem for me, this did not work, still write error
I have a similar problem. Everything is stuck. I am tryingo to go back to stock, but if I try to connect (via Odin, Heimdall, fastbot or adb sideload) i can't.
Is there any advice?
Thanks
nope not yet
I'm early ???
So it turned out that my AMAZING tablet had its storage device corrupted... I. E I exceeded the read write count
Similar problem Bricked N8005
I bought my N8005 (variant of N8000 but phone is disabled just data 3G is available) in 2012. I rooted it once and used custom rom for a while but last year installed official stock ROM again. Yesterday I started a game called "zombidle" (possibly this is an unnecessary info) and tablet restarted itself but stuck on "samsung" logo.
I tried to enter recovery mode but it always restarted and cannot enter recovery mode.
Tried to install different versions of CWM, Philz and TWRP recovery using odin but it always FAILed when NANDwrite started. Tried odin 1.85, 1.87, 3.07, 3.09, 3.12 but all same.
I tried to install same stock ROM but always FAILed.
Then I tried to install a custom rom but it failed too.
I read about bad pit files. Searched internet and found some pit files but nothing changed, FAILed at same point.
Did I finished all solutions?
Should I take it to the doctor?
Any sugesstions?
Thanks in advance.
Edit: Today I took it to the Samsung doctors. They said that; this is a mainboard issue and mainboard needs to be changed. That will be over 400TL (TL=Turkish Lira). Device is still in markets and new N8005 is 1300TL (i think this is also expensive. Because new Samsung Galaxy Tab S2 T817 32GB 9.7" is 1900TL in my country).
Does it worth to fix? Any opinions? Can I fix it myself somehow?
Nand write fail probable defunct memory.
Hi all..or anyone out there
I have had the seemingly strange bootloop problem on my stock note N8010...which stuck on the dreaded "samsung galaxy note 10.1" and only has odin feature working. (and no factory reset options because I think the poor old tab is crammed to bursting with apps, files and cache and so had a meltdown) poor thing.
so anyway I check these sites of techie wonder and wisdom and followed every logical option..starting with the simple ones
first ran power down and tried to boot up (x3) with no joy, then take apart the tablet to disconnect / reconnect the battery and boot up (x3) still no change.
So went and got the firmware from samwares (both jelly bean and kitkat) to then flash through odin....tried and failed first because of dodgy cable, but the then got a new one...and joy of joys (at first) odin recognised my tab and the firmware flashed across with pass..but then auto rebooted straight back into the dreaded samsung 10.1 again....so tried different versions of odins... and tried other global n8010 firmware...but funnily and frustratingly then all fully download and pass in odin (and the andoid logo and green download status bar on the tablet seems to shown that downloading is and has fully taken place.... but the darn thing still wont boot up past the samsung galaxy note 10.1
Sadly coming to the ends of my tether (of so many nearly there false hopes, high and lows) and very little cash to send it to the Sami tech bods doesnt help matter....I then read and tried the (supposed) last resort pit file/firmware option...first with kitkat (as apparently that worked for someone somewhere) and then tried with jelly bean..again each time itAlways passes in odin.... but auto reboots into the dreaded bootloop logo .... to haunt and torment me.. Aaaaagh!!!!.....I would not mind if it said action failed (for once) like some others seem to experiencet...but it always passes in ODIN????
So.....have come to the semi ignorant conclusion it is either the bootloader section of the tablet or the original software that is messed up or some internal hardware component has a fault.
but was wondering if there is anthing left to try...or would it potentially be possible or worth trying to root a tablet in this condition?
As although I have not ventured into the wild worlds of rooting.....I am now pretty confident of messing with this tablets mind..and have little to lose...so any further ideas and help would be great.
Exact same here. Never flashed, totally stock N8010. My wife hadn't used it for a couple of weeks. So she grabs it again and it was off. booted to nothing but the boot logo. Nothing worked except Download mode.
Flashing stock roms has Odin reporting success, but it still won't boot up. Trying re-Partition does give a fail as soon as I press start.
And we aren't alone. It appears there are quite a few of these cases. I have no idea how to solve this.
I have done a bit of rom flashing on my old galaxy S (the first one) and bootloaders and such usually were included in a ROM. Rooting was done with Recovery or an app and I think it was also possible with adb, IIRC (it's been a while).
It's my wife's Note and she's starting to scope out mini iPads...
Same problem with GT-N8010
I am also having the same problem.
I tried to upload a new ROM via ODIN. All was successful from the ODIN app (PASSED). but stuck on the boot screen. Power and Vol up does not work (it appears to but then crashes out to the boot screen again) so no way to do a hard factory reset.
Volume down/power does work and allows you to get to Odin mode. but as above, uploading a new ROM does not seem to work.
This is an un-rooted GT-N8010 with the stock ROM when I purchased it back in 2013 I believe.
Come on guys, give us some ideas.
Thanks
Gene
Sounds like wrong model firmware flashed as that's the usual bootloop problem .
Try Odin firmware flash wait to passed then remove battery for a short while and replace and try recovery mode .
In my case there is no incompatible firmware issue... The tablet just stopped working one morning and that was that.
Can't comment on the other posters though.
Sent from my GT-I9305 using XDA Free mobile app
Gene_uk said:
In my case there is no incompatible firmware issue... The tablet just stopped working one morning and that was that.
Can't comment on the other posters though.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
My wife's the same. Never done anything to it. No idea how to remove the battery. I let the battery run down once, then recharged it, made no difference.
That was before trying to flash the new firmware. My Note says N8010 on the back, it says so in the download mode. I got a firmware from SamMobile for the N8010. Don't know what else I can do.
Widdly said:
My wife's the same. Never done anything to it. No idea how to remove the battery. I let the battery run down once, then recharged it, made no difference.
That was before trying to flash the new firmware. My Note says N8010 on the back, it says so in the download mode. I got a firmware from SamMobile for the N8010. Don't know what else I can do.
Click to expand...
Click to collapse
Having same problem here ... tried flashing different firmwares along with PIT file - still no luck ..
stuck on samsung galaxy note screen .. cannot get recovery mode
Any help guys?
Hi all I will keep it brief.
I have tried to flash with Odin 3.10.6, 3.10.7, 3.09, 3.10 root, twrp, stock firmware G920F but everything fails at "Nand Write Start" its driving me crazy. I've tried different versions of Odin, Twrp, and even Smart switch multiple times but nothing will write to the phone. ODIN ALWAYS FAILS AT NAND WRITE START.
My phone will only boot into download and NOTHING else not even recovery.
Any help welcome......
Try different firmware revisions. You flashing stock? What was the last fw successfully flashed?
Sent from my SM-G920F using Tapatalk
It is Stock G920F (united kingdom EE (EVR).
My problem is No matter what version of Odin or what I try to flash Odin always fails after Nand Write Start. It's not just the stock firmware, it's anything I try to flash in download mode.
Im actually in the same boat just now. ODIN wont flash the EVR Firmware (previously it did, mine fails on the cm.bin). I have tried different ODIN versions and also different laptops. Also the Smart Switch / Kies3 recovery procedure didnt work for me either. I was able to flash TWRP via down and get into recovery, but it see a lot of unable to mounts when trying to flash custom ROM and fails to do so. I think that i might have stupidly wiped via recovery something i should not have as i did noticed before all this i lost me IMEI (unknown).
I always assumed that if you can get into download you would always be ok but this is the first time for me that im having big issues.
I really hope someone can help out other wise i have a really expensive paperweight.
cooltt said:
It is Stock G920F (united kingdom EE (EVR).
My problem is No matter what version of Odin or what I try to flash Odin always fails after Nand Write Start. It's not just the stock firmware, it's anything I try to flash in download mode.
Click to expand...
Click to collapse
Reactivation lockn as seen in download mode?.
Sent from my SM-G925F
---------- Post added at 04:06 PM ---------- Previous post was at 04:04 PM ----------
johnnyblaze1977 said:
Im actually in the same boat just now. ODIN wont flash the EVR Firmware (previously it did, mine fails on the cm.bin). I have tried different ODIN versions and also different laptops. Also the Smart Switch / Kies3 recovery procedure didnt work for me either. I was able to flash TWRP via down and get into recovery, but it see a lot of unable to mounts when trying to flash custom ROM and fails to do so. I think that i might have stupidly wiped via recovery something i should not have as i did noticed before all this i lost me IMEI (unknown).
I always assumed that if you can get into download you would always be ok but this is the first time for me that im having big issues.
I really hope someone can help out other wise i have a really expensive paperweight.
Click to expand...
Click to collapse
Try to flash latest fw. Probably you've upgraded the bootloader to which cannot be downgraded.
Sent from my SM-G925F
What i've noticed with the S6 (and S7 i presume) is because you can't shut the phone down completely when your stuck on the download screen it never fully resets itself for another attempt at flashing by Odin. If your hold Power+Volume down to shut it off, the screen just goes black briefly then it comes back onto that error message about connecting it to Smart Switch for emergency recovery.
Smart Switch is a waste of time, it will download all the software for your device , say it's going to install then you get an error message telling you to use recovery code which of course it does not give you! So basically you just go round and round in circles with Odin and Smart Switch, i'm convinced it's not being able to shut the phone down completely that causing the problem of failed attempts.
Anyway something you might try that allowed me to flash G920F United Kingdom EE (EVR) PDP in the end. >>>
The phone battery eventually died, i waited for 10 minutes before charging it up to around 15% again, then i put it into Download mode, made sure my windows 10 laptop had "debugging" enabled at start up (i think this is why Nand Write Start is failing).
I loaded up ODIN 3.10.7 with "Cf auto root", connected my phone then flashed the root file straight away. It worked, so i reset Odin, put phone back in download mode and flashed EVR quickly via odin and it worked.
Over all i thin there's 2 issues here: The phone cannot be completely shut down when it will only boot to download or that smart switch recovery error and Windows 10 keeps turning off "debugging mode" which prevent Nand Write to device. I may be wrong but after hours of attempts with lots of different Odin and Firmware thats what i noticed. There has to be a way of shutting the S6 off completely .
NB: Tried latest BTU firmware, won't flash same problem "Nand Write Fail"
NB; Reactivation lock is OFF
cooltt said:
What i've noticed with the S6 (and S& i presume) is because you can't shut the phone down completely when your stuck on the download screen it never fully resets itself for another attempt at flashing by Odin. If your hold Power+Volume down to shut it off, the scree just goes black briefly then it comes back onto that error message about connecting it to Smart Switch for emergency recovery.
Smart Switch is a waste of time, it will download all the software for your device , say it's going to install then you get an error message telling you to use recovery code which of course it does not give you! So basically you just go round and round in circles with Odin and Smart Switch, i'm convinced it's not being able to shut the phone down completely that causing the problem of failed attempts.
Anyway something you might try that allowed me to flash G920F United Kingdom EE (EVR) PDP in the end. >>>
The phone battery eventually died, i waited for 10 minutes before charging it up to around 15% again, then i put it into Download mode, made sure my windows 10 laptop had "debugging" enabled at start up (i think this is why Nand Write Start is failing).
I loaded up ODIN 3.10.7 with "Cf auto root", connected my phone then flashed the root file straight away. It worked, so i reset Odin, put phone back in download mode and flashed EVR quickly via odin and it worked.
Over all i thin there's 2 issues here: The phone cannot be completely shut down when it will only boot to download or that smart switch recovery error and Windows 10 keeps turning off "debugging mode" which prevent Nand Write to device. I may be wrong but after hours of attempts with lots of different Odin and Firmware thats what i noticed. There has to be a way of shutting the S6 off completely .
Click to expand...
Click to collapse
There is no recovery code as far as I remember. As long as you have the sn that should make a go.
And there is no way to shutdown the phone completely. We can force reset but it will only shutdown whem the battery depleted.
Sent from my SM-G925F
Rosli59564 said:
There is no recovery code as far as I remember. As long as you have the sn that should make a go.
And there is no way to shutdown the phone completely. We can force reset but it will only shutdown whem the battery depleted.
Sent from my SM-G925F
Click to expand...
Click to collapse
Smart Switch is useless! I put in the model SM-G920F then the serial number and SS tells me the correct firmware is (EVR), downloads it, prepares it for installing, starts to install, gets to 1% then says "an error has occurred please use the Emergency code below to recover your phone" BUT there is no code! It says Emergency recovery code: .......nothing.
The main issue i'm experiencing is ODIN will not flash anything of any version, always fails at "Nand Write Start".
I've tried multiple versions of Odin, Stock Firmwares, TWRP, Root. Nothing will flash until the battery is dead, then when i try with a little charge for the first time Odin will usually flash the 1st file i give it (no matter what it is) then thats it, back to failing after "Nand Write Start".
Driving me crazy.
Quick update. I loaded a later FW (Still UK) and it passed in ODIN, so that was better.
But after that it booted into stock recovery, showed unable to mount efs (no sim card in). I then rebooted and its been on a blank screen ( with the blue light flashing) for the last 30mins. No real signs of life.
Cheers
johnnyblaze1977 said:
Quick update. I loaded a later FW (Still UK) and it passed in ODIN, so that was better.
But after that it booted into stock recovery, showed unable to mount efs (no sim card in). I then rebooted and its been on a blank screen ( with the blue light flashing) for the last 30mins. No real signs of life.
Cheers
Click to expand...
Click to collapse
The stock didn't flash correctly then. After you flash stock with ODIN it should reboot into recovery, should just boot into MM, and go through phone set up.
The problem with flashing different Stock firmware (even if it's same region) it can cause all sorts of issues. There's G920F BTU which is the non branded stock for Galaxy S6 G920F then there's G920F EE (EVR) G920F Vodafone (VOD) etc
You'd think the non branded BTU would be fine on any UK S6 but that's not the case unfortunately.
Use Smart Switch and go through the emergency recovery option, one you put in your model and serial number it actually tells you what stock firmware your phone was shipped with, then you find it and flash it through ODIN.
cooltt said:
The stock didn't flash correctly then. After you flash stock with ODIN it should reboot into recovery, should just boot into MM, and go through phone set up.
The problem with flashing different Stock firmware (even if it's same region) it can cause all sorts of issues. There's G920F BTU which is the non branded stock for Galaxy S6 G920F then there's G920F EE (EVR) G920F Vodafone (VOD) etc
You'd think the non branded BTU would be fine on any UK S6 but that's not the case unfortunately.
Use Smart Switch and go through the emergency recovery option, one you put in your model and serial number it actually tells you what stock firmware your phone was shipped with, then you find it and flash it through ODIN.
Click to expand...
Click to collapse
Already tried that. Flashing the EVR just doesnt work, ODIN Fails every time. Smart Switch says it should be EVR based on S/N but i just cant get it flashed.
Dont know what else to try.
Cheers
You might also try Win7 or earlier, 32-bit, if possible. There are known issues with Win8 and later.
Sent from my SM-G920F using Tapatalk
DarryDoo said:
You might also try Win7 or earlier, 32-bit, if possible. There are known issues with Win8 and later.
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Its WIN7 im using on both the work and personal laptop, neither of which have had any issues in the past.
IF i flash EVR, it fails, i then flash TWRP to reboot into Recovery, but i see there alot of unable to mount / error messages, possibly the partitions are damaged? I dont know.
cheers
Hello community,
I regulary use some custom or stock firmware for my Samasung phones for several years (since My first Galaxy S1 !)
I love refurbirsh old phones withh new relases of android when operators and Samsung stop maintenance. I Limit my experimentation to last stock roms from Sammobile or CyanogeneMod/LineageOS wihth open Gapps.
Last days it was my galaxy S7's turn, to give it to my daughter : New battery,new back cover and new ROM.
My goal was to install Android 9/lineageOS 16 herolte version from operator stock rom.
First try : install TWRP with adb and linux heimdall. Tricky part was to reboot in recovery mode before it is overwritten by stock rom.
Not so easy without battery removal. Result, I ended in boot loop because of crypted data partition. First mistake.
2nd try : Format system and data via TWRP install lieageos zip and nano Gapps. Worked OK.
BUT, impossible to power off the phone. Only reboot was possible even power off with TWRP.
Not happy with this.
3rd try : reinstall last stock Firmware from sammobile via Odin. Process successfull reboot OK. Minimal configuration to check all is working as expected.
4th try : Install TWRP via Odin. Process Successfull but haven't succeed to get Recovery mode befor normal boot.
Then things became bad : After boot to welcome screen (with the hour and notifications), phone became completly stuck. No touchscreen or button responsive.
I forced reboot with volume down + power.
And I fell into the green screen of death with the error message "emergency recover".
Since then I can still boot in download mode and Odin detect the phone correctly, but impossible to write anything back in the phone.
after clicking start button, Odin failed with timeout either at the begining, or at system.img from stock rom.
I have tried others USB cables, Other releases of Odin, others stock roms.
I although tried repart with PIT file, even "erase all" option. But Nothing else than timeouts, and reboots in green screen of death.
I'm afraid internal memory has been definitiveley corrupted.
I ended up with reopen the phone and remove battery to keep it safe.
Before I seek for another motherboard, I ask here if there is something else to try.
Thanks for your help.
Yes
1. Reinstall drivers
2. Try new Odin version
3. flash latest available stock firmware for your region.
4. Try to Run Odin with Administrator rights
5. Flash 4 file firmware
6. Flash one by one file firmware
7. Extract boot, kernel and recovery files from stock firmware and flash one by one, then do full firmware flash...
If can go to download mode can reflash stock firmware with odin.
Teddy Lo said:
Yes
1. Reinstall drivers
2. Try new Odin version
3. flash latest available stock firmware for your region.
4. Try to Run Odin with Administrator rights
5. Flash 4 file firmware
6. Flash one by one file firmware
7. Extract boot, kernel and recovery files from stock firmware and flash one by one, then do full firmware flash...
Click to expand...
Click to collapse
Which version of MS Windos? I have tried windows 7, and 10 neither worked!
What drivers?
I have tried 3.14.1, 3.14.4 - neither worked!
1. Samsung drivers :
Samsung_USB_Driver_v1.7.48.0.zip
drive.google.com
2. Latest stock firmware by using your full model name, and region for your device otherwhise it will fail all the time...
Latest stock firmware by using your full model name, and region for your device otherwhise it will fail all the time...
Hi thank you for suggestions. I have prepared flash with heimdall by untar unlzm4 the imgs. But something went wrong maybe by unplug the battery. The phone never woke up.
Use multimater and check battery voltage it must be minimum 3.8v to boot up.... Since you messed up your bootloader you wont be able to charge your phone most likely. So you need then or buy new battery or charge manually direct...
Here is example:
Red wire is +
Black Wire is -
on your battery
See picture where is + and where -
Once you are Successfully charge your battery, put your phone into the Download mode Vol+ / Home /Power button, etc...
Good luck
Hi, I'm back with some more news. I've tried th above solution, Test battery with multimeter showed me 1V. I then tried to charge the battery. Tricky part was to stick the wire on such small pins. Anyway It sort of worked as I could measure 3.8V after charging
But bad luck, the phone still doesn't want to power up.
didou691 said:
Hi, I'm back with some more news. I've tried th above solution, Test battery with multimeter showed me 1V. I then tried to charge the battery. Tricky part was to stick the wire on such small pins. Anyway It sort of worked as I could measure 3.8V after charging
But bad luck, the phone still doesn't want to power up.
Click to expand...
Click to collapse
Make sure that the power button, and volume buttons has good connection, also check charging port if it is good connected and clean all dirt inside usb port.
My take on the battery would be buy a "new" one.
didou691 said:
Hi, I'm back with some more news. I've tried th above solution, Test battery with multimeter showed me 1V. I then tried to charge the battery. Tricky part was to stick the wire on such small pins. Anyway It sort of worked as I could measure 3.8V after charging
But bad luck, the phone still doesn't want to power up.
Click to expand...
Click to collapse
From past experience any fiddling with the contacts and "plugs" on the battery or else where is a very dodgy proposition. My suggestion is (as above) buy a new battery, the very low voltage (1V) makes me think that the battery is shot.
Good luck