Related
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?
Hi all,
I have a Lumia 710, with an unlocked Qualcomm bootloader. Yesterday accidently while flashing a rom as the NAND Disk Drive, whilst doing that i 'didn't' select the OSBL mode & the one beneath it which says W7 Qualcomm, before flashing it. Now it got flashed but the problem is its stuck to one rom. The App deployement tools gives errors such as 'make sure the phone is booted' even though its booted & fine. Or the other error it gives is 'request rejected by host machine'. When connected to Zune i now get pop up from Zune stating 'we can't create a connection from your phone to the internet' now this comes up all the time. I can sync stuff but can't deploy stuff or flash stuff
When i did try flashing the same rom again. After flashing it started directly at the livetiles screen as if nothing happened. I was expecting the 'Welcome to Lumia' screen. Please tell me whats happening. Also i was able to flash another rom on it. However still Zune gives the same error when connected so does the Deployment Tool. I can't figure out what can be done to solve this. I suppose the bootloader might be affected. How do i refresh it? I thought about going to Dload & then Back to Qualcomm. But it seems that many people have bricked phones trying to goto Dload from Qualcomm.
I want my Lumia to be unlocked, but more over, i want it working fine...
Any help & info is appreciated, Thanks
try going back to DLOAD..or do a hard reset to your phone and flash another Custom ROM again.
wen u connect the phone..open device manager and uninstall the drivers..reconnect in same mode..let the drivers reinstall.
surya467 said:
try going back to DLOAD..or do a hard reset to your phone and flash another Custom ROM again.
wen u connect the phone..open device manager and uninstall the drivers..reconnect in same mode..let the drivers reinstall.
Click to expand...
Click to collapse
I followed your instructions... Heres what i did...
Step I: Performed a Hard Reset using the Vol Dwn + Camera + Power Up keys.
Step II: Turned the Phone off & connected the phone with Vol Up + Usb connect. Theres an asterisk sign on Qualcomm CDMA Technologies MSM (I had it uninstalled prior to the reset using the Device Manager, It was detected whilst i connected it in Nand mode again)
Step III: Flashed a new rom on it. Lumiatrix v4.3. Still Zune is giving the same error & Application Deployment is not yet possible.
Surya there are three things i need to ask you.
1. In your Noob Guide the rom flash part you are asking people to turn On their phone, select Nokia Connectivity Mode & then select the .nb file & click Write Os. When i try that it asks me for a Nand Drive.
2. If i should try going back to Dload (can i switch to Qualcomm whenever i feel like?), can you please suggest me a clear & concise method, as to how to do it. I wanted to try this (http://forum.xda-developers.com/showthread.php?t=1702815) but its too confusing.
3. Is a bootloader refresh possible? I connected my phone when it was On. I got the Nokia Connectivity Mode. I tried installing the bootloader it found the phone but wanted me to be in the flash mode. However, when i enter the Nand mode it never finds my phone except when i Write Os on it.
I know i have a long list of questions. Its only because of the fact that i want to understand this better. I dun wanna end up bricking my phone. Thanks in Advance. Tc & Godbless!
Ok..wen u connect your phone to the PC while its ON, its in normal mode...the moment u turn on NSS, it will change modes, so it doesnt matter unless u click WRITE OS, which switches the phone OFF and puts it in the NAND dDrive.
as you have a 710, you can try going back to DLOAD and flash a Stock rom and see if that works, and then you can always go back to a qualcomm by my guide.
your at no loss , unless the problem you have a more complicated than we think it is.
surya467 said:
Ok..wen u connect your phone to the PC while its ON, its in normal mode...the moment u turn on NSS, it will change modes, so it doesnt matter unless u click WRITE OS, which switches the phone OFF and puts it in the NAND dDrive.
as you have a 710, you can try going back to DLOAD and flash a Stock rom and see if that works, and then you can always go back to a qualcomm by my guide.
your at no loss , unless the problem you have a more complicated than we think it is.
Click to expand...
Click to collapse
i would try going back to Dload. However, can you please suggest me a clear & concise method, as to how to do it. I wanted to try this (http://forum.xda-developers.com/show....php?t=1702815) but its too confusing.
Are you suggesting using NSS Bootloader Restore? If so, is there a mode that i need to be in? I'm using NSS 0.51b & when I click on restore it brings up a very scary warning message. As I don't want to brick it, i haven't used it yet.
Please suggest me a method... to return to Dload
Dear All,
I am a newbie on this so please bear with me. I did take the time out to read up on some of the basics before I posted this but I am not familiar with most of the acronyms.
I bought a HTC One X+ with no power button. The seller claimed he bought the phone as is and didnt know if the phone worked or not.
When I received it, I placed a power button and put it on charge. Within minutes the phone loaded with the 3 logo (UK) but to the bootloader screen. I tried all the various options from Hboot, Restart, Restart with Bootloader and Power Down. When I choose HBoot, I get the following error:
sd checking....
Failed to open USB master mode
(preload) Failed to open USB master mode
loading image....
Failed to open USB master mode
Plug off device.
When I try to power down, it simply restarts. When I choose Recovery, nothing works. I just keep coming back to the bootloader screen no matter what I do.
I read the following thread but I didnt understand some of it, eg RUU. I assume this is the type of ROM that is flashed to the phone.
http://forum.xda-developers.com/showthread.php?t=1940194
I have tried connecting phone to the laptop to see if I can see the drive in windows explorer. Laptop recognises the HTC phone in System Device (loaded HTC Sync Manager from HTC website) but it wont recognise the phone's drive. When I try to use the CMD box, i get same issue. It cannot find the phone's storage, therefore I cannot write anything to the phone.
It seems like whoever tried to flash this phone which is on the 3 network made a hash of it, as from reading the above thread, it looks like 3 networked HTC One X cannot be unlocked.
Therefore is it possible to get this phone back to working mode as it was, given the issues I am having.
Any help will be mightily appreciated! :good:
Thanks
Shanni
you got those "errors" because you have the usb cable plugged in too soon.
Lloir said:
you got those "errors" because you have the usb cable plugged in too soon.
Click to expand...
Click to collapse
I have tried it with cable in early and late. It is the same issue
I just realised it is NOT on the 3 network, that is my HTC One X! Cant believe I got that mixed up!
Actually I dont know what network this is on as I cant get out of bootloader!
I have been informed by a friend that the phone needs to be s-off before it can be flashed. How can I do this?
this device DOES NOT need s-off so your friend is talking out of his ass,
the guide to flash ruu's is in the general section
also there is NO WAY to s-off the X+
Lloir said:
this device DOES NOT need s-off so your friend is talking out of his ass,
the guide to flash ruu's is in the general section
also there is NO WAY to s-off the X+
Click to expand...
Click to collapse
Ok cool, I will have a look at flashing ruu's. Will that fix my phone?
shanni10 said:
Ok cool, I will have a look at flashing ruu's. Will that fix my phone?
Click to expand...
Click to collapse
I keep getting signature errors everytime I try a different UK network RUU! I dont even know what this signature error means!
Also how do I know which RUU to use as there are so many different types. Any help will be gladly appreciated
I have followed Hasoon's directions using his utility tool. I have managed to unlock the phone but cant get beyond that.
Every single viable HTC One X+ RUU I use simply doesnt work. I cant access the USB drive to my phone (prob because the person previously never ticked USB Debugging when he/she attempted to root the phone) so cannot transfer the RUU files to my phone.
I have tried to run the original RUU for this phone but it keeps giving me an error. I have no idea what to do next. I have read all the posts on the General Forum for instructions on ADB, rooting, unlocking, RUUs etc.
I would truly be thankful if I can get some assistance here please.
shanni10 said:
I have followed Hasoon's directions using his utility tool. I have managed to unlock the phone but cant get beyond that.
Every single viable HTC One X+ RUU I use simply doesnt work. I cant access the USB drive to my phone (prob because the person previously never ticked USB Debugging when he/she attempted to root the phone) so cannot transfer the RUU files to my phone.
I have tried to run the original RUU for this phone but it keeps giving me an error. I have no idea what to do next. I have read all the posts on the General Forum for instructions on ADB, rooting, unlocking, RUUs etc.
I would truly be thankful if I can get some assistance here please.
Click to expand...
Click to collapse
where in the UK are you? if you are close to me i can sort it out for you. Also you need to relock the bootloader put the device into bootloader > fastboot usb and THEN run the correct RUU
Lloir said:
where in the UK are you? if you are close to me i can sort it out for you. Also you need to relock the bootloader put the device into bootloader > fastboot usb and THEN run the correct RUU
Click to expand...
Click to collapse
I am in Manchester. I have relocked the bootloader but now the phone wont charge. I have seen a post here how to fix that, so I will try that.
I have done the above but I simply do not know what the correct RUU is. How do I even know which is right? I have tried around 10 so far and none have worked.
Fixed It!!!!
I cant believe it! I fixed it!!!!
I accidentally came up on a post here on this forum looking for something else and a member discussed the same problem as me. The reason why he was getting the signature error etc because he had the wrong recovery loaded.
I therefore loaded the latest TWRP version from here (link provided from General Settings) - http://techerrata.com/browse/twrp2/enrc2b
I didnt use Hasoon's recovery as TWRP is user friendly. I relocked the phone, loaded the correct RUU and it worked!
So to summarise this is how I fixed my phone
1. Downloaded Hasoon2000's toolkit from here - http://forum.xda-developers.com/showthread.php?t=2066390
2. Rooted the phone
3. Unlocked the phone
4. Flashed latest recovery file using his toolkit (Your Own Recovery)
5. Loaded the correct RUU - RUU_ENRC2B_U_JB_45_HTC_Europe_1.17.401.1_Radio_3.1204.168.32_release_299688_signed.exe from http://androidfiles.org/ruu/?dir=ENRC2B
NB to know which RUU to use, go into bootloader and you will see the RUU details at the top part of the screen - in my case it was Radio_3.1204.168.32. Also when I tried to run any RUU.exe file it told me the version I had was 1.17.401.1. I searched for it on the android files and found the above RUU to match my RUU. This I guess is the stock RUU.
As a newbie, it can be very tough trying to understand this, but this forum is just awesome!! I am an accountant by profession, and I cant believe I figured how to fix an HTC One X+ by going through this forum! The FAQ has it all - http://forum.xda-developers.com/showthread.php?t=2179337
Thanks to everyone who gave their advice here!
I am now going to try performance tweaks next as I am feeling confident
http://forum.xda-developers.com/showpost.php?p=34021248&postcount=2
Shanni
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
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.