[Q] How do I retain the configuration? - Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A

Hi, I've signed up for an account quite a while ago since I was on HTC Tattoo, but this is my first post because I've gotten really desperate here but I couldn't figure out what has been wrong.
I've done searching around xda-developers and tried Googling. I have an Xperia mini pro SK17i and here's my problem:
What I've done:
1. I've unlocked its bootloader.
2. Flashed Rage Kernel (http://forum.xda-developers.com/showthread.php?t=1398910).
3. Using CWM included after flashing Rage Kernel, I flashed Hybrom V6 (http://forum.xda-developers.com/showthread.php?t=1373435).
4. Before this I partitioned my SanDisk Mobile Ultra 32GB Class 6 microSDHC for sd-ext (27.7GB of FAT32 and 4.06GB of ext2).
5. Installed Titanium Backup.
6. Yay, from Titanium Backup I could see that a2sd is enabled.
Then came the problem:
7. I POWERED OFF my device.
8. Pulled its battery out.
9. Put it back in.
10. Turned the phone back on. When it's at the homescreen, Titanium Backup is gone.
11. So, I installed Titanium Backup again. But this time, I can't see a2sd's remaining free space, means it's not enabled?
12. So, I went ahead and rebooted into recovery, reflashed the rom again, and it all goes back to step 1.
While I was doing those, I tried checking whether a2sd was enabled each time, and it seemed that it was random. Sometimes enabled, then after a reboot, it got disabled, then I reflashed again and so on.
I'm really frustrated now. Any help is really appreciated!!

Try installing Hybrom v7 now
And when ever you flash your rom everything which is inside your SD card and was associated with system files will be of no use as you have to reassign it to system after you flash your rom
To solve this,when you think you have fully working system and now you want to keep it as backup to avoid reconfiguration when you reflash your ROM then make a backup of current working ROM for this
Reboot in recovery mode of CWM
Go in backup and restore
Make a backup of your ROM and you are done !
(This backup can be found on SDCARD/clockworkmod folder)
When you want to reinastall the "Same ROM" then you can use that created backup to get back to the status where you made backup.So there is no need to reinstall software and no need to make settings again.
This backup creates MD5 check sum so it can't be used for any versions of ROM.Use it with same version of ROM.And you will get ex-sd back as you mod in before back up.
I hope you got what i said ... cause when ever you completely flash the ROM and start it freshly you will have to go to step 1 as you said and do all things again so backup is good way to avoid this frustration and problem
And because of that sd-ext will not work...

Thx for the advice.
But I still can't get a2sd to work.
I connected my device to my computer, then I via adb shell I typed
a2sd check
everything seems to be okay except that sd-ext is not mounted. :'(
What should I do to get it to work?

I managed to get a2sd working consistently.
What I did was to partition my sdcard and format it separately.
Whenever I did a wipe data/system/cache CWM would wipe and format the sd-ext partition too, because of this, upon flashing a new ROM, a2sd would not be enabled.
But now I have another problem, I would love to move dalvik-cache to sd-ext, I tried doing it with:
#a2sd cachesdreset
then it reboots my device, but it ended up in a bootloop.
What should I do next?

I found out another issue. Everytime I pulled the battery out, my Xperia mini pro would fail to mount sd-ext.
THEN I would have to first do:
# a2sd repair
then the device reboots, then:
# a2sd reinstall
then it would get a2sd back again. But this time, all of the settings for the apps on sd-ext are lost.

i don't know bro
sorry
sent by
Xperia Mini Pro

scrotumsasi said:
i don't know bro
sorry
sent by
Xperia Mini Pro
Click to expand...
Click to collapse
If you have nothing to say, don't post at all. We don't need random spam here like this.
Also, this topic is 4 months old, why bump it?
Sent from my Xperia Live using xda premium

Related

[Q] CM7 RC1 upgrade issues and questions

I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
kabell4 said:
I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
Click to expand...
Click to collapse
Regarding your nightly question, they are full ROMs...the difference between them is the code that was committed within the previous 24 hours. Of course that also means that, in theory, some of the nightlies could be 100% the same...anyway, the nightlies can be a beautiful thing or a disasterous thing...usually if there's an issue with a nightly it is quickly found by those who flash each nightly and it is brought up around 3.2 million times and it is typically fixed by the next nightly.
Partitioning usually does mean a wipe of data on the SD. Careful!
When I upgraded to a 32GB flash from the stock 2GB from my Aria, I backed up the entire contents and restored on the new one. Apparently there is volume information stored somewhere (not sure where) and the phone couldn't recognize the card and asked me to partition it.
Because I had a backup, I decided to do so, but instead of partitioning for the entire size of the chip, it partitioned only 2GB!
So I had to stick it into a reader and repartition it manually and then selectively restore music, etc back on the card.
After that it worked just fine. So short version: yes it does.
kabell4 said:
I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
Click to expand...
Click to collapse
You will need to creaate an sd-ext partition to fix the issue of installing (larger) apps with CM7.
The best way would be through ROM Manager.
wifi
Installed the RC2 and can't connect to a hidden SSID wifi network.
That is a known issue with the wifi driver on cm7 thus far. Not sure if it will be corrected though. Anyone else know if it is in the works?
"Do you mind if I turn up the AC?"
I believe if you flash to nightly 14 all will be good, not 100% sure though.
TheFurnace said:
That is a known issue with the wifi driver on cm7 thus far. Not sure if it will be corrected though. Anyone else know if it is in the works?
"Do you mind if I turn up the AC?"
Click to expand...
Click to collapse
As far as I know there are no plans to change it. But then again we weren't supposed to get fm radio working either...
Sent from my cm7 Aria using XDA App
Too true. Never know what is coming down the pipeline!
"Do you mind if I turn up the AC?"
stellarhopper said:
You will need to creaate an sd-ext partition to fix the issue of installing (larger) apps with CM7.
The best way would be through ROM Manager.
Click to expand...
Click to collapse
Great input from everyone. Thanks! Following up on the sd-card partitioning... I have a new 8g card and want to more to CM7. If I partition it, what happens when I restore the backed up app using My Backup Root? And, what is the best partition configuration, why, and what info get store in each section (ext)?
Thanks...
kabell4 said:
Great input from everyone. Thanks! Following up on the sd-card partitioning... I have a new 8g card and want to more to CM7. If I partition it, what happens when I restore the backed up app using My Backup Root? And, what is the best partition configuration, why, and what info get store in each section (ext)?
Thanks...
Click to expand...
Click to collapse
The easiest way to partition is using your ROM manager.
Just select the max size for SD-EXT (I think it would got to 512MB), and none for swap.
I'm not sure if this would have any effect on your backup - I myself started out from scratch and got my apps from the market even though I had made an Astro backup...
You will store all your stuff - music, pictures etc in the normal partition. The SD-EXT will be automatically handled by the phone.
Tried flashing Nightly 22 on my Aria from 17. I spent a lot of time customizing 17. Is there a way to keep all of the old home screens? Also, GPS lock isn't working for me. Using MyBackup Root for Apps, but it seems to duplicate the apps?
kabell4 said:
Tried flashing Nightly 22 on my Aria from 17. I spent a lot of time customizing 17. Is there a way to keep all of the old home screens? Also, GPS lock isn't working for me. Using MyBackup Root for Apps, but it seems to duplicate the apps?
Click to expand...
Click to collapse
You should be able to flash each new nightly without losing any of your settings/customizations/homescreens and apps.
While upgrading from ROM manager, just check the backup option, don't check wipe data and cache.
I can confirm this works transitioning from 14 to 22 because I just did it yesterday night
As for the GPS problem, thats a known issue - the workaround is to make a nandroid backup of your current cm7, then do a complete phone reset, then do a nandroid restore of cm6 or 6.1 (hope you have one), do another factory reset, and restore your cm7 from the backup you took in the 1st step
stellarhopper said:
You should be able to flash each new nightly without losing any of your settings/customizations/homescreens and apps.
While upgrading from ROM manager, just check the backup option, don't check wipe data and cache.
I can confirm this works transitioning from 14 to 22 because I just did it yesterday night
As for the GPS problem, thats a known issue - the workaround is to make a nandroid backup of your current cm7, then do a complete phone reset, then do a nandroid restore of cm6 or 6.1 (hope you have one), do another factory reset, and restore your cm7 from the backup you took in the 1st step
Click to expand...
Click to collapse
first of all, i would never suggest using rom manager for things such as that. historically it has only caused problems and has been more of an inconvenience than anything. second of all, when you boot into CWM and do it the right way, don't wipe data, it's suggested but not necessary that you wipe cache and dalvik, then flash the rom and you'll be good.
Thanks to both of you. Big help and not deleting the data did the trick. Looks like I'm good to go and GPS is working well again. Is there a way to ensure I don't have duplicate apps taking up space on the card and phone? I'm getting errors on moving some apps to the sd card.
kabell4 said:
Thanks to both of you. Big help and not deleting the data did the trick. Looks like I'm good to go and GPS is working well again. Is there a way to ensure I don't have duplicate apps taking up space on the card and phone? I'm getting errors on moving some apps to the sd card.
Click to expand...
Click to collapse
Not all apps can be moved to the FAT32 partition on the SD card. Widgets also, won't work properly if moved to the SD FAT32.
If you need more memory, look into (read up) partitioning your sd card with a ext3 partition and installing S2E or Dark Tremor a2sd (DT a2sd).
zervic said:
first of all, i would never suggest using rom manager for things such as that. historically it has only caused problems and has been more of an inconvenience than anything. second of all, when you boot into CWM and do it the right way, don't wipe data, it's suggested but not necessary that you wipe cache and dalvik, then flash the rom and you'll be good.
Click to expand...
Click to collapse
Oh, I had no idea about that, thanks for the info.
I've been using ROM manager without any problems so far, apart from one lately, that when I reboot to recovery, I always get an error screen - exclamation mark in triangle...but I just pull the battery and reboot into recovery manually and it starts whatever command I had given it (backup/new rom) automatically...

[Q] anyone tried cyangonmod 7???

[/FONT]
hi anyone tried cyangonmod 7...bcz i am using void rom n i loved it n dont want to waste my time for bugging based rom....so if any 1 try this...then explain about that rom n also discuss about the bugzing matters of that rom
shyammm said:
[/FONT]
hi anyone tried cyangonmod 7...bcz i am using void rom n i loved it n dont want to waste my time for bugging based rom....so if any 1 try this...then explain about that rom n also discuss about the bugzing matters of that rom
Click to expand...
Click to collapse
I've been on CM7 by almost a week now, and I can tell you it's amazing. Very smart rom, lots of customizations possible, gingerbread based...
The only side effect is that it's still on beta stage. This means that has a list of medium and small bugs that could upset the phone user. It depends on what kind of user you are. If you like to try new features and don't mind encountering some little issues, then I recommend you to give it a shot
For any reference, question, problem, read the CM7 thread in the development branch.
hey thanx then i will try today xda rocks...!!!!!!!
CM 7 is awesome!!! But still there are some bugs in beta 1.1 like after a call, sometimes the screen turns black and returns to usable state after a minute or so. There are some bugs in DSP manager and hardware decoding of videos don't work. But remember it is still beta, so no complaints
Sent from my LG-P500 using the XDA mobile application powered by Tapatalk
Heyyy , where can i get this rom u r using . I still finding for it
Sent from my LG-P500 using XDA App
wwe007 said:
Heyyy , where can i get this rom u r using . I still finding for it
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
Here it is .
http://forum.xda-developers.com/showthread.php?t=946354
free2talk.183 said:
CM 7 is awesome!!! But still there are some bugs in beta 1.1 like after a call, sometimes the screen turns black and returns to usable state after a minute or so. There are some bugs in DSP manager and hardware decoding of videos don't work. But remember it is still beta, so no complaints
Sent from my LG-P500 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
For the black screen you can press the proximity sensor or download the latest version
hy everybody
i flashed my phone, here's what i did,
i installed z4root @Permanent , then i copied flash_image and
recovery-RA-GNM-thunderg-1.1.0.img , all command's worked except this one mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak , i continued , then i downloaded the CM7 b2 by mik, format.zip , kernell.zip by mik, googleaps.zip by mik, ii entered the boot mode , i flashed format , then kernell , then cm7 then googleaps , then i chose reboot , the phone rebooted showed me LG logo , then CM7 Android LOGO and it froze, ii had to remove battery , and restart phone and the same it froze,
can anyone help me ?
sorry for my bad english
@xzet2
I too had the same problem. Here's what I did :
(First wipe all cache, dalvik, android.secure (?) , factory...etc.)
1) Reboot in recovery
2) Flash the format.zip ( or better yet, the Debug-FormatSYSTEM.zip )
3) Flash cm7 beta2
4) Reboot into CM7 beta2
5) Reboot into recovery
6) Flash gapps
7) Reboot into CM7 beta7
Hopefully, it'll work.
Can any of the CM7 users tell me what all is different in it as compared to normal 2.2/2.2.1 ROMs?
Awsome 2.3 for Optimus One
Hello to all,
Great build of Gingerbread for P500H.
Just installed last night and seems to be great.
For tethering, download Android Wifi Tether from Market.
So far no black screen issues.
Gps getting a faster lock then with original rom.
However, bluetooth still seems not to work properly.
Thanks a bunch
My device, Opti one from Telus unlocked and using Bell
cyanide911 said:
Can any of the CM7 users tell me what all is different in it as compared to normal 2.2/2.2.1 ROMs?
Click to expand...
Click to collapse
It is much faster than Froyo ROM
Hi, I have question about CM7. When I want upgrade from .void and save some kind of image of my system, can I do it without consequences? I mean make nand backup, flash CM7 and when wont like it I could return back to void and use it as before using restore nand backup am I right?
k3rb3r0s_cz said:
Hi, I have question about CM7. When I want upgrade from .void and save some kind of image of my system, can I do it without consequences? I mean make nand backup, flash CM7 and when wont like it I could return back to void and use it as before using restore nand backup am I right?
Click to expand...
Click to collapse
Hi, yes, it is possible, I have the same option of going back, I also used .void, and wanted to try CM7, but I was very impressed by .void ROM, and I have just finish all customizations, so I didn't want to loose it all. Here's what you need to do:
Start phone in recovery, and try to make nand backup (nand + ext + .android_secure) but what happened to me, it wrote an error and that I have to make it via adb shell. You will find how to install adb here:
addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
(Sorry, I'm still quite new to forum, so I can't post it as link)
When you have adb, run cmd and type (Phone must be connected and in recovery mod, and have to have mounted /system - but I'm not sure about mounting ):
"adb devices" - you should see your devices with serial number.
"adb shell"
"nandroid-mobile.sh -b" - this will start backup to your SD card into "nandroid" folder
When you have your backup done, you can start flashing CM7. I wiped data+cache, then flashed "Debug-FormatSYSTEM.zip" from CM7 thread, flashed CM7 itself, restart your phone and you should be running CyanogenMod
note: if you want to flash Google apps (I assume you would), you have to boot CM7 at least once, because if you flash it immediately after flashing ROM itself, you will see .void booting screen and phone will freeze, and you will have to flash it all again.
And finally, if you'll prefer going back to .void, just restore your backup in recovery mod, and you're back I have two backups, one of .void, one of CM7, and can switch theese ROMs (by restoring backups) in up to five minutes
Hope it helps
Man its awesome. Real speedy. Installed yesterday. I even installed Darktremor a2sd. It is also working cool. Moved cache and data all to my SD.
Cm7 though, does not have titanium backup pre-installed. Rename ur titanium backup folder before u install. I lost mine. Got over written.
Will be testing during week end.
Here is what i did.
Downloaded the 3 files from the first post.
1. Backed up my apps using Titanium.
2. Backed up contacts.
3. Booted into recovery.
4. Connected into PC.(Linux in my case.)
5. Formatted the ext partition to ext4.
6. Deleted the Android folder in the fat partition.
7. Wiped cache, Dalvik Cache, and android_secure from recovery.
8. Copied the 3 files into the fat partition.
9. Copied the Darktremor A2sd zip (Do a google search for "Darktremor a2sd zip" without quotes)
10. Flashed the Debug-FormatSYSTEM.zip and the ROM.
11. Then rebooted.
12. Again Booted into Recovery.
13. Flashed the Darktremor A2sd zip.
14. Reboot and start terminal app.
15. su (to get root access)
16. a2sd cachesd (phone will reboot)
17. a2sd datasd (phone will reboot)
Thats it folks.
Ganesh
Update:
No Black screen after making/receiving phone call.
Sent from my LG-P500 using XDA App
Yes, it's great, but there are some small problems with black screen after calls for me, slow GPS and the most important is battery drain. But its still beta and its amazing on the other side. I am looking forward to next steps beta 3 or rc.
I'm testing it too, It's relly great and fast.. but i've found some bugs, hope that devs see this thread as well(I don't have permitions to post on the official thread):
- Black screen after call;
- Do not save the keyboard selection over reboots(I have to activate a select every boot)
- Can't connect to eduroam, don't know why tho..
EDIT: GPS icon is not showing on status-bar.
I relly apreciate the job done!

[Q] updating gsb 2.0 to 2.6?

So, I'm kinda new at this, as I was told by the forums when trying to post this question in the official gsb thread
I got an eris a few weeks ago for free, and its my first android device. I used it for a while, then rooted it and installed GSB.v2.0-CM7.0.0_RC2_STABLE
I've got it all customized and got some cool apps installed and am loving it. My question is, can I just go into recovery and install GSB.v2.6-CM7.0.0_RC4_STABLE and be good to go, or do I have to back up all my apps and settings and start fresh? I have most of my apps moved to sd. Will they be okay? Also, I went into system and changed my bootscreen, lock and unlock sounds, and added a boot script. I will have to back those up and redo them if anything, right?
skot85 said:
So, I'm kinda new at this, as I was told by the forums when trying to post this question in the official gsb thread
I got an eris a few weeks ago for free, and its my first android device. I used it for a while, then rooted it and installed GSB.v2.0-CM7.0.0_RC2_STABLE
I've got it all customized and got some cool apps installed and am loving it. My question is, can I just go into recovery and install GSB.v2.6-CM7.0.0_RC4_STABLE and be good to go, or do I have to back up all my apps and settings and start fresh? I have most of my apps moved to sd. Will they be okay? Also, I went into system and changed my bootscreen, lock and unlock sounds, and added a boot script. I will have to back those up and redo them if anything, right?
Click to expand...
Click to collapse
You will lose your bootscreen during any ROM flash, plus whatever your boot script is I assume it's somewhere where it would get lost, too.
This may not work for your apps and system settings, but it's safe to try, then you'll know for sure if it'll work.
1. Go to your recovery and create a Nandroid backup of everything just the way it is.
2. Wipe Dalvik cache ONLY, do NOT Factory Reset/Wipe Data.
3. Flash GSB v2.6 and immediately after flash the GAPPs package, just like before.
4. If you had flashed the Cache2Cache script before you have to do that again as well, right after flashing the GAPPs.
5. Reboot and test everything to see if everything works to your satisfaction.
If it's doesn't then you have the Nandroid backup that you can restore. I can provide instructions that I use, and at least one other person has recently used and reported good about which uses Titanium Backup, but you'd really probably want to buy it off the market for it to be easier to do Batch backups and Restores (choose Menu/Batch from TB's main screen).
1. First, make sure the option is checked in TB's preferences to "Force to same location". FYI I do NOT use the checkbox for "Migrate system data". At THIS time (you can change it later), I suggest changing the Compression method to No Compression. This'll make sense in step 6.
2. From Menu/Batch, choose "Backup all user apps + system data".
3. Boot into recovery, do a COMPLETE wipe (Factory Reset/Data/Dalvik cache), flash your ROM and then your GAPPs (it's recommended at this time to NOT flash C2C just yet).
4. Reboot, SKIP setup of your Google account, go into Preferences/CyanogenMod settings/Application and check the box for "Allow application moving". I also change "Install location" to External, but that's up to you; this is just what works for me.
5. Boot back into recovery and flash C2C and reboot the ROM again.
6. Use File Manager, which comes with GSB and navigate to the TitaniumBackup folder (not TitaniumBackup-system). Find the Titanium Backup apk app installer file and reinstall it from here.
7. In TB, under Menu/Batch, choose "Restore all apps with data".
After this is done, reboot. If this works for you and you want to do this again in the future, you can make a copy of the Titanium Backup apk file to some other folder, that way you can re-enable compression in TB's preferences for future backups. I recommend LZ0.
I've been using this second method for the last 3-4 new versions of GSB, don't know how it would work with such a big jump in versions. If neither of these work for you, let me know if you still need help.
You will lose your bootanimation and any scripts you have but your apps will be fine. Like WRT said above just make sure you do a nandroid back up in recovery then wipe cache only. Once that's done flash 2.6 and gapps. Enjoy!
DINC|CM7|SLAYHER#27
Awesome. I had done a nandroid and ti backup to prepare, but I never saw the option in ti for force same location. I know how to backup and reinstall my lockscreen sounds and bootani, so I've got that down. Now that I look there's a 2.7 release which integrates the sdcard speed fix, so I won't need my init script now
Thanks for clearing that up for me, I'll post back when its done and tested if there's any issues.
Update: Well everything worked great! Thanks for all the help guys

[Q/A] Boot Manager Guide and Discussion Thread also works on hboot 1.50 s-on

This thread is for noobs by noobs , a place to talk about the app so that we don't clutter the ROM threads .
I hope this works out and helps anyone including myself with using this app.
Here is another GUIDE by JJsax posted on The Root Of All EVO that is a lot more detailed then this one.
The Official forum for BootManager is Init2winit if you would like to learn even more about the app.
As I learn about this app ,as to how and what works with it I'll update this and maybe it will help everyone out that is trying to use BootManager.
This app also works with EVO 3D's with hboot 1.50 s-on
Thank XDA member mnomaanw for that information.
If you use this app and have the time to reply to this post , please share what ROMs you've got to work and a little info on how you installed it. This way I can add it to the op to make it easier and faster for everyone to find.
This is what I've learned so far.
How to install* ROMs via Boot Manager...
Thank seraph863 for filling me in and writing this up. I just changed a few details cause his was for a specific ROM.
MAKE SURE THE ROM IS ON THE ROOT OF YOUR SD CARD NOT IN ANY FOLDERS
1.)* PURCHASE Boot Manager. It does a License check upon boot, so your jacked version will just give you a headache. Seriously, I tried it. Doesn't work.
Here is a Market link to Boot Manager if you didn't already purchase it.
1.a) IF you didn't purchase it... WIPE ALL Boot Manager data and files, including the folder on your SD Card. Then buy it and let it setup again.
2.) Open SuperUser. Hit Menu -> Settings -> Disable Logging.
3. Open BootManager. If you're at work and on Wi-Fi, you may not pass the License check due to firewall issues. If you get a black screen, or license failures, switch to 3/4G and try again.
4.) If all is good, you're asked to Setup the Phone. Do so now. [ You will need to set up your Phone ROM any time you flash a new ROM or kernel to your phone ROM.]
5.) Once installed, hit Menu -> Settings -> Force Large Boot.img
6.) Swipe right to Slot 1. Hit Install .zip and browse to your downloaded ROM.zip file. Make sure to check the Wipe System, Data, and Cache boxes so that it will wipe before it flashes the ROM. Select EXT4 as the file structure.
[This is the important part. This build will take a LONG time. Do NOT use your phone while it is running.]
8.) Once the install has been successful if you need to flash a kernel , theme gapps etc..., go back to Slot 1 and select Install .zip (again). Choose the .zip file. Do NOT wipe system, data or cache. It will ask you to over write it just hit OK.
9.) You should now be ready to boot to your new ROM! Celebrate!
Since this is for the EVO 3D I recommend to always use ext4 as your file structure.
If you get any error messages start over.
Known working ROMs to my knowledge.
These are ROMs that I've set up.
Infected Eternity Phone ROM and sd ROM
KMyers CM7 beta 7.4* with gapps ext4 sd ROM
MeanROM ext4 sd ROM
TrevE Zone v2.3.12 ext4 phone and sd ROM
Mikrunny ext4 phone ROM and sd ROM
XDA members setups
JJsax setup
CDMA Evo3D
hboot 1.50 s-on
TWRP 2.0 touch recovery
Phone ROM SteeleROM 2.73
ROM1 CM9 (The latest version couple days old)
ROM2 Evervolve ICS
mnomaanw's set up
PhoneROM: ViperROM Redline v2.5 RC2
ROM1:CyanogenMOD9
ROM2:MIUI v2.1.6
I've found it to work better to flash and set up my ROM on the phone ROM and then back it up and restore it to a slot.
If your having problems restoring backups and your using TWRP recovery try using CWM. I was having issues with TWRP and since I went back to CWM (touch and 5.0.2.0 both work great but there is no usb mount on the touch version) and I haven't had a single issue restoring a backup to a ROM slot.
My setup will be changing all the time.
CDMA EVO 3D
Eng Hboot s-off
Radio 1.06.00.1216
Phone ROM Infected Eternity Sense 3.0
ROM1 Mikrunny
ROM2 EVOZone
ROM3 SteelROM
ROM4 MeanROM Aria51
Thank you for putting this here. I know I'm to blame for going off topic in some threads about Boot Manager.
I too am having issues getting a ROM to load into slot 1.
Here's my setup...
SteeleROM 2.73
Anthrax #2 kernel
Over 5GB of storage space available.
HBOOT 1.50
TWRP 2.0 recovery (the newest touch one)
I load steele just fine as the phone ROM then try to load CM9, or whatever other ROM into slot 1 it goes through everything then it get's killed at mounting img's. I have it setup for screen on, to load large files, and I even have SU logging turned off. This happens everytime I try to load a ROM into slot 1 it just kills it and never finishes 100%
JJsax said:
Thank you for putting this here. I know I'm to blame for going off topic in some threads about Boot Manager.
I too am having issues getting a ROM to load into slot 1.
Here's my setup...
SteeleROM 2.73
Anthrax #2 kernel
Over 5GB of storage space available.
HBOOT 1.50
TWRP 2.0 recovery (the newest touch one)
I load steele just fine as the phone ROM then try to load CM9, or whatever other ROM into slot 1 it goes through everything then it get's killed at mounting img's. I have it setup for screen on, to load large files, and I even have SU logging turned off. This happens everytime I try to load a ROM into slot 1 it just kills it and never finishes 100%
Click to expand...
Click to collapse
Mine say they install fine and they finish but when I hit boot to the slot it just gets stuck on the splash screen.
I had TrevE Zone on my phone ROM but just switched to eternity. I got MeanROM to install in slot 2 and it booted up fine and is running great but thats the only one I out of the 3 I tried. I set the boot.img to large or what ever the setting is cause thats what they said to do in the video on the site for the app. My real issue though is that restoring my backup to a slot it installs to my system memory. I would like to be able to install backups cause I've read they run better. Hopefully some that knows more about this will come in here and school us a little, I'll even add it to the op and make this a guide if we get enough info.
Here's my quick and dirty instructable I posted in the CM9 thread.
How to install this via Boot Manager...
1.) PURCHASE Boot Manager. It does a License check upon boot, so your cracked version will just give you a headache. Seriously, I tried it. Doesn't work.
1.a) IF you didn't purchase it... delete ALL Boot Manager files, including the folder on your SD Card. Then buy it and let it setup again.
2.) Open SuperUser. Hit Menu -> Settings -> Disable Logging
3. Open BM. If you're at work and on Wi-Fi, you may not pass the License check due to firewall issues. If you get a black screen, or license failures, uninstall BM and delete the folder. Switch to 3/4G and try again.
4.) If all is good, you're asked to Setup the Phone. Do so now.
5.) Once installed, hit Menu -> Settings -> Force Large Boot.img
6.) Swipe right to Slot 1. Hit Install .zip and browse to your downloaded CM9 .zip file. Wipe System, Data, and Cache. Select EXT4 as the file structure
7.) This is the important part. This build will take a LONG time. Do NOT use your phone while it is running.
8.) Once the install has been successful, go back to Slot 1 and select Install .zip (again). Choose the Google Apps .zip file. Do NOT wipe system, data or cache.
9.) You should now be ready to boot to your new ROM! Celebrate!
Warning: Several users report to NOT use any Backup app such as Titanium to restore your apps and data, since the apps on this ROM are very very different. Your mileage may vary.
FYI I'm doing this by memory, so the minor steps might not be accurate (i.e. disable Superuser logging).
If you get any error messages, start over. I assure you, this process worked for me step by step.
Go to their official forum
Applications-->boot manager
You will find my thread named [REF]working and not working rom list
There are many phones
And if you test a rom that is not listed please report if it is working or not
Thanks
Sent from my HTC Desire S using XDA Premium App
I saw your guide in the cm9 thread and tried it with no luck I did exactly what you said and everything seemed to go fine but when I hit boot to ROM on slot one where I installed the ROM I'm stuck on the splash screen. Any ideas why? Thanks for the help also.
kylon said:
Go to their official forum
Applications-->boot manager
You will find my thread named [REF]working and not working rom list
There are many phones
And if you test a rom that is not listed please report if it is working or not
Thanks
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
I was on there I even posted my issue and my log but haven't gotten any help. I did see your list of ROMs but didn't know if its up to date.
I'll have another look at it cause I really want to get this to work and its driving me crazy cause I can usually figure problems out on my own or by searching but I just can't get this.
Thanks for the replies.
linsalata28 said:
I saw your guide in the cm9 thread and tried it with no luck I did exactly what you said and everything seemed to go fine but when I hit boot to ROM on slot one where I installed the ROM I'm stuck on the splash screen. Any ideas why? Thanks for the help also.
Click to expand...
Click to collapse
Which ROM are you using?
I would start over. Use a file manager to delete your ROM from the SD Card and take another image. Make sure you have plenty of storage on your SD card. You could also try clearing the Cache and Dalvik.
You can always get back to your phone ROM manually by booting to Recovery and flashing sdcard\bootmanager\phonerom\update.zip
Edit: Don't forget to check "Use Large boot.img" within Boot Manager
seraph863 said:
Which ROM are you using?
I would start over. Use a file manager to delete your ROM from the SD Card and take another image. Make sure you have plenty of storage on your SD card. You could also try clearing the Cache and Dalvik.
You can always get back to your phone ROM manually by booting to Recovery and flashing sdcard\bootmanager\phonerom\update.zip
Edit: Don't forget to check "Use Large boot.img" within Boot Manager
Click to expand...
Click to collapse
Should I just delete the whole bootmanager folder and clear the data for the app also?
another thing is why when I restore a backup to a slot its installing to my internal memory?
Yeah I just had another look at your list and there aren't many ROMs for this phone on there and they look old.
Thanks again for the help.
It up to date
Anyway gflame is busy
What do you do to install the rom
And wich rom?
Sent from my HTC Desire S using XDA Premium App
I wiped everything out and starting over. I'm going to just try and install viperom in one slot and see if that boots, then I'm going to try and restore a backup to another slot from within a ROM slot to see if that will fix my internal memory issue cause it wont have anywhere to install to . I'll post back with what happens.
kylon said:
It up to date
Anyway gflame is busy
What do you do to install the rom
And wich rom?
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
I disabled logging in su checked off larg boot.img then whet to slot one hit install zip choose cm9 ext4 then checked all the wipe opinions, when that finished I flashed the gapps the same way but without wiping . Everything finished with that I didn't get any errors but when I went to boot to that slot it just hung at the splash screen.
I did that 2 times with cm9 , 1 time with the Eternity ROM sense 3.0 r130 , 1 time with Team Nocturnal's Blackened ROM and they all got stuck at the splash screen.
I did get MeanROM to work using those same steps last night.
Now with the restore of my backup I did basically the same thing but it doesn't give any wipe options when you install it but it would get an error saying boot.img something like that and then I would get a low memory popup saying I only had about 30mb left internal memory when I had over 800mb when I started.
Edit: I have about 6gb free on a 16gb class 10 sd card. I believe its a Samsung card I think.
Edit2: I finished flashing viperom and now that to is stuck on the splash screen. Is there a way to wipe caches for that slot and fix permissions like you would for a regular ROM in recovery if something like this happened.
I'm really starting to think I wasted $3 this is very frustrating sorry.
Thanks for your replies and trying to help.
I went into recovery to go to flash the update zip to restore my phone ROM but when I open the bootmanager folder I don't see anything in it. I'm using twrp 2.0 recovery. Could this have something to do with my problems?
linsalata28 said:
I went into recovery to go to flash the update zip to restore my phone ROM but when I open the bootmanager folder I don't see anything in it. I'm using twrp 2.0 recovery. Could this have something to do with my problems?
Click to expand...
Click to collapse
The steps in your previous post were all correct, except you said you turned OFF "Use large boot.img" ? Make sure that option is ENABLED (has an X on it)
I'm confused as to why the app is trying to install to your internal memory... Mine installs to my SD Card. Make sure the USB cable is not plugged into the phone, and try increasing your screen timeout so it doesn't sleep during the install.
The fact that you're getting the splash screen means you're getting somewhere. Maybe you're being too impatient on the install? Wait a few minutes even after it says Install Complete before continuing.
seraph863 said:
The steps in your previous post were all correct, except you said you turned OFF "Use large boot.img" ? Make sure that option is ENABLED (has an X on it)
I'm confused as to why the app is trying to install to your internal memory... Mine installs to my SD Card. Make sure the USB cable is not plugged into the phone, and try increasing your screen timeout so it doesn't sleep during the install.
The fact that you're getting the splash screen means you're getting somewhere. Maybe you're being too impatient on the install? Wait a few minutes even after it says Install Complete before continuing.
Click to expand...
Click to collapse
I said I checked the larger boot.img off meaning it was enabled sorry for that misunderstanding. I flashed 2 of the slots last night and didn't even test them till today so I don't think that its cause I'm not waiting long enough. Why would none of the folders inside of the bootmanager folder show up in twrp recovery? Could I copy and paste the phone update.zip to the root of my sd card so that I can recover without having to nand restore cause I've already wiped and restored about 10 times trying to get this to work.
Sent from my Eternity 3D using tapatalk
linsalata28 said:
I disabled logging in su checked off larg boot.img then whet to slot one hit install zip choose cm9 ext4 then checked all the wipe opinions, when that finished I flashed the gapps the same way but without wiping . Everything finished with that I didn't get any errors but when I went to boot to that slot it just hung at the splash screen.
I did that 2 times with cm9 , 1 time with the Eternity ROM sense 3.0 r130 , 1 time with Team Nocturnal's Blackened ROM and they all got stuck at the splash screen.
I did get MeanROM to work using those same steps last night.
Now with the restore of my backup I did basically the same thing but it doesn't give any wipe options when you install it but it would get an error saying boot.img something like that and then I would get a low memory popup saying I only had about 30mb left internal memory when I had over 800mb when I started.
Edit: I have about 6gb free on a 16gb class 10 sd card. I believe its a Samsung card I think.
Edit2: I finished flashing viperom and now that to is stuck on the splash screen. Is there a way to wipe caches for that slot and fix permissions like you would for a regular ROM in recovery if something like this happened.
I'm really starting to think I wasted $3 this is very frustrating sorry.
Thanks for your replies and trying to help.
Click to expand...
Click to collapse
My phone:
Phone ROM: SteelROM 2.72
Slot 1: AOSP ICS - wifi doesn't work
Slot 2: CM9 - (google talk and books FC)
Slot 3: MIUI
Slot 4: CM7 (kmeyers)
Boot Manager has a problem trying to restore from a NAND backup, it did the same thing to me where it was installing to the phone's internal memory. I was trying to figure out the problem, but I moved on without success.
I've had the best time installing tricking ROM's by this method. I installed CM7 to a slot, booted into CM7 and installed the ICS and CM9 from there. It's been pretty successful.
If you are getting it to freeze with mounting images, I came across this issue because my SD card did not have enough room. You can try to free up some more space to see if this is the same issue.
I had most problems installing due to not enough space on my SD card, I now have a 32gb card, and have had no issues
Also, I've never had to set it to large boot.img to get things to work, and make sure you disable logging in SU, and use EXT4
---------- Post added at 02:08 PM ---------- Previous post was at 02:04 PM ----------
linsalata28 said:
I said I checked the larger boot.img off meaning it was enabled sorry for that misunderstanding. I flashed 2 of the slots last night and didn't even test them till today so I don't think that its cause I'm not waiting long enough. Why would none of the folders inside of the bootmanager folder show up in twrp recovery? Could I copy and paste the phone update.zip to the root of my sd card so that I can recover without having to nand restore cause I've already wiped and restored about 10 times trying to get this to work.
Sent from my Eternity 3D using tapatalk
Click to expand...
Click to collapse
To quickly get back to your phone ROM (make sure you setup your phoneRom in boot manager first to create the update.zip file, you need to recreate this anytime you change the ROM or Kernel for your phoneROM)
Boot into Recovery
Install the update.zip inside the \boot manager\phonerom\update.zip (not sure if location is accurate, but you get the idea)
Reboot system
Phone should boot to phone ROM, or you can install any other update.zip from your slots, to boot to them etc
spookytay said:
My phone:
Phone ROM: SteelROM 2.72
Slot 1: AOSP ICS - wifi doesn't work
Slot 2: CM9 - (google talk and books FC)
Slot 3: MIUI
Slot 4: CM7 (kmeyers)
Boot Manager has a problem trying to restore from a NAND backup, it did the same thing to me where it was installing to the phone's internal memory. I was trying to figure out the problem, but I moved on without success.
I've had the best time installing tricking ROM's by this method. I installed CM7 to a slot, booted into CM7 and installed the ICS and CM9 from there. It's been pretty successful.
If you are getting it to freeze with mounting images, I came across this issue because my SD card did not have enough room. You can try to free up some more space to see if this is the same issue.
I had most problems installing due to not enough space on my SD card, I now have a 32gb card, and have had no issues
Also, I've never had to set it to large boot.img to get things to work, and make sure you disable logging in SU, and use EXT4
---------- Post added at 02:08 PM ---------- Previous post was at 02:04 PM ----------
To quickly get back to your phone ROM (make sure you setup your phoneRom in boot manager first to create the update.zip file, you need to recreate this anytime you change the ROM or Kernel for your phoneROM)
Boot into Recovery
Install the update.zip inside the \boot manager\phonerom\update.zip (not sure if location is accurate, but you get the idea)
Reboot system
Phone should boot to phone ROM, or you can install any other update.zip from your slots, to boot to them etc
Click to expand...
Click to collapse
What cm7 ROM would you recommend ? For some reason I couldn't see files inside of the BootManager folder but I checked and they are there. I have about 5gb free on a 16gb card ,I was looking into getting a 32gb if I get this app working.
Sent from my Eternity 3D using tapatalk
try
http://forum.xda-developers.com/showthread.php?t=1393613
I upgraded my card, I had about 3-4 gb free and was having problems, but once I upgraded I haven't had many since
I've purchased boot manager and when i run it, it says "application not licenced" Any fix?
spookytay said:
try
http://forum.xda-developers.com/showthread.php?t=1393613
I upgraded my card, I had about 3-4 gb free and was having problems, but once I upgraded I haven't had many since
Click to expand...
Click to collapse
cm7 worked thanks.

[Q] CWM error while making backup image of /data

This error is still not answered on the forums so im starting a new thread.
i get the error as the title.
sd card space is not the problem.
i tried formatting the sd card.
i have less than 50 apps installed.
wiped dalvik cache, and all other sorts people say on other posts.
(my phone is LG P936 so "fix permission" screws up the phone. all text disappears)
have latest cwm recovery.
and still get the error.
any answers please?
and please dont reply if you are going to write an opinion.
only answers please.
sorry for my rude behaviour but I'm sick and tired of reading posts full of opinions and "maybe"s.
Not sure if you ever got this fixed but I 'm suffering from the same error. I tried pretty much everything you tried (even fix permissions) and I have about 20GB free on my SD card so space shouldn't be an issue. I have not yet tried formatting the SD card since it has always worked and CWM is able to write to it because the following files are created:
- boot.img
- data.ext3.tar
- recovery.img
- system.ext3.tar
The files that are missing are (based on older backups):
- .android_secure.vfat.tar
- cache.ext3.tar (probably because I wiped it first?)
- nandroid.md5
I have attached the log from CWM in the hopes that someone can tell me what is wrong. The error occurs at the end of the progress bar of 'backing up /data'.
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Today I have formatted the SD card and tried again, but as expected it did not change anything.
ceoleaders said:
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Click to expand...
Click to collapse
I guess I will give this a try. Can I just install it over CWM or can they run side by side?
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
ceoleaders said:
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
Click to expand...
Click to collapse
Well, I tried TWRP and it also fails at backing up my data partition. The log is a bit more clear though and it seems to get stuck on "/data/data/com.android.vending/cache/images" which is the last line before it gives an error. I checked the "images" folder and it seems empty but I cannot delete it. Tried ES File Explorer and Terminal Emulator but no way to get rid of it. The folder appears to be related to Google Play, so I cleared all data and cache from Google Play, even uninstalled the updates but there 's simply no way to get rid of it. I 'm not sure if this is the reason why the backup fails, but I CAN copy the folder and even rename it.
Pff looks like I 'm going to have to do a clean install after all .
Hello, I too have this problem and unfortunately TWRP is not available for my phone.
I used to be able to do CWM backups fine on my old phone, and they work great on my tablet. But they consistently fail at "/data" on my Galaxy Ace II x. Might it be because I'm using Link2SD? I don't see why that would cause a problem, but maybe it's having trouble with the symlinks?
Hmm. Seems the issue was that, despite having only 1.28 GB total available storage space on stock, the backups wanted more than 4 GB. Cleared some room on my microSD card and suddenly backups worked fine! Of course, shortly after I installed CyanogenMod, which has much smaller backups...
Sent from my GT-S7560M using Tapatalk 4
I forgot to report back here but the only way I found to fix the problem was by doing a clean install. After that, I was able to backup my data partition again. I then restored my apps ' data with TB and was unable to backup the data partition again. I 'm guessing one of my apps had corrupt data, but never got to find out which one it was.
maybe your partition not match with recovery, like something wrong vold.fstab
Just in case anyone still wants to know how to fix this, I managed to solve it by running these commands:
1. run adb shell in recovery.
2. unmount data partition (umount /dev/block/mmcblk0p26). -> this one failed so I skipped it
3. run e2fsck /dev/block/mmcblk0p26
See http://forum.xda-developers.com/showpost.php?p=48659092&postcount=868 for original post.
I got a few HTREE errors and a bunch of duplicate names which I renamed when prompted. Booted the phone and rebooted into TWRP and now I am able to backup my data partition again. :good:
EDIT: Problem reappeared so I tried the above commands again but it said that the filesystem was clean. Ran 'e2fsck -f /dev/block/mmcblk0p26' instead and had to fix a bunch of HTREE errors from Facebook again and duplicate names from Xprivacy but now I 'm able to backup my data partition again.
Dude just selest the backup format as both zip and tar filea

Categories

Resources