Another "Bootlooping"-Problem - Xperia Z1 Compact Q&A, Help & Troubleshooting

My Audio-Jack was brocken, so I replaced it (and with it a new touch/display-unit and a new battery).
After reassembling the sony-logo appears but thats it (the status-led is off but works, as in fastbootmode it turns blue). I came from Resurrection Remix® Lollipop v5.5.9.
I can access flash/fastboot and also tried to (not exactly in this order):
Did a full wipe
Relock bootloader
Do a System-Reset with PCC
Unlock bootloader again
Flash TWRP recovery.img with fastboot
Flash Stock-Rom with flashtool (1.236 custom de, downloaded via xperifirm)
Flash boot.img from CM via fastboot
Access TWRP and install Custom-Rom
...
Nothing helped, sometimes I only had the Sony-Logo, sometimes also the small xperia on bottom.
the phone is still "open", I checked all the connectors inside twice.
Any ideas?

nampill said:
My Audio-Jack was brocken, so I replaced it (and with it a new touch/display-unit and a new battery).
After reassembling the sony-logo appears but thats it (the status-led is off but works, as in fastbootmode it turns blue). I came from Resurrection Remix® Lollipop v5.5.9.
I can access flash/fastboot and also tried to (not exactly in this order):
Did a full wipe
Relock bootloader
Do a System-Reset with PCC
Unlock bootloader again
Flash TWRP recovery.img with fastboot
Flash Stock-Rom with flashtool (1.236 custom de, downloaded via xperifirm)
Flash boot.img from CM via fastboot
Access TWRP and install Custom-Rom
...
Nothing helped, sometimes I only had the Sony-Logo, sometimes also the small xperia on bottom.
the phone is still "open", I checked all the connectors inside twice.
Any ideas?
Click to expand...
Click to collapse
I don't know, but since it happened from opening the phone, I wonder if it might be hard brick. I've seen a tutorial on fixing it with test-point - http://forum.xda-developers.com/showthread.php?t=2682255 If your fastboot works but flashes are not applying, I don't know if anything else is going to work.

levone1 said:
I don't know, but since it happened from opening the phone, I wonder if it might be hard brick. I've seen a tutorial on fixing it with test-point - http://forum.xda-developers.com/showthread.php?t=2682255 If your fastboot works but flashes are not applying, I don't know if anything else is going to work.
Click to expand...
Click to collapse
Ive never "played" with gdisk, so Flashes are applying, the phone just doesnt start. If i flash factory with flashtool, only sony logo appears, led is off. When I flash TWRP sony logo and experia logo appear, the led turns green shortly and the phone vibrates and i can access twrp. if i connect it to pc, i can even see the sony z1 and access the internal storage... strange
Is there any way to access the service menu without the dialer (from recovery, ...)?

nampill said:
Ive never "played" with gdisk, so Flashes are applying, the phone just doesnt start. If i flash factory with flashtool, only sony logo appears, led is off. When I flash TWRP sony logo and experia logo appear, the led turns green shortly and the phone vibrates and i can access twrp. if i connect it to pc, i can even see the sony z1 and access the internal storage... strange
Is there any way to access the service menu without the dialer (from recovery, ...)?
Click to expand...
Click to collapse
Try this if you can get adb shell... http://forum.xda-developers.com/showpost.php?p=41687928&postcount=5
And you said you did try repair with PC Companion, right?

levone1 said:
Try this if you can get adb shell... http://forum.xda-developers.com/showpost.php?p=41687928&postcount=5
And you said you did try repair with PC Companion, right?
Click to expand...
Click to collapse
I cant run the command out of recovery: "Error: device unauthorized. Please check the confirmation dialog on your device."
Yes, I tryed a factory reset with pc companion.

nampill said:
I cant run the command out of recovery: "Error: device unauthorized. Please check the confirmation dialog on your device."
Yes, I tryed a factory reset with pc companion.
Click to expand...
Click to collapse
With an other recovery it worked. now it says : "/sbin/sh: am: not found"

nampill said:
With an other recovery it worked. now it says : "/sbin/sh: am: not found"
Click to expand...
Click to collapse
That's odd. It would seem like adb would recognize the -am- command. Did you confirm that you're in /adb, and device recognized?

What do you mean with "in ADB"?
I flashed twrp with fastboot and entered it
I did a full wipe and flashed a custom rom
Opened cmd in plattformtools and entered the command. --> error
ADB devices -l shows the device
The infernal storage is shown in Windows, but has only one empty folder " twrp". Is that normal?
Another Problem since today: the display has now almost no backgroundlight. Hard to read.
Im suggesting a Hardware Problem in the mainboard (changed display and audiojack to the old ones and had the same problem). Is there any way to check the Hardware outside Android system?

nampill said:
What do you mean with "in ADB"?
I flashed twrp with fastboot and entered it
I did a full wipe and flashed a custom rom
Opened cmd in plattformtools and entered the command. --> error
ADB devices -l shows the device
The infernal storage is shown in Windows, but has only one empty folder " twrp". Is that normal?
Another Problem since today: the display has now almost no backgroundlight. Hard to read.
Im suggesting a Hardware Problem in the mainboard (changed display and audiojack to the old ones and had the same problem). Is there any way to check the Hardware outside Android system?
Click to expand...
Click to collapse
I'm not an expert, so just guessing, but it seems to me that your rom is not being written. I would agree that it seems like hw, especially since it happened after opening the phone.

Related

Help me is my phone is a brick?

Hi guys, I was gonna install a custom rom for the first time and yeah, everything didn't go to plan.
While the install was going on the phone shut down and now IM stuck seeing the Sony logo on my screen, (got a sony z1 compact).
I've tried all possible combinations to get it intro twrp or just the recovery but no success.
When I plug it intro my computer I get a sound but I can't connect in any way, not even adb can reconcile it with "adb devices".
Am I screwed?
How i fixed it
So this describes my problem: my phone was completely black after a bad rom install and the only thing I was able to do with the phone was to restart it using power button and volume up.
It wasn't detected in my computer but it was detected in flashtools, but when I tried to install the original firmware http://forum.xda-developers.com/showpost.php?p=62429564&postcount=5 using flashtools I got errors.
Why? My flashtool was to new and I had to dowload version 0.9.18.6 and then it was smooth as butter! hope that helped
sigurtt said:
Hi guys, I was gonna install a custom rom for the first time and yeah, everything didn't go to plan.
While the install was going on the phone shut down and now IM stuck seeing the Sony logo on my screen, (got a sony z1 compact).
I've tried all possible combinations to get it intro twrp or just the recovery but no success.
When I plug it intro my computer I get a sound but I can't connect in any way, not even adb can reconcile it with "adb devices".
Am I screwed?
Click to expand...
Click to collapse
Boot loader unlocked? Do you have fastboot on PC?
yes i got bootloader unlocked on the device and fastboot on my pc
quick update: sony companion app can detect my phone (only when turned off) but it cant interact with the phone tho.
so what would be the next logical steep to take?
i think my os i totaly deleted so there is no use trying to repair it, i need to accses the recovery mode somehow.
iv tryed doing that with fastboot (adb) (latest version) but it cant even detect the device.
-adb devices
-list of devices attaced
Is there any other way to accses recovery mode? or flash the phone w/o recovery mode (cant access phone files).
heard somthing about odin?
sigurtt said:
yes i got bootloader unlocked on the device and fastboot on my pc
Click to expand...
Click to collapse
Assuming you have phone drivers:
1 - download a custom ROM from this forum, (e.g. - crdroid)
2 - copy the boot.IMG file from the zip to whatever directory on your PC fastboot is in
3 - download twrp recovery IMG file, move it to fastboot directory
4 - hold vol up, and connect phone until you see blue LED
5 - open command prompt, cd /(wherever fastboot is)
6 - type, fastboot flash boot boot.img
7 - type, fastboot flash recovery (name of recovery).IMG
8 - unplug phone, power on, volume up when you see LED to enter recovery.
(You'll need a ROM file somewhere on your phone or SD card.)
Optionally, if you have Flashtool or Emma installed, and your phone drivers, you can open the program and connect in flash mode, ( power off hold vol down), and see if it's recognized.
Hope that helps.
Which twrp recovery IMG file shod I dowload?
Found this webpage "twrp .me/Devices" but z1 compact isn't listed.
Tried the one listed as just z and it worked (stage 6,7) and I didn't encounter the same "stuck at sonylogo" this time, just darkness when I tried to start.
I feel like a complete noob for asking this but I found the drivers for the phone here
developer.sonymobile .com/downloads/drivers/xperia-z1-compact-driver/
and iv dowloaded them but how do I install them? Tried using device manager but didn't work, tho before I ****ed up my phone I could connect like nothing so the driver shod be ok?
sigurtt said:
Which twrp recovery IMG file shod I dowload?
Found this webpage "twrp .me/Devices" but z1 compact isn't listed.
Tried the one listed as just z and it worked (stage 6,7) and I didn't encounter the same "stuck at sonylogo" this time, just darkness when I tried to start.
I feel like a complete noob for asking this but I found the drivers for the phone here
developer.sonymobile .com/downloads/drivers/xperia-z1-compact-driver/
and iv dowloaded them but how do I install them? Tried using device manager but didn't work, tho before I ****ed up my phone I could connect like nothing so the driver shod be ok?
Click to expand...
Click to collapse
If fastboot is working, you're probably fine. Recovery for Z probably won't work, try this- https://drive.google.com/file/d/0B1niPALD2vPeYnU4ZUtKYklZUFNwVWVQcnpUeHB1dGppd2pj/view?usp=sharing - Make sure to type commands properly, and make sure you have a ROM zip available. Once you flash boot and recovery, unplug phone, power on, and when you see LED, press vol up a couple times. You should be in recovery and you can flash ROM.
(Let me know if there's trouble with the link, I'll figure it out. The file's too big to attach)
Hi again! First of your an angel for helping me with this!
This is what iv done: imgur com/3xDHfKt (cant post links yet -.-)
And now the screen is just black instead of the Sony logo, flashtool can detect the phone and iv tried to install the original firmware (pretty sure iv done that correct), didn't really do anything tho.
If I try to start the phone it blinks red twice and then nothing, the computer still can't detect my phone as a device in my devices and removable storages.
What's the next logical steep? Feels like IM out in deep water :S
So just to clarify if someone else is reading this:
Phone with no rom installed at all, screen total black, can connect to the computer with fastboot, flashboot but not thought devices with removable storages.
I would have a try with Flashtool if I were you
So iv tried to learn how flashtools work and it seems pretty basic BUT its says I need a scatter file which no rom the iv dowloaded yet has :S
I did watch a couple of youtube guides on flashtools and the roms that they used to flash look nothing like mine (I dowloaded Cm for z1 compact)
And another problem is that the phone disconnects the usb connection and then reconnects exacly every 60 seconds and it might do that while ill flash the phone using flashtools.
What kind of results shall I expect if I correctly flash my phone with Cm? A fully working os with Google apps or just the os or just an access to recovery?
sigurtt said:
So iv tried to learn how flashtools work and it seems pretty basic BUT its says I need a scatter file which no rom the iv dowloaded yet has :S
I did watch a couple of youtube guides on flashtools and the roms that they used to flash look nothing like mine (I dowloaded Cm for z1 compact)
And another problem is that the phone disconnects the usb connection and then reconnects exacly every 60 seconds and it might do that while ill flash the phone using flashtools.
What kind of results shall I expect if I correctly flash my phone with Cm? A fully working os with Google apps or just the os or just an access to recovery?
Click to expand...
Click to collapse
If you want to try Flashtool...
-make sure you have a good ftf in 'firmwares', (i posted a good one here - http://forum.xda-developers.com/showpost.php?p=62429564&postcount=5 - but it's not rooted. Use a prf if you want).
-make sure you have drivers installed
1. Open Flashtool with device disconnected, wait for it to be ready
2. click 'flash' key, (top left), then check 'flash mode'
3. select chosen ftf, then click 'flash'
4. wait for 'preparing files...', takes a few minutes, then you see a new screen pop up with a diagram
5. with phone off, hold vol down while plugging it in to computer. Let go of vol down when you see Flashtool start working.
Either that will work, or you'll get an error message.
I also just remembered reading something about how you should not use newest version unless you're using certain phones. I've been using 0.9.18.6 for Z1c, and it works fine.
---------- Post added at 10:00 PM ---------- Previous post was at 09:36 PM ----------
sigurtt said:
So iv tried to learn how flashtools work and it seems pretty basic BUT its says I need a scatter file which no rom the iv dowloaded yet has :S
I did watch a couple of youtube guides on flashtools and the roms that they used to flash look nothing like mine (I dowloaded Cm for z1 compact)
And another problem is that the phone disconnects the usb connection and then reconnects exacly every 60 seconds and it might do that while ill flash the phone using flashtools.
What kind of results shall I expect if I correctly flash my phone with Cm? A fully working os with Google apps or just the os or just an access to recovery?
Click to expand...
Click to collapse
As far as CM being a good ROM, for the most part, I'd say CM-based Roms are certainly better. The only area I've seen stock Roms excel is in battery life, and some custom Roms are catching up there too, (like Euphoria 5.1, and Oregon69's MIUI port). CM interface, or AOSP, is far better than Sony's, and I personally don't like all of the fluff 'social' apps in Sony Roms. Also much better themes with CM.
imgur com/gHDYX8y
"you must have according fsc script to flash this device" but i do have the right one for sure
sigurtt said:
imgur com/gHDYX8y
"you must have according fsc script to flash this device" but i do have the right one for sure
Click to expand...
Click to collapse
I believe that is the message that goes along with what I was saying about the FT version. Which version are you using? Look at FT homepage. Also, double check 'unknown sources', and 'USB debugging' - (oh, never mind, I forgot you can't boot).
---------- Post added at 07:43 AM ---------- Previous post was at 07:35 AM ----------
sigurtt said:
imgur com/gHDYX8y
"you must have according fsc script to flash this device" but i do have the right one for sure
Click to expand...
Click to collapse
This is the list from the website- ZL,Z1,Z2,Z3,Z3c,Z3+/Z4,Z4Tablet,E4,E4G,M2,M4.
OMG I finally got it to work! Man ur an angel!
Will edit the first post with the whole process
sigurtt said:
OMG I finally got it to work! Man ur an angel!
Will edit the first post with the whole process
Click to expand...
Click to collapse
Glad to help.

LG G Pro E988 stuck on the Logo screen

I have just flash the custom 5.0.2 ROM using philz touch 6.48.4.
After I flashed the ROM, I reboot to the philz recovery and flashed back to cwm 6.0.4.8.
However, the device stuck on the LG logo screen.
I have try to enter Download mode/Emergence mode/Hard reset mode/Recovery, but all of them I cannot go into.
Please help! Thank you for your helping!!
pchuen said:
I have just flash the custom 5.0.2 ROM using philz touch 6.48.4.
After I flashed the ROM, I reboot to the philz recovery and flashed back to cwm 6.0.4.8.
However, the device stuck on the LG logo screen.
I have try to enter Download mode/Emergence mode/Hard reset mode/Recovery, but all of them I cannot go into.
Please help! Thank you for your helping!!
Click to expand...
Click to collapse
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
hawkwind212 said:
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
Click to expand...
Click to collapse
Thank you for replying.
I cannot do anythings since I cannot enter into download mode.
I pressed volume key + and - and insert the usb cable to computer. There is nothing happened, computer dose not show the devices attached and the phone stay in the LG logo screen.
Also, I cannot use adb commands to force the phone enters into download mode as it shows nothings under "List of devices".
Is there any methods I can go into the download mode???
Thank you!
pchuen said:
Thank you for replying.
I cannot do anythings since I cannot enter into download mode.
I pressed volume key + and - and insert the usb cable to computer. There is nothing happened, computer dose not show the devices attached and the phone stay in the LG logo screen.
Also, I cannot use adb commands to force the phone enters into download mode as it shows nothings under "List of devices".
Is there any methods I can go into the download mode???
Thank you!
Click to expand...
Click to collapse
If your phone shows LG start screen, it should go into Download mode. I had similar problem few days ago while I was testing some kernel patches, it just froze on the LG screen. Solution was to unplug it, remove it's battery, SIM & SD (you don't have to remove SIM & SD, I just work that way) , make sure it's off, return battery back, press Vol + & Vol - at the same time and plug-in the USB cable.
Before that, make sure you have installed LG Unified driver (can be obtained via LG's software from support site), because without that Windows won't recognise your device.
After that, once you make your phone usable with Freegee/whatever you use to install initial recovery, flash official TWRP, because others are too old - that Philz CWM is old but still working with Lollipop but not work good and is tends to lock itself into a bootloop if you use hardware keys to enter; that other one, from GPRO_recovery APK is not supported and not working well (for me since day one), so it should be replaced as soon as possible.
Also, I can suggest you to flash your phone from stock 4.1 (not KitKat), root, flash recovery via freegee and after reboot update to latest official TWRP via Flashify.
hawkwind212 said:
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
Click to expand...
Click to collapse
ShadySquirrel said:
If your phone shows LG start screen, it should go into Download mode. I had similar problem few days ago while I was testing some kernel patches, it just froze on the LG screen. Solution was to unplug it, remove it's battery, SIM & SD (you don't have to remove SIM & SD, I just work that way) , make sure it's off, return battery back, press Vol + & Vol - at the same time and plug-in the USB cable.
Before that, make sure you have installed LG Unified driver (can be obtained via LG's software from support site), because without that Windows won't recognise your device.
After that, once you make your phone usable with Freegee/whatever you use to install initial recovery, flash official TWRP, because others are too old - that Philz CWM is old but still working with Lollipop but not work good and is tends to lock itself into a bootloop if you use hardware keys to enter; that other one, from GPRO_recovery APK is not supported and not working well (for me since day one), so it should be replaced as soon as possible.
Also, I can suggest you to flash your phone from stock 4.1 (not KitKat), root, flash recovery via freegee and after reboot update to latest official TWRP via Flashify.
Click to expand...
Click to collapse
Thank you for your detail reply.
I have tried to reinstall the LG driver and try to enter download mode again.
The screen is still stuck on LG logo and I cannot find the device in hardware manager (cannot recognize it).
I cannot do anythings until it can recognize it.
(Is it the bootloader is broken? and can I fix it?)
Thank you very much and waiting for your reply soon.:good:
pchuen said:
Thank you for your detail reply.
I have tried to reinstall the LG driver and try to enter download mode again.
The screen is still stuck on LG logo and I cannot find the device in hardware manager (cannot recognize it).
I cannot do anythings until it can recognize it.
(Is it the bootloader is broken? and can I fix it?)
Thank you very much and waiting for your reply soon.:good:
Click to expand...
Click to collapse
Which version of Windows are you using? It should be displayed under Serial ports in Device manager (named something like LGE Serial device) and LGFlashTool should recognise it immediately. I can't make you a screenshot/check for real name because I'm running Linux right now and can't reboot.
Also, try with another cable/port, remove all other android drivers you may have (Samsung's, Google's...) and disable antivirus.
ShadySquirrel said:
Which version of Windows are you using? It should be displayed under Serial ports in Device manager (named something like LGE Serial device) and LGFlashTool should recognise it immediately. I can't make you a screenshot/check for real name because I'm running Linux right now and can't reboot.
Also, try with another cable/port, remove all other android drivers you may have (Samsung's, Google's...) and disable antivirus.
Click to expand...
Click to collapse
It does not work on Windows 7 and XP.
I did not find any LGE XXX under Serial ports part.
Thank you!
pchuen said:
It does not work on Windows 7 and XP.
I did not find any LGE XXX under Serial ports part.
Thank you!
Click to expand...
Click to collapse
Hm.... Phone shows that it have entered download mode? Black screen, centered gray message and "DOWNLOAD MODE" red text?
ShadySquirrel said:
Hm.... Phone shows that it have entered download mode? Black screen, centered gray message and "DOWNLOAD MODE" red text?
Click to expand...
Click to collapse
No... nothing happens, just showing LG logo...
pchuen said:
No... nothing happens, just showing LG logo...
Click to expand...
Click to collapse
OK, it doesn't enter download mode. So, step by step:
- remove battery and leave it for 15-30 seconds, return battery
- press Vol+ and Vol- at the same time and keep them pressed,
- plug USB cable in while keys are pressed
It should immediately put you into download mode, with no LG screen, just black screen with gray box and red text I've described to you.
ShadySquirrel said:
OK, it doesn't enter download mode. So, step by step:
- remove battery and leave it for 15-30 seconds,
- press Vol+ and Vol- at the same time and keep them pressed,
- plug USB cable in while keys are pressed
It should immediately put you into download mode, with no LG screen, just black screen with gray box and red text I've described to you.
Click to expand...
Click to collapse
I understand what download mode screen is.
I followed your methods, bur I still cannot enter it and the computer cannot recognize that.
Sorry for disturbing :crying:
pchuen said:
I understand what download mode screen is.
I followed your methods, bur I still cannot enter it and the computer cannot recognize that.
Sorry for disturbing :crying:
Click to expand...
Click to collapse
So, whatever you try to do, phone just shows LG logo, not even a message in an upper left corner?
I'm running out of ideas. I have exact same variant (E988) but only time it didn't want to enter download mode this way was when cable I was using was broken...
ShadySquirrel said:
So, whatever you try to do, phone just shows LG logo, not even a message in an upper left corner?
I'm running out of ideas. I have exact same variant (E988) but only time it didn't want to enter download mode this way was when cable I was using was broken...
Click to expand...
Click to collapse
I have changed the cable, but it is the same.

brick after format data

Hello,
I think I bricked my phone
I wanted to upgrade from 4.4.2 to Lollipop http://forum.xda-developers.com/sony-xperia-z1-compact/general/stock-14-6-1-236-customized-lollipop-5-t3264557
And before that I did a factory reset and format data (I got some issues on my phone and wanted to get rid of them).
Now I can not enter TWRP, I can not enter any thing. At the time beeing, after many restarts my red button is broken, I switch it off by "Power/Vol+". When I connect USB or push Power it starts and showing "SONY"-Logo, and that's it.
I can not enter flash-mode by swith off, hold Vol- and connect USB :crying:
What can I do to revive my Z1c?
Thanks for advices
BerWatch!
BerWatch said:
Hello,
I think I bricked my phone
I wanted to upgrade from 4.4.2 to Lollipop http://forum.xda-developers.com/sony-xperia-z1-compact/general/stock-14-6-1-236-customized-lollipop-5-t3264557
And before that I did a factory reset and format data (I got some issues on my phone and wanted to get rid of them).
Now I can not enter TWRP, I can not enter any thing. At the time beeing, after many restarts my red button is broken, I switch it off by "Power/Vol+". When I connect USB or push Power it starts and showing "SONY"-Logo, and that's it.
I can not enter flash-mode by swith off, hold Vol- and connect USB :crying:
What can I do to revive my Z1c?
Thanks for advices
BerWatch!
Click to expand...
Click to collapse
Do you have adb / fastboot on your computer?
levone1 said:
Do you have adb / fastboot on your computer?
Click to expand...
Click to collapse
Yes, I have, but can not enter my phone/don't know how to enter.
I tried switch off (by Power and Vol+), holding Vol- (the same with Vol+) and plug in USB - it starts by showing red light for 2 sec than "SONY", and than stps - no vibration, no light, only steady "SONY"
cmd shows: D:\Programme\Android-Tools\ADB>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
D:\Programme\Android-Tools\ADB>adb reboot recovery
error: device not found
D:\Programme\Android-Tools\ADB>adb reboot bootloader
error: device not found
Phhu, hopefully I do something wrong?!
Install these:
http://developer.sonymobile.com/downloads/drivers/xperia-z1-compact-driver/
and try again
BerWatch said:
Yes, I have, but can not enter my phone/don't know how to enter.
I tried switch off (by Power and Vol+), holding Vol- (the same with Vol+) and plug in USB - it starts by showing red light for 2 sec than "SONY", and than stps - no vibration, no light, only steady "SONY"
cmd shows: D:\Programme\Android-Tools\ADB>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
D:\Programme\Android-Tools\ADB>adb reboot recovery
error: device not found
D:\Programme\Android-Tools\ADB>adb reboot bootloader
error: device not found
Phhu, hopefully I do something wrong?!
Click to expand...
Click to collapse
Power off by holding power and volume up, just wait until it turns off. When it's totally shut off, just hold volume up while plugging in cable and don't let go of volume until you see blue led. Then you're in fastboot mode. If you have drivers installed, it's very easy to get into recovery from there. Report back.
If everything fails...
Install Flashtool on your PC, install the necessary drivers (flashtool helps you with that), download the current firmware in .ftf format and apply it with Flashtool to your phone.
No worries, we all were at your point sometime but you can always recover
Thanks for your hints, folks!
I'll try them tomorrow and give feedback than.
Happened to me once.. Accidentally wiped my data..
Only thing I managed to do is reinstall kk via flashtool
Xperia Z1 Compact .386 rooted
...nothing works.
I have almost everything installed: adb.exe (800kb from 25.07.2013), fastboot.exe (157kb from 25.07.2013), Flashtool (Version 0.9.14.0 built on 12-02-2014 22:45:00), Xperia Companion (Vers. 1.1.24.0), Z1 Compact drivers (device manager says: Sony sa0109 ADB Interface Driver Vers. 2.0.10.30018 from 13.05.2013).
Nothing can connect my Win10-PC via USB3.0 to my phone, it always starts (when I connect it to USB by holding wether Vol+ or Vol-) with red (...pink?) light for about 4sec, followed by showing "SONY" - end of anything.
I'm desperate :crying:
Do you get the green led light when connected in flash mode (vol down when connecting)?
Xperia Z1 Compact LP .386 rooted
No, only red light, than "SONY" without any vibration...
May it be, that usb-debugging was off, whenn I did format data?
BerWatch said:
No, only red light, than "SONY" without any vibration...
May it be, that usb-debugging was off, whenn I did format data?
Click to expand...
Click to collapse
I don't think it's related..
Maybe you don't have the right drivers on pc?
Xperia Z1 Compact LP .386 rooted
The fastboot or flashmode mode should always work - regardless of what you did regarding ROMs or setting or wipe etc.
It is there to save your phone if you messed up.
It is strange that you cant enter these modes. Normally its really a driver issue and you PC does not recognize your phone.
But it seems that you have tried installing them already.
Just to make sure... Your phone charges normally when you plug it in right? So it cant be a broken cable or broken micro-USB connection on your phone?
Also make sure your phone is really shut down - try resetting it with the red button next to your SIM-card slot.
Your volume buttons were fine before right?
Schlengge said:
The fastboot or flashmode mode should always work - regardless of what you did regarding ROMs or setting or wipe etc.
It is there to save your phone if you messed up.
It is strange that you cant enter these modes. Normally its really a driver issue and you PC does not recognize your phone.
But it seems that you have tried installing them already.
Just to make sure... Your phone charges normally when you plug it in right? So it cant be a broken cable or broken micro-USB connection on your phone?
Also make sure your phone is really shut down - try resetting it with the red button next to your SIM-card slot.
Your volume buttons were fine before right?
Click to expand...
Click to collapse
BINGO!!! ...the usb-cable, it's a pretty new one, but I know, the Z1c doesn't like every cable
Now I can enter Flashtools flash and fastboot mode.
I think I lost almost everything on my Z1c, even my TWRP, don't I?
What is now for noobs like me the best way to install this? http://forum.xda-developers.com/sony-xperia-z1-compact/general/stock-14-6-1-236-customized-lollipop-5-t3264557
Many Thanks!
Flash kitkat, root with pc, install twrp recovery, and flash lp rom from recovery
Xperia Z1 Compact LP .386 rooted
Oreltub said:
Flash kitkat, root with pc, install twrp recovery, and flash lp rom from recover/QUOTE]
...uuumpf, but thanks!
Does kiktkat mean 14.4.A.0.108 Android 4.4.4?
Click to expand...
Click to collapse
Yes
Xperia Z1 Compact LP .386 rooted
Thank you all for your input!
It was the usb-cable which did load my Z1c and in this case (no other data on the phone) light the purple LED and display the "SONY"-logo - but nothing else!
All the future problems are more on the software-side (my head) than on the hardware (the cable)...
Haha glad you sorted it out. I don't know why but I also have USB cables in my collection that just won't work with my Z1C... But now you know
If you need further help in restoring with flashtool you can also look up this thread for some helpful links : http://forum.xda-developers.com/showthread.php?t=2631291
Try to get your hands on a .108 firmware (I always keep one on my PC in case I f*** up ). They are easy to root with EasyRoot and from there you can flash dualrecovery. With TWRP you are good to access your backups or flash anything you want again.
Sent from my D5503 using XDA-Developers mobile app
Schlengge said:
Haha glad you sorted it out. I don't know why but I also have USB cables in my collection that just won't work with my Z1C... But now you know
If you need further help in restoring with flashtool you can also look up this thread for some helpful links : http://forum.xda-developers.com/showthread.php?t=2631291
Try to get your hands on a .108 firmware (I always keep one on my PC in case I f*** up ). They are easy to root with EasyRoot and from there you can flash dualrecovery. With TWRP you are good to access your backups or flash anything you want again.
Sent from my D5503 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks - I'll give a feedback when i'm through!

Arc S stuck on Legacy Xperia boot logo

Hey guys, so my Xperia Z's screen broke and the touch is unresponsive, so I took out my old Arc S out of the box and decided to boot it up, apparently I had gotten a new phone because this one had a booting problem.
Things I know:
It's been rooted, bootloader is unlocked, current ROM is Legacy Xperia, can't go into CWM recovery, connecting phone to PC and trying to flash new kernel won't work because flashtool doesn't recognize the device.
In device manager the phone comes up as an unknown device, downloaded the drivers from Sony's site, no luck, get error message saying "this file is not compatible with your version of Windows" or something.
I'm on W10 64bit.
So basically I'm kinda stuck, tried Google and other forums and nothing, I can't seem to get anywhere.
Could you guys help me out?
EDIT: Tried installing Android Studio, launching cmd from /appdata/roaming/android/sdk/platform-tools but when I enter the command line it says "waiting for device".
So I'm thinking this has to do with my PC not detecting my phone in fastboot mode or anyother mode.
This seems like a corrupted /system partition. First off, try another cable. Your current one might not be working (happened to me, kept reporting that it "did not recognize the device"). If that does not work, let's start with the basic troubleshooting steps. Does your phone boot info fastboot (turn off your phone, disconnect USB cable, hold menu button, reconnect USB while holding)? If it does, run "fastboot erase system" (I'm assuming you have the fastboot drivers installed and fastboot.exe in the working directory), and try booting into the recovery.
If not, let's try flashmode (turn off phone, disconnect USB, hold back button, reconnect while holding). If that works, just start up Flashtool (Download), wait for it to do its thing (sync), download the latest 4.1.B.0.587 ICS .ftf file from here. Once done, exit Flashtool, and go to the "drivers" folder. Install the flashmode drivers. Go back to Flashtool now.
In Flashtool, click the flash icon in the top-right of the program, and on the top you will find the working directory. Click the button on the right to it and select the directory where you downloaded the .ftf file. A new entry will show up in the menu on the left side. Click on it. Flashtool will prepare the file for flashing and instruct you how to connect your phone in flashmode. Be patient, this process may take a while. Once done (Flashtool will tell you), disconnect the phone, take the battery out for 5 seconds and put it back in, and then boot up the phone. The "SONY" logo should show up, followed by the "XPERIA" logo.
Set your phone up, and have fun flashing!
P.S. If you have any problems with your PC not recognizing your device while in USB Debugging (ADB says no devices), this worked for me.
bsevcenk said:
This seems like a corrupted /system partition. First off, try another cable. Your current one might not be working (happened to me, kept reporting that it "did not recognize the device"). If that does not work, let's start with the basic troubleshooting steps. Does your phone boot info fastboot (turn off your phone, disconnect USB cable, hold menu button, reconnect USB while holding)? If it does, run "fastboot erase system" (I'm assuming you have the fastboot drivers installed and fastboot.exe in the working directory), and try booting into the recovery.
If not, let's try flashmode (turn off phone, disconnect USB, hold back button, reconnect while holding). If that works, just start up Flashtool (Download), wait for it to do its thing (sync), download the latest 4.1.B.0.587 ICS .ftf file from here. Once done, exit Flashtool, and go to the "drivers" folder. Install the flashmode drivers. Go back to Flashtool now.
In Flashtool, click the flash icon in the top-right of the program, and on the top you will find the working directory. Click the button on the right to it and select the directory where you downloaded the .ftf file. A new entry will show up in the menu on the left side. Click on it. Flashtool will prepare the file for flashing and instruct you how to connect your phone in flashmode. Be patient, this process may take a while. Once done (Flashtool will tell you), disconnect the phone, take the battery out for 5 seconds and put it back in, and then boot up the phone. The "SONY" logo should show up, followed by the "XPERIA" logo.
Set your phone up, and have fun flashing!
P.S. If you have any problems with your PC not recognizing your device while in USB Debugging (ADB says no devices), this worked for me.
Click to expand...
Click to collapse
Hey man thank you so much for replying to the thread.
So I feel like a dumbass, multiple times I've read about changing cables, guess what, that's all it took.
So basically I changed the cable and instead of "unrecognized device" I got "S1 fastboot device", after that I installed the adb drivers for the Xperia Arc and voilà, it recognized as an adb device.
Onto platform-tools folder, cmd, flashed the kernel for Cyanogen 10, finally got into recovery and now after a full system wipe I'm flashing CM.
I'll let you know how it turns out.
Thanks a bunch!
Wolfarm141 said:
Hey man thank you so much for replying to the thread.
So I feel like a dumbass, multiple times I've read about changing cables, guess what, that's all it took.
So basically I changed the cable and instead of "unrecognized device" I got "S1 fastboot device", after that I installed the adb drivers for the Xperia Arc and voilà, it recognized as an adb device.
Onto platform-tools folder, cmd, flashed the kernel for Cyanogen 10, finally got into recovery and now after a full system wipe I'm flashing CM.
I'll let you know how it turns out.
Thanks a bunch!
Click to expand...
Click to collapse
Glad to know I helped!
Everything works fine now! Thanks sooo much!

Sorta/Kinda Brick After Attempted TWRP Install - Moto G7 Play 1952-4

Ok, so I’ve run myself off the road into a deep hole and am hoping someone can help me climb out and get back onto the correct path.
I have a Motorola Moto G7 Play 1952-4 (channel). My goal is to install TWRP, and LineageOS 18.1 with GAPPS. Root is not important at the moment.
Here’s what I did:
After successfully unlocking the bootloader (thank you Motorola), I downloaded TWRP for Chanel from the TWRP.me site. My plan was to first install TWRP, then use TWRP’s install feature for LoS 18.1 and the GAPPS.
To install TWRP recovery, I followed the instructions on the TWRP site. After starting the ADB server on my Windows 10 PC and booting the phone into the stock recovery, I used “adb boot twrp-3.5.2_10-0-channel.img” to temporarily boot into TWRP recovery. I then used ADB to push TWRP.zip onto the internal SDCARD. I used TWRP’s install feature to install "twrp-installer-3.5.2_10-0-channel.zip", presumably to both slots. To the best of my memory, everything completed correctly.
BUT . . . when I powered down the phone and attempted to boot into recovery, all I got was a black screen with a small N/A in the upper left corner instead of the familiar TWRP screens. After a while, the phone booted itself into the stock U.S. Cellular Android 10 (Hell Oh - Moe Toe). I've done several power-off/power-on cycles to no avail. I am able to get to and use the stock OS.
So, like TWRP.me suggests, I figured I’d just flash it back to stock and start over. Um, nope. I can Vol-DN/Power to the bootloader menu, but “adb devices” doesn’t see the phone, preventing me from flashing anything. USB Debugging is enabled and the phone says "USB Transfer Mode: Connected". “adb devices” sees the phone while Android 10 is running, but as soon as I boot into recovery, the phone “disappears” from ADB.
The only other thing I could think to do was to use the “Rescue” function in the Lenovo/Motorola Smart Assistant. While ADB can’t see the phone, LMSC sees it just fine and I was able to rescue/reinstall the stock OS successfully, or so LMSC said. Unfortunately, LMSC doesn’t seem to fix whatever is wrong with the recovery. Interestingly, “N/A” no longer appears after Vol-DN/Power and select Recovery Mode, the black screen now says “bad key”, followed a little while later by the Android logo with a “!” in the middle of the screen and “No command” below it.
And that’s the hole I now reside in. Despite considerable searching/reading here at XDA, I'm at a total loss for what to do next.
SOOOO, I’m hoping someone can help me:
1. Fix the N/A black screen
2. Get into a mode that ADB can see
3. Properly install TWRP
Thank you in advance,
Tenaya
Did you flash the copy-partitions.zip while in TWRP?
Maybe you could borrow some ideas from the official install instructions for LineageOS.
Install LineageOS on channel | LineageOS Wiki
wiki.lineageos.org
I had some strange intermittent USB connectivity issues with a few Moto G7 Plus devices with my main laptop, but was fine connecting on a 12 year old desktop computer. So perhaps you could check to see if adb connects on another machine. Only other idea I have is to somehow flash back to stock again with fastboot.
[Guide][Channel][Stock]Moto g7 play Factory Firmware Images
Moto g7 play Android 9 and 10 Factory Firmware Stock Images Info Updated on 23-11-2020 Hi there. I have found the moto g7 play stock images mirrored in lolinet servers for Android 9, and from motorola servers for Android 10. Go and download...
forum.xda-developers.com
zpunout,
Thank you for your response.
zpunout said:
Did you flash the copy-partitions.zip while in TWRP?
Click to expand...
Click to collapse
No, I didn't know I needed to; nothing about that is mentioned by TWRP.me.
This is unknown territory for me, but your question sparks a thought for me. I wonder if 1) The stock recovery is in the "other" slot, and 2) there is some way to boot from it. That could be a way to sidestep the ADB devices problem I'm having?
zpunout said:
So perhaps you could check to see if adb connects on another machine.
Click to expand...
Click to collapse
At the moment, I have no way to do that. I don't think the USB connection is the culprit, ADB "sees" the phone just fine while the phone is in the stock OS, just not in recovery (EDL?.
zpunout said:
Only other idea I have is to somehow flash back to stock again with fastboot.
Click to expand...
Click to collapse
That's my current plan, but FASTBOOT won't flash anything while ADB devices won't/can't see the phone. I'm hoping someone has a workaround of some sort for that.
Tenaya
Hi, first of all lets set some things straight, you are experiencing a Boot Loop, in other words a software brick. (Soft Brick) now luckily these are fairly simple to fix. Sorry to break it to you but the N/A Screen won't disappear, that used to be the Blue/Yellow Motorola Splash Screen, but since you unlocked your phone it'll only show N/A but thats okay there are tools that can help you customize this and change it later on.
Now why is it on a boot loop you may ask, well that is because there is no more operating system to load in. But worry not, try to get into your bootloader, and try to connect adb through there.
Tenaya43 said:
Ok, so I’ve run myself off the road into a deep hole and am hoping someone can help me climb out and get back onto the correct path.
I have a Motorola Moto G7 Play 1952-4 (channel). My goal is to install TWRP, and LineageOS 18.1 with GAPPS. Root is not important at the moment.
Here’s what I did:
After successfully unlocking the bootloader (thank you Motorola), I downloaded TWRP for Chanel from the TWRP.me site. My plan was to first install TWRP, then use TWRP’s install feature for LoS 18.1 and the GAPPS.
To install TWRP recovery, I followed the instructions on the TWRP site. After starting the ADB server on my Windows 10 PC and booting the phone into the stock recovery, I used “adb boot twrp-3.5.2_10-0-channel.img” to temporarily boot into TWRP recovery. I then used ADB to push TWRP.zip onto the internal SDCARD. I used TWRP’s install feature to install "twrp-installer-3.5.2_10-0-channel.zip", presumably to both slots. To the best of my memory, everything completed correctly.
BUT . . . when I powered down the phone and attempted to boot into recovery, all I got was a black screen with a small N/A in the upper left corner instead of the familiar TWRP screens. After a while, the phone booted itself into the stock U.S. Cellular Android 10 (Hell Oh - Moe Toe). I've done several power-off/power-on cycles to no avail. I am able to get to and use the stock OS.
So, like TWRP.me suggests, I figured I’d just flash it back to stock and start over. Um, nope. I can Vol-DN/Power to the bootloader menu, but “adb devices” doesn’t see the phone, preventing me from flashing anything. USB Debugging is enabled and the phone says "USB Transfer Mode: Connected". “adb devices” sees the phone while Android 10 is running, but as soon as I boot into recovery, the phone “disappears” from ADB.
The only other thing I could think to do was to use the “Rescue” function in the Lenovo/Motorola Smart Assistant. While ADB can’t see the phone, LMSC sees it just fine and I was able to rescue/reinstall the stock OS successfully, or so LMSC said. Unfortunately, LMSC doesn’t seem to fix whatever is wrong with the recovery. Interestingly, “N/A” no longer appears after Vol-DN/Power and select Recovery Mode, the black screen now says “bad key”, followed a little while later by the Android logo with a “!” in the middle of the screen and “No command” below it.
And that’s the hole I now reside in. Despite considerable searching/reading here at XDA, I'm at a total loss for what to do next.
SOOOO, I’m hoping someone can help me:
1. Fix the N/A black screen
2. Get into a mode that ADB can see
3. Properly install TWRP
Thank you in advance,
Tenaya
Click to expand...
Click to collapse
HellxDo,
Thanks for the reply.
After I used LSMC to "rescue" the phone, it stopped displaying N/A" and began showing "Bad key". Different, but not better.
HellxDo said:
Now why is it on a boot loop you may ask, well that is because there is no more operating system to load in.
Click to expand...
Click to collapse
Hmmm . . . The phone currently boots into the stock rom (U.S. Cellular Android 10) if I wait a while after "Bad key" displays. If there's no more OS to load in, how do it do dat?
HellxDo said:
But worry not, try to get into your bootloader, and try to connect adb through there.
Click to expand...
Click to collapse
My (limited) understanding is that the only way to "get into" my bootloader was with the Vol-DN/PWR button combination. When I do that , I get the bootloader menu, but ADB doesn't/can't see the phone - nothing is listed when I run ADB devices and fastboot won't/can't flash anything.
Is there a different/better way to get into my bootloader?
Tenaya
And the adventure continues. Here's some more information.
While continuing to research this, I was wondering if there was another way to boot the phone into EDL mode and Google found some instructions at thecustomdroid.com for using ADB to boot the phone into EDL. I booted the phone to the stock OS and used the command adb reboot edl. The phone immediately went blank, followed shortly by the "bad key" message. After a while it again booted into the stock rom.
I still cannot use fastboot because it doesn't/can't see the phone.
I have also discovered that if i use VOL-UP/PWR, the phone boots directly to "bad key", followed by the stock rom. Another dead end.
I also used LMSC to "Rescue" the phone again and learned several things:
While LMSC is running, it boots the phone into the bootloader menu and begins to flash. If I do adb devices while LMSC is flashing, the phone STILL doesn't appear in the list.
LMSC definitely flashed the stock OS - when the phone rebooted, it was back to the stock OS Android start screen as if it had never been configured.
There is still no recovery and I still can't flash anything.
LMSC is somehow able to flash without a recovery present.
Anyone have any other ideas?
Tenaya
Tenaya43 said:
And the adventure continues. Here's some more information.
While continuing to research this, I was wondering if there was another way to boot the phone into EDL mode and Google found some instructions at thecustomdroid.com for using ADB to boot the phone into EDL. I booted the phone to the stock OS and used the command adb reboot edl. The phone immediately went blank, followed shortly by the "bad key" message. After a while it again booted into the stock rom.
I still cannot use fastboot because it doesn't/can't see the phone.
I have also discovered that if i use VOL-UP/PWR, the phone boots directly to "bad key", followed by the stock rom. Another dead end.
I also used LMSC to "Rescue" the phone again and learned several things:
While LMSC is running, it boots the phone into the bootloader menu and begins to flash. If I do adb devices while LMSC is flashing, the phone STILL doesn't appear in the list.
LMSC definitely flashed the stock OS - when the phone rebooted, it was back to the stock OS Android start screen as if it had never been configured.
There is still no recovery and I still can't flash anything.
LMSC is somehow able to flash without a recovery present.
Anyone have any other ideas?
Tenaya
Click to expand...
Click to collapse
If "fastboot devices" can't see your device while in bootloader mode, that could be the same issue I had relating to your USB compatibility with your computer. Try to borrow someone else's computer, install "platform-tools" to see if the "fastboot devices" command works.
If that works, next see if the command "fastboot getvar all" works. You should get many lines of info come up. If it gets stuck after a couple of lines, then the symptoms are the same as what I had. I have a bunch of really old laptops and a desktop sitting around with platform-tools just for this issue. I have heard others say that plugging the phone in via a USB hub sometimes gets fastboot to connect properly, but I haven't had success yet.
OK, some progress.
I found this:
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
kenzo has graciously hacked fastboot.exe to force the phone into EDL mode. Using that, the phone booted into EDL and fastboot devices can now "see" the phone. Thank you kenzo.
BTW, kenzo's fastboot-edl isn't G7 Play specific, it was originally for the Xiaomi Redme Note 3 and seems to work for some other Android phones as well.
I'm still working on getting TWRP and LoS installed, but at least fastboot can talk to the phone.
zpunout said:
I have heard others say that plugging the phone in via a USB hub sometimes gets fastboot to connect properly
Click to expand...
Click to collapse
I also had no luck with a USB hub.
I haven't tried another computer yet; I'm going to see what I can accomplish with fastboot-edl.
Tenaya
fastboot oem blankflash

Categories

Resources