Related
hey there!
Ok so I got this problem. My phone felt to the floor like 2 weeks ago and the screen got crashed, everything else works normally, touch is ok, screen is ok, just glass is broken, after 2 days I downloaded some dota apps and it suddenly started rebooting and crashing:
By this I mean, apps stopped working and lots of pop-up messages appeared, after some reboots It stopped turning on, so I decided to root it and installed a custom ROM the one from mike, Android Revolution, this was last week, this weekend it worked fine until sunday when it got bricked because of an outdated recovery from clockwork. I managed to solve this with some help from you guys, but now again.
I flashed the android monday again with same version, it was working well until yesterday at night, it started showing some whatsapp stopped working stuff again, i rebooted it and now a bunch of window errors... reboot it again and well... no luck it stayed in the Android loading window.
After this I was trying to install the stock version ROM from mike also, and that's when it got worse.
Flashed boot and recovery OK, then rebooted and when I tried to install the ROM it just won't let me, failed unknown error, failed remote : 00030000, and other messages, now when I try to flash the recovery again it says low battery, and when I try the script to charge it it won't work, FAILED remote: unknown reason.
What can I do guys? =S (Sorry for the long post, I just don't know what could it be, and I wish by giving that much information someone can find out the reason, contacted HTC and they said it has no guarantee since I rooted and the glass is broken)
can you still access fastboot??
if you can.. then flash the latest CWM 5.8.4.0
It will allow the phone to charge.
faiz02 said:
can you still access fastboot??
if you can.. then flash the latest CWM 5.8.4.0
It will allow the phone to charge.
Click to expand...
Click to collapse
I can but there is some weird reason that won't let me do any flash, either low battery and when it gets charged a bit (because it may charge enough sometimes) it says FAILED remote:00030000 or unknown reason.
Don't know what it could be.
I ran into the exact same problem, the charger script does not help me too (low power on usb port of pc).
Thats how I fix this:
1) disconnect original charger, let's phone die. or use shutdown in fastboot.
2) connect original charger, and wait while phone powered up (He himself off as he does not have enough battery power.). disconnect charger.
3) vol.down and hold power,choose fastboot
4) connect charger
5) choose reboot bootloader (phone will reboot in fastboot)
6) choose reboot bootloader (phone will reboot in fastboot)
7) choose reboot bootloader (phone will reboot in fastboot)
....(do it fast)
249) choose reboot bootloader (phone will reboot in fastboot)
250) choose reboot bootloader (phone will reboot in fastboot)
251) disconnect charger, choose shutdown.
252) go to PC
253) vol down, power up
254) choose fastboot
255) flash the custom recovery with power supply support
256) flash custom kernel
257) don't disconnect USB!
258) fastboot / reboot bootloader / hboot
259) recovery
260) mount USB storage
261) drop zip of custom flash to the phone
262) unmount
263) advanced / restart recovery
264) flash the zip of rom
265) restart phone and dont disturb it, at 30 minute, let hi charge.
266) disconnect USB and connect original charger (1A)
267) Have fun!
It worked but bad news... now as always I am getting the message windows, with some weird apps.
First it was htc.com.bgp or something which I found it was the weather, then whatsapp, then Personalize, pretty much everything I open stops working after a while, what can I do? This was the exact reason that brought me here in the first place. It started showing these messages and I decided to install a custom ROM, it was first stock and locked and happened, now with this Android HD ROM it is still the same.
Thanks man... i was scared like hell when i realised that by script my battery voltage didnt raise up... even worse... it became less... i was reboting bootloader for 1h, but finally it worked... now im charging it to max... then ill flash stock rom
Thanks again.
Hi everybody,
ok I will try to make this short
I have an experienced user level ROM, recovery, boot, ..
My phone is BRICKED! Is it?
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
- Using different, multiple different, no thousand different methods I tried flashing the stock OS (Yakju 4.3)
- I like SkipSoft Android ToolKit (Although I used fastboot and adb commands, I find the toolkit to do the same thing..)
- I always get an Error, when the process of flashing starts.
> PC says : Error
> Phone (in fastboot mode) says: FAILWrite Fail
INTERESTING:
- While I still was able to get into Recovery, the phone couldnt mount the sdcard (=> the internal drive)
- Some of the methods I use make the phone CRASH
> means the screen stops at its position and slowly turns completely purple
- The phone power button doesnt start the phone, to get the phone doing something at all I have to trick it:
..> I plug it into the wall charger
..> I take the battery out
..> I put the battery back in
..> I wait
..> I can get into 3 routines:
^Normal starting routine (of course stuck at google start up, since no Rom is installed)
^fastboot mode (VOL + & - & Power)
^odin mode (VOL - & Power)
..> Then I can just plug the USB cable into the PC
- 2 days ago I had (every single version) of Odin PC Software recognizing the phone (phone was in Odin mode), but it also failed after trying the recommended and unrecommended settings. Ended with an error message.
HOW:
I left my phone overnight in the car (Temp: -2 deg C), while Im sure spotify and maybe other consuming apps were playing.
Next day, my phone battery was empty and I couldnt start my normal ROM. (I had Slim Rom installed)
It was stuck at the "Google" start up display.
First intentions showed that it might be more than just the Software :/
Many days and so many hours of work, research and reading in forums, I decided to take a shot and ask here.
I appreciate everything xda-members have done for me already. Though I never needed to register for my earlier questions.
Phone data:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version -
carrier info - none
serial number - -a3c208 ***
signing - production
lock state- unlocked
BUMP!!! I have absolutely the same problem!! I can access everything, i enter the recovery trying to WIPE every single thing data,system,cache,storage etc.. but it seems it doesnt work. The information stays. I tried to "softbrick unroot & stock" with a nexus kit, everything seems ok, but after it finishes installing, it boots up on GOOGLE and after 10-15 min it starts to BOOT MY OLD CUSTOM ROM THAT I HAD BEFORE, after another 15-20 min it finally boots up and the system is EXTREMELY choppy and unresponsive and after a few minutes it restarts itself. I tried ODIN and I faced the same problem, it goes well to ~45% and then it freezes, and after a short delay odin gives FAILED. I tried several more things that i found on the internet and xda but nothing helps. Probably a corrupted partition or something. THE DAMN STORAGE DOESNT WANT TO DELETE ITSELF FFS!! PLEASE IF YOU KNOW ANY FIX/ALREADY FIXED YOURS PLEASE HELP!!! I need my phone!
can you give us more information about the error message?
valkata1212 said:
Click to expand...
Click to collapse
your issue sounds like this one, can you confirm?
Soulaysahmi said:
can you give us more information about the error message?
your issue sounds like this one, can you confirm?
Click to expand...
Click to collapse
Similar, only difference is with fastboot i can successfully flash system.img but nothing happens. With odin it fails at around 45% and then freezes. Only difference is that i cannot boot to old stock and i dont have this pulpish problem. I simply reboot on my old custom ROM configuration with all my last known icons widgets.. but the phone is choppy and unresponsive as hell.
I only get an error without any further message after flashing any of the images...
Any idea anyone? Isn't it some hardware issue?
Noo man i dont think its hardware problem, for me it all happened when my phone suddenly restarted itself and after that it bootloops forever and i have those problems
Anyone?
does erase work?
yes
can you get into recovery?
oxxomexico said:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
Click to expand...
Click to collapse
ka
how do you know that erase works, I mean that what you erased has really been erased?
One of the erase command in the toolkit was succesful, I guess. But I will recheck every error or successful message later tonight.
still NOT working
2 months have passed and I was too busy with other things.
now back to it. the problem hasnt changed.
i try fastboot flash command:
[fastboot flash bootloader x.img]
- in Computer Terminal: 'FAILED(remote:Write Fail) '
- on phone: ' FASTBOOT STATUS - FAILWriteFail '
any idea, please?
Hi guys,
my wiley fox swift gets stuck in a continual optimising apps cycle. I can't enter recovery mode, when i press power+volume up it enters fastboot
(only see the black fastboot screen can't do anything). I did not change anything on my phone (not rooted) it worked fine yesterday and today i can't get it to work.
It's always optimising apps, if it's finished then i see the cyanogen logo and it starts optimising again shortly after.
I removed the battery and did wait about 15 minutes before putting it back in, i tried waiting (after 2 hours+ of it optimising i gave up),
i does not get recognised when i connect it to the pc (although i only used it to put stuff on the sd-card before) maybe a driver would fix this but i'm not sure which one.
I'm pretty clueless right now and i would be happy if someone can help me.
Saw the same thing on a friend's device today, used fastboot to factory reset the device. Insert USB in a powered-off device while holding vol+ then using fastboot do a "fastboot -w" to factory reset and recreate the (probably corrupted) data partitions.
i installed the minimal adb and fastboot connected my phone with my pc started it and tried it.
it doesn't recognize my phone and is stuck "waiting for any devices".
what can i do now? i'm not very experienced with android phones and fastboot.
dajohre said:
i installed the minimal adb and fastboot connected my phone with my pc started it and tried it.
it doesn't recognize my phone and is stuck "waiting for any devices".
what can i do now? i'm not very experienced with android phones and fastboot.
Click to expand...
Click to collapse
ADB needs debugging to be enabled in developer options
FASTBOOT will only work if the phone is in bootloader mode
I already said in my first post:
dajohre said:
I can't enter recovery mode, when i press power+volume up it enters fastboot
(only see the black fastboot screen can't do anything). I did not change anything on my phone (not rooted)
Click to expand...
Click to collapse
since i never changed anything in my phone I haven't enabled debugging in developer options, if I could access the bootloader mode I could reset my phone but like i said,
it enters fastboot and not the bootloader from which i could enter recovery mode
under these circumstances, can i do anything?
see here https://wiki.lineageos.org/devices/crackling/
Note they call bootloader mode Download
Ok i can access recovery mode now (it was explained wrong here)
i tried to factory reset but the problem still persits.
in recovery mode i did go to ->Wipe data/factory reset then i had the options (No/No/Yes -- delete all User data/No)
i choose the third option and it did load a short while. after a reboot it still wants to optimise apps.
what's the best option now? i can choose (Apply update\ Wipe data/factory reset\Wipe cache partition\wipe media\reboot to bootloader\View recovery logs)
Fix
Hi,
I had the same issue and wrote the Wileyfox customer support.
They provided me the following instructions to fix the issue:
Download:
* 1 - ZNH0EAS2NH
* 2 - ZNH2KAS7EB
* 3 - TOS111B
Repeat for File X in [1, 2,3] :
* Goto Recovery
* Update your phone using File X
Since this is my first post I am not allowed to post links.
Find the full document including file links here: h t t p s : / / we . tl / B1IpUP6wtB
Already after running the first update my phone booted again.
Only thing I noticed is that the UI feels a little laggy / slower than before.
Regards
My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP
crazyfox21 said:
My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP
Click to expand...
Click to collapse
Can you get it to stop at fastboot, and stop rebooting over and over? Like, when it first powers down (black screen), before it starts to come back up, hold power and volume down, and boot to the fastboot screen. It should stick. From there you can flash stock ROM.
You might need to only flash stock boot.img, but when that's happened to me, I flashed the whole thing
beachfl said:
Can you get it to stop at fastboot, and stop rebooting over and over? Like, when it first powers down (black screen), before it starts to come back up, hold power and volume down, and boot to the fastboot screen. It should stick. From there you can flash stock ROM.
You might need to only flash stock boot.img, but when that's happened to me, I flashed the whole thing
Click to expand...
Click to collapse
Get some info from youtube it seems this laptop fail to detect/install adb/fastboot driver,, then my Device go to charging mode and ended up bootloop instead of charging. (because if i let the phone itself, without connecting to Laptop. . .it's rock solid on Fastboot mode)
Still try to get other PC/Laptop, seems current available one has a messy Windows. . .
When i execute "fastboot devices" on cmd,, pop-out error api-crt-. . . .- l1.1.0.dll missing
Try installing vc_redist failed to execute MSU
crazyfox21 said:
My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP
Click to expand...
Click to collapse
So Sad, was stuck in the same situation tried 100 of methods but all in vain, in the end had to send my device to customer care center & received after 15 days without charges
I use to flash rom`s when i was younger phones and tablets and never had a brick, I am glad it`s out of my system, Anyway the 8pro works fine for me as a non-gamer as it seem to be very risky to flash.
Good luck getting your problem solved.
crazyfox21 said:
My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP
Click to expand...
Click to collapse
crazyfox21 said:
Get some info from youtube it seems this laptop fail to detect/install adb/fastboot driver,, then my Device go to charging mode and ended up bootloop instead of charging. (because if i let the phone itself, without connecting to Laptop. . .it's rock solid on Fastboot mode)
Still try to get other PC/Laptop, seems current available one has a messy Windows. . .
When i execute "fastboot devices" on cmd,, pop-out error api-crt-. . . .- l1.1.0.dll missing
Try installing vc_redist failed to execute MSU
Click to expand...
Click to collapse
Greetings,
First thing I would do is grab the latest version of ADB/Fastboot, uninstall previous version and reinstall it on your Laptop as Admin, turn off your Anti-virus anti-spyware, optimization program or whatever app you may have running on your Laptop and which could prevent system modification, then run it as Admin. If during installation you are poped with installing more things like MS or google's libraries and such, install them.
You may also try to reboot your phone to fastboot while already being connected to computer which may prevent it to boot to the charging page.
If you manage to get fastboot stable enough when connected and if you have no done already, you may want to proceed with reading the [GUIDE][INFO][PSA] Redmi Note 8 Pro - Megathread + CFW and applying the anti-brick solution before flashing anything else like a recovery again.
Assuming you have not damaged anything else, to recovery from a Magisk installation failure you may only need to flash the boot.img from your exact same Stock image you were on.
If that does not suffice, flashing additionally system and userdata (all data will be lost) should fix it.
Hope this helps,
Good Luck!
PS: I am assuming your bootloader is unlocked right?
[SOLVED]
Sorry for late update. . .
Just like i mention above, cause of laptop that i borrowed so messy. . .its anti-core thing won't allow adb/fastboot connection (that's why, my device suddenly disconected and going to charging mode)
*as soon as i go to nearest net-cafe, i can do fastboot thing (Re-flash stock boot.img and TWRP) and my phone booted up normally ??
Edit : my false because i'm forget to close AVB before flashing Magisk
crazyfox21 said:
[SOLVED]
Sorry for late update. . .
Just like i mention above, cause of laptop that i borrowed so messy. . .its anti-core thing won't allow adb/fastboot connection (that's why, my device suddenly disconected and going to charging mode)
*as soon as i go to nearest net-cafe, i can do fastboot thing (Re-flash stock boot.img and TWRP) and my phone booted up normally ?
Edit : my false because i'm forget to close AVB before flashing Magisk
Click to expand...
Click to collapse
So glad you could fix it and make it work in the end! That's all what matters!
You can now mark your thread as "[SOLVED]" by editing original message tittle
Cheers!
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