Related
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
DESPERATE FOR HELP!
I bought a LG G2 D802 after deciding that ~ thats the phone i needed and after i bought it of course it had the 4.4.2 when i really wanted the 4.2.2
The reception was horrible too in low signal zones i had 90% of time no signal so after studying a little i decided i would Root it & install a new Rom possibly a Tmobile Version so i could fix my reception with Wifi-calling. Rooting was straight forward and no problems but Twrp was horrible i tried different ways and i couldnt install a recovery that worked or opened. Before i started playing with Twrp i made a Back up of the stock just in case.
AS it was BOUND to happen ~ flash errors occurred when i installed autorec.apk and rebooted. After that all i get is:
Fastboot mode started
udc_start()
and when im connected by USB
-reset-
-portcharge-
fastboot: proccessing commands
Pretty popular on the forum. So i tried to keep my cool and went through all same cases> I tried to get Recovery ( never installed right so ) tried to fix it by a method someone shared on the forum ~ didnt work Fastboot would flash the new recovery but once i went through the reboot and factory settings would go back to same black screen with fastboot mode started. To make things worse my download mode pops out and stays half a sec before it goes to same Awful screen. Tried to fix download with Laf file ~ fastboot erase and flash new one for my version as suggested by another member who unbriked his LG G2 didnt work ~ same issue.
ADB doesnt recognize the device. I have installed all device software in the beginning when i was rooting and trying to install Twrp. its an LG G2 with no SD slot and not a removable battery. Im losing all hope i dont know what to do anymore. If you guys can help me would be a life saver im close to smashing it to pieces and go back to my old Blackberry~...~
:crying::crying::crying::crying::crying::crying::crying: Please help !
DflMaster said:
DESPERATE FOR HELP!
I bought a LG G2 D802 after deciding that ~ thats the phone i needed and after i bought it of course it had the 4.4.2 when i really wanted the 4.2.2
The reception was horrible too in low signal zones i had 90% of time no signal so after studying a little i decided i would Root it & install a new Rom possibly a Tmobile Version so i could fix my reception with Wifi-calling. Rooting was straight forward and no problems but Twrp was horrible i tried different ways and i couldnt install a recovery that worked or opened. Before i started playing with Twrp i made a Back up of the stock just in case.
AS it was BOUND to happen ~ flash errors occurred when i installed autorec.apk and rebooted. After that all i get is:
Fastboot mode started
udc_start()
and when im connected by USB
-reset-
-portcharge-
fastboot: proccessing commands
Pretty popular on the forum. So i tried to keep my cool and went through all same cases> I tried to get Recovery ( never installed right so ) tried to fix it by a method someone shared on the forum ~ didnt work Fastboot would flash the new recovery but once i went through the reboot and factory settings would go back to same black screen with fastboot mode started. To make things worse my download mode pops out and stays half a sec before it goes to same Awful screen. Tried to fix download with Laf file ~ fastboot erase and flash new one for my version as suggested by another member who unbriked his LG G2 didnt work ~ same issue.
ADB doesnt recognize the device. I have installed all device software in the beginning when i was rooting and trying to install Twrp. its an LG G2 with no SD slot and not a removable battery. Im losing all hope i dont know what to do anymore. If you guys can help me would be a life saver im close to smashing it to pieces and go back to my old Blackberry~...~
:crying::crying::crying::crying::crying::crying::crying: Please help !
Click to expand...
Click to collapse
is your fastboot working?? do you have proper drivers... please search for x64 drivers if you have 64 bit os... sometimes that help.. i can be simple driver problem.. i tried to read you post twice but couldn't understand moreover i am not familiar with specifically LG but still i have some experience in flashing samsung s devices and nexus
pushkardua said:
is your fastboot working?? do you have proper drivers... please search for x64 drivers if you have 64 bit os... sometimes that help.. i can be simple driver problem.. i tried to read you post twice but couldn't understand moreover i am not familiar with specifically LG but still i have some experience in flashing samsung s devices and nexus
Click to expand...
Click to collapse
I dont know! I can Erase and Flash .img files into the phone ~ by using CMD and the SDK but i dont seem to be able to flash a system.img the one i have is 3gb and says error allocating memory. I dont see my device on adb ~ and fastboot shows ? Fastboot as device. I went and installed Ubuntu into a Virtual drive to try to push files into phone so i could access download mode or recovery. No luck there i couldnt find the phone under devices either.
When i use CMD on the PC and flash recovery recovery.img or any other image command the phone displays the work being done. So i think i am connected to Fastboot.
[UPDATE - SOLVED - It was the USB cable. Tried another cable in another USB port on my PC, everything came up roses!]
Hi Everyone, I"ve been following XDA since I got my A700 in late 2012 and have finally decided to attempt rooting and flashing. I wanted to try something based on CM11, like the Omni, PacMan or base Cyanogen ROMs located here. I appreciate your patience with my noobness, I haven't programmed anything since my VB6/VBA days and that was a good decade ago!
First I tried the methods located here:
http://forum.xda-developers.com/showthread.php?t=1984566
Note that I have owned the tab for almost two years and have not modified it in any way. I did a full reset and wipe through Android in preparation for this.
I did get as far as unlocking the bootloader. However, when I attempted to install the recovery at this command:
fastboot flash recovery recovery.img
the tablet reboots and the text in the upper left blinks:
Bootloader vJB-XXXX(Unlock Mode): Starting Fastboot USB download protocol
And stops there. In my cmd window it mentions that it is flashing my recovery.img and the file size, but stops there. I am able to power off and reboot, at which point the cmd window says that it has failed to send the .img with this message:
FAILED (data transfer failure (Too many links))
finished. total time: XXXX s
Update: Another attempt gets be the following message:
FAILED (data transfer failure (Unknown error))
Do you have to root it first? I have since tried the Vorbeth Easyroot from here:
http://forum.xda-developers.com/showthread.php?t=1953917
And it still hangs at the same USB Download Protocol message above, also unable to send the boot.img to the tab.
I will try wiping and rebooting the tab again next. I have downloaded the Adnroid SDK and installed the Eclipse add-on as instructed.
Update: I've wiped again (though it still seems to stay in Unlock Mode) and tried the Root again, same results.
Any thoughts? Thanks in advance from an old-timer!
Mark
Impromark said:
Hi Everyone, I"ve been following XDA since I got my A700 in late 2012 and have finally decided to attempt rooting and flashing. I wanted to try something based on CM11, like the Omni, PacMan or base Cyanogen ROMs located here. I appreciate your patience with my noobness, I haven't programmed anything since my VB6/VBA days and that was a good decade ago!
First I tried the methods located here:
http://forum.xda-developers.com/showthread.php?t=1984566
Note that I have owned the tab for almost two years and have not modified it in any way. I did a full reset and wipe through Android in preparation for this.
I did get as far as unlocking the bootloader. However, when I attempted to install the recovery at this command:
fastboot flash recovery recovery.img
the tablet reboots and the text in the upper left blinks:
Bootloader vJB-XXXX(Unlock Mode): Starting Fastboot USB download protocol
And stops there. In my cmd window it mentions that it is flashing my recovery.img and the file size, but stops there. I am able to power off and reboot, at which point the cmd window says that it has failed to send the .img with this message:
FAILED (data transfer failure (Too many links))
finished. total time: XXXX s
Update: Another attempt gets be the following message:
FAILED (data transfer failure (Unknown error))
Do you have to root it first? I have since tried the Vorbeth Easyroot from here:
http://forum.xda-developers.com/showthread.php?t=1953917
And it still hangs at the same USB Download Protocol message above, also unable to send the boot.img to the tab.
I will try wiping and rebooting the tab again next. I have downloaded the Adnroid SDK and installed the Eclipse add-on as instructed.
Update: I've wiped again (though it still seems to stay in Unlock Mode) and tried the Root again, same results.
Any thoughts? Thanks in advance from an old-timer!
Mark
Click to expand...
Click to collapse
It should be a pretty straightforward process. Let's make sure you're doing it in order.
1) Turn on USB Debugging in your tabs Settings/development options
2) Plug in the tab to the PC
3) In the folder where you have the custom recovery.img, open a CMD window
4) Type adb devices and hit ENTER (should see a device listed, not offline)
5) Type adb reboot bootloader and hit ENTER (should reboot to the bootloader)
6) Type fastboot flash recovery recovery.img and hit ENTER (should go to download mode and transfer file)
Some things you might try;
Fresh boot your PC
Use a different USB port on the PC
Use a different USB cable
Use a win 7 pc, win 8 is ok, but win 8.1 can be a bit wonky
Now, some info for you. If you plan on installing a KitKat (4.4.x) rom, you will need to use a newer adb.exe file after installation. The older one won't work anymore. You can usually find the small package in some of the newer device forums that use Android 4.4.x. That's what I did. Generally you can find the small packages that contain adb.exe, fastboot.exe and the 4 or 5 .dll files. I think I snagged mine from a Samsung forum. But this is only after you get the 4.4.x ROM installed.
Also, make sure your recovery matches your Android version ROM you are using. If ICS, use an ICS recovery. If JB, use a JB based recovery, if Kit Kat 4.4.x, use the newest recovery. I believe the newest TWRP works well with KitKat ROMs.
You do not need to install the Android SDK. For what you are doing, you only need the small package. My and Vorbeths "Easy Root" threads have the necessary files for JB based roms, and also contain a compatible JB based recovery. But vorbeths download links are probably bad if I recall.
As for rooting, it's always best to root it first. This can be done with a modified boot.img and superuser, but I don't think it's necessary.
Hope this helps.
That's fantastic MD, thanks for this! I'll try it over the next couple days (it's Canadian Thanksgiving, don'cha know) and report back. At the end of it, I hope to post some step-by-steps for newbies such as myself to go straight to a KK ROM, which is my ultimate goal.
Mark
Update - the problem was the USB cable. I had no idea that this could be a factor, as I had been using the same cable to transfer files to the tab all this time and it accepted my commands to unlock the bootloader just fine. Once I swapped out the .99 eBay cable for the nice thick one that came with my LG G-Pad 8.3 (which should be telling, really), everything was fine and I was able to root, flash CWM and then a ROM without issues.
Note that in my case I didn't need to update the ADB.exe file, the one I had downloaded was from 6/14/2014 and while I'm not at all sure where it comes into play, I had no problems flashing and using a Kitkat ROM.
Currently on the PacMan ROM, and it's like having a new tablet to play with, albeit with half the RAM I'm used to on my other tablet, and the ever-so-annoying touch response problems that came with the A700. Will be trying the Omni, CM11 nightly and others in due course.
Thanks again MD for the assist!
Mark
Hi Friends, is the title says I have a problem getting into the custom rom think on my old z3 6603 .291? 6.0.1 i think android...
now whats my problem?
I am despered already! spent almost 2 full days trying around without luck.
little off topic:
I did custom roms a few years ago and it worked pretty well with a step by step tutorial.
now i started to read around and try to update the Z3 to android 7Nougat or at least GoogleStylev1 because the standard/stock rom is sooo full with s**t i never really used and pure clean 5.1 from my mothers 60€ Chinamobile is fast and has all i need...
the z3 is much slower than it could i belive and the batterylife should be longer(new replaced battery >3000mAh, its almost like my new s7edge, wich i have to recharge every 3 days, the sony almost every night...)
back to topic:
i read so many different ways to do the update and everything is super complicated and at some point it doesn´t work out like in the tutorials. stupiiiid..
for example: hold power+vol down to enter recoverymode utility, i tried it so many times but my z3 is booting as usual. somone mentioned to let power button go as soon the led blinks or the vibration appers. sad: my screen is replaced and as i replaced it by myself i disconnected the vibration and glued the backplate on ... sh**
maybe someone can tell me how many secods to wait until let the power button go or other ways of erasing the system before i continue with linage install.
what i have:
win7 pc ( lack of updates and stuff but i already got the insane big android studio and somehow installed the usb driveds as it seems but thats all i still have missing drivers as i connect the phone trough flash-tool for example. xperia companion detects the phone most of the time..
so i went to my mac mini os x..
similar but little better: i can detect the device when i connect flashtool it says device connected in flash mode, good!?
i downloaded:
flashtool-driver
android tools
flashtool 0.92.1mac
lineage14.1 xkeita
twrp 3.1.1 xkierta
sr1 super su v2.82
D6603 23.5.A.0.291_kernel.zip
D6603 23.5.A.0.575_kernel.zip
root.rar
I guess i first have to get a little XDA developer university degree to update a sony mobile device hummmm???
sorry i am stressed out, please could somebody take a newb like me by hand and guide trough this piece of complicated labyrinth?
I want to give this phone to my gf for the next few years and i whink a clean slim and stable system would be much more pleasure in future than what i have now.
its a nice phone...
thanks
forgot to mention, usb debugging and developer mode are activated on the phone.. when i type in the *#7384whatever code it says: bootload activation: yes does it mean its ready to be activated or is it already active?
please its so many steps and tutorials i tried i am comletely confused
HI, glad to hear you're trying to install my rom
Since you're already on 6.0.1 all you need to do is unlock your bootloader before flashing the custom rom. To do so please refer to this page which will provide all the help you need for this step https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ (before doing this, make a backup of your internal storage because it will be wiped after unlocking the bootloader)
After unlocking your bootloader, let's proceed to installing the recovery. To do this unpack the contents from the TWRP zip and copy recovery.img to the folder where you have fastboot.exe and run this command from Windows command line
Code:
fastboot flash FOTAKernel recovery.img
Now for our final step, boot into recovery by using the power on+volume down combo, connect your phone to the computer and copy the LineageOS zip to your internal storage. Before flashing the rom remember to wipe system/data/cache/dalvik. And you're all good to go.
thanks for replying xkeita,
i did this step until the point where i got a code for bootloader.
after this they tell me to go to connect my phone to the pc and to do what?
A. Install the Android SDK and the device drivers (what drivers? i have mac) i have android studio on my mac, but i have no clue how it works.
b. If you’re running OSX or Linux, you are not required to install any additional drivers. (check!)
2. On your device, turn on USB debugging by going to Settings > Developer options and click to enable USB debugging. (check!)
B. Connect to Fastboot
1. Turn off your Xperia™ Z3.
2. Connect a USB-cable to your computer.
3. On your Xperia™ Z3, press the Volume up button at the same time as you connect the other end of the USB-cable.
(check!) i did it...
4. When your device is connected, open a command window on your computer and go to the platform-tools folder within the Android SDK folder.
5. Enter the following command: fastboot devices
here i am struggeling... how to do this on mac? i have no directories and no idea how to proceed, please help me!
xdan00b#1 said:
thanks for replying xkeita,
i did this step until the point where i got a code for bootloader.
after this they tell me to go to connect my phone to the pc and to do what?
A. Install the Android SDK and the device drivers (what drivers? i have mac) i have android studio on my mac, but i have no clue how it works.
b. If you’re running OSX or Linux, you are not required to install any additional drivers. (check!)
2. On your device, turn on USB debugging by going to Settings > Developer options and click to enable USB debugging. (check!)
B. Connect to Fastboot
1. Turn off your Xperia™ Z3.
2. Connect a USB-cable to your computer.
3. On your Xperia™ Z3, press the Volume up button at the same time as you connect the other end of the USB-cable.
(check!) i did it...
4. When your device is connected, open a command window on your computer and go to the platform-tools folder within the Android SDK folder.
5. Enter the following command: fastboot devices
here i am struggeling... how to do this on mac? i have no directories and no idea how to proceed, please help me!
Click to expand...
Click to collapse
Extract this zip https://forum.xda-developers.com/attachment.php?attachmentid=1396782&d=1350078941 and open terminal in the directory where you have unpacked the zip, then you can run the command directly
Mac-mini:android "XXXXX"$ fastboot devices
-bash: fastboot: command not found
should any software run in the background like xperiacompanion or flash-tool? i managed to open the terminal in the android directory but no luck...
this z3 is a tough piece...
thanks again for your effort to help me out, maybe you or somebody else can help me trough this. I have the feeling that we can crack this device together, it cant be that compliceted, can it?
nobody has Ideas as what could be going wrong in my case?
i was thinking XdaDevelopers is a big international site, and z3 is a mainstream phone, why the heck is there nobody to guide me trough this
remember how it was when you did your first Rom experiances, difficult, many different new steps, after foing it couple of times its getting easier, like everything in life.
please somebody sacrifice a litte time on me and my priject, it wont be my last for sure but i need a little help in the beginning, xperia z3 seems to be much more complicated than my old (p880LG 4xhd or xpezia z from 2012)
xkeita said:
Extract this zip https://forum.xda-developers.com/attachment.php?attachmentid=1396782&d=1350078941 and open terminal in the directory where you have unpacked the zip, then you can run the command directly
Click to expand...
Click to collapse
do i have to extract on my mac, or onto the phone? i extracted into my desktop and it didnt work ether in desktop/android/
i am going to try out to extract onto the cellphones memory and to run fastboot line from there
should i record a video how i do all my steps and somebody can tell me what im doing wrong?
eeehh.. official sony webpage is so flapsy and unprecise when it comes to bootloader...
bump
did i say something wrong or..?
...
You should use windows instead of mac it's better for unlocking your bootloader then follow the sony unlock bootloader website exactly don't skip any steps
hello omar, and thanks for reply!
my problem is to unlock the bootlocker on this phone.. i cant get my phone bpptloader unlocked and i dont know why.. its the staps on this website that dont work. i will take time on weekend maybe and try again..
piece of crap phone , replaced screed and back and my girlfriend drops it once and everything is broken again many years ago sony was better. they should make walkmans again.. casette walkmans
Hi XDA,
It's been a while since I've done any work on any phones, I've previously used roms on Galaxy S and SIII. But those are a while ago as you can see. I've got an Xperia XZ, the bootloader is currently unlocked. But I cannot, for the life of me, get any further despite following several guides and programs. So I'm at a loss.
At this exact moment, I have my XZ connected to my pc with the blue light on. CMD in ADB/Fastboot cannot detect the device. My understanding is I need to flash the kernal and recovery first, then I can consider flashing a custom rom.
Would anybody be able to assist me? I dropped this project a few months ago, so I'll need to check what rom I was going to use and update the img files I have.
Thanks
Installed fastboot abd on pc?
Yep, that's been installed. I do have an issue which I thought/think is driver related as the daemon doesn't always start, and doesn't detect the phone correctly either.
What OS is on your computer?
Windows 10, I also tried Linux Mint but didn't get much further.
Have you disable the drivers vetification?
Yep!
Can flashtool detect your device? Sorry for all the questions but got to start somewhere and have you tried changing USB ports and cables?
No, the questions are good. There will be something wrong that I can't find, so we need to work it out somehow.
Flashtool doesn't consistently detect the device. The computer does, flashtool doesn't. I have changed the cables with some success, but that hasn't helped me progress much further.
Hmm, have you install the drivers from Sony developer site? Also try it on another computer..i wonder if you have a bad connection port on your phone thus the reason I asked about another computer.. Try reinstalling fastboot and adb, drivers etc. with your anti-virus disable.. And does Sony companion work? USB debugging turned on?
Sounds silly but sometimes we forget, like redoing doing your phone from scratch and you can't delete some stuff and only to remember later that you forgot to install busybox or mount your system partition.. lol
Thanks Lilbrat,
I'll be doing a fresh install, hopefully this weekend. And will cover what you have mentioned and report back. Thanks!
since this is your first Xperia device, you must first familiarize yourself with the ENVIRONMENT and TOOLS in which SONY Xperias can be played with !
some basics I wrote for X, but applies for XZ also , please read as it will be helpful!
https://forum.xda-developers.com/showpost.php?p=72141176&postcount=7
now
since your boot is already unlocked so I can safely assume that you don't have TA.img file at all!
this leaves you with only two solutions
1. install 3rd part ROMS
2. flash sony STOCKROM and flash MODDED kernel (most of us do this)
your XZ has project name by SONY called KAGURA, your device on xperifirm is recognized by this name, dual/single you have to specify
from flashtool, xperifirm, download latest firmware 41.3.A.2.157 under KAGURA, close xperifirm and FLASHTOOL will start creating FTF file AUTOMATICALLY, click OK to any script question. and let it create ftf for u
flash it on your XZ,
send me kernel for 41.3.A.2.157, i will patch it for u! (patching guide is given in this forum but at this point i think it will be too much for you, so i will fix the kernel for u)
KAGURA twrp can be found at https://dl.twrp.me/kagura/ ( unlike SAMSUNGS, sony Xperias don't have inbuilt RECOVERY )
flashing recovery is MUST!
when device is switched off, connecting USB CABLE to PC and MObile while
1. HOLDING VOLUME UP KEY (blue LED) is FASTBOOT MODE (used mainly for sending twrp and kernels )
2. HODLING VOLUME down KEY (GREEN LED) is FLASHMODE (used mainly to FLASH stock roms using FLASHTOOL
you must install
1. Xperia Companion
2. flashtool ( www.flashtool.net) (after installing goto C:\flasthool\Drivers folder and install the driver.exe select COMMON Fastboot / flashmode drivers + z5/z4/z3 family of all drivers (there is no XZ , as Z5p drivers supports XZ)
3. install minimal adb and fastboot 1.4x from XDA (google it)
4. using these TOOLS you can
a-flash firmwere
b flash recovery
c flash modded kernel
d boot in to recovery (twrp) and flash MAGISK 16.x .zip from twrp + drm patch files! ( i will give you later with modded kernel)
e reboot and your device will wakeup ROOTED having DRM FIX! ---- switch off the SOFTWARE updater using any ROOT APP FREEZE app from playstore!
Currently working through a reinstall of flashtool etc, I can detect the phone using the Sony Companion tool, so thats positive. I haven't seen any notification that drivers have installed, but I do have the XZ drivers unzipped here.
Edit1: It doesn't detect or anything when the blue or green lights are on phone either. Not sure about them at this point.
Edit2: Just going through your guide as well Yasu, I cannot locate "sony Xperia X motherboard drivers (sa0107)" or anything similar to my device. Just throwing that out there. Installing the two common results in Sony Mobile Communications (ggsomc( USB (11/10/14 3.1.0.0) installing, but Google. Inc (WinUSB) AndroidUsbDeviceClass (12/06/10 4.0.0...) failing.
Will continue. Derp, just noticed I have a completely different flash tool. Sony Mobile Flaster by Androxyde, v0.9.25.0 but atleast it detects the connected device more than previously.
21/004/2018 13:04:44 - INFO - List of connected devices (Device Id) :
21/004/2018 13:04:44 - INFO - - USB\VID_0FCE&PID_0DDE\CB512CK84Q Driver installed : false
21/004/2018 13:04:44 - INFO - List of ADB devices :
21/004/2018 13:04:48 - INFO - - none
21/004/2018 13:04:48 - INFO - List of fastboot devices :
21/004/2018 13:04:50 - INFO - - none
Edit 3: Right, forgot to disable Win10's driver signature. Fixed that part again.
Downloaded the wrong firmware, so just working on that again (41.3.A.2.157 / R1E).
I was planning to flash Rudy's AOSP Oreo, but I'll have to go back and see as I chose that several months back.
Edit1: Completed flash. Phone is now 41.3.A.2.157, kernal 3.18.66. Android 8.0.0, bootloader unlocked. Rooted says no. This is certainly a lot more difficult than I remember!
Edit2: Recovery flash completes when command is ran, but adb does not register the device being listed, fastboot does. So I've hit the stump again with being unable to successfully flash twrp-3.2.2-0-kagura.img as recovery.img
Edit3: Last one for today. I can't open recovery from my phone, but can force it with fastboot boot recovery.img which has worked. However, it has loaded to a Mount - Decrypt Data screen and wants a password. I'm not aware of a password being required, and if I recall the device is encrypted. Ouch, should have seen this coming.
AVeers said:
Downloaded the wrong firmware, so just working on that again (41.3.A.2.157 / R1E).
I was planning to flash Rudy's AOSP Oreo, but I'll have to go back and see as I chose that several months back.
Edit1: Completed flash. Phone is now 41.3.A.2.157, kernal 3.18.66. Android 8.0.0, bootloader unlocked. Rooted says no. This is certainly a lot more difficult than I remember!
Edit2: Recovery flash completes when command is ran, but adb does not register the device being listed, fastboot does. So I've hit the stump again with being unable to successfully flash twrp-3.2.2-0-kagura.img as recovery.img
Edit3: Last one for today. I can't open recovery from my phone, but can force it with fastboot boot recovery.img which has worked. However, it has loaded to a Mount - Decrypt Data screen and wants a password. I'm not aware of a password being required, and if I recall the device is encrypted. Ouch, should have seen this coming.
Click to expand...
Click to collapse
1. as i mentioned " (after installing goto C:\flasthool\Drivers folder and install the driver.exe select COMMON Fastboot / flashmode drivers + z5/z4/z3 family of all drivers (there is no XZ , as Z5p drivers supports XZ) "
2. once these drivers are installed, you will get SOMC notification when very first time you connect your XZ in any MODE (volume up / and /or / volume down)
3. while flashing firmware, if you didnt tick WIPE areas, you will get encryption error , you must perform CLEAN FLASHING
4. before booting in to twrp, you must flash MODIFIED KERNEL - you can take modded kernel from my post in this forum
5, boot into twrp, flash drm fix files, flash magisk and wipe delvik cache/ cache and Reboot!
Yep, I see what you mean now. I missed the options on the flash screen, I thought it was odd that the time it took didn't match anything close to the times you described.
That didn't end well, clean flash, flashed kernel, TWRP booted correctly this time from the phone. Except phone now won't boot past the Sony logo.
I was also comparing your instructions against korom42's, and another third party. Which naturally are all similar and straight forward, still didn't help.
AVeers said:
That didn't end well, clean flash, flashed kernel, TWRP booted correctly this time from the phone. Except phone now won't boot past the Sony logo.
I was also comparing your instructions against korom42's, and another third party. Which naturally are all similar and straight forward, still didn't help.
Click to expand...
Click to collapse
did you flash the modded kernel?
if you simply flash magisk on original kernel!
you will be stuck on SONY LOGO
OK, I still following this with some interest, as a bit of clarification seems to be needed.. Now granted for some reason Flashtool doesn't have the XZ drivers even the newest version but there are mb drivers on Sony Developer site.. https://developer.sony.com/develop/drivers/ . (see pic)
@AVeers, more computer questions reason being you said Flashtool is seeing your phone a bit better, which leads me to believe you're still having driver issues.. Are you on a laptop or a desktop? If it's a desktop have you tried plugging your USB into the rear panel, straight into the mb also have you tried disabling your anti-virus when installing your drivers? Oh, and where are you located as your firmware is for the middle east, if I remember correctly..
Hi Mate,
I won't be able to work on this further until the weekend. But I do have those drivers from Sony here. And have been using firmware as per Australia (generic). Which is correct for my location.
The phone is plugged into the mobo via rear panel, and this is a desktop running Win10. I'm in test mode to eliminate the driver signing issue. I have not disabled the anti-virus, but I haven't had issues before.
When I run the flash for the firmware, boot.img or twrp.img, it takes seconds to complete, generally less.