Database Users

[Q] Custom Recovery Doesn't Work Anymore

Hello,
I've rooted my own note 3 and flashed Temaseks unofficial cm 12 rom. Everything works perfect so I decided to do the same thing for my father. It all went well, first I rooted his phone, then I flashed CWM and flashed cm 12 by temasek. The rom works fine but I forget to install the Gapps. So I tried to install Gapps but I got an error "Failure Status 6". I googled on that error and someone told it has to do something with CWM. I tried to flash a different version of CWM but now I can't reboot into recovery mode anymore. So I can't flash anything.
I flashed another version of CWM but this one also doesn't work. Whenever I try to boot the phone into recovery mode, the blue line shows up. Rebooting into recovery mode, but after a few secs, the phone just boots the normal way. Is there anyone that can help me to get CWM back to work? In the mean time I'll try to flash TWRP by Odin.
Thanks in advance!

So I flashed latest version of CWM: Buildversion; 6.13.0, CWM Base Version V6.0.4.7. I can reboot into recovery now but still can't install Google Apps due to failure status 6. On my own Phone I run a different version of CWM, but when I try to flash it, the phone won't boot into recovery mode anymore. It only boots into recovery when I flash this V6.0.4.7 . How can I get rid of this version and flash an older version of CWM?

You'll probably have to Odin back to stock and start over...

Morningstar said:
You'll probably have to Odin back to stock and start over...
Click to expand...
Click to collapse
You mean If there is no other way to get the Google Apps on the phone, I have to go back to stock. I did make a backup with CWM on the while it was running custom firmware. Now I have 4 files on my comuter, 3.tar and 1.md5 . If I recover them, I will still have this not working CWM version on my phone right? Isn't there a easier way to delete CWM, can I flash TWRP over CWM and see if it will install these Gapps?

Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.

Morningstar said:
Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.
Click to expand...
Click to collapse
I appreciate your effort, thank you. The recovery issue is solved. I flashed Chainfires Root script and that installed the stock recovery. However, when I tried to install and older CWM version I got back in the recovery reboot cycle. But once I installed the latest CWM it booted in recovery. So I flashed Chainfires Root once again and had the stock recovery back. From there on I tried to install TWRP but got the recovery boot cycle again. My phone is now running android 5.0.2 and I think that's the problem.... :S I'll try again to flash Chainfires Root script to get the stock recovery back. From there on I will try to flash the link you gave to me with Odin and hope that will fix it. Do you have any ideas on what I'm doing wrong?

Your version of TWRP works so far. It reboots into RecoveryMode. Now I'll wipe and try to install Temaseks Cm 12 followed by Gapps! Thanks so far!
Okay, it's solved. Can't thank you enough for you help. Bless you!!

No problem. Glad you got it figured out!
[emoji106]

Phone only boots into TWRP

I decided today to try and root my phone and followed the steps on this tutorial: http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
I had unlocked my phone and installed the latest version of TWRP. Now I can only boot into TWRP and bootloader. My phone is not being picked up by my PC. I tried a factory reset and format of data on TWRP but my phone still only boots into TWRP.
Is my phone permanently bricked?
Any help will be greatly appreciated

I actually have just made some progress now. I've managed to get the phone connected to the computer by going into ADB sideload and installing the ADB drivers again on my computer.
Typing ADB devices in CMD now shows my device as connected.
Any advice on what I should do now?

What happens when you try to boot it normally? Is it stuck at the boot animation or does it go directly to the bootloader or recovery? Since you already had to wipe everything you could try flashing a factory image via fastboot.

theminikiller said:
What happens when you try to boot it normally? Is it stuck at the boot animation or does it go directly to the bootloader or recovery? Since you already had to wipe everything you could try flashing a factory image via fastboot.
Click to expand...
Click to collapse
Booting the phone normally loads it into TWRP. Booting the phone with the volume key pressed down loads the bootloader. I think I may have just wiped the OS present on the Phone.
I want my phone to be rooted running CyanogenMOD (phone is currently unrooted). Should I first install a stock rom then root by installing SuperSU and CyanogenMOD or can I just skip installing a stock rom and install SuperSU and CyanogenMOD?
Thanks for the help

You could try flashing a cyanogenmod zip from TWRP, and if that doesn't work I would suggest flashing I factory image.

theminikiller said:
You could try flashing a cyanogenmod zip from TWRP, and if that doesn't work I would suggest flashing I factory image.
Click to expand...
Click to collapse
But my phone is not rooted yet. Can I install SuperSU by copying onto my phone and installing it through TWRP?

umair_ said:
But my phone is not rooted yet. Can I install SuperSU by copying onto my phone and installing it through TWRP?
Click to expand...
Click to collapse
Yes, if it is a zip file. But I'm pretty sure installing cyanogenmod will automatically root it for you.

theminikiller said:
Yes, if it is a zip file. But I'm pretty sure installing cyanogenmod will automatically root it for you.
Click to expand...
Click to collapse
I installed SuperSU then CyanogenMOD and lastly GApps. It still only boots into TWRP and it doesn't look like there has been any files added to the phone's storage. Should I first flash a stock rom and then try to install CyanogenMOD?

umair_ said:
I installed SuperSU then CyanogenMOD and lastly GApps. It still only boots into TWRP and it doesn't look like there has been any files added to the phone's storage. Should I first flash a stock rom and then try to install CyanogenMOD?
Click to expand...
Click to collapse
Yes, try flashing a factory image. If it boots then you could try flashing cyanogenmod.
EDIT: here is a guide on how to flash a factory image: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

theminikiller said:
Yes, try flashing a factory image. If it boots then you could try flashing cyanogenmod.
EDIT: here is a guide on how to flash a factory image: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
I've managed to get it all working by first flashing the stock ROM and starting all over again.
Thanks for your help.

Is there a workaround to this other than flashing factory images...?

hwweiler said:
Is there a workaround to this other than flashing factory images...?
Click to expand...
Click to collapse
@hwweiler, No friend there is no other way.Please before do this as is one direction way take the pain to look on my post #180 on zaclmon's thread http://forum.xda-developers.com/nexus-4/orig-development/wip-aosp-7-0-nougat-t3448444/page18 and keep in mind that is impossible to return back on any nandroid backup u kept e.g to 5.1.1 or M furthermore its also impossible to flash any rom zip if u use this N (WIP) rom,the only way to have a workable phone again is to flash the stock rom from scratch.Exceperienced with and never again untill we have the appropriate solution..The twrp used and i still use on M is TWRP 3.0.2.0.The possibility to return on LP ffrom M and reverse still exists but not when u flash this rom.
Regards,Christos

Can't get into recovery :( would appreciate some help

Hello everyone,
yes i tried the search, but i really could not find anything matching my problem
I want so gift my S4 to a friend for christmas and wanna do a full wipe + new custom rom (currently sitting on Ressurection Remix Remix 5.5.5)
When i try to enter TWRP i get stuck at the teamwin screen
I've tried the following:
- flash older TWRP again via Odin
- install newest TWRP again via TWRP Manager App
- flashing Stock Recovery (could not even get into anything, bootloop)
Any suggetions how to solve this problem?
Sorry for any grammar/vocabulary mistakes. English is not my first language

Try flashing stock rom. That also includes the stock recovery. Then reflash twrp.

GDReaper said:
Try flashing stock rom. That also includes the stock recovery. Then reflash twrp.
Click to expand...
Click to collapse
Thanks :3
do i need to root again now?

der Blonde said:
Thanks :3
do i need to root again now?
Click to expand...
Click to collapse
Unless you want to stay on the stock rom, or want to backup some apps, then no. Rooting will not be necessary if you plan on changing to a custom rom again.

rooted my s4 again,
twrp is finally working
but i cant flash the rom
Error executing updater binary in zip
anyone has an idea?
i allready downloaded the rom again but the zip is not broken

Are you using the latest version of twrp?

Yes 2.8.7.0

der Blonde said:
Yes 2.8.7.0
Click to expand...
Click to collapse
That error is caused because the recovery thinks the rom is not compatible with your phone.
Make sure your phone is compatible with the rom.
Or try these steps I found online:
1. Advance Wipe > Wipe cache, data, system, dalvik partitions.
2. Select ZIP file of your ROM and flash it.
3. You will get E:Error executing updater binary in zip (Don’t panic!)
4. Go to Reboot menu > Select Reboot to recovery.
5. After rebooting in recovery, flash the ZIP file of the ROM again WITHOUT WIPING.
Then it should work, according to the site I found it on.

The execution error indicates that the phone may not be supported by the ROM you're trying to flash..

A6000 rom and Gapps problems

Hey folks I'm new here and I recently rooted my phone and flashed a z5 rom from the XDA rom thread. Link below
http://forum.xda-developers.com/len.../rom-xperia-z5-rom-lenovo-a6000-plus-t3393251
And flashed this nano pack of this gapps Link below
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
So it all went fine but now I'm incurring some problems.
Firstly I didn't notice that the Gapps is closed for updates I don't know if that affected the issue but the Google play is not working and some other Google stuff as well.
And I thought I'll flash new Gapps which are being kept up to date but my phone won't connect with the PC with the usb now so I don't know how do I flash the Gapps now.
I have re Rooted my phone using the Kingo app but it still won't reconnect.
So any help on these issues would be really helpful!
One last question that if I do find a way to flash the Gapps will I have to reflash the rom again?
Thanks

Parvarsingh said:
Hey folks I'm new here and I recently rooted my phone and flashed a z5 rom from the XDA rom thread. Link below
http://forum.xda-developers.com/len.../rom-xperia-z5-rom-lenovo-a6000-plus-t3393251
And flashed this nano pack of this gapps Link below
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
So it all went fine but now I'm incurring some problems.
Firstly I didn't notice that the Gapps is closed for updates I don't know if that affected the issue but the Google play is not working and some other Google stuff as well.
And I thought I'll flash new Gapps which are being kept up to date but my phone won't connect with the PC with the usb now so I don't know how do I flash the Gapps now.
I have re Rooted my phone using the Kingo app but it still won't reconnect.
So any help on these issues would be really helpful!
One last question that if I do find a way to flash the Gapps will I have to reflash the rom again?
Thanks
Click to expand...
Click to collapse
First dowload the gapps from opengapps.org. Go here choose ARM>>5.1.1>>nano/pico.
Then, boot into recovery, wipe system, data, cache, dalvik and then flash the ROM again and the gapps. All done...!!!

sasukay said:
First dowload the gapps from opengapps.org. Go here choose ARM>>5.1.1>>nano/pico.
Then, boot into recovery, wipe system, data, cache, dalvik and then flash the ROM again and the gapps. All done...!!!
Click to expand...
Click to collapse
That's the prob right. I cant reach the custom bootloader I don't know why. Do you think its because of the new rom ill have to use some different recovery? I am usin twrp right now and even I used it to flash this rom. Please help

Parvarsingh said:
That's the prob right. I cant reach the custom bootloader I don't know why. Do you think its because of the new rom ill have to use some different recovery? I am usin twrp right now and even I used it to flash this rom. Please help
Click to expand...
Click to collapse
""usin twrp right now"" -- can you boot into it..??
You press vol up + vol down along with power key and release the power key once the lenovo logo shows up, to boot into twrp

sasukay said:
""usin twrp right now"" -- can you boot into it..??
You press vol up + vol down along with power key and release the power key once the lenovo logo shows up, to boot into twrp
Click to expand...
Click to collapse
no cant boot into it.
I go into the fast boot mode enter recovery commands in the command window. Then try to boot into recovery but it doesn't go into recovery. The Lenovo screen stays there or it boots straight into the phone
This method worked before like I used this way to flash the rom but now its not working.
Any help?

Parvarsingh said:
no cant boot into it.
I go into the fast boot mode enter recovery commands in the command window. Then try to boot into recovery but it doesn't go into recovery. The Lenovo screen stays there or it boots straight into the phone
Click to expand...
Click to collapse
Brother, you have made it really confusing for me. Earlier you said that you can't boot into bootloader, but now you can boot into fastboot..!!
Also, your phone, instead going to recovery, boots directly to system. That means your phone is in working condition(Is it..?), which you didn't told me earlier.
So, if you can boot into system (normal boot). Download Rashr from play store (or from any other source) and flash this TWRP 3.0.2. (First extract this zip and then choose recovery from storage option in Rashr to flash).

Bricked but still have twrp

Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.

almost looks like it can't mount the system

IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.

I have no idea how it happened but I got my system mounted again that was my problem. I'm back.
thread can be closed

keeganjk said:
IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.
Click to expand...
Click to collapse
thanks for the reply mate

snipeez1987 said:
thanks for the reply mate
Click to expand...
Click to collapse
yw

snipeez1987 said:
Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.
Click to expand...
Click to collapse
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.

ipredatorv said:
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.
Click to expand...
Click to collapse
Awesome. I'll keep that in mind. I'm sure I'll mess it up again lol. Hopefully not though.