Hello People
I am trying to downgrade Pie to Oreo as Pie has borked ACR Call Recorder (unchained) and it is a very bit of important software for me, now I have tried everything and nothing works which is really odd as 2 months ago the downgrade went swimmingly, but tried Pie again with the OTA so alas I wish to go back again and leave it at that.
I have a Windows 7 PC all up to date and powerful enough to get the job done.
I have tried so many variants it's silly now
Different Ports
Different cables including the genuine one
Different ROM's - XEU and BTU
Connected the phone first, connected the phone last
Different Odin versions with Admin Rights
Hours have been spent but still no go, it is really odd, can any of you kind folks come up with any ideas and if any more info like the Odin log is needed please let me know.
If all else fails could you recommend a Samsung phone with Android 8 with similar specs that won't get any more updates to replace the phone that I am trying to downgrade which is the A8 2018 SM-A530F
Many Thanks for any help/replies
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 5478 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HULK SMASH.......
lomax512 said:
Hello People
I am trying to downgrade Pie to Oreo as Pie has borked ACR Call Recorder (unchained) and it is a very bit of important software for me, now I have tried everything and nothing works which is really odd as 2 months ago the downgrade went swimmingly, but tried Pie again with the OTA so alas I wish to go back again and leave it at that.
I have a Windows 7 PC all up to date and powerful enough to get the job done.
I have tried so many variants it's silly now
Different Ports
Different cables including the genuine one
Different ROM's - XEU and BTU
Connected the phone first, connected the phone last
Different Odin versions with Admin Rights
Hours have been spent but still no go, it is really odd, can any of you kind folks come up with any ideas and if any more info like the Odin log is needed please let me know.
If all else fails could you recommend a Samsung phone with Android 8 with similar specs that won't get any more updates to replace the phone that I am trying to downgrade which is the A8 2018 SM-A530F
Many Thanks for any help/replies
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 5478 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HULK SMASH.......
Click to expand...
Click to collapse
First thing don't post questions in development section.
If you upgraded your bootloader you can't down grade ever again.
mchlbenner said:
First thing don't post questions in development section.
If you upgraded your bootloader you can't down grade ever again.
Click to expand...
Click to collapse
Hi, a chap called Thanos helped me out with putting the thread in the right place, sorry about that.
As I reverted back to Oreo a few months back and then the OTA went to Pie again and after that I may of had another update do you think that the last OTA update after Pie may of upgraded the bootloader, as said I did revert to Oreo a few months back.
Thanks
lomax512 said:
Hi, a chap called Thanos helped me out with putting the thread in the right place, sorry about that.
As I reverted back to Oreo a few months back and then the OTA went to Pie again and after that I may of had another update do you think that the last OTA update after Pie may of upgraded the bootloader, as said I did revert to Oreo a few months back.
Thanks
Click to expand...
Click to collapse
I would say yes it had upgraded your bootloader.
For that reason you will not be able to down grade again.
The only way you can get back to Oreo would be to root your device.
mchlbenner said:
I would say yes it had upgraded your bootloader.
For that reason you will not be able to down grade again.
The only way you can get back to Oreo would be to root your device.
Click to expand...
Click to collapse
Right that's a final nail in the coffin for trying to roll back the device as I won't be rooting, so with this in mind would
you know of a device by Samsung that has similar specs but will never get the Pie update.
I do appreciate your help
lomax512 said:
Right that's a final nail in the coffin for trying to roll back the device as I won't be rooting, so with this in mind would
you know of a device by Samsung that has similar specs but will never get the Pie update.
I do appreciate your help
Click to expand...
Click to collapse
I have no idea.
So how would I go about unlocking the bootloader I really need to get back to Oreo.
The S7 stopped at Oreo. It's about the closest you'll get. Forget about Oreo on your A8. You could try a combination ROM.
But before you brick it, go to Settings, About phone, Software information and give the Baseband version.. The 9th digit specifically. Is it a 6? 7?
I have the W variant in Canada, which is the exact same hardware. I have call recording. I can cook you up a rom to flash in twrp that won't have root. I just need to know your region.
It is call recording, right? That's the reason? No problem. It's already built in to your phone.
But you need to flash a custom recovery. And, it's free. Or do this:
get superr's kitchen
unpack your stock rom
go to the omc folder and locate your carrier and add this neatly within the paramaters of the cscfeature.xml file:
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
Build full rom zip
Flash TWRP in Odin to your device
Flash the ROM zip from the kitchen in TWRP
Problem solved. No root. Make sure to eliminate the space in the .xml entry. Don't want you to do all that for nothing. It just comes out like that when i paste it. All owed. No good.
This thread is in the wrong section. If it does not get moved, start a new one in the right location and go from there. Or just get an S7
---------- Post added at 05:21 AM ---------- Previous post was at 04:57 AM ----------
Oopsie! Almost forgot!
Before building the zip in superr, unpack the boot.img and i believe it'll be options 3 and 4 to disable dm-verity and force encrypt. Leave option 2 alone and secure.
If you're OEM locked, well then that's a whole other issue.
Get crackin'!
mindlery said:
The S7 stopped at Oreo. It's about the closest you'll get. Forget about Oreo on your A8. You could try a combination ROM.
But before you brick it, go to Settings, About phone, Software information and give the Baseband version.. The 9th digit specifically. Is it a 6? 7?
I have the W variant in Canada, which is the exact same hardware. I have call recording. I can cook you up a rom to flash in twrp that won't have root. I just need to know your region.
It is call recording, right? That's the reason? No problem. It's already built in to your phone.
But you need to flash a custom recovery. And, it's free. Or do this:
get superr's kitchen
unpack your stock rom
go to the omc folder and locate your carrier and add this neatly within the paramaters of the cscfeature.xml file:
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
Build full rom zip
Flash TWRP in Odin to your device
Flash the ROM zip from the kitchen in TWRP
Problem solved. No root. Make sure to eliminate the space in the .xml entry. Don't want you to do all that for nothing. It just comes out like that when i paste it. All owed. No good.
This thread is in the wrong section. If it does not get moved, start a new one in the right location and go from there. Or just get an S7
---------- Post added at 05:21 AM ---------- Previous post was at 04:57 AM ----------
Oopsie! Almost forgot!
Before building the zip in superr, unpack the boot.img and i believe it'll be options 3 and 4 to disable dm-verity and force encrypt. Leave option 2 alone and secure.
If you're OEM locked, well then that's a whole other issue.
Get crackin'!
Click to expand...
Click to collapse
Hi there
Before I do any of that.... Wil it invalidate my warranty?
I am looking at the A7 2017 and S7
Also this thread has been moved once by Thanos just after the snap, lol
I may also have some other news that I can't post just yet via Samsung themselves...
Well there cannot be too much left on your warranty...
My previous unit was an A5 2017. Screwed that thing up so many times and back again. No CSC, different CSC, how did it boot and why did i try it... My A8 just in the past week has done well over 25 zips in TWRP.
Not saying these are invincible, but if you do it right and with the proper preparation (one thing really) then it's not likely going to cause any harm.
What you've already done is much worse than what you can do. You've attempted quite literally to break your device by flashing software onto it that is being rejected. And you did it a lot.
Why not do it one more time and have it work?
Tell me what region you are using and if you do it soon enough you'll have a debloated ROM with call recording by tomorrow afternoon... umm... my time for sure.
I've learned to keep Odin ready for any 911 emergencies. It's already loaded and on stand by if things get critical. But i am also doing things i have to test. This site is our manual. It is written here. When it's not in the manual i make it up.
You can probably flash a stable ROM now if you look around. Or just tell me what you want removed/added and i'll do it.
When you install twrp (wait for the zip so you can do it all at the same time)... all you gotta do is have your hand ready to hold volume up + power the second your phone turns off. The file WILL work. If you watch it on your computer screen, you'll more than likely fail. (Fixable but boring). The moment you click on start, you need eyes on the phone and fingers poised. Try not to sweat or have greasy hands. I mean it.
It takes about 2.5 seconds to flash and while you are feeling victorious, you missed a half second of boot and now you gotta put stock on it and try again after the blue circle of pain dances on your screen during the excitng google set up.
DON'T LOOK AT THE COMPUTER SCREEN! DON'T DO IT!
Anyway... have your stock ready just in case.
And tell me what it is. I do it for fun. It'll get used.
mindlery said:
Well there cannot be too much left on your warranty...
Click to expand...
Click to collapse
Yes there is a lot of warranty as my contract falls in a funny time of the year.
mindlery said:
My previous unit was an A5 2017. Screwed that thing up so many times and back again. No CSC, different CSC, how did it boot and why did i try it... My A8 just in the past week has done well over 25 zips in TWRP.
Not saying these are invincible, but if you do it right and with the proper preparation (one thing really) then it's not likely going to cause any harm.
What you've already done is much worse than what you can do. You've attempted quite literally to break your device by flashing software onto it that is being rejected. And you did it a lot.
Click to expand...
Click to collapse
Sorry buddy you are wrong, I flashed it once a few months back first go and it worked fine as said, then I tried again after the Pie OTA update happened again my fault, but I went to flash it again and no go so inbetween the first flash and my next go Samsung released a patch that stopped the OS downgrade.
Not once did the flash take all I got was FAIL in Odin time and again so I thought maybe it's a USB, Firmware, Cable, or some mistake I was making but alas not, the phone is fine.
mindlery said:
Why not do it one more time and have it work?
Tell me what region you are using and if you do it soon enough you'll have a debloated ROM with call recording by tomorrow afternoon... umm... my time for sure.
Click to expand...
Click to collapse
I am in the UK thats why I wanted to try the BTU firmware
mindlery said:
When you install twrp (wait for the zip so you can do it all at the same time)... all you gotta do is have your hand ready to hold volume up + power the second your phone turns off. The file WILL work. If you watch it on your screen, you'll more than likely fail. (Fixable but boring).
It takes about 2.5 seconds to flash and while you are feeling victorious, you missed a half second of boot and now you gotta put stock on it and try again after the blue circle of pain dances on your screen during the exciting google set up.
DON'T LOOK AT THE COMPUTER SCREEN! DON'T DO IT!
Anyway... have your stock ready just in case.
And tell me what it is. I do it for fun. It'll get used.
Click to expand...
Click to collapse
But I do not wish to void the warranty x
I don't think you can avoid that.
---------- Post added at 03:24 PM ---------- Previous post was at 03:01 PM ----------
Unless you learn to make a combination file (which probably will not even allow a downgrade) there is NO other option besides purchasing another device.
The member you chatted with yesterday already told you.
You are using a phone that is running the latest Samsung software AND one relatively unpopular. You can try, but your much more likely to end up with hardcore browser pop-ups and a door stop.
You can flash a zip made from official firmware altered in an extremely well made kitchen using TWRP, the best custom recovery available and i years of expert design... which thousands of people are doing right now... or not.
mindlery said:
I don't think you can avoid that.
---------- Post added at 03:24 PM ---------- Previous post was at 03:01 PM ----------
Unless you learn to make a combination file (which probably will not even allow a downgrade) there is NO other option besides purchasing another device.
The member you chatted with yesterday already told you.
You are using a phone that is running the latest Samsung software AND one relatively unpopular. You can try, but your much more likely to end up with hardcore browser pop-ups and a door stop.
You can flash a zip made from official firmware altered in an extremely well made kitchen using TWRP, the best custom recovery available and i years of expert design... which thousands of people are doing right now... or not.
Click to expand...
Click to collapse
Hello again
Samsung have got back to me to say they won't help as it will affect my devices security if they roll back the firmware or if they give me the tools and steps on how to do, they confirmed it is all Googles fault that call recording has been withdrawn but I fired off another email to say I do not care about device security etc.... I think it is more to do with they can't be bothered or don't want to loan me any software of instructions, anyway still gotta try.
They did say that Android Q has no option to call record with 3rd party apps but in 2020 Android R is bringing it back, so it seems that Google are run by idiots, lol
As for what you say I am willing to take the plunge if I don't sell the device on fleabay to get money to get an A7 2017 or S7, and if in a final email Samsung still refuse to play ball.
After that I may as well just do what the hell I like with it, in actual fact I may just flash it with a custom ROM anyway, also is there anything to 0 the knew Knox junk like Yellow Triangle Away if I even put it back to stock etc.
Cheers :highfive:
Totally true, eh? EH?
mchlbenner said:
I would say yes it had upgraded your bootloader.
For that reason you will not be able to down grade again.
The only way you can get back to Oreo would be to root your device.
Click to expand...
Click to collapse
lomax512 said:
Hello again
Samsung have got back to me to say they won't help as it will affect my devices security if they roll back the firmware or if they give me the tools and steps on how to do, they confirmed it is all Googles fault that call recording has been withdrawn but I fired off another email to say I do not care about device security etc.... I think it is more to do with they can't be bothered or don't want to loan me any software of instructions, anyway still gotta try.
They did say that Android Q has no option to call record with 3rd party apps but in 2020 Android R is bringing it back, so it seems that Google are run by idiots, lol
As for what you say I am willing to take the plunge if I don't sell the device on fleabay to get money to get an A7 2017 or S7, and if in a final email Samsung still refuse to play ball.
After that I may as well just do what the hell I like with it, in actual fact I may just flash it with a custom ROM anyway, also is there anything to 0 the knew Knox junk like Yellow Triangle Away if I even put it back to stock etc.
Cheers :highfive:
Click to expand...
Click to collapse
Ohhhhhhh I see. Samsung has NO IDEA that one line in the cscfeature.xml enables what I and many others have had long before the A8 and to this day. Not one person there is aware. Nobody. Their best and brightest engineers just have no idea about it. In fact, little is known about why it's there, or if it even exists at all. Maybe it's not there. Yeah that's it. Photographs 1, 2 and 3 do not exist and are well known fakes. See? You know it has to be fake because of Google or something . Please ignore them.
Wait, wait... this wouldn't happen to be the same Samsung that told me I had no FM tuner and had to buy a different phone, would it? Maybe because they omitted an xml with about 4 lines. When the A8 first shipped out here, Samsung left the hybridradi apk in the phone. Why? Only because there was no tuner. It was only a coincidence that an xml was missing from the no FM tuner version. Totally true.
And I get it. Why bother using a built in feature when you can fire in a 3rd party app to do the job? That's your best bet. Ask Samsung.
Pictures 4,5, and 6 are a lie as well. If any Canadian tells you their A5, A8 or S8 has an FM tuner they're a liar. Samsung will tell you the truth, right? Guess that makes me a liar. Next thing you know, I'll say the Raptors beat Golden State in 6 for the title. I'm gonna go put on my toque and ride my polar bear over to the next igloo. No time for this stuff in June.
*Photos 7,8, and 9 are clear fakes*. Factory Binary is a myth, the S8 doesn't have an FM tuner in Canada. Darn. The lying never stops here eh? EH?
I'm finished here. Good luck.
mindlery said:
Ohhhhhhh I see. Samsung has NO IDEA that one line in the cscfeature.xml enables what I and many others have had long before the A8 and to this day. Not one person there is aware. Nobody. Their best and brightest engineers just have no idea about it. In fact, little is known about why it's there, or if it even exists at all. Maybe it's not there. Yeah that's it. Photographs 1, 2 and 3 do not exist and are well known fakes. See? You know it has to be fake because of Google or something . Please ignore them.
Click to expand...
Click to collapse
Haha I feel exactly the same way after the last reply I got, I will paste it here..............
Dear Mr xxxxxxxx, thank you for your email.
We would not have the information or tools to revert to a previous operating system. For provision of feedback about your product and operating system, this can be sent directly to Google through the feedback report feature, I have included the link below for your reference:
So yes they do not give one single snot, what an awful company it must be embarrassing to work for them, just try to imagine my reply back to Samsung (I would put names here but) :angel:
mindlery said:
Wait, wait... this wouldn't happen to be the same Samsung that told me I had no FM tuner and had to buy a different phone, would it? Maybe because they omitted an xml with about 4 lines. When the A8 first shipped out here, Samsung left the hybridradi apk in the phone. Why? Only because there was no tuner. It was only a coincidence that an xml was missing from the no FM tuner version. Totally true.
And I get it. Why bother using a built in feature when you can fire in a 3rd party app to do the job? That's your best bet. Ask Samsung.
Pictures 4,5, and 6 are a lie as well. If any Canadian tells you their A5, A8 or S8 has an FM tuner they're a liar. Samsung will tell you the truth, right? Guess that makes me a liar. Next thing you know, I'll say the Raptors beat Golden State in 6 for the title. I'm gonna go put on my toque and ride my polar bear over to the next igloo. No time for this stuff in June.
I'm finished here. Good luck.
Click to expand...
Click to collapse
Being from the UK I have no idea what or who the Raptors are but they would beat Samsung any day.
I totally believe what you have written and I am very grateful, I just wish Samsung had the know how and patience you have.
Thank you for everything
With this in mind I will be going to an S7 edge, I have found new ones in the UK from fleabay new at very good prices, obviously I will make sure they are new via inspection.
Thank you again, throw a snow ball for me :highfive: :good:
Image 9 was so fake I was blocked by internet cops on horses. I knew because they use seals for sirens. Here it is... i think...The fake Canadian S8 with FM tuner.
K NOW I'm done here. Your solution may outlast your warranty in my mind. Hope I am wrong. I've never assembled a combination ROM either.. I don't think you should even try.
mindlery said:
Ohhhhhhh I see. Samsung has NO IDEA that one line in the cscfeature.xml enables what I and many others have had long before the A8 and to this day. Not one person there is aware. Nobody. Their best and brightest engineers just have no idea about it. In fact, little is known about why it's there, or if it even exists at all. Maybe it's not there. Yeah that's it. Photographs 1, 2 and 3 do not exist and are well known fakes. See? You know it has to be fake because of Google or something . Please ignore them.
Wait, wait... this wouldn't happen to be the same Samsung that told me I had no FM tuner and had to buy a different phone, would it? Maybe because they omitted an xml with about 4 lines. When the A8 first shipped out here, Samsung left the hybridradi apk in the phone. Why? Only because there was no tuner. It was only a coincidence that an xml was missing from the no FM tuner version. Totally true.
And I get it. Why bother using a built in feature when you can fire in a 3rd party app to do the job? That's your best bet. Ask Samsung.
Pictures 4,5, and 6 are a lie as well. If any Canadian tells you their A5, A8 or S8 has an FM tuner they're a liar. Samsung will tell you the truth, right? Guess that makes me a liar. Next thing you know, I'll say the Raptors beat Golden State in 6 for the title. I'm gonna go put on my toque and ride my polar bear over to the next igloo. No time for this stuff in June.
*Photos 7,8, and 9 are clear fakes*. Factory Binary is a myth, the S8 doesn't have an FM tuner in Canada. Darn. The lying never stops here eh? EH?
I'm finished here. Good luck.
Click to expand...
Click to collapse
mindlery said:
Image 9 was so fake I was blocked by internet cops on horses. I knew because they use seals for sirens. Here it is... i think...The fake Canadian S8 with FM tuner.
K NOW I'm done here. Your solution may outlast your warranty in my mind. Hope I am wrong. I've never assembled a combination ROM either.. I don't think you should even try.
Click to expand...
Click to collapse
I have sent thee a PM, hope that's OK
mchlbenner said:
I would say yes it had upgraded your bootloader.
For that reason you will not be able to down grade again.
The only way you can get back to Oreo would be to root your device.
Click to expand...
Click to collapse
Please brother can you help me with explaining the method step by step i will be so grateful and thankful
I have the last version of oreo downloaded, on my phone I have uploaded the pie in the version given in the picture, which versions of oreo or other pie should I download to power the oreo to download without a problem ??
Related
Well I barely got my phone about 4 days ago, and i couldn't get my mind out of rooting and flashing the device.. and without much research... that's where I think I was being a little stupid.. I had got online and saw this program on wiki for samsung vibrant phones called "heimdall-suite-1.1.1-win32" and I read what it told me to do.. now this wikipedia site said that with heimdall i can flash "Cmenard-overstock-vibrant" I had done that and right away the phone would load up to the galaxy S boot logo and turn black... the only thing after that were the little lights would react to touching them. I got freaked out and started looking for information like crazy.. I honestly can say I started around 11Pm and did not go to bed researching til 7am and sadly still nothing.. I grabbed a better usb cable just today. my other one is kind of torn and kept coming on and off I would have to keep it at a certain angle. But this one works perfect! I don't get the actual charger til monday, the person I bought this phone has an Iphone 4s and didn't want his galaxy anymore so I took the opportunity to buy it for $100. A good deal like that I should of never played with this phone and I regret it... a day later I find out I don't have the vibrant.. I have the galaxy s 4g. I can still boot into download mode however now everytime it boots up it bootloops and has the samsung vibrant logo instead of the standard Samsung Galaxy 4g s logo with T-mobile. I'm finding this to be so complicated I wish I could go back to stock... please someone on here help me.. I'd appreciate it so much. Thank you for reading and I hope to get someone's response soon
**************************************************
12:52Am
I first want to say thank you guys for directing me towards the right area.
This is going to sound a little weird...
I've gotten the stock KC1 rom to flash and I kept getting failed. I thought I was stuck at the samsung screen logo
i waited about 2 minutes later and it booted up! Weird so anyways now what's bugging me now is this phone keeps Vibrating! what's going on? is there another update to a stock rom I can flash that will work? Do I have to be rooted? Can I unroot yet? (because I don't wanna mess with this no more!) lol what can I do to make this phone back to normal?
I'll tell you what I am capable of doing now
Go into stock recovery
Go into download mode
and boot my phone
once again I'd like to thank you all
*************************
UPDATE!!!!!
12:17AM Central
I have fully restored my rom with Mr. bkoon1218 assistance!!!
Here's what I did just in case anyone runs into what I did. I will say what mistakes I had done and then give my resolutions that couldn't have been possible without the assistance of these awesome members!
1. I was curious on flashing a custom recovery to my device, STUPIDLY I did not read or research anything regarding this phone.
2. I flashed Cmenard with heimdall-suite-1.1.1-win32 thinking that it would give me a recovery because I thought that I had the Samsung Galaxy *Vibrant*
3.Two days stressfully googling and googling for corrections and mistakes other may have done like me I had no choice but to ask myself.
I started off in the Vibrant section and a guy helped me out with flashing the rom but still nothing. Given instructions I felt my phone was done. I would get glitches and a nasty pixelated boot.
4. I researched my phone model number on the back of my phone and realized my phone wasn't the Vibrant.. Then it banged my head when another emailed me saying it was weird that my Samsung Vibrant was a 4g device lol.
5. I then moved to Samsung Galaxy S 4g and proceeded to find help along with the research I had done.. I even tried all the Odin updates thinking that could've made the difference.
*Resolution*
1. THANKS TO ALL FOR HELPING FIRST OFF ALL!!! YOU ARE ALL GREATLY APPRECIATED!! Next! A BIG THANKS! to * bkoon1218 *
for providing me with a helpful link where I read and understood what this rom was for. LINK - http://forum.xda-developers.com/show....php?t=1129933
2.Downloading Hawk.zip file I then used Winrar to extract it and there are four files!
-1.SGH-T959V-CSC-TMB.tar.md5
-2.Sgs4g.pit
-3.T959VUVKC1-Phone-CL932707.tar.md5
-4.T959VUVKC1-REV00-ALL-low-CL933594.tar.md5
3. I tried Odin 1.85 and it didn't work for me however I now know the reason why and what's funny is it happend accidentally.
I forgot to uncheck Re-Partition and I thought it would immediately softbrick my phone!! I started to see however it doing it's magic!
I said "ahh might as well let it go through the process I'll just one click unbrick my phone if it doesn't do it again..". By the way I used Odin 1.7.
and poom!!!! I got a pass!!! *This was only with Checking the box Re-Partition!*
4.So I am now fully fresh back to stock and unrooted and I am done. I decided to write this for any others that go through the same problem I did. I don't mean to take anybody's credit or anything I just want other to look this up when they accidentally flash their phone with a different rom and are as lucky as I am.
**MY ENDING RESULTS**
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T959VUVKC1-REV00-ALL-low-CL933594.tar.md5 is valid.
<OSM> T959VUVKC1-Phone-CL932707.tar.md5 is valid.
<OSM> SGH-T959V-CSC-TMB.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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> boot.bin
<ID:0/005> Sbl.bin
<ID:0/005> param.lfs
<ID:0/005> factoryfs.rfs
<ID:0/005> cache.rfs
<ID:0/005> data.rfs
<ID:0/005> modem.bin
<ID:0/005> cache.rfs
<ID:0/005> data.rfs
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
THANK YOU ALL AND GOOD LUCK TO YOU ALL!!!!!
Read the Bible in the stickies and Odin stock.
Sent from my SGH-T959V using XDA App
can you please provide me a link? I'm new sorry
Here's the Bible: http://forum.xda-developers.com/showthread.php?t=1117554
Read through it before you really brick your phone. You got lucky this time.
http://lmgtfy.com/?q=galaxy+s+4g+stock+odin
There is always a 5 second search on Google too.
Please use the search button to look around xda.... you the 9001st (over 9000!!!!) person to not read up on things before getting in over your head.
Sent from my SGH-T959V using XDA App
I've flashed with these and get all the way to the end and come up with a Fail.
I don't know what to do anymore I just want to go back to stock rom and not flash anything else but I'm a bit tired I've been doing this for almost three days and am starting to lose hope.. I just don't know what else to do
If you want to go back to stock, you might as well do stock GB.
Look for KI3 LEAK (you'll need bootloaders). Odin that in PDA and you'll be fine.
Hi I got a tab from China i think originally the baseband said ZCLA1. The default search engine and the chinese market app was annoying me since I couldn't read any of that. I thought I could just flash to a stock Euro firmware like XXKL7. . I've tried a few different versions from the Heimdall thread here and also firmwares I d/led from check fusI attempted many times with both heimdall and Odin. Heimdall got the furthest for me. I
Heimdall v1.3.2 would stop at cache and older versions of heimdall would fail at modem.bin both stopping after 100% and saying it could not confirm end of file transfer. after the heimdall update the language changed to russian i think but all the chinese apps were still there and default search baidu.
Code:
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Uploading PIT
PIT upload successful
Uploading KERNEL
0%
1%
100%
KERNEL upload successful
Uploading RECOVERY
0%
100%
RECOVERY upload successful
Uploading CACHE
0%
100%
ERROR: Failed to confirm end of file transfer sequence!
CACHE upload failed!
Ending session...
Rebooting device...
Odin would always fail before starting until I d/led the the new ICS update.
then i got
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P6200OXALQ1_P6200XXLQ1_P6200XXLQ1_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> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007> factoryfs.img
<ID:0/007> hidden.img
<ID:0/007> recovery.img
<ID:0/007> Sbl.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Right now it seems bricked and I can not do a recovery. I tried to do a search for zcla1 firmware and I couldn't find anything for the P6200. I saw the tab 10.1 and a few others had zcla1 firmware. But is that the same?
Is there something about the chinese tabs that prevents me from installing other firmware? Is there another way for me to install a non chinese firmware?
Also I've noticed everytime I flash with heimdall theres a counter that keeps going up on the download screen of the tab "Custom Binary Download: Yes (13 counts)" Should I need to worry about that?
Thanks for any suggestions you may have!
Perhaps it is a knock off ???
I'm getting same problem. Please help us!
MrNo said:
Perhaps it is a knock off ???
Click to expand...
Click to collapse
I don't believe it is but I really don't know how to prove or disprove that.
So after d/ling a ton of different firmwares and trying each one, I seem to have been able to install something that allows google apps.
Is it right that the Baseband,kernal and build are all different?
I'm a little afraid of trying to install ICS again because I really dunno how I fixed the problem in the first place. Does anyone else know what I can try to make this work? Or has anyone else know anything about these Chinese P6200s?
Try using Odin 1.85 it should work.
same thing here,
purchased a p6200 from china with no google support, wasn't too affraid at the start, just decided to use odin and push another firmware to it...
I tried ICS, nop same error as the original post here, so i tried a EU version, still not, tried a HK version, and still not.
Looks i can just push the original firmware back into it.
Will try to root and use mobile odin see if it can get better,...
Also there's no VPN option in the wireless settings.
Will let you know more about what i can find
Getting somewhere
ok so,...
I successfully flash a stock rom with heimdall using this post method:
http://forum.xda-developers.com/showthread.php?t=1517934
Thanks oarth
And i'm now running on 3.2 HC
Will now try to get the ICS running
will keep you guys posted
And..... Done
Ok, so I made it finally, ICS is running on my +***&"#@// Chinese P6200
Was tough in the first place to deal with it, has, I believe, the chinese ZCLA1 was kind of locked at some point...
I had to create a specific heimdall firmware tar.gz and flash it to the tab.
I'll upload it and link it tomorrow with a brief tutorial and explanation.
First time dealing with any of these, just knew what was rooting, and so on bout 3-4 days ago, so please feel free to let me know in the coming post if i did anything wrong or how it can be improved.
Thanks to XDA community for the different posts i went through, was a BIG help!
Post link for us
sirprize_p6200 said:
Ok, so I made it finally, ICS is running on my +***&"#@// Chinese P6200
Was tough in the first place to deal with it, has, I believe, the chinese ZCLA1 was kind of locked at some point...
I had to create a specific heimdall firmware tar.gz and flash it to the tab.
I'll upload it and link it tomorrow with a brief tutorial and explanation.
First time dealing with any of these, just knew what was rooting, and so on bout 3-4 days ago, so please feel free to let me know in the coming post if i did anything wrong or how it can be improved.
Thanks to XDA community for the different posts i went through, was a BIG help!
Click to expand...
Click to collapse
Hello Guys,
I am facing the same problem with my GT-P6200 Chinese version, now I get stucked on download mode or another screen telling me to connect KIES in restore mode. Could you post the link for tar file that you create and finally get ICS on P6200.
I am downloading now the file that you mention on the link (http://forum.xda-developers.com/showthread.php?t=1517934) and try to get live on my tablet again.
Thanks,
sirprize_p6200 said:
Ok, so I made it finally, ICS is running on my +***&"#@// Chinese P6200
Was tough in the first place to deal with it, has, I believe, the chinese ZCLA1 was kind of locked at some point...
I had to create a specific heimdall firmware tar.gz and flash it to the tab.
I'll upload it and link it tomorrow with a brief tutorial and explanation.
First time dealing with any of these, just knew what was rooting, and so on bout 3-4 days ago, so please feel free to let me know in the coming post if i did anything wrong or how it can be improved.
Thanks to XDA community for the different posts i went through, was a BIG help!
Click to expand...
Click to collapse
sirprize_p6200, could you post your solution? Currently I have a Chinese P6200 keep rebooting at the logo. Bricked? Desperately need a solution.
sirprize_p6200 said:
Ok, so I made it finally, ICS is running on my +***&"#@// Chinese P6200
Was tough in the first place to deal with it, has, I believe, the chinese ZCLA1 was kind of locked at some point...
I had to create a specific heimdall firmware tar.gz and flash it to the tab.
I'll upload it and link it tomorrow with a brief tutorial and explanation.
First time dealing with any of these, just knew what was rooting, and so on bout 3-4 days ago, so please feel free to let me know in the coming post if i did anything wrong or how it can be improved.
Thanks to XDA community for the different posts i went through, was a BIG help!
Click to expand...
Click to collapse
PLEASE can u upload the files you used i need to ressurect on Tab asap.....
Even with PIT file and Phone Bootloader Update checked...
Odin 1.85 log
<ID:0/082> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P6200DXKL3_P6200OLBKK8_P6200DXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/082> Odin v.3 engine (ID:82)..
<ID:0/082> File analysis..
<ID:0/082> SetupConnection..
<ID:0/082> Initialzation..
<ID:0/082> Set PIT file..
<ID:0/082> DO NOT TURN OFF TARGET!!
<ID:0/082> Get PIT for mapping..
<ID:0/082> Firmware update start..
<ID:0/082> boot.bin
<ID:0/082> NAND Write Start!!
<ID:0/082>
<ID:0/082> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone share any Success story with these Chinese ones?
BR
---------- Post added at 05:22 PM ---------- Previous post was at 05:11 PM ----------
And no Codes entered via keypad works ???
e.g. *#06#, *#1234#, *#197328640#, *#9090# etc...
Regardless of SIM in tablet on no... Really "LOCKED" huh....
Phone is factory Simfree...
How about that tutorial.... I dont want to RIFF-it if I don't need to.
BR
And I can't extract PIT file from device with Heimdall 1.31running on XP
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
Heimdall is a bit glitchy here, sometimes it flashes some partition, sometimes it does not...
I tried lot's of combinations of BOOT.img KERNEL, FactoryFS, SBL1 etc In between Chinese version 4.0.4. GT-P6200_CHN_P6200ZCLPM_P6200OZHLPM_P6200ZCLPG
And Malaysia version 4.0.4. P6200DXKL3_P6200OLBKK8_XME
The goal was not Chinese 4.0.4. Stock Android but it Faled.
I revived tab with odin and stock firmware I had inside in a first place...
Hex editor claims that .pit extracted from my fully working chinese no google and market firmware IS IDENTICAL to serveral here on forum published ones.
So. Since I DO HAVE RIFF JTAG box I am planning to update bootloader even if it bricks device, but cant find any.
Anyone?
BR
Weird... It look's that won't accept different boot even trough Odin...
P6200_APBOOT_P6200XXLQ7_XXXXXXXXX_REV02_user_low_ship.tar.md5
Do I really have to JTAG fully working phone in order to get Google and Market? Hmpfff....
BR
hi :
heimidal not work for me but mobile odin 1.85 work like of charm an recovery installed .
backup and restore work good
also wipe data and cash
i erase all my files and restore all of themes by recovey
Hi there,
I was trying to flash my Galaxy S i9000 with ROM-ODIN-2.3.6-Gingerbread Offical, but it did not work.
I tried several times but the operation failed .
There is a copy of the logs fromODIN3
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T959VUVKJ6-REV00-home-low-CL694130.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> Sbl.bin
<ID:0/016> NAND Write Start!!
<ID:0/016> cache.rfs
<ID:0/016> factoryfs.rfs
<ID:0/016> modem.bin
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
After that my phone is not turning on and the only thing showed on screen is a exclamation mark between PC and Phone.
Please give me some advice on what should I do now!:crying:
Cheers,
Oscar_Barlop
First off, check that your ROM image is correct -- if you can get an md5sum for what it should be and use a tool like HashTab to check what you have. If that's not the problem...
I would suggest trying the "repartition" option in Odin. You'll need a .pit file to go with that though, so you'll have to try find one. I'm not sure where you got your ROM from, but I know you can get all of that from samfirmware . com (sorry, can't post links; too junior apparently)
davydm said:
First off, check that your ROM image is correct -- if you can get an md5sum for what it should be and use a tool like HashTab to check what you have. If that's not the problem...
I would suggest trying the "repartition" option in Odin. You'll need a .pit file to go with that though, so you'll have to try find one. I'm not sure where you got your ROM from, but I know you can get all of that from samfirmware . com (sorry, can't post links; too junior apparently)
Click to expand...
Click to collapse
Thank you for your reply,I resolved the issue downloading a previous ROM 2.3.3 which worked fine.
I will follow your advise and will verify in the future with hashtab the md5sum verification is correct before going ahead.
One more question, the .pit file is a generic one or it has variations from ROM to ROM?
Regards,
Oscar_barlop
oscar_barlop said:
Thank you for your reply,I resolved the issue downloading a previous ROM 2.3.3 which worked fine.
I will follow your advise and will verify in the future with hashtab the md5sum verification is correct before going ahead.
One more question, the .pit file is a generic one or it has variations from ROM to ROM?
Regards,
Oscar_barlop
Click to expand...
Click to collapse
AFAIK, each .pit file works for one or more ROMs. Again, I'm not 100% knowledgeable here, but it looks (to me) like the .pit file defines partitions for Odin to make on your device before flashing. I used to *always* make sure I had a .pit file to go with my ROM, then I found that I mostly didn't need one. If you're trying to resurrect your phone "from the dead", as it were, it's probably a good idea, but mostly, even though there are a couple of .pit files out there, there seems to be little variance between the ones I've come across. I would typically only use one if I can't seem to get a ROM on without out or if the package I got the ROM in recommended it.
As for your current ROM, I really recommend giving CyanogenMod another go -- it made a world of difference on my i9000 -- speed of device, battery, themes, usability. If you can get Clockwork Recovery on your phone, then it's easy to install. I also recommend checking out DarkyROM as they provide a really nice ROM for the S1 which installs Clockwork Recovery as part of its install process. Indeed, I would say that installing DarkyROM and then CM10 is the path of least resistance for getting CyanogenMod on an S1. Give it a go if you're up for it -- you won't regret it Just bear in mind that your very first boot (DarkyROM and CyanogenMod) may take a few minutes each -- try to be patient and just let the phone do its thing
davydm said:
AFAIK, each .pit file works for one or more ROMs. Again, I'm not 100% knowledgeable here, but it looks (to me) like the .pit file defines partitions for Odin to make on your device before flashing. I used to *always* make sure I had a .pit file to go with my ROM, then I found that I mostly didn't need one. If you're trying to resurrect your phone "from the dead", as it were, it's probably a good idea, but mostly, even though there are a couple of .pit files out there, there seems to be little variance between the ones I've come across. I would typically only use one if I can't seem to get a ROM on without out or if the package I got the ROM in recommended it.
As for your current ROM, I really recommend giving CyanogenMod another go -- it made a world of difference on my i9000 -- speed of device, battery, themes, usability. If you can get Clockwork Recovery on your phone, then it's easy to install. I also recommend checking out DarkyROM as they provide a really nice ROM for the S1 which installs Clockwork Recovery as part of its install process. Indeed, I would say that installing DarkyROM and then CM10 is the path of least resistance for getting CyanogenMod on an S1. Give it a go if you're up for it -- you won't regret it Just bear in mind that your very first boot (DarkyROM and CyanogenMod) may take a few minutes each -- try to be patient and just let the phone do its thing
Click to expand...
Click to collapse
I appreciate your reply and will give it a try next monday, I already have downloaded all the required files and I will let you know the outcome for sure.
Thank you again!!!
davydm said:
AFAIK, each .pit file works for one or more ROMs. Again, I'm not 100% knowledgeable here, but it looks (to me) like the .pit file defines partitions for Odin to make on your device before flashing. I used to *always* make sure I had a .pit file to go with my ROM, then I found that I mostly didn't need one. If you're trying to resurrect your phone "from the dead", as it were, it's probably a good idea, but mostly, even though there are a couple of .pit files out there, there seems to be little variance between the ones I've come across. I would typically only use one if I can't seem to get a ROM on without out or if the package I got the ROM in recommended it.
As for your current ROM, I really recommend giving CyanogenMod another go -- it made a world of difference on my i9000 -- speed of device, battery, themes, usability. If you can get Clockwork Recovery on your phone, then it's easy to install. I also recommend checking out DarkyROM as they provide a really nice ROM for the S1 which installs Clockwork Recovery as part of its install process. Indeed, I would say that installing DarkyROM and then CM10 is the path of least resistance for getting CyanogenMod on an S1. Give it a go if you're up for it -- you won't regret it Just bear in mind that your very first boot (DarkyROM and CyanogenMod) may take a few minutes each -- try to be patient and just let the phone do its thing
Click to expand...
Click to collapse
Hi Davidm,
I have follow your advise and I have installed DarkyRom but I went with CM9, it made a huge difference on my SGS, it is running very smooth and I have noticed as well that the size of the RAM increased as well from 329 to 389MB so there is no more lagging issues.
Thank you once again fro your advise.
Regards,
Oscar_barlop
Ive got a sprint galaxy s5 that was running 5.0 fine. i tried installing a custom rom on it, as i've done before, and i'm stuck on the logo screen. i've read through a lot of stuff on here, and appreciate any feedback i can get. i've seen similar issues, but i was getting philz touch successfully loaded, but it wont boot past samsung logo after i've wiped everyting, in both standard recovery and on custom recovery.
i've now tried going to put a stock 5.0 rom back on in odin, and i'm failing odin. the only thing thats passed lately is putting on philz touch.
blazingoose503 said:
Ive got a sprint galaxy s5 that was running 5.0 fine. i tried installing a custom rom on it, as i've done before, and i'm stuck on the logo screen. i've read through a lot of stuff on here, and appreciate any feedback i can get. i've seen similar issues, but i was getting philz touch successfully loaded, but it wont boot past samsung logo after i've wiped everyting, in both standard recovery and on custom recovery.
i've now tried going to put a stock 5.0 rom back on in odin, and i'm failing odin. the only thing thats passed lately is putting on philz touch.
Click to expand...
Click to collapse
Which custom rom did you try installing? I'm sure you know, but Lollipop can be very temperamental the first time on a custom rom. Also, the first boot can take about 20 minutes the first time.
i was attempting to use MOAR v6.1 oa6
First, thanks for your reply.
so i had a rooted device with running moar initially. it was starting to get really laggy, so i decided to update it, flash this version. well i realized after that i wasn't on lollipop, got stuck in a bootloop then, and through this site, thankfully, was able to recover. then i did an OTA update to 5.0, so that was woriking fine, but now that ive been using my hotspot since i got this phone, im used to it and not having it blows!! so, after lollipop, (i backed up to kies 3 before attempting anything) i tried it again. philz worked fine, i put the super su in my phone's memory, and then went into super su to ignore knox or whatever, and it asked if i wanted to do it manually or normally. i think i did manual. but something didn't go right, i'm sure, and so now i don't even think i'm rooted, therefor need to go to stock, correct?
I'm new on here, well, posting, i use it a lot to figure **** out. like i mentioned earlier, the only thing that my phone will pass in odin is putting philz custom recovery on. it fails everything else, which all i've tried is to put stock 5.0 rom back on there. i will post my bootloader info as well as my odin script in hopes that someone will be able to help this dumbass(myself!) shouldnt have ****d with it after 5.0 was running fine, but it's like quitting a drug, once you root, i at least, don't wanna go back to stock.
i use my phone for work tho, so stock working is better than boot loop. any info/advice is greatly appreciated, i had to go buy a piece of **** prepaid phone just so i can work, and this thing is complete garbage!
my bootloader text
odin mode
product name: sm-g900p
current binary: custom
system status: custom
reactivation lock(kk): off
knox warranty void: 0x1 (2)
qualcomm secureboot: enable (csb)
rp swrev: s1, t2, r1, a2, p1
secure download: enable
udc start
kies was closed every time i've tried doing anyting in odin, fyi
my other question is can i use custom recovery to install a stock rom? prob dumb question, but like i said, i'm fairly new at this and anything helps. i just had no issues the first time i rooted, did a bunch of research, and clearly didn't do enough this time around to get it working properly.
blazingoose503 said:
my other question is can i use custom recovery to install a stock rom? prob dumb question, but like i said, i'm fairly new at this and anything helps. i just had no issues the first time i rooted, did a bunch of research, and clearly didn't do enough this time around to get it working properly.
Click to expand...
Click to collapse
Just so you know, if you quote the person, he'll get a flag. I didn't notice your post again until just now. IMO, your best bet is to follow the complete instructions from my post #2 It's important to follow it carefully, in your case, thread your phone like it was on Kitkat and don't take any corner. If you need help during that process, post in the Q&A that my link is in. To answer your question on this post, you can't use custom recovery for stock rom, you use Odin. All links to files needed are there too.
so im a little confused
Ramer said:
Just so you know, if you quote the person, he'll get a flag. I didn't notice your post again until just now. IMO, your best bet is to follow the complete instructions from my post #2 It's important to follow it carefully, in your case, thread your phone like it was on Kitkat and don't take any corner. If you need help during that process, post in the Q&A that my link is in. To answer your question on this post, you can't use custom recovery for stock rom, you use Odin. All links to files needed are there too.
Click to expand...
Click to collapse
are you telling me to put moar on, or flash a stock rom? and kitkat install should work even tho last time phone was working it was running 5.0?
im sorry im sure i sound retarded im just sort of at a loss, confused, and dont want to further damage my phone and make it unusable. so dont feel bad and you can explain to me as if i were a complete noob... i will donate for your help as well, id just really like to fix my phone. was gonna take it to a sprint store and have a tech look, but i know knox is tripped and theyll prob tell me to kick rocks
another thing
my phone wont get past samsung boot screen so i cant do anything on my phone itself, ive gotta do it all externally... im not worried about losing all data, i can get my stuff from other sources, so a fresh start isnt an issue for me
blazingoose503 said:
are you telling me to put moar on, or flash a stock rom? and kitkat install should work even tho last time phone was working it was running 5.0?
im sorry im sure i sound retarded im just sort of at a loss, confused, and dont want to further damage my phone and make it unusable. so dont feel bad and you can explain to me as if i were a complete noob... i will donate for your help as well, id just really like to fix my phone. was gonna take it to a sprint store and have a tech look, but i know knox is tripped and theyll prob tell me to kick rocks
Click to expand...
Click to collapse
The great thing about our phones is it's nearly impossible to truly brick it. As far as MOAR, of course I'm biased, but I'd highly recommend it. Because I can't really say for sure what state your phone is in. If you follow the instructions in the post I linked earlier, click on the "Click to Show Content" below the big red note and follow those instructions, I bet we can get you back on MOAR with Lollipop. Even though those instructions are written for someone who has never been on Lollipop they will still work, just takes longer to go through all the steps. Read it through a couple of times, download everything you'll need in advance and I bet you'll get up and running. If you run into any problem, PM me and I'll try to help.
really appreciate the help
Ramer said:
The great thing about our phones is it's nearly impossible to truly brick it. As far as MOAR, of course I'm biased, but I'd highly recommend it. Because I can't really say for sure what state your phone is in. If you follow the instructions in the post I linked earlier, click on the "Click to Show Content" below the big red note and follow those instructions, I bet we can get you back on MOAR with Lollipop. Even though those instructions are written for someone who has never been on Lollipop they will still work, just takes longer to go through all the steps. Read it through a couple of times, download everything you'll need in advance and I bet you'll get up and running. If you run into any problem, PM me and I'll try to help.
Click to expand...
Click to collapse
I'm getting all the files now, just deleted all i had got before and am starting with new downloads from #2, your instructions. do i have to do anything with super su and root before i can install MOAR? and there was no question of which rom to use, i just wasn't sure if your instructions for me were to get moar or stock, but i'm understanding now that i'm going to stock 5.0 then to moar, correct? does it matter which build of moar i use, i'm getting 6.2 as i figured the newer the better. if not let me know. i put money in my account so i can truly appreciate you help and i obviously cant do the steps where i back anything up in my phone, since it wont turn all the way on, so i'm hoping all of this will work without those steps as well. Like i wont be able to go and delete the android file. i hope that's not a deal breaker... i could just pull my sd card, or is that a bad idea? these are the things i'm worried about, but i guess i will learn one way or another!!
gonna throw another 10 your way
just really wanna figure this out, and i cant stress enough how thankful i am. if i had more money i'd be giving it to you, thanks dude!!
blazingoose503 said:
I'm getting all the files now, just deleted all i had got before and am starting with new downloads from #2, your instructions. do i have to do anything with super su and root before i can install MOAR? and there was no question of which rom to use, i just wasn't sure if your instructions for me were to get moar or stock, but i'm understanding now that i'm going to stock 5.0 then to moar, correct? does it matter which build of moar i use, i'm getting 6.2 as i figured the newer the better. if not let me know. i put money in my account so i can truly appreciate you help and i obviously cant do the steps where i back anything up in my phone, since it wont turn all the way on, so i'm hoping all of this will work without those steps as well. Like i wont be able to go and delete the android file. i hope that's not a deal breaker... i could just pull my sd card, or is that a bad idea? these are the things i'm worried about, but i guess i will learn one way or another!!
Click to expand...
Click to collapse
1. Don't need to do anything with SuperSu or root. MOAR is pre-rooted.
2. Yes, go to stock then MOAR. Make sure to set up your google and samsung accounts in stock rom per instructions.
3. You are correct, install the latest which is MOAR 6.2. Don't worry about it now, but once you're up and running, read through the FAQ. There's another update which is called New Stuff mods. Also, down the road you'll enjoy a theme for MOAR.
4. Correct, you can't backup your phone since you're in a bootloop now, so skip.
5. Do you have a card reader on your PC? If so, pull your SD card out now, delete the android folder and you'll need to copy the MOAR rom to your card to flash when you reach that step. If that's not possible you'll have to go through a more difficult route of copying the MOAR rom from your PC to your internal SD while you're in the stock rom. Keep in mind, while your in stock rom, you're not rooted, which is why you just want to get the initial sign-in done before doing a battery pull.
6. The android file on your SD may not be important anyway, since I believe you were on Lollipop at some point. It was just an issue for people going from Kitkat to Lollipop for the first time.
Good luck, I'll be around for the next two hours if you need more help, but if you're getting started now, you should be up and running in less than two hours. Just remember, the first boot in stock and in MOAR can take about 20 minutes, so be a bit patient.
---------- Post added at 07:19 PM ---------- Previous post was at 07:06 PM ----------
blazingoose503 said:
just really wanna figure this out, and i cant stress enough how thankful i am. if i had more money i'd be giving it to you, thanks dude!!
Click to expand...
Click to collapse
I'm always happy to help (well, almost always). I saw your edit, you don't have to un-check auto-reboot after odin'ing stock. Just where it's mentioned.
after putting moar zip on my sd, via computer...
Ramer said:
1. Don't need to do anything with SuperSu or root. MOAR is pre-rooted.
2. Yes, go to stock then MOAR. Make sure to set up your google and samsung accounts in stock rom per instructions.
3. You are correct, install the latest which is MOAR 6.2. Don't worry about it now, but once you're up and running, read through the FAQ. There's another update which is called New Stuff mods. Also, down the road you'll enjoy a theme for MOAR.
4. Correct, you can't backup your phone since you're in a bootloop now, so skip.
5. Do you have a card reader on your PC? If so, pull your SD card out now, delete the android folder and you'll need to copy the MOAR rom to your card to flash when you reach that step. If that's not possible you'll have to go through a more difficult route of copying the MOAR rom from your PC to your internal SD while you're in the stock rom. Keep in mind, while your in stock rom, you're not rooted, which is why you just want to get the initial sign-in done before doing a battery pull.
6. The android file on your SD may not be important anyway, since I believe you were on Lollipop at some point. It was just an issue for people going from Kitkat to Lollipop for the first time.
Good luck, I'll be around for the next two hours if you need more help, but if you're getting started now, you should be up and running in less than two hours. Just remember, the first boot in stock and in MOAR can take about 20 minutes, so be a bit patient.
---------- Post added at 07:19 PM ---------- Previous post was at 07:06 PM ----------
I'm always happy to help (well, almost always). I saw your edit, you don't have to un-check auto-reboot after odin'ing stock. Just where it's mentioned.
Click to expand...
Click to collapse
it said that i needed to insert the last disk of the multi-volume set and click ok to continue? i put the unzipped folder onto my sd card, that's how i'm supposed to do it right? i'm gonna try, hoping that message doesn't mean anything. and sorry to blow you up bro, i'm just stoked on getting my phone back, running MOAR, baby:silly:
lastly...
blazingoose503 said:
it said that i needed to insert the last disk of the multi-volume set and click ok to continue? i put the unzipped folder onto my sd card, that's how i'm supposed to do it right? i'm gonna try, hoping that message doesn't mean anything. and sorry to blow you up bro, i'm just stoked on getting my phone back, running MOAR, baby:silly:
Click to expand...
Click to collapse
do i put philz on before i odin to stock, i think step 3 is to wipe everything, and im on stock recovery, so do i odin philz, then wipe, then stock, then install moar from my sd card once i'm ready for that step? sorry again dude. i know you're trying your best, and unfortunately, so am i!! told you i'm (as you guys kindly refer to us as) a new user
blazingoose503 said:
do i put philz on before i odin to stock, i think step 3 is to wipe everything, and im on stock recovery, so do i odin philz, then wipe, then stock, then install moar from my sd card once i'm ready for that step? sorry again dude. i know you're trying your best, and unfortunately, so am i!! told you i'm (as you guys kindly refer to us as) a new user
Click to expand...
Click to collapse
You can odin Philz after you set up the stock rom. It sounds like your very familiar with Philz, I haven't used that for a long time. I think I read somewhere that he was retiring, so I've stayed with TWRP. But for now, use what you're comfortable with.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
blazingoose503 said:
it said that i needed to insert the last disk of the multi-volume set and click ok to continue? i put the unzipped folder onto my sd card, that's how i'm supposed to do it right? i'm gonna try, hoping that message doesn't mean anything. and sorry to blow you up bro, i'm just stoked on getting my phone back, running MOAR, baby:silly:
Click to expand...
Click to collapse
Whoa, stop there. Don't unzip MOAR, just copy it to your phone. Philz or TWRP, when you install a rom takes care of that.
this is what odin says when i try to go stock
using the dl from your tutorial
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_G900PVPU1BOA6_G900PSPT1BOA6_CL3859396_QB3804569_REV00_user_low_ship_MULTI_CERT.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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
using odin 3.07
cuz that's what it said it was tested on somewhere in my reading. so i got that one, put the file in the pda box in odin, and it won't pass, just like my initial post!!
my bad, i didn't unzip
Ramer said:
You can odin Philz after you set up the stock rom. It sounds like your very familiar with Philz, I haven't used that for a long time. I think I read somewhere that he was retiring, so I've stayed with TWRP. But for now, use what you're comfortable with.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
Whoa, stop there. Don't unzip MOAR, just copy it to your phone. Philz or TWRP, when you install a rom takes care of that.
Click to expand...
Click to collapse
i put the zipped file onto sd card, dunno why i put that. i left it in zip format. my apologies. still can't odin stock rom tho...
blazingoose503 said:
using the dl from your tutorial
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_G900PVPU1BOA6_G900PSPT1BOA6_CL3859396_QB3804569_REV00_user_low_ship_MULTI_CERT.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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You didn't download the stock that I linked to. Hold on a few minutes and let me find it...
i got it from the install instructions page
Ramer said:
You didn't download the stock that I linked to. Hold on a few minutes and let me find it...
Click to expand...
Click to collapse
but thank you, ill re dl from you. thanks again
Hi everyone,
Firstly, I'm sorry if this is posted in the wrong area but I'm in a state of despair at the moment!
Basically, I was manually backing up my girlfriend's phone to my PC (backing up pictures) - naturally clicking the folders to backup, ctrl+c and then ctrl+v in the relevant folder on my PC and voila. Backup done. Except, it didnt copy all of the files and now my girlfriend has deleted in excess of 400 pictures, most of which of our 6 month old baby that we desperately want back.
I have seen many ways to do this but all seem to need root access - I have tried rooting using many different unikernels (excuse my ignorance, this is the first time I've tried rooting a device!) but none seem to work...
Useful info: Android version: 5.1.1 (out of the box), model number: SM-G920F, Build number: LMY47X.G920FXXU3QOKN.
Any help or advice at all is greatly appreciated and I will forever be in your debt if you can successfully help get my files back. And I'm willing to purchase any payware needed!
EDIT: I have tried: Kingo Root, iRoot, One-click-root, Root Genius, Coolmusters recovery tool, wondershare's recovery tool... essentially all of the first 2 or 3 pages of any Google search remotely related to this.
Download odin 3.7 for windows. And google CF auto root instructions for your device and firmware.
So the links ensure you use the right CF auto root
That should work.
You shouldn't be finding it hard to root whilst on
Lollipop! !
kush2.0 said:
Download odin 3.7 for windows. And google CF auto root instructions for your device and firmware.
So the links ensure you use the right CF auto root
That should work.
You shouldn't be finding it hard to root whilst on
Lollipop! !
Click to expand...
Click to collapse
Thanks! Looks like DiskDigger (Free app on Play store) has recovered all my files and then some... Currently verifying this...
EDIT: DiskDigger recovered files but without being rooted, it only recovered low-res images. I'm still trying to figure out how to root this thing! Why so hard?!
So I've been following this, and all other tuts that I can find, www [dot] ndroidrootz [dot] com/2015/05/how-to-unroot-galaxy-s6-and-s6-edge.html
The phone is bricked and will only go between 2 screens. Download Mode and a screen that shows "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software" - but this fails too!
Any way of fixing my girlfriends S6? I just keep getting FAIL in ODIN!
lemons55 said:
So I've been following this, and all other tuts that I can find, www [dot] ndroidrootz [dot] com/2015/05/how-to-unroot-galaxy-s6-and-s6-edge.html
The phone is bricked and will only go between 2 screens. Download Mode and a screen that shows "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software" - but this fails too!
Any way of fixing my girlfriends S6? I just keep getting FAIL in ODIN!
Click to expand...
Click to collapse
the smart switch option is a nice way to clean up everything and try again, i know that sounds strange but even the usb cable can make the difference (hope u r using the original one) and odin 3.10 i think should help a bit with all these fail attempt..
in case via smart switch reinstall the drivers and.. let me know if it helped somehow
ps: sorry for bad english
lemons55 said:
So I've been following this, and all other tuts that I can find, www [dot] ndroidrootz [dot] com/2015/05/how-to-unroot-galaxy-s6-and-s6-edge.html
The phone is bricked and will only go between 2 screens. Download Mode and a screen that shows "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software" - but this fails too!
Any way of fixing my girlfriends S6? I just keep getting FAIL in ODIN!
Click to expand...
Click to collapse
Jesus christ, what an old guide, no wonder you've ruined it in your desperation.
First, You need a newer version of Odin. (3.10.7)
http://forum.xda-developers.com/attachment.php?attachmentid=3446301&d=1440131361
Then your best bet is to find the exact firmware you were on prior to this mess to have the best chance of keeping your original files in tact if you haven't completely trashed them by now.
Not sure what region / provider your phone is from. Does this look correct?
The link you gave was linking to older versions of android then what you were on to start with.
http://samsung-updates.com/details/58161/Galaxy_S6/SM-G920F/VDI/G920FXXU3QOKN.html
If so download it and flash via odin making sure "nand erase" or "repartition" is not selected!
Hopefully that will get the phone running again.
Then Flash TWRP recovery via odin
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/arter97-recovery-g920fi-13.0-twrp_3.0.0-0.tar.md5
Finally, reboot into recovery and install supersu to get root.
http://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
self_slaughter said:
Jesus christ, what an old guide, no wonder you've ruined it in your desperation.
First, You need a newer version of Odin. (3.10.7)
http://forum.xda-developers.com/attachment.php?attachmentid=3446301&d=1440131361
Then your best bet is to find the exact firmware you were on prior to this mess to have the best chance of keeping your original files in tact if you haven't completely trashed them by now.
Not sure what region / provider your phone is from. Does this look correct?
The link you gave was linking to older versions of android then what you were on to start with.
http://samsung-updates.com/details/58161/Galaxy_S6/SM-G920F/VDI/G920FXXU3QOKN.html
If so download it and flash via odin making sure "nand erase" or "repartition" is not selected!
Hopefully that will get the phone running again.
Then Flash TWRP recovery via odin
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/arter97-recovery-g920fi-13.0-twrp_3.0.0-0.tar.md5
Finally, reboot into recovery and install supersu to get root.
http://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
Click to expand...
Click to collapse
Thanks man! Unfortunately, flashing the stock firmware using the link you provided above (I even paid for a faster download!) didn't work, got about 30% through then failed. I've PM'd you with the log but anyone else who can help, see it here below:
<ID:0/004> Added!!
<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/004> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Odin 3.10.6 seems to work when others fail try that one bud.
Jimmy1life said:
Odin 3.10.6 seems to work when others fail try that one bud.
Click to expand...
Click to collapse
Thanks mate, tried that and it just fails as with all other attempts. Went a bought a new S6 (£400 later!) and that seems to be the end of it :/ Thanks to all for your advice though! I'll keep trying with the bricked S6!