Hi,
I flashed my oneplus one with different roms using twrp 2.8.4.0, Recently i Changed my recovery to Multirom twrp 2.8.6.0 (bacon),
It used to work, but now when I'm trying to flash any rom, it is taking too long, Menu is also taking too long. When I'm flashing the rom it is getting flashed, but there is an error message showing "Error:// Too many files to open", after it got flashed for some time the UI whatever i flashed will work correctly, but after some time it is saying "Unfortunatley, the System UI Stopped", It will restart again and work.
I will do clean flash. I don't know what is the problem...
Please help me.
http://cdn3.xda-developers.com/images/smilies/smile.gif
Related
Hi all. I own a Moto G xt1032 UK version. (GSM right?)
I was on 4.4.4 Epsilon ROM but I wanted to flash stock 4.4.4, so I used a tutorial I found on youtube that set me up to stock 4.4.2, then I upgraded to 4.4.4 and THEN there was another update to 5.0.1. So as you can guess, I upgraded to lollipop and that was it - bootloop. I have tried flashing other roms through fastboot and nothing worked, I get an error when I flash ''system'' that says ''image is too large'' once all is done, phone restarts and its stuck on bootloop once again. The bootlogo changes when I flash different rom etc. But I don't know what to do, any ideas? :/ I have also tried to flash a custom recovery and sideload the Epsilon ROM but I only get an error in my command line that says no device connected after I hit the command. Any suggestions guys? I appreciate any sort of help, thanks guys.
I'll also add that I think I have the 41.18 bootloader if it helps (it says so in the bootloader settings)
When flashing a ROM in fastboot, are you also flashing the gpt file?
Yeah. I flash everything there's to flash as all tutorials instruct.
To try and get your phone up and running, flash a custom recovery from fastboot. Once the recovery image has been flashed, use the phone's volume buttons to boot into recovery. If you can get into recovery, try and flash a custom ROM.
Ah, I forgot to add. When I attempt to flash anything from my storage it says some sort of error coun't mount /sdcard and others when the recovery opens up. I tried flashing other recoveries, TWRP, CWM both show the exact same errors..Can't mount SDcard etc. :/ That is why I tried the sideload method which didn't work for me either.
You're flashing recovery for the falcon?
Yes..for falcon. I've done it a bunch of times before, however I never had the unable to mount error in the recovery..
I don't have my moto g on me but I found Philz Touch (based on CWM) worked besr for me after i switched back from GPE to CM12. I was getting weird error messages in TWRP.
My P5100 is acting strange. Short after booting it gives errors about gapps and other apps being stopped. Those messages keep popping up, so nothing else except rebooting/shutting down is possible.
Everything I try to change (in the short time before the errors pop up) is gone after a reboot.
I tried flashing several new roms with the recovery. They all where flashed succesfully according the recovery, but still after reboot the old omni rom is back.
I tried flashing stock roms with odin, they flashed succesfull according ODIN, but still, after a reboot the old omni rom is back
I tried flashing Andi's latest TWRP build with ODIN and my current recovery. ODIN and recovery said it was succesfull but after reboot there is still the old recovery.
So basically it seems this damn thing is insome kind of read-only mode......
Any idea howto fix this ?
This is what is currently installed on the tablet :
TWRP 2.8.7.2
omnirom 5.1.1-20151116-2332-p5100-HOMEMADE
kernel 3.0.101-Omni [email protected] #1
zorka said:
My P5100 is acting strange. Short after booting it gives errors about gapps and other apps being stopped. Those messages keep popping up, so nothing else except rebooting/shutting down is possible.
Everything I try to change (in the short time before the errors pop up) is gone after a reboot.
I tried flashing several new roms with the recovery. They all where flashed succesfully according the recovery, but still after reboot the old omni rom is back.
I tried flashing stock roms with odin, they flashed succesfull according ODIN, but still, after a reboot the old omni rom is back
I tried flashing Andi's latest TWRP build with ODIN and my current recovery. ODIN and recovery said it was succesfull but after reboot there is still the old recovery.
So basically it seems this damn thing is insome kind of read-only mode......
Any idea howto fix this ?
This is what is currently installed on the tablet :
TWRP 2.8.7.2
omnirom 5.1.1-20151116-2332-p5100-HOMEMADE
kernel 3.0.101-Omni [email protected] #1
Click to expand...
Click to collapse
Something strange I just noticed.... In download mode it says "downlaod" instead of "download". Is this normal ? see screenshot
probably the same as this.......
http://forum.xda-developers.com/galaxy-tab-2/help/gt-p3100-boot-loop-recovery-information-t3307456
zorka said:
probably the same as this.......
http://forum.xda-developers.com/galaxy-tab-2/help/gt-p3100-boot-loop-recovery-information-t3307456
Click to expand...
Click to collapse
Find the 4 firmware files for tab 2 series, I tried but can't find working links anywhere. That may recover some cases of bricks and errors. I requested on other forums but, still found none available.
The emmc bug, has only one solution until now, replacement.
Hi,
This is a new Mi4w Global and I got tired of waiting to Marshmallow to come OTA so decided to try CM13 and seem to have bricked it. Please help!
I flashed latest TWRP (also tried CyanogenMod recovery), then I did the factory reset, wipe cache, flashed the CM13 ROM but it won't boot. Always flashes the Mi logo and then straight into Fastboot. I can still access recovery by holding volume up and power, but no amount of flashing the ROM seems to work. I've tried latest Stable and Nightly CyanogenMod ROMs.
Did I miss a step? One thing I remember doing which might have been the problem is while I still had the original Xiaomi recovery I opted to boot onto System 2 or whatever. I think I flashed recovery straight afterwards. I wonder if that is the cause?
Anyway, please help me! Many thanks if you can help me get my phone working again.
Update: In case this helps anyone else, I did manage to find an original Mi4 recovery so I flashed it and the I also flashed the official MIUI developer build of Marshmallow. Now my phone is unbricked. I would still like to figure out how to root it and install CM13 sometime, but at least I have a working phone for now.
It's simple, you selected system 2 before installing cm13, and two installed rom in system 1. Be on system 1 and try again.
Prashanth Meesara: said:
It's simple, you selected system 2 before installing cm13, and two installed rom in system 1. Be on system 1 and try again.
Click to expand...
Click to collapse
OK thanks. What is system 2 then, is that the "sdcard" partition? I had looked in both TWRP and Cyan recovery for an option to change the boot partition but couldn't find it.
Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.
I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Same thing happened to me! Where did you get a copy of the stock recovery? Link?
resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!
First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.
Hi everyone,
I've been trying to get TWRP to stick for a while now, but still haven't been able to get it to install. A while ago I managed to flash Resurrection Remix using Lineage recovery which does work, but since Lineage recovery is quite limited, I really wanted to get TWRP to work. Since TWRP 3.5.0 released yesterday, I gave it another shot hoping that they fixed the issue, to no success.
I can get into TWRP just fine by temp booting it with fastboot, but after flashing the installer zip, any recovery that was previously installed gets wiped and the device will reboot when trying to get into recovery. I can still boot my phone otherwise.
The steps I took to get to this point:
Unlocked bootloader
fastboot boot twrp.img
Decrypt using screen pattern (successfully)
Flashed twrp installer zip (no error messages, process finishes successfully)
Reboot into recovery (both from twrp and bootloader at a later point)
Things I've tried:
Use a different TWRP version. Same problem as described above on both 3.4.x and 3.5.x, can't get it to decrypt on lower versions due to Android 10.
Install to recovery ramdisk, this just breaks things even more, probably because it's an A/B device?
Try a different recovery. Lineage recovery works just fine, but it's very very limited. Would really like to get TWRP working.
Trying to flash the zip results in no error messages, but any previously installed recovery gets wiped and magisk is uninstalled, which leads me to believe that it has done at least something to the boot img.
Thank you in advance.
EDIT 25.02.2021:
- Attached TWRP log
EDIT 12.03.2021:
- Log didn't want to attach, they can be found here: https://pastebin.com/awnhHDBU
Same question here. It seems that you can only boot from TWRP, not install it.
Tried installing again today, to no avail. However, I was smart enough to save the log this time. I have attached it to the main post, would be much appreciated if someone could check it out.