Database Info

[Q] Multi-Booting

Hi,
It just came into my mind. Since we can have custom recovery and android recovery also boots, can we have multi boot option in Defy as like in a PC's

Good question ..............i think there is no answer for this question

rvd_516 said:
Hi,
It just came into my mind. Since we can have custom recovery and android recovery also boots, can we have multi boot option in Defy as like in a PC's
Click to expand...
Click to collapse
some resources would have to be used by both ROMs..
with the current hacks it can't be done easily.
i guess some way of ramdisking the shared resources will have to be used.
basically, if you think about a hack for defy ask first:
can it be done in a completely open (=bootloader not locked) phone like nexus ?
if yes, ask:
is it WORKING?
if yes also, so maybe it can be done.
nevertheless, it's easy enough to create a script to backup & restore NANDROIDS.
but then every switch between roms will take like 25+ minutes, so it won't be a real multiboot.

Somebody at one point on the desire was working on something like this. Run rom from nand and other rom from sdcard.
Ephumuris.

ephumuris said:
Somebody at one point on the desire was working on something like this. Run rom from nand and other rom from sdcard.
Ephumuris.
Click to expand...
Click to collapse
I think there are two possibilities for this to happen: first of all, we should try NAND boot for the primary ROM, and try somehow to load the secondary ROM from the internal memory (it'll be faster than the SD Card, I think). The problem here would be allowing the bootloader to read from internal memory instead of NAND. I know this can be done based on the number of WinMo-Android and iOS-Android dual boot solutions, with a menu to choose which system to load, in the boot screen.
The second option is the method used by Wing Linux to run Android on old WinMo devices. In this method, you MUST boot in WinMo (or, in our case, in the primary ROM), then open the app that loads Android (the secondary ROM, for us). Android does NOT run emulated in this method, but, since the device can't dual boot directly, the app sends a signal for the device to restart running from the bootloader to the SD Card (for us, internal memory). This second option is, somehow, like the System Recovery app (not 2ndInit), that has an option that reboots directly into Recovery. So, if we can tell the phone to load from custom Recovery (which is, in fact, in internal memory, not in NAND), I think it's possible to make it load an entire ROM from the internal memory (without having to mount it everytime and waiting for the dalvik-cache to load).
However, it's surely a hard work to do.

Yes one from nand and one from sd card..........good......can we partition nand and use it both on the nand itself??

it should really work if we use virtual images or sdcard-partitions instead of system, data and cache partitions.
This can be changed in the init.rc-file(of 2nd-init).
The creator of the 2nd-init-bootmenu should implement this feature.

it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings

Epsylon3 said:
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Click to expand...
Click to collapse
Did you try it?

Epsylon3 said:
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Click to expand...
Click to collapse
even i like to know tht did u tried tht?

I managed to boot from virtual system,data and cache partitions with the 2nd-boot-option of bootmenu like ep3 said.
It was a bit difficult because android-init remounts /dev so the changes will be lost but now I found a way.
And: I got recovery working for the virtual system so you don't need to prepare your images, BUT: only the wipe and restore are working. "install zip" will still affect your real system.
My scripts need some testing but after that I will release a first version.

the multboot works for me i writed a cutsom boot sh and init.rc and woila WORKS!
NOT PUBLUC because it not works for all rom
---------- Post added at 04:59 PM ---------- Previous post was at 04:36 PM ----------
this is a dualboot rom
http://forum.xda-developers.com/showthread.php?t=1225179

So here is the first (very early) version of 2nd-boot:
http://www.multiupload.com/Z17M0WO3SU
Before continuing please make a backup of your phone!
Installation:
Just install it via CWM.
This will place the script in your 2nd-boot and replace the "CWM-Lastest"-script so it will install into the images. BUt can still use the "CWM-Stable" option for your normal system.
I've created 3 empty 300MB ext3-images for system,data and cache so you don't have todo that. Download them here:
http://www.multiupload.com/VY3U4IXRO1
Just copy the folder "fsimages" to your sdcard.
Usage:
After installing the update-zip and copying the files to the sdcard you can reboot into bootmenu, select "Lastest Recovery" and Restore an backup.
Please DO NOT install a ROM with a zip-file. Currently this will affect your real system.
After you restored your backup into the virtual file-system you can boot them with the 2nd-boot-option in bootmenu.
I successfully installed CM7.1 and MIUI-Pikachu-Edition in the virtual filesystem.

I uploaded a new version of my multiboot-script(v0.2)
changelog:
- "Install zip from SDcard" works now
- changed hook-method so it works with more ROM's(including ICS)
Download:
http://www.multiupload.com/UT0TLPR3ZW

m11kkaa said:
So here is the first (very early) version of 2nd-boot:
http://www.multiupload.com/Z17M0WO3SU
Before continuing please make a backup of your phone!
Installation:
Just install it via CWM.
This will place the script in your 2nd-boot and replace the "CWM-Lastest"-script so it will install into the images. BUt can still use the "CWM-Stable" option for your normal system.
I've created 3 empty 300MB ext3-images for system,data and cache so you don't have todo that. Download them here:
http://www.multiupload.com/VY3U4IXRO1
Just copy the folder "fsimages" to your sdcard.
Usage:
After installing the update-zip and copying the files to the sdcard you can reboot into bootmenu, select "Lastest Recovery" and Restore an backup.
Please DO NOT install a ROM with a zip-file. Currently this will affect your real system.
After you restored your backup into the virtual file-system you can boot them with the 2nd-boot-option in bootmenu.
I successfully installed CM7.1 and MIUI-Pikachu-Edition in the virtual filesystem.
Click to expand...
Click to collapse
Thanks for your work.
Did the 2nd android system boots from sdcard?

Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.

m11kkaa said:
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
Click to expand...
Click to collapse
Ask pedrodh http://forum.xda-developers.com/member.php?u=2098689
He can help.

Nice work, thanks i will add this soon, in the future bootmenu versions

m11kkaa said:
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
Click to expand...
Click to collapse
I released a dual boot version that uses 2nd-boot a few months back, hadn't have much time to improve it since.
I was using loop-back mount with /system and bind mount with /data since it's much more space efficient than just use an ext3 image.

Awesome job. I think u shud create a new thread for it. Dual booting cm7 and miui :O
Sent from my Moto Defy

Question about 4EXTRecovery

Hi everybody,
i am sure, that everybody except me seems to know how to install this awesome recovery...
I already renamed the zipfile to PG88IMG.zip, have put it into the root of the sd card, rebooted, the bootloader says 'parsing PG88IMG.zip', then nothing happens...
So, could someone please enlihgten me how to flash this thing? (if possible without creating an expensive brick ;-)) thanks a lot

Who told you to do that?
EDIT:
This should be a one click zip.
http://forum.xda-developers.com/showthread.php?t=1130004

Hi,
wow, that was fast ;-) thanks a lot...
Hmm, no, i already installed ClockworkMod via the method i described above.
i also -successfully- installed the saga LBC mod - both are running fine.
Now i want to just replace the ClockworkMod, (not the LBC Mod - i know how to install a new ROM ;-)) with 4ExtRecovery.
basically the question is:
how can i flash 4ExtRecovery from within the bootloder.
the PG88IMG.zip Method seems to fail here...
you know, i basically followed the instructions found the lbd mod homepage
[lbc-mod-homepage]/custom-recovery/modded-clockworkmod-recovery/
install-instructions for on this page
(i cannot post links to outside the forums, sorry)
can somebody help me?
EDIT:
yes, i found the one-click-zip but dont want to use it; i don't want to flash via the adb tool, i don't know why, just personal preferences ;-)

glubber008 said:
Hi,
wow, that was fast ;-) thanks a lot...
Hmm, no, i already installed ClockworkMod via the method i described above.
i also -successfully- installed the saga LBC mod - both are running fine.
Now i want to just replace the ClockworkMod, (not the LBC Mod - i know how to install a new ROM ;-)) with 4ExtRecovery.
basically the question is:
how can i flash 4ExtRecovery from within the bootloder.
the PG88IMG.zip Method seems to fail here...
you know, i basically followed the instructions found the lbd mod homepage
[lbc-mod-homepage]/custom-recovery/modded-clockworkmod-recovery/
install-instructions for on this page
(i cannot post links to outside the forums, sorry)
can somebody help me?
EDIT:
yes, i found the one-click-zip but dont want to use it; i don't want to flash via the adb tool, i don't know why, just personal preferences ;-)
Click to expand...
Click to collapse
................... You'll need to extract the images from the zip images and I suspect, with respect that you don't know what your doing.
So leave that method well alone!

yes, of course - i don't know how to flash this recovery ;-)
i already know that
that's the reason, why i'm asking here, you know... ;-)

try doing this
1.put the zip on your sd card
2.reboot into recovery
3.go to install from sd card
4.choose the zip from sd card
5.select the zip file & choose yes
the phone should flash the recovery & restart again into recovery
choose reboot

ah, thanks a lot ;-)
btw, exploring the zip, i found the following in the updater-script:
assert(getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga" || getprop("ro.product.board") == "saga");
assert(package_extract_file("recovery.img", "/tmp/recovery.img"),
write_raw_image("/tmp/recovery.img", "recovery"),
delete("/tmp/recovery.img"));
So, you are right, it flashes the recovery.img correctly to the recovery partition, then reboots again into recovery, all understood now, thanks again...
btw:
i might be new to android, but not to computers - i am actually a programmer ;-)
that's why i'm usually asking before doing something i don't understand completely...
anyways,
it worked, thanks again for pointing me into the right direction

Ah,
i found out, that the PG88IMG.zip method only works, if there's an android-info.txt file in the archive, so it seems, that the parser of the hboot checks the contents of this file and if this thing is valid, it continues to the builtin flash routine.
That's the reason, why this method fails with the 4Extrecovery zip file.
on the other hand, if you want to flash from the recovery system, there must be a folder called META-INF with 'some' defined structure in it, a file called updater-script (i dont know, what this update-binary file is - it is a binary ELF executable, maybe the interpreter? maybe the compiled form of the updater-script? - will run 'strings' on it...); anyways, this file is then executed and contains basically the information how to install / flash this thing.
So, thanks for helping me doing the first steps on this awesome platform ;-)
EDIT:
it seems, the update-binary file is the interpreter for the updater-script:
the relevant strings are:
wrong updater binary API; expected 1, 2, or 3; got %s
failed to open package %s: %s
META-INF/com/google/android/updater-script
Ok, enough for today... ;-)
EDIT2:
...and update-binary is part of the recovery, as found here for example:
https://github.com/arco/android_bootable_recovery/blob/gingerbread/updater/install.c
nice, nice...
EDIT3:
...currently building my own recovery, this thing is plain c, so not a big problem for me, we'll see...
EDIT4:
..flashed this thing, it's working, so i guess i can now start hacking on it ;-)

is it possible to install 4EXTRecovery to desire s with s-on? and how?

realies said:
is it possible to install 4EXTRecovery to desire s with s-on? and how?
Click to expand...
Click to collapse
no, it is not possible
you need s-off to install recovery

does CWM have to be removed to install this?

greenster4470 said:
does CWM have to be removed to install this?
Click to expand...
Click to collapse
No. Use CWM to flash it like any other mod! It'll automatically re-start recovery, and you'll in be in your shiny new 4EXT recovery.

As log as we are on this topic, I have a few doubts too:
1) Can I use my CWM nandroid backups with 4EXT without any conversion?
2) Will the paid 4EXT app from the android market automate the changeover process?
3) As our phones have a decent internal memory, it is advisable to convert the partitions to ext3/4 including the SD card or not and if done will a ROM/backup have to be reflashed?
4) Other benefits over CWM?
Could someone please enlighten me. Thanks

harshs23 said:
As log as we are on this topic, I have a few doubts too:
1) Can I use my CWM nandroid backups with 4EXT without any conversion?
2) Will the paid 4EXT app from the android market automate the changeover process?
3) As our phones have a decent internal memory, it is advisable to convert the partitions to ext3/4 including the SD card or not and if done will a ROM/backup have to be reflashed?
4) Other benefits over CWM?
Could someone please enlighten me. Thanks
Click to expand...
Click to collapse
Answers:
1) Yes you can.
4EXT will restore CWM backups to the file system they were taken in (most probably ext3 {default of CWM}). But you can even restore old ext3 backups as ext4 without any data loss or corruption with 4EXT Recovery. You'll need to tweak a few things, but i can help you if you want.
2) Yes it will, and so will the free app, 4EXT Recovery Updater..
I suggest you try out the free app first, which includes the features of the paid app for the first 3 days, and then still remains functional enough to let you update your recovery whenever you want. Then you can go ahead and purchase the paid app from the market.
3) No, do not try to change SD Card file system. Just convert the system, data and cache partitions to ext4. No need to touch the SD card, as it works only in the Fat32 format.
4) There are numerous benefits.
Prominent ones include MD5 cheksum verification, Theming support, option to remain in recovery after flashing zips or taking backups, better interface and menus, auto ROM name detection and labeling of Backups unlike CWM and great developer support from Madmaxx.
I suggest you read THIS.
Hope this helps you.

Thank you, make a lot more sense to me now.
enigmaamit said:
Answers:
1) Yes you can.
4EXT will restore CWM backups to the file system they were taken in (most probably ext3 {default of CWM}). But you can even restore old ext3 backups as ext4 without any data loss or corruption with 4EXT Recovery. You'll need to tweak a few things, but i can help you if you want.
2) Yes it will, and so will the free app, 4EXT Recovery Updater..
I suggest you try out the free app first, which includes the features of the paid app for the first 3 days, and then still remains functional enough to let you update your recovery whenever you want. Then you can go ahead and purchase the paid app from the market.
3) No, do not try to change SD Card file system. Just convert the system, data and cache partitions to ext4. No need to touch the SD card, as it works only in the Fat32 format.
4) There are numerous benefits.
Prominent ones include MD5 cheksum verification, Theming support, option to remain in recovery after flashing zips or taking backups, better interface and menus, auto ROM name detection and labeling of Backups unlike CWM and great developer support from Madmaxx.
I suggest you read THIS.
Hope this helps you.
Click to expand...
Click to collapse

Everyone in doubt about 4EXT, go through enigmaamit's post, you will be sorted. Have flashed the new recovery and am totally satisfied. No clobbering needed... LOL

4EXT Recovery Control
https://market.android.com/details?id=ext.recovery.control
Although the free version is available, I highly recommend an investment in the application that supports this incredible recovery. The added features in the market version outweigh the free version drastically.

harshs23 said:
Everyone in doubt about 4EXT, go through enigmaamit's post, you will be sorted. Have flashed the new recovery and am totally satisfied. No clobbering needed... LOL
Click to expand...
Click to collapse
@ Harsh, regarding my earlier commitment on helping you with the partition conversion and advanced restore:
Before you do any of this,
1. Take a nandroid backup. The whole procedure below is utterly harmless but you should develop a habit of doing this whenever you play around with anything.
2. Make sure you have at least 50% charge, and preferably have it plugged into your laptop. The reasons are pretty obvious.. first, you dont want to run out of charge while doing something as grass-root level as this, and secondly, having hooked it up to a laptop, adb access is available to start with. (i'm assuming you have adb set up on your pc)
3. Make sure you have adequate free space on your sd card. I would recommend around 1.5 to 2 GB. This is because when changing a file system the recovery first backs up your data from the partition onto the sd card, formats the partition into the new file system and then moves the data back into the partition after that into the new file system (ext4, in our case). So you need to give enough room for the recovery to be able to temporarily cache the contents of the partitions on the sd card. Hope this is clear to you.
EDIT: Don't worry about insufficient space on your sd card...since the 2.2.7 version, 4ext calculates the actual required free space needed for a conversion of a selected partition before it even starts doing that. If space needed is too low it won't do the conversion.
Let us begin:
1.) To convert existing file system:
To convert your existing file system, go into recovery and see what the partitions are right now. You'll see four partitions: 1. system, 2. data, 3. cache, 4. sd card
Next to these you'll see the file system they're on. I'm guessing it will look something like ext4, ext3, ext3, fat32 respectively, if you're coming from ClockWorkMod recovery. What you need to do to convert the ext3 partitions to ext4 is go to the EXT3 - 4EXT - EXT4 option in the menu and once inside, choose the first option (convert l change a backup -> ext4).
In that sub-menu, choose the partition you want to convert. (2nd, 3rd and 4th options SYSTEM, DATA & CACHE respectively). The execute menu will prompt you regarding going ahead. Select Yes - do it!
Now the process that i had described earlier will begin and at the end you'll have all your original data on the ext4 file system on whichever partition you selected.
Do the same for each partition that is in ext3 format.
2.) To change file system for old backups:
Again, if you want to change one of your old backups that you took while on CWM Recovery (which were most probably taken in ext3 default format), you need to convert them to ext4, otherwise 4EXT Recovery will restore them to their default file system (another neat feature of this recovery) as a safeguard against restore onto contrasting file systems.
To do this, go to EXT3 - 4EXT - EXT4 menu > then convert l change a backup -> EXT4 > THEN change one of your backups > now select the backup you want to change to ext4 > at the prompt menu, select Yes, do it!
Once you've done this, you'll get a hang of what all the other sub menus are for... You'll figure them out on your own in no time.
Whew! That was long and tedious... But i've tried to be as elaborate as i can for all those users new to 4EXT and apprehensive about migrating. I've also posted this in the Development section in the relevant thread.
I remember how i was before i converted for the first time and there was no detailed guide available.
Hope this has helped!!
P.S. Thanks to Madmaxx for the tips and inputs that helped me write this mini tutorial.

enigmaamit said:
@ Harsh, regarding my earlier commitment on helping you with the partition conversion and advanced restore:
Before you do any of this,
1. Take a nandroid backup. The whole procedure below is utterly harmless but you should develop a habit of doing this whenever you play around with anything.
2. Make sure you have at least 50% charge, and preferably have it plugged into your laptop. The reasons are pretty obvious.. first, you dont want to run out of charge while doing something as grass-root level as this, and secondly, having hooked it up to a laptop, adb access is available to start with. (i'm assuming you have adb set up on your pc)
3. Make sure you have adequate free space on your sd card. I would recommend around 1.5 to 2 GB. This is because when changing a file system the recovery first backs up your data from the partition onto the sd card, formats the partition into the new file system and then moves the data back into the partition after that into the new file system (ext4, in our case). So you need to give enough room for the recovery to be able to temporarily cache the contents of the partitions on the sd card. Hope this is clear to you.
EDIT: Don't worry about insufficient space on your sd card...since the 2.2.7 version, 4ext calculates the actual required free space needed for a conversion of a selected partition before it even starts doing that. If space needed is too low it won't do the conversion.
Let us begin:
1.) To convert existing file system:
To convert your existing file system, go into recovery and see what the partitions are right now. You'll see four partitions: 1. system, 2. data, 3. cache, 4. sd card
Next to these you'll see the file system they're on. I'm guessing it will look something like ext4, ext3, ext3, fat32 respectively, if you're coming from ClockWorkMod recovery. What you need to do to convert the ext3 partitions to ext4 is go to the EXT3 - 4EXT - EXT4 option in the menu and once inside, choose the first option (convert l change a backup -> ext4).
In that sub-menu, choose the partition you want to convert. (2nd, 3rd and 4th options SYSTEM, DATA & CACHE respectively). The execute menu will prompt you regarding going ahead. Select Yes - do it!
Now the process that i had described earlier will begin and at the end you'll have all your original data on the ext4 file system on whichever partition you selected.
Do the same for each partition that is in ext3 format.
2.) To change file system for old backups:
Again, if you want to change one of your old backups that you took while on CWM Recovery (which were most probably taken in ext3 default format), you need to convert them to ext4, otherwise 4EXT Recovery will restore them to their default file system (another neat feature of this recovery) as a safeguard against restore onto contrasting file systems.
To do this, go to EXT3 - 4EXT - EXT4 menu > then convert l change a backup -> EXT4 > THEN change one of your backups > now select the backup you want to change to ext4 > at the prompt menu, select Yes, do it!
Once you've done this, you'll get a hang of what all the other sub menus are for... You'll figure them out on your own in no time.
Whew! That was long and tedious... But i've tried to be as elaborate as i can for all those users new to 4EXT and apprehensive about migrating. I've also posted this in the Development section in the relevant thread.
I remember how i was before i converted for the first time and there was no detailed guide available.
Hope this has helped!!
P.S. Thanks to Madmaxx for the tips and inputs that helped me write this mini tutorial.
Click to expand...
Click to collapse
Thank you very much for the detailed tutorial, I think the following 3 posts should be compiled and made a stickied tutorial for all the others here and to come.
http://forum.xda-developers.com/showpost.php?p=18562457&postcount=14
http://forum.xda-developers.com/showpost.php?p=18593426&postcount=18
http://forum.xda-developers.com/showpost.php?p=18565951&postcount=437
With your and madmaxx's help, I have changed over to 4EXT without a single hitch. Thanks once again.

harshs23 said:
Thank you very much for the detailed tutorial, I think the following 3 posts should be compiled and made a stickied tutorial for all the others here and to come.
http://forum.xda-developers.com/showpost.php?p=18562457&postcount=14
http://forum.xda-developers.com/showpost.php?p=18593426&postcount=18
http://forum.xda-developers.com/showpost.php?p=18565951&postcount=437
With your and madmaxx's help, I have changed over to 4EXT without a single hitch. Thanks once again.
Click to expand...
Click to collapse
You're more than welcome. This is what all of us are here for...

Wiping/Formatting Internal Storage. How to perform a real....(read:actual) wipe.

Even after doing a factory reset....and after wiping every time of cache i could in recovery...my internal storage is still stuffed with stuff from the stock when my i first got the device. How do i actually perform a wipe.

Jamesyboy said:
Even after doing a factory reset....and after wiping every time of cache i could in recovery...my internal storage is still stuffed with stuff from the stock when my i first got the device. How do i actually perform a wipe.
Click to expand...
Click to collapse
Why don't you just go into Settings -> Storage -> Format? Or just delete everything with your computer?

Product F(RED) said:
Why don't you just go into Settings -> Storage -> Format? Or just delete everything with your computer?
Click to expand...
Click to collapse
There's no option to format the internal storage.

Jamesyboy said:
Even after doing a factory reset....and after wiping every time of cache i could in recovery...my internal storage is still stuffed with stuff from the stock when my i first got the device. How do i actually perform a wipe.
Click to expand...
Click to collapse
As well, wiping the internal storage may be possible through the stock ROM under settings-> storage....but i was working with codename android. I tried the "Erase Tablet" under Settings->Backup and Restore-> Factory Reset-> Wipe all personal information.
However, after restarting, nothing was deleted.
I'm going to flash the stock ROM and try to look for a format option under Settings->Storage, and i'll try doing a factory reset under settings-> Privacy.
If that doesn't work, i'll have to reflash Revolver 4 beta, and try to look in the settings there.
But as far as trying to delete everything from a computer, idk if i have to have USB debugging enabled, or some settings switched, because browsing the contents of the internal storage over USB doesn't even show all of the folders.

if you have a SBK1 devics you can use NVFlash that wipes everything and repartitions it and i believe there is a superwipe script in the arhd thread that wipes internal storage

mrevankyle said:
if you have a SBK1 devics you can use NVFlash that wipes everything and repartitions it and i believe there is a superwipe script in the arhd thread that wipes internal storage
Click to expand...
Click to collapse
Will this wipe CWM as well? Was hoping this wouldn't be too complicated. This will be a joke if i have to redo EVERYTHING.
I really just wanna wipe the internal storage and then flash a ROM from my sdcard.
So if things do work out like i want them to, I can just use the ICS Nvflash and things will be wiped?
Or will this be convoluted---as in i'll have to use the script, install ARHD (which is honeycomb right?) install CWM, rewipe (at which point i'll have some crap from ARHD in my internal storage...grr), and then, finally, install my ROM?
BTW, i have a B70 transformer that was rootable via the one-click live CD. I assume that means i have a SBK1.
I can remove my MicroSD during this, amirite?

C'mon asus, this is such a basic feature.
If i recall correctly, wasn't there a feature in settings, that if you entered your pattern or password incorrectly a certain number of times, your data would be wiped? If this wipes ALL personal information, that feature would be really handy right now.

Go here:
http://forum.xda-developers.com/showthread.php?t=1245892
Download the super wipe. Then use the recovery to run it. It will handle all things internal.

Not sure which CWM you are using but in Rogue XM Recovery, there's an option to format /sdcard under Mounts and Storage. IIRC the regular CWM has that option too. There is also an option to partition the SD card under Advanced.
You can also use the the superwipe(full version) script to delete everything on internal storage. No it doesn't remove CWM.
BTW, i have a B70 transformer that was rootable via the one-click live CD. I assume that means i have a SBK1.
Click to expand...
Click to collapse
what is this one click live cd rooting? Some sort of linux live cd? Why didn't you just use ViperMod?
How did you come to the assumption that you have a SBK1? Did the author of the rooting method specifically say it only works for SBK1 devices?
FROM THE MODERATOR . . . Watch the use of profanity... please use respectful language in this forum--- THX

The One-Click live CD was in it's prime during intitial release. ASUS changed the bootloader encryption key during the second half of B70* production. Before the second encryption key was released, B70*+ users were in limbo.
I came to that conclusion because i had no issue rooting and installing CWM with the first batch of tools, while others, who had devices with serial numbers in the second half of the B70* spectrum did. So yes, there is a method to my madness.
And i used the Live CD One-Click method because i was rusty with a CMD prompt. To each his own. It rooted, partitioned, and installed CWM.
I might add...this was my first Android device, and it was certainly my first time lurking around root. It was perfect for someone with a limited knowledge of android and Linux (at the time).

Thanks! I might as well give ARHD a try while im at it! Will report back!

Oh I see. Yes you are right about having sbk1.
Not sure which version of CWM comes with it but it should have an option to format sdcard like I said earlier. I know this because I used that option to delete everything before flashing ICS.

horndroid said:
Oh I see. Yes you are right about having sbk1.
Not sure which version of CWM comes with it but it should have an option to format sdcard like I said earlier. I know this because I used that option to delete everything before flashing ICS.
Click to expand...
Click to collapse
The Super-Wipe script worked perfectly for deleting the data, but the ARHD thread says that it reformats the partitions as EXT4. i installed ARHD after using the super wipe script and during the restore (Google's cloud restore), iI immediately got swamped with Google Play Store errors- Error 403 every time it tried to install an app.
Codename Android installed, restored, and ran fine...including app installation, so im not sure what was the problem, but i have a feeling it has to do with the file system change. If this is true, be aware. The script may function well, but its also possible you'll end up having to reformat anyways to change the filesystem back. Ill post this as well in the proper thread...but i thinks it's also relevant to this discussion.
I suppose XDA and Android have led me to my next topic of research--filesystem usage in Android with stock and custom ROMs.

What Is Android and Custom Recovery Image..?

ClockworkMod – also known as Clockwork and CWM – is a custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery. In what follows, we will cover all that this recovery is capable of doing, and how to do it.
About Android Recovery
All Android devices ship with a recovery console that is basically a partition on the device’s internal memory and can be booted into. The stock recovery of almost all Android devices provides a few basic yet handy options that allow you to factory reset your device and also to recover its operating system using an official ROM in zip format, but that’s all you can do with it. That’s where a custom recovery comes handy.
A custom Android recovery basically replaces the stock recovery with one that lets you do all you can do with the stock recovery, plus a plethora of more options to give you a lot more control on your device. With a custom recovery, you can install official and unofficial ROMs as well as other updates including apps, themes, kernels etc. using zip files, wipe not just user data but pretty much every partition on your device, mount the storage card for USB mass storage access without leaving recovery, partition your SD card, wipe Dalvik cache and battery stats, fix permissions, perform, manage and restore backups and so on...

Complete Article:
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/

Aspire said:
Complete Article:
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/
Click to expand...
Click to collapse
Thnkss fr ur concern soon ivl complete..

mohitawasthi said:
ClockworkMod – also known as Clockwork and CWM – is a custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery. In what follows, we will cover all that this recovery is capable of doing, and how to do it.
About Android Recovery
All Android devices ship with a recovery console that is basically a partition on the device’s internal memory and can be booted into. The stock recovery of almost all Android devices provides a few basic yet handy options that allow you to factory reset your device and also to recover its operating system using an official ROM in zip format, but that’s all you can do with it. That’s where a custom recovery comes handy.
A custom Android recovery basically replaces the stock recovery with one that lets you do all you can do with the stock recovery, plus a plethora of more options to give you a lot more control on your device. With a custom recovery, you can install official and unofficial ROMs as well as other updates including apps, themes, kernels etc. using zip files, wipe not just user data but pretty much every partition on your device, mount the storage card for USB mass storage access without leaving recovery, partition your SD card, wipe Dalvik cache and battery stats, fix permissions, perform, manage and restore backups and so on...
Click to expand...
Click to collapse
I'm a little confused, I'm a noob. So if I root a phone and delete bloatware, can I make a custom recovery so the phone doesn't brick and the factory reset resets all settings to a certain way I want it to? Or is my perception of a custom recovery totally off?

factory reset cannot work according to you
it will remove all the data you have in your /data partition
@op
you should delete the [Q] tag from the title
@s.d.oconnor
good to see you as the mod here, wanna post something related to rc let me know

I have removed the [Q] from your thread title, to avoid mistakes.

matthewm223 said:
I'm a little confused, I'm a noob. So if I root a phone and delete bloatware, can I make a custom recovery so the phone doesn't brick and the factory reset resets all settings to a certain way I want it to? Or is my perception of a custom recovery totally off?
Click to expand...
Click to collapse
replacing the recovery.img file with the custom recovery.img file just by simply coping/overwritting , Will this be same as installing the custom ROM?

Custom recovery partition program killed 32 GB sd card
Is it possible that this partition programmer from clockwork recovery can't work with the new big 32 gb cards?
I wanted to let the custom recovery make an ext2 partition, and a fat 32 partition on a brandnew 32 GB sd card.
Seems that the custom recovery partition program wiped my master boot record from the sd card, I tried everything, the card is recognised,
but it is impossible to write anyting on it. I tried to repair the mbr, but so far it didn't work. I tried with windows fdisk but no solution found.
Someone knows how to save my sd card without sending back to factory?

Custom recovery can be downloaded from ROM manger for fit????

adityaf said:
Custom recovery can be downloaded from ROM manger for fit????
Click to expand...
Click to collapse
Yes but it can cause a brick

mohitawasthi said:
ClockworkMod – also known as Clockwork and CWM – is a custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery. In what follows, we will cover all that this recovery is capable of doing, and how to do it.
About Android Recovery
All Android devices ship with a recovery console that is basically a partition on the device’s internal memory and can be booted into. The stock recovery of almost all Android devices provides a few basic yet handy options that allow you to factory reset your device and also to recover its operating system using an official ROM in zip format, but that’s all you can do with it. That’s where a custom recovery comes handy.
A custom Android recovery basically replaces the stock recovery with one that lets you do all you can do with the stock recovery, plus a plethora of more options to give you a lot more control on your device. With a custom recovery, you can install official and unofficial ROMs as well as other updates including apps, themes, kernels etc. using zip files, wipe not just user data but pretty much every partition on your device, mount the storage card for USB mass storage access without leaving recovery, partition your SD card, wipe Dalvik cache and battery stats, fix permissions, perform, manage and restore backups and so on...
Click to expand...
Click to collapse
thanks

adityaf said:
Custom recovery can be downloaded from ROM manger for fit????
Click to expand...
Click to collapse
best thing would be to use odin for CWM

I have CWM installed on my Fit but my CM 10 is buggy and I want to use both CM 9 and CM 10. Is dual boot possible on the Fit?
---------- Post added at 11:02 PM ---------- Previous post was at 10:57 PM ----------
Also, my CWM is not flashing the latest update of CM10. Can anyone help me? I'm getting a status 7 error :crying:

Kronosthelordoftime said:
I have CWM installed on my Fit but my CM 10 is buggy and I want to use both CM 9 and CM 10. Is dual boot possible on the Fit?
---------- Post added at 11:02 PM ---------- Previous post was at 10:57 PM ----------
Also, my CWM is not flashing the latest update of CM10. Can anyone help me? I'm getting a status 7 error :crying:
Click to expand...
Click to collapse
Dual boot is not possible on fit.
Make sure you have CWM5 not CWM4 or any touch versions..only the one by tj_style is gonna work.

but what is a recovery.img?
But is the recovery.img specific to device like the ROMs or it does not make any difference?
The recovery.img I am talking about is like not more than 5MB in size....
It maybe a stupid question but I am unable to find any particular information regarding this point so please help me.....

How do i get cwm without pc please
Sent from my GT-S5670 using xda app-developers app

Asus Memo Pad HD 7
I wiped some necessary programs and completely kill my tablet.
Is there any idea how to recover the device (I'm not maked backup).
CU

shadow452 said:
I wiped some necessary programs and completely kill my tablet.
Is there any idea how to recover the device (I'm not maked backup).
CU
Click to expand...
Click to collapse
Flash any custom rom...
♪Cheers♪

RE
Galaxy_Rohit said:
Flash any custom rom...
♪Cheers♪
Click to expand...
Click to collapse
I don't find costom rom for Asus ME173X.
If I use roms for other devices that can make tablet-brick instead of tablet-android.
Do you have same device like me?

shadow452 said:
I don't find costom rom for Asus ME173X.
If I use roms for other devices that can make tablet-brick instead of tablet-android.
Do you have same device like me?
Click to expand...
Click to collapse
I guess it's a new tablet arrived this year. It might b under warranty. So u can freely expect assistance from customer care
Btw I don't have this tablet

So many years on forum, still many times i manage to brick/bootloop my phone.. Help!

I need some explanation to make things clear..
1) First and most important. If you want to make a clean install, what you have to wipe? Should you format data also, and why? Format data affects system? Can you format data and still boot into rom? When you format/wipe all, is there something left in the phone? If no, then why still i can see in mount settings, that the folders still have Mb/Gb inside them? What are they? I guess you can';t delete everything from the phone? For example now i am stuck on custom animation bootloop. So there is still data left.
2) Format data make your encrypted or decrypted? Or just removes all encryption and if a) you install a rom you go automatically encrypted, b) you install a rom and flash no_verity you go decrypted?
3) If i go decrypted, the only way to go encypted is to install stock OS and why?
4) When is necessary to have the stock rom flashed in order to flash custom rom afterwards? If you want to install a different android version from the one that you have? Any other reason? Is it necessary to install the whole stock image, or just enough to install firmware + radio?
5) If you wipe/format all, the phone has some firmware,radio,vendor etc stored inside or it's empty 100%?
6) Is it 100% safe to install a TWRP through TWRP?
And now let's say the problem i had. But i think i know where was the problem.. I had installed android pie + xXx no_limits on my oneplus5 and i was decrypted. Some months later i decided to try something else, so i installed an AOSP android 10 version. I just wipe/format system,data,dalvik,cache then flashed rom, gapps, magisk. But i had some bugs on this version, lags and huge battery drain. Also whenever i was booting into TWRP it moved me on Mount --> Decrypt screen.. And i don't know why?
Now that i try to figure i know that the problem was i install a custom android 10 rom, without first installing the android 10 stock rom? In order to get the proper firmware etc? Or what? The instructions for installing the rom are the following, which i followed them 100% :
NOTE:
WE ARE ENCRYPTED (FILE BASED FORCED ENCRYPTION). So if you are unencrypted format data partition or use any no_verity solution you want. We don't support it.
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended). Bluspark twrp recovery recommended.
3. Wipe the System, Cache, and Data (you might need to format the data partition in some cases!).
4. Flash firmware. Actual one is 9.0.11. Download.
5. Flash the ROM Zipfile.
6. Reboot to TWRP recovery.
7. Flash the GApps (optional, needed for e.g. Google Playstore to work) and Magisk (optional too if you want a root solution).
8. Reboot and set up your device.
Click to expand...
Click to collapse
The ROM should contain everything you need to enjoy Android Q. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
Click to expand...
Click to collapse
The only system app i restored was the Vanced youtube, but i don't this is the source of my problems.
Thanks in advance!

Guys i think i cleared some things on my mind..
When you install a rom you go encrypted. So you have to FORMAT data RIGHT AFTER installing the rom and then flashing no_verity? Am i right? When you format data do you lose Magisk also?

lazostat said:
I need some explanation to make things clear..
1) First and most important. If you want to make a clean install, what you have to wipe? Should you format data also, and why? Format data affects system? Can you format data and still boot into rom? When you format/wipe all, is there something left in the phone? If no, then why still i can see in mount settings, that the folders still have Mb/Gb inside them? What are they? I guess you can';t delete everything from the phone? For example now i am stuck on custom animation bootloop. So there is still data left.
2) Format data make your encrypted or decrypted? Or just removes all encryption and if a) you install a rom you go automatically encrypted, b) you install a rom and flash no_verity you go decrypted?
3) If i go decrypted, the only way to go encypted is to install stock OS and why?
4) When is necessary to have the stock rom flashed in order to flash custom rom afterwards? If you want to install a different android version from the one that you have? Any other reason? Is it necessary to install the whole stock image, or just enough to install firmware + radio?
5) If you wipe/format all, the phone has some firmware,radio,vendor etc stored inside or it's empty 100%?
6) Is it 100% safe to install a TWRP through TWRP?
And now let's say the problem i had. But i think i know where was the problem.. I had installed android pie + xXx no_limits on my oneplus5 and i was decrypted. Some months later i decided to try something else, so i installed an AOSP android 10 version. I just wipe/format system,data,dalvik,cache then flashed rom, gapps, magisk. But i had some bugs on this version, lags and huge battery drain. Also whenever i was booting into TWRP it moved me on Mount --> Decrypt screen.. And i don't know why?
Now that i try to figure i know that the problem was i install a custom android 10 rom, without first installing the android 10 stock rom? In order to get the proper firmware etc? Or what? The instructions for installing the rom are the following, which i followed them 100% :
The only system app i restored was the Vanced youtube, but i don't this is the source of my problems. Formatting data does not effect system in most cases.
Thanks in advance!
Click to expand...
Click to collapse
1) a clean install involves wiping system, data, cache and dalvik cache. All of these partitions must be wiped in order to remove data things that might conflict with the new software that you intend to flash. Yes, you can wipe data and still boot into your ROM. Yes, there are things still on the phone even after wiping the device, but, the things left behind are in partitions that are separate from what you can actually wipe, these other, separate partitions contain all the other stuff that is essential for your device to be able to function. These parts have nothing to do with the ROM that you are using and have nothing to do with what you have installed in your data partition. TWRP does not wipe /data/media partition(internal storage), /data/media is where your personal user data is stored, such as, photos, videos, downloaded files, data from apps such as games, etc. Basically, /data/media contains things that you have stored that are not apps. Your internal storage will still have all the files and folders that were there before you did the wipe. If you want to wipe internal storage, you have to specifically select your internal storage when you use TWRP to wipe the device, it will not wipe internal storage by default. If you still have a custom animation even after wiping the device, it is probably because the boot animation is in your system partition, that can only be removed by selecting the /system partition when using TWRP to wipe the device.
2) Formatting data "should" remove encryption. No, flashing a new ROM after removing encryption will not encrypt the device again unless you specifically choose to encrypt the device in its settings. Flashing no verity only eliminates issues involved with rooting a device and getting root to actually work without corrupting the device.
3)I'm not sure but I think you can encrypt a device without using stock.
4) It depends on which device you have, what your current firmware version is and what you are trying to flash. Some devices require a certain firmware to be installed before flashing certain custom ROMs but it is a case by case scenario. There is no specific answer to this, there is only the question of whether your specific device requires this or a question of whether the custom ROM that you are trying to flash requires this. This is best answered by reading the thread where the ROM is posted, if your device requires installing a certain stock firmware before flashing the custom ROM, it will tell you that somewhere in the thread for that ROM. Whether you need to install the entire firmware or just parts of the firmware also depends on which device you are using in some cases, you might only need the modem or only the bootloader or maybe both, or maybe none, or maybe the complete firmware.
5) As I stated above, there are partitions on the device that do not get wiped when using TWRP to wipe the device. If it wiped EVERYTHING, the device would no longer function at all, it wouldn't be able to power on, it wouldn't be able to boot into any of its modes and you wouldn't be able to flash anything at all on the device, not even it's original stock firmware. There are software elements that MUST remain on the device in order for it to continue to function.
6) It is perfectly safe to use your existing version of TWRP to flash another TWRP version, assuming the new TWRP is also built for your specific model number.
If you have installed a custom ROM and you are having issues, you need to go to the thread where you got the ROM and post your issues/questions there. The users there will know more about your device and what you actually need to do and the developer may also need to fix things in their ROM to solve the issues that you are experiencing.
Sent from my SM-S767VL using Tapatalk