Hello,
I am saerching for a recovery that implements 'sideload' flashing option since my CWM won't mount the sdcard partition, and it is not letting me flashing zip from other places,
I have done some research but almost all links that provides recovery with sideload option are broken (TWRP, CWM 6 Touch ...),
Thanks in advance
Related
Hi! Im a noob with a couple of questions hope anyone can help me...
I was recently at 4.2.1 on my nexus 7 had twrp installed, and accidentally updated to stock 4.2.2 my cstom recovery wash flashed by a stock one and forced me to install another via fastboot, but this time i installed cwm then i decided to go back to twrp coZ i dont personally like cwm,. So here is my problem i used rom toolbox to reboot into recovery and it said that i have a cwm installed but when i rebooted i was on twrp, its confusing did i installed both? And made me decide to use rom manager it said that i have twrp and cwm already installed how can i uninstall cmw...
Hope u could help me.. Anyone?
ROM manager plays a clever trick where it temporarily replaces the recovery, even though it is not flashed into the recovery partition.
If you start the recovery from the bootloader, you'll see TWRP; and if you boot into recovery from ROM manager, you will (eventually) see the CWM recovery (you may see some graphics produced by TWRP first, though).
If you have a way (separate from ROM Manager) to boot from the OS into the recovery, you will get TWRP.
bftb0 said:
ROM manager plays a clever trick where it temporarily replaces the recovery, even though it is not flashed into the recovery partition.
If you start the recovery from the bootloader, you'll see TWRP; and if you boot into recovery from ROM manager, you will (eventually) see the CWM recovery (you may see some graphics produced by TWRP first, though).
If you have a way (separate from ROM Manager) to boot from the OS into the recovery, you will get TWRP.
Click to expand...
Click to collapse
Hi thnx for the help, actualy i was able to boot into twrp already and i belive i flashed it completely, my only concern is did i overwrite the cwm in my rec partition? Or it is still there?
Sent from my Nexus 7 using xda app-developers app
There can be only one bootable image in the recovery partition at a time.
If you boot from the bootloader into recovery, and you see TWRP... then that is what is flashed there.
If you want to see what I am talking about, go into ROM manager and select the menu item that causes a boot into recovery. What you will see (after a little bit) is the CWM U/I.
What is going on is that ROM manager boots whatever recovery is actually flashed in the recovery partition, and then immediately replaces /sbin/recovery with it's own version (CWM) and then kills & restarts that same program.
So - what you *see* is the CWM version of /shin/recovery - running on top of the kernel & ramdisk were provisioned by the whatever recovery was actually flashed to the recovery partition.
If you want to actually flash CWM to the recovery partition, ROM Manager has a menu item for that. I'm not sure what the exact wording is.
If you are confused by this, just read the first two sentences in this post.
While starting to upgrade from CM10 to CM10.2/10.3 on MB526, I flashed TWRP zip file downloaded from Team-win website.
steps:
1) downloaded recovery and copied to SDcard.
2) reboot into custom recovery (CWM)
3) Flash zip of TWRP recovery
Since than, I am getting black screen after clicking on custom recovery from Bootmenu.
Device is working fine,
but with no custom recovery, my hands are tied...
can't restore backup, can't flash rom or do anything..
tried installing zip from stock recovery.. Installation aborted appears
Is there any solution to get recovery working without starting from scratch (flashing SPF and 2ndinit, and so on.... )
warewolf4586 said:
While starting to upgrade from CM10 to CM10.2/10.3 on MB526, I flashed TWRP zip file downloaded from Team-win website.
steps:
1) downloaded recovery and copied to SDcard.
2) reboot into custom recovery (CWM)
3) Flash zip of TWRP recovery
Since than, I am getting black screen after clicking on custom recovery from Bootmenu.
Device is working fine,
but with no custom recovery, my hands are tied...
can't restore backup, can't flash rom or do anything..
tried installing zip from stock recovery.. Installation aborted appears
Is there any solution to get recovery working without starting from scratch (flashing SPF and 2ndinit, and so on.... )
Click to expand...
Click to collapse
I think stock recovery can't help you now, you should start from scratch...
It isn't so hard, just takes time...
From CM10 to CM10.2, you don't need to change recovery, just install it. From CM10.2 to CM11 you should install update-recovery.zip, reboot, install CM11 + GApps.
Hope it helps... :highfive:
warewolf4586 said:
While starting to upgrade from CM10 to CM10.2/10.3 on MB526, I flashed TWRP zip file downloaded from Team-win website.
steps:
1) downloaded recovery and copied to SDcard.
2) reboot into custom recovery (CWM)
3) Flash zip of TWRP recovery
Since than, I am getting black screen after clicking on custom recovery from Bootmenu.
Device is working fine,
but with no custom recovery, my hands are tied...
can't restore backup, can't flash rom or do anything..
tried installing zip from stock recovery.. Installation aborted appears
Is there any solution to get recovery working without starting from scratch (flashing SPF and 2ndinit, and so on.... )
Click to expand...
Click to collapse
Start from scrach >.>
Hi i make the mistake of erasing all partitions without backup in philz touch recovery on my lg d803 and now im i can just go in recovery..i flashed twrp 2.6.3.2 and now the phone boot only in twrp..no download mode no rom i flashed a lot of roms but always boot in twrp ..help plz i have no idea what to do ..i can do adb commands...tanxs in advance.
demon66678 said:
Hi i make the mistake of erasing all partitions without backup in philz touch recovery on my lg d803 and now im i can just go in recovery..i flashed twrp 2.6.3.2 and now the phone boot only in twrp..no download mode no rom i flashed a lot of roms but always boot in twrp ..help plz i have no idea what to do ..i can do adb commands...tanxs in advance.
Click to expand...
Click to collapse
If you have ADB access, you are in a good spot.
You'll have to ADB sidelaod a ROM, and flash it. shouldn't be hard to find info on.
Good luck.
congratulations for not saying your bricked.
you probably get an error when flashing right ?!
you need a newer version of twrp... get a flashable zip and update itself in twrp. then you will be able to flash roms.
Yep. darkobas is correct.
I missed your TWRP version. find 2.6.3.3 push it (I mistakenly said sideload above) and a ROM to your 'SDcard', then flash TWRP, restart to recovery, and flash ROM (and any other required packages (Gapps, system patch, etc).
adb push path/filename /sdcard/filename
re
CxanDroid said:
Yep. darkobas is correct.
I missed your TWRP version. find 2.6.3.3 push it (I mistakenly said sideload above) and a ROM to your 'SDcard', then flash TWRP, restart to recovery, and flash ROM (and any other required packages (Gapps, system patch, etc).
adb push path/filename /sdcard/filename
Click to expand...
Click to collapse
sorry but i try it and no matter what the phone is always restarting in twrp no download mode no system no nothing everytime rebooting in recovery twrp 2.6.3.3
So.... Twrp is fine... Flash a rom now
Sent from my LG-D802 using Tapatalk
Hi All,
So I have CM11 installed on my Note 3 with CWM 6.0.4.6 as my recovery. I want to now flash the TWRP recovery and replace CWM.
1) I download the official hlte twrp zip from twrp website
2) Go into cwm recovery and flash the twrp zip
3) But when I reboot, I see that I am still stuck with CWM and the TWRP recovery hasn't been installed
Can someone tell me if there is any step I am missing or what am I doing wrong? I just can't seem to get rid of CWM.
Is it because of CM11? I don't think so honestly (but I maybe wrong).
Thanks for any help that you can give
Bumping this question to top
Please help
I flashed twrp 2.8.3 last time but when reboot recovery i'm still at 2.8.2. Then flashed latest 2.8.4 it's updated as it should be. Maybe corrupted zip unless you downloaded a few times then i'm not sure.
Good evening everyone.
I write because I have a problem with the installation of the CM on my meizu MX4.
I ran perfectly the procedure of unlocking the bootloader, and once unlocked, I flashed the recovery Philz. Later I tried to flash the CM with adb, but in at end it always says "Installation Aborted". I tried with the patched recovery and with cofface, but I just can not flash it.
I then tried to do a wipe cache but no with any recovery that I flashed always appears to me:
"E: Can not mount / cache / recovery / command
E: Can not mount / cache / recovery / log
E: Can not open / cache / recovery / log
E: Can not mount / cache / recovery / last_log
E: Can not open / cache / recovery / last_log "
I read here http://forum.xda-developers.com/meizu-mx/general/tutorial-bootloader-unlocking-mx4-m1-t3201715 that I could flash the patched rom deleting the file uboot.img and preloader.bin but I can not find anywhere the second file, and also I'm afraid to brick the phone ... someone has already done it?
Tell me that at least in the future I will be able to install the CM. Loved and hated Flyme.
Sorry for the English and thanks in advance for your reply.
Why you don't install CM from the recovery?
Sent from my D6603 using Tapatalk
I has this problem also when try to wipe cache. I fix cache mount with "wipe for new rom" option in wipe menu on philz recovery.
After that install cyanogen .zip with recovery.
Now i'm back to flyme but i flash patched flyme4.5.6i-twrp.zip found on 4pda forum, with twrp recovery for mx4.
Here is link for tutorial *4pda.ru/forum/index.php?showtopic=689760&st=780#entry43612111*
My MX4 is now on Flyme international version (original was A firmware) and i still have unlocked bootloader and custom recovery.
Everything works fine without any bug.
artlov I installed the recovery and then I did:
1) install zip
2) install zip from sideload
3) MX4 connect to pc
4) open CDM and write "adb devices" enter
5) "adb sideload cm12 ect * enter *
6) sull'mx4 appeared the word "installation aborted" after loading on pc
Now i have flyme 4.2.8.2A with philz recovery.
mmdag82 i don't find on philz the option "wipe for new rom"
"Clean to Install a New Rom" is exactly name of option under Wipe menu
And then i can try to flash CM? By terminal or with file zip on mx4's memory?
Thank you for your answers!
With zip file on mx4 memory
did you tried factory reset because you must do that befor adb sideload and i woildn't do Clean to Install a New Rom because it will delete everything about current system
Yeeah! CM installed! Thanks a lot guys!
MX4 not read sim card with CM...
federicolucchesi said:
artlov I installed the recovery and then I did:
1) install zip
2) install zip from sideload
3) MX4 connect to pc
4) open CDM and write "adb devices" enter
5) "adb sideload cm12 ect * enter *
6) sull'mx4 appeared the word "installation aborted" after loading on pc
Now i have flyme 4.2.8.2A with philz recovery.
mmdag82 i don't find on philz the option "wipe for new rom"
Click to expand...
Click to collapse
There is a solution. Try to reflash the patched recovery.
Now reflash 4.2.1.2 with clean.
Reboot, and reroot, reinstall flashify and terminal.
Do again the tuto step by step.
Try and tell me
Edit : Sorry, i didn't saw you have done ^^
I've done! Not reads SIM but i think is problem of card, cause i tried other SIM that weren't chopped from old SIM card and them run perfectly!
Hey,
hope somebody can help me.
I wanted to install flymeos on my arale until the cm-version is usable for me.
I am only able to install version 4.0.4 i or a but i cannot upgrade nor directly flash a version later than that...
I tried several recoveries (philz, cofface, twrp) and several versions (4.2.8.2i/a, 4.5.6i). Any ideas?
-----------------
EDIT: Recovery logs always tell me that there is no space on /custom left. Do i have to reformat my arale with a android scatter? I installed 4.0.4 and ran fastboot -w. Thought this would be sufficient. /custom is only 4.8M big...