Hello, everyone! I'm in search of a hero who can help me resolve this (frustrating) issue! I'm sure you have heard it before: my phone will not boot fully; it is instead stuck permanently on the white VERIZON logo screen.
Model: SCH-I545
Carrier: VERIZON
Color: BLACK
Size: 16GB
The phone has not been rooted.
It does not have USB debugging enabled.
I have not installed any custom recovery software or mods.
There is no external SD card installed.
First, some back story. My phone asked me to perform a software update roughly a week ago. About a minute into the update, it told me the update failed. I assume this occurred because I was on the train and passed through a tunnel. Afterwards, my phone began acting up, rebooting itself randomly, and applications(such as web browser, text messaging) would randomly crash on me. I assumed another update would come to resolve the issue, but unfortunately yesterday(Sunday), my phone again rebooted itself, only this time it would not make it past the white VERIZON screen.
My goal is simply to recover my files from the device before either returning it or performing a factory reset. I have scoured the internet for hours trying to find a way to achieve this. I can boot my device into the stock recovery console and into ODIN download mode. I have tried clearing my phone's cache in recovery mode, which did not help. I have tried booting into safe mode by repeatedly tapping the menu screen, but it did not help.
I have ADB installed and a USB driver from Samsung and a USB driver from Google. I can get my phone to appear using ADB in sideload mode only while in the recovery console. Unfortunately, this is of limited use because apparently it can only be used to install software packages, and the phone seemingly rejects all attempts to install packages such as CWM and TWRK, which I had hoped would allow me to use the ADB pull command.
I have tried installing these mods using ODIN as well. Again, failure due to security apparently. :crying:
If anyone has any idea how I can retrieve the files from my phone, you'll be my hero forever!
BeefJerkyAddict said:
Hello, everyone! I'm in search of a hero who can help me resolve this (frustrating) issue! I'm sure you have heard it before: my phone will not boot fully; it is instead stuck permanently on the white VERIZON logo screen.
Model: SCH-I545
Carrier: VERIZON
Color: BLACK
Size: 16GB
The phone has not been rooted.
It does not have USB debugging enabled.
I have not installed any custom recovery software or mods.
There is no external SD card installed.
First, some back story. My phone asked me to perform a software update roughly a week ago. About a minute into the update, it told me the update failed. I assume this occurred because I was on the train and passed through a tunnel. Afterwards, my phone began acting up, rebooting itself randomly, and applications(such as web browser, text messaging) would randomly crash on me. I assumed another update would come to resolve the issue, but unfortunately yesterday(Sunday), my phone again rebooted itself, only this time it would not make it past the white VERIZON screen.
My goal is simply to recover my files from the device before either returning it or performing a factory reset. I have scoured the internet for hours trying to find a way to achieve this. I can boot my device into the stock recovery console and into ODIN download mode. I have tried clearing my phone's cache in recovery mode, which did not help. I have tried booting into safe mode by repeatedly tapping the menu screen, but it did not help.
I have ADB installed and a USB driver from Samsung and a USB driver from Google. I can get my phone to appear using ADB in sideload mode only while in the recovery console. Unfortunately, this is of limited use because apparently it can only be used to install software packages, and the phone seemingly rejects all attempts to install packages such as CWM and TWRK, which I had hoped would allow me to use the ADB pull command.
I have tried installing these mods using ODIN as well. Again, failure due to security apparently. :crying:
If anyone has any idea how I can retrieve the files from my phone, you'll be my hero forever!
Click to expand...
Click to collapse
Sounds like that upgrade definitely went wrong. Since you were upgrading to Kit Kat I'd say flash the No Wipe file from here http://forum.xda-developers.com/showthread.php?t=2735172
Your phone won't allow for CWM or TWRP recoveries since it's a build past MDK. Also if you want prior to using that Odin file go to play store and get the app " Samsung phone info" and run that app and take a screen shot of the bootloader section. Actually do that before hand anyways. I'll link you to it
Sent from my SCH-I545 using Tapatalk
---------- Post added at 06:39 AM ---------- Previous post was at 06:39 AM ----------
Here
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Sent from my SCH-I545 using Tapatalk
hopefully people will learn by this NEVER take any update while traveling, too much can and will go wrong.............
Yea I think people have to much faith in Verizon. There not setup to handle anything but a perfect download and install when it comes to their OTAs. They're best done on WiFi at home
Sent from my SCH-I545 using Tapatalk
Reply
BeefJerkyAddict said:
Hello, everyone! I'm in search of a hero who can help me resolve this (frustrating) issue! I'm sure you have heard it before: my phone will not boot fully; it is instead stuck permanently on the white VERIZON logo screen.
Model: SCH-I545
Carrier: VERIZON
Color: BLACK
Size: 16GB
The phone has not been rooted.
It does not have USB debugging enabled.
I have not installed any custom recovery software or mods.
There is no external SD card installed.
First, some back story. My phone asked me to perform a software update roughly a week ago. About a minute into the update, it told me the update failed. I assume this occurred because I was on the train and passed through a tunnel. Afterwards, my phone began acting up, rebooting itself randomly, and applications(such as web browser, text messaging) would randomly crash on me. I assumed another update would come to resolve the issue, but unfortunately yesterday(Sunday), my phone again rebooted itself, only this time it would not make it past the white VERIZON screen.
My goal is simply to recover my files from the device before either returning it or performing a factory reset. I have scoured the internet for hours trying to find a way to achieve this. I can boot my device into the stock recovery console and into ODIN download mode. I have tried clearing my phone's cache in recovery mode, which did not help. I have tried booting into safe mode by repeatedly tapping the menu screen, but it did not help.
I have ADB installed and a USB driver from Samsung and a USB driver from Google. I can get my phone to appear using ADB in sideload mode only while in the recovery console. Unfortunately, this is of limited use because apparently it can only be used to install software packages, and the phone seemingly rejects all attempts to install packages such as CWM and TWRK, which I had hoped would allow me to use the ADB pull command.
I have tried installing these mods using ODIN as well. Again, failure due to security apparently. :crying:
If anyone has any idea how I can retrieve the files from my phone, you'll be my hero forever!
Click to expand...
Click to collapse
Hi BeefJerkyAddict,
I would reccomend to do a total full wipe with Odin, this usually solves all of your problems. All of your stuff should be clear for restoring once you do that. But after you do the full wipe, immediately go to settings and then software update because your phone will be on android 4.3 and not 4.4.2.
Here is the link with the instructions as well:
http://forum.xda-developers.com/showthread.php?t=2578209
You're welcome.
Yea I guess I'm just biased to updating straight to kit kat lol if the op has the chance to stay on mk2 he might as well. And I suggested no wipe first just so not to lose data. Up to the op though
Sent from my SCH-I545 using Tapatalk
Hi guys,
Just posting to say THANK YOU for the help. After a long download, I got ahold of the VRUFNC5 No-Wipe file and successfully installed it using ODIN3 v3.09 without a hitch! All of my pictures, videos, text messages, are all right where they were, and my operating system is upgraded.
Thank you so much for taking the time to point me in the right direction. I had nearly given up!
Related
Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
rushmix said:
Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
Click to expand...
Click to collapse
which rom did u come from?
Froyo. I followed the guide to a 't' and got this black screen. I have no idea what I did wrong.
Well, I need to run off to work now, but I'd really appreciate any responses.
It seems like my phone isn't being detected by odin or windows when it is in download mode, though windows does recognize that a Samsung USB device is being connected. This is recognized in the windows tray (under the name "Samsung_Android"), and in Heimdall's Zadig driver tool ("Samsung_Android").
Hmm first tthings first, your reinstall package error seems pretty simple, yu dont have the right update.zip and recovery combination... if u wanna solve that problem, find the recovery 3e to 2e tool (google it) and run it (follow directions).. then you can run reinstall packages (might havr tto do it twice). If that doesnt cut it, find the CWM update.zip and put iit into the root of your internal sd card (the 12gb one), then run reinstall packages again. You may have to reinstall packages more than once.
Your odin problem might be caused by a lack of drivers on your comp... go on the android dev section and look for a thread talking aboout ms64 and 86 drivers samsung something...
If you can get into download mode, you can unbrick your phone so dont panic
Now odin is a very dangerous tool imo so if you really are sorry about askint, do us a favir and read the sticky oon how to odin before you use it so you dont have to come back and ask us about how to Really unbrick your phone
Also, your brick is referred to as a soft brick and the android recovery program is referred to as recovery mode.
And if you really **** up, we now have the unbrickable mod in the vibrant android dev section which will unbrick your phone no matter wat (it takes somr hardware modifying though)
Sent from a cell tower to the XDA server to you.
And if i were you, id redownload the cm7 package again to make sure that it wasnt a bad download and id read some general vibrant info before diving into cm7... if youre running stock recov and have never odined before etc, youre prob not the best candidate for flashing.. just my opinion
Sent from a cell tower to the XDA server to you.
Thank you very much for your reply. I couldn't find a related tool with the Google search string "3e to 2e recovery tool vibrant," but I did find a modified 3e tool at dkszone(*)net/bypass-e-signature-verification-fail-issue-on-samsung-vibrant-android-2.2 . However, this gets stuck at "checking for temporary root."
As for installing drivers, I have installed the Samsung galaxy 64 bit drivers several times now, but I'll give the 32 bit drivers a whirl as well.
I am unable to access the SD card, and don't have a mini SD card reader, so that compounds the problem (damn my lack of cash!).
*Edit* Upon my attempted installation of the 32 bit drivers I get the following (word for word) "Swallowtail has being used. You need to eject device and reboot your computer. Rerun (Japanese or Chinese characters) after reboot your computer." Google returns zero results when I search for this error. I tried rebooting my computer and running it again, but got the same error (even with the phone unplugged from the computer).
*Double Edit* I've been trying to use the AIO Vibrant Toolbox to restore my phone to factory defaults, but I've been having no luck, as it claims my phone is not in USB debugging mode (and obviously I can't change this, as I have no access to the Android OS).
Try this, mate and hopefully you will be up and running soon...
http://forum.xda-developers.com/showthread.php?t=1278683
When I run this the program handshakes, downloads the pit file, then restarts and "...Local and device PIT files don't match and repartition wasn't specified!
Ending session...
Rebooting device...
Device not connected.."
It reboots to the black screen of death and stays there. Perhaps I could select "Flash Bootloader," but the warning of possible permanent damage scares me.
According to the thread...
"REPARTITIONING ISSUE WITH HEIMDALL 1.3.0
Heimdall currently has an issue with repartitioning. 99% of the time you will not need to repartition. Failure to follow these directions can possibly lead to bricking:
Do not flash bootloaders if you see this message:
Code:
Local and device PIT files don't match and repartition wasn't specified!
This message means your partition tables do not match the firmware."
So I guess one of the roots of my problem is that my partition tables do not match the firmware. I have no idea what to do about that.
In this case try another computer if you can, install the right drivers and see odin recognizes your phone. I'm sure it will, for some people sometimes it takes fair few tries for no reason.
Another suggestion, take out sim card and external sd while connecting in download mode. Sometimes that helps.
---------- Post added 29th September 2011 at 12:01 AM ---------- Previous post was 28th September 2011 at 11:43 PM ----------
Here is a recent thread where someone had issue with odin connection.
http://forum.xda-developers.com/showthread.php?t=1225197#16797271
Well, I ran Heim one click on another computer and had the same boot-to-blackscreen process happen.
I was, however, successful at getting Odin to recognize the phone with AIO vibrant toolbox. Odin kept getting stuck at "set pit file" though.
Baby steps...
This is so frustrating. I feel like I'm so close.
How do I get the right PIT file on my phone if ODIN is getting stuck at that step?
Now, after installing the drivers provided with Heimdall-one-click's Zadig, ODIN doesn't recognize the phone.
One step forward, two steps back.
*Edit* Nevermind, got ODIN to recognize it again by uninstalling/reinstalling all related drivers.
Then odin to stock with tthe stock jfd files.. follow the manual, report results
Sent from a cell tower to the XDA server to you.
http://forum.xda-developers.com/showthread.php?t=734475
Use those files and the procedure for ODIN.
As for what caused your problem. You flashed a clockwork recovery for a different phone, possibly the Vibrant (non-MTD) mode? Usually installing Clockwork on the Vibrant only works from ROM Manager app when its running stock JFD. At least for me anyway. Any other ROM it ****s it somehow and I end up in a situation like yours. Not to worry though. Here's a quick install guide after you ODIN the phone to stock.
Put latest nightly of CM7 on the phone memory (not external microSD)
Install clockwork (Easiest way to do this is put the update.zip file I've attached onto the root of your phone memory, not the external microsd card, then reboot into recovery (hold both volume buttons and turn it on) and select Reinstall packages twice. It will then boot you into Clockwork).
Wipe data and cache in clockwork
Install zip from SD card--> pick the latest CM7 nightly.
DONE.
I'd like to use those files, but every single link is broken...
*Edit* Never mind. Found another source. I'll post upon success/failure.
*Edit again* Actually, it doesn't seem like the new link on mediafire has all the files required by the process (OP: http://forum.xda-developers.com/showthread.php?t=734475), and I can't post in that thread (because I'm a new user).
This is the post that uploaded the files: http://forum.xda-developers.com/showpost.php?p=17512889&postcount=615
So I haven't changed a damn thing yet, and all that happens when I try to put the phone in download mode is | Phone----Warning (!) Sign----Computer | screen comes up.
Even when I only plug it into a power outlet...
Flashing the IPhone was easier and more stable than this, years ago. I honestly expected better from Google.
*Edit*
OH MY GOD. Odin is going somewhere! Go, AIO Vibrant Toolbox, Go!
*Edit again*
And it stopped at about 90% with "<ID:0/003> dbdata.rfs
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
"
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
rushmix said:
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
Click to expand...
Click to collapse
959v is the not the vibrant, tis the galaxy s4g, if you odined vibrant files on your 4g then that's why you are in a bootloop
Dear god do I feel stupid. I googled it a while ago just to be sure, and it seemed to say that the V stood for "Vibrant." I guess that would be why I've been having this sneaking suspicion...
Well it's good news for you, mate. Head over to galaxy s 4g
forums and hopefully you will be able to get your phone back.
hello xda. been browsing for a couple weeks, but finally registered today.
I have run into a problem I would like to try and solve without having to go through my insurance or carrier. my phone bricked itself after only 16 days, with 0 modifications on it. it was factory stock still. let me describe what happened, and what I did:
1st problem: I was using my online banking app (reputable bank), when the app minimized to the main screen; however, nothing OS related loaded. the phone just froze. only the wallpaper was visible. I tried powering it down, but it wasn't responding, so I pulled the battery, and put it back in. I powered on the phone, it loaded the SAMSUNG screen, then went to the Exhibit II 4G page, but then it stopped. it failed to load past the Exhibit II splash screen. no matter what I did, it stayed there. I googled for hours, trying various things, until I finally found this site with a stock rom setup.
2nd problem: I followed jocala's guide for flashing it, using Odin 4.43, and after it finished flashing, I got a "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." so now I have been googling this issue, and I cannot seem to find anything on how to fix it. I don't understand how my phone can just brick itself while using a banking app that i'd been using since I got the phone.
any help would be appreciated
also, if this isn't the forum for it, feel free to move it. this just looked the most appropriate seeing as there wasn't a board for the phone specifically.
deathbenotproud said:
hello xda. been browsing for a couple weeks, but finally registered today.
I have run into a problem I would like to try and solve without having to go through my insurance or carrier. my phone bricked itself after only 16 days, with 0 modifications on it. it was factory stock still. let me describe what happened, and what I did:
1st problem: I was using my online banking app (reputable bank), when the app minimized to the main screen; however, nothing OS related loaded. the phone just froze. only the wallpaper was visible. I tried powering it down, but it wasn't responding, so I pulled the battery, and put it back in. I powered on the phone, it loaded the SAMSUNG screen, then went to the Exhibit II 4G page, but then it stopped. it failed to load past the Exhibit II splash screen. no matter what I did, it stayed there. I googled for hours, trying various things, until I finally found this site with a stock rom setup.
2nd problem: I followed jocala's guide for flashing it, using Odin 4.43, and after it finished flashing, I got a "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." so now I have been googling this issue, and I cannot seem to find anything on how to fix it. I don't understand how my phone can just brick itself while using a banking app that i'd been using since I got the phone.
any help would be appreciated
also, if this isn't the forum for it, feel free to move it. this just looked the most appropriate seeing as there wasn't a board for the phone specifically.
Click to expand...
Click to collapse
Howdy, DBNP,
The Exhibit II is pretty much unbrickable...you won't need to resort to esoterica like jtag
The guide in the Exhibit II Wiki usually works out well. I'd try booting into stock recovery, doing a data wipe, then install stock with Odin. The Wiki has the links to the files you need. BTW, I didn't write the Odin portion @ the wiki; I just hosted required files when the links went stale.
Easy way to start recovery
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Once you're back up and running first thing you should do is install Clockworkmod. HTH, & good luck.
I cannot get my phone to get into recovery mode, though. if I press volume+up, the phone simply displays the firmware error message. thus, I cannot do a data wipe.
deathbenotproud said:
I cannot get my phone to get into recovery mode, though. if I press volume+up, the phone simply displays the firmware error message. thus, I cannot do a data wipe.
Click to expand...
Click to collapse
Sorry if this is redundant, but this was with:
Easy way to start recovery
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
This has never failed for me. IDK, Perhaps your earlier Odin try wiped the recover partition. Can you get into Download mode? (hold Power-on Vol-Down)
I can enter download mode, but I cannot enter recovery mode. volume down gets me into download, while up gets me the error message. I cannot get to that menu anymore.
deathbenotproud said:
I can enter download mode, but I cannot enter recovery mode. volume down gets me into download, while up gets me the error message. I cannot get to that menu anymore.
Click to expand...
Click to collapse
Are you saying that you get an error when you press Vol-Up at the initial "Warning!" "A custom OS can cause..." screen, the initial download mode screen?
when I press and hold the vol-up sequence, it takes me to the initial error of "firmware upgrade has encountered an issue..."
when I press and hold the vol-up sequence, it takes me to the menu where it says custom OS etc., press up to continue, down to cancel (restart phone).
deathbenotproud said:
when I press and hold the vol-up sequence, it takes me to the menu where it says custom OS etc., press up to continue, down to cancel (restart phone).
Click to expand...
Click to collapse
And when you press Vol-Up at this screen what happens?
it takes me to odin mode/download mode.
deathbenotproud said:
it takes me to odin mode/download mode.
Click to expand...
Click to collapse
OK, that's good. That tells us that your exhibit2's /dev/block/mmcblk0p5 partition is undamaged. AFAIK Odin when properly used, can flash a new rom to your phone. Please try again, following the instructions in the wiki, reading carefully, downloading any files that you need, if you don't have them. Please walk through the wiki procedure to reflash stock from Odin, this procedure has worked for many,many people. Keep careful notes, you may be an edge case for some reason.
I'm posting links to this thread in the discussion threads that we use, since we're not allowed a forum. These threads get the most attention.
Exhibit II 4g discussion HERE
Exhibit II 4g dev thread HERE
yeah, I have tried doing that myself, as well as my friend who is rather skilled with android devices. he tried that all himself today, as well as attempting add. nothing worked.
deathbenotproud said:
yeah, I have tried doing that myself, as well as my friend who is rather skilled with android devices. he tried that all himself today, as well as attempting add. nothing worked.
Click to expand...
Click to collapse
I think you and your friend did it wrong. You should try again, following the wiki carefully.
we re-did it this morning step-by-step with no new results. we tried three times.
odin does its thing successfully, then when it goes to reboot, instead of going into recovery mod, it just goes to the firmware upgrade issue message.
deathbenotproud said:
we re-did it this morning step-by-step with no new results. we tried three times.
odin does its thing successfully, then when it goes to reboot, instead of going into recovery mod, it just goes to the firmware upgrade issue message.
Click to expand...
Click to collapse
Sorry to hear it. If Odin won't fix your phone and you've only had it a few weeks, I'd return it. I've linked your thread to our discussion threads, perhaps someone else has an idea.
that's the issue. because I have tried to flash it via odin, they're saying they won't take it because of the firmware upgrade error that keeps coming up. :/
because they won't take it, and the normal flashing to stock method isn't working, what do you think I should do next?
deathbenotproud said:
because they won't take it, and the normal flashing to stock method isn't working, what do you think I should do next?
Click to expand...
Click to collapse
I don't know who "they" are, but the chances of anyone at a T-Mob store or a Walmart knowing you touched your phone with Odin or even what Odin is are practically nil. "It's three weeks old, I turned it on and it doesn't work. Gimmie my replacement."
Or seek out a repair service to reflash your phone.
all right, i'll take it back and get a different rep. thanks for your help, though
deathbenotproud said:
all right, i'll take it back and get a different rep. thanks for your help, though
Click to expand...
Click to collapse
I'm sorry we didn't resolve the problem. Better luck next time!
deathbenotproud said:
hello xda. been browsing for a couple weeks, but finally registered today.
I have run into a problem I would like to try and solve without having to go through my insurance or carrier. my phone bricked itself after only 16 days, with 0 modifications on it. it was factory stock still. let me describe what happened, and what I did:
1st problem: I was using my online banking app (reputable bank), when the app minimized to the main screen; however, nothing OS related loaded. the phone just froze. only the wallpaper was visible. I tried powering it down, but it wasn't responding, so I pulled the battery, and put it back in. I powered on the phone, it loaded the SAMSUNG screen, then went to the Exhibit II 4G page, but then it stopped. it failed to load past the Exhibit II splash screen. no matter what I did, it stayed there. I googled for hours, trying various things, until I finally found this site with a stock rom setup.
2nd problem: I followed jocala's guide for flashing it, using Odin 4.43, and after it finished flashing, I got a "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." so now I have been googling this issue, and I cannot seem to find anything on how to fix it. I don't understand how my phone can just brick itself while using a banking app that i'd been using since I got the phone.
any help would be appreciated
also, if this isn't the forum for it, feel free to move it. this just looked the most appropriate seeing as there wasn't a board for the phone specifically.
Click to expand...
Click to collapse
go into recovery and do a factory reset then reboot from recovery.
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
laxsrbija said:
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
Click to expand...
Click to collapse
did you try reflashing your recovery via Odin?
SuperSU
laxsrbija said:
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
Click to expand...
Click to collapse
First of all what are co workers doing messing with your phone I would seriously not be happy!! screen lock comes to mind!
As the above post said flash another recovery in odin I recommend Philz recovery,backup your data in recovery then factory reset if that does not work flash another rom via recovery or return to stock with odin. You can also boot into recovery with adb but I would try above first.
Then charge your co-worker for all the time wasted trying to fix phone
Thank you so much for the idea, I just tried this and it worked! After flashing new recovery via ODIN, I'm now able to access my phone. There was no need to flash the ROM again, as it was fine, the only problem was with the recovery.
And I still have my data!
Thank you very much again, cheers :laugh:
tallman43 said:
First of all what are co workers doing messing with your phone I would seriously not be happy!! screen lock comes to mind!
Click to expand...
Click to collapse
He's actually a good guy and I'm sure he didn't do it on purpose. He told me that he was playing a game and he tried to add more coins using GameCIH. Then the prompt to allow root access to the app came up along with a notification to update the SU binary. He said he pressed that button by mistake. I wasn't mad at the guy, I was only upset that I may lose my data.
laxsrbija said:
Thank you so much for the idea, I just tried this and it worked! After flashing new recovery via ODIN, I'm now able to access my phone. There was no need to flash the ROM again, as it was fine, the only problem was with the recovery.
And I still have my data!
Thank you very much again, cheers :laugh:
Click to expand...
Click to collapse
you are welcome! glad to see that it works again.
Hi guys,
I'm sorry if you might find this answered somewhere else. But as far as my xda and google searching skills go, I've exhausted all options.
The rooted S3 (GT-I9300 on stock 4.3 ROM) I've been using was working perfectly fine until I decided to flash touch CWM. (Note: I had already installed the app through play store or blackmart). Now my phone is stuck in a weird download mode loop. It's weird because it's not the normal download mode that comes when you press the Volume Down+Home+Power buttons. It's almost the same, except that the other details on the top-left corner are not being displayed (such as Odin Mode, product name, custom binary download, custom binary ...).
However, I can still access the normal download mode using the above key combinations, only that that phone isn't recognized in Odin. Thus, I couldn't flash the stock rom using the same. Secondly, I can also access the recovery mode, but it's not CWM; instead, it's the stock android system recovery <3e>
Now, to make things worse, all my attempts at flashing custom recovery and stock rom through ADB were in vain. Every time I tried flashing a custom rom or recovery (using adb sideload filename), the phone gave me the following message (E:signature verification failed). I understand it's the case with stock recovery, but I just can't install custom recovery. And to top it all, my attempts at installing CWM and stock rom (I9300XWUGML4_I9300DDGML4_INU.zip) using the 'apply update from external storage' option (yes, I can access my extSDcard) yield me same results (E:signature verification failed).
So there you are, I tried adb; I tried Odin; I tried applying an update through external storage; I tried removing the battering and reinserting it (after almost four hours); I even tried factory resetting the handset, yet no positive results. My phone still goes to the weird download mode when rebooted. Please help. I don't want to bother everyone with stupid questions. I'm ready to do my research and help my case, but for now I'm at a roadblock. Your help would be much appreciated.
Details:
Was running on stock 4.3; no custom ROMs were installed; it was only rooted
GT-I9300
4.3
I9300DDUGNB1
Kernel: 3.0.31-2363855
[email protected] #1
Fri Dec 27 20:00:26 KST 2013
Build: JSS15J.I9300XWUGML4
AP: I9300XWUGML4
CP: I9300DUGNB1
CSC: I9300DDGML4
Anything at all?
Guys,
Is there a way out of this? I've started the day thinking I might have missed something but still can't seem to figure it out.
Try taking the battery out, while the phone is connected to the pc, in download mode.
Without connection to Odin there is little you can do, take for a repair.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Try taking the battery out, while the phone is connected to the pc, in download mode.
Without connection to Odin there is little you can do, take for a repair.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Tried that.. when I remove the battery, nothing changes (the screen shows the download mode) until I unplug the USB cable.
Is there anyway I can flash a ROM using adb? I tried adb sideload <filename> (stock rom downloaded from sammobile) but nothing happens. Command prompt is stuck for some time, then the phone restarts into recovery mode but not completely. It gets stuck at the animation screen, where the bot is being repaired.
You would have to write each image part to the correct partition, complicated and risky.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
You would have to write each image part to the correct partition, complicated and risky.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Well, took it to the service center a while back. Got it repaired. Tried to get some information from the tech guys on what is it that they did. But well, a cloak of anonymity was thrown over the process. Nevertheless, I understand why they wouldn't let me know. But glad that the phone is working. Although can't say for how long, as I'm going to root it again and install a custom ROM. Just can't keep my hands off of it. :laugh:
Thanks anyway for everything. This was my first thread and I'm glad with the responses. Cheers!!!
Stupid me! Just found out the problem. It was the USB cable. I didn't suspect it earlier as it was working fine in adb. Now after the repair when I tried installing a ROM through odin, the phone wasn't getting detected, like earlier. That's when it struck me to check the cable. I was using the original data cable that came with the phone, as it was in mint condition. I tried connecting the phone using my sister's Xperia Z's data cable. And lo and behold! Device added in Odin. Stupid me! No wonder the tech guys were a bit apprehensive in telling me what the problem.
Hello. I have a Sprint M9. It had been acting flaking lately (I would try to install the latest update, and it would reboot without installing and report that the phone had recovered from an error and ask if I wanted to send to HTC). Tonight, I was trying to use DLNA to play video from my phone to my TV, I was in settings and gave DLNA permission to access my storage. As soon as I did that the phone rebooted without warning and continues in a loop of displaying the HTC logo, then restarting over and over.
I can get into bootloader, download, and recovery mode by holding down the volume down key. I have tried Wipe Cache Partition and Wipe Data, but the phone still will not get out of the loop.
Phone is stock. I have never tried to root or disable S-on or load my own recovery.
What, if anything, can I do to get my phone working again?
Just tried doing what I think is called RUU? I downloaded the .exe from this site:
http://www.htc.com/us/support/htc-one-m9-sprint/news/
It found my phone, and rebooted into download mode. It tried to flash my rom, but shortly after trying to send the file (progress bar jumped from 0% to 100% in 1/2 second). The utility gives me a Error [155]: Unknown Error. I've tried a couple times and get the same problem each time.
The utility reports I have version 3.41.651.21 and tries to flash to 3.41.651.31
Great, now it is telling me my software has been modified. (it hasn't) The only things I've done is run the RUU and reboot into recover to clear cache/data. Bad NAND?
Well, found out why RUU wouldn't work. Low battery. Apparently it ate a lot more battery than I realized while it was in the reboot cycle. Tried manually flashing the firmware and fastboot told me the reason it was failing. C'mon HTC, if the CLI can tell me there's not enough battery to proceed, your GUI utility should be able to as well.
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
shawndoc said:
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
Click to expand...
Click to collapse
Same thing happened to me. The update that Sprint pushed last Wednesday completely bricked my HTC One M9. Same failure mode that you experienced. Sprint technical center was unable to do anything with it, so they are replacing it, allegedly ( been waiting a week for said replacement ).
I talked to a few other people who had the same problem, by the way. Someone in Sprint's QA team completely dropped the ball on this update.
Well, even after RUU it says my system has been modified and the phone will no longer boot into recovery. Just errors back to Download with the message that recovery couldn't launch.
I've also now got intermittent problems with the com.android.settings crashing. So I've thrown in the towel and purchased my first non HTC phone since the original Windows Mobile days.
Hello there. The same problem has come to my mind and the phone has been off for almost a month. Did you solve your problem? If you could solve it, how did you do it? I sent you above the original stock rom set. Nothing changed. The phone developer rum works. but the original 0pja200 rom is starting again.
my phone soft bricked, unlocked bootloader and S-off. Whether it is possible without blocking bootloader flashed RUU rom?