So a while back I installed CM11, took some time but did it. Then I found out that CM12 is out. Installed that, no problems. But soon my phone started to get slow so I thought I'd go back to stock. Well.. Of course I forgot to do a backup when I installed CM11... So then I tried to install 11 again, maybe that could make my phone faster. Then the CM Recovery said that the CM11 can't be installed. After that I tried several other ROM's, but with no luck. I also had lost CWM when I installed CM12. So now I somehow managed to get TWPR but I can't do anything with it. When I wipe data and try to install a ROM, it fails. Right now I have some random 4.4.1 ROM installed but I don't have recovery and I can't install Cwm nor twpr without making the ROM disappear. So therefore I can't install any Google apps.
What I would eventually like to have is Cm11 with Google apps
Update
I unzipped FXP .zip file, in there made an IMG file from 'system' folder with ImgBurn, flashed boot.img and system.img with fastboot.
Rebooted phone.
CWM was on it and I flashed gapps.zip
Rebooted and everything working properly now.
Fastboot - recovery install fail
In SDK android tools I wrote
fastboot flash recovery [IMG name]
and it said
sending 'recovery' (size)
OKAY [0.0436s]
writing 'recovery'
FAILED (remote: command not allowed)
finished
So.. that happens with any recovery IMG I try to install.
The way I managed to finally install TWRP I wrote
fastboot flash boot recovery.img
Pretty sure that I shouldn't have done that but that installed TWRP so I could flash .zip files in it.
The only problem is that they all fail. I tried official CM11 nightly for taoshan, FXP CM11 for taoshan and neither of them worked.
The recovery said something about M5 file.. that it skipped checking it or something. Since I dont know what that means, I dont know what I'm doing wrong. I'm also pretty sure that the FXP CM11 is the excact same one I used the first time around and then it worked.
So.... any ideas about my problem?
Related
Hello,i accidentally deleted my operating system,i tried everything to flash a new one ,every custom roms out there.
The TWRP version is 2.5.0.0
Everytime i execute the ZIP files from TWRP errors appear :
Error flashing zip '/sdcard/BackToBasicsV2.zip'
Error executing updater binary in zip : 'sdcard/BackToBasics'
Could you provide me a working tutorial?I tried every tutorial from here and nothing worked,i don't know what to do anymore.
I had a similar problem in which I accidentally pressed factory reset in bootloader instead of recovery (WHY ARE THEY SO CLOSE?!). Anyway, I ended up having to factory reset from recovery and wipe everything on my phone, then I adb pushed a rom to my phone and it finally let me flash it. Although I recommend waiting until someone else posts something as this is more of a "last resort" lol
S1mpleR said:
Hello,i accidentally deleted my operating system,i tried everything to flash a new one ,every custom roms out there.
The TWRP version is 2.5.0.0
Everytime i execute the ZIP files from TWRP errors appear :
Error flashing zip '/sdcard/BackToBasicsV2.zip'
Error executing updater binary in zip : 'sdcard/BackToBasics'
Could you provide me a working tutorial?I tried every tutorial from here and nothing worked,i don't know what to do anymore.
Click to expand...
Click to collapse
Connect your phone to your PC find it in devices and format it... Download twrp 2.3.3 recovery image and install it with fast boot.. Then paste a ROM to your SD card and flash away NP...don't forget the boot.IMG when flashing your new ROM it will have to be flashed with fast boot also..
Sent from my One S using xda premium
Still not working,anyone please,any other ideas?
I was just brought a phone that's stuck at a screen with a red exclamation point in a triangle. He said he had installed the latest version of TWRP and was trying to install Xposed from recovery. At one point it was stuck booting in to TWRP recovery and after some messing around he got it stuck on the stock recovery screen. He brought it to me and now we can't get it to do anything - doesn't show up in adb or fastboot devices and can't turn it off. I have no idea what to do...?
Edit: Well, just sitting there on the desk it suddenly rebooted in to TWRP on its own. Still stuck booting in to TWRP now.
Trying holding power and volume up at same time, as soon as it shuts down switch to holding power and volume down helpfully that will get you to boot loader
HTC One (M8)
Ok, I'm lost now. We got it in to fastboot and flashed CWM to the recovery partition. Now, if it reboots in to recovery, we see CWM, and if we try to reboot to system it opens TWRP. Did he flash TWRP to the wrong partition or something? What do I do from here?
qoncept said:
Ok, I'm lost now. We got it in to fastboot and flashed CWM to the recovery partition. Now, if it reboots in to recovery, we see CWM, and if we try to reboot to system it opens TWRP. Did he flash TWRP to the wrong partition or something? What do I do from here?
Click to expand...
Click to collapse
sounds like system is wiped flash a rom
Grr, androidfilehost.com is blocked at work and I can't find a single rom anywhere else. He swears there's no way he could have wiped system -- is there anything else that could be wrong?
qoncept said:
Grr, androidfilehost.com is blocked at work and I can't find a single rom anywhere else. He swears there's no way he could have wiped system -- is there anything else that could be wrong?
Click to expand...
Click to collapse
he did something he shouldnt have
i dont think its anything else other then maybe a bad rom flash or like you said flash recovery to wrong partition i dunno, if you boot to system and it doesn't boot system thats a good sign there is no system to boot to
try this its not on androidfilehost,
http://goo.im/devs/Turge/ViperOneM8/ViperOneM8_1.3.0.zip
http://www.ab-ed.de/baadnewz/m8/insertcoin_sense6_m8-2.3.2.zip
qoncept said:
Grr, androidfilehost.com is blocked at work and I can't find a single rom anywhere else. He swears there's no way he could have wiped system -- is there anything else that could be wrong?
Click to expand...
Click to collapse
Sounds to me like TWRP got flashed to the "boot" partition. That's why you were able to flash CWM (presumably correctly), then "reboot system" from CWM but instead go into TWRP. Now that you have a recovery in the "recovery" partition you just need to flash a ROM within CWM and you'll be good to go.
I heard that the TWRP abd terminal instruction on their website are wrong and will cause this problem (flashing recovery to the "boot" partition). I always flash recoveries (and boot.img's for my other s-on devices)) via fastboot since I can easily understand the syntax.
Fastboot flash <partition> <filename>
Alright, it looks like he tried to flash a bad zip like you guys say. He wants a stock rom - can I use the stock RUU without wiping data or is he going to end up with a fresh phone no matter what?
qoncept said:
Alright, it looks like he tried to flash a bad zip like you guys say. He wants a stock rom - can I use the stock RUU without wiping data or is he going to end up with a fresh phone no matter what?
Click to expand...
Click to collapse
he can use RUU, he can use this stock rom
http://forum.xda-developers.com/showthread.php?t=2722699 (but it hosted at androidfile)
these are stock'ish( these arent androidfile)
http://forum.xda-developers.com/showthread.php?t=2727300
http://forum.xda-developers.com/showthread.php?t=2722927
Sigh.. I'm getting this when I try to flash the RUU:
Code:
C:\phone\Data>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
sending 'zip' (1572932 KB)...
OKAY [ 47.228s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 47.237s
Edit: Same with all other zips.
qoncept said:
Sigh.. I'm getting this when I try to flash the RUU:
Code:
C:\phone\Data>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
sending 'zip' (1572932 KB)...
OKAY [ 47.228s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 47.237s
Edit: Same with all other zips.
Click to expand...
Click to collapse
Since you can get into recovery (pretty sure CWM is the recovery properly installed in this case) you should just download a ROM and put it on the phone's SD Card (always check md5) and install it through CWM. If he wants stock, at least give him a pretty stock ROM like one from here:
http://forum.xda-developers.com/showthread.php?t=2708291
Keep the command line stuff to a minimum and use the GUI of the recovery, that's why they're there.
Ok, I got that BoneStock rom installed. BlinkFeed is crashing occasionally (he's using a different launcher) which is annoying but at least it works. Is there a way to get back to the stock rom from this? What will happen if he tries to do a software update?
Could I flash this?
qoncept said:
Ok, I got that BoneStock rom installed. BlinkFeed is crashing occasionally (he's using a different launcher) which is annoying but at least it works. Is there a way to get back to the stock rom from this? What will happen if he tries to do a software update?
Click to expand...
Click to collapse
If you really insist on a true stock, unrooted phone, I'd say your easiest options are either the RUU'ish option you seem to have already tried or you could look to the nandroid someone posted in this forum of his stock setup.
http://forum.xda-developers.com/showthread.php?t=2725001
Note that the nandroid was made with TWRP so you'll have to replace your CWM with TWRP (hopefully correctly this time )
Personally, I'm a fan so far of the ViperOne ROM while I'm waiting for a stable AOSP ROM. That's entirely up to you though.
cntryby429 said:
If you really insist on a true stock, unrooted phone, I'd say your easiest options are either the RUU'ish option you seem to have already tried or you could look to the nandroid someone posted in this forum of his stock setup.
http://forum.xda-developers.com/showthread.php?t=2725001
Note that the nandroid was made with TWRP so you'll have to replace your CWM with TWRP (hopefully correctly this time )
Personally, I'm a fan so far of the ViperOne ROM while I'm waiting for a stable AOSP ROM. That's entirely up to you though.
Click to expand...
Click to collapse
He just wants to get it back to bone stock so when he goes and tries again he knows what he's dealing with. It looks like restoring the system partition from that nandroid backup did it. Thanks a lot for your help!
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
angrygamer1023 said:
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
Click to expand...
Click to collapse
Try another recovery / another version. Did the trick for me and you have nothing to lose
I have 2 XT925s. I bricked one to the point that I could boot to fastboot but could not even get into stock recovery. I was running stock 4.4.2.
I did the following.
I got the DROID_RAZR_HD_Utility_1.41. I used the TWRP 2.7.1.0 in that utility specifically for XT925.
I used fastboot to manually flash TWRP into the recovery partition.
DO NOT reboot past boot menu. Right after flashing, boot into recovery. That should give you TWRP.
I used TWRP to Install CM11 snapshot. I had to manually flash into the modem partition, the modem file also obtained from the above utility. You will need to flash in gapps for 4.4.2.
That recovered the bricked phone.
Of note, I was able to flash TWRP in the other phone. Backed it up. Transfered the backed up OEM ROM into the phone running CM. And get it to run stock ROM.
I now have one running CM11, and one running stock 4.4.2. I'm just comparing battery life. I've noticed CM11 has a smaller memory footprint than stock 4.4.2.
Cheers
did not work for me anywhere to be found stock 4.4.2 recovery img for 926?
It's been quite a while since I messed with ROMs on my phone, so I thought I might look into updating it. I am currently running TWRP 2.8.5. Using the app from the app store, I tried to update it to the current version, but it failed. From there, I restarted my phone, and it took me into recovery. From here, I have been unable to escape. I keep rebooting from within TWRP, and it just returns me right back to TWRP. I'm sure it's something that I'm overlooking. Can someone help me figure out what I'm doing wrong? I am rooted, with S off.
Thanks!!
Your recovery may have been flashed to the boot partition. This was a problem with the twrp app a long while back which I assumed had been fixed but perhaps not. Download the latest twrp (2.8.5 is kinda old at this point) and flash it from a computer via fastboot:
Fastboot flash recovery [nameofrecovery].img
Boot into your new recovery, check the version number to make sure it's the new properly flashed recovery, and either restore a nandroid or flash a new Rom.
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.