Related
I recently got my Samsung Galaxy S6 and decided to root and install TWRP for a custom rom. I was able to root the phone and then installed their android app. TWRP Manager (ROOT).
After that I went to the app and one of the sidebars labeled install TRWP on the app then to the codename zeroflte for the Samsung Galaxy S6. It told me to restart my phone and I did but after that I was not able to use my phone again. Whenever I would turn on my phone it would show the normal Samsung s6 screen with a unlock picture and the words custom underneath. After that it would display a turquoise color screen with a words
Start Up Failed. Your device didn’t start up successfully. Use the Verizon Software Repair Assistant on a computer to repair your device.
I tried to google and see if anyone had a similar problem but nothing popped up. I don’t know where to find a copy for the Verizon Software Repair Assistant for the Galaxy S6.
I also tried and factory reset the phone or anything but the only combinations of buttons that would work on my phone were the down volume + power button. It gave me a list of options including factory reset but every option that I chose would lead me back to the same screen. The turquoise screen saying Start Up Failed.
Any help would be great. I don’t know what to do now. Tomorrow I am going to down to a local repair store and see what they can do. But if you know of anything that would be great. Thank you for your time and have a nice day.
inolil said:
I recently got my Samsung Galaxy S6 and decided to root and install TWRP for a custom rom. I was able to root the phone and then installed their android app. TWRP Manager (ROOT).
After that I went to the app and one of the sidebars labeled install TRWP on the app then to the codename zeroflte for the Samsung Galaxy S6. It told me to restart my phone and I did but after that I was not able to use my phone again. Whenever I would turn on my phone it would show the normal Samsung s6 screen with a unlock picture and the words custom underneath. After that it would display a turquoise color screen with a words
Start Up Failed. Your device didn’t start up successfully. Use the Verizon Software Repair Assistant on a computer to repair your device.
I tried to google and see if anyone had a similar problem but nothing popped up. I don’t know where to find a copy for the Verizon Software Repair Assistant for the Galaxy S6.
I also tried and factory reset the phone or anything but the only combinations of buttons that would work on my phone were the down volume + power button. It gave me a list of options including factory reset but every option that I chose would lead me back to the same screen. The turquoise screen saying Start Up Failed.
Any help would be great. I don’t know what to do now. Tomorrow I am going to down to a local repair store and see what they can do. But if you know of anything that would be great. Thank you for your time and have a nice day.
Click to expand...
Click to collapse
Have you tried to Odin back to stock?
http://forum.xda-developers.com/verizon-galaxy-s6/development/5-15-stock-odin-tar-t3109676
Ya, you'll need to odin back to stock like he said. And TWRP isn't available for our phone since we don't have an unlocked bootloader. Do not try and install TWRP again. You'll want to use Flashfire if you need to flash anything.
brholt6 said:
Ya, you'll need to odin back to stock like he said. And TWRP isn't available for our phone since we don't have an unlocked bootloader. Do not try and install TWRP again. You'll want to use Flashfire if you need to flash anything.
Click to expand...
Click to collapse
Awesome thank you
I need help!
I did the exact same thing with my Galaxy s6, i tried to do the same thing with my newly acquired root, I am very new but very interested in rooting and customizing my phone, when I plug my phone into a computer it only pops up with the start up failed screen, I installed the odin thing but i have no clue where to go from here and any assistance would be greatly appreciated. thank you
Bubblegum Mage said:
I did the exact same thing with my Galaxy s6, i tried to do the same thing with my newly acquired root, I am very new but very interested in rooting and customizing my phone, when I plug my phone into a computer it only pops up with the start up failed screen, I installed the odin thing but i have no clue where to go from here and any assistance would be greatly appreciated. thank you
Click to expand...
Click to collapse
Keep in mind XDA is a community for developers by developers. People are also willing to help, but you got to put forth your own effort. You will get ignored if you think people on this site are going to act as free tech support. Your question is posted just a few posts down from a link to the process on using odin to return to stock. You need to just follow those instructions. If you don't understand a step then Google it. I'm saying this because I noticed you joined XDA to ask this question. Or at least it's your first post. You will make a lot of enemies here if you don't take the time to read and research things before posting.
HELP
I have the same problem (Start up failed) but ODIN is not working for me... I am using the stock firmware for the GS6 edge and it says failed... what should I do?
Bee Funny said:
I have the same problem (Start up failed) but ODIN is not working for me... I am using the stock firmware for the GS6 edge and it says failed... what should I do?
Click to expand...
Click to collapse
If you have an edge you should use their forum. It's different than the GS6.
Just had to Odin my Verizon S6 (sm-g920v) to get it back to factory defaults.
I've been rooted for months with no issues and have known my bootloader was locked with no nice way around it but then i read some stupid guides saying to go get twrp manager to load custom roms on the Galaxy s6 phones and they even included the sm-g920v model number. I went to the app store, downloaded twrp manager, followed the first few steps, rebooted and that was that. Could not boot up anymore without Start Up Failed. A few checks and warning would have been greatly appreciated from the app developers but oh well.
Well that was fun. Now to redo everything on my phone.
Oooah said:
Just had to Odin my Verizon S6 (sm-g920v) to get it back to factory defaults.
I've been rooted for months with no issues and have known my bootloader was locked with no nice way around it but then i read some stupid guides saying to go get twrp manager to load custom roms on the Galaxy s6 phones and they even included the sm-g920v model number. I went to the app store, downloaded twrp manager, followed the first few steps, rebooted and that was that. Could not boot up anymore without Start Up Failed. A few checks and warning would have been greatly appreciated from the app developers but oh well.
Well that was fun. Now to redo everything on my phone.
Click to expand...
Click to collapse
Same exact crap just happened to me. I was running CleanRom Lite....thought I could use TWRP...some times I do stupid things...should have just stuck with FlashFire.
I've tried odin back to stock, it keeps failing. it says nand write fail and it stops. I've tried many different times. I've run Odin 3.10.6 and 3.10.7 I have the latest drivers, it recognizes the device but it will not load anything via odin. I've tried on two different computers as well.
...
Gizmoe said:
...
Click to expand...
Click to collapse
I have a Galaxy s6 edge btw. Not much info on the edge, in desperation, I'm combing thru galaxy s6 forums seeking answers. I have been rooted for awhile. I wanted to turn off the nagging volume warning so I downloaded a zip file to flash but only to find that my twrp recovery was no longer there. So I try to download twrp and flash. Now I'm in a boot loop with the turquoise screen telling me to use a verzion tool to reset the device. Klies says my phone isn't compatible as well as smart switch. Odin fails every time after NAND WRITE. I'm about to microwave this crap and get new phone.
keith7120 said:
I have a Galaxy s6 edge btw. Not much info on the edge, in desperation, I'm combing thru galaxy s6 forums seeking answers. I have been rooted for awhile. I wanted to turn off the nagging volume warning so I downloaded a zip file to flash but only to find that my twrp recovery was no longer there. So I try to download twrp and flash. Now I'm in a boot loop with the turquoise screen telling me to use a verzion tool to reset the device. Klies says my phone isn't compatible as well as smart switch. Odin fails every time after NAND WRITE. I'm about to microwave this crap and get new phone.
Click to expand...
Click to collapse
Did you ever get your phone up and running? I ran into similar issue with odin. After looking around on web I found a forum that mentioned using an older version of odin.
---------- Post added at 06:50 PM ---------- Previous post was at 06:44 PM ----------
Fe Mike said:
Did you ever get your phone up and running? I ran into similar issue with odin. After looking around on web I found a forum that mentioned using an older version of odin.
Click to expand...
Click to collapse
Sorry I saw you tried other odin versions 3. 10.x, I meant going lower. 3.09 is recommended for jb/kk but that worked for me.
Hi guys,
Not started a thread on XDA for years but I really am stumped.
I have claimed my girlfriends s6 (SM-G920F) after she upgraded and intended to root it and maybe try a few Oreo ROMs etc. After investigation I saw that (I think this is right) I don't need to OEM unlock this version of the device and rooting via Odin is the best way to do it. BTW if I do need to OEM unlock then that might be the solution to my issue, so if some one could clarify that'd be great.
So a week ago I downloaded Odin and also my old favourite CF-AutoRoot after putting in the device details. The package was generated, I unzipped and put it in a folder in my desktop
After putting the device in download mode I run Odin as administrator and plug it in. The device is recognised and I get the blue box to show this.
I then click the AP box and select the image file and click start, everything runs as expected to this point and I get PASS displayed in the info bar. On the phone the progress bar looks like it has not completed and I can see a small portion still to run. On the first try I left phone like this waiting for it reboot for over an hour. I was expecting 5he device to reboot and get the android with the red exclamation point. At this point I restarted manually and saw during the boot process an error message saying Recovery not SE Enforcing in red.
I have read a few posts saying this can be caused by the wrong image being used, so I downloaded the Auto root package again and made sure that it was all correct, but the same thing occurred.
I have been looking and reading for the last week to find a solution, but I'm still in the same position. Can anyone help or point me in the right direction?
If you need any more info let me know.
Thanks in advance
Jon
im in exacltly the same boat pal. was running nanorom on my rooted s6, but had no vr capability and just got some galaxy gear goggles. tried to reflash arter97 kernal and lost my whole setup. ive been in and out of hard brick for last 24hrs and am back now to where you are, i can access download and recoveries via three button combo, but any packages i flash with odin just fail out right.
ive been here before though and usually get out once i find the right stock rom and csc's for my version. iof i find anything ill come back and share it with you pal.
Cheers mate, it's really frustrating. I'll keep looking too and post back if I have any success.
Hi guys, this thread hasn't been responded to so I thought I'd just replied to it to give it a little bump up. I'd much appreciate it if anybody could help me out here.
Thanks again,
Jon
copernicus666 said:
Hi guys, this thread hasn't been responded to so I thought I'd just replied to it to give it a little bump up. I'd much appreciate it if anybody could help me out here.
Thanks again,
Jon
Click to expand...
Click to collapse
Just try bro to reflash full stock rom again by odin and after flash it , reflash cf-autoroot again
also , can you provide more information about your android version and your csc stock rom ?
what a f**k about!!!!
Right then Jon,
sorry for my delay but not the greatest at reponding to things at the best of times, but with my own s6 in a right old state, and a 7y.o and 4 month old in the house, my pc time is limited.
anyways, im guessing you're a bit like me, and you've had your fair share of flashing roms and roots since the days of old! (Galaxy thru and thru for me s 1,3,4,6, plus tabs and watches).
this s6 gt-920f is a completely different kettle of fish mate. where you're at at the minute, if your still stuck in bootloop with no recovery, your gonna want to find twrp recovery, as you know mate, google will be your guide. you flash this just like a rom or the old cwm, download a zip, bang it in ap/pda in odin and let it flash. KEY NOTE IS MAKE SURE ODIN HAS ~"AUTO-REBOOT"~ UNTICKED, UNCHECKED, NO MARK IN THE BOX. THIS IS KEY TO THE RESTORATION PROCESS GOING FORWARD. Once odin shows that the file has flashed and passed, get ready to perform a three button power reset, Home button, Vol DOWN and Power for 8 seconds. when your pc makes the badong sound and the screen goes off, IMMEDIATELY SWITCH TO Vol UP, Home and Power, thus straight into recovery mode, AND WAIT.
You should see the blue and silver TWRP splash screen and then the recovery options. Firstly, wipe and format everything, dalvik, caches and perform a factory reset. twrp should ask you to type yes to confirm, do it, there's nothing there yet any ways. if you get any issues about cant mount data or some jazz, DONT PANIC, use twrp to reformat the partition to ext4, your pc should ping to show reconnection to the phone.
Now whilst still in twrp, nav to the reset options and reboot into download mode. if all has go well, the scren should have the regular greenish odin screen but without all the samsung odin mode in at the top. odin should show the phone as a connected device, you should be able to access your memory card from your pc to transfer rom zips etc and get the phone back up the way you are used to.
if on the other hand you want to get back to vanila stock style android, with the expense of a tonload of bloatware and crapps, you're gonna wanna take a goggle at stuff like "G920F Repair Firmware X.X UK YYY) , Where X.X is 5.1, 6.1, 7.1, depending on the original android version your brick was on, and YYY is your carrier or network operator, off the top of my head they are VOD, TMO, O2U, H3G.
AGAIN A KEY POINT IF YOUR GOING THIS ROUTE, THESE FILES ARE MADE FOR INDIVIDUAL MODELS OF S6 (THERES ABOUT 12 MODEL NUMBERS -YOURS IS AND ALWAYS WILL BE SM-G920F - SO DO NOT EVER STRAY FROM THAT NUMBER!!!! ) THAT MEANS YOU NEED TO BE FINDING FILES LIKE "G920XXU5EXUE 4 files repair firmwares", THESE ARE YOUR SAVIOUR. GET THE ONE THAT MATCHES YOUR PHONE AND CARRIER OR ONE THAT IS AS NEAR AS DAMMIT, AND AGAIN PLEASE MAKE SURE FOR THE LOVE OF YOUR PHONE THAT YOU ONLY GET FILES MARKED G920, ANYTHING ELSE WILL RESULT IN VERY SERIOUS ERRORS.
YOUR ALSO GOING TO NEED SOMETHING CALLED A PIT FILE, EASY TO FIND, LOOK FOR " S6 ZEROFLTE HIDDEN IMG FILE" IN GOOGLE.
USE OUR OLD BUDDY ODIN TO FLASH THE FOUR FILES YOU GOT FROM THE REPAIR FIRMWARE ZIP, WHICH ARE USUALLY LABEL AP, BL, CP AND CSC.. NOW TAP THE PIT TAB IN ODIN (IGNORE THE WARNING) AND NAVIGATE TO THE HIDDEN.IMG FILE YOU GOT AND BANG IT HERE. ON THE OPTIONS TAB YOU WANT TO TICK AUTO REBOOT, REPARTITION, and NAND ERASE ALL. i know, i know, you probably never use it out of some shear panic but right now its kosher.
start the flash and take a break. like a big break. the process is gonna wipe the phone in totalilty, rewrite every bit of code and software and reload like new after about forty minutes.
now, if it doesnt, there are a few things we can look at but am gonna leave it here and hope you can make some use of the ramblings of a lost man. my 6 is currently in an inverted touch bug where if i touch one side of the screen, the opposite side responds so its a proper nightmare, typing anything means that a becomes l, s becomes k etc. thisis down to me drunk flashing the wrong roms for and s6 edge, g925f, hence all my warnings earlier. anyways, i need a reefer and a scran after all this, God, allah, buddah i hope it helps someone.
shiko2007 said:
Just try bro to reflash full stock rom again by odin and after flash it , reflash cf-autoroot again
also , can you provide more information about your android version and your csc stock rom ?
Click to expand...
Click to collapse
Hi, thanks for replying.
I'm on the original stock, I've not flashed any thing just yet. To be honest, I'm not sure it'd work.
The android version is 7.0 and the build is NRD90M.G920FXXS5EQH6
Be glad if you have any advise.
Thanks
copernicus666 said:
Hi, thanks for replying.
I'm on the original stock, I've not flashed any thing just yet. To be honest, I'm not sure it'd work.
The android version is 7.0 and the build is NRD90M.G920FXXS5EQH6
Be glad if you have any advise.
Thanks
Click to expand...
Click to collapse
if your not root yet just download latest your carrier/country firmware
from sammobile
and flash it by odin
but you are probably trip knox so you must root
so the steps you should do :
1-download your carrier/country firmware from sammobile
2-flash it by odin
3-flash cf-auto root to pass bootloop
or
download twrp recovery of g920f and flash it by odin to replace stock recovery then after flash it ,wipe delvik cash then flash su binary
DagsyMc said:
Right then Jon,
sorry for my delay but not the greatest at reponding to things at the best of times, but with my own s6 in a right old state, and a 7y.o and 4 month old in the house, my pc time is limited.
anyways, im guessing you're a bit like me, and you've had your fair share of flashing roms and roots since the days of old! (Galaxy thru and thru for me s 1,3,4,6, plus tabs and watches).
this s6 gt-920f is a completely different kettle of fish mate. where you're at at the minute, if your still stuck in bootloop with no recovery, your gonna want to find twrp recovery, as you know mate, google will be your guide. you flash this just like a rom or the old cwm, download a zip, bang it in ap/pda in odin and let it flash. KEY NOTE IS MAKE SURE ODIN HAS ~"AUTO-REBOOT"~ UNTICKED, UNCHECKED, NO MARK IN THE BOX. THIS IS KEY TO THE RESTORATION PROCESS GOING FORWARD. Once odin shows that the file has flashed and passed, get ready to perform a three button power reset, Home button, Vol DOWN and Power for 8 seconds. when your pc makes the badong sound and the screen goes off, IMMEDIATELY SWITCH TO Vol UP, Home and Power, thus straight into recovery mode, AND WAIT.
You should see the blue and silver TWRP splash screen and then the recovery options. Firstly, wipe and format everything, dalvik, caches and perform a factory reset. twrp should ask you to type yes to confirm, do it, there's nothing there yet any ways. if you get any issues about cant mount data or some jazz, DONT PANIC, use twrp to reformat the partition to ext4, your pc should ping to show reconnection to the phone.
Now whilst still in twrp, nav to the reset options and reboot into download mode. if all has go well, the scren should have the regular greenish odin screen but without all the samsung odin mode in at the top. odin should show the phone as a connected device, you should be able to access your memory card from your pc to transfer rom zips etc and get the phone back up the way you are used to.
if on the other hand you want to get back to vanila stock style android, with the expense of a tonload of bloatware and crapps, you're gonna wanna take a goggle at stuff like "G920F Repair Firmware X.X UK YYY) , Where X.X is 5.1, 6.1, 7.1, depending on the original android version your brick was on, and YYY is your carrier or network operator, off the top of my head they are VOD, TMO, O2U, H3G.
AGAIN A KEY POINT IF YOUR GOING THIS ROUTE, THESE FILES ARE MADE FOR INDIVIDUAL MODELS OF S6 (THERES ABOUT 12 MODEL NUMBERS -YOURS IS AND ALWAYS WILL BE SM-G920F - SO DO NOT EVER STRAY FROM THAT NUMBER!!!! ) THAT MEANS YOU NEED TO BE FINDING FILES LIKE "G920XXU5EXUE 4 files repair firmwares", THESE ARE YOUR SAVIOUR. GET THE ONE THAT MATCHES YOUR PHONE AND CARRIER OR ONE THAT IS AS NEAR AS DAMMIT, AND AGAIN PLEASE MAKE SURE FOR THE LOVE OF YOUR PHONE THAT YOU ONLY GET FILES MARKED G920, ANYTHING ELSE WILL RESULT IN VERY SERIOUS ERRORS.
YOUR ALSO GOING TO NEED SOMETHING CALLED A PIT FILE, EASY TO FIND, LOOK FOR " S6 ZEROFLTE HIDDEN IMG FILE" IN GOOGLE.
USE OUR OLD BUDDY ODIN TO FLASH THE FOUR FILES YOU GOT FROM THE REPAIR FIRMWARE ZIP, WHICH ARE USUALLY LABEL AP, BL, CP AND CSC.. NOW TAP THE PIT TAB IN ODIN (IGNORE THE WARNING) AND NAVIGATE TO THE HIDDEN.IMG FILE YOU GOT AND BANG IT HERE. ON THE OPTIONS TAB YOU WANT TO TICK AUTO REBOOT, REPARTITION, and NAND ERASE ALL. i know, i know, you probably never use it out of some shear panic but right now its kosher.
start the flash and take a break. like a big break. the process is gonna wipe the phone in totalilty, rewrite every bit of code and software and reload like new after about forty minutes.
now, if it doesnt, there are a few things we can look at but am gonna leave it here and hope you can make some use of the ramblings of a lost man. my 6 is currently in an inverted touch bug where if i touch one side of the screen, the opposite side responds so its a proper nightmare, typing anything means that a becomes l, s becomes k etc. thisis down to me drunk flashing the wrong roms for and s6 edge, g925f, hence all my warnings earlier. anyways, i need a reefer and a scran after all this, God, allah, buddah i hope it helps someone.
Click to expand...
Click to collapse
Legendary post! Cheers mate you just made my morning. I knew the XDA guys would pull through.
I'm on my way to work, but I'll give it a crack later.
Cheers bud - Kudos
All links to articles that I tried to follow are at the bottom of this post. Attempt this root at your own risk!
Let me start out by saying I have successfully rooted Android phones before (Motorola Droid from 2009 and LG G3 Vigor from but this phone was not wanting to cooperate from the very start. My intention was to root my Galaxy S8 so that I can install a custom ROM and get rid of unneeded software (i.e. Google, Sprint software, etc...). As it turns out, this is easier said then done. After A LOT of searching on this site and DuckDuckGo, I came across a few articles that seemed like they were legit and would get the job done. So, I prepared by downloading all the necessary files (the new firmware, Odin, adb, etc...) and factory resetting my device. I then tried to follow along with the first tutorial. Everything looked good. I was able to get everything set up just fine. My problem started when I was in the Download mode on the device (the light blue screen that says "Downloading..." in the center).
Before even connecting the device, I had PrinceComsy Odin fired up and ready to go being sure to follow the tutorial steps completely and accurately. Then, I connected my device and hit start.
...It's looking good!...
...Added!...
After a few other very promising log outputs .... nothing happened. I thought to myself, "Okay, no big deal. It said I may have to retry a couple times to get it to work." So, I reset everything back up and rebooted the phone back into Download mode. This time I tried the regular Odin version instead. However, I was presented with an error after hitting start: "SHA256 Invalid". After some searching, I found out that if you get that error in the regular Odin you should try the PrinceComsy Odin. Wow, okay, so I went back to PrinceComsy Odin and tried again to no avail. Still didn't work.
This is when I started to become concerned that I wouldn't be able to root this phone. Note: At this point, the phone still booted back into the OS with no problems. i.e. It was not bricked...yet!
I wasn't even past the Odin part of the root and already I was having problems. What was going on? I did some more searching around the web and these forums and found something interesting. Supposedly having your device plugged into the USB3.0 ports on your computer can sometimes mess Odin up. I tried plugging the phone into the normal USB2.0 ports on the back of my computer and restarted the whole process again.
Now, I was getting some weird errors. Stuff like "odin fail complete(write) operation" and "fail (no pit partition)". I started to sweat a little bit. I can't screw this phone up! I rebooted the phone just to make sure everything was still fine on the device. It booted into OS perfectly fine, again.
Okay, so one more try, and then I'll stop. I did everything again (booted phone into download mode, fired up PrinceComsy Odin, added firmware to appropriate slots, connected the device, and hit start). Once again, everything looked fine until I got another error, "Error SW REV CHECK FAIL : [aboot] Fused 4 > Binary 2". It was at this point I looked more closely at the text on the top left of the Download mode.
My bootloader was locked and for some reason that had something to do with all this failing. After all, I wasn't trying to change the bootloader at all; just trying to gain access to root permissions. Most of the tutorials I looked at said to enable the "OEM Unlocking" option in settings. However, I didn't have this option at all. I didn't think it would matter that much but boy was I wrong. I decided to give up, boot back into the OS, and call it a day.
I rebooted the phone and it took longer than normal. Like way longer. It was stuck at the Samsung splash screen for about an hour before I realized that the device was probably bricked. "Great," I thought. So, I managed to find the stock firmware on Sam Mobile. Once again, I used Odin and tried flashing the stock firmware. This time however, Odin actually completed! I thought I had done it. I successfully restored my phone, right? Nope, turns out the firmware I installed wasn't actually Sprint's original stock firmware. I'm not sure exactly what it was but everything looked fine until I entered the setup device screen. Some settings were greyed out and I was getting some weird error messages (I don't remember what they were). Then, after completing the setup, I noticed that I was no longer on the Sprint network. I also had some of Cricket's and MetroPCS apps installed by default. It was like the phone was in a so called "carrier limbo" and unable to connect to any one carrier. The weird thing is I was still able to send and receive phone calls and receive text messages. It was at this point, I realized I royally screwed up my phone I tried to factory reset (through the Recovery mode) hoping that would fix some issues but nope. Didn't seem to fix anything.
The next day, I took the phone back to the Sprint store to see if they could do anything. Of course, I knew they were just going to try factory resetting it as well. The tech came back and said they could ship it off to Samsung and have them repair it or replace it. I am really crossing my fingers and hoping that they just replace the phone. That would fix all of my issues (including the cracked screen ). Now, I have to wait 5-7 business days before I know if I'm going to be stuck without a Galaxy phone or if I'm going to get a new phone straight from the factory. Who knows? As of now, I am using my old LG G3 Vigor temporarily while Samsung looks at my phone.
TL;DR: If you are on the Sprint network, have a Samsung Galaxy S8, model sm-g950u, US variant, ATTEMPT ROOTING AT YOUR OWN RISK! Sprint apparently has some pretty intense software locks on their phones which is rather unfortunate seeing as I believe Android to be an open-source and modifiable OS. Basically, we have to use the phone as it is from Sprint or we can't use it all. This is unacceptable.
I will update this post with any new information as it becomes available.
Links
LG G3 Vigor: https://support.sprint.com/support/device/LG/LG_G3_Vigortrade-dvc8360002prd
Motorola Droid: https://www.cnet.com/products/motorola-droid-verizon-wireless/review/
1st Root Method: http://www.stechguide.com/root-galaxy-s8-and-s8-plus-snapdragon-variants/
2nd Root Method: https://forum.xda-developers.com/ga...on-sampwnd-t3658911/post73455543#post73455543
3rd Root Method: https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
Restoring Stock Firmware: http://rootmygalaxy.net/stock-firmware-on-galaxy-s8-and-galaxy-s8-plus/
Before rooting, flash it with the unbranded "U1" firmware which is much cleaner (bloat free), and also works on all carriers as long as the sim lock is unlocked.
I just use the regular Odin and flash TWRP for the correct Samsung device then find a nice custom ROM you can install using TWRP I wrote several guides for it using Samsung phones, A3(2017, A5(2017, A7(2017, A5(2014, J8(2018 other than the button sequence for DL/recovery it is pretty much works the same, installing a stock ROM I did with Odin but finding a good stock ROM that you can download at a decent pace is harder. The OEM unlock is under Dev option in your phone though combined with USB debugging so you would need to do that before using Odin. But I get where you are coming from most guides are confusing as hell.
Here is what I did so far to get here.
First I followed the guide to root my phone, and to be honest, all was perfect. I had to restore stock rom cause my first few tries failed. But seems I flashed a rom for a different provider. It worked anyway, but I don't have my sim card in that phone, it's temporarily in another device.
I had a little issue in settings, where battery was coming up two times in the list. That bugged me, I wanted to restore the rom and see if a full restore would take care of this issue, but somehow, after I installed twrp and rooted my phone, I can no longer flash anything stock with odin, it fails.
If I try to flash the AP tar.md5 file, it fails when it gets to system. And then after rebooting, I see this message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
I tried installing smart switch and kies, and both software doesn't detect my device in download mode or twrp (obviously)...
So to get rid of the emergency message, I flashed twrp again with odin, and been successful. If I tried to flash the AP image again, or CSC, it fails. And then I get the message back.
After flashing twrp, I'm stuck in a boot loop. Would need to restore system I think, but cannot seem to be able to do it with Odin.
Any possible way to recover my device?
Update: Turns out I must have made a mistake with the firmware I thought I had flashed, versus the one I was trying to flash and was failing. I downloaded the latest october firmware and it's currently flashing in odin!
This not be posted in development !
mchlbenner said:
This not be posted in development !
Click to expand...
Click to collapse
Sorry about that, I thought it was related to the topic. Obviously, you saw that I do not have a thousand posts around here, a wise thing to do would have been to suggest me where should I have posted this, and how can I move my thread around? Do I wait for a mod to move it himself?
pleclair said:
Here is what I did so far to get here.
First I followed the guide to root my phone, and to be honest, all was perfect. I had to restore stock rom cause my first few tries failed. But seems I flashed a rom for a different provider. It worked anyway, but I don't have my sim card in that phone, it's temporarily in another device.
I had a little issue in settings, where battery was coming up two times in the list. That bugged me, I wanted to restore the rom and see if a full restore would take care of this issue, but somehow, after I installed twrp and rooted my phone, I can no longer flash anything stock with odin, it fails.
If I try to flash the AP tar.md5 file, it fails when it gets to system. And then after rebooting, I see this message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
I tried installing smart switch and kies, and both software doesn't detect my device in download mode or twrp (obviously)...
So to get rid of the emergency message, I flashed twrp again with odin, and been successful. If I tried to flash the AP image again, or CSC, it fails. And then I get the message back.
After flashing twrp, I'm stuck in a boot loop. Would need to restore system I think, but cannot seem to be able to do it with Odin.
Any possible way to recover my device?
Click to expand...
Click to collapse
You forgot to flash all of them
BL, AP, CP, CSC
pleclair said:
Sorry about that, I thought it was related to the topic. Obviously, you saw that I do not have a thousand posts around here, a wise thing to do would have been to suggest me where should I have posted this, and how can I move my thread around? Do I wait for a mod to move it himself?
Click to expand...
Click to collapse
Just because you have a lot of post you don't post question in development section.
587.saboor said:
You forgot to flash all of them
BL, AP, CP, CSC
Click to expand...
Click to collapse
I did flashed all of them. But it always fails. No matter if I select only BL, AP, CP, CSC... or all of them. Almost seems like twrp is preventing write or something else does.
It fails after a few seconds in the process. Is there any kind of log generated by odin? If so, where can I find it? I don't see much information beside that it fails.
OEM unlock checked in dev options?
USB debuging checked? these were always the go to mischecks...
back when I had the galaxy a5 2017 520W canada unit I flashed a european rom to see if FM radio was going to work. it Worked, but I had the simular issue with battery showing up twice AND I ended up tripping knox while doing it. phone seemed to work fine other then that issue and the radio worked as well.
Flashed it back to 520W stock... later sold the phone... no issues. perhaps it was different with nougat
supertac said:
OEM unlock checked in dev options?
USB debuging checked? these were always the go to mischecks...
back when I had the galaxy a5 2017 520W canada unit I flashed a european rom to see if FM radio was going to work. it Worked, but I had the simular issue with battery showing up twice AND I ended up tripping knox while doing it. phone seemed to work fine other then that issue and the radio worked as well.
Flashed it back to 520W stock... later sold the phone... no issues. perhaps it was different with nougat
Click to expand...
Click to collapse
Yeah, I have those two checked. For some reasons, I was tired that night, and was actually trying to flash 7.1.1 firmware, while having already upgraded to 8.0. So I believe this operation wasn't getting thru because of that. I was tired, and picked the wrong folder, and flashed 7.1.1. Well, I was trying to flash, but it kept failing, but had a tiny bit done, enough to screw this up like this.
When I picked the right folder, 8.0, then it worked.
As for tripping knox, you probably tripped it while flashing twrp. I believe it trips it, haven't heard of a way to do it.
pleclair said:
Yeah, I have those two checked. For some reasons, I was tired that night, and was actually trying to flash 7.1.1 firmware, while having already upgraded to 8.0. So I believe this operation wasn't getting thru because of that. I was tired, and picked the wrong folder, and flashed 7.1.1. Well, I was trying to flash, but it kept failing, but had a tiny bit done, enough to screw this up like this.
When I picked the right folder, 8.0, then it worked.
As for tripping knox, you probably tripped it while flashing twrp. I believe it trips it, haven't heard of a way to do it.
Click to expand...
Click to collapse
nope. NEVER flashed twrp once on the A5- the european firmware tripped it on the 520W
wilsen23 said:
My bad eyes failed me.
I dLoad'd and used the cf-autoroot sm-g900f
when I should have used
sm-g901f.
The first one seemed to root as it changed 0x0 to 0x1, but would not reboot after that.
I pulled batt & tried the correct one later, but looks hard-bricked to me. Goes thru the steps on Odin, but says Failed and of course no reboot. The blue progress bar shows abt 2% and stays there until disconnect.
Question: anything I can try? Not too concerned for hardware...had a bit o' data I would like back.
Most forum root problems I could find start with unknown issues. I know what I did.
Click to expand...
Click to collapse
Try flashing the stock firmware via Odin. You have to be certain that you flash the exact same firmware build number that you already had on the device before you tried to modify it or at least a firmware that has the same binary version as the firmware that was already on the device. The binary version can be identified by looking at the 5th character from the end of the firmware build number. As long as the firmware that you flash is not an upgraded or a downgraded binary from what you had, your data should still be after the flash is finished. If what you flash is an upgrade or a downgrade from what you had, it will wipe your data. If your firmware comes with two different CSC files, use the HOME CSC to preserve your data, using the other CSC will wipe your data.
Sent from my SM-S767VL using Tapatalk
My bad eyes failed me.
I dLoad'd and used the cf-autoroot sm-g900f
when I should have used
sm-g901f.
The first one seemed to root as it changed 0x0 to 0x1, but would not reboot after that.
I pulled batt & tried the correct one later, but looks hard-bricked to me. Goes thru the steps on Odin, but says Failed and of course no reboot. The blue progress bar shows abt 2% and stays there until disconnect.
Question: anything I can try? Not too concerned for hardware...had a bit o' data I would like back.
Most forum root problems I could find start with unknown issues. I know what I did.
Epilogue
So to finish this off:
I had written stuff down but not the exact build. There were several and I was willing to gamble (nothing to lose).
Originally I was using a Win7 box with and old Odin....and as I said in orig post....the Root did take as there were changes noted on the download screen, but no reboot bcz wrong file. At any rate....
To prep for the gamble I dLoad'd newest Odin to a Win10 box. I also dLoad'd Kies3 to ensure I had drivers as the phn had never been connected to this box. After it was all set up I had trouble finding the firmware I had decided on. Just for poops and giggles I decided to try flashing the CORRECT file again. I had tried that a couple times on the Win7 box right after I discovered my error.
I didn't expect much and wasn't even looking at the phone....and it buzzed. That was gooood buzz bcz it took.
So I got it back, rooted, with all data.
I guess the take away is try with freshest drivers, softwares etc b4 giving up. That is standard advice, but clearly it made all the difference in my case.