Hello everyone
I brick my device yesterday by reflashing franco kernel r2 on top of r1 , then suddenly my device behavior was so strange it boot me into the device but i lost google services and the 2nd restart i stuck out
i tried to use twrp cant boot into it to restore
i tried many method but nothing happens
i tried to flashboot boot.img , flashboot system system.img (cant)
then i tried to install the stock recovery and that went successfully but when i try to boot into it i get stuck
so all recoveries not working stock and twrp
i already unlocked my device
any idea?
Here's the unbrick too thread for this device. I know it works because I did the same thing the other day flashing Franco from r1 to r2. Enjoy and make sure you read all directions carefully.
http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306/page2
Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.
probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.
Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.
Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!
I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.
Hi all!
I have a problem and i hope you guys can help solving this. I finally decided to install a custom Rom into my Mi A2.
After some trial and error i managed to do it and i have a working phone with this ROM installed:
[ROM][11.0][OFFICIAL] DotOS v5.0 [AOSP][2021-02-15]
My problem is that i can´t access recovery because when i attempt that, the phone just hangs in the beginning (logo/splash screen) of the recovery. I have waited hours and it won´t enter recovery menu.
If i need to reboot my phone for some reason i get stuck into the same issue.
My temporary solution so far is to use fastboot and load a recovery.img and from there boot into system. This way i have a functional phone.
I have tried to install other recovery versions, but all lead to the same result so far. I have no idea what is going on and have searched a solution for this but no avail.
Does someone knows how to solve this?
Thank in advance!
SOLVED!
By chance flashed one TWRP version that worked.
twrp-3.4.0-jasmine_sprout.img by Nebrassy
Hello!
So I wanted to flash Evolution X 5.7, because I had problems with the new version, now it's stuck in the boot logo and it also wiped the recovery?! I'm stuck in fastboot. I tried flashing Orangefox using fastboot flash recovery recovery.img it returns success, no error. Then, fastboot reboot recovery. It reboots, but into the system. After that, I did a hard reset into the recovery with the upper vol. button and it got me back into fastboot. Now I'm clueless...
Thanks for reading.
Additional information:
I wiped the data and the system partition before flashing the ROM.
I'm using Artix Linux as my OS (I also have Windows 10 x86_64 but fastboot didn't see my phone, even after installing Qualcomm drivers and android_winusb.inf so I stayed with Linux)
All commands are ran under superuser privileges (with the su command)
Slymi4n said:
Hello!
So I wanted to flash Evolution X 5.7, because I had problems with the new version, now it's stuck in the boot logo and it also wiped the recovery?! I'm stuck in fastboot. I tried flashing Orangefox using fastboot flash recovery recovery.img it returns success, no error. Then, fastboot reboot recovery. It reboots, but into the system. After that, I did a hard reset into the recovery with the upper vol. button and it got me back into fastboot. Now I'm clueless...
Thanks for reading.
Additional information:
I wiped the data and the system partition before flashing the ROM.
I'm using Artix Linux as my OS (I also have Windows 10 x86_64 but fastboot didn't see my phone, even after installing Qualcomm drivers and android_winusb.inf so I stayed with Linux)
All commands are ran under superuser privileges (with the su command)
Click to expand...
Click to collapse
Search/read about Mi Flash and flashing the stock fastboot/tgz firmwares (general method for all Xiaomi phones, hence guides are not specific to this or that phone and can be found elswhere)
This is the only proper way how you should always return to the stock firmware (it means it will also install back the stock recovery, etc)
Hopefully, you didn't hard brick your phone in which case you would need to look for the paid support from someone with an authorized EDL account
zgfg said:
Search/read about Mi Flash and flashing the stock fastboot/tgz firmwares (general method for all Xiaomi phones, hence guides are not specific to this or that phone and can be found elswhere)
This is the only proper way how you should always return to the stock firmware (it means it will also install back the stock recovery, etc)
Hopefully, you didn't hard brick your phone in which case you would need to look for the paid support from someone with an authorized EDL account
Click to expand...
Click to collapse
YES!! IT WORKED!!! Thank you so much
i was installing a gsi, i went into recovery, i wiped all, and then when i rebooted, it said dm-verity is corrupted, i tried to go into recovery, it doesn't work and i get the same error, so i tried to flash the official stock rom, nothing, do you have a way to fix it? (adb doesn't work since the recovery doesn't work, i tried to reflash it but nothing)
Gamer_Mida said:
i was installing a gsi, i went into recovery, i wiped all, and then when i rebooted, it said dm-verity is corrupted, i tried to go into recovery, it doesn't work and i get the same error, so i tried to flash the official stock rom, nothing, do you have a way to fix it? (adb doesn't work since the recovery doesn't work, i tried to reflash it but nothing)
Click to expand...
Click to collapse
You can always start from scratch, in BROM mode.
Here I show how to do it:
No Recovery, No Fastboot, No FastbootD – No Problem! – Case Study with Xiaomi Redmi Note 10 5G
Caution: The process shown below is not for the average user. If you do not understand the process, you should not do it at all. There is a risk of rendering your phone completely dead. Should you …
diy.viktak.com
thanks