Related
I tried flashing Ken's GB ROM today and for some reason it would just load the AT&T screen then restart. I flashed the zips through CWM, what might I have done wrong?
which recovery did you use? did you wipe? and try to re-download it. you may have gotten a damaged file. it happens. this is why we have MD5 sums
I used rom manager, I wiped after (maybe I should have done it before?), and what's an mds sum?
Sent from my MB860 using XDA App
I just used the new official CWM for Atrix (as opposed to tenfar's custom build) to flash navalynt's CherryBlur1.2 over my old 2.3.4HKTW ROM, which I had modified with navalynt's 1.8 rollup package.
I'm also bootlooping on the Atrix logo (instead of the Motorola logo; I think it was part of the theme included in the update package, and it'd be nice to be able to change it back to the stock somehow). I'd take your advice and try redownloading the .zip of the ROM, but, uh, I don't really know how to access my phone's internal storage without being able to boot it up.
Should I manually try flashing the .img files via fastboot interface, or what? I really picked a bad time to screw with my phone, because I'm expecting a call about a new job...
Obscene Topiary said:
I just used the new official CWM for Atrix (as opposed to tenfar's custom build) to flash navalynt's CherryBlur1.2 over my old 2.3.4HKTW ROM, which I had modified with navalynt's 1.8 rollup package.
I'm also bootlooping on the Atrix logo (instead of the Motorola logo; I think it was part of the theme included in the update package, and it'd be nice to be able to change it back to the stock somehow). I'd take your advice and try redownloading the .zip of the ROM, but, uh, I don't really know how to access my phone's internal storage without being able to boot it up.
Should I manually try flashing the .img files via fastboot interface, or what? I really picked a bad time to screw with my phone, because I'm expecting a call about a new job...
Click to expand...
Click to collapse
Yea, if you didn't make a nandroid backup, you need to flash the image files of your previous rom
Sent from my MB860 using XDA App
Well, this is very strange. I restored the backup I had made, although I got an error from CWM about being unable to wipe /data... nonetheless it booted properly. I loaded a new download of the .zip, flashed it in CWM with no apparent errors, and now instead of bootlooping on the custom Atrix animation, it's bootlooping on the Motorola "dual core technology" screen (not the actual bootloader screen with "unlocked" in the corner, but after that). I'm really confounded by all of this.
Forum is full of similar threads.
Rom Manager doesn't successfully wipe. You need to run a fastboot -w or reinstall tenfar's CWM and wipe, then reinstall your ROM. This will resolve your bootloop.
EDIT: You're seeing the same problem...bootlooping. The ROM's just have different boot animations: Atrix logo vs. Default Moto.
quicklyspent said:
Forum is full of similar threads.
Rom Manager doesn't successfully wipe. You need to run a fastboot -w or reinstall tenfar's CWM and wipe, then reinstall your ROM. This will resolve your bootloop.
EDIT: You're seeing the same problem...bootlooping. The ROM's just have different boot animations: Atrix logo vs. Default Moto.
Click to expand...
Click to collapse
Yes, I just used fastboot to reflash the stock HKTW images, and of course it's fine now. I'd just like to be able to get CherryBlur to work properly.
Edit: Got it. The .zip installed properly using tenfar's CWM. Ironically enough, tenfar's custom implementation of CWM works better than ROM Manager's, although obnoxiously it's unable to mount the phone's internal SD storage, so an external SD card must be used for installing .zips. ROM Manager's CWM can mount the internal storage, but has other issues. Lol, so convoluted.
Obscene Topiary said:
Yes, I just used fastboot to reflash the stock HKTW images, and of course it's fine now. I'd just like to be able to get CherryBlur to work properly.
Edit: Got it. The .zip installed properly using tenfar's CWM. Ironically enough, tenfar's custom implementation of CWM works better than ROM Manager's, although obnoxiously it's unable to mount the phone's internal SD storage, so an external SD card must be used for installing .zips. ROM Manager's CWM can mount the internal storage, but has other issues. Lol, so convoluted.
Click to expand...
Click to collapse
It's just a matter of time before rom managers cwm works properly
Sent from my MB860 using XDA App
For those of us using CM7 and other MTD roms, it's common knowledge that three-button recovery is useless to us after that first install from CWM4fixed. Try to use it again and you get the obvious mounting errors since it's hard-wired to boot to that BML recovery partition. Yep, of course you can only use the reboot menu or ADB to boot to the new MTD-based recovery partition that was created during that first CM7 install if you want to do anything.
I had a bootloop between CM7 nightlies tonight that has me questioning that logic, because, just for kicks before the inevitable Odin session, I interrupted the boot loop with three-button and (to my increasing disbelief) from BML recovery successfully reinstalled and booted CM7, rebooted to MTD recovery, and did a full nandroid restore. No Odin required. Unless I'm missing something though, this actually makes perfect sense.
When we use CWM4fixed to install CM7 over a BML rom, the CM7 install runs within that recovery and installs the new MTD recovery to a separate partition. This is why we're left with 2 different recoveries afterwards. But here's the catch: sure, the BML recovery can't interact with our new MTD file system, but the SD card holding our zips is still FAT32 and should thus remain readable by either recovery. Assuming I understand all of this correctly, what does this mean to us?
Simple: say you get a boot loop but there isn't a desktop with Odin or ADB handy. As long as you have a working SD card with an uncorrupted CM7 install zip and can access CWM4fixed via three-button, you should be able to get CM7 back up and running rather painlessly.
So here's my question: Am I correct? I've done it myself on my Fascinate, but that could have been a fluke and I'm mistakenly applying logic here that simply doesn't belong. It just seems to make sense though in retrospect. If this does in fact hold true, we've been avoiding a potentially useful and time-saving fix this whole time. If not, then this whole thing just makes me look stupid.
Jazz848 said:
For those of us using CM7 and other MTD roms, it's common knowledge that three-button recovery is useless to us after that first install from CWM4fixed. Try to use it again and you get the obvious mounting errors since it's hard-wired to boot to that BML recovery partition. Yep, of course you can only use the reboot menu or ADB to boot to the new MTD-based recovery partition that was created during that first CM7 install if you want to do anything.
I had a bootloop between CM7 nightlies tonight that has me questioning that logic, because, just for kicks before the inevitable Odin session, I interrupted the boot loop with three-button and (to my increasing disbelief) from BML recovery successfully reinstalled and booted CM7, rebooted to MTD recovery, and did a full nandroid restore. No Odin required. Unless I'm missing something though, this actually makes perfect sense.
When we use CWM4fixed to install CM7 over a BML rom, the CM7 install runs within that recovery and installs the new MTD recovery to a separate partition. This is why we're left with 2 different recoveries afterwards. But here's the catch: sure, the BML recovery can't interact with our new MTD file system, but the SD card holding our zips is still FAT32 and should thus remain readable by either recovery. Assuming I understand all of this correctly, what does this mean to us?
Simple: say you get a boot loop but there isn't a desktop with Odin or ADB handy. As long as you have a working SD card with an uncorrupted CM7 install zip and can access CWM4fixed via three-button, you should be able to get CM7 back up and running rather painlessly.
So here's my question: Am I correct? I've done it myself on my Fascinate, but that could have been a fluke and I'm mistakenly applying logic here that simply doesn't belong. It just seems to make sense though in retrospect. If this does in fact hold true, we've been avoiding a potentially useful and time-saving fix this whole time. If not, then this whole thing just makes me look stupid.
Click to expand...
Click to collapse
Whatever works for you man, but you know the saying "better to be safe than odining"
Sent from my SCH-I500 using XDA App
Hello all,
I've looked on the Forum but can't seem to find the answer to this. In fact, I only found a comment about this issue on another forum and there were no solutions. Here's the problem:
I'm running a rooted T-Mobile Vibrant with Froyo 2.2. I don't have any lagfix or additional kernels, I have ROM Manager and Titanium Backup. I'm trying to flash Bionix Next Gen V2.
The first time I did it, I got the failed verification error, so used the batch file on this forum to fix the 3e recovery installer, did that, and the result is the same.
So, here's where I am:
-I go into rom manager, do the flash clockworkmod recovery, I'm on 2.5.1.2
-I have the update.zip and bionix.zip both on my sd card.
-I go to Install Rom from SD Card, choose Bionix, check backup existing rom and wipe data and cache.
-I click ok, it reboots it, gets me into recovery.
-THIS is where I have trouble. There is no option to "Install Zip from SD Card", only to "Reinstall Package". If I do that, it reboots the phone to my regular Froyo.
I can't seem to understand why the option to install Zip from SD Card isn't showing up even though it did the very first time I tried flashing (when I got the verification error).
Any help would be greatly appreciated. I feel like I'm so close that it's very frustrating.
Thanks in advance!
Flash back to 2.1 and use the update.zip in the noob guide sticky to install clockwork recovery. Clockwork doesn't play nice on the stock 2.2
Sent from my T959 using XDA App
Vinotas said:
Hello all,
I've looked on the Forum but can't seem to find the answer to this. In fact, I only found a comment about this issue on another forum and there were no solutions. Here's the problem:
I'm running a rooted T-Mobile Vibrant with Froyo 2.2. I don't have any lagfix or additional kernels, I have ROM Manager and Titanium Backup. I'm trying to flash Bionix Next Gen V2.
The first time I did it, I got the failed verification error, so used the batch file on this forum to fix the 3e recovery installer, did that, and the result is the same.
So, here's where I am:
-I go into rom manager, do the flash clockworkmod recovery, I'm on 2.5.1.2
-I have the update.zip and bionix.zip both on my sd card.
-I go to Install Rom from SD Card, choose Bionix, check backup existing rom and wipe data and cache.
-I click ok, it reboots it, gets me into recovery.
-THIS is where I have trouble. There is no option to "Install Zip from SD Card", only to "Reinstall Package". If I do that, it reboots the phone to my regular Froyo.
I can't seem to understand why the option to install Zip from SD Card isn't showing up even though it did the very first time I tried flashing (when I got the verification error).
Any help would be greatly appreciated. I feel like I'm so close that it's very frustrating.
Thanks in advance!
Click to expand...
Click to collapse
try hitting "install packages" twice then cwm should pop up
THANK YOU!!!!
A great big MERCI, you guys ROCK!!!!!
I double-clicked the Install Packages option and poof CWM recover popped up and allowed me to install from zip. I'm running Bionix Next Gen V2 and the speed's eye-popping. GPS locks on nearly instantly too.
Thanks again!
I've tried installing ClockworkMod Recovery 5.0.2.0 and ClockworkMod Touch Recovery 5.8.1.8 on my AT&T Atrix 4G with the same results:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
The result is that I can boot to recovery and flash CM7 to the phone, but ROM Manager does not recognize the recovery partition. To install CWM I used "fastboot erase recovery" and "fastboot flash recovery <cwm filename>". It was unlocked and rooted using Pete's Motorola Tools.
This has appeared on other threads that have been closed and appear to end around November 2011. I can't find a definitive answer in the forums - there appears to be disagreement on whether or not there is a reliable ClockworkMod Recovery image. Some tips refer to removing /system/etc/install-recovery.sh, but this file is not present.
Is this a known issue? Is there a fix? Have I missed something obvious?
tbazett said:
I've tried installing ClockworkMod Recovery 5.0.2.0 and ClockworkMod Touch Recovery 5.8.1.8 on my AT&T Atrix 4G with the same results:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
The result is that I can boot to recovery and flash CM7 to the phone, but ROM Manager does not recognize the recovery partition. To install CWM I used "fastboot erase recovery" and "fastboot flash recovery ". It was unlocked and rooted using Pete's Motorola Tools.
This has appeared on other threads that have been closed and appear to end around November 2011. I can't find a definitive answer in the forums - there appears to be disagreement on whether or not there is a reliable ClockworkMod Recovery image. Some tips refer to removing /system/etc/install-recovery.sh, but this file is not present.
Is this a known issue? Is there a fix? Have I missed something obvious?
Click to expand...
Click to collapse
Same problem, can't locate an answer. Can someone weigh in, point us to the solution, etc.?
Thanks.
Edit: never mind. Touch removed, issue solved.
Phone: Atrix 4G (2.3.6)
Carrier: AT&T
I began this process with a stock phone. I wanted to install Cyanogenmod and was following the instructions listed on their site. The title of the article was 'Motorola Atrix 4G: Full Update Guide'. I was able to install the unlocked bootloader, but when I go to try and install CWM I am also receiving the:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
messages. I have booted into the OS and browsed my /system/etc for anything called install_recovery.sh, but this file does not exist. I would love to continue installing Cyanogenmod, but have hit a brick wall.
Also if I boot into fastboot and do a 'fastboot erase recovery' I receive a different error:
StorMgr Formatting SOS
Any help is appreciated!
matrixx333 said:
Phone: Atrix 4G (2.3.6)
Carrier: AT&T
I began this process with a stock phone. I wanted to install Cyanogenmod and was following the instructions listed on their site. The title of the article was 'Motorola Atrix 4G: Full Update Guide'. I was able to install the unlocked bootloader, but when I go to try and install CWM I am also receiving the:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
messages. I have booted into the OS and browsed my /system/etc for anything called install_recovery.sh, but this file does not exist. I would love to continue installing Cyanogenmod, but have hit a brick wall.
Also if I boot into fastboot and do a 'fastboot erase recovery' I receive a different error:
StorMgr Formatting SOS
Any help is appreciated!
Click to expand...
Click to collapse
That is not an error actually. That's how fastboot shows you are currently formatting Recovery partition (and it calls it SOS).
It happens when you erase or flash recovery. If you look closely, when you tell moto-fastboot to erase webtop, the phone calls it "osh".
I personally only use TWRP recovery, and I would recommend that over CWM (or CWM Touch).
vladeco said:
That is not an error actually. That's how fastboot shows you are currently formatting Recovery partition (and it calls it SOS).
It happens when you erase or flash recovery. If you look closely, when you tell moto-fastboot to erase webtop, the phone calls it "osh".
I personally only use TWRP recovery, and I would recommend that over CWM (or CWM Touch).
Click to expand...
Click to collapse
Thank you for the fast reply, but I also receive the exact same message when trying to install twrp 2.2.
*sigh*
matrixx333 said:
Thank you for the fast reply, but I also receive the exact same message when trying to install twrp 2.2.
*sigh*
Click to expand...
Click to collapse
Did you try rom manager. download it from the market and flash CWM through it.
matrixx333 said:
Thank you for the fast reply, but I also receive the exact same message when trying to install twrp 2.2.
*sigh*
Click to expand...
Click to collapse
I've come to the conclusion that it is an error, probably due to hardware, and it's not going to be fixed. The main disadvantage is that the ROM Manager app doesn't recognize the recovery partition so you can't use any of the features there that require it. I just use CWM directly and it seems to work just fine. I've been running CWM Touch, switching between CM7 and CM9 several times, for the past 5 months and it's good enough for backing up, recovering, and flashing.
harishatrix said:
Did you try rom manager. download it from the market and flash CWM through it.
Click to expand...
Click to collapse
harishatrix,
From reading the 'THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs' information I was under the impression that rooting and unlocking the bootloader are two seperate things. I did unlock the bootloader, but I thought you had to 'root' the device in order to install ROM Manager. Am I mistaken?
tbazett said:
I've come to the conclusion that it is an error, probably due to hardware, and it's not going to be fixed. The main disadvantage is that the ROM Manager app doesn't recognize the recovery partition so you can't use any of the features there that require it. I just use CWM directly and it seems to work just fine. I've been running CWM Touch, switching between CM7 and CM9 several times, for the past 5 months and it's good enough for backing up, recovering, and flashing.
Click to expand...
Click to collapse
tbazett,
You said you use CWM directly. How do you do this? I thought you were getting the 'SOS' error when you tried to install CMW. Was there a work-around that you used to bypass this message?
matrixx333 said:
harishatrix,
From reading the 'THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs' information I was under the impression that rooting and unlocking the bootloader are two seperate things. I did unlock the bootloader, but I thought you had to 'root' the device in order to install ROM Manager. Am I mistaken?
tbazett,
You said you use CWM directly. How do you do this? I thought you were getting the 'SOS' error when you tried to install CMW. Was there a work-around that you used to bypass this message?
Click to expand...
Click to collapse
If I remember correctly, it just stays at the SOS error message so I had to pull the battery to turn it off. After putting the battery back in I was able to turn it on, access the boot menu (using volume down button), and then boot up to the recovery partition.
I don't know what causes the error, but my guess is there is something at the very end of the process that fails, like a checksum or some sort of signature. The result is that it actually works fine on it's own but the ROM Manager fails to recognize it.
Tbazett,
Do you remember how long you waited before you pulled the battery? Im curious if im just not waiting long enough for the install to complete.
Also, would i access CWM by powering down, holding vol down + power, then use the vol down button to cycle to 'android recovery'?
Sent from my MB860 using xda app-developers app
HA! I just rebooted into android recovery for the heck of it and twrp 2.2 was installed successfully!!!
Now im on my way to modding!
Thanks again to everyone, I found everyone's advise helpful!
Sent from my MB860 using xda app-developers app
matrixx333 said:
HA! I just rebooted into android recovery for the heck of it and twrp 2.2 was installed successfully!!!
Now im on my way to modding!
Thanks again to everyone, I found everyone's advise helpful!
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Cool - check out CM9 from Jokersax. You just download the cm9 zip and the google apps zip and flash both in that order.
Here's the forum for it: http://forum.xda-developers.com/showthread.php?t=1445052
I just tried to flash a ROM and it ended up strangly. As a disclaimer: this is not a "MY PHONE IS BROKEN PLZ HELP ME!" post. I managed to get around this somehow, but I want to realize what technically happened in order to deepen my knowlage about the Android boot process. I come from a background of a Linux PC developer, but I didn't develop anything for Android yet.
So this is the boot process as I understand it, please correct me where I'm wrong:
When you turn on the device, the first thing that happens is that the CPU executes the Radio. The Radio allows the software to preform basic communication with the hardware, and is similar to the PC's BIOS. The Radio can be replaced, but if replaced with a problematic Radio, there's nothing you can do with home equipment to restore it (meaning a full brick).
Once loaded, the Radio executes the boot loader from the flash memory. The boot loader is like GRUB on a PC Linux system. It is the one that traps magic keys like "Volume up + Home" and decides, whether to boot the ROM, the recovery console or just "boot itself".
Both the ROM and the recovery software reside in differents partitions, and the bootloader chooses which partition to boot from.
In normal boot, the bootloader chooses to load the Linux kernel from the system partition and pass the execution to it. The Linux kernel loads Java, which loads the launcher, etc etc...
As I understand, a normal boot process doesn't involve the recovery software at all, and each ROM comes with its own custom-compiled Linux kernel.
The recovery software is like another operating system, which allows you replace the operating system in the system partition (AKA the ROM). Is the recovery software based on the Linux kernel too, or is it an independed software written in C/Assembly? If it is based on the Linux kernel, does it share a kernel with the ROM, or does it have its own version of the Linux kernel?
Now, this is what happened when I tried to flash Cyanogenmod 10 into a Galaxy S device running Cyanogenmod 7. I booted into recovery, backed up and wiped. To my understanding, backup means creating images of the system and data partition, storing these image files in the SD card and sign them with MD5.
When I tried to install the ROM, it warned me that my current partition layout won't fit to the new ROM, and I need to install again to confirm.
Now, when installing an OS in a PC, you can alter the partitions because the OS installation runs from a CD or a DOK, but if the recovery software runs from the disk too, how can it alter the partition table?
Anyways, once I confirmed, the phoned crashed and entered a boot loop. As I understood, flashing a ROM doesn't do anything to the recovery partition, so in any case I can always boot back to recovery and restore the backup. I was probably wrong, because when I tried to boot into recovery I found out that I have a different recovery software (The previous one had the Clockwork icon and a black background, and the new one had gray background and the Android Logo. I tried to restore the backup using the new recovery software but it failed, complaining that it can't format the system partition and that there's a problem with "MTD" (What's that?). I tried to reformat the system partition from the recovery software, but doing so caused it just to return to the main recovery screen without preforming anything or complaining about errors. Same thing when I tried to preform factory reset.
After some failed attemps, what I tried is to flash the old CM7 ROM, not from a backup, but from a clean zip. The recovery console claimed that it succeeded, but it did it too fast to be true, and there were almost no prompts beside the one that says that it succeeded.
I tried to restart, and got into a boot-loop again. This time, however, in each boot I could see my prevoius Clockwork recovery software for a second before the phone restarted again. I booted again into recovery mode to find my previous old recovery software. I tried to restore the backup and it succeeded. Now, I don't really understand what happened:
1. How come flashing ROMs changed the recovery software? I though that I zip containing a ROM contains only a ROM (A Linux kernel, Java JVM etc etc...), not a recovery software.
2. After I tried to flash CM7 back I could see the recovery screen in the boot-loop. Why did I see that screen if I didn't choose explicitly to boot into recovery?
3. How can the recovery software change the partition layout of the memory that it resides on by itself?
4. How come that the previous recovery software managed to restore that backup? As I understood, I ruined the partition layout, so what magic did the old recovery software that the new one couldn't do?
Thanks for the help
r.darwish said:
I just tried to flash a ROM and it ended up strangly. As a disclaimer: this is not a "MY PHONE IS BROKEN PLZ HELP ME!" post. I managed to get around this somehow, but I want to realize what technically happened in order to deepen my knowlage about the Android boot process. I come from a background of a Linux PC developer, but I didn't develop anything for Android yet.
So this is the boot process as I understand it, please correct me where I'm wrong:
When you turn on the device, the first thing that happens is that the CPU executes the Radio. The Radio allows the software to preform basic communication with the hardware, and is similar to the PC's BIOS. The Radio can be replaced, but if replaced with a problematic Radio, there's nothing you can do with home equipment to restore it (meaning a full brick).
Once loaded, the Radio executes the boot loader from the flash memory. The boot loader is like GRUB on a PC Linux system. It is the one that traps magic keys like "Volume up + Home" and decides, whether to boot the ROM, the recovery console or just "boot itself".
Both the ROM and the recovery software reside in differents partitions, and the bootloader chooses which partition to boot from.
In normal boot, the bootloader chooses to load the Linux kernel from the system partition and pass the execution to it. The Linux kernel loads Java, which loads the launcher, etc etc...
As I understand, a normal boot process doesn't involve the recovery software at all, and each ROM comes with its own custom-compiled Linux kernel.
The recovery software is like another operating system, which allows you replace the operating system in the system partition (AKA the ROM). Is the recovery software based on the Linux kernel too, or is it an independed software written in C/Assembly? If it is based on the Linux kernel, does it share a kernel with the ROM, or does it have its own version of the Linux kernel?
Now, this is what happened when I tried to flash Cyanogenmod 10 into a Galaxy S device running Cyanogenmod 7. I booted into recovery, backed up and wiped. To my understanding, backup means creating images of the system and data partition, storing these image files in the SD card and sign them with MD5.
When I tried to install the ROM, it warned me that my current partition layout won't fit to the new ROM, and I need to install again to confirm.
Now, when installing an OS in a PC, you can alter the partitions because the OS installation runs from a CD or a DOK, but if the recovery software runs from the disk too, how can it alter the partition table?
Anyways, once I confirmed, the phoned crashed and entered a boot loop. As I understood, flashing a ROM doesn't do anything to the recovery partition, so in any case I can always boot back to recovery and restore the backup. I was probably wrong, because when I tried to boot into recovery I found out that I have a different recovery software (The previous one had the Clockwork icon and a black background, and the new one had gray background and the Android Logo. I tried to restore the backup using the new recovery software but it failed, complaining that it can't format the system partition and that there's a problem with "MTD" (What's that?). I tried to reformat the system partition from the recovery software, but doing so caused it just to return to the main recovery screen without preforming anything or complaining about errors. Same thing when I tried to preform factory reset.
After some failed attemps, what I tried is to flash the old CM7 ROM, not from a backup, but from a clean zip. The recovery console claimed that it succeeded, but it did it too fast to be true, and there were almost no prompts beside the one that says that it succeeded.
I tried to restart, and got into a boot-loop again. This time, however, in each boot I could see my prevoius Clockwork recovery software for a second before the phone restarted again. I booted again into recovery mode to find my previous old recovery software. I tried to restore the backup and it succeeded. Now, I don't really understand what happened:
1. How come flashing ROMs changed the recovery software? I though that I zip containing a ROM contains only a ROM (A Linux kernel, Java JVM etc etc...), not a recovery software.
2. After I tried to flash CM7 back I could see the recovery screen in the boot-loop. Why did I see that screen if I didn't choose explicitly to boot into recovery?
3. How can the recovery software change the partition layout of the memory that it resides on by itself?
4. How come that the previous recovery software managed to restore that backup? As I understood, I ruined the partition layout, so what magic did the old recovery software that the new one couldn't do?
Thanks for the help
Click to expand...
Click to collapse
1.A recovery could have been packaged in the zip (i use zips to install recoveries too).
2.Im not sure about this but it could be that your bootloader got messed up and didn know what to load.
3.I think this is possible since recovery loads itself into ram and works from there allowing the partition to be changed.
4. I don't know about this one
Also the recovery has it's own kernel it doesn't share it with the rom one(ex. if touch doesnt work in a rom due to its kernel it can work in recovery)
Sent from my LG-P350 using xda premium
nerot said:
1.A recovery could have been packaged in the zip (i use zips to install recoveries too).
2.Im not sure about this but it could be that your bootloader got messed up and didn know what to load.
3.I think this is possible since recovery loads itself into ram and works from there allowing the partition to be changed.
4. I don't know about this one
Also the recovery has it's own kernel it doesn't share it with the rom one(ex. if touch doesnt work in a rom due to its kernel it can work in recovery)
Sent from my LG-P350 using xda premium
Click to expand...
Click to collapse
Thank you for the answer
Maybe someone can confirm if Cyanogenmod is shipped with a recovery software?
r.darwish said:
Thank you for the answer
Maybe someone can confirm if Cyanogenmod is shipped with a recovery software?
Click to expand...
Click to collapse
Official builds do not contain the recovery.
Sent from my LG-P350 using xda premium
oneovo establish
I used official builds for both 10 and 7.