When I download CM I also downloaded their recovery thinking I needed it, when I booted into twrp I wiped my data and then went to install and I didn't realize I flashed the recovery until I booted back up. Their is no OS on my phone and I'm stuck in CM recovery and I don't know how to fix my phone. LG flashtoo doesn't work, when I try to flash the stock rom it just says Failed PreviousLoad(). So if anyone knows how to fix my phone or lg flashtool please help, thanks.
isaiahramos said:
When I download CM I also downloaded their recovery thinking I needed it, when I booted into twrp I wiped my data and then went to install and I didn't realize I flashed the recovery until I booted back up. Their is no OS on my phone and I'm stuck in CM recovery and I don't know how to fix my phone. LG flashtoo doesn't work, when I try to flash the stock rom it just says Failed PreviousLoad(). So if anyone knows how to fix my phone or lg flashtool please help, thanks.
Click to expand...
Click to collapse
Hello,
Can you tell us the make and model of your device?
-Vatsal
Related
im trying to flash a recovery but i think i screwed my bootloader, up i used an app (flashify) to try to install twrp on my lg g2 d800 running android L 5.0.2 software version d80030f but now i cant even get to the stock recovery it automatically goes into fastboot mode and before that it was saying something about a critical error when i tried going into recovery. the phone still boots up normally and works so should i just give up on trying to install a custom recovery and count my losses now before i mess it up for good. i wont try anything else unless i get some logical advice from someone who knows about this problem.
Use AutoRec
I have tried that already it says i can now flash twrp but when i tried to reboot into recovery it was still stock android recovery
jesse640 said:
im trying to flash a recovery but i think i screwed my bootloader, up i used an app (flashify) to try to install twrp on my lg g2 d800 running android L 5.0.2 software version d80030f but now i cant even get to the stock recovery it automatically goes into fastboot mode and before that it was saying something about a critical error when i tried going into recovery. the phone still boots up normally and works so should i just give up on trying to install a custom recovery and count my losses now before i mess it up for good. i wont try anything else unless i get some logical advice from someone who knows about this problem.
Click to expand...
Click to collapse
Please do not post questions more than once see http://forum.xda-developers.com/general/xda-assist/lg-g2-d800-t3120582/post61015809#post61015809
This thread will be close.
Hi.
Today I wanted to upgrade from CM11 to CM12.1, but I had to upgrade the bootloader first. It all worked and I'm now on bootloader version 41.18.
When I flashed the ROM it flashed in 20 seconds from an USB stick. It seemed a little to fast. When I rebooted it worked fine and I was on Android 5.1.1, but after installing SuperSU and rebooting I stuck into a bootloop.
I'm now in a bootloop and when I try to enter the recovery the TWRP splash screen comes up, but then it goes into the bootloop again.
I have the XT1032 and my TWRP version is 2.8.6.0 and I have a TWRP backup from CM11
If someone could push me in the right direction how I can access TWRP then that would be great.
Thanks in advance.
Quick update
The phone now booted into TWRP, but when I do a restore to my backup the phone goes back to the bootloop. The same happens when I try to wipe.
zomgwalrus said:
The phone now booted into TWRP, but when I do a restore to my backup the phone goes back to the bootloop. The same happens when I try to wipe.
Click to expand...
Click to collapse
I have the same issue, cannot get into twrp, how did you managed to boot into TWRP?
i had same issues in my moto g xt1032 i tried below CM12.1 works without issues.
go recovery --- wipe---- format data
and try step install steps like install rom zip & gapps
Ok, first what do you use to flash recovery, can you reflash recovery with the lastest TWRP version (2.8.7.0) and post back the logs here? Then tell me if you can get into recovery
Its common place that twrp cause bootloop with backups.
No problem try to
Install new twrp using fastboot mode it will be work fine
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.
Hello, some days ago i found a Samsung Galaxy Ace Style (SM-G310HN/heatnfc3g) and i decided to mod it, i installed TWRP via Odin and all was ok, but when i tried to install CyanogenMod 12.1 it didn't work. Since it didn't work, i decided to flash stock ROM. It worked once, but now it doesn't work anymore. I suspect it's the PIT file, because when i reflashed stock ROM another time with a PIT file now it doesn't work anymore, let me try to explain:
When i try to flash anything (Stock ROM or recovery, custom or stock), it... doesn't, Odin says it flashed but when i reboot to recovery or reboot to stock, it stays at the Samsung logo or doesn't flash the recovery, even if it says that it flashed. What should i do? Is my phone bricked? How can i unbrick it if it's bricked?
Michy234 said:
Hello, some days ago i found a Samsung Galaxy Ace Style (SM-G310HN/heatnfc3g) and i decided to mod it, i installed TWRP via Odin and all was ok, but when i tried to install CyanogenMod 12.1 it didn't work. Since it didn't work, i decided to flash stock ROM. It worked once, but now it doesn't work anymore. I suspect it's the PIT file, because when i reflashed stock ROM another time with a PIT file now it doesn't work anymore, let me try to explain:
When i try to flash anything (Stock ROM or recovery, custom or stock), it... doesn't, Odin says it flashed but when i reboot to recovery or reboot to stock, it stays at the Samsung logo or doesn't flash the recovery, even if it says that it flashed. What should i do? Is my phone bricked? How can i unbrick it if it's bricked?
Click to expand...
Click to collapse
Have you tried booting into stock recovery and selecting the factory reset option and the wipe cache partition option? It is sometimes necessary after flashing via Odin, I've had to do it a few times to solve a bootloop.
Droidriven said:
Have you tried booting into stock recovery and selecting the factory reset option and the wipe cache partition option? It is sometimes necessary after flashing via Odin, I've had to do it a few times to solve a bootloop.
Click to expand...
Click to collapse
Well the problem is... i cant reboot into stock recovery. Its stuck in twrp, and it's not really a "bootloop", it stays stuck at the Samsung logo. I tried to wipe cache and dalvik on Twrp but nothing.
I cant even flash the stock recovery since as i said in the original post, if i try to flash EVERYTHING Odin says it flashed but on the phone nothing happened.
Michy234 said:
Well the problem is... i cant reboot into stock recovery. Its stuck in twrp, and it's not really a "bootloop", it stays stuck at the Samsung logo. I tried to wipe cache and dalvik on Twrp but nothing.
I cant even flash the stock recovery since as i said in the original post, if i try to flash EVERYTHING Odin says it flashed but on the phone nothing happened.
Click to expand...
Click to collapse
Could please someone help me?
Michy234 said:
Could please someone help me?
Click to expand...
Click to collapse
I revive this post even if its pretty old. Could someone please help?