Rom-CWM-2.3.4-Samsung-Admire-R720-MetroPCS-04-16-2012 - Android Software Development

Install Directions
Boot Into recovery
Make a Backup!!!!!
Wipe Cache /Davilk Cache
Factory Rest / Wipe Data
Flash rom though Cwm
Reboot let sit for 10 mins
Rom Features
Deodexed. i don't do odex roms.
Removed All metro pcs bloat (left metro @appstore so you can add it all back.) Removed swipe keyboard and swipe libcore download swipe beta for better swipe experience.
Build Prop Tweaked
Rooted with Superuser and Busybox installed by default
Power menu mod with screen capture.
Boot Animations support
Download
Rc-3
MD5
e28a7d9d0ef75cc28168bfeb97917719
To Do
Fix power menu so reboot /recovery /download mode/Screen Capture don't just cause the phone to power off.
Chainlog
Release-3
Updated device to ext 4 support. Power menu has 7 total options still trying to work on fixing it.
Added Init D scripts to remount system as rw and remount the file system for better i/o.
Fixed symbolic links for super user for device sometime denying applications root access.
Ics Transitions re added.
Tried to theme the rom some forgot it was a mdpi device not hdpi so some of the images are larger will fix later on.
Added crt off
added 100 percent battery mod so u can GASP ACTUALLY SEE YOUR BATTERY
ADDED robo font for easier reading

woohoo first to post nice work Raver yet another awesome rom

We just couldn't get him not to dev.
I'm glad you're still doing it man.

RaverX3X said:
Install Directions
Boot Into recovery
Make a Backup!!!!!
Wipe Cache /Davilk Cache
Factory Rest / Wipe Data
Flash rom though Cwm
Reboot let sit for 10 mins
Rom Features
Deodexed. i don't do odex roms.
Removed All metro pcs bloat (left metro @appstore so you can add it all back.) Removed swipe keyboard and swipe libcore download swipe beta for better swipe experience.
Build Prop Tweaked
Rooted with Superuser and Busybox installed by default
Power menu mod with screen capture.
Boot Animations support
Download
Rc-3
MD5
e28a7d9d0ef75cc28168bfeb97917719
To Do
Fix power menu so reboot /recovery /download mode/Screen Capture don't just cause the phone to power off.
Chainlog
Release-3
Updated device to ext 4 support. Power menu has 7 total options still trying to work on fixing it.
Added Init D scripts to remount system as rw and remount the file system for better i/o.
Fixed symbolic links for super user for device sometime denying applications root access.
Ics Transitions re added.
Tried to theme the rom some forgot it was a mdpi device not hdpi so some of the images are larger will fix later on.
Added crt off
added 100 percent battery mod so u can GASP ACTUALLY SEE YOUR BATTERY
ADDED robo font for easier reading
Click to expand...
Click to collapse
yo wat up , can the R720 get flashed to pageplus with MMS/WAP/APPs working or is there a custom rom i dont know about yet ?

Related

Noob's Guide to a Droid X

Welcome to the Droid X guide! I hope to expand up on this as much as possible, so be sure to check back for updates!
The Benefits of rooting
So why root your android phone? Well, there are several benefits... First, you can backup up your phones current state whenever you would like (makes is easy to jump back and forth if you mess things up!). In addition, you can also install different themes (different color interfaces for the basic framework and applications). You can also install custom ROMs (this is an Android OS that has been built from either Motorola's source, or the Google SDK and released through their generosity for the rest of us to enjoy!
Rooting: Many people are unsure of rooting their phones but have heard of other people doing it. Here is my stance on rooting your phone:
If you are technically savvy, or can follow instructions well and have confidence in your ability to do so, I would definitely recommend it! If you are unsure of your abilities to do so, and simply use your Droid X because it is a great phone right out of the box, then I would recommend reading through this guide and some other threads on the Droid X forums so you can familiarize yourself with the potential possibilities and process' involved with rooting and customizing your phone. I do not say any of this to deter anyone from wanting to root their phone, it just can be a dangerous situation for those who are not familiar with how it could potentially damage their phone.
I have seen many ask about the dangers of rooting. First off, yes it will void your warranty, but you CAN unroot your phone. I will include this information later =)
#1 rule of modding your phone: ALWAYS TAKE A BACKUP BEFORE MAKING ANY MODIFICATIONS!
with that said... let's continue =)
Rooting: Just because you have a rooted phone, does not explicitly open up new features on your phone.... What it does do, is open up the possibility for features on your phone =) Keep reading...
Themes: In order to theme your phone, you first have to deodex it. If you attempt to theme the phone without deodexing it, you can run into issues... Themes allow you to change the look of the phone framework and applications (e.g. different colors or images). Make sure to follow rule #1, and then follow any specific instructions that the creator of the theme may have included with their post.
Droid X Bootstrap: This is the saving grace for the Droid X created by Koush. Installing this application once rooted allows you to create backups, restore backups and install custom themes, ROM's, and other modifications that have been made into flashable zip format. I will explain how to use this later as well.
Custom ROMs: Custom ROM's are a developers build of the android operating system either using the Motorola ROM as their base, or building directly from Google's SDK. Many of the ROM's for the Droid X are "blur-free" which means that they look like a generic android OS install the way Google intended it. The default "ROM" that comes on your phone has what is known as "blur" by Motorola. It is just graphical enhancements to the way the phone operates that mostly tie into social networking applications and widgets. Many Android enthusiasts believe that Motorola Blur or HTC Sense ruins the Android feel. Whether or not to use a blurred or blur-free ROM is really up to you and how you like your phone to look and feel.
I will cover more about ROM's later in my posts and try to give an overall description of each. As usual, before trying to flash any ROM, be sure to backup your phone.
Overclocking your phone: Overclocking for those who do not already know what this means, is basically the ability to tell your phone's processor to run at a higher speed. This basically just improves performance on your phone, but can be harder on the phone as well. By telling the phone run at a faster processor speed, you can decrease the battery life of your phone. The droid X overclocks in a different manner than with most Android phones, due to the inability to run custom kernels on the Droid X.
For those who are not familiar with the potential of overclocking your phone, I highly recommend not doing it. While rooting can be dangerous, if you mess up overclock settings on your phone, you can do more harm than good.
So I have seen a bunch of people asking questions that seem to pop up repeatedly on the forums... I plan on adding to this as i put this guide together for a few people who really needed more step by step instructions to get going. Feel free to suggest stuff for me to add, and I will throw it in.
Thanks, and enjoy the following:
Ok, here are the steps for setting up the sdk, getting rooted, and all that good stuff... have a feeling I will be making this into a new thread...perhaps....
SDK:
First off... you will want to go to the following site to download the sdk:
http://developer.android.com/sdk/index.html
Grab the following download: android-sdk_r08-windows.zip
I saved it to C:\sdk (i created a folder called SDK right at the root of C: drive). When it finishes, unzip this using 7zip (or any other unzip program you like) to the sdk folder. When it is finished unzipping, you should have a folder called "android-sdk_r10-windows". If you open up that folder, you will find a folder called "android-sdk-windows". Open this folder up and double click on the "SDK Manager.exe". This will open up a window, and bring up additional windows, one of which will ask you to "choose packages to install". You can download any or all of them. I recommend downloading the following: (NOTE: this may have changed as I don't recall the API versions for sdk r10)
• Android SDK Platform-tools, revision 1 (the top-most download)
• SDK Platform Android 2.3, API 9, revision 1
• SDK Platform Android 2.2, API 8, revision 2
• USB drivers (I don't think this shows up in the latest version of the sdk's first download window. I believe it is found if you go to the available packages section the "Android SDK and AVD Manager and expand the 3rd party section....but if you happen to see it in there...grab it)
This should be sufficient for now. All packages are accepted by default. If you do not wish to download all of them, simply highlight each one (one at a time) and then click the reject button towards the bottom middle of the window. When you have selected the packages you wish to download, click the install button.
After this has installed, you now have the Android SDK installed on your machine. You can close all windows related to the SDK, as we don't actually need to do anything with it, it simply has tools within it that we will need later. (This is where the adb command originates from. There is an adb.exe tool in the "platform-tools" folder of the sdk install, but we will get to this later).
Now you will want to go to your desktop (or anywhere you have a shortcut or icon for My Computer), right click on My Computer, and select properties. Under the "advanced" tab of the window that opens, you should see a button at the bottom that says "environment variables". Click on this, and then find the "Path" variable under System Variables NOT user variables. Click Edit and go to the end of the "Variable Value" field. You will want to make sure there is a semicolon ";" at the end of this before typing any additional info. You will want to add the full path of your android SDK install. For example, if you followed my example for download/saving/extracting/installing above, you would type the following information into the end of the "Variable Value" section:
C:\sdk\android-sdk_r10-windows\android-sdk-windows\platform-tools
If you installed to another location, be sure to type the correct path to the "tools" folder within your installation of the Android SDK. Then click the OK button, and close any windows that were opened from adding to the "path variable".
Droid X Drivers
This section is a little more difficult to explain, as there are so many variables depending on what operating system you are running (windows XP, Windows Vista, Windows 7, etc). and whether or not you are running a 32-bit or 64-bit instance of your chosen Operating system.
Here is one link for Droid X drivers:
http://www.verizon-phones.org/verizon-motorola-droid-x-usb-drivers-pc-charging-drivers-download.html
I simply googled Droid X drivers, I'm sure this isn't the best link, but just for example I'm throwing it out there. If you google Droid X USB drivers you should be able to find the drivers you need, as well as help and instructions on how to get everything working.
Once you get the usb drivers installed, you will want to connect your Droid X to your computer. If it is recognized, you will get a notification in your drop down bar on your phone. On your phone, press on the USB connection in the drop down menu, and select "charge only". Next, open up a command prompt on your computer. Type the following in and hit enter:
adb devices
You should see something simiilar to the following come up if everything is configured correctly:
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015A882315005010 device
If you see something similar to what I have above... then ADB is working correctly, and we can continue! Now we will move on to getting your device rooted! You will want to grab the z4root.apk that I have attached earlier in this thread and download it onto your computer. We will now test out if adb is indeed working! Save the z4root.1.3.0.apk and put it in the "tools" folder of the sdk we downloaded earlier. Now open up a new command prompt (or use the one we opened earlier if you haven't already closed it!) Change directories to the "tools" folder of the sdk:
If you installed the SDK where I used in my example.... type the following:
cd C:\sdk\android-sdk_r10-windows\android-sdk-windows\platform-tools (press enter)
type the following: adb install z4root.1.3.0.apk (press enter)
You should now see the following:
C:\android-sdk-windows\tools>adb install z4root.1.3.0.apk
1833 KB/s (978414 bytes in 0.521s)
pkg: /data/local/tmp/z4root.1.3.0.apk
Success
z4root and ROOTING
If you get all of this, you have now installed a package using adb and we know the interface works. If you don't want to have to mess with this method of installing, you could also download "Astro File Manager" from the android market. You would then need to save z4root.apk to your sdcard of your Droid X. Then open the Astro program and browse to your SDcard and file the z4root.1.3.0.apk. Press on the .apk file and it should come up with a box that says something similar to "open with app installer" or "app manager"... don't recall exactly what it says, but should be something similar to package management or install of some sort. After pressing on that, you should see an install button. Press on that to install z4root.
Now that z4root is installed, you will want to go to your application list on your phone and press on the z4root to open the application. Press on the permanent root button and wait! This process may take a while, and your phone will reboot, but when it does, you are now rooted.
Make sure when trying to root your phone that you go into Settings-->Applications-->Development make sure "usb bebugging" is enabled.
Removing BOOTSTRAP COMPLETELY (You only need to follow these steps if you WANT to remove Droid X bootstrap by Koush, this is not installed on your phone by default).
If you would like to completely remove Droid X bootstrap from your phone, here is what you need to do:
1) connect your phone to ur pc in charge only mode. Make sure it is recognized by adb
A) open command prompt and type "adb devices" (hit enter, your phone should show up)
2) in the command prompt, type "adb shell" (press enter)
3) type "su" (press enter)
4) type "mount -o rw, remount /dev/block/mtdblock4 /system" (press enter)
5) type "cp /system/bin/logwrapper.bin /system/bin/logwrapper"(press enter)
6) type "adb reboot" (press enter)
Your phone will reboot after typing adb reboot, and may take a little bit longer to boot the first time after bootstrap is removed (it may not, I just haven't gone through this process in a while).
Bootstrap should now be completely removed.
Note: all text in quotes is just what you should type...do not include the quotation marks when entering commands.
Disclaimer: I take no responsibility if you mess up your phone. Typing these commands incorrectly CAN mess up your phone. By following these directions, you do so at your own risk.
Installing Droid X Bootstrap
You can grab this .apk file from this thread as well, as I have it posted in one of my previous posts. You will then install this .apk file the same way that you installed z4root. Obviously if you are using the adb command prompt method, you will want to replace z4root.apk with the full name of the droid X bootstrap apk; if you are using a file manager or installer, just follow the same instructions as before as well.
With the bootstrap installed, you are now able to take backups and restore them as well in the event your phone has problems.
Will be adding SBF instructions and links soon =)
If this guide has helped you, please say thanks!
THEMES AND HOW TO USE:
NOTE: In order to install a theme, you must deodex your phone. If you attempt to try and install a theme without deodexing your phone, you can run into problems down the road.
How to Deodex Your phone the EASY way:
Below is a link that Septhin (from Sephtin.com, all credits go to him for this) posted. This is a SYSTEM ONLY flashable .zip that will give you root, as well as deodex your phone ONLY if you are on the 2.3.340 OTA for verizon. Copy this to your sdcard, and flash in bootstrap recovery! Note: If coming from anything other than an existing 2.3.340 system, then you should wipe data/factory reset for safety's sake!
http://www.mediafire.com/?gvvgnum0uma2huk
If you are on the 2.3.15 OTA looking for Deodexed system:
http://www.mediafire.com/?drixq6ry6ja83oq
How to Manually Deodex your Droid X:
Note: all credit for this portion of the writeup goes to Webst3r on droidxforums and those he has mentioned at the bottom of this section. I did not write up the deodex portion of this guide. I am simply including it as a one stop guide to help as many people as possible.
I AM NOT RESPONSIBLE FOR WHATEVER HAPPENS TO YOUR PHONE!
You must be rooted!
What you'll need:
A Windows based machine
xUltimate v2.2
Patience
Process:
1. Unzip xUltimate v2.2, and launch "Main.exe"
2. If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
3. Run option 1. After option 1 is done, run option 2.
4. Now these well take a while. Run option 3.
5. IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
6. Now run option 4, and wait.
7. Exit xUltimate, and put the phone in USB mass storage.
8. Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
9. Open a command prompt, and do the following: (note: at the end of each of the following lines, press the enter/return key on your keyboard)
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Your phone should now be deodexed!
You may notice an increase in speed, and you now have the ability to edit certain files with greater effects. (i.e. services.jar)
Credits: (note these credits are from the original post made by Webst3r, not me, but I would also like to thank them for their work and contributions!)
Rainabba and Mike919: For initially working with me to get a white clock, and later deodex.
toxman: For testing, and being a huge risk taker.
teenfaces: For letting me use his services.jar
And especially Xeudoxus: For letting me a guinea pig, for xUltimate, and answering my questions. And also for the making the xUltimate tool. It defiantly makes thing easier.
SBF: What is it, and what does it do?!?
An sbf file contains the data files necessary to return an Motorola phone back to its "out of the box state". This means it is as if you just pulled the phone out of the box and turned it on. A successful sbf will return you to stock status without any custom ROM, or theme. Usually when one uses and sbf file, you will also want to wipe data/factory reset before hand, and after using and sbf for best results.
SO WHAT DO I NEED?
• RSDlite 4.8 http://www.multiupload.com/HL0ZAL9GK8
• Motorola Drivers: http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
• Correct SBF files for your phone:
o If you are on 2.3.15 OTA (bootloader 30.03): http://www.multiupload.com/HS3Q4U95CG
o 2.3.32 Full SBF: Then go to this site for all the mirror lists. I will post a few direct links below: http://www.mydroidworld.com/forums/droid-x-discussion/5633-droid-x-2-3-32-full-sbf.html
• http://www.multiupload.com/QX7Q3B53UQNOTE: http://depositfiles.com/en/files/60kvlswk2
o If you have already flashed 2.3.32, and/or have 30.04 bootloader: 2.3.34 SYSTEM ONLY SBF:
• DIRECT LINK TO SBF: http://www.megaupload.com/?d=OXK9Q1ZG
• some have preferred to flash individual files through Bootstrap recovery from MyDroidWorld. If you would like to use this method and are more comfortable flashing files than SBF, use this site:
o http://mydroidworld.com/forums/droi...ystem-baseband-2-3-340-kernel-bootloader.html
• 2.3.340 FULL SBF: http://www.mydroidworld.com/forums/droid-x-discussion/6367-new-full-sbf-droid-x-2-3-340-a.html
• Thanks to Maderschramm, there is any easier way to get back to stock on 2.3.340 OTA WITH ROOT
MADERSTCOK "SBF" (note I did not do this write-up, all credit goes to Bouchigo on android forums. Original credit goes to Maderschramm over at DroidXforums and XDA)
NOTICE: Coming from ANY non-blur based ROM and doing Maderstcok is guaranteed to bootloop due to mismatch in framework without a data/cache wipe.
http://www.droidxforums.com/forum/droid-x-hacks/15666-maderstcok-ota-2-3-340-update-zip.html
maderstcok - OTA 2.3.340 update.zip
None are responsible for your phone but you.
After a bit of work I've created an update.zip for you guys that want a fresh install of 2.3.340 without sbfing.
This is the FULL, OTA 2.3.340 - contains radio, kernel, and all other updates, even those EXCLUDED by the 2.3.340 system only sbf.
What that means is that if you have 2.3.15, 2.3.151, or 2.3.320 you're one update.zip away from the OTA 2.3.340
This is useful in many ways:
• You want stock .340 but didn't create a nandroid backup
• Can't OTA (modded phone)
• Get ready for an OTA
• Remove Root
• Add bloat back
• Re-Odex
• Your phone is acting weird on the update
• Something broke
• Fresh ROM install
• You don't want to flash 5 update.zips or sbf to update your phone
• etc.
This will format your system data (helps prevents bootloops - not 100%) and system (in case a rom put some apps in the /system/app) partitions and also changes the boot image to the stock moto M (to fix the Tranquility boot logo - something even an SBF won't fix).
As always, make a backup and I'm not responsible for what happens to your phone.
Download the file here and place it on your sdcard: http://www.droidxforums.com/forum/
• Mirror 1 http://ubuntuone.com/p/XAk/
• Mirror 2 http://www.megaupload.com/?d=4AO672L1
Instructions:
1. Using the Droid X Bootstrapper make a backup. (more information here)
2. Browse (using volume buttons) to "install zip from sdcard" and select it with the camera button.
3. Select "choose zip from sdcard".
4. Select "maderstcok340.zip"
5. Confirm the install.
6. Be patient, wait for the install to finish.
7. Reboot the Droid X. DO NOTHING ELSE IN CLOCKWORKMOD!!!!!!!
8. Activate the phone with VZW (more instructions below).
If you attempt to create a backup or flash a rom post maderstcok installation you're going to have a paperweight. This seems to be because maderstcok removes root and the clockworkmod recovery area, so it doesn't like you playing around in there. Re-root and reinstall the bootstrapper, then create a backup or flash a new rom, DON'T DO IT BEFORE REBOOTING THE DX AFTER ISNTALL.
Formatting Data and Cache is optional; however, if you want a really clean install do so. If you factory reset you'll be forced to activate the phone automatically while if you don't you'll have to follow the quick and dirty activation instructions below - the choice is ultimately yours.
Quick and dirty instructions for activation:
1. Dial *228
2. Press 1
3. Enter last 4 of primary acct holder's SSN
4. Wait - more in depth instructions in a link further down.
This can take some time, especially on the two system installs and the radio install. Don't battery pull unless you want a brick.
The file won't flash properly if you have a botched download - this seems to be caused by the size of the file. Please check your file size before flashing:
Size: 284.7 MB (298481300 bytes)
MD5: ce7122280eafad4a39ba7fefeb764bf5
My free filehosters sometimes .zip the .zip - it looks like maderstcok340.zip.zip
Just unzip once and check the md5 to make sure it checks out - if not, redownload. Don't try to flash the .zip.zip without unzipping it once!
You'll have to activate your phone again after the install. See this for additional help.
If you encounter any problems during the flashing process follow standard ROM installation troubleshooting (i.e. battery pull, factory reset, etc.)
A lot of this stuff is from Team Black Hat - I did pull some of my own phone files too - but if you're looking to donate, please hit them up. Without them we'd be up a creek. Tell 'em I sent ya
One final note - z4root seems to work flawlessly after flashing this file. Just thought I'd throw that in there...
Enjoy!
How to use RSDlite and an SBF file:
NOTES ABOUT USING SBF and RSDlite: Make sure your battery is fully charged. If your phone dies while applying an SBF file, you could be stuck...Be sure to create a backup before using SBF, this could be a nandroid backup, and I would also recommend backing up your SMS messages and applications and any application data (use Titanium backup).
I have found this to have the best results.... before applying an SBF, boot into bootstrap recovery and do a wipe data/factory reset.
1. Turn off your phone. Hold down the "Volume down" + camera button while holding the power button. Your screen should flash and say
Bootloader
30.03 (or 30.04 if you are on the latest update)
Battery OK
OK to program
Connect USB
Data Cable
2. Open up RSDlite and click the " ... " button to browse to the appropriate SBF that you need to use.
a. If on bootloader version 30.03 then you will want to use the VRZ_MB810_2.3.15_1FF_01.sbf file
b. If on bootloader 30.04, then you will more than likely want to flash the 2.3.34 system only sbf (SHADO_X6_2.3.34_SYSTEM-ONLY.sbf)
3. Once it recognizes the file, connect your droid X to the computer via the usb cable. You should see your phone listed in the bottom section of RSDlite.
4. Click the start button, and watch the magic at work =)
5. When your phone reboots, I generally try to do another wipe data/factory reset.
a. When turning phone on, hold down home button + power button. When the droid with the ! comes up, press the search button. You can use the volume up/down buttons to navigate, and the camera button to select.
If your phone dies during sbf, A) make sure to charge your battery before sbf next time B) here are some instructions
IF YOUR PHONE DIES DURING SBF
How to Fix
One thing that you may notice is that when you have this error, your phone will not charge the battery and you'll only be able to see the screen turn on if its plugged into the wall. Somewhere on the screen it will say "Your Battery is Low" and "Cannot Reprogram" or something like that. The easiest way to get through this is to find a friend with a charged battery or go to your local Verizon store and see if they have a demo phone they can use to charge your battery. If you're like me though you will not be lucky in any sense like this so you will have to find the MacGyver inside of you and get a little creative. What you need for this is an old USB cord. One end must be a standard USB cable head and the other can pretty much be anything. Once you have that, follow these steps:
NOTE: I TAKE NO RESPONSIBILITY FOR DAMAGE DONE TO ANY PHONE, BATTERY, ETC. FOLLOW THESE STEPS WITH CAUTION TO AVOID RISK OF DAMAGE.
1. Take your cable and cut off one of the ends, leaving a standard USB plug at the opposite end to plug into your computer.
2. Now you need to strip about and inch of the wire off until you get to the core where you should see 4 colored wires (red, black, white, and green). The colors don't really matter and they may vary, just as long as you can see a red wire and a black wire.
3. Strip off about a quarter inch of the rubber sleeving on the red and black cables, exposing the actual metal wire.
4. Twist the metal strands of each of the wires a couple of times so that all of the wires from the black cable are together and all of the wires from the red cable are together. This is just to make sure that you don't create a short circuit.
5. Here's where it gets a little tricky. You are going to use this cable to make the phone think the battery is fully charged, when in fact you will just be powering the phone using the power from the USB port. Pull out the battery on your phone and find the 4 exposed metal slots (the battery terminals).
6. Each of the far terminals should be labeled with a plus (+) or a minus (-). What you need to do is put exposed leads on the red wire up to the positive terminal and the leads of the black wire up to the negative terminal.
7. While still holding the leads on their respective terminals, slide the battery back into place in the phone. MAKE SURE THE WIRES ARE NOT TOUCHING WHEN YOU PUT THE BATTERY INTO THE PHONE! BAD THINGS COULD HAPPEN ONCE YOU PLUG THE CORD INTO THE COMPUTER!
Note: As tested by parm289, you can skip step 7 and just use the cable to charge the battery if you'd like. He recommends allowing it to charge for 6-7 minutes before placing it back into the phone. Thanks parm!
8. Once the battery is in place and the wires are on the correct terminals but not touching each other, plug the USB cord into the computer. If all has gone as it should, the screen on your phone should come on (may have to press the power button) and the phone should be telling you that the battery charge is okay and that it is okay to program. YAY! Your phone is almost back to normal!
9. Go back up to the previous section in this post that tells you how to reflash the .sbf and follow all of the instructions there. Once that has finished flashing the .sbf to your phone, your phone should be back to working order! You will most likely have to redo the entire setup on your phone but at least your phone is no longer a fancy paperweight
ROM overviews:
Note due to the constant change in version numbers, I have may not have updated this list. I will try to keep it updated as I can.
BLUR ROMs: Apex 1.3, ZapX Bazinga, Rubix Blurry 1.8, Simply Stunning X, DarkSlide 4.2, Fusion 2.0, Tranquility 3.7.0 (has option to add blur)
Blur-less ROMs: Tranquility3.7.0, Rubix Focused 1.9.7, Liberty 1.5, Cobalt 1.0 , Ultimate Droid, FlyX, Darkslide 4.2, GummyJar 2.5, Incredibly Re-Engineered 1.0, Obsidian 2.0.2, Fission 2.5.7
LIBERTY 1.5
http://forum.xda-developers.com/showthread.php?t=939592
ROM Features:
Base....Originally based on GummyJAR, I would call Liberty's bas a evolution of GummyJAR at this point
95% of all the apps were built from source.... rather than decompiled and hacked apps via APKmanager!! And it shows in pure speed!!!!
Blurless
Wycontacts
Cytown Phone
AOSP Pattern lock
AOSP tab Lockscreen with the option for Rotary as well
Custom terminal emulator with added color options
Reboot option in power down menu
Launcher2 with increased snap velocity
Custom Liberty wallpapers app
Custom Liberty live wallpapers (nexus Mod like, modded from CM source)
Music control's in lockscreen (will control any music source including Pandora)
MusicMod by Eliot Stocker (built from CM source and compiled by Team Liberty)
Inverted Gtalk and Gvoice
Gingerbread keyboard - built by hotaru modified by Team Liberty for better button size
AppWidgetPicker - credit boombuler
Latest Market included
build.prop tweaks - thanks to LexusBrian400
Ads blocked via hosts file - thanks to delta_foxtrot2
10% battery increments support
Clockwork recovery (bootstrap) installs on initial install
Working init.d with config file (start-up scripts)
Liberty scripts:
(Run them in terminal emulator. Type script_name -help for more info)
** ads, allinone, apploc, backup, bootani, cache, camsound, compcache, chglog, donate, exe, fixperms, freemem, install_zip, load, pulldown_text, install_zip, load, market_history pulldown_text, rb, restore,rmapk, setcpu, setprops, slim, sound, switch, symlink, sysro, sysrw, usb, zipalign_apks **
All apps optimized and zip aligned
More to come...
Toolbox Features:
• App Management:
* Apps2SD
* Remove/Backup system/data apps
* Install Add-Ons on the fly (blur, non-blur, extras, etc.)
* Backup/restore feature
• Liberty Mods
* Switch between transition animations
* Change boot logos
* Set Build Properties * File editor included by Fr4gg0r *
* Install Fonts
* Install Themes from the toolbox
* Pulldown-bar text editor
* Icon Chooser (change application and battery icons)
• Liberty Tweaks
* Ad Blocker (Block/Unblock)
* Cache Manager (clear/move to SD)
* Free Memory
* Manage Boot Animation
* Mount system rw, fix permissions, zipalign apps, etc.
• Reboot Options
* Reboot, reboot bootstrap, reboot recovery, powerdown
• Settings
* App Theme (change theme of toolbox)
* Notify for ROM updates/patches
* Lockscreen Settings
* Recovery safe mode
* Overclocking
* Sysctl Support
* Camera Shutter Sound
* Tools (Spare Parts, Dev Tools, Testing Menu)
* Restore apps feature
* Set install location on boot
* Zipalign apps on reboot
* Clear cache on reboot
* Fix permissions on reboot
Rubix 1.9.7
http://forum.xda-developers.com/showthread.php?t=927644
Rubix Focused 1.9.7 overview: If you are looking for a ROM with great stability and battery life, then look no further than Rubix Focused 1.9.7. Drod2169 has thrown some amazing scripts in this ROM that allow for app backup, ad-block, and many others. His direct support for the ROM and great speed and responsiveness from his dev work makes it a solid choice. In addition, he has fully customized sysctl.conf to help improve battery life, Java VM management, speed and performance.
* SMART One-Click Overclock App (QuickClock for rubiX) (Credit to Paul Anderson’s amazing work!)
* This is a very brilliant OC app. It configures specifically for your device, and OC’s to the BEST value, and voltage settings for your phone.
**If your max speed turns out to be <1100, it will only overclock to 1100. This is for the sake of Overclocking, and the safety of your device to not push it higher.
* Base is GummyJar (Credit Kejar)
* Full firstboot functionality.
* Rotary Lockscreen Option
* AOSP Settings Menu (No Compass Calibrate/Battery Manager. For Battery Info, check out About Phone/Battery Use)
* GB Keyboard with working size (cause size does matter )
* Theme by Mycahya
* Working 3G HotSpot
* Phone as Modem/USB Tether Option (Instructions stored in rubiX Folder on your SDCard)
* AOSP Lock screen instead of themed Moto tabs!
* Lockscreen pattern no longer on a timer.
* Market Apps installed to Data Partition
* This Includes:
* Maps
* Gmail
* Voice Search
* YouTube
* ADW Launcher
* Street View
* Spare Parts
* Adobe Flash Player
* DL Crutch Lite (For Browser Downloads)
* Tweaks adjusted
* File Manager (Credit to Cyanogen)
Gingerbread Parts: (Credit to Pete)
* Launcher 2
* Gallery 3D
* Alarm Clock
* Desk Clock
SCRIPTS: Credit to Fabulous, JRummy, Sephtin and myself.
adblock: block or view ads
apps: run the script for directions. If you choose restore, you must reboot after for it to take effect
backup: backs up all of your user apps. backup -bk is the correct way to run the script
calc: remove/restore the calculator
carhome: remove/restore the car home launcher
dxeye: remove/restore the DX LWP Please note that this is removed by default, and placed in /data/rubix run the script to restore.
email: remove/restore the email app
fixperm: fixes permissions (credit Koush)
gallery: switches between the 2D (credit to Cyanogen) and 3D AOSP Gallery
genie: remove/restore the news/weather app
office: remove/restore QuickOffice: Please note that this is removed by default, and placed in /data/rubix run the script to restore.
sys: write the system read/only (-ro) or read/write (-rw)
zipalign_apks: zipaligns all the apps in system. Unnecessary since this is ran on every boot!
Fission 2.5.7
http://forum.xda-developers.com/showthread.php?t=839246
About Fission: The first generic Android platform for current and future Droid devices. We are a bunch of mad hackers, modders and developers that were not happy with the current model of Droids being "Blurred" so we began a mission to rid our devices from the blurriness of VZW Android systems. It started with a crazy idea of messing with the Droid2 SDK that has turned into a full fledge AOSP generic type of ROM. We have incorporated many features that were only seen in AOSP ROMs before this. Some of the features include Reboot in Power Menu, custom built Framework, vanilla Android GUI, totally blur free app folder and many more AOSP like features to come in the short term future.
Features:
True Vanilla ROM with generic Android feel, not themed to look like one. No blur apps...
Reboot in Power Menu.
Custom Framework - 10% battery increments with display percent number & without.
Overclock ready out of box.
Lots of free memory.
ROM has root and has been deodexed, and zip aligned.
Busybox installed and symlinks have been applied.
Clean base for you to customize how you like.
And many more...
WILL COVER MORE THIS WEEK! Will also clean up this list to cover most important features to reduce lengthy posts.
Short Little MetaMorph Guide for Changing Icons
Had someone in a post ask about changing some battery icons... So this is a little blip about using it...
I recommend checking out DroidPirate.com if you are looking for images. If anyone else has a place they use for icons, please let me know, and I will add it to this post! Thanks
How-To
MetaMorph ONLY installs the current theme files to the app that exist in the /system/app/ if there is no file you must find the .apk on your phone and place it into the /system/app/ directory.
1) pick the icons you want and download the .zip
2) The file should be a “.ZIP” extension, make sure you do not unzip the file.
3) Connect your device via USB and mount
4) On the root of your SD-Card you need to create a folder called “AndroidThemes” IT MUST LOOK EXACTLY LIKE THAT OR IT WILL NOT WORK
5) Copy the .ZIP file you downloaded and place it in the “AndroidThemes” folder.
6) Assuming you already have the MetaMorph application installed on your phone. Open the MetaMorph app.
7) Click on “Unzip/Extract New Theme”
8) You should the .zip file you have added to the AndroidThemes folder like in the image shown below.
9) Click on the file inside of MetaMorph a MetaMorph install screen should come up telling you about the theme you are installing like shown below (just click Close)
10) Now you should see a button located on the bottom click on “Apply All” this will begin the process of the application skinning.
11) You should see a message box that pops up that says “All Themes Applied” like shown below
12) Reboot your phone and make sure whatever app you where skinning is now skinned.
Recovering Contacts If You Lose Backup Assistant When Using a Custom ROM:
For those of you who relied on Backup Assistant in the default Moto ROM for your contacts, you are in luck =)
Go to backupassistant.com and log in. From here, you can see all of the contacts as of your last sync, and then you can back them up as an Outlook CSV. Next, login to your gmail account, click on "Contacts" and then click "Import". Import the .csv file that you generated from backupassistant.com and....VOILA, all of your contacts are now synced to your gmail account, and you can kiss backup assistant goodbye!
SysCtl.conf Tweaks
Credit for this section goes to macpro88 at DroidXforums and Marius from whom macpro mentions below
Liberty 1.0 and Syssctl Config
Listen up everyone! Since the release of Liberty 1.0, JRummy16 also released a new app in the market called Sysctl Config, which gave users an interface to manually edit and tweak the sysctl.conf file. Alongside this, Liberty made it easier to configure the sysctl.conf file using the integrated menu option under Liberty Settings without the use of the app.
Please take special note! That any ROM can utilize these sysctl.conf tweaks, not just Liberty, and rooted stock as well.
(You must be rooted and have busybox installed for this to work on stock)
So what is the purpose of this thread? And what is Sysctl.conf all about?
First of all, we are going to explore what sysctl.conf is.
Second of all, we are going to explore what sysctl.conf does, and what it can do for your phone.
Lastly, we are going to explore how sysctl.conf works and what kind of benefit is has on the Android OS.
Now, before we get started, we need to clear something up! The tweaks and modifications we will discuss in this thread, WILL NOT IN ANYWAY INFLUENCE BENCHMARK SCORES SUCH AS QUADRANT! Benchmark apps are meant to measure hardware performance only and are in no way affected by these tweaks and modifications, but make no mistake! You will notice at least a slight increase in Android's performance and a possible increase in battery life as well.
Another thing that everyone needs to know is that the Android OS is a Linux based operating system, so there will be a lot of references to Linux, just so you are not confused.
So lets get started shall we?!?!
Ok, so first of all, let’s explore what sysctl.conf is.
The sysctl.conf is a configuration file for "sysctl" which is an interface for dynamically changing kernel parameters in the Linux OS. The configuration file contains the following elements, vm.min_free_kbytes, vm.dirty_ratio, vm.dirty_backgroud_ratio, vm.vfs_cache_pressure, vm.oom_kill_allocating_task. There are many other elements within the file, but we will be primarily focusing on these specifically (the vm prefix stands for virtual memory). The sysctl.conf file should be located in /etc (/system/etc) by default. To enable it you need your ROM to execute "sysctl -p" somewhere during the boot process (or shortly afterward). We will also be discussing how to enable it if it is not already done so. You can also run sysctl -p manually to enable it any time after the OS is started.
Now, let’s get down to what sysctl.conf does and how it works.
Min Free KBytes (vm.min_free_kbytes) - This is used to force the Linux VM to keep a minimum number of kilobytes free. The VM uses this number to compute a pages_min value for each lowmem zone in the system. Each lowmem zone gets a number of reserved free pages based proportionally on its size. Default is 2048kb.
Dirty Ratio (vm.dirty_ratio) and Dirty Background Ratio (vm.dirty_background_ratio) control how often the kernel writes data to "disk" (in our case the internal microSD system card, not the removable microSD card). When your apps write data to disk, Linux actually doesn't write the data out to the disk right away, it actually writes the stuff to system memory and the kernel handles when and how the data is actually going to be flushed to the disk. These values represent a percentage, the higher the percentage, the longer it waits to flush, the lower the percentage, the more often flushes will occur. Now remember, we are dealing with solid state storage, not the traditional disk platter and spindle. So we are actually able to delay flushes a little longer with solid state versus a traditional hard drive disk.
VFS Cache Pressure (vm.vfs_cache_pressure) -Now here is where it gets interesting! File system cache (dentry/inode) is really more important than the block cache above in dirty ratio and dirty background ratio, so we really want the kernel to use up much more of the RAM for file system cache, this will increas the performance of the system without sacrificing performance at the application level. The default value is 100, as a percentage, and what you want to do is lower the value to tell the kernel to favor the file system cache and not drop them aggressively.
Oom Allocating Task (vm.oom_kill_allocating_task) (enable or disable, generally in Linux this value is either a "1" or a "0," representing as on or off.) -This enables or disables killing the OOM-triggering task in out-of-memory (oom) situations. If this is set to zero, or disabled, the OOM killer will scan through the entire task list and select a task based on heuristics to kill. This normally selects a rogue memory-hogging task that frees up a large amount of memory when killed. If this is set to non-zero, or enabled, the OOM killer simply kills the task that triggered the out-of-memory condition. This avoids the expensive task list scan, which can take mass amounts of time and "hang" or freeze the system.
This information has been pulled from the following sites:
imoseyon: Sysctl tweaking for faster, longer lasting Android
imoseyon: sysctl (and minfree) tweaks revisited
http://www.linuxinsight.com/proc_sys_vm_hierarchy.html
How to edit the values manually, follow these steps:
1) First enable sysctl from Liberty settings, if you are on Liberty
2) Run Root Explorer
3) Modify /data/liberty/init.d.conf to make sure that sysctl is enabled ("sysctl = 1")
4) Go to /system/etc/, and mount it r/w
5) Modify sysctl.conf by long pressing the sysctl.conf file and selecting "Open in Text Editor." When finished, save the file and exit
6) Run Terminal Emulator
7) Type "sysctl -p" (output should confirm whether you've done step 4&5 correctly)
(Soon to come, how to enable if your ROM does not support sysctl, which will require much more tweaking.)
If you want to check to see if your changes take hold after reboots, run this in Terminal Emulator:
sysctl -a| grep vm
or
sysctl -p
This command will give you all the sysctl values, scroll down to find the ones you edited and verify that they are the same values you changed them too.
Now, if you want the easy way out, our good friend Marius has been great, and created a flash-able .zip that does all of the work for you!
The .zip can be found here, at Marius' blog titled "imoseyon."
When you flash the .zip file, in Bootstrap Recovery, the following will take effect, and please note, any settings you may have altered, will be overwritten!
Applying the .zip will do the following:
1. Install BusyBox 1.18.0 (in an alternate location)
2. Enables cron, which is a Linux time-base job scheduler
3. Tweaks certain kernel elements (vm, minfree, etc.)
4. Tweaks build.prop (on some ROMs)
5. Flushes system caches once a day (1AM PT)
This .zip should be all you need to get your phone running in tip-top shape. The zip is fairly ROM agnostic, meaning that almost any rooted ROM is going to work (rubiX, Liberty, ApeX, Darkslide, etc. and maybe even stock ROM, as long as you are rooted). It should also work for both Droid X and Droid 2.
Please make sure you create a backup before flashing anything!
After you flash the .zip, you can run the following command in Terminal to make sure it was applied successfully:
pgrep -f crond
If you get a value on the following line, the .zip has been applied successfully, don't worry about what number you, everyone may end up with a different number.
If you are really feeling adventurous and are down for a good read, and really want to get to know the Android OS even better, please follow Marius' blog, as it is a great read!
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
There really is NO right answer when you research sysctl. The best thing to do would be to search VM Linux tweaks. Most of the time, you'll see sysctl values that people optimizing their Linux systems use. Take a look at those, and then look into the actual name of what you're tweaking, to find out what it does.
VFS Cache Pressure, go ahead and disable that. I think the stock value is 100, so enter that. At the value of "12" which is the default in Liberty (from one of my old sysctl's) causes a slowdown after a while, even though makes everything much more responsive at the get go. The slowdown is why I removed it from rubiX roms. OOM Kill Allocating Task kills off the app that caused you to run out of memory, which runs better than the stock android configuration.
The default values in Liberty sysctl tweaks are what I suggested to JRummy after extensive research and testing with Drod on RubiX. The settings Marius used up above are actually the stock settings, so you would have those values by disabling sysctl all-together, which is definitely an option. By raising the dirty ratio and dirty background ratio to 95 and 60 respectively, you are allowing for fewer memory flushes which results in much improved battery life. I found, as Drod mentioned, that with vfs_cache_pressure too low, you will see some slowdowns in performance at around 50 hours without a reboot. Through additional testing, I determined that a setting of 50 here, half that of stock will provide a good blend of benefits without risk. You would need to be running for something like 150 hours without a reboot in order to ever see a slowdown with this setting. It may be even more than that.
From what I have gathered it seems the general consensus in this thread is that there are two main approaches to this:
vm.min_free_kbytes = a
vm.dirty_ratio = b
vm.dirty_background_ratio = c
vm.vfs_cache_pressure = d
One is the self-maintained, improved overall performance approach:
3072 => a => 2048
95 => b => 70
60 => c => 40
50 => d => 25*
*at 25 you’re probably going to have to reboot after about two days
Recommend values in bold
The other is the automated purge cache controlled, extreme performance approach:
3072 => a => 2048
95 => b => 70
60 => c => 40
10** => d => 1***
**Need to run a script to purge cache every 22-30
*** Need to run a script to purge cache every 10-16
Personal recommendation for most people (no manual flushing required):
dirty_ratio = 90
dirty_background_ratio = 55
vfs_cache_pressure = 20
If you are willing to play around with manual or timed flushing I think you can squeeze a little more performance and battery life with:
dirty_ratio = 90
dirty_background_ratio = 70
vfs_cache_pressure = 1
A lot of this stuff is subjective and very dependent on your usage pattern. I've gone about 3 days with the latter without having to flush and probably could have gone a lot longer except i was running some other experiments that caused my phone to reboot.
-------------------------------------------------------------------------------------------------------------------------------------
thanks I really needed this thread
Glad to hear it helped. I will be adding to it this weekend hopefully if I can escape from work...
Sent from my DROIDX using XDA App
Your example of a semicolon turned into a winky face instead of a ( ; ). Might wanna put a couple spaces in there for the noobs
Sent from my DROIDX using Tapatalk
zwade01 said:
Your example of a semicolon turned into a winky face instead of a ( ; ). Might wanna put a couple spaces in there for the noobs
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Haha, oops. Thanks for catching that. Think I fixed it... But dont think it shows up with the same formatting on my phone, so I cant tell.
Sent from my DROIDX using XDA App
<-- n00b
So I rooted my phone and tried to install a rom with rom manager and nothing happened. I tried manually and no roms appeared in the boot menu. Soooooooo my question is, do I need the bootstrapper app in order to install roms?
Sent from my DROIDX using XDA App
angryjello said:
<-- n00b
So I rooted my phone and tried to install a rom with rom manager and nothing happened. I tried manually and no roms appeared in the boot menu. Soooooooo my question is, do I need the bootstrapper app in order to install roms?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Yes, you do.
Sent from my DROIDX using Tapatalk
angryjello said:
<-- n00b
So I rooted my phone and tried to install a rom with rom manager and nothing happened. I tried manually and no roms appeared in the boot menu. Soooooooo my question is, do I need the bootstrapper app in order to install roms?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I think if you press on "flash clockwork" that you dont necessarily need bootstrap recovery, as it is built in.
I personally only use bootstrap recovery as you can still do backups/restores, and install themes and Roms. Just one less step in my opinion. I just manually download the ROMs or themes and move them to my sdcard.
Sent from my DROIDX using XDA App
SysAdmin-X said:
I think if you press on "flash clockwork" that you dont necessarily need bootstrap recovery, as it is built in.
I personally only use bootstrap recovery as you can still do backups/restores, and install themes and Roms. Just one less step in my opinion. I just manually download the ROMs or themes and move them to my sdcard.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
alright so i downloaded a rom from romManager but it won't load it from the app. I located the file on my sd card:
clockworkmod/www sephtin.com/rubix/rubiX.js
Now can i just zip the rubiX folder and do a manual boot to it?
angryjello said:
alright so i downloaded a rom from romManager but it won't load it from the app. I located the file on my sd card:
clockworkmod/www sephtin.com/rubix/rubiX.js
Now can i just zip the rubiX folder and do a manual boot to it?
Click to expand...
Click to collapse
Um... I'm not super familiar with ROM manager, as I don't personally use it to download ROMs, but from what I know, that looks like a javascript file, and not a .zip for a ROM or theme installation. This looks more like a script that sephtin may have written... I'm not sure if maybe ROM manager calls a javascript file to install the ROM or not, but to my knowledge, if you download the ROM from within ROM manager, it should be able to install it.
Here is my suggestion (I'm assuming you are trying to install Rubix 1.9.7...
Download the ROM from here:
http://bit.ly/hw6rE8
Then connect your phone to your computer via the usb cable. Put the phone in USB mass storage mode and copy the file you downloaded to your SDcard.
Before installing the ROM, use one of the free apps from the market to backup your SMS messages if you don't want to lose them. Also download Titanium backup to backup your applications and data if you don't want to lose that as well. As for your contacts, if you don't have those backed up to your google (gmail) account, then those will be wiped out as well with the Rubix installation.
Then if you haven't already... download Droid X bootstrap recovery and install it. Open the app, and press the top button to hijack the boot process. Then press the "reboot recovery" button to reboot into bootstrap recovery. When the phone reboots in bootstrap, use the volume up/down buttons to move the green highlighted selection, and the camera button the phone to make your selections. Go to the option that says "Wipe data/factory reset, and do this use the camera button to select this (this will wipe out all the downloaded apps and user data on your phone). Next, use the back arrow button on your phone to get back to the main menu if necessary. Browse to install .zip from sdcard, then locate the Rubix file that you copied to your sdcard and use the camera button to select it. This will then install the Rubix ROM. when it finishes, it should bring you back to the main menu, but if not, use the back arrow button on the phone to get back to the main menu. Choose the "reboot system now" button and it will reboot normally.
From the first reboot after installing, it may take SEVERAL minutes before the phone actually boots up, this is normal; give it some time and let it do its thing. If it does not boot up after 15 minutes, something is wrong, and you should post back here for more help (or browse on the forums and google, they are both your friend).
Good luck!
@SysAdmin-X thanks alot bro i was trying so hard to find that file on the web. Must have not been looking hard enough!
angryjello said:
@SysAdmin-X thanks alot bro i was trying so hard to find that file on the web. Must have not been looking hard enough!
Click to expand...
Click to collapse
No problem at all, im glad I could help. Post back if you have more questions
Sent from my DROIDX using XDA App
So I backed everything up, hit the top and bottom buttons on the bootstrapper app.
took me to the bootstrap recovery. I wiped all the data, then i selected install from zip. Selected the rubiXFocused1.9.7.zip, and the this happened:
Can't Open rubiXFocused1.9.7.zip
(bad)
installation aborted...
Not Good, any idea why?
Great guide for noobs and for-getters like me.
Is their any reason why you don't also include Maderstcok's SBF method ??
Personally I use it every few weeks especially when jumping Rom's so much.
Thanks for all you do.
Ps when I see someone "new" this is one guide that I refer them too.
kdkinc said:
Great guide for noobs and for-getters like me.
Is their any reason why you don't also include Maderstcok's SBF method ??
Personally I use it every few weeks especially when jumping Rom's so much.
Thanks for all you do.
Ps when I see someone "new" this is one guide that I refer them too.
Click to expand...
Click to collapse
Thanks, I havent included Maderstcok's yet just cuz I havent gotten to type it up =( plan is to get that and hopefully a lot more info.thrown up there this week!
Appreciate you referring people here! My plan is to make this a one stop guide for all the basics at a minimum.
Sent from my DROIDX using XDA App
angryjello said:
So I backed everything up, hit the top and bottom buttons on the bootstrapper app.
took me to the bootstrap recovery. I wiped all the data, then i selected install from zip. Selected the rubiXFocused1.9.7.zip, and the this happened:
Can't Open rubiXFocused1.9.7.zip
(bad)
installation aborted...
Not Good, any idea why?
Click to expand...
Click to collapse
Sounds like it might have been a bad download. Try downloading from that link again, if th at doesnt work, here is another link:
http://bit.ly/ga0ejk
Sent from my DROIDX using XDA App
SysAdmin-X said:
Sounds like it might have been a bad download. Try downloading from that link again, if th at doesnt work, here is another link:
http://bit.ly/ga0ejk
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Alright bro it worked for sure now! I got it up and running, thanks so much for this op and all the extra help!

[ROM]HC3.2-civato-FLEXTHUNDER-AdHoc-3GHuawei-Hulu

FLEXTHUNDER rom is discontinued
Last update was on 29/Dec/2011.
I added the red mod , I think this is a great rom and it does what it should.
I will not put anymore time in this rom , I'm not taking it down , so you users still can enjoy it but don't expect active support from me.
My next and final rom is named flexstriker and will recieve a whole new thread.
civ.2011​Always take a "NANdroid" backup with cwm before you flash anything and take a "Titanium Backup" from your APPS.after flexspeed =FLEXTHUNDER=even faster
CIVATO-FLEXTHUNDER-BASE-V3.7Kernel.zip(with V3.7 kernel)​​ (Base on Acer A500_7.006.03_COM_GEN1 with updates to match 3.2.1)
Hulu support with included modded Flashplayer.
Rooted
Bootloader.blob removed
deodexed
pngoptimized
zipaligned
Tweaked for speed
BusyBox
Superuser 3.07 , bin 3.03
Specials:
Crypted gps patch V3.1[FONT="][URL="http://forum.xda-developers.com/showthread.php?t=1267899"]AGPS patch[/URL][/FONT]
Integrated Ad-Hoc-Wifi
Integrated DHCP wifi lease patch (Thanks to ezterry)
Optional 3Gusb Huawei support​​
Change/Update log:
7/DEC/2011 : Release WIFI optima patch
8/DEC/2011 : Release New ICS inspired Blue mod theme
11/DEC/2011: Release New ICS inspired White mod theme
12/DEC 2011: Release Alternative ICS inspired Blue mod
14/Dec/2011 : update on the ICS alternative Bleu mod and ICS white mod
29/DEC/2011: RED mod added
31-jan-2012: reuploaded with other kernel
Click to expand...
Click to collapse
APK'S and widget included in the base rom:
Agenda/Browser/Camcorder/camera/contacts/Clock/Downloads/E-Mail/Galery/GMAIL4.0/GoogleSearch/Settings/Streets/Market3.3.11/Mediaserver/Navigate/VoiceRecorder/VoiceSearch/Superuser3.07/Talk/YouTube
APK'S in data (can be removed in Apps)
Adobe Flash PlayerV10.3.186.7 (fixed for Hulu) Thanks to WilliamFold
ESFileExplorer1.6.0.8
Drivemount
HideBar
PhotoEditor
Skype
Terminal
HULU-Plus
Polaris Office
TouchscreenBooster
QuickPic-1.4.0
DefaultAppMananger-1.0
Click to expand...
Click to collapse
Flexspeed addON's
How it works:
Method 1:
-First download the .rar File "System APPs for use with addON-Flasher"
-Open the file "System APPs for use with addON-Flasher" , all the system apps and widgets are in there.
-Drag the APK's that you want in the system/app folder of the ROM (DON'T unzip) with winrar or something simular .
-Now flash the rom with all the apps that you want in one time , no need to use the addON-FLASHER.
Method 2:
-First download the .rar File "System APPs for use with addON-Flasher" , now download the "addON-FLASHER".Download addON FLASHER zip
-Open the file "System APPs for use with addON-Flasher" , all the system apps and widgets are in there.
-Now you open the "addON-FLASHER" (don't unzip), go to the folder "system/app" , you drag the apps that you want to that "app" folder.
-Put the addON-FLASHER on your externalSD and flash with CWM - reboot and enjoy.
Apps that are in the "system APPS for use with addON-FLASHER" [FONT=&quot]System apps for use with addON-Flasher[/FONT]
3DPhotoBrowser/AgendaWidget/AsusWeatherWidget/ClearFI/DTG(documents to go full)/Dualclock/ICSClock/LinkToFacebook/Lumiread/MagicSmokeWallpaper
Music2(google music player)/MyWater(livewallpaper)/nemoplayer(acermediaplayer)/SocialJogger/Supernote/VideoEditorGoogle/VisualizationWallpaper
WeatherWidget.
Game-addON Download Game addON zip
NFS and LetsGolf
Put the .zip on your externalSD and flash with CWM
APK's for installation with file manager Download APK for installation with File manager rar
LenovoCalendarWidget
LenovoMailCalendarProvider
SimpleCalendarWidget
SocialTouch
USBFileCopyUtility
(Download the .rar file , unrar it and install apps with a file manager)
Click to expand...
Click to collapse
3Gusb-Huawei-Patch FLEXTHUNDER 3Gusb Huawei patch
3Gusb Huawei support on A500 and Packard Bell LibertyTab G100W if you install the 3Gusb-addON. Install with CWM.
Click to expand...
Click to collapse
[FONT=&quot]WIFI Optima patch [/FONT][FONT=&quot]WIFI-FLEXTHUNDER-OPTIMA[/FONT]
-Installs the official Acer wifi fix .
-Reinstalls the DHCP lease patch, wifi disconnection problem. (By Ezterry and Civato)
-Installs a wifi TWEAK for the A500 by "roach" for better connection in some country's.
-Repeats the needed permissions.
Click to expand...
Click to collapse
TIPS:
- 3Gusb:
If the connection won't start use the ril-deamon-restarter.apk or when you put the 3Gusb in after boot ALWAYS use the ril-deamon-restarter.(3g icon in notification bar and mobile settings will be available in settings then)
It is possible you need to change APN settings in the mobile settings.
(I got a Huawei E1552 and it is working supurb)
Had to follow this tutorial to make my 3G dongle ready : http://vache-android.com/v1/index.ph...tutorialsID=12
-You don't want HULU , or want the flashplayer from the market ?
You need to remove "com.adobe.flashplayer-1.apk" in data/app and reboot.
Now you can download the flashplayer from the market.
- Problems with GPS, try the v2.2 patch from crypted,the rom contains patch 3.0 but it seems that some people have problems with it AGPS Patch Iconia 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO MORE SATS - xda-developers
First time you install this ROM
Wipe Data/factory reset , Cache and dalvik BEFORE you flash this ROM with CWM.
Updating from MIX3 or FLEXSPEED version
Download zip and flash with cwm , if problems clear cache and dalvik , you need to reinstall the batteryMod if you are using it and the custom kernel if you use a different one that is installed.
Click to expand...
Click to collapse
FLEXSPEED+FLEXTHUNDER MODS:
Custom home , menu , back button and custom WIFI icon-PACKAGE
Multiupload.com - upload your files to multiple file hosting sites!(optimized mods for FLEXSPEED)
Thanks to "kjy2010 "
How to use:
Download the .rar file "MODS FOR FLEXSPEED" , unrar it and place the zip file on your externalSD and flash with CWM
What's in the package?
- FLEXSPEED-BATTERY-MOD ( circular battery icon + custom status bar icones)
- FLEXSPEED-BUTTON-MOD (Custom home , menu , back button)
- FLEXSPEED-BUTTON-MOD-WIFI (custom home , menu , back button and custom WIFI icon)
- FLEXSPEED-STOCK-BUTTON-WIFI ( back to stock wifi and buttons)
Battery-MODS (that you can do)flash with cwm.
Based on these threads : http://forum.xda-developers.com/show....php?t=1234328 and http://forum.xda-developers.com/show....php?t=1316846
Thanks to "krid.of-k" and "kjy2010 "
Stock: Multiupload.com - upload your files to multiple file hosting sites!
Droid: Multiupload.com - upload your files to multiple file hosting sites!
Meter: Multiupload.com - upload your files to multiple file hosting sites!
Tiny: Multiupload.com - upload your files to multiple file hosting sites!
Circul: Multiupload.com - upload your files to multiple file hosting sites!
Modded fonts
-For Fonts and digits type that you want and how to change http://forum.xda-developers.com/show...ighlight=Fonts Thanks to "pimpmaneaton"
Click to expand...
Click to collapse
​NEW:XOOM MOD for Flexspeed /FLEXTHUNDER .(Battery in steps of 1%)
Based on this :[THEME] ☢ BigDX Xoom|Zoom Theme ☢ Tiamat 2.2 & Stock 3.2.2 ☢ Red, White, Blue & Green - xda-developers
FLASH WITH CWM.(ONLY for A500/501 and Packard bell LibertyTab)
TIP:IF you flash battery MOD , clear Batterystats in CWM !!!!!
ICS (inspired) BLUE MOD: [FONT=&quot]ICS inspired BLEU MOD[/FONT]
New google search theme , ICS deskClock (widget) , New system buttons , ICS wallpaper and bootanimation , ICS fonts and more little details. Grey 1% battery, new ICS wifi statusbar icon.........
See attachment on bottom.
ICS (inspired) BLUE MOD -alternative: [FONT=&quot]ICS inspired BLEU-MOD Alternative release2[/FONT]
Same as ICS bleu mod but new ICS icones , ICS System buttons and app icon
ICS (inspired) WHITE MOD [FONT=&quot]ICS-White-MOD release2[/FONT]
Same as ICS bleu mod but other color , there are some blue icons and blue stuff in there because that is ICS , don't worry it is a nice touch and doesn't look strange.
BLUE MOD:http://www58.zippyshare.com/v/57315168/file.html
GREEN MOD:http://www29.zippyshare.com/v/59529652/file.html
WHITE MOD : Download WHITEMOD FULL MUSIC2 included zip
RED MOD : [FONT=&quot]RED mod FULL music2 included[/FONT]
Back to stock A500 HC3.2Download A500 STOCK THEME zip
Some pictures: look at the attachments
Click to expand...
Click to collapse
Remark:
Tested on a Packard Bell LibertyTab and Acer A500 WIFI only , NO 3G if you don't use the patch.
BIG thanks to Williamfold , Vache , ezterry ,Crypted , richardtrip , GamezR2eZ ,THOR , smaury , dexter and ......for giving use these roms , CWM ,kernels and apk.s so I can mess with them.
Again I'm a noob at these linux things , and I'm planning on staying a noob , it's just I like to mess around for my own rom and I wan't to share it with anyone that likes it.
I got this rom running on my tab now and it works good (with THOR3.9 kernel) ,I almost bricked my tab testing this rom but he that is the price you have to pay , lucky for me I always got a backup so people always take a nandroid backup !!!
Civato 2011 the mixer. Family and friends come first !!!!!
==================================
OLD ROM + patches and 3Gusb
ROM Civato-FLEXSPEED
[FONT=&quot]Download CIVATO FLEXSPEED2 BaseROM zip[/FONT]
[FONT=&quot]Download FLEXSPEED updateR3 zip
[/FONT][FONT=&quot]wifi-patch-3 :[/FONT][FONT=&quot](update 3 same as patch-2 + [/FONT][FONT=&quot]DHCP fix inlcluded[/FONT][FONT=&quot] , this is for the lease problem that some have)[/FONT][FONT=&quot]
[/FONT][FONT=&quot]Download WIFI PATCH3 DHCP FIX zip
[/FONT][FONT=&quot]
3G usb Huawei support patch[/FONT]
[FONT=&quot]Download Civato FLEXSPEED PATCH3 zip[/FONT]
Ad-Hoc-wifi
[FONT=&quot][FONT=&quot]Download Hoc WifiPATCH zip[/FONT][/FONT]
which kernel do you prefer? I probably won't uc or PC. Just running "stock"
blcklab said:
which kernel do you prefer? I probably won't uc or PC. Just running "stock"
Click to expand...
Click to collapse
This rom comes with custom kernel , if you'r not going to oc leave the one that is on there.
But I like the Thor Kernels, more clock settings.
might wanna check your download. Same issue as last time. Only getting 23.4 k download. eager to check this rom out.
Ohh!
A new rom...
Is it tasty?
u r the man
Sent from my A500 using Tapatalk
Just flashed this one (I had your previous ROM on my tab), after wiping Data , Cache and dalvik. Netflix works, and camcorder does not crash. Tried Hulu using the default browser, at the site I got an error that said I had to upgrade my flash.
I am having a gps problem, no sats locking. It finds up to 6 sats.
Everything else is great! Thanks, just wanted to give some feedback
edit: uninstalled the flash apk and reinstalled it from your ROM and Hulu is now working!! Not sure what happened the first time.
Everything working as advertised and new boot animation is sick but i still have the su denied for setcpu at boot......
Flashed rom
Wiped data
Wiped cache
Wiped dalvik
Booted up
Rebooted and Flashed thors 3.7 kernel
Rebooted
Oooooooooooooooo nm just occured that i also flashed circular battery mod for taboonay......this mods framework-res.apk
Could this be my problem??
Sent from my A500 using Tapatalk
I think megaupload does not download well direct to devices.
hatefuel19 said:
Everything working as advertised and new boot animation is sick but i still have the su denied for setcpu at boot......
Flashed rom
Wiped data
Wiped cache
Wiped dalvik
Booted up
Rebooted and Flashed thors 3.7 kernel
Rebooted
Oooooooooooooooo nm just occured that i also flashed circular battery mod for taboonay......this mods framework-res.apk
Could this be my problem??
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Do you have root explorer or any other app that can give you root access to /system/app?
Sent from my Sensation Rockin CoreDroid!
EDIT: If you do have an app that can access /system with root then do me a favor and try this. Go into /system/root and copy the superuser.apk that is located there. Paste it somewhere in either your sdcard or external sdcard. Then take the attached superuser.apk and move to /system/ and set the correct permissions(Verify old permissions of old superuser.apk before you paste.) Now do a reboot, and once booted back up go into settings/applications/manage applications/all applications and scroll down to superuser and clear out the data for superuser. Now go back into your root apps and setcpu and regrant everything superuser permissions and I'm willing to bet that your issues will be solved. Hope this helped.
pimpmaneaton said:
Do you have root explorer or any other app that can give you root access to /system/app?
Sent from my Sensation Rockin CoreDroid!
Click to expand...
Click to collapse
Yup.....setcpu sets oc if i do it manually........im only denied su at boot
Sent from my A500 using Tapatalk
hatefuel19 said:
Yup.....setcpu sets oc if i do it manually........im only denied su at boot
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Sorry just redid my post with a fix that works great for me in both taboonay and the roms made by william so should work here.
Is there a flash to have stock font? Really liking this ROM but just not a fan of the font.
---------- Post added at 12:10 AM ---------- Previous post was at 12:04 AM ----------
where's the GPS patch 2.0 beta?
+1 on No GPS lock.
blcklab said:
Is there a flash to have stock font? Really liking this ROM but just not a fan of the font.
---------- Post added at 12:10 AM ---------- Previous post was at 12:04 AM ----------
where's the GPS patch 2.0 beta?
+1 on No GPS lock.
Click to expand...
Click to collapse
Crypted has just updated his thread with 2.0 included with other goodies.
Sent from my Sensation Rockin CoreDroid!
pimpmaneaton said:
Then take the attached superuser.apk and move to /system/ and set the correct permissions(Verify old permissions of old superuser.apk before you paste.)
Click to expand...
Click to collapse
Did u mean to say put it back in /system/ or /system/root
EDIT: didnt have su.apk in system and dont have a system/root lol so i went to system/app and replaced su there and it worked like a charm!!!!!! Thanks
Sent from my A500 using Tapatalk
hatefuel19 said:
Did u mean to say put it back in /system/ or /system/root
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Put the one I posted back in /system/app
Sent from my Sensation Rockin CoreDroid!
pimpmaneaton said:
Crypted has just updated his thread with 2.0 included with other goodies.
Sent from my Sensation Rockin CoreDroid!
Click to expand...
Click to collapse
Works great
GPS patch is excellent, everything working now.
hatefuel19 said:
Everything working as advertised and new boot animation is sick but i still have the su denied for setcpu at boot......
Flashed rom
Wiped data
Wiped cache
Wiped dalvik
Booted up
Rebooted and Flashed thors 3.7 kernel
Rebooted
Oooooooooooooooo nm just occured that i also flashed circular battery mod for taboonay......this mods framework-res.apk
Could this be my problem??
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
It is not the battery mod , I got it running on mine .I got no SU problems.
This is how I install rom:
-Reboot in recovery
-Wipe DATA/reset to factory
-Wipe cache
-Wipe Dalvik
-Flash new ROM
-Reboot.
Better to wipe everything before you flash rom.
Sometimes I got SU denied after I restore my system with a Nandroid backup , then I only wipe cache and dalvik and flash the rom again that I'm using in that backup so I don't lose my data/setup.
I did a update of the SU bin and apk in the one I upload later , for the GPS I got really fast lock on , but I live in europe , I will update the gps config file in the updated rom for you guys in the states , if you cannot wait just use the link to the crypted gps in first post and update yourself.
Will be uploading MIX_3B = updated the SU bin and apk. and updated gps config to V2.0 , over her I have even faster gps lock , so thanks for the tip guys.
twice now my tablet ha shut down while in sleep.is there a setting I need to change.
And please let me know if there's a flash for stock font.
This is really good

[RECOVERY] [Touchpad] TWRP 2.3.2.3 with on-screen keyboard! [2012-12-17]

Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.2.3:
-Fix to libraries to avoid issues when formatting partitions
CHANGELOG for 2.3.2.1:
-Updates to fix permissions
-Fix USB OTG on GNex
CHANGELOG for 2.3.2.0:
-Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
-Fixed a bug with deleting a backup with a space in the name
-Added highlights on keyboard key presses
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
Direct Download
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Awesome job guys
Sent from my EVO 3D using tapatalk
Very well done!
I have a nice recovery theme on my E3D. Maybe someone can make some nice TP ones, so we're not stuck with grey
vWvSTATICvWv said:
I have a nice recovery theme on my E3D. Maybe someone can make some nice TP ones, so we're not stuck with grey
Click to expand...
Click to collapse
Hmmm, I will look in to this .....
vWvSTATICvWv said:
I have a nice recovery theme on my E3D. Maybe someone can make some nice TP ones, so we're not stuck with grey
Click to expand...
Click to collapse
Which theme? Maybe someone would want to convert it.
Sent from my Touchpad using xda premium
Awesome work teamwin. This is awesome. Need this on my samsung epic.
Leoisright said:
Hmmm, I will look in to this .....
Click to expand...
Click to collapse
Yea I probably will make a theme when I get the tp in a few days
Sent from my Nexus S 4G using xda premium
I have switched to using TWRP for recovery on both Touchpad and Nook as it is very nice to use without having to fiddle with the buttons.
To make it even easier on Touchpad I thought I'd make the boot to recovery from CM7 go into TWRP rather than have to catch the moboot menu.
So in /boot I did mv uImage.ClockworkMod uImage.ClockworkMod1 and mv uImage.TWRP uImage.ClockworkMod
This superficially worked in that the boot to recovery from CM7 went into TWRP very nicely. But unfortunately when I then select Reboot to System from TWRP it then reboots straight back into ClockworkMod and restarts TWRP rather than go through moboot and into CYanogenMod
I guess there must be something going on in the real ClockworkMod to flip the default boot back which TWRP isn't doing.
For the moment I changed the names back so it uses Clockwork for the default and behaves normally.
bobtidey said:
I have switched to using TWRP for recovery on both Touchpad and Nook as it is very nice to use without having to fiddle with the buttons.
To make it even easier on Touchpad I thought I'd make the boot to recovery from CM7 go into TWRP rather than have to catch the moboot menu.
So in /boot I did mv uImage.ClockworkMod uImage.ClockworkMod1 and mv uImage.TWRP uImage.ClockworkMod
This superficially worked in that the boot to recovery from CM7 went into TWRP very nicely. But unfortunately when I then select Reboot to System from TWRP it then reboots straight back into ClockworkMod and restarts TWRP rather than go through moboot and into CYanogenMod
I guess there must be something going on in the real ClockworkMod to flip the default boot back which TWRP isn't doing.
For the moment I changed the names back so it uses Clockwork for the default and behaves normally.
Click to expand...
Click to collapse
The bootloader project is here: http://code.google.com/p/moboot/
If you're feeling inclined you can ask how you set the default boot for recovery and whatnot. That would probably be a good start. Maybe someone on my team knows, but it can't hurt to learn anyway.
Thanks for that pointer. There does seem to be some anomaly around the use of moboot.next and moboot.action.d
I think when rebooting from CM7 into recovery then either moboot.next or moboot.action.d is being set up to action ClockworkMod so it goes straight in without the moboot menu. Real ClockworkMod then deletes the action files so that when it does a reboot moboot goes through its menu, times out and re-enters the default CM7.
When TWRP is renamed then the sequence starts the same but there is then a moboot.next file that points to ClockworkMod and when it tries to do a system boot then moboot kicks in and repeats the action back into recovery.
I'll comment back on the moboot project as I suspect the cleanest actions here are for moboot to do the housekeeping of action and next files so it doesn't get stuck in this loop.
anyone flash roms with this yet. In the eco people are stating wipin isn't working and hey flash and get stuck in a boot loop
Sent from my PC36100 using xda premium
I installed the newest XRON rom along with moboot and TWRP on my Touchpad and TWRP did not seem to install. Is there a way to just install TWRP without having to do the whole thing over again? Maybe threw terminal mode or something. Since I tried to install TWRP I did not install CWM.
bobtidey said:
Thanks for that pointer. There does seem to be some anomaly around the use of moboot.next and moboot.action.d
I think when rebooting from CM7 into recovery then either moboot.next or moboot.action.d is being set up to action ClockworkMod so it goes straight in without the moboot menu. Real ClockworkMod then deletes the action files so that when it does a reboot moboot goes through its menu, times out and re-enters the default CM7.
When TWRP is renamed then the sequence starts the same but there is then a moboot.next file that points to ClockworkMod and when it tries to do a system boot then moboot kicks in and repeats the action back into recovery.
I'll comment back on the moboot project as I suspect the cleanest actions here are for moboot to do the housekeeping of action and next files so it doesn't get stuck in this loop.
Click to expand...
Click to collapse
All versions of moboot have a README in the moboot_X.X.X.zip file.
From the README (this part was the same in all versions, I think):
##
## to select *next* boot image
##
echo "NAME1" >/boot/moboot.next # will boot uImage.NAME1 without menu
# NOTE: moboot does not delete the file, so the OS booted should
You are correct, it would be cleanest if moboot removed/managed this.
However, there is no code in moboot (or specifically, the ext2 fs code
it uses) to write to the filesystem. After I am done adding lvm support
to moboot, I plan on adding support to moboot to save some state information
to a raw partition (raw lvm volume). Once that is done, I should be able
to lift the requirement that the OS (or recovery, etc.) remove the
moboot.next file.
Also, for v0.3.5+ of moboot, you can hold the Home key to force it to
show the menu (thus overriding the moboot.next file).
Regardless, I am told the next release of TWRP for the Touchpad will
remove the moboot.next file.
bluedogtouchpad said:
I installed the newest XRON rom along with moboot and TWRP on my Touchpad and TWRP did not seem to install. Is there a way to just install TWRP without having to do the whole thing over again? Maybe threw terminal mode or something. Since I tried to install TWRP I did not install CWM.
Click to expand...
Click to collapse
I had the same problem. I installed CWM first, then install TWRP through CWM.
Installed successfully after running the clean boot zip.
I went to the backup section to try and perform a backup but it gives me options that i can select/unselect and am not sure what should and shouldn't be selected.
Thanks
jcsullins said:
All versions of moboot have a README in the moboot_X.X.X.zip file.
...
Also, for v0.3.5+ of moboot, you can hold the Home key to force it to
show the menu (thus overriding the moboot.next file).
Regardless, I am told the next release of TWRP for the Touchpad will
remove the moboot.next file.
Click to expand...
Click to collapse
Thanks. I should have checked the readme.
I discovered the home key trick the first time I tried this and was beginning to wonder how to get out of the loop.
Good to hear TWRP will remove it as well as I'm keen to use this as the standard and be able to reboot into recovery from CM7.
Extra refinement would be if CM7 reboot menu listed all the boot options it could find so that it wouldn't be necessary to rename the image to match the Clockwork that will be used when recovery is chosen.
LastQuark said:
I had the same problem. I installed CWM first, then install TWRP through CWM.
Click to expand...
Click to collapse
Did you install CWM by itself? If so how did you do that?
Thanks,
Wow awesome I never thought this would be possible. A revolution in recovery it seems. Wonder why other devices haven't got this already.
jcsullins said:
All versions of moboot have a README in the moboot_X.X.X.zip file.
From the README (this part was the same in all versions, I think):
##
## to select *next* boot image
##
echo "NAME1" >/boot/moboot.next # will boot uImage.NAME1 without menu
# NOTE: moboot does not delete the file, so the OS booted should
You are correct, it would be cleanest if moboot removed/managed this.
However, there is no code in moboot (or specifically, the ext2 fs code
it uses) to write to the filesystem. After I am done adding lvm support
to moboot, I plan on adding support to moboot to save some state information
to a raw partition (raw lvm volume). Once that is done, I should be able
to lift the requirement that the OS (or recovery, etc.) remove the
moboot.next file.
Also, for v0.3.5+ of moboot, you can hold the Home key to force it to
show the menu (thus overriding the moboot.next file).
Regardless, I am told the next release of TWRP for the Touchpad will
remove the moboot.next file.
Click to expand...
Click to collapse
Thanks, I tested this extensively in an attempt to get my Touchpad into TWRP by default and ran into the same issue with moboot.next, I tried to make it read only after putting Cyanogemnod into it among other things but couldn't get it to work 100%. For now, seems like other folks are running into the same issues and sounds like you guys will take care of it in the next release of moboot. Thanks for all the work.

[DEV/CWM/ROOT/ROM] Hisense US/UK Sero 7 Pro CWM Touch, Stock ROM & XE-SeroROM v².²

[DEV/CWM/ROOT/ROM] Hisense US/UK Sero 7 Pro CWM Touch, Stock ROM & XE-SeroROM v².²
Feel free to donate or click the little Thank You button if I helped you achieve a better device
NOT for the Aussie Sero 7 pro
Important: Current Development CM10.2 Android 4.3 by Randomblame
This first post is just a DEV post. If you wish to flash recovery and have a working system you should use Post 2...unless of course you know what your doing already
Skip to Post 2 if you wish to use the all-in-one root / recovery package I created...if you just want to update your CWM Recovery you can do so with the recovery image below.
Skip to Post 3 if you want XE-Sero7 ROM v².², my custom debloated/deodexed rom with some serious cleaning done and massive additional tweaks.
US VERSION
CWM Touch works on both internal and external sdcard cards. If you have made backups with the previous CWM Recovery they will not be seen with this version unless you move them from /data/media/clockworkmod/ to /sdcard/clockworkmod with Root Explorer
Once more! /sdcard/0 is the default device structure so when you backup to internal sd you backup to /data/media/clockworkmod instead of /sdcard/0/clockworkmod You will not be able to see your backups but they are there. Again, You can use root explorer to browse for them.
To flash;
adb push ./cwm_touch_recovery.img /sdcard/
adb shell su -c "dd if=/sdcard/cwm_touch_recovery.img of=/dev/block/mmcblk0p5"
adb reboot recovery
To go back to stock;
adb push ./stock_recovery.img /sdcard/
adb shell su -c "dd if=/sdcard/stock_recovery.img of=/dev/block/mmcblk0p5"
adb reboot recovery
For full Root Package see post two, below.
If you wish to know whats changed in the recovery.fstab of CWM;
Code:
# mount point fstype device
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
/modem ext4 /dev/block/platform/sdhci-tegra.3/by-name/MDM
/metadata emmc /dev/block/platform/sdhci-tegra.3/by-name/MDA
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-32768
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/platform/sdhci-tegra.0/by-num/p1
UK 32GB VERSION
Most importantly the UK Version's blocks and partitions are different! Mainly the boot/kernel block is now located on mmcblk0p6! Anyone who ran the root script on a UK Version probably flashed mmcblk0p2 with the boot.img potentially bricking the device. This is fixable by running fastboot and flashing the attached files in this post
fastboot flash boot stock_uk32_boot.img
fastboot flash recovery stock_uk32_recovery.img
Code:
# mount point fstype device
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
/modem ext4 /dev/block/platform/sdhci-tegra.3/by-name/MDM
/metadata emmc /dev/block/platform/sdhci-tegra.3/by-name/MDA
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-32768
/sdcard vfat /dev/block/platform/sdhci-tegra.0/by-num/p1
/thirdparty ext4 /dev/block/platform/sdhci-tegra.3/by-name/THD
Update: 8-14-2013
Updated this post with UK 32GB Info and Stock Recovery and Kernel...CWM Touch for 32GB to follow shortly.
Update: 7-28-2013
[KERNEL] nightshack0's Sero7 US kernel (Original Post): Mirror 1 - Mirror 2
Update: 6-11-2013
I've posted the boot.img (kernel) for anyone to pull apart if they wish.
*
This is a full blown rock your sox off root/cwm touch recovery script. Oh and did I mention Revert back to Factory Flashable Zip?
It will not only insert the correct strings in your user folder ./android directory but it will open up device manager and tell you step by step what to do from start to finish. It will also reboot your device a couple of times to complete the process. Get a towel from your bathroom because you will need to wipe your chin once this is finished.
Root/Touch Recovery for Stock US/UK ROM:
Note: If you have blue stacks installed please stop the service (services.msc) or uninstall and reboot.
Step 1: Download the Zip file from my GoogleDrive
Step 2: Unrar the files attached to this post somewhere (DO NOT RUN THE FILES WITHIN THE ARCHIVE THEY NEED TO BE EXTRACTED!)
Step 3: Make sure you have ADB Debugging checked. To enable go to Settings > About > Click 8 times on Build number and back out to Settings it will be under the Developer menu.
Step 4: Run XESeroRootUS.exe (US VERSION) or XESeroRootUK.exe (UK VERSION)
Step 5: Follow instructions
Step 6: Look at your tablet while it installs superuser apk it may ask for verification by Google. Just accept.
Step 7: If it hangs at FASTBOOT please check to see if fastboot drivers are installed correctly!
Step 8: Profit
Want to revert back to Out of the box stock OS [ODEXED]?
[US ROM] Stock Sero 7 Pro Rom (P756.6.01.11.00) CWM Flashable zip
[US ROM] Stock Sero 7 Pro Rom (P756.6.02.11.00) CWM Flashable zip
[UK ROM] Stock Sero 7 Pro Rom (P756.6.01.04.EN00) CWM Flashable zip
NO TABLET UI FOR ODEXED DO NOT FLASH IT
Boot to CWM Touch Recovery (No USB Cord, Volume - and Power On)
Step 1: Wipe System
Step 2: Wipe Data
Step 3: Wipe Cache
Step 4: Wipe Dalvik-Cache
Step 5: Flash the zip located in above
Step 6: Reboot (Choose Yes to disable recovery flash and when asked if you want to root you can choose yes if you want to add the su bianary - see step 7)
Step 7 (optional): Once rebooted if you chose to root in CWM, download SuperSU from market then run it and update the binary to become rooted.
Want to flash a Deodexed version of the stock OS so you can build you own rom? Okay fine here you go!
[US ROM] Sero 7 Stock Rom (P756.6.01.11.00) [Deodexed]
[US ROM] Sero 7 Stock Rom (P756.6.02.11.00) [Deodexed]
[US MOD] Sero 7 Stock (P756.6.02.11.00) tabletUI [Deodexed]
[US MOD] Sero 7 Stock (P756.6.02.11.00) stockUI [Deodexed]
Anyone can feel free to use this zip to create their own ROM build it will flash and work 100% of the time.
Please test your work before you release to public!
Step 1: Flash the zip located above
Step 2: Wipe Cache
Step 3: Wipe Dalvik-Cache
Step 4: Reboot (Choose Yes to disable recovery flash and when asked if you want to root you can choose yes if you want to add the su bianary - see step 7)
Step 5 (optional): Once rebooted if you chose to root in CWM, download SuperSU from market then run it and update the binary to become rooted.
Step 6 (optional): Reboot to recovery and flash a tabletUI mod or battery mod
Want to flash a Deodexed version of the stock OS but keep your current data? Flash this ROM it will retain your data partition.
You can then boot into it once then flash a tabletUI and battery mod
[US ROM] Sero 7 Stock Rom (P756.6.01.11.00) [Deodexed/NOWIPE]
[US ROM] Sero 7 Stock Rom (P756.6.02.11.00) [Deodexed/NOWIPE]
[US MOD] Sero 7 Stock (P756.6.02.11.00) tabletUI [Deodexed]
[US MOD] Sero 7 Stock (P756.6.02.11.00) stockUI [Deodexed]
Anyone can feel free to use this zip to create their own ROM build it will flash and work 100% of the time.
Please test your work before you release to public!
Step 1: Flash the zip located above
Step 2: Wipe Cache
Step 3: Wipe Dalvik-Cache
Step 4: Reboot (Choose Yes to disable recovery flash and when asked if you want to root you can choose yes if you want to add the su bianary - see step 5)
Step 5 (optional): Once rebooted if you chose to root in CWM, download SuperSU from market then run it and update the binary to become rooted.
Step 6 (optional): Reboot to recovery and flash a tabletUI mod or battery mod
Fonts...fonts....fonts...Some games require two fonts that are not in STOCK. Below is the flashable font patch for games like Sims and Movie Star Planet
[US PATCH] XE-Sero7Pro-factory-4.2.1-fonts_patch (P756.6.02.11.00)
Oh I'm sorry you wanted the BEST ROM out for the Sero 7 Pro? Okay you asked for it, XE-SeroROM v².²:
Skip to Post 3
***NEW***
Holy **** my tablet is bricked! WTF, Xboxexpert you broke my ****!:
First off, no I did not. It is definitely not bricked you can not brick this tablet thanks to my scripts.
Step 1: Remove all USB Cables and Hold Volume up and Power from a off state, you will see FASTBOOT on the tablet screen. Let go of power once you see FASTBOOT!
Step 2: Provided you have a USB cable and a PC you can plug it in now and run the recovery.exe from within the folder where my root script is located.
Step 3: By the time you read this if you followed the instructions XERecovery.exe told you to do you should have access to CWM Recovery go install a ROM.
Changelog:
8/20
Added UK Stock ROM
8/17
Revised of the Root script. UK exe is now available it will root your system & install CWM!
8/14
Revised (v²¹) of the Root script. UK exe is now available it will root your system but NOT install CWM, yet.
8/13
Revised (v²) of the Root script. Fastboot is now the primary for flashing CWM and Kernel.
7/30
Added a stockUI CWM Flashable zip for users that want to revert back to the stockUI from tabletUI
7/28
Revised the XESeroRoot script to include upgraded kernel and some fixes for the linux.sh root script. Now fully functional in Linux!
Updated Superuser.apk to latest version
7/27
Added Fonts patch for games that did not work correctly with out them
7/26-27/2013
Added CWM flashable STOCK zips for P756.6.02.11.00
Fully tested existing root scrip with P756.6.02.11.00 [WORKS]
Added tabletUI for stock DEODEXED CWM FLASHABLES ONLY!
6/15/2013
Added a deodexed stockOS that retains data partition for users who want to utilize the tabletUI but not flash my stripped rom
5/31/2013
Added fastboot recovery flash for broken/bricked tablets. I really don't understand how you brick this thing but the XERecovery.exe software will resolve it.
5/30/2013 PM
Added deodexed stock rom for people to build their own
5/30/2013 AM
Recompiled CWM Touch Recovery background image to include "compiled by xboxexpert" just so no one gets confused
Removed bootanimation from being changed when running batch for root
5/29/2013 PM
Uploading XE-SeroROM a completely debloated rom with some additional tweaks.
5/29/2013 AM
Added Fully Functional CWM Touch Recovery (If your already rooted you can just rerun the batch)
Removed the CM10 Bootanimation from the root script.
Added alternate root method if factory resetting from CWM!
5/28/2013
Added Factory Recovery zip
*
Introducing XE-Sero7ROM US/UK (w/ TabletUI) v².² [P756.6.02.11.00]
nightshack0's Sero7 kernel integrated into the installer
Fully Debloated with minimal but professional apps
Fully Deodex Framework and APK files
Full EXT4 Support
180 or 213 DPI ROMS to choose from! 180 may break some market Apps but it looks GREAT!
Over 80 megs of BS remove from the factory rom.
Rooted with SuperSU & binaries have been updated to latest version
Removed stock launcher and added Apex Launcher
Daydream has been fixed! Finally..
Added Xposed Framework, XposedApps, Modaco, Tweakbox, Bubblelevel & Sound Recorder
(Modaco adds Multi-Reboot menu!) (screenshot) (screenshot)
(Modaco adds Multi-User on Lockscreen!) (screenshot)
(Modaco adds Battery % for those who don't want tabletUI!)
Added missing fonts that fix a magnitude of applications and games from not working.
Added hosts file that blocks over 36,000 ad pushing sites.
Added bast525's build.prop mod to make most market applications compatible.
Added Quickboot for fast Application based reboot option and Uninstaller for a fast uninstaller option.
Updated Google Framework and Google Play Store (no need to wait for Play Store to update to the latest version)
Updated ALL /system apks to latest versions!
Removed initial setup wizard for Google Play Store
TABLET UI v²!! No Screenshot button!!!!!! & Circle Battery Mods!
Pressing Volume Down and Power exactly at the same time for a 1 second HOLD will snap a screen shot! (Stop complaining about the lost button)
Download links [To download go to File > Download]:
[US ROM] XE-SeroROM v².² 213 DPI [Slightly Stripped] P756.6.02.11.00
[US ROM] XE-SeroROM v².² 180 DPI [Slightly Stripped] P756.6.02.11.00
Coming Soon:
[UK ROM] XE-SeroROM v².² 213 DPI [Slightly Stripped] P756.6.01.04.EN00
[UK ROM] XE-SeroROM v².² 180 DPI [Slightly Stripped] P756.6.01.04.EN00
[US ONLY KERNEL] nightshack0's Sero7 kernel is built into the ROM see Post 1 for the link if you need to flash separately
[MOD] TabletUI Mod v² w/ Stock Battery Icon
[MOD] StockUI Mod v² w/ Stock Battery Icon (uninstalls tabletUI)
[MOD] Green Circle Battery Icon (with charging animation)
{
"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"
}
[MOD] Blue Circle Battery Icon (with charging animation)
[MOD] Green Tiny Circle Battery Icon (with charging animation)
[MOD/My Favorite] Blue Tiny Circle Battery Icon (with charging animation)
ROM Install Instructions:
Step 1: Copy both zips to your internal or external SDCard
Step 2: Boot to CWM Touch Recovery (No USB Cord, Volume - and Power On)
Step 3: Wipe System
Step 4: Wipe Data
Step 5: Wipe Cache
Step 6: Wipe Dalvik-Cache
Step 7: Flash the zip
Step 8: Reboot (DO NOT INSTALL TABLETUI MOD YET!)
Step 9: Boot into the ROM once and setup Google Play Store
You are now free to Proceed to the MODS section and get your tabletUI groove on!
MODS Install Instructions:
Pre: If you are going to flash a Custom Battery Icon and want TabletUI you need to flash the TabletUI 1st then the Circle Mod of your choice directly after.
Step 1: Copy zip to your internal or external SDCard
Step 2: Boot to CWM Touch Recovery (No USB Cord, Volume - and Power On)
Step 3: Flash the zip
Step 4: Reboot
Additional tweaks for the Apex Launcher you will need to perform for full Tablet UI:
First double tab the main screen to get the menu to pop up. Click Apex Settings.
In Homescreen Settings enable TabletUI checkbox.
In Drawer settings make Horizontal Margin (NONE)
In Drawer settings make Drawer background transparency 70%
In Drawer settings make Portrait Grid 8 x 4
In Drawer settings make Landscape Grid 4 x 8
In Behavior settings make Screen orientation (landscape)
In Behavior settings check Home key to default screen
In Advanced Settings check Keep in memory
In Advanced settings uncheck Report usage and errors
Download Bubble level by Antoine Vianey it will allow you to calibrate your Sero 7 Accelerometer sensor
Additional tweaks for the system framework for faster performance:
Enable Developer options - Go to System > About tablet > tap 7 times on Build number
Enter into Developer options menu on left side and change Window, Transition and Animator scale to ".5"
You can also enable the ADB Debugging feature in Developer options.
Install Xposed Framework from the included APP and then enable all modules within the app module section, reboot.
Use Modaco and enable the following Under Google Nexus (all)
Enable advanced reboot and show users on lockscreen, reboot again.
Enjoy a nice Reboot Power Menu and multiuser functionality through the settings application!!
There is an Google Play app called Thumb Keyboard it is amazing and should be purchased if you want a great keyboard for this 7" Tablet just choose 7" Standard layout when you set it up for the first time.
Additional application cleanup:
I was made aware that there are still 3rd party applications installed even after you wipe your device. They are located in /thirdparty and can either be moved or deleted. In the next release I will have that folder wiped clean, for now you can use a file manager to do it yourself.
Teaser of the XE-SeroROM in action
XBMC over WiFi HDMI on XE-SeroROM
[MOD] Sero 7 Pro Inductive Charging Pad
You might want to ad in your OP that this version will not see backups that were made with the previous version, and you'll need to copy them over using a root explorer (verified).
ATGAdmin said:
You might want to ad in your OP that this version will not see backups that were made with the previous version, and you'll need to copy them over using a root explorer (verified).
Click to expand...
Click to collapse
Done, I also updated post #2 with something great
Downloaded and installed post #2. Works like a charm!
Thanks!
Purchased one online, hope I can pick it up today and try it out!
Sent from my GT-I9300 using Tapatalk 4 Beta
Thank You.
Great app to get "root" for the terminal deficient user.
Quick question if I have already rooted and installed CWM from the other thread is this a newer/better version or am I all set?
jpisini said:
Quick question if I have already rooted and installed CWM from the other thread is this a newer/better version or am I all set?
Click to expand...
Click to collapse
You can run my root over your root it will just change the bootanimation and update the CWM to a version that sees the sdcard.
Does the new version of CWM save back ups to the internal or external card? Because 5g of storage is getting used fast.
jeeps13 said:
Does the new version of CWM save back ups to the internal or external card? Because 5g of storage is getting used fast.
Click to expand...
Click to collapse
You can choose where it goes in the menu the added external menu is in CWM now.
Awesome. Installed cam and made a backup.
Can we add this device to XDA.
warunamail said:
Can we add this device to XDA.
Click to expand...
Click to collapse
Would be nice.
This worked great thanks. Anyway to get stock boot animation back?
jpisini said:
This worked great thanks. Anyway to get stock boot animation back?
Click to expand...
Click to collapse
I attached a zip you can run the batch it will revert.
Code:
adb shell su -c "mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system"
Watch the tablet it will ask for SU access to remount.
adb shell su -c "rm /system/media/bootanimation.zip"
adb shell su -c "mv /system/media/bootanimation.bak /system/media/bootanimation.zip"
adb reboot
adb kill-server
just rooted and installed your recovery.
it was very quick and simple!
thank you!
Simple and quick rooting ... Thanks to you sir. It was a matter of downloading attachments and then executing the batch file. Rest was done automatically.
I am liking this Tablet so far. Just got it like two hours ago from walmart. Even the guy behind the counter was asking me why are you buying this ... is it good?
I got the N7 when it came out ... one day I took it out of the bag and found the screen was shattered. Even though I had the Original Nexus 7 cover on it ... so I was looking for a replacement that would be like N7 but slightly better. I was thinking more of 1080p screen and sd card slot. Bad news is that there is no 7 inch tablet out there (atleast I couldn't find a single one) that has a 1080p screen which is a surprise as Samsung, Sony, LG as well as HTC have put 1080p on a much smaller screen sizes but they forgot to make a display for tablets. lol. So I gave up and went to walmart to pick up any cheap tablet to get by something like Galaxy Tab 2 and spotted this behind the glass. Did a price check on it and it came out at $149 ... with 720 screen, SD card slot and HDMI out ... so it was an easy pick after that. Its more like N7 Rev 2
I couldn't make the Xposed settings to work. Have tried it on a couple of apps but no go. Me missing something?
Sorry if this is a stupid question, but how do you boot into CWM? I thought recovery was turning it on while holding down the volume down rocker. I used your XE Sero Root zips and have the boot animation running, but I can't get into recovery to wipe everything and install the Serolicious ROM...

[P][G8141/G8142][.306] M-ROM P v1

I DID NOT CREATE THIS ROM OR THE RECOVERIES OR FLASH TOOLS LINKED, I ONLY MODIFIED THE SYSTEM UI AND SETTINGS AND BUILD PROP ZIPS BELOW.
I am not responsible for any damage (if any) to your device, data, life, job or anything else you'd care to think of.
ANY QUESTIONS, PLEASE ASK IN THE THREAD AS EVERYONE BENEFITS, PM'S WILL MOSTLY BE IGNORED.
IF YOU DON'T HAVE AN UNLOCKED BOOTLOADER YOU MUST FIRST UNLOCK IT.
Download all files you want/need to your PC/External SD before starting...just saying.
[/CENTER]
​Step One
​
Flash stock firmware for your device that the rom is based off. Readily available from Xperifirm (attached to flashtool - Bonus!), or XDA. Flash via Flashtool or Newflasher. Again, there's plenty of guides on using flashtool and newflasher, i'm not covering that here.
​
Step Two
​
Once flashing has completed, turn the device on and allow it to fully boot. Complete the setup process, and log in to your google account. Move the ROM file you already (hopefully) downloaded to internal storage (IMPORTANT STEP: I had symlink errors flashing the ROM from the External SD Card). I normally disable auto-updates in the Play Store/Whats New apps and then let it rest for 5 minutes.​
Step Three​
Turn your device off, boot into FASTBOOT MODE, and flash TWRP (fastboot flash recovery TWRP/ATWRP.img). If you don't know how to fastboot, see above re: XDA/Google. Unplug your device, wait 10 seconds, then boot into recovery (Hold power and volume down together, release both at at the vibration). Tick the checkbox then swipe right, and the first thing you SHOULD do is go to settings and turn the damn vibration off. :laugh:
​Step Four​
DON'T WIPE ANYTHING!!! You are installing on top of an already clean installation, its pointless. Press Install, select the XPERIA_PIE_XZP_1.0.zip file you downloaded earlier, and swipe right to install that sucker. Don't freak out when it takes 5 to 8 minutes for the recovery screen to change, its doing its thing, trust me. Once you get the all clear and the button down the bottom says reboot, that's pretty much all that's left to do.​
Step Five​
Once the phone reboots, let it settle again for a while, and deny all the requests the Chinese apps throw at you. After a few minutes, go into the root explorer app, allow root permissions when it requests it, then go to system/priv-app and delete any app starting with TG. Unless you really like Chinese bloat, in that case, proceed to set up your phone as usual.
The ROM is pretty basic at the moment but given time and based off the Oreo series, more System UI mods will become available with later versions.​
CREDITS: @machao44 @uditrawat @Myself5 @Androxyde @munjeni @Ticklefish @Pandemic
@fOmey[/SIZE]
DOWNLOAD LINKS​
M-ROM P v1: BASED ON 306 FIRMWARE https://drive.google.com/file/d/1eOWzREBPehv8QoCFYQfPdF4yqKH2NdB1/view
M-ROM P v1.1: BASED ON .33 FIRMWARE
https://mega.nz/#F!MNYGhKhR!OtCS6j-YBXaxcDI1sa7FlQ
Thanks to @sam.foro for uploading.
M-ROM P v1.2: BASED ON .41 FIRMWARE
https://drive.google.com/open?id=1ZX...ixVN09Ry_vVhDf
Thanks to @Yanun
https://drive.google.com/file/d/14K-...ew?usp=sharing
Thanks to @karrouma
M-ROM P v1.3: BASED ON .41 FIRMWARE
https://drive.google.com/open?id=10l...uGinaYCEzy-vt_
Thanks to @Yanun
TWRP: https://dl.twrp.me/maple/
Aroma TWRP: https://mega.nz/#!TdxmiaLb!FYBet5eRYHGqiLT0niRH9F90Ts_QeRdfkOfPWOAgQCM
Flashtool: www.flashtool.net/
Newflasher: https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
M-Rom P v1.6 - BASED ON 10.28 FIRMWARE - Thanks to @karrouma for uploading and sharing
https://drive.google.com/file/d/1pNsIaGR2_r74INyH8p053bQStiruPEWd/view?usp=sharing
M-Rom v1.6 - English Translated
https://mega.nz/#!6ExSGYQZ!HD0YM_Sypeu5h-6K4vhKT9NkiQn_63PZG0ZPwf_kRmY
M-ROM 1.6 aroma add-on.
M-ROM v1.6 aroma add-on - contains .25 animation mod, font picker and fonts, xperia 10 boot animation, double tap to wake kernel selection (g8141/g8142), and magisk 18.1/19.0 selection.
Enjoy.
https://mega.nz/#!nZpihCqK!TvB0_-w0cdTWFBKylPUk5Da3YdLAJCc_vk5d8XNDySc
Beetle84 said:
ADD-ONS​
And now we have a few add-ons. You don't really need any of these, but its XDA and if you've come this far you obviously like flashing stuff so here we go...
The Modified Animation Values zip has one extra setting added in developer options, to the animation duration settings. .25 duration has been added (extra fast). Theres no real point to this other than making things seem quicker, but this zip has the added bonus of having the XZ3 Settings.apk included. (Stock XZ3 settings.zip also supplied) FLASH IN RECOVERY
Modified Settings: https://mega.nz/#!qF4gBazC!R4hoXd_1fEOCxwrrttpXRR0CBCO9A3L8QZq3y3A-NEY
Stock Settings: https://mega.nz/#!HQwSSCAC!T3rPbcPLCCVVcMVCZGk3cDKp6DreHtjVYxEcRer3ORQ
The Rounded Recents zip has a modified SystemUI.apk that has (surprisingly) rounded recents modified into the apk. I have also pushed all the right side status bar icons across a little and shortened the space between the data icon and the battery (stock SystemUI.apk zip supplied). FLASH IN RECOVERY
Modified System UI: https://mega.nz/#!iQ4URIzJ!ssb0Wn7rXfqdU9ll3PWGp6Ba7Qx7rfnzH_QxHocEOV4
Stock System UI: https://mega.nz/#!qEpQwIYT!6QDuEWPHiWT111ah2X39z2UzcXvpmEqO2KlAnNpnA_E
The G8141 build prop zip has a build prop modified to say G8141 for those picky (like me) and don't like seeing G8142 in about phone. If you have a G8142, ignore this whole bit about build.prop. Unzip the file and move the file with a root explorer to /system and apply R-W-R-R permissions and reboot.
G8141 Build.prop: https://mega.nz/#!WBwklSCZ!3AfXbN6JmsE0eihgx8Rn7O7deEnbz2KW048WLUm4Grc
MAKE A BACKUP FIRST MAKE A BACKUP FIRST MAKE A BACKUP FIRST
Last but not least, is the Deodex patch (COMING SOON - UPLOADING) for this ROM. Expect lengthy boot time first go, and then longer than usual every time after that. If you flash this zip, your keyboard will be removed, unless you have a keyboard already installed from the Play Store. YOU WILL HAVE NO KEYBOARD AFTER FLASHING THIS ZIP UNLESS YOU ALREADY HAVE ONE INSTALLED FROM THE PLAY STORE! YOU HAVE BEEN WARNED! TWICE!!!
Deodex Patch:
Enjoy
Click to expand...
Click to collapse
Thank you my friend
Great job
Nice
Thanks for this
Nice bro
Keep it up ^^
Added Patched Services.jar Magisk Module to Post 3.
I wonder if the uploaded file is not damaged.
I downloaded twice, filesize reached 1.52 GB at 100%. But the zip file fails to open. Can not be extracted as well
Therefore I did not try it in TWRP.
hasaan6545 said:
I wonder if the uploaded file is not damaged.
I downloaded twice, filesize reached 1.52 GB at 100%. But the zip file fails to open. Can not be extracted as well
Therefore I did not try it in TWRP.
Click to expand...
Click to collapse
Its not a new upload so I wonder what is happening. It is the same link available from the Oreo M-ROM thread, just copied and pasted.
Are you downloading from your device or from a PC?
Removed
link opened fine. and the file is fine opened normally . no problem
Beetle84 said:
ADD-ONS​
And now we have a few add-ons. You don't really need any of these, but its XDA and if you've come this far you obviously like flashing stuff so here we go...
The Modified Animation Values zip has one extra setting added in developer options, to the animation duration settings. .25 duration has been added (extra fast). Theres no real point to this other than making things seem quicker, but this zip has the added bonus of having the XZ3 Settings.apk included. (Stock XZ3 settings.zip also supplied) FLASH IN RECOVERY
Modified Settings: https://mega.nz/#!qF4gBazC!R4hoXd_1fEOCxwrrttpXRR0CBCO9A3L8QZq3y3A-NEY
Stock Settings: https://mega.nz/#!HQwSSCAC!T3rPbcPLCCVVcMVCZGk3cDKp6DreHtjVYxEcRer3ORQ
The Rounded Recents zip has a modified SystemUI.apk that has (surprisingly) rounded recents modified into the apk. I have also pushed all the right side status bar icons across a little and shortened the space between the data icon and the battery (stock SystemUI.apk zip supplied). FLASH IN RECOVERY
Modified System UI: https://mega.nz/#!iQ4URIzJ!ssb0Wn7rXfqdU9ll3PWGp6Ba7Qx7rfnzH_QxHocEOV4
Stock System UI: https://mega.nz/#!qEpQwIYT!6QDuEWPHiWT111ah2X39z2UzcXvpmEqO2KlAnNpnA_E
The G8141 build prop zip has a build prop modified to say G8141 for those picky (like me) and don't like seeing G8142 in about phone. If you have a G8142, ignore this whole bit about build.prop. Unzip the file and move the file with a root explorer to /system and apply R-W-R-R permissions and reboot.
G8141 Build.prop: https://mega.nz/#!WBwklSCZ!3AfXbN6JmsE0eihgx8Rn7O7deEnbz2KW048WLUm4Grc
MAKE A BACKUP FIRST MAKE A BACKUP FIRST MAKE A BACKUP FIRST
Last but not least, is the Deodex patch for this ROM. Expect lengthy boot time first go, and then longer than usual every time after that. If you flash this zip, your keyboard will be removed, unless you have a keyboard already installed from the Play Store. YOU WILL HAVE NO KEYBOARD AFTER FLASHING THIS ZIP UNLESS YOU ALREADY HAVE ONE INSTALLED FROM THE PLAY STORE! YOU HAVE BEEN WARNED! TWICE!!!
Deodex Patch: https://mega.nz/#!mdhmnKwS!POI9MLzZRH9g4isgy0XCZLIhYmu6pUAnZwlXcgaM2xM
And a Patched Services.jar Magisk Module. Flash in Magisk and reboot.
306 Patched Services.jar.zip: https://mega.nz/#!LYpyHQyD!Ka21OVx-yWIM1WUb-WQLoLoJEGOZItz7V_BQMz6fbsk
Enjoy
Click to expand...
Click to collapse
can you explain the step how to deodex the pie ??
rizky_zulfikar said:
can you explain the step how to deodex the pie ?
Click to expand...
Click to collapse
All is explained here brother
https://forum.xda-developers.com/android/general/toad-source-android-deodexer-t3848307?nocache=1
Beetle84 said:
All is explained here brother
https://forum.xda-developers.com/android/general/toad-source-android-deodexer-t3848307?nocache=1
Click to expand...
Click to collapse
i've tried that tool, but my priv-app and framework fail to deodex there still odex and vdex file, only my app ?
Hey just downloading, what rom is this or based on what rom, deodexed xperia rom or custom rom, which kind, sory missed this, thank you
stipi69 said:
Hey just downloading, what rom is this or based on what rom, deodexed xperia rom or custom rom, which kind, sory missed this, thank you
Click to expand...
Click to collapse
Its a slightly modified stock rom, based on .306 dual sim Pie firmware. The rom is odexed.
I have it flashed root working, looks nice, refreshing and snappy, i guess xzp does not have hardware side sensors but you can still tap on edge of screen and bring side menu out , nice!!!
I love new camera look, huge icons in pull down menu.... not so much, haha , it is a matter of gettin use to it i guess
Great work, thanks
If you cannot flash 47.2.A.0.306 via flashtool and get same error as i did below download and copy next file:
downloaded "47.2.fsc" file to: username/.flashtool/device/G81XX, delete 47.1.fsc
https://drive.google.com/file/d/1hZR...w?usp=drivesdk (not my work in this link, credits to xda user xrenoix)
Hi, i get error in flashtool, somoene else same error?
28/048/2018 13:48:07 - INFO - Start Flashing
28/048/2018 13:48:07 - INFO - Parsing boot delivery
28/048/2018 13:48:07 - INFO - Found a boot delivery
28/048/2018 13:48:07 - ERROR - No flash script found. Flash script is mandatory
28/048/2018 13:48:08 - INFO - Sending Sync
28/048/2018 13:48:09 - INFO - Sync status : OKAY
28/048/2018 13:48:09 - INFO - Sending powerdown
28/048/2018 13:48:09 - INFO - powerdown status : OKAY
28/048/2018 13:48:11 - INFO - Device disconnected
old .270 rom flashes with no problem
XZ3/XZ2 systemui.apk Sony Loops Clock/ Ambient/ Night Mode port to XZ3 All functions
You need several attempts. I know the description is not simple. Try! All functions currently work Only not double tap to wake
Thanx for http://bbs.gfan.com/android-9527088-1-1.html
https://forum.xda-developers.com/xp...enz-pie-v1-0-0-26-11-18-t3871854/post78281536
OneHand/Night Mode and XZ2 premium systemUI in zip XZ3 systemUIS has rounded corners It looks weird Better XZ2
Indashio said:
XZ3/XZ2 systemui.apk Sony Loops Clock/ Ambient/ Night Mode port to XZ3 All functions
You need several attempts. I know the description is not simple. Try! All functions currently work Only not double tap to wake
Thanx for http://bbs.gfan.com/android-9527088-1-1.html
https://forum.xda-developers.com/xp...enz-pie-v1-0-0-26-11-18-t3871854/post78281536
OneHand/Night Mode and XZ2 premium systemUI in zip XZ3 systemUIS has rounded corners It looks weird Better XZ2
Click to expand...
Click to collapse
Does it work for XZ1?
Thanks
unless we get gravitybox (from xposed) features, like in Resurrection Remix, i'm not moving to Pie.

Categories

Resources