[Recovery] RA Revamped for Iconia HC&ICS

drellisdee · Jan 23, 2012

pimpmaneaton said:
Very nice addition to the A500, thanks for the hard work.

Np. It only took me about 30 test builds to get the touch stuff working the way I wanted

Im glad you are enjoying it.

pimpmaneaton · Jan 23, 2012

drellisdee said:
Np. It only took me about 30 test builds to get the touch stuff working the way I wanted

Im glad you are enjoying it.

Yeah I'm about 28 builds so far getting TWRP 2.0 up and going, but has been really slow lately, dev on TWRP side is really caught up getting touch driver working properly for HP touchpad and CM7.

internetpilot · Jan 23, 2012

drellisdee said:
It works I developed and tested this on my own a500 I just got a few days ago. The beta restore CWM backup option only works for a true sdcard not the usb_drive. The amon ra backup & restore options will work with both usb_drive and sdcard fyi.

Awesome! Thanks a TON for this. Really, it's nice to finally have a recovery that can be discussed or even...gulp!...on XDA! Very slick and very nice!

I like RA better than CWM anyway -- it's what I've used on my HTC EVO 4G from the very beginning.

And sorry, I didn't mean to imply that a restore wouldn't work, it's just that was a problem with several previous CWM offerings for the A500, and no one had posted that they had tried a restore with your recovery yet. But I'll take your word for it, and no offense was meant!

Thanks again for all your hard work!

themono · Jan 24, 2012

Fantastic job, thanks for your hard work. Recovery working wonderfully here, installed via kjy's flashable zip (also thanks to you!).

As an aside - is it recommended to upgrade the EXT3 FS to EXT4 on the iconia?

drellisdee · Jan 24, 2012

themono said:
Fantastic job, thanks for your hard work. Recovery working wonderfully here, installed via kjy's flashable zip (also thanks to you!).

As an aside - is it recommended to upgrade the EXT3 FS to EXT4 on the iconia?

Its ext4 by default. There is another namless recovery that seems to mess up cache when wiped by formatting cache as ext3 with data writeback when it should be be ext4 and data ordered by default. If you want to repair it force the the full format to ext3 option on cache in this recovery then pick the upgrade to ext4 on cache. Use ext4 if possible. To check if your cache is set ext3 incorrectly from wiping in cwm do "adb shell mount" in recovery and see.

birkoffsjunk · Jan 24, 2012

oh! so many thanks you's for this!!! Finally free of thor's crap.

I got 1 feature request, can you add the option to install rom from internal storage?

kjy2010 · Jan 24, 2012

drellisdee said:
Its ext4 by default. There is another namless recovery that seems to mess up cache when wiped by formatting cache as ext3 with data writeback when it should be be ext4 and data ordered by default. If you want to repair it force the the full format to ext3 option on cache in this recovery then pick the upgrade to ext4 on cache. Use ext4 if possible. To check if your cache is set ext3 incorrectly from wiping in cwm do "adb shell mount" in recovery and see.

edit: nvm...fixed it

ty

dincdoes.me · Jan 24, 2012

So do can we expect rom manager anytime soon?

I only ask so we can get themes kernels and roms in one location from other forum sites?

Sent from my A500 using Tapatalk

ZsDaniel · Jan 24, 2012

Can anyone post a pic?

drellisdee · Jan 24, 2012

birkoffsjunk said:
oh! so many thanks you's for this!!! Finally free of thor's crap.

I got 1 feature request, can you add the option to install rom from internal storage?

Ill take a look at installing zips from /data/media.

joe9002 · Jan 24, 2012

drellisdee said:
Its ext4 by default. There is another namless recovery that seems to mess up cache when wiped by formatting cache as ext3 with data writeback when it should be be ext4 and data ordered by default. If you want to repair it force the the full format to ext3 option on cache in this recovery then pick the upgrade to ext4 on cache. Use ext4 if possible. To check if your cache is set ext3 incorrectly from wiping in cwm do "adb shell mount" in recovery and see.

Um very important information to no i think is this the same in the latest? Doesn't matter now any way we have a way of installing ROMs that is not breaking laws.
Thank you for the hard work.

Moscow Desire · Jan 24, 2012

Thanks for the good work. It seems to have fixed my issue which has bothered me for a few days (inability to flash 70% of roms), I can only guess old data was not getting cleaned properly.

However;

1) touch buttons go crazy on occassion. Random inputs not assigned. I saw this on Thor's recovery also.

2) where is the option to wipe/format Flexrom? I don;t see it in the Wipes menu,

3) In the Wipes Menu;
(Data/factory Reset)
(Data)
(cache)
Dalvak)

I chose only data,cache, Dalvak
Then Format all to EXT3
Then Update to EXT4

Flashed rom, rebooted. All ok

Above procedures correct? Or did I miss something?

4) In the "messages" after formatting, it stated I can flash a rom, or restore a nand Backup. Then it mentioned to do a "manual /data wipe" after restoring??

What exactly do you mean?

5) Now that things are formatted, when we flash new roms, should we repeat the above steps again? Or will the 3 wipes work ok. Would be nice to know.

Thanks for the great work!

spoupard · Jan 24, 2012

Help Needed! I tried to reformat my /data partition to EXT4. Now, no matter what I do, /data will not mount. if I try to mount /data or wipe /data or format /data, I get an error message that says "E:Can't mount /dev/block/mmcblk0p8 (File exits)."

I have tried rebooting with no luck. If I let it boot, it asks for a password. I tried a hard reset with no luck. I tried reflashing my ROM (using Epiphany) with no luck.

Anyone have any suggestions?

Moscow Desire · Jan 24, 2012

spoupard said:
Help Needed! I tried to reformat my /data partition to EXT4. Now, no matter what I do, /data will not mount. if I try to mount /data or wipe /data or format /data, I get an error message that says "E:Can't mount /dev/block/mmcblk0p8 (File exits)."

I have tried rebooting with no luck. If I let it boot, it asks for a password. I tried a hard reset with no luck. I tried reflashing my ROM (using Epiphany) with no luck.

Anyone have any suggestions?

Not sure I can help. but I noticed, if you follow the steps for the FIRST TIME install, (wipes as I listed below, Format all to EXT3, then Upgrade to EXT 4

Then after flashing a rom, you boot to recovery, and try to do a format EXT 3 or 4 on any item, it gives you that same message repeatedly, no matter what other option you chose. (it went crazy )

I rebooted back to recovery, then just did Wipes

Factory Data/reset
Data
Cache
Dalvak
Sd card/android secure
System

Then flashed my rom and all was ok

It seems, that once you do the initial procedure, you do not need to go back and format. So far the wipes above seem to work.

The reason you get a password, is that you do not have an operating system more than likely.

drellisdee · Jan 24, 2012

Moscow Desire said:
Thanks for the good work. It seems to have fixed my issue which has bothered me for a few days (inability to flash 70% of roms), I can only guess old data was not getting cleaned properly.

However;

1) touch buttons go crazy on occassion. Random inputs not assigned. I saw this on Thor's recovery also.

2) where is the option to wipe/format Flexrom? I don;t see it in the Wipes menu,

3) In the Wipes Menu;
(Data/factory Reset)
(Data)
(cache)
Dalvak)

I chose only data,cache, Dalvak
Then Format all to EXT3
Then Update to EXT4

Flashed rom, rebooted. All ok

Above procedures correct? Or did I miss something?

4) In the "messages" after formatting, it stated I can flash a rom, or restore a nand Backup. Then it mentioned to do a "manual /data wipe" after restoring??

What exactly do you mean?

5) Now that things are formatted, when we flash new roms, should we repeat the above steps again? Or will the 3 wipes work ok. Would be nice to know.

Thanks for the great work!

1) Its the best I can do for now. You can always use the physical keys if you don't like the touch ones.

2) I left out wipe flexrom by accident I'll add it soon

3) To flash a rom you only need to wipe data and cache. Dalvik is contained inside of /data and is wiped when data is wiped. Normally you would NOT use the ext3|4 format menu as thats only there for advanced partitioning and is NOT needed to wipe at all.

4) you formatted /data, /cache & /system and your device will not boot up untill you restore a /system from a nandroid or flash a rom.

5) only needed item is wipe all for most setups as it will wipe data and cache and dalvik as it (dalvik) is contained inside of data. By default this is a quick rm -rf wipe that removes the contents of the file system but does not destroy the file system and recreate it. To enable a full destruction and reformat of a partition select the full ext wipe toggle option to on (beware as this will casue the loss of the contents of /data/media which is your internal sdcard.)

spoupard said:
Help Needed! I tried to reformat my /data partition to EXT4. Now, no matter what I do, /data will not mount. if I try to mount /data or wipe /data or format /data, I get an error message that says "E:Can't mount /dev/block/mmcblk0p8 (File exits)."

I have tried rebooting with no luck. If I let it boot, it asks for a password. I tried a hard reset with no luck. I tried reflashing my ROM (using Epiphany) with no luck.

Anyone have any suggestions?

Those are advanced options that most users shouldn't have a need for and shouldn't normally use. Your data should have already been ext4 and you tried to reupgrade it to ext4 and looks like you corrupted your /data partition. For reference the 1st page has a description of the menu items. Dont just go selecting every option if you dont know what it does.

To fix your blunder you will need to boot into my recovery and open adb shell.
This will cause loss of all data contained on /data which will lose your /data/media.

From adb shell

Code:

mount (this is to check data isn't mounted) if mounted use "umount data"

mke2fs -j -b 4096 /dev/block/mmcblk0p8
tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
e2fsck -fy /dev/block/mmcblk0p8

After this is done your file system on /data will be fixed.

spoupard · Jan 24, 2012

Moscow Desire said:
Not sure I can help. but I noticed, if you follow the steps for the FIRST TIME install, (wipes as I listed below, Format all to EXT3, then Upgrade to EXT 4

Then after flashing a rom, you boot to recovery, and try to do a format EXT 3 or 4 on any item, it gives you that same message repeatedly, no matter what other option you chose. (it went crazy )

I rebooted back to recovery, then just did Wipes

Factory Data/reset
Data
Cache
Dalvak
Sd card/android secure
System

Then flashed my rom and all was ok

It seems, that once you do the initial procedure, you do not need to go back and format. So far the wipes above seem to work.

The reason you get a password, is that you do not have an operating system more than likely.

Thanks for your help, but my problem now is that the /data partion is gone and I cannot seem to get it back. I have tried to repartition the sdcard and that doesn't help. No matter what I try to do, I always get a message saying "E:Cant mount /dev/block/mmcblk0p8 (File exists) Error mounting /data!"

---------- Post added at 12:28 PM ---------- Previous post was at 12:24 PM ----------

Moscow Desire said:
Not sure I can help. but I noticed, if you follow the steps for the FIRST TIME install, (wipes as I listed below, Format all to EXT3, then Upgrade to EXT 4

Then after flashing a rom, you boot to recovery, and try to do a format EXT 3 or 4 on any item, it gives you that same message repeatedly, no matter what other option you chose. (it went crazy )

I rebooted back to recovery, then just did Wipes

Factory Data/reset
Data
Cache
Dalvak
Sd card/android secure
System

Then flashed my rom and all was ok

It seems, that once you do the initial procedure, you do not need to go back and format. So far the wipes above seem to work.

The reason you get a password, is that you do not have an operating system more than likely.

drellisdee said:
2) I left out wipe flexrom by accident I'll add it soon

3) To flash a rom you only need to wipe data and cache. Dalvik is contained inside of /data and is wiped when data is wiped. Normally you would NOT use the ext3|4 format menu as thats only there for advanced partitioning and is NOT needed to wipe at all.

4) you formatted /data, /cache & /system and your device will not boot up untill you restore a /system from a nandroid or flash a rom.

5) only needed item is wipe all for most setups as it will wipe data and cache and dalvik as it (dalvik) is contained inside of data. By default this is a quick rm -rf wipe that removes the contents of the file system but does not destroy the file system and recreate it. To enable a full destruction and reformat of a partition select the full ext wipe toggle option to on (beware as this will casue the loss of the contents of /data/media which is your internal sdcard.)

Those are advanced options that most users shouldn't have a need for and shouldn't use. Your data should have already been ext4 and you tried to reupgrade it to ext4. There is an option in recovery to check the fs and it will tell you what it is. For reference the 1st page has a description of the menu items. Dont just go selecting every option if you dont know what it does.

To fix your blunder you will need to boot into my recovery and open adb shell.
This will cause loss of all data contained on /data which will lose your /data/media.

From adb shell

Code:

mount (this is to check data isn't mounted) if mounted use "umount data" mke2fs -j -b 4096 /dev/block/mmcblk0p8 tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8 e2fsck -fy /dev/block/mmcblk0p8

After this is done your file system on /data will be fixed.

Thanks. I'll give this a try. I'll have to download and install ADB first. Just to clarify, though, the reason I was trying to upgrade /data to EXT3 was because FS info showed that it was an EXT3 fs.

drellisdee · Jan 24, 2012

spoupard said:
Thanks. I'll give this a try. I'll have to download and install ADB first. Just to clarify, though, the reason I was trying to upgrade /data to EXT3 was because FS info showed that it was an EXT3 fs.

There is a option under ext3|ext4 menu to check the fs (1st option). If you have to change the format use the restore to ext3 option on the partition 1st then use the upgrade to ext4 option on that partition. Be warned those as it will erase all data contained on that partition in the process.

The error you got on upgrading was most like by having a data-writeback set on the partition. I'm positive cwm set my cache as ext3 and data-writeback after wiping it. Data-writeback flag causes a delayed write of the journal and will/can cause loss of data if a power loss occurs (reboot/freeze, call reboot from terminal etc). This is not ideal at all for a phone/tablet and the small performance gains you can get from it are at the expense of the integrity of your data.

Moscow Desire · Jan 24, 2012

Thanks for your reply. Sorry it was a long post.

Not sure if it's an issue or not, but, I've been flashing about 9 times so far tonight. (stripping apps from the 3.2.1)

Mostly it goes ok, but sometimes. I hit animationloop. (twice)

Both times I checked formatting in EXT3-EXT4, and it shows cache at EXT3, which is ok, but my System is EXT3 also. I upgrade it back to EXT4, and flashes normally. Not sure if it's my rom, although I haven't modified anything that would effect it.

Otherwise, I'm learning the tricks.

Good work.

drellisdee · Jan 24, 2012

Moscow Desire said:
Thanks for your reply. Sorry it was a long post.

Not sure if it's an issue or not, but, I've been flashing about 9 times so far tonight. (stripping apps from the 3.2.1)

Mostly it goes ok, but sometimes. I hit animationloop. (twice)

Both times I checked formatting in EXT3-EXT4, and it shows cache at EXT3, which is ok, but my System is EXT3 also. I upgrade it back to EXT4, and flashes normally. Not sure if it's my rom, although I haven't modified anything that would effect it.

Otherwise, I'm learning the tricks.

Good work.

On the anim loops while looping what does adb logcat tell you? Also when booted do adb pull /proc/config.gz and unzip the config.gz file it pulls and see if your rom kernel has rhe kernel config option of USE_EXT4_AS_EXT3 or something similar as I cant remember the wording. Also are you using any init.d scripts to alter the filesystems?

Moscow Desire · Jan 24, 2012

drellisdee said:
On the anim loops while looping what does adb logcat tell you? Also when booted do adb pull /proc/config.gz and unzip the config.gz file it pulls and see if your rom kernel has rhe kernel config option of USE_EXT4_AS_EXT3 or something similar as I cant remember the wording. Also are you using any init.d scripts to alter the filesystems?

Wasn't running adb at the time and really didn't think about it, But considering it's a factory rooted acer rom complete with factory flexrom, I'm tending to agree with you about the format. Seems 3.2.1 changes system to EXT3 then installs normally. But when you install the next version of the same rom, it loops. Setting it back to EXT4 results in a normal install.

Running no scripts. Stock 3.2.1 kernel.

If I get it to replicate again, I'll pull a logcat. This is what happened with Thors version, but I didn't have the option to fix it through recovery if I remember.

Never had this issue with 3.2 roms. Only after going to 3.2.1

[Recovery] RA Revamped for Iconia HC&ICS

Inactive Recognized Developer

Inactive Recognized Contributor

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

kjy2010

Guest

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Retired Senior Moderator

Member

Retired Senior Moderator

Inactive Recognized Developer

Member

Inactive Recognized Developer

Retired Senior Moderator

Inactive Recognized Developer

Retired Senior Moderator

Similar threads

Top Liked Posts