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
Related
Hello Everyone!
I recently tried to root my wileyfox swift but failed miserably. I did the following when fastbooting the recovery image -> fastboot flash system ****.img.
However, i realized my mistake too late, and now my phone is all messed up!
The phone doesnt show anything when i try to start it and i cant access fastboot again, to undo my mistake. My device manager recognizes my phone when its plugged in to my computer but i cant access any files.
Am i screwed or is there any solution to this?
Thanks in advance!!
Try to access the bootloader with the hardware button combo first (volume down + power / volume up + power). If you get into recovery, you will be able to get to the bootloader with adb or a menu entry. Depends on what recovery you have installed for the latter.
In case you have no access to the bootloader (proper soft brick), go for the QFIL method. Avoid using it unless there is no other option.
Here is the thread:
http://forum.xda-developers.com/wileyfox-swift/general/how-to-set-device-tampered-to-false-t3276317
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
Does the phone give any indication of being connected? Notification light, starting the display, etc?
If yes, make sure the phone is in the correct mode and check the drivers - some of the other forum members mentioned this and the gymnastics around the battery. This would be on my to-do list. The device might come up on the device manager as different one, so monitor the manager for any changes once you connect the device.
If you happen to have Windows 7 device laying at you house, you can try with it (if only not to worry about compatibility and sporadic Win10 behaviour).
It will be a good idea to check the turkish website for General Mobile 4G (one of the Android one derivatives of the hardware) where some people have faced similar problems using the same tool.
narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
If you need my help via TeamViewer then WhatsApp me at +27799261595 or pm me
Finally got my phone back on the device manager! However, I still get sahara error when trying the back to false method.
imgur.com/a/FsSX0
*It says no port available since i removed the phone*
Hi there!
I think I may have bricked my Fire TV Stick 1 (bought at launch in Germany)...
Current situation:
- stick turns on, shows white amazon logo on black background
- continuously rebooting; ~5s black screen, ~5s amazon logo
After months not having it used, I found out I may be able to root it by now. So I did research over the vast amount of threads and posts and was overwhelmed by the information... So I tried to get started but struggled to find the right steps and therefore maybe failed.
I updated it to 5.0.5 (stock) and tried King Root, then Kingo Root, which was a success.
I tried to use the TWRP 3.0.0-7 v2 zip and used the sh command from the respective thread (I thought that was it, since all my devices before used either TWRP or CWM).
To this point, all went through and I wanted to reboot into recovery, but there was only this generic (stock?) red text recovery screen. I waited to be sure, nothing happened and I unplugged it to reboot.
It booted fine and I reflashed the TWRP zip, in case I didn't do it properly. Again it did as expected.
I then pushed the latest prerooted 5.2.0.1 zip and rebooted to recovery, but again this generic screen, so I unplugged it early, I think.
From there on, I got stuck at the white amazon logo, see above.
I did not unlock the bootloader, adb shell confirmed it not being unlocked before.
During bootloops, I did not manage to get any control via adb or fastboot.
So, is it bricked once and for all? If not, how can I save it?
I don't care about anything stored on it.
I also have a Y-USB-OTG cable and connected a keyboard before, but could not interfere yet.
(If bricked, would a Teensy be of any use? I have one from CCast rooting days)
Thanks for reading and in advance.
I had same problem with my fire stick when used the USB power of my TV.
Did you try to power the fire stick TV with the power point and USB adapter?
l_aios said:
Hi there!
I think I may have bricked my Fire TV Stick 1 (bought at launch in Germany)...
Current situation:
- stick turns on, shows white amazon logo on black background
- continuously rebooting; ~5s black screen, ~5s amazon logo
After months not having it used, I found out I may be able to root it by now. So I did research over the vast amount of threads and posts and was overwhelmed by the information... So I tried to get started but struggled to find the right steps and therefore maybe failed.
I updated it to 5.0.5 (stock) and tried King Root, then Kingo Root, which was a success.
I tried to use the TWRP 3.0.0-7 v2 zip and used the sh command from the respective thread (I thought that was it, since all my devices before used either TWRP or CWM).
To this point, all went through and I wanted to reboot into recovery, but there was only this generic (stock?) red text recovery screen. I waited to be sure, nothing happened and I unplugged it to reboot.
It booted fine and I reflashed the TWRP zip, in case I didn't do it properly. Again it did as expected.
I then pushed the latest prerooted 5.2.0.1 zip and rebooted to recovery, but again this generic screen, so I unplugged it early, I think.
From there on, I got stuck at the white amazon logo, see above.
I did not unlock the bootloader, adb shell confirmed it not being unlocked before.
During bootloops, I did not manage to get any control via adb or fastboot.
So, is it bricked once and for all? If not, how can I save it?
I don't care about anything stored on it.
I also have a Y-USB-OTG cable and connected a keyboard before, but could not interfere yet.
(If bricked, would a Teensy be of any use? I have one from CCast rooting days)
Thanks for reading and in advance.
Click to expand...
Click to collapse
I guess you did not read enough.
At this point in time you can only root (kingoroot or kingroot) and replace root with SuperSu on a Firestick. TWRP (recovery) can not be installed because it was not released by rbox as of yet, that particular recovery\pre-rooted image is for firetv1 upgraded to OS5 and not for firestick.
Sorry man.
Have you tried to connect to a computer via USB and run kingoroot or kingroot for windows (whatever you used)? It is a small chance that will recover but it is a slim one....
mjnman said:
I had same problem with my fire stick when used the USB power of my TV.
Did you try to power the fire stick TV with the power point and USB adapter?
Click to expand...
Click to collapse
I could not remember, so I just retried it with two different chargers and two different cables (both used to power my Nexus 5).
Unfortunately resulting in the very same loop... But thanks nonetheless.
bula1ca said:
I guess you did not read enough.
At this point in time you can only root (kingoroot or kingroot) and replace root with SuperSu on a Firestick. TWRP (recovery) can not be installed because it was not released by rbox as of yet, that particular recovery\pre-rooted image is for firetv1 upgraded to OS5 and not for firestick.
Sorry man.
Have you tried to connect to a computer via USB and run kingoroot or kingroot for windows (whatever you used)? It is a small chance that will recover but it is a slim one....
Click to expand...
Click to collapse
Dang... Usually I don't make mistakes this dumb. Guess I learned my first lesson. I'll try to trace my mistake though, for future attempts.
I rooted it with the Kingo app, I think, and got that typical "stuck at 90%" and rebooted it like others did. It rebooted fine and Kingo verified it rooted.
I did not use Windows, I use Ubuntu, occasionally with Wine, yet I had no luck passing USB devices to it. (And always these missing libs...)
Normally, adb and fastboot (console) work fine (i.e. with my phone).
Now I have no chance to interfere with the bootloop, I think.
IIRC, sometimes I could spam commands and at one point adb was stuck at "waiting for device".
I tried to reproduce it just now, but could not get it again.
So, should I try adb or fastboot on another computer to be sure?
Would King(o) for Windows be of any help at this point? If so, what would be my best bet to catch it at some point I can recover it?
Is there any other way I could try? From my nooby perspective, could the bootsplash be an entrance for fastboot? Could it be just stuck trying to access erroneous partitions?
At this point I would try the most crazy and risky idea, since it is unusable anyway.
Thanks both of you for your answers.
l_aios said:
I could not remember, so I just retried it with two different chargers and two different cables (both used to power my Nexus 5).
Unfortunately resulting in the very same loop... But thanks nonetheless.
Dang... Usually I don't make mistakes this dumb. Guess I learned my first lesson. I'll try to trace my mistake though, for future attempts.
I rooted it with the Kingo app, I think, and got that typical "stuck at 90%" and rebooted it like others did. It rebooted fine and Kingo verified it rooted.
I did not use Windows, I use Ubuntu, occasionally with Wine, yet I had no luck passing USB devices to it. (And always these missing libs...)
Normally, adb and fastboot (console) work fine (i.e. with my phone).
Now I have no chance to interfere with the bootloop, I think.
IIRC, sometimes I could spam commands and at one point adb was stuck at "waiting for device".
I tried to reproduce it just now, but could not get it again.
So, should I try adb or fastboot on another computer to be sure?
Would King(o) for Windows be of any help at this point? If so, what would be my best bet to catch it at some point I can recover it?
Is there any other way I could try? From my nooby perspective, could the bootsplash be an entrance for fastboot? Could it be just stuck trying to access erroneous partitions?
At this point I would try the most crazy and risky idea, since it is unusable anyway.
Thanks both of you for your answers.
Click to expand...
Click to collapse
Do you still have root? Is your stick responding to the su command?
If so read this post: http://forum.xda-developers.com/fire-tv/help/guidance-recovering-bootloop-firetv-t3446902
If not:
Try kingoroot for windows however it is a slim change in my opinion as you wrote a FireTv image to your FireStick.
Copy and paste from: http://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
"IF YOU RUN INTO SOFTBRICK ISSUE (stuck at fire tv logo)
Make sure you have ADB drivers properly installed in your windows pc/laptop.
connect a genuine usb lead to the firestick/pc.
download the windows version of KINGO ROOT and install it.
open KINGO ROOT on the pc with Fire Stick connected up to pc and tv.
wait for the button to pop up and click root.
if you dont see AFTV or get enable debugging in the KINGO ROOT program on pc/laptop please unplug the stick from usb and replug it back in.
if this still wont work restart the pc/laptop or try another pc/laptop.
you should after clicking root boot back up into your homescreen, if it doesnt boot back into your homescreen automatically, wait around 5 minutes and unplug usb and re-plug it again. "
bula1ca said:
Do you still have root? Is your stick responding to the su command?
If so read this post: http://forum.xda-developers.com/fire-tv/help/guidance-recovering-bootloop-firetv-t3446902
If not:
Try kingoroot for windows however it is a slim change in my opinion as you wrote a FireTv image to your FireStick.
Copy and paste from: http://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
"[...]"
Click to expand...
Click to collapse
Thanks for the links, but from what I see, I need to get past the bootloader splash for adb to work. I'm stuck at the white "amazon" splash, not the colored "FireTV Stick" splash after the amazon one.
Sorry for not making it clear (and for that amount of text that maybe hid it)...
From what I understand and recall, I did only flash the recovery, right? Or does it automatically flash the zip I pushed to internal storage?
And what confuses me, the first attempt booting into recovery AFTER flashing the wrong one I got the former mentioned screen with red text. Reboot worked and the Stick was running. So I did retry and got the same red text after rebooting to recovery. I assumed it did not flash again and unplugged it earlier than the first attempt. Since then it got stuck at the white bootsplash.
Since I am still a noob, it seems to me the system wasn't touched, maybe a faulty recovery integrity forcing the bootloader to loop.
l_aios said:
Thanks for the links, but from what I see, I need to get past the bootloader splash for adb to work. I'm stuck at the white "amazon" splash, not the colored "FireTV Stick" splash after the amazon one.
Sorry for not making it clear (and for that amount of text that maybe hid it)...
From what I understand and recall, I did only flash the recovery, right? Or does it automatically flash the zip I pushed to internal storage?
And what confuses me, the first attempt booting into recovery AFTER flashing the wrong one I got the former mentioned screen with red text. Reboot worked and the Stick was running. So I did retry and got the same red text after rebooting to recovery. I assumed it did not flash again and unplugged it earlier than the first attempt. Since then it got stuck at the white bootsplash.
Since I am still a noob, it seems to me the system wasn't touched, maybe a faulty recovery integrity forcing the bootloader to loop.
Click to expand...
Click to collapse
I have no idea what you did however it will not automatically flash your zip, problem is you installed TRWP that was not meant for Firestick and overwrote its booting sequence. You most probably would had recover from your first attempt by re-installing a new image but once you tried to install it again it most probably finished writing the whole thing and damaged booting sequence.
bula1ca said:
I have no idea what you did however it will not automatically flash your zip, problem is you installed TRWP that was not meant for Firestick and overwrote its booting sequence. You most probably would had recover from your first attempt by re-installing a new image but once you tried to install it again it most probably finished writing the whole thing and damaged booting sequence.
Click to expand...
Click to collapse
Yeah, sad thing I got the wrong device, should have taken my time even more...
I googled the screen I got to two times before getting stuck:
http://forum.xda-developers.com/showpost.php?p=65968901&postcount=60
First time I waited approx. 15 minutes before pulling the plug to reboot. Since I noticed no difference I tried again and got the same screen. But this time I pulled the plug earlier, <1 minute.
I'd like to add that my bootloader was locked. Can I damage the booting sequence by corrupting the recovery or was my mistake that major to be able to do that?
I googled some key combinations to get into recovery or to bypass it, but I don't know if I get the right keys.
With my remote control I don't think I have enough time to hold the keys. Additionally I have a USB keyboard (Cherry KC1000; if possible, which keys btw?) and may be able to connect it via powered Y OTG cable.
So if anyone got any further input or ideas for me to rescue my FTVS, I'd be glad to receive it.
Thanks to all.
Anyone else maybe an idea?
The thing is, I cannot believe it is unsavable.
To summarize the current state (please see full details above):
- stuck in bootloop, white amazon logo
- flashed wrong recovery, after first flash the system booted, after second flash it got stuck (characteristics above)
- never flashed anything other than recovery
Strange thing it booted in first place, but now it refuses. Also I got the screen I mentioned above and unplugged as described above.
Can I possibly bypass the recovery check and try to boot directly to system? Or maybe interrupt for fastboot access?
If connected to PC, can you see it thru 'lsusb'? Or 'dmesg | tail'?
Kramar111 said:
If connected to PC, can you see it thru 'lsusb'? Or 'dmesg | tail'?
Click to expand...
Click to collapse
I tried both
watch -n 0.5 'dmesg | tail'
and
watch -n 0.5 'lsusb'
but with no identification whatsoever.
I double-checked with my Nexus 5 on the same port with the same cable, it identified fine.
One last bump for ideas before putting it into the trash.
At this point I've been at it for so long that I don't even remember what I did to get to this point. When I turn on the phone it comes up to a screen with a small phone that has a red triangle and exclamation point on it. I can boot into download mode and recovery mode, and the bootloader which is unlocked. I just want to know how I can flash a ROM or something so I can get the phone back to normal operating conditions. In its current state the phone does not connect to my computer no matter what I've tried so I can't use adb.
I would like help as soon as possible. I'm sure I wont get it until its too late.
well, then you better offer more details because no one CAN help you with no info not even htc itself, start by mentioning what caused the issue , what state is your phone in ( stock tom , s-off, what recovery,what firmware version.......) then we'll see how to proceed.
I think your system partition has been wiped and the exclamation mark you see is probably from the recovery.
But how can you wipe if you haven't flashed twrp yet.
You can boot to download mode, flash twrp, copy some rom to internal using twrp and then flash the rom.
shadow0820 said:
At this point I've been at it for so long that I don't even remember what I did to get to this point. When I turn on the phone it comes up to a screen with a small phone that has a red triangle and exclamation point on it. I can boot into download mode and recovery mode, and the bootloader which is unlocked. I just want to know how I can flash a ROM or something so I can get the phone back to normal operating conditions. In its current state the phone does not connect to my computer no matter what I've tried so I can't use adb.
I would like help as soon as possible. I'm sure I wont get it until its too late.
Click to expand...
Click to collapse
If you can get into download mode you should be able to connect. You are more than likely having an issue with drivers, make sure the necessary drivers for HTC fastboot/adb are installed on your system. If I'm not mistaken installing HTC sync manager will install an umbrella driver package that should work for you. Download ADB version 1.0.32.x or newer and run it from the command prompt (cd to adb directory and use 'adb x y z' format commands). Issue the command 'adb devices' and the adb program will attempt to detect your HTC 10. If you get a device identifier you are more than likely set to unbrick, let me know if that works and I'll walk you through it.
Edit: Also answers to John_124's post above will be essential in restoring your phone!
shadow0820 said:
At this point I've been at it for so long that I don't even remember what I did to get to this point. When I turn on the phone it comes up to a screen with a small phone that has a red triangle and exclamation point on it. I can boot into download mode and recovery mode, and the bootloader which is unlocked. I just want to know how I can flash a ROM or something so I can get the phone back to normal operating conditions. In its current state the phone does not connect to my computer no matter what I've tried so I can't use adb.
I would like help as soon as possible. I'm sure I wont get it until its too late.
Click to expand...
Click to collapse
Did you ever make progress on your issue? i'm having the same issue and I really need to get my phone working again soon! thanks in advance.
I was completely braindead doing too many things at once.
I was running the russion-bear stock-based rom with twrp.
Got to reading about the MM update, downloaded it, dropped it in the root folder without really thinking, and the phone rebooted and loaded twrp and then tried to install. I had to step away for a while, when I came back, the phone was black, and nothing fired up.
All I get is the double buzz when I hit the power button. No screen, nothing.
What is the best way for me to fix it?
Try plug it into your pc, fastboot devices to see if it is in fastboot or not. If yes, download the mm bootloader upgrade script and run it (find it somewhere on xda, like AICP thread). If no, use xFSTK and AFT http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Thanks. Fastboot devices didn't show anything. However, I was able to use the intel moorefield soc utility to get back into fastboot and then reflash the phone. On a whim, I skipped the fastboot flash data and did all the other steps, and it's all working fine and I don't seem to have lost anything.
But now I'm fully stock, so the marshmallow update should apply, which I'm trying next.
I just bought a 2013 Nexus 7 today for very cheap, to use in my car as a headunit and learn a bit about flashing different roms, using the timur kernal, etc. It looks like it was used at some sort of healthcare facility though, because it has some "Optum Health" software on it, deeper than just an app it remained after a factory reset. On restart the optum health logo comes up, immediately after the google logo and says loading, well before it actually loads to the home page of the tablet. So it's pretty deep. I was thinking a fresh factory ROM would help me out.
I was following this guide to get twrp on the phone, as wifi wasn't working (most likely because I had tried to remove the optum stuff by disabling apps, and I got a little trigger happy) load via adb:
https://www.xda-developers.com/how-to-install-twrp/
Everything was cool until I went to restart it. I typed "fastboot reboot" into the command prompt, she restarted, and gets infinitely stuck at the "Optum Health" logo, and the word "Loading" pulses underneath.
I can't get it back to the bootloader by holding the volume buttons and "hold", the cmd/powershell doesn't see the device connected. However, the computer makes the chime sound of a device connecting when I try to open the bootload menu using the buttons, the power shell waits longer to say it failed, but it still doesn't work.
Do I have any options? Or did I completely brick my old, cheap, facebook marketplace, probably stolen from a hospital tablet?
solson1041 said:
I can't get it back to the bootloader by holding the volume buttons and "hold", the cmd/powershell doesn't see the device connected. However, the computer makes the chime sound of a device connecting when I try to open the bootload menu using the buttons, the power shell waits longer to say it failed, but it still doesn't work.
Do I have any options? Or did I completely brick my old, cheap, facebook marketplace, probably stolen from a hospital tablet?
Click to expand...
Click to collapse
Follow these instructions to resolve the problem and flash up-to-date Android - https://wiki.lineageos.org/devices/flo/install
"With the device powered off, hold Volume Down + Power until the bootloader appears, then release the buttons." it really works.
Then connect it to a PC and install proper USB driver - https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Once you get ADB & Fastboot installed on your PC or linux , do a command prompt with the device connected.
adb devices
It should list your device in your terminal output. If and when it does..If your a little hinky on the buttons just do a command prompt: adb reboot recovery, adb will reboot your device for you into recovery mode. Then follow the LOS instructions provided for you & you will be amazed at how great your tablet works. Just a little FYI, if you've never done this before, find the "pico" gapps, don't try to install any of the bigger ones, there is not enough room on the sys partition for the full gapps install. After & if you get pico installed you can always add to it with all the room you have left now on the rest of the device. Also when you are installing LOS, make sure you find and install the gapps at the same time you install the OS, before you reboot your device. It will save you a lot of headaches. Just follow the directions and you will be very happy.