Related
hi,
just recenty got a t mobile.
apparently it is SID lock. tried all the utilities (Xda developer, showpin, xdaunlock, xdamsetup)
while running the nbf file the process got stuck and I'm getting " upgradind,,,,, it will take 5 minutes...
I don't mind reseting because there is no info on it but it is stuck.
how do I get out of it?
What upgrade method are you using SD or PC install?
If its the PC try using the SD method also if your device is SID locked
try upgrading to XDA SP ROM 1.2 it has a built-in unlocking program.
Good Luck!
right now I am trying pc install.
at the moment my pc won't recognize the device throu the USB, so I cant sync.
the PDA is stuck on flash tools or when I tried to reset it returned to " upgrading... 5 minutes"
is there is a way to get out of it?
Yea use the SD card method!
HTH
could you be more specific ( I am new in this stuff)
1. how do I get out ?
2. how do I get my pc to recognize the device again?
Hello,
Complete Noob here. I'm hopeful that I can get some assistance restoring my phone to a semi-useful function. I've searched these forums, and while I've found some solutions, none of them seem to work when you can get your phone past the initial boot screen when turning on the phone. Here's the story, appreciate it if you can help.
Yesterday I saw that there was an update from Samsung for the vibrant, so I installed Kies Mini on my computer and followed the instructions. It would have been nice if the program would have detected that I was running the 64 bit version of Windows 7 as a Samsung Tech person told me afterward that it wasn't compatible with that version of W7.
When Samsung heard that the screen on my phone showed a picture of a cell phone, with a orange triangle connected to a computer they said I'd need to mail them the phone and wait over a week to get a working phone. I figured I have nothing to lose at this point, and searched for a "do it yourself" solution. I found one click unbrick or something like that, and it went to work, but my phone now is stuck in the initial boot screen for the Vibrant. So all you see is "Vibrant" and "Samsung" on the phone.
I've read several posts about putting the phone into developer or restore mode, pushing combinations of the up/down vol button with the power button, etc., perhaps I'm doing this incorrectly, but nothing seems to get my computer to recognize the phone. I downloaded Odin, and the pit and pda files to start back at Eclair, but odin doesn't detect the device, nor does it have anything listed in the id-com section. I also tried the heimdall one click for the vibrant, but again it can find the device.
Couple of questions -
Can the phone be returned to a working status or should I just return it to Samsung and wait a week for the phone?
Is there any chance that I will be able to recover anything that was on the phone? I expect not, but wonder if so. I backed up my important files, but it would be nice not to have to start from scratch.
sounds like you are able to get your phone into download mode, but odin is not recognizing, which means we have a driver issue. Put your phone into download mode, and then uninstall kies on your computer, then re-install it, this will uninstall and then reinstall the drivers, I have to do this nearly every time I use odin.
Thanks for the quick response. I assume I'll need to do this on an XP machine, and not a 64 bit W7 machine? Plugged the phone into a XP machine, and now the phone is able to get to the downloading... yellow icons. I hope this means I'm making progress
Try the drivers here:
http://forum.xda-developers.com/showthread.php?p=11633550#post11633550
And stay away from Kies. It will murder you're phone.
Sent from my ZenDroid using XDA Premium App
Okay, thanks for the link. I see what I can do with that. Prior to your post, I got into download mode, download the pit file s1_odin_20100512.pit and the pda file T959UVJI6.tar. Tried to reload things on the phone. The phone now boots to a screen where it says
Android system recover (2e)
Samsung Recovery Utils
Vol up
Vol down
Power - select items
etc, given the option to reboot, reinstall packages, clear user data, or delete cache
below it says...
Movi_check Start
checksum confirmation need_checksum[0]
Not need checksum confirmation
Movi_check already executed...
movi_checking done!
update media, please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdate_media: Can't mount DBDATA:
copy default media content failed
The ji6 Odin file is known for doing that. Pull the battery, get back into download mode, and use these two files in Odin.
http://www.justanotherdev.slackdev.com/T959UVJFD.tar
http://www.justanotherdev.slackdev.com/s1_odin_20100512.rar
Sent from my ZenDroid using XDA Premium App
Same thing here, but I got it finally by using an ancient version of odin to flash to stock jfd. Kies picked it up right away after that.
That said, now that I have no fear of odin there are no traces of kies left on my pc...
Do you know if those file are located some place else, the link doesn't appear to have either file?
Sorry about that. Didn't realize the links were dead.
http://www.multiupload.com/NP507B6P8A
This should have both the pit and tar files in it.
Sent from my ZenDroid using XDA Premium App
SUCCESS!!!!!
Thanks so much. It worked. Now to replace my backup files. No more Kies for me.
I am trying to install the Android 4.3 update released yesterday. I have a Galaxy S4 SCH-i545 (Verizon). The phone currently runs stock firmware and is not rooted. When I press install now, the phone reboots, looks like it is updating, than says error and restarts. A message pops up when the phone restarts stating the update failed due to error 402. I tried to update via Kies, but it says there is no available update in Kies, but my phone says the update is available. Please help me with this issue. I have a lot of data on the phone and I need my warranty to stay intact, so no Odin please.
Error 402
bistwo1 said:
I am trying to install the Android 4.3 update released yesterday. I have a Galaxy S4 SCH-i545 (Verizon). The phone currently runs stock firmware and is not rooted. When I press install now, the phone reboots, looks like it is updating, than says error and restarts. A message pops up when the phone restarts stating the update failed due to error 402. I tried to update via Kies, but it says there is no available update in Kies, but my phone says the update is available. Please help me with this issue. I have a lot of data on the phone and I need my warranty to stay intact, so no Odin please.[/QUOT
I have the same issue. Anybody have any insight ??
Click to expand...
Click to collapse
walshdroid said:
bistwo1 said:
I am trying to install the Android 4.3 update released yesterday. I have a Galaxy S4 SCH-i545 (Verizon). The phone currently runs stock firmware and is not rooted. When I press install now, the phone reboots, looks like it is updating, than says error and restarts. A message pops up when the phone restarts stating the update failed due to error 402. I tried to update via Kies, but it says there is no available update in Kies, but my phone says the update is available. Please help me with this issue. I have a lot of data on the phone and I need my warranty to stay intact, so no Odin please.[/QUOT
I have the same issue. Anybody have any insight ??
Click to expand...
Click to collapse
same problem here...anyone??
Click to expand...
Click to collapse
Maybe similar issue in Verizon can help understand the problem
https://community.verizonwireless.com/thread/785863
Check this out! You , YES! you are an " Android ". Not your phone but U.
Software Upgrade Assistant
Fixed mine! I was also getting the 402 error and the Verizon store had no idea what to do when soft resets didn't work. They told me to do a hard reset when I got home.
I connected to my pc with usb and in the popup (windows 8.1) I selected to install the software upgrade assistant. I ran the assistant and after 10min or so and a phone reboot it said update complete. After that I unplugged my phone from the pc and checked the software update on the phone. It said there was still an update to run so I downloaded and installed it in about 20min and it worked. Now it's up to date.
Hope this helps someone.
need software upgrade assistant file
I delete My file from my phone is there any way you can send me the file
thank you
sublucent said:
Fixed mine! I was also getting the 402 error and the Verizon store had no idea what to do when soft resets didn't work. They told me to do a hard reset when I got home.
I connected to my pc with usb and in the popup (windows 8.1) I selected to install the software upgrade assistant. I ran the assistant and after 10min or so and a phone reboot it said update complete. After that I unplugged my phone from the pc and checked the software update on the phone. It said there was still an update to run so I downloaded and installed it in about 20min and it worked. Now it's up to date.
Hope this helps someone.
Click to expand...
Click to collapse
Sorry, it's been awhile. I no longer have any of the files.
pmontu said:
I delete My file from my phone is there any way you can send me the file
thank you
Click to expand...
Click to collapse
EDIT: Adding what I did to solve this at the bottom.
Hey everyone. Thanks for your time. I'm new to this forum and in a bit of a panic as this is the first time my phone's been so far gone I couldn't find an easy guide to fixing it. I'm not exactly clueless but I'd say I know enough to get myself in trouble, and this time not enough to get myself out. I'll give you the rundown.
Phone:
SCH-I545
Verizon Galaxy S4
Last stable version of Android was 4.4.2
I wish I had the build numbers or anything but since I was using official tools I didn't take any backup steps
Computer:
Macbook Pro Late 2013
OSX Yosemite 10.10.3
(I also have access to a Windows 7/LinuxMint dual boot machine if needed)
Using OEM USB cable connected directly into the USB on the motherboard.
Until yesterday my S4 was happily running 4.4.2, when I received a notification of a new update. I ran both Verizon updates that came through. The first one finished fine, the second one (the actual Lolipop update) kept failing in the bootloader type screen (Odin mode?). It would look like an android on his back with 'Error!' written out then restart to 4.4.2.
I did a bit of reading and found out that if your phone was rooted and unrooted, it may not take the OTA update. I recalled that I used a one-click style, app-based root a while back, and quickly reverted it because I didn't end up needing root anyway. (I think the logo for the rooter apk was a Greek letter but that's all I remember. It's on my SD card still. If it would be useful I can figure out a way to read the SD card through another phone or adapter or something and figure out the name. I think it was Towelroot but not positive)
So as I researched how to do the update, I read a post that said the Verizon Software Upgrade Assistant would do the job just fine. I figured, since it's a Verizon branded application, I couldn't go wrong. Well, that's where the trouble started.
Everything looked to be going according to plan. The Verizon assistant downloaded the Lollipop update and then began to install it. It booted the phone into what I think is Odin mode and said "Downloading... Do not turn off target!!"
Somewhere in the first third (going by the progress bar) a message popped up on my Mac saying that the phone was unplugged (it wasn't). My phone now displayed a message stating "Software update failed. Your device didn't update successfully. Use the Verizon Software Repair Assistant on a computer to repair your device and complete the update."
Naturally, I attempted to use the Verizon Software Repair Assistant (seems to be part of the same application as the updater) and to my horror found that every time I plug in my phone, the Verizon app crashes immediately! No matter what I do; plug in the phone then open the app, open the app then plug in the phone, app in update mode, app in repair mode, etc., I cannot get the application to keep running when the phone is attached to my Mac. This might be where I did the most damage to myself... In my attempts to clear the crash issue and get the Verizon app working, I clicked something to the effect of "Forget this device" in the Verizon app and all info about my phone was gone. I'm now thinking that included my chance of repairing the broken update, and Kies needs some code to repair from and I think I lost that with the clear
I have not tried the Verizon application on Windows because I can't find it to download it (the phone itself installs the application when you plug it in, but my phone is fried and can't help me right now.) Luckily my wife also has an S4 so when she get's home, I'll be able to try the Verizon application for Windows and see if that can repair.
What I have tried:
Installing Kies on both Mac and Windows and connecting the phone in both "Software Update Failed" mode by simply powering the device on, and in "Downloading..." mode by holding Vol Dwn while powering the device, then saying yes to the confirmation.
I also tried Odin on Windows following this guide – http://forum.xda-developers.com/showthread.php?t=2301259 and I received a missing PIT error.
I found a PIT file and tried it, with the supplied file from the guide, in Odin, but that ends up disconnecting the phone after a second then ending with an error and reconnecting the phone. It wasn't a very descriptive error but I can get more specifics if needed.
Took it to a Verizon store, wasted thirty minutes of my life, left with the same problem and more anger.
At this point I don't want to do more damage so I would really appreciate some advice on how to approach fixing this.
I'd be happy to take any advice and give any further info. Hopefully one of you guys can help me here.
Thanks again for your time and thanks for anyone that might help!!
–––
RESOLUTION
So I was able to get my phone restored and updated to Lollipop, and thanks to my cloud backups I didn't lose my data!
I think my problem was something with my Mac and Phone not getting along together. I'm not sure if it was the Mac version of the Verizon app or some other factor, what I do know is I'm REALLY lucky I have a Windows machine AND my wife has the same phone.
I needed the Verizon app to repair my phone, but I needed the Verizon app on my PC because the Mac version kept crashing when I'd connect my phone. The only source for the Verizon application is to plug the phone into your computer and install it from the phone, which obviously wasn't an option in this case! Luckily I could use my wife's identical S4 to install the utility onto my PC.
Once I was able to do that, I opened the application on my PC, went into Repair Mode by navigating to the Repair tab on the left then selecting Enter Repair Mode or whatever. Then I connected my phone with a clean boot (no special button presses). It was just displaying the error message which instructed me to use the Verizon Repair utility.
After a few seconds the computer recognized the device and it appeared in the list on the repair utility.
I selected the device in the list (it was the only item in the list) then pressed the 'REPAIR DEVICE' button on the right.
It displayed a warning that 'due to the condition of the device' I would lose all of my personal data and settings. I agreed.
The utility then downloaded the latest firmware (the Lollipop update) and proceeded to install it to my device.
After about 15 minutes I had a factory fresh install of Lollipop ready to go!
BONUS, in the initial setup it remembered my settings and automatically offered to restore from a cloud backup. No data loss!!
Hey skullzarmy,
I may be in a similar situation. I to had root awhile back via Towlroot (i think thats the name), received and OTA update. Afterwards checked root with root checker and said No root but SU was found? I assumed I lost root? Now I downloaded the first OTA this morning and it worked. But the second OTA is failing.
I have factory reset my phone and still no worky.
However, I am in the middle of running the Software Repair Assistant as I read your post. We shall see how it goes. Hopefully it does not blow up.
To run the Software Repair Assistant in Windows just plug your phone is and when the prompt appears click the run option. You can install the assistant from there.
Good luck...
Spyke562 said:
Hey skullzarmy,
I may be in a similar situation. I to had root awhile back via Towlroot (i think thats the name), received and OTA update. Afterwards checked root with root checker and said No root but SU was found? I assumed I lost root? Now I downloaded the first OTA this morning and it worked. But the second OTA is failing.
I have factory reset my phone and still no worky.
However, I am in the middle of running the Software Repair Assistant as I read your post. We shall see how it goes. Hopefully it does not blow up.
To run the Software Repair Assistant in Windows just plug your phone is and when the prompt appears click the run option. You can install the assistant from there.
Good luck...
Click to expand...
Click to collapse
Thanks Spyke, I'm just waiting on my wife to get home with her S4 so I can do just that. It's pretty much my only hope. I'm just hoping it doesn't need that device profile that I deleted from my Mac... Good luck with yours! Let me know how it turns out!
OK, quick update. I was able to get the Verizon application installed on my PC and it was able to connect to the phone. It gave me a message saying due to the condition I would lose my data but it would restore it for me. Of course I went with it, so it's doing its thing now. I'll update with how it goes from here.
Please do...in the middle of my repair/update it BSOD my PC and now i think my phone is jacked
Spyke562 said:
Please do...in the middle of my repair/update it BSOD my PC and now i think my phone is jacked
Click to expand...
Click to collapse
Once I got the phone connected to my PC it was smooth sailing.
At what point did you BSOD? What version of Windows are you running?
Glad to hear you got it working!
I think it BSOD somewhere after 50%.
I am on Windows 8.1
Running it again and its a 93% so far.
Phone stuck on Software Update Failed on boot
Spyke562 said:
Glad to hear you got it working!
I think it BSOD somewhere after 50%.
I am on Windows 8.1
Running it again and its a 93% so far.
Phone stuck on Software Update Failed on boot
Click to expand...
Click to collapse
I ran it on Windows 7. Sounds like you are where I was. I'm hoping it was a fluke and pulls through this time! Fingers crossed for you!
skullzarmy said:
I ran it on Windows 7. Sounds like you are where I was. I'm hoping it was a fluke and pulls through this time! Fingers crossed for you!
Click to expand...
Click to collapse
Hey skullzarmy,
looks like keeping your figners crossed help me. After disconnecting my phone, pulling the battery and re-connecting the repair worked and I am back up and running.
Thanks for your help!
Spyke562 said:
Hey skullzarmy,
looks like keeping your figners crossed help me. After disconnecting my phone, pulling the battery and re-connecting the repair worked and I am back up and running.
Thanks for your help!
Click to expand...
Click to collapse
Great news! Not sure I helped but glad we both got our phones up and running again!
Hi guys
I followed this guide for unlock bootloader and install magisk: https://forum.xda-developers.com/t/...re-and-gsi-rom-flashing-without-twrp.4344371/
I don't blame the author of the guide, it is my device, my responsibility, my decision to attempt this. My fault.
Everything was going great, I unlocked the bootloader successfully and my device wiped and rebooted. It boot back into android, I turn off, go to fastboot mode, and try to flash magisk img file I made earlier in the guide. It says success, then last step of the guide is to wipe with fastboot -w. This fails, says cannot wipe metadata. Reboot, now my phone says "your device is corrupted and cannot be trusted and will not boot"
No idea what to do here, so i try to use Xperia Companion to restore. But it refuses because it detect bootloader is unlocked. Now I try to use NewFlasher to flash firmware from XperiFirm, this starts off fine but then NewFlasher reaches this point
"Extracting sparse chunk super.040"
"Uploading sparse chunk C:\temp\xperiafirmware\flash_sesson_super.0.40"
"download:03b4c9c"
"ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress
I have tried to do this with another computer, I have tried 2 other USB cables, I have tried another firmware (originally tried the latest version with open carrier but also tried with carrier specific one) I am now running out of ideas to try.
I can get to fastboot mode or flash mode, but if I try to boot OS it says "your device is corrupted and cannot be trusted and will not boot"
Any help or a point in the right direction would be much appreciated
Thank you so much in advance
Last week that happened to me. As long as you can go to fastboot you're good. First is relock the bootlaloader via fastboot then repair it using xperia companion. Or if you can download the firmware via xperifirm then flash it via flasher.
Also make sure that the PC your using has both an Intel CPU or AMD CPU and a full windows install not that cheap windows store only crap..but one you can actually install windows .exe files and make sure you have installed the Xperia drivers by turning off driver verification...o tried without and my 2 in 1 couldn't find my phone for Xperia companion nor the other flashing tool...
Thank you @Mangtas_666 @Ainz_Ooal_Gown I have no idea why but I just couldn't flash the UK firmware, tried 2 versions but neither would flash with NewFlasher. kept getting these timeout errors. But then i randomly decide to try the US firmware (XQ-BC62 instead of XQ-BC52) and it worked 1st try. My phone is up and running again!
The strangest part, when it connect to the internet and I apply all my UK settings, it somehow change back to XQ-BC52 on its own. It is detected as such in "about phone" now even though I didn't re-install firmware since fixing it with the US one. Oh well, i'm not going to complain, I'm just happy it's fixed. Thanks for replying
marshedpotato said:
Thank you @Mangtas_666 @Ainz_Ooal_Gown I have no idea why but I just couldn't flash the UK firmware, tried 2 versions but neither would flash with NewFlasher. kept getting these timeout errors. But then i randomly decide to try the US firmware (XQ-BC62 instead of XQ-BC52) and it worked 1st try. My phone is up and running again!
The strangest part, when it connect to the internet and I apply all my UK settings, it somehow change back to XQ-BC52 on its own. It is detected as such in "about phone" now even though I didn't re-install firmware since fixing it with the US one. Oh well, i'm not going to complain, I'm just happy it's fixed. Thanks for replying
Click to expand...
Click to collapse
No problem fam, glad it got sorted out