Related
This Eclair 2.1 rom is fast and stable.
The interface is standard AOSP ui.
This is a ported version of [email protected]'s latest SuperEclair v8.8. He based his rom off CM5 and made some improvements. Some users in other forums are saying they think it is better than the latest CM5. I have never used CM5 so I can't comment from personal experience.
Linpack scores of 3.6+ with Sanpei's OC kernel update, JitHack, and AutoKiller.
A HUGE thanks goes to lefeudedieu and Switch33 for their contributions.
Apps2SD is working and is the same as Apps2SD in CM5 with sd-ext.
---> The rom will also boot without sd-ext defined. If you want to use Apps2SD make sure the correct partitions defined on your sd card. Read CM5 guides for partition instructions.
It uses Sanpei's latest .32 OC Kernel for 6.35 radio.
Works with both Cursordroid's and Amon Ra's recovery images.
Everything seems to be working except for LWP (see change log in second post for what is working).
Working:
-Multi-language support
-JitHack
-GPS
-Youtube
-Camera
-Bluetooth
-wifi
-VPN
-3D Gallery
-SupSetup4 (not in v2.1)
-Camcorder recording & video playback
-Apps2SD (Must format ext partition to sd-ext[/COLOR]
-Battery life is improved because of kernel update
See change log in next post
Download the cooked ROM :
rapidshare v2.1 FULL
MD5sum 1c1234ce14dc13749461cdce37c64fff
NOTE: If coming from a previous version of this rom or any other rom, do a full wipe and delete the SupSetup folder from your sdcard before booting for the first time.
Instructions:
You need new radio 6.35.10.18, SPL 1.76.2007 and recovery-RA-Magic32A-6.35-v1.6.2 or recovery-RA-hero-v1.6.2.img.
It might work on with other recovery images, but I have not tested them.
If you do not know how to change your radio, SPL and recovery, click here at Cursor's post.
Partition SD Card:
1. Use Cursor's or Amon Ra's recoveries to partition SD card.
2. When phone is off, press Home and Power buttons at the same time to start into recovery.
3. Select Partition sdcard.
4. Select Partition SD.
5. Press Home to confirm.
6. Use trackball to select minimum swap-size of 64 MB (I use 96 MB).
7. Press Home to set swap-size.
8. Press Home to set Ext-size of 512 MB. FAT32-size will be the remainder of the sd card.
9. Press Home to confirm and partition.
10. Press Home to confirm.
11. Exit.
Install ROM:
1. Download the cooked ROM
2. Save the ROM to sd card
3. Wipe data/factory reset
4. Wipe Dalvik-cache
5. Wipe SD:ext partition
6. Flash ROM
7. Reboot
8. Let the rom take its time.
9. Open AutoKiller, click Menu, select/click Presets, select/click Optimal.
10. Open SupSetup and activate JIT.
11. Open TasKiller and AutoKiller to ignore (not sure if this matters, but I don't want TasKiller to shutdown these 2 apps)
12. Configure phone settings, set up accounts, sync, etc.
13. Reboot.
NOTES:
(1) The SupSetup app (if you flashed a version where it is included) in the ROM allows you to tweek the settings for Apps2SD, LinuxSwap, CPU Options, JIT, etc.
(2) AutoKiller optimises the allocation/use/freeing up of memory. After first boot and initial set up, launch AutoKiller app, select Presets, apply desired setting, and reboot.
I am not responsible if you brick your phone.
Apps/Features:
-Sanpei's .32 kernel for 32A 6.35 radio
-JitHack
-Multi-language support
-AutoKiller (for memory optimisation & performance)
-Camcorder recording & video playback
-Apps2SD
-Default home launcher
-3D Gallery
-Gallery
-Astro File Manager
-Battery Widget (by geekyouup)
-Bluetooth File Transfer
-Bookmark Backup
-Car Dock/Home
-Car Mode
-Circular Battery (with percentage) in notification bar
-Custom Locale
-Desk Clock
-Facebook Sync
-Maps4.1 With Navigation Outside USA (Brut's Maps)
-Music Player Widget (from SuperD)
-Phonalyzr
-SupSetup4 (if included)
-TasKiller
-Voice Keyboard
Credits and roms I based my rom on:
....SuperEclair V8.8 original rom by Superatmel
....[KITCHEN] Basic ROM kitchen for aspiring Magic cooks by dsixda
....I used Sanpei's latest 32a .32 new radio 6.35 kernel with OC
....I pulled some lib files from ahmgsk to get the camera working
....Autokiller app by ratson
Change Log:
v2.1
Download v2.1 here
rapidshare v2.1 FULL
MD5sum 1c1234ce14dc13749461cdce37c64fff
- Updated to Sanpei's OC 576MHz kernel
- Removed SupSetup
- Enabled JIT
- Disabled Swap
- Apps2SD is in Settings -> Applications
- Improved camera (still not 100%)
- GPS issue has not been fixed
v2.0
Download v2.0 here
rapidshare v2.0 FULL
MD5sum dca7c6c85da2b891287ca8ea06e03f3a
-Updated rom with latest SuperEclair v8.8 build based off CM5
-Apps2SD updated to work the same as Apps2SD on CM5
-Live Wallpapers are not currently working
Flash Sanpei's kernel OC here over v2.0 for better performance including improved battery. Flash it as you would a rom from the recovery.
v1.2
NOTE: If coming from a previous version of this rom, do a full wipe and delete the SupSetup folder from your SD card to fully remove SupSetup before booting for the first time.
-Removed SupSetup application --> I think rom is more stable now, powers down better & performance has not been sacrificed
-Fixed 3D Gallery --> Bug when rotating phone is fixed; must open 3D Gallery and rotate phone a couple of times then it will work without error
+After flashing rom, you may want to flash radio again - some report it improves GPS issues
v1.1
-Updated to latest Sanpei .32 kernel with BT battery drain fix
-Added boot animation back
-Fixed audio volume level issues
Known issues:
(1) 3D Gallery has bug with rotation but does not FC
(2) Camera has blurry line after taken pics, but works fine
(3) Tethering may not work
(4) GPS was/is unstable as with other roms for 6.35 radio, but Sanpei's latest .32 kernel may have fixed this issue (you can also try flashing radio again and/or rebooting when GPS is on)
(5) Occasional lock up when shutting down / rebooting phone - just pull battery to boot again
v0.9
-Ap2sd fixed !!! (Must format ext partition to ext3)
-Camcorder recording & video playback fixed !!!
-Reverted back to Superatmel's original 8.2 build for performance improvement
-Added new build for Android wireless tether
v0.8
-Removed all launchers and replaced them with regular default home launcher to prevent forced close some people were getting
-Added regular gallery and 3D gallery
-Ap2sd (buggy - check out Firerat's thread on Ap2sd)
v0.7
-Added JitHack
-Added AutoKiller (memory optimisation app - you must open app and tweak settings)
v0.6
-Will now flash and boot with both Cursordroid's and Amon Ra's recovery images
v0.5
-Added Home++
-Updated 3D Gallery
v0.4
-Updated to Sanpei's .32 32A 6.35 kernel
-SupSetup4 fully functioning
-Ap2sd fully functioning
v0.3
Fixed:
-3D Gallery (still buggy)
-Live Wallpapers (still buggy)
*For best results with LWP, disable 3D acceleration using SupSetup, select desired LWP, turn 3D acceleration back on - LWP seem to be working fine this way - according to Wes Gerner LWPs break when using 3D Kernel
Not working:
-Camcorder
-Battery (performance is poor)
v0.2
Working:
-GPS
-Youtube
-Camera
-Bluetooth
-wifi
-VPN
Not working:
-Camcorder
-Live Wallpapers (buggy)
-3D Gallery (buggy)
I tried to flash the Rom but installation was aborted... Don't know if this is the fault but my sd card is not partitioned..
magicbu said:
I tried to flash the Rom but installation was aborted... Don't know if this is the fault but my sd card is not partitioned..
Click to expand...
Click to collapse
I m too getting err @ line 2: assert group blahblah.....
camelacml said:
I m too getting err @ line 2: assert group blahblah.....
Click to expand...
Click to collapse
Yeah, unfortunately something like that is the message... and then ti aborts the installation. There's something that cannot be loaded i think.. maybe i am wrong..
Install works for me, make sure you're using the sapphire-6.53 recovery rather than the hero recovery.
Testing the ROM now, so far so good.
Unfortunately got the dreaded sleep of death. After the phone went to sleep I wasn't able to wake it.
@magicbu You need to use AmonRA's MAGIC recovery, not the HERO one then it will be ok - forum.xda-developers.com/showthread.php?t=530492
had no problem with flashing.
looks really nice.
Problems:
- camera
- 3D Gallery
- weird bootlogo
- I am missing HTC Sense , I know this is Eclair...
+ I really like the new battery indicator
-> where can I find it / put it on my rom?
switched back to Villain rom
Everything works well,but GPS did not start.
HTC Magic 32A
Radio:6.35.....
Rom:Supereclair 2.1 V8.2
Recovery:Magic 32A 6.35-v1.6.2
baga10 said:
Everything works well,but GPS did not start.
Click to expand...
Click to collapse
same here; gps doesn't seem to work. nice rom otherwise
I got GPS, 3D Gallery, and Live Wallpapers working (although live wallpapers have a couple glitches still).
See link to new version in first post.
See change log in second post.
YOU NEED CURSOR'S recovery-RA-Magic32A-6.35-v1.6.2 RECOVERY TO BOOT THIS ROM
Livewallpapers don't work here. Rest looks good
Not for everyday use. Slow, some live wallpapers don't work correctly. But most things work (but too slow).
mastermid said:
Not for everyday use. Slow, some live wallpapers don't work correctly. But most things work (but too slow).
Click to expand...
Click to collapse
The speed thing is weird. During my testing and flashing this rom maybe 10 times, it was really slow maybe 2 times. All the other times it ran fast. Right now it feels as fast or faster than any eclair for me.
nice ROM, flashed it. but crushed after i ve taken photos and viewed in 3D gallery. Live wallpapers do not work too. phone jammed, restarted after i selected one of them.
I hope to fix live wallpapers in the next release even though I don't use them because they kill the battery.
gallery should also be fixed. its not working for me
unable to flash it, error in line 2
ododoo said:
unable to flash it, error in line 2
Click to expand...
Click to collapse
wrong recovery installed? you should have cursor's 6.35 recovery hope this helps
!!This is ONLY for Toshiba Folio 100!!!
This Mod is based on Toshiba Stock with additions from Nvidia SDK, to make a better functioning stock rom with google apps and better OpenGL ES support.
Currently giving you an amazing
- 3000+ in Quadrant score!! (screenshot here )
- 50.5 frames in neocore (not amazing compared to HTC desireHD, i think, but still good)
You can also follow updates on Twitter now: Dexter Picard (DexterPicard) on Twitter or
me a Red bull, and you're sure i stay up working on this mod or you can visit my new homepage at Dexter's mods
for new users with latest 2.2.5.0131 firmware, here is a howto on reverting tablet to be able to install custom roms.
Wiki pages available here and here Other non-FolioMod , but folio100 threads Kernel&Tweaks & General questions thread
Please use these for non-FolioMod questions, like screen,battery etc...
Video illustration of FolioMod (Thanks to kevin.hansen)
Installation Instructions:
ALWAYS HAVE CHARGER CONNECTED WHEN UPDATING A FIRMWARE.
A FACTORY RESET IN RECOVERY MENU IS ALWAYS RECOMMENDED TOO.
You can also try these instructions for v1.1 and lower versions here or here if those help you in another way than the one provided below.
download latest FolioMod full zipfile- Extract contents to a folder and follow instructions below.
copy the update.zip from inside downloaded zipfile to the root of your sdcard, and insert sdcard into folio.
Enter "Recovery menu" when folio is just turned on and press (POWER) once and (VOL up) next.
press (VOL up) Factory reset or system update.
press(VOL down) to continue to system update.
press (VOL up) to confirm system update.
during installation progress bar will show har far it is.
folio will reboot after installation.
if you need to wipe, repeat the steps above without sdcard inserted, and you get into recovery menu. Press "HOME" button to see menu and choose "factory reset".
After reboot a BLACK screen appear for 1 or 2 minutes!! don't worry, its normal!
Rollback to original stock rom:Download Folio stock image for full restore to stock rom
extract zip to a folder, and from here follow steps 1 - 7 above, to install the update.zip .
This image is for rollback purpose, if you do not want the mod edition, here is the way back to stock rom.
Remember to run a factory reset before or after this stock rom install..
Latest Full update
Download Mirror 1 - FolioMod v1.4 or Mirror 2
Patches
FolioWidget fix here , solves the compressed issue on regular launcher or LauncherPRo. now shows all icons.
V1.4 - Rollback of graphics tweak driver - if you got problems with touch screen here
V1.3+ old wifi driver(1.0 release) works better for some ppl. (Requested by many) here
V0.0+ Generic format internal storage for all mods (so far) here, only needed if you got internal storage problems.
Rename downloaded patch to update.zip and install using recovery.
Old releases
Download Mirror 1 - FolioMod v1.3d
Download Mirror 1 - FolioMod v1.3b
Download Mirror 1 - FolioMod v1.3 - Mirror 2 - easyshare - Mirror 3 - (NOT THERE)
Known issues (also reported by users)
NONE
THANKS to
ownhere - coming up with the initial idea on how to implement the loopback solution for optimized database access.
Weeds2000 , for the great help and fixes done so far for us (Orientation + paid apps, vold with NTFS corrections to FolioMod) + Kernel compiles
DerArtem - Compiling kernel + and being very active on getting 3G modem support for us on our folio!!
Sol Ido - Foliowidget
Teknoraver - Foliobuttons
badstorm2010 - First custom kernel on folio available.
CHANGELOG
v1.4 (changes compared to v2.2.5.0131)
libraries from v 2.2.5.0131 release of 18-feb-2011
eUpdate patch from stock release of 18-feb-2011 (touchscreen+i2c update)
Paid apps working. (thanks to weeds2000 for the fix)
rotation & mouse (fixed by Weeds2000)
Fixed toshiba pegadroid support (ext.jar missing pegadroid service), important for toshiba services.
added newest Market app (2.2.11)
3D frame hack (increased framerate from 51 to 70), if you got touchscreen issues, here is the rollback patch
BROKEN: 3G support (new toshiba kernel required for display driver, and we got no source available yet)
BROKEN: CIFS support
Filesystem optimization still active
newest flashplayer v10.1.120.10 included.
newest mediaplayer & filemanager update from toshiba.
Maps 5.0 added with multitouch rotation support
build.prop changed to emulate GalaxyTab (tablet Market support with more apps)
NOTE: Name is written as SGH-T849 (please just ignore, forum reports will be ignored too)
HDMI option added in Settings, for option to switch between 480p,576p,720p,1080p
note: tablet is still just 1024x600, so desktop is scaled, movieplayback should be correct.
360 degree rotation
settings - gapps sync enabled
deodex'd
wpa supplicant (adhoc) support (use FolioWidget to enable)
Added WMA/WMV support (upto 1080p)
Fixed Wifi script issues
Fixed /mnt/sdcard mount location (apps issue, better support now)
Root'd (Superuser + su included)
Rooted recovery + busybox tools
increased main filesystem (252MB)
SpareParts (disable "compatibility mode" to have old apps fullscreen.
Taskkiller included (Fixed for Toshiba framework)
More Locale 2 included (so all languages can be selected)
BROKEN: NTFS / CIFS / 3G support will be enabled as soon as a kernel source update is available, so DerArtem can compile
a working kernel for us.
Thanks to all those which have donated because of this FolioMod. Its truly appreciated to see people actually
like this and would pay a little to get the improvements in place!!
Thanks!
WARNING: Use this image at your own risk and i take no responsibility if
you brick your tablet.. Image has been tested on a Toshiba Folio 100 and works fine if guidelines are followed.
11.01.2011
Weeds2000 gave it a go, and fixed the download of paid apps! im sure alot will be happy to read this.
Then i found another tweak in the screen driver, to increase framerate which currently was only 51. now its increased to 80.
on top of this, DerArtem is currently working on making it possible to use USB 3G dongles on our folio, so we can go online using the phone functionality in Android. I have for now, enabled some phone functions and activated the signal level indicator (might be annoying, but enhancement has a cost for now).
It also seems, that i by mistake had enabled locationservices in the build.prop, so at every boot the GPS, which we don't have, was enabled and caused an additional CPU load during a bootup. this is now fixed as well.
31.12.2010
the update pack includes some fixes for wpa_supplicant issue, where it did not switch to the correct adhoc wpa_supplicant.
and weeds2000 has brought a new update to the orientation so compass works, but mouse is still wrong.
lastly it fixes the sensor readings which made your tablet unable to rotate.
30.12.2010
A little more details on v1.3 update release..
V1.3 went through a public beta1 stage and issues were found and fixed where possible.
While fixing bugs in 1.3beta a 3D performance pack was found with the Viewsonic forum, and i tested it with our Folio, with changes as required to match our system. and it increased framerates. So that is now part of the new 1.3.
Furthermore the filesystem I/O performance bugs were found and fixed, and we now have a 330MB partition running on a loopback device, making database calls and small file changes much faster.
With the ElocityA7 i found the newest Flashplayer minor update revision, and of course replaced our Toshiba beta with the new one found.
Other users has suggested kernel tweaks which also has been added to the v1.3, one of them is the "swappiness" parameter, it is suggested to increase application handling on our folio and its now "live" in this release.
Sol Ido, provided us with the 0.3.4 edition of the FolioWidget, which includes a tricker enabler for switching between the regular wpa_supplicant and the wpa_supplicant for adhoc use also included in 1.3.
The orientation fix from weeds2000 is now default included into v1.3, but can be removed with a rollback patch found in the patches section in Post #1. it does have flaws like mouse pointer moves in "portrait" mode right now. compass should not be working correctly. but in general more apps utilizing the orientation/sensor is now working much better.
With FolioMod 1.3 a small milestone is reached, getting 3000+ in Quadrant score without actually cheating here
But of course Quadrant benchmarking is just one way of meassuring our device, CPU performance has not changed at all, so dont get too excited, but it does help in the overall experience of your tablet.
19.12.2010
A little picture to document the problem with rotation on our tablet and other tegra2 tablets. click picture for better details.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
as you see on the picture above, our tablet has native 0 degree in landscape mode where mobilephones got portrait native.. you can call this failure of nvidia, or someone else, but it seems that someone thinks this should be the standard.
if we can get the X and Y curve switched, we might just get it working normally.
12.12.2010
- Version 1.2 introduce use of the official patch installer from Toshiba which shows progress bar indicator movements on the screen, if recovery menu is not shown.
- Version 1.2 offers the newest toshiba update 2.5.0053 features, but which?
- BadStorm2010 managed to get a custom kernel compiled, which for adds support for ext4(future support),OpenVPN and cifs support, so you can mount filesystems over network.
- The FolioWidget offers control of your hardware buttons to have lights enabled and turns off only when pressed (good during evening/night)
- By failure of mine, the Vending.apk (Market app) included in 1.2, slows down the folio, so to enhance and fix it, i added a patch which adds the newest Market app to our folio with new design and way of selecting apps (actually is much better).
- as the framework is new, i tried to include all old features as 360 rotation , wma/wmv , Google apps + /mnt/sdcard location fix and other small issues.
- Paid apps still remain an issue with toshiba framework, only solution for you that want/need it, is to use the old 0.2 edition with nvidia framework.
29.11.2010
Currently the Toshiba edition 1.0b is having more issues than compared to 0.2a software wise. there is a freeze issues, and awake issues(solved,but fix is not released) and google paid apps cannot be downloaded.
So if you're ok without proper BT functions and usbstick unmounting, the 0.2a is probably you're best choice right now..
But if you need mouse/keyboard, usbstick proper unmount, 360rotation, the toshiba mod is the way forward.
I will try and get the freezing fixed, but more testing is needed..
28.11.2010
the Toshiba mod was created due to all the small differences in the framrwork with Bluetooth, USB functionality and sdcard card functions. Like on phones, vendors always do a little customization, which not always serves all users nicely when the image is modded based on other models. But now the stock rom is available with modded functions, so all should be happy now.
25.11.2010- on top of the above mentioned changes, here are some more regular info
- The new 0.2a still has USB stick/sdcard unmount issues, which is only part of the toshiba framework to handle for now. Im working on getting it to work on stock android.
- Increased the desktop sizing to 7 vert/horz , so more space for widgets and placement.
- media player extract image information.
- Wpa supplicant will not show signal strength for now, but im sure the better functionality might compesate for this.
(this has been tested with my Galaxy S running tetherAP function, and i could go online using my mobile connection)
Tested(v0.2a),
-Gapps,Angrybirds,Movieplayback(Yxplayer)+WMV/WMA, HDMI out, usb mass storage to pc, sdcard,usbstick, websurf+flash
- rotation , Market download, Power off,ad-hoc connectivity,.
I will test it now, downloading (very very slow :S), thank you very much for your work your are my hero
zizouth said:
I will test it now, downloading (very very slow :S), thank you very much for your work your are my hero
Click to expand...
Click to collapse
its very slow, because there is like 20 of us who are downloading the file at the same time.
well the one who gets it up an running first, please post a step by step for the noobs ( like me) and give some impressions how the device works with this first better rom!
Anyone is welcome to post mirrors, i dont needs credits for those.
Btw, im also uploading a stock mod for this folio..not sure it takes bandwidth, maybe too many mods on my hosting solution, as its probably busy somehow..
and we all know Folio100 is not THAT popular yet! so many is so much said
Downloaded but file is corrupt... re-downloading
Great , going to download it and try it ! Thanks
zizouth said:
Downloaded but file is corrupt... re-downloading
Click to expand...
Click to collapse
Re-downloading with download manager --> file is corrupt again, please re-upload it
Dexter_nlb.
regards
No problems with the Download here.
I installed everything through the System Update, but nothing changed at all. Do I have to perform a factory reset before applying the folio mod? (My folio is rooted, I tried to install some google apps and so on...)
The first line when applying the mod says "E: can't mount DEFAULT_PATH" - how about the others?
Anyway: thanks a lot for your work!
At some point you have to select "apply sdcard:update.zip" or something like that with vol - and (i think) power
For me it did a factory reset but nothing else, tried angry birds to see if anything had changed but nope.
zizouth said:
Re-downloading with download manager --> file is corrupt again, please re-upload it
Dexter_nlb.
regards
Click to expand...
Click to collapse
i have uploaded to that site like 100 times, never had problems...
but yes, today the speed seems very slow even when im uploading, maybe its simply timeouts on your download so the zip gets corrupt.
filesize should be 164.256.143
shinebar1001 said:
No problems with the Download here.
I installed everything through the System Update, but nothing changed at all. Do I have to perform a factory reset before applying the folio mod? (My folio is rooted, I tried to install some google apps and so on...)
The first line when applying the mod says "E: can't mount DEFAULT_PATH" - how about the others?
Anyway: thanks a lot for your work!
Click to expand...
Click to collapse
Some people in http://forum.frandroid.com/topic/31757-foliomod-v01/page__gopid__526895#entry526895 who have tested your rom say also nothing changed at all...?
also for me nothing changed. Download and update work fine. After update I try to install Angry Birds but when I
run it I can hear the sound of the game, but I don't see nothing.
Is possibile with this mod install the Android Market?
Oneiros7 said:
For me it did a factory reset but nothing else, tried angry birds to see if anything had changed but nope.
Click to expand...
Click to collapse
Process takes like 1 minute.. so did it reboot instantly or?
zizouth said:
Some people in http://forum.frandroid.com/topic/31757-foliomod-v01/page__gopid__526895#entry526895 who have tested your rom say also nothing changed at all...?
Click to expand...
Click to collapse
are people using the "update.zip" inside the zip i released? or simply putting this one on the sdcard?
when installing it shows text, when HOME button is pressed this is clearly one way to confirm something.. just rebooting does not say much here..
here is another way:
- Reboot into "Firmware Update" menu.. (Press MENU to show actual recovery menu screen when booted into recovery kernel, after the "recovery logo" shows)
- Insert sdcard into slot, and move to "update firmware" second line.. and press power button to execute.
below you should see the information on steps taken..
Dexter_nlb said:
are people using the "update.zip" inside the zip i released? or simply putting this one on the sdcard?
when installing it shows text, when HOME button is pressed this is clearly one way to confirm something.. just rebooting does not say much here..
Click to expand...
Click to collapse
Yes they are using update.zip inside the zip.
Hello, I tried and the message was :
Code:
Extractiong packs...
Done Extraction...
Preparing filesystem...
tun adbd
+---------start adb daemon-------+
+---------installing boot-------+
+---------installing recovery-------+
+---------extracting system-------+
+Instaling system, this takes a while
+-----------------------------------------+
Installation done.now reboot system.
Formating MISC:...
I reboot and same launcher, no gapps, no opengl2.0
Okay, tried the other way:
Booted into Firmware update without the sd-card until the android with an exclamation-mark-sign shows up.
Pressed the Home-Button an got into the system recovery utility.
Second lin is apply sdcard:update.zip (Vol down + Power on)
Code:
Folio100 Open Recovery starts:
Extrackting packs.
Done Extraction
preparing filesystem
rund adbd
+--start adb daemon--+
+--installing boot--+
+--installing recovery--+
+--extracting system--+
+Installing system, this takes a while (correct ;))
+---
Installation done.now reboot system.
Install from sdcard complete.
Formatting MISC:...
Rebooting system (Power)
So, unitil now everything looks fine. After a reboot nothing changed
Hope this helps to debug.
Danny
shinebar1001 said:
Okay, tried the other way:
Booted into Firmware update without the sd-card until the android with an exclamation-mark-sign shows up.
Pressed the Home-Button an got into the system recovery utility.
Second lin is apply sdcard:update.zip (Vol down + Power on)
Code:
Folio100 Open Recovery starts:
Extrackting packs.
Done Extraction
preparing filesystem
rund adbd
+--start adb daemon--+
+--installing boot--+
+--installing recovery--+
+--extracting system--+
+Installing system, this takes a while (correct ;))
+---
Installation done.now reboot system.
Install from sdcard complete.
Formatting MISC:...
Rebooting system (Power)
So, unitil now everything looks fine. After a reboot nothing changed
Hope this helps to debug.
Danny
Click to expand...
Click to collapse
well, it looks correct, so next question is; can you use adb? and login with shell and maybe extract the /tmp/recovery.log file?
if you got no root, just enter "rootme" and you should be disconnected from adb.
kill adb with "adb kill-server" and relogin with adb.
and you got root.
Is this correct?
power vol+
vol+ ->"continue factory data reset..."
vol- ->"continue system update"
vol+ ->"confirm"
when adroid appears HOME button
vol- ->"apply sdcard:update.zip"
power
then
"reboot now"
no need to do any wipe data/factory reset or wipe cache partition?
at the end I have
Finding update package...
Opening update package...
Installing update...
-----------------------------------
| FOLIO100 Open Recovery |
-----------------------------------
Extracting packs...
Done extracting...
Preparing Filesystem...
run adbd
blahblah
Installing system, this takes a while (not really in my case)
Installation done.now reboot system.
Install from sdcard complete.
Formatting MISC...
The picture behind is the little android with a exclamation point.
It's my 5th time doing that and still no luck
hum sorry for the post not fast enough
[Patch] Adlxmod.F4D.2.03-patch
This patch includes previous Adlxmod.F4D.2.02 patch, plus:
- Semi-transparent pulldown bar
- Updated: Google Maps 5.2
- Updated: Market 2.3.4
- Latest Cyanogen APN list (February 06, 2011)
- Fixed notification texts not always white in the DarkBar version (only applies to Adlxmod.F4D.2.03-DarkBarOnly patch)
- Note 1: This patch will restore the white notification bar. Download the new DarkBar patch to switch again to a Black bar.
- Note 2: This patch will automatically wipe the Dalvik cache, so the first reboot will take some more time (can take >5 min depending if you have many apps installed) - Don't freak out.
New Notification bar patches:
- Dark Bar : Adlxmod.F4D.2.03-DarkBarOnly-signed.zip
- White Bar: Adlxmod.F4D.2.03-WhiteBarOnly-signed.zip
[Patch] Adlxmod.F4D.2.02-patch
This patch includes previous Adlxmod.F4D.2.01 patch, plus:
- BlurHome selectable: You can switch to BlurHome if you like it
- Added: Adobe Flash 10.1.106.16
- Updated: Market 2.3.2
- Updated TitaniumBackup 3.7.1
- Added: Copy to Clipboard
- Added: Shrinkpipe
- Removed BlurUpdater.apk
Base rom Adlxmod "Froyo for Defy" v2.0:
- Based off UK 3.4.2-117 Froyo leak
- Fully Deodexed by me -> Theme ready
- Optionally a dark notification bar patch can be installed, see below. White patch also provide to get back at it.
- Rooted, Recovery installed
- Phone can be used with no SIM
- Includes Motoblur, but it can be skipped
- Many language supported: Spanish, English, French, Portuguese,...
- Camera flash IS working and synced
Added:
- LG Optimus 2X ringtones (some literal in chinese)
- Adlxmod splash (installed on 1rst boot, will appear on 2nd boot)
- HTC_IME Keyboard para Froyo!
- Gingerbread Keyboard
- Android Terminal Emulator
- Wireless (Wifi & Bluetooth) Tethering
- Busybox fully installed
- AOSP Email App
- Titanium 3.6.7.1
- LauncherPro 0.8.3
- Tenfar Recovery
- 3D Gallery (my mod)
- Overclock support (phone won't be OCed by default)
- SetCPU (free from XDA, please donate on the Market)
- Milestone Overclock
- Added in /system/xbin: rwsystem/rosystem, wpa_cli, zipalign, strace, ssh, sqlite3, dexopt-wrapper, tcpdump, fix_permissions, iptables,...
- Extensive APNs list (Cyanogenmod)
- Ad-Blocking
- AOSP Eclair icons & lock screen sliders
Updated:
- Market 2.2.11 + Market Fix (Paypal shows up for example)
- Google Maps 5.1.0
- Adobe FlashPlayer 10.1
Download these files:
Chinese sbf : Defy_2_2_CN.zip
Rom's Nandroid: Adlxmod.F4D.2.00.zip
Boot+Devtree : Tmo_2.2.1-3.4.2-107-boot-devtree-ONLY.sbf
SuperOneClick : SuperOneClickFor2.1.zip
(this link included Tenfar Recovery with an installer) -> use this one.
Latest Adlxmod Froyo for Defy patch: Adlxmod.F4D.2.03-patch-signed.zip
Optional files you may need:
- Dark Bar : Adlxmod.F4D.2.03-DarkBarOnly-signed.zip
- White Bar: Adlxmod.F4D.2.03-WhiteBarOnly-signed.zip
- Patches for fixing signal/baseband, 2g/3g
- Alternative languages (like PortugueseBR,...) for Swype: see here
Instructions: Please READ-RELAX-READ-FOLLOW
First of all, check CAREFULLY in which case you are:
Case 1:
If you come from a US T-Mobile Defy with the 3.6.90 update
If you have already flashed a non-downgrabable sbf (2.51 or 3.4.2).
Case 2: If you are not in case 1.
Due to Motorola Defy having a locked bootloader at the time of doing this rom, the flashing process is quite complex, so READ AND FOLLOW it VERY CAREFULLY, or you will end with a non booting phone. If it is the case, you should restart again the whole procedure from the beginning.
I recommend you print the whole procedure, and check every step as you do them.
PLEASE READ EVERY SINGLE STEP BEFORE STARTING IT AND FOLLOW THE ORDER CAREFULLY.
If you don't respect the steps and order, the result can be unpredictable.
Only run the steps that apply for your case!
This Rom is a Nandroid backup of system to be restored over the phone:
Unzip the rom file, and place the 2011-02-03.11.17_Adlxmod.F4D.2.00-WhiteBar folder into the SD:/goapkrev/backup/ folder. If SD:/goapkrev/backup/ doesn't exist you have to create it. It should look as follow:
SD:/goapkrev/backup/2011-02-03.11.17_Adlxmod.F4D.2.00-WhiteBar/system.img
SD:/goapkrev/backup/2011-02-03.11.17_Adlxmod.F4D.2.00-WhiteBar/nandroid.md5
Start with FULL battery! (cases 1 & 2)
Be sure your phone's battery is charged 100% before starting.
Wipe all (case 2 ONLY)
Boot your Defy into Stock Recovery (Power + Volume Down button)
Tap in the bottom right corner of the screen to get into the menu
Select Wipe Data, then press OK
Reboot phone into USB Bootloader Init mode (Power + Volume Up button)
Flash Chinese sbf, root, install recovery (case 2 ONLY)
!! WARNING !! Be sure you are in case 2 before you follow! If you are in case 1, read instructions again!
Connect the phone via USB to your computer
Flash Chinese Froyo sbf using latest RSD Lite (4.9) & latest Motorola drivers (4.8)
After flashing the phone will reboot. As we have wiped, it should boot correctly into the Chinese rom.
At the Chinese Motoblur login screen:
Select English language
Press Menu -> Skip Motoblur setup
Root, Install recovery (case 2. also case 1 if you have never rooted & installed recovery)
Go to Settings, Applications, Development -> Enable USB Debugging Mode
Root the phone using the provided SuperOneClick
Don't reboot yet. Run the "Install Recovery.bat" in the same SuperOneClick folder.
This will copy Tenfar Custom bootstrap recovery to the phone and reboot it.
Power up the phone again & wait until it boots.
Go to Settings, Applications, Development -> DISABLE USB Debugging Mode
Open "System Recovery" App in the App Drawer
Press "Install Recovery System", when Asked for Superuser permissions, give them and wait until it says "Install Success!"
Reboot into Custom Recovery & Flash Rom (case 1 & 2)
Go to Settings, Applications, Development -> DISABLE USB Debugging Mode
Open "System Recovery" App in the App Drawer
Press "Recovery Boot"
In Recovery, Select Backup & Restore -> Restore > Select the rom Adlxmod F4D v2.00 folder
Here you can also flash the patches you want to install (Apply zip from sdcard)
Get back to the recovery main menu, and WIPE ALL
(case 1 ONLY) Reboot. End.
Flash boot&devtree (fixes cam flash) (case 1 & 2)
Reboot. /!\ While the phone powers off and on again, maintain the "Volume UP" button pressed!!
Phone should now boot into USB Bootloader Init mode again.
If your phone doesn't boot into USB Bootloader Init mode, and you start to see the (M) Moto logo, pull the battery, unplug the USB cable. wait 10 sec. Plug the battery again, maintain the "Volume UP" button pressed and press Power. maintain the "Volume UP" button pressed until it you get to USB Bootloader Init mode.
Connect the phone via USB to your computer (if it was unplugged)
Flash the boot+devtree sbf provided by me using latest RSD Lite (4.9) & latest Motorola drivers (4.8)
End. Enjoy your Adlxmod Froyo for Defy!
Once you have correctly done the process, you may want to flash some option patches. Just go into Recovery mode and flash the zip you need from the optional patches.
Phew what a detailed protocol. Thank you so much will try it tomorroow
Sent from my MB525 using XDA App
Thanks for this! So your ROM is downgradable if we follow these instructions? I don't want to lose downgradability.
Update0: You really need to add that if you don't remove the battery FAST enough and your phone DOES go into Tenfar recovery, it will brick your phone. Because that is where I'm at right now.
I'm trying to start over, but I can't get anywhere except Stock recovery (which doesn't respond to any commands on the OK Button - wierd) and the USB Bootloader, which doesn't help because if I go through the whole process without doing the factory reset, I can't get to Tenfar's recovery boot after flashing the devtree only sbf - I just get a blank screen.
So I'm pretty much effed.
Update1: no wait, the Stock recovery is working, it's just going ... really ... really .. slow. Hope my battery doesn't run out before I get the factory reset done.
Update2: Ok yeah, still not working. Tried three times now. Can't get to Tenfar Custom Recovery after flashing the devtree sbf no matter what I do. If I leave it plugged in after flashing devtree and allow RSD lite to reboot the phone, I get "please manually power up this phone" and a blank screen. If I reboot manually, I just get the motorola logo forever.
Update3: I am going to try a different ROM entirely and maybe I can get a working phone before work tomorrow...
Update4: Yeah, your instructions were backwards. I should have noticed that right away, but didn't notice until I tried Higgsy's 2.2.1 Froyo build. You need to flash the boot+devtree sbf AFTER you restore the Adlxmod F4D v2.00 folder image - i.e. follow these steps: http://forum.xda-developers.com/showthread.php?t=937319
If you do it in the right order, this ROM works fine and is actually pretty cool (first boot takes a long time of course so be patient.)
THX Adlxmud for you custom rom! your description is great...
But 1 question, the optional patch (Dark-Bar) is work on other ROMS for example Rom 3.4.2 UK?
Tomorrow maybe try it
Thank you!
will try it rite now, coming from chinese sbf, never flashed 2.51. will post feedback tomorrow.
Darkcaptain said:
THX Adlxmud for you custom rom! your description is great...
But 1 question, the optional patch (Dark-Bar) is work on other ROMS for example Rom 3.4.2 UK?
Tomorrow maybe try it
Thank you!
Click to expand...
Click to collapse
hmm good question dude dark bar would look awesome going to try it as im board let you know if it works
edit tried it, it works but imo doesn't suite stock rom
rob-t said:
Thanks for this! So your ROM is downgradable if we follow these instructions? I don't want to lose downgradability.
Click to expand...
Click to collapse
If you haven't flashed any UNdowngrabable rom, you should be able to flash this one. After flashing this rom using my procedure, you will NOT loose downgradability. In other words, yes, my rom is downgradable.
rob-t said:
You really need to add that if you don't remove the battery FAST enough and your phone DOES go into Tenfar recovery, it will brick your phone. Because that is where I'm at right now.
Click to expand...
Click to collapse
If you land in Tenfar recovery you haven't followed my instructions that say:
- Press "Recovery Boot". /!\ Phone should now reboot. While the phone powers off and on again, maintain the "Volume UP" button pressed!!
- Phone should now boot into USB Bootloader Init mode again.
If your phone doesn't boot into USB Bootloader Init mode, and you start to see the (M) Moto logo, pull the battery, unplug the USB cable. wait 10 sec. Plug the battery again, maintain the "Volume UP" button pressed and press Power. maintain the "Volume UP" button pressed until it you get to USB Bootloader Init mode.
Click to expand...
Click to collapse
That means that, anyway you land in Tenfar recovery, just reboot your phone into USB Bootloader Init mode again to flash the boot-devtree.sbf.
If you get a non-booting device at some step, try to just reboot your phone into USB Bootloader Init mode again to flash the boot-devtree.sbf at this step.
rob-t said:
Update1: no wait, the Stock recovery is working, it's just going ... really ... really .. slow. Hope my battery doesn't run out before I get the factory reset done.
Click to expand...
Click to collapse
Well, Stock Recovery is a bit tricky to use... In my particular case I use the vol up/down to select menu entry, and I tap on [ok] (I usually have to tap several time to have the [ok] actually do something. Once it starts, yes, the Wipe is very slow! Like 1-2 minutes.
rob-t said:
Update2: Ok yeah, still not working. Tried three times now. Can't get to Tenfar Custom Recovery after flashing the devtree sbf no matter what I do. If I leave it plugged in after flashing devtree and allow RSD lite to reboot the phone, I get "please manually power up this phone" and a blank screen. If I reboot manually, I just get the motorola logo forever.
Click to expand...
Click to collapse
That is weird... Anyway I'll double check later, but it's what I have written on my notes, and I've followed my notes a lot of times, so I guess this order worked for me at least.
rob-t said:
Update4: Yeah, your instructions are backwards. I should have noticed that right away, but didn't notice until I tried Higgsy's 2.2.1 Froyo build. You need to flash the boot+devtree sbf AFTER you restore the Adlxmod F4D v2.00 folder image - i.e. follow these steps: http://forum.xda-developers.com/showthread.php?t=937319
If you do it in the right order, this ROM works fine and is actually pretty cool (first boot takes a long time of course so be patient.) PM me when you fix your instructions and I'll remove this.
Click to expand...
Click to collapse
I guess there is nothing wrong in flashing the boot-devtree sbf at the end, it should work the same, so I have updated the instruccions here. Maybe it reduce the problems. Anyone here with the same issue? If so, from what rom do you come from?
Also, one more thing: if you come from another UK or US based froyo rom, you should be able to skip the whole procedure and just restore the nandroid backup.
adlxdum said:
Also, one more thing: if you come from another UK or US based froyo rom, you should be able to skip the whole procedure and just restore the nandroid backup.
Click to expand...
Click to collapse
ill give that ago running uk 2.2
Nice rom, will feedback you...
can confirm that if you already running 2.2 all you need to do is run the nadroid back up and all should be good btw dude nice rom
First of all thanks for this rom! I am expecting my Defy over the mail by monday or tuesday and up till now this rom is the most appealing.
I have one question. How do you prevent motoblur installation? Is that simply a matter of skipping at first boot? Do you have plans to make a deblurred version of your rom?
coming from a 2.2 Chinese rom, it stuck on motoblur animation and didnt boot, i followed each letter from the instructions , no luck on this yet.
that happened to me pulling the battery sorted it and it booted fine after that
i think native boot+devtree would be better, so here it is.
racca said:
i think native boot+devtree would be better, so here it is.
Click to expand...
Click to collapse
I also had this one, but as the US one was working correctly I sticked with it. I have posted what I have tested.
Boot loop in Motoblur Animation?
fabianowerner said:
coming from a 2.2 Chinese rom, it stuck on motoblur animation and didnt boot, i followed each letter from the instructions , no luck on this yet.
Click to expand...
Click to collapse
If you have Boot loop in Motoblur Animation, please try this:
- Boot your Defy into Stock Recovery (Power + Volume Down button)
- Tap in the bottom right corner of the screen to get into the menu
- Select Wipe Data, then press OK
- Reboot phone into USB Bootloader Init mode (Power + Volume Up button)
- Flash the boot+devtree sbf provided by me using latest RSD Lite (4.9) & latest Motorola drivers (4.8)
Then reboot. How does it go?
adlxdum said:
I guess there is nothing wrong in flashing the boot-devtree sbf at the end, it should work the same, so I have updated the instruccions here. Maybe it reduce the problems. Anyone here with the same issue? If so, from what rom do you come from?
Click to expand...
Click to collapse
Thanks, yeah I was coming from Eclair 2.34, so I should be downgradable. Can confirm that the camera works fine on this ROM.
Sadly, I have the dreaded "Unable to open connection to server" problem with Android 2.2 so no more exchange email.
Update: Ran a quadrant benchmark on my phone with this ROM, got 1299, so pretty good! I haven't removed any apps, and also added SetVsel and DroidWall. Overclocking in SetVsel was set to: 1000mhz/52 600mhz/36 300mhz/26. About the same speed as I had going in Eclair.
Missing WIpe!
There was a missing step (to Wipe all) in my instructions, sorry. It's fixed on the first post.
- In Recovery, Select Backup & Restore -> Restore > Select the rom Adlxmod F4D v2.00 folder
- Get back to the Recovery Menu, and WIPE ALL once more.
Click to expand...
Click to collapse
Hmmm, I'm not sure having both email apps installed is a good idea. Once you get past setup in either app (took about 20 tries but finally it connected to the server and completed setup), either app will both force-close as soon as they are launched. Were you actually set up an exchange account during testing of this rom?
Will give this a try, Is market working?
also can i flash the data.img from my backup to restore my apps and data?
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.