Ok, here it goes: I have tried searching for the answer, and haven't quite found the answer that pertains to my situation. I recently flashed Obsidian on my Vibrant and decided to revert back to my backed up stock rom using ClockworkMod Recovery app. My phone then failed to boot past the Vibrant/Samsung screen. I have tried to get into recovery, but the phone only stays on Vibrant/Samsung screen and fails to go to recovery screen. No matter what method is tried to get to recovery, the phone gets stuck on the Vibrant/Samsung screen and will not boot past that or go to recovery. This being said, my question is: When my phone goes back to T-Mobile for warranty, will they be able to tell if its rooted if it doesn't boot and can't get to recovery? Or will they just do their thing and reflash the stock rom thus wiping any evidence?
BULLITT3200 said:
Ok, here it goes: I have tried searching for the answer, and haven't quite found the answer that pertains to my situation. I recently flashed Obsidian on my Vibrant and decided to revert back to my backed up stock rom using ClockworkMod Recovery app. My phone then failed to boot past the Vibrant/Samsung screen. I have tried to get into recovery, but the phone only stays on Vibrant/Samsung screen and fails to go to recovery screen. No matter what method is tried to get to recovery, the phone gets stuck on the Vibrant/Samsung screen and will not boot past that or go to recovery. This being said, my question is: When my phone goes back to T-Mobile for warranty, will they be able to tell if its rooted if it doesn't boot and can't get to recovery? Or will they just do their thing and reflash the stock rom thus wiping any evidence?
Click to expand...
Click to collapse
Another person trying to scam a company..
That being said, It is a 50/50 chance of them knowing, and I hope they do know.
Why dont you odin back to stock and not claim a warranty exchange for something that is your own fault
Sent from my SGH-T959 using XDA App
Go to the Vibrant android development section and look for the vibrant bible.
once there read up on using ODIN.
USE IT.
Than put down the phone and never flash a rom again until you learn to read directions.
oh and by the way, how bout you NOT try and scam ppl cuz you cant follow simple directions. going to tmobile and filing a claim is BS. YOU are the one responsible for your phone no longer working. Ppl wonder why prices on data plans and other costs go up. They have to keep paying out the ass on other crap that could easily have been avoided had the end user had any durn sense
BULLITT3200 said:
Ok, here it goes: I have tried searching for the answer, and haven't quite found the answer that pertains to my situation. I recently flashed Obsidian on my Vibrant and decided to revert back to my backed up stock rom using ClockworkMod Recovery app. My phone then failed to boot past the Vibrant/Samsung screen. I have tried to get into recovery, but the phone only stays on Vibrant/Samsung screen and fails to go to recovery screen. No matter what method is tried to get to recovery, the phone gets stuck on the Vibrant/Samsung screen and will not boot past that or go to recovery. This being said, my question is: When my phone goes back to T-Mobile for warranty, will they be able to tell if its rooted if it doesn't boot and can't get to recovery? Or will they just do their thing and reflash the stock rom thus wiping any evidence?
Click to expand...
Click to collapse
Can people ever take responsibility for their acts? The warnings posted on all the ROM threads are there for a reason. If you cannot bring your phone back to live with the information available online including these forums just suck it up, be a man.
I know I should take resposibilty for my own actions, but when a phone is supposed to be able to boot into recovery by using the 3-button method, but that method isn't funtioning because Samsung disabled it (like many other people have experienced) how do I take responsibilty for equipment that doesn't do what its supposed to? When the phone doesn't boot into recovery like it is supposed to, how do I fix my own actions. My brick is partly my fault and I know that, but partly a faulty phone.
BULLITT3200 said:
I know I should take resposibilty for my own actions, but when a phone is supposed to be able to boot into recovery by using the 3-button method, but that method isn't funtioning because Samsung disabled it (like many other people have experienced) how do I take responsibilty for equipment that doesn't do what its supposed to? When the phone doesn't boot into recovery like it is supposed to, how do I fix my own actions. My brick is partly my fault and I know that, but partly a faulty phone.
Click to expand...
Click to collapse
Not at all! They released a fix for that (JI6)
You were the one who bricked your phone & are trying to scam T-Mobile.
Adb into download mode, use odin, flash to stock
Sent from my SGH-T959 using XDA App
Master™ said:
Not at all! They released a fix for that (JI6)
You were the one who bricked your phone & are trying to scam T-Mobile.
Click to expand...
Click to collapse
So if J16 was supposed to fix that, why was it that even T-Mobile couldn't get it to boot into recovery?
BULLITT3200 said:
So if J16 was supposed to fix that, why was it that even T-Mobile couldn't get it to boot into recovery?
Click to expand...
Click to collapse
Ok, first off, you bricked it because JK2 and JI6 or any 2.1 version run on different kernels, and clockwork doesnt install kernels (and this is why you can't go into recovery, not because the phone is faulty.). I did this before and ODIN will fix it right up. Use it.
It will only take about an hour to get everything back the way you want rather than waiting a week or so. No need to file a warranty complaint, this is your fault but very easy to fix.
BULLITT3200 said:
So if J16 was supposed to fix that, why was it that even T-Mobile couldn't get it to boot into recovery?
Click to expand...
Click to collapse
Because YOU modified your phone, and messed up!
Odin will fix one of your problems. The other can't be fixed...
recovery won't do you any good because it needs the kernel to load.
you need download mode.
with the phone completely off and not connected to the computer, press and hold the vol + and vol - buttons at the same time. then plug in the usb and you'll boot into download mod.
You then go about flashing w/ odin to get your phone working again.
Related
So, I was in the recovery mode and accidently bumped the power button when it was on "delete davlick cache" or something similar and now the phone goes to the galaxy s screen, hangs a while, and the screen goes blank and will not load. The buttons do light up still however. I have tried the odin steps to repair a soft brick using odin 1.0 and 1.3 and I have tried both JVD and JI6, nothing will get the phone going. I have followed the directions to a T so I am wondering if anyone else has any ideas. FYI I have spent the last 3 hours reading and trying methods already described, which is why I am posting a new thread. Thanks in advance for any help.
Can you get into download/recovery mode?
Does Odin recognize it when you plug it into the computer?
Were you trying to flash something when this happened (i.e. why were you in recovery mode in the first place)?
A little more information never hurts =)
~SB
sounds like exactly what happened to me, you'll have to go into download mode and use odin to fix it.
I have the same issue. It happened after I received a T-Mo ota update. I've cleared everything I can find to clear. I can get into recovery mode, but when I select the reboot option nothing changes. Anyone have a link to a walk through that a novice could understand? One with nice little things like links to the programs/files necessary? Thanks in advance.
ok this also happened to me i used this to return to stock and everything came back fine.
since i cant yet post a link i provided the thread # paste it to the end of the address in your browser.
/showthread.php?t=803492
forum,xda-developers,com/showthread.php?t=803492
replacing the ,'s with .'s
Try using eugene's froyo that does not brick w/ odin
Sent from my SGH-T959 using XDA App
I tried flashing back to the orginal stock t-mobile rom (JFD) through odin but no luck after multiple attempts. I finally just brought it to a t-mobile store and the are sending a replacement. I was fully prepared to take my lumps if they told me it was my problem but since they want to replace it I'm okay with that too. I still have the phone and am going to try some of the other steps that you guys listed before I send it to T-mobile. I was actually partitioning my sd card with the rom manager app and while in recovery I accidentally bumped the power button while "clear davlick cache" or whatever was highlighted. Next thing you know I don't have a working phone. I'm not sure exactly what that does but I do know it messed up my phone. This isn't the first time I've modded phones, did a lot of flashing on my old G1 and Wing and never had anything like this happen.
Oh and I was able to get a good connection with odin, it stated it was successful everytime I tried flashing back to the stock rom but it never fixed the problem.
When I bricked my phone I made sure the insurance company couldn't tell I modded it. Vibrant's don't do to well falling down stairs lol
Sent from my SGH-T959 using XDA App
Joshochoa187 said:
When I bricked my phone I made sure the insurance company couldn't tell I modded it. Vibrant's don't do to well falling down stairs lol
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I didn't go through insurance, T-mo is just replacing it through the warranty. I started to sweat a little when they booted it into recovery mode thinking the tech guy was going to ask the rep at the store to give him the info that comes up to see if it was rooted or modded but the tech just had him clear the phone data and reboot and when that did not work they went ahead and sebt one out. I wouldn't have complained if they told me I was SOL since it was a risk i was taking but I also don't feel bad as they are charging me $10 dollars more a month then I was quoted after my upgrade and I am not sure if I want to go through the hassle of putting in a complaint through the Attorney Generals office. this just may be my payback.
Got it fixed!!!!!
Just got my phone running! Follow the steps in this thread, you first download eugenes froyo and flash to your phone through odin and then immediately flash stock 2.1 through odin and your phone is fixed. I am so happy right now!
Here is the thread with full instructions:
http://forum.xda-developers.com/showthread.php?t=745547
Okay, so after installing the kang build 25 ICS for the vibrant, everything went fine. Randomly I get a random reboot and my phone says there was an "encryption error" and that I have to do a factory reset. Since I already had everything backed up, I didn't mind the data wipe. When it went rebooted the CWM screen came up and started wiping everything but when it got to the "formatting data" part, it failed. I tried this many times and it kept failing... SO, I decided to ODIN back to JFD. After doing so, all I get is the Vibrant screen, then an instant shut down. I even tried Eugene's old No Brick Froyo PDA, then tried to reinstall the JFD image, but got no luck.
Question is: What should I do now?
Any help will be GREATLY appreciated. Thanks!
Its a little involved but It's all I could find to help buddy
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Perhaps it could be a bootloader problem? If you're sure you are doing Odin right, including repartition with the pit file, you could look at your SBL.
.
Sorry but what is SBL?
lolrus101 said:
Sorry but what is SBL?
Click to expand...
Click to collapse
I dont know how to explain it very well lol but to check if the rom you are trying to odin has the sbl in it. Rename it and put a .zip at the end. Then extract to see if its in there it should be named "sbl". To change it back simply delete the .zip off the original file.
JFD
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Try odining a rom that has the sbl file in it thats probably why its not working.
---------- Post added at 04:14 AM ---------- Previous post was at 04:09 AM ----------
Here http://forum.xda-developers.com/showthread.php?t=1278683 you need to have java installed to open it
Just tried the Heimdall thing. No luck. As soon as it says rebooting, it goes to the vibrant screen, then the battery charging screen, then continues to bootloop. Same thing happened with Odin
why don't you try what I did
http://forum.xda-developers.com/showpost.php?p=23056603&postcount=10
lolrus101 said:
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Click to expand...
Click to collapse
The SBL is the Secondary Boot Loader, which is loaded by the Primary Boot Loader.
I haven't personally encountered any roms which also flash bootloaders.
I did manage to get my phone bootlooped in some weird way which apparently could only be fixed by reflashing the SBL. Note: flashing bootloaders is more dangerous than regular roms.
I am presently running a GB SBL from this thread:
http://forum.xda-developers.com/showthread.php?t=1117990
ian577416 said:
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Click to expand...
Click to collapse
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Flashed the GB bootloader and no luck either . Flashed back to the froyo one, and got the data wipe error again, the phone rebooted, and now its at "KERNEL PANIC - UPLOAD MODE"
AdamOutler said:
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Click to expand...
Click to collapse
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
lolrus101 said:
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
Click to expand...
Click to collapse
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
cashmundy said:
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
Click to expand...
Click to collapse
SO the thing is I used the GLITCH kernel with vibrant build 25... I dont think I was supposed to... could that have caused the problem? maybe a voodoo problem?
There are two glitch kernel series that I know of, one for CM7 and one for CM9 and ICS (I think, not sure, that all ICS builds and CM9 use the same basic filesystem scheme).
All stock builds use a Samsung FS scheme which is different from the two above. So there are at least three mutually-incompatible families of FS+kernel pairs.
I used the CM9 kernel I think...
After the installation went fine, I got the encryption error which told me to reboot. as soon as I did, I got the Data wipe fail. Any ideas?
Encryption Error
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
tabthelab said:
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
Click to expand...
Click to collapse
If you are still able to access Clockworkmod Recovery CWM (NOT STOCK RECOVERY) then try this:
http://forum.xda-developers.com/showthread.php?t=1447303
Otherwise just give up. There is currently no fix for this bug as of now.
This is really getting out of hand ICS rom devs should put a big caution sign on their thread(s) stating the following:
WARNING THIS ROM WILL BRICK YOUR DEVICE!!!
Goodluck... in the meantime find yourself a spare phone like i did cuz you certainly ain't fixing this one.
Sent from my Galaxy Nexus using XDA
mother of god
I hope this helps you. I finally, after hours of nothing, tried to use Odin to flash to 2.2 froyo. cha ching. got in.
tar file I used here: http://forum.xda-developers.com/showthread.php?t=833024&page=49
worked for me. I hope it helps you
I have an I777, I did a factory reset, and when it rebooted, I got the Galaxy sII image, but then just a black screen for 30 mins. I pulled the battery out, and now when I boot it, the SGSII logo appears, but just a black screen comes up. I can boot it into download mode by plugging it in by usb/vol rocker down. Did I brick it?
More info is needed for this...... Rooted? Stock rom or custom?
Michael3214 said:
More info is needed for this...... Rooted? Stock rom or custom?
Click to expand...
Click to collapse
I had been running a rom for months, decided to try another, got that installed just fine (ICS) but was having some other minor issues (kies wouldnt connect etc) so i did a factory reset and thought I would just start fresh. On reboot to perform the reset it hung on a black screen.
Update, as of now I have used ODIN to flash CWM back on and gotten into recovery mode.
Do you have a nandroid backup from the original rom you were running? The ICS rom you installed, was it one of the leaks?
I would have made one, yes, but I don't have that computer any more (died). I had made one today before installing the rom, but I can't access it, it is on the phone
1c0n said:
I would have made one, yes, but I don't have that computer any more (died). I had made one today before installing the rom, but I can't access it, it is on the phone
Click to expand...
Click to collapse
If you made a nandroid backup, you obviously have CWM recovery, right? Can you get into recovery mode by vol up + vol down + power, without being plugged in?
unfortunately no, the phone wouldn't do anything other than the SGSII screen, then black. I'm downloading the stock .tar file now and intend to just use odin to put it back to factory and start again
Check out Entropy512's Thread in Development regarding [Odin][Stock][Root]UCKH7/KK6 Return/Unbrick to Stock (or Root), any other files can be found in there. Its saved me many times.
thanks, that is exactly where I found everything, figure if i'm gonna keep buggerin with this phone, keeping those on the new computer can't hurt!
You weren't running one of the ATT ICS leaks were you? The "stock" ones come with a nice "feature" that can corrupt your internal memory and brick the phone when a wipe happens....
If your Odin back to stock doesn't work, this could be the case.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
no, thankfully, and i just finished. With success, I am back to 100% stock, with the counter set to NO and my bootloader back to the i777. thanks for the help, panicked a bit. I am comfortable flashing roms with ODIN, I wasn't expecting it to hang using the built in restore feature, luckily it was minor.
Now to get CWM back, backup, and try some more ROMS
ICS AOSP question, my phone wont connect to kies to restore my phone but it does with stock/gingerbread roms i have tried
1c0n said:
no, thankfully, and i just finished. With success, I am back to 100% stock, with the counter set to NO and my bootloader back to the i777. thanks for the help, panicked a bit. I am comfortable flashing roms with ODIN, I wasn't expecting it to hang using the built in restore feature, luckily it was minor.
Now to get CWM back, backup, and try some more ROMS
ICS AOSP question, my phone wont connect to kies to restore my phone but it does with stock/gingerbread roms i have tried
Click to expand...
Click to collapse
thats a statemnent, not a question.
and IRRC your correct. but Odin, and Kies, are both things that are not used often.
Odin, should just be used to get back to stock. Kies....well IDK what that even does, but its from samsung. so it sucks.
Odin should not be used as a tool to flash ROMs.
that indeed was a statement, somehow the end of my question got cut off, either on my computer, or, more than likely, in my head. anyways, i don't use kies ever, I only used it as an easy way to back up all my contacts, calender etc, which now i cannot retrieve
Yeah from the little I've used it, Kies is just a browser based backup app, but only for pics/music/etc. I think OS updates come through it but there's nothing like CWMs restore/backup options..
I actually uninstalled it on my Mac cause it prevents Heimdall (a Mac version of Odin) from properly connecting to my phone.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
yeah, it is useless for anything else
1c0n said:
that indeed was a statement, somehow the end of my question got cut off, either on my computer, or, more than likely, in my head. anyways, i don't use kies ever, I only used it as an easy way to back up all my contacts, calender etc, which now i cannot retrieve
Click to expand...
Click to collapse
Sorry man but contacs, calender? really? do you not know that google keeps that stuff for ya?
I do, but i didnt have reliable access to the internet earlier
1c0n said:
I do, but i didnt have reliable access to the internet earlier
Click to expand...
Click to collapse
Have you looked into using MyBackup to back up that stuff?
1c0n said:
no, thankfully, and i just finished. With success, I am back to 100% stock, with the counter set to NO and my bootloader back to the i777. thanks for the help, panicked a bit. I am comfortable flashing roms with ODIN, I wasn't expecting it to hang using the built in restore feature, luckily it was minor.
Now to get CWM back, backup, and try some more ROMS
ICS AOSP question, my phone wont connect to kies to restore my phone but it does with stock/gingerbread roms i have tried
Click to expand...
Click to collapse
I am in the same situation. Could yould tell me how to un brick your phone? Thank you so much?
Please help
1c0n said:
I have an I777, I did a factory reset, and when it rebooted, I got the Galaxy sII image, but then just a black screen for 30 mins. I pulled the battery out, and now when I boot it, the SGSII logo appears, but just a black screen comes up. I can boot it into download mode by plugging it in by usb/vol rocker down. Did I brick it?
Click to expand...
Click to collapse
I am having the same problem. I rooted my Samsung i777 and then decided to factory reset it. I did and it went blanked with a black screen and did not want to turn on. Please help.
Not paying attention while updating supersu has led to my s2(i777) not being usable. Updated binary selecting wrong option and and phone would not boot past the splash screen. At this point I used creepyncrawly's I777UCKH7-CL5038881-No-Bl.exe to return to factory settings. Was able to do this using battery pulls to turn off and on and enter download mode. Appeared all was going to work but now phone will not boot past initial setup screen. Can get into recovery but unable to enter selection as power button not working at this point even though I use it to get into factory recovery. About to flash stock sbl.tar (downloaded from repository) using Odin but decided I should probably get some feedback first.Phone was running Semi_v18 and Siyah 3.3.3d and working well B/4 I messed things up.
I have no idea what gets changed or corrupted when you have a problem updating supersu. Maybe you could go to chainfire's supersu thread and see if you can get an idea what it might be.
Your thinking may be right though, because the sbl seems to be the place that controls power and volume button actions.
creepyncrawly said:
I have no idea what gets changed or corrupted when you have a problem updating supersu. Maybe you could go to chainfire's supersu thread and see if you can get an idea what it might be.
Your thinking may be right though, because the sbl seems to be the place that controls power and volume button actions.
Click to expand...
Click to collapse
Thanks Creepy, been to the other thread nothing helpful from reading responses to others posting wih the same problem. I'm just going to flash sbl.tar with Odin unless you think it may just cause a bigger problem.
It should be no problem to flash it as long as the flash doesn't get interrupted. If the sbl is not damaged, it won't do any harm to re-flash it.
creepyncrawly said:
It should be no problem to flash it as long as the flash doesn't get interrupted. If the sbl is not damaged, it won't do any harm to re-flash it.
Click to expand...
Click to collapse
Thanks, flash went fine but no go on getting power button to work in recovery. Not sure what to try next but maybe flashing rom and kernel from odin. Any way thanks again.
GJMX said:
Thanks, flash went fine but no go on getting power button to work in recovery. Not sure what to try next but maybe flashing rom and kernel from odin. Any way thanks again.
Click to expand...
Click to collapse
Just wanted to let you know what happened with S2. Took a long shot and called at&t cs.
After 2 calls to at&t and 2 to Samsung tech support I got lucky on the third cal to at&t and the rep set up a
free appointment at a nearby device support center. Guy there said all he could do was to wipe the phone and
install ICS 4.0.4. Phone works now but seems the power button stopped working at the same time I messed up the update.
Need a new power button, rom and a kernel with cwmr and I will be set.
Please help! I have a Verizon Samsung Galaxy S4 (SCH-I545) rooted on VRUAME7.
I did something really stupid and tried to flash the Google Wallet Mod and it ended up bricking my phone. It would show the Samsung and unlocked Custom logo and then the screen would go blank with the blue light on permanently. For some reason, I couldn't get into recovery mode (ClockWorkMod). Only Download mode worked.
So, I tried following the instructions here: http://droidviews.com/2013/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/ to get my phone back.
I repartitioned with the pit file in those instructions and tried to flash a MDK build, which didn't do anything. Then I wised up and tried the ME7 build. It also didn't work. The phone would still only show the screen with the unlocked Custom logo and then it would turn off. I could still only get into Download mode.
I also tried the instructions here: http://forum.xda-developers.com/showthread.php?t=2301259, which got me a little further at one point, where I could hear the boot up sound and it would get stuck on the white screen with the Verizon logo. After doing that once and rebooting it is back to just showing the unlocked Custom logo and turning off again.
Is there anything else I can try? I've searched and searched the forums and I'm coming up empty now.
lobo78 said:
Please help! I have a Verizon Samsung Galaxy S4 (SCH-I545) rooted on VRUAME7.
I did something really stupid and tried to flash the Google Wallet Mod and it ended up bricking my phone. It would show the Samsung and unlocked Custom logo and then the screen would go blank with the blue light on permanently. For some reason, I couldn't get into recovery mode (ClockWorkMod). Only Download mode worked.
So, I tried following the instructions here: http://droidviews.com/2013/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/ to get my phone back.
I repartitioned with the pit file in those instructions and tried to flash a MDK build, which didn't do anything. Then I wised up and tried the ME7 build. It also didn't work. The phone would still only show the screen with the unlocked Custom logo and then it would turn off. I could still only get into Download mode.
I also tried the instructions here: http://forum.xda-developers.com/showthread.php?t=2301259, which got me a little further at one point, where I could hear the boot up sound and it would get stuck on the white screen with the Verizon logo. After doing that once and rebooting it is back to just showing the unlocked Custom logo and turning off again.
Is there anything else I can try? I've searched and searched the forums and I'm coming up empty now.
Click to expand...
Click to collapse
Soft brick can ALWAYS be fixed by reflashing stock ROM. Find the stock ROM and put it on ur device (in CW recovery is mount USB-OGT while plugged into ur computer). Flash it after you WIPE the device. Then reboot. Thumbs up if this helped!
Also a tip is DONT FUDGE AROUND WITH THE DEVICE. If its bricked, the device can be recovered. But if you do random attempts it will cause other problems. That's from experience. Hard bricked my friends Galaxy S cause I kept on flashing **** on it. Root on!
Sent from my SCH-I545 using xda premium
Just make sure you Odin ME7 stock ..you cant go to the older firmware..
Use odin to flash stock me7 and you should be good to go.
sulla65 said:
Use odin to flash stock me7 and you should be good to go.
Click to expand...
Click to collapse
Any chance of linking the ME7 download. Thats been the hard part for me. Cant find it anywhere.
ballsagna said:
Any chance of linking the ME7 download. Thats been the hard part for me. Cant find it anywhere.
Click to expand...
Click to collapse
samsung-updates.com
http://forum.xda-developers.com/showthread.php?t=2301259