Related
I messed up my phone trying http://forum.xda-developers.com/showthread.php?t=892297 I can't figure out how to get the phone into recovery now that it just goes to black screen after it boots. I can't turn on debugging mode, and I've tried all the button combination's I could find to boot in recovery.
It is a little tricky but with the phone powered off push and hold the volume up and volume down button at the same time while you push and hold the power button. Keep holding the whole volume button in until it gets into recovery. You will see the splash screen then recovery should come up.
holy hell thank you so much... now how to restore this thing... hmmm
How do I get ADB now?
Can I start ADB while in recovery?
You shouldn't even be in recovery seeing as how there is no recovery yet.
Sent from my SGH-T959V using XDA App
What do you mean.. I'm staring at it now.. appears legit as well:
Android system recovery <3e>
Samsung Recovery Utils
-for BML-
etc...
that's stock recovery. there is no modded recovery to allow backup/restore/rom flashing.
You will need to ODIN if your phone is hosed.
Stock recovery? No, adb pretty much won't work in that.
Sent from my SGH-T959V using XDA App
krylon360 said:
that's stock recovery. there is no modded recovery to allow backup/restore/rom flashing.
You will need to ODIN if your phone is hosed.
Click to expand...
Click to collapse
How exactly do I ODIN.. because its hosed...
aloneinshadow said:
Stock recovery? No, adb pretty much won't work in that.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I got ADB to work.. however it doesn't allow root.. so pretty much pointless. It was really odd though ADB would work on and off, if it didn't work I would reboot into recovery and try again and it would work, if I rebooted back into recovery it wouldn't work until I rebooted back into recovery again.
adb reboot download
grab ODIN 1.7
flash the tar located here
http://forum.xda-developers.com/showthread.php?t=978836
the tar needs to go in PDA. DO NOT check any boxes that aren't already checked.
Do Not use a PIT
krylon360 said:
adb reboot download
grab ODIN 1.7
flash the tar located here
http://forum.xda-developers.com/showthread.php?t=978836
the tar needs to go in PDA. DO NOT check any boxes that aren't already checked.
Do Not use a PIT
Click to expand...
Click to collapse
Just to confirm I need ADB reboot download, ODIN 1.7, and [ROM-ODIN]T959VUVKB5 Stock + Root? I'm very new to this sorry, just switched over from an iPhone and learning very quickly Android modding is a lot more dangerous then iOS. Also maybe is there a guide for doing this? I really don't want to mess anything up.
Sario27 said:
Just to confirm I need ADB reboot download, ODIN 1.7, and [ROM-ODIN]T959VUVKB5 Stock + Root? I'm very new to this sorry, just switched over from an iPhone and learning very quickly Android modding is a lot more dangerous then iOS.
Click to expand...
Click to collapse
you are correct.
krylon360 said:
you are correct.
Click to expand...
Click to collapse
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> factoryfs.rfs
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What am I doing wrong?
Sario27 said:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> factoryfs.rfs
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What am I doing wrong?
Click to expand...
Click to collapse
keep trying. ODIN sucks like that.
Thanks everyone! It is now working and I still have root!
Thanks for all your help everyone especially krylon360 for the fixing advice.
New to Android, so please forgive a question that may be obvious to those more experienced.
On entering the recovery console, there are four options:
reboot system
reinstall packages
delete all user data
delete cache data
While the first is pretty clear, the others aren't so much. Any greater clarity would be helpful, as well as how these options differ from the user-land
Settings > Privacy > Factory data reset
which, I assume, returns everything except the SD card to as-shipped configuration, yes? I'm also guessing that there are things like usage counters that aren't reset either, yes?
One of the things I want to do before I go hog-wild with new firmware is to at least get a good tar of the stock configuration.
TIA
I guess it depends on what you did to your system. if you messed it up and want to get back to a clean stock system, follow krylon360 post top of this second page. get the tar file and odin 1.7 (that's the one that is working mostly for everyone) Shut down your phone. pull the battery out. connect your tether cable to the phone and USB to computer. start oden put tar file in PDA box. don't change any other settings. Put your phone in download mode by pressing both up/down volume buttons and insert the battery. once in download mode, click on Start on oden. wait for it to finish and the phone will reboot when successfull tranfer is complete. give the phone time to boot up and you should be good. note: you need to make sure that the samsung USB drivers are installed in your computer properly for this to work. ( I assume they are if you got this far) Good Luck.
nwpro3 said:
I guess it depends on what you did to your system. if you messed it up and want to get back to a clean stock system, follow krylon360 post top of this second page. get the tar file and odin 1.7 (that's the one that is working mostly for everyone) Shut down your phone. pull the battery out. connect your tether cable to the phone and USB to computer. start oden put tar file in PDA box. don't change any other settings. Put your phone in download mode by pressing both up/down volume buttons and insert the battery. once in download mode, click on Start on oden. wait for it to finish and the phone will reboot when successfull tranfer is complete. give the phone time to boot up and you should be good.
Click to expand...
Click to collapse
you'll also have better results if you remove your SD and sim as well.
Well Crap
After reading a lot of the post on this forum, it is clear that I'm an idiot. Since I seem to be the only one who screwed this up. I installed Gingerbread on my Galaxy S 4g. I was successful in that endeavour. However, I went looking for a root and screwed that up. Now my phone just says, "firmware upgrade fail! Try using recovery mode." The problem is that I can't get into recovery mode the same way anymore. I can't get into download mode either. Can anyone offer any help.
Hi you all guys, few days ago i purshaced an skyrocket sgh i727 and it was working perfect, then when i was using the
internet browser my phone ramdomly turn off, i just powered on but it never boot up so i decide to boot it up on clockwork
mode and restore to factory data after that the phone did no boot anymore neither in clockwork mode, when i try to power it
on it shows the samsung splash but stuck there, the phone can be put on download mode which is a good signal however when i
try to install a stock rom from odin this does no start, it keep saying initializing step, i though my battery was
discharged and i tried the battery in a friend's phone but the battery was full charged, so i discarded that was a battery
issue, i installed the lastest kies driver, i got differents odin version, downloaded few times differents stock rom version and re tried to intalled; but odin keep sticking on initializing step, tried differents batteries (full charged), differents usb cables, differents computers, but its seems the phone is completely bricked i tried almost everything also i found that kies can make an emergency restore but when i try to do it, kies request me the error code to proceed, but i dont have such code since my phone never give me an error on installing, it just doest start the restore with odin, when i plug my phone its recognized from odin and shows as added, can you suggest me something? im tired of trying all what i described above and the phone does no have warranty since i purshaced it on ebay and the seller doesnt no accepted to be responsible since the phone worked when he sold it, i cant find any place to purshace a main board but before to purshace one i think there will be posibility to fix it since its still easy to power it on download mode without the JTAG, i cant get it on clockwork mode anymore http://forum.xda-developers.com/images/smilies/crying.gif
First off, I can't really make complete heads or tails of your problem. Please use sentences and paragraphs.
Second, is Odin recognizing your phone when you plug it in? Read the ODIN sticky.
Third, how long is your phone "stuck" on the Sammy splash for? You're definitely booting into CWM recovery and not factory recovery, right?
Honestly, if your phone turns on, it's not hard-bricked and it can be saved. There are lots of stickies here that walk you through how to root/unroot, restore to stock, use ODIN, etc. Read through those and that'll give you your best shot at finding an answer.
response
Hi im sorry if i writed it with sentences and paragraphs, well actually odin does recognized the phone and shows as added, but when i start the restore the phone keep in download mode and odin just stuck in the step that says initializing.
I used another battery, another usb cable and other computer but odin keep sticking in that step.
I tried downloading differents odin versions and differents stock rom version from differents sites but i can see its not a corrupt download.
the phone had CWM but in the time i made a factory reset from the CWM the phone did no boot anymore on CWM neither the OS because it stuck on the Samsung splash, this splash stuck permanently maybe hours if i dont remove the battery.
I think im booting on CWM im not sure because (it does no appear the menu to install zips make factory reset, clear cache partition etc)
Kies recognize my phone also but unable me to make an emergency restore until i put the error code in the box that pop up (i dont have such error code since my phone does no give me any error the process just doesnt start)
i tried killing kies in the task manager because i read sometimes kies intefere with oding while restoring, i can make put the phone in download mode as i said but im not able to make the restore because ODIN Stuck on INITIALIZING MODE.
I read some forums and post before i post but i havent found nobody with the same issue i just found this http://forum.xda-developers.com/showthread.php?t=1240333 but this didnt work for me
jakeharriss said:
I think im booting on CWM im not sure
Click to expand...
Click to collapse
In fairness, at least you're not out flashing ROMs and saying this.
How are you trying to boot into recovery? Are you holding both volume buttons and the power button down, and keeping them down until the Sammy splash comes up? Or are you just using the power button? If you're just pressing power, you're trying to boot a phone that has no ROM, and you'll have the same result every time.
Second, are you positive you're using the right version of Odin? v1.85?
Third, when you plug your phone into the computer and Odin, does the screen look like the screenshot in the OP of this thread?
http://forum.xda-developers.com/showthread.php?t=1773659
I'll be really honest, this screams of user error, and that's really the only explanation I can think of--especially because the phone can apparently still be forced into download mode. Maybe someone more experienced has seen this happen before and can help more than I can, but from the panicked style of posting and your asking questions about whether it's booting into recovery or not, I have to assume that it's user error. We just have to figure out what that error was.
thanks for your answer to my post i apreciate you all your time, well actually i use the both odin version the Odin v1.85 and the odin v3.04 also the odin rom installer (i mean the odin package that you just need to plug the phone and then press start to update it) yes i hold the both volume button + the power button and i release it when the samsung splash comes up but now it does no give me the CWM since i used it to factory reset the phone and i think neither the factory recovery menu, however i can hold the volume down + plug the phone and then start it on download mode by presing the volume up button.
When i turn the phone in download mode, the phone appear in my odin as added like in the screenshot you sent me, then i select in the pda checkbox, then i choose the stock rom from my desktop, i leave the other checkbox selected like when oddin start ( i mean selected the options on auto reboot and F. Reset Time) then i press start, odin verify the rom and when it follow to the next step, odin stuck on initializing procees but my phone stays on download mode and do not pop any error neither the odin, as i said i dont think is a corrupt rom because i downloaded different isc version isc 4.04 and isc 4.03 also android froyo 2.3.5 but nothing works also i used different computers and usb cables and tried with a friend battery full charged maybe i dont have the OS in my phone as you say but my question is how to reinstall it if oddin doesnt seems to work on my phone also i have a galaxy s3 and i installed the jelly bean without a problem in the same computer with the same odin and cable usb
jakeharriss said:
thanks for your answer to my post i apreciate you all your time, well actually i use the both odin version the Odin v1.85 and the odin v3.04 also the odin rom installer (i mean the odin package that you just need to plug the phone and then press start to update it) yes i hold the both volume button + the power button and i release it when the samsung splash comes up but now it does no give me the CWM since i used it to factory reset the phone and i think neither the factory recovery menu, however i can hold the volume down + plug the phone and then start it on download mode by presing the volume up button.
When i turn the phone in download mode, the phone appear in my odin as added like in the screenshot you sent me, then i select in the pda checkbox, then i choose the stock rom from my desktop, i leave the other checkbox selected like when oddin start ( i mean selected the options on auto reboot and F. Reset Time) then i press start, odin verify the rom and when it follow to the next step, odin stuck on initializing procees but my phone stays on download mode and do not pop any error neither the odin, as i said i dont think is a corrupt rom because i downloaded different isc version isc 4.04 and isc 4.03 also android froyo 2.3.5 but nothing works also i used different computers and usb cables and tried with a friend battery full charged maybe i dont have the OS in my phone as you say but my question is how to reinstall it if oddin doesnt seems to work on my phone also i have a galaxy s3 and i installed the jelly bean without a problem in the same computer with the same odin and cable usb
Click to expand...
Click to collapse
read this, its a sticky for newbs, follow it to the t, read the the whole post 3x b4 you proceed http://forum.xda-developers.com/showthread.php?t=1652398, if that doesnt work, either user error or hardware problem with nand
Make sure in Odin Only the reset time and reboot boxes are checked. Don't re partition.
Hmm... Well I occasionally have your initial problem, where my phone randomly turns off. Here, it doesnt boot right away, but I have to remove all power sources (battery, cable), put the battery back in, then it turns on fine, no questions asked.
What ROM were you using at the time? My phone started doing this after I installed the Liquid Beta 2Jellybean Rom. If you were using that at the time, it may have just been a ROM issue. Hope I helped...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Brick LOGS PIT
Hi, well actually i was running the stock rom 2.3.5 GINGERBREAD, that was the rom that came with my phone, i tried the step to enter my skyrocket in recovery mode but im not able to do it, the odin keep sticking on initializing i have tried the steps you gave me, is there a way i can get an error code to try the emergency restore from kies? because i dont know where to get an error code,
i tried to re flash the CWM but odin also stick on initializing
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
and this is the log when i disconnect the phone from my computer
\<ID:0/007> Added!!
<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>
<ID:0/007> Get PIT for mapping..
<ID:0/007> Removed!!
<ID:0/007> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
i have reading a post about PIT
PIT – the PIT file refers as ‘Partition Information Table’. This is only useful for fixing bricked devices if somehow something changed with the partition table layout of the phone’s system memory. But in normal flashing, you should not use this file, or you may screw up your phone if handed carelessly.
does anyone have any idea how can i remap my partition in my phone or if it nessesary?
also here i leave the log when i try to make a restore with odin to an stock rom
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727UCLF6_I727ATTLF6_I727UCLF6_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.. (in this step my phone stuck while trying to install and never advance)
when i unplug this is what appear
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727UCLF6_I727ATTLF6_I727UCLF6_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>
<ID:0/007> Get PIT for mapping..
<ID:0/007> Removed!!
<ID:0/007> There is no PIT partition. (It keep saying i dont have a PIT partition)
<OSM> All threads completed. (succeed 0 / failed 1)
do you all guys have any idea what is going wrong? i tried to turn in restore mode following this steps
ENTERING IN TO RECOVERY MODE IS THE SAME METHOD FOR BOTH STOCK AND A CUSTOM RECOVERY (CWM)
Now turn off your phone, unplugged(might work plugged in)
Press and keep both volume keys down
Then press the power button while still holding down the volume keys
When you feel the phone vibrate or see a logo on the screen, release the power button but not the volume keys.
When screen goes black release the volume keys.
Wait a few seconds to boot in to recovery
You are now in recovery mode
But when i release the power but and keep holding the volume button my screen keep stuck in the samsung splash even when i release the volume butto + the power button after the splash comes up
I appreciate your time and im sorry if i dont write in paragraph senteces etc i just tried to explain my issue as it was posible for me thanks
i think your problem was this "odin v3.04 also the odin rom installer", never heard of the odin rom installer used for our phones, you could of fracked up the partitions, but i dont know the fix for that, if there is even a way to fix it
edit: nvm, i read that it was a prob b4 you tried that, then its a bad nand, there might be a way to push a recovery back onto the phone using adb, just cant find the post on how
here it is, it will get you started, you need to learn how to use adb http://forum.xda-developers.com/showpost.php?p=31172875&postcount=19
Can you explain me what does NAND mean please, well when i mean odin installer i mean a comprimed package of odin that comes with the rom but you dont need to download the rom separately because this package include exerything its the same like the other odin but instead of use the PDA box you just plug the phone and once is added, you just press start and this does everything, the only thing that looks weird for me is that the phone can be put on download mode without any problem, and you said that if the phone can be put in download mode without j tag this mean its not breaked, do you have any information about if if i can make a re partition in my phone and resolve the PIT issue that odin says?
jakeharriss said:
Can you explain me what does NAND mean please, well when i mean odin installer i mean a comprimed package of odin that comes with the rom but you dont need to download the rom separately because this package include exerything its the same like the other odin but instead of use the PDA box you just plug the phone and once is added, you just press start and this does everything, the only thing that looks weird for me is that the phone can be put on download mode without any problem, and you said that if the phone can be put in download mode without j tag this mean its not breaked, do you have any information about if if i can make a re partition in my phone and resolve the PIT issue that odin says?
Click to expand...
Click to collapse
The thing you are taking about is an Odin one click.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Yes, this is absolutely what im trying to say but i didnt know how to say it, tried to flash a leaked 4.04 isc, that previously worked perfect for 3 skyrockets i had and i updated them without a problem, the matter was i never meant to update this phone but i had to try it due in that moment the phone ramdomly turned off and it did no allow me to boot up my OS, so i got into CWM and press factory reset and then i reset the phone but it never boot up back it just keep sticking in the samsung splash, then i tried to go back to the CWM again but now i couldnt do it again, so i tried to install the rom leaked 4.0.4 with odin one click but it never passed, just stuck in the intializing step, then i tried to use the odin 1.85 and downloading an stock rom and putting in the box PDA, but also kept in sticking in the Intializing step never transfered anything to my phone my phone was always in download mode and never gave me an error, i did tried the odin 3.04 that i used to flash the rom in my galaxy s3 i9300 but also kept with the same issue, im not sure if it hard bricked because i can get into the download mode easily, but im unable to get in the recovery mode following the right steps, im thinking is a PIT issue here i found this threat for another model
http://forum.xda-developers.com/showthread.php?t=1760107
this guy explain he had his phone hard bricked and flashed a PIT file to his phone and could restore it back
Do any of you all guys have ever flashed a pit file or have any idea about what is happening to my phone?
jakeharriss said:
Yes, this is absolutely what im trying to say but i didnt know how to say it, tried to flash a leaked 4.04 isc, that previously worked perfect for 3 skyrockets i had and i updated them without a problem, the matter was i never meant to update this phone but i had to try it due in that moment the phone ramdomly turned off and it did no allow me to boot up my OS, so i got into CWM and press factory reset and then i reset the phone but it never boot up back it just keep sticking in the samsung splash, then i tried to go back to the CWM again but now i couldnt do it again, so i tried to install the rom leaked 4.0.4 with odin one click but it never passed, just stuck in the intializing step, then i tried to use the odin 1.85 and downloading an stock rom and putting in the box PDA, but also kept in sticking in the Intializing step never transfered anything to my phone my phone was always in download mode and never gave me an error, i did tried the odin 3.04 that i used to flash the rom in my galaxy s3 i9300 but also kept with the same issue, im not sure if it hard bricked because i can get into the download mode easily, but im unable to get in the recovery mode following the right steps, im thinking is a PIT issue here i found this threat for another model
http://forum.xda-developers.com/showthread.php?t=1760107
this guy explain he had his phone hard bricked and flashed a PIT file to his phone and could restore it back
Do any of you all guys have ever flashed a pit file or have any idea about what is happening to my phone?
Click to expand...
Click to collapse
We don't have a pit file for the skyrocket. At least as far as i know. You should be able to flash the stock firmware if you can get into dl mode. Use Odin 1.85 and follow vincoms guide
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Yes so do i think the same, however for any extrange reason everytime i put my phone in download mode my phone stick in this step
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727UCLF6_I727ATTLF6_I727UCLF6_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.. (in this step my phone stuck while trying to install and never advance)
i tried using differents odin version, differents stock roms, different usb cables, differents usb ports and computers, also reinstalled the right drivers for my phone and i verified it in the device manager from my computer, so i can say the issue is in the phone
i tried to reinstall the CWM but it also keep on the initializing step so if this dont pass there is no way to get in CWM and neither to the factory recovery mode, as i said everytime i try to get in factory recovery mode i cant due my phone stuck in the samsung splash and never goes black as it should to say that now is on factory recovery mode.
Install kies, Run odin as administrator, use sammobile stock firmware.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
Install kies, Run odin as administrator, use sammobile stock firmware.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I did it but keep sticking in download mode with the odin in initializing step even my kies download the emergency restore firmware and it stuck while trying to install is there a way a can make a dual boot without the cwm or factory recovery working?
I am having the exact same problem and have done just about all the same steps you outlined before I came across this thread. What was the final resolution for getting past the "Initialization.." phase in Odin?
UBetchYa said:
I am having the exact same problem and have done just about all the same steps you outlined before I came across this thread. What was the final resolution for getting past the "Initialization.." phase in Odin?
Click to expand...
Click to collapse
Hi well i tried the whole method i could but i realized that would be quicker buying a new motherboard for the phone i got it on 50 usd on ebay it was a look that a guy tried to change his broken screen but he couldnt and decided to put his phone on auction i won and i repaired my phone however i send the mainboard to a friend of mine and he said the he couldnt repair it, i talked with a guy that said he could create the partition map again but i couldnt understand him maybe you can talk to him but he explained me that what killed my phone was to put a leaked firmware and make a wiping on the partition from the restore mode http://forum.xda-developers.com/member.php?u=3597010 this is the guy just send him a message wish you good luck with that
Hello guys,
so usually i get my stuff to work again if i was the one who broke it... But today is the day i have to admit i'm lost. never wrote a thread before but now it's the time.
So i was about to install the Carhd rom for my s6. After i forgot to do a factory reset before installing i got a really messed up system with my apps and stuff but the new rom. But it was really unstable. So i went back in recovery mode and did a wipe.. unfortunately i forgot that this will wipe the rom too. Soo then everything started. I know how to push files via adb or sideload. The problem is my Phone doenst get recognized in recovery mode. Not at all. On the other hand if i connect it in download mode then it's shown perfectly fine. With name and manufacturer and so on. Next i tried to flash a stock rom with odin.. But there i got some error Messages right at the start. Something about NAND :S.(will look it up later when i'm on my pc again)
I hope my phone isnt hardbricked :s.
Thanks for the help in advance.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Thats the odin error.
and on the phone an error shows up: SW REV. CHECK FAIL. DEVICE: 3, BINARY: 2
Try Smart Switch emergency initialization as mentioned in this post:
http://forum.xda-developers.com/galaxy-s6/help/help-plz-s6-bootloops-t3303822
If you are stuck at logo afterwards, you may need custom kernel, e.g. unikernel (trips knox)
brenner650 said:
Try Smart Switch emergency initialization as mentioned in this post:
http://forum.xda-developers.com/galaxy-s6/help/help-plz-s6-bootloops-t3303822
If you are stuck at logo afterwards, you may need custom kernel, e.g. unikernel (trips knox)
Click to expand...
Click to collapse
Knox is triggered already anyways. I had an custom Rom installed before. Does Smart Switch recognize Phones in Download mode? otherwise, as stated, my Pc doesnt detect my Phone..
Cant try it now. But when i am getting home from work i will. Before, i will try to Flash another stock Rom, one that is more up to date then the one i used. because i think that maybe the rom caused the Odin error.
hsrye said:
Knox is triggered already anyways. I had an custom Rom installed before. Does Smart Switch recognize Phones in Download mode? otherwise, as stated, my Pc doesnt detect my Phone..
Cant try it now. But when i am getting home from work i will. Before, i will try to Flash another stock Rom, one that is more up to date then the one i used. because i think that maybe the rom caused the Odin error.
Click to expand...
Click to collapse
if you do the emergency recovery at smart switch it will ask you to go to download mode so no problem
Sboot fail is coused trying to flash an older firmware than phone already have... Do you see logs.. Wtf dude... Download newest firmware and flash
lummujaj said:
Sboot fail is coused trying to flash an older firmware than phone already have... Do you see logs.. Wtf dude... Download newest firmware and flash
Click to expand...
Click to collapse
ok, i'm home now. Need to download the rom and then we will see . But thats what i suspected already too, but download failed over night so couldnt try it this morning. Hopefully it will stay as easy as that .
Edit: Thank god it worked . The newest firmware flashed just fine after the second try
I've been running the latest Darthstalker rom on my T-mobile Galaxy Note 5 (SM-N920T). After midnight New Years.. I powered the phone off and then later powered it on and I get this message Custom Binary Blocked by FRP Lock. I can't mount anything via my WIndows laptop and I can't get into Recovery. Since it's a note 5 I can't even open it to get the serial number or any thing or pull the SIM chip. I've seen some posts telling me to use Kies 3 and some saying using Odin to install stock and reroot. A lot of these posts seem to have been using Darthstalker as a ROM.
Is there any path I can follow that will allow me to get back and up and running without data loss? What's the best steps to take?
Thanks in advance and Happy New Years XDA!
mryanmarkryan said:
I've been running the latest Darthstalker rom on my T-mobile Galaxy Note 5 (SM-N920T). After midnight New Years.. I powered the phone off and then later powered it on and I get this message Custom Binary Blocked by FRP Lock. I can't mount anything via my WIndows laptop and I can't get into Recovery. Since it's a note 5 I can't even open it to get the serial number or any thing or pull the SIM chip. I've seen some posts telling me to use Kies 3 and some saying using Odin to install stock and reroot. A lot of these posts seem to have been using Darthstalker as a ROM.
Is there any path I can follow that will allow me to get back and up and running without data loss? What's the best steps to take?
Thanks in advance and Happy New Years XDA!
Click to expand...
Click to collapse
If you can't even mount it on Windows or get into recovery that's not good.
True Dat!
MrMike2182 said:
If you can't even mount it on Windows or get into recovery that's not good.
Click to expand...
Click to collapse
The other examples I read said the same thing.. at this point I'm going to try to find a stock and odin it and root again and see if I even get my files back.. Unless someone has a better idea?
mryanmarkryan said:
The other examples I read said the same thing.. at this point I'm going to try to find a stock and odin it and root again and see if I even get my files back.. Unless someone has a better idea?
Click to expand...
Click to collapse
I would suggest pushing the root kernel to it anyway just to see if it will go.. I do have an FRPbypass but it's an apk meaning you need to install it and if you cannot mount to push it and then try to do adb shell pm install FRPbypass.apk then there's no point in that either.. Can you even get into download mode? If not the last thing I could suggest is the PIT file to repartition it. Unless someone else has a better idea? I do have the PIT file for odin too.
Also I think you're past the point of losing your data and if you can hold the volume down button and power button at the same time until it shuts off and turns back on again you can select factory reset and that's going to ruin all data..
My god, this happened to me on my first Note 5 I had. I was trying to restore it to stock before selling it and like an asshole I forgot to check for "OEM Unlock" and ran into that exact message. It put the fear of god into me. Like you I didn't have the serial number written down and I couldn't get it from anywhere. T-Mobile tech reps tried to tell me the IMEI number acts as a serial number, cool, that doesn't help me. I gave up on Kies and just played around with Odin after I was FINALLY able to find a stock firmware. I can't believe how difficult that was to get. I managed to flash the stock firmware thru Odin and I got the phone back! Stock as it came out the box.
I can't remember how I was able to get it into download mode but whatever button order I kept trying I finally did because Odin recognized the mofo and I flashed that stock firmware as fast as I could. It rebooted and I saw that beautiful stock welcome screen once more. Try to do this, I didn't need to do anything else.
For this reason I now keep a copy of stock firmware along with screen shot of my phone's status screen showing the serial number and everything else. All that's backed up to one of my external drives. Alone with several nandroid backups of various stages of owning this second Note 5 I have now. I'm running V10 of Darthstalker but I haven't heard of other users running into FRP lock. That would mean something tripped their OEM unlock option but how would that happen without you doing it? Is there something inside the ROM (a bug) that's tripping the option in Developer Options?
Best of luck with this, I know how stressful this can be. As far as getting your data back, yeah that's likely a no go. At this point you should be hopeful of getting a working phone back, let alone recover any personal data. Hope you can sort this.
More Info
MrMike2182 said:
If you can't even mount it on Windows or get into recovery that's not good.
Click to expand...
Click to collapse
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
mryanmarkryan said:
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
Click to expand...
Click to collapse
Yeah if you can get it into download mode and you've got the stock firmware you should be good to go and flash tru Odin. That's key. If I were you I'd be like, "To hell with my personal data! Get me a working phone back!".
Good luck.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mryanmarkryan said:
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
Click to expand...
Click to collapse
Ohh I see what you did now and unfortunately all your data is gone because there's only one way to fix this now and that's to either flash TWRP again and then re-flash the rom you want or use odin to flash stock firmware to at least get your phone going.. The mistake you made was disabling developer options which in turn, turned around and re-disabled oem unlock and turned debugging off.. Never ever turn that off while using a custom rom and kernel!!
MrMike2182 said:
Ohh I see what you did now and unfortunately all your data is gone because there's only one way to fix this now and that's to either flash TWRP again and then re-flash the rom you want or use odin to flash stock firmware to at least get your phone going.. The mistake you made was disabling developer options which in turn, turned around and re-disabled oem unlock and turned debugging off.. Never ever turn that off while using a custom rom and kernel!!
Click to expand...
Click to collapse
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
mryanmarkryan said:
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
Click to expand...
Click to collapse
Try downloading the newest odin version sometimes that can help.. Can you tell me how it's failing? Like what exactly happens when you try to do all the flashing? Did you try the adb commands that I suggested? You only need to install minimal adb and Fastboot on the windows pc and then connect your device and then open a terminal in the same exact folder where adb and Fastboot were installed and then type Fastboot devices or adb devices if it give you a bunch of numbers it means that it can see the device and we can then manually push and install the firmware. The other thing I suggest you try to do is flash the Lollipop 5.1 T-mobile firmware because I think it doesn't have frp on it yet and before flashing it go into the actual firmware you downloaded and delete cm.bin then rezip the firmware again and flash that one without the cm.bin but first try flashing the entire firmware as is with the md5 and all before resorting to deleting cm.bin.. Don't try flashing the Marshmallow 6 rom because that's where they started that frp bullcrap if you ask me. FRP stands for Factory Reset Protection... I understand the need for it and it's importance but Google could have been a lot more open about it and explaining to its customers what it's for and what it does not just do it and let most of us learn the hard way!!
When you try to flash in Odin tell me what file it fails on.
If none of this works this page is your last bet buddy
https://www.sammobile.com/forum/showthread.php?t=31136
I'm working on it now! Give you guys a summary of what happened as I as check off your suggestions..
SO far I have the ADB and Fastboot installed (found the link on XDA). However, when I plug my phone in and issue adb devices or fastboot device it does not show. I did also hook up a note II which is my older phone. It used to be rooted and had ROMs installed but I snafued it up one day and didn't bother with it. It says System software not authorized by Verizon Wireless has been found on your phone.. blah blah.. SO that phone doesn't appear in adb devices either.. I've already updated and re-installed the samsung drivers.. Shouldn't the Note II have shown up? There is no FRP for that old model..
I"ve also got Odin and am currently downloading the 5.1.1 firmware.. the free way lol
Progress!
mryanmarkryan said:
SO far I have the ADB and Fastboot installed (found the link on XDA). However, when I plug my phone in and issue adb devices or fastboot device it does not show. I did also hook up a note II which is my older phone. It used to be rooted and had ROMs installed but I snafued it up one day and didn't bother with it. It says System software not authorized by Verizon Wireless has been found on your phone.. blah blah.. SO that phone doesn't appear in adb devices either.. I've already updated and re-installed the samsung drivers.. Shouldn't the Note II have shown up? There is no FRP for that old model..
I"ve also got Odin and am currently downloading the 5.1.1 firmware.. the free way lol
Click to expand...
Click to collapse
I was able to install the 5.1.1 firmware and it reboots, has tmobile's (or samsung's) recovery and boots to a TMOBILE logo and stops. Thinking it is not rooted anymore and Perhaps I should try to re-root.. I did try to install twrp and it failed.. Twrp 2.8.7.1 alpha.. and also the most recent..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Advice?
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
mryanmarkryan said:
I was able to install the 5.1.1 firmware and it reboots, has tmobile's (or samsung's) recovery and boots to a TMOBILE logo and stops. Thinking it is not rooted anymore and Perhaps I should try to re-root.. I did try to install twrp and it failed.. Twrp 2.8.7.1 alpha.. and also the most recent..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
mryanmarkryan said:
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
Click to expand...
Click to collapse
Your gonna have to flash the LATEST 6.0.1 ROM and firmware thru Odin. I don't think 5.1.1 will boot your phone up completely.
mryanmarkryan said:
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
Click to expand...
Click to collapse
It stopped right while trying to flash the recovery part of it so here's what I suggest you try to do.. unzip the 5.1.1 firmware you downloaded and unzip it again until you can see all the files in it and then manually flash them 1 by 1 in the AP slot but don't allow the phone to auto reboot uncheck that option and after 1 files flashed hold the volume down button and power button until you can select shut down device or turn off whichever then again hold the buttons to get into download mode again and continue until they are all flashed and then finally again hold the volume down button and power button and when it comes back on then select factory reset.
---------- Post added at 08:31 PM ---------- Previous post was at 08:28 PM ----------
E-POUND said:
Your gonna have to flash the LATEST 6.0.1 ROM and firmware thru Odin. I don't think 5.1.1 will boot your phone up completely.
Click to expand...
Click to collapse
If he flashes the latest firmware with the security updates he can never go back to 5.1.1 so I don't suggest he do that yet
Ok, potentially some progress.. I flashed all the .bin files . Then I converted all the img files to tar.md5 and flashed those including the recovery and system.img. I rebooted the phone into download each time. Afterwards I rebooted and it did a system update icon for a bite and then the samsung animation.. Now it's at t-moile.. and sitting. I'll let it sit for a while.. maybe it's just rebuilding the cache.. I didn't see an option for factory reset, but I could go into recovery and do it there?
Update: It finally rebooted and has done so 3 times after sitting at the T Mobile (white screen) ..
Update2: I tried to flash the contents of file twrp-3.0.2-0-nobleltetmo.img.tar.. it failed so I extracted the recovery.img file and converted it back to tar.md5 (I know probably just a circle). It failed too..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does this mean I'm not rooted anymore?
mryanmarkryan said:
Ok, potentially some progress.. I flashed all the .bin files . Then I converted all the img files to tar.md5 and flashed those including the recovery and system.img. I rebooted the phone into download each time. Afterwards I rebooted and it did a system update icon for a bite and then the samsung animation.. Now it's at t-moile.. and sitting. I'll let it sit for a while.. maybe it's just rebuilding the cache.. I didn't see an option for factory reset, but I could go into recovery and do it there?
Update: It finally rebooted and has done so 3 times after sitting at the T Mobile (white screen) ..
Update2: I tried to flash the contents of file twrp-3.0.2-0-nobleltetmo.img.tar.. it failed so I extracted the recovery.img file and converted it back to tar.md5 (I know probably just a circle). It failed too..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does this mean I'm not rooted anymore?
Click to expand...
Click to collapse
You're not rooted at all right now but you should not have needed to turn the imgs back into md5s again you should have just flashed them the way they were they don't need md5 just to flash. Try holding the volume down button and power button until it shuts off and turns back on again then select factory reset if that doesn't work then go into download mode again and connect to a Windows pc and use Smart Switch to try and fix it.
The reason I converted them was because Odin wouldn't find the files.. I tried just running them by typing a *.img but it didn't work. I'll go read about smart switch.. I"m learning stuff here
Update,: On a hunch I went back and ran the firmware install again, but just in it's original format. It succeeded and I'm setting up the phone now.. Thanks for your help MrMike. I appreciate you putting the time in..
mryanmarkryan said:
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
Click to expand...
Click to collapse
You are using the wrong stock firmware. Download the DPG1 firmware since that is was darthstalker v.11 is on. If you backed up your ROM then you don't have any troubles at all. Just ODIN back to stock, root, twrp recovery data only and done. But not all at once. First get the firmware going and reboot your phone. Once you know it's working the try rooting. Once you are rooted download TWRP and recover your data only.
Btw - FRP is when you log into your google account in the beginning of the setup so don't do that if you want to flash other ROMs.
P.S. I'be been running Darthstalker v.11 since it came out with no problems.
So basically I have a FRP locked S7 running nougat (not anymore ). I tried various guides to bypass FRP lock, but none worked. Stumbled upon this guide, and got Custom Binary Blocked by FRP Lock. Searched some more, found out I should downgrade to marshmallow (apparently) to make it work. Started up Odin, and I only loaded only the AP, found a video of a guy doing it and working, but in retrospect I think I should have loaded the bootloader, etc.
Long story short, after I rebooted the phone after flashing, it got stuck at Galaxy S7 logo, and I couldn't turn the phone off for the life of me (held power button for like 10 minutes). Simulated battery pull command just restarted the phone, still stuck. I let the battery drain, thought I could charge the phone while off for a bit, put it back into download mode, and try to reflash back to 7.0 or something. Same story.
Any advice or ideas would be greatly appreciated.
On your second Odin flash attempt did you include all 4 firmware files (CP, CSC, BL, AP)? If not, do it again using all of those, and don't use HOME_CSC
Beanvee7 said:
On your second Odin flash attempt did you include all 4 firmware files (CP, CSC, BL, AP)? If not, do it again using all of those, and don't use HOME_CSC
Click to expand...
Click to collapse
I only flashed once, just with AP ticked. That's when I got stuck in bootloop. Now I can't get the phone into download mode. It's fully discharged now, and if i plug in the charging cable it just starts on S7 logo and freezes again.
Give it some charge, then try get into download mode with USB disconnected. Even when on the Samsung logo, the download mode combo is meant to interrupt and reboot no matter what the phone is doing, but when USB is connected it goes into the charging state.
Beanvee7 said:
Give it some charge, then try get into download mode with USB disconnected. Even when on the Samsung logo, the download mode combo is meant to interrupt and reboot no matter what the phone is doing, but when USB is connected it goes into the charging state.
Click to expand...
Click to collapse
Charged it for a bit, removed cable, stuck on S7 Logo. Proceeded to apply home + vol down + power, phone restarted, back at S7 logo still stuck.
LE: Kept holding download mode combo, managed to get it working. Will update soon
Are you releasing hole + vol down + power when it restarts or holding it the whole time? You should be holding it until you get to the download mode screen.
Beanvee7 said:
Are you releasing hole + vol down + power when it restarts or holding it the whole time? You should be holding it until you get to the download mode screen.
Click to expand...
Click to collapse
As I said up top, managed to get into download mode. Added all files to odin, clicked start, fail on BL.
Phone says SW REV. CHECK FAIL. DEVICEL: 2, BINARY: 1
What version did you start on, Nougat? And you're trying to go back to Marshmallow?
It could be that the last bootloader version that came with Nougat prevents downgrades, but if you flash to Oreo first including the newest bootloader, you should then be able to downgrade from Oreo to Marshmallow.
Beanvee7 said:
What version did you start on, Nougat? And you're trying to go back to Marshmallow?
It could be that the last bootloader version that came with Nougat prevents downgrades, but if you flash to Oreo first including the newest bootloader, you should then be able to downgrade from Oreo to Marshmallow.
Click to expand...
Click to collapse
Yes, it was on Nougat. Will try to flash Oreo. I`m guessing there's no way to bypass FRP on Oreo tho ? Also thanks for all your help so far ! :good:
Yea Oreo is as secure if not more secure than Nougat, the only FRP bypass methods I'm aware of only work on Marshmallow.
Beanvee7 said:
Yea Oreo is as secure if not more secure than Nougat, the only FRP bypass methods I'm aware of only work on Marshmallow.
Click to expand...
Click to collapse
Right so now I downloaded the Oreo update. Put everything in Odin, press start, it just restarts the phone and says success. Should I flash bootloader first and then the rest of the files ?
Part of log:
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Flashing all at the same time should work fine, what happens if you try marshmallow now?
Beanvee7 said:
Flashing all at the same time should work fine, what happens if you try marshmallow now?
Click to expand...
Click to collapse
Fails right off the bat. Same SW REV error
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> param.bin
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Then yea try just the Oreo BL, see what happens, then the marshmallow files.
You've definitely got the right firmware for the phone model that is displayed in download mode?
Beanvee7 said:
Then yea try just the Oreo BL, see what happens, then the marshmallow files.
You've definitely got the right firmware for the phone model that is displayed in download mode?
Click to expand...
Click to collapse
Pretty sure yeah, here's the list:
Oreo:
Country / RegionNordic countries
PDAG930FXXU2ERE8
Product CodeNEE
CSCG930FNEE2ERE8
PhoneG930FXXU2ERD6
Nougat:
G930FXXS1APG3 - Poland Version i think
Marshmallow:
G930FXXU1DQB7 - Bulgaria Version
Also odin stuck at
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin.lz4
Click to expand...
Click to collapse
And you've definitely got a G930F international model and not US/Canada?
You can use Odin to repartition when there's boot issues, but it's risky and I'm not personally familiar with the correct way to do it.
Beanvee7 said:
And you've definitely got a G930F international model and not US/Canada?
You can use Odin to repartition when there's boot issues, but it's risky and I'm not personally familiar with the correct way to do it.
Click to expand...
Click to collapse
Pretty sure yeah. Phone is from the UK. In download mode it says SM-G930F, and when I could get into recovery up top it said G930FXXsomething something
LE: Trying to flash nougat back, see if I can at least get it back working the way it was.
LE2: Same SW REV CHECK FAIL with nougat as well :|
LE3: Managed to flash nougat back just by writing the AP, phone now started normally. That just leaves the problem with the FRP lock, so I`m back to square one )
Why does Samsung disallow downgrading? Why can't we just tick a box that says "I understand that the security will be downgraded too" so their butts are covered and we can have what we want? What a dumb move on their parts... Obviously not gonna blame Samsung if someone got my info because I choose to downgrade...
Btw been trying to do the same. I rooted first and made a backup before messing with things. Only tried the 2 things, got in a boot loop but was able to reflash twrp, then booted into twrp by pressing the download buttons combo, but switching to recovery combo as soon as the screen went black. That worked. For now restored my backup.
But I'm determined to figure this out one way or another. SO many people want to downgrade, so why isn't Samsung listening? "Everyone hates nougat, but hey let's make Oreo exactly the same..."
Ugh sorry just frustrated right along with you!
Sent from my [device_name] using XDA-Developers Legacy app
You cant downgrade U2 to U1, efuses prevent this! Try to FRP unlock your phone though G930FXXU2DRAG firmware of UAE, its the only one that worked with z3x and octoplus boxes for me.