Related
This is a new thread for kernel ports of CyanogenMod 4.1.99 and greater versions only.
This kernel port will now work on any EBI1 kernel: this includes both the HTC Magic 32a and Rogers Dream.
If you wish to port earlier versions of CyanogenMod - please see Bcrook's thread. Bcrook has asked me to start a new thread for 4.1.99+ and ongoing versions as I've been doing the recent ports for it.
This is a kernel port from the 32b ION/HTC Magic/mytouch3g version of CyanogenMod that should work on any EBI1 (32a/rogers dream) device.
In most cases our hardware is identical, but we have twice the memory and so the kernel and wlan modules need to be rebuilt.
The steps for installing CyanogenMod on a 32a are much the same and are listed below for your convenience:
I have tested these steps personally, as have a number of people:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
NEW INSTALL (ie. never installed CM 4.1.99 or greater before):
Download HTC ADP 1.6 DRC83
(http://www.androidspin.com/downloads...ooted_base.zip)
Download CyanogenMod 4.2.4
(http://n0rp.chemlab.org/android/update-cm-4.2.4-signed.zip)
Download the Kernel Port file (see below)
Copy all three .zip files to your SD and reboot in recovery mode (press Home+Power at the same time or fastboot into your recovery)
Do a "Wipe data/factory reset"
Do a "Wipe SD: ext partition" ** (see below)
(it is recommended to wipe your Apps2SD partition for this release)
Apply Zip: HTC_ADP_1.6_DRC83_rooted_base.zip
Apply Zip: update-cm-4.2.4-signed.zip
Apply Kernel Port Zip: rad-4.xxxx.zip or bc-4.xxxx.zip
Reboot
Either grab some popcorn and watch adb lolcat as it goes past, or go do something else.. this might take a while
UPGRADE INSTALL (ie. already installed 4.1.99 or greater):
Download latest CyanogenMod update (now 4.2.4)
(http://n0rp.chemlab.org/android/update-cm-4.2.4-signed.zip)
Download the associated Kernel Port file (see below)
Copy both .zip files to your SD and reboot in recovery mode (press Home+Power at the same time or fastboot into your recovery)
Apply Zip: update-cm-4.2.4-signed.zip
Apply Kernel Port Zip: rad-4.xxxx.zip or bc-4.xxxx.zip
Reboot
Either grab some popcorn and watch adb lolcat as it goes past, or go do something else.. this might take a while
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The following Kernel Ports are available:
CyanogenMod 4.2.4 EBI1 kernel for 32a/Rogers Dream (recommended) (give thanks to bcrook for porting this one!)
Download: http://www.briancrook.ca/magic/bc-4.2.4-ebi1-signed.zip
md5: 174dd7403052f9173660b817232b47e6
Older kernel ports:
CyanogenMod 4.2.3.1 EBI1 kernel for 32a/Rogers Dream (now with USB tethering!)
http://fdsfiles.com/temp/rad-4.2.3.1-EBI1.zip
(md5sum: 0d52bc8986e11c0382b3f6336d6d71d4)
CyanogenMod 4.2.2 EBI1 kernel for 32a/Rogers Dream with no BFS
http://fdsfiles.com/temp/rad-4.2.2-EBI1.zip
(md5sum: 38c52bedceef516a03bd07e034ae9b13)
CyanogenMod 4.2.1 EBI1 kernel with no BFS
http://fdsfiles.com/temp/rad-4.2.1-EBI1.zip
(md5sum: 39c536b93425f8c1f94bc79cc97b9baf)
CyanogenMod 4.2 EBI1 kernel with BFS 304
http://fdsfiles.com/temp/rad-4.2-bfs-ebi1.zip
(md5sum: 8875e2e8a25d394455f2d4864d9c6c67)
CyanogenMod 4.1.9999 EBI1 kernel with BFS 304 (now with full EBI1 support and fixed ramdisk)
http://fdsfiles.com/temp/rad-cm4.1.9999-EBI1.zip
(md5sum: 48e4d30e81c0b531e00dde05d1108416)
CyanogenMod 4.1.9999 with BFS 304 (Hacked - doesn't work for Rogers Dream)
http://fdsfiles.com/temp/rad-4.1.9999-32a-bfs304.zip
(md5sum: 54c225da975a08ae8cf7e006e97caf41 )
CyanogenMod 4.1.99 and 4.1.999 with BFS 303 (N.B. this port file will work fine with both releases - Cyanogen's just catching up to me
http://fdsfiles.com/temp/rad-4.1.99-32a-bfs303.zip
(md5sum: ced37f39fd419a4b11fa3f64eb7f93e9 )
CyanogenMod 4.1.99 with BFS 302:
http://fdsfiles.com/temp/rad-4.1.99-32a-bfs302v3.zip
(md5sum: 2b33a2d57b1497c167e50dfbec23953f )
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Please Note: I have started including AudioPara4.csv in my package once more as it does seem to be needed.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
HTC IME: Hero Keyboard
For those who want the HTC IME back you need to download HTC_IME.apk and Clicker.apk from here:
http://n0rp.chemlab.org/android/apps
then either ADB install them or use an app like ASTRO to install them.
Do not use any other versions of HTC_IME - they will force-close.
Then go to Menu->Settings->Locale and Text->Touch Input and activate for it to appear, then long press on a text box to switch to it by default.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Special thanks go to Cyanogen, bcrook, TigerTael, Amon_RA, jerpelea, hakyuro, TheStrider, redglasses, and all the people who have contributed towards making these roms possible for us.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
** After a bit of inspection it looks like no 32a recovery rom has this option at present.
if your recovery rom doesn't have the option 'Wipe SD: ext' then you can duplicate it by doing (while in your recovery rom):
$ adb shell
# mount /system/sd
# rm -rf /system/sd/*
# unmount /system/sd
Click to expand...
Click to collapse
Basically this is done to make sure you have no previous apps, nothing to foul things up and you're truly starting from scratch.
[Reserved for future use]
Hello,I flashed my HTC Magic(32A) using signed-google_ion-ota-14721.zip, which I download here:http://developer.htc.com/google-io-device.html.
Then,My phone can't boot into normal mode and can't boot into recovery mode too.
Do you known how to repair it?
Thanks~support you~!
imake said:
Hello,I flashed my HTC Magic(32A) using signed-google_ion-ota-14721.zip, which I download here:http://developer.htc.com/google-io-device.html.
Then,My phone can't boot into normal mode and can't boot into recovery mode too.
Do you known how to repair it?
Click to expand...
Click to collapse
How did you try to reboot in recovery mode? Have you tried using fastboot? You don't have to write the recovery image to the phone, you can use fastboot.
Basically you turn off the phone, then press the Back+Turn on keys and you should be in fastboot.
Then at the computer cd into the directory where you have the recovery image then type:
fastboot boot <recovery.img>
(replace recovery.img with the actual recovery image name; make sure the phone is connected via usb to the computer and adb "sees" it, check with adb devices).
Then you should be able to follow the procedure as described in the first post.
If you didn't copy all the zips on the memory card first, you need to take out the memory card and use a card reader to copy them first.
Hope this helps!
S.
siancu said:
How did you try to reboot in recovery mode? Have you tried using fastboot? You don't have to write the recovery image to the phone, you can use fastboot.
Basically you turn off the phone, then press the Back+Turn on keys and you should be in fastboot.
Then at the computer cd into the directory where you have the recovery image then type:
fastboot boot <recovery.img>
(replace recovery.img with the actual recovery image name; make sure the phone is connected via usb to the computer and adb "sees" it, check with adb devices).
Then you should be able to follow the procedure as described in the first post.
If you didn't copy all the zips on the memory card first, you need to take out the memory card and use a card reader to copy them first.
Hope this helps!
S.
Click to expand...
Click to collapse
Hi,thanks.But when I press the Back+Turn on keys, my phone boot into a htc magic screen,not the fastboot mode.
Do we also need the two extra reboots?
9- Once at home screen.....Reboot 2 more times. This will mix everything together, just like making soup =) You will get the true speed of this rom.
Click to expand...
Click to collapse
Thank's Radix999....great work's !!!!
BUGabundo said:
Do we also need the two extra reboots?
Click to expand...
Click to collapse
I would say yes as this thread only adds the 32A kernel and I doubt the requirement of booting 2 more times has anything to do with the kernel.
On the other hand, I've rebooted actually more than 2 times (for other reasons) and it doesn't seem faster to me. Too bad cyanogen didn't say what exactly will/should be faster so that we can test.
so my journey is finally complete.
in the past 24 hours since the update came out, i have managed to :
1. brick my phone
2. sent it for warranty repairs
3. live (like an undead) for a bit without my beloved 32A magic
4. gotten back my 32A magic
5. figured out how to restore my old nandroid of 4.1.11.1 while still keeping the perfect SPL (i am still on .0010)
6. gotten 4.1.99 to work without wiping (still lost my my HTC_IME dictionary which is a minor thorn is the behind)
7. will live happily ever after.
so thanks for the people who figured out what to do. what are the steps.
mad mad props goes out to Radix999 for the porting files.
now for my lockscreen and black status bar
What about all the google programs, this might be a stupid question. Think i have read somewhere online that we who have google programs need to take a backup of those or else they want be "transfered" to the 4.1.99 ROM. Am i right or just me that haven't understood anything?
Per
str4vag said:
so my journey is finally complete.
in the past 24 hours since the update came out, i have managed to :
1. brick my phone
Click to expand...
Click to collapse
how the heck did u do that?
did u get that ION roms that applied a radio update?
perevers said:
What about all the google programs, this might be a stupid question. Think i have read somewhere online that we who have google programs need to take a backup of those or else they want be "transfered" to the 4.1.99 ROM. Am i right or just me that haven't understood anything?
Per
Click to expand...
Click to collapse
cyanogenmod installer extracts it from the oficial ROM, thats why you need to install that 1st!
BUGabundo said:
cyanogenmod installer extracts it from the oficial ROM, thats why you need to install that 1st!
Click to expand...
Click to collapse
Ahh, thanks alot
It's all done transparently by Cyanogen's install script.
BUGabundo said:
how the heck did u do that?
did u get that ION roms that applied a radio update?
Click to expand...
Click to collapse
yea..basically that..thank god it was covered by the warranty..
I'm just curious....is there a version of this rom that doesn't require apps2sd (and by extension, doesn't require a partitioned sd card) ?
The reason I ask is since it's for a 32A board, is it really necessary?
Thanks for any info.
Err, I don't think it requires apps2sd. You're right, most 32a users don't need it. It will install automatically should it find the ext partition on the card, but it's not required. I'd be interested to know if otherwise.
DT
Wipe SD and loose Apps?
Radix999 said:
[*]Do a "Wipe data/factory reset" and then a "Wipe SD: ext partition"
(it is recommended to wipe your Apps2SD partition for this release)
Click to expand...
Click to collapse
I understood everything about the instructions for the ROM update except this one.
I have cyanogen's recovery 1.4 and I can't find the Wipe SD: ext partition option. By this you mean that we have to manually wipe the partition on a linux OS or that there's a recovery ROM with this option? If we have to wipe it we will loose our installed apps that we had before, right?
Thanks for your work radix!
To be quite honest, I don't know how to wipe the ext2/3 partition for the Apps2SD users - I'm just using the instructions from the mytouch3g installs and they did recommend any partition you may have.
If you have an Apps2SD partition you'll need to figure it out (you'll probably find you can 'adb shell' in Amon_RA's recovery rom and there's a script for formatting your apps2sd partition somewhere, but you'll need to check with his recovery rom and what's included)
Personally I don't use Apps2SD and never will
And for the record I'm still using Amon_RA's 1.2.0 recovery - never bothered changing as it works fine for me
This project is now discontinued and will recieve no further updates nor support.
First of all, thanks petter (https://github.com/havlenapetr), Czech Samsung Galaxy developer, for idea and source codes.
What do I mean?
You have one ROM in internal memory as usual, and another one in folder on SD card ext partition. You can easily switch between them - just move rom from ext partition to some backup folder.
See guide in second post
How is it done?
Lets look on how android boots - its (roughly) like that:
1. Bootloader - forks between recovery, fastboot and normal boot
2. Linux kernel - Unpacks its initrd, loads drivers and many more things, not important now
3. Init - kernel runs this program, which mounts android partitions, sets correct permissions to files, starts services, and in the end, starts android itself
4. Android - Dunno much about it yet, anyway not important now
So, what we need to do is mount something else than internal memory in init. Init parses & runs simple scripts, which makes it simpler to mount sdcard folders.
We need to add mknod and bind mounting to init binary. Unfortunately, we dont have sources of init modified by LG (that thing is three(!) times larger than init compiled from AOSP, what the hell is in there?!). That is solved by running modified init, which parses "preinit.rc" with mounts and then runs LG init.
Commit: https://github.com/Tasssadar/init/commit/aa3604ca90f5ef9b688fdc2e3cc865aa29a54809
preinit.rc: https://github.com/Tasssadar/init/blob/b4e701e8bc4831fadbefa64be48300139dcc2023/ramdisk/preinit.rc
This would be all, if original LG init would not remount /system and /data from internal memory. Also, nearly every ROM has different init.rc, and wont boot without it.
To solve this, I created "import_boot" command in init, which copies *.rc files and LG init from ramdisk(well, its only folder with these files extracted from ramdisk for now) on sdcard ext partition. This command also puts comments out every line with mount /data, /system or /cache in init.rc file, so LG init wont remount them.
Commit: https://github.com/Tasssadar/init/commit/dc3fa50d65d1221a4fb819d8ee616765ee043e83, https://github.com/Tasssadar/init/commit/f7bc141b1e4b7d214e49d4bb005c71237231436c and https://github.com/Tasssadar/init/commit/1cde6b6a093d4ac1f961e610c5229605bc517b52
Format of ROM on ext partition:
All files from paritions in internal memory copied to sd ext partition with preserved owners and permissions(!).
So, when I copy data, I do "cp -r -p /data/* /sd-ext/multirom/rom/data/" (I suggest to run this via adb shell while in recovery).
Currently, I mount /system, /data and /cache from sdcard. If one or more of these folders does not exist, its equivalent from internal memory is used.
It would be nice to have *.img files from nandroid backups instead of this, but as far as I know, they cant be just mounted.
As for *.rc files, I put them into /sd-ext/multirom/rom/boot folder. I would like to just copy boot.img and extract files in init, but I did not find way to extract it when I have hardly STL usable in init. I'd like to use kernel's internal decompressor, but I dont know how.
Limitations
- Both ROMs must be compatible with one kernel - kernel is already loaded in init
- ROMs must be for same baseband, obviously
- Kernel modules(wifi, for example) of both ROMs must be compatible with one kernel. That can be easily solved by copying modules from one ROM to another, though.
- It will be slower than internal memory.
Integration with recovery
Definitely possible & usefull. This is integration in my modified AmonRa recovery: https://github.com/Tasssadar/Amon-R...mmit/bd0232f7379993c296b0223973b81e8c55dc3ee2
Security risk
/system on sdcard can't be mounted read-only - I'd have to mount whole sdcard read-only. This is possible security hole, but you cant do much without root anyway, because of permissions. And if you have root, it does not matter if its read-only or not.
Conclusion
So, it is possible to have dual-boot. You can use it to develop ROMs(you can directly edit data in /data and /system), as backup ROM when you are testing something in internal memory which does not boot, and you need to call someone or when our devices will be so old that bad blocks in internal memory wont allow us to boot
But, as you can see, It is not something that average user could do, at least not yet. Maybe I could modify recovery to do everything for the user (copy data from /system, /data and /cache, extract *.rc files from boot) and create some flashable ZIPs which would modify the init.
But there are some problems - some ROMs may not be compatible with this and there are multiple recoveries out there, but theres not single one which is only for our phone - both AmonRa and ClockworkMod are developed for wide range of devices. Yes, both of them can be modified, but I doubt they creators would accept such inflexible and device-specific thing.
What do you think, is it worth it?
Tested ROMs (first one is in internal memory, second one is on SDcard)
Working:
Megatron and stock v10a ROM - stock rom is slow
Megatron and devoid #froyo-final - like ten times faster than stock xD
LightRom(2.2.2) and devoid #froyo-final (and vice versa)
Megatron and Megatron - both ROMs can have a2sd
Megatron and Mik's CM7 6.5.8 - since v2
Gingerbread 2.3.4 from Optimus Net and CM7 6.6.1 (thx eduardogouveia for testing)
Stock 2.2.2 and CM7 6.5.8 (thx eduardogouveia for testing) - if you have ext4 partition, you need custom kernel for stock ROM.
.void 2.3.4 and stock V20B (thx diazneoones for testing)
CM7 6.5.8 and .void 2.3.4 (thx diazneoones for testing)
CM7 nightlies and Lupohirp's СM9 (thx aquapp for testing)
Not working
None found yet, but when CM7 is on sdcard, it looses root. Trying to figure out why. - fixed in v10
PS: I hope I explained it correctly, not exactly good at this. Do not fear to ask, if you don't understand something.
OK, here goes guide for average user. This is still highly experimental feature, keep that in mind. Backup, backup backups and backup them to PC, read whole guide first, I am not responsible for your bricked phone etc.
GUIDE:1. Requirements
Ext4/Ext2/Ext3 partition on SDcard big enough to hold all files from /system and /data, which is from 170mb to 400mb (depends on ROM and apps installed), so I think 512mb partition is minimum (if its 90% or so free).
Modified recovery. Only AmonRa and CWM version is available at this time, TeamWin is coming "soon". You can find flashable zip at the bottom of this post, flash it before you proceed to next move. If something goes wrong, you can restore your recovery with zips from here.
Kernel with ext2/3/4 support, which is basically every but stock
Both ROMs you wanna use must be compatible with same kernel. See Limitations in previous post
2. MultiROM instalation
- Via MultiROM Mgr application
I recommend you do nandroid backup before installing via this app.
Download MultiROM Manager (link at the bottom of this), tap to "Tap to install via this app" and wait. As simple as that. Mgr will also install recovery for you (It will ask you which one, you can select AmonRa, CWM and none). App can check & install update, too.- Via recovery
Just download multirom.zip at the bottom of the post, make nandroid backup and flash it. Your current ROM will be the one in internal memory, we will setup the one on the SDCard in next move.
Now, try to reboot the phone (boot will take little longer, because it has to mount ext partition). If it boots up correctly, then its OK - your ROM is supported. If not, then restore your nandroid backup and post your ROM name here, maybe I'll try to make it working.
3. Setup ROM on the sdcard
Make nandroid backup (I am not kidding, you will need this one), flash ROM which you wanna to have on SDcard, do the first boot (because it will create dalvik-cache, and you dont wanna do that when its already on sdcard) and reboot to recovery again.
Go to "MultiROM options" menu and select "Create from current ROM". It will do everything for you (it takes time, though). ROM on the sdcard is placed in /sd-ext/multirom/rom/, backups are in /sd-ext/multirom/backup/.
Restore nandroid backup from beggining of this step and reboot. Wait until Boot manager shows up, and select SDcard as boot location. ROM from sdcard should boot. If your ROM from internal memory boots or if its stuck, something got wrong and you should restore from backup.
4. MultiROM recovery menu description
Active/deactive state is for recovery only, you can boot ROMs from backup in boot manager - that means its N-times boot rather than dual-boot.
When not active(boot from internal memory):
Activate (move from backup) - when you already have backup, this will move it to active folder (fast).
Activate (copy from backup) - same as above, but it copies it instead of moving
Create from current ROM - pretty self-explanatory
Create from ZIP file - see http://forum.xda-developers.com/showthread.php?p=22194117#post22194117
When active(boot from sdcard):
Deactivate (move to backup) - Moves current ROM to backup folder, so next boot will be from internal memory
Backup - Creates backup of current ROM
Erase current ROM - Deletes current rom, next boot will be from internal memory
Copy modules from int mem - Copies modules from ROM in internal memory to SDcard. Try this if WiFi does not work in SDcard ROM.
Flash ZIP - flash ZIP file to ROM on SD card, for example gapps.
5. Config file:
It is recommended to use Multirom Manager(see bottom of this post) to change config file.
File itself is placed on sdcard and its name is multirom.txt. Description of its contents is in this post(post is updated if something changes): http://forum.xda-developers.com/showthread.php?p=20045183#post20045183
6. Key bindings:
Since v11, you also can control MultiROM via touchscreen.
Anywhere: Hold Power button to shut down the phone
While on main screen:
VolUp/Down - list between actions
Menu - Confirm action
Back - Reboot to recovery
Power button - Sleep mode
While playing tetris
VolUp - return to main screen
VolDown - pause
Menu - move the piece to left
Home - hard-drop
Back - rotate piece
Search - move the piece to right
FAQ:Q: It is slow!
A: Its sdcard. It just is slower than nand memory.
Q: It does not work with my ROM
A: Post your ROM combination here, maybe I'll see to it.
Q: When do I need to reflash?
A: When you flash new ROM or do something which rewrites boot partition. Most (if not all) kernels are using Koush's AnyKernel, so they should not cause any problems.
Changelog & Download:(Always flash newest version)
Uninstaller: http://www.mediafire.com/?3eco51f2t0at77o (info here)
Changelog AND DOWNLOAD LINKS have moved to github: http://tasssadar.github.com/multirom/
Recoveries
AmonRa - based on 3.06: http://www.mediafire.com/?ld9g81igvze7na0 (9th March 2012 21:57)
AmonRa - based on 2.2.1: http://www.multiupload.com/7Y5HHNEPOT (20th October 2011 22:29)
CWM: http://www.mediafire.com/?6rfw0qbrddzq5d8 (9th March 2012 21:57)
TWRP: http://www.mediafire.com/download.php?o8kphxmfk9l01tl (21st October 2012 23:49)
MultiROM Manager app
http://forum.xda-developers.com/showthread.php?p=20610052#post20610052
(Always use newest version)
v24 - http://www.mediafire.com/download.php?1xy52tamzepibrx (TWRP support)
v21 - http://www.mediafire.com/?u9c3bmfbtf57dtm (Add charger settings)
v18 - http://www.mediafire.com/?g1lpsp66jc1cb1b (Add boot location settings)
v17 - http://www.mediafire.com/?l1li51sseaisz5j (Add brightness setting)
v15 - http://www.multiupload.com/B65WPFMFXP (Show & reset tetris high score)
v14 - http://www.multiupload.com/FWB5UBSMO1 (Updater now also check for app update, some minor fixes)
v13 - http://www.multiupload.com/NYYBX9CAFD (Update translations, add support for optimus V - http://forum.xda-developers.com/showthread.php?p=20657898#post20657898)
v11 - http://www.multiupload.com/1L3294ZAU7 (Fix mount issues on some roms, add menu to main screen, add link to xda)
v10 - http://www.multiupload.com/B3AVSFKDOW (Create /sd-ext/multirom folder on install)
v9 - http://www.multiupload.com/WW7TUNP7RY (read http://forum.xda-developers.com/showthread.php?p=20624306#post20624306)
v8 - http://www.multiupload.com/6OD7RQ74OE
v7 - http://www.multiupload.com/DJKMUGIVJ0
Something like this have the Xperia series. Maybe u find something u can use there.
Sent from my LG-P500 using XDA App
so this means we can test roms without replace current ??
Yes. Is my english so bad or you just don't read what I wrote?
Tasssadar said:
Yes. Is my english so bad or you just don't read what I wrote?
Click to expand...
Click to collapse
For the last time,you're speaking english perfectly p)
how to install your zip of amonra recovery i try but the recovery says that the zip dont have updatescript so it gives error....
i dont understand how to do this but ii´m searching this for a long time,if you can make a more frindley all user guide it will be very cool thankyou and hope you could doot....
*sigh* once again, this is [dev] thread, this is not something you can flash, at least not yet. You would know that, if you'd read whole post.
eduardogouveia said:
how to install your zip of amonra recovery i try but the recovery says that the zip dont have updatescript so it gives error....
i dont understand how to do this but ii´m searching this for a long time,if you can make a more frindley all user guide it will be very cool thankyou and hope you could doot....
Click to expand...
Click to collapse
[dev] means this is not something ordinary. Don't know what it is, don't mess with it.
Tasssadar said:
*sigh* once again, this is [dev] thread, this is not something you can flash, at least not yet. You would know that, if you'd read whole post.
Click to expand...
Click to collapse
Don't worry, you'll get more "hao cán i flush this into ma phones?" questions, good luck.
sounds like fun
thanks for bringing it for optimus one
but i have one question for you
I think in future kernel changing will also possible
because if we can flash kernel then we can make it to change
right?
Tasssadar said:
Yes. Is my english so bad or you just don't read what I wrote?
Click to expand...
Click to collapse
Maybe you just helped us with boot manager app
Sent from my LG-P500 using xda premium
I read the post but since the download you have is of a amonra recovery modified by you,i thougt that was a regular zip and only then make by abd the tutorial,thats why hi also ask a more friendly use because i now its not for averager use no need to get obset however im still happy hi was searching for that so hi dont mind waiting you make it more simple... sorry if that ofend you or franco lol we have to learn and its very hard now how to develop without having the proper nowledge like you all devs have and hi respect every dev even of he just make a simple app,by the way just dont send me to school lol where could i learn the bases to umderstand how to program java and then develop im asking this because all books hi find rekire previous nowleged of some progaming could some dev. Pointing me somewhere where i could learn and please dont be rude im just asking because i just dont love i want and hi will learn...
And baking to the thread what you find for me is one of the best and most important for our phones thanks a lot now just wainting a day everybody could use your work thank you
Sent from my LG-P500 using XDA Premium App
So your main question is: "Is it worth it?"
I would say, "Hell yeah it is!" but then again I do not have the know-how to pull something like this off.
If you decide to go ahead with it, I wish you the best of luck =P
I just modified Koush's AnyKernel so that it can modify ramdisk's content, so it is possible to install it with .zip file via recovery. I will add some modified version of CWM & AmonRA, create some walkthrough video and write some guide soon(c).
By the way, that kernel which is in devoid #froyo-final cant mount ext4 partition in init, dunno why, I'll look into it after raid.
EDIT: wtf, it just works now, and I did nothing Oo
EDIT2: Changes commited, now It can installed/controlled only by flashable ZIPs and recovery(well, only my modified AmonRa recovery for now). I'll do the rest soon, but I dont know when - maybe tomorrow (oh my, it is today actually already), maybe next month.
Flashable zips and guide added, see first and second post.
keep going I wanted something like this waiting when it can boot stock<froyo> and cm7....
thanx
gingerbread test
well i try with V20C,2.3.4 port(both with a2sd)and didnt woork after flash multiromv1.zip,when reobooting always return to recovery,so in recovery i go to multirom options and says no multirom folder so i start to think a2sd imcompatibelity,so i grab 2.3.3 V20G without changes oficial as lg give us but the results where the same no a2sd problem....
well later i will flash oldbaseband and try one of your combinations but i think its not compatible with gingerbread.....
I think I found it - on GB, there is "on fs" trigger in init.rc, which has only mounts in there, but I need to comment them out - all of them, so "on fs" trigger is empty, and init parser cant handle that. Will update soon.
Ok i will remain in new baseband to try when you update your exclente work...
Sent from my LG-P500 using XDA Premium App
v2 released, I have tested it with CM7 6.5.8, problem with stock GB should be the same as with CM7.
So I created a new thread for this so I can edit the first post for release-info.
This is the old thread:
http://forum.xda-developers.com/showthread.php?t=1133866
Please note that the multiboot-feature will be removed if you update your real system.
The virtual systems will stay on the sdcard so just reinstall the mod and you can boot your virtual systems again
Changelog:
Code:
[B]v0.8:[/B]
- addon.d (Multiboot will be kept on ROM-Update)
- working reboot recovery inside multiboot-rom(will boot directly into the recovery for that rom)
- working reboot into bootmenu inside multiboot-rom
- security-fixes
- TLS-support
- fixed sdcard-problems for NAND-system
[B]v0.7:[/B]
- added integration in touchbootmenu. This is no compatibility-patch - since now multiboot can only be used in combination with touchbootmenu
[B]v0.6.1:[/B]
- fixed some memory-leaks in kernel-module
- fixed stupid bug which prevented creating backups on first start
[B]v0.6:[/B]
- new hook-method with kernel-side code which should be the solution to most rom-problems
- fixed a bug which prevented mounting cache-partition inside recovery
- fixed installer-bug when TouchBootmenu is used on NAND
- reboot to recovery/bootmenu does not work for now. will be fixed in future
[B]v0.5.5:[/B]
- support for Stock-roms with Greenbreadmod
- added version-file(for updater which comes soon)
[B]v0.5.4:[/B]
- fixed problem with install-script
[B]v0.5.3:[/B]
- support for TWRP recovery
- fixed problem with virtual systems with names longer than 9 chars
- don't change 2ndBoot-script for bootmenus with 2ndSystem-support
- show graphical error-message when error was detected and copy log to "/cache/multiboot/error.log"
- experimental support for booting stock-roms
[B]v0.5.2:[/B]
- more configurable(via config-file)
- fixed error-detection. On early errors you will get back to bootmenu
- fix boot-problems for some roms
[B]v0.5.1:[/B]
- fixed crash of GUI when choosing recovery
- fixed bug which prevented creating important images on first boot
- virtual systems now are using nand-backups with real data so you could install backups of virtual systems on NAND
- installer sets default bootmode to 2nd-boot
- added recovery-option for NAND
- patch background-image of virtual recovery so you see if you are flashing real or virtual system
- reboot system if you click "Go Back" in virtual recovery(until I found a solution for going back to multiboot-GUI)
[B]v0.5:[/B]
- better protection against unwanted changes on real partitions(thanks wizwin)
- fix Phone for for GB-kernel(thanks quarx)
- set props so apps can detect if phone started with multiboot or not(for future versions of multiboot-manager)
- reboot into bootmenu/recovery now works
ATTENTION: reboot into recovery will open recovery for REAL system!!!
- added GUI for choosing which (virtual) system you want to boot
[B]v0.4:[/B]
- replacing all references to real system with stub-image(will be automatically created at /sdcard/fsimage/stub.img).
Now the recovery for the virtual system should be completely abstracted and it shouldn't make any changes to the real system
- a PDS-backup will be created and injected because it's needed by android-system and above change removes the reference
[B]v0.3/v0.3.1:[/B]
- moving original system-partition to another location instead of lazy unmount so she will be accessible in 2ndBoot-system and will not be busy
- fixed recovery to improve installer-zip compatibility. MIUI works now
- internal script-changes
[B]v0.2:[/B]
- "Install zip from SDcard" works now
- changed hook-method so it works with more ROM's(including ICS)
[B]v0.1:[/B]
First release
Source:
https://github.com/M1cha/DefyMultiboot
Download:
http://forum.xda-developers.com/attachment.php?attachmentid=1289953&d=1346244428
Installation:
1. Download zip-file and copy to sdcard
2. create 3 filesystem-images in ext3-format and copy them to /sdcard/multiboot/NAME with the names system.img, data.img and cache.img.
Please replace NAME with the folder-name of your virtual system(you have to create this)
You can download ready-to-use images from here:
http://www.multiupload.com/VY3U4IXRO1
2. install zip-file in CWM
Some info:
- The menu-entry "Lastest Recovery" is no longer supported and will affect your real system!
- boot the System-Chooser with the 2ndBoot-option in bootmenu
Bugs:
- Data-Wipe deletes android_secure
Donate:
Developing Multiboot makes much fun and I really like the results but takes much time, so feel free to donate a beer.
Hey,
i have no "Lastest Recovery" but a "Custom Recovery"
Can i install your script or does it not work with this version of the Bootmenu?
Which rom do you have installed?
I will check if it's compatible.
Thanks for the fast answer
i installed the CM7.2 Nightly "cm72-111125.0850-NIGHTLY-Defy"
The nightlys should always have the newest version of bootmenu.
Where you downloaded the nightly? I only could find "cm72-111123.1710-NIGHTLY-Defy.zip".
But generally it would work if you install but the problem is that you will never be able to change your real system because recovery will only make changes to the virtual one.
That bootmenu has 2 recovery-entrys is a lucky thing which I use as trick so I don't need to modify bootmenu
But when bootmenu-integration is done and you have an old version you will have to update bootmenu.
updated to v0.4
See first post for more info
Gonna try this now. I downloaded your empty .img files but how do I create my own img's on Win7? And what do you think is the smallest size I can make them safely to use with MIUI or ICS?
I don't know how you can create the images on windows, sry.
Maybe I can write a little App which does this directly on Android.
I have to admit that the images I uploaded are a little bit oversized.
system needs max 200MB
cache and data depends on your usage.
I would choose a minimum of 100MB for data and cache. If you plan to install many Apps you should make the data-partition over 300-500MB
Doesn't matter, instructions for Linux would do too
Hmm..oversized but no prob downloading because they were empty, only transferring via USB takes time. 200 MB for system and data and 100 for cache sounds good I'll make them myself if you can give me the instructions, I have Ubuntu.
App to do this on the phone itself sounds good, makes it even faster, no transferring from PC Thanks for your work
The Problem is that I can't find a mkfs.ext3-binary for Android
Maybe I'll extract it from another phone which contains this.
But as of now, here are the instructions:
Code:
dd if=/dev/zero of=./system.img bs=1000000 count=200
mkfs.ext3 ./system.img
The number 200 specifies the size in MegaBytes. I hope this will help you so far
Sure does
But like the poster above said, CM7 latest nightiles contain Custom Recovery, Stable Recovery, and Stock Recovery in the Bootmenu option for recovery. So Custom Recovery = Latest Recovery for your tool? I remember it used to say Latest recovery a few months back, dunno when that changed.
Oh, now I unsterstand what he wants to say.
I thought there is ONLY "custom recovery".
But if there are two recovery's it's ok to install. So you can use "Custom Recovery" for your virtual filesystem.
I'm downloading the CM7-source so I can extend and compile bootmenu and everything will be easier.
But with a download-speed of 170KiB/s this will take a long time
How fast is the virtual system? Could it be laggy because it is loaded from the sd-card?
the time from bootmenu to the boot-process itself takes a little bit time sometimes if I'm debugging.
But normally the booted system is in normal speed for me.
I think this depends on the speed of your sd-card and the usage of your apps.
m11kkaa said:
But normally the booted system is in normal speed for me.
I think this depends on the speed of your sd-card and the usage of your apps.
Click to expand...
Click to collapse
What class brand capacity card do you use?
I'll be trying with miui and ics tonight
Sent from my MB525 using XDA App
I don't know which class my card is because there is no label. It's completely black
But I don't think I have the best one(maybe class 2 or something else?)
An APP for windows to create ext-3 partitions http://forum.xda-developers.com/showthread.php?t=824154
download link: http://www.multiupload.com/SV7SOY33MQ
I have a 8GB class 4 card. Will test it in a few minutes with CM7 as real system and ICS as virtual system. Do you know what happen if I restore a backup in the real system? As far as I know a backup will override the bootmenu, too. Or am I wrong?
Yes, that will override the bootmenu.
But your virtual system stays on the sdcard.
You just need to patch again bootmenu with the downloaded "defy_multiboot_vX".
I'm on CM7 latest nightly and got boot loop when i tried to install Galnet MIUI ICS on virtual system. Could you fix it?
Dear Owners,
Discontinued
In this post you can find a multilingual (mainly European) modified rom for the smartphone Lenovo A820.
IMPORTANT NOTE!
The newer phones do not work well with S138 or older kernel (no info about S147).
The sympthom is that the touch screen works on inappropriate way: after the first screenlock it does not work again.
For this reason it is highly recommended that update your kernel if you have got this issue.
The kernel changer to S150 zip can be run from modified recovery (CWM, TWRP, COT, Carliv, etc...).
Note that all the things in this thread you do with your phone can be dangerous. I cannot take responsibility for your phone damage.
So, do it at your own risk.
Before you do anything, I recommend you to save your current ROM (I would say it is mandatory!)
There are many ways to save and I highlight some (links will be added later):
1, for non-rooted phones:
- SP_Flashtool, readback option.
- CWM (or TWRP) backup, if it is available on your phone
2, for rooted phones:
- MTKDroidTools backup
- command line dd-backup
In order to install this ROM, you need to have CWM recovery on your phone.
If you have not got this recovery or you do not know which recovery you have got, you have to read post#3 before you do anything.
If you get error during the installation of the ROM, see post#4.
The restore option of the CWM rcovery is not as good as it could have been expected, so please read post#4 carefuly for CWM restoration issues, tricks.
Update: CWM 6.0.4.0 with S150 stock kernel.
Just to clarify the power-on modes:
Normal phone mode: press the power button
Meta mode: VOLUME DOWN + POWER
Factory mode: VOLUME UP + POWER
Recovery mode: VOLUME DOWN + VOLUME UP + POWER
Consider the warranty issues, you need to backup you rom.
In addition, I always suggest to do a backup before install any new ROM to your phone.
You can do it with CWM recovery in backup menu.
About installation in general.
Pre-requisites: CWM recovery menu installed on your phone. (This ROM can be installed from CWM recovery.)
The ROM file must be saved on your physical SD card.
Enter into CWM recovery.
In CWM recovery you can go up/down with the volume up/down keys. The “enter” is the power button.
Choose the “install zip from SD card” menu item.
Choose the “choose zip from SD card” menu item.
Select the rom you want to install.
Choose “OK” in the menu item.
If you need a detailed explanation of its use, see the tutorial : http://bm-smartphone-reviews.blogspot.com/2012/02/complete-guide-to-clockworkmod-recovery.html
Right after the ROM installation has been finished, you can install gapps as well, before restart.
Windorws driver installation:
Please do not ask me about it. I use mainly Linux, which is more friendly.
What I did in XP under Virtualbox was:
Downloaded the Lenovo drivers from here: <link>
Manually added the com ports in control panel.
MOD CP4.0
V1
The modified rom has got the stock kernel - Lenovo A820_ydss_S135_130403
This completely changes your phone appearance, your Lenovo UI will be disappeared.
Also Lenovo applications are not integrated to this rom.
It will look like the stock Jelly Bean.
Main features:
-The firmware is rooted.
-Boot logo, boot/shutdown animations and sounds are changed to Lenovo.
-Minimalist appearance and content, for this reason you have to install google applications manually, from CWM recovery <link>. After gapps installation everything works well (many people wants to have mainly Google Play. It do work.)
-Slide unlock.
-Multilingual. For supported languages, see the screenshots.
-The default language/region is Hungarian, but you can easily choose your one.
Known bugs:
- I found was that the charging logo with turned off phone is not proper.
-the camera does not work adequately in video-camera mode.
-the default setting in some of the application is V987.
V2
The modified rom has got the stock kernel - Lenovo A820_S135_130403
The camera was changed to a non-multilingual one. It looked that the black screen in camcorder mode solved.
But after googleapps something went wrong... black screen again.
V3
The modified rom has got the stock kernel - Lenovo A820_S135_130403
In V3 there is not any significant changes (camera app was changed back to the multilingual one), but I modified the gapps, which caused the camcorder issue.
So, for this modified rom you need to use this gapps.
V3 download link: CP4.0-by-cappa72-v3 - dropbox
or
CP4.0-by-cappa72-v3 - 4shared
Bug: Still, the camera has got green lines in the case of playback.
CP4.1
V1
The kernel has changed to A820_YDSS_S130_130324.
The camera application does not generate green bands in playback.
The default language was set to English, default time zone was set to London.
CP4.1-by-cappa72-v1
You can use the googleapps mentioned for CP4.0-v3
CP4.2
V1
The kernel has changed to A820_S138_130419
CP4.2-by-cappa72-v1
Bug list
#3 - CP4.2-v1 - Wen try to choose themes, the laucher is Force Closed (FC) - Settings was modified to resolve this issue.
#4 - CP4.2-v1 - Serial number is 0123456789ABCDEF instead of the original S/N - not a real bug
#5 - CP4.2-v1 - Under the battery level of 15% the SystemUI is Force Closed (FC) - was a user error, when people deleted the necessary ui files.
CP4.3
This release will be the continuation of the 4.2, but with the newest available kernel (S150) and will (plan) contain all the things that are included in the 5.3.
This will not be with Aromainstaller and will contain the gapps.
Hopefully comng within two weeks.
MOD CP5.3
Available now (25.11.2013.)
CP5.3
V1
Change log; what’s new compared to CP4.2
Aromainstaller is used for optional installation possibilities.
- still Jelly Bean 4.1
- kernel is the stock S150
- Modified systemUI by [email protected] (1% battery signal; automatic hide function for non-used sim signal)
- Modified Settings by apeelme (sloving bug #3)
- Baseband is from the stock ROM S150.
- gps.conf is set to EU by default
- apns.xml is modified for Telenor-HU from “net” to “online”
- gps-tracker solver added to build.prop (dalvik.vm.execution-mode=int:fast)
- libvcodecdrv.so replaced to solve green bars in case of video playback.
- updated MobileUncleTools (2.9.5) in case of 3rd party SW.
There is no default ringtone set! Right after the installation you have to set the ringtone, message alert and so on... otherwise your phone will not play sound...
Important feature!
If you have already repartitioned with the script, you can simply install this ROM, it will recognise that the repartition had been done; and you do not have to run "disable internal SD card" script from CWM.
But please note that this function is onyl available with the repartition script; with Meteos rom editor repartitioning this function is not available.
Right after the installatio, there is not any sound set. Nor the ringtone, nor the message an alert. So, you have to set it first.
Available on mediafire : Link
md5sum: 86e241fcac6faf4fa6baf0f9cc4a18a0
Additional possibility:Change of FM radio
The FM radio can be changed back to Lenovo’s one with this script. It was requested by some people due to the fact that Lenovo’s FM radio can work without connecting the earphone.
The link is here. http://data.hu/get/6494163/FM-radio-change.zip
You can install it from CWM recovery, with the same method that you used during the installation of the ROM. This script does not affect any other part of the ROM, but the FM radio.
Repartition
Please DO NOT USE IT for Lenovo-based ROMs. Sometimes it can cause bootloop or other inconvenience.
The repartition of internal memory of the Lenovo A820 phone has been solved already.
With this action youd intednal SD card will be disappeared and will be added to the /data partition.
Before you do anything, make a CWM backup, and save all your data from internal SD card!
The easiest way is to use this CWM script, if you want to have the maximum available size (2,7GB) for the /data partition.
You have to install it from CWM recovery.
After the installation you need to do a factory reset.
After the factory reset, you have to disable your internal SD card, with CWM script.
And then, you can reboot your phone to check if yo have got the new size of /data partition:
settings --> storage
"internal data storage; full capacity 2,7GB"
"internal SD card; full capacity <your physical SD card capacity"
If the above data appear, you have successfully repartitioned you phone's internal memory!
If you want to have your data back, go into CWM recovery, and choose
backup and restore --> advanced restore --> <choose your save> --> Restore data
And then, your data are available again, after the reboot.
Please do not use it, if you do not want to have the 2,7GB of /data partition!
For Lenovo-based ROMs you need to use Meteos-apk for repartition of A820.
Internal/external SD card exchanger
If you want to use your physical SD card as the default one, and still want to use your emmc-SD card (aka internal SD card by default), you can change it by this CWM script.
Important link in summary:
The driver what works is here.
The original stock recovery is here
The autoroot package can be found here.
The preferred CWM is here.
The root script is here, you can install is from CMW, and your phone will be rooted.
The usable Flashtool is here.
The scattel file for Flashtool is here.
Credits:
bgcngm for the base of the ROM (BM1.0 for ZTE V987), and his amazing tutorials
iBotPeaches and brut.all for apktool
dsixda for his ROM kitchen which is really helpfull for easy-deodexing
Koush for his wonderfull CWM recovery
amarullz for his amazing AROMA installer
...and finally to all the devs whose apps, tweaks and scripts I have used on my custom ROMs
Very nice Thanks for your hard work and good luck
CWM recovery
Installing CWM on your phone
You need to install proper drivers to your computer.
Available (ported) CWM recoveries:
With newest kernel:
CWM recovery 6.0.1.2 - S150 - ported from [email protected] ZTE V970 recovery.
CWM recovery 6.0.4.0 - S150 - ported from [email protected] ZTE V967S recovery.
CWM recovery 6.0.1.2 - S138 - ported from [email protected] ZTE V970 recovery.
CWM recovery 6.0.1.2 - S135 - ported from [email protected] ZTE V970 recovery.
Option 1, with SP Flashtool
Download the SP_Flashtool software to your computer. Extract it to a directory, where you want to run it from.
Download the scatter file, which you will need if you want to use SP_Flashtool.
Download the CWM
(5.5.0.4, 6.0.1.2, 6.0.2.8; it is your decision)
Run the SP_Flashtool.
Browse your scatter file.
Choose only the recovery.
Tick the “DA DL all with checksum” (you can find it close to the download button). It is a really important point!
If your phone is connected, let’s disconnect it from the computer.
Turn off your phone. Take the battery out from your phone for 5 sec. Insert the battery to you phone. Keep it still turned off.
In the flashtool press the Download button.
Choose OK to the warning message.
Connect your phone to the computer.
The flashtool will flash the recovery into your phone.
When the green circle appears, wait for 5-10 secs, and the unplug your phone.
If everything went well, you can enter into the recovery menu (see 1st post, power-on modes)
Option 2, on rooted phone, with MobileUncleTools.
Install MobileUncletools 2.8.x or higher from the Play Store.
Save one of the CWM I linked to the root directory of your physical SD card.
- select menuitem Recovery Update. The program will list the available recovery images.
- choose the one, what you want to install
- It asks back: "Are you sure flash recovery!" - Use recovery file: <name of the recovery what you choose previously>. Tap to OK.
- After the flashing process it offers you to reboot into recovery. If you tap OK, it will automatically reboot your phone to recovery. If you tap cancel, you can use your phone as a phone.
- Before you tap to "reboot to recovery", I suggest you to wait approx. 5-10sec.
Use of the CWM.
If you enter into the CWM (6.x.x.x) recovery, the following buttons can be used:
- Power button : “enter”
- Volume down : step down in the menu
- Volume up : step up in the menu
- Soft key “option”: step down in the menu
- Soft key “back” : step back in the menu
In 5.x.x.x you cannot use soft keys, but the physical buttons works on the same way as in the case of 6.x.x.x
CWM restoration
I experienced failures in restoration of the CWM backup.
This was a real surprise for me because I have not faced this issue with other MTK phones.
So, the issue is that the CWM restoration does not work immediately.
In details:
-I saved the stock rom by CWM 6.0.1.2 (CWM was complied by Bruno, and I modified it for A820)
-For checking the restore function, I did a factory reset: the phone stopped working.
-I did the CWM restoration, but still the phone stopped at the boot animation. And stayed it for 15min. I removed the battery then.
In order to solve the issue, the following method was done:
-In the advanced restore I choose the restore /system (only!)
-After restoring the /system I turned off the phone took the battery out, waited 5 secs, inserted the battery back.
-Turning on the phone it worked again with the restored data, BUT the internal SD card was injured! I formatted the internal SD card – with this action I lost all my data that were saved on the internal SD card.
So, please be careful using it! Save your internal SD card data before the CWM restoration!
This was experience in case of all the available CWM (5.5.0.4, 6.0.1.2, 6.0.2.8).
Installation issues
Post#4 troubleshooting
If you cannot install the ROM by an error:
Code:
assert failed: getprop("ro.product.model") == "Lenovo A820"
E:Error in /sdcard/Lenovo-a820-update-CP4.0-v1.zip (status 7)
This is a safety feature, not a bug.
This error message is a warning that you have not got the proper CWM. (Most of the available CWMs are based on ZTE, STAR phones and contain improper model description.
My CWMs contain the proper one, I modified them, so you need to install a CWM I mod for Lenovo A820.
In this case you have to update your CWM to a ported one that I did.
Great!
I would love an multi lingual rom, but for now I just want to root it. (ones it gets delivered that is)
Are there tools specific for this device to root is with out flashing?
Checking out your rom in the meantime. :fingers-crossed:
ebsbow said:
Great!
I would love an multi lingual rom, but for now I just want to root it. (ones it gets delivered that is)
Are there tools specific for this device to root is with out flashing?
Checking out your rom in the meantime. :fingers-crossed:
Click to expand...
Click to collapse
If you have got CWM recovery on your phone (or a chinese one that has got "xx SD yyy ZIP" menuitem), then you can use root-zip, installing it from CWM recovery.
Thanks
Thanks
Where are the screenshots?
please add some screenshots.
deathhand said:
please add some screenshots.
Click to expand...
Click to collapse
I tried to upload some, but the server was down that time.
I will try it again tomorrow.
Thanks for this rom, I flashed it succesfull on the Lenovo A820, it also takes away that terrible skin from Lenovo.
Gapps link
Thnak you for your ROM. I tried it for a couple of hours and there some minor problems that I don´t know if there are rom related.
1. There is no link to the gapps, so I downloaded a random one and I have errors with google search.
2. The videocam record with a green band on one side.
3. The gps is slow, doesn´t pick satellites easily.
4. If you choose automatic time the it always consider that you´re in china. If you choose manually your timezone then it is ok.
Overall it is a very well-done rom and I would keep it for daily use.
Thanks
1. Are you sure you downloaded the Gapps for Android 4.1.x? You should have this gapps version: gapps-jb-20121011-signed, this the right version you should flash. I first flashed the rom and after that the gapps.
I have reproduced your issue and you need to update the Google search app in the playstore, after that the errors are gone.
2. I have reproduced what you reported, I want to try if I can grab the original camera app from Lenovo and see if it still has the issue, but I don't think its a big problem, I bought the phone for someone else, but this issue is not to big, I don't suppose people often record with an smartphone and this rom at least got Dutch in, the original phone firmware was bloated with China Unicom bloatware, Lenovo skin and had no Dutch support.
3. Try GPSfix, ussualy this kinda works, but the MT6577 chip was know for having GPS problems, perhaps its the same with MT6589? But there are many apps out there that can help you fix it.
I think this in a great rom, Lenovo is a big brand in China, so many will choose Lenovo and with this rom you get rid off the terrible lephone skin, I mentioned this rom in my review about this phone
Oh here you got some screenshots.
Feel free to use them in the OP.
Don't know about you but I do use my device a lot for video recording.
I think it is imperative that all basic functions work flawlessly.
The custom rom's with android 4.2 also have an video bug at this time, which is a bit unacceptable.
I'm sure it will be sorted out :victory:
Well yes, but having fully Dutch support is better, you can always flash new update off the custom rom when it get fixed. I only recorded a few time video with my own smartphone.
Lebrija said:
Thnak you for your ROM. I tried it for a couple of hours and there some minor problems that I don´t know if there are rom related.
1. There is no link to the gapps, so I downloaded a random one and I have errors with google search.
2. The videocam record with a green band on one side.
3. The gps is slow, doesn´t pick satellites easily.
4. If you choose automatic time the it always consider that you´re in china. If you choose manually your timezone then it is ok.
Overall it is a very well-done rom and I would keep it for daily use.
Thanks
Click to expand...
Click to collapse
1, I have added the link.
2, Thanks for the feedback, it is really useful to know. The playback contains the green band, the file itself does not.
I changed the kernel to the '130'-one, and now it works with the camera application, and the playback is also correct.
3, You shall try the EPO / A-GPS support for getting it better. Or thy DexterMorganNL's suggestion.
4, I have never faced this issue, but in the new version I set the default time zone to London.
The new one is available, you can see it in the first post.
cappa72 said:
1, I have added the link.
2, Thanks for the feedback, it is really useful to know. The playback contains the green band, the file itself does not.
I changed the kernel to the '130'-one, and now it works with the camera application, and the playback is also correct.
3, You shall try the EPO / A-GPS support for getting it better. Or thy DexterMorganNL's suggestion.
4, I have never faced this issue, but in the new version I set the default time zone to London.
The new one is available, you can see it in the first post.
Click to expand...
Click to collapse
Thank you for your time. I will try the new version. But, why have you used an older kernel?
By the way, with version 3 I also had some problems with the gyroscope when playing Real Racing 3.
Great work
Its great you released the update so fast, you brought us really good work. I think new owner off this phone is going be thankful, they requested me to buy a phone for them while I'm in China, and when I got it it was not fully Dutch supported, had the terrible skin.
So its great have this phone, because this way I can deliver it without the Chinese bloatware and with full Dutch language and ofcourse Google apps.
EDIT
The newest release gives me a black screen after I boot it up after having it flashed, so I have reverted back to your previous release.
OK. I'm ready to weep.
I've previously had a ROM from NeedRom on my A820.
I'd like to give Cappa's ROM a try, but when I try to install from CWM Recovery I hit the Error outlined in Post 4.
I then follow the advice of Post 3... But there are no links to A820-compatible CWM Recovery installations. I found one on a hungarian site linked to Cappa, but all I get is a .img file and no idea how to get that on to my phone.
Can anyone post detailed instructions, or send me to a page (in English) where I can find instructions on how to get the ball rolling so I can use Cappa's ROM?
Thanks.
Google is my friend. Yes. But Google Translate isn't.
TheTen said:
OK. I'm ready to weep.
I've previously had a ROM from NeedRom on my A820.
I'd like to give Cappa's ROM a try, but when I try to install from CWM Recovery I hit the Error outlined in Post 4.
I then follow the advice of Post 3... But there are no links to A820-compatible CWM Recovery installations. I found one on a hungarian site linked to Cappa, but all I get is a .img file and no idea how to get that on to my phone.
Can anyone post detailed instructions, or send me to a page (in English) where I can find instructions on how to get the ball rolling so I can use Cappa's ROM?
Thanks.
Google is my friend. Yes. But Google Translate isn't.
Click to expand...
Click to collapse
Update, I think I sorted it...
Bit of imagination (and could have totally done the wrong thing, but it seems to be making progress...)
I decided to take a known ROM install that I've tested and that works, which has a recovery.img included, and I renamed the recovery.img to recovery_bak. I then renamed my 'new' CWMRecovery image to recovery.img and dumped it in the directory with the ROM data that I got off NeedRom. I loaded up SPFlashTool and loaded the scatter file from that ROM, then deselected every component except 'recovery' and flashed it.
End result is that I have a phone which recovery-boots to the version 6 cappa-modded CWMR which I found on the Hungarian site, and in turn that CWMR has just installed both the required ZIP updates outlined in Post 1, and Cappa's ROM is now sat on my second A820 awaiting setting up...
I hope I did the right thing, and this won't come back to bite me in the ass later... The newer recovery.img was slightly larger than the old one, but I'm assuming that the scatter file isn't about storing specific pieces of the ROM in specific places based on exact size of file, and thus perhaps all things will continue to work swimmingly.
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Galaxy Note 3 LTE International
Now: one common recovery for all: hlte
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
The below specific variants are no more updated, use hlte common variant
- hltexx
For older bootloader, use versions before 6.13.0
Click to expand...
Click to collapse
Big thanks to @eybee1970 for the first flash
To @Chenglu for guide in dtbTool + support in fixing mount usb storage
To TeamWin for the primitive device tree
To @wanam for his help in compiling kernels
Reserved
Info:
Kernel compiled from sources update3
No sensors flashing: fast boot in recovery
Root allowed
Selinux enforced mode preserved
Built in NTFS/Exfat kernel module support for fast backups
Recovery: based on cm-11.0 kitkat branch
More info:
At worst, it would bootloop and you have to know how to get out of a bootloop, that's it
But you're still warned: Read Post 1
Credits to @Chenglu for parts of the ramdisk
Can you build a version for SM-N9005 hlte?
regards
Great your here! Best recovery option! Now can you get some of your buddies to push us an aosp rom??
Sent from my SM-N9005 using XDA Premium 4 mobile app
First, someone has to flash it so that we debug it
The risks are a boot hand so you need odin to flash another recovery
Either selinux missing permissions I will add later or needed graphics.c
Waiting for feedback
Yay \(^o^)/
I've been waiting for you Phil
Welcome
Sent from my Note 3 powered by Omega v4.0
Vocaloid fan? Check out this thread!
cool to see you here, mate
EDIT: ok, I flashed it
- CWM zip to flash Recovery does not work (at least for me...)
- ODIN flashable works
- CWM Touch Recovery works, no issues so far
Thx.
The warnings in post 1 are for noobs
So do not be do scared others
Phil3759 said:
The warnings in post 1 are for noobs
So do not be do scared others
Click to expand...
Click to collapse
post above yours
eybee1970 said:
cool to see you here, mate
EDIT: ok, I flashed it
- CWM zip to flash Recovery does not work (at least for me...)
- ODIN flashable works
- CWM Touch Recovery works, no issues so far
Thx.
Click to expand...
Click to collapse
Are you kidding?
It works?
LoL
Never thought on first release. This has no device tree. I built near from scratch, based on twrp broken device tree for cwm
Big thanks. I am removing noob warnings in op so that we start debugging where needed
:thumbup::thumbup:
Phil3759 said:
Are you kidding?
It works?
LoL
Never thought on first release. This has no device tree. I built near from scratch, based on twrp broken device tree for cwm
Big thanks. I am removing noob warnings in op so that we start debugging where needed
:thumbup::thumbup:
Click to expand...
Click to collapse
I have to thank you...I don't like TWRP, so I used CWM so far...but as I use Sammy Flip Cover, it is really hard to handle volume buttons....now I don't need them any more
EDIT: Thx for mentioning me in OP...but please correct my nick ...its a funny kind of my initials (A.B.) and the number behind is quite clear I guess
Phil3759 said:
Info:
Kernel compiled from sources update3
No sensors flashing: fast boot in recovery
Root allowed
Selinux enforced mode preserved
Built in NTFS/Exfat kernel module support for fast backups
Recovery: based on cm-11.0 kitkat branch
More info:
At worst, it would bootloop and you have to know how to get out of a bootloop, that's it
But you're still warned: Read Post 1
Credits to @Chenglu for parts of the ramdisk
Click to expand...
Click to collapse
Nice to see this ramping-up :good:
Obvious warning that should be added to the top post - like every single custom (non-Samsung) recovery so far, this is also tripping the Knox flag.
eybee1970 said:
I have to thank you...I don't like TWRP, so I used CWM so far...but as I use Sammy Flip Cover, it is really hard to handle volume buttons....now I don't need them any more
EDIT: Thx for mentioning me in OP...but please correct my nick ...its a funny kind of my initials (A.B.) and the number behind is quite clear I guess
Click to expand...
Click to collapse
Fixed with your correct nick
- is backup to exfat extrnal sd ok?
- mount usb storage and OTG USB?
- format usb otg in exfst/ntfs/ext4/ext2?
- boot into recovery is fast?
- time/date?
If all ok I will clean it and release other variants
Phil3759 said:
Fixed with your correct nick
- is backup to exfat extrnal sd ok?
- mount usb storage and OTG USB?
- format usb otg in exfst/ntfs/ext4/ext2?
- boot into recovery is fast?
- time/date?
If all ok I will clean it and release other variants
Click to expand...
Click to collapse
- will test backup...right now not enough free space on external sd
- usb storage mounting does not work
- won't test format
- boot in recovery is fast enough - same as before on regular CWM
- time/date not showing up correctly...for me it is 10.05 am now and it shows up 20.12 pm though I set the correct timezone
Phil3759 said:
Fixed with your correct nick
- is backup to exfat extrnal sd ok?
- mount usb storage and OTG USB?
- format usb otg in exfst/ntfs/ext4/ext2?
- boot into recovery is fast?
- time/date?
If all ok I will clean it and release other variants
Click to expand...
Click to collapse
Backup to extsdcard (fat) OK : Time 20min
Backup usb otg OK : Time 10 min
don't try format
boot in recovery speed time seem to be the same as normal cwm
time/date : in cwm I had 23h29 instead of 14h32 (I'm in france), in backup name the date is false (01_01_1970)
aromafm feature not working.
i have /aromafm/aromafm.zip in the clockworkmod folder on internal storage and sdcard...
Philz touch can´t found this folder...
"now clockworkmod/aromafm/aromafm.zip in storage paths"
i started aromafm.zip via install zip -> Choose zip from /sdcard -> clockworkmod -> aromafm -> aromafm.zip and this work it...
go in the sdcard folder ... -> empty! no data found on internal storage...
external storage is this problem too.
regards
Sakaschi
tr72 said:
Backup to extsdcard (fat) OK : Time 20min
Backup usb otg OK : Time 10 min
don't try format
boot in recovery speed time seem to be the same as normal cwm
time/date : in cwm I had 23h29 instead of 14h32 (I'm in france), in backup name the date is false (01_01_1970)
Click to expand...
Click to collapse
Many thanks
Can you verify mount usb storage on pc for external sd?
Sakaschi said:
aromafm feature not working.
i have /aromafm/aromafm.zip in the clockworkmod folder on internal storage and sdcard...
Philz touch can´t found this folder...
"now clockworkmod/aromafm/aromafm.zip in storage paths"
i started aromafm.zip via install zip -> Choose zip from /sdcard -> clockworkmod -> aromafm -> aromafm.zip and this work it...
go in the sdcard folder ... -> empty! no data found on internal storage...
external storage is this problem too.
regards
Sakaschi
Click to expand...
Click to collapse
Check data/media/0 stories in FAQ
storage set to /data/media/0 is selected....
Phil3759 said:
Many thanks
Can you verify mount usb storage on pc for external sd?
Check data/media/0 stories in FAQ
Click to expand...
Click to collapse
I can't check, I'm on mac. Try with virtual machine without success but it's not a good test.
Find an old flashdrive to try some format :
vfat : OK
extfat : OK on windows (VM), not on mac (ask to initialise the disc)
ntfs : OK
Don't have the driver to test the other.