Related
Hi,
I really love your ROM, But unfortunately i am unable to install completely in my Google Nexus One mobile. I followed all your steps from
Steps 1 to 3 i ahev done in PC.
1.Downloading Kang-o-rama Zip file
2. Copying Kang-o-rama to root Nexus One phone's SD Card
3. Seted up Advanced Installer by creating the directories
<sdcard>\android\kangorama\
and in kangorama directory, I created a txt file with name install.cfg with apps2ext and bootanimation flags only.
I followed Steps 4 to 7 after inserting the SDcard in mobile.
4. Rebooted into Recovery
5. Did a Nandroid backup
6. Wiped Data, Cache and Dalvik-Cache
7. Installed the Kang-o-rama zip file from your SD Card
In Step 7 i am facing the problem, when i started installing, i got System Installation and kernel installation completed. after that i got "Application installing" and after 70% in progress... there is no further progress..
At this point the Mobile is static for more than 4 hours. Can you please help me out in successfull installation..Thanks in Advance
regards
Manickam
You don't have to use the advanced install. Just put the ROM on to your root of your SD and flash in recovery after full wipe.
just a few ideas...did you partition your sd card first? did you check the m5dsum of the file you downloaded?
i would also recommend posting this in the kangorama thread.
you can also look in /tmp/recovery.log to see where it got up to or if there were any errors.
if it got to the step "installing applications" or something similar then it may have completed but had trouble unmounting the sd-ext partition and froze.
if this is the case you can try rebooting and see if it has worked or try re-partitioniong using clockworkmod or any other recovery..
Hi,
I didn't see this tread (lucky actually that I ever saw it).
Since new users can't post in /dev even with replies you can PM me if you have these problems.
I suspect you're using ClockworkMod recovery? If so, try installing Amon_RA recovery, it has less problems:
http://forum.xda-developers.com/showthread.php?t=611829
If this doesn't help or you're still struggling feel free to send me a PM.
No. So far i didt Partitioned my SD card. Whether i Need to partition?
Ya. I am using ClockworkMod recovery.So what i should do now to make the MOD work properly..
Currently I am having ClockworkMod recovery 3.0.0.5. Whether I have to change my recovery?
I have also tried by partitioning the SD-EXT to 512MB and swap to 64mb. Still I am facing the problem in same point of application installation.
Can any one guide me to resolve this issue.
manicsen said:
Currently I am having ClockworkMod recovery 3.0.0.5. Whether I have to change my recovery?
I have also tried by partitioning the SD-EXT to 512MB and swap to 64mb. Still I am facing the problem in same point of application installation.
Can any one guide me to resolve this issue.
Click to expand...
Click to collapse
Replied to your PM...
Was this problem solved, if so how?
Im having the exact same problem. Tried with a noapps Advanced Installer, but no luck.
Edit: Turns out, going to Amon_RA did solve the problem.
I had CM7.1 installed onto the microSD (verygreen's method) and also had MIUI on emmc.
Today I decided to the unusable MIUI and install CM7 to emmc. Installation went fine but post installation of CM7(emmc) I booted into my SD CM7 to do a TB to restore onto emmc but it couldnt read/find the supposed SD(i.e. mmcblk1p4)
Next up I tried NookColor UMS. It mounts emmcblk1p1 as boot and I can add/remove files but the emmcblk1p4 gets mounted as a removable drive that "needs to be formatted".
(P.S. I did try mmcblk1p2/p3 but couldn't see anything in them either. I assumed they must be ext and since I'm on win7 I cant view them)
How do I get the emmcblk1p4 to mount/read?
thanks!
Did you use the same sd card to install CM7 to the emmc as you used for CM7?
gallahad2000 said:
Did you use the same sd card to install CM7 to the emmc as you used for CM7?
Click to expand...
Click to collapse
Yeah. The same. I put the zip in the boot partition of the card. (mmcblk1p1)
Sent from my MB502 using XDA App
Are you sure that you didn't format your card when you wrote the boot image to install CM7 to the emmc?
How did you go about installing CM7 to emmc? Which emmc install method did you use?
gallahad2000 said:
Are you sure that you didn't format your card when you wrote the boot image to install CM7 to the emmc?
How did you go about installing CM7 to emmc? Which emmc install method did you use?
Click to expand...
Click to collapse
Here's what I did:
1. Reboot into recovery. (Emmc CWM, not verygreen's installer.)
2. Unmount/remove SDcard.
3. Wipe/data factory reset.
4. Insert/ mount SDcard
5. Install zip from SDcard.
6. Choose zip and confirm
I know when we do a wipe data/factory reset then the sd-ext partition is formatted and that would delete any one of my CM7 SD partitions so I removed SD before this step.
Could it be that during flashing something happened to mmcblk1p4?
I had no ideas about the various methds for emmc install. I thought this was the standard procedure. Please tell me how to recover. Also if possible can you tell which would be the best method for doing something like this?
Sent from my MB502 using XDA App
How possibly you can use ONE uSD for both CwMR and CM7?
I don't think it works that way.
Either your provided info is incorrect or it is a completely new to us.
votinh said:
How possibly you can use ONE uSD for both CwMR and CM7?
I don't think it works that way.
Either your provided info is incorrect or it is a completely new to us.
Click to expand...
Click to collapse
As I stated in my previous post..the CWM is emmc while have 2 copies of CM7 (sdcard- verygreen and the normal emmc). And CWM recognises emmcblk1p1 as sd-card. So I put ROMs there.
And my emmcblk1p4 can't be read.
Sent from my MB502 using XDA App
Hi everyone!
I just got CM7 (latest stable release) installed on on external sdhc card. I have wifi issues with CM7 (and looking around the forums tells me that CM7 can be finicky with certain routers) so I would love to be able to use Nook's stock ROM (4.1.4) when I am having issues.
But, when I am on NC ROM, I don't see anything except the small boot partition on the SD and when I am on CM7, I don't get access to this boot partition. I am wondering if there is a way to either create another partition or make the currently existing partitions accessible on both ROMS so that I can share data between them.
I am a n00b without any Android experience so thanks in advance for your patient responses.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
andrandom said:
Hi everyone!
I just got CM7 (latest stable release) installed on on external sdhc card. I have wifi issues with CM7 (and looking around the forums tells me that CM7 can be finicky with certain routers) so I would love to be able to use Nook's stock ROM (4.1.4) when I am having issues.
But, when I am on NC ROM, I don't see anything except the small boot partition on the SD and when I am on CM7, I don't get access to this boot partition. I am wondering if there is a way to either create another partition or make the currently existing partitions accessible on both ROMS so that I can share data between them.
I am a n00b without any Android experience so thanks in advance for your patient responses.
Click to expand...
Click to collapse
Look in my signature for a link to my tips thread. I explain there how to make the SD media partition available to both ROMs (item B3).
leapinlar said:
Look in my signature for a link to my tips thread. I explain there how to make the SD media partition available to both ROMs (item B3).
Click to expand...
Click to collapse
*That's* the one I wanted to point them to.
leapinlar said:
Look in my signature for a link to my tips thread. I explain there how to make the SD media partition available to both ROMs (item B3).
Click to expand...
Click to collapse
Thanks.
Do you mean step #3 in Section B? I could edit it without running your script too, can't I?
andrandom said:
Thanks.
Do you mean step #3 in Section B? I could edit it without running your script too, can't I?
Click to expand...
Click to collapse
If whatever you have on emmc is rooted, you can manually edit it. If you have unrooted stock, then you need to flash the zip since without root you cannot edit those files manually. And I did mean item B3. Each item is a different topic, they are not steps. One topic does not depend on another. Just do B3 and no others if you want.
Yes, item B3. My mistake...
I should be able to do flash the zip from my current CM7 SD card's boot partition, shouldn't I?
So I put the update-stockemmc-vold-fstab-modified-for-partition4.zip file in the boot partition of the SD card, rebooted to Recovery mode and then booted to NC's stock ROM. NC is still using the tiny boot partition on the SD card as my external storage instead of the much larger CM7 partition. This was the same partition that was under 'My Files / Memory card' before I flashed so nothing has changed. I did this twice to double-check.
Am I doing this wrong?
andrandom said:
Yes, item B3. My mistake...
I should be able to do flash the zip from my current CM7 SD card's boot partition, shouldn't I?
So I put the update-stockemmc-vold-fstab-modified-for-partition4.zip file in the boot partition of the SD card, rebooted to Recovery mode and then booted to NC's stock ROM. NC is still using the tiny boot partition on the SD card as my external storage instead of the much larger CM7 partition. This was the same partition that was under 'My Files / Memory card' before I flashed so nothing has changed. I did this twice to double-check.
Am I doing this wrong?
Click to expand...
Click to collapse
Yes you are doing it wrong. You need to flash that file with a CWM card, not put in the boot partition of your SD. And since you did that, you need to re-flash your latest ROM on SD to correct your mistake. (I will edit my instructions to make it a little clearer that you use CWM to flash that file.)
I got NC stock ROM to see my SD card partition by following item A10. That is most excellent and thanks again!
Unfortunately, I no longer see the boot partition when I attach NC to my computer whether NC is running off stock ROM or CM7. My guess is that this is due to my failed attempt to flash from my CM7 SD card yesterday. Am I right?
I thought I could reverse that by copying the update-stockemmc-vold-fstab-return-to-stock.zip file to CM7's boot (and then booting to the recovery mode) but that seemed to have nothing.
If I understand your previous message correctly, I should re-do my entire SD card but... I have already spent a few hours downloading and customizing the Android apps. Is there a way to preserve all that before Win32diskimager destroys the contents of the SD card?
Is there a way to manually mount the /etc folder from a unix prompt and alter the file?
Does it even matter if I don't see boot while I attach NC to a computer? Are there any caveats to 'let it be'?
Questions, questions and more questions...
That leads me to the obvious question, is there a book that explains Android to someone who is not interested in programming it but wants to understand the architecture and design of the OS (and custom ROMs)?
Thanks for being patient with all these n00b questions.
andrandom said:
I got NC stock ROM to see my SD card partition by following item A10. That is most excellent and thanks again!
Unfortunately, I no longer see the boot partition when I attach NC to my computer whether NC is running off stock ROM or CM7. My guess is that this is due to my failed attempt to flash from my CM7 SD card yesterday. Am I right?
I thought I could reverse that by copying the update-stockemmc-vold-fstab-return-to-stock.zip file to CM7's boot (and then booting to the recovery mode) but that seemed to have nothing.
If I understand your previous message correctly, I should re-do my entire SD card but... I have already spent a few hours downloading and customizing the Android apps. Is there a way to preserve all that before Win32diskimager destroys the contents of the SD card?
Is there a way to manually mount the /etc folder from a unix prompt and alter the file?
Does it even matter if I don't see boot while I attach NC to a computer? Are there any caveats to 'let it be'?
Questions, questions and more questions...
That leads me to the obvious question, is there a book that explains Android to someone who is not interested in programming it but wants to understand the architecture and design of the OS (and custom ROMs)?
Thanks for being patient with all these n00b questions.
Click to expand...
Click to collapse
You do not need or want to re-set up the whole SD installation. Just put the same CM7 zip file back in the boot partition and boot to SD recovery. It will put the correct vold.fstab back on the SD. You will not lose any settings or apps you have already set up. (And putting the return to stock zip there was also the wrong thing to do. The vold.fstab for stock and CM7 are different. But don't worry, it will fix that too.)
You are not supposed to see the boot partition on the PC when you plug the nook in with the cable. You are only supposed to see 'emmc' and 'sdcard'. Under the original setup, your stock system thought the boot partition was 'sdcard' and that was why you saw it on your PC. Since you modified stock to see partition 4 as 'sdcard', partition 4 is what the PC sees, not the boot partition.
Most people have to physically take the card out of the nook and put it in the PC to see the boot partition on the PC. If you don't want to do that, use my script in item B4. But since you are on CM7, you will not be adding many things to the boot partition to install with SD recovery in the future. So it is probably best to leave things be.
And I don't know of any books to help you.
Sent from my Nook Color running ICS and Tapatalk
That is excellent news!
A bit of playing around with Astro tells me that I was wrong about seeing the 'CM7 SDCARD' partition when I was on CM7 ROM. I am only seeing the boot. Anyway, I am going to flash the CM7 ROM again and I am hoping it would fix everything.
Also, yes, I can see the boot partition when I put the SD card directly on my computer but I was also able to see it when I hooked up the NC to my computer via USB before I did my unintended tweaks but... I'll survive.
I'll be back after I flash. (Famous last words??)
Mission accomplished!
Thanks again for all your help.
For future reference after you alter stock's fstab... all you have to do is:
mkdir /sdcard/boot (only have to do this one time)
mount /dev/block/mmcblk1p1 /sdcard/boot (do this every time you want to put something on the boot partition)
put anything you want on boot partition in /sdcard/boot
DizzyDen said:
For future reference after you alter stock's fstab... all you have to do is:
mkdir /sdcard/boot (only have to do this one time)
mount /dev/block/mmcblk1p1 /sdcard/boot (do this every time you want to put something on the boot partition)
put anything you want on boot partition in /sdcard/boot
Click to expand...
Click to collapse
Yes, there is one big advantage to using that method. I think it allows the boot partition to be seen not only on the nook, but also on the PC when you plug in the usb.
leapinlar said:
Yes, there is one big advantage to using that method. I think it allows the boot partition to be seen not only on the nook, but also on the PC when you plug in the usb.
Click to expand...
Click to collapse
We could probably come up with a symlink to /dev/block/mmcblk1p1 to /sdcard/boot and avoid having to mount it everytime as well.
DizzyDen said:
We could probably come up with a symlink to /dev/block/mmcblk1p1 to /sdcard/boot and avoid having to mount it everytime as well.
Click to expand...
Click to collapse
Thank you Dizz, your suggestion got me to thinking and I was able to come up with an init.d bash script that does the trick. I just temporarily mounted sdcard and created the sdcard/boot directory and the mounted the boot partition to it, then unmounted sdcard so it could be mounted again by the system later in the boot sequence.
The only problem is now sdcard will not mount on the PC using UMS mass storage. Must be because of having a second mount within the mount. But it does mount with MTP. But that may be acceptable. I will test some more, including using Goo Manager tomorrow.
EDIT (6-21): Goo Manager works. But I think I have figured out why sdcard is not mounting in UMS. Once it is mounted in my script and the boot partition mounted under it, it cannot be unmounted. And since it cannot be unmounted, it cannot be mounted later by the system as vold. If it cannot be mounted as vold, it does not show in UMS. For now I think I will leave it as I have it in Rev 2 of my script (symlinking to the root directory with full r/w permissions). If people want to see the boot partition on the PC, just use my modified for CM9 NookColorUMS available in my tips thread.
Sent from my Nook Color running ICS and Tapatalk
Help!
When CM7 is running, my computer is no longer mounting any of the partitions when I connect NC to my computer via the USB cable.
If the NC stock ROM is running, my computer mounts all three partitions (MyNook..., boot and CM7SDcard) but calibre is not recognizing the external partitions for transfers.
Further, when I boot to my NC stock ROM, I am no longer seeing my SD card's contents in the NC's library.
This may have something to do with the fact that NC stock ROM seemed to have updated itself to 4.1.3.
Should I re-run the scripts again or am I missing something else?
When it was updated to 1.4.3, you lost the emmc mods. Just re-flash my zip with the CWM SD. You may have lost CWM on emmc too.
On CM7, you have to select the turn on storage button after you plug it in. It is not automatic like stock. Pull up the notification area and touch the turn on button.
Darn, I forgot about that 'USB' option under notifications. Enabling it allows me to find the partitions. I will run your scripts again when I find a spare mUSB card.
Thanks again for your help!
Hi,
I have a nook that I rooted and put a custom rom on back about a year and a half ago. I flashed the ROM to the internal EMMC and CWM 3.2.0.1 was flashed as recovery. If it makes any difference it was a CM9 ROM
Now here's where I'm at. I can run ROMs off the sd-card but they are not stable at all. I get a whole bunch of force closes and such.
When I try and flash a new ROM to the internal EMMC it says it completes, but nothing changes. It is still the previous ROM. When I try and format the /data and /system partitions with the EMMC recovery, it doesn't complete. It says there is an error. When I format with TWRP off an sd card, it says it completes but once again, the rom is not wiped.
I've tried the 8 reboot error method, and it never gets to the stock recovery screen. It keeps booting to the EMMC ROM.
I've tried repartioning the EMMC with leapinlar's zip files. It says it successfully completes, but once again nothing changes.
Ideally I'd like to get the emmc back to stock and try and run a rom off the sdcard.
I've read the threads that I thought were applicable to my issues, but nothing seemed to work. I'm completely out of ideas. Anyone have similar issues or can provide some guidance?
Thanks.
The problem you are having running a ROM from SD is the brand and speed of SD you are using. It needs to be SanDisk class 4.
The reason the 8 failed boot does not work is you replaced the stock recovery with CWM. It needs the stock recovery to be able to complete. See my NC tips thread linked in my signature and read item A12. Assuming you can get it to flash, I have a stock recovery zip there.
I don't understand why the ROMs are not flashing. You say it gives errors when you try to wipe with CWM. What do the errors say? You used the internal CWM and TWRP on SD, but none worked. Try my bootable CWM SD to see if that helps.
I don't understand why my partition zips did not work. I know the newest TWRP will not flash them without giving an error 2 message. Try my bootable CWM SD.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Thanks for the advice...
I've been using a Patriot class 10 micro sd to run the roms/attempt to flash new roms. Its worked fine before, but I'll try and pickup another one from someplace.
When I try and format /system and /data from the emmc CWM it says "Error formatting /system" or "error formatting /data" after working away for about 5 minutes
Here's what i did:
Created CWM 6.0.1.2 Bootable SD
- Flashed NookColor-emmc-stockrecovery.zip
- Message said successfull.
- tried to restart and old CWM recovery 3.2.0.1 was still installed
Booted into CWM 6.0.1.2 Bootable SD Recovery
- mounted /system and /data
- attempted to format
- Message "Done." for both
- attempted to flash stock 1.4.3 that you have modified for CWM
- install from sdcard complete
- reboot
- Old CynanogenMod bootscreen and old rom still installed.
Using same CWM 6.0.1.2 Bootable Sd Recovery
-flashed NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip and NookColor-emmc-format-partitions-5-6-7.zip
-said success
-attempted to flash stock 1.4.3
- nothing changed. Old rom still installed
One more thing I noticed:
Everytime I login to the currently flashed rom, any changes I make are never saved. For example, if i install an apk or uninstall an app, the next time i can successfully boot into the emmc ROM, those changes are reversed to the previous version. Could it be that the current rom is being stored somewhere and being reflashed when it tries to bootup?
I hate to say this, but it sounds like your internal embedded card has become read only. I have had this happen to SDs but not to emmc. The apps act like they are writing and if you leave the folder and come back, they are not there. It is like they are writing to a ramdisk instead of your SD. You might try booting to a ROM on SD and see if you can write to any of the internal partitions like /cache or /rom and see if they stick. If not, you may only be able to run off SD and maybe not even then. You might have to change your dalvik cache setting on SD so it uses /data instead of /cache.
Sent from my Galaxy Tab running Tapatalk
I tried copying a file to the emmc partition from twrp and it didn't persist after reboot... so it looks like the emmc is set to read only. I don't supposed I can change that using adb and/or software solutions right? It's a hardware issue?
Any guidance on how to change davlik cache to use /data instead of /cache? I'll be happy to get any sort of stable rom running off any SD card.
I was hoping to repurpose the nook as in in car tablet to tether a data connection to my phone and play music and such.
Thanks for your help. I appreciate you taking the time.
canjoe said:
I tried copying a file to the emmc partition from twrp and it didn't persist after reboot... so it looks like the emmc is set to read only. I don't supposed I can change that using adb and/or software solutions right? It's a hardware issue?
Any guidance on how to change davlik cache to use /data instead of /cache? I'll be happy to get any sort of stable rom running off any SD card.
I was hoping to repurpose the nook as in in car tablet to tether a data connection to my phone and play music and such.
Thanks for your help. I appreciate you taking the time.
Click to expand...
Click to collapse
I don't know of anything that can revive it. I never could revive my SD that that happened to.
To make your ROM on SD use /data for all of the dalvik cache, create a file in /data named local.prop. In that file put this line:
dalvik.vm.dexopt-data-only=1
Next time it boots the system file portion of dalvik cache will be on /data along with the installed app portion.
Sent from my stock Nook HD+ using XDA Premium
I now have a stable version of CM 7.2 running off the SD card. I put the davlik cache on the data partition and everything seems to be running pretty smooth.
I'll keep messing around seeing if there is anything to revive the internal emmc, but at least I can use the nook off the SD card again.
Thanks for helping me troubleshoot and figure this out. Cheers.
EDIT: Ok, I've located where my problem is. Basically what happens is when I install the Custom ROM it replaces my 2ndInit bootmenu and CWM and it 'upgrades' them. But because it has 'upgraded' them I can no longer mount sd card. I have to reinstall 2ndInit to 'downgrade' CWM and then I can flash again.
Hi there,
A few weeks back I flashed Paranoid Android onto my phone (latest release), however now I have discovered that in recovery mode, my phone can't read or mount the sdcard, i.e. I can't apply updates.
Code:
If I select 'Install zip from sdcard > Choose zip from sdcard' I get:
E:Can't mount /sdcard/
And if I try 'Mounts and storage > mount /sdcard' I get:
Error mounting /sdcard!
I would really appreciate any help on this issue.
Note it was working previously (which is how I installed the ParanoidAndroid ROM) but now my phone can't read the sdcard in recovery. IT CAN READ IT ONCE THE PHONE HAS BOOTED UP.
Try running a chkdsk scan from a Windows machine to check if there's corruption in the filesystem
Sent from my MB526 using xda premium
thekguy said:
Try running a chkdsk scan from a Windows machine to check if there's corruption in the filesystem
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
will do and will post the results, but before I do, would that show anything because the sdcard works fine once the phone has booted up?
Not sure myself, it just eliminates any filesystem corruption as the cause. Also try using another build like quarx to check for this problem
Sent from my MB526 using xda premium
thekguy said:
Not sure myself, it just eliminates any filesystem corruption as the cause. Also try using another build like quarx to check for this problem
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
But I can't flash using recovery, so how would I test Quarx's build? Haven't had time to boot up my windows partition, but I will eventually.
EDIT: Ran fsck on fedora partition (forgot about the command). It came up with this
Code:
fsck from util-linux 2.21.2
e2fsck 1.42.3 (14-May-2012)
fsck.ext2: Is a directory while trying to open /media/CDF2-6BE2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
I've backed up my SDCard and am going to run e2fsck command (will post results) otherwise I'm going to have to reformat it
EDIT 2: Came up with same error. Should I reformat it? As ext3/ext4? What should I do?
My memory card was standard fat32
And I'm no Linux expert but I think you're trying to check for a wrong filesystem, what is your current sdcard format(filesystem)
And I think you should reformat as fat32
Sent from my MB526 using xda premium
thekguy said:
My memory card was standard fat32
And I'm no Linux expert but I think you're trying to check for a wrong filesystem, what is your current sdcard format(filesystem)
And I think you should reformat as fat32
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Code:
/dev/sdb vfat 7856128 1361952 6494176 18% /media/CDF2-6BE2
Now I've checked fsck again
Code:
fsck.vfat /media/CDF2-6BE2/
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
Read 512 bytes at 0:Is a directory
Can you try with Windows? And format to fat32
Sent from my MB526 using xda premium
thekguy said:
Can you try with Windows? And format to fat32
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
will do
EDIT:
Code:
The type of the file system is RAW.
CHKDSK is not available for RAW drives.
OK, Am backing up now. Will reformat as fat32
Ok... So now I've formatted as fat32, tried again, flashed full sbf, re-rooted phone, installed 2nd-init, flashed Quarx's latest build (before wi-fi experimentation builds) and still I have the problem
Sorry for the triple post
I've located where my problem is. Basically what happens is when I install the Custom ROM it replaces my 2ndInit bootmenu and CWM and it 'upgrades' them. But because it has 'upgraded' them I can no longer mount sd card. I have to reinstall 2ndInit to 'downgrade' CWM and then I can flash again.
Any suggestions on how I might be able to fix this?
Probably there isn't any fix, but you could make zip containing the working recovery, and flash it after every rom flash
Sent from my MB526 using xda premium
thekguy said:
Probably there isn't any fix, but you could make zip containing the working recovery, and flash it after every rom flash
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
If you could show me how to do that, I would so extremely grateful
Aparently there was a similar problem with the Defy running the 'official' CM and the wiki documented a fix here: http://oldwiki.cyanogenmod.org/wiki/Motorola_Defy:_FAQ#SD_Card
Do you think that could possibly work for the Defy+?
EDIT: However if I make a .zip file, would that put my phone in bootloop though? Because whenever I reinstall 2ndInit (v2.3) and it 'downgrades' my CWM/Bootmenu it causes a bootloop where I have to reflash everything. If I make a .zip that I flash after each install would it cause the same problem because it's 'downgrading' from the Bootmenu/CWM of the JB CM10 ROM.
I would've made you one, but unfortunately my computer is not working. I think it should be enough if the boot menu folder is replaced by your working set by a flash after every install
Sent from my MB526 using xda premium
thekguy said:
I would've made you one, but unfortunately my computer is not working. I think it should be enough if the boot menu folder is replaced by your working set by a flash after every install
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
I really appreciate your help! I guess you could perhaps guide me in doing it, or I could wait till you've got a wroking computer.
So, computer just started working, and I made you a zip
Download the zip to your computer and extract the contents[META-INF and system) folders. Add your working bootmenu files inside the system/bootmenu folder you just extracted and delete the pre-existing text file there. Then add both META-INF and system to a zip(not rar!) and try flashing it. Make sure that the file consists of META-INF and system folders within itself. It should work
IF THERE'S A SIGNATURE VERIFICATION ERROR JUST TOGGLE SIGNATURE VERIFICATION WHICH IS PRESENT JUST BEFORE SELECTING THE ZIP FILE TO FLASH VIA RECOVERY
thekguy said:
So, computer just started working, and I made you a zip
Download the zip to your computer and extract the contents[META-INF and system) folders. Add your working bootmenu files inside the system/bootmenu folder you just extracted and delete the pre-existing text file there. Then add both META-INF and system to a zip(not rar!) and try flashing it. Make sure that the file consists of META-INF and system folders within itself. It should work
IF THERE'S A SIGNATURE VERIFICATION ERROR JUST TOGGLE SIGNATURE VERIFICATION WHICH IS PRESENT JUST BEFORE SELECTING THE ZIP FILE TO FLASH VIA RECOVERY
Click to expand...
Click to collapse
Thank you very much, I'll definitely try this out!
EDIT1: First attempt, didn't work
Trying something again...
EDIT2: Second attempt.... Put phone into bootloop :\
EDIT3: Third attempt... Seems like a bootloop again
So basically it changes the Recovery version (not the bootmenu) and puts it into bootloop :\ however I can flash via recovery.
Try copying only recovery folder from inside boot menu
I'll try to make a zip which first deletes the folder to avoid incompatibilities.
BTW can you enter the boot menu when there's boot loop?
And also try fixing permissions
Sent from my MB526 using xda premium
thekguy said:
Try copying only recovery folder from inside boot menu
I'll try to make a zip which first deletes the folder to avoid incompatibilities.
BTW can you enter the boot menu when there's boot loop?
And also try fixing permissions
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Yeah I can enter bootmenu during bootloop before it starts. I'll retry with the recovery folder only.
EDIT: Wow it worked! Thank you so much I hope you don't mind too much, but if you can modify the recovery slightly that it'd help out a lot and make everything perfect. But I can't thank you enough
I'll upload my working Patch.zip:
If you can do these, that would be amazing: (this is from the working CWM)
1) When I select 'Wipe data/factory reset' it says 'Formatting /data...' and then immediately says 'Formatting /cache...' and when the phone boots up, all my data is there. Now that isn't a problem as such but if I needed to do a clean install that may cause some issues.
2) This isn't a problem, but I was wondering if you could add a printed line whenever I execute the 'Wipe dalvik cache' because it wipes it very fast, but doesn't say anything in the console so I'm not sure if I clicked it or not. Nevertheless when I boot my phone up it says optimising apps which means that it worked.
But yeah only minor things.
Thank you so much
1)I can't modify the recovery, since I'm not really a dev but I can try to make you another zip to wipe data separately
2)Again, that is something coded in the recovery, which I don't know how to alter. Plus, my computer isn't working again(bad ram :banghead: ) so I'm limited to the phone
But are you able at all to wipe data from the custom recovery? Bootmenu? Are both not working?
Sent from my MB526 using xda premium