I had some issues when I tried to update from 2.2 to 4.4. The description in http://forum.xda-developers.com/showthread.php?t=2515036 is good, but the zip files can not be flashed to a 2.2 Defy with standard recovery. The more or less helpful error message was "E: Error in /sdcard/update-recovery.zip (status 0)". So there are some pre-requirements.
To get the zip-files installed I did install (maybe step 1 and 2 are not needed):
2ndInitDefy
TWRP-2.1.1
CM10 (I think with TWRP-2.6.1.0)
update-recovery.zip (TWRP-2.6.3.0), then CM11, then gapps.
Even better:
1) install 2ndInitDefy
2) flash defy_twrp_recovery_2.6.3.0
3) reboot into TWRP recovery and flash safewipe, then CM11, then Core gapps (NOT full or standard gapps)
@Quarx -- perhaps you could add this to the OP of your CM11 thread, so that the forums don't get spammed by noobs who didn't install properly.
1. root with framaroot
2. install 2ndinit 2.0 not 2.4
3 boot in recovery and do a cache and dalvik wipe. Install twrp 2.6.3.0
4. reboot in recovery twrp. Install recovery update. reboot in recovery twrp
5. Install CM 11
Enjoy
pgreed said:
1. root with framaroot
2. install 2ndinit 2.0 not 2.4
3 boot in recovery and do a cache and dalvik wipe. Install twrp 2.6.3.0
4. reboot in recovery twrp. Install recovery update. reboot in recovery twrp
5. Install CM 11
Enjoy
Click to expand...
Click to collapse
Why do you recommend this method instead of the steps I gave in the previous post? Your method doesn't give a clean install, because you didn't wipe the system partition, so it may lead to problems. You can wipe the system partition in TWRP, but doing so will also wipe recovery, so if a problem occurs during flashing you'll be stuck without recovery and have to go back to sbf. That's why TJKV created the safewipe script, which I linked in my previous post: it wipes the system partition but leaves recovery intact.
And why do you recommend such an old version of 2ndinit? I've used version 2.3 without any problems.
Also, TJKV's defy_twrp_recovery_2.6.3.0.zip, which I linked in my previous post, already includes the updated recovery, so installing the recovery update afterwards (your step #4) does nothing.
Proverbs2 said:
Why do you recommend this method instead of the steps I gave in the previous post? Your method doesn't give a clean install, because you didn't wipe the system partition, so it may lead to problems. You can wipe the system partition in TWRP, but doing so will also wipe recovery, so if a problem occurs during flashing you'll be stuck without recovery and have to go back to sbf. That's why TJKV created the safewipe script, which I linked in my previous post: it wipes the system partition but leaves recovery intact.
And why do you recommend such an old version of 2ndinit? I've used version 2.3 without any problems.
Also, TJKV's defy_twrp_recovery_2.6.3.0.zip, which I linked in my previous post, already includes the updated recovery, so installing the recovery update afterwards (your step #4) does nothing.
Click to expand...
Click to collapse
I use myself this method. If you wanna wipe something after boot into recovery you can install safewipe before installing TWRP (to convert partitions from ext3 to ext4).
Why 2ndinit 2.0? Because is all you need and is much smaller than 2.3 plus is safer.
From my experience the twrp 2.6.3.0 without patch failed to install CM11.
pgreed said:
Why 2ndinit 2.0? Because is all you need and is much smaller than 2.3 plus is safer.
Click to expand...
Click to collapse
2ndinit 2.0 is smaller because it doesn't include the actual bootmenu; it just downloads it from the web during the install process. Version 2.3 doesn't require internet access during installation.
pgreed said:
From my experience the twrp 2.6.3.0 without patch failed to install CM11.
Click to expand...
Click to collapse
It worked fine for me, and other users reported it working as well. Are you sure you installed the latest TWRP (version 2.6.3.0, using TJKV's zip), or did you perhaps install an earlier version? Version 2.6.3.0 is the version used by Quarx's CM11 builds.
Proverbs2 said:
2ndinit 2.0 is smaller because it doesn't include the actual bootmenu; it just downloads it from the web during the install process. Version 2.3 doesn't require internet access during installation.
It worked fine for me, and other users reported it working as well. Are you sure you installed the latest TWRP (version 2.6.3.0, using TJKV's zip), or did you perhaps install an earlier version? Version 2.6.3.0 is the version used by Quarx's CM11 builds.
Click to expand...
Click to collapse
V 2.3 is reported to not work on some machine (green lens) -this version is made especially for Defy+
I used a TWRP 2.6.3.0 I dunno if is TJKV's and w/o Quarx patch it doesn't work.
Reallocate Partitions
I have a question (may be off topic): exist a way to reallocate space in partitions?
I´ve installed cm11, and tried to add gmail.apk in /system/app with adb and i get: "no space left on device"
lfuentes said:
I have a question (may be off topic): exist a way to reallocate space in partitions?
I´ve installed cm11, and tried to add gmail.apk in /system/app with adb and i get: "no space left on device"
Click to expand...
Click to collapse
No. One very talented dev (Epsylon3, who helped develop CM7 and CM9 for the defy) hardbricked his device by trying to resize the system partition.
To save space in system, delete ringtones (which you can put on the SD card instead) and any system apps you don't use. See here and here for lists of apps that are safe to remove.
*delete* (wrong thread)
Related
Hi
I'm trying to flash a gingerbread rom to my desire but I always end up being stuck on the HTC logo. I tried several ROMS( opendesire, modaco with sense and without, some more too but can't remember the names,... ) The only gingerbread ROM that installs is CM7, but i have market problems that annoy the hell out of me ( can't find certain apps, need to hack to install bigger apps ). A shame because i really like CM, but i want to compare with others
Any idea why gingerbread won't flash correctly. I have tried several froyo ROMS without any issues before, by the way
I have
BRAVO PVT1 SHIP S-ON
HBOOT-0.93.0001
RADIO-5.14.05.17
thx
ntdst
Did you remember to wipe your data between each different install?
That's the most common problem when you get stuck at boot.
i use rom-manager and always create a back-up and wipe.
I also tried with an empty SD-Card and repartioned it ( with rom-manager ). The results are always the same, every gingerbread rom gets stuck. I thought there was something wrong with the partitions or maybe i need s-off for gingerbread... ?
What version of CWM do you have? Did you update manually to the new radio for the GB Roms?
- Recommended RADIO
http://insertcoin.dataninja.net/Addons/Radio/
If you flash the 32.56.00.32U_5.17.05.23. Radio a good idea will be to flash
the ril-firmare-drivers updates for it too
Click to expand...
Click to collapse
I'm using Rom Manager v4.2.0.2
It is possible that i flashed that radio with a previous modaco sense/froyo ROM.
should i first flash that one you mention and then try again?
Okay, Rom Manager Is not a recovery What's your recovery exactly?
And what ROMs do you try to flash?
AFAIK, you need to flash that first in order to get booted.
sorry clockworkmod 2.5.0.7 is current recovery
I really tried several ROMS
Modaco sense gingerbread
Modaco without sense
opendesire
oxygen
etc...
all and always stuck on HTC Logo except for CM7, that one works fine except for the market issues
- Clockworkmod Recovery 3.x.x.x (Recommended to be used! 2.x recoveries MAY have some problems with the updater-script => boot loop)
Click to expand...
Click to collapse
I found this in one of the ROM threads.
So my suggestion:
First try to update the radio to the newest (alredy posted the link).
If that does not help, then try to update your recovery.
updating radio and flashing updates did not help
i'm still stuck when trying to install oxygen
I could use some help in updating my recovery. I f i do this with rom manager 2.5.0.7 is the most recent.
I seems there's a 2.5.1.2 out and 3.x.x.x is not advised. Is there an update zip somewhere to use?
People report that Insertcoin S v22 can be installed with 2.5.0.7
Make sure you do a full wipe in THE RECOVERY, not ROM Manager or any program.
Too boot into recovery hold down Power+Vol Down while phone is off.
There:
1. Wipe data/factory reset
2. Wipe cahce
3. Under advanced menu > Wipe dalvik-cache
Also make sure your SD card is partitioned right.
And for the update - you can only update your recovery if you are S-OFF or you use Unrevoked3 with a custom recovery image.
Grab a copy of Ubuntu and check that the apps2sd partition on your card is formatted correctly. I tried all ways of formatting and partitioning (via clockwork/rom manager) and it never formatted correctly and always caused HTC boot sticking.
If I completely reformatted SD and reflashed an older rom (like Leedroid 2.3) would then boot fine. I then used Rom Manager to repartition & format SD, boot ubuntu (live CD is enough - no install required) then reformatted partition to EXT4, flashed and worked fine.
Also, is 2.5.0.7 your TRUE recovery version? Turn your phone on with vol-down held then select recovery - does the version change to an older one? If this is the case you may need to re-root is (Unrevoked) to update your recovery version permanantly.
Hope that helps.
If you are S-off you can flash newest recovery using fastboot, this flash would be permanent!
fastboot flash recovery recovery-clockwork-3.0.2.8-bravo.img
i agree with TMSsecret,
the gingerbread ROMs i have used seem to need a more recent version of HBOOT. First time I tried to flash LeeDroid 3.0.2, it didnt work. Applied S-OFF (which updates your HBOOT during the process) and tried again, worked no worries. Also, if you're keen to install the latest ROMs, upgrade to clockworkmod recovery 3.x... It took me a few tries to get FASTBOOT working properly (possibly because my version of windows XP has had too long to decompose), but if you persevere, it will work.
The best way to make sure your ROM will work is a thorough research session. Not slagging you at all, just pointing out the obvious. Look up everything to do with your intended ROM and read the threads.
Hi,
I am trying to flash MIUI on my Defy which is currently running the official 2.2.2 released here in India.
What i have done so far (and repeated the entire process several times):
-Rooted the phone using SuperOneClick
-Installed ROM Manager
-Installed Clockworkmod Recovery 2.5.1.8 for Defy
-Downloaded 'miuiandroid_Defy-2.3.4a' the then latest version of MIUI from their site and the corresponding language pack
-Installed and booted into custom recovery
-Took a nandroid backup of the current ROM
-Wiped data, cache and dalvik cache
-Selected the .zip ROM file from the sdcard and installed it
-After the installation was done, i rebooted the system
This is where the problem started. I had read that the phone might take forever for its first boot. But in my case, the phone would stay stuck on the M logo till i removed the battery. On restart, the same thing repeated.
I found the SBF for the retail version of 2.2 i found on the forums and used RSD Lite 4.9 to flash it to the phone and then restored the nandroid backup i had made previously to get back to where i started from. And i repeated the entire process 4 times using 3 different versions of MIUI.
Am i missing something here? What can i do to get the phone to move past that M logo? I have been trying to find a solution to this issue since over a week now. None of the forums seem to have a solution to a similar problem. Any help would be appreciated.
Answer to all Your problems
It's a common mistake. You must have forgotten about wipe all (cache and personal data) before installing zip package containing MIUI.
hex24 said:
It's a common mistake. You must have forgotten about wipe all (cache and personal data) before installing zip package containing MIUI.
Click to expand...
Click to collapse
I did that. Everytime i tried to install the ROM i did all the three.
Install 2nd inti not CMW and than install MIUI...
Sent from my MB526 using XDA App
ifu said:
Install 2nd inti not CMW and than install MIUI...
Sent from my MB526 using XDA App
Click to expand...
Click to collapse
It worked! It worked!
Thanks a lot!
Hello,
More than 1year ago, i've S-Off, root and installed CyanogenMod7, but, since i've got few problems with it, so I would like to install another versions of CyanogenMod in order to fix bugs, or, install another ROM, but, i don't remember how to do it?
I've heard that i can do it with RUU but, it will unroot my phone? and, i don't want to. So how can i do?
Thank you.
Boot into recovery mode and then install a new ROM with its ZIP archive.
I've tried to install this .zip ROM :
Safe_Buzz_Froyo_HTC_WWE_2.22.405.1_Rooted.zip (found on depositfiles)
So, i've wipe every things and then Install .zip from sdcard but, it writes me this :
Installing update...
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in android 1.5.
It was necessary to remove it when upgrading to the ClockWorkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation aborted.
Thanks,
Edit: Can i download ROM cyanogenmod cm-7.2.0-buzz.zip and install it on the recovery?
A friend of me told me that i must install an official rom before reinstalling cgm but he is not sure of that. (It's why I wanted to install Buzz_Froyo but, if it's not necessary... maybe i could directly re-install cgm ? )
hi,ruu's are .exe mainly and are for restoring rom to original sense state etc.
now for flashing roms and in your case a newer cm7 then you just need to download the cm7 zip rom,place it on your sdcard,reboot into recovery,wipe data/factory restore,wipe cache and wipe dalvik cache from advanced. Then install zip from sdcard navigating to the cm7 zip file and confirm. This is the basic method to install many custom roms.
goodluck.
Invalid user id !!!!
slymobi said:
hi,ruu's are .exe mainly and are for restoring rom to original sense state etc.
now for flashing roms and in your case a newer cm7 then you just need to download the cm7 zip rom,place it on your sdcard,reboot into recovery,wipe data/factory restore,wipe cache and wipe dalvik cache from advanced. Then install zip from sdcard navigating to the cm7 zip file and confirm. This is the basic method to install many custom roms.
goodluck.
Invalid user id !!!!
Click to expand...
Click to collapse
Thank you it worked perfectly =)
Not allowed to do any posts in the Android Revolution HD (ARHD) forum yet http://forum.xda-developers.com/showthread.php?t=1925402 so I'll share my experience here.
It seems like people sometimes have various issues after a Note II N7100 upgrade to AHRD rom 4.3 20.0 (or 20.1) , from earlier 4.1.2 versions like 19.0 and after reading all posts of this upgrade of various tips, fixes and install steps, I felt it was time to try the upgrade myself. It turned out to be successful without any issues with root working as well as everything else with a "butter" smooth experience since 2 weeks back..
These are the steps I followed.
- There was some importance regarding a specific bootloader that was recommended to flash first and also a custom recovery.
I was in version AHRD 19.0 on bootloader LJ3 but MJ5 was recommended most often. So MJ5 was flashed with Odin v3.09
- Next a custom recovery was mentioned and it seemed that most people were successful with TWRP 2.6.3.1
So I flashed TWRP 2.6.3.1 with Odin v3.09.
- Then the AHRD 20.1 rom was transferred to EXT SD card on the phone.
- Next, a wipe of data was done in TWRP
- Then the rom AHRD 20.1 rom was flashed after following the AROMA install procedure.
- After successfull boot, all my apps were installed from my Titanium backups.
Good you shared this with people who having trouble... but some may ask if you were able to update the SuperSU... then reboot and see if you still have root?
TWRP or Philz touch recovery (6.1.28) seem to work good (less problems).
Someone else also posted success like this:
1. Flash latest Philz touch recovery (6.1.28).
2. wipe everything (pick option flash new rom).
3. flash ARHD 20.1.
4. Reboot and set up everything like usual.
5. Update supersu and everything else/ restore titanium backup
Good luck to all.
cyberboob said:
Good you shared this with people who having trouble... but some may ask if you were able to update the SuperSU... then reboot and see if you still have root?
TWRP or Philz touch recovery (6.1.28) seem to work good (less problems).
Someone else also posted success like this:
1. Flash latest Philz touch recovery (6.1.28).
2. wipe everything (pick option flash new rom).
3. flash ARHD 20.1.
4. Reboot and set up everything like usual.
5. Update supersu and everything else/ restore titanium backup
Good luck to all.
Click to expand...
Click to collapse
Yes, root remains after SuperSU update and reboot !
Hi, I need your help to backup my current ROM and to update to some Android 10 custom ROM.
I am currently on a very old OOS based custom ROM with a rooted android version 7.1.1 (encrypted) and TWRP 3.2.1-0.
From what I remember, this TWRP version I have is bugged so that I cannot restore backups with it. However, since everything worked in the last years I didn't touch anything.
So, I want to..
1. backup my whole system and
2. install new custom ROM
Can someone tell me the steps I have to do?
I guess I have to..
1. Flash new TWRP (which one?)
2. Backup my partitions (does this work with a new TWRP for Android 7? Or would I need to use an older version?)
3. Install recent OOS firmware (which one and how? just flash it in TWRP?)
4. Wipe cache and data
5. Install new custom ROM
6. Install Magisk
7. Install Xposed
Is this correct?
I recently did the same thing. Your steps are correct, although I would add a couple more.
TWRP backup, TIBU backup, SMS backup, Then move all of those backups to your computer. Plus any contents of [Download, Documents, Pictures, Videos, DCIM, etc. ]
Download OOS from here, https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156155944
This will completely reset you to factory. so you will need to set up the phone just enough to get developer mode on*, enable ADB*, & Unlock Bl
** I forgot this part and tried going to fastboot and directly flashing TWRP and got strange errors bc ADB wasn't enabled.
> Flashboot install recovery TWRP
Then I struggled with a few ROMS, but finally got CR Droid to install.
I flashed each file listed here, https://forum.xda-developers.com/oneplus-5t/development/rom-crdroid-android-6-t3972533
Hey there, thanks so far.
But would you install newest TWRP first before backing up, right? Or Will the newest version of TWRP not work anymore with android 7.1.1?
And do you use normal TWRP or Bluspark version?
Edit: I think I would prefer to just install the OOS firmware because I don't have a windows system anymore so I can't do the ADB stuff via command line. Or I guess I would have to setup a VM with windows installed.. O_x