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.
Related
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
muazra said:
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
Click to expand...
Click to collapse
Hi there,
it seems an easy problem but do it at your own risk I don't take responsibility of bricked device,etc
so lets go with what you need:
A- Odin [I believe you already have it]
B- stock rom go to this site:
androidayos.com/samsung-galaxy-s4-odin-stock-firmware/
and choose the suitable stock rom based on your Baseband version
C- Drivers installed for your device [if your mac/laptop recognizes your device then skip this step if not google it,download the drivers and install them]
IMPORTANT:Make sure you have 80% or more on battery
after you get these stuff install the device drivers as mentions in C then turn your device off and power it while holding volume up it should take you to download.now open odin and navigate it to the rom which you downloaded from B and flash it .wait for green color to appear and your back to your stock now it should open normally hope that I helped
I am new to this forum in terms of posting but I have read a lot in the past. Three months ago I used this site to root my Samsung Note 2 on Verizon. I used Adam Outler's one step method to root the phone. I never downloaded any other ROMs or anything. I just used the root to delete Verizon programs. I ran across some issues with my screen and I was planning to send my phone back to Samsung since it is still under warranty. I unrooted the phone using "imnuts" instructions and everything went well. I then shut off the developer options since I was planning to send the phone back. The binary counter never changed from no and life was good. Later that day the phone ask to do an update with Verizon. I said ok and let the phone reboot. A few minutes later I looked at the phone and the Samsung Note 2 screen kept flashing and shutting down. I am unable to get into recovery mode (power+up volume+home). I am able to get into download mode but odin won't work since the debugger is off. Some people online say you can run odin without the debugger on but I don't think that is the case. I tried to run the "imnuts" Verizon stock but odin quickly says fail. I have read a lot of posts about similar issues but most of the replies were either telling the OP to recover or flash a recover. If my phone is dead I just want to hear that. If you have any ideas please let me know. If I send back to Samsung is this something they will fix? I don't know why it happened but it happened when the phone was back to stock. Any help you can provide would be great. Thanks.
This is the results I get from odin. When I unrooted my phone the first time (the time that it worked) it took about a minute to show the file in the pda section. When I do it now it instantly pops up. I'm thinking the ID COM isn't actually connecting to the phone sine debugging isn't active.
Please, for the love of god, someone help me!!
I have spent the past 2 days trying to root my brand new Tab 2 (verizon) p3100 (android 4.1.2). I've tried every tutorial that I can find. I've tried various versions of Odin, various versions of heimdall, various versions of CWM and other rooting files. I get error after error. The device still works fine but it WILL NOT ROOT!!
I am currently trying to use Odin3 and CF Auto Root (my 100th attempt probably). Every time I use Odin, any version, any tar file, it fails with a "Fail! (Auth)" error. The message in download mode says "SECURE CHECK FAIL: recovery".
I've done a factory reset of the Tab. I've cleared cache. I've tried running Odin is an admin. I've tried different usb ports on my PC (Windows 7, 64bit).
It doesn't matter what I try, it always results in an error. This thing just WILL NOT ROOT!
Can anybody tell me what the problem is? Or another way to root? Please. This is driving me crazy!!
Thank you!!
Try this.
Huge problem
I found these instructions:
droidviews.com/how-to-root-and-install-cwm-twrp-recovery-verizon-galaxy-tab-2-sch-i705-on-ics-jelly-bean/
And finally got it to root. Then I got to the part where I installed the terminal emulator, granted it root access, and followed the instructions to install aboot.img. Then the Tab shut down, I thought it was going to reboot but it never started back up. Now I can't get it to turn on or go into recovery or download mode. Nothing. Everything was fine up to that point. Now nothing at all. How do I fix this??
ninasmith said:
I found these instructions:
droidviews.com/how-to-root-and-install-cwm-twrp-recovery-verizon-galaxy-tab-2-sch-i705-on-ics-jelly-bean/
And finally got it to root. Then I got to the part where I installed the terminal emulator, granted it root access, and followed the instructions to install aboot.img. Then the Tab shut down, I thought it was going to reboot but it never started back up. Now I can't get it to turn on or go into recovery or download mode. Nothing. Everything was fine up to that point. Now nothing at all. How do I fix this??
Click to expand...
Click to collapse
<facepalm>
Oh boy... WHY the heck did you flash a bootloader (totally unnecessary step to begin with) from a completely different device?!?! There is so much info on rooting P31xx here on XDA, describing several different methods in details, and yet you managed not only to find a way that is not even intended for your device, but to proceed with no understanding of the process whatsoever...
I would suggest to take a deep breath, and try again (and again) to get your tab started in download mode (hold Volume DOWN + Power until you see a warning screen). If you can do that, flash the proper ROM with Odin -- whatever version you can find, but the one for your device. Then promise yourself to NEVER do anything without at least a basic understanding of what you are doing.
If you can't get the download mode working, then look up the service centre. You have an option to play dumb and just say it suddenly died on you -- maybe, you get lucky and could claim the warranty.
EDIT: OK, I am really confused now... You specifically said you have a P3100, but you also mentioned Verizon. So, which one is it that you have -- GT-P3100, or SGH-i705??? These are very different devices! If you indeed have an i705, disregard what I said above (it's relevant to P3110), and start with this thread. It may not be as bad after all...
kt-Froggy said:
<facepalm>
Oh boy... WHY the heck did you flash a bootloader (totally unnecessary step to begin with) from a completely different device?!?! There is so much info on rooting P31xx here on XDA, describing several different methods in details, and yet you managed not only to find a way that is not even intended for your device, but to proceed with no understanding of the process whatsoever...
I would suggest to take a deep breath, and try again (and again) to get your tab started in download mode (hold Volume DOWN + Power until you see a warning screen. If you can do that, flash the proper ROM -- whatever version you can find, but the one for your device. Then promise yourself to NEVER do anything without at least a basic understanding of what you are doing.
If you can't get the download mode working, then look up the service centre. You have an option to play dumb and just say it suddenly died on you -- maybe, you get lucky and could claim the warranty.
Click to expand...
Click to collapse
It's not a different device. I have the Tab 2 from Verizon, which is the i705. I thought it was the same as a p3100 but I guess it's not because verizon locks it down more. The model number, listed in settings, is the i705. So I found these instructions and actually rooted it just fine using odin (finally). When it rebooted, I had super user and all was good. Until the part where it told me to do the aboot.img with the terminal emulator.
I have been trying for the past half hour and cannot get it to do ANYTHING. I've held down every combination of buttons and nothing at all. It will not turn on. It will not go into recovery. It will not go into download mode. Nothing. I plug it into the computer and it's not recognized by the PC (because it's not on). I've plugged it into the wall. Nothing. It will not do anything! I don't know what will happen if I try to take this back to Verizon.
ninasmith said:
It's not a different device. I have the Tab 2 from Verizon, which is the i705. I thought it was the same as a p3100 but I guess it's not because verizon locks it down more.
Click to expand...
Click to collapse
It's more clear now, thanks! I updated my post above, before I read your reply. i705 and P3100 are very different, not just because of customizations by VZW, but technically -- different CPU, chipset, radio module, everything.
One thing I can think of is to just leave it plugged in to the wall charger overnight, and try again. You might also want to ask your question in the respective thread that I linked above. But if you really can't get your tab to show any signs of life, you are out of luck, I guess...
BTW, here is another thread for you, related to unlocking the bootloader on i705.
kt-Froggy said:
It's more clear now, thanks! I updated my post above, before I read your reply. i705 and P3100 are very different, not just because of customizations by VZW, but technically -- different CPU, chipset, radio module, everything.
One thing I can think of is to just leave it plugged in to the wall charger overnight, and try again. You might also want to ask your question in the respective thread that I linked above. But if you really can't get your tab to show any signs of life, you are out of luck, I guess...
BTW, here is another thread for you, related to unlocking the bootloader on i705.
Click to expand...
Click to collapse
Thanks. Yeah I tried for about an hour. I had it plugged into the wall. It would not do ANYTHING at all. I took it back to Verizon and exchanged it. Now I just cross my fingers and hope they don't figure it out.
ninasmith said:
Thanks. Yeah I tried for about an hour. I had it plugged into the wall. It would not do ANYTHING at all. I took it back to Verizon and exchanged it. Now I just cross my fingers and hope they don't figure it out.
Click to expand...
Click to collapse
Good that they exchanged it for you. Better luck next time! Read those two threads I linked, it should give you enough info.
BTW, my apologies if I sounded like an a$$. To be fair, you said you had a P3100, and I didn't realize it was actually a different device until I noticed that you also mentioned Verizon. Looks like you tried to do the right thing, but somehow it went sideways. Well, sh!t happens...
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.
I've been getting help in the Newbie thread, but it's time I start a new topic, since it's getting harder and harder to find replies.
All I'm trying to do is upgrade an old LG from Android 5.0 to 6.0. That's it.
I've got the drivers installed. I've downloaded three different versions of Flash Tool. The only one I got to do anything was "Flash Tool 2014".
The first time I ran it (following the directions on the web page where I found it), I picked "CDMA", "DIAG", and "CSE Flash". I was able to pick "Other Country" and "English" and got the phone to start installing. However, it only got as far as 4% and gave me an error. Now, when I run it, I pick "Other Country" and can't even pick a language. They're all blank. If I continue, all the messages consist of Question Marks, however, it still gets as far as 4% before stopping.
The phone is bricked in Download Mode. I have tried two different USB cables, two different computers, one of which has Windows 7 & 8.1 installed. I've tried all different USB ports to make sure I'm on USB 2.0 and not 3.0. I've tried running in Administrator Mode.
I see many posts about the 4% Error. The solution involves downloading a "wx.dll" file and putting it in the C:\system32\LGMOBILEAX\PHONE folder, but that didn't work. I also so one that said when you get the error, take the battery out of the phone, unplug it, put it all back together, and then Continue. That didn't work either.
What else can I possibly do? Thanks.
Hey, I have been trying to find a rom for 6.0 and I can't find anything. The only way to get to 6.0 is through ota. If you have 5.0 then your lucky. Ota can only be used if you still have a sim card that's active in the phone. There isn't roms for stock android 6. I would try and help but I can't.
If anyone finds away to get stock 6.0 please let me know.
Talking about your issue of your phone being bricked, there is many unbrick methods. I personally used https://forum.xda-developers.com/t/...n-qualcomm-hs-usb-qdloader-9008-mode.2933853/ it helped and fixed my issue. I still had my device info wiped off my phone somehow but at least it works. Your at a issue with a flash tool, fresh reflash with that method I sent if you can use it and start over. I can guide you through it if needed.
You might be stuck at a stand still, tell me what your phone says in device manager. You probably flashed a bad firmware. In that case I used the method above.