Long story short I was running latest nightly of cm13, I decided to flash to cm14 to try nougat. I had backups, during the process I pulled an idiot and wiped everything dalvik, system,data,internal storage,cache . So now I have no backups, I can still get into TWRP and attempt to flash Roms but I've tried countless ones and same outcome, TWRP just restarts half a second after it tries to flash, I've even tried the stock rom with no luck.it starts and gets to MTP enabled installing "name of rom" and then reboots . I've been using a tablet to install the Roms onto an sdcard and then using the sdcard to flash, I'm hoping it's an sdcard issue and I'm waiting to get the laptop to try and put the Roms on internal phone storage and try. I'm hoping I won't have to go back to unroofed stock using kdz tot. If anyone knows what's wrong please help.
Well I tried flashing to stock and can't get into download mode, computer won't recognize phone. So I decided to try updating Twrp flashed the image, rebooted and now I'm stuck on [11050] fast boot mode started. Nothing gets me out of that.
Hi all,
I have a P5110 tab 2.
I rooted and installed CM 10 on this device some time ago, and it's been working fine for many months.
Recently, it's started rebooting itself from the OS - i.e not at boot logo etc - it actually gets into the OS, lets you do a few things for a few seconds, then thows you out and reboots.
This device has an older version of CWM on.
I can boot into CWM Recovery, have tried wiping dalvic, cache, - everything - but still the reboots.
Have tried to load twp from zip via CWM, it says installed ok. I reboot, go back into recovery, and its still this old version of CWM.
With this being an older version of CWM, it wont let me install the later versions of CWM.
Im thinking of reflashing the stock rom (4.x.x afair), to hopefully stop the reboots, so I can get into the OS and flash the later version of TWRP, so I can then flash a later version of CM.
All a PITA!
Question is - why does the p5110 keep rebooting, out of the OS?
I read somewhere that this could be a hardware issue - chip over heating or something.
Is this device worth bothering with?
Second question - why wont CWM let me install TWRP (from Zip in external SD, .img is in the zip) - even though it says it has installed it?
Any thoughts or assistance greatly appreciated!
Could this be the "dreaded emmc chip" issue?
If this was indeed the issue - would it boot to the OS at all?
I'm assuming not, and therefore this isnt the issue - can someone confirm?
http://forum.xda-developers.com/galaxy-tab-2/general/discussion-alternative-tab-2-emmc-bug-t3306862
Maybe it is. You said you tried to flash the later versions of cwm but it didn't work yes? I think one of the symptoms is that you can't flash anything on the device because it became read-only. I may be wrong though so kindly check
EDIT: Maybe do a factory reset? If everything is still there after the wipe, 99% your emmc got read-only.
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.
After flashing TWRP and being successful, i installed LineageOS 14.1 and gapps as you have guided on your posts, i saw that there were some old folders that were left over from the many apps my wife have installed previously, so i decided to do a factory reset. After pressing factory reset, the phone restarted and booted into TWRP recovery, which then i clicked on "Format Data" from the wipe tab.
Things went really south from here on, i am unable to boot into anything i have flashed (i tried flashing LineageOS 14.1 and gapps). Once the rom and gapps are installed, the phone reboots back into TWRP again. it seems like the internal storage of the phone is still empty except with the 2 zip files i've put in. I am able to access TWRP Recovery and detect it as a R7S on my computer, but i cannot boot into anything else, its been stuck like that booting ONLY into TWRP ever since i've pressed "Format Data" which in this case is my mistake and i apologize, is there any solutions to unbrick the phone? Could anyone please help me? I would be very very thankful.
Edit: I have flashed a newer TWRP via TWRP itself under Install > install image. previously running on 3.0.2-2-r7sf-final.img but i tried downloading from TWRP website twrp-3.1.0-0-r7sf.img and flashed it vi TWRP since i cannot get into fastboot. phone booted up after wards into OS and made backups and kept it somewhere safe. was reading and panicking around the web for a good 10 hours
I was using RR Nougat for almost 1.5 year, it wasnt that stable but it was ok, but today I got stuck in a bootloop for no reason.
I tried reflashing the ROM and nothing. I wiped dalvik/cache bla bla still nothing. So I backup up everything through Tuga TWRP and then proceeded to wipe everything besides Internal storage.
I tried to install RR 6.1.0 but I had a problem installing Gapps(error 139??), so I proceeded to install TWRP-k2 and then everything went to hell. I had EFIDROID installed which is extremely buggy and now it wont enter into TWRP because of efidroid and its ramdisk errors. I have no way to uninstall Efidroid and no way to install anything else.
What is the procedure to make my phone working again? How do I Install a new ROM and TWRP and Gapps through fastboot?
Edit: Update: After following the steps in this thread https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061 it now looks like my phone is completely and utterly bricked. It won't turn on and no button combination works. Ideas?
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732