Related
I know there is threads about this, but I am having troubles, I will be willing to donate $20 to anyone who can help me. I am hoping it will be relatively easy............. I shouldn't have said that.
I loaded a bad framework-res.apk on my phone, and now it won't boot.
I have read DG's thread on recovering from the brick, but I can't figure out how to make it work.
In order to get the framework loaded I used root explorer to copy it over, because I couldn't get ADB to push the file. (I know, if I couldn't get ADB to work why would I muck with it....)
Now the first step in his guide is to boot into fastboot and wait for adb to work, then use superoneclick and hit 'shell root'
well, I can load into fastboot, but adb consistently says "error: device not found" or it doesn't list anything when I check devices. The troubles I was having before with adb were with pushing files, I could still see the device and pull files.
When I did the superoneclick step it ended up freezing the program, and I am not sure what is supposed to happen with fastboot but all it said was starting fastboot protocol support then did nothing.
I would be very grateful to anyone who can help me with this problem, I do have a backup framework on my computer and on the external sd card in the phone.
One thing I should note is that I did originally boot into the recovery mode, but all i did from there was reboot the phone (and go into fastboot mode).
Please help me! I have learned my lesson.
does the phone turn on
Do you have USB debugging enabled?
If you do, its possible to use adb by selecting Early USB Enumeration from boot menu. If not, you'll need to reflash using an SBF.
Come to my gtalk id texasdude11 and I'll help you out on chat.
Sent from my MB860 using Tapatalk
brian2220 said:
does the phone turn on
Click to expand...
Click to collapse
from what i gather, it turns on, but won't fully boot into android.
by that token, early USB enumeration will allow ADB to work on the phone usually, but in this case i believe debugging was turned off before his device was bricked. so, he can't boot into full android UI, and also can't use ADB to push the restore files because debugging is off.
i've seen this problem with one person before, but i couldn't find a way to force debugging on without going into the UI, if someone can chime in with a way to turn debugging on without initial ADB access, or UI then this problem is solved and more than one person is helped.
Although - he can just reflash if he's on AT&T, if he's on Bell then he's SOL
brian2220 said:
does the phone turn on
Click to expand...
Click to collapse
Sorry, I obviously suck at giving info.
The phone boots but not past the moto screen, I get the flashing red lights and it reboots. I can get into recovery and fastboot (though I suspect fast boot isn't work right since it freezes almost instantly), I also cant see the device in adb while trying fast boot (or anything else for that matter). I could before it bricked.
raybond25 said:
from what i gather, it turns on, but won't fully boot into android.
by that token, early USB enumeration will allow ADB to work on the phone usually, but in this case i believe debugging was turned off before his device was bricked. so, he can't boot into full android UI, and also can't use ADB to push the restore files because debugging is off.
i've seen this problem with one person before, but i couldn't find a way to force debugging on without going into the UI, if someone can chime in with a way to turn debugging on without initial ADB access, or UI then this problem is solved and more than one person is helped.
Click to expand...
Click to collapse
I think debugging was on, but I was also in USB data mode (the one above none). And yes, I am the poor Bell SOL'er.
toughbax said:
Sorry, I obviously suck at giving info.
The phone boots but not past the moto screen, I get the flashing red lights and it reboots. I can get into recovery and fastboot (though I suspect fast boot isn't work right since it freezes almost instantly), I also cant see the device in adb while trying fast boot (or anything else for that matter). I could before it bricked.
Click to expand...
Click to collapse
hold the volume up and the power button together and see if u can get into RSD engineering screen
and just follow this and flash everything over
http://forum.xda-developers.com/showthread.php?t=991072
Id download RSD 5 and one of the sbf files 1.26 or 1.52 and boot phone into rsd(power button+volume up) and flash the sbf
lsxrx7 said:
hold the volume up and the power button together and see if u can get into RSD engineering screen
and just follow this and flash everything over
http://forum.xda-developers.com/showthread.php?t=991072
Click to expand...
Click to collapse
blaque72 said:
Id download RSD 5 and one of the sbf files 1.26 or 1.52 and boot phone into rsd(power button+volume up) and flash the sbf
Click to expand...
Click to collapse
the problem is that he's on Bell, so there's no sbf for us poor Bell users to flash to yet.
raybond25 said:
the problem is that he's on Bell, so there's no sbf for us poor Bell users to flash to yet.
Click to expand...
Click to collapse
Blah guess I should be more observate when trying to help my apologies hope someone on bell helps him
blaque72 said:
Blah guess I should be more observate when trying to help my apologies hope someone on bell helps him
Click to expand...
Click to collapse
yeah, i don't think he explicitly said that, but i just PM'ed him because i guessed that that was the case and it was, i'm on Bell and ima see what i can do
I HAVE BEEN SAVED. Thank you all for your quick help. I am now up and running again and I have learned from my mistakes.
Kudos to Kenneth for his amazingly quick response and supplying me with an idiot proof script to get my phone back to exactly where it was. YOU DA MAN!
Honorable mention to raybond25 for the quick response and solution as well, YOU DA CANADIAN MAN!
toughbax said:
I HAVE BEEN SAVED. Thank you all for your quick help. I am now up and running again and I have learned from my mistakes.
Kudos to Kenneth for his amazingly quick response and supplying me with an idiot proof script to get my phone back to exactly where it was. YOU DA MAN!
Honorable mention to raybond25 for the quick response and solution as well, YOU DA CANADIAN MAN!
Click to expand...
Click to collapse
What was the solution?
shawnbuck said:
What was the solution?
Click to expand...
Click to collapse
NO IDEA.
Kenneth made me a script that did it all for me all I did was hit the space bar a few times.
Basically the problem seemed to be on this side of the keyboard.....
Moved to Q&A
Please post this script so that we may use this in the future
yes, please post the script toughbax or kenneth so that all can benefit from it, i already bricked and returned one atrix and cant afford to brick another. thanks in advance toughbax and kenneth
erik10002 said:
yes, please post the script toughbax or kenneth so that all can benefit from it, i already bricked and returned one atrix and cant afford to brick another. thanks in advance toughbax and kenneth
Click to expand...
Click to collapse
The problem is that the script that ken wrote for the OP only restores the framework-res.apk file, and nothing else. If you really need this to recover from soft brick in the first place I'm not sure if you have the ability to edit it the way that is required.
Sent from my MB860 using XDA App
raybond25 said:
from what i gather, it turns on, but won't fully boot into android.
by that token, early USB enumeration will allow ADB to work on the phone usually, but in this case i believe debugging was turned off before his device was bricked. so, he can't boot into full android UI, and also can't use ADB to push the restore files because debugging is off.
i've seen this problem with one person before, but i couldn't find a way to force debugging on without going into the UI, if someone can chime in with a way to turn debugging on without initial ADB access, or UI then this problem is solved and more than one person is helped.
Although - he can just reflash if he's on AT&T, if he's on Bell then he's SOL
Click to expand...
Click to collapse
Freaking beautiful. Early USB enumeration was just what I needed to fix my f*ck up.
I have spent a week sifting this forum and was unsuccessful in answering my own question. Please guide me as I am a NOOB to Android. Or straight up tell me I gotta send this in to Sony.
I bought this Xperia Tablet 2 in May. LOVE it! Made no Root mods, totally stock. Updated to 4.1.1 - OK! Updated to 4.1.1 release2 - issues.
Within a week, the tablet would shut off in the middle of Paper Monster and web browsing. I would restart and everything was fine, for a while. Then it shut down and would not boot back up. Sticks on SONY.
Tried soft reset, no luck. Tried Recovery (very hard to get into, fails 80% of the time to enter) no luck, still sticks on SONY.
So I don't have access to put the USB Debugging feature on, and its not rooted so 6.5 All-in-One can't help me (at least not in my current NOOB status)
I did purchase a brand new SGPT122 to replace this one, but have not set it up in hopes maybe someone could tell me how to copy the OS or RECOVERY off of it and install it on my SGPT121 to revive it.
Whats my next step?
SirStorm said:
I have spent a week sifting this forum and was unsuccessful in answering my own question. Please guide me as I am a NOOB to Android. Or straight up tell me I gotta send this in to Sony.
I bought this Xperia Tablet 2 in May. LOVE it! Made no Root mods, totally stock. Updated to 4.1.1 - OK! Updated to 4.1.1 release2 - issues.
Within a week, the tablet would shut off in the middle of Paper Monster and web browsing. I would restart and everything was fine, for a while. Then it shut down and would not boot back up. Sticks on SONY.
Tried soft reset, no luck. Tried Recovery (very hard to get into, fails 80% of the time to enter) no luck, still sticks on SONY.
So I don't have access to put the USB Debugging feature on, and its not rooted so 6.5 All-in-One can't help me (at least not in my current NOOB status)
I did purchase a brand new SGPT122 to replace this one, but have not set it up in hopes maybe someone could tell me how to copy the OS or RECOVERY off of it and install it on my SGPT121 to revive it.
Whats my next step?
Click to expand...
Click to collapse
Option 1 send to Sony tell them issues and ask for downgrade in firmware. They will probably say it is not possible.
Option 2 root and use AiO tool to install rescure back-door then you can install JB r1. You can then unroot and have it as stock.
stifilz said:
Option 1 send to Sony tell them issues and ask for downgrade in firmware. They will probably say it is not possible.
Option 2 root and use AiO tool to install rescure back-door then you can install JB r1. You can then unroot and have it as stock.
Click to expand...
Click to collapse
OK I have been attempting this all evening. I cannot get my computer to recognize the tablet. That is because I cannot enable USB Debugging because I cannot get past the SONY screen, right? Or is there another way to root?
It appears I can only access the Recovery Screen, and it does not like the version of OTA.zip I have. I have not found Recovery ROMS for this tablet.
I really appreciate your time, Thank You.
SirStorm said:
OK I have been attempting this all evening. I cannot get my computer to recognize the tablet. That is because I cannot enable USB Debugging because I cannot get past the SONY screen, right? Or is there another way to root?
It appears I can only access the Recovery Screen, and it does not like the version of OTA.zip I have. I have not found Recovery ROMS for this tablet.
I really appreciate your time, Thank You.
Click to expand...
Click to collapse
Adb should still be available in recovery wether usb debugging is on or not. Is it asking for a driver at all?
If you had the latest update installed then. You wont be able to install anything and it will need to go to sony.
SirStorm said:
It appears I can only access the Recovery Screen, and it does not like the version of OTA.zip I have. I have not found Recovery ROMS for this tablet.
I really appreciate your time, Thank You.
Click to expand...
Click to collapse
Check your device manager to see if the tablet driver is properly installed, if not, install it. This might help.
Sent from my GT-I9505 using xda app-developers app
Thanks for the help! I called Sony today, they said since the computer doesn't recognize the device and it will only go into recovery sometimes the pad needs service. (I know OF COURSE) But is does stand to reason since I have plugged into multiple PCs and no recognition. They are sending a box for me. I just hope my 32Gb version doesn't tank also.
I can't for the life of me get adb to recognize my max. It's Verizon, H-boot 2.46. Trying to root and unlock. I've tried everything here....nothing. A little help please.
Only thing I can suggest, because it's happened to me, is to make sure you have the correct, most current device drivers loaded on your PC.
Sent from my HTC6525LVW using Tapatalk
they are correct up to date and most current.
HellRayzer said:
I can't for the life of me get adb to recognize my max. It's Verizon, H-boot 2.46. Trying to root and unlock. I've tried everything here....nothing. A little help please.
Click to expand...
Click to collapse
Are you unlocked, s-off, and rooted? Do you have developer options activated on your phone? Please explain what you´ve done up till now.
What happens when you type adb reboot. Does it start and not find it or come back with command not recognized?
Sent from my HTC6525LVW using xda app-developers app
i was having issues myself. then I found this thread and things worked again. http://forum.xda-developers.com/showthread.php?t=2588979
it doesn't find anything. I haven't been able to root s-off or anything because adb cant find my device. Do I need adb files in rumrunner folder on C drive to make it recognize it and work or what the hell am I doing wrong? I have rooted and s-offed every htc device I have ever owned...this one isn't working out. It's showing as a portable media player not android device. In the past I remember when I connected the usb I had the option to select media storage or connect as android.
HellRayzer said:
it doesn't find anything. I haven't been able to root s-off or anything because adb cant find my device. Do I need adb files in rumrunner folder on C drive to make it recognize it and work or what the hell am I doing wrong? I have rooted and s-offed every htc device I have ever owned...this one isn't working out. It's showing as a portable media player not android device. In the past I remember when I connected the usb I had the option to select media storage or connect as android.
Click to expand...
Click to collapse
my rumrunner folder was still in my downloads folder no where near my adb files and everything worked ok for me. also my Max shows up as a media device also but adb/fastboot still working fine. did you try to reinstall your adb with the link I provided in the above post, its the only thing that helped me when I was having pretty much the same problem as you.
you may also need to unlocked dev tools in your settings... have you done that yet
Where and how do you unlock developer tools...haven't found that under anything in the settings?
HellRayzer said:
Where and how do you unlock developer tools...haven't found that under anything in the settings?
Click to expand...
Click to collapse
Enter Settings, then scroll down to about... pick "Software Information" -- then "More" --- Then press the "Build" 8 times fast. You´ll then have access to the developer tools.
Well thanks for the help. still can't get anything to work, guess this will be the first device I've owned that will never be rooted unless I find something that tells me what to put where and what to do.
HellRayzer said:
Well thanks for the help. still can't get anything to work, guess this will be the first device I've owned that will never be rooted unless I find something that tells me what to put where and what to do.
Click to expand...
Click to collapse
When you type in adb devices, can you see your seriel number?
RayHeath said:
When you type in adb devices, can you see your seriel number?
Click to expand...
Click to collapse
no. it says list of devices, then it's blank.
HellRayzer said:
no. it says list of devices, then it's blank.
Click to expand...
Click to collapse
Ok, I´m not sure what you time zone is, but I can help you tomorrow. It´s 10pm here right now, and I´m gonna hit the hay soon. When you´re online tomorrow, pm me. I´ll log in, and we´ll start.
Hey relax bud, do me a favor and PM and I will help you out with everything and getting your phone to be recognized by dab and fast boot and make sure you properly s-off unlock and root if that's what you are trying to accomplish! Hit me up, I have nothing going on tonight so I can jump right in to it with you right away
HellRayzer said:
no. it says list of devices, then it's blank.
Click to expand...
Click to collapse
Have Win XP or server 2003?!?
This: http://forum.xda-developers.com/showthread.php?p=49045175
Don't know if you guys ever got this issue solved or not. I'm having the same issue S-on, cannot get adb devices command to recognize my t6spr for the life of me. on Hboot 2.46, it will detect the USB device malfunction if I put the device in fastboot mode, but thats about it. Device manager shows Unknown USB (Device Descriptor Request Failed). Tried the KB update for devices that fail enumeration on Windows 8.1 for x64 but the update package said my system is not affected so that never installed. Tried the alternative miniadb pakage previously mentioned but didnt seem to have an affect installing fastboot, adb, and drivers, across the system universally. Just not having any luck apparently. I guess I could just sell the phone Tampered and Unlocked haha with no fingerprint scanner functionality, flash ViperRom or some other stock look alike ROM. Was just really hoping to go back completely stock. At one point it time I was trying different PCs to see if it was just a system issue for me. Occasionally it seemed like if I let it sit in Fastboot AC it would eventually get detected and flip over to Fastboot USB long enough for me to push a couple commands to the phone. I have the right RUU but it dosent do me any good if the computer cant see the phone haha. Now no computer seems to recognize it. It all seemed to happen after I tried to S-Off the device with Firewater's method. Idk if I bricked something because it never worked or changed a CID or some other ID to where the USB isnt recognizable, but all I can get this phone to do is take an electric current from the USB, lol thats about it. I thought I had it fixed enough to where I knew what to do if i absolutely needed to get fastboot to recognize the phone but now, nothing.
Just a curiousity question here....a bad usb cable can produce this also...read through posts didnt see anyone trying a new cable...
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
Hey everyone, i'm sorry if this isn't the right section to post that kind of stuff in, i have a galaxy s7 edge with a broken screen, it's unresponsive and it shows nothing, so it's pointless for me to plug a mouse via an OTG cable in order to operate it, other than the screen, i think it still functions though, it's relatively expensive to repair here in my country so i figured i might as well recover my data and get rid of it altogether afterwards, i don't have usb debugging enabled, and i don't how how to enable it via recovery mode (if it's possible that is), is there some way to like cast its display to a computer and use the latter the interact with it ? or at least access its storage ? i really have important data in the device, so if there's no way to recover it, i'll be forced to repair the screen, i really appreciate any help
Have you asked this already - like a year ago?
https://forum.xda-developers.com/t/samsung-galaxy-s7-edge-cracked-screen.3995855
So, no TWRP. Then flash a modified stock recovery of your own. Enable adb in it. Pull stuff if not encrypted. If not, root with SuperSu. Then pull stuff...
That was just guesswork. Try yourself what can be done...
CXZa said:
Have you asked this already - like a year ago?
https://forum.xda-developers.com/t/samsung-galaxy-s7-edge-cracked-screen.3995855
So, no TWRP. Then flash a modified stock recovery of your own. Enable adb in it. Pull stuff if not encrypted. If not, root with SuperSu. Then pull stuff...
That was just guesswork. Try yourself what can be done...
Click to expand...
Click to collapse
Yes i did, i completely forgot about it however ! anyway, there's no custom recovery (i figured it's pretty much a must just in case something like that happens, but it was too late unfortunately), i didn't search thoroughly yet, but i can't find already modified stock recovery files for the device (assuming there's any of course), and i don't know how to modify such files if that's possible, can you walk me though some steps ? although i thought i knew a little bit about that stuff, apparently it's not enough ! and thanks a lot, i really appreciate your help
Sisine said:
although i thought i knew a little bit about that stuff, apparently it's not enough
Click to expand...
Click to collapse
Same here. And that guesswork went wrong too as I forgot that you said in that other thread that usb debugging isn't enabled...
CXZa said:
Same here. And that guesswork went wrong too as I forgot that you said in that other thread that usb debugging isn't enabled...
Click to expand...
Click to collapse
It looks like i'm out of luck