Stuck in setup with missing files and can't get stock ROM to flash - Blu Vivo 5

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?

Related

Enable USB Debugging from Computer

It is possible to enable USB debug from computer? I need to delete some file from the internal memory that causes the problem. I can't connect through adb at all.
I'm trying to fix my secondary phone (Garminfone) that that loads into desktop, but force close launcher and everything else. The only thing that I can do is connect to the computer for file sharing with the phone.
Thank you in advance.
I'm in a bit of a conundrum, myself...
I am attempting to do this, too, but for a totally different reason.
I am a VZW agent trying to extract contacts for a customer from a Moto. RAZR with a completely non-functional touch screen (no display, no function). Phone boots up fine, no sweat. Stock ROM, no backup :crying:, all of the typical means of transfer have been exhausted.
More or less, the only chance I have at succeeding is to either:
Enable USB debugging through some kind of shortcut or trick, or
Somehow, without USB debugging, figure out the user name for the customer's G-mail account (he has two, and cannot remember/doesn't use the one with all his contacts...)
Wouldn't be surprised if it's simply not possible.... but maybe somebody with a bit more knowledge can let us know! :good:
Edit: Hmm, not possible to run adb from the bootloader, but you can run Fastboot commands. None of those seem to be of use for these purposes though...
as mentioned by PhantasmRezound, It's not possible, However. adb is enabled in most recoveries. Also If the device is unlocked ( and you can flash custom recoveries ) in any way you can flash a custom recovery, back up the boot img. pull that off the device or simply put the sdcard in your computer with unpack that, edit the init.rc to start adb. and reflash it with fastboot not quiet what your after but might do the trick.
or
With the non functioning touch screen issue, If the device acts as a usb host, plug a mouse in and away you go
There's always a way.
Thanks for the input...
I appreciate the feedback, but the way I read it... it's either not going to help in this situation, or it's too technical for a noob such as myself and I'm in over my head
If the device is unlocked ( and you can flash custom recoveries ) in any way you can flash a custom recovery, back up the boot img. pull that off the device or simply put the sdcard in your computer with unpack that, edit the init.rc to start adb. and reflash it with fastboot not quiet what your after but might do the trick.
Click to expand...
Click to collapse
Customer's phone is completely stock. Hope I'm following along correctly, but I don't think this is possible without having something like ClockworkMod and pre-existing root access?
With the non functioning touch screen issue, If the device acts as a usb host, plug a mouse in and away you go
Click to expand...
Click to collapse
Never really tried this... but, I suspect, this won't work... not only does the touch screen not work, but the display is black.
I suppose it could be possible in combination with HDMI-out... but since the HDMI has never been set to "mirroring," I cannot simply plug it in and go (the best and only result I've gotten in this case is the red "M" logo on the screen...)
I would have given up on this hours ago, but it really bothers me when I can't figure out how to do something that appears to be so fundamental and simple...
Thanks for the inputs :good:
jad57pitt said:
Customer's phone is completely stock. Hope I'm following along correctly, but I don't think this is
possible without having something like ClockworkMod and pre-existing root access?
Click to expand...
Click to collapse
Well, I was thinking about this, and I think you can do adb in a stock recovery, should be able to create a backup image with the right software. It all gets a little hazy and wolly on techinical details, so I'm afraid I can't help anyone there.
jad57pitt said:
appreciate the feedback, but the way I read it... it's either not going to help in this situation, or it's too technical for a noob such as myself and I'm in over my head
Click to expand...
Click to collapse
And you're a noob , I fully understand that my casual, off the cuff, do a,b,c etc reply assumes a lot of technical knowledge, If it's not your phone man, don't stress it too much ..... Just hand it back to them look blankly into the middle distance while shaking your head.....use the following phrase " Nah man you've F*ed this up good, did you not sync it up with your google account at anytime "
Sorry man, I'm drunk, probably shouldn't be at this keyboard now
trevd said:
as mentioned by PhantasmRezound, It's not possible, However. adb is enabled in most recoveries. Also If the device is unlocked ( and you can flash custom recoveries ) in any way you can flash a custom recovery, back up the boot img. pull that off the device or simply put the sdcard in your computer with unpack that, edit the init.rc to start adb. and reflash it with fastboot not quiet what your after but might do the trick.
or
With the non functioning touch screen issue, If the device acts as a usb host, plug a mouse in and away you go
There's always a way.
Click to expand...
Click to collapse
Unfortunately, Garminfone is a piece of garbage, lol. There's no custom recovery for it. There is nothing I can do now, I guess. I can't get into fastboot or anything because every time I try adb or fastboot it would not recognize the device.
wolftou said:
Unfortunately, Garminfone is a piece of garbage, lol. There's no custom recovery for it. There is nothing I can do now, I guess. I can't get into fastboot or anything because every time I try adb or fastboot it would not recognize the device.
Click to expand...
Click to collapse
If nothing else, you can do a Factory Reset. You'll lose all data but it will be running again.
Make sure the phone is charged up since this will take a while.
With the phone off, hold down left on the d-pad as you power it on. It will show "Wipe User Data" and then you can let go of the buttons. Just leave it for an hour or so, it will go about wiping and restoring system files from it's own recovery partition.
Also, random Garminfone blog with interesting entries to read while waiting on your phone lol. The person started to develop a port for CWM:
http://mygarminfone.blogspot.com/
PhantasmRezound, I've done tons of wipes but no luck and I'm familiar with the website you posted. Everytime I wipe, I get force process com.android.setupwizard stopped unexpectedly on the phone.
@wolftou
Ok.... A couple more tricks to try for your specific device and then I'm all out of ideas plus it's kinda getting away the original question/topic
1 Android Safe Mode:
Android does have a safemode, exactly the same idea as windows safemode, only needed apps are loaded. This might let you remove the troublesome app.
How to get into it on your device? I have no idea and from my limted research ( google as always ), it appears to vary by manufacturer and probably device. I have booted my tablet into it a couple of times by accident but never really stopped to figure out how, that's not important anyway Just I can confirm this mode exists ( In some androids at least ).
2 Flashing an alternative rom:
Have you tried flashing a different rom? I'm not sure of your model number so I don't whether this is relevant to you but have a look at this thread it looks like you can trigger an update using a sdcard swap trick....
I'm thinking about buying one myself now... just to see what's possible with them, fortunately ( for my wallet at least ) they are not available in the UK and I've got plenty of things to fill my Android addiction for now :laugh:
all answer not similliar the question
across tablet 8"
i have 8 inc across tablet,i cannot open my tab,,i think the operating not found,,how can i install it..because i cant open the system ,,unit help me pls...
actually i got canvas doodle 2 with no external sd support nd my usb debugging mode is off nd no backup is there in my phone...
but there is adb sideload...is there any way to enable usb debugging? and my phone is rooted and it is stucked at boot logo
Alternative usb debugging...
Hey my phone is stuck in an bootloop.....is there anyway to enable usb debugging even tho i cant get into the phone
My lenovo vibe s1 is showing black screen
I tried rooting my phone by the steps given by your site and now my phone is showing black screen. i tried pressing volume buttons and power button still it is not working. so when i am connecting my phone to computer it gets connected for 1 min and disconnects and again connects after 1 min. so is there any possible way that i can send my phone to USB debugging through computer.
I need use my samsung j2 mobile on pc bcoz my mobile display is not working.
usb debugging off
Keyah Cort said:
Hey my phone is stuck in an bootloop.....is there anyway to enable usb debugging even tho i cant get into the phone
Click to expand...
Click to collapse
mine too... how to enable usb debugging? please help...
trevd said:
as mentioned by PhantasmRezound, It's not possible, However. adb is enabled in most recoveries. Also If the device is unlocked ( and you can flash custom recoveries ) in any way you can flash a custom recovery, back up the boot img. pull that off the device or simply put the sdcard in your computer with unpack that, edit the init.rc to start adb. and reflash it with fastboot not quiet what your after but might do the trick.
or
With the non functioning touch screen issue, If the device acts as a usb host, plug a mouse in and away you go
There's always a way.
Click to expand...
Click to collapse
Can you create a step-by-step tutorial? I have a LG Leon. Stock. Bluetooth/Wi-Fi disabled. My Google account won't accept. I've been trying to find ways to enable "Developer Options", "USB Debugging" just so I recover access. ADB and most of the programs I've used required USB Debugging, or wireless access.
Hello Everyone, I hope the you can help me with my request, How can I enable the USB debugging mode in android vers. 2.2.2 to 2.3.4
I really had a hard time since my Huawei Ideos s7-105 screen had been broken. I am not sure if the USB debugging was enabled. I have a really have a good reasons why I need to recover the files from my device.
Hoping for your kind response and help.
Monsterkid09
I'm sorry. I'm in doubt. I have a problem: Navon predator 10 tabs have dropped my gmail account. Adb debug off (or something you see 1-2 programs see something in adb mode but only in device info.If anything else i want always say do not connect. Very strong frp protection.What can I do?

Phone will not get past "Vibrant - Samsung" screen

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.

[Q] p769 - softbricked by noob

i finally figured out how to get CWM installed and working, after a couple of months of fighting with it, off and on. so, i guessed that meant i have my bootloader unlocked - "wrong!".
i deleted some thing that wasn't supposed to be deleted, then the damned cell network and lan network stopped working (keeps saying com.android.phone has stopped). so i was going to put cyanogenmod on it, because i thought that i could, and just be done with the whole "missing apps" crap. it turns out "just because you CAN put CM on it doesn't mean you CAN put CM on it". i bricked it. i have NO options to "load" or "flash" or "boot" any thing when the phone is booting up. i would love some clarification as to what i CAN do from here.
i would rather install CM and be done with all of this, but i'll take any advice that gets rid of the problem. the biggest problem is understanding how to put CM on your phone, or to do any thing at all like that, when you cant get into any kind of recovery / boot menu, even though you ARE rooted... i don't care if i have to install cyanogenmod or some one else's CWM backup, i just don't know HOW to do it - especially with no windows (only linux). it's a rooted p769v20d (originally p769v10g).
thanks
sentientsystem said:
i AM rooted, but i have NO options to "load" or "flash" or "boot" any thing when the phone is booting up. i deleted some thing that wasn't supposed to be deleted, now the damned thing doesn't work (keeps saying com.android.phone has stopped), so i was going to put cyanogenmod on it, but not sure how. i keep seeing people mention CWM, and i installed that from google play, but i don't know what to do with it.
i was going to try some stuff mentioned in other threads, but i don't have access to a windows computer - and i don't think i need to root my phone again any way, considering it is still rooted.
i would love some clarification, and assistance, as to what i CAN do from here. i am rooted, i don't care if i have to install cyanogenmod or some one else's CWM backup, i just don't know HOW to do it - especially with no windows (only linux). it's a rooted p769v20d (originally p769v10g).
fwiw, regarding the mysterious deleted app:
i lose my internet signal as soon as it says "com.android.phone has stopped", then i get it back again right before it says that message again - it ALSO shows a cell-phone signal right before that message. this repeats over and over and over every few seconds - aggravating as hell...
here's the apps that i still have installed: http://forum.xda-developers.com/showthread.php?p=45774770
again, i would rather install CM and be done with all of this, but i'll take any advice that gets rid of the problem. the biggest problem is understanding how to put CM on your phone, or to do any thing at all like that, when you cant get into any kind of recovery / boot menu, even though you ARE rooted...
thanks
=== EDIT ===
i finally figured out how to get CWM installed and working, after a couple of months of fighting with it, off and on. so, now i guess that means i have my bootloader unlocked?
Click to expand...
Click to collapse
Nice thread title. That is how I am feeling right now with this phone. I feel like calling tech care and yell at them for a bit to vent. Anyway, why not install fastboot for Linux and flash the ics u and x? I uploaded my u and x folder in the Unlock Bootloader for Noobs thread. Then, flash the 20h.....oh, dang.... sorry. Forgot.... no Windows. Maybe do the built-in restore by holding the volume down, home and power keys?
Sent from my TBD753B using XDA Premium HD app
thanks, but i think i finally got it working. i never knew, after all this time, that after you do the l9recoveryinstaller, at the reboot, there are no cues to tell when when to hit some buttons, and it's not clear what buttons to hit. here's what i did, and, so far, its progress:
1: be rooted
2: install busy box, completely
3: install l9recoveryinstaller
4: reboot
5: after you see the LG logo, hold vol-down until you see the flashing lights (i thought you see the flashing lights and THEN you hit vol-down, but i was wrong).
still fighting to get a rooted rom installed ...
if i choose "install zip from external sdcard" is says:
"finding update ... opening update ... installing update ...installation aborted".
if i choose "restore" instead of "install" it will not let me select any thing, it just keeps saying file not found, when i try to select any further options, whether "restore" or "restore from external sdcard" or "advanced restore from external sdcard". and i already checked to make sure the sdcard was mounted...
sentientsystem said:
thanks, but i think i finally got it working. i never knew, after all this time, that after you do the l9recoveryinstaller, at the reboot, there are no cues to tell when when to hit some buttons, and it's not clear what buttons to hit. here's what i did, and, so far, its progress:
1: be rooted
2: install busy box, completely
3: install l9recoveryinstaller
4: reboot
5: after you see the LG logo, hold vol-down until you see the flashing lights (i thought you see the flashing lights and THEN you hit vol-down, but i was wrong).
still fighting to get a rooted rom installed ...
if i choose "install zip from external sdcard" is says:
"finding update ... opening update ... installing update ...installation aborted".
if i choose "restore" instead of "install" it will not let me select any thing, it just keeps saying file not found, when i try to select any further options, whether "restore" or "restore from external sdcard" or "advanced restore from external sdcard". and i already checked to make sure the sdcard was mounted...
Click to expand...
Click to collapse
I think your phone bootloader is locked, you cannot flash any custom rom zip file. It will soft brick your phone.
Please restore P769 CWM back from this thread http://forum.xda-developers.com/showthread.php?t=2136204. Download backup file and unbzip it. Put extract files in your sdcard /clockworkmod/backup/2013-08-30.12.00.00 folder. Extract file should contain several .img, .tar, .a, .log and .md5
artit said:
I think your phone bootloader is locked, you cannot flash any custom rom zip file. It will soft brick your phone.
Please restore P769 CWM back from this thread http://forum.xda-developers.com/showthread.php?t=2136204
Click to expand...
Click to collapse
too late - bricked it... currently looking for a way to unf*ck myself...
BTW, those were the ones i WAS trying to flash...
thanks
sentientsystem said:
too late - bricked it... currently looking for a way to unf*ck myself...
BTW, those were the ones i WAS trying to flash...
thanks
Click to expand...
Click to collapse
Then try to use LG mobile support tool to recover your phone. Load it from LG website, start your phone to S/W upload mode, connect usb then start program and select recover phone from menu.
artit said:
Then try to use LG mobile support tool to recover your phone. Load it from LG website, start your phone to S/W upload mode, connect usb then start program and select recover phone from menu.
Click to expand...
Click to collapse
i don't have a windows computer. looks like i'm out a 350$ phone. lesson learned. never will cease to be amazed that so many mobile hackers are using windows... seems like they would be linux users too... that would be awesome, because then there are likely to be linux tools to do this with... and i don't have a windows img to load into a virtual machine... lucky lucky lucky...
thanks any way...
sentientsystem said:
i don't have a windows computer. looks like i'm out a 350$ phone. lesson learned. never will cease to be amazed that so many mobile hackers are using windows... seems like they would be linux users too... that would be awesome, because then there are likely to be linux tools to do this with... and i don't have a windows img to load into a virtual machine... lucky lucky lucky...
thanks any way...
Click to expand...
Click to collapse
Well correct me if I am wrong, but I guess you "only" deleted some system files, right? Do you remember which ones were the ones? Or at least the folder they were in? Then you only need to extract that stuff from a kdz/ the bin file and push them on your phone using adb or maybe even the dd command.
Maybe if someone is kind enough, he ll probably provide you with the files you need. And cmiiw, but I guess you deleted stuff from /system/app...
Sent from my LG-P760 using xda app-developers app
sentientsystem said:
i don't have a windows computer. looks like i'm out a 350$ phone. lesson learned. never will cease to be amazed that so many mobile hackers are using windows... seems like they would be linux users too... that would be awesome, because then there are likely to be linux tools to do this with... and i don't have a windows img to load into a virtual machine... lucky lucky lucky...
thanks any way...
Click to expand...
Click to collapse
Lol, you are a Linux user, you should know how to get your hands on a windows.iso
However, i would recommend using a portable windows xp (bootable usb)
VR is not the best option IMO
You will need this program http://unetbootin.sourceforge.net/
&
Sorry I can't provide a link to the iso but do a google search for
portable windows xp bootable usb Osheraj
artit said:
Then try to use LG mobile support tool to recover your phone. Load it from LG website, start your phone to S/W upload mode, connect usb then start program and select recover phone from menu.
Click to expand...
Click to collapse
okay, what do i need to download to load onto the phone? kdz images, right? i'll check and see if i can find a kdz in the forum, and borrow a windows computer. i think i got it - this thread: http://forum.xda-developers.com/showthread.php?t=2107971
sentientsystem said:
okay, what do i need to download to load onto the phone? kdz images, right? i'll check and see if i can find a kdz in the forum, and borrow a windows computer.
Click to expand...
Click to collapse
It's depend on what method you use. You can flash kdz using offline method here http://forum.xda-developers.com/showthread.php?t=2085344
or use LG mobile support tools from LG website. If you choose this you don't need to download any kdz. It'll download kdz automatically from LG server then flash it on your phone. It take about an hour or two.
artit said:
It's depend on what method you use. You can flash kdz using offline method here http://forum.xda-developers.com/showthread.php?t=2085344
or use LG mobile support tools from LG website. If you choose this you don't need to download any kdz. It'll download kdz automatically from LG server then flash it on your phone. It take about an hour or two.
Click to expand...
Click to collapse
thats awesome - i wonder if i can get by with using that on wine on linux, instead of borrowing a windows computer... i'm gonna try it...
well, the verdict is in, on this one: i'm screwed. i've tried and tried and tried and tried and tried and tried and tried and tried and tried and tried and tried and tried, and i can NOT flash this damned phone. it's BRICKED.
i borrowed / hijacked my brother's computer (windows7), all day. i tried a few different things - i even tried the same way i flashed it to update it ( http://forum.xda-developers.com/showthread.php?t=2356536 ), which was worthless to unbrick it.
the problem in every case was that every time the damned flasher got so far along it would "lose the connection to the phone". drivers installed, etc, etc, no difference. i suspect its because i couldnt connect it in all the various modes (mtp ptp etc), since the ONLY way it would connect is in "software upgrade mode".
i had to buy another phone, won't have it till tuesday. lesson learned: NEVER buy a phone that didn't come from samsung... you just can't do what you want with them, without a lot of time, patience, experience, and a windows computer.
thanks for all the help.
sentientsystem said:
well, the verdict is in, on this one: i'm screwed. i've tried and tried and tried and tried and tried and tried and tried and tried and tried and tried and tried and tried, and i can NOT flash this damned phone. it's BRICKED.
i borrowed / hijacked my brother's computer (windows7), all day. i tried a few different things - i even tried the same way i flashed it to update it ( http://forum.xda-developers.com/showthread.php?t=2356536 ), which was worthless to unbrick it.
the problem in every case was that every time the damned flasher got so far along it would "lose the connection to the phone". drivers installed, etc, etc, no difference. i suspect its because i couldnt connect it in all the various modes (mtp ptp etc), since the ONLY way it would connect is in "software upgrade mode".
i had to buy another phone, won't have it till tuesday. lesson learned: NEVER buy a phone that didn't come from samsung... you just can't do what you want with them, without a lot of time, patience, experience, and a windows computer.
thanks for all the help.
Click to expand...
Click to collapse
Did you try to recover your phone with LG mobile support tool. It can reinstall rom in almost any soft-brick case. Please try it if you haven't try it yet. Many people restore their phone by that software. The steps are
- Download LG mobile support tool from LG web site
- Boot you phone to S/W update mode
- Run Tool and select recover phone
- Wait about 1-2 hours to download and flash
If it's not hardware problem, this should solve your problem
artit said:
Did you try to recover your phone with LG mobile support tool.
Click to expand...
Click to collapse
i never found that on their website, and i looked quite a few times. however, i noticed when i used the b2clientsetup.exe that if i run it without running the shttp server first, that it downloads a support tool from the net, which does not work - keeps saying phone lost connection. not sure if its the same tool.
sentientsystem said:
i never found that on their website, and i looked quite a few times. however, i noticed when i used the b2clientsetup.exe that if i run it without running the shttp server first, that it downloads a support tool from the net, which does not work - keeps saying phone lost connection. not sure if its the same tool.
Click to expand...
Click to collapse
Yes that tool. In my region, it has download link but for P769 it has request repair service.
Download from http://tool.xcdn.gdms.lge.com/client/app/B2CAppSetup.exe
You must remove following lines from hosts file
127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com
Then run it
artit said:
Yes that tool. You must remove lines from hosts file. Then run it
Click to expand...
Click to collapse
yeah, that's exactly what i did, but it would keep "losing the connection to the phone". not sure why, but i suspect it was a driver issue - and i installed the latest drivers, which made no difference. i also went back and installed older drivers, which made no difference. i must just be lucky as hell, or some thing .
sentientsystem said:
yeah, that's exactly what i did, but it would keep "losing the connection to the phone". not sure why, but i suspect it was a driver issue - and i installed the latest drivers, which made no difference. i also went back and installed older drivers, which made no difference. i must just be lucky as hell, or some thing .
Click to expand...
Click to collapse
Try to use others USB ports, if that also doesn't work maybe you have to try on other computer.
artit said:
Try to use others USB ports, if that also doesn't work maybe you have to try on other computer.
Click to expand...
Click to collapse
yeah, i tried switching between the usb 3.0 ports and usb 2.0 ports, but it made no difference. i have no access to any other computers, so, that's why i ended up ordering another phone. i'll never buy another phone that is not a samsung...
thanks
In my country (RO) there are some GSM Repair Centers. You should not give up and you should go to them. Par example, I flashed an HTC Mozart when the battery was dead and I bricked it (idiot, I know). I went to a shop like the ones mentioned above and I think he said that he has to flash the phone using a JTAG or something like that (I know that he has to open the phone to reach it's motherboard, solder some **** out there and... flash I guess). The whole thing was about ~20E. Anyway, keep digging, maybe you'll eventually find something that works for you. If not, go to someone who can "force flash" it and maybe you can save the device.

My first Sony Phone.. how to get the basics done?

Could someone give me a super quick guide on how to get this on my phone? I coming from years of Samsung phones and never owned a Sony before or know anything about it. I have CM on all my Samsung devices for years and simply want a CM ROM in the Z and get it done with with. I picked up a 99% like new second-hand Ultra Z LTE C6833 today, has stock 5.02 and I don't have a clue how to get this flashed in the easiest and simplest way possible. As for locked or not bootloader, I also don't have a clue. First step which is to install TWRP I immediately got stuck because the links posted are dead (teamw.in/project/twrp2/219)
Without wanting to waste anyone's time, if someone could give me the simplest and most painless info on how to get the Z flashed, I'd be super appreciative. The threads on this phone are in the hundreds at this point and I read all sorts of very confusing and contradictory info. I worry to kill or brick it immediately before I even get started.
Thanks much in advance
Read. Thats my tip.
Every sony device past 2011 works the same way.
Look at different xperia forums, for example at the Z1 section, Z2, Z3 etc.
Look at the rooting guides. Unlock guides. Ta backup guide. Just read and read.
Dont just look at the first guide and jump right in.. read first.
Explore the Xda forum. You will find the guides im talking about. im on my phone.. a bit difficult to post links atm
Much good information can be found here
http://forum.xda-developers.com/crossdevice-dev/sony
You can check if the bootloader is unlocked or locked by opening the dialer and entering *#*#7378423#*#*. Then tap "Service Info" and then "Configuration". It'll either say "Bootloader unlocked: Yes", or "Bootloader unlock allowed: Yes/No". If it says NO on the latter, then you can't unlock the bootloader and you're pretty much screwed. Bell Canada devices have locked bootloaders, and I believe it's the same with UK O2. Chances are that you can unlock it, but you could of course be really unlucky.
If you can unlock the bootloader, then your Ultra will pretty much behave like a Nexus device when it comes to rooting and stuff like that. Just flash a custom kernel with recovery, like NUT's Dual Recovery (with CWM and TWRP), then flash SuperSU, and you'll have recovery and root. Next step is to flash CM12.1 and you're done. It's very easy once you have recovery.
Klaos3000 said:
You can check if the bootloader is unlocked or locked by opening the dialer and entering *#*#7378423#*#*. Then tap "Service Info" and then "Configuration". It'll either say "Bootloader unlocked: Yes", or "Bootloader unlock allowed: Yes/No". If it says NO on the latter, then you can't unlock the bootloader and you're pretty much screwed. Bell Canada devices have locked bootloaders, and I believe it's the same with UK O2. Chances are that you can unlock it, but you could of course be really unlucky.
If you can unlock the bootloader, then your Ultra will pretty much behave like a Nexus device when it comes to rooting and stuff like that. Just flash a custom kernel with recovery, like NUT's Dual Recovery (with CWM and TWRP), then flash SuperSU, and you'll have recovery and root. Next step is to flash CM12.1 and you're done. It's very easy once you have recovery.
Click to expand...
Click to collapse
Thanks MUCH for the detailed info!
I checked the bootloader info as you said and it's not unlocked, but can be done. It seems a daunting task but let me start by trying to get it done. Hopefully I won't screw-up the phone. I'm searching how to do it as there seem to be several ways.. After I complete the unlocking (let's hope) I'll report back and try jump on the next steps. Probably will have some follow-up doubts or questions.. this is all a very different and more complex process than the Samsung devices I've owned that never required any of this crazy gymnastics..
Anyway, thanks again very much and keep you posted!
VeEuzUKY said:
Thanks MUCH for the detailed info!
I checked the bootloader info as you said and it's not unlocked, but can be done. It seems a daunting task but let me start by trying to get it done. Hopefully I won't screw-up the phone. I'm searching how to do it as there seem to be several ways.. After I complete the unlocking (let's hope) I'll report back and try jump on the next steps. Probably will have some follow-up doubts or questions.. this is all a very different and more complex process than the Samsung devices I've owned that never required any of this crazy gymnastics..
Anyway, thanks again very much and keep you posted!
Click to expand...
Click to collapse
I'll give you the short guide:
- Go to this (offical Sony) site and give them your IMEI and whatnot
- Wait a couple of minutes, and you'll receive a key
- Now, there are two ways to unlock the bootloader - both equally official, but the easiest one is to use Flashtool.
- Hit the "BLU" button and enter the key you got fra Sony. You only have to do this once.
- Once this is done, you can start flashing a kernel with recovery and flash whatever you'd like.
I'll help you along the way if you need to, so don't be afraid to ask any questions. Start by unlocking the bootloader, and I'll be here if you need any help.
Klaos3000 said:
I'll give you the short guide:
- Go to this (offical Sony) site and give them your IMEI and whatnot
- Wait a couple of minutes, and you'll receive a key
- Now, there are two ways to unlock the bootloader - both equally official, but the easiest one is to use Flashtool.
- Hit the "BLU" button and enter the key you got fra Sony. You only have to do this once.
- Once this is done, you can start flashing a kernel with recovery and flash whatever you'd like.
I'll help you along the way if you need to, so don't be afraid to ask any questions. Start by unlocking the bootloader, and I'll be here if you need any help.
Click to expand...
Click to collapse
Hello I am new to Sony too and I have a question. If I unlock the bootloader root flash custom roms and then decide to get back to stock and lock the bootloader will my warranty be voided?
Sent from my C6833 using Tapatalk
mike13ftw said:
Hello I am new to Sony too and I have a question. If I unlock the bootloader root flash custom roms and then decide to get back to stock and lock the bootloader will my warranty be voided?
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Yes, and that's why it's a good idea to backup your TA folder, which contains the DRM keys. Once you unlock the bootloader, these keys disappears, and that's why it's a good idea to make a backup of them. There are a couple of tools that does this for you, and you can find them in the cross-development section.
Klaos3000 said:
I'll give you the short guide:
- Go to this (offical Sony) site and give them your IMEI and whatnot
- Wait a couple of minutes, and you'll receive a key
- Now, there are two ways to unlock the bootloader - both equally official, but the easiest one is to use Flashtool.
- Hit the "BLU" button and enter the key you got fra Sony. You only have to do this once.
- Once this is done, you can start flashing a kernel with recovery and flash whatever you'd like.
I'll help you along the way if you need to, so don't be afraid to ask any questions. Start by unlocking the bootloader, and I'll be here if you need any help.
Click to expand...
Click to collapse
Thank you very much!
Well so far EVERYTHING HAS BEEN A TOTAL NIGHTMARE! Nothing I try to do works!
First I installed flashtool, latest version. Im running Windows 7 64bit. It was a nightmare to get flashtool downloaded and installed. After I finally got it installed, ot took another hour updating itself and syncing stuff. When it finally finished and while holding down the Volume Down key I connected the phone to the PC via USB cable, Immediately I get an error of device driver errors. flashtool gives me also several errors. Then I tried to install the Flashtool-drivers-1.1-20130911. Then another problem, the drivers dont install at all with a message "DPinst.exe cannot execute on your operating system". That's it, finished! When I go to the Windows Device Manager, all I see is an exclamation mark under S1 Service.
So then I tried the FastBoot method. Also no luck. While holding down the Volume Up key I connected the phone to the PC via USB cable, the phone's blue light turns on, and again I get a DRIVER NOT INSTALLED ERROR. My computer refuses to recognize the phone and the device driver is never installed . The Windows Device Manager shows an exclamation mark under S1Boot FastBoot.
Then I tried the Sony way and installed the Android SDK!!!!! Immediately I find I need to download more crap, thie time the JRE Development Kit! Takes me 3 hours do download this with my useless internet connection. At this point I am already ready to throw my laptop out the window and break the stupid phone in a million pieces!
But then, there is the next problem. After all downloaded and installed, before I can even started I get stuck again, because Im supposed to go to the android SDK folder c:\android-sdk\extras\google\usb_driver and replace/install the fastboot drivers “android_winusb.inf”.. well, I dont have an extras or google or usb_driver folder on my SDK installed folder! NOTHING! THIS IS ALL RIDICULOUS!
Finally I searched everywhere on the internet for other possible Ultra Z drivers. I ft to Sony's own site and found Xperia Z Ultra (C6833, C6806, and C6843) drivers, Xperia Z Ultra (XL39h) drivers, Xperia Z Ultra (SOL24) drivers, Xperia Z Ultra (SGP412) drivers and others.. this is all crazy what a nightmare of mess and miss-information everywhere about this phone! Anyway, I tried all of them. None works.
I am so frustrated and desperate. My God! Cant get anything done. Nothing.................................. I cant believe this..
UPDATE: I give-up. Ive spent the whole day and downloaded and installed GIGS of apps and software and drivers. Nothing communicates with this useless phone. Im done.
Could anyone give me advice if its there is an alternate way to, root install a recover and flash this piece of **** phone without unlocking the bootloader which basically I cant do? If not, it will fly out the window asap, I cant deal with this ridiculous drama. Years of handling and flashing all sorts of hardware COMBINED, never gave me 1/10th of the misery and headaches this hardware has given me in one day. Xperia, never again..
By the way, Sony's "AMAZING" PC Companion app is so great and fantastic that it doesn't even have an uninstaller! No joke! Once in the computer, crawling endless directories with all sorts of files, drivers and registry entries, it will NEVER come out again. All is amazing..
You did the opposite of what I advised you to do. You did not read correct guides.
Q:Ask yourself what do you want to achieve?
You wrote in your first post "if someone could give me the simplest and most painless info on how to get the Z flashed".
Q:My counterquestion is why? Is your phones software unstable? Are you curious to learn to modify the devices software?
A:If your device is unstable. Please do a factory reset.
Q:Are you curious to learn how to modify the software?
A:Then collect information. Read. Set a timer for how long you will spend learning. Let say 45 minutes.
When 45 minutes has passed. STOP.
Take a break. Do something else and continue the next day. Repeat until you are confident to try a simple operation
For example: learn how to use adb and fastboot. Learn the commands. What they do.
I can not stretch enough how important it is to read and learn before you jump into things.
I do not see why I or anyone here should help you to unlock your bootloader. Because you do not have a clear purpose or knowledge how to do this.
VeEuzUKY said:
UPDATE: I give-up. Ive spent the whole day and downloaded and installed GIGS of apps and software and drivers. Nothing communicates with this useless phone. Im done.
Could anyone give me advice if its there is an alternate way to, root install a recover and flash this piece of **** phone without unlocking the bootloader which basically I cant do? If not, it will fly out the window asap, I cant deal with this ridiculous drama. Years of handling and flashing all sorts of hardware COMBINED, never gave me 1/10th of the misery and headaches this hardware has given me in one day. Xperia, never again..
By the way, Sony's "AMAZING" PC Companion app is so great and fantastic that it doesn't even have an uninstaller! No joke! Once in the computer, crawling endless directories with all sorts of files, drivers and registry entries, it will NEVER come out again. All is amazing..
Click to expand...
Click to collapse
That what I did for the drivers and work just fine .Try it
Edit: forgot to post link http://forum.xda-developers.com/showthread.php?t=2095087
Sent from my Xperia Z Ultra using Tapatalk
SÜPERUSER said:
You did the opposite of what I advised you to do. You did not read correct guides.
Q:Ask yourself what do you want to achieve?
You wrote in your first post "if someone could give me the simplest and most painless info on how to get the Z flashed".
Q:My counterquestion is why? Is your phones software unstable? Are you curious to learn to modify the devices software?
A:If your device is unstable. Please do a factory reset.
Q:Are you curious to learn how to modify the software?
A:Then collect information. Read. Set a timer for how long you will spend learning. Let say 45 minutes.
When 45 minutes has passed. STOP.
Take a break. Do something else and continue the next day. Repeat until you are confident to try a simple operation
For example: learn how to use adb and fastboot. Learn the commands. What they do.
I can not stretch enough how important it is to read and learn before you jump into things.
I do not see why I or anyone here should help you to unlock your bootloader. Because you do not have a clear purpose or knowledge how to do this.
Click to expand...
Click to collapse
Just to briefly correct you: I'm the type of guy that has NEVER gotten a virus on a computer. I'm the type of guy that has rooted, flashed and played around with phones for many years with more or less degree of difficulties, but always successful. I'm the type of guy that has helped many many people in this community with their hardware, when I know how. I'm the type of guy that has knows many things about the works of Samsung devices that I have used for many years and have never had an issue learning what's needed. I am the type of guy always ready to offer friendly advice when someone is in need of something I may offer help with. Finally, I am the kind of guy that has a Dell laptop, running Windows 7 64bit, that by whatever reason refuses to install the proper drivers for the Ultra Z, or the kind of guy that maybe has a flawed Ultra Z. After all, it's a second hand unit and about 2 years old, despite that it looks new.
So, the only thing this type of guy can do, is 1) try a different computer to see if the communications with the phone work, and if not, check the phone because obviously that's where the only place the problem can come from. To try different USB cables and do phone resets, that I did today several times. I learned those basics the first day of my flashing life, long long ago.
There is NOTHING to read or learn or do, when there is no communication between the phone and the computer that connects to it. You seem not to understand the very basics of the problem here is not lack of reading, instead is only lack data flow between devices.
Anyway, thanks for the constructive advice!
2 extra things: all the tools, apps and drivers you have suggested, I have them all. All the procedures, steps, folders where stuff is and goes.. I've done all. I learn very quickly. The issue is none of that.. the issue is, no driver for this phone will install on my laptop, for whatever reason. Is that simple.
And then there is another issue.. for you, and most people on XDA, downloading and getting "stuff" is a breeze. But not me. Where I am, XDA is blocked, and even with a VPN, hardly works. To reply to you or just log-in, sometimes is an hour. And most file hosts? Mega? Rapidgator.net? Zippy share?.. a few hundred others? Well.. they doesn't work. Uploaded.net.. Mediafire.. Google Drive.. AndroidFile Host, and just about everything else, all DON'T WORK. All blocked. So are blocked most of the VPNs now. So, while for you, go here, get this, download that, is all a piece of cake, for me, is not. Most things to get download are truly a nightmare. And when it comes to download a ROM or any 2 or 3 hundred Mg files, sometimes takes me days of endless wait and interrupted downloads. I live in a crazy country called China, where all Google stuff, Android included, is forbidden, and all around it.. XDA included.
So, talk is easy. But when access to simple and basic information is so difficult to get and everything comes at a premium, life is really a bit more complicated than maybe you can imagine. So...... yeah, help is very much appreciated indeed, in the same way I am always willing to help others when I can, without calling out their lack or reading or question their abilities to follow my advice
Alright, that was quite painful to read, not because of something wrong you wrote, but because I've been there too. I don't know what device you had prior to the Ultra, but just forget what you learned from that device.
Just sit down, relax and figure out what you're trying to do, and then how to maybe achieve it. Yes, I do understand that your laptop doesn't cooperate at all, but that's just technology. Of course it won't work when it should. We've all been there.
1. Set up your computer to be able to communicate with your Ultra. Installing the SDK is overkill since the only thing from the SDK you need is Fastboot and ADB drivers. You can easily install those two by installing this tiny tool that does it for you.
Fastboot and ADB is now installed.
2. Install Flashtool. You've already done this. Connect your Ultra and open Flashtool. Flashtool should grab and set things up for the Z Ultra automatically. This should only take 5-30 seconds. Not three hours. The device should still be powered on at this stage.
3. Okay, now you have Flashtool installed, and it recognizes your Ultra. Next step is to go to that Sony site I linked to, to get the unlock key. Fill in the required info, and you'll get the key sent on your email. Don't misplace it.
4. Go back to Flashtool, hit the "BLU" button, paste the key in, and that's it. Don't set the device into fastboot or flashmode until Flashmode asks you to do it. Fastboot can be active and connected forever, but Flashmode will disconnect by itself after a minute or so.
5. Your bootloader is now unlocked. This means that you're free to do whatever you'd like to do with it. Xperia devices do not come with a default recovery system, so we'll have to flash a custom kernel that includes a recovery. You can find them in the dev section. Once you've flashed or hotbooted a custom kernel with CWM or TWRP, you're free to root by flashing SuperSU, and flash whatever ROM you'd like to flash.
It's very easy to deal with Xperia devices once you have things set up (mainly Flashtool), and the basic steps are:
- Unlock bootloader (one time thing)
- Flash custom kernel
- Done
It's the same procedure as Nexus devices, only that we have to use special tools to unlock our bootloaders, while Nexus' use one command in a terminal. The issue here though is the tools, and not the process, and I feel your pain. I really do. It would've been so much easier if I could just show up at your door, do it for you, and leave
---------- Post added at 06:46 PM ---------- Previous post was at 06:43 PM ----------
VeEuzUKY said:
And then there is another issue.. for you, and most people on XDA, downloading and getting "stuff" is a breeze. But not me. Where I am, XDA is blocked, and even with a VPN, hardly works.
Click to expand...
Click to collapse
Then let's make it easier? My upload speeds aren't an issue, so please point to a site that I can upload the tools too, which you then can download from at proper speeds
Klaos3000 said:
Alright, that was quite painful to read, not because of something wrong you wrote, but because I've been there too. I don't know what device you had prior to the Ultra, but just forget what you learned from that device.
Just sit down, relax and figure out what you're trying to do, and then how to maybe achieve it. Yes, I do understand that your laptop doesn't cooperate at all, but that's just technology. Of course it won't work when it should. We've all been there.
1. Set up your computer to be able to communicate with your Ultra. Installing the SDK is overkill since the only thing from the SDK you need is Fastboot and ADB drivers. You can easily install those two by installing this tiny tool that does it for you.
Fastboot and ADB is now installed.
2. Install Flashtool. You've already done this. Connect your Ultra and open Flashtool. Flashtool should grab and set things up for the Z Ultra automatically. This should only take 5-30 seconds. Not three hours. The device should still be powered on at this stage.
3. Okay, now you have Flashtool installed, and it recognizes your Ultra. Next step is to go to that Sony site I linked to, to get the unlock key. Fill in the required info, and you'll get the key sent on your email. Don't misplace it.
4. Go back to Flashtool, hit the "BLU" button, paste the key in, and that's it. Don't set the device into fastboot or flashmode until Flashmode asks you to do it. Fastboot can be active and connected forever, but Flashmode will disconnect by itself after a minute or so.
5. Your bootloader is now unlocked. This means that you're free to do whatever you'd like to do with it. Xperia devices do not come with a default recovery system, so we'll have to flash a custom kernel that includes a recovery. You can find them in the dev section. Once you've flashed or hotbooted a custom kernel with CWM or TWRP, you're free to root by flashing SuperSU, and flash whatever ROM you'd like to flash.
It's very easy to deal with Xperia devices once you have things set up (mainly Flashtool), and the basic steps are:
- Unlock bootloader (one time thing)
- Flash custom kernel
- Done
It's the same procedure as Nexus devices, only that we have to use special tools to unlock our bootloaders, while Nexus' use one command in a terminal. The issue here though is the tools, and not the process, and I feel your pain. I really do. It would've been so much easier if I could just show up at your door, do it for you, and leave
Click to expand...
Click to collapse
Klaos3000, you are great. Difficult to find words to thank you the time you take to try help me out. Really much appreciated. It's almost 1AM my local time here and tomorrow I will give a try to all you suggest me step by step. If I run into additional difficulties, I will try use another computer. Maybe is my specific laptop with my windows installation that is being stupid with the Ultra Z hardware. I have installed endless drivers for HTC, LG and mainly Samsung phones and tabs, and have never had any difficulty.. just last week I installed drivers for a friend's new Galaxy Tab S2, got a recovery in, got it rooted and manually cleaned of a lot of useless samsung system bloat stock apps and crap, all about 20 minutes. Hard to understand why with an Xperia phone, things are so complicated. Anyway, tomorrow will follow your advice and report back.
Again, thanks a lot for your help
Klaos3000, despite being so late, I decided to give this another try and follow your steps.
But I Immediately run into similar problems.. I CANNOT get drivers installed.
1. I have downloaded and installed Minimal ADB and Fastboot as you suggested.
2. I have flashtool-0.9.19.7 installed and did the 0.9.19.8 upgrade by updating the x10flasher.jar file.
3. Now you suggest I connect my phone and open Flashtool. But connect my phone how? Boot it up? USB debugging on or off? Or you mean connect the phone turned off and then on press Volume up? Or press Volume down?
I tried all this, and again I get a device driver error. Because there are NO DRIVERS installed for the phone. This is same problem as before. And if I go to the drivers folder inside Flashtool and try install the drives, I immediately get an error that they cant be installed in my operating system.
I am completely stuck as before in this very simple step.
Attached screnshots when I enter Flashmode:
And this is what happens when I try install drivers from C:\Flashtool\drivers:
And if I try go to FastBoot Mode with the phone's blue light on (Volume up + connect USB Cable) this is what I get:
UPDATE:
I have finally unlocked the bootloader, using the Fastboot method! I still could not get the Flashtool drivers to recognize my phone, but the FastBoot ADB drivers installed without a problem. 2 things Ive learned with this experience I want share with anyone in the future that has similar difficulties:
1) I switched to a friend's old laptop with Windows XP. Under XP, FastBoot ADB drivers installed at the first time and absolutely zero problems.
2) I used a USB 2.0 port! If connected to a USB 3.0 port, another cascade of new problems immediately arise.
So that's it. I want thank VERY MUCH everyone in this thread that was so kind to try and help me as much as possible. I would not have gotten this done with it
My next step is to install a recovery from:
http://forum.xda-developers.com/showthread.php?t=2261606
But I only see downloadable versions for looked bootloaders. Also, I want to flash a custom CM based ROM next and see a warning regarding Unlocked Bootloader with CyanogenMod, AOSP and OmniRom that the kernel needs be repack to replace the built in recovery with XZDualRecovery or things will either not work at all or require unexpected operating instructions. So again, I am extremely confused as what files to choose and what to do and worry to look for the wrong thing and worry to make a catastrophic mistake. And also I have no idea what method I should use:
- ZU-lockeddualrecovery2.8.21-RELEASE.flashable
- ZU-lockeddualrecovery2.8.21-RELEASE.installer
Thanks again for the advice and the feedback in all this

Moto X (2014) Model: XT1092, Error: Failed to validate system image

So my Moto X (2014) which is around 20 months old just up and started giving this problem. When I try to boot it, it just goes to the fastboot screen and gives the error: "Fastboot reason: Failed to validate system image". The usual fastboot options like Normal Power up, factory, recovery, etc show up, but no matter what I select it gives the error: "Failed to validate system image. Boot up failed". I tried to attach some images, but being a new user was unable to link them.
Now the thing is, I am a complete noob at this stuff. So all I did was try to use adb sideload to try and re-flash the official ROM. But the adb command window doesn't seem to detect my device. Also, I'd just like to add, when I connect my phone to the PC, the standard windows sound of a USB being connected is heard, I don't know if that means anything, but I just thought I'd put it out there.
So obviously, the next thing I did was approach the service center. After a days inspection, they said, and I quote "There is an issue with the motherboard and/or PCB". I don't know what a PCB is. To fix the issue it's gonna cost me INR 12500, which is almost as much as a new phone. When I asked if they had tried re-flashing the ROM, they didn't seem to understand what I was saying, which made me a little skeptical. So, I came home and tried with the adb again, without any luck of course. Only this time when I connect my USB, I get a new error: "Fastboot reason: UTAG 'bootmode' configured as fastboot. USB connected".
Is there any way to fix this?
Or do I use it as a door stopper?
Thank you for any help in advance.
You should find some helpful info over this way: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515. You must make sure to find the correct firmware for your model and the storage that it has.
es0tericcha0s said:
You should find some helpful info over this way: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515. You must make sure to find the correct firmware for your model and the storage that it has.
Click to expand...
Click to collapse
Hi, first of all, thanks for the reply, really appreciate that.
Okay, so I went through the post you referred me to, and I have a few questions regarding that, if you don't mind.
1) The phone in that post is the Moto X (2013), I have the 2014 model (the 2nd Gen). Does it make any difference? or is it the same procedure?
2) It says "Return to stock". I never left the stock ROM. Never rooted the phone, didn't even unlock the bootloader. I'm not even sure if my USB debugging was enabled.
4) Most of the download links on the post seem to be dead.
How should I proceed?
Again, thanks for any help in advance.
souamguha said:
Hi, first of all, thanks for the reply, really appreciate that.
Okay, so I went through the post you referred me to, and I have a few questions regarding that, if you don't mind.
1) The phone in that post is the Moto X (2013), I have the 2014 model (the 2nd Gen). Does it make any difference? or is it the same procedure?
2) It says "Return to stock". I never left the stock ROM. Never rooted the phone, didn't even unlock the bootloader. I'm not even sure if my USB debugging was enabled.
4) Most of the download links on the post seem to be dead.
How should I proceed?
Again, thanks for any help in advance.
Click to expand...
Click to collapse
I'm terribly sorry about the mix-up with the generation. I was half asleep looking through the forum.
This is the one you need: http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
I realize that you have not modified the phone, but this is how you reload the software+firmware back to the phone, or what you referred to as "flashing the stock rom" to the shop you took your phone to. If this fails, there's not much else that you would personally be able to do to fix the device.
USB Debugging on does not matter as you can boot directly to the bootloader by powering off, then press the power and volume down buttons simultaneously.
Good luck!
es0tericcha0s said:
I'm terribly sorry about the mix-up with the generation. I was half asleep looking through the forum.
This is the one you need: http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
I realize that you have not modified the phone, but this is how you reload the software+firmware back to the phone, or what you referred to as "flashing the stock rom" to the shop you took your phone to. If this fails, there's not much else that you would personally be able to do to fix the device.
USB Debugging on does not matter as you can boot directly to the bootloader by powering off, then press the power and volume down buttons simultaneously.
Good luck!
Click to expand...
Click to collapse
Okay, so I followed the thread exactly. But I can't get past the first step. When I type in "adb devices" on the adb command window, nothing shows up on the device list. (Note: My phone is already in the AP fastboot mode. I don't know if adb is supposed to detect it when it's in that mode).
But, Motorola device manager is able to detect my phone. When I run Motorola device manager with my phone connected, it searches for "repair software" for a while and then gives a pop-up saying "Your software is up to date" (and the name of the ROM installed).
Any further advice?
Thanks.
Use the fastboot method since you're in the bootloader. The adb is only mentioned there as an alternative way to get to the bootloader. Since you are there, skip that step.
Sorry for the late reply. But turns out the Boot IC of my motherboard was faulty. Whatever I did, it would always get stuck on the fast boot screen. Replaced my motherboard and now it's all good .
Thanks for all the help guys.

Categories

Resources