Related
Basicly I have A samsung galaxy s i9000 // 2.3.6 // XXJW4
And I have flashed clock work recovery so many times and every time I tap "reboot into recovery" it takes me to Android System Recovery (3e) not clockwork mod, please help me?
Meet too!!!
Cinemah said:
Basicly I have A samsung galaxy s i9000 // 2.3.6 // XXJW4
And I have flashed clock work recovery so many times and every time I tap "reboot into recovery" it takes me to Android System Recovery (3e) not clockwork mod, please help me?
Click to expand...
Click to collapse
Do
Code:
fastboot erase recovery
then reflash it.
Theonew said:
Do
Code:
fastboot erase recovery
then reflash it.
Click to expand...
Click to collapse
When you say reflash "it", what exactly do you mean by "it"?
I have CWM 5.0.2.7 provided by the Semaphore kernel. When I enter Recovery via either 3-button salute method or QuickBoot app, I get CWM 5.0.2.7: No problem.
BUT if I choose recover from Titanium Backup, I get the dreaded Samsung Stock recovery 3e. So apparently I have both recoveries on my device.
Which one will the Fastboot command erase?
Thanks!
cmd:
fastboot erase recovery
then go to Recovery Mode immediately after it
PlanetPron said:
cmd:
fastboot erase recovery
then go to Recovery Mode immediately after it
Click to expand...
Click to collapse
well this is not good because with fastboot erase recovery command you delete recovery partition from phone
so you have to reflash it before to go recovery
Code:
fastboot flash recovery recovery.img
now you can enter recovery directly
in fact if you have a corrupted recovery is not necessary to erase it just flash it again by fastboot flash
look here for a tutor how to use fastboot
Catalyst2012 said:
When you say reflash "it", what exactly do you mean by "it"?
I have CWM 5.0.2.7 provided by the Semaphore kernel. When I enter Recovery via either 3-button salute method or QuickBoot app, I get CWM 5.0.2.7: No problem.
BUT if I choose recover from Titanium Backup, I get the dreaded Samsung Stock recovery 3e. So apparently I have both recoveries on my device.
Which one will the Fastboot command erase?
Thanks!
Click to expand...
Click to collapse
By "it" I mean the recovery image. So do
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Theonew said:
By "it" I mean the recovery image. So do
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thank you for the clarification!
I don't have any recovery.img to flash. The only CWM image available directly from CWM site is very old, 2.5.x.x and not compatible with newer 5.0.2.7 backups.
I have three "recovery" files on my device. The Samsung recovery files are: \recovery, and \sbin\recovery-samsung; both are identical.
The Semaphore/CWM 5.0.2.7 file is: \sbin\recovery. I suspect that depending what method or app is used to enter recovery, one location is chosen or the other.
I am considering renaming the Samsung: \recovery to something like \recovery.bak, and then copying the Semaphore/CWM 5.0.2.7 recovery into its location. If it works, I will always enter the newer recovery. It if does not work, I could boot into download and revert. But not sure?
Any advice is welcome
You could try building your own.
Theonew said:
You could try building your own.
Click to expand...
Click to collapse
Thanks Theonew. The Recovery Builder attempt failed. Nearly 50% of the attempts on that website are also failed builds, so I don't feel so bad.
Thanks anyway.
App "Quick Boot"
And did you try (free) App "Quick Boot" for rooted devices? Does it boot to stock recovery or CWM recovery mode?
I'm having a problem flashing a custom recovery on my Nexus 7. I'm trying to install the TWRP recovery for the "flo" version and it doesn't seem to install. I mean, it says it does in fastboot mode but when I reboot to recovery it goes to the stock recovery instead (the green android with the red triangle) and just stays on that screen for minutes. What gives?
Brushstroke said:
I'm having a problem flashing a custom recovery on my Nexus 7. I'm trying to install the TWRP recovery for the "flo" version and it doesn't seem to install. I mean, it says it does in fastboot mode but when I reboot to recovery it goes to the stock recovery instead (the green android with the red triangle) and just stays on that screen for minutes. What gives?
Click to expand...
Click to collapse
You used
fastboot flash recovery twrp.img?
meekrawb said:
You used
fastboot flash recovery twrp.img?
Click to expand...
Click to collapse
Yep. Solved it though. Apparently in 4.4 they've made it so that the device will replace TWRP with the stock recovery immediately after rebooting if you don't boot into TWRP immediately after installing it using:
fastboot boot name-of-recovery.img
Then you have to change the name of a file while in TWRP. In TWRP go to Mount and select System. Then go back to the main screen and press Advanced > File Manager. Browse to /system and select a file named recovery-from-boot.p and rename it to recovery-from-boot.bak. And you should be able to go into TWRP like normal.
Brushstroke said:
Yep. Solved it though. Apparently in 4.4 they've made it so that the device will replace TWRP with the stock recovery immediately after rebooting if you don't boot into TWRP immediately after installing it using:
fastboot boot name-of-recovery.img
Then you have to change the name of a file while in TWRP. In TWRP go to Mount and select System. Then go back to the main screen and press Advanced > File Manager. Browse to /system and select a file named recovery-from-boot.p and rename it to recovery-from-boot.bak. And you should be able to go into TWRP like normal.
Click to expand...
Click to collapse
Could you please describe this procedure detailed?
Where can I find the "Mount" option?
Must my device being rooted?
Some tricks for you guys if you are stuck like I was :
-if you can't boot to custom recovery, try naming your custom recovery img "recovery.img" instead of "twrp.img" when you flash it.
so --> "fastboot flash recovery recovery.img" will be the command you execute.
-if you can't flash recovery at all, try executing the command without the phone plugged, then plug the device when you see the prompt "<waiting for any device>"
Hope this helps !
Hi guys,
I've just updated to newest OOS firmware wich is 5.1.2 and I'm facing a weird problem.
Every time I flash codeworks TWRP and reboot to system, the next time i try to boot to recovery it boots to the original recovery.
It's like when I flash TWRP it doesn't remain persistent. When i flash it through fastboot and straightly boot from fastboot to recoverry I succeed to get in TWRP but as soon as I reboot to system and try to boot to recovery I reach the original OnePlus recovery.
Is anyone facing the same problem ?
And also do you have any idea about what i could do to solve this problem ?
Thanks in advance for your answers !
If you don't have root or custom kernel its normal, plus you should use blu spark's twrp, its newer and more reliable.
Adnan008 said:
If you don't have root or custom kernel its normal, plus you should use blu spark's twrp, its newer and more reliable.
Click to expand...
Click to collapse
Indeed, I just needed to flash magisk to get it persistent. I'll try blu spark's one as you suggested.
Thank you very much for your answer !
Cheers !
Nothing to do with recoveries or kernel. After you do the fastboot flash recovery TWRP in fastboot, do this: "fastboot boot TWRP". I believe that's the right command. Basically after you flash it, manually boot to recovery through fastboot one time. After that it'll work from inside the phone or with the button combination with the phone off.
Jesus people are lazy these days.
First off there are official twrp versions for a reason!
Download the latest version: https://dl.twrp.me/dumpling/
Reboot into flash boot with the following command from your rom: adb reboot bootloader
With phone in fastboot mode: fastboot flash recovery 'twrp.img'
(You don't need to type out the entire file path you can just drag the file into the terminal and it'll insert the file location)
The reason you're not getting back into that recovery is because you're not booting into the recovery before you reboot into your ROM.
There is an option to boot straight into the recovery from the fastboot mode
pinnekeshaar said:
Jesus people are lazy these days.
First off there are official twrp versions for a reason!
Download the latest version: https://dl.twrp.me/dumpling/
Reboot into flash boot with the following command from your rom: adb reboot bootloader
With phone in fastboot mode: fastboot flash recovery 'twrp.img'
(You don't need to type out the entire file path you can just drag the file into the terminal and it'll insert the file location)
The reason you're not getting back into that recovery is because you're not booting into the recovery before you reboot into your ROM.
There is an option to boot straight into the recovery from the fastboot mode
Click to expand...
Click to collapse
Actually not that lazy because I used to do what you mentionned.
The thing is that a flash of Magik is needed to patch twrp. That's the step I forgot in the procedure and explained here.
So before being unpleasant, please know what you're talking about...
Cheers !
I installed Linux by a mistake into my Nokia 3.2 which led me here, I am stuck in fast boot mode I tried multiple solutions like scratching the edl trigger, going to recovery mode, and restarting the bootloader. it only vibrates and reopens the fastboot menu, I cannot install, or perhaps I don't know how to install the default OS, IMG, or whatever you call it I am really new to this kinda stuff, sorry, and I appreciate your help.
I had the same issue after trying to install an incompatible custom ROM the way I fixed it is by:
1- downloading the stock ROM
2- extract it
3- while the phone is in fastboot flash all .img files like this:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
etc...
after flashing all .img files type
Code:
fastboot reboot
and that's it, it might tell you your phone isn't trusted this will go after a system update.
MRza3ter said:
I had the same issue after trying to install an incompatible custom ROM the way I fixed it is by:
1- downloading the stock ROM
2- extract it
3- while the phone is in fastboot flash all .img files like this:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
etc...
after flashing all .img files type
Code:
fastboot reboot
and that's it, it might tell you your phone isn't trusted this will go after a system update.
Click to expand...
Click to collapse
to download the stock ROM just search Nokia 3.2 stock rom
So I installed a A13 AOSP rom (Evolution x) via orangefox and when I rebooted to recovery orangfox was gone and now I'm on AOSP recovery. I tried to "fastboot boot" TWRP but the phone restarts on black screen for several seconds then restarts again to system. and when I enter fastboot thro AOSP recovery and try to boot TWRP it just fails (says unrecognized command boot). how can I flash custom recovery? i was thinking of trying sideload but with fastboot not working properly, I dont want guessing and rather ask someone with more knowledge with AOSP recovery and what could be causing fastboot not working properly
PS/ AOSP recovery is not detecting otg, and when choosing apply updates from internal storage it says it cant mount /data
Aserar said:
So I installed a A13 AOSP rom (Evolution x) via orangefox and when I rebooted to recovery orangfox was gone and now I'm on AOSP recovery. I tried to "fastboot boot" TWRP but the phone restarts on black screen for several seconds then restarts again to system. and when I enter fastboot thro AOSP recovery and try to boot TWRP it just fails (says unrecognized command boot). how can I flash custom recovery? i was thinking of trying sideload but with fastboot not working properly, I dont want guessing and rather ask someone with more knowledge with AOSP recovery and what could be causing fastboot not working properly
PS/ AOSP recovery is not detecting otg, and when choosing apply updates from internal storage it says it cant mount /data
Click to expand...
Click to collapse
What is the code name of your device?
NOSS8 said:
What is the code name of your device?
Click to expand...
Click to collapse
Its alioth poco f3
Aserar said:
Its alioth poco f3
Click to expand...
Click to collapse
Seems that in official no TWRP A13
https://androidfilehost.com/?w=files&flid=322193
Here boot version A12(more recent).
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
https://dl.akr-developers.com/?dir=skkk/TWRP/A12/v5.6_A12
https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4272625/
Aserar said:
So I installed a A13 AOSP rom (Evolution x) via orangefox and when I rebooted to recovery orangfox was gone and now I'm on AOSP recovery. I tried to "fastboot boot" TWRP but the phone restarts on black screen for several seconds then restarts again to system. and when I enter fastboot thro AOSP recovery and try to boot TWRP it just fails (says unrecognized command boot). how can I flash custom recovery? i was thinking of trying sideload but with fastboot not working properly, I dont want guessing and rather ask someone with more knowledge with AOSP recovery and what could be causing fastboot not working properly
PS/ AOSP recovery is not detecting otg, and when choosing apply updates from internal storage it says it cant mount /data
Click to expand...
Click to collapse
It is because flashing rom also flash the recovery packed along with the rom, and it will replace your old recovery. To prevent it you need to also tick on the reflash ofox option when you flash a rom, which is too late in your case.
So, if you want to reflash ofox recovery, download and extract the zip file, locate the recovery.img in the extracted folder, reboot to bootloader and issue this command:
Code:
fastboot boot /path/to/recovery.img
then reboot to recovery with the command:
Code:
fastboot reboot recovery
and your device will temporarily boot into ofox recovery
The last step is to flash the recovery to ramdisk to make it permanently, you can find this option in ofox settings.
NOSS8 said:
Seems that in official no TWRP A13
https://androidfilehost.com/?w=files&flid=322193
Here boot version A12(more recent).
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
https://dl.akr-developers.com/?dir=skkk/TWRP/A12/v5.6_A12
https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4272625/
Click to expand...
Click to collapse
This is what I did befor posting but but TWRP wouldnt boot through fastboot. it just gives me blackscreen for a few seconds then it boots to system. but the problem was solved with ofx. thank you for your help
disconmair said:
It is because flashing rom also flash the recovery packed along with the rom, and it will replace your old recovery. To prevent it you need to also tick on the reflash ofox option when you flash a rom, which is too late in your case.
So, if you want to reflash ofox recovery, download and extract the zip file, locate the recovery.img in the extracted folder, reboot to bootloader and issue this command:
Code:
fastboot boot /path/to/recovery.img
then reboot to recovery with the command:
Code:
fastboot reboot recovery
and your device will temporarily boot into ofox recovery
The last step is to flash the recovery to ramdisk to make it permanently, you can find this option in ofox settings.
Click to expand...
Click to collapse
Thank you mf this worked! Booting twrp through fastbood just gave me black screen so I didnt think that booting Ofox would be any different but it actually booted Ofox recovery and I flashed it no problem. If anyone's going to attempt this make sure to backup your data before cause you'll need to format data