I unfortinately formated system in clockworkmod touch recovery. Afterwards phone gets stuck at sony logo when i power on the phone. Am able to boot into fastboot and flashmode using key combinations but cant enter into the clockworkmod with key combinations as i used to do before the system format. However, i unlocked my bootloader and rooted the device before i had this problem. As a result, am not able to get sony pc companion to repair my phone. I tried flashtool but then upon flashing, it asks me to enable usb debug mode and am not able to enable debud mode since the phone doesnt boot past the sony logo.
I will appreaciate it greatly if anyobe can help me get my cute phone out of this situation
Am on android 4.0.4
For some reason, my default android OS (which comes with Xperia, once updated via Sony PC Companion app) is stuck in "Type password to decrypt storage" screen. Which is strange, because I've never put any password on it before. PC Companion wouldn't help in this regard either, so I thought I'd try to unlock it and flash it with CyanogenMOD.
But I can't seem to install the recovery. It seems to keep giving me the error:
Code:
FAILED <remote: Command not allowed>
Note that my phone isn't on Debug mode because I can't access the os. Trying to unlock the phone and swiftly installing recovery "seems" to work, but on rebooting the device I don't see a pink light. Again, after powering off and into Fastboot, I can't seem to install recovery again.
I'm stuck with a pseudo-bricked phone and not sure what to do! I'd VERY much appreciate some help!
AFAIK, there are currently no solutions, other than replacing the motherboard. There were several attempt with Flashtool with no luck.
P.S. Warranty doesn't cover it.
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.
Accidentally flashed a bad file and now it won't get past the sony logo.
Recovery is completely dead, Xperia companion doesn't continue when plugged in it just reboots, and Windows doesn't see it at all in fastboot mode (nothing in device manager - normally there should be something in "Other Devices" but it's not there)
Is there a way out of this?
did u get past it? just did the same thing.. trying to install AsteroidOS
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