Related
Hello I need a way to restore the phones partitions. Like boot and recovery and u-boot and x-boot and system and cache and data and all the others. The phone has no known partitions. And because of that I am unable to flash my phone back to a working state. I have tried in fastboot to run OEM format. But it failed. If there is something I can flash in a .bin or a kdz I can flash it in software mode. Or if there is a way to do it in fastboot mode I can also do that. But those are the only two things my phone can do right now. And worse is each time I enter either fastboot or software download mode it will only stay on and active for about 2 minutes until the phone shuts off. And I have to start over completely. So I can flash a whole kdz or bin as they take too long. Please help me?!
Sent from my Note II
theshamrockking said:
Hello I need a way to restore the phones partitions. Like boot and recovery and u-boot and x-boot and system and cache and data and all the others. The phone has no known partitions. And because of that I am unable to flash my phone back to a working state. I have tried in fastboot to run OEM format. But it failed. If there is something I can flash in a .bin or a kdz I can flash it in software mode. Or if there is a way to do it in fastboot mode I can also do that. But those are the only two things my phone can do right now. And worse is each time I enter either fastboot or software download mode it will only stay on and active for about 2 minutes until the phone shuts off. And I have to start over completely. So I can flash a whole kdz or bin as they take too long. Please help me?!
Sent from my Note II
Click to expand...
Click to collapse
Are you getting an error of "Remote Partition Doesn't Exist"? If so that usually means you have a hardware problem.
Try this -
http://forum.xda-developers.com/showthread.php?t=2546571
Yes that is what it says.
Sent from my Note II
I am not sure how to do a lelus method. Unless his method is the omap4boot thing normally called fastboot? If so I have done that. If not can you explain how I can do the lelus method?
Sent from my Note II
theshamrockking said:
I am not sure how to do a lelus method. Unless his method is the omap4boot thing normally called fastboot? If so I have done that. If not can you explain how I can do the lelus method?
Sent from my Note II
Click to expand...
Click to collapse
Yeah the lelus method is for fastboot... Did you install the drivers on your PC twice? You have to run the lelus script 2 times to get it to actually work.
You might also want to look at this thread - http://forum.xda-developers.com/showthread.php?t=2585161
I do believe i did the driver correctly and iv done the flashing of the lelus script like 60 times lol
Sent from my Note II
Thanks I'll try this and report back. But I do think I have a hardware issue but it still trys to work so I want to try and fix it lol
Sent from my Note II
theshamrockking said:
Thanks I'll try this and report back. But I do think I have a hardware issue but it still trys to work so I want to try and fix it lol
Sent from my Note II
Click to expand...
Click to collapse
Im pretty sure it's a hardware problem but, Exactly... It's definitely worth trying to fix it.
I got a remote partition does not exist on every count. For the erase commands and for the write commands. So does that mean im **** out of luck? I keep thinking since i can get into fastboot and software mode i should be able to do something but yet nothing is working.
Is there any way to use the omap4boot to send the infor to the phone? Since i cant send the phone into fastboot or software mode without omap4boot it seems to show that that program gets the phone into a more working state maybe it can also do the flashing? or a script to keep the phone in the software mode for longer than 2 minutes?
theshamrockking said:
Is there any way to use the omap4boot to send the infor to the phone? Since i cant send the phone into fastboot or software mode without omap4boot it seems to show that that program gets the phone into a more working state maybe it can also do the flashing? or a script to keep the phone in the software mode for longer than 2 minutes?
Click to expand...
Click to collapse
Unfortunately I think the EMMC is fried...
If you can figure out how to adapt this method and get it to work on the L9 this is probably your only hope -
http://forum.cyanogenmod.com/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/
Other than that you could try taking it to a service center and having them try an OctopusBox to repair it or go where you bought it and try to make a warrant claim.
I know it sucks but I think these are your only real options. I'm not sure about were you live but I can buy a brand new L9 right now for $30 from MetroPCS.
Ouch. And it does look promising the link you provided just not sure if I will be able to make it work for my phone model. But I'm going to look into it. Looks like only one thing might be device specific that I don't already have and may have to make or find someone to make for my phone.
Sent from my Note II
theshamrockking said:
Ouch. And it does look promising the link you provided just not sure if I will be able to make it work for my phone model. But I'm going to look into it. Looks like only one thing might be device specific that I don't already have and may have to make or find someone to make for my phone.
Sent from my Note II
Click to expand...
Click to collapse
I have exact same problem. Only have to fix partitions is by Omap flasher. But we need to port the memory configuration for it. People have done it for galaxy Nexus (Tuna ) and galaxy tab. Omap flasher is the last hope in this phone.
Or
Hardware way would be flashing emmc using Z3X easy JTAG box.
er.davinder said:
I have exact same problem. Only have to fix partitions is by Omap flasher. But we need to port the memory configuration for it. People have done it for galaxy Nexus (Tuna ) and galaxy tab. Omap flasher is the last hope in this phone.
Or
Hardware way would be flashing emmc using Z3X easy JTAG box.
Click to expand...
Click to collapse
I still have the phone and it's still in the same condition. I was never able to get it working I gave up probably the next days as I had spent like a week on it already I had decided it's probably just a brick. I have no idea where or what I was doing with it at that time tho. I know I was only very slightly ever able to see that it wasn't completely bricked like some program was able to see it when connected to the PC. But no lights on the device no nothing. So I have no clue how to fix it.
Sent from my SM-N910T using Tapatalk
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
Hello,
I just jumped on a good deal for Xperia Z5 (E5823) with software issue. Device boots up to the Xperia logo screen and hags there. I am preparing myself for flashing but hoping a simple hard reset might solve the problem. What should my steps be? I already downloaded Flashtool and did some reading on the forum to get myself familiar with the process. Looks like I will need to download FTF file (I am in US, prefer to have unbranded with minimal carrier bloat) and can use your advice on which version/file to start with. Ideally I would want to root as well, but for now more concerned about restoring back to stock. I did read that Lollipop has a better performance, but open to suggestions for whatever is easier/stable. Any guidance/advice is appreciated (with links to tools or downloads if avail). Is there a way to tell what version # along with region/customization I have installed now?! Should I try the Sony Companion software?
For the record, I have successfully flashed custom ROMS on various Samsung/LG devices, as well as Nexus 4/5. Therefore, feel pretty confident this should not be impossible or any harder. Thanks A LOT.
An update after spending few hours yesterday. PC Companion doesn't recognize the phone when attempting to repair (Vol down + insert USB). It did install few drivers when connected to PC, and it looks like the phone does go into flashmode (as indicated by LED staying green). Then tried the Flashtool, created FTF file (based on tutorial at XperiaBlog) and again the same thing, can't get the phone to be recognized in flashmode. It does respond in fastboot mode and able to get some identifying information. I couldn't find any information on how to flash system, kernel, etc through fastboot (was hoping to use the Flashtool FastBoot mode option, but picking corresponding SIN files resulted is fail errors). I am afraid that flashmode might not work for me as the phone might not have USB debugging enabled (not sure what was done to it and who had it prior).
Are the other alternatives/methods I should try? I wish there was a way to send flash commands from ADB command prompt (like with Nexus phones) and from fastboot mode. Any ideas? Really love the phone, though and want to get it repaired to replace my huge LG! Thanks everyone.
coolmen777 said:
An update after spending few hours yesterday. PC Companion doesn't recognize the phone when attempting to repair (Vol down + insert USB). It did install few drivers when connected to PC, and it looks like the phone does go into flashmode (as indicated by LED staying green). Then tried the Flashtool, created FTF file (based on tutorial at XperiaBlog) and again the same thing, can't get the phone to be recognized in flashmode. It does respond in fastboot mode and able to get some identifying information. I couldn't find any information on how to flash system, kernel, etc through fastboot (was hoping to use the Flashtool FastBoot mode option, but picking corresponding SIN files resulted is fail errors). I am afraid that flashmode might not work for me as the phone might not have USB debugging enabled (not sure what was done to it and who had it prior).
Are the other alternatives/methods I should try? I wish there was a way to send flash commands from ADB command prompt (like with Nexus phones) and from fastboot mode. Any ideas? Really love the phone, though and want to get it repaired to replace my huge LG! Thanks everyone.
Click to expand...
Click to collapse
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
civicsr2cool said:
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
Click to expand...
Click to collapse
I gladly would, except that I am not very comfortable using it due to lack of experience and available zips for my Z5 compact. Can you point me to that info and how to make zips to flash and what to start with? I am willing to try it.
Also, how can I check if my boot loader is unlocked? Can't seemed to find a command to use. Thanks again.
Any pointers for zips or how to flash a rom through fastboot? Thanks.
coolmen777 said:
Any pointers for zips or how to flash a rom through fastboot? Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2277112
We have a couple aosp Roms available to flash, I'd try cm13. I don't know if you've tried to unlock your bootloader yet or not but you should try that. You could also try flashing zombie kernal and see if that'd boot up.
civicsr2cool said:
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
Click to expand...
Click to collapse
civicsr2cool said:
http://forum.xda-developers.com/showthread.php?t=2277112
We have a couple aosp Roms available to flash, I'd try cm13. I don't know if you've tried to unlock your bootloader yet or not but you should try that. You could also try flashing zombie kernal and see if that'd boot up.
Click to expand...
Click to collapse
Thanks for the reply and guidance. I would prefer to stick with Stock Xperia software and launcher. From my experience, CM tends to be buggy and I need full stable functionality with max battery (hoping to give Stamina a test). I am not sure if the bootloader is unlocked and don't want to mess with it unless I absolutely have to (does unlocking BL still messes with DRM keys for camera processing?) Wish I could see if it is unlocked somehow, maybe someone tried to flash/root it and messed up the bootloader somehow.
I will look at zombie kernel (does it need unlocked bootloader or recovery to flash, will it work with stock ROM?) Thanks again for your help.
coolmen777 said:
Thanks for the reply and guidance. I would prefer to stick with Stock Xperia software and launcher. From my experience, CM tends to be buggy and I need full stable functionality with max battery (hoping to give Stamina a test). I am not sure if the bootloader is unlocked and don't want to mess with it unless I absolutely have to (does unlocking BL still messes with DRM keys for camera processing?) Wish I could see if it is unlocked somehow, maybe someone tried to flash/root it and messed up the bootloader somehow.
I will look at zombie kernel (does it need unlocked bootloader or recovery to flash, will it work with stock ROM?) Thanks again for your help.
Click to expand...
Click to collapse
I'm only trying to suggest things that could get the phone working again not permanent solutions lol I don't run cm13 yet as it's definitely not refined. Flashing a stock ftf should be able to bring you to complete original specs without unlocking bootloader or anything.
civicsr2cool said:
I'm only trying to suggest things that could get the phone working again not permanent solutions lol I don't run cm13 yet as it's definitely not refined. Flashing a stock ftf should be able to bring you to complete original specs without unlocking bootloader or anything.
Click to expand...
Click to collapse
Lol, I understand now. It looks like the bootloader might still be locked as I am unable to flash zombie kernel (command: "fastboot flash boot boot.img" results in sending OK, but Failed: remote command not allowed). Looks like I am stuck to trying to unlock a bootloader to keep trying to revive the phone. Just bothers me that I can't get into Flashmode (even after installing drivers that come with Flashtool). Could this be because the phone might not have USB debugging enabled? Is there a way to try to flash the stock through fastboot (as zip) instead of ftf?
My big concern is loosing TA partition and associated DRM keys (any way to back it up from fastboot or toolkit?). Or is that not a factor with the hack available now? Sorry for all these questions, just getting more and more frustrated with this.
coolmen777 said:
Lol, I understand now. It looks like the bootloader might still be locked as I am unable to flash zombie kernel (command: "fastboot flash boot boot.img" results in sending OK, but Failed: remote command not allowed). Looks like I am stuck to trying to unlock a bootloader to keep trying to revive the phone. Just bothers me that I can't get into Flashmode (even after installing drivers that come with Flashtool). Could this be because the phone might not have USB debugging enabled? Is there a way to try to flash the stock through fastboot (as zip) instead of ftf?
My big concern is loosing TA partition and associated DRM keys (any way to back it up from fastboot or toolkit?). Or is that not a factor with the hack available now? Sorry for all these questions, just getting more and more frustrated with this.
Click to expand...
Click to collapse
Come to think of it without getting into the phone to enable unlocking the bootloader I don't think you would even be able to do that. Even if the drivers weren't installed the phone should go into flash mode. I had a hard time with my first attempt with flash tool at getting into flash mode. If you hold power and volume up you should be able to power down the phone completely then hold volume up while plugging in. The problem I had was my PC has a few different USB ports and I was using one that was meant for charging and it wouldn't go into flash mode, tried a different port and it went well after that.
Failed: remote command not allowed ???
This error is because you have not enabled OEM Unlocking from the Developer Option.
If you have enabled it but still receiving the error then you have not unlocked bootloader properly.
There is no need to unlock bootloader for flashing official sony firmwares. It is pretty simple. If you are facing any problems then please feel free to message me.
my email : [email protected]
#coolmen777
Looks like this phone got the dreaded sleep of death bug (won't turn on at all, no matter which combination of buttons I press). Had it on the charger for last 3 days (no led indicators at all and no vibrations), so I got a brick now. Any ideas? This phone should still be under warranty (manufactored week 9 of 2016), but Sony USA refuses to service International phones in their facility. Learned that based on IMEI, this is a Hong Kong version and they want an invoice from authorized dealer for warranty work. Are there are other countries that honor warranty without checking invoice (go by date of manufactoring?) I had Moto and LG repaired before just based on age of phone, no invoice needed. This is my last resort option (to attempt sending in for service).
coolmen777 said:
Looks like this phone got the dreaded sleep of death bug (won't turn on at all, no matter which combination of buttons I press). Had it on the charger for last 3 days (no led indicators at all and no vibrations), so I got a brick now. Any ideas? This phone should still be under warranty (manufactored week 9 of 2016), but Sony USA refuses to service International phones in their facility. Learned that based on IMEI, this is a Hong Kong version and they want an invoice from authorized dealer for warranty work. Are there are other countries that honor warranty without checking invoice (go by date of manufactoring?) I had Moto and LG repaired before just based on age of phone, no invoice needed. This is my last resort option (to attempt sending in for service).
Click to expand...
Click to collapse
search on here for a thread about flashing the wrong ftf onto the phone, I think op used a tablet ftf and had teh same results and had to send to sony
edit:
http://forum.xda-developers.com/z5-compact/help/flashed-wrong-mm-rom-phone-dead-help-t3330929
civicsr2cool said:
search on here for a thread about flashing the wrong ftf onto the phone, I think op used a tablet ftf and had teh same results and had to send to sony
edit:
http://forum.xda-developers.com/z5-compact/help/flashed-wrong-mm-rom-phone-dead-help-t3330929
Click to expand...
Click to collapse
Thanks, not very encouraging given the fact that Sony USA supposedly doesn't currently have a service center to repair international phones (closed their TX center). Are there other countries (Canada or UK) which have less stringent policies of needing invoice (for proof of purchase) and can simply go off of manufacture date from the IMEI or device info? Thanks again.
Hi guys,
I got unlock permissions from Xiaomi today, and I wanted to install Cyanogenmod 13 beta 2 as I hate MIUI with passion. Yet I couldn't unlock my device ("Couldn't verify device" on 50% of verifying). Went through some googling, found out I have to update my 7.3.2.0.0 Global to Developer version. (Yes, I have that infamous 7.3.2.0.0 rom everyone hates and I am trying hard to get rid of it.)
So I tried it. Went to Updater, chose "Choose update package" and chose the package I've downloaded from official miui site, which was located in "downloaded_rom" folder in root right as official manual said.
And the phone turned off and started again.
Yet nothing happened. It just restarted without actually doing anything. My all data are as they were, my version is still 7.3.2.0.0 Global.
Recovery mode update doesn't work, as I don't get that usual recovery mode menu, but just a picture showing me I should plug my Redmi into PC (does nothing when I do).
Fastboot update has this notice underneath it: "If your device is locked. please click here to unlock it first." ... hell, I'm trying to do that whole time, that's why I need to change that ROM first.
I've ran out of options. And so I'm turning to you guys - help me, please.
I'm not an experienced user, haven't owned Android for like 3 years, although I've flashed some roms earlier. But I need to get rid of this vendor rom. Google play services are terribly unstable on it, for example.
Ask me any additional questions you need to know. I'm not married and I own a dog, for example.
Any help is appreciated. Thank you very much.
EDIT: That title doesn't really reflect my thread at all. I just wanted to talk about the first updating option, but then I started ranting about it all and couldn't stop. Please, forgive me the title isn't really pinpoint right.
EDIT2: My recovery looks like this: choimobile *dot* vn/attachments/vao-che-do-download-redmi-3-jpg.21534/ ... as a newbie user I can't post links, so please, exchange that *dot* for an actual dot and you'll see. I don't speak chinese.
I had that too, you need to flash it via fastboot
http://en.miui.com/a-234.html
Edit: or you could flash SpaceX via fastboot without unlocking bootloader, and then flash via the TWRP installed with that. People say that works.
Thing is, I can't see my device in MiFlash. No idea why - on "adb devices" it shows up without any problems, but in fastboot mode it just doesn't cooperate.
Could that be because I'm not using the original cable? Heard it can cause some issues. Can't try it atm sadly.
Sent from my Redmi 3 using Tapatalk
Barty19 said:
Thing is, I can't see my device in MiFlash. No idea why - on "adb devices" it shows up without any problems, but in fastboot mode it just doesn't cooperate.
Could that be because I'm not using the original cable? Heard it can cause some issues. Can't try it atm sadly.
Sent from my Redmi 3 using Tapatalk
Click to expand...
Click to collapse
In normal Google fastboot.exe, I couldn't see my device, but in MiFlash's fastboot.exe, I could.
Open the folder with the fastboot.exe you want to check if it's working, shift+right click and "open command window here", then run "fastboot devices".
Also, to open fastboot mode you need to use power + vol up and it opens to that image, no menu. Or was it vol down? Try the one that opens to that image directly, no menu.
Vol down it was. Anyway meanwhile you were writing your advice I've deleted some drivers that were apparently messing with my device and now I see it in MiFlash! Yay!!!
Well, let's hope I won't screw it now. I'm in a middle of SpaceX download. Should I try to MiFlash a normal MIUI with a locked bootloader, or should I do it through SpaceX?
Barty19 said:
Vol down it was. Anyway meanwhile you were writing your advice I've deleted some drivers that were apparently messing with my device and now I see it in MiFlash! Yay!!!
Well, let's hope I won't screw it now. I'm in a middle of SpaceX download. Should I try to MiFlash a normal MIUI with a locked bootloader, or should I do it through SpaceX?
Click to expand...
Click to collapse
What I did is I installed SpaceX MIUI 8 by ManhIT and it came pre-loaded with TWRP recovery and then I booted into the recovery by MIUI 8's updater app and bam....there you go. Now you can flash any ROM you'd like. Btw, I did this while my bootloader is still locked; never went to Xiaomi to unlock it for me. I've flashed several locked bootloader roms such as CM 13, CM12.1 , and locked versions of MIUI roms and I've never encountered any bricks....yet lol
I DID IT!
Not quite your way, to be honest - the fault was in my already installed (and faulty) PC drivers. Yet I did it with your support and I really appreciate the fact you were willing to help me with the problem. Thank you very much, mate.
Anyway, good night.
*a very happy Barty*
Barty19 said:
I DID IT!
Not quite your way, to be honest - the fault was in my already installed (and faulty) PC drivers. Yet I did it with your support and I really appreciate the fact you were willing to help me with the problem. Thank you very much, mate.
Anyway, good night.
*a very happy Barty*
Click to expand...
Click to collapse
Cheers to you my friend!!
I fear I may have bricked my phone while trying to flash a custom rom. I had TWRP installed. I used it to flash LineageOS and everything seemed to be going correctly, but then I rebooted the device and it after showing the initial splash screen it just turned off again. It only shows the splash screen now if I hold down Volume down and the Power button for 20 seconds. It doesn't boot into recovery mode or download mode and I don't understand why. I don't know if there's anything that could be done in a situation like this, but if anyone might be able to help I'd really appreciate it. The device is still in warranty, but when you turn it on it says that it's not running stock software so I don't know good of an idea it would be to try to get a replacement unit. I've done that before, successfully with another samsung phone I had about 7 years ago.
mimshipio said:
I fear I may have bricked my phone while trying to flash a custom rom. I had TWRP installed. I used it to flash LineageOS and everything seemed to be going correctly, but then I rebooted the device and it after showing the initial splash screen it just turned off again. It only shows the splash screen now if I hold down Volume down and the Power button for 20 seconds. It doesn't boot into recovery mode or download mode and I don't understand why. I don't know if there's anything that could be done in a situation like this, but if anyone might be able to help I'd really appreciate it. The device is still in warranty, but when you turn it on it says that it's not running stock software so I don't know good of an idea it would be to try to get a replacement unit. I've done that before, successfully with another samsung phone I had about 7 years ago.
Click to expand...
Click to collapse
Seems it's completely bricked and will need to reflash in EDL mode
TheExploitedOne said:
Seems it's completely bricked and will need to reflash in EDL mode
Click to expand...
Click to collapse
How do I boot into edl mode?
mimshipio said:
How do I boot into edl mode?
Click to expand...
Click to collapse
Usually through test points in the back of your device. If your able to get into recovery/main OS try adb reboot edl. If not you can able make or buy a deep flash cable that sets the device into EDL mode
TheExploitedOne said:
Usually through test points in the back of your device. If your able to get into recovery/main OS try adb reboot edl. If not you can able make or buy a deep flash cable that sets the device into EDL mode
Click to expand...
Click to collapse
I opened the device but there's no documentation on where the test points are. Will any EDL cable work? As I mentioned already, the device does not boot beyond the bootloader, no matter what.
mimshipio said:
I opened the device but there's no documentation on where the test points are. Will any EDL cable work? As I mentioned already, the device does not boot beyond the bootloader, no matter what.
Click to expand...
Click to collapse
Yep it's definitely in EDL. When you plug it in do you see Qcom HS-USB 9008 (or 9006) or just Qcom USB bulk or similar? If so then that's a good sign that you can recover, but you'll need a programmer that works with your device. Yes a deep flash cable should do the trick if not already in edl
TheExploitedOne said:
Yep it's definitely in EDL. When you plug it in do you see Qcom HS-USB 9008 (or 9006) or just Qcom USB bulk or similar? If so then that's a good sign that you can recover, but you'll need a programmer that works with your device. Yes a deep flash cable should do the trick if not already in edl
Click to expand...
Click to collapse
When I plug it in nothing happens at all. Thanks for the help. I think I'll buy a cable on amazon and see if it works :good:
mimshipio said:
When I plug it in nothing happens at all. Thanks for the help. I think I'll buy a cable on amazon and see if it works :good:
Click to expand...
Click to collapse
Do you not see anything in device manager or hear a connection? Unless your on a different chipset because the PBL cannot be corrupt by software. You're welcome! If you need further help please do send me a PM and we can go from there
TheExploitedOne said:
Do you not see anything in device manager or hear a connection? Unless your on a different chipset because the PBL cannot be corrupt by software. You're welcome! If you need further help please do send me a PM and we can go from there
Click to expand...
Click to collapse
When I plug it in nothing happens at all. If I try to turn it on while it's plugged, I get the charging screen but that's it.
mimshipio said:
When I plug it in nothing happens at all. If I try to turn it on while it's plugged, I get the charging screen but that's it.
Click to expand...
Click to collapse
Hmm seems it can boot into the kernel. Do you know the specs of the device? If it's Qualcomm I can go have a look around and see what I can find to point you into the right direction
TheExploitedOne said:
Hmm seems it can boot into the kernel. Do you know the specs of the device? If it's Qualcomm I can go have a look around and see what I can find to point you into the right direction
Click to expand...
Click to collapse
It's SoC is a proprietary Samsung chip. All Samsungs use proprietary chips afaik. The A10 uses the Exynos 7884.
mimshipio said:
It's SoC is a proprietary Samsung chip. All Samsungs use proprietary chips afaik. The A10 uses the Exynos 7884.
Click to expand...
Click to collapse
I thought they would have implemented a special mode of operation if you got into a brick like that. If the device comes on with the charger then it's probably not fully bricked. I've seen other threads that have had the same issue so you may have to check them out
TheExploitedOne said:
I thought they would have implemented a special mode of operation if you got into a brick like that. If the device comes on with the charger then it's probably not fully bricked. I've seen other threads that have had the same issue so you may have to check them out
Click to expand...
Click to collapse
Really? where have you seen other people with this issue? I've looked on the A10's forums but I found nothing. Could you send me some links?
mimshipio said:
Really? where have you seen other people with this issue? I've looked on the A10's forums but I found nothing. Could you send me some links?
Click to expand...
Click to collapse
Try to look for other devices and search deeply good sir you may find what you need. I use Qualcomm devices because we have a special EDL mode and I have a programmer for all my devices to restore in the case of a hard brick like yours. I've been able to use custom tools to create a restore firmware like the Zone 2 (LG) and flash the device far enough to get it into download mode to flash the KDZ
mimshipio said:
Really? where have you seen other people with this issue? I've looked on the A10's forums but I found nothing. Could you send me some links?
Click to expand...
Click to collapse
You'll need to search with other devices or just in general. I seen posts about it being in some USB mode but Samsung probably don't have that implementation
Hello,
I am currently facing the same problem. Were you able to solve the problem?