Update : NVM I fixed it
I am sorry if I am posting this in the wrong place. But I need serious help.
-I was on Lineage 18.
-went to Lineage recovery
-used All in One tool to flash stock
-It was idle on System image 6 and I closed the window because nothing was happening on my phone's screen, it still showed Fastboot of Lineage. Stupid move I know
-I restarted and it showed the "Bootloader is unlocked screen" and is bootlooping to this screen ever since.
-I can only access stock recovery and stock Fastboot mode
- Tried restoring through ADB but it the device doesn't show up.
-On device manager under ports it shows Communications Port COM1 and under Other devices it shows "Android" with a yellow error symbol
Basically, I am stuck here and don't know how to proceed further.
Related
Hello.
I rooted my phone using Kingo Root and then installed the chinese recovery. However, I uninstalled a system app without realizing it and then the system began to malfunction. I flashed the stock recovery backup which I had, and, that is when my phone became useless.
The status quo:
1. The phone switches on, shows the gionee logo and then proceeds to the stock recovery.
2. When I choose to reboot, it just returns to the same screen.
3. I can enter fastboot mode (the logo screen with "fastboot mode" written in the bottom left corner") but, "fastboot devices" returns blank and any other command results in a <waiting for device>.
I have no idea how to proceed further and, without any help this phone is doomed for the drawer. I'm researching online but, so far I haven't been able to come up with a solution. I updated the fastboot+adb drivers but, the fastboot command line still doesn't work. The adb sideload command line is working but, I don't know of any way in which a custom recovery may be installed by using the sideload command in stock recovery.
Any and all help will be greatly appreciated.
Material Particulars:
H/W version: E7 Mainboard 1.3.2
S/W version E7 0301 V5636
16 GB
India
Weird: I was just using it normally, it switched off and now it stays stuck on the Google logo; when entering recovery mode, I get TWRP"s splash screen and it stays there, so I cannot even recover.
Suggestions please??
Note 1: I'm pretty bad with this kind of stuff, need step-by-step instructions.
Note 2: rom is AOSP 7.1.2 but I guess is irrelevant, as even TWRP does not load.
Thanks in advance!!
Can you fastboot boot the TWRP recovery?
Hmmm dont know exactly what that means sorry; I mean I havent tried connecting it to the laptop and using thr ADB toolkit, but I can reset via Power+VolDown to the bootloader menu (? the android layind down and giving the option to StartSystem/ SwitchOff/ Restart/ RecoveryMode), and choosing RecoveyMode it tries to launch TWRP (it even shows the logo) but stays there on the splashscreen, doesn't quite manage to give me the TWRP menus
Someone?
AndDiSa said:
Can you fastboot boot the TWRP recovery?
Click to expand...
Click to collapse
let's see... I set in recovery mode, connect to the PC (does not recognise it), and with "fastboot boot twrp.img" it just sends/writes the file, the tab shows the Google logo with open lock, and then tries to launch Twrp, but as before, it just get stuck in the splashscreen "TeamWin Recovery Project 3.3.1.0" , so just the same.
Command "fastboot flash boot twrp.img" the same
Command "fastboot flash recovery twrp.img" the same
Command "adb devices" returns the list empty
Command "adb reboot recovery" returns "error: no devices / emulators found"
Command "fastboot oem unlock" returns "(bootloader) bootloader is already unlocked"
I tried running a tool called FirstAid (https://forum.xda-developers.com/devdb/project/dl/?id=16684) but does nothing for me
I'm lost, please help
Video and photos of the issue (device, not adb)
video: https://photos.app.goo.gl/GrFrmQhbyQeHVFZN7
Well, looking at your video it seems that there is no bootable ROM installed and also the recovery (for what ever reason) has some issues to start.
The fact, that you are able to boot into bootloader shows that at least it's not completely bricked ... but there's still the chance that the flash memory has some issues.
I would connect the device via usb with a PC and try to do a
fastboot boot <twrp-3.3.1-grouper.img>
to whether in that case the recovery is booting.
If this is successful, the next step would be re-flashing the recovery into the recovery partition and booing into recovery mode from the bootloader.
If this is successful, too, wiping and flashing a new ROM would be the last step.
Hi all.
I have a Moto G7 device. I installed TWRP and then rooted with Magisk. Some time ago I got a screen with the message "System update available" and, by mistake, I pressed the "Download and install" button; the update didn't take place but now I don't have access to the recovery.
When I boot into recovery I get a message that says "No command" and the image of a broken Android robot.
When I boot into fastboot mode there is a line in red letters: AP Fastboot Flash Mode (Secure). I think that this is where the problem resides.
The phone is working fine with the stock OS. I want to reinstall TWRP and flash a GSI.
Any ideas?
Thanks in advance
Regards
PS: To temporarily boot the recovery I executed:
Code:
fastboot boot twrp-3.3.1-0-river.img
In the PC's command line I get the following message: "< waiting for any device >"
Several months back I encountered the error "E:[liblp]Logical partition metadata has invalid geometry magic signature." when trying to apply updates. I've been unable to apply updates since that time, which has concerned me.
Yesterday I noticed the release notes for a multiple month old release of Lineage Recovery stated the "Logical partition metadata has invalid geometry magic signature." error had been fixed. It made reference to returning to stock to upgrade.
Last evening I downloaded the stock rom for this device and installed it using ODIN. All is well.
I would like to put both LineageOS and Lineage Recovery back on the device. Unfortunately, I can't enter Fastboot. When I use either the key combinations or "adb reboot bootloader" I see the text "Entering Fastboot..." on the display of the device, but nothing more. I've let the device sit for about five minutes without any change. It's definitely not in fastboot because "fastboot devices" shows nothing. "adb devices" shows the device when it's in recovery, I just can't enter fastboot.
Has anyone seen this problem? I've tried wiping cache and system using the Samsung Recovery (which overwrote LineageOS Recovery when I installed the stock rom) without any improvement.
Thanks,
Bob
I've got the same issue. Anyone can help here.?
You are NOT supposed to ever use adb reboot fastboot. EVER! Always use ODIN mode.
If I remember correctly, do Samsung devices even have fastboot?
They don't but Samsung added a what's basically a dummy version of fastboot that does nothing.
Try using the key combowith the tablet connected to your PC. That got me in recovery mode and from there you should be able to go into fastboot.
The whole point is not to use fastboot LMAO, because fastboot on modern Sammy devices is just a dummy version.
Hello. I'm a newbie to these kinds of things. This secondhand phone that I bought has a HavocOS, so I've been meaning to change it. I successfully got ArrowOS 12.1 for my phone, but then I couldn't access TWRP (screen remains at the TWRP 3.23 logo). I assumed that perhaps I should reinstall the TWRP, so I tried to follow the guide in https://twrp.me/asus/asuszenfonemaxprom1.html. My phone successfully entered into fastboot mode, but when I enter the "fastboot flash recovery twrp.img" command, it says <waiting for any devices> . Where did I go wrong and how do I fix this?
Thank you in advance.
Oh, and I followed this https://forum.xda-developers.com/t/...ng-up-in-fastboot-mode-windows-10-11.4194491/ and "android" showed up in my device manager, but cmd still says <waiting for any devices>