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!
Related
Here is the problem:
My phone is stuck on the screen you see immediately after pressing the power button, which has a big "Vibrant" and a smaller "Samsung" both white on black. Whatever I do, it won't get past that.
Here is what happened:
- I had Eclair on it for a long while, and updated to Froyo via Kies, also a long while ago. Then, tired of bad performances, I followed a tutorial to install ICS on it. It worked fine for a month and I was very pleased of the newly gained performances. However this week, (while I was on vacation away from my computer and even internet in fact) it started giving me messages saying something about "Memory low, close some applications" (paraphrasing), even thought my memory indicator said that I was using around 160 MB, which should not be that bad. Then, after a couple of hours like that, applications started to crash (because of low memory I assume). I killed applications not that useful, but it did not change the message. Then, the core application also started to crash, whatever I did. I rebooted several times to get it to start fresh, but as soon as I booted, I got the low memory message and the core crashing. At one point, it would get stuck on the ICS 3D flying boot scene, and not past that.
- So, I rebooted in recovery mode and tried to see if I had an option to just restore part of the ROM so I could use my phone anew. I wanted to avoid restoring it completely since I did not have the information about my APN (I have the T-Mobile Vibrant, but I live in Canada and I'm on Videotron's network), and performances before ICS where really bad (lagging, freezing, name it). Also, I figured it was only a booting problem, so (biggest mistake is here I believe) I tried to restore the boot only. I found somewhere in the advanced options of Clockwork an option to restore parts of the backed-up ROM. So I did it, but I got an error saying something about the checksum I think. There I realized that I was trying to restore an Eclair boot backup to an ICS ROM, so the checksum error probably came from that. I try it a second time... same result. Then, when I rebooted it stopped at the Vibrant screen I described above.
What I tried to resolve it:
- Tried to go back to recovery mode by holding the three buttons as usual. Cannot get in. The only thing that "works" is that if I hold the power button for 6-8 second, it will reboot. And get stuck at the same place.
- Search intensively on the web to see if anyone had the same kind of issue. Saw a lot of the "Exclamation mark bricked" type, resolved by going in recovery mode. Not useful to me.
- Tried to connect it to my computer and see where I could go from there. I am unable to mount the device. If the phone is powered down, as soon as I connect it, it starts to boot (and get stuck you know where). Windows does not recognizes the device, and gives me the message "This device cannot start. (Code 10)". I tried to use the drivers from ADB and those from Kies with the same results.
- I tried to install Android Debug Bridge, but without the phone mounted, it doesn't work.
- I tried to see if Odin would detect it, with the same results
- I tried to pray, but there is no answer there yet. :crying:
So here I am, with the following things still untried:
- I would try the "resistor" way of booting in download mode it that could help. However, I don't have soldering iron, don't know how to solder and don't have the parts required, so that would take me a lot of time just the try this option, without any clue that I would resolve my problem with this. I am willing to go that way if I am pretty sure it will work
- I haven't tried using the Riff Box, and I have no idea what it is and where it would get me. I would not even know where to get access to that.
On a final note, this is my only phone in the house, and to make the matter worse, I changed providers with this phone, so my older cell phones don't work with Videotron's SIM card... I would rather have the issue resolved fast if possible, because otherwise, I'll have to buy a new phone. Let's say that I would have better uses for that cash, so I hope it does not come to that.
So that concludes my sad story for today.
Any clues welcome. If the answer is "get a new phone", I would rather do it that trying stuff for two weeks and having to buy a new phone anyway.
Try reinstalling the drivers and add the nexus drivers since some people report that you may need it. Then get into download mode for Odin, on my phone its both volume buttons, but now power, then keep holding while put the USB in. The pit and pda and reparation should be selected, since that's what I do.
Sent from my SGH-T959 using xda app-developers app
pbeaumont said:
- I would try the "resistor" way of booting in download mode it that could help. However, I don't have soldering iron, don't know how to solder and don't have the parts required, so that would take me a lot of time just the try this option, without any clue that I would resolve my problem with this. I am willing to go that way if I am pretty sure it will work.
Click to expand...
Click to collapse
This method should work for you, what your talking about is called a "USB Jig". You can buy one for around $5 online, I would recommend www.mobiletechvideos.com to buy from. Before you buy the jig I would try booting into download mode with the gingerbread button combos just in case you somehow installed them. Download mode is volume + and power button. Recovery is volume - and power.
Sent from my SGH-T959 using Tapatalk
iKoolkid said:
Try reinstalling the drivers and add the nexus drivers since some people report that you may need it. Then get into download mode for Odin, on my phone its both volume buttons, but now power, then keep holding while put the USB in.
Click to expand...
Click to collapse
I uninstalled and reinstalled the drivers several times, to no effect. In fact, whatever driver there is, it does not matter since Windows always give the message about device not able to start. So I just can't use Odin.
iTz KeeFy said:
This method should work for you, what your talking about is called a "USB Jig". Before you buy the jig I would try booting into download mode with the gingerbread button combos just in case you somehow installed them. Download mode is volume + and power button. Recovery is volume - and power.
Click to expand...
Click to collapse
I just tried the gingerbread combo buttons, but no more results. I will try to get a Jig assembled asap, it would still be faster than ordering it and waiting 10 days to get it. I'll let you know how it goes.
I went and made myself an USB Jig and tada!, it worked!
So I'll now reinstall something with Odin and report a last and final time to confirm everything went right.
Many thanks guys!
Still no joy, I now only get the following message while connection the phone to the computer "windows has stopped this device because it has reported problems. (code 43)". I tried to use the drivers from Kies, the ones from ADB (unsigned, therefore cannot install them on my Windows 7 x64).
Tried to uninstall, then reinstall. Rebooted and reinstalled, and finally tried every USB port on my computer. Always the same result. Anyone has a clue?
Will try tomorrow on the computer @ work...
pbeaumont said:
Still no joy, I now only get the following message while connection the phone to the computer "windows has stopped this device because it has reported problems. (code 43)". I tried to use the drivers from Kies, the ones from ADB (unsigned, therefore cannot install them on my Windows 7 x64).
Tried to uninstall, then reinstall. Rebooted and reinstalled, and finally tried every USB port on my computer. Always the same result. Anyone has a clue?
Will try tomorrow on the computer @ work...
Click to expand...
Click to collapse
Have you tried a different usb cable?
Sent from my SGH-T959 using Tapatalk
Tried it on a different computer, with a different USB cable. Both cables and computer used to work to connect the phone.
I am at a loss for options to try right now... Any suggestion?
Just to clarify, if Odin is up and you connect your phone to the computer, does Odin give you a com port?
sent from my magic box to yours
samsgun357 said:
Just to clarify, if Odin is up and you connect your phone to the computer, does Odin give you a com port?
sent from my magic box to yours
Click to expand...
Click to collapse
Nope, not at all. The OS never gets to the point where it detects correctly the phone and mounts it.
First thing I have to ask is do you have a stock front facing camera?
sent from my magic box to yours
samsgun357 said:
First thing I have to ask is do you have a stock front facing camera?
sent from my magic box to yours
Click to expand...
Click to collapse
^^^You learn fast my friend. I'll hit you up a bunch of thanks later on when I get off work. I've hit my limit for the day already on my PC and I can't whip out my phone while I am here.
OP, I am following this thread cause I have a spare Vibe that is doing somethings similar and not being recognized by my PC. I have actually read your OP more than a few times and tried all that you have, even sent it away to a developer friend of mine. He hasn't been able to get it to recognize yet either. Xenoism is in the same boat too. Keep trying and if you get Odin to see it, please come back here and post how. We'll do the same.
Here is another thread about it (Help please! Unique problem!!!)
samsgun357 said:
First thing I have to ask is do you have a stock front facing camera?
sent from my magic box to yours
Click to expand...
Click to collapse
No, it is a T-Mobile Vibrant, and thus has only one camera facing the back. However, I fail to see how it could be relevant...
Woodrube said:
^^^You learn fast my friend. I'll hit you up a bunch of thanks later on when I get off work. I've hit my limit for the day already on my PC and I can't whip out my phone while I am here.
OP, I am following this thread cause I have a spare Vibe that is doing somethings similar and not being recognized by my PC. I have actually read your OP more than a few times and tried all that you have, even sent it away to a developer friend of mine. He hasn't been able to get it to recognize yet either. Xenoism is in the same boat too. Keep trying and if you get Odin to see it, please come back here and post how. We'll do the same.
Here is another thread about it (Help please! Unique problem!!!)
Click to expand...
Click to collapse
Ok, thanks for that. Today, Ill go buy myself a new phone (probably SIII) since I don't seem to have much other choices. I'll still try to get this one to work and keep you posted if I get any results.
I recently got my new Verizon Galaxy S4 and decided to play around with it. I got it rooted fine and got a few apps on there (like Titanium backup) and decided that, since I would eventually want to play around with ROMs, I would want to unlock the phone.
I looked around and found there were some options for me, the one I chose being the "all in one" option that roots, unlocks and installs a custom recovery mode for you. I went through this process and now get nothing but the Downloader Mode (could not do normal boot). Even if I pop out the battery and try to reboot it, I get this screen.
I later found that apparently the ME7 model currently will not accept attempts to unlock the phone and install a custom ROM or recovery menu. How do I fix this? I tried using Odin, but it doesn't recognize the phone as being connected. I am currently trying other methods like Kies, to see if there is any way to at least to an emergency recovery and get it back to normal.
EDIT: Ran into the same issue with Kies as I did with Odin, it does not see anything connected to the computer.
Do you have the correct drivers installed? Does adb recognize the device? You're in Odin mode when you try to use Odin to push something? I believe with ME7 you can Odin back to the official stuff.
Sent from my SCH-I545 using Tapatalk 4
TheColdOne said:
I recently got my new Verizon Galaxy S4 and decided to play around with it. I got it rooted fine and got a few apps on there (like Titanium backup) and decided that, since I would eventually want to play around with ROMs, I would want to unlock the phone.
I looked around and found there were some options for me, the one I chose being the "all in one" option that roots, unlocks and installs a custom recovery mode for you. I went through this process and now get nothing but the Downloader Mode (could not do normal boot). Even if I pop out the battery and try to reboot it, I get this screen.
I later found that apparently the ME7 model currently will not accept attempts to unlock the phone and install a custom ROM or recovery menu. How do I fix this? I tried using Odin, but it doesn't recognize the phone as being connected. I am currently trying other methods like Kies, to see if there is any way to at least to an emergency recovery and get it back to normal.
EDIT: Ran into the same issue with Kies as I did with Odin, it does not see anything connected to the computer.
Click to expand...
Click to collapse
You need to make sure you have the drivers for the phone and have a solid USB connection (I prefer the rear of a tower)
sent from my GE gs4
I ended up getting it to work. I had to go here:
http://www.intel.com/support/chipsets/inf/sb/CS-013541.htm
and get files to get the computer to recognize the device. Even afterwards, Keis had no idea what was going on, and Odin saw it and was able to install a stock firmware I downloaded earlier, saving the phone.
For now I will be satisfied with just root access and will wait for ROM capabilities.
I hate to hijack a thread but I'm stuck here. My GS 4 (Vzw) was supposedly successfully rooted using TWRP, but now I have no way to enter any sort of recovery. The package I downloaded for the root does not have an Odin version to run. I've been getting the endless prompts to install the 4.3 update but there is no way to do this on my phone. I get the same "Could not do normal boot. Odin mode. Write protection enabled" message with the downloading screen. I try to boot into recovery via CWM or Goomanager but it always goes to the same screen. I can't make any backups or restore now either or I would just do a factory reset. Any ideas? I'm on VRUAME7.
Um.... there's no recovery available with ME7.... are you on the MDK bootloader?
Sent from your mom's smartphone
I don't think so but how would I confirm? I'm just trying to get the 4.3 update installed but at every attempt it goes into Odin Mode and gets stuck.
BoltsRUs said:
I don't think so but how would I confirm? I'm just trying to get the 4.3 update installed but at every attempt it goes into Odin Mode and gets stuck.
Click to expand...
Click to collapse
You're said that you're on ME7 - what you need to do is to flash the "No wipe" ME7 ROM onto your phone. It's in the Development forum.
http://forum.xda-developers.com/showthread.php?t=2301259
You've got to update to MI1 before you can install the 4.3 update (MJ7).
ONLY flash files intended for whatever release you're running. You can't mix and match, can't go backwards, and can't skip updates.
Theres also an ml1 factory image in the dev section.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
TheColdOne said:
I ended up getting it to work. I had to go here:
and get files to get the computer to recognize the device. Even afterwards, Keis had no idea what was going on, and Odin saw it and was able to install a stock firmware I downloaded earlier, saving the phone.
For now I will be satisfied with just root access and will wait for ROM capabilities.
Click to expand...
Click to collapse
Hi! Sorry to kind of "butt in" on your thread, but I'm somewhat of a noob and have the same exact problem as you. If you don't mind, can you explain what you downloaded from Intel and what you did afterwards that fixed your problem? I'd really appreciate it, since my phone's been dead to me for more than a week now....
nyankat said:
Hi! Sorry to kind of "butt in" on your thread, but I'm somewhat of a noob and have the same exact problem as you. If you don't mind, can you explain what you downloaded from Intel and what you did afterwards that fixed your problem? I'd really appreciate it, since my phone's been dead to me for more than a week now....
Click to expand...
Click to collapse
On that page I linked to, look for this:
Solution:
Download and run the Intel® Chipset Software Installation Utility so Windows* properly recognizes the SMBus controller.
Get the proper driver download according to your OS, then install it. This should allow Odin to see the phone for you to install a clean copy of the stock ROM onto the phone.
If you want more details I am sorry to say I cannot provide them. When things involve me fixing my own technology, it is a lot of rapid-fire troubleshooting and I just go with what sticks without really memorizing what I did (so if I run into this issue again, I have to re-research).
TheColdOne said:
On that page I linked to, look for this:
Solution:
Download and run the Intel® Chipset Software Installation Utility so Windows* properly recognizes the SMBus controller.
Get the proper driver download according to your OS, then install it. This should allow Odin to see the phone for you to install a clean copy of the stock ROM onto the phone.
If you want more details I am sorry to say I cannot provide them. When things involve me fixing my own technology, it is a lot of rapid-fire troubleshooting and I just go with what sticks without really memorizing what I did (so if I run into this issue again, I have to re-research).
Click to expand...
Click to collapse
Thanks! Finally Oden recognizes my phone
my amazing method
the same problem was with me 3-4 weeks ago...
follow the url-
dbloo dbloo dbloo dot autoroot dot chainfire dot eu
(i cant post the URL because the website is not allowing me.....understand and use the code)
1) choose your samsung model and download the recovery file
2) download and open odin on a dekstop
3) connect your device to the dekstop
4) press the volume down, home button and power button together till the screen changes
5) press the volume down button again
6) odin will show the message "attatched or connected"
7) click pda
8) attatch the file you downloaded
9) your device will be fixed and will be restarted
ur welcome
hai i am stuck at download mode with message as could not normal boot how to fix it
Alright. I have lurked XDA for a long time and this is the first time in seven years of WinPhone/Android flashing I have felt the need to create an account and actually ask a question myself. I really, really did try to find the answers on my own.
So here's the story: Bought an Atrix 4G when they first came out a couple of years ago. Used it for a couple of months, upgraded to Gingerbread no problem. Eventually gave the phone to my girlfriend on T-Mobile, so I had to unlock it. I was very clear with my instructions to NEVER update that phone when it prompts for it.
And she was good! For two years she used that phone with minimal problems. She switched to AT&T this summer and got a new phone, so I got the Atrix 4G back. I hadn't touched that thing in two years and when the prompt came up for an update, of course I updated it. I knew, the *instant* I hit the update button I knew, that I was not supposed to do that. I figured whatever, I want to throw Jelly Bean on it anyway, so let it go and I'll sort it all out on the other end.
Well here I am on the other end, and this thing is effed. It gets as far as the Moto logo and DUAL CORE TECHNOLOGY... and just sits. Still says UNLOCKED up in the upper left, so I guess that's a good sign.
So that's where I am now. Here are the problems I have:
-I want to upgrade this to CM 7.2.0, but first I need to be able to talk to it. Every link for the drivers I can find points directly to Motorola's (now defunct) MotoHub site. I found ONE link that didn't, and it was just an installer for Device Manager. So I can't talk to the thing.
-When I try to do a recovery, it fails and I get a splash screen that says www . goapk . com. No idea what that's all about.
-When I try flashing from a ROM on the SD card, it says it completes the install, but still will not boot past the Moto logo.
So guys, I come to you now at my most desperate hour. Help me, XDA. You're my only hope.
b0bert said:
Alright. I have lurked XDA for a long time and this is the first time in seven years of WinPhone/Android flashing I have felt the need to create an account and actually ask a question myself. I really, really did try to find the answers on my own.
So here's the story: Bought an Atrix 4G when they first came out a couple of years ago. Used it for a couple of months, upgraded to Gingerbread no problem. Eventually gave the phone to my girlfriend on T-Mobile, so I had to unlock it. I was very clear with my instructions to NEVER update that phone when it prompts for it.
And she was good! For two years she used that phone with minimal problems. She switched to AT&T this summer and got a new phone, so I got the Atrix 4G back. I hadn't touched that thing in two years and when the prompt came up for an update, of course I updated it. I knew, the *instant* I hit the update button I knew, that I was not supposed to do that. I figured whatever, I want to throw Jelly Bean on it anyway, so let it go and I'll sort it all out on the other end.
Well here I am on the other end, and this thing is effed. It gets as far as the Moto logo and DUAL CORE TECHNOLOGY... and just sits. Still says UNLOCKED up in the upper left, so I guess that's a good sign.
So that's where I am now. Here are the problems I have:
-I want to upgrade this to CM 7.2.0, but first I need to be able to talk to it. Every link for the drivers I can find points directly to Motorola's (now defunct) MotoHub site. I found ONE link that didn't, and it was just an installer for Device Manager. So I can't talk to the thing.
-When I try to do a recovery, it fails and I get a splash screen that says www . goapk . com. No idea what that's all about.
-When I try flashing from a ROM on the SD card, it says it completes the install, but still will not boot past the Moto logo.
So guys, I come to you now at my most desperate hour. Help me, XDA. You're my only hope.
Click to expand...
Click to collapse
Goapk is the recovery from I believe it was romracer or someone. Since then, there have been updated recovery.imgs that can be used. Usually the drivers install automatically when you hook up the device to the computer, but i'm assuming you're referring to adb and fastboot files? Those files are here on xda, off hand i'm not exactly sure which thread, but they are here online. If that's what you need, download them, and then via fastboot flash an updated recovery to your device, then try flashing the ROM following the usual proceedures.
palmbeach05 said:
Goapk is the recovery from I believe it was romracer or someone. Since then, there have been updated recovery.imgs that can be used. Usually the drivers install automatically when you hook up the device to the computer, but i'm assuming you're referring to adb and fastboot files? Those files are here on xda, off hand i'm not exactly sure which thread, but they are here online. If that's what you need, download them, and then via fastboot flash an updated recovery to your device, then try flashing the ROM following the usual proceedures.
Click to expand...
Click to collapse
Thank you for your response, but man I really cannot find those drivers anywhere.
I know there are two different drivers I need to have the PC driver and the USB driver... but the only thing I can find *at all* is the Motorola Device Manager. I knew I should have saved those the last time I downloaded them.
b0bert said:
Thank you for your response, but man I really cannot find those drivers anywhere.
I know there are two different drivers I need to have the PC driver and the USB driver... but the only thing I can find *at all* is the Motorola Device Manager. I knew I should have saved those the last time I downloaded them.
Click to expand...
Click to collapse
If the drivers are not automatically being installed, then yes, download Motorola Device Manager for the drivers
palmbeach05 said:
If the drivers are not automatically being installed, then yes, download Motorola Device Manager for the drivers
Click to expand...
Click to collapse
Sure but the motorola device manager only works if you phone its working, cuz when you open the MDM it`ll only look for updates and the shut down... sooo.... any other way?
I was in the same quandary and installing the Motorola Device Manager - is THE only known way to get the drivers for Motorola devices. It should auto detect your phone as Atrix and go ahead. However, I don't think you're going past the bootloader, so not much luck there.
You said, you could still access recovery? Why don't you try the fruitcake stock ATT GB ROM then (from recovery)?
The phone notified me there is a system update so I went ahead. Unfortunately, towards the end, it gave me an error message. I remember seeing the big Android robot lying flat on its back.
Now, the phone is completely dead. When I connect it to my computer I can hear the "new hardware connected" sound then immediately the disconnecting sound. This goes on and on for ever.
I tried using the tools provided on Leagoo's site, but they're useless as the computer is not able to recognize the phone.
Is there a hard reset key combination?
Thanks.
Eddie
silentmonolith said:
The phone notified me there is a system update so I went ahead. Unfortunately, towards the end, it gave me an error message. I remember seeing the big Android robot lying flat on its back.
Now, the phone is completely dead. When I connect it to my computer I can hear the "new hardware connected" sound then immediately the disconnecting sound. This goes on and on for ever.
I tried using the tools provided on Leagoo's site, but they're useless as the computer is not able to recognize the phone.
Is there a hard reset key combination?
Thanks.
Eddie
Click to expand...
Click to collapse
I've here 4 brick-phone (friends have updated with the same result!).
leagoo support didn't answer to my polite email of support.
Anyone can give us a sugestion to recover it!?
j045 said:
I've here 4 brick-phone (friends have updated with the same result!).
leagoo support didn't answer to my polite email of support.
Anyone can give us a sugestion to recover it!?
Click to expand...
Click to collapse
In the end, I was able to finally recover it. I just kept trying and trying: while the phone was connected to the computer, I removed the battery, then I put it back in; as well I was disconnecting it from the computer, then plug it back - I did this several times until the software on the computer was able to recognize it.
Even so, when I managed to reflash it, around 60%-70%, I got a message that it failed; so I tried again - it failed around 80% then I tried one more time and it was successful. Now the phone is working fine.
So my advice to you is to keep trying - leave the software on and click on the "download firmware" or whatever it was called, meanwhile keep unplugging the phone (and play with the battery as well).
Good luck! (you will need it)
Same problem, but leagoo responded with driver, firmware, flash tool, instructions and a video.
But nothing changed, so i have to retry.
Thanks for your post.
Edit:
I was thinking that was a hardware problem with micro usb connector!
ItalianWolf said:
Same problem, but leagoo responded with driver, firmware, flash tool, instructions and a video.
But nothing changed, so i have to retry.
Thanks for your post.
Edit:
I was thinking that was a hardware problem with micro usb connector!
Click to expand...
Click to collapse
i did it! just tried a lot of times, but firmware from leagoo doesn't work, display shows only "stipes".
I found another firmware (don't remember where) and then all things went good.
Now the phone notified me there is a system update, i have to do it?
I beat my head against this for about eight hours yesterday and am at my wit's end. Thanks in advance for any help.
The short version: After rooting my Blue VIvo 5, installing a few apps and setting Nova Launcher as my launcher, I started getting some errors. Apps would fail mysteriously or not launch at all. Reinstalling the apps didn't help. I tried to take an OS update that the phone said was available, but when I tried to update it said the system was damaged and I couldn't install the update.
Well, I thought naively, I'll just remove all my user data and start over. That will restore the original ROM and I'll just start over, right?
BIG mistake.
Now when I try to start up my phone the sequence goes like this:
1. I get a popup that says "Unfortunately, Carefree Launcher has stopped."
2. After clearing that popup I can choose my language.
3. Next I go tot he screen where I choose my wireless connection. Choosing the connection works, but the next screen where I put in my password only allows me to speak - there's no keyboard option. The only time during the process I really laughed was when I saw what Google's voice recognition software tried to enter for the wifi password.
4. I managed to get the password entered by using the OTG dongle and a USB keyboard. After that, though, it goes to the "Checking for updates" screen, at which point it tells me "Unfortunately, Google Play Services has stopped." Then it loops back to the "choose your network" screen.
5. Lather, rinse, repeat.
I managed to get TWRP installed and running, but the stock ROM file I found on another thread (BLU_V0050UU_V09_REPAIR.zip) won't install. SP Flasher (which I also tried) throws a message about a mismatched baseband unit of some kind, and TWRP says there's a file called META-INF/com/google/android/update-binary missing from the archive.
So here I am, asking the community what I can do short of laying out $200 for another phone. I might be able to install the AOSP or CM12 ROMs that are in this forum, and I might do that if I have to replace the phone anyway, but if there's a way to restore the phone to its initial OOB state, I would love to know how to do it.
Again, thanks for any help you can give me.
Update, 16 hours later: I had a flash of inspiration this morning. Since it looked like at any rate I was going to have to get another phone I went ahead and ordered the replacement for same-day delivery. It arrived this afternoon, I unboxed it, set it up and backed it up with "adb backup". Then, I tried to restore the backup onto the bricked phone.
You guessed it. I never saw a notification that the backup was loading. It was the same wifi network, check for updates, broken google play loop again.
So unless someone has a brilliant idea as to how to restore the original firmware, I am going to keep the old bricked phone around and try installing aosp or cm12 on it, whichever looks like it's further along. Maybe both. Why not?
Anyway cheers.
Do you not know how to use SP Flash Tool?
Download the original rom + SP Flash Tool from elsewhere in this forums and flash it. The one for the Gionee S6 or A55 slim on the Marshmallow thread will do. I think someone has posted the original vivo 5 ROM somewhere as well.
Basic steps are open SP Flash Tool.
Load the scatter file (comes with the rom). This will fill a lot of fields in the flash screen (boot, recovery, logo, system, userdata, etc.).
Do not change anything. Click "Start"—this will wipe your phone. If you don't want it wiped, disable the "userdata" field.
Connect your phone properly turned off.
It should detect your phone right away.
Wait for the flash to end.
Disconnect your phone and turn it on.
Should boot alright.
If it doesn't detect your phone, see in Device Manager if your phone is properly recognized. If it's not, download the MediaTek PreLoader USB VCOM drivers.
victorvscn said:
Do you not know how to use SP Flash Tool?
Click to expand...
Click to collapse
Thank you for your reply. In answer to your quesiton: Maybe not. Everybody starts somewhere, and while I have quite a few years of experience in desktop computers, I'm still learning the world of Android. I've flashed quite a few Kindle Fire tablets (that's the origin of my user name, 'nerdfire') but this has been my first experience with a phone.
victorvscn said:
Download the original rom + SP Flash Tool from elsewhere in this forums and flash it. The one for the Gionee S6 or A55 slim on the Marshmallow thread will do. I think someone has posted the original vivo 5 ROM somewhere as well.
Basic steps are open SP Flash Tool.
Load the scatter file (comes with the rom). This will fill a lot of fields in the flash screen (boot, recovery, logo, system, userdata, etc.).
Do not change anything. Click "Start"—this will wipe your phone. If you don't want it wiped, disable the "userdata" field.
Connect your phone properly turned off.
It should detect your phone right away.
Wait for the flash to end.
Disconnect your phone and turn it on.
Should boot alright.
If it doesn't detect your phone, see in Device Manager if your phone is properly recognized. If it's not, download the MediaTek PreLoader USB VCOM drivers.
Click to expand...
Click to collapse
I've got SP Flash running, but it's the Linux version. which I think is the same, as Windows except that it looks like there's a "Download" button rather than a "Start" button. Unless I'm missing something, which could easily be.
I followed the directions above, not checking "userdata", and hit "Download." No response from the program for over 30 minutes. I eventually found the timeout setting, lowered it to 2 minutes, and ran the program from a console window. The console output indicated that SP Flash was finding the proper USB port, but then nothing. No communication with the phone and the program eventually timed out.
It could be a lack of drivers. Linux comes with drivers for most common USB devices baked in, but this might not be one of them. Thanks for the hint - I'll check when I get home later tonight.
Again, I appreciate the help.
NerdFire said:
Thank you for your reply. In answer to your quesiton: Maybe not. Everybody starts somewhere, and while I have quite a few years of experience in desktop computers, I'm still learning the world of Android. I've flashed quite a few Kindle Fire tablets (that's the origin of my user name, 'nerdfire') but this has been my first experience with a phone.
Click to expand...
Click to collapse
Sorry about that, mate, I came out rather bluntly for some reason. Just wanted to ask whether you'd had any experience with it.
NerdFire said:
I've got SP Flash running, but it's the Linux version. which I think is the same, as Windows except that it looks like there's a "Download" button rather than a "Start" button. Unless I'm missing something, which could easily be.
I followed the directions above, not checking "userdata", and hit "Download." No response from the program for over 30 minutes. I eventually found the timeout setting, lowered it to 2 minutes, and ran the program from a console window. The console output indicated that SP Flash was finding the proper USB port, but then nothing. No communication with the phone and the program eventually timed out.
It could be a lack of drivers. Linux comes with drivers for most common USB devices baked in, but this might not be one of them. Thanks for the hint - I'll check when I get home later tonight.
Again, I appreciate the help.
Click to expand...
Click to collapse
I have no experience flashing with Linux, but that definitely looks like lack of the right drivers. Maybe following this tutorial will work for you: https://forum.xda-developers.com/ge...torial-how-to-setup-spflashtoollinux-t3160802
The thread says you need to know the specific way to boot up after connecting the cable, depending on the phone. On the Vivo, my experience is that you don't need to press anything, just connecting the cable with the phone powered off will do. However, if you happen to brick your phone by flashing something wrong, or interrupting a flash, you'll need to press volume down upon connecting the cable.
victorvscn said:
Sorry about that, mate, I came out rather bluntly for some reason. Just wanted to ask whether you'd had any experience with it..
Click to expand...
Click to collapse
No worries, I didn't take offense.
victorvscn said:
I have no experience flashing with Linux, but that definitely looks like lack of the right drivers. Maybe following this tutorial will work for you: https://forum.xda-developers.com/ge...torial-how-to-setup-spflashtoollinux-t3160802
The thread says you need to know the specific way to boot up after connecting the cable, depending on the phone. On the Vivo, my experience is that you don't need to press anything, just connecting the cable with the phone powered off will do. However, if you happen to brick your phone by flashing something wrong, or interrupting a flash, you'll need to press volume down upon connecting the cable.
Click to expand...
Click to collapse
I did a little digging and won't go through all the gory details, but the long and short of it was, after removing a package in my Linux distribution that was interfering with accessing the serial port, I was able to flash the stock ROM onto the phone. So I am good to go. Plus, now I have a good idea of how to start over again if necessary
Thank you again so much for your help.,
NerdFire said:
No worries, I didn't take offense.
I did a little digging and won't go through all the gory details, but the long and short of it was, after removing a package in my Linux distribution that was interfering with accessing the serial port, I was able to flash the stock ROM onto the phone. So I am good to go. Plus, now I have a good idea of how to start over again if necessary
Thank you again so much for your help.,
Click to expand...
Click to collapse
Good to hear!
NerdFire said:
No worries, I didn't take offense.
I did a little digging and won't go through all the gory details, but the long and short of it was, after removing a package in my Linux distribution that was interfering with accessing the serial port, I was able to flash the stock ROM onto the phone. So I am good to go. Plus, now I have a good idea of how to start over again if necessary
Thank you again so much for your help.,
Click to expand...
Click to collapse
where can I find the stock Rom ? Can you Share link please?