Hey all,
I was going to root my damn Galaxy S3 (Sprint SPH-L710) and I saw this utility that did it all (yes, I know, it was stupid).
After I ran the All in Unlock Tool and after I selected the file from Odin it said 'PASS' and then restarted but never goes past the Samsung logo. I can't get it to boot anymore.
I can still get to Download mode and I can get to Clockwork Mod (Which installed on Odin after I couldn't get the thing to boot).
Does anyone know how to fix this?
Please get back to me.
-Dark
Solution
Oh man, I stumbled upon a fix.
http://forum.xda-developers.com/showthread.php?t=1727443
I can't respond to that thread since I'm a new user, but thank you mskip. That stock image was a life saver.
dangerdark said:
Oh man, I stumbled upon a fix.
http://forum.xda-developers.com/showthread.php?t=1727443
I can't respond to that thread since I'm a new user, but thank you mskip. That stock image was a life saver.
Click to expand...
Click to collapse
Another update:
One consequence I noticed is that the rotation orientation is backwards (top and bottom are reversed, so you're always upside down in landscape view)
Related
I just got a new samsung vibrant and I hate the Stock UI so I wanted to root and drop a mod on it. Rooted no problem then remembered a friend with a Galaxy S phone told me he really loved this one Rom. so I snagged it and flashed it without even thinking about the fact that his phone is a Captivate.
That went awful, screen orientation, home, menu, return buttons were all screwy. But I used ODIN to return to stock as per the Development forum here in XDA. Now however, my phone says ATT World Phone as the first thing during boot sequence. Even putting on a new rom with a custom boot animation doesn't change a thing.
Any suggestions how I might go about fixing this?
TheDejos said:
I just got a new samsung vibrant and I hate the Stock UI so I wanted to root and drop a mod on it. Rooted no problem then remembered a friend with a Galaxy S phone told me he really loved this one Rom. so I snagged it and flashed it without even thinking about the fact that his phone is a Captivate.
That went awful, screen orientation, home, menu, return buttons were all screwy. But I used ODIN to return to stock as per the Development forum here in XDA. Now however, my phone says ATT World Phone as the first thing during boot sequence. Even putting on a new rom with a custom boot animation doesn't change a thing.
Any suggestions how I might go about fixing this?
Click to expand...
Click to collapse
did you ODIN fully? does the bootanimation INCLUDE the ATT world phone part?
Helpin another guy with basically the same problem...
read this ..... http://forum.xda-developers.com/showthread.php?t=849028 -To understand the basics
and
that... http://forum.xda-developers.com/showthread.php?t=848737 - To Get you back to stock..
you probably used AT&T stock file when u Odin'ed....read those (well mostly the bottom one) and it should get u back to T-Mobile stock
@xrider Can you define fully? I used the Pit file and the Tar file, attached my phone in dl mode. Clicked start and let it go till it rebooted my phone and told me it was done.
@fearless That second link is what I've been working from, I've been using the T959UVJFD.tar
Here's the exact boot up process,
1) ATT World Phone logo
2) Vibrant / Samsung logo
3) T-mobile sound and animation
4) Swirly Galaxy S logo
5) at main locked screen going through media checks and aquiring signal
something in that Captivate ROM must have really screwed up stuff....i'm thinking the playlogos file got tampered with when you flashed that Captivate ROM....but ODIN would've restored it back to normal....i'll do some more searching....
Thanks, if it helps any, this is the ROM I flashed the first time http://forum.xda-developers.com/showthread.php?t=856877
Hey all, this is my first post on this forum. I registered just to let my voice be heard.
Let me just say that I have done extensive research into these problems but I don't want to brick my phone so I want to know the direct steps for me.
OK my problems are:
Upon turning on the phone the original Motorola logo is gone and is instead replaced by:
"Unlocked. PwrReason: PWR_KEY_PRESS. OS will boot in 5 seconds. Press a key to stop countdown. Avaliable Modes are: " and lists 14 different modes I can choose
This happened after I accidentally deleted my pds folder or something of the sort. I must've partitioned something accidentally and as a result my phone did not boot the next time around. It booted after I did a battery pull but gave me the next problem.
Upon booting into CM10.1 I noticed that the soft keys would not work. The entire screen was recognized as one big touch surface.
I deduced that some file was deleted which makes the screen recognize the soft keys, so I proceeded to do some research into it. The methods I saw to do were doing some sort of pdsfix which is not recommended unless necessary, which in my case is very necessary. I can boot into Romracer's recovery (5.0.2.7 I believe it is) as well as my OS. Everything is working except for those problems I listed. I am not sure if my phone can boot into fastboot but I can try. Please post your answers because I really need to get my phone working perfectly again. At this point, it is only useful for texting and a little music (and settings). I can't go into much else without restarting the phone each time (you must know why).
EDIT 15/04/13
-----------------------------------------------------------
I just flashed pdsfix(gingerbread).zip and I am now able to use my phone at normal speeds and even overclock if necessary. I was running epinter's CM10.1 Rom
Fixed half the problem!
Okay so after many hours of trying, I managed to install the drivers for fastboot on my computer and did the fix for the pds file.
First I downloaded moto-fastboot.zip and extracted to my C:/ drive.
Then I tested if my device was recognized. It didn't recognize it at all, so I went into device manager.
In device manager there was my problem. I saw fastboot with a yellow exclamation sign. I right-clicked it and directed it to where I had previously downloaded fastboot drivers. (Found them here: FASTBOOT DRIVERS
It installed nicely and when I tried the commands listed in Method 2 on this page PDS Partition Fix it worked perfectly!
So I proceeded to restart the phone, no issues. But the Motorola logo at the very beginning is still not there. It says unlocked at the top left and displays the same options as before. The phone is still fully functional without it, but I want to get it back. I will be doing more to fix this though.
But the best part is that, my soft-keys are working perfectly! :laugh: I do notice a little lag in the system but that will be fixed soon. Hope this helped anyone who didn't know what to do.
P.S. If you find a way to restore the Motorola logo on boot, please tell me!
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Mojar7070 said:
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Click to expand...
Click to collapse
Perfect! Thanks much for finding that for me. I now have the problems fixed except that my cpu won't clock above 608 mhz even when I put the min clock slider higher than that value.
I suspect that perhaps I flashed the froyo pdsfix instead of gingerbread. Maybe that is causing the problem. I'll try and post my results soon.
My Atrix 4g is fixed!!
Wow I can't believe I finally fixed it! It was as I suspected. After downloading the pdsfix(gingerbread).zip I rebooted my phone into fastboot and proceeded to flash the zip. And who would've guessed it? I am now able to clock at usual speeds including the 1000MHz of old ^_^. I am sooo glad I found this forum. If anyone had similar problems you can try the steps I did.
P.S. For the record I was running epinter's CM10.1 Rom for the Atrix 4g. I may go to Neutrino's in the near future, but I am just glad to have my phone back in working order :laugh::laugh:
Verizon Galaxy Tab 10.1 4G LTE (sch-i905)
So I got this tablet from a friend who said it was bricked, said I could have it if I got it working. So I plug it in and it turns on no problem, strange. wiped tablet and added a couple apps. Got busy at work and the tablet drain power. That's when I got to see it bricked, but still not sure why it booted for a bit for me.
Symptoms:
Boots to Samsung Galaxy Tab 10.1 splash screen (not the animated one after), sits there for ever.
Boots to Odin update mode
When booting to recovery I get a blank, back lit screen and nothing ever.
I've tried:
-Pushing clockwork mode to fix recovery
-I've had a hell of a time finding stock firmware for some reason (it isn't on sammobile), but I did find one eventually. I pushed it to the tablet via Odin, and it was successful, but rebooted to blank black back-lit screen. Have to hard boot and hold power buttun until I see the splash screen to get that far. I followed the guide on rootzwiki reposted on icsforums - www icsforums com/forum/showthread / 13525 (sorry new member can't post links)
-Followed another guide that involved draining battery completely, no go.
I don't care what firmware I end up on, or if I can use LTE (I won't anyway)
I'm a network engineer so I'm tech savy, but not heavy on Android OS. I'm looking for anything else I can try. I saw another method involving heimdall suite, but can't find the files for my model.
Any help or guidance is greatly appreciated.
@Juicebox4242
I had this problem on my gt-p7510...
What I ended up doing was wiping my sdcard..I must have had something corrupt in my file system or a kernel issue( still not sure which )..
Since you have no recovery..I think you can use odin to repartition ( I CAN NOT STRESS ENOUGH THAT THIS IS JUST A GUESS )..I have not tried it..but i will search after this post to confirm..I also believe there is a way using ADB..again not sure..
I just wanted to post this so you would know somebody was looking and to maybe give you a couple ideas to follow up on...I'll search around and see what I find
Edit...I believe ADB will only work with usb debugging checked...But you can flash a stock rom in odin with re-partition checked..you need a .pit file....I think...
Edit...Here is a link to a stock rom thread for you're device..It seems to have helped a couple people with their soft-bricked devices..just follow directions in OP..no repartition checked. I cant even find a .pit file to do a re-partition with for you're device..
http://forum.xda-developers.com/showthread.php?t=1342995 Let me know if this works for you..
Thanks for the post!! Really appreciate it.
That firmware is the one I found in the end and tried. Odin pushes it ok, but then still doesn't boot. In fact after pushing that firmware it boots to backlit blank screen, but when hard reset boots to splash screen.
I tried a pit file I found that I thought was the right one, but it failed when I used that so it must have been wrong.
Juicebox4242 said:
Thanks for the post!! Really appreciate it.
That firmware is the one I found in the end and tried. Odin pushes it ok, but then still doesn't boot. In fact after pushing that firmware it boots to backlit blank screen, but when hard reset boots to splash screen.
I tried a pit file I found that I thought was the right one, but it failed when I used that so it must have been wrong.
Click to expand...
Click to collapse
I have the exact same problem as you, except sometimes I can't my tablet to boot. I know it is a software problem because before I was messing with recovery yesterday, everything was working just fine. All I wanted to do was restore to factory settings and instead ended up bricking the device... If you find / know the answer, please do share.
Juicebox4242 said:
Verizon Galaxy Tab 10.1 4G LTE (sch-i905)
So I got this tablet from a friend who said it was bricked, said I could have it if I got it working. So I plug it in and it turns on no problem, strange. wiped tablet and added a couple apps. Got busy at work and the tablet drain power. That's when I got to see it bricked, but still not sure why it booted for a bit for me.
Symptoms:
Boots to Samsung Galaxy Tab 10.1 splash screen (not the animated one after), sits there for ever.
Boots to Odin update mode
When booting to recovery I get a blank, back lit screen and nothing ever.
I've tried:
-Pushing clockwork mode to fix recovery
-I've had a hell of a time finding stock firmware for some reason (it isn't on sammobile), but I did find one eventually. I pushed it to the tablet via Odin, and it was successful, but rebooted to blank black back-lit screen. Have to hard boot and hold power buttun until I see the splash screen to get that far. I followed the guide on rootzwiki reposted on icsforums - www icsforums com/forum/showthread / 13525 (sorry new member can't post links)
-Followed another guide that involved draining battery completely, no go.
I don't care what firmware I end up on, or if I can use LTE (I won't anyway)
I'm a network engineer so I'm tech savy, but not heavy on Android OS. I'm looking for anything else I can try. I saw another method involving heimdall suite, but can't find the files for my model.
Any help or guidance is greatly appreciated.
Click to expand...
Click to collapse
Did you ever get this fixed? I've had the same problem for months. I just gave up and put it away. I recently fixed a Galaxy Tab 2 and now I want to see if anyone else was able to fix this i905 not booting issue.
did anyone know the solution of this question
hi all
after an ota update i have only a black sreen when in download mode and also i have not anymore the screen whith the model name at boot. this is a small issue as the download mode still works and i have been able to install with no problems cmw recovery and the wonderfull megafirev3 rom but i would like to fix it. Is there any way to reinstall the bootloader avoiding to install a new rom with knox ?
thanks
Im sorry that i don't have a solution, but i just want to let you know that i have the exact same problem. it was that way after i got it back from display repairs. it's apparently not that uncommon amongst other Samsung devices as well...
brunte said:
Im sorry that i don't have a solution, but i just want to let you know that i have the exact same problem. it was that way after i got it back from display repairs. it's apparently not that uncommon amongst other Samsung devices as well...
Click to expand...
Click to collapse
thank you for your answer. the funny thing is that also for me it was after taking back my phone from samsung service which changed the display. but i think it's only a coincidence as immediately after i took the phone it worked then i installed the french stock firmware and after this an ota update and then the download mode page disappeared.
As I wrote before is not a big issue but I'm afraid could happen the same for the recovery page.
hopefully it will not... I managed to enter recovery but not download mode graphically after i got it back from repairs. After that i flashed CWM and that is working well with graphics also. Probably it all comes down to a quirky boot loader installed at the service place. I would expect the problem to disappear if I flashed a new firmware with KNOX boot loader, but I'm definitely not sure. Anyways I got myself a jig to make it easier to enter download mode since the timing gets a bit tricky without the graphical guidance
Greetings Everyone,
First, as a newbie to this site, thanks for all the great assistance. Two suggestions to other newbies, if I may be so bold.
1) Recovery Mode - In literally hours of searching, I couldn't figure out why my S3 wouldn't go into recovery when pushing Volume Up, Home, and Power keys. Finally, I found one post that suggested I push the Volume Up and Home Keys first, then press the Power Key. This has worked consistently ever since. Don't know if it's a quirk specifically to the S3, but it certainly empowered me.
2) Download Mode Soft Brick Bootloop - My S3 was soft-bricked with a bootloop in Download mode. I searched for hours for a solution. Finally, one post said I simply had to use Odin to give it something to Download, which would subsequently release it from its bootloop. When I did this, the progress bar magically appeared, the file transferred, and when it was done, my phone was no longer stuck. Problem solved.
Since these two fixes worked for me, but were so hard to find, I thought I'd post them again, in case someone else gets stuck in the same hell I was. Literally spent a day on these two issues alone.
Thanks again to all. I surely would have been stuck in many other states of confusion if it wasn't for this wonderful forum. Best to all.
It's nice to see a post where the user has used their noggin and fixed it by trial and error!.
Well done and thanks for posting!.
shivadow said:
It's nice to see a post where the user has used their noggin and fixed it by trial and error!.
Well done and thanks for posting!.
Click to expand...
Click to collapse
Thanks. )