1. Will I be able to boot into recovery after wiping /boot ?
2. Will I be able to boot into fastboot mode wfter wiping /boot ?
3. If I flash a incompatable rom that contains the incompatable boot.img will I be able to boot into recovery ?
I'm not trying to do any of these, just wondering.
janekmuric said:
1. Will I be able to boot into recovery after wiping /boot ?
2. Will I be able to boot into fastboot mode wfter wiping /boot ?
3. If I flash a incompatable rom that contains the incompatable boot.img will I be able to boot into recovery ?
I'm not trying to do any of these, just wondering.
Click to expand...
Click to collapse
In most cases: Yes, yes and yes.
To be more precise:
1. "boot" partition stores the "kernel" which is needed to boot up android itself. ***
2. "fastboot" or for Samsung devices "download" mode is implemented into the "bootloader" and will mostly not be affected by changing / deleting the kernel.
3. Most devices have seperate partitions for kernel ("boot") and recovery ("recovery") and in that case channging / corrupting the kernel will not affect your (custom) recovery. BUT on some devices e.g. my Samsung Galaxy Ace II (GT-I8160) kernel + recovery are both stored on the "boot" partition, which means there is no dedicated partition for the recovery and if I delete or install a incompatible kernel, I'm not able to enter the recovery anymore.
I have boot and recovery partitions seperated. Also isn't the kernel required so the software (in this case the recovery) would be able to "comunicate" with hardware (screen, buttons, etc.)?
Related
All, I'm trying to port clockworkmod recovery to the T-Mobile MyTouch Q (lgec800). I have completed all steps and am at the point where I need to test it to correctly modify recovery.fstab and BoardConfig.mk. I can't use flash_image through terminal on the phone, my understanding is because the partitions are emmc. I have successfully used dd command to flash my first modded recovery, however the phone won't boot into the recovery. Upon telling it with adb command or an app, it boots into main logo, goes black, then back to main logo and hangs. Battery pull and boot brings it back to normal. Also, I don't believe my phone has hboot or fastboot, as no amount of commands in terminal on phone or from computer get it to boot into those. Was wondering if someone can answer some questions for me.
1.) I am correct that I should be using original boot.img for the port and not recovery.img? I haven't found documentation specifying and why.
2.) I am correct in flashing the modded recovery(originally the stock boot.img) into the recovery partition?
3.) Is the recovery.zip output only flashable w/ hboot?
I tried making the cwm recovery port with the original recovery.img and flashing that to the recovery partition, same thing happens.
Anyone have any ideas?
Sent from my LG-C800 using XDA App
Is there maybe a way to read/write to the recovery partition from an external system, such as through ADB? Is the CWM port small enough to fit in the recovery partition? If there were, then forcing a CWM port for the C800 ought to work...
Hi
Tried to flash my HTC with cm-12.1-20151018-UNOFFICIAL-pyramid - now stuck in recovery mode
Had a backup of previous system, tried restore but it won't boot into original system, just ends up in recovery mode.
Have rooted phone, installed CWR, and copied the cm-12.1-20151018-UNOFFICIAL-pyramid.zip and the gapps-lp-20141109-signed.zip to the SD card. when trying to install it fails - seems it has some mount problems ?
Please help
OddE
oefiske said:
Hi
Tried to flash my HTC with cm-12.1-20151018-UNOFFICIAL-pyramid - now stuck in recovery mode
Had a backup of previous system, tried restore but it won't boot into original system, just ends up in recovery mode.
Have rooted phone, installed CWR, and copied the cm-12.1-20151018-UNOFFICIAL-pyramid.zip and the gapps-lp-20141109-signed.zip to the SD card. when trying to install it fails - seems it has some mount problems ?
Please help
OddE
Click to expand...
Click to collapse
change your recovery to 4ext
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot
the command is fastboot flash recovery recovery.img
then from 4ext
format all partitions except sdcard
enable smartflash (only if you are on S-ON)
flash the rom
done
Screen flaw as well
rzr86 said:
change your recovery to 4ext
extract the recovery.img and flash it via fastboot
the command is fastboot flash recovery recovery.img
then from 4ext
format all partitions except sdcard
enable smartflash (only if you are on S-ON)
flash the rom
done
Click to expand...
Click to collapse
Thanks a lot !
Managed to flash the 4ext, and it's running well. But I ran into another problem that makes me wonder if I should discard the Sensation totally. I started this because I wanted to give it to a friend, I currently have a S4 active.
When I changed from HTC to Samsung it was mostly because I tought it was too slow, but in the end there was also a issue with the upper right corner of screen starting to be unresponsive. Seems the flaw have gotten bigger, and now it seems that a larger portion of the screen failing - I can't even manage to press install from SD card in 4ext - lol
**** happens !!
OddE
After flashing TWRP 3.1.0.0 from USB-OTG to my XT1039 the phone boots to TWRP and not into system.
The "funny" thing is that if i keep my USB-OTG stick connected after hitting reboot the system boots. It gets even funnier. If i disconnect the stick the phones goes blank (or powers off) immediately. I checked the stick, there are no partitions, besides the storage partition i created.
Does anyone have an idea what i did wrong to achieve this strange behaviour?
EDIT:
Looks like i flashed recovery.img to boot partition. After manually chosing to install boot.img to recovery partition the system boots, but setup assistant crashes. Seems i'm going to have a long night...
Looks like a complete reinstall is necessary, and if you have to use a flashable ZIP instead of just the recovery image to install the recovery, then do that. In the meantime, try installing the boot.img and recovery.img to the correct partitions.
Got it to work, but only after flashing boot.img to recovery partition and wipe all partitions. When i flash to boot.img, reboot takes me to recovery. When i flash to recovery, system boots, but to get to recovery again i have to flash recovery.img to boot via adb.
All in all very strange and i have no idea what i can do in order to make boot and recovery work side by side.
Hello XDA learnt members, Is it possible to boot a secondary ROM from recovery partition? I am trying to flash a full ROM image in recovery partition (Ofcourse I resized my recovery partition to fit the ROM first) but it doesn't boot. The idea is to access secondary ROM via key combination (power+volume up) used for recovery. Instead of running recovery image such as TWRP etc I want full Android OS to load. Here is what I have already done and need help and insights from you guys.
1. Repartition the mmc of phone with increased recovery partition size - I have almost 5GB now for recovery partition (I am using Redmi 5)
2. Flash stock ROM normally to /system partition and TWRP to recovery partition
3. Everything works at this stage. TWRP boots up on pressing power+volume up, stock ROM boots up normally too
What I am trying to do is:
Flash stock ROM system into recovery partition - hoping volume up + power key will boot my secondary OS
This doesn't work. While I understand that recovery is just another OS with its own minimal kernel and tools and so bootloader should not have any problem if I flash system into recovery.
I am new to Android internals and still learning. Any help will be great.
Thanks
Hello, I was wondering could an Android device still boot if I were to lets say try and flash a custom recovery and it not go so well or is something during booting of the device dependent upon the recovery being there and being functional?
Of course you can. The recovery partition can be considered as an alternative boot partition that lets you boot the device into a recovery console for performing advanced recovery and maintenance operations on it.