Related
OK fellas, I have a brand new Captivate. Build is 1102. The phone shipped with 2.2. I bricked the first one so bad I had no choice but to replace it. The second one was almost to that point before I got Odin 3-click to get back to stock 2.1 update 1. Now I'm trying to get back to stock 2.2 and I can't seem to find anything relating on how to do that from my situation. I have literally been up for 38 hours working on this. Took me the first 24 just to get 2.1 on it. I am really stuck here. If anyone has a tool, or a guide, or a hint or a .9mm that can get 2.2 on my phone, please throw me a freaking bone...
Thanks in advance
up for 36 hours isnt going to help.
go get some sleep. come back later.
wait...
you are on your 3rd cappy and still dont know what to do?
Wait so it came with 2.2 you used odin to go to 2.1 and now you wanna go back to where you started?
Ummm ... have you tried kies mini?
When I couldn't use Kies Mini to update my phone from Eclair, I used ODIN 3 (not one click) to upgrade to Froyo - using the image found http://forum.xda-developers.com/showpost.php?p=11526718&postcount=1
My build is 1011
TRusselo said:
up for 36 hours isnt going to help.
go get some sleep. come back later.
wait...
you are on your 3rd cappy and still dont know what to do?
Click to expand...
Click to collapse
Im on my second Captivate. I was actually able to bring it back from brick by building a jig.
@studacris::: It came with 2.2, i flashed a custom rom which was giving me problems, tried flashing back and it failed leaving me with a brick. Built a jig and flashed odin 3-click which put 2.1 on it. I tried to use mini kies but it says my phones firmware is unregistered and will not let me update it...
redneck.nerd said:
Im on my second Captivate. I was actually able to bring it back from brick by building a jig.
@studacris::: It came with 2.2, i flashed a custom rom which was giving me problems, tried flashing back and it failed leaving me with a brick. Built a jig and flashed odin 3-click which put 2.1 on it. I tried to use mini kies but it says my phones firmware is unregistered and will not let me update it...
Click to expand...
Click to collapse
turn on usb debugging before you connect it to kies
i have not tried the following link but I saved the file just in case I needed it. According to the post that I download the file from, it said its supposed to take you back to JI6:
download here
just be careful because I did not test this file myself
Use the jf6(2.1) odin one click and then there is a file you can use in the odin standalone to get you to kb1(2.2).
Sent from my SAMSUNG-SGH-I897 using XDA App
redneck.nerd said:
Im on my second Captivate. I was actually able to bring it back from brick by building a jig.
@studacris::: It came with 2.2, i flashed a custom rom which was giving me problems, tried flashing back and it failed leaving me with a brick. Built a jig and flashed odin 3-click which put 2.1 on it. I tried to use mini kies but it says my phones firmware is unregistered and will not let me update it...
Click to expand...
Click to collapse
Please push *2767*4387264636# or download SGS Tools and select the second option in the Secret Codes section. This will output your product code. If it says anything other than SGH-I897ZKAATT, your product code has probably been tainted, which causes the Kies "unregistered device" error.
The reason this always happened for me is that the product code was changed by the custom ROM. If you do not have a backup of your EFS partition, then correcting this will require a hex editor. I used the method described here - http://forum.xda-developers.com/showthread.php?t=880223 . Messing around with EFS is inadvisable unless you know perfectly what you are doing. (Trust me on this as Sammy has my first phone for this reason alone.) It wont hurt anything to have an incorrect product code, aside from not being able to update to new software through Kies, but if you mess up anything inside of the file that is edited during the process in the forum link listed above, your radio firmware won't know what its own IMEI is. This can cause your phone to stop functioning as a phone.
The first thing that you should do before flashing any ROM is to backup EFS. There is a method for that here: http://forum.xda-developers.com/showthread.php?t=859914 . I backed up EFS using every backup method described there (there are two or three I think), then I copied those backups to every thumb drive and storage device I have. I always have restored using the "tarball" method and have used Kies to get back to 2.2 about 20 times without the "unregistered device" issue.
So the most important question is - Do you have a backup of your EFS? (please say yes) If so, then it is just as simple as restoring EFS.
Another possibility if your redneck.nerdishness extends to Linux usage is to use Heimdall for your Froyo upgrade. I used that on my phone when Kies mini was failing on me. Search for Heimdall in the Captivate and standard Galaxy S forums, then follow the instructions to use it with the stock update.zip file linked in the forums.
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Dr. Light said:
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Click to expand...
Click to collapse
first of all you can't flash anything on a stock recovery hence the need of a custom recovery. Second you don't accept the OTA when rooted as it can cause the exact issue that you have. Last there isn't a way to fix your problem via another android device that I know of.
U are going to need a pc and then u will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery. Then you can access your backups.
Always_Jonezen said:
U will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery.
Click to expand...
Click to collapse
He doesn't have access to his PC PLUS he already knows what to do on that end.
jmxc23 said:
He doesn't have access to his PC PLUS he already knows what to do on that end.
Click to expand...
Click to collapse
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Thanks for all of advice guys. I'll prob just wait it out till Monday. Thanks again.
Always_Jonezen said:
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Click to expand...
Click to collapse
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
jmxc23 said:
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
Click to expand...
Click to collapse
hey all, I've been reading , downloading etc for hours trying to get back into my GS3.. i was as usual roaming around and saw a post that said something to this effect "do ya need to get back to stock?" and figured yes i need to so i jumped in with both feet ..i had my boot loader unlocked and for some reason locked the darned thing remembering it was locked before i rooted and then i get the screen that says ie: "System software not authorized ~~~~~~~~~~~~" with a yellow triangle over it with an "!" mark in it..
all would have been ok except the line up of the way to do things was kinda outta line.. after i had locked bootloader "which is the way the GS3 came" i thought. at any rate i am now where i said i was and if i can be helped it would be appreciated.. and no repeated.. next time i'll read their whole line up first.. so help me if ya can and i am game right now for about anything ..
This should work on all Qualcomm Snapdragon based Samsung galaxy SIII's, if it doesn't, PM me the model and I'll try and find a solution.
WHILE THIS IS VERY LIKELY TO WORK FOR ANY BOOTLOADER/MODEM/FIRMWARE BRICKED PHONE, THERE IS NO UNCONDITIONAL GUARANTEE THAT THIS WILL WORK FOR YOUR PARTICULAR SITUATION, THERE IS A POSSIBILITY THAT THERE ARE SOME BRICK STATES THAT THIS WILL NOT WORK FOR, but in my experience, almost all cases can be resolved by rewriting the sdcard with correct partitioning.
Disclaimer out of the way, let us begin.
Needed Materials and Files:
EDIT: if you have another phone or know someone else with the same phone have them run this and the output will be a debrick image you can use: busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=200 if it does not work then change the last number (count=) to something larger and try it. If you create an image please upload it so I can put it into a repository I'm creating
16GB or 32GB class10 microSD card
A hard bricked Samsung galaxy S3 US Cellular
The debrick image for your device:
[[Here is the drive image for a folder containing all the debrick images that I currently have uploaded, more will be coming: https://drive.google.com/folderview?id=0B612qYHFMILfWUlMTTEwdUstcXM&usp=sharing ]]
If you have any images that I missed, please send me a link or, better yet, upload them to drive, make them publicly shared, and share them with me at [email protected], I will put them in this folder for all to use
US Cellular R530: ftp://sdbruington.us/d2usc/SCH-R530_ALIVE_MJA_200MB_16GB.bin
Sprint L710: http://www.mediafire.com/download/23...ph_l710.img.xz
AT&T I747: http://d-h.st/iEy
T-mobile T999: http://www.mediafire.com/download/gr...k_SGH-T999.img
---I did not upload these images, I have simply collected the links over time, please thank Cnexus for his help in finding these and
---helping me to originally unbrick my S3
Your computer
A card reader that will accept the card (another phone will not work as this is an image, and it needs to repartition the SD card)
Either a partition editor (I've heard that you can use dd or something on linux, but I haven't tried) or this: View attachment win32diskimager-v0.9-binary.zip
A wall charger (computer charging isn't as reliable)
Procedure:
1. Take the sdcard and insert it into your computer
2. Download the mentioned image and the software to put it onto the sdcard
3. Use your computer to pull the data already on the card onto your computer hard drive, as the sdcard will be wiped when the image is put onto it
4. use the software that you downloaded earlier to burn the image to the sdcard
5. Remove the battery from the SGS3
6. insert the sdcard into the S3
7. Put the battery into the S3
8. The S3 may boot automatically, or you may have to manually boot it by holding down the power button for 5< seconds
9. If the update that bricked your phone also messed up /system, then you'll have to coerce Odin mode to shove a stock firmware image to your phone, though I've had more than just SOME trouble with that in the past (in other words I haven't been able to get back to stock yet...), if you simply had a radio update or something go wrong, then proceed to the next step.
10. Do a victory dance with your phone in your pocket not the repair bench, or on second thought, make sure you don't drop it, don't create another problem.
11. After that, you can just use your device normally with the sdcard in it without worry of bricking it, though it will not be able to boot if you remove the sdcard;
the only known method of getting it to boot without the sdcard is reflashing stock firmware, which completely wipes the phone and resets everything back to complete stock. Also, Odin mode has, at least for me, objected when I've tried to flash the stock image back onto it, and even if Odin mode was sure of working, backing up ~16GB of data isn't a fast process, especially with the most reliable means being ADB. If you try to flash a stock image and it fails, your device will almost definitely come up with a version of dmode when you try to turn it on with the sdcard (still bricked otherwise) that says something about Kies update failure, the only way of correcting this that I've had success with is flashing an image that won't do much, such as the same recovery that you already had, over odin mode from that special dmode, as while that won't correct the actual brick, it will at least make you able to boot from the sdcard again. I will provide links to the stock images in a little while, once someone gets that far, as I will have to find all but the one from the US Cellular version.
I am currently looking for firmware images that will only flash the bootloader/modem, if anyone knows of an odin file that could do that, please let me know as soon as possible, in the meantime, I will try and create an update.zip that will flash the necessary files; as most bricks are likely cause by an update.zip that was meant for a different device, I am very confident that it can be fixed with another .zip file.---Stay tuned!
---Don't forget, that thanks button won't bite your finger off if you push it:fingers-crossed:
If any of the links are not fully functional, PM me to let me know, and if you have the link to another debrick image for another device, send me the link so I can include it here!
Please note: While there is a similar procedure for Xynos based S3's, they apparently require a physical modification that requires an amount of soldering, so it is most likely best for them to simply take them in for Jtagging and then just not brick them after that.
EDIT: here is the link to a full youtube tutorial that I made, just for those of you who like watching a video instead of getting lost in a written guide https://www.youtube.com/watch?v=-RTAbLBVfMI
EDIT AGAIN: I'm sorry about both of the mediafire links being down, I will try and find some more and upload them to my google drive, along with the others just to make sure they exist somewhere safe.I'm downloading the images now and uploading some that I already have, they will be available in this folder (https://drive.google.com/folderview?id=0B612qYHFMILfWUlMTTEwdUstcXM&usp=sharing) on google drive and will be available by email upon request
here is a sprint image that should work, sorry I haven't tested it http://www.mediafire.com/download/231uhy6l80jx74n/debrick_sph_l710.img.xz
for the t999 4.1: https://www.copy.com/s/xSAswQZbhQX8/t999_debrick.zip for the t999 4.3: https://www.copy.com/s/7ICfKXMC3ccr/T999_4.3_debrick.zip
I know this is becoming a mess of links but here is a link to an xda post that has t999 variant images http://forum.xda-developers.com/showthread.php?t=2439367
here is a sprint 4.4 debrick image: http://www.androidfilehost.com/?fid=23329332407591176
If you want to get your phone to operate without an sd card in there for every boot, stay tuned, I'll have a guide to return to stock soon, though a quick google search shouldn't be that hard if you're desperate
I will clean up this guide in a little bit but currently I have school and such to attend to so it may not be immediate
I know this is getting unwieldy but (big thanks to youdoofus) I have a way to completely debrick and fix it so it doesn't require even the sd to boot.
"Restoring stock bootloader
1) You were able to boot into the ROM
2) Plug your phone into a computer and use MTP mode
3) Move the debrick file onto your internal sdcard (/sdcard/debrick.bin)
4) Disconnect your phone
5) Open up a Terminal Emulator on your phone and input this code
Code:
su
dd if=/sdcard/debrick.bin of=/dev/block/mmcblk0
6) Reboot"
Of course this should be modified for the different versions and types of debrick image as some are img, some are bin, I think there might even be an ISO hanging around somewhere
EDIT: As of October 10th I'm working on a tool that will get an image directly from a stock rom/tar and put it on the SDcard. This is pretty complex so it will probably take a little while, but it should make it easier to get images if all that's required is a stock tar.
I've followed all these guides and haven't had any luck. I did use a CM 4.4 rom and some people are saying i need a debrick.img of a 4.4 to get it working again. i'm on an i-747. can you help?
derget1212 said:
I've followed all these guides and haven't had any luck. I did use a CM 4.4 rom and some people are saying i need a debrick.img of a 4.4 to get it working again. i'm on an i-747. can you help?
Click to expand...
Click to collapse
You don't need a debrick.img of a 4.4 to get it working, you need a debrick.img of the correct bootloader. If you bricked your phone by flashing an older bootloader after upgrading to the 4.3 bootloader, then you need a debrick.img with the 4.3 bootloader.
polobunny said:
You don't need a debrick.img of a 4.4 to get it working, you need a debrick.img of the correct bootloader. If you bricked your phone by flashing an older bootloader after upgrading to the 4.3 bootloader, then you need a debrick.img with the 4.3 bootloader.
Click to expand...
Click to collapse
how do i find out the correct bootloader? i was using this rom http://forum.xda-developers.com/showthread.php?t=2518998 for a couple months and randomly got hard bricked yesterday. any help is greatly appreciated.
Thanks for sharing this
derget1212 said:
how do i find out the correct bootloader? i was using this rom http://forum.xda-developers.com/showthread.php?t=2518998 for a couple months and randomly got hard bricked yesterday. any help is greatly appreciated.
Click to expand...
Click to collapse
Explain your situation. Randomly bricked is very vague. Did you flash anything? Do you remember doing anything? It's important. Phones don't go and "randomly brick" unless of a HW problem, and to either confirm or eliminate that possibility we need more details.
polobunny said:
Explain your situation. Randomly bricked is very vague. Did you flash anything? Do you remember doing anything? It's important. Phones don't go and "randomly brick" unless of a HW problem, and to either confirm or eliminate that possibility we need more details.
Click to expand...
Click to collapse
Like i said, it was totally random. My phone froze and rebooted yesterday. It got to the Samsung logo so i thought everything was okay. I fell asleep and woke up to a bricked phone. After all of my attempts, I got one debrick.img to show something on my screen and it shows "BOOT RECOVERY MODE". Odin sees my phone and tries to fix the PIT and the Bootloader but it always fails. From what i gather, it seems to be a hardware issue.
derget1212 said:
Like i said, it was totally random. My phone froze and rebooted yesterday. It got to the Samsung logo so i thought everything was okay. I fell asleep and woke up to a bricked phone. After all of my attempts, I got one debrick.img to show something on my screen and it shows "BOOT RECOVERY MODE". Odin sees my phone and tries to fix the PIT and the Bootloader but it always fails. From what i gather, it seems to be a hardware issue.
Click to expand...
Click to collapse
Whoa whoa there, if your phone still boots in either recovery or download mode, then you don't need to use a debrick.img.
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM using ODIN in download mode.
polobunny said:
Whoa whoa there, if your phone still boots in either recovery or download mode, then you don't need to use a debrick.img.
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM using ODIN in download mode.
Click to expand...
Click to collapse
It is hard bricked. Without the sd with a debrick.img installed, I get no response at all. And I've tried all the i747 debrick.img files I could find here with no success.
I can get to boot recovery mode with one .img I could find but boot recovery os different than recovery mode. It's essentially useless and Odin doesn't like it.
derget1212 said:
Like i said, it was totally random. My phone froze and rebooted yesterday. It got to the Samsung logo so i thought everything was okay. I fell asleep and woke up to a bricked phone. After all of my attempts, I got one debrick.img to show something on my screen and it shows "BOOT RECOVERY MODE". Odin sees my phone and tries to fix the PIT and the Bootloader but it always fails. From what i gather, it seems to be a hardware issue.
Click to expand...
Click to collapse
It really sounds a lot like the BRICKBUG to me, anyone know how to tell if a chip is insane without it working? And did you have the 4.3 bootloader? If you got that you should have been safe, but if you didn't then the kernel may have burned out the chips from the "bug" (it really doesn't seem too much like a "bug", more like an issue worthy of recall)
Sorry I don't know exactly what's wrong off the top of my head
derget1212 said:
It is hard bricked. Without the sd with a debrick.img installed, I get no response at all. And I've tried all the i747 debrick.img files I could find here with no success.
I can get to boot recovery mode with one .img I could find but boot recovery os different than recovery mode. It's essentially useless and Odin doesn't like it.
Click to expand...
Click to collapse
If you get ANY response at all, then the debrick image is doing its job; what you need is a stock image, I'll try to find a link for you to use. Try using Kies or something, alternatively, as if you have the serial number you can apparently flash it quite cleanly, all data on the phone will be lost though, as it effectively wipes the eMMC.
polobunny said:
You don't need a debrick.img of a 4.4 to get it working, you need a debrick.img of the correct bootloader. If you bricked your phone by flashing an older bootloader after upgrading to the 4.3 bootloader, then you need a debrick.img with the 4.3 bootloader.
Click to expand...
Click to collapse
Exactly
This image gets you in the clear if the ONLY thing screwed up is the boot partition, meaning modem/firmware/bootloader, it does NOT get you fixed if you got your rom F***ed up, and do not expect it to, this will get you into dmode so you can use odin or something like fastboot to flash a /system image or a FULL stock rom if you want to get your bootloader fixed without the SD card being in all the time.
dreamwave said:
If you get ANY response at all, then the debrick image is doing its job; what you need is a stock image, I'll try to find a link for you to use. Try using Kies or something, alternatively, as if you have the serial number you can apparently flash it quite cleanly, all data on the phone will be lost though, as it effectively wipes the eMMC.
Click to expand...
Click to collapse
if anyone can find the correct debrick.img i need to use, i would greatly appreciate it. I have tried Kies and Odin without success. They can see the phone but seem not to be able to access it. I can't flash anything via odin or get to the CWM recovery or download mode. this is a really weird screen i haven't seen before.
derget1212 said:
if anyone can find the correct debrick.img i need to use, i would greatly appreciate it. I have tried Kies and Odin without success. They can see the phone but seem not to be able to access it. I can't flash anything via odin or get to the CWM recovery or download mode. this is a really weird screen i haven't seen before.
Click to expand...
Click to collapse
Is there any way at all to get into dmode? What is windows recognizing it as?
Thanks for sharing.
EvangelineX said:
Thanks for sharing.
Click to expand...
Click to collapse
no problem, I hope it helped!
derget1212 said:
I've followed all these guides and haven't had any luck. I did use a CM 4.4 rom and some people are saying i need a debrick.img of a 4.4 to get it working again. i'm on an i-747. can you help?
Click to expand...
Click to collapse
If you bricked the /system partition AND the boot partition you will need a stock rom as well, just use Odin or something if possible after using a 4.3 image, a 4.4 image is more or less the same as a 4.3 as far as I know, I mean I bricked mine after using cm11 by flashing the wrong rom, it's just that the rom you tried tried to flash a 4.1 bootloader, and thus tripped the eFUSE or something in the Knox bootloader, what you need is a 4.3 unbrick image, as 4.4 didn't really change the modems/bootloader from 4.3, and the unbrick image isn't really that much more than a collection of pieces from the boot partition that are used as an autoboot by the phone when the eMMC fails to load properly.
This is pretty neat..
does it always work?
It's nice to have such a recover method whenever something like this happens to you.
halfdead1993 said:
This is pretty neat..
does it always work?
It's nice to have such a recover method whenever something like this happens to you.
Click to expand...
Click to collapse
I believe it will work on basically anything, as in I haven't seen a case that can't be cured at least somewhat by this, I think it works like an alternative boot, as if the bootloader on the eMMC is corrupted, it seems to remove the boot flag, thus making it so that the phone does not detect a bootable partition, the unbrick image has a partition layout mirroring the one that is supposed to be on the phone, so it is used as the boot partition but then redirects control back to whatever is on the eMMC after the bootloader, think of it as a liveCD on windows, just one that hands control back to the system after it has gotten past booting the BIOS.
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 bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
I know more about Motorola Droid phones. This is phone is new to me. I did do a lot of research out there and mainly on XDA. I have the option to return the phone for a full refund. I would like to see if I can fix the phone before hand. I have till this weekend to send it back.
Claps1775 said:
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
Click to expand...
Click to collapse
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Droidriven said:
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yes and yes. Okay. I know with droids when I was bootloader locked and rooted. I was fine updating. There was a change on loosing root. It's all about learning. I will try to find out how to unblock my phone. Thank you for the response.
Have you came across the ota .IMG file?
I was able to power my phone off. I connected the phone to my computer, installed the software, and tried the repair part. Failed on downloading. Version on my phone is 1.102VZ.
I found more info on xda refuring to the http://4pda.ru/forum/index.php?showtopic=597313&st=3680 site. I am not able to do anything with my phone now. Cannot get it to boot in recovery or even have my pc see it. The verizon apk sees it where I can still try to repair or update. That is it. I am going to send it back for a full refund and be done with this phone. Cannot spend weeks trying to fix this right now. Thanks all for the help.
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
I was able to flash the Rom_5.1.1_3153LR_Modem_3153LR_E6782 and my phone booted up and went into the optimizing but it is in Russian. I am further than I was. Need to find out if this is changeable to English and it all works. Yes, I do know that I will not flash anything than 5.0 now since the bootloader is locked or it can be unlocked with a code. Phone is up and running. I need a 5.1.1 US now.
It is not in Russian. It is in vietnamese. But I still need a clean 5.0 full rom.
Claps1775 said:
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
Click to expand...
Click to collapse
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I will try that. I have to get it into fastboot and that can take a few tries. The firmware I have on it has no verizon apps. It is a mod by someone. I am going to try original firmware 5.1.1 firmware. Downloading right now. it is a .rar file. Making head way witch is good. I am learning for sure.
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Claps1775 said:
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Click to expand...
Click to collapse
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Claps1775 said:
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Click to expand...
Click to collapse
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Claps1775 said:
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Click to expand...
Click to collapse
When some, lose some.
For future reference, when you want to update or modify a device, try doing some research into what NOT to do or what can go wrong with that particular device and how to fix it if it does BEFORE you focus on what CAN be done on that device and before you actually do anything to the device. Cover the bases, ask questions, search for issues others might have had when they modified their device.
Remember, just because something is available for that device, doesn't mean you can use it. Things change from android version to android version and this stock firmware to that stock firmware for a device, such as whether the bootloader is locked or unlocked, among other possible differences that can turn things into a train wreck.
Android devices are all different and are not all done the same. What and how it is done on "this" device is not the same on "that" device.
Sent from my SM-S903VL using Tapatalk