Database Develop

help: stuck on ANDROID screen of CM7

Hi all,
I've recently rooted my nook color. I installed CM7 through rom manager and it installed, etc and then when it boots up it stays stuck on the android screen with the android logo and rays.
Sorry, but I'm new to nook color and modding. Can anyone help?
Thanks,
Brett

bdws1975 said:
Hi all,
I've recently rooted my nook color. I installed CM7 through rom manager and it installed, etc and then when it boots up it stays stuck on the android screen with the android logo and rays.
Sorry, but I'm new to nook color and modding. Can anyone help?
Thanks,
Brett
Click to expand...
Click to collapse
Which version of CM7 did you install? Sounds to me like you installed a corrupt copy. Make sure the download is correct. If you can open the .zip file, then the file is OK.
Also, did you wipe cache partition before installing CM7? Then wipe Dalvik cache?

CM7 boot gets stuck
I had the same problem when i first installed cm7 on my nook, but for some miraculous and unknown (at least to me) reason, after i plugged it into my computer (while the boot screen was stuck) it booted up no problem. idk what causes it to happen, but plugging it into my computer made it get past the stalled boot.

Fwiw the android screen suggests the kernel has loaded. Are you able to capture a log w adb logcat?
Sent from my HTC Vision using XDA App

Did you wipe data/clear cache?
the android and rays sound like you rooted the stock right(autonooter)?
I had the same issue, i used the 8 fails boots to get to the CWR then wipe data and clear cache and tada boots up to CM7 correctly.

Hi all
I ended up tajing it back to stock, rerooting and flashing cm7 again. All is well now.
I believe i wiped the boot accidentally and thats what started it all.
Thanks for your help.
Brett
Sent from my HTC Desire HD using XDA Premium App

I updated my NC to run the latest CM7 release on the SD card. When I tried to add the latest Dalingrin OC kernel it appears to boot but doesn't get to the CM animation screen. Do I need to clear the cache before updating the kernel? Is this the correct way to do it? "rm -rf /data/dalvik-cache/*"? Will I loose any data or apps?

jmak10 said:
I updated my NC to run the latest CM7 release on the SD card. When I tried to add the latest Dalingrin OC kernel it appears to boot but doesn't get to the CM animation screen. Do I need to clear the cache before updating the kernel? Is this the correct way to do it? "rm -rf /data/dalvik-cache/*"? Will I loose any data or apps?
Click to expand...
Click to collapse
I had the same thing happen to me yesterday , and then realized that I had downloaded the wrong OC version - the emmc instead of the sd. I reflashed the CM7 build, then copied the correct uimage and all was well

Is factory reset recommended before flashing cm7?
sent from PinoyNook

wrdoss said:
I had the same thing happen to me yesterday , and then realized that I had downloaded the wrong OC version - the emmc instead of the sd. I reflashed the CM7 build, then copied the correct uimage and all was well
Click to expand...
Click to collapse
Thanks for the reply. I double checked it and I did download the latest SD version (SD-041811c) but it didn't work. I then tried the SD-040411 version and it worked fine. Note that I didn't clear the cache either time.

wrdoss said:
I had the same thing happen to me yesterday , and then realized that I had downloaded the wrong OC version - the emmc instead of the sd. I reflashed the CM7 build, then copied the correct uimage and all was well
Click to expand...
Click to collapse
Did you replace the uImage file from the 040411 version? Or the latest experimental build which is 041811C?
My CM7 was installed using verygreen's size agnostic installer, and all the while it was easy to install the OC kernels by just swapping uImage.
But 4/18C can't be installed by just swapping the uImage unlike all the previous kernels. If you do that it will hang just before the bootanimation appears.
Can anyone please explain how to install the 4/18C kernel to CM7 (nightly 41) running on SD card?

robot8 said:
Did you replace the uImage file from the 040411 version? Or the latest experimental build which is 041811C?
My CM7 was installed using verygreen's size agnostic installer, and all the while it was easy to install the OC kernels by just swapping uImage.
But 4/18C can't be installed by just swapping the uImage unlike all the previous kernels. If you do that it will hang just before the bootanimation appears.
Can anyone please explain how to install the 4/18C kernel to CM7 (nightly 41) running on SD card?
Click to expand...
Click to collapse
This is the exact same setup and problem that I experienced.

robot8 said:
Did you replace the uImage file from the 040411 version? Or the latest experimental build which is 041811C?
My CM7 was installed using verygreen's size agnostic installer, and all the while it was easy to install the OC kernels by just swapping uImage.
But 4/18C can't be installed by just swapping the uImage unlike all the previous kernels. If you do that it will hang just before the bootanimation appears.
Can anyone please explain how to install the 4/18C kernel to CM7 (nightly 41) running on SD card?
Click to expand...
Click to collapse
Have you tried posting this issue in the development forum?

Yes I did, and it seems there's no easy way. Need to install the SDK and then adb push system from the extracted zip file then swap uImage.
edit: not that it's all that difficult but compared to just swapping uImage previously, well I'll probably wait a bit for the final update. Seems to be some issues with wi-fi.
edit:
Well I couldn't wait so I went ahead and popped 4/18C in. No issues so far.

robot8 said:
Yes I did, and it seems there's no easy way. Need to install the SDK and then adb push system from the extracted zip file then swap uImage.
Click to expand...
Click to collapse
Well that is unfortunate because you have to reinstall the OC kernal every time you install a new CM7 version.

I think I am going to stay with the latest CM7 nightly build and the SD-040411 OC kernel. I ran it some last night and it appeared stable and I didn't experience any of the video issues that people were reporting.

jmak10 said:
Well that is unfortunate because you have to reinstall the OC kernal every time you install a new CM7 release.
Click to expand...
Click to collapse
All this while when you update CM7 you'd need to reinstall the OC kernel, but it was way easy as you just needed to swap uImage. But not with the new test kernels.
Correct me if I'm wrong but I suppose once it's finalized I suppose the system stuff will be merged with main CM7 and we'd be able to swap OC kernels just like before.

robot8 said:
All this while when you update CM7 you'd need to reinstall the OC kernel, but it was way easy as you just needed to swap uImage. But not with the new test kernels.
Correct me if I'm wrong but I suppose once it's finalized I suppose the system stuff will be merged with main CM7 and we'd be able to swap OC kernels just like before.
Click to expand...
Click to collapse
I don't have any idea what is being planned but I hope the developers make this as easy as it was before.

I'm in the same boat. I know wiping the cache will fix it but I'm just stuck again if I reboot.
I'm running CM7, I wiped system, data, cach, dalvik, and did a factory reset before flashing.
Right now I'm just making sure my batter never runs out because reboot = wipe cache and then waste my time restoring apps and settings

[RECOVERY][MOD][O2X][02-Nov-2011] Clockwork 5.0.2.7.111102

First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, version compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the LG Optimus 2X. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for most of the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-p990.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-p990.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
Now that Koush added backup support for internal/external sdcard I'll only build onw version (exernal sdcard in file lists) If you really want one build for internal sdcard, let me know and I'll do it.)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
As of this version, I'll only be providing one img file. It seems 5.0 has native support for internal/external SD card. Need confirmation of this, as I don't have this phone myself.
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Reverted back to ext3 for the meantime, since I didn't get ext4 working. Any suggestions are welcome!
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Two versions. One for internal storage and one for external microSD card (same zip file)
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.

This recovery bricked my phone

Hell_97 said:
This recovery bricked my phone
Click to expand...
Click to collapse
Anybody with same problem?

Hell_97 said:
This recovery bricked my phone
Click to expand...
Click to collapse
How did you install it? Can you still boot into whatever ROM you were running before? What happens when you start to phone now? Exactly what did you do? Please be a bit more specific so we might have a chance of helping you fix the problem.
Sent from my Nexus S using Tapatalk

Updated recovery.fstab to allow ext4. Might work better. Try at your own risk.

zyonee said:
How did you install it? Can you still boot into whatever ROM you were running before? What happens when you start to phone now? Exactly what did you do? Please be a bit more specific so we might have a chance of helping you fix the problem.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I tried to change kernel and the device is locked on the LG screen, I solved with smartflash.

that's not even related to this recovery mod.... I had the same problem with "original" 4.0.0.5 and after flashing vorkernel had the same problem.... I solved it with restoring nandroid backup. The kernel does not work for me with CM latest nightlies.

So can someone please test the newest recovery version? I'd like to know if ext4 works as it should.
Sent from my Nexus S using Tapatalk

klubipiff said:
that's not even related to this recovery mod.... I had the same problem with "original" 4.0.0.5 and after flashing vorkernel had the same problem.... I solved it with restoring nandroid backup. The kernel does not work for me with CM latest nightlies.
Click to expand...
Click to collapse
I installed vork kernel with "original" 4.0.0.5 on CM53 without problem.

To have ext4 you also need a kernel with ext4 support (correct me if im wrong) So which kernel has the ext4 support?
Sent from my Optimus 2X using XDA App

peewster said:
To have ext4 you also need a kernel with ext4 support (correct me if im wrong) So which kernel has the ext4 support?
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
Please stay on topic. This thread is about the modified ClockworkMod recovery and possibly its ability to work with ext4, not about custom ROMs or kernels...
Sent from my Nexus S using Tapatalk

If you've changed recovery.fstab, then it should be OK with EXT4, that's all I had to do with my releases to get it working.

zyonee said:
Please stay on topic. This thread is about the modified ClockworkMod recovery and possibly its ability to work with ext4, not about custom ROMs or kernels...
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Just asking because it looks nice but then i need to know wich kernels i can use?
Sent from my Optimus 2X using XDA App

Just flashed the recovery, all ok. The confirmation menu is much better now with just 1: no line
Sent from my Optimus 2X using XDA App

peewster said:
Just flashed the recovery, all ok. The confirmation menu is much better now with just 1: no line
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
Very glad to hear it. Wipe, nandroid backup/restore and ext4, did you test all these?
Sent from my Nexus S using Tapatalk

peewster said:
Just asking because it looks nice but then i need to know wich kernels i can use?
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
Well, see, the problem isn't really which zips you can or cannot flash. It's more about whether you can flash at all or if ext4 works properly. If nandroid backup and restore works or not. I'm fairly certain that all kernels can be flashed, but how well they work is something that I don't see would be affected by this recovery.
Sent from my Nexus S using Tapatalk

Hmm doesnt seem to wipe correctly...after doing a clean install of CM7 I still have all my old apps and settings. That said I did install it in an odd way (replaced Paul's recovery with it and ran his .bat script). What is the easiest method to flash recovery?

That is the easiest way.

xAdaM-- said:
Hmm doesnt seem to wipe correctly...after doing a clean install of CM7 I still have all my old apps and settings. That said I did install it in an odd way (replaced Paul's recovery with it and ran his .bat script). What is the easiest method to flash recovery?
Click to expand...
Click to collapse
Exactly how did you wipe? Did you use the "format" commands in "mounts and storage" or did you use "clear data/factory reset"? I'm starting to think that the format command is not working.

zyonee said:
Exactly how did you wipe? Did you use the "format" commands in "mounts and storage" or did you use "clear data/factory reset"? I'm starting to think that the format command is not working.
Click to expand...
Click to collapse
Didn't go near the format command in mount and storage. In the specific "Wipe" menu --> tried factory reset etc/cache partition...all seemed to work way to quickly to actually be doing anything. Like I'd select wipe data/factory reset, hit yes and it would say completed after like 1 second (usually takes more than 5 with regular recovery). And then of course when I rebooted my device my data was still there, nothing wiped (except perhaps dalvik, but who knows).

[MOD] EXT4All Continued + Now with TWRP 2.3 Support

The purpose of this thread is to host a location and continue support for a really neat ext4 mod.
IMPORTANT: If you flash the no data limit mod you need to do it after every update or your data, which won't be lost will be hidden by the contents of the data data partition.
I'm going to keep this brief. The original thread was closed so I wanted to have a new location where everyone can find the files. But this is a new thread for Jermaine151's and my EXT4all mod.
Below is the original thread which already has a lot of useful information:
http://forum.xda-developers.com/showthread.php?t=1315372
Here is where you can find most of if not all the EXT4All files:
http://dinc.does-it.net/EXT4_Mods/
Sorry this thread isn't too organized but I threw one together so people could post on it with their comments.
This mod should work on all AOSP ROMs including ICS ROMs and MIUI. It's been confirmed on CM7 and MIUI but I've also tested on CM9. It should also work on all Sense ROMs and does work on every Sense ROM I've tested. Be sure to flash a newer version of the gingertiny kernel if you use a Sense ROM as the kernel version flashed to add ext4 compatibility is out of date.
V2 Mods with TWRP 2.3+ support and proper support for filesystem tweaks for ROMs that are already set to use ext4 found below:
V2 EXT4All Mods
FAQ
Q. How do I know if the ext4 mod(s) worked?
A. The best way is to do the following from terminal:
su
mount | grep /data
It should show a line with /data and ext4 and, if it has the no data limit, also a line with /data/data and ext4. If you're on an ICS/JB ROM it will show ext4 anyways. The best way to tell with the new version of the mod is to see if noauto_da_alloc shows in the results of the above commands.

Hey tiny, thanks for opening this btw. Wasn't sure if I should post here or on ur kernal thread but my girls dinc was having the data limit problem so I wiped cache and dalvic, flashed ext4 no data limit normal dalvic then flashed ur newest kernal (3/11 date). And I have been having the hardest time keeping her phone stable. I've tried every governor sav2, interactivex, ondemand, even sa, tried deadline, sio schedulers, even tried raising the voltages to a post u had on ur kernal thread, page 85 or something (wasn't sure if I should set the min and max of the voltages for the same thing, but that's wat I did). But she still says its very unstable. She's running stock+ 3.01 and she DOES have a cheap ebay battery in her phone, not quite sure how much that plays a role in the problem. She's at work right now so I can't pull any logs, but I know ull probably need a logcat? Or I dunno. If u could gimme directions on anything I should post to assist u. And I'm not overclocking at all for the record. On stock kernal she never had any stability issues, uptime of 200 hours+. But urs is definitely snappier and that damned data limit is the main reason y I even switched her over to begin with. Thanks tiny in advanced for everything u do!!!
Sent from my ADR6400L using xda premium

I'd prefer the kernel thread.
And I'll need a last_kmsg. Just copy /proc/last_kmsg with root explorer or another file explorer and attach it to a post on the kernel thread. Since you most likely eliminated undervolting by using the voltages on page 85 of the kernel thread, then it's possible the battery has an effect. I've heard that poorly made batteries can cause issues that stock batteries don't have so further deviation from stock may have an influence. Either way, I'll look at that log once you get it. Make sure not to battery pull until you can copy that log and try to do it within 24 hours of the last reboot to be safe.

the following thread contains very simple and plain english directions for using this MOD. it helped me, and it was my first time rooting. Thanks also to tiny4579 for posting this new thread.
http://forum.xda-developers.com/showthread.php?t=1488351

Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?

funkpod said:
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
Click to expand...
Click to collapse
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2

I've been running various ICS roms and switched back to Warm rev 58. Upon installing the latest kernel and the Ext4 mod. I am unable to install apps. Any idea what may be causing this. I wasn't sure if it was the rom or not do I did an update with SVN and installed that with the same results. I have a nandroid with just the rom and all the apps I want, but would like to overclock and the stock kernel won't allow. And would also like to be able to install a new app should one arise.
Sent from my HTC Droid Incredible using xda premium

tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks, how do I generate the logcat?
Sent from my Incredible.
Aw yeah.

Ok. It's not the kernel. Installed the most recent and everything is fine. Installed the ext4 with dalvik moved before that and rebooted and apps were missing and it wouldn't let me install new apps and some of my previously installed apps were missing. When I tried to install them it said it was going to replace an existing app and then said app not installed.
Any ideas???
Sent from my HTC Droid Incredible using xda premium

tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...

funkpod said:
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
Click to expand...
Click to collapse
Sorry I just dont have time tonight to explain. Maybe tomorrow.
Sent from my Galaxy Nexus using Tapatalk 2

hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?

funkpod said:
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
Click to expand...
Click to collapse
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?

funkpod said:
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
Click to expand...
Click to collapse
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended

Sirknifealot said:
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Click to expand...
Click to collapse
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?

funkpod said:
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
Click to expand...
Click to collapse
If you're wiping I don't see the point of fix permissions as it will fix it back to what it already probably is. I haven't fixed permissions in a while flashing ROMs and I've been ok. Force closes that I got that made me try fix permissions then weren't fixable with fix permissions anyway.
I would wipe, flash ROM, flash kernel if desired, then mod. Though if it's a sense ROM I would switch the order of kernel and mod flashing. So really you can do: ROM, ext4all mod, kernel after a wipe if you choose to wipe to fix your issue.

hey, flashed over to RC3! so far so good, slowly adding things back! will let everyone know how it goes!

Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...

omniatic said:
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
Click to expand...
Click to collapse
No, if you actually format the device like when the system runs the format command the filesystem will be ext4. However in your example of CM9 the ramdisk mounts data and cache as ext4. This will actually have a minor improvement over ext3. It'd still be an ext3 filesystem but loaded as ext4 so there's minimal performance gains.
In reality any time you flash a ROM or a boot.img type kernel (not any of mine) you will use the ramdisk of the ROM and reverse part of the effects. But since ROMs like CM9 and newer CM7 versions mount as ext4 you'll still see data and cache showing as ext4. Make sense? I never really did explain it properly before I think.

[RECOVERY] TWRP 2.6.0.0 Flashable ZIP

This thread serves the purpose of providing a flashable ZIP file for TWRP that can be flashed in CWM or an older TWRP.
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, some of the changes in 2.6.0.0 will likely not be visible with your custom theme.
- Can encrypt a backup to prevent theft of private data from your backup files
- Updated graphics / icon courtesy of shift
- Updated exFAT to latest commits
- Fixed a problem with Samsung TouchWiz decryption
- Update SuperSU binary
- Fixed saving of backup partitions list
- Fixed saving of last used zip install folder
- Fixed backup of datadata on devices that use a separate partition for datadata
- Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
- Fixed some problems with partitioning a SD card
- Various other bug fixes and tweaks
DOWNLOAD: TWRP-2.6.0.0-olympus.

Thanks!
=]

I know it's all based on personal preferences but I was wondering if anyone can give me their opinions on which in their point of view is better? This version of twrp or the current version on cwm. I have done my research on the two but was wondering in the case of the Atrix which do people prefer.
Sent from my MB860 using xda app-developers app

If you have a lot of files and folders (like I do) you will love the ability to easily browse files in TWRP. In CWM pressing the volume key is a nuisance.
Being able to name the backup within TWRP is also very helpful.
I think CWM is simpler. If your touchscreen breaks you can still flash ROMs.
For the average user TWRP is probably the better choice. I have used it for a few months with no issue.

Thanks a lot

Thank you very much atrix4g18! :good:

great job ty

May I ask how I install it over CMW? Don't want to brake anything.
Thx in advanced.
Sent from my MB860 using Tapatalk 2

DowJonesARG said:
May I ask how I install it over CMW? Don't want to brake anything.
Thx in advanced.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
CWM? You just flash it. Select the zip like it was a ROM. You don't need to wipe anything.

atrix4g18 said:
CWM? You just flash it. Select the zip like it was a ROM. You don't need to wipe anything.
Click to expand...
Click to collapse
So, I can Flash it with CMW? Ok. Thx.
Sent from my MB860 using Tapatalk 2

Yes, you can. Or install the Goo Manager from the Market and install It automatically.

nozorrog said:
Yes, you can. Or install the Goo Manager from the Market and install It automatically.
Click to expand...
Click to collapse
Which defeats the purpose of this flashable zip.

Guys guys! Don't fight over me, it makes me blush:laugh:
Just installed with CRW, works like a charm. Thx for the help!
Cheers:good:

I don't know if there is any huge change from previous recovey...but i feel as a user that is full wipe make this time critical (not ver much). in browsing zip for flashing it always go to root menu...where previous recovery stay on that page where i left. and the lockscreen very much anoying to me....
thanks

is it possible to add scroll by volume keys??

aaurnab said:
is it possible to add scroll by volume keys??
Click to expand...
Click to collapse
Ask in the thread for TWRP. I just package a flashable zip so I can't answer your question.

atrix4g18 said:
Since the other thread hasn't been updated and I posted the last build to it I decided to make a thread here.
CHANGELOG for 2.5.0.0:
DOWNLOAD: TWRP-2.5.0.0-olympus.
Click to expand...
Click to collapse
Do you know if I can have the new one for Atrix ? Thank you very much.
http://forum.xda-developers.com/showthread.php?t=2231049
RECOVERY] TWRP 2.6.0.0 touch recovery [2013-07-11]

sintoo said:
Do you know if I can have the new one for Atrix ? Thank you very much.
http://forum.xda-developers.com/showthread.php?t=2231049
RECOVERY] TWRP 2.6.0.0 touch recovery [2013-07-11]
Click to expand...
Click to collapse
Yes you could.
If you want to be safe with the next TWRP update, you should use goomanager.

Tested: 2.6.0.0 and installed with gooManager:
openrecovery-twrp-2.6.0.0-olympus.img /devs/OpenRecovery/olympus 1cde61c469fe949d2f113ba2047a8546
http://goo.im/devs/OpenRecovery/olympus/
NOTE: inside goomanager (market), click: Flash Rom. Select "I don't have one. Install for me a recovery". Confirm (OK): openrecovery-twrp-2.6.0.0-olympus

sintoo said:
Do you know if I can have the new one for Atrix ? Thank you very much.
http://forum.xda-developers.com/showthread.php?t=2231049
RECOVERY] TWRP 2.6.0.0 touch recovery [2013-07-11]
Click to expand...
Click to collapse
Sorry this is late. OP updated.
DOWNLOAD: TWRP-2.6.0.0-olympus.

[L3] [MOD] CWM recovery for e400 [CM/MIUI/SDMERGE]

Hi to all!! I've done a little modification to the original CWM to add support to the secondary partition we use in every CM/MIUI etc...
All is done! Now works without an error of mounting "/sd-ext" due to an "unknown volume type!!" in recovery.fstab.
I also included the recovery for the SDMerge and also a linux script. Sorry, but the archive is too big to post it here on xda so i had to upload it on 4shared.
Requirements:
1) Rooted phone (obviously!!)
Instuctions Windows:
1) Download the package from 4shared
2) Extract it in any folder you prefer
3) Make sure you have USB Debugging on
4) Run "CWM-Installer.bat" as administrator
5) Hit enter
6) Wait, if it takes too long simply disconnect the device and reconnect it immediatly.
5) Enjoy the new recovery!!:victory:
Instructions Ubuntu/Debian/Mint:
1) Download the package from 4shared
2) Extract it
3) Make sure you have the sdk properly installed with adb (if not check here: http://forum.xda-developers.com/showthread.php?t=2100673 )
4) Run the script by typing
Code:
./CWM-Installer.sh
5) Enjoy the new recovery
The script is for stock roms but it works well even on CM or CM-Based ROMs so don't worry if you get errors, it's normal.
If you want your old recovery back you can open the CWM-Installer.bat with an editor and replace this
Code:
Files\adb push Files\recovery.img /data/local/recovery.img
With this:
Code:
Files\adb push Files\[COLOR=Red]CWMrecovery_orig[/COLOR].img /data/local/recovery.img
or if you want the recovery for the SDMerge just replace:
Code:
Files\adb push Files\recovery.img /data/local/recovery.img
with this:
Code:
Files\adb push Files\SDmergerecovery.img /data/local/recovery.img
And then run the script again.
Feel free to post comments!!
Download here:
http://www.4shared.com/archive/8HmnogYQ/CWM-Installer-E400tar.html

wow, long time no see...
keep it up buddy

yayakuya said:
wow, long time no see...
keep it up buddy
Click to expand...
Click to collapse
Thanks yaya, I was busy with work and home and I haven't internet at home so I can't download the huge GBs of a repo.

Works like said great job keep it up buddy!

Cobmaster said:
Hi to all!! I've done a little modification to the original CWM to add support to the secondary partition we use in every CM/MIUI etc...
All is done! Now works without an error of mounting "/sd-ext" due to an "unknown volume type!!" in recovery.fstab.
Requirements:
1) Rooted phone (obviously!!)
Instuctions:
1) Download the attachment
2) Extract it in any folder you prefer
3) Make sure you have USB Debugging on
4) Run "CWM-Installer.bat" as administrator
5) Hit enter
6) Wait, if it takes too long simply disconnect the device and reconnect it immediatly.
5) Enjoy the new recovery!!:victory:
The script is for stock roms but it works well even on CM or CM-Based ROMs so don't worry if you get errors, it's normal.
IT DOESN'T WORK WITH SDMerge MOD!!!
If you want your old recovery back you can open the CWM-Installer.bat with an editor and replace this
Code:
Files\adb push Files\recovery.img /mnt/extra-sd/recovery.img
With this:
Code:
Files\adb push Files\[COLOR=Red]CWMrecovery_orig[/COLOR].img /mnt/extra-sd/recovery.img
And then run the script again.
Feel free to post comments!!
Click to expand...
Click to collapse
i created a flashable zip for the recovery her it is please thank me.:good:

jeffreyvh said:
i created a flashable zip for the recovery her it is please thank me.:good:
Click to expand...
Click to collapse
I used the script written a long time ago for who has only the device rooted but hasn't the recovery installed... Btw good job!

@Cobmaster, could you make similar recovery specifically for data2sdext on stock rom?
I already create similar mod based on this tutorial and it works flawlessly but lack of support from recovery (i.e can't backup/restore from sd-ext)

andwie said:
@Cobmaster, could you make similar recovery specifically for data2sdext on stock rom?
I already create similar mod based on this tutorial and it works flawlessly but lack of support from recovery (i.e can't backup/restore from sd-ext)
Click to expand...
Click to collapse
Are you talking about e405? Or you want a recovery modded to support the partition table in stock rom?
I think I can but I need more specs of the partitioning you use for the sd. I need the specific "/dev/block/mmcblk***" of the partitions in the sd. Nothing more (and a little bit of time obviously!).

Cobmaster said:
Are you talking about e405? Or you want a recovery modded to support the partition table in stock rom?
I think I can but I need more specs of the partitioning you use for the sd. I need the specific "/dev/block/mmcblk***" of the partitions in the sd. Nothing more (and a little bit of time obviously!).
Click to expand...
Click to collapse
it's for stock rom in E400 (E400 and E405 shared the same partitioning system though).
it's the same partition structure created by CWM recovery :
swap -> /dev/block/mmcblk1p1
ext4 -> /dev/block/mmcblk1p2 -> mounted as /data
vfat -> /dev/block/mmcblk1p3
thanks again for your effort

andwie said:
it's for stock rom in E400 (E400 and E405 shared the same partitioning system though).
it's the same partition structure created by CWM recovery :
swap -> /dev/block/mmcblk1p1
ext4 -> /dev/block/mmcblk1p2 -> mounted as /data
vfat -> /dev/block/mmcblk1p3
thanks again for your effort
Click to expand...
Click to collapse
Here it is, to flash it use my script replacing the recovery.img with the one attached and report if it works or not.
Btw, are you sure that the "/data" partition is ext4? Because if it's wrong the recovery doesn't mount it.

Very sorry for the very late reply, I just had the time to test your new recovery (I had to create flashable zip for it since the script didn't work) and it work perfectly.
Now we have alternative to increase data partition without having to edit apps like gellmar's StockMergE400, means it will be compatible with all stock-based rom :victory:
Thanks again @Cobmaster :good:

Don't worry about it. It's very pleasing to see that it works.

hi!
 @Cobmaster, could you make recovery for E405?
after make SDMerge MOD from '' lgl3e405.blogspot.com/2013/05/sd-merge-mod-for-e405-under-testing.html''. i can't restore my backup and i can't mount internal sd.
can you help me. Sorry for my english. i am not good

dricoarmani said:
hi!
@Cobmaster, could you make recovery for E405?
after make SDMerge MOD from '' lgl3e405.blogspot.com/2013/05/sd-merge-mod-for-e405-under-testing.html''. i can't restore my backup and i can't mount internal sd.
can you help me. Sorry for my english. i am not good
Click to expand...
Click to collapse
Could you give me the link of the recovery for e405?
and if you can give me the partition layout of your phone using this: https://play.google.com/store/apps/details?id=com.cls.partition
Or this:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo

Cobmaster said:
Could you give me the link of the recovery for e405?
and if you can give me the partition layout of your phone using this: https://play.google.com/store/apps/details?id=com.cls.partition
Or this:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo
Click to expand...
Click to collapse
How about L5 E455 users? what do you think would happen if i try this recovery on e455?
will it brick it for good ?
-Rant
most of my previous droid phones were SE and then Sony and i never had to deal with any of this
int mem/int sd/ext sd crap. just int mem and sdcard .period
now i've two Chinese tablets and a sammy and now this e455 cuz i needed an affordable dual sim.
man, it's a clusterF. most my backups wont work cuz they've restored on the wrong partition and
yesterday i got some error message like "this dosnt work on emulated storage" and i was like wtf?
/Rant off

Axims said:
How about L5 E455 users? what do you think would happen if i try this recovery on e455?
will it brick it for good ?
-Rant
most of my previous droid phones were SE and then Sony and i never had to deal with any of this
int mem/int sd/ext sd crap. just int mem and sdcard .period
now i've two Chinese tablets and a sammy and now this e455 cuz i needed an affordable dual sim.
man, it's a clusterF. most my backups wont work cuz they've restored on the wrong partition and
yesterday i got some error message like "this dosnt work on emulated storage" and i was like wtf?
/Rant off
Click to expand...
Click to collapse
It will probably get bricked. It's a matter of kernel...
Sent from my LG-E400 using xda premium

Cobmaster said:
It will probably get bricked. It's a matter of kernel...
Sent from my LG-E400 using xda premium
Click to expand...
Click to collapse
hi all,
i have a problem with sdmerge roms. when i install a rom with sdmerge wipe doesn't work.
in cwm i see wipe done succesfully, but nothing happens, and when i reboot i have the same background, same apps etc...
with this update i could fix the problem?

lomax84 said:
hi all,
i have a problem with sdmerge roms. when i install a rom with sdmerge wipe doesn't work.
in cwm i see wipe done succesfully, but nothing happens, and when i reboot i have the same background, same apps etc...
with this update i could fix the problem?
Click to expand...
Click to collapse
only use gellmar recovery, because it is fixed for sdmerge

kien_vip said:
only use gellmar recovery, because it is fixed for sdmerge
Click to expand...
Click to collapse
Where can i find gellmar recovery?
Do you mean step1?
Inviato dal mio LG-E400 con Tapatalk 2

lomax84 said:
Where can i find gellmar recovery?
Do you mean step1?
Inviato dal mio LG-E400 con Tapatalk 2
Click to expand...
Click to collapse
it contain in step 2 or you can see it on some sdmerge rom