Database Info

[MOD]Epic 4G Dual Boot Support -- NOW WITH APP!!!

Dual Boot Support
DualBoot Helper APP is now on the market! (See bottom of this post for more info)
DISCLAIMER: I am not responsible for anything, ever. It is not my fault if you do not read. I do not explain things because I enjoy banging on the keyboard. If you do not read this entire post before jumping in then do not expect me or anyone else to be much help. By following this guide and any links YOU assume all responsibility for your device and anything that happens with it.
What is it?
Dual booting allows you to run two separate roms on your device at one time. It is done by intercepting the mount points during the startup of the device. This is accomplished by checking the sdcard for a specifically named file when the kernel first loads and uses the appropriate files to boot with the correct partitions. Reading from the sdcard is slower than reading from the internal memory of the phone so the speed of your sdcard will drastically determine the speed any rom runs. On the same note a rom flashed to the sdcard will take longer than usual on the first boot.
What does it do for me?
Running two separate roms has many uses for just about everyone. Users can use dual booting to try different roms, themes, apps, modifications, or anything while keeping their existing installation intact. The uses are just about endless. Besides testing different roms, this allows the user try these things and make sure they are compatible and stable before pushing the changes to their internal memory. Rom developers have all of the above options plus a few. Rom developers can additionally use dual booting to test builds of their roms without fear of soft bricking their device. For advanced users, you can mount the partitions of the other rom (be it sdcard or internal) and fix bad apk files or messed up files. The options really are limitless!
What do I need?
Sdcard 2GB or larger
Dual boot compatible kernel
Other things I should know...
*The kernel MUST support BOTH roms you flash. Unfortunately this means you can NOT mix froyo and gingerbread roms. Make sure you know what the kernel supports before you flash anything!
*If you compare roms, benchmarks will hold no value due to the sdcard being so much slower than internal memory.
*Faster sdcards will perform better than slower ones. Note: the stock 16GB sdcard is a class 2 which simply classifies it's minimum speed. A higher class sdcard will more than likely perform faster but the class rating is a minimum and not a maximum. It is entirely possible that a certain class 2 card can out perform a different class 6 card. Keep this in mind when researching to buy a new faster sdcard. More info in this post.
*First boot takes longer than usual. Up to 15 minutes! Please wait until the rom boots and the initial media scanner is done before you judge usability.
*Using a rom from the sdcard will cause the sdcard to wear faster. This is due to many more reads and writes of data than normal. The Epic simply does not have the internal capacity to run dual roms on the NAND. That being said the sdcard is our next option. While it may reduce the over all life of the sdcard keep in mind there are other android devices like the Nook Color and the other Galaxy S phones that have internal sdcards running the Android operating system. My personal opinion with is with other devices running off internal sdcards and with the price of sdcards getting cheaper and cheaper it was worth it to explore this option for the Epic.
Ok ok, so how do I get started?
I am going to break the steps down into sections. Please read everything to ensure you understand what all is involved in getting everything working. I recommend making a backup in Clockwork Mod and saving it to your PC before you even get started.
Section 1 - Setting up the environment
Step 1. Flash a compatible kernel (Kernel developers, PM me if you add my dual boot support to your kernel and I will update the list below) Remember you can NOT mix a eclair, froyo, or gingerbread roms and the kernel MUST support both roms!
Currently compatible kernels:
Genocide 2.0 Supported Roms: EC05, EB13, and DK28
Section 2 - Preparing sdcard
Important information!!!! This will destroy ALL data on your sdcard so if you lose pictures of your dog, cwm backups, nudies of your spouse, etc then you can't blame me. BACKUP YOUR SDCARD!
The easy way:
Reboot into recovery mode with a program like Rom Manager, Quick Boot, or type 'reboot recovery' from a terminal. (NOT 3-finger boot to recovery...this will NOT work)
The easy way WILL erase your sdcard with NO confirmation....you have been warned!
Choose one of the following flashable zips to automatically partition your sdcard
DualBoot_Partition_RFS.zip
DualBoot_Partition_EXT4.zip
The manual way:
Reboot into recovery mode with a program like Rom Manager, Quick Boot, or type 'adb reboot recovery' from a command line. (adb commands assume you have a working install of the Android SDK)
While in recovery issue the following commands:
Code:
adb shell
cd /sbin
./dbpart.sh --help
I put many hours into the partitioning script to make it as simple to use as possible. Simply follow program usage instructions.
Section 3 - Preparing a rom
Since we have blank partitions on the sdcard we need to populate them with data. There are multiple ways to accomplish this and you can choose which solution best suits your needs. I am not going to cover ALL methods here but enough to suffice any likely scenario needed.
The dd method will clone your current setup to the sdcard (these commands may take up to 15 minutes)
The easy way:
Flash this dd script: DualBoot_Clone_to_sdcard.zip
The manual way:
Code:
adb shell
dd if=/dev/block/stl9 of=/dev/block/mmcblk0p2
dd if=/dev/block/stl10 of=/dev/block/mmcblk0p3
dd if=/dev/block/stl11 of=/dev/block/mmcblk0p4
Preparation is complete. Please skip down to booting from sdcard.
The flash method is for flashing a new rom to the sdcard.
The easy way:
There is no sure fire easy way just yet. Stay tuned though.
The manual way:
This method is not that difficult so there is no need to be intimidated by it. It requires editing a few lines of the script that Clockwork Mod executes when flashing a rom or addon. For this example I am going to use a file named epicrom.zip but you can use any name you wish.
Step 1. On your PC, open epicrom.zip (I recommend using a program like 7zip)
Step 2. Navigate to the META_INF\com\google\android\ folder.
Step 3. Drag the file updater-script out of the zip to your desktop.
Step 4. Open the updater-script file with a text editor such as notepad (I recommend notepad++ or textpad)
Step 5. Change every instance of /dev/block/stl9 to /dev/block/mmcblk0p2
Step 6. Change every instance of /dev/block/stl10 to /dev/block/mmcblk0p3
Step 7. Change every instance of /dev/block/stl11 to /dev/block/mmcblk0p4
Step 8. Delete the entire line for any lines that contain /dev/block/bml7 or /dev/block/stl7 to disable flashing another kernel and breaking dual boot support.
Step 9. Save the file and drag and drop it back into epicrom.zip and let it replace the old one.
Note: If you get a status 6 or some other error when trying to flash it is likely you made a typo or your text editor did no save the updater-script file correctly. Recommended action is to correct the typo and/or use one of the recommended text editors note in Step 4.
Section 4 - Flashing to sdcard
Flashing a rom from this point is the same as you usually do. Put the modified rom on your sdcard and flash with Clockwork Mod like usual. I recommend doing a backup in Clockwork Mod BEFORE you flash in case you messed anything up by accident and end up flashing over internal memory when you meant to flash to the sdcard.
Section 5 - Booting sdcard
To boot from the sdcard place a file in the root of your sdcard called 'bootsdcard'. If you named it correctly upon reboot, the kernel will load the rom from the sdcard and not internal memory.
To boot back into internal memory simply remove this file from your sdcard and reboot.
You can switch back and forth using this method. If the file is there it boots sdcard, if the file is not there it boots normally. Pretty simple right?
Section 6 - Other flashables (not roms)
Themes, addons, and anything else that is flashable with Clockwork Mod must be modified in the same fashion as the rom. Use the same procedure documented in Section 3, The flash method.
Kernel Developers:
If you would like to add dual boot support to your kernel please refer to this commit: https://github.com/Rodderik/Genocide-Kernel/commit/a5dfd9f369ae4f2c90c1e7fc7d8995f88f72bd01
I will update this section if I push any specific changes to dual booting.
Now with an APP!
DualBoot Helper
VenumX coded up an APK to work with Clockwork Mod to run the scripts.
http://forum.xda-developers.com/showthread.php?p=15486144#post15486144
Questions, concerns, gripes, or complaints can be left in this thread. If you need to report any problems please be as detailed as possible.

woot
Thats my boy!!!! Make me proud!!!!!!!!!!

w00t! go man go!

Holy ****! This is huge! Thanks!
Sent from my SPH-D700 using Tapatalk

OMFG this is way amazing ;P

Thr genious once again with another first
Sent from my SPH-D700 using XDA Premium App

Edit
nevermind...
good work!!!!!!!!!!!!

davidrules7778 said:
I got a question...
Would i be able to run dual versions of android
Ex 2.1 and 2.2
or 2.2 and 2.3
if the kernal is compatible?
Click to expand...
Click to collapse
if the kernEl was compatible yes...but none of them are...and likely won't be

Good damn job bro.. Let's keep the dev community developing

Rodderik said:
if the kernEl was compatible yes...but none of them are...and likely won't be
Click to expand...
Click to collapse
what if u made one of the eclair kernal compatible or gingerbread whenever we get custom kernals for it?
Or is it not possible to make eclair kernals compatible?

i think i could make a GB kernel now.. but you wouldnt be able to mix gb with froyo or eclair, because a GB kernel wont boot those builds..

Awesome work bro! Amazing...simply amazing!

chris41g said:
i think i could make a GB kernel now.. but you wouldnt be able to mix gb with froyo or eclair, because a GB kernel wont boot those builds..
Click to expand...
Click to collapse
yup i'm going to help chris41g put together a gb kernel for you guys
as far as eclair...honestly who still uses eclair? and why?

Rodderik said:
as far as eclair...honestly who still uses eclair? and why?
Click to expand...
Click to collapse
Just what I was thinking.

Tested on EC05 just now. I uhh... likey? =)
to bad no multi android versions though =(
why cant the kernel read off the sdcard? do you need drivers from samsung once again?

Shoulon said:
Tested on EC05 just now. I uhh... likey? =)
to bad no multi android versions though =(
why cant the kernel read off the sdcard? do you need drivers from samsung once again?
Click to expand...
Click to collapse
well the kernel is stored in bml7 and called by sbl/param during boot so unless we can get a bootloader to intercept the initial loading of the kernel and pass it off we are stuck with one kernel at a time

Very Nice Work !!!

Hey rodd... I think you should work on an aosp gingerbread kernel ... this is a great advancement in devlopment man... right when it was slowing again
Sent from my SPH-D700 using XDA App

this is amazing, thanks for this!!

You cannot make a cross OS kernel. We cannot integrate this into GB yet because there is no GB source, no GB source, no custom kernel. This is Froyo only, and well, someone else can make an eclair only kernel, but that is stupid.

[Q] Flashing Cyanogenmod system.img to LG-P999

Hi everyone! I'm new to Android. I recently bought a T-Mobile G2X / LG-P999, flashed the recovery partition with NVFlash (ClockworkMod) and installed CyanogenMod 7 (nightly). It's working great so far. My question is this: is it possible to flash only the /system partition at a later time with a newer build of CM7? For example, there is a Netflix app available that allows non-approved devices to connect to Netflix. I've tried installing this, but am suffering from the "chipmunk" problem where both the video and audio play back too fast. I read somewhere that an update the the media layer may fix this. It would be convenient to update the entire system partition once newer releases / fixes come out to address problems like this, without wiping out my data.
Also, I've noticed that most of the partitions are listed as ext3 when running mount to view mounted partitions. This seems to be in conflict with what apparently should be the yaffs2 file system. Is CM7 using ext3 instead of yaffs2? I found some source code I compiled that allowed the extraction of the factory G2X ROM dumps, which seemed to be yaffs2 (I did this because I wanted to reinstall the NFS Shift game that ships with the G2X). I suppose it's possible that the original ROMs could be in yaffs2 format, while CyanogenMod defaults to ext3.
Sorry if these are easy questions, but I am really excited about learning more about this OS and doing a little development of my own!

No advice, eh? Well, I'll simplify the question.
If I'm flashing nightly CyanogenMod builds, I'd like to be able to update them every few days, weeks, etc. However, I don't want to have to erase my data so I'd like to only flash the /system partition without touching anything else.
The CyanogenMod zip file contains a system.img, which is what I need to replace /system on my device. However, Clockwork Mod Recovery only has options for flashing complete zip files. Is it possible, perhaps, to just take system.img and zip it? Will ClockworkMod Recovery then only flash the /system partition?

I figured it out, so I'll post my findings:
CyanogenMod nightly zip files contain only boot (kernel) and system files. So, by booting into ClockWorkMod Recovery and choosing "install zip from sdcard," you can update to a new nightly without affecting user data. I assume only the boot.img and /system files are updated. This is what I did, and it seemed to work fine. None of my data was affected!

Mtd vs Bml

The question has been asked several times. Recently a senior member asked a similar question and was told to read post two of a thread. That post did not answer the question but created more doubt. So Im going to steal some information from various posts to hopefully clarify this. Please if I get anything wrong let me know so I can correct it. But most of this will be stripped from various posts.
What is a partition?
A partition is an area of allocated space, a division of the whole overall area of space. In this case our partitions on the Epic 4G are /System, /Data, as well as /Cache. All with set permanent sizes.
What is a partition map?
A partition map is the configuration of our partitions, it's what in a vagueness sets our required sizes for the divisions of our nand also known as flash memory. A partition or partition map should not be confused with a file system. An example would be BML and MTD.
What is a file system?
A file system resides on the partition map and governs the data being read/wrote/moved/etc by the Operating System, in this case Android. Changing a file system is less complex than an overall change in partition mapping. They again, are not the same thing.
What is MTD?
MTD is an Open Source Partition map. It allows those who are using it control over how their partitions are sized and how much space is allocated here and how much space is taken away from there. Currently on MTD we have 689 megabytes of space allocated to our /data partition allowing more to be downloaded from the market as an example. MTD as a partition config has YAFFS2 as a file system residing on it governing how data is transferred and the speed of which it is done. EXT2 through 4 aren't possible on the MTD platform, just as YAFFS2 may not be possible on the BML proprietary platform.
What is BML?
BML like MTD is a partition map, however it is proprietary in nature, Close Source if you will. The size for /System /Data /Cache is set and permanent and makes opening up space more of a task for Developers. Stock the Epic 4G comes on BML, and is running RFS as it's file system, once rooted you can leave RFS for EXT4 (Journaled or Un-Journaled) as long as the kernel you use allows for EXT4. But in the end, changing a file system on BML does not lessen or enhance the control you have over your partitions.
What does it mean for me as an end user?
As an End User, MTD is an opening to a new life for the Galaxy S 4G. Things like ICS, more space in data or system, are more within our reach and grasp due to the nature of Open Source MTD is immersed in. We're closer to the Captivate, Fascinate, Vibrant, and Galaxy S international by being on MTD, we have that new freedom they've had for a long time. Not to say things like ICS aren't possible on BML but with this we're at a better standing point.
Click to expand...
Click to collapse
Basically, the internal storage on your phone is a flash device.
BML and FSR (aka XSR) acts as a software-based FTL (Flash Translation Layer).
This allows you to put filesystems like fat or ext4 on a flash device.
Hardware FTLs are everywhere. Look at your memory stick for instance. There is an FTL between the usb device controller and the nand flash chips that actually store the data. You can format your memory stick with ext4, btrfs, ntfs, whatever...
Samsung decided to go further down the rabbit hole with RFS, which is basically a modified version of FAT(32?) with ACLs and Journalling. IMO, silly.
BUT, fsr/rfs are proprietary modules and are built with a kernel that has a set of symbols exposed. If I disabled debugging (like I did) and something in one of those fsr/rfs modules depended on it, then the fsr/rfs modules wouldn't load (unless you trick it).
Moving to controlling the flash on the phone (in which the flash type on this phone isn't nand, but OneNAND-Flex) with MTD gets us away from the proprietary modules, but introduces a new problem. Can't use ext4 for /system, /data, and /cache anymore. Instead you have to use a flash filesystem, like yaffs2 (which is what the CM supported Samsung phones use). I would like to see a test on this phone with UBI/UBIFS though. I think that might have better performance then yaffs2 or jffs2 (but almost everything, including my grandma is faster then jffs2... seriously).
Click to expand...
Click to collapse
Mtd is the open source partition system used by aosp. Doing so allows more flexibility in porting roms and building from source. The proprietary stuff can be removed and get away from having to keep things like VVM for voicemail **.
This also moves us more towards vanilla android experience. Getting rid of proprietary file systems and and apps and various things to work properly.
Stolen from this thread and this post.
**note Antonx has found a way to remove the requirement for VVM. But is still working out if removing the code will break VVM for those people that use it.

I suggest we put BML to MTD and MTD to BML guides in the stickies. I know this info exists, but having it in the stickies will save many noob disasters and questions as this is getting more and more popular.
Sent from my SGH-T959V using xda premium

itzik2sh said:
I suggest we put BML to MTD and MTD to BML guides in the stickies. I know this info exists, but having it in the stickies will save many noob disasters and questions as this is getting more and more popular.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
BML -> MTD will be a non-issue now since as of the latest commits I made to the CM7 update system (and whatever MTD roms base themselves off of that) we will be able to flash using only the rom.zip. You no longer need to fiddle with the efs backup/restore since the rom.zip will take care of it for you. The basic procedure will be
Reboot to RED cwm
Flash rom.zip
You will be rebooted to BLUE cwm
Flash rom.zip again
I just tested this myself from a completely stock KJ6 install and got onto a working CM7 install using a build I just made (with working IMEI/network/data) using those exact steps.
EDIT
Going back to BML will require a one-click for the time being until we can find a better solution, preferably one that involves CWM

One thing I didn't understand - why do we need a separated one click flash just for bootloaders? Can't it be done on the same time?
2nd, do we really need the bootloaders flash if we move from GB MTD to GB BML?
I assume I can odin just the kj1 kernel after the stock one click, just to get root. Do we have an odin version of AntonX's 1.1.0 kernel?
Sent from my SGH-T959V using xda premium

Well the bootloaders aren't a problem if the person is already on gingerbread. I had been messing with flashing bootloaders via CWM a while back but that just got my phone bricked. Until someone with unbrickablemod helps me test this or I get my own phone ubm'd, we'll have to do it this way.
No, you don't need to flash bootloaders all the time. The only times you need bootloaders are from GB -> Froyo or Froyo -> GB.
You should look into making your own custom one click, it's as easy as opening the .jar file in a program like 7-zip and extracting the files within, then you can recompress them. You can customize exactly what gets installed. I say you start with bhundven's kj6 one click and replace the kernel with your favorite custom one.
The files that get flashed from a one click are these:
one-click.jar/com/AdamOutler/HeimdallOneClick/resources/ROMPackage/HeimdallPackage.tar.gz
If you open that, you'll see all the files that get flashed, particularly zImage and zImage-1.
zImage gets flashed into the KERNEL partition
zImage-1 gets flashed into the RECOVERY partition
As it stands now, both zImage and zImage-1 should be identical since we don't have any recovery images and we have to use a kernel image instead.

[NookHD+] CM10.1 native emmc install Now part of CM Nightlies

By popular demand, I am bringing to you CM10.1 that you can install into Nook's internal ROM.
Note, this version totally overwrites your ROM, so back up everything important before proceeding. This is not a dual-boot solution as before, you do loose B&N ROM for good after installing this.
This is work in progress, yadda yadda.
Simplified instructions if instructions below don't work for you or you cannot follow them.
Get emmc-cwm-early2.1.img.gz, gunzip and write it to an sdcard of at least 1G in size (all content on that card will be lost).
Download CWM recovery (text) or TWRP recovery (gui) zip if you want internal recovery to be replaced with CM one (if you don't know what is it about, then you need ONE of these).
Also download latest binary zip from CM nightlies: http://download.cyanogenmod.com/?device=ovation
Add all these files + whatever other packages you might need right away on to the sdcard.
Boot from that sdcard, and install recovery (if desired) and the cm10.1 binary and whatever else you put there.
Erase /data (During initial install only. this is important to avoid crashes on bootup! Naturally, make sure you have copies of whatever important info from there).
unmount /sdcard and remove the card from the Nook. You might need to use this sdcard for your recovery needs in the future should EMMC content become badly damaged, so probably a good idea to have a copy of it somewhere.
Congrats, now on reboot you'll get into cm10.1 on your Nook HD+.
When you need to get into recovery, you can either do "reboot to recovery" in reboot menu (need to enable that in settings) or reboot the nook, and when you see original nook boot logo, press and hold power + home buttons for about 4 seconds.
If you plan to use USB Host feature, you will need a gender changer, as B&N decided not to release a special cable so far. The control to enable USBHost is in quick settings panel (slide down in the top right corner of the screen to bring it up). (QS controls are not available in CM nightly builds so you'll need to install the switcher app for now if you need it).
Known problems:
- Nook app reports incompatible in market (workaround1: just sideload it ; workaround2: change ro.product.device to nookhdplus in build.prop) - This is because they specifically blacklist Nooks! Note that workaround #2 will actually kill your sound, so revert back when you are done.
- Certain sdcards still remain unstable.
- Google Earth crashes when pressing "my location" button (but works fine otherwise).
Useful apps:
Overall loudness and volume control app: NookHDVolumeAdjuster-1.apk
Touch screen sensitivity control: NookTouchscreenSensitivityAdjuster-4.apk (backup link)
USB host control (not really needed, as you can use Quick Settings panel): USBHostSwitcher.apk
Changelog:
13/08/09 - We are official part of CM now, yay! Further updates will be at http://download.cyanogenmod.com/?device=ovation
13/08/01 - cm-10.1-20130801-UNOFFICIAL-ovation-emmc.zip
- Data usage display should work now
13/07/19 - cm-10.1-20130719-UNOFFICIAL-ovation-emmc.zip
- Picked some kernel fixes from omapzoom tree that I think would be useful for us too, this includes some voltage changes (decreases).
- Disabled hwui scissors optimization as it seems to be doing more harm than good.
- Reverted too greedy davlik vm settings
13/07/16 - cm-10.1-20130716-UNOFFICIAL-ovation-emmc.zip *Experimental*
- Update wifi drivers to R5.SP3.06
13/07/11 - cm-10.1-20130712-UNOFFICIAL-ovation-emmc.zip (backup link)
- Added Apple keyboard support
- Updated to CM-10.1.2 for security fixes
13/07/10 - cm-10.1-20130710-UNOFFICIAL-ovation-emmc.zip
- Updated to CM-10.1.1 for security fixes
13/07/08 - cm-10.1-20130708-UNOFFICIAL-ovation-emmc.zip
- NTFS and ExFAT support from upstream
13/07/06 - cm-10.1-20130706-UNOFFICIAL-ovation-emmc.zip
- redone touchscreen sensitivity changing mechanism. (app to control touchscreen sensitivity NookTouchscreenSensitivityAdjuster-4.apk)
13/07/04 - cm-10.1-20130704-UNOFFICIAL-ovation-emmc.zip
- upgraded to fixed SGX DDK [email protected] (this fixes Google Earth, and a bunch of games)
13/07/03 - cm-10.1-20130703-UNOFFICIAL-ovation-emmc.zip Experimental
- experimental touchscreen sensitivity change
- usb ids changed to match stock
- swap support enabled
13/06/30 - cm-10.1-20130630-UNOFFICIAL-ovation-emmc.zip
- Serial number is now visible in Android
- usb audio now actually works (only for output)
13/06/29 - cm-10.1-20130629-UNOFFICIAL-ovation-emmc.zip
- in-kernel bluetooth
13/06/26 - cm-10.1-20130626-UNOFFICIAL-ovation-emmc.zip Experimental
- cpu frequency changes for screen on scenario, new sgx binary blobs.
13/06/24 - cm-10.1-20130624-UNOFFICIAL-ovation-emmc.zip
- more kernel drivers for bt hid, usb 3g modems and gps devices
13/06/15 - cm-10.1-20130615-UNOFFICIAL-ovation-emmc.zip
- WiFi Direct and BT tethering are now working
- /sdcard now points to internal storage.
13/06/13 - cm-10.1-20130613-UNOFFICIAL-ovation-emmc.zip
- Boosted speaker volume. If you do not like new loud volume, flash this reversal zip after every ROM update: quietvolume-2.zip
- zinio now should work out of the box
13/06/11 - cm-10.1-20130612-UNOFFICIAL-ovation-emmc.zip
- Fixed HDMI audio
- Added USB audio support
13/06/08 - cm-10.1-20130608-UNOFFICIAL-ovation-emmc.zip
- Fixed nav bar settings crash
13/06/05 - cm-10.1-20130605-UNOFFICIAL-ovation-emmc.zip
- USBHost access is now conveniently located in QuickSettings. (IF you use some mod that disables quick settings, you still need my old ugly USBHost switcher app, just sideload it).
- now any (one at a time) usb storage should be automounted no matter how you plug it.
13/06/02 - cm-10.1-20130603-UNOFFICIAL-ovation-emmc.zip
- Forced USB Host support.
13/05/30 - cm-10.1-20130530-UNOFFICIAL-ovation-emmc.zip
- No Nook-specific changes, based on CM10.1-RC3
13/05/27 - cm-10.1-20130527-UNOFFICIAL-ovation-emmc.zip
- Fixed microphone input volume
- Kernel change to hopefully better work with some sdcards.
13/05/12 - cm-10.1-20130512-UNOFFICIAL-ovation-emmc.zip
- Fixed A2DP audio
- Fixed booting when not connected to PC/charger.
13/05/11 - cm-10.1-20130511-UNOFFICIAL-ovation-emmc.zip
- Should fix sgx crash on startup for those affected -- not.
- Cover close now should sleep the device (please test)
- Updated screen properties to highdpi (though that did not fix Nook app compatibility in market)
- Baselined on CM10.1-RC2
13/05/10 - cm-10.1-20130510-UNOFFICIAL-ovation-emmc.zip
- Wifi battery drain should be gone now.
13/05/05 - cm-10.1-20130505-UNOFFICIAL-ovation-emmc.zip
- Fixed mmc presentation, BT, sdcard mounting.
13/05/04 - cm-10.1-20130504-UNOFFICIAL-ovation-emmc.zip initial release.

Thanks for this though.
Verygreen, I am interested how this boots without sdcard as before the expliot worked because B&N left dev code to boot a kernel from sd card.
What exploit is used to boot from internal since sdcard isn't used.
Also I don't think cm10 is needed really.
I think its best to put the work into cm10.1 as its the latest platform and try bring that up to the same stage as cm10.

Wow, thank you once again verygreen! Thank you so much for your efforts!
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Regardless, appreciate your efforts once again!

HiddenG said:
Wow, thank you once again verygreen! Thank you so much for your efforts!
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Regardless, appreciate your efforts once again!
Click to expand...
Click to collapse
Is the reboot to 99% problem solved ? This is the biggest issue to me.

sorrowuk said:
Verygreen, I am interested how this boots without sdcard as before the expliot worked because B&N left dev code to boot a kernel from sd card.
What exploit is used to boot from internal since sdcard isn't used.
Click to expand...
Click to collapse
Same method as Bauwks, B&N forgot to fix it, they fixed some other possible vectors only.
I was holding to this knowledge hoping that it would be useful on next B&N reader, but it does not look like they'll release another omap-based one, so no need to keep suffering anymore.
So here's hope whatever they release next, the debugging code will remain in place
HiddenG said:
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Click to expand...
Click to collapse
Yes, this does overwrite stock ROM, so no dualboot.
While it's possible to perform some hair-splitting by putting multiple kernels into boot partition, that's quite a bit of hassle + all the /data splitting, so I decided to not go that way, at least yet.
There are performance differences. I did not perform any real studies, but I was shocked at how fast the install phase in cwm works compared to sdcard.

lchen5 said:
Is the reboot to 99% problem solved ? This is the biggest issue to me.
Click to expand...
Click to collapse
Yes, it is solved by removing the ROM, so nothing is left there that could complain about cards with too many partitions

Awesome
I've gotten this loaded up this morning, haven't done a whole lot with it as of yet, but it did boot right up
I have noticed one thing that is not working correctly, specifically the sd card. It's reported as not mounted.

aszid said:
I've gotten this loaded up this morning, haven't done a whole lot with it as of yet, but it did boot right up
I have noticed one thing that is not working correctly, specifically the sd card. It's reported as not mounted.
Click to expand...
Click to collapse
Yes, I was just going to post that. Verygreen forgot to change the vold.fstab file from the sdcard version to emmc version.
Go to /system/etc/ and edit the vold.fstab file to say "/storage/sdcard1 auto" instead of "/storage/sdcard1 5". Just change the 5 to an auto. Then reboot and it should be ok.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
Yes, I was just going to post that. Verygreen forgot to change the vold.fstab file from the sdcard version to emmc version.
Go to /system/etc/ and edit the vold.fstab file to say "/storage/sdcard1 auto" instead of "/storage/sdcard1 5". Just change the 5 to an auto. Then reboot and it should be ok.
Click to expand...
Click to collapse
It's always the small things that gets forgotten, sigh.
I knew I needed to update that, but did not find it at 4am. Now it's in my tree, so next version will have it fixed.
Also need a better way to write sdcard image, I guess, without uploading a whole gig or so of zeros which will get slow. I tried to put in some shortcuts to minimize the write area, but failed so far. Since everything is in the same partition, changing stuff on the fly is hard.
Perhaps a solution where we only use sdcard as means to do initial bootstrap and write correct recovery and use /data/media as the actual sdcard would be better after all.

Follow up question
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?

jentous said:
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
Click to expand...
Click to collapse
For restore (note, I did not really test any of these steps, but that's how it should unfold):
boot into recovery image from sdcard you made at the beginning.
Upload the backup boot image there (adb push mmcblk0p4 /tmp)
then do adb shell and in there write the image in place:
dd if=/tmp/mmcblk0p4 of=/dev/block/mmcblk0p4 bs=1048576
then do:
mount /bootdata ; rm /bootdata/BootCnt
The removal of BootCnt will tell stock u-boot to force factory restore.
now remove sdcard and reboot, the Nook will do factory restore and you are back to some sort of early 2.0.0 B&N release.

verygreen said:
It's always the small things that gets forgotten, sigh.
I knew I needed to update that, but did not find it at 4am. Now it's in my tree, so next version will have it fixed.
Also need a better way to write sdcard image, I guess, without uploading a whole gig or so of zeros which will get slow. I tried to put in some shortcuts to minimize the write area, but failed so far. Since everything is in the same partition, changing stuff on the fly is hard.
Perhaps a solution where we only use sdcard as means to do initial bootstrap and write correct recovery and use /data/media as the actual sdcard would be better after all.
Click to expand...
Click to collapse
I've been trying to examine what you have done here, and have most of it figured.
That CM zip is pretty straight forward where it just flashes the rom to emmc /system and replaces the boot.img.
The CWM looks straight forward too, but you must use the empty file for something and I can't quite figure that. I thought maybe you were using it to mount something on emmc but I see no code to do that in the ramdisk. You might have the code in a customized init binary. Recovery looks like just a normal 6.0.3.2 recovery from CM.
A suggestion on the CWM recovery.fstab. Change the boot partition fstype from vfat to emmc and backup/restore will handle it properly. And change the emmc to datamedia and /dev/null instead of vfat and 0p10. That way the emmc media partition will mount properly.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
That CM zip is pretty straight forward where it just flashes the rom to emmc /system and replaces the boot.img.
Click to expand...
Click to collapse
Yes, it's pretty straight-forward, and that was one of the goals. Unlike Kindle where you need to jump through some crazy hoops due to Amazon design decisions, Nook is significantly more relaxed.
The CWM looks straight forward too, but you must use the empty file for something and I can't quite figure that. I thought maybe you were using it to mount something on emmc but I see no code to do that in the ramdisk. You might have the code in a customized init binary. Recovery looks like just a normal 6.0.3.2 recovery from CM.
Click to expand...
Click to collapse
The recovery IS straighforward, there's no modified init or anything like that. I am not sure what empty file do you refer to.
The only difference between this CWM and sdcard cwm for sdcard installs are: removed repartitioning code in postboot script and updated fstab to point back at emmc.
A suggestion on the CWM recovery.fstab, change the boot partition fstype from vfat to emmc and backup/restore will handle it properly. And change the emmc to datamedia and /dev/null instead of vfat and 0p10. That way the emmc media partition will mount properly.
Click to expand...
Click to collapse
Aha, thanks. I'll try this and it'll probably solve the remaining CWM problems for me.
Also need to do twrp image, I guess.

verygreen said:
The recovery IS straighforward, there's no modified init or anything like that. I am not sure what empty file do you refer to.
Click to expand...
Click to collapse
I'm talking about the "file" in the recovery image. It is about 950MB and all zeros.
And if you make those mods to the recovery.fstab, then users can use that CWM to reflash back to stock using the B&N zips.

leapinlar said:
I'm talking about the "file" in the recovery image. It is about 950MB and all zeros.
Click to expand...
Click to collapse
Whoops, forgot to remove.
This is how I zero out sdcard content so it better compresses before uploading it somewhere.

jentous said:
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
Click to expand...
Click to collapse
Based on what verygreen said in the posts above, you should be able to use my stock CWM SD to both backup and restore his new setup. And you can restore an earlier backup of stock too. You can use my 2.1 zip on my thread to put the new stock on if you want replacing his CM10.1 on emmc.
Thanks verygreen, you are awesome!
EDIT: Yes! I just flashed verygreen's new CM10.1 emmc to my internal memory using my stock CWM SD. Worked perfectly.

I just uploaded emmc-cwm-early2.img.gz with fixed recovery.fstab and a zero file removed as well.

Got it going
Thanks Verygreen and Leapinlar.
I got it installed and I saved the boot partition just in case. I hopefully will not be needing to restore, but it is nice to know that I can.
The installed ROM appears snappy and I will report back any issues I discover.

my sdcard is working great after updating the mount. Thanks!
leapinlar said:
Based on what verygreen said in the posts above, you should be able to use my stock CWM SD to both backup and restore his new setup. And you can restore an earlier backup of stock too. You can use my 2.1 zip on my thread to put the new stock on if you want replacing his CM10.1 on emmc.
Thanks verygreen, you are awesome!
EDIT: Yes! I just flashed verygreen's new CM10.1 emmc to my internal memory using my stock CWM SD. Worked perfectly.
Click to expand...
Click to collapse
verygreen said:
I just uploaded emmc-cwm-early2.img.gz with fixed recovery.fstab and a zero file removed as well.
Click to expand...
Click to collapse
Is there any effective difference between the 2 recoveries? That is.. is there any reason i should be bothering to keep 2 different recovery SD cards?
Thanks for all the great work!

aszid said:
Is there any effective difference between the 2 recoveries? That is.. is there any reason i should be bothering to keep 2 different recovery SD cards?
Click to expand...
Click to collapse
There's no great logic in my recovery, just an image I use to test-drive my installs for now.
So you can use whatever other recovery you like.

[RECOVERY][Huawei Prism II aka Huawei U8686] CWM 6

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or
* unfulfilled sexual partners. Please do some research if you have any
* concerns about features included in this Recovery before flashing it! YOU are
* choosing to make these modifications, and if you point the finger at me
* for messing up your device, I will point that finger back at you and laugh.
* Then I will put it in your eye.
*/
By using the Recovery you agree with the above terms!
ver = 6.0.3.7
This CWM recovery image is UNOFFICIAL
CWM recovery allows you to flash custom roms on to your Prism 2.
What works:
wipe cache partition seems to work
wipe dalvik cache seems to work
reboot to recovery works
reboot to bootloader works
volume keys/power button work
backup works
wipe data/factory reset also works
What doesn't work:
USB mounting
Installing Clockworkmod Recovery
Prerequisites:
Unlock boot loader: http://forum.xda-developers.com/showthread.php?t=2546455
Install adb/fastboot on your computer
Turn on usb debugging in developer settings on your phone
[optional] install quickboot to easily enter recovery/fastboot on your phone https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot (requires root)
CWM Installation
open terminal on your computer
cd to directory where you downloaded recovery3.img
Enter fastboot mode on your phone
type in the terminal:
Code:
fastboot flash recovery recovery3.img
Thanks to:
@streetdev22 for fearlessly testing all those unstable recovery images
the developers of Cyanogenmod and ClockworkMod for making their work open to everyone
General Guidelines for Going back to Stock Rom, Recovery, and Bootloader for Warranty.
Prerequisites:
Unlocked bootloader on your phone
CWM recovery on your phone
Fastboot on your computer
Restoring to Stock
Download "Android 4.1.1 - 100 Perfect stock. No root. Has carrier IQ! Beware" from http://droid-hive.com/index.php?/topic/2610-rom-flashable-stock-based-roms-for-the-u8686-prism-ii/
Copy the zip file to sdcard on your phone
Boot into recovery
Select "install zip"
Choose zip from sdcard
Reboot into fastboot
Download and extract recovery-dd.rar
Open terminal
cd to extracted img from recovery-dd.rar
Type in terminal
Code:
fastboot flash recovery recovery-dd.img
Type in terminal
Code:
fastboot oem lock
Files & Source :
recovery3.img = CWM 6 recovery image for Huawei Prism II
recovery-dd.rar= original Huawei Prism II recovery image
update.zip = alternate way to install CWM recovery. (same files as recovery3.img)
Stock Rom: http://droid-hive.com/index.php?/topic/2610-rom-flashable-stock-based-roms-for-the-u8686-prism-ii/ Credit to @mattlgroff
Source if you want to build your own recovery image: https://github.com/Prism2/Huawei-Prism-2-U8686/tree/master/hwu8686 (Only tested with CM 10.2 M1)

Thank you for making this turd a little more bearable. Waiting on unlock and I can test ROMs. 50 dollar temp phone till my s4 get fixed so not worried. Really appreciate the hard work and the fearless testing by Mr double down aka streetdev22. Lol.
Sent from my Prism II using Tapatalk

DevilDog512 said:
Thank you for making this turd a little more bearable. Waiting on unlock and I can test ROMs. 50 dollar temp phone till my s4 get fixed so not worried. Really appreciate the hard work and the fearless testing by Mr double down aka streetdev22. Lol.
Sent from my Prism II using Tapatalk
Click to expand...
Click to collapse
You're welcome! Haha. I couldn't have described the phone better myself :laugh:

Can anyone post a virgin list of apps for the Prism II?
Or at least close? I want to build a list of uninstallable apps. I have uninstalled a lot so far, but I should have uploaded the list of original apps. Right now, I have around 59 Apps, and Idle RAM usage(all previous apps closed) is around 225MB used and 180MB free. I want to slim the bloatware from this little turd, and I've done a decent job so far, but more can be improved. I am trying to delete the automatically mounted autorun.iso when the phone is plugged in, since that is just wasted storage. I am also trying to find out what the cust partition contains and whether or not I can delete the contents in order to expand system storage. A new bootanimation would be nice as well

streetdev22 said:
Or at least close? I want to build a list of uninstallable apps. I have uninstalled a lot so far, but I should have uploaded the list of original apps. Right now, I have around 59 Apps, and Idle RAM usage(all previous apps closed) is around 225MB used and 180MB free. I want to slim the bloatware from this little turd, and I've done a decent job so far, but more can be improved. I am trying to delete the automatically mounted autorun.iso when the phone is plugged in, since that is just wasted storage. I am also trying to find out what the cust partition contains and whether or not I can delete the contents in order to expand system storage. A new bootanimation would be nice as well
Click to expand...
Click to collapse
I also have around 180 mb free. I found greenify helps me identify and close unwanted apps. https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en Just make sure auto greenification is turned off in the setting or else it will run in the background!
autorun.iso is in /system/cdrom/autorun.iso (don't know the effect of removing this file though)
I think boot animation is in /cust/t-mobile/us/media
cust partition is mounted to /cust so it contains the boot animation along with some tmobile ringtones(again don't know the effect of removing this partition)

I too had about that. Even after installing v6supercharger. Still lags like a B. Cust has boot animation in it. I renamed all with .bak and could just copy and paste some I had for s4. Display was off tho. Unfortunately I accidentally flashed custom recovery on locked bootloader and haven't been able to get it back. Might toss in the microwave for a few secs. and take it back to wally world. Only had the thing for a week and I got note 3 today.
Sent from my SM-N900P using Tapatalk
---------- Post added at 10:24 PM ---------- Previous post was at 10:21 PM ----------
Prism 2 said:
I also have around 180 mb free. I found greenify helps me identify and close unwanted apps. https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en Just make sure auto greenification is turned off in the setting or else it will run in the background!
autorun.iso is in /system/cdrom/autorun.iso (don't know the effect of removing this file though)
I think boot animation is in /cust/t-mobile/us/media
cust partition is mounted to /cust so it contains the boot animation along with some tmobile ringtones(again don't know the effect of removing this partition)
Click to expand...
Click to collapse
It also has a build prop in it. I wouldn't erase it just. Nothing in there is using any ram that I'm aware of.
Sent from my SM-N900P using Tapatalk

AnTuTu benchmarks me at 4298, which is fairly good for a $50-$60 device. For comparison: http://www.antutu.net/Ranking.shtml?cmd=mobile&page=5
Shows that my phone is right around the Samsung Galaxy Ace 2. With a custom ROM and some tweaks, i'm hoping this phone could pull a 4800 and I'd be happy. I deleted the autorun.iso, so the cd is now empty, but I'm working on dismounting it entirely.
The cust folder can be edited and eventually deleted, as is done in custom ROMs for other Huawei devices.
Also, I got about 200MB free RAM by deleting 2DHome, installing nemus launcher, and moving nemus launcher to /system/app, so I can retain the launcher even after factory reset.
I will work my hardest to rid this phone of the T-mobile crap and debloat. I got down to about 50 system apps(including Nemus) and 2 installed apps.
If I can manage to get rid of this cust partition, I might expand a nearby partition to that empty partition. Eventually, I'm considering deleting the cust partition, expanding a nearby partition, and trimming system partition so data can have more.
What do you guys think?

I liked Nemus Launcher, got rid of considerable lag. But I switched back to Action launcher because of the way the app drawer works.
Just a thought...

Rom for Prism II
I have rooted several phones, including the notoriously difficult VM Evo V. (It only took me 3 times to get the timing of the connectors right!).
I have my Prism II unlocked and rooted. I have been constantly watching the forums because I can't shake the feeling like a custom rom would make this crappy little phone (which I got for $30 on sale at best buy) not suck so hard. I had my s4 ripped off, so you can imagine the suck of having to use the Prism II instead.
I guess my question is: Does this mean I can use Cyanogenmod on this phone? I might be able to follow guides and unlock most phones, but I am only in my first year of my software development degree and I my knowledge about how Roms work is pretty limited.
I am not seeing anything on teh internets about u8686 roms, and everyone said they were waiting for CWM to be able to bring roms in. Since this has happened according to this post, is there anything available now?

The resources for anyone willing to build a custom ROM is there.
Here is a link to my 4shared folder containing everything and anything Huawei Prism II related including a detailed/cleaned up version of the partition layout, working recoveries, the kernel released by Huawei, my nandroid backup(from which you can extract /system), and my cust.img.
http://www.4shared.com/folder/ycaEzuL3/Huawei_Prism_II.html
All someone has to do is either put in the time porting cyanogenmod to this phone using the resources given, or someone can start with stock and debloat, debrand, tweak, and theme in order to get a custom ROM.
My goals in the near future:
-Remove /system/cdrom from ever being mounted, it just annoys me
-Remove /cust partition by symbolic linking, and expanding cache to cover the wiped /cust partition
-Removing /HWUserData partition and expanding /data partition to cover the wiped partition(expands /data to 2GB)
-Removing /HWUserData mount, so that /sdcard will be the only one mounted when USB is connected.
-Removing CarrierIQ permanently(not just the apps)

streetdev22 said:
All someone has to do is either put in the time porting cyanogenmod to this phone using the resources given, or someone can start with stock and debloat, debrand, tweak, and theme in order to get a custom ROM.
Click to expand...
Click to collapse
Can you suggest any guides or anything that someone can view to get started. I would love to do what you suggest, but I'm not even sure where to start.

I will post some more links once I get home. Here is a good one to get started:
http://forum.xda-developers.com/showthread.php?t=1801690

For those looking to start from scratch, this is a really good reference (the Prism 2 is based on msm7627a chipset) https://github.com/Dazzozo/android_device_huawei_msm7x27a-common. His other github repositories also contain some really helpful information!

Prism 2 said:
For those looking to start from scratch, this is a really good reference (the Prism 2 is based on msm7627a chipset) https://github.com/Dazzozo/android_device_huawei_msm7x27a-common. His other github repositories also contain some really helpful information!
Click to expand...
Click to collapse
I'll be working off of this tree as soon as I get my T-Mobile Prism II

Sweet,Thanks!
Update for cust.img:
All boot animations can be moved to /system/media and they will still function. I moved all audio to /system/media/audio in their
corresponding folders, also works. This means that I only have my wallpapers and a few other files left in the cust.img (around 5MB used/75MB free). If the rest of the files could be symbolically linked through a modification in the kernel, then the partition could be wiped. Otherwise, around ~10MB (some buffer space) would have to be left for the cust partition. We could take advantage of ~70MB to extend the system partition or cache.
System partition with stripped bloatware(only 50 system apps left) leaves about ~585MB free.If you want the list of apps I have left, I can post them. This means that about 500MB can be freed to /data if /HWUserData partition is removed as well. /HWUserData is somewhat trivial, since most people have an external sd card, and the space can be freed to the /data partition.
Altogether, the /data partition can grow from 1.1GB to about 2.9GB! That would be plenty of storage for things we really need.
/HWUserData is mounted in the kernel as is /cust, so a modified kernel may be necessary.
I just don't appreciate the mess of a partition layout they made. If that could be fixed, /data would be much larger.
Also, anyone have any kernel suggestions? We could go one of three routes typically according to this guide: http://forum.xda-developers.com/showthread.php?t=1369817
We could go for speed(at the sake of battery life), battery life(not really change much of performance), or a combination of both. I think this phone has a decent battery life, so we could go for a combination of both performance/battery life improvements.
Some other features that would be helpful:
-block OTA updates(doubt we will ever get one, but just in case)
-renaming of mounts for /sdcard in kernel(init.rc) to /sd_ext(so possibly usb mount in recovery would work) instead of /sdcard0 and /sdcard1(one of which is actually /HWUserData
-custom boot animation(because this one just makes me cringe)
-debloat(already have the list of apps able to be deleted)
-improved RAM usage(got to about 200MB used /200MB free with no apps running, but would be nice to get down to 150MB used/250MB free)
-add data on/off switch in notification area(I know there are widgets that can replace it)
-deletion of that annoying cdrom that pops up when you plug in through USB(yes, you can delete autorun.iso and the cdrom folder, but the mount still occurs, even though it is empty)
- as amamartin999 mentioned, It would be nice that the physical home button acts as the launcher instead of another one above it.
-Last, but certainly not least, I know there is still carrierIQ software on this phone somewhere..I deleted all the apps, but I just have a feeling it is still running in the background.
Obviously, this is a mighty list of changes and there is no doubt not all of them will be added, but they are just considerations. Thank you for being the first developer to pick up this phone!

Is there an OTA that anyone has managed to pull so we can modify it and try to boot up a stock ROM in CWM?
And has anyone tried making their own system.IMG.ext4 and flashing it in fastboot? Or flashing a pulled boot.IMG in fastboot? Or knows if 'fastboot boot' works?
I'm looking at the 28th of this month for a delivery date.
Symlinking in init.rc shouldn't be hard to do at all.
Sent from my XT1053 using Tapatalk

Never tried reflashing my system partition
No OTA's were ever given for my phone(although I did purchase off of ebay). I do have a pulled system.ext4.tar from cwm nandroid backup(does it work the same?), and the stock boot.img from the nandroid backup as well including all necessary files in my 4shared fiolder:
http://www.4shared.com/folder/ycaEzuL3/Huawei_Prism_II.html
Which includes the partition layout with as much info as we know revealed by recovery.fstab, a cust.img, my whole backup,the working stock recovery, the kernel released by Huawei, and the cwm recovery.
I never tried booting the boot.img, but I believe it is the right size and I will try the fastboot boot command later tonight. The fastboot boot recovery.img command never seemed to work, but hopefully fastboot boot boot.img will.
Let me know if you need anything!

streetdev22 said:
No OTA's were ever given for my phone(although I did purchase off of ebay). I do have a pulled system.ext4.tar from cwm nandroid backup(does it work the same?), and the stock boot.img from the nandroid backup as well including all necessary files in my 4shared fiolder:
http://www.4shared.com/folder/ycaEzuL3/Huawei_Prism_II.html
Which includes the partition layout with as much info as we know revealed by recovery.fstab, a cust.img, my whole backup,the working stock recovery, the kernel released by Huawei, and the cwm recovery.
I never tried booting the boot.img, but I believe it is the right size and I will try the fastboot boot command later tonight. The fastboot boot recovery.img command never seemed to work, but hopefully fastboot boot boot.img will.
Let me know if you need anything!
Click to expand...
Click to collapse
Could you possibly upload them to Mega.co.nz or another site like dev-host? I don't really want to create an account and/or give 4shared ad revenue. And check your PM I can do some tests on your device to see if we can make a system.img.ext4. And unfortunately no the .tar file from CWM isn't the same.
However, if you can restore from that backup perfectly fine then there really isn't a big need to make a system.img.ext4 for fastboot restore.

I thought huawei released the kernel? I may be mistaken. I'll look into it when I get a chance.
Sent from my Prism II using Tapatalk

Excitement at its finest.
Flashed first customized kernel made by mattlgroff..worked fine. Removed some carrierIQ stuff, freed up about another 20MB of RAM just from that. Working on some more stuff. Will keep you guys updated. Looking very promising! Of course, big credit to Prism 2 and mattlgroff!
Edit:
-CarrierIQ mostly removed
-annoying CDROM is gone
-some memory also released
Can't wait until we get to that partition layout!