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

[Q] Pre-flash, some questions

I'm about to flash my first custom ROM on my Desire S.
It's S-OFF, rooted and fully backed up (nandroid, titanium backup, SD to PC).
I tried to read as much as possible abut the flashing process and some of the android internals. Excuse me if my questions are still a bit noobish, I tried to read a lot.
I've decided to try CM7 and repartition my SD card to add an ext4 sd-ext partition.
Before I flash, I still have some questions:
- Where is HBOOT located exactly? /boot ?
- Where is the recovery (ClockworkMod in my case) located? /recovery ?
- Revolutionary installed ClockworkMod. However, ROM Manager also offered me to flash it (that's what I did). Did ROM Manager overwrite the ClockworkMod in /recovery?
- Assuming that /boot and /recovery are critical (from my previous questions), and that they are backed up and available (nandroid backup files) on my PC, can I always push those back with adb in case something goes wrong?
- What's the correct order for the flash + repartition?
Repartition first, allow the wipe (data + everything) to wipe the SD during flashing, copy data back after new ROM is running?
- What's the safest/best way to flash? From HBOOT/recovery? Or ROM Manager? Or do they actually do exactly the same?
I.e. ROM Manager rebooting and starting ClockworkMod?
Sorry for all the questions. I'm pretty sure that the flash will work fine, but I always like to know more about the internals first.

Quark^2 said:
I'm about to flash my first custom ROM on my Desire S.
It's S-OFF, rooted and fully backed up (nandroid, titanium backup, SD to PC).
I tried to read as much as possible abut the flashing process and some of the android internals. Excuse me if my questions are still a bit noobish, I tried to read a lot.
I've decided to try CM7 and repartition my SD card to add an ext4 sd-ext partition.
Before I flash, I still have some questions:
- Where is HBOOT located exactly? /boot ?
- Where is the recovery (ClockworkMod in my case) located? /recovery ?
- Revolutionary installed ClockworkMod. However, ROM Manager also offered me to flash it (that's what I did). Did ROM Manager overwrite the ClockworkMod in /recovery?
- Assuming that /boot and /recovery are critical (from my previous questions), and that they are backed up and available (nandroid backup files) on my PC, can I always push those back with adb in case something goes wrong?
- What's the correct order for the flash + repartition?
Repartition first, allow the wipe (data + everything) to wipe the SD during flashing, copy data back after new ROM is running?
- What's the safest/best way to flash? From HBOOT/recovery? Or ROM Manager? Or do they actually do exactly the same?
I.e. ROM Manager rebooting and starting ClockworkMod?
Sorry for all the questions. I'm pretty sure that the flash will work fine, but I always like to know more about the internals first.
Click to expand...
Click to collapse
Very impressed to see someone actually ask intelligent questions....and seek a real understanding..
Unfortunately its now my dinner time....so I only have a few minutes....so I'll attempt to answer quickly:
YES (boot.img in backup), YES (recovery.img in backup) and unless you play lots of games and require lots of ext space this device has a decent amount of internal storage so that it doesn't require sd-ext partitions (that's just my opinion anyway - these partitions are something from when devices had minimal internal storage)
What I will say is yes you downgraded the CWM version that revolutionary had installed with an older one from ROM Mananager. So you'll be much better of to install EXT4 recovery (which is based on CWM) and overwrite the old CWM, so simply download this file onto your SD card and flash it from recovery over the existing CWM recovery....then when you reboot recovery you'll have the EXT4.

what are the advantages of ext4 recovery exactly? im also running the CWM from the CWMM.

kazen44 said:
what are the advantages of ext4 recovery exactly? im also running the CWM from the CWMM.
Click to expand...
Click to collapse
For a start its based on the same code base as CWM, but, has lots of added functionality, is far more user friendly, is constantly being updated and can be themed! The support is immense as well, just look at the thread.
there's too many to mention, simply read the EXT4 forum link in the page above so see them for yourself!
Just the file system conversion part of it is worth it!

whats the advantage of ext4 on a phone instead of ext3? ive worked with both filesystems quite a lot on my desktop PC. but there does not seem to be a major diffrence. i know that EXT4 supports journaling far better then ext3 does. but thats about the only thing i notice as diffrent on my linux install.

Actually boot and hboot are different things. I'm not 100% sure but I think that the kernel is located in the /boot partition, you are able to format it or replace its content from within the recovery.
Hboot is the initial bootloader that is located in a secure block of eMMC, you can't access it from recovery and can't backup it. If you completely wipe all partitions accessible through recovery, you still can easily install new ROM or restore from backup, even if you lose your recovery you can still restore it through fastboot. Phone with damaged or incorrect hboot is definitely a brick, it won't be accessible through PC connection and won't load up. Normally it's only possible to make permanent damage to the phone if you incorrectly flash hboot or radio image, while it's possible to brick even without messing with them, it's usually caused by faulty hardware (eMMC chip).

Ok thanks all so far.
So, HBOOT resides in eMMC and not is easily accessible (but still flashable).
At least, that's what Revolutionary did, my current HBOOT shows "Revolutionary" in the first line.
The kernel resides in /boot, which is the same for all all regular linux distros.
I think I have a clearer picture of the internals now. Still not 100% clear, but getting there.
I am going to flash 4EXTRecovery first, before trying to flash my first custom ROM.
Ofcourse, repeating the backup cycle, just in case.
I'm only left with these questions (for now ;-):
- What's the best way to flash now? From ROM Manager or 4EXTRecovery (from HBOOT manually)?
- Does the Wiping (everything, data + cache) also clear my SD card? I'm fairly sure it does.

Quark^2 said:
I'm only left with these questions (for now ;-):
- What's the best way to flash now? From ROM Manager or 4EXTRecovery (from HBOOT manually)?
- Does the Wiping (everything, data + cache) also clear my SD card? I'm fairly sure it does.
Click to expand...
Click to collapse
ROM Manager loads recovery in order to flash, so there is no real difference. Flashing from HBOOT is only required for updating hboot itself or radio, I'm pretty sure it's better to use recovery to flash everything else.
Wiping everything formats /boot, /system, /data and /cache partitions, it doesn't wipe SD card (would be kinda stupid if it did actually, as CWM recovery places backup files on SD). I still make SD card backups from time to time, just for convenience.

Evilmystic said:
Actually boot and hboot are different things. I'm not 100% sure but I think that the kernel is located in the /boot partition, you are able to format it or replace its content from within the recovery.
Hboot is the initial bootloader that is located in a secure block of eMMC, you can't access it from recovery and can't backup it. If you completely wipe all partitions accessible through recovery, you still can easily install new ROM or restore from backup, even if you lose your recovery you can still restore it through fastboot. Phone with damaged or incorrect hboot is definitely a brick, it won't be accessible through PC connection and won't load up. Normally it's only possible to make permanent damage to the phone if you incorrectly flash hboot or radio image, while it's possible to brick even without messing with them, it's usually caused by faulty hardware (eMMC chip).
Click to expand...
Click to collapse
Thanks for the correction , I also have a slightly clearer picture of the internals myself.

Evilmystic said:
ROM Manager loads recovery in order to flash, so there is no real difference. Flashing from HBOOT is only required for updating hboot itself or radio, I'm pretty sure it's better to use recovery to flash everything else.
Wiping everything formats /boot, /system, /data and /cache partitions, it doesn't wipe SD card (would be kinda stupid if it did actually, as CWM recovery places backup files on SD). I still make SD card backups from time to time, just for convenience.
Click to expand...
Click to collapse
Thanks for the correction , and on thinking it through of course you're right, I also have a slightly clearer picture of the internals myself.

[Q] New G2X: Should I mod/root?

I got a new LG P999 (I think that's the G2X). I'm new to Android but I'm not sure if I should root/mod or not.
Is there really any significant benefits from modding (like speed or stability) or it's just to make your Android flashier?
Also, what mod would be best to go for? And if someone could link me to a beginner tutorial on how to mod (with simpler terminology; I only found some with terminology like NANDroid, clockwork recovery, etc... which I don't really understand), that would be much appreciated.
Hope someone can help, thanks!

kefloxin said:
I got a new LG P999 (I think that's the G2X). I'm new to Android but I'm not sure if I should root/mod or not.
Is there really any significant benefits from modding (like speed or stability) or it's just to make your Android flashier?
Also, what mod would be best to go for? And if someone could link me to a beginner tutorial on how to mod (with simpler terminology; I only found some with terminology like NANDroid, clockwork recovery, etc... which I don't really understand), that would be much appreciated.
Hope someone can help, thanks!
Click to expand...
Click to collapse
Well, rooting/modding gives you every benefit out there. Battery life, speed, options, features, the list goes on. Flashing ROM's is basically 99% the reason why people root or install a custom recovery on their phones. NANdroid, Clockwork MOD, etc are basically the basis and the stuff that you need to know about rooting. Since you're new I suggest you read a lot first and get to know what those terminologies are. ClockWork is a custom recovery that enables you to flash a custom ROM onto your phone.
Here is the G2x Bible. That's a reference guide to most, if not everything, that you need to know.
Here is the NVFlash method that you need to do to install Clockwork onto your G2x. You don't really need root for the G2x, just install Clockwork via that guide and you'll be good to go.
Remember: Read, read, and read.

Thanks for your reply! Those links helped me a lot. A few questions though:
1) If I don't have an external SD card, will I be able to put an external SD card without problems later? And can I re-flash for the external SD card support if desired?
2) Once I'm in the ClockworkMod Recovery, how do I put the ROM on my phone? (Flash is the correct terminology if I'm not mistaken).
3) Which ROM or mod should I go with? From the looks of it, a lot of people use CyanogenMod, but is there one that's most stable/fast?
Thanks again for your answer.

Here's another guide on NVFlashing.
These are my 3 favorite ROM's. And I'm sure most of the G2x people would agree as well.
Eagle's Blood: Based on LG's stock 2.3.3 Gingerbread.
Weapon G2x: Again, based on LG's stock 2.3.3 Gingerbread, but with Whitehawx's many tweaks and features.
And of course, CyanogenMOD 7 Nightlies: It's based on Google's AOSP, but the CM team has added in hundreds of tweaks that makes the user experience the best you can ever get on Android.
My favorite is CM but I suggest you try all 3 to see which one you like the best.
Yes, you can slip in an SD card after you've flashed if you want. Just follow the instructions carefully on how to NVFlash, there's even a YouTube video on how to do it.
Once you're in CWM, I suggest you do a NANDroid backup to backup your current ROM. Then do the following steps.
1. Wipe Data
2. Wipe Cache
3. Wipe Dalvik Cache (within Advanced)
4. Then go into mounts and format your /system
5. Then proceed to flashing your desired ROM.
Here's a quick video on how to flash a ROM.
But note; that video is how to flash a ROM on a myTouch 4G, just ignore the ROM's I showed in that video as it's for the MT4G. But the Clockwork MOD that you see there is just like the one for the G2x, except now the letters are blue. Do as I did in that video by wiping everything. Only thing I left out is formating /system since it wasn't needed on the MT4G. So don't forget to do that on your G2x.
Also, do you have Froyo or Gingerbread right now?

If you need any help with your g2x just drop me an email at [email protected]. I will be happy to help with any questions you may have.
Sent from the fastest g2x in the world

Thanks again for your awesome reply mackster248.
To answer your question, I'm currently running Froyo and I'm not actually with T-Mobile. I'm in Quebec with Videotron but I read it's the same phone. The phone model I have is LG P999DW.
I think I'll go with CM V7.1.0.1 as my first ROM (the nightlies may not be as stable as I want them to be). Do you think that would be an okay ROM as a first?
So just to confirm, this is what I will be doing as a whole process:
First, I will follow the NVFlashing guide which will allow me to use ClockworkMod Recovery. Next, I'll do a backup with NANDroid (which I assume is an option in CWM). Following that, I follow the wiping steps you listed (same as your video). Is that correct or am I missing something?
Thanks again!
EDIT: So I followed the NVFlash steps and it worked fine until I tried to boot in Recover by holding Vol Down + Power, but it doesn't seem to do anything... I can boot up the phone fine normally by holding the power button though. Is there a reason booting into recovery wouldn't work?
EDIT 2: Ah, nevermind. It works after I took out the battery and tried again.
EDIT 3: I haven't wiped my data yet in the recovery, but it seems I need an SD card so I can load the zip of the ROM I want. Is there a way to load the ROM from my computer or will I need to get an SD card first? Also, I would like to know if I should root as well? Does it make a difference? If not, why do people root before flashing?

Do you mind making a video of all the steps you did in exact order? also people root because most phones just use ROM manager to flash clockworkmod right from ROM Manger, but we are using NVFlash so we dont technically need it. Also new to the G2x, from (wind Mobile, i believe its the same one as the videotron P999-DW)
but im so scared to flash lol i had a vibrant i9000-m die on me before :3

Well, I can't make a video of what I did since I don't have a spare camera. All I did up until now is follow the NVFlashing guide to get ClockworkMod Recovery. It's not very hard to do actually.
I'm apparently supposed to wipe data, etc. now but I don't want to do that because steps later say that I need to flash from the SD card which I don't have. So I need to know now whether I need an SD card to flash a ROM on the phone? I've ordered an SD card which might take a while to get but after I get it, I also would like to know whether I need to root to flash? (since ROM manager says I need to root to use it, maybe I need to root to flash a ROM via CWM as well?)
I downloaded ROM manager and it says I need to root my phone for it to function. I also tried "Flash ClockworkMod Recovery" via the ROM manager which gives me an error as well.
So if someone could let me know whether 1) I can flash without an SD card and 2) whether I need to root to flash via CWM, that would be much appreciated. Thanks!

The newest version of CWM Recovery requires a physical SD to put the rom backups on. Go get yourself one. The smaller capacities are very inexpensive now, but it is nice to have a larger one if you can afford it. Each backup is very large, so a small card would run out of space quickly if you don't offload them to your computer or another storage medium. If you want to backup to the internal sd then install the older version (4.0.1.5) of CWM that support internal sd only, then you don't need a physical sd card. That is why TGA_Gunnman put that version back into his flasher.

With the latest CWM and a g2x and NO sd card, I was able to root, and flash roms. Just select the flash zip from internal SD option in CWM. I did not backup though.

hesher said:
With the latest CWM and a g2x and NO sd card, I was able to root, and flash roms. Just select the flash zip from internal SD option in CWM. I did not backup though.
Click to expand...
Click to collapse
Wouldn't the flash zip be deleted after you wipe the data, etc.?
Also, do I need to root for flash via CWM to work?

No just place it in the root.

kefloxin said:
Wouldn't the flash zip be deleted after you wipe the data, etc.?
Also, do I need to root for flash via CWM to work?
Click to expand...
Click to collapse
So you're saying that if I place the ROM on the root of the phone, it won't be deleted once I wipe data, wipe cache, wipe dalvik cache and format my /system?
I would just like to make sure as I don't want to be stuck without a phone until I get an SD card and no backup.
Thanks

kefloxin said:
So you're saying that if I place the ROM on the root of the phone, it won't be deleted once I wipe data, wipe cache, wipe dalvik cache and format my /system?
I would just like to make sure as I don't want to be stuck without a phone until I get an SD card and no backup.
Thanks
Click to expand...
Click to collapse
If you were factory resetting a Samsung the internal SD is also wiped; but thankfully, LG does not do that. When you do a factory reset on the P999 all it does is wipe the data and cache partitions. The internal sd is left alone. So yes you can place the zip package on the internal sd, reset and then flash it. It also doesn't have to be on the root. In CWM if you select install zip from sd card, you can then choose external or internal sd and navigate to any folder and zip file you want to flash. Have fun!

I was able to install the old CWM with internal SD card support and I used that to make a backup and flash the ROM successfully. Everything seems to be awesome so far except that I can't use USB mass storage from the O/S. I turn on USB mass storage and my computer doesn't detect it. The only way to make it work is going to CWM and mounting the USB. Anyone know how I would be able to make it work through the O/S again?
I also can't install Swype without an external SD card, but I'll have one soon so that's not a big worry.
Aside from those things, I think it's pretty cool.
Thanks to everyone who helped.

Have fun bud. No phone is perfect, but the G2x is pretty awesome.
Powered by a G2x

Yeah, it's awesome. But anyone know why USB mass storage doesn't show the removable drive on my computer? I have to go into CWM and mount it to make it work, but I would prefer to be able to do it via the O/S.
Thanks for all your help though guys, you guys are awesome

kefloxin said:
Yeah, it's awesome. But anyone know why USB mass storage doesn't show the removable drive on my computer? I have to go into CWM and mount it to make it work, but I would prefer to be able to do it via the O/S.
Thanks for all your help though guys, you guys are awesome
Click to expand...
Click to collapse
Install the LG Gingerbread drivers. Let me find a link.
Edit: I had the same problem as you, but this fixed that.
http://www.lg-phones.org/t-mobile-g2x-usb-driver.html
Powered by a G2x

It doesn't seem to work. I installed the drivers via the download link in the link you provided. Didn't work, then I tried to update following the instructions using the LG mobile support tool, and it still doesn't work either. (I've tried on 2 computers btw.)
I'm not sure why it only works via CWM, any other suggestions?

kefloxin said:
It doesn't seem to work. I installed the drivers via the download link in the link you provided. Didn't work, then I tried to update following the instructions using the LG mobile support tool, and it still doesn't work either. (I've tried on 2 computers btw.)
I'm not sure why it only works via CWM, any other suggestions?
Click to expand...
Click to collapse
Could be USB connection type is set wrong internally. See if there is some setting in CM7 for it. On a stock rom you can go into LG Hidden menu and set USB to automatic.

[Completed] (status 6) installation aborted - That error on 4 diffirent MODs

Hi guys.
I am a noob in this, but i have done my research and did what i was told.
i have an I9100 and i have rooted it.
when installing CM12.1 (tried 3 diffirent versions) i am always getting status 6 installation aborted.
can the problem be with the kernels? i tried 3 diffirent kernels for I9100.
Please help
Much appreciated.

Hello,
Welcome to XDA.
If you are certain that the ROMs you are flashing are for the I9100 specifically(not another model), then you may be able to use jrummy's root browser to unzip the ROM zip that you are trying to flash, after unzipping, find the META.INF folder and open it then edit the updater script in that file, then using jrummy's root browser compress everything back into a flashable zip, when it prompts you asking which compression level you want to use, select "best", after its zipped, make sure it's placed on your extsdcard(do NOT put it on internal sdcard). When you get in recovery, go to the advanced options and select the option that lets you wipe individual partitions, wipe the system partition and the data partition(DO NOT WIPE ANY OF THE OTHER PARTITIONS), after wiping the system and data partitions you flash the ROM and see what happens.
If you need help understanding all that, you can ask in the forum linked below.
http://forum.xda-developers.com/android/help
I hope this helps, good luck.

Droidriven said:
Hello,
Welcome to XDA.
If you are certain that the ROMs you are flashing are for the I9100 specifically(not another model), then you may be able to use jrummy's root browser to unzip the ROM zip that you are trying to flash, after unzipping, find the META.INF folder and open it then edit the updater script in that file, then using jrummy's root browser compress everything back into a flashable zip, when it prompts you asking which compression level you want to use, select "best", after its zipped, make sure it's placed on your extsdcard(do NOT put it on internal sdcard). When you get in recovery, go to the advanced options and select the option that lets you wipe individual partitions, wipe the system partition and the data partition(DO NOT WIPE ANY OF THE OTHER PARTITIONS), after wiping the system and data partitions you flash the ROM and see what happens.
If you need help understanding all that, you can ask in the forum linked below.
http://forum.xda-developers.com/android/help
I hope this helps, good luck.
Click to expand...
Click to collapse
sorry i wasnt clear,
my phone now has "Kernel_Dorimanx-V10.44-LP-SGII-PWR-CORE_-[08-01]-[26-06]-LP-SGII-PWR-CORE.zip"
When im flashing "cm-12.1-20151114-NIGHTLY-i9100.zip" , i get status 6 error.
i followed the instructions on how to fix it using notepad++, and it still doesnt work. tried 4 roms, same error.
unfortunately my external sd card with the backup was wiped. so i have no rom installed.
did i brick my phone? if so let me know what i did wrong please.
much appreciated friend.

When coming from jelly bean or kit kat to lollipop you have to format system and data partition before flashing. Did you do that, you didn't mention in your last two posts that you did that.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
When coming from jelly bean or kit kat to lollipop you have to format system and data partition before flashing. Did you do that, you didn't mention in your last two posts that you did that.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I was coming from icecream sandwich, and yes, i wiped data, cache partition, and dalvik cache.

Uncle Sam the 1st said:
I was coming from icecream sandwich, and yes, i wiped data, cache partition, and dalvik cache.
Click to expand...
Click to collapse
No, those are the normal wipes, I'm talking about the format options. Which recovery do you have? CWM or TWRP?
If CWM, boot to CWM, then choose the mounts and storage option in recovery, in that menu you will see the option to format partitions, format system and data partitions, don't format any other partitions or you'll cause more problems. After they are formatted go back to main menu in recovery then continue into flashing your ROM and Gapps. If it doesn't work after that then there are probably things like your modem or bootloader that need to be updated, if that is the case then it means you need to flash any stock updates that came after Jelly bean for your device(to flash stock updates you have to be unroofed and have an unmodified system partition) and then flash your custom ROM, but you need to check that because some devices can't be rooted after certain updates have been taken, it varies from device to device.
If you have TWRP then you'll see an option saying format or wipe in TWRP, choose that option and find where you wipe system and data(again, do not format any other partitions). Then after format is done go flash the ROM.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
No, those are the normal wipes, I'm talking about the advanced format options. Which recovery do you have? CWM or TWRP?
If CWM, boot to CWM, then choose the advanced option in recovery, in the advanced menu you will see the option to format partitions, format system and data partitions, don't format any other partitions or you'll cause more problems. After they are formatted go back to main menu in recovery then continue into flashing your ROM and Gapps. If it doesn't work after that then there are probably things like your modem or bootloader that need to be updated, if that is the case then it means you need to flash any stock updates that came after Jelly bean for your device(to flash stock updates you have to be unroofed and have an unmodified system partition) and then flash your custom ROM, but you need to check that because some devices can't be rooted after certain updates have been taken, it varies from device to device.
If you have TWRP then you'll see an option saying format or wipe in the TWRP main menu, choose that option and find where you wipe system and data(again, do not format any other partitions). Then after format is done go flash the ROM.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
i have CWM but i dont see any option to format partitions. and frankly i dunno what am doin anymore
i dont wanna loose this phone it means alot to me.
i was wondering, at this point can i unroot it and go back to original firmware and then do everything again?
If so can you please post the links i will need to do so.
you have been very helpful thanks man.

Uncle Sam the 1st said:
i have CWM but i dont see any option to format partitions. and frankly i dunno what am doin anymore
i dont wanna loose this phone it means alot to me.
i was wondering, at this point can i unroot it and go back to original firmware and then do everything again?
If so can you please post the links i will need to do so.
you have been very helpful thanks man.
Click to expand...
Click to collapse
Sorry, the format options are in the mounts and storage option in recovery, i misspoke earlier, it has been a while since i used CWM, I use TWRP because of some things i do. Try doing the format system and data and then installing your ROM and see if it works.

Droidriven said:
Sorry, the format options are in the mounts and storage option in recovery, i misspoke earlier, it has been a while since i used CWM, I use TWRP because of some things i do. Try doing the format system and data and then installing your ROM and see if it works.
Click to expand...
Click to collapse
cant i install TWRP and do it like u said ? cz i tried doing the format system and data and nothing changed. :/

Turns out the Roms i was trying to install were faulty.
i downloaded a new rom and flashed it successfully.
thanks for your help Droidriven. :good:

Uncle Sam the 1st said:
Turns out the Roms i was trying to install were faulty.
i downloaded a new rom and flashed it successfully.
thanks for your help Droidriven. :good:
Click to expand...
Click to collapse
Sorry man, I was at work, I just got home. Glad you got it going, enjoy.
Sent from my SCH-I535 using Tapatalk

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