Hi,
I have been using my P Smart (FIG-LX1) for a while with LineageOS 16 and decided to move on to Android 10. Installed LineageOS 17.1 (found it on this forum) and pph-Magisk 20.3 for root - it did work, but the system was unstable so i decided to try AOSP 10.0 instead. I entered TWRP, wiped cache,dalvik,system and data, flashed the ROM, gapps etc. It was advised to now flash stock recovery and use it to do a factory reset - and now i'm stuck here.
After flashing the recovery_ramdisk img the phone stopped being able to enter any recovery at all. The system itself does not boot (stuck on the "Your device has been unlocked (...) Your device is booting now..." screen forever), the recovery never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now"). As i can still access fastboot, I tried flashing TWRP again - the TWRP splash screen does appear, but the phone gets stuck on it. Also tried flashing another system's img - nothing changed.
Is there anything I can do or did i just brick it completely?
Thanks for help!
SOLVED:
Apparently running fastboot erase on system and userdata partitions made me able to boot into recovery/erecovery again. I do have another problem now, but it's not connected with this one so I will create another thread for that.
Could you try help me? I can't even get ADB to work anymore
Related
Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.
If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.
I decided to unlock the bootloader so that i could flash TWRP recovery but after unlocking the bootloader on my device, it has been stuck on the logo screen with "powered by android" under it. I have tried using fastboot to clear userdata & cache but that just leads to my phone again being stuck on the logo screen. The device also can't boot into recovery. When I chose to power off in fastboot it causes me to be stuck on the logo screen. Any help is appreciated I am on android oreo btw
Did you try a back to stock zip? go to fastboot and run flash-all.bat, while your device is plugged in ofcourse.
supervandd said:
I decided to unlock the bootloader so that i could flash TWRP recovery but after unlocking the bootloader on my device, it has been stuck on the logo screen with "powered by android" under it. I have tried using fastboot to clear userdata & cache but that just leads to my phone again being stuck on the logo screen. The device also can't boot into recovery. When I chose to power off in fastboot it causes me to be stuck on the logo screen. Any help is appreciated I am on android oreo btw
Click to expand...
Click to collapse
Let me guess.
You unlocked the boot loader and flashed TWRP and now you are looping, right?
There is no compatible TWRP that is compatible with Oreo on this phone.
You cannot leave TWRP installed. You can only install it along enough to get the recovery to boot.
You then must flash the stock boot image.
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
did you remember to flash a stock boot.img before flashing magisk (to clear TWRP?)
Hey everyone,
I decided to root my lg g6 and got a fickle. After unlocking the device and flashing TWRP I tried to boot into it (''adb reboot recovery'' command) and it deleted all data and then twrp shows on screen for a split second and almost instantly boots normally into android so I set it up while still being unable to access twrp and any of it's functions. Does anyone have any idea what could be the problem?
P.S. Of it helps: before that i had a problem that every time I tried to use the ''adb reboot recovery'' command the console said ''no devices/emulators found''. After a couple tries I wanted to check whether the phone was connected just to make sure (''adb devices'') and after that it worked and I ran into the problem above.
Thanks for all the answers
When you first unlock BL and flash recovery you have to manually enter recovery mode.
Hold power and vol down till it turns off. Hold same buttons again until you see lg logo. Release power and press and hold again.
Then ask you to wipe etc hit yes both times and it will boot to twrp.
I tried that but it still doesn't go into twrp. After confirming that wipe stuff it just boots into android (without wiping)
Ulrih said:
I tried that but it still doesn't go into twrp. After confirming that wipe stuff it just boots into android (without wiping)
Click to expand...
Click to collapse
You have to flash TWRP recovery and when it complete then use the button combo to boot into twrp, otherwise it will boot and restore the recovery.
flash twrp
button combo to twrp
done
Yes I've done that but the problem still exist.
btw thanks for the help
Maybe try fastboot flash recovery recovery.img
Try the all-in-one tool on this forum
By the way, I am running into the same issue.. I have a LG G6 US997,.. I have tried installing TWRP unofficial ones so many times and every time i manually try to access the recovery.. the phone simply wipes all my data to default
Hello,
I have the same problem. Did anyone figure out how to solve it? I'd highly appreciate any help.
If I try to boot into recovery, it asks me to factory reset, i hit yes twice and then the phone just goes on to boot normally. The data is not wiped but I can't get into TWRP.
If I enter "fastboot reboot recovery" after flashing TWRP it returns "fastboot: usage: unknown reboot target recovery"
So after stupidly trying to update twrp through twrp instead of fastboot, I can only access fastboot and the universal bootloader installed on the phone. If I don't do anything, the phone simply goes through universal bootloader and I see a small penguin before the screen goes back and I need to restart the phone again. However, in the bootloader I can select to go to fastboot which does work. I've tried flashing TWRP through fastboot (fastboot flash recovery twrp...) and it said success however after clicking 'reboot to recovery', the phone once again just boots to the bootloader and I'm back at square one.
Thank you so much if anyone can help!
FYI, you can update TWRP using TWRP. Nothing wrong with that, I do it all the time. It's faster and easier to do so.
You might have an incompatibility between bootstack and TWRP.
So, please provide us more info.
ROM:
Bootstack used:
TWRP version:
What were you trying to do besides updating TWRP?:
Funny thing... I'm having the exact same problem.
I instaled TWRP (3.1.1-0-9c3b7e99) using the AxonToolkit 1.2.1.
Everything went smooth with the toolkit. I could get into TWRP and did some back-ups (as recommended), then wipe Dalvik/ART Cache, System, data, cache, and finally, try to install LineageOS 15.1.
I used the files:
- ZTE_A7LOSv1_UniversalBootStack.zip
- A2017U_OreoModem.zip
- lineage-15.1-20180810-UNOFFICIAL-axon7.zip
UniversalBoot and Modem were installed correctly, but I got an error when trying to install Lineage. I can't remeber the error number but it said something like: "this ROM is for device ailsa_ii_axon7 but this device is ."
Since then... my phone is in eternal loop and can only get into Fastboot. Can't access TWRP.
Thanks in advance to anyone willing to help me.
Don't mind... I have it back.
After many reboots, It only seems that this is working different with the Universal O bootloader. On the main screen, I tap the volumen button, choose "Recovery", reboot, press the power button on the main screen, press it again, the Linux Pinguin appears, press power button again, and then TWRP is back.
After that, I got to wipe and do the normal ROM installation process.
Hey,
I have a moto e4 flashed with dotOS and TWRP, it ran out of battery yesterday, and on reboot refused to boot into the OS. My first reflex was to try booting into recovery, i managed to get into fastboot, but when i try to enter recovery it freezes on the TWRP splash screen.
I tried to reflash it, and although fastboot reports a successful reflash, It still freezes at the splash screen. I also tried to use the fastboot boot command to boot the recovery directly from memory, unsuccessfully.
For information, exact model number is XT1762.
If anyone has any ideas or experience with this issue i'd really appreciate some help !
Thanks
jman6495 said:
Hey,
I have a moto e4 flashed with dotOS and TWRP, it ran out of battery yesterday, and on reboot refused to boot into the OS. My first reflex was to try booting into recovery, i managed to get into fastboot, but when i try to enter recovery it freezes on the TWRP splash screen.
I tried to reflash it, and although fastboot reports a successful reflash, It still freezes at the splash screen. I also tried to use the fastboot boot command to boot the recovery directly from memory, unsuccessfully.
For information, exact model number is XT1762.
If anyone has any ideas or experience with this issue i'd really appreciate some help !
Thanks
Click to expand...
Click to collapse
You need to repair your /data
Caution All your Data will be lost. Get a Backup first of all!
1) Go to wipe option in twrp.
2) Select Advanced wipe
3) Tick on to Data and Select Repair or Change file system option.
4) Click on Change file system.
Most of the rom support ext4. but in this time it gave some error.
5) Change the data system to exFAT option and re change option to EXT4.
6) That"s it bro :good::good::good:
JOIN IN OUR TELEGRAM GROUP FOR MORE SUPPORTS AND NEW CUSTOM ROM LINKS.