I have rooted my phone and installed CM 12.1. Yesterday I backed up my data using twrp and then tried to reboot it but it didn't. It just shows up the boot image and then turns off and then shows up the same. I tried to wipe data using twrp and install a fresh rom and but now i can't access twrp. On entering twrp, it shows just the image to twrp and then suddenly the phone tries to reboot.
I also tried to install CWM recovery and then tried to wipe data but it just stuck in wiping data for a long time.
Please help...:crying::crying:
Related
So I unlocked, rooted and installed Euphoria ROM on my Moto G today, and now I'm perplexed to find that when I select the "Reboot" option either in Android or TWRP, I immediately get shoved back into TWRP. Rebooting to Bootloader works as expected, rebooting to Recovery works as expected, but the normal reboot doesn't.
Also, when my phone is offline and I plug it in, it immediately lights up and boots directly into TWRP. I don't know why this is, but I'd like to fix it since it's hit and miss trying to boot into the ROM normally.
Can anyone help me pin point the problem? In all my years with Android I've never seen an issue with boot priority such as this.
Things I have done:
-I tried to decide on a recovery so I flashed PhilZ, CWM, and TWRP in that order from the fastboot commandline
-wiped system, data, cache, dalvik cache, and flashed Euphoria ROM
Thanks!
One thing I would suggest is to flash the stock recovery and try rebooting, even i had encountered this problem. Later you can flash twrp again and everything will work fine.
Are you getting any errors while wiping partitions
sjandroiddeveloper said:
Are you getting any errors while wiping partitions
Click to expand...
Click to collapse
I'm having the same problem here. Wiping works alright, no errors at all. Although the built-in TWRP file manager is unable to see any files in the system folder.
so i wanted to backup my oneplus one using twrp 3.0 and for some reason i decided to wipe the cache before i backed it up. I went to wipe (just the regular cache) and it kept trying to wipe but it never succeeded so i just forced rebooted it went back to twrp and backed up my phone. Once the backup was done i tried to boot it up and i was met with a boot loop. Then i kept rebooting my phone and no luck. then i tried to completely wipe my phone. well just a factory reset. it didn't work i was greeted with an error saying my cache is not mounted or something like that. so now i cant even wipe anything at all and i think twrp has a feature where you can access files from recovery and that doesn't work for me. adb isnt working either i was trying to push a file. What im trying to do is flash a newer version of twrp or try to adb sideload my same rom. but i dont have access to my same rom cause the links are down. my rom is minimal os btw. any ideas ?
Edit: I've fixed the problem by booting into fastboot and flashing a newer version of twrp 3.0.2. then i wiped the cache and it was successful. then i booted up and it works!
Hi,
I recently tried to install a custom rom (Resurrection Remix) on the latest EMUI version which resulted in my device not booting anymore.
After several tries I gave up and wanted to simply use stock with root.
I installed SuperSU, but that did not show up in the application menu.
After that I recovered system and boot from a recent full backup and installed magisk.
That resulted in the device not booting anymore at all. This condition stays now.
I then reinstalled the stock rom via dload method, with a factory reset after, but it then started to be stuck in the blue screen with the honor logo.
Is there anything I can do? TWRP is gone, I only get the stock EMUI recovery.
This happened to mee too. You should try a wipe data and cache from recovery, then reboot. It worked for me.
P.s i flashed a stock recovery don't know if TWRP will work the same, try.
After the dload update the stock recovery is installed again, I wiped data and cache already, but that didnt make it work too :/
EDIT: Found the error: The /data partition is unusable in it's current state (f2fs). Is F2FS the default filesystem for /data or do I need to change it to ext4 or something?
Hi,
I had installed TWRP 2.8.5 on Galaxy Note 4. I did a factory data reset, and formatted all the system and the data partitions as my device was encrypted. I restarted my phone, and as expected it wouldn't be able to boot to an OS as I had formatted everything, but I was hoping to get into the recovery menu, but it just shows the TWRP splash image, and the screen switches off, it again activates shows a the splash image for a second and then goes blank, and does this again, it does not load into the recovery menu. I tried installing the recovery menu again via odin but experienced the same error. Can you please advise on what should be done?
Thank you
Hi, so short story is.
1. I had a backup of my stock rom that i did using twrp.
2. I flashed Franco Kernel for COS 13 downloaded from his website (https://kernels.franco-lnx.net/OnePlusOne/6.0.1/anyKernel/)
3. When i flashed i performed a Wipe dalvik cache from recovery
4. Reboted phone, and started optimizing apps but suddenly it rebooted.
5. Started optimizing apps but when it showed optimizing app 1 of 103 the phone keept restarting.
6. I decided to restore my backup made from TWRP, but then phone got stuck and restated everytime from the CYANOGENOS logo.
7. Since it was not booting, i decided to install from fastboot a clean CM13.
8. Flashed, finished and then the phone restarted, but heeey, again stuck in the CYANOGENOS Logo and restarting when the logo shows up.
9. I freak out and I don't know what to do.
So far:
fastboot is working
Cyanogen Recovery is Working ( tried the wipe from that, but still no luck)
When I plug the device directly to my PC, it shows "QHSUSB_BULK", but as i say: fastboot and COS recovery are working.
Can you guys help me, please
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
leokook said:
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
Click to expand...
Click to collapse
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Mr.Ak said:
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Click to expand...
Click to collapse
Lesson learned.