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.
Related
I am a relatively new android user but do enjoy flashing roms, kernels etc
My problems began when i was trying to flash a new rom on my Nexus 5
I was trying to flash this rom http://forum.xda-developers.com/showthread.php?t=2655722 but despite doing a factory reset and wiping the dalvik cache and cache it refused to boot in to the new rom
I tried to flash the rom multiple times but without success, eventually when trying to boot into recovery to try again i was greeted with an unthemed TWRP recovery asking for a password despite the fact that i had a custom theme and multirom installed I tried to proceed anyways but was greeted with E: unable to mount storage
In desperation i tried to solve this problem and found this
UsoftTech :: WwW.UsoftTech.CoM ::
TWRP asking for password
After unboxing my Nexus 5, here's what I did:
1. Booted into bootloader
2. fastboot oem unlock
3. Flashed TWRP v2.6.3.0
4. Booted to recovery
The screen that greeted me says "Please Enter Your Password".
I can hit the cancel button below this which takes me to the normal TWRP screen. I then pushed SuperSU to /sdcard, but when I flash it it fails because it's unable to mount /cache or storage.
When I reboot to the system, it takes an awfully long time (approximately 30s) to progress past the "Google" screen, and then it just seems to sit on the booting animation forever.
Any help?
EDIT: Solved my own problem.
Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
TWRP asking for password
Click to expand...
Click to collapse
I now fear that i maybe without both a rom and all my files such as my music that was stored on my phone.
Is there any way for me to undo the damage i may have done to to my phone?
You can't recover the data. But you can push files over with ADB.
Sent from my Nexus 7 using Tapatalk
JoJostar said:
I am a relatively new android user but do enjoy flashing roms, kernels etc
My problems began when i was trying to flash a new rom on my Nexus 5
I was trying to flash this rom http://forum.xda-developers.com/showthread.php?t=2655722 but despite doing a factory reset and wiping the dalvik cache and cache it refused to boot in to the new rom
I tried to flash the rom multiple times but without success, eventually when trying to boot into recovery to try again i was greeted with an unthemed TWRP recovery asking for a password despite the fact that i had a custom theme and multirom installed I tried to proceed anyways but was greeted with E: unable to mount storage
In desperation i tried to solve this problem and found this
Wrong thread.
d
Click to expand...
Click to collapse
Hello fellas,
I had few problems with my Moto G. I was on official Moto lolipop.
I've unlocked bootloader, flashed TWRP, flashed SlimRom from dev thread, but it was hard to boot (bootlooping after phone restart, I was forced to turn down, and then turn on the phone, and sometimes it was booting) and I wanted to flash other rom, without ,,hard boot" problem.
And there is how I bricked my phone.
When I tried to wipe data in TWRP (factory/cache wipe) my phone reboots suddenly. It didn't wipe anything. It just reboot my system. I tried many times - always ending with reboot.
So, I tried to flash AICP rom without wiping anything. I installed it, and I had ,,android.acore has stopped working" error. Phone was rebooting often.
I tried to wipe my data again, without succeed. It was rebooting, and I've seen all my apps I had installed before.
I though it was TWRP fault, so I flashed CM recovery. Same thing occured. Next, I flashed CWM recovery. Same situation (reboot after choosing wipe).
So, I deleted my userdata and cache from fastboot, and tried this to solve my problems :
http://forum.xda-developers.com/moto-g/general/how-to-to-stock-5-0-2-motorola-lollipop-t3077806
Unfortunetly, it didn't helped me. Now I have one big bootloop.
What to do? Help me, please.
Thank you for your time!
////EDIT
I think I know whats happening. I have deleted my partition accidentally... I have Internal storage 0MB free, and mount errors... Is there a way to fix that, or I am screwed?
radogost said:
Hello fellas,
I had few problems with my Moto G. I was on official Moto lolipop.
I've unlocked bootloader, flashed TWRP, flashed SlimRom from dev thread, but it was hard to boot (bootlooping after phone restart, I was forced to turn down, and then turn on the phone, and sometimes it was booting) and I wanted to flash other rom, without ,,hard boot" problem.
And there is how I bricked my phone.
When I tried to wipe data in TWRP (factory/cache wipe) my phone reboots suddenly. It didn't wipe anything. It just reboot my system. I tried many times - always ending with reboot.
So, I tried to flash AICP rom without wiping anything. I installed it, and I had ,,android.acore has stopped working" error. Phone was rebooting often.
I tried to wipe my data again, without succeed. It was rebooting, and I've seen all my apps I had installed before.
I though it was TWRP fault, so I flashed CM recovery. Same thing occured. Next, I flashed CWM recovery. Same situation (reboot after choosing wipe).
So, I deleted my userdata and cache from fastboot, and tried this to solve my problems :
http://forum.xda-developers.com/moto-g/general/how-to-to-stock-5-0-2-motorola-lollipop-t3077806
Unfortunetly, it didn't helped me. Now I have one big bootloop.
What to do? Help me, please.
Thank you for your time!
Click to expand...
Click to collapse
Easiest thing to do . Reflash stock via fastboot
I tried, my friend. Bootloop. Always bootloop.
I think I have deleted my partition accidentally... I have Internal storage 0MB free, and mount errors...
Thread closed per OPs request.
Regards,
XDA-Staff
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!
About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.
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.