Hey guys,
I need your help. I have a Sony Xperia XZ1 Compact and it hangs in a bootloop.
I am able (at least according to the flash tool) to successfully establish flash as well as fastboot mode.
But: If I try to flash a firmware, then the flash tool stops working at "Sending getvarroduct"?
As I am a noob I would be really happy about help from the community!!
Thanks a lot in advance!
Best,
balero
Edit: I want to keep my data or at least save it before reinstalling. Otherwise I would try using the Xperia Software fix in the Companion. Although this maybe wouldn t work as well..
balero1 said:
Hey guys,
I need your help. I have a Sony Xperia XZ1 Compact and it hangs in a bootloop.
I am able (at least according to the flash tool) to successfully establish flash as well as fastboot mode.
But: If I try to flash a firmware, then the flash tool stops working at "Sending getvarroduct"?
As I am a noob I would be really happy about help from the community!!
Thanks a lot in advance!
Best,
balero
Edit: I want to keep my data or at least save it before reinstalling. Otherwise I would try using the Xperia Software fix in the Companion. Although this maybe wouldn t work as well..
Click to expand...
Click to collapse
I'm not the most knowledgeable member here but I've learned a few things from my mistakes so I'll see if I can help. First, I've never used flash tool, only newflasher and xperia companion. I recommend newflasher if you can get it, as it's a very easy process.
As far as I know, you're going to lose your data either way unless you've backed it up. Xperia Companion does have the xperia transfer option, so you might give that a try as a last resort.
And just to get the ball rolling for others to help, do you know what caused the bootloop? Did you install something or change something? The more information, the better. Sometimes it's a simple fix.
Hope it works out,
AK
AlexKarimov said:
I'm not the most knowledgeable member here but I've learned a few things from my mistakes so I'll see if I can help. First, I've never used flash tool, only newflasher and xperia companion. I recommend newflasher if you can get it, as it's a very easy process.
As far as I know, you're going to lose your data either way unless you've backed it up. Xperia Companion does have the xperia transfer option, so you might give that a try as a last resort.
And just to get the ball rolling for others to help, do you know what caused the bootloop? Did you install something or change something? The more information, the better. Sometimes it's a simple fix.
Hope it works out,
AK
Click to expand...
Click to collapse
Thanks for your input!
I did try newflasher as well, the process was terminated through an I/O error. (Error write! Need n Bytes: 0x18 but done: 0x0) and (Error writing command getvar:max-download-size) :/
The phone is not recognized by the Companion when trying to use the software fixing or with the transfer function.
For more background: The bootloop originated from normal usage, I was not trying to flash a custom ROM. My intention was to fix this crash by flashing stock ROM on the phone because my system installation seems to be corrupted. My phone is not recognized by Sonys Emma....
Cheers
balero1 said:
Thanks for your input!
I did try newflasher as well, the process was terminated through an I/O error. (Error write! Need n Bytes: 0x18 but done: 0x0) and (Error writing command getvar:max-download-size) :/
The phone is not recognized by the Companion when trying to use the software fixing or with the transfer function.
For more background: The bootloop originated from normal usage, I was not trying to flash a custom ROM. My intention was to fix this crash by flashing stock ROM on the phone because my system installation seems to be corrupted. My phone is not recognized by Sonys Emma....
Cheers
Click to expand...
Click to collapse
Not sure if it'll help but I googled the "Error write! Need n Bytes: 0x18 but done: 0x0" and found this:
https://forum.xda-developers.com/cr...newflasher-xperia-command-line-t3619426/page2
as well as this:
https://dev.bettermobileapp.com/article/12291089/Newflasher
It sounds like the common problem in both threads is a driver issue. Getting the correct drivers can be a huge pain and having your device recognized when connected in normal mode, is not the same as having it recognized when connected in fastboot or flash mode.
For fastboot and flash mode, i use the 15sec ADB driver and it works every time. What I've found is that I can't count on device manager to search or find the driver automatically, it always has to be manual.
AK
Related
So I got myself into really funny situation I'm stuck.
I worked with xperia mini pro everything was fine.
Now I got x8 well older one... And all i did was rooted it with flashtool.
Everything was working fine from that point with root rights like root uninstaller (I just tested didn't deleted anything).
And then I made "factory reset" Deletes everything from sd card and bla bla bla well you guys know what i mean.
After that I wanted to install kernel but it's not that easy. So I first read alot and did not do that. Since it would require bootloader unlock and thats pain with 11W29.
So just after factory rest somehow I bricked my phone...
But it's interesting brick... VERY INTERESTING.
It turns on, it has flash mode. I can update it via update setup and tried to do that.
Nothing helps all I get is :
phone loading normally, then there is no menu, not sony ericsson home, not go launcher, no settings available no nothing...
To explain my problem i will upload screenshot.
And I can't flash it now since it's not bootloader unlocked.
And I can't access anything from phone.
This is what you call hard brick?
Hard brick is when You can't turn on phone, so there isn't any way to install ROM again. In Your case it's strange soft brick, cause it looks like ther isn't any launcher If You can enter into flash mode than You should reinstall stock ROM and kernel using flashtool (with version 0.2.9.1 cause it's more stable with older devices, such as x8).
Its not bricked. / You can use android commander to push recovery.
It's stock already and I tried stock launcher via updatesetup of SE,
And I think i need bootloader unlock to flash it ? or I'm wrong.
And Later on i will try with older version of flashtools
thx for answers guys.
No, unlocked bootloader allows You to install custom kernels, but some ROMs works also with stock SE kernel, so You don't have to unlock bootloader to install custom ROM or back to stock ROM
So i'm back again on same problem....
I have a Question if you wanna flash phone from flashmode u don't have to have unknown sources and debugging turned on.
Since i can't do that...
My following actions :
I will try to install fresh win7 32bit, since now i'm on 64 and on this system i was working with mini pro xperia, so maybe that may be the case...
I'll try to flash it with older version of flashtools 0.2.9.1 I guess if i remember it right (but on this windows OS It gives me : Error Flashing. aborted)
And I installed flashtools drivers and everything i'm 100% sure of that.
What I tried :
I also tried flashing it from Linux / ubuntu . same as with windows i get :
Error flashing. Aborted.
PCC gives me error when i try to repair it.
Update Service Dose everything as normal but same problem remains I don't get launcher or something just that empty desktop
And I would love you guys if you would give me few links to stock firmware of
x8 11W29 / E15i
And if you have something else to suggest please help me ;D
Hello, sorry for necroing thread but i have exactly same problem like OP, and as he didnt post solution i would like to ask how to do it.
Thanks for your time!
X8 OFW
deamerz said:
Hello, sorry for necroing thread but i have exactly same problem like OP, and as he didnt post solution i would like to ask how to do it.
Thanks for your time!
Click to expand...
Click to collapse
Try Flashing This via FlashTool.
TheScriptKitty said:
Try Flashing
Click to expand...
Click to collapse
Hello and thanks for your reply. I tried flashing my x8 with provded ftf file and the problem still remains the same. If it is any help i can normally increase volume, access emergency calls and keyboard and other things. But the screen remains blue. And i also remember that the thing which is supposed to appear here is the language setup, if there is any way to set up main language outside android system i guess that could help.
Again thanks for your reply and your time!
deamerz said:
Hello and thanks for your reply. I tried flashing my x8 with provded ftf file and the problem still remains the same. If it is any help i can normally increase volume, access emergency calls and keyboard and other things. But the screen remains blue. And i also remember that the thing which is supposed to appear here is the language setup, if there is any way to set up main language outside android system i guess that could help.
Again thanks for your reply and your time!
Click to expand...
Click to collapse
Try Flashing a Costume ROM for stock kernel via Recovery.
Here is a list of ROMs. Just make sure you download one that says (Stock).
Hey everyone,
I've been eyeing this forum ever since I got my XZ, two months ago. I decided to root a few days ago (that Kingo one click program) and tried to improve my phone a bit everyday.
Today, I tried to hide the navbar by adding that line at the bottom of build.prop. I edited the file with QuikOffice but when I wanted to save, I couldn't simply replace the one there so I saved it somewhere else and copy/pasted it in place of the old one. I shut down the phone and when I tried to turn it on again : bootloop. I don't know how an extra line could mess the phone this much but I'm wondering if I haven't modified some other line without knowing it.
I read that using flashtool was an option so I downloaded an installed SEUS and then Flashtool (EMMA). I connected the phone following the instructions (volume down button) but I got a "Locked phone error". I haven't done much after rooting, especially not setting up a recovery or unlocking the bootloader.
Can anyone guide me through this ? I read things about using an update.zip file but have no idea how that works. I also don't have access to the original build.prop. I've also read people who espaced a bootloop without losing data. But the "locked phone" part doesn't seem to be common. As for the Sony Update Service, it just tells me that the phone already has the last "software version" and that's it.
Thanks.
hm, can you download sony pc companion and try? I used it yesterday and there is a service tab where you can fix and download updates etc. Maybe there is a reinstall firmware or some such
pixellegolas said:
hm, can you download sony pc companion and try? I used it yesterday and there is a service tab where you can fix and download updates etc. Maybe there is a reinstall firmware or some such
Click to expand...
Click to collapse
Thank but PC Companion offered to repair the device but at the cost of all data.
I was able to solve the issue and keep my data by flashing a stock ROM using the actual Flashtool and not Emma. I'm not running CM10.2 and everything is looking great .
hi. I read somewhere here about rooting using doomlord's method (http://forum.xda-developers.com/showthread.php?t=2440375). my questions are:
1. will this method work for stock Xperia SP? Literally just out of the box, everything stock. running JB 4.1.2 v.254.
2. what are the chances of bricking my phone? i really want to root mine because i want custom ROMs on it but im really nervous because its my only phone, and this will be the first time ill do it.
thanks in advance. appreciate all your replies
1.-Yes, thats the method for .254: You need to flash .257 kernel first.
2.-Sony phones can't get "bricked"...99% of the times they only get a boot loop, which means your SP wont get past the Sony-Xperia logo. In this scenario you need to repair via Flashtool or Update Service. Flashtool is more effective for "bricked" phones.
cachanilla86 said:
1.-Yes, thats the method for .254: You need to flash .257 kernel first.
2.-Sony phones can't get "bricked"...99% of the times they only get a boot loop, which means your SP wont get past the Sony-Xperia logo. In this scenario you need to repair via Flashtool or Update Service. Flashtool is more effective for "bricked" phones.
Click to expand...
Click to collapse
thanks. incase of bootloop, is it easy to repair?
papawil01 said:
thanks. incase of bootloop, is it easy to repair?
Click to expand...
Click to collapse
Yes, just do a lil' research about flashtool and how to turn off the phone.
cachanilla86 said:
Yes, just do a lil' research about flashtool and how to turn off the phone.
Click to expand...
Click to collapse
alright. lastly, what are the chances that ill get my phone to bootloop? is it high, or not likely if i follow the steps thoroughly?
Still nervous about rooting my phone. (sigh)
Sent from my C5303
papawil01 said:
Still nervous about rooting my phone. (sigh)
Sent from my C5303
Click to expand...
Click to collapse
I have done it 8 times, with no problems at all. At first one I have only offline charging bug, but when I repair software with PC Companion, than make root with this method again that solve the problem with offline charging.
But only root? When U first read than do - its unable to brick your phone.
smogf said:
I have done it 8 times, with no problems at all. At first one I have only offline charging bug, but when I repair software with PC Companion, than make root with this method again that solve the problem with offline charging.
But only root? When U first read than do - its unable to brick your phone.
Click to expand...
Click to collapse
i tried rooting my phone two times. but i cant. whenever i run doomlords runme_win file, it says "error: cannot find device" or "error: device disconnected". any ideas? ive mustered enough courage to root my phone and it seems easy, but i dont know why it keeps getting this error. TIA
papawil01 said:
i tried rooting my phone two times. but i cant. whenever i run doomlords runme_win file, it says "error: cannot find device" or "error: device disconnected". any ideas? ive mustered enough courage to root my phone and it seems easy, but i dont know why it keeps getting this error. TIA
Click to expand...
Click to collapse
First of all connect your phone in flashtool, select Devices -> Chek Drivers and check if you have ABD driver installed.
Have you enable USB Debugging? Phone have to be also connected in MSC mode.
And at last. Have you turn off Flashtool before running script??
So on. More questions ask better in "ROOTing" thread. Or at first read this thread from start to the end before aksing quiestions. Theres a lot of answers.
smogf said:
First of all connect your phone in flashtool, select Devices -> Chek Drivers and check if you have ABD driver installed.
Have you enable USB Debugging? Phone have to be also connected in MSC mode.
And at last. Have you turn off Flashtool before running script??
So on. More questions ask better in "ROOTing" thread. Or at first read this thread from start to the end before aksing quiestions. Theres a lot of answers.
Click to expand...
Click to collapse
i think adb drivers are not installed. do you know how? it says: "list of adb devices: none" sorry but i get too flooded with all the info here so i try to ask on this thread. thanks
Hello,
I think I did something really wrong with my Xperia Z. I rooted it a month ago, I have the latest stock rom. Yesterday, I downloaded an app called Flashify on the play store who claimed to be able to flash recoveries and zips directly from phone, as long as it was rooted. I tried to flash the purexaudio mod to my phone, and since then it has become unusable. It first started to be very hot, then laggy, which forced me to shut it down. Now everytime I turn it on, it is usable for barely two minutes, before it becomes really laggy and nothing works or it freezes. Some actions directly crash my phone, such as opening the developers settings. I looked at the RAM usage on the phone's settings and the RAM is filling up progressively until the total 1.8GB of RAM is used and my phone freezes. I really don't know what is causing this.
It gets even worse, as I've managed to factory reset my phone with the sony PC companion, but the problem is still there. I can't access reccovery but I can access fastboot mode. However, neither Flashtool or fastboot command shell will flash a recovery for me (I get an "access denied" error). I can't flash the stock kerne with Flashtooll, I have the message : "Processing of loader.sin finished with errors." (I had this problem when I rooted it but I really can't remember how I fixed it).
I'm really anxious about what I've done with my phone, I hope someone could help me recover my phone as I honestly don't know what to do at this point...
Thank you so much in advance.
williaam said:
Hello,
I think I did something really wrong with my Xperia Z. I rooted it a month ago, I have the latest stock rom. Yesterday, I downloaded an app called Flashify on the play store who claimed to be able to flash recoveries and zips directly from phone, as long as it was rooted. I tried to flash the purexaudio mod to my phone, and since then it has become unusable. It first started to be very hot, then laggy, which forced me to shut it down. Now everytime I turn it on, it is usable for barely two minutes, before it becomes really laggy and nothing works or it freezes. Some actions directly crash my phone, such as opening the developers settings. I looked at the RAM usage on the phone's settings and the RAM is filling up progressively until the total 1.8GB of RAM is used and my phone freezes. I really don't know what is causing this.
It gets even worse, as I've managed to factory reset my phone with the sony PC companion, but the problem is still there. I can't access reccovery but I can access fastboot mode. However, neither Flashtool or fastboot command shell will flash a recovery for me (I get an "access denied" error). I can't flash the stock kerne with Flashtooll, I have the message : "Processing of loader.sin finished with errors." (I had this problem when I rooted it but I really can't remember how I fixed it).
I'm really anxious about what I've done with my phone, I hope someone could help me recover my phone as I honestly don't know what to do at this point...
Thank you so much in advance.
Click to expand...
Click to collapse
Well, that's not weird at all that you're getting "access denied" via fastboot. You said you've rooted your device, but did you unlock your phone's bootloader?
LaurynasVP said:
Well, that's not weird at all that you're getting "access denied" via fastboot. You said you've rooted your device, but did you unlock your phone's bootloader?
Click to expand...
Click to collapse
No, I guess I didn't... My bootloader status in Flashtool is : ROOTABLE I'm going to try doing that first. Thank you so much for your fast answer
I have a big problem actually now, as repairing my firmware with the sony software removed the USB debugging option. And opening the "developers settigns" to turn it back on still makes the settings crash. So I have no way of unlocking the bootloader now have I?
EDIT : Okay, nevermind. I managed to unlock the bootloader and flash a custom recovery (Cyanogen recovery). But now I'm on a boot loop (Sony message then Xperia then phone restarts)
What should I do now?
EDIT 2 : Solved the problem by simply wiping all caches/data from my recovery (ended up setting up the more traditional CW recovery) + sideloading a custom ROM (Ultimate PureZ). Now everything's working perfectly.
Thank you again for suggesting to unlock the bootloader, I couldn't have flashed the recovery otherwise. Have a nice day!
williaam said:
I have a big problem actually now, as repairing my firmware with the sony software removed the USB debugging option. And opening the "developers settigns" to turn it back on still makes the settings crash. So I have no way of unlocking the bootloader now have I?
EDIT : Okay, nevermind. I managed to unlock the bootloader and flash a custom recovery (Cyanogen recovery). But now I'm on a boot loop (Sony message then Xperia then phone restarts)
What should I do now?
EDIT 2 : Solved the problem by simply wiping all caches/data from my recovery (ended up setting up the more traditional CW recovery) + sideloading a custom ROM (Ultimate PureZ). Now everything's working perfectly.
Thank you again for suggesting to unlock the bootloader, I couldn't have flashed the recovery otherwise. Have a nice day!
Click to expand...
Click to collapse
You're welcome, but in this case you've made a major mistake - you didn't take TA Partition backup in which all DRM keys are being kept. Now you've erased them permanently, this will cause some stock applications to won't work (camera stabilization and etc.,).
Have a nice day you too
LaurynasVP said:
You're welcome, but in this case you've made a major mistake - you didn't take TA Partition backup in which all DRM keys are being kept. Now you've erased them permanently, this will cause some stock applications to won't work (camera stabilization and etc.,).
Have a nice day you too
Click to expand...
Click to collapse
Really? :/ What won't work exactly.?. I bootloaded my phone the official way though...
And BTW that's strange but when I put my SDCard back into my phone it crashed just like before? I guess I should format it?
williaam said:
Really? :/ What won't work exactly.?. I bootloaded my phone the official way though...
And BTW that's strange but when I put my SDCard back into my phone it crashed just like before? I guess I should format it?
Click to expand...
Click to collapse
Guess so. If even will update to earlier version (4.4.x) or later BE2 won't work, as well as camera stabilization (focus, well, it works, but photos are a bit like blured) and some other functions that I don't remember at the moment. It doesn't matter how did you unlock your bootloader, the fact that you've unlocked your bootloader is the most important. I'm sorry, but there's nothing we can do about it (DRM keys recover) at the moment. Maybe in a future there will be found a solution for this, but then our phone, I suppose will be like a nokia 3310 in nowadays.
Btw, you can still get some functions working, just surf this forum for unlocked bootloader functions "Get back" or sth., don't remember thread name either.. :|
Hello,
I got my Xperia 10 into a bootloop. I'm still able to enter recovery, but I've never been able to get out of the bootloop, no matter what I tried.
I started trying to flash software onto it with Sony Mobile Flasher. I'm using version 0.9.28.0. Every time I try flashing, the process gets stuck on the same line:
Sending getvar:max-download-size
Does anyone know what exactly this means or how I can fix this?
Any help is greatly appreciated. :good:
Did you find a solution, I am facing the same problem.
gluzm said:
Did you find a solution, I am facing the same problem.
Click to expand...
Click to collapse
The problem stopped occurring.
However, I began having problems with the missing flash script. I fixed that and was able to flash firmware from XperiFirm.
Do you have a missing script file as well or is it just me?
Update
Here's an update.
The problem with getting stuck on getvar:max-download-size only occurs if it's the second time flashing the device after initial connection (and any attempt after that I guess).
This means, connect the phone, try flashing. If for some reason you try another flash without disconnecting the phone, it will get stuck.
This has always helped me, not sure if it's a universal solution.
Flash using Newflasher
Chronic2k13 said:
Flash using Newflasher
Click to expand...
Click to collapse
I tried that too, but it consistently reports the same errors as FlashTool concerning this problem.
Kestnix said:
I tried that too, but it consistently reports the same errors as FlashTool concerning this problem.
Click to expand...
Click to collapse
Are you deleting all the TA files before you flash?
Chronic2k13 said:
Are you deleting all the TA files before you flash?
Click to expand...
Click to collapse
Yes, I am. I don't remember whether I deleted all of them or just the ones I didn't want.
Should've I kept some in particular?
Kestnix said:
Yes, I am. I don't remember whether I deleted all of them or just the ones I didn't want.
Should've I kept some in particular?
Click to expand...
Click to collapse
Delete all of them! The one in the partition folder too! Then drag the rest of the folder into the Newflasher folder and then follow the instructions on the Newflasher page
Chronic2k13 said:
Delete all of them! The one in the partition folder too! Then drag the rest of the folder into the Newflasher folder and then follow the instructions on the Newflasher page
Click to expand...
Click to collapse
I see. Thanks! Just curious, that applies to all Xperia phones and all ROMs or is it different for older ones?
Also, is a flash script needed for NewFlasher. I don't think one is, but I haven't looked into NewFlasher as much as I should have.
Kestnix said:
I see. Thanks! Just curious, that applies to all Xperia phones and all ROMs or is it different for older ones?
Also, is a flash script needed for NewFlasher. I don't think one is, but I haven't looked into NewFlasher as much as I should have.
Click to expand...
Click to collapse
I think it's for all Xperias after 2019! No flash script needed. You just have to have fastboot drivers and the drivers for your phone! No need to have your bootloader unlocked either.
Kestnix said:
Hello,
I got my Xperia 10 into a bootloop. I'm still able to enter recovery, but I've never been able to get out of the bootloop, no matter what I tried.
I started trying to flash software onto it with Sony Mobile Flasher. I'm using version 0.9.28.0. Every time I try flashing, the process gets stuck on the same line:
Sending getvar:max-download-size
Does anyone know what exactly this means or how I can fix this?
Any help is greatly appreciated. :good:
Click to expand...
Click to collapse
You can use newflasher(https://forum.xda-developers.com/crossdevice-dev/sony/progress-newflasher-xperia-command-line-t3619426 to flash the firmware
Tried via newflasher, deleted all .ta files, even in boot folder, but i got again and again getvar:max-download-size error. Any solution, please?
Edit: Solved. Forgot to tap on usb debugging option and then allow to computer
Solutions:
1. Tap many times build number to open developer options
2. Turn on usb debugging
3. Connect phone via cable while it is turned on and press Allow when computer asks in it
4. Then try to flash android 10. Write n n n to commands, no need any gordon driver or etc
Maybe need restart phone and pc one time, when you turn on usb debugging and then Allow it
Also i installed android driver, after connect via cable, it was yellow ? <= that sign (in computer > manage > device manager)
Kestnix said:
Update
Here's an update.
The problem with getting stuck on getvar:max-download-size only occurs if it's the second time flashing the device after initial connection (and any attempt after that I guess).
This means, connect the phone, try flashing. If for some reason you try another flash without disconnecting the phone, it will get stuck.
This has always helped me, not sure if it's a universal solution.
Click to expand...
Click to collapse
im facing the same problem, how can i flash again after it got stuck?
imkofficial said:
im facing the same problem, how can i flash again after it got stuck?
Click to expand...
Click to collapse
Try closing the program and opening it again.
Make sure it's always the first flash after opening the program.
That's what solved it for me. Though honestly, this was more than a year ago , new versions of FlashTool might not have this problem anymore? I honestly don't know, haven't tried in a while.
Kestnix said:
Try closing the program and opening it again.
Make sure it's always the first flash after opening the program.
That's what solved it for me. Though honestly, this was more than a year ago , new versions of FlashTool might not have this problem anymore? I honestly don't know, haven't tried in a while.
Click to expand...
Click to collapse
ive tried that and it didnt work
imkofficial said:
ive tried that and it didnt work
Click to expand...
Click to collapse
Also the part with reconnecting the phone for each flash? If none of this works, I don't currently have a solution... Sorry