Database Info

[ROM] VegaBean for Advent Vega / PoV Mobii Tegra and other P10AN01 clones

[INTRODUCTION]
This ROM is based of the joined effort of a couple of devs (Ejtable, Scanno and Brucelee666) who are working on getting JellyBean working for our device. As soon as JellyBean is getting stable, my goal is also to put everything on github, just like i did with VegaCream. This way other devs can also work on this.
Please remember that I, ejtagle and brucelee666 are *NOT* professionals and do this in our spare time. We all have full time jobs and a family. So be happy that there is an Android ROM based on Android 4.1.1 / JellyBean for a device that was sold with Android 2.2 and never had an update.
We do our best to make this ROM as good as possible. With VegaCream we gave you a ROM that gave a new life to your tablet and unleashed its full potential. But we are not wizzards and there might be problems that we cannot solve or do not have time for.
[SPECIFICATIONS]
This ROM is based on AOSP 4.1.1 and the device config made by Ejtagle, brucelee666 and myself.
- INT2EXT+ (Needs a correctly partitioned SDCard)
- zRAM
- DPI is set at 120dpi
- Default JellyBean Launcher installed
- Apex Launcher installed
- Filemanager installed
- Terminal installed
- Google Apps is installed. This means that the Google base is installed and all the apps that are available in the Play Store are not installed (i.e. GMail, Maps)
- All languages that are available in AOSP are included
- Partition layout is the same as VegaCream / VegaICS beta1 / Modded stock
- /system/app, /system/lib, /system/fonts, /system/framework and /system/usr are Squashfs filesystems.
[INSTALLATION]
There are 2 methods of installation. There is a CWM recovery flashable ZIP and a NVFlash file.
I realy recommend flashing VegaBean the first time with the NVFlash version.
Before installing any version, you have to make sure that you have a SDCard that has the correct partition layout:
- First partition is a primary partition formatted as FAT32
- Second partition is a primary partition formatted as EXT4
EXT4 is a linux filesystem so you will need a program that can handle Linux filesystems when you are using Windows.
Before installing the ZIP file make sure that:
- You have the correct partition layout (if you have VegaCream installed, you have the correct layout, if not then use the NVFlash installer. This will repartition your internal memory))
- Copy the ZIP file to your SD-Card
- Boot into Recovery
- Do a FULL WIPE / FACTORY RESET
- Install the ZIP file from your SDCard
- After installing reboot the tablet.
[WORKING]
- WiFi
- Bluetooth (Tested with a A2DP headset)
- Camera
- HDMI including audio
- 3G (only fro the Huawei internal modem, usb modems may work)
- GPS not tested by me, but some say it kind of works.
[CREDITS]
- Ejtagle
- Brucelee666
- Scanno
- LeoP for his zRAM implementation
- Legionaire (for the VegaBean bootanimation)

[DOWNLOADS]
Please do *NOT* use Link2SD anymore. You do not need it. With the INT2EXT script, your apps will install on SDCard by default. Just make sure you have 2 primary partition. First partition *MUST* be a FAT32 partition. The second partition *SHOULD* be EXT4. When upgrading from a previous version, make sure your EXT partition is empty / reformatted. Also when using the NVflash version !!!
Downloads:
https://www.androidfilehost.com/?w=files&flid=118264

[Changelist]
[Beta 6]
- RIL updated to the latest version (3 october i think)
- updated to AOSP 4.1.2
- Added check to see if there is a second partition on the SDCard. If not INT2EXT is not excecuted (PLEASE TEST !!!)
- Updated GApps
[Beta 5]
Changes compared to Beta 3-1:
- New kernel with the following changes:
- Suspend problem solved. Tablet does not enter LP0 anymore
- Compiled with zRAM support
- zRAM modules added
- zRAM implementation from LeoP included
- RIL from ejtagle updated
[Beta 3-1]
- Included int2ext+
- Included bootanimation for legionnaire
[Beta 3]
- Latest RIL from EJTagle
- CM10 keyboard
- Stock browser with the option to set User Agent
- You can now just wipe cache and dalvik-cache when updating from a previous VegaBean version. Please remember that from other version you will have to do a full wipe / factory reset !!!
[Beta 2.2]
What has changed compared to Beta 2
- AOSP updated to JRO03L
- Latest update to the huaweigeneric RIL (from aug 27) by EJTagle
The stripped version has the following apps removed from /system/app compared to the original version:
- ApexLauncher.apk
- PlayMusic.apk
- Talk.apk
- YouTube.apk
The stripped version should give you around 10 MiB extra on /system. So if you have bad NAND problems and have problems booting (not able to) you can try this.
[Beta 2]
- HDMI audio working
- VegaBean bootanimation added by indigolemon
[Beta 1]
- Rotation really fixed and HW acceleration working
- Disable / Enable GPS would crash, fixed (thanks Eduardo)
Alpha 3:
- Rotation Fixed. Portrait mode is working correctly
- 3G files included... Sadly no 3G because of too old version of Huawei RIL. Need at least version 6 and we have version 4. So if anybody can get his / her hands on a newer version, please let us know.

Hey , very nice to see JellyBean here
I have ViewSonic 10s
I am using at this moment VegaICS , so i am thinking to upgrate it to JB. So my questions :
- kernel with hostdriver ?
- is system rewritable?? its Squashfs so i think its not (like VegaICS, no deletable apps...)
- can I update BusyBOX and Superuser ??? (always after i did it , WIFI was brocken and I lost root (VegaICS))
- is it possible to change DPI to normal 160 ??
............................
One more question about CWM
always after installing any Roms via CWM , it booted , but after first reboot/turnoff my device died... only what help is reflashing via NVflash....
So what should i flash first to use a stable-CWM (without killing device)
any suggestions

If you are still using VegaICS, I suggest you switch to VegaCream RC2. It has an NVFlash installer, so you don't have to use CWM at all. It is by far the most stable and fast ROM ever built for our devices, and is 100% feature complete.
This ROM is a beta, and if you have not experienced VegaCream RC2 yet, you should try that first and wait on this for a later release.

rpmccormick said:
If you are still using VegaICS, I suggest you switch to VegaCream RC2. It has an NVFlash installer, so you don't have to use CWM at all. It is by far the most stable and fast ROM ever built for our devices, and is 100% feature complete.
This ROM is a beta, and if you have not experienced VegaCream RC2 yet, you should try that first and wait on this for a later release.
Click to expand...
Click to collapse
ye but its 120 dpi... its horrible and all is toooo small .. can see pixels

What a great ROM, but I've got a problem where my Viewpad don't boot. Ok, it boots the first time after installing it, but not on 2nd boot. I've tried to install it over both VegaICS and VegaCream RC2. Does anybody have a solution? I really want this ROM. I had the same problem on VegaCream in the past, but it I think it works now, but not in VegaBean. I hope I get any help...
Sent from my HTC Sensation, Venom-infected with the ViperS ROM!

2minuutes said:
What a great ROM, but I've got a problem where my Viewpad don't boot. Ok, it boots the first time after installing it, but not on 2nd boot. I've tried to install it over both VegaICS and VegaCream RC2. Does anybody have a solution? I really want this ROM. I had the same problem on VegaCream in the past, but it I think it works now, but not in VegaBean. I hope I get any help...
Sent from my HTC Sensation, Venom-infected with the ViperS ROM!
Click to expand...
Click to collapse
ye its the same problem , flashing with CWM kill your Pad at second boot
thats why i am flashing only via NVflash

Vlad87do said:
ye its the same problem , flashing with CWM kill your Pad at second boot
thats why i am flashing only via NVflash
Click to expand...
Click to collapse
VegaCream works now after flashing it through NVFlash. Could the boot problem have something with an uncomplete CWM or something? Like it "destroys" the important partitions?Since both VegaCream and VegaICS use an unofficial build of CWM with Touch-interface? Mabye I'll try to flash an official version and install VegaBean through there! Will report back if it works!

Nice, will test this out!

2minuutes said:
VegaCream works now after flashing it through NVFlash. Could the boot problem have something with an uncomplete CWM or something? Like it "destroys" the important partitions?Since both VegaCream and VegaICS use an unofficial build of CWM with Touch-interface? Mabye I'll try to flash an official version and install VegaBean through there! Will report back if it works!
Click to expand...
Click to collapse
I can now confirm that flashing VegaBean through official CWM works, and it boots and 2nd boot too... Just download the .zip file at the bottom and follow this guide by me: http://forum.xda-developers.com/showthread.php?t=1597556 or this guide by add.thebad: http://forum.xda-developers.com/showthread.php?t=1041036
Don't forget to hit the "Thanks" button if I helped you out
Link: https://dl.dropbox.com/u/85837377/recovery.zip

Thank you , i will do it then today !
Should i do it better via PC-adb and flash 3.0.2.8 with guide from add.thebad or better your method and recovery OR its just the same recovery 3.0.2.8 just deffirend flash method ???
...........................
Permission request to scanno: can I use his rom as base for Remics-Vega??

Vlad87do said:
Thank you , i will do it then today !
Should i do it better via PC-adb and flash 3.0.2.8 with guide from add.thebad or better your method and recovery OR its just the same recovery 3.0.2.8 just deffirend flash method ???
...........................
Permission request to scanno: can I use his rom as base for Remics-Vega??
Click to expand...
Click to collapse
If you want to use this for a new rom go ahead. Just give the credits for the work done (also ejtagle and brucelee666)
Modifications to the standard AOSP source code can be found on my github. Also the kernel sources are there too.
They are not up-to-date yet.
If you find solutions to problems in the ROM, give them back to the community so they can also be used in other ROMS.

scanno said:
If you want to use this for a new rom go ahead. Just give the credits for the work done (also ejtagle and brucelee666)
Modifications to the standard AOSP source code can be found on my github. Also the kernel sources are there too.
They are not up-to-date yet.
If you find solutions to problems in the ROM, give them back to the community so they can also be used in other ROMS.
Click to expand...
Click to collapse
yes ofc i will.
Is there Host-Driver in the kernel included ?
I am searching developers for Advent Vega device : http://remics.bennz.eu
If you have interests to join Remics-Team pm me!

Vlad87do said:
yes ofc i will.
Is there Host-Driver in the kernel included ?
I am searching developers for Advent Vega device : http://remics.bennz.eu
If you have interests to join Remics-Team pm me!
Click to expand...
Click to collapse
If you mean USB host... Yes it is... On my github there are the sources of the 3.1.10 kernel (based on the rel-15r7 version of nvidia) with the patches ejtagle made. But they are not up to date yet.
As soon as i have time i have to clean up the lunch target of beta1 and do a commit on github. Then you can fork from there and build a version for yourself. If you use the manifest file for vegabean you also get the modifications made to the framework, wpa_supplicant etc to make it all work.
See https://github.com/scanno
Again do not use it yet because they are not up to beta 1.
Thanks for the offer, but i do not have time to do a lot of work and join a development team. For the development of roms for the advent vega i would prefer and suggest that you and the Remics team go to the modaco forum and join the kernel development thread and join the efforts.
This way we have more changes of getting a very good base and from there make ROMS. The more roms to choose from, the better for the people using an advent vega.

Thx for answere, but i dont will compile it , i will use the ready zip file and edit it.
I am not a kernel-developer
thats why i asked you about team

Vlad87do said:
Thx for answere, but i dont will compile it , i will use the ready zip file and edit it.
I am not a kernel-developer
thats why i asked you about team
Click to expand...
Click to collapse
Ok... but again all help is welcome, but you know that. Besides kernel development is done by EJtagle and not by me. He reversed engineerd most of the device specific vega stuff.
Also... /system/lib, /system/framework, /system/usr, /system/app are squashfs filesystems. To access the files in there you have to unsquash them.

do you can tell me programm on windows how to unsquash and again to squash after editing ?

Vlad87do said:
do you can tell me programm on windows how to unsquash and again to squash after editing ?
Click to expand...
Click to collapse
Sorry... I am using Linux and it is available in the repository there. On windows I really do not know. You could Google to see if there are any hits on mksquashfs and unsquashfs. That are the tools used on Linux.
You will need to find a version that supports XZ ( LZMA2) compression. That is the compression algorithm used in vegabean.
This is needed because otherwise the ROM does not fit in the /system partition.

very nice!
7zip can do it under windows - unpack

[ROM]DoubleX-JRO03D ota stock/rooted/deodex/bettery%etc..

Base On stock otaJB4.1.1 JRO03D for Nexus7
Didnt sign this zip,before flash,check Ur reovery sign Verify switch off
Cause I'm chinese,sorry about my English
chinese user may go gfan,same post in chinese
=============Features/log=============
What's works：
Google Now (Seems offline voicedata not support nexus s now) only work in N7&GalaxyNexus
Every thing works.
=======================================
*1 deodex/zipalign
*2 busybox
*3 rooted by superSU(Chainfire)
*4 bettery% ，mostly like this
*5 Advanced Power Management (1reboot 2reboot to recovery ，long press recovery to BLmode)
*6 Camera join，works fine，(MODACO)
*7 Volume button wake up
*8 USBdebugging works fine
including full google services,but books/video/etc...not support my location,just download them from google play,that's easy
If anyone wanna disable the Nvbar,go check my app fullscreen toggle
This app madefor galaxy nexus,also support Nexus7
==========Download JB4.1.1 JRO03D =============
N7-Stock-OTA-rooted-deodex-zipaling-JRO03D.zip - 233.80 MB

Thanks for this. I'll give it a flash and let you know how it goes. Also, I think you're English is pretty good!:good:

Can I flash this ROM?
I unlock bootloader, flash clockworkmod and made root in my nexus 7, can I make OTA update to 4.1.1 or is better flash this rom in recovery clockworkmod?
What is the boot.img file?
My state is in the fallowing:
* BOOTLOADER *
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - 015d24a424042006
SIGNING - not defined yet
LOCK STATE - UNLOCKED
* SYSTEM *
Modelo: Nexus 7
Versão do Android: 4.1
Versão do Kernel: 3.1.10-g55edff4
Número da compilação: JRN84D

if. ota ,you need unroot first
Sent from my GT-P1000 using xda premium

What is the boot.img file?
What is the boot.img file?

kernel
Sent from my GT-P1000 using xda premium

Hold on here, PLEASE !!!
The boot.img is not the Kernel, they are very different and separate.
The boot.img contains the instruction set and fixed files the computers needs to start, bootup this then calls the kernel after it is done.
When you update a kernel you are NOT UPDATING THE boot.img unless the developer has included it in the package.
RED OR BLUE YOU CHOOSE !!!

Angst said:
Hold on here, PLEASE !!!
The boot.img is not the Kernel, they are very different and separate.
The boot.img contains the instruction set and fixed files the computers needs to start, bootup this then calls the kernel after it is done.
When you update a kernel you are NOT UPDATING THE boot.img unless the developer has included it in the package.
RED OR BLUE YOU CHOOSE !!!
Click to expand...
Click to collapse
I can't tell if you're trolling or don't know but the boot.img is the kernel. u wanna check? go look in the zip of the Trinity kernel b4 u flash.its boot.img..same with the Franco kernel or any other kernels.

examples of this can be seen with grub or lilo (linux bootloaders).
Hope this has cleared this up.
RED OR BLUE YOU CHOOSE !!!

Boot.img contains the kernel, believe the OP was just using that ad a shorthand explanation.
But the boot.img does indeed contain more than that. When unpacked it has all of the init.rc files and other essential system operations. If you build your own kernel, you can pack the boot.img and replace the kernel with your own newly made zimage.

<del>

Angst said:
Hold on here, PLEASE !!!
The boot.img is not the Kernel, they are very different and separate.
The boot.img contains the instruction set and fixed files the computers needs to start, bootup this then calls the kernel after it is done.
When you update a kernel you are NOT UPDATING THE boot.img unless the developer has included it in the package.
RED OR BLUE YOU CHOOSE !!!
Click to expand...
Click to collapse
Put the zImage from boot.img in your pipe.

This ROM won't even boot for me, which is really weird. Anybody else have that issue?

test on cwm6.1.0
Sent from my Galaxy Nexus using xda premium

[RECOVERY] Custom Recoveries for Galaxy R

Hello everybody!
Yesterday, I collected my previous recoveries, updated them and built a new one (TWRP) too. I made CWM-flashable and Odin-flashable packages too.
CWM v4.0.0.2: (Thanks to The-Droidster for the recovery! )
- This is the first ever custom recovery for the Galaxy R.
- It has all the nice CWM features.
- You can restore ICS with this.
- It has no known bugs. Everybody used it as a starting point.
- What I changed:
- Removed the /lib/modules directory. --> 0,1MB size decrease.
- Enabled button backlight.
- Key layout: Scrolling: Volume up+down, Selecting: Home key, Going Back: Power+Back button. (Menu key doesn't do anything.)
CWM: http://www.mediafire.com/download.php?71ynk9btw7euocr
ODIN: http://www.mediafire.com/download.php?iczq8xed26ohakw
CWM v5.5.0.4:
- Built from the latest CM9 sources.
- It has all the nice CWM features.
- It can restore v4 backups (you can restore ICS with this too).
- Very stable!
- It has no known bugs yet (Lot of users have been using it and no bugs have been reported).
- Toggle feature is disabled! (I find it really annoying and it doesn't make real sense for a recovery to lock the screen.)
- Key layout: Scrolling: Volume up+down, Selecting: Home key, Going Back: Power+Back button. (Menu key doesn't do anything.)
CWM: http://www.mediafire.com/download.php?98c1smq7nk4485d
ODIN: http://www.mediafire.com/download.php?c7qbjaqwgpnbr9w
CWM v6.0.3.2:
- Built from the latest CM10.1 sources.
- It has all the nice CWM features.
- It can restore v4 backups (you can restore ICS with this too).
- Key layout: Scrolling: Volume up+down, Selecting: Home key, Going Back: Power+Back button. (Menu key doesn't do anything.)
- Known issues: ADB Sideload
CWM: http://www.mediafire.com/download/7xyevjf32fixf3a/CWMv6.0.3.2_CWM.zip
ODIN: http://www.mediafire.com/download/oksv1o2hu63gohi/CWMv6.0.3.2_ODIN.tar
CWM v6.0.1.5 Touch:
- Built using the online builder at http://builder.clockworkmod.com
- It has all the nice CWM features.
- It can restore v4 backups (you can restore ICS with this too).
- Key layout: Scrolling up: Volume up or home button, Scrolling down: Volume down or menu button, Selecting: Power button, Going back: Back button. (This is the default layout and cannot be changed.)
- The touch responsiveness is a little lazy. You have to wait some seconds before it starts working. (The online builder says it needs an ICS kernel for the touch version. We use the CM10 kernel (based on stock ICS one), but it's still lazy.)
CWM: http://www.mediafire.com/download.php?jz24eugrrr988f2
ODIN: http://www.mediafire.com/download.php?6vju9tlf9byeufe
TWRP v2.5.0.0: (Thanks to 'cooleagle' for the tip! )
- Built from the latest TWRP and CM10.1 sources.
- It has a lot of nice features, more than CWM does.
(For example:
- on-screen keyboard -> custom backup names
- built-in file manager
- built-in terminal)
- It has a fully touch-driven and very intuitive interface.
- The touch responsiveness is a little lazy. You have to wait some seconds before it starts working. (The online builder says it needs an ICS kernel for the touch version. We use the CM10.1 kernel (based on stock ICS one), but it's still lazy.)
Note: Backups of TWRP are said not to be compatible with those of CWM. For everything to work well, I recommend that you create a TWRP backup too before modding.
CWM: http://www.mediafire.com/download/8ibammwrtwrwo3d/TWRPv2.5.0.0_CWM.zip
ODIN: http://www.mediafire.com/download/pjxp5xhi96gtbvb/TWRPv2.5.0.0_ODIN.tar
PhilZ v5.06.6: (Thanks to Tha TechnoCrat for the tip! )
- Built from the latest PhilZ and CM10.1 sources.
- It has a lot of nice features, more than CWM does. Check here: http://forum.xda-developers.com/showthread.php?t=2201860
- Based on CWMv6.0.3.2
- Known issues: ADB Sideload
CWM: http://www.mediafire.com/download/4qz1g86oncn4foq/PhilZv5.06.6_CWM.zip
ODIN: http://www.mediafire.com/download/ixlxkh87s2lxbp9/PhilZv5.06.6_ODIN.tar
Stock GB recovery (XWLA4): (Thanks to xlm13x for this! )
- Use this if you want to return to the stock version.
CWM: http://www.mediafire.com/download.php?di4e3ms3qrxuapy
ODIN: http://www.mediafire.com/download.php?i4a1t7ntavvguu7
Stock ICS recovery (XXLQ7): (Thanks to xlm13x for this! )
- Use this if you want to return to the stock version.
CWM: http://www.mediafire.com/download.php?kg58rxmlnxkpkqv
ODIN: http://www.mediafire.com/download.php?pjn87j4fyjs34vt
If you want to install a custom recovery for the first time, you always have to start with an Odin-flashable package first. Flashing a recovery with Odin doesn't increase the download counter!
Tutorial (Flashing with Odin):
Please refer to the following thread (This is very detailed and good in my opinion): http://forum.xda-developers.com/showthread.php?t=1406664
Choose a downloaded TAR file (ODIN-flashable) for PDA option.
Tutorial (Flashing with CWM):
Note: This only works if you have already flashed CWM with Odin.
1: Reboot into recovery mode. Do this with a custom rom or by powering on your phone and pushing Volume UP+Home button simultaneously while the Samsung boot logo appears (you have to be fast).
2: Select 'Install zip from sdcard' menu.
3: Select 'Choose zip from sdcard' menu (or if you want to flash something from your internal sdcard, select 'Choose zip from internal sdcard' menu.) Note: On CWM v4.0.0.2, there isn't any separate menu for internal sdcard. It shows internal sdcard by default. External sdcard is mounted under the external_sd folder on the internal sdcard.
4: Navigate to the file you want and choose it.
5: Choose 'yes'.
6: Wait for it to finish and you're done.
Changelog:
08 July 2012: Initial release of v5.5.0.4 in old thread
09 July 2012: Added CWMv6.0.0.0 Touch (alpha)
17 July 2012: Added CWMv6.0.0.3
18 August 2012: New thread (this) created. CWMv5.5.0.4, CWMv6.0.1.1, CWMv6.0.1.1 Touch and TWRPv2.2.1.4 added.
30 August 2012: Modified CWMv4.0.0.2 (touchkey backlight, some init tweaks and smaller image) added.
2 September 2012: Stock GB (XWLA4) and ICS (XXLQ7) recoveries added.
10 November 2012: CWMv4.0.0.2 and CWMv5.5.0.4 reuploaded. CWMv6.0.1.5, CWMv6.0.1.5 Touch and TWRPv2.3.1.1 with new CM10 kernel added.
14 June 2013: CWMv6.0.3.2 and TWRPv2.5.0.0 added
16 June 2013: CWMv6.0.3.2 and TWRPv2.5.0.0 with USB Mass Storage fix updated, PhilZv5.06.6 added
Every custom modification to devices have risks. Flash these at your own risk!
Have fun and enjoy!

Dude, you're awesome
Sent from my Galaxy Nexus using xda app-developers app

Man thanks. you are the one who making Galaxy R known to the world. thanks again:angel:

wow you are rocking buddy :good:, thank's a lot just now flashed TWRP and its rocking........

Hey guys, sorry for the links being disabled. I've just received a mail about it. Dropbox thinks the links are generating too much traffic. Thank you for downloading so much! I'll reupload everything to somewhere else asap.
Sent from my GT-I9103

Adam77Root said:
Hey guys, sorry for the links being disabled. I've just received a mail about it. Dropbox thinks the links are generating too much traffic. Thank you for downloading so much! I'll reupload everything to somewhere else asap.
Sent from my GT-I9103
Click to expand...
Click to collapse
Thats means u r world famous buddy.. Bt we are waiting.. If someone need that one then we will ask in PM.
Sent from my GT-I9103 using Tapatalk 2

I think this should be stickied!:good:

The-Droidster said:
I think this should be stickied!:good:
Click to expand...
Click to collapse
Me too :good:

Update the OP!
@Adam...Now that this thread has been stickied it is best that you also add the attached CWM recovery v4.0.0.2 to the OP. This will make it a one stop thread for all recoveries for Galaxy R. Also please include a short tut about flashing these recoveries through recovery and ODIN separately!(With screenies if possible!)
One more thing, the attached v4 CWM recovery is ODIN flashable. See if u can make a CWM flashable version out of it as you did for other recoveries!
Thnx:good:

The-Droidster said:
@Adam...Now that this thread has been stickied it is best that you also add the attached CWM recovery v4.0.0.2 to the OP. This will make it a one stop thread for all recoveries for Galaxy R. Also please include a short tut about flashing these recoveries through recovery and ODIN separately!(With screenies if possible!)
One more thing, the attached v4 CWM recovery is ODIN flashable. See if u can make a CWM flashable version out of it as you did for other recoveries!
Thnx:good:
Click to expand...
Click to collapse
Thanks for the idea! I'll do it on tuesday (I'll arrive home then.) as well as I'll reupload everything to somewhere else as Dropbox has limits with file downloads. I may also add a flashable stock recovery if somebody wants to revert only the recovery.
Sent from my GT-I9103

Adam77Root said:
Thanks for the idea! I'll do it on tuesday (I'll arrive home then.) as well as I'll reupload everything to somewhere else as Dropbox has limits with file downloads. I may also add a flashable stock recovery if somebody wants to revert only the recovery.
Sent from my GT-I9103
Click to expand...
Click to collapse
Along with the stock recoveries of ICS & GB CWM flashable zips kindly try to add a Unroot CWM zip (ICS / GB separate if needed) so that everyone can just flash that zip & get unrooted if in any circumstances they can't flash the stock ROM via a USB if the port is damaged. This will serve as a way for people who have damaged their USB port to get unrooted, flash stock recovery & claim warranty for the damaged USB port.
pankaj88 has already made one but it doesn't remove the busybox so if possible try to make a zip which removes all the traces of the a rooted stock ROM.
You could start a new thread for it if you think it's needed as it is pretty useful & important.
Cheers !

Adam Now we are having ICS, so is it possible to rectify the touch Recovery bug (little lazy for few seconds) please.....
oops sorry i haven't read the OP fully, Ok now i understood because of kernel size you are not able to do it.....

UPDATE:
I updated the links, added CWM v4.0.0.2 and a short tutorial.
I'll get stock GB and ICS recoveries and add them in the following days (It depends on when I get them.)

If u want I can send u stock recovery images.
Sent from my Galaxy Royale using Tapatalk 2.

xlm13x said:
If u want I can send u stock recovery images.
Sent from my Galaxy Royale using Tapatalk 2.
Click to expand...
Click to collapse
It'd be really great! I think a GB and an ICS one is enough. Thanks in advance!

ICS Stock Recovery: http://d-h.st/Zgw
(extracted from XXLQ7)
GB Stock Recovery: http://d-h.st/M1R
(extracted from XWLA4)

This is great since I need to repack the stock firmware with CWM now just to get rid of the emmc bug.

xlm13x said:
ICS Stock Recovery: http://d-h.st/Zgw
(extracted from XXLQ7)
GB Stock Recovery: http://d-h.st/M1R
(extracted from XWLA4)
Click to expand...
Click to collapse
Added them to the OP.

can we flash through stock recovery
Sent from my GT-I9103 using xda app-developers app

kartiknnn said:
can we flash through stock recovery
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
You cannot flash through stock recovery right now. Flash a one with Odin first, it'll not increase the binary counter.
Sent from my GT-I9103

[NON-DEV][TOOL][AuTORAMDISK EXCHANGE PROJECT ALPHA][NO PC/LINUX]

AUTORAMDISK™ EXCHANGE PROJECT alpha™
『Moved by touch™』Inc.
In association with
Google Nose beta™
Presents
AUTORAMDISK™ EXCHANGE PROJECT alpha™
Current version: 0.0.0.0.072 Alpha
Created with Es explorer 1.6
Created on HTC explorer Pico a310e
Intro:
It's a common experience for newbies , when a new kernel is released by developers for a particular Rom and we want it for our Rom,but just can't wait for someone to change the ramdisk. For those, this is a noob friendly guide to change your ramdisk. And also, to make a universal zip for new kernel, so that no separate kernel zips for cm9,10,aokp exist.
Prerequisites:
Files:
New kernel boot.img and modules
Zip below
Software:
Android 2.3+ rooted
cwm 5+/twrp any other recovery with dump_image binary
Hardware:
Any Android smartphone
Features:
No PC/Linux needed
No different zips needed for different roms ~universal zip[One kernel-one zip project]
Credits:
trevd,rd for helping me along the way and for arm executable binaries .
So, a huge thanks to him.
Xda university
Procedure:
Short version:
Just add the new boot image and modules to generic kernel.zip and Flash on any Rom
Long version:
1.Download the generic kernel below
2. Open it with Es explorer 1.6 app
3. Select all and extract it into generic kernel folder
4. Download your favorite kernel.zip
5. Unzip your favorite kernel.zip into kernel folder
6. Copy boot.img from kernel folder to generic kernel folder
7. Copy modules present in /system/lib/modules in kernel folder and put it in /system/lib/modules in generic kernel folder
8. Now zip up your generic kernel folder and Flash
9. Voila
10. New kernel on any Rom.
11. So, is that easy /what?
Bugs and conditions
Even though this project is in alpha stage, if your Rom doesn't boot, blame the new kernel and your script first.
1. This is a simple method to change ramdisk and it doesn't work ,if you need anything more than that.
The binaries can also be used to open ramdisk and probably kernel as well using terminal emulator on your phone. If you face something unable to do on phone, go here for full PC workout
2. Essentially sense4 kernels cannot be used with this project to make it cm kernels,since it almost always need more work than just ramdisk changing
3. You need a working kernel present in boot partition. Wiping your boot and flashing will not work. It needs ramdisk from your phone and only updates the kernel part.
4. Does it work on other phones?
Yes. It bases itself on update script used. So, change update binary to suit your device
Try to change kernel address in the command for mkimg binary to make it work on other phones.
4.2 Does this mean that I can Flash kernel from any other phone to my Pico?
No. You can't. This only means you can Flash any other kernel made for other roms and your Pico to your Rom and Pico only.
4.3 Not tested fully guys.
Tired of 15 to 20 flashings to make it work. Test and try. I only tested aokp jb bhargz16`s kernel #1 on cm10b6 with twrp.
Reuse it,and try not to edit ui print and sleep parts
5. If it doesn't work, copy recovery log to SDcard and post here.
Original binaries from here
http://forum.xda-developers.com/showthread.php?p=36931024
(1.not the same script here~that is used to update ramdisk. This is used to update kernel and modified usage of binary to suit Pico
2. Without the binaries there, it would have been impossible. Don't forget to thank him. )

Reserved
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E.
If I haven't given you link, it's above. Just click it

Reserved 2
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E.
If I haven't given you link, it's above. Just click it

One more
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E.
If I haven't given you link, it's above. Just click it

All I can say is an ingenious piece of work bro. Nice use of the updaterscripts and good and simple way to swap ramdisks without much hassles.
:good: :good:
All the best !

akshat.shenoy said:
How does this work ?
All the best !
Click to expand...
Click to collapse
It's ramdisk changer... uses arm executable binaries from trevd to unpack and remake boot.îmg to change ramdisk.
Literally, it changes only kernel and doesn't touch ramdisk and so, we can use universal zips for cm7,9, 10,aokp.
That's the aim..
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E.
If I haven't given you link, it's above. Just click it

New poll added. Just fill up the no poll, if you don't like it.

Thread cleaned
Cleaned thread of some nonsense. Some ppl have to learn the hard way to not post spam or OT obviously

Deleted: Never mind

ptcpayme said:
New poll added. Just fill up the no poll, if you don't like it.
Click to expand...
Click to collapse
so that means now i can flash any kernel from any phone to my pico?? If not,plz explain.
THnx.

salil.bajaj said:
so that means now i can flash any kernel from any phone to my pico?? If not,plz explain.
THnx.
Click to expand...
Click to collapse
Without a kernel , we cannot use our phone. Learn more about " Kernels "
NOTE : Kernel == Boot.img ( Actual kernel is the zImage.. but never mind)
Yes we have to flash a kernel everytime we flash a ROM on our phone. It is simplified for our phone cause it gets flashed by itself ( thru the updater script )... And you could flash a kernel from our phone even normally thru
Code:
fastboot flash boot boot.img
What this tool does swaps Ramdisks of 2 kernels . Why is that useful ?
Cause then it makes one kernel of a particular ROM compatible with another ROM.
And I just forgot, this isnt the Q and A.

Got ya man!! Now this is really awesome work u hv cme up with!! :thumbup:
Sent from my HTC Explorer using xda premium

akshat.shenoy said:
Without a kernel , we cannot use our phone. Learn more about " Kernels "
NOTE : Kernel == Boot.img ( Actual kernel is the zImage.. but never mind)
Yes we have to flash a kernel everytime we flash a ROM on our phone. It is simplified for our phone cause it gets flashed by itself ( thru the updater script )... And you could flash a kernel from our phone even normally thru
Code:
fastboot flash boot boot.img
What this tool does swaps Ramdisks of 2 kernels . Why is that useful ?
Cause then it makes one kernel of a particular ROM compatible with another ROM.
And I just forgot, this isnt the Q and A.
Click to expand...
Click to collapse
Thanks for sharing usefull Information...........!!

Hey @BANNED i tried today and its working great. And nice updater-script troll.
Sent from my HTC Explorer A310e using xda app-developers app

thank you for your guide.

[MOD][07 August] MultiROM v32a

Code:
#include
/*
* Your warranty is now void.
*
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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 laugh at you.
*
*/
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy ACE 3 LTE. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from external SD card. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the image above. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from Internal memory and MicroSD Card (non tested)
Warning!
This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong (even if never happened until now) and you will have to flash stock firmware with Odin. Make backups. Always.
Installation, Note: Only manual installation is supported, because this mod is not officially supported.
MultiROM has 3 parts you need to install:
MultiROM
Modified recovery
Patched kernel
Now let's head to the installation. Note: Your primary ROM is recommended to be lollipop, because it doesn't act well as a secondary, due to enforcing selinux. Although you can use it as secondary, but change it's selinux status. My setup is Lollipop as primary, and KitKat as secondary. Stock ROM was not tested, because I hate it
I spent about 5 days working on this. My head will explode There is a tiny issue. MultiROM boot menu does not show up as it should. That's why we should use the MultiROM manager apk. and switch ROMs from the app.
Attention: The steps are if you use CM-12.1 as primary ROM
Kernel for Stock ROM with kexec-hardboot patch here
Step 1: Install this patched kernel over CM12.1. Or this, if you want OC.
Step 2: Install the modified Multirom Manager apk, I added support for our device
Step 3: Install Multirom
Step 4: Install MultiROM TWRP, via previous TWRP recovery, it can flash images
Step 5: Reboot into new recovery
Step 6: Install CM11, as secondary ROM!!
Step 7: Go to recovery-->Advanced-->MultiRom-->List ROM-->Choose CM11-->Flash Zip. Flash either stock kernel, or oc_kernel. Both include the necessary kexec-hardboot patch. Usually Multirom requires only primary ROM to have the kexec-hardboot patch, but in our case it does not work this way.
Now you are ready to switch ROMs. Ooh, almost forgot. MultiROM boot manager will show up if you connect the phone for offline charging, you will find out what happens on each case. This is the only bug that I can't resolve yet. Although multirom can be used, with this bug.
Code:
Update 20150829: Download everything from this [URL="https://androidfilehost.com/?w=files&flid=37974"]folder[/URL]
Kernel will be updated when ROM is built
Changelog: Re-implemented kexec hardboot and fixe last_kmsg creation
Video on how to install
Video on how to flash updates
*Thanks Tech Tutorials channel for the videos
NOTE: If secondary ROM does not boot, select Restorecon under multirom
Click to expand...
Click to collapse
Switch ROMs from the MultiRom manager app
NOTICE: I can't guarantee it will work on other variants rather than "R"
To uninstall Multirom simply flash this
You current ROM will not be erased by the installation.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using MicroSD Card
During installation, recovery lets you select install location. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to MicroSD Card takes a bit more, because the external memory is (usually) slower and it needs to create the images. Also boot process is longer, highly depends on card's class. You can find ROMs installed on SD card in the "External" tab in boot menu.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - Add ROM to boot manager
- List ROMs - List installed ROMs and manage them
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - Well, settings
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - Flash ZIP to the ROM, for example GApps
- Add/replace boot.img - Replaces boot.img used by the ROM, this is more like developer option.
Source Code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
CM12.1 stock kernel w/ kexec-hardboot patch- https://github.com/kostoulhs/android_kernel_samsung_msm8930-common/tree/cm-12.1
CM11 stock kernel w/ kexec-hardboot patch- https://github.com/kostoulhs/android_kernel_samsung_msm8930-common/tree/cm-11.0
Stock kernel for stock rom w/ kexec-hardboot patch - https://github.com/kostoulhs/android_kernel_samsung_loganrelte/tree/master
MultiROM device tree - https://github.com/kostoulhs/android_device_samsung_loganreltexx/tree/multirom
Big thanks to Tasssadar for this awesome utility.
Also thanks @Grarak for the melius patch, i was based on it

Reserved

All the zip files listed above(steps 1 and 3) should be installed via TWRP, is that correct?

Levivig said:
All the zip files listed above(steps 1 and 3) should be installed via TWRP, is that correct?
Click to expand...
Click to collapse
Exactly
Sent from my GT-S7275R

This looks great, will defenatly try it. With 4,5 GB free internal memory do you recommend installing rom's on internal or SD ?

F. Dutch said:
This looks great, will defenatly try it. With 4,5 GB free internal memory do you recommend installing rom's on internal or SD ?
Click to expand...
Click to collapse
Installing on internal works. I haven't tried to install on sdcard yet
My setup is Lollipop as primary and KitKat as secondary, installed on internal
Sent from my GT-S7275R

kotzir said:
Installing on internal works. I haven't tried to install on sdcard yet
My setup is Lollipop as primary and KitKat as secondary, installed on internal
Sent from my GT-S7275R
Click to expand...
Click to collapse
Can I Make My Setup Like This ? :
Stock ROM(4.2.2) as primary and Lollipop as secondary , Stock ROM installed on internal , Lollipop ROM installed on SD card .
And my sd card use ext4 partition , is this partition supported ?
This is amazing feature !
Thanks a lot for this great work !
Sent from my GT-S7275R using XDA Free mobile app

zh_eco said:
Can I Make My Setup Like This ? :
Stock ROM(4.2.2) as primary and Lollipop as secondary , Stock ROM installed on internal , Lollipop ROM installed on SD card .
And my sd card use ext4 partition , is this partition supported ?
This is amazing feature !
Thanks a lot for this great work !
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
Multirom works on fat systems on sdcard as fas as I know, see more info about the limitations on the OP. To use stock ROM you need a stock kernel with kexec hardboot patch, I have already patched it, it is also available on my github. I just haven't built it. I can build it although
Edit: Due to the bug, that multirom does not show up on boot, we actually can't install ROMS on Sdcard, they are not visible by MultiRom manager app.
Edit2: stock kernel with kexec-hardboot patch download
Edit3: Trying to make it fully functional
Sent from my GT-S7275R

kotzir said:
Multirom works on fat systems on sdcard as fas as I know, see more info about the limitations on the OP. To use stock ROM you need a stock kernel with kexec hardboot patch, I have already patched it, it is also available on my github. I just haven't built it. I can build it although
Edit: Due to the bug, that multirom does not show up on boot, we actually can't install ROMS on Sdcard, they are not visible by MultiRom manager app.
Edit2: stock kernel with kexec-hardboot patch download
Edit3: Trying to make it fully functional
Sent from my GT-S7275R
Click to expand...
Click to collapse
So I can't install any ROM on the SD card ..
until you fix the bug .. Right ?
Or just we will never can install ROMs on the SD card ?
Sent from my GT-S7275R using XDA Free mobile app

zh_eco said:
So I can't install any ROM on the SD card ..
until you fix the bug .. Right ?
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
you can boot into multirom menu, if the phone is off and you connect it to the charger, so you can experiment a little

kotzir said:
you can boot into multirom menu, if the phone is off and you connect it to the charger, so you can experiment a little
Click to expand...
Click to collapse
So we will stay do this , just if we install a ROM in the SD card .
Or what ?! :|
OK , after flashing the stock kernel with kexec-hardboot patch, I can't flash any other kernel like arasma kernel in my stock ROM(4.2.2) ?
If I can't .. Can you make a kexec-hardboot patch for arasma kernel ?
Here : http://d-h.st/aYr
Or .. Can you make the lollipop kernel (1.7GHz) work on the stock ROM ?
Sent from my GT-S7275R using XDA Free mobile app

Its not my problem if I'm always not understand.
Its my brain problem ..
Just answer me ..
Why you always Ignore me ?
I'm just asking you , you can tell me oh I'm sorry ! I can't .. Just like this and I will accept .

zh_eco said:
Its not my problem if I'm always not understand.
Its my brain problem ..
Just answer me ..
Why you always Ignore me ?
I'm just asking you , you can tell me oh I'm sorry ! I can't .. Just like this and I will accept .
Click to expand...
Click to collapse
Mate I want to answer you and I do the best I can. Now I am working to make multirom fully functional, what don't you understand? The same time I am studying. It is pretty hard for me. The thing you ask me requires fully functional multirom. Enjoy it as it is, if you can and wait for the fix. Thanks
*Also, I will modify the stock kernel, as the others

kotzir said:
Mate I want to answer you and I do the best I can. Now I am working to make multirom fully functional, what don't you understand? The same time I am studying. It is pretty hard for me. The thing you ask me requires fully functional multirom. Enjoy it as it is, if you can and wait for the fix. Thanks
*Also, I will modify the stock kernel, as the others
Click to expand...
Click to collapse
:good::good: Nice Work Man

zh_eco said:
Can I Make My Setup Like This ? :
...my sd card use ext4 partition , is this partition supported ?
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
May I ask why you do this?
MTP practically destroys any real world benefit that EXT could possibly offer you, and if you use UMS et al you'll hit permissions issues with the media that completely ruin its ability to function as removable storage unless every single one of the systems it touches only has a single user or you carefully craft the system environment so that the user always has the same UID.
It's just weird to use a journalled filesystem with access permissions as removable storage. Either MTP destroys any gains you might possibly get, or UMS makes it impossible to access the contents of the volume on ~99% of all the systems you'll ever encounter in the wild. Ever wondered why you never see external storage volumes with permission based filesystems? This is why. It's largely silly.

I tried to restore a backup of stock rom, i want to try if it works and maybe use it as 3rd rom but CWM says .android_secure.vfat.tar and .Android_secure.vfat.Tar.a are missing does anyone know what it means and how to fix it. Does CWM version matter? Can TWRP instal backups made by CWM?

F. Dutch said:
I tried to restore a backup of stock rom, i want to try if it works and maybe use it as 3rd rom but CWM says .android_secure.vfat.tar and .Android_secure.vfat.Tar.a are missing does anyone know what it means and how to fix it. Does CWM version matter? Can TWRP instal backups made by CWM?
Click to expand...
Click to collapse
To use it with stock ROM, you need to install a stock kernel with hardboot patch, there is one in the OP. TWRP can't restore backups from CWM, different format of backup. I don't see any reason of using CWM, since there is TWRP.
Sent from my GT-S7275R

kotzir said:
To use it with stock ROM, you need to install a stock kernel with hardboot patch, there is one in the OP. TWRP can't restore backups from CWM, different format of backup. I don't see any reason of using CWM, since there is TWRP.
Sent from my GT-S7275R
Click to expand...
Click to collapse
Thanks but the only backups i have of stock are made with CWM. When i try to restore it says .Android_secure.vfat.Tar and .Android_secure.vfat.Tar.a are missing so i can't restore and make a backup with TWRP. Found some info about it and trying tot make it work right now.

kotzir said:
Video on how to install
Video on how to flash updates
*Thanks Tech Tutorials channel for the videos
Click to expand...
Click to collapse
Thank U Very Much @kotzir For Adding My Videos To "OP"

Small update, check OP