CleanViewpad7 v1.0
based on latest official stock Viewpad 7 firmware Android 2.2.2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With installed ADW Launcher EX:
This build is for Viewsonic Viewpad 7. I’ve made this build mainly because I had one big problem with stock one – it was offering little space for my apps. I've used this opportunity to add extra features and remove some annoying ones. Here is the list of changes:
based on latest official stock Viewpad 7 firmware Android 2.2.2
added Darktremor Apps2SD 2.7.5.2 functionality (require that you have extra partition on your SD card for storing your apps; exact procedure to create one is described in installation procedure)
fully deodexed and zipalligned ROM
ROM is rooted (Superuser.apk + su)
installed BusyBox with support for init.d scripts
replaced "Welcome" boot animation with stock android 2.2 animation
installed Gingerbread keyboard
installed Morelocale2 for more languages
modified framework-res.apk and services.jar with Gingerbread look like + % battery
removed Aldiko,RSS, TouchPAL_M20
updated gapps to newest version (Gmail, GoogleQuickSearchBox, Maps, Market, VoiceSearch) & YouTube
modified host file for ad-free
Now you don’t have to worry about decreasing internal storage when you install more application. You don’t also lose access to application when you phone is connected in drive mode to computer, because application data is being hold on ext3 partition on SD card. That partition isn’t mounted when your phone is connected to computer. The things that are redirected to this partition are: /data/app, /data/app-private and /data/dalvik-cache. Firmware should also work with compatible devices such as: Cherry Mobile Superion, Commtiva Linx N700, Olivepad VT-100, Spice MI700, and Camangi FM600 but I don't have these devices, so I cannot verify. As always make a backup before installing any custom firmwares.
Requirements:
installed Clockwork Recovery Partition as described here [TOOL] Viewpad 7 Backup, Root & Recovery
Changelog:
V1.0
initial release
Installation:
Power down your device.
Power on device holding power button and both volume keys simultaneously.
Upon power up you will see the birds logo and 'enter recovery' text in the top left corner of the screen.
Use the volume keys to step through the menu, power to select and back. (there is bug in clockwork when you press volume keys it jumps 2 steps; to jump one step press and hold volume and then press power to select)
Select the "advanced->Partition SD Card" item, next select size for your Apps2SD partition (1024MB recommended), next select 0 as size of swap partition. (Remember that this will delete all data on your SD card, so make backup of SD card if you need !!!)
After the partitioning will be done select the "reboot system now" item.
Using USB cable connection or SD card reader copy CleanViewpad7_signed_v1.0.zip to root folder of SD card.
Power down your device.
Power on device holding power button and both volume keys simultaneously.
Select the "backup and restore->Backup" item to make a backup of the current firmware in case something goes wrong. The backed up ROM should be located in: /sdcard/clockworkmod/backup/date&time/
Select the "wipe data/factory reset->Yes – delete all user data” to clear old stuff.
Select the "install zip from sdcard->choose zip from sdcard" item and select CleanViewpad7_signed_v1.0.zip.
After flashing will be done select the "reboot system now" item. First boot may take a few minutes.
Migrate from stock or another build:
Make backup of your phone using Titanium Backup (select all user applications).
Copy all files and folders from SD card to local folder on your computer.
Install Clockwork Recovery Partition, create partition on SD card and install ROM as described in installation guide.
Copy all files and folders from local folder on your computer back to SD card.
Restore applications using Titanium Backup and reboot your phone.
Download:
http://www.multiupload.com/79WKJUXMX5
Credits to:
Darktremor
hucqim80
dsixda
mendozinas
-Mr. X-
If you like my work please consider donating:
Thanks everyone for donations.
Nice work bro.although it would be better to use the latest a2sd version of darktremor(2.7.5.3)
which supports ext4 partition and data2sd feature.so instead of adding a2sd 2.7.5.2 you can provide a link to the flashable zip of the latest DT-a2sd (http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip). it works i have tested it.
hi
thanks i have downloaded this from ur tablet rom post
thanks a mill this is exactly what i want will use the same give u a feedback on the same
thanks
hari
works on Olivepad VT-100
hi
this is FYI for Olivepad VT-100 users
i have Flashed this ROM and works for Olivepad VT-100
thanks for this nice rom ill give a feed back latter as i have just installed the same
Feedback
not sure if the apps are getting installed on the SD the first time i installed the ROM i did a data/factory reset
installed the rom and i had only 118MB phone storage(i have the ext partition done before stating the process)
ok then i re in stalled rom again and i still see 118 MB so i tried installed skype its a 7MB file but still i see 1MB used on the phone
not confy with titanium and i have a similar rom installed on my samsung galaxy 3
on that all i do is install the new rom without any wipe and the same works
kindly advise on the same as i really would like the apps2SD working
thanks
hari
googlehome said:
Nice work bro.although it would be better to use the latest a2sd version of darktremor(2.7.5.3)
which supports ext4 partition and data2sd feature.so instead of adding a2sd 2.7.5.2 you can provide a link to the flashable zip of the latest DT-a2sd (http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip). it works i have tested it.
Click to expand...
Click to collapse
hi
i installed this attachment on ur ROM via CWM and bang i got 154MB free on phone Storage and i can see than all installed app are on my SD so i would like to confirm that this works
one small request im more confy with the Touchpad keyboard i did try installing the one i had of the original rom its getting installed but im not getting an option to use it i think because ur apps are deodexed and the official on coming on stok rom is only odexed can any one help on this pls
but thanks now i got exactly what i want
hari
I have had huge issues getting this to flash properly, keep getting to the 3 birds and no further...followed your steps exactly...1gb ext part thru cwm and wiped everything...would flashing from another custom rom affect this ? should i try from stock maybe?
joethc said:
I have had huge issues getting this to flash properly, keep getting to the 3 birds and no further...followed your steps exactly...1gb ext part thru cwm and wiped everything...would flashing from another custom rom affect this ? should i try from stock maybe?
Click to expand...
Click to collapse
hi
i flashed from stock ROM
try flashing from stock rom it should work
flashed back to stock, rooted, flashed cwm through adb shell, reboot to recovery, wipe data /factory reset...install cleanviewpad7 signed zip and it still sticks at the 3 birds gets no further after waiting 10mins one time and 20 the next....any other ideas? I dont know why this is not working for me...I can flash other roms no problem using sut or cwm.....it seems to be flashing the file really fast ...open to anything i really want to get this going
hi buddy
i tried to help with what ever limited knowledge i had based on my experience
sorry im not a techie i just go by the instructions given and do it
even yesterday i flashed another rom and re flashed this one everything went well for me
so sorry i think on one of the developer can help u as i dont seem to understand why u are having this problem sorry im not able to help u
joethc said:
flashed back to stock, rooted, flashed cwm through adb shell, reboot to recovery, wipe data /factory reset...install cleanviewpad7 signed zip and it still sticks at the 3 birds gets no further after waiting 10mins one time and 20 the next....any other ideas? I dont know why this is not working for me...I can flash other roms no problem using sut or cwm.....it seems to be flashing the file really fast ...open to anything i really want to get this going
Click to expand...
Click to collapse
joethc said:
flashed back to stock, rooted, flashed cwm through adb shell, reboot to recovery, wipe data /factory reset...install cleanviewpad7 signed zip and it still sticks at the 3 birds gets no further after waiting 10mins one time and 20 the next....any other ideas? I dont know why this is not working for me...I can flash other roms no problem using sut or cwm.....it seems to be flashing the file really fast ...open to anything i really want to get this going
Click to expand...
Click to collapse
Remember to wipe your data,cache as well as dalvik cache before flashing the rom.
i followed step by step. once booted it showed android setup but touch screen wasnt working. any one know why? i am using viewpad 7. thanks in advance
smargarites said:
i followed step by step. once booted it showed android setup but touch screen wasnt working. any one know why? i am using viewpad 7. thanks in advance
Click to expand...
Click to collapse
hi
have u rooted added CWM & busy box only on doing these can u flash this roms
it worked on my Olivepad so im quite sure it will work for u
I still can not get this going I have tried a billion different things..wiped everything stock, still no luck. The only other time I have had this issue is an incomplete upload but if everyone else has it working from this specific upload i dont know what to say ...ill keep trying and hopefully get it soon Thanks everyone for the quick responses!!!!! Is there a way to get this packaged to flash with sut l3?
FlashoManiac said:
hi
have u rooted added CWM & busy box only on doing these can u flash this roms
it worked on my Olivepad so im quite sure it will work for u
Click to expand...
Click to collapse
yes i have it rooted. what i had to do was boot the stock rom boot.img with this rom. working great right now.
I followed the directions in the first post and then downloaded the file from post#2.
Once you have the file from post #2 on your SD card, rename it to update.zip and then boot your device into Clockwork Recovery and select the "update from zip" option. Rebooted and my device now has 167MB of available space on the internal phone storage.
Thanks guys... this is the way the device should have shipped from Viewsonic, and although it aint no Gingerbread, I'm finally happy with my Viewpad after several months if dissapointment.
One thing that I find to be very strange is that it appears that some data is saved somewhere?
Even after I performed the following:
Formatting the SD Card
Wipe data/factory reset
Wipe cache partition
Wipe dalvik cache
Load the new ROM
Did not log into any kind of google account and basically skipped all the setup options.
The device still shows all the wireless hotspot data that I logged into before. Why does it have the password for my WiFi router after all those steps were performed.
If I were to sell the device to someone else, is there any way to be sure ALL data has been cleared from the device?
Cheers!
Great work, good to see another ROM for the Viewpad!!!
Will for sure try it...
A few questions:
You are using the a2sd version of darktremor(2.7.5.3), I personally use Link2SD which also moves all data, cache,... to the 2nd partition of the SD card...
It's actively developed and it's free, so check it out...
Is this ROM with the kernel from tj-style? Then we can overclock to 824Mhz and it gives a nice speed boost...
If then you do not want to use it for your ROM, you can set it to the stock speed with SetCPU...
Thanks,
Nick
Since many people are requesting for TJstyle's oc'd kernel.I modified this ROM to add the kernel and some other stuff.
Here is the download link:
http://dl.dropbox.com/u/21654931/VPAD7_signed.zip
My quadrant score crossed the 1000 mark for the first time
Screenshot:
googlehome said:
Since many people are requesting for TJstyle's oc'd kernel.I modified this ROM to add the kernel and some other stuff.
Here is the download link:
http://dl.dropbox.com/u/21654931/VPAD7_signed.zip
My quadrant score crossed the 1000 mark for the first time
Screenshot:
hi
thanks flashed this it works on a Olivepad
can u kindly give me the same with the touchpad keyboard as i was not able to install the same on the previous rom. haven't tried on ur rom will try and keep u posted. May be in future u could start a separate rom thread for ur roms
thanks for the nice rom like the battery indicator
Click to expand...
Click to collapse
Worked perfect here! I love the boot animation! This is exactly what i needed! many thanks to everyone here for helping out!
Have installed this rom and the dark tremor update but my phone storage is still decreasing when I install apps. I have set up an ext 4 partition on my sd card.
:'(
Related
What is ClockworkMod Recovery and what is Stock Recovery?
Please explain in simple terms, benefits, possible uses?
What is Nandroid? Is Nandroid same as ClockworkMod Recovery? or Stock Recovery?
thank you
Stock recovery is just that, stock comes loaded on the phone. Allows you to wipe the phone and flash official updates.
ClockworkMod Recovery is a custom recovery that allows you to do more. First you need to root your phone then you can flash it. With Clockwork you can flash custom roms and do nandroid back ups. Nandroid backups basically back up you phone, so if you have to wipe your phone or flash something unstable you can revert back to a stable point on your phone.
That helps...would you please explain below? This is in reference to ROM manager application from Market I downloaded.
I have question though on restoring to "stock".
Let's suppose I have screwed up and can't start my phone for whatever reason, so that I won't have access to "ROM Manager" application, correct? In that case, how do I "Reboot into Recovery"? I am confused here...
When I reboot using POWER KEY and VOLUME UP key, options I see are very limited and I don't see Nandroid there, so how exactly would I able to restore from my Nandroid images?
Basically if I am hard down, can't even get to home screen, how can I restore my phone from mybackups? I think I am having small gap in my understand!
thank you so much!
When you install clockwordmod recovery, it installs a file on your internal SD vs the External SD card. When you enter stock recovery, you would choose "reinstall packages" and that would bring you back into clockworkmod recovery so you can install custom roms, perform a nandroid backup, etc...
csci1000 said:
That helps...would you please explain below? This is in reference to ROM manager application from Market I downloaded.
I have question though on restoring to "stock".
Let's suppose I have screwed up and can't start my phone for whatever reason, so that I won't have access to "ROM Manager" application, correct? In that case, how do I "Reboot into Recovery"? I am confused here...
When I reboot using POWER KEY and VOLUME UP key, options I see are very limited and I don't see Nandroid there, so how exactly would I able to restore from my Nandroid images?
Basically if I am hard down, can't even get to home screen, how can I restore my phone from mybackups? I think I am having small gap in my understand!
thank you so much!
Click to expand...
Click to collapse
rom manager is made by koush, who also makes clock work recovery.
in rom manager "flash clockworkmod recovery"
Now check your SD card (internal) do you have an "update.zip" file? Is so it probably the zip you used to root the phone, delete it and look inside the clockwork folder. you'll see "recover-update.zip" copy this to the root of your SD card and rename it update.zip.
turn phone off and turn it back on going into recovery... vol up+down and power.
Select 'reinstall package" press power to confirm.
now you are in clockwork recovery and can nadroid restore/backup, install roms etc...
You can do all ^^^ from rom manager also but if you can't get the phone to boot this can a restore or rom flash...
if you truly bugger up your phone you will need to odin a rom. Nandroid will not re flash kernel or radio ODIN will
This is trully great reply! It clarifies so much!
2 questions pls.
1) can I make Odin images of my current ROM by myself? and store away on flash drive for future rescue?
2) my Vibrant looks into internal-storage Not microSD card when I try to boot into clockwork recovery. Can I make it to look into microSD card? Do I make some directory or what? how please?
it says like this
--Install from sdcard....
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted.
I have tried twice by putting update.zip into root of sd card AND /sdcard/update.zip subfolder. but no luck!
thank you
csci1000 said:
This is trully great reply! It clarifies so much!
2 questions pls.
1) can I make Odin images of my current ROM by myself? and store away on flash drive for future rescue?
2) my Vibrant looks into internal-storage Not microSD card when I try to boot into clockwork recovery. Can I make it to look into microSD card? Do I make some directory or what? how please?
it says like this
--Install from sdcard....
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted.
I have tried twice by putting update.zip into root of sd card AND /sdcard/update.zip subfolder. but no luck!
thank you
Click to expand...
Click to collapse
1. Why would you do that? Just do Nandroid backups, its the same thing of what you're asking but so much simpler.
2. Clockwork is built to look at internal, it's good. Just drop the things you flash into the root of your internal. Internal is built in 12GB. It will always be the internal.
Are you sure its "update.zip" and not update.zip.zip?
One can made an odin image but why? just make nandroids. easier and all you really need.
sorry to calarrify... both internal memory and removeable SD card are listed as SD cards.
update.zip needs to be in root of internal memory.
zephiK said:
1. Why would you do that? Just do Nandroid backups, its the same thing of what you're asking but so much simpler.
2. Clockwork is built to look at internal, it's good. Just drop the things you flash into the root of your internal. Internal is built in 12GB. It will always be the internal.
Are you sure its "update.zip" and not update.zip.zip?
Click to expand...
Click to collapse
1) I just asked because SykesAT said above that Nandroid will not re flash kernel or radio ODIN will. In short is it very hard to make Odin image?
2) I was after booting into Clockwork recovery from SDCARD because,
A) what if I don't have update.zip on internal memory when I crash my phone? and it's too late. There wouldn't be any way for me to put update.zip, will I? wouldn't it be too late?
B) what if I don't have "whatever things" I want to flash on my internal memory? I'd like to keep my stock ROM or whatever on home PC, not carrying around all the time. You see what I am saying? How exactly will I be able to load it on internal memory from PC if I cannot even get to home screen?
I tried clockwork recovery from internal memory and it works perfect. It's just I was after microSD card for reasons above.
csci1000 said:
1) I just asked because SykesAT said above that Nandroid will not re flash kernel or radio ODIN will. In short is it very hard to make Odin image?
2) I was after booting into Clockwork recovery from SDCARD because,
A) what if I don't have update.zip on internal memory when I crash my phone? and it's too late. There wouldn't be any way for me to put update.zip, will I? wouldn't it be too late?
B) what if I don't have "whatever things" I want to flash on my internal memory? I'd like to keep my stock ROM or whatever on home PC, not carrying around all the time. You see what I am saying? How exactly will I be able to load it on internal memory from PC if I cannot even get to home screen?
I tried clockwork recovery from internal memory and it works perfect. It's just I was after microSD card for reasons above.
Click to expand...
Click to collapse
and SkyesAT just said: One can made an odin image but why? just make nandroids. easier and all you really need.
1. You shouldn't be flashing a seperate radio anyway. Unless you're in Europe but you shouldn't be on the Vibrant forum in that case anyway, at least not applying hacks/tweaks/etc from this forum (some will work some will cause problems).
Kernels.. you shouldn't be flashing them ANYWAY since you said that you're a "newbee." Kernels aren't something that you should be messing with until you're more comfortable because it'll cause problems if you don't know what you're doing.
I don't even know what you're trying to accomplish. What exactly is it?
zephiK said:
and SkyesAT just said: One can made an odin image but why? just make nandroids. easier and all you really need.
1. You shouldn't be flashing a seperate radio anyway. Unless you're in Europe but you shouldn't be on the Vibrant forum in that case anyway, at least not applying hacks/tweaks/etc from this forum (some will work some will cause problems).
Kernels.. you shouldn't be flashing them ANYWAY since you said that you're a "newbee." Kernels aren't something that you should be messing with until you're more comfortable because it'll cause problems if you don't know what you're doing.
I don't even know what you're trying to accomplish. What exactly is it?
Click to expand...
Click to collapse
I was just being careful before I start flashing my vibrant. I recently rooted and it wasn't bad and wanted to go further but thought of slowing down and learning what I read all over this forum and came up with these questions...I have made Nandroid backup now so I will try flashing custom ROM over this weekend!
it's easy.. just put it on your root of /sdcard
boot into clockwork recovery
flash a zip on your sdcard
select the one u want to flash and then reboot
as zephiK said... best not to mess with radio and kernels until you are comfortable. Not sure we even have optimized radios yet.
the quickest way to flash a rom. put the rom in a folder on the internal memory and use rom manager to isntal a rom from SD... It's a great idea to leave the clockwork update.zip in the root of your internal just incase you need clockwork recovery for a nandroid restore.
zephiK said:
it's easy.. just put it on your root of /sdcard
boot into clockwork recovery
flash a zip on your sdcard
select the one u want to flash and then reboot
Click to expand...
Click to collapse
I want to get Froyo installed if I can over weekend and be able to get Ad-Hoc working.
Does Froyo have Ad-Hoc capability or requires separate patch?
when you say flash a zip on sdcard, do you mean internal storage?
csci1000 said:
I want to get Froyo installed if I can over weekend and be able to get Ad-Hoc working.
Does Froyo have Ad-Hoc capability or requires separate patch?
when you say flash a zip on sdcard, do you mean internal storage?
Click to expand...
Click to collapse
Yes. Everything is on the INTERNAL sd card, not your sd card. So it'll always be /sdcard/ not /sdcard/sd/.
There is not a 100.00% functional Froyo ROM, there is the international leaked rom modified by Eugene that doesn't flash the baseband radio and kernel. But it is highly buggy and not suggested to be used as a daily driver. Froyo is coming very soon (not officially announced but rumored to be later this month).
I read lot on froyo since last post and you are right, it's not as good as official rom so I think I will wait as I need something reliable. Ya hopefully it will be out by end of month! Hey guys again and again, thank you so much!
sorry that I am asking totally different but only because I haven't got any replies on original thread....
stock Email app that I have setup, (2 separate hotmail accounts), they work so good but only thing is that email is displayed in plain-text format. Does anyone know how to change it to show HTML format? I can't find that option...!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/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!
MAJOR UPDATE 2/22/12: While the process hasn't changed too much, the key files have all been replaced for greater flexibility, and they are NOT compatible with the old method using rookie1's prep-dualboot zip. See this post for an update path from the old method to the current one.
This guide details how to repartition your internal storage and install two operating systems, or ROMs, side by side. If you're looking for a SD install that leaves the Nook's main storage untouched, you're in the wrong place (see my sig).
This guide takes advantage of the multiboot functionality built-in to CM7.1 nightlies since about #140. As such, it is not compatible with CM7.0.x builds or with earlier boot menus.
What you'll get: Whatever two ROMs you install, each will have a nearly 2GB /data partition for apps and they will share a nearly 2GB /media partition for storage, and both will have access to the SD card for more storage. At startup you will see either a small green bar labeled "CyanogenMod," or the word "cyanoboot" in blue. Both boot menus work the same:
Do nothing, and your primary system will boot
Hold down both volume buttons, and your alternate system will boot
Hold down 'n' for a more detailed boot menu
Hold 'n'+power and recovery will boot (if you installed CWM internally).
All of these actions must be taken in the first couple seconds, before a "loading" message appears below the logo. Once you see a confirmation message, you can release all buttons.
DISCLAIMER: As usual, YOU are responsible for changes YOU make to YOUR device. This process is intermediate difficulty level. It probably shouldn't be the first thing you've ever done with ClockworkMod Recovery, and you probably shouldn't just follow the steps if you don't understand them. If you don't know how your NC is currently partitioned, turn back now. If you want to preserve your warranty, turn back now. Here be serpents; be so warned.
Following the guide as-is with all default options gets you a stock 1.4.1* install on secondary and a CM7 install on primary. I hope you can figure out what to substitute where for different results.
*I don't have access to a CWM-flashable 1.4.2 zip right now, but there are instructions for making one here.
The Guide
Prerequisites:
CWM on either SD or internal recovery (internal recommended)
Wi-Fi access
Materials:
repartitionDual2GBdata
BNpri2alt
reformatData
1.4.1-keep-CWM (IF you're not starting with an up-to-date stock install)
CM7.1+ OR MiRaGe's CM7.2 OR unofficial CM9 nightlies (w/ compatible gapps)
CM7 gapps(look near the bottom of the page)
Steps:
Put all materials in your SD card's root directory (DO NOT UNZIP).
Boot into CWM.
From CWM main menu, "backup and restore" and "backup."
From CWM main menu, "install zip from sdcard," and "choose zip from sdcard."
Choose the repartitionDual2GB file.
Reboot recovery. If you have internal CWM and no boot menu, you may need to use the rhythm method:
verygreen said:
hold nook N key and then press and hold power until the {first} message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the {first} message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long
Click to expand...
Click to collapse
Repeat step 4 and choose reformatData
If your backup in step 3 was stock, you can "backup and restore" then "restore" and skip to step 13.
Otherwise, repeat step 4 and choose 1.4.1-keep-CWM.
When it finishes, hold the power button to shut down, remove your CWM card (if applicable), and power back on.
Complete B&N registration process¹
Power off and boot back into CWM (may require rhythm method above).
Repeat step 4 and choose BNpri2alt.
From CWM main menu, in "mounts and storage," format system, data, and cache.
From CWM main menu, choose "Advanced" and "Wipe dalvik cache."
Repeat step 4 and choose CM7 update zip.²
Reboot into main partition and set up Wi-Fi.
Reboot into alt partition (hit both volume buttons at once on "CyanogenMod" loading screen) to make sure it's working.
optional: install gapps, keysmod, etc from CWM.
¹Any mods you want to make to stock, do it now: update to a newer version, root with Manual Nooter (if rooting 1.4.x firmware, follow the linked instructions but use MN 5.12.20), flash keysmod, overclock kernels, or anything else CWM-flashable.
²If you backed up an existing CM7/9 install in step 3, then after step 16 just install gapps, install keysmod if you want it, then from CWM's main menu, Backup & restore > Advanced Restore, and restore data only from your most recent backup. When you boot into CM7 (not tested with CM9), it will be just like you left it.³
³Steps 17 and 18 may look unnecessary, but several users experienced force closes in their CM7 installs when they didn't take these steps.
Other Resources:
CMpri2alt: Moves a CyanogenMod install from the primary partition set to the alternate partition set
BNalt2pri: Moves a stock install from the alternate partition set to the primary partition set
CMalt2pri: Moves a CyanogenMod install from the alternate partition set to the primary partition set
Revert dual boot: deletes the alternate partition set and alternate boot files. Does not restore stock partition sizes, but must be run prior to partitioning back to stock.
1.4.1 full restore: removes CWM from internal recovery, does not affect partitioning
1.4.1-to-alt-partition: updates any existing stock install on the dual boot partition (removes root, does not remove installed apps)
Steps to back up and/or update both partitions
Instructions to rename boot files created with j4mm3r's old multiboot
Possible fix for rooted stock boot-looping at 'n' screen on secondary
Credits:
repartitionDual2GB and reformatData provided by DeanGibson
1.4.1 zips provided by rajendra82
possible boot-loop fix provided by sryan1983
BNpri2alt, BNalt2pri, CMpri2alt and CMalt2pri are minor alterations of DeanGibson's files
revert-dualboot is a minor alteration of rookie1's remove-dualboot
Racks11479 provided key info for the above alterations
________________________________________________________
Old Resources (Do Not Use with Current Method):
prep-dualboot
froyo-to-dualboot
Remove dual boot: returns partitioning altered with prep-dualboot to stock (1GB/5GB, non-blue-dot)
1.2 full restore: removes CWM from internal recovery, does not affect partitioning
1.3-to-alt-partition: updates any existing stock install on the dual boot partition (removes root, does not remove installed apps)
Video documenting setup for a CM9 (Ice Cream Sandwich Alpha) dual boot with Nook Color stock 1.4.1
Old Credits:
1.2 full restore provided by nemith: thank here
prep dual boot and remove dual boot by rookie1: thank here
froyo-to-dualboot from jasoraso: thank here
1.4-to-alt from jasoraso: thank here
You can thank me with the button below, or if you feel real strongly about it, you can make a donation at my blog.
UPDATE 5/25/12: Removed the prerequisite for 1GB/5GB partitioning. A little bird named jicama confirmed that the newer partitioning script doesn't care if you start with a blue dot NC. Prep-dualboot would carve the alt partitions out of /media, which doesn't work if /media's not big enough. RepartitionDual just deletes the last three partitions (/system, /data and /media) and makes new partitions from the now-unallocated space, so as long as you have the right number of partitions, it doesn't matter how big they are.
Added to my Subscribed list !! ...Thank you
I'm getting more daring , so I went through this step-by-step this afternoon (thanks for the guide!).
This was a fresh install into a previously stock Nook (I was running CM7 through the SD).
Booting into stock 1.3 works fine - no difference at all.
In CM7, however, I'm having some problems. I installed nightly 201, which worked fine from the SD card. When I boot into CM7, I get a couple "android.process.media" errors at startup, and again when I try to start Market, which just hangs up after a couple of error message popups. I tried to reinstall 201 through CWM which didn't help.
Any ideas? Should I try a different nightly build?
EDIT: also tried 202 with the same results.
oppy said:
I'm getting more daring , so I went through this step-by-step this afternoon (thanks for the guide!).
This was a fresh install into a previously stock Nook (I was running CM7 through the SD).
Booting into stock 1.3 works fine - no difference at all.
In CM7, however, I'm having some problems. I installed nightly 201, which worked fine from the SD card. When I boot into CM7, I get a couple "android.process.media" errors at startup, and again when I try to start Market, which just hangs up after a couple of error message popups. I tried to reinstall 201 through CWM which didn't help.
Any ideas? Should I try a different nightly build?
EDIT: also tried 202 with the same results.
Click to expand...
Click to collapse
You wiped system, data, and cache after running froyo-to-dualboot and before installing CM7? Try wiping dalvik cache, too (under Advanced in CWM), and boot into both partitions after installing CM7 but before gapps or any other packages/restores.
Taosaur said:
You wiped system, data, and cache after running froyo-to-dualboot and before installing CM7?
Click to expand...
Click to collapse
Yes.
Try wiping dalvik cache, too (under Advanced in CWM), and boot into both partitions after installing CM7 but before gapps or any other packages/restores.
Click to expand...
Click to collapse
Okay, I'll do that and post results. Thanks.
EDIT: Looks like that did it. Seems to work fine, other than some app FCs, which, from what I've read, are fairly common. Thanks for the assist!
I worked that info into the OP. I've done this process twice now without taking those steps and without getting FCs, but you're not the first to report them.
I was a bit confused about the backup and restore part also. Seeing as my Nook was stock to start, I probably didn't need to do that step, and might have actually caused a problem or two by restoring data that didn't exist to start.
Still working great. The only FCs I've had so far were while trying to run Facebook.
Excellent guide! Thanks for all the work on this, it works great.
This is an awesome guide. Thanks for the help. I've been wanting to do this for a while.
Thanks man.
I appreciate you putting all the tools in one place, and I especially appreciate you posting that us blue dot people needed to repartition to 1gb data before doing this; I should've figured that, but I didn't for some reason.
Moving 1.3 to the dual boot partition as I type
Question though; after I move 1.3 to the dual boot, can I still install modifications to it via CWM?
SCrid2000 said:
Question though; after I move 1.3 to the dual boot, can I still install modifications to it via CWM?
Click to expand...
Click to collapse
Short answer: no. As-is, most zips tell CWM to install them to the primary partition. You can modify them to to install to the secondary, but it's a lot simpler if you want to root, install keysmod, or overclock, to do it before you shuffle stock to secondary.
There's a decent chance rajendra82 or someone else will provide dual boot compatible versions of any future B&N software upgrades.
Taosaur said:
Short answer: no. As-is, most zips tell CWM to install them to the primary partition. You can modify them to to install to the secondary, but it's a lot simpler if you want to root, install keysmod, or overclock, to do it before you shuffle stock to secondary.
There's a decent chance rajendra82 or someone else will provide dual boot compatible versions of any future B&N software upgrades.
Click to expand...
Click to collapse
Thanks man. That's what I figured.
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
This is the best thing EVER. I got sick of the nook app on my CM7 build, so this worked flawlessly.
I am running the CM7.1.0 RC1 build, and everything runs smooth as silk
ChaOConnor said:
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
Click to expand...
Click to collapse
Negative, that's built on CM 7.0.3. You would have to use j4mm3r's multiboot and the matching stock-to-secondary file found in this thread: http://forum.xda-developers.com/showthread.php?t=1156909
Nevermind, dumb question.
Updated with a link to CM7.1 stable
I kept a stock install of 1.2 and installed phiremod 6.3 because the 7.2 links weren't working and I couldn't find one anywhere. How do I boot into the alt-partition on boot? There is no CM7 boot screen (google gears, maybe?) and pressing volume buttons several times throughout the entire boot didn't do it.
can somebody please tell me what I am doing wrong. I followed the steps, CM7 boots ok but when I use the alt, the nook gets stuck on the "n" screen.
TomMelee said:
I kept a stock install of 1.2 and installed phiremod 6.3 because the 7.2 links weren't working and I couldn't find one anywhere. How do I boot into the alt-partition on boot? There is no CM7 boot screen (google gears, maybe?) and pressing volume buttons several times throughout the entire boot didn't do it.
Click to expand...
Click to collapse
I'll just leave these here:
Taosaur said:
this guide is not compatible with CM 7.0.x sta(b)le releases, nor branch ROMs based on those builds
Click to expand...
Click to collapse
Taosaur said:
Phiremod 7+
Click to expand...
Click to collapse
Taosaur said:
ChaOConnor said:
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
Click to expand...
Click to collapse
Negative, that's built on CM 7.0.3.
Click to expand...
Click to collapse
Try installing regular CM 7.1.
rabi347 said:
can somebody please tell me what I am doing wrong. I followed the steps, CM7 boots ok but when I use the alt, the nook gets stuck on the "n" screen.
Click to expand...
Click to collapse
Sounds like you got close. I would say start over at step 5.
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.
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Boot Menu Manager (BMM-101) Video Tutorials
A Hrishi21007™ Productions Presentation
(Exclusive and First Ever On XDA and YouTUBE)
------------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------------
Before you read this I would like to Thank :victory: & Congratulate :highfive: Mr.Whirleyes for making such an Awesome Recovery:good::good:
You Can Donate to him if you like this efforts :good:
Paypal Donation Visit http://www.projectlense.com/About
Official Support: [email protected]
------------------------------------------------------------------------------------------------------------------------------------------------
P.s. THIS IS A BIG TOPIC and Will Require some time to complete with videos and additional writeups...
Please Let me Finish the whole thread before starting with Incomplete complains...
I hope you guys Appreciate the time i have spent making this! :highfive::good:
Subscribe to thread to Get Updates.Thank You
Warning: :silly:
Please Follow and read the Instructions carefully before experimenting
Being a Powerful tool,BMM can harm your device if not used correctly
Try and read first and Don't try out things that you don't know about
I or any one else in the World will not be responsible for the things you do to ur device!!!
We may help you in better understanding the Use of it!
ALL THE BEST!
P.s This warning is not to make you afraid...But Rather to make you careful
So the DOWNLOAD link is @ end of thread!
Click to expand...
Click to collapse
Introduction:
As its name suggest, Boot Menu Manager is a Multi-ROM boot manager. It consist of a CWM-based recovery, a boot menu & configuration app.
* Requires ROOT permission *
* Only tested/compatible with Motorola Razr/Droid Razr (codename spyder)
A multi ROM boot manager for android for device with a locked bootloader. Main target is Motorola Razr (spyder)
possibly work with other Motorola OMAP4 device (ICS/JB).
Click to expand...
Click to collapse
CONFUSED ??
See What you need to know in short??
How to BMM-101 Series Episode 0:Introduction by.:Hrishi21007™:.
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
:victory:BASIC USE OF BMM for installing a Kexec ROM: :victory:
BMM-101 Series Episode-01 Tutorial for Kexec ROMS Feat.Carbon ROM by .:Hrishi21007™:.
Video Contents:
Part 1 contains following Tutorial Topics:
1) Installing BMM properly (Switching From SS<->BMM)
2) Boot to BMM & Browsing thru BMM
3) Installing a BASIC Kexec ROM
Click to expand...
Click to collapse
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
:victory:ADVANCED USE OF BMM for installing Non-Kexec ROMs::victory:
How to BMM-101 Series Episode-02 Tutorial NON-Kexec ROMS Proudly Feat.WDSEA Rom by .:Hrishi21007™:.
Video Contents:
Part 2 contains following Tutorial Topics:
1) Installing NON-Kexec ROMS
2) Using Advanced Options Like Kernel Flashing, Backup /Restore CID etc...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------------
WriteUp And Short Explaination
(Currently Borrowed from Projectlense.com :good:
which Will be Updated constantly as i get time)
------------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------------
Recovery main menu
1. Switch System
Menu to switch BMM recovery mode. To avoid confusion, each mode has different UI color.
2. Install Zip package
Menu to install a zip file installer (e.g. ROM installer)
3. Firmware Flashing
Menu to flash kernel, baseband & cid
4. Backup & Restore
Menu to backup & restore partition data (e.g system, userdata)
5. Mount & Format
Menu to mount & format filesystem.
6. Wipe & Clean
Menu to clean userdata, cache & battery statistic
7. System Keeper
Menu for preserving system function. (e.g Reinstall root)
8. Reboot Options
Menu for shutdown & reboot options
9. Advanced Options
Menu for misc options (e.g mount as usb storage)
10. Filemanager & console
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
MENU 1: Systems in BMM
1. System 1
1st set of system (consist of system,userdata & cache partition)
Use original system partition except cache partition (loop image)
2. System 2
2nd set of system.
Utilize unused internal partition. (e.g webtop, cdrom)
Filesysten performance is better than System 1 (if all partition is ext4)
3. System 3
3rd set of system.
This is a virtual system. All partition is a loop image.
User have to create required image file before booting into recovery. Learn more here
4. System 4
4th set of system (same as above)
5. System 5
5th set of system (same as above)
6. System 6
6th set of system (same as above)
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
Menu 2: Menu to install a zip file installer
1. Install a zip package
This menu will open a file chooser.
After item is choosen, an instalation confirmation menu will appear.
2. Apply an update.zip
This is simplified install menu,
where recovery will install an update.zip file located inside /ext (external sdcard).
3. Toggle signature verification
Menu to turn on zip file cryptography check.
This menu is hardly used.
4. Change zip file location
Menu to change current file chooser lookup path.
/int refer to internal storage
/ext refer to external storage
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
MENU 3:Menu to flash kernel, baseband & cid
1. Flash kernel
Menu to flash kernel (boot.img).
2. Backup kernel
Menu to backup current kernel.
Kernel is automatic name according to released version.
3. Restore CID
Menu to restore your own CID backup.
4. Backup CID
Menu to backup device CID partition.
5. Erase CID
Menu to erase CID. Make to have a backup first.
Erasing CID allow flashing of other region image.
6. Flash baseband
Menu to flash baseband firmware.
Accept bp.img & cefs (usually found inside OTA zip file)
7. Change firmware location
Menu to change current file chooser lookup path.
/int refer to internal storage
/ext refer to external storage
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
MENU 4:Menu to backup & restore partition data
1. Fast backup
Menu to backup only system, userdata & cache partition.
2. Full backup
Menu to backup all backup-able partition
3. Selective backup
Menu to backup only selectivr partition.
4. Restore
Restore all partion found in selected backup file.
5. Mount & Format
Restore only selected partion found in selected backup file.
6. Choose backup location
Menu to change current file chooser lookup path.
/int refer to internal storage
/ext refer to external storage
7. Choose backup format
Menu to change backup format
tar - Make backup as tar acrhive (uncompressed)
dup - Make backup using deduplication technique
# dup is CWM6 features : Currently problematic as it create a lot of folder
(fat filesystem doesn't like it, not to mention mediascanner)
8. Delete backup files
Menu to delete selected backup file
9. Clean unused dedupe blob
Menu to delete file undefine in any dedupe backup list.
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
MENU 5:Menu to mount & format filesystem
1. Mount/unmount partition
This menu will mount/unmount partition. (Menu name display current state)
2. Format partition
Menu to format partition.
For this recovery, format command has been replaced with remove command.
No actual format is done here due to locked bootloader.(high security)
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
MENU 6:Menu to mount & format filesystem
1. Wipe data & cache
Menu to erase data & cache partition.
Using this menu currently same as doing format data & cache partition.
2. Wipe cache
Menu to erase cache partition.
Using this menu currently same as doing format cache partition.
3. Wipe dalvik cache
Menu to erase dalvik-cache patition inside data & cache partition.
4. Wipe battery stats
Menu to wipe battery stats
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
MENU 7:Menu for preserving system function
1. Install BMM
Menu to reinstall BMM to main system.
2. Install ROOT
Menu to install su to current system.
3. Backup ROOT
Menu to backup su for OTA survival (No guarantees though).
4. Unroot (with backup)
Menu to remove su binary & keep a hidden backup.
5. Unroot (without backup)
Menu to erase su completely.
6. Unset immutable flag
Menu to remove file protection flag set by chattr or app like Voodoo OTA rootkeeper.
Main source of bootloop problem back in ICS leak days.
BMM will always remove fileprotection flag during restore process,
so this menu is hardly used (Kept only as convenience)
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
MENU 8:Menu for shutdown & reboot options
1. Reboot
Reboot normally.
2. Power off
Shutdown device
3. Reboot to stock recovery
Reboot directly to stock recovery.
4. Reboot to bootloader
Reboot directly to bootloader (AP fastboot).
5. Reboot to System
Reboot directly to selected system mode.
Bootmenu will not be displayed.
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
MENU 9:Menu for misc option
1. Restart ADB daemon
Force restart of ADB service.
2. Connect as USB mass storage
Connect internal & external storage to PC.
3. Adjust screen brightness
Increase/decrease screen brightness
4. Turn on/off keypad light
Turn on/off keypad light.
5. Report error
Copy recovery log file to default storage location.
6. Key test
Menu to test keypad/volume/power key
7. Show log
Menu to show current recovery log
8. Partition SD card
CWM Menu to format SD card
Untested with BMM
9. Fix permisssions
CWM Menu to repair data partition permission
Untested with BMM.
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
MENU 10:Filemanager & console
BMM recovery has a direct link to launch Aroma Filemanager
An aroma.zip file is expected to be found inside clockworkmod folder
Aroma Filemanager XDA thread
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Change logs: :highfive:
0.3.4 - 07/02/2013
- Fix auto creation of cache.img for system 1
0.3.3 - 07/02/2013
- Auto repair/trim all partition on every 20 mount count of mmcblk1p20
- Independent off charging mode. Works with JB & ICS kernel
- Adb sideload install. Just another convenient way to install zip
- Fix insecure adbd. Works with ICS & JB based ROM
0.3.2 - 16/01/2013
- Big jump from old 0.2.x series
Click to expand...
Click to collapse
Official Download Link :good:
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
ALL GSM RAZR tutorial Thread ...Click the text below to visit
ALL RAZR GSM Tutorials u Need Under 1 thread! [Regularly Updated]
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
"Special Thanks to @heblu for his efforts and helping me with this series" :highfive:
awesome job buddy this will help newbies
Sent from my XT910 using Tapatalk 2
assassin34 said:
awesome job buddy this will help newbies
Sent from my XT910 using Tapatalk 2
Click to expand...
Click to collapse
That was my intension for this...:victory:
I Hope to make RAZR hacking easier for new people
P.s. I've requested the MODERATORS to make shift this Thread to DEV section or atleast make it a Sticky Post so that people can see
Lets see :fingers-crossed:
Thanks so much
I came from using the HTC Thunderbolt that I had rooted and re-ROMed many times over. I loved not having all the VZW junk apps and a speedier processor than I thought possible. Almost immediately, I realized that I could not use the same programs and processes to make my Maxx mine.
FINALLY, After all the reading i have done over the past week trying to decide whether rooting and flashing my Razr Maxx, your videos made me actually feel comfortable to make the decision and go with BMM. I actually installed it and looked around on it as you were teaching in the video. As I learn more, I'll start trying the ROM you suggested. It's a different concept to me to have the stock system just sitting on my phone while running another ROM completely, but I think I can get used to it :good:
THANK YOU, this thread is very helpful. I agree that it making this thread a sticky for us NewBees, is a great idea!
Thank You
leeco said:
I came from using the HTC Thunderbolt that I had rooted and re-ROMed many times over. I loved not having all the VZW junk apps and a speedier processor than I thought possible. Almost immediately, I realized that I could not use the same programs and processes to make my Maxx mine.
FINALLY, After all the reading i have done over the past week trying to decide whether rooting and flashing my Razr Maxx, your videos made me actually feel comfortable to make the decision and go with BMM. I actually installed it and looked around on it as you were teaching in the video. As I learn more, I'll start trying the ROM you suggested. It's a different concept to me to have the stock system just sitting on my phone while running another ROM completely, but I think I can get used to it :good:
THANK YOU, this thread is very helpful. I agree that it making this thread a sticky for us NewBees, is a great idea!
Click to expand...
Click to collapse
You're welcome buddy!
Thanks for kind words
You can subscribe to my youtube channel and Comment and like video there too...
Many more BMM101 basic are still to be shown..
The videos that are currently attached are just Basics the advanced use of BMM is still to be Seen...
Hope you enjoy the videos..
Any suggestions are always welcome.
Cya
Yep, subscribed. Looking forward to your upcoming videos.
leeco said:
Yep, subscribed. Looking forward to your upcoming videos.
Click to expand...
Click to collapse
Thanks & stay Tunned
Updates updates updates!!
------------------------------------------------------------------------------------------------------------------------------------------------
:victory:ADVANCED USE OF BMM for installing Non-Kexec ROMs::victory:
How to BMM-101 Series Episode-02 Tutorial NON-Kexec ROMS Proudly Feat.WDSEA Rom by .:Hrishi21007™:.
Video Contents:
Part 2 contains following Tutorial Topics:
1) Installing NON-Kexec ROMS
2) Using Advanced Options Like Kernel Flashing, Backup /Restore CID etc...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------
Updates
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
NEW Facebook Support/ROM updates Page created Please visit the Page
Join Now
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
Thank you very much for making these videos!! They are really helpful!! I've upgraded my phone twice with the help of your videos...
You're Welcome
dinosz1000 said:
Thank you very much for making these videos!! They are really helpful!! I've upgraded my phone twice with the help of your videos...
Click to expand...
Click to collapse
No problem....Glad to hear that
Join the FB page for support from me for my videos
Subscribe to Youtube if ur not already
Comment on respective video tat helped you....it helps me
(apprantly youtube will suggest my videos only if you guys comment n like it) :fingers-crossed:
DONT FORGET TO VOTE THIS THREAD if ur free
I did a full backup and there was a folder created in ext-sd (clockworkmod). Inside there are 3 folders, backup, blobs, firmware.
I'm ok with backup and firmware (I know what these are).
What about bolbs folder?
It contains a lot of sub-folders, named with numbers.
Thanks in advance.
excelent! is very helpful
maxnaxos said:
I did a full backup and there was a folder created in ext-sd (clockworkmod). Inside there are 3 folders, backup, blobs, firmware.
I'm ok with backup and firmware (I know what these are).
What about bolbs folder?
It contains a lot of sub-folders, named with numbers.
Thanks in advance.
Click to expand...
Click to collapse
its backup files...its required by Recovery to take incremental backup!
you can't delete it No, you can't. Or your back-ups will no longer work.
The blobs are most of the back-up. Storing it this way means you can make incremental back-ups rather than all of them being stand-alone. Certain back-ups will share blobs, saving you space.
It's annoying, and it would be great if you could choose the stand-alone method or the blobs-method. But you can't.
hope that helps!
erickelime said:
excelent! is very helpful
Click to expand...
Click to collapse
Thank you Bro
Subscribe to youtube for more stuff!
hit a like on video if it helps you and
Comment and Favorite it if you like it
hrishi21007 said:
its backup files...its required by Recovery to take incremental backup!
you can't delete it No, you can't. Or your back-ups will no longer work.
The blobs are most of the back-up. Storing it this way means you can make incremental back-ups rather than all of them being stand-alone. Certain back-ups will share blobs, saving you space.
It's annoying, and it would be great if you could choose the stand-alone method or the blobs-method. But you can't.
hope that helps!
Click to expand...
Click to collapse
It did help! Thanks a lot!
One last question: I have stored all the backup files in my pc, can I delete them from the phone and then, if needed, place them back again, and restore normally?
Thanks in advance!
maxnaxos said:
It did help! Thanks a lot!
One last question: I have stored all the backup files in my pc, can I delete them from the phone and then, if needed, place them back again, and restore normally?
Thanks in advance!
Click to expand...
Click to collapse
Yes...if you backup All contents...then it would work out..
p.s. never tried it though!
I usually take backup of apps only(Titanium backup)...i have a single (Fresh- with no apps installed) nandroid backup on my phone that's it!
ok guys, i have xt910S rooted ics 4.0.4
i installed BMM, and from installer installed
from reboot went to reboot to recovery it opened bmm recovery
but when i do complete power off, press power plus vol up plus vol down, it goes to fastboot mode, then i select recovery but it go to android recovery 3e instead of bmm but goes to bmm when i do in rom
---------- Post added at 11:08 PM ---------- Previous post was at 11:08 PM ----------
ok guys, i have xt910S rooted ics 4.0.4
i installed BMM, and from installer installed
from reboot went to reboot to recovery it opened bmm recovery
but when i do complete power off, press power plus vol up plus vol down, it goes to fastboot mode, then i select recovery but it go to android recovery 3e instead of bmm but goes to bmm when i do in rom
faheemakbar18 said:
ok guys, i have xt910S rooted ics 4.0.4
i installed BMM, and from installer installed
from reboot went to reboot to recovery it opened bmm recovery
but when i do complete power off, press power plus vol up plus vol down, it goes to fastboot mode, then i select recovery but it go to android recovery 3e instead of bmm but goes to bmm when i do in rom
---------- Post added at 11:08 PM ---------- Previous post was at 11:08 PM ----------
ok guys, i have xt910S rooted ics 4.0.4
i installed BMM, and from installer installed
from reboot went to reboot to recovery it opened bmm recovery
but when i do complete power off, press power plus vol up plus vol down, it goes to fastboot mode, then i select recovery but it go to android recovery 3e instead of bmm but goes to bmm when i do in rom
Click to expand...
Click to collapse
you dont have to boot into BMM like that....just simply turn on ur device with power key and it will show a splash screen ..when it does ....just tao it and it will show the recovery options