CM10.2 for Milestone2
[Downloads][Gapps]
It's based on defy(made by Quarx) version.
Changelog:
12.03.2014 - CM code synced. This is most likely the final CM10.2 build.
18.12.2013 - CM code synced
21.11.2013 - CM code synced
07.11.2013 - reverted wpa supplicant(fixes wifi tethering, wifi network list do not refresh again); torch tile added to quick settings; CM code synced
31.10.2013 - wpa supplicant updated(fixes wifi list updates); more kernel tweaks; TWRP updated; keyboard file names aligned(sholes-qwerty.kcm->sholes->keypad.kcm); CM code synced; new gapps available
23.10.2013 - Fixed baseband switching; no other changes, so don't update if you do not have problems with carrier signal
21.10.2013 - Interactive and ondemand CPU governors tweaked(Blachd0se) - this should fix battery drain in the latest build; polish keychars updated(thanks to Rabinhood; see NOTES); CM code synced
17.10.2013 - 720p recording enabled; CM code synced(Long Term Orbits(LTO) added)
10.10.2013 - Fixed(hope that this time for good) camera orientation when using custom camera apps(e.g. igcamera).
09.10.2013 - Reverted camera orientation changes(colors should be ok right now, but igcamera orientation is again incorrect-need some more time to figure this out); data transfer statistics(download/upload arrows on the wifi icon) fixed(Quarx/Blachd0se); CM code synced(resolved Settings->Buttons crash and black camera preview after taking a picture).
02.10.2013 - Fixed multitouch points number setting; Igcamera should behave ok right now; CM code synced
30.09.2013 - Added switching to horizontal mode when hardware keyboard is open; CM code synced; NOTE: you may need to add google account again after update from previous version(s), so sync/backup your google stuff.
26.09.2013 - Call recording fixed(tried with AutoCallRecorder 1.0.9 - present in some tezet's ROM's); Some more work on internal storage; CM code synced
25.09.2013 - Internal storage size fixed
24.09.2013 - Keyboard layout fixed
23.09.2013 - Camera should work ok at 848x480(720p not supported yet); CM code synced
20.09.2013 - Initial version
NOTES:
Keyboard - to access polish letters, choose Qwerty polish in Settings->Language & Input->Sholes keypad->Set up keyboard layout. Use ALT LOCK or ALT LOCK + SHIFT to get polish letters. ALT LOCK + '?' is mapped to pipe symbol('|').
If you wish to see national symbols for some other language, please download and update the following file (similarly as Rabinhood has done for polish symbols(look at letter A and ralt/shift+ralt modifiers)), test it by replacing file /system/usr/keychars/sholes-keypad.kcm with your version(reboot required), and once you are satisfied with the outcome, send it to me.
Known issues:
If bluetooth is on, and autocallrecording is installed, no sound during calls(reported by Fedroid)
Sound quality when using BT headset is not very high
Wifi list does not refresh.. workaround: turn wifi off and on
Sources:
repo init -u git://github.com/czechop/android.git -b cm-10.2
Installation
If coming from stock ROM or CM7:
install tezet's CM10 first(http://forum.xda-developers.com/showthread.php?t=1827801) and look at next point
If using tezet's CM10 ROM or engle mars's CM10.1:
go to bootmenu(press VOLUME DOWN key when booting);
choose recovery->custome recovery;
when in recovery, choose install zip from sdcard, and select the latest CM10.2 on your card;
in the same way install gapps.
reboot, and hold VOLUME DOWN button to go directly into bootmenu.
choose tools->file tools->format DATA + CACHE to ext4(note that you will loose your data(the ones on the sdcard are safe)).
reboot and... that's it
If coming from engle mars's CM10.2 ROM(haven't tried it, but should work):
go to bootmenu(press VOLUME DOWN key when booting);
choose recovery->TWRP;
when in recovery, choose install zip from sdcard, and select the latest CM10.2 on your card;
in the same way install gapps.
reboot, and hold VOLUME DOWN button to go directly into bootmenu.
choose tools->file tools->format DATA + CACHE to EXT4(note that you will loose your data(the ones on the sdcard are safe)).
reboot and... that's it
If want to get back to tezet's CM10 or engle mars's CM10.1:
go to bootmenu(press VOLUME DOWN key when booting);
choose tools->file tools->format data + cache to EXT3(not that you will loose your data(the ones on the sdcard are safe))
choose recovery->TWRP recovery
when in recovery, choose install zip from sdcard and instlall ROM you want.
in the same way install gapps(if not included in the ROM)
reboot
if something goes wrong... post here describing what's going on... there is a slight chance that someone will help you
Credits:
Credits for this rom goes to: Quarx2k, Tezet, Blachd0se, CM team... and many, many more.
czechop said:
CM10.2 for Milestone2
[Downloads][Gapps]
It's based on defy(made by Quarx) version.
Changelog:
20.09.2013 - Initial version
Known issues:
Camera is far from good
Call recording not working
Hardware keyboard might produce incorrect characters when ALT used in some languages(polish version works quite well)
Notes:
For installation instructions look at other threads
Full wipe recommended!!!
Sources:
repo init -u git://github.com/czechop/android.git -b cm-10.2
Click to expand...
Click to collapse
1. Fix camera, and it will be perfekt rom.
2. Just copy keyboard layout from CM10.2 of EngleMars.
3. Its very fast, and really nice ROM.
Bye
Faster than engle mars rom?
Can someone post photos how the rom looks like?
Good to see you back in the game, Czechop! The ROM is really great, very snappy. It seems like it is ready for daily use, but I hope you will be able to find time for future updates as well. Thanks!
---------- Post added at 08:46 PM ---------- Previous post was at 08:26 PM ----------
Just one minor issue. Keyboard layout doesn't work for me on version from 23th. I have tried with QWERTY, QWERTZ and AZERTY as well as with no keyboard layout selected at all. In all cases the characters with ALT were (totally) incorrect.
One more observation. The internal storage is only 256MB, and not 8GB. I suposse it's a leftover from Defy.
tezet said:
One more observation. The internal storage is only 256MB, and not 8GB. I suposse it's a leftover from Defy.
Click to expand...
Click to collapse
tezet is still alive! cm10.2 seems to become a really great and stable rom
you will find the qwertz keyfile attached. download and decompress it and change it, by replacing this file in system/usr/keychars and set permission to rw r r
cheers
Hey guys. I believe at least some of you have already tried this fresh ROM. Could you please share your comments? How does this ROM look like in comparison to Engle_Mars CM 10.2 in terms of performance and features? Do you think the differences make this ROM worth trying?
Thanks.
tezet said:
Good to see you back in the game, Czechop! The ROM is really great, very snappy. It seems like it is ready for daily use, but I hope you will be able to find time for future updates as well. Thanks!
---------- Post added at 08:46 PM ---------- Previous post was at 08:26 PM ----------
Just one minor issue. Keyboard layout doesn't work for me on version from 23th. I have tried with QWERTY, QWERTZ and AZERTY as well as with no keyboard layout selected at all. In all cases the characters with ALT were (totally) incorrect.
Click to expand...
Click to collapse
Hi Tezet... good to see you too You haven't posted anything for so long, that I started thinking you sold your phone and switched to some other brand. But after all, motorola is the best
Keyboard layout should be fine right now.
tezet said:
One more observation. The internal storage is only 256MB, and not 8GB. I suposse it's a leftover from Defy.
Click to expand...
Click to collapse
Haven't noticed it earlier... thanks, will have a look.
downloading the rom to test.
After I have installed'll post a print for the curious :cyclops:
To those who have installed this:
- How is battery life compared to EngleMars's 10.2?
- Can this be backed up via recovery, ie does the restore function actually work?
These are the only two areas in which EngleMars's, otherwise perfect in my opinion, ROM is lacking.
first impression: very, very similar to the ROM CM10.2 Engle_Mars.
In visual and performance ... Very stable.
Surely in the next updates will be even better.:good:
{ Internal memory showing wrong size. (~ 254mb only) }
gigabruno said:
{ Internal memory showing wrong size. (~ 254mb only) }
Click to expand...
Click to collapse
Should be fixed in the newest version
Tried to install this ROM twice (downloaded latest release twice from Google Drive), but ClockworkMod Recovery v2.5.0.8 is telling me:
E:Error in /sdcard/cm-10.2-20130925-UNOFFICIAL-milestone2.zip
(Status 0)
Installation aborted.
Am I doing something wrong? I don't see any installation instructions in the OP except "For installation instructions look at other threads" which doesn't help someone who isn't used to doing this sort of thing at all... I searched and found tezet's instructions for stock ROM users installing his CM10 release... they are as follows:
Installation guide for stock roms users
1) Root your phone (you may use SuperOneClick root method)
2) Install Droid2 Bootstrap Recovery
3) Open Droid2 Bootstrap Recovery and tap "Bootstrap Recovery", then "Reboot Recovery" granting root privileges. The phone should reboot into recovery. Use volume buttons to navigate, camera button to accept, power button to go back. You will install files by selecting "Install zip from sdcard".
4) Optionally: create a backup of your data
5) Install latest CM ROM image file.
6) Optionally: install Google Apps
7) Select "Wipe data/factory reset"
8) Reboot and enjoy
9) Optionally: select baseband version corresponding to your country and BPSW version
Click to expand...
Click to collapse
Is that not correct? I'm stuck at step 5 as CWM seemingly won't accept the .zip file I've downloaded (twice, to be sure I didn't get a corrupted download). So far I've only ever loaded SBF files using RSDLite (stock UK 2.3.4), so I'm sure I must be doing something wrong... A little help?
Thanks
As it is not mentioned anywhere, am I correctly assuming that Bluetooth is working flawlessly?
I'm excited to try this but BT is crucial!
Have you tried the "TWRP Recovery"?
xyphur said:
Tried to install this ROM twice (downloaded latest release twice from Google Drive), but ClockworkMod Recovery v2.5.0.8 is telling me:
E:Error in /sdcard/cm-10.2-20130925-UNOFFICIAL-milestone2.zip
(Status 0)
Installation aborted.
Am I doing something wrong? I don't see any installation instructions in the OP except "For installation instructions look at other threads" which doesn't help someone who isn't used to doing this sort of thing at all... I searched and found tezet's instructions for stock ROM users installing his CM10 release... they are as follows:
Is that not correct? I'm stuck at step 5 as CWM seemingly won't accept the .zip file I've downloaded (twice, to be sure I didn't get a corrupted download). So far I've only ever loaded SBF files using RSDLite (stock UK 2.3.4), so I'm sure I must be doing something wrong... A little help?
Thanks
Click to expand...
Click to collapse
Flash Bootmenue with cwm3 first, out of your cwm2 (its the bootstrap recovery)
After that, boot into cwm3 and flash cwm5.
Now boot into cwm5 and flash the rom zip.
Here are the files you will need: http://www.mediafire.com/folder/1p23cv7r38491aq,nteg1stu575rjde/shared
gigabruno said:
Have you tried the "TWRP Recovery"?
Click to expand...
Click to collapse
I haven't yet, no. Of course, that may be because I was completely unaware of its existence, probably because most of these ROM release threads expect everyone reading them to know the ins and outs already... quite frustrating.
Is "TWRP 2.1.1" the latest available? Should I attempt to use that?
Appreciate the help btw...
---------- Post added at 08:43 AM ---------- Previous post was at 08:37 AM ----------
lulli1 said:
Flash Bootmenue with cwm3 first, out of your cwm2 (its the bootstrap recovery)
After that, boot into cwm3 and flash cwm5.
Now boot into cwm5 and flash the rom zip.
Click to expand...
Click to collapse
That seems.... exceptionally convoluted, lol... I'll give it a try though. Thanks for the link.
---------- Post added at 09:12 AM ---------- Previous post was at 08:43 AM ----------
lulli1 said:
Flash Bootmenue with cwm3 first, out of your cwm2 (its the bootstrap recovery)
After that, boot into cwm3 and flash cwm5.
Now boot into cwm5 and flash the rom zip.
Click to expand...
Click to collapse
Okay, got CWM3 loaded, rebooted, CWM3 booted on its own. Then I loaded CWM5... took me a few tries, but I finally remembered how to enter the recovery menu... tried to load the ROM zip, now it says:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
...should I also have downloaded the matching .md5 file from OP's Google Drive link?
Also, I held 'X' during power-up, waited for the android exclamation logo, then hit vol down/vol up and got the blue text recovery menu titled "Android system recovery (3e)" is this correct? Or am I sitting in the stock recovery menu instead of CWM5? Sorry, I've forgotten much of this, it's been forever since last time...
---------- Post added at 09:45 AM ---------- Previous post was at 09:12 AM ----------
Okay, so it looks like CWM5 didn't flash... according to google searches, I should be staring at a recovery menu where Clockworkmod Recovery 5 is prominently displayed at the top... instead, as I outlined above, I'm seeing "Android system recovery (3e)" which sounds to me like I'm looking at the stock one...
What exactly should I be doing to load CWM5 from CWM3? The menus are completely different between CWM2 & CWM3, and once CWM5 is loaded/flashed, I can't seem to get into it... booting recovery simply reverts to whatever the (3e) menu is...
See what I meant about it sounding convoluted now? lol, yeah...
xyphur said:
Okay, got CWM3 loaded, rebooted, CWM3 booted on its own. Then I loaded CWM5... took me a few tries, but I finally remembered how to enter the recovery menu... tried to load the ROM zip, now it says:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
...should I also have downloaded the matching .md5 file from OP's Google Drive link?
Also, I held 'X' during power-up, waited for the android exclamation logo, then hit vol down/vol up and got the blue text recovery menu titled "Android system recovery (3e)" is this correct? Or am I sitting in the stock recovery menu instead of CWM5? Sorry, I've forgotten much of this, it's been forever since last time...
---------- Post added at 09:45 AM ---------- Previous post was at 09:12 AM ----------
Okay, so it looks like CWM5 didn't flash... according to google searches, I should be staring at a recovery menu where Clockworkmod Recovery 5 is prominently displayed at the top... instead, as I outlined above, I'm seeing "Android system recovery (3e)" which sounds to me like I'm looking at the stock one...
What exactly should I be doing to load CWM5 from CWM3? The menus are completely different between CWM2 & CWM3, and once CWM5 is loaded/flashed, I can't seem to get into it... booting recovery simply reverts to whatever the (3e) menu is...
See what I meant about it sounding convoluted now? lol, yeah...
Click to expand...
Click to collapse
reboot/turn on your device, press vol-down button while blue LED blink and choose recovery, then custom recovery. now you can install rom or cwm5.
henediac said:
reboot/turn on your device, press vol-down button while blue LED blink and choose recovery, then custom recovery. now you can install rom or cwm5.
Click to expand...
Click to collapse
Got into CWM5 finally via the bootmenu... the CWM5 .zip file that was linked to earlier by lulli1 is "CyanogenDefy Recovery v5.0.3.4-jordan" if that matters.
It's still not accepting the latest release of this ROM though (25.09.2013), keeps claiming the following:
...
E:Error in /sdcard/cm-10.2-20130925-UNOFFICIAL-milestone2.zip
(Status 0)
Installation aborted.
Obviously there's something wrong somewhere... has anyone else successfully installed latest version?
This is really starting to frustrate me...
Maybe I should attempt TWRP method?
Thanks for the pointer abut vol down during blue LED... that's what I had forgotten and why I kept seeing the stock recovery menu. :S
---------- Post added at 11:40 AM ---------- Previous post was at 11:16 AM ----------
Just verified the MD5 hash for the heck of it. File checks out OK.
Any ideas?
Related
[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?
This is gweedo767's touch recovery ported to the skyrocket/hercules. Because many people have been asking me what the difference between this one and the version that koush put out here is the difference:
This one is open source.
This one has swipe gestures (up,down,left,right)
This one has different UI settings
This one has soft keys on the bottom of the screen
This one has 2 different options of font
Here is a youtube video I made of how it works: ------> VIDEO
4 ways to use recovery:
volume rockers
soft keys on bottom of screen
capacitive buttons
swipe gestures (up/down = scroll && left = back && right = select)
HOW TO INSTALL:
CWMR5504_INSTALL-4.3.zip (NEW ICS BACKGROUND): ---------> BLUE-FONT
CWMR5504_INSTALL-4.3.zip (NEW ICS BACKGROUND): ---------> ROBOTO-FONT
- Just flash in CWM
Click to expand...
Click to collapse
TERMINAL INSTALL:
recovery.img: (NEW ICS BACKGROUND) ----------------> BLUE-FONT
recovery.img: (NEW ICS BACKGROUND) ----------------> ROBOTO-FONT
- download to sdcard
- open terminal emulator (or adb) type:
Code:
$ su
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22 bs=4096
Click to expand...
Click to collapse
Odin Install
recovery.tar.md5 (NEW ICS BACKGROUND): ---------> BLUE-FONT
recovery.tar.md5 (NEW ICS BACKGROUND): ---------> ROBOTO-FONT
Click to expand...
Click to collapse
Test Drive:
CWMRT5504_TEST-4.3.zip(NEW ICS BACKGROUND): -------------------> BLUE-FONT
CWMRT5504_TEST-4.3.zip(NEW ICS BACKGROUND): -------------------> ROBOTO-FONT
(This will not alter ANY files on your phone. It is just a test drive basically. You flash it through ClockworkMod that you have already installed and it runs over it showing you how it would be if you did install it. Once you reboot you will still have the same recovery that you had.)
Click to expand...
Click to collapse
v1:
Code:
- Initial release
v2:
Code:
- fixed "back button disabled/enabled" when scrolling past top to bottom
- 2 different font versions (roboto and normal)
-- roboto font is a little bigger
- complete fix of adb and usb mounting
v2.5:
Code:
- added a cool new ICS background! (thanks CyanmodICS for the idea)
- added green/red font versions
- cleaned up the code a bit
v3:
Code:
- in process of fixing hanging backup issue (need extensive list of apps people have installed when having issue)
- fixed ALOT of bugs
- added many more options for internal/external sdcard
- more....(i cant remember)
- i will add the other color options back in a few days
v3.5
Code:
- fixed recovery.fstab to mount internal sdcard as /sdcard to recognize .hidenandroidprogress file
- ascii art???
v4.0
Code:
- fixed the fix_permissions not working (thanks minotauri)
- fixed sd-ext and .android_secure errors in backup
v4.1
Code:
- re-arranged order of "install from internal/external sdcard" to put internal first
- added "Reboot Recovery" option to the bottom of the advanced menu
- a few code cleanups
v4.2
Code:
- fixed bug where background would reset to blank black after installing a zip/backing up/restoring
- added option to reboot into download mode in advanced>>reboot download mode
v4.3
Code:
- hopefully fixed the hanging backup bug once and for all
- merged all of CWM's latest code changes
Thanks to:
Code:
gweedo767
plastikman
utkanos
romracer
Thanks! I guess i'll be the first tester, to make sure i don't get bricked or anything
Badass!!! Guess I be tester number 2 haha
Sent from my Desire HD using xda premium
Sweet. Flashing now
Sent from my SAMSUNG-SGH-I727 using xda premium
so i created a recovery.tar.md5 to flash through odin. I flashed it and it automatically booted back into android. Once i rebooted into recovery everything worked in there but when i tried to reboot it would only reboot back into recovery. i did a battery pull and waited a few minutes but it only booted into clockworkmod. I had to flash the original clockworkmod 5.5.0.2 i had before to be able to boot back into android. anyone have any ideas on why it gets stuck in a clockworkmod boot loop?
this is only for the recovery.tar.md5...not for the cwmrt5504.zip. just wanted to clarify that. the .zip file is completely safe and will not alter any files on your device when you flash it.
How's the cwm working
Sent from my SAMSUNG-SGH-I727 using xda premium
the zip file seems to work fine. restored a red sonja backup, then flashed another to try it out more. all went well.
so to everyone who has tried it out:
how do you feel about the sensitivity on the swipe gestures? up/down sensitivity? left/right sensitivity? does the sensitivity need to be lowered or raised or stay the same?
thanks
so will this be an actual new recovery or an overlay of type for our current cwm
Sent from my SAMSUNG-SGH-I727 using xda premium
im going to create a recovery.tar.md5 that is flashable via Odin and will be a whole new recovery. but the one i have now gets stuck in a boot loop that only boots into recovery.
Problem with Scrolling...
For me obviously noticed the colours as well noticed that when I pushed Volume increase menu scrolled down and when I pushed Volume Decrease menu scrolled up. Anyone else get that issue... overall what is the difference between this and the other clockworkmod recovery... basically what is the benefit to flashing this over flashing the one that comes with ROM Manager....
Weird when I restarted my phone and went back into recovery it went back to CWM 5.0.2.7 is that what it's supposed to do?
i hadnt checked the volume rocker mappings yet. ill fix that. i just havent used anything but the swipe gestures.
the difference between this and the original one is that you do not need to touch any buttons. you swipe your finger up and down to scroll and swipe left to go back and swipe right to select. and there are the soft buttons on the bottom of the screen. basically there are 4 ways to move around and select and go back.
1.) volume rockers
2.) swipe gestures
3.) soft keys
4.) capacitive buttons
and i explained in the OP that it was a fakeflash. which means that it does not install it on your phone. thats the reason why you booted back into your original clockworkmod. i have an installable version but it is not ready yet. i do not want to release it yet because it could mess up your device.
My Bad... I missed the fake flash... that's why you should read the entire comment I guess LOL... Anyways awesome thanks for the quick reply.
no problem. ive done that before. usually its when i get really excited about a new rom and i download it without reading the whole post and then something doesnt work with it and i get frustrated and realize they have a patch in the OP or something. haha
anyways, once i get the boot loop problem fixed i will make a recovery.tar.md5 that you can just flash in Odin and itll be an entirely new recovery installed
i updated the file on my box.com account with the correct volume rocker key mappings.
So this is the same CWM just a touch screen version... aren't we using a version of CWM that is made for the regular galaxy s2? Isn't that why there are tons of problems with FC's because this CWM does not delete everything it is suppose to and we end up having to install the stock recovery to do a factory reset?
well this is the latest clockworkmod 5.5.0.4. the only other CWM i can find is 5.0.2.7. so its updated. not sure what the changelog is on that though. And this isnt a version that was made for the gs2. it was originally made for the galaxy nexus. Im pretty sure its the same source code as the code from the cm9 repo. Im not 100% sure on that though. ill have to ask gweedo.
and ive been using this recovery for about a week and have backed up/restored/flashed new roms/reset to factory/erase cache/dalvik all a few times and havent had any issues with it not deleting everything.
I have to ask, have you figured out what's up with the colors? They could hurt your eyes if you looked at it too long. xD
Also note, which is something that's also been an issue with the current CWM, Fix Permissions doesn't do a thing. Press it and it instantly tells you it's done. Should at least take a minute to get everything done. Just wanted to mention that this problem still exists. Definitely not at all any kind of dealbreakef, but I just don't get why any ports have worked for our devices.
Sent from my SAMSUNG-SGH-I727 using xda premium
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.
Team Win Recovery Project 2.8, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
For official change logs, see here:
http://teamw.in/project/twrp2
For recent code merges, see the Omnirom gerrit here:
https://gerrit.omnirom.org/#/q/proje...+status:merged
______________________________________
Download flashable TWRP 2.8.1.1 zip for TF101:
signed_twrp-2.8.1.1_tf101.zip
TWRP 2.8.1.1 MD5 sum for TF101:
signed_twrp-2.8.1.1_tf101.zip.md5
______________________________________
Download flashable TWRP-2.8.1.1 zip for TF101G:
signed_twrp-2.8.1.1_tf101g.zip
TWRP-2.8.1.1 MD5 sum for TF101G:
signed_twrp-2.8.1.1_tf101g.zip.md5
______________________________________
Download flashable TWRP 2.8.1.1 zip for SL101 Slider:
signed_twrp-2.8.1.1_sl101.zip
TWRP 2.8.1.1 MD5 sum for SL101 Slider:
signed_twrp-2.8.1.1_sl101.zip.md5
____________________________________
If experiencing any boot loops or you don't see the blue-green flash progress bar after you thought you just flashed a recovery, then try the suggestions from this post:
http://forum.xda-developers.com/showpost.php?p=46806749&postcount=187
concerning dd methods to clear a stuck flag and maybe flash a recovery blob if other methods aren't working for you, particularly if you attempted to use ROM Manager or certain versions of CWM or other programs to flash this recovery.
____________________________________
Credits:
Team Win Recovery Project
josteink for tf101 device tree
timduru for tf101 device tree
josteink for tf101 kernel source
OmniROM for Android 4.4.2 base
Google for Android AOSP
Anyone else who previously contributed to this.
In particular, many thanks to josteink who encouraged this and provided much useful information to get it going.
For more information:
http://teamw.in/project/twrp2
TWRP Screenshots
Latest screen shots from TWRP:
{
"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"
}
TWRP Custom Themes [10-10-2013]
I will use this post to post links to custom TWRP themes, both my own and any that users would like to provide me the links to in a PM. This first one is my first attempt at TWRP theming and is just a pretty basic, modified stock theme. It is based on the stock theme for 1280x800 devices. I know everyone won't like it, but it is my first stab at it. Have fun and if anyone would like some instructions for creating a custom theme, then hit me up with a PM and I'll try to help. It is not really difficult, just time consuming and tedious work. There are also links to guides on the twrp site for theming.
Instructions:
Just download, reboot to recovery (you are running TWRP recovery?), flash the theme zip file, reboot, and reboot to recovery again to see the results.
[EDIT] Here's a second one for you:
sidneyk-theme2.zip download link:
https://dl.dropboxusercontent.com/u/47619656/sidneyk-theme2.zip
sidneyk-theme2.zip.md5 download link:
https://dl.dropboxusercontent.com/u/47619656/sidneyk-theme2.zip.md5
[EDIT] Here are some screenshots taken with my camera, as I don't know any other way to get them right now:
##########################
sidneyk TWRP custom theme zip download:
https://dl.dropboxusercontent.com/u/47619656/sidneyk-theme.zip
sidneyk-theme MD5 sum:
https://dl.dropboxusercontent.com/u/47619656/sidneyk-theme.zip.md5
Reserved #3
Awesome thanks a lot. I was wondering if you can do titanium custom zips with twrp? It seems i was not able to previously. Like flashing a user app or titanium itself?
Installed perfect!! Now waiting for KatKiss 4.3 v021
Thx for continuing to keep our beloved tf alive!!
Sent from my Transformer TF101 using XDA Premium 4 mobile app
YayYouFixedIt said:
Awesome thanks a lot. I was wondering if you can do titanium custom zips with twrp? It seems i was not able to previously. Like flashing a user app or titanium itself?
Click to expand...
Click to collapse
I never had much luck with titanium zips myself. I'll have to give it a try sometime.
Sent from my SAMSUNG-SGH-T769 using XDA Premium HD app
Thanks for taking this over man! Flashed it and it works perfeclty. Did a backup, full wipe, restore and it had no issues.
Is there anyway to have this app recognize the USB port (with a thumb drive) that's built into the keyboard attachment ?
Good jeez I need a third job just for donations! This is outstanding work man. Made a backup all good last night, and installing, wiping, fix perms seems work all fine for me as well. Thank you so very much for continue support in this awesome tab
~S-Off LTEvo; Back on the Always Solid Viper4G Latest; Expletive Deleted Kernel
cpu0/1: 1.5ghz ¦ 384mhz ¦ sleep: 486mhz max
Ondemand
fiops
thermald: dynamic
With tapatalk4
Hey all,
I've got a small problem with this version of TWRP 2.6.1.0 that was not present in any of the previous version I've used. The problem is each time I use this version no matter what function is preformed (all works fine) when it comes to restart the system I am presented with the following screen:
*********************************************
*********************************************
Fix Superuser Permissions?
Root permissions appear to be lost.
Fix root permissions now?
(Fixes permissions on su binary & app)
<Do Not Fix>
>> Swipe to fix Root >>
*********************************************
*********************************************
I've have cleaned SurerSU on system and reinstalled it with no errors, but did not work.
I've downgraded to 2.6.0.0 but still not worked.
I've restored from a working Nandroid Backup but no joy (TWRP 2.5.0.0) and no more permission screens.
Any idea what is going on???
worf105 said:
Hey all,
I've got a small problem with this version of TWRP 2.6.1.0 that was not present in any of the previous version I've used. The problem is each time I use this version no matter what function is preformed (all works fine) when it comes to restart the system I am presented with the following screen:
*********************************************
*********************************************
Fix Superuser Permissions?
Root permissions appear to be lost.
Fix root permissions now?
(Fixes permissions on su binary & app)
<Do Not Fix>
>> Swipe to fix Root >>
*********************************************
*********************************************
I've have cleaned SurerSU on system and reinstalled it with no errors, but did not work.
I've downgraded to 2.6.0.0 but still not worked.
I've restored from a working Nandroid Backup but no joy (TWRP 2.5.0.0) and no more permission screens.
Any idea what is going on???
Click to expand...
Click to collapse
I've only ever seen anything about reinstalling supersu after I've formatted data ( and factory reset ) and am getting ready to reboot, as suggested, because, of course, I've just wiped it out and have no OS or anything installed. I've said yes and I've said no, without any issues either way, but that was previous versions and not this particular one. Maybe your root really was messed up? There was supposedly an updated supersu included in this version or 1 back I believe according to the change logs.
the.teejster said:
Is there anyway to have this app recognize the USB port (with a thumb drive) that's built into the keyboard attachment ?
Click to expand...
Click to collapse
Did it work with any previous versions? I've not made any changes that would affect that functionality one way or the other, so if it worked before it should work now, if it didn't then it probably still won't.
sidneyk said:
I've only ever seen anything about reinstalling supersu after I've formatted data ( and factory reset ) and am getting ready to reboot, as suggested, because, of course, I've just wiped it out and have no OS or anything installed. I've said yes and I've said no, without any issues either way, but that was previous versions and not this particular one. Maybe your root really was messed up? There was supposedly an updated supersu included in this version or 1 back I believe according to the change logs.
Click to expand...
Click to collapse
Thanks sidneyk :good:
My root still functions flawlessly when using my TF101 no matter if I select Yes fix or No to the fix at reboot system. I now have restore the nandroid back up for earlier today as I have loads of changes that are not on my later backup. Now to look where ive found the download link to twrp2.5-tf101-unofficial.beta which works flawlessly
Cheers
worf105
worf105 said:
Thanks sidneyk :good:
My root still functions flawlessly when using my TF101 no matter if I select Yes fix or No to the fix at reboot system. I now have restore the nandroid back up for earlier today as I have loads of changes that are not on my later backup. Now to look where ive found the download link to twrp2.5-tf101-unofficial.beta which works flawlessly
Cheers
worf105
Click to expand...
Click to collapse
Sorry you had a bad experience with it. Did you also download the md5 file to verify a good download?
worf105 said:
Thanks sidneyk :good:
My root still functions flawlessly when using my TF101 no matter if I select Yes fix or No to the fix at reboot system. I now have restore the nandroid back up for earlier today as I have loads of changes that are not on my later backup. Now to look where ive found the download link to twrp2.5-tf101-unofficial.beta which works flawlessly
Cheers
worf105
Click to expand...
Click to collapse
2.5.0.0 download is in the 2.6.0.0 (joesteink's) thread.
frederuco said:
2.5.0.0 download is in the 2.6.0.0 (joesteink's) thread.
Click to expand...
Click to collapse
Thanks, found it :good:
---------- Post added at 01:31 PM ---------- Previous post was at 01:10 PM ----------
sidneyk said:
Sorry you had a bad experience with it. Did you also download the md5 file to verify a good download?
Click to expand...
Click to collapse
Now even 2.5.0.0 is doing the same.
I have now since done the following:
Wiped Cache, Dalvik cache and System,
Flashed KatKiss 4.3 r2.2 #20 ROM'
Flashed Gapps,
Flashed KatKernel 107b,
Flashed TWRP 2.6.1.0,
Wiped Cache & Dalvik Cache
Rebooted with no fix root permission screen,
Rebooted in to recovery, (2.6.1.0)
Deleted older Nandroid Backups,
Created new Nandroid Backup,
when finished creating new backup I am now presented with the fix superuser permission screen,
Swiped to fix superuser,
Reboots and root works fine, (opened up SuperSU v1.60 and no error or updates to binary required, Opened Root Checker Basic v5.0.6 by Joes Krim and verified root access with no errors.)
Rebooted into recover again,
Fixed Permission's (Successful)
selected Reboot button and still taking to the Fix Superuser Permission screen again so Swiped to Fix and TF101 reboots with no screen output,
Again check if root is OK on system, which it is,
Reboot to Recovery again and when in recovery I select reboot then system,
Presented with the Fix Superuser Premission screen again so I select Do Not Fix,
Reboot to system to verify Root which is OK,
Reboot into Recovery for the last time and selected reboot then system which brings up the Fix Superuser screen again,
Swiped to fix, system reboots OK and user (me) gives up
Any Ideas
worf105 said:
Thanks, found it :good:
---------- Post added at 01:31 PM ---------- Previous post was at 01:10 PM ----------
Now even 2.5.0.0 is doing the same.
I have now since done the following:
Wiped Cache, Dalvik cache and System,
Flashed KatKiss 4.3 r2.2 #20 ROM'
Flashed Gapps,
Flashed KatKernel 107b,
Flashed TWRP 2.6.1.0,
Wiped Cache & Dalvik Cache
Rebooted with no fix root permission screen,
Rebooted in to recovery, (2.6.1.0)
Deleted older Nandroid Backups,
Created new Nandroid Backup,
when finished creating new backup I am now presented with the fix superuser permission screen,
Swiped to fix superuser,
Reboots and root works fine, (opened up SuperSU v1.60 and no error or updates to binary required, Opened Root Checker Basic v5.0.6 by Joes Krim and verified root access with no errors.)
Rebooted into recover again,
Fixed Permission's (Successful)
selected Reboot button and still taking to the Fix Superuser Permission screen again so Swiped to Fix and TF101 reboots with no screen output,
Again check if root is OK on system, which it is,
Reboot to Recovery again and when in recovery I select reboot then system,
Presented with the Fix Superuser Premission screen again so I select Do Not Fix,
Reboot to system to verify Root which is OK,
Reboot into Recovery for the last time and selected reboot then system which brings up the Fix Superuser screen again,
Swiped to fix, system reboots OK and user (me) gives up
Any Ideas
Click to expand...
Click to collapse
You can't flash TWRP together with a ROM as flashing TWRP will overwrite the staging partition and the ROM's kernel will then not get flashed. So first flash your ROM, gapps and katkernel, then reboot into your rom, then reboot into recovery to flash TWRP, then reboot again.
sidneyk said:
Did it work with any previous versions? I've not made any changes that would affect that functionality one way or the other, so if it worked before it should work now, if it didn't then it probably still won't.
Click to expand...
Click to collapse
Ye it work great when running 2.5.0.0, no errors
worf105
---------- Post added at 01:49 PM ---------- Previous post was at 01:47 PM ----------
jrohwer said:
You can't flash TWRP together with a ROM as flashing TWRP will overwrite the staging partition and the ROM's kernel will then not get flashed. So first flash your ROM, gapps and katkernel, then reboot into your rom, then reboot into recovery to flash TWRP, then reboot again.
Click to expand...
Click to collapse
Ok Thanks will flash on that order and remember it in future, will get back to you as I've done it with results. :good:
cheers
worf105
---------- Post added at 02:18 PM ---------- Previous post was at 01:49 PM ----------
worf105 said:
Ye it work great when running 2.5.0.0, no errors
worf105
---------- Post added at 01:49 PM ---------- Previous post was at 01:47 PM ----------
Ok Thanks will flash on that order and remember it in future, will get back to you as I've done it with results. :good:
cheers
worf105
Click to expand...
Click to collapse
Done what you said but no joy. When I swipe to fix superuser it reboots that quickly it looks as if it doesn't have time to fix the problem before it reboots
sidneyk said:
Did it work with any previous versions? I've not made any changes that would affect that functionality one way or the other, so if it worked before it should work now, if it didn't then it probably still won't.
Click to expand...
Click to collapse
it didnt work before.
[RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [/B]
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
coral Device Config: https://github.com/bigbiff/android_device_google_coral
A11 Testing:
https://build.twrp.me/test/coral/twrp-3.5.0-0-test1-coral.img
Please test and let me know if anything isn't working.
DOWNLOAD:
Please go to https://twrp.me to download the recovery image.
Old info:
Hello, this is a test build for coral users (will work on crosshatch/blueline later).
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up.
TWRP seems to be pretty stable now as of test 5. Missing features include adb sideload and repacking recovery which I will be working on in the upcoming months. Android 11 will be supported when stable APIs have been release and we have time to update to that release.
June FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test1-coral.img
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test4-coral.img
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test5-coral.img
- fix restoring of persist partition
- fix restoring of super partition
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test6-coral.img
- allow repacking of TWRP from boot.img
- magisk not working currently on repacked image
August FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test7-coral.img
August FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test8-coral.img
- fix repacking magisk with TWRP
- Credit to @Freak07 https://github.com/freak07/FLORAL - using his kernel as a base for Coral/Flame TWRP
http://twrp.me
What to backup
* super
* data
* persist
* boot
* any other partition desired
What to restore
* super
* data
* boot - depending on ROM support
Please just restore persist if you have a failed partition. I do not recommend restoring backups from phone to phone unless you know what you are doing.
These devices do not have a recovery partition. You will not be able to flash the img file directly to the phone. Make sure you use fastboot boot to temporarily boot TWRP and use adb to push it to the /sdcard folder for repacking.
Repacking TWRP into Boot partition
To repack TWRP into the boot partition to override stock recovery when rebooting to recovery, perform the following steps
1. adb push <latest_twrp_boot.img> /sdcard/
2. reboot to bootloader and fastboot latest boot.img of TWRP
3. Go to Install
4. Select your TWRP boot.img from /sdcard
5. Touch Install Image Recovery Ramdisk
6. Swipe to confirm flash
7. Reboot to recovery and android to verify installation
Glad to see this!
Finally TWRPified! Thanks for bringing this to us!
bigbiff said:
[RECOVERY] TWRP 3.4.0-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
coral Device Config: https://github.com/bigbiff/android_device_google_coral
DOWNLOAD:
Hello, this is a test build for coral users (will work on crosshatch/blueline later). I was hoping adventurous people would try this fastbootable image out for testing.
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up. Will check back later to see feedback. Don't try if you are unable to reset back to stock. Only try if you are curious to kick the tires.
June FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test1-coral.img
http://twrp.me
Click to expand...
Click to collapse
When trying to boot the image it gets stuck on the TWRP flash screen. I'm on a rooted custom rom. Sorry to sound stupid if I'm missing something obvious.
Daisymae said:
When trying to boot the image it gets stuck on the TWRP flash screen. I'm on a rooted custom rom. Sorry to sound stupid if I'm missing something obvious.
Click to expand...
Click to collapse
Same here ?
I'm stuck on splash screen as well, but I'm gonna try to push this thread in a more helpful direction with a detailed description and a logcat:
I'm on June radio/bootloader, running AOSiP, rooted with Magisk, build # QQ3A.200605.001
Here's the logcat of stuck @ splash
https://pastebin.com/sAMURQKw
If anything else you need tested or logged please don't be shy to tag me - I'm excited to see TWRP making its way here and I know it's been hard work. Hope the log helps and will gladly take more if it doesn't show the pertinent info you need.:good:
I'll follow in Wrong Ways example.
Build: du_coral-userdebug 10 QQ3A.200605.002.A1 eng.surge.20200605.155815 release-keys
Probs wont do much more than this for now. But figured id upload to help the cause
Few things I thought I might add.
-manually adding libion.so to /system/lib64 allows you to get further but then it requests libandroidicu.so which is an apex/android runtime lib which isn't available since system isn't mounted
-toybox missing pigz always shows up
Surge1223 said:
I'll follow in Wrong Ways example.
Build: du_coral-userdebug 10 QQ3A.200605.002.A1 eng.surge.20200605.155815 release-keys
Probs wont do much more than this for now. But figured id upload to help the cause
Few things I thought I might add.
-manually adding libion.so to /system/lib64 allows you to get further but then it requests libandroidicu.so which is an apex/android runtime lib which isn't available since system isn't mounted
-toybox missing pigz always shows up
Click to expand...
Click to collapse
Thanks for the logs, I am working on getting our relink process working better so I hope to get that done soon to get all the built objects into the right space.
Apex files should be mounted and available before the decryption process happens. init is then configured to use these apex libraries for loading. It works locally but not on your pixels for some reason.
Can you post the results of mount -v?
Here is a new test image as well, I verified it on my own coral and it decrypted with pin: https://build.twrp.me/test/coral/twrp-3.4.0-0-test2-coral.img
Also this image is fastboot only. I need to work on installing into the ramdisk.
bigbiff said:
Thanks for the logs, I am working on getting our relink process working better so I hope to get that done soon to get all the built objects into the right space.
Apex files should be mounted and available before the decryption process happens. init is then configured to use these apex libraries for loading. It works locally but not on your pixels for some reason.
Can you post the results of mount -v?
Here is a new test image as well, I verified it on my own coral and it decrypted with pin: https://build.twrp.me/test/coral/twrp-3.4.0-0-test2-coral.img
Also this image is fastboot only. I need to work on installing into the ramdisk.
Click to expand...
Click to collapse
Sure, no problem. logs attached
Surge1223 said:
Sure, no problem. logs attached
Click to expand...
Click to collapse
Thanks, did you try test2?
bigbiff said:
Thanks, did you try test2?
Click to expand...
Click to collapse
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
bigbiff said:
Thanks, did you try test2?
Click to expand...
Click to collapse
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Surge1223 said:
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Click to expand...
Click to collapse
Boggling my mind that it works on my coral with out linking issues.
Can you post the results of getprop please?
Surge1223 said:
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Click to expand...
Click to collapse
It might be something funky happening with qsecomd starting up. There is a whole orchestration of steps that might cause an issue unfortunately. Until we get things ironed out you might have to wipe via stock recovery a few times. I assume by splash you mean the white G screen?
bigbiff said:
It might be something funky happening with qsecomd starting up. There is a whole orchestration of steps that might cause an issue unfortunately. Until we get things ironed out you might have to wipe via stock recovery a few times. I assume by splash you mean the white G screen?
Click to expand...
Click to collapse
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------
Surge1223 said:
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
Click to expand...
Click to collapse
Wait did you want getprop while in recovery or booted?
Surge1223 said:
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------
Wait did you want getprop while in recovery or booted?
Click to expand...
Click to collapse
Sorry, I would like it executed in recovery. I want to try and find out why it seems as when apex libraries are mounted, they do not seem to be added to the library search path in init.
Since some of the decryption programs don't find libion.so, they cannot start up.
bigbiff said:
Sorry, I would like it executed in recovery. I want to try and find out why it seems as when apex libraries are mounted, they do not seem to be added to the library search path in init.
Since some of the decryption programs don't find libion.so, they cannot start up.
Click to expand...
Click to collapse
heres getprop
https://hastebin.com/eluqagolub.md
heres list of files in /system/lib64
https://hastebin.com/uqoxuheqef.pl
Got some $$ coming your way Monday OP.
Thank you for this. It could not have been easy
@bigbiff,
i tested the test2 img, too and i have the same result as wrongway213 and Surge1223. It hangs on the twrp Splash Screen.
I'm on AOSiP Official (no Gapps) from june (=> latest build) so my factory image is on june, too (i don't know which slot is active atm).
Just a theory: Can it have to do with the fact that on the other slot is still the old AOSiP build with may factory image installed? Mayby this makes a crash on the decryption. I'm not a dev so it's just a assumption.
If you need logs i'm glad to give them to you but i know only the logcat from adb. So for more i would need guides/help.
dhacke said:
@bigbiff,
i tested the test2 img, too and i have the same result as wrongway213 and Surge1223. It hangs on the twrp Splash Screen.
I'm on AOSiP Official (no Gapps) from june (=> latest build) so my factory image is on june, too (i don't know which slot is active atm).
Just a theory: Can it have to do with the fact that on the other slot is still the old AOSiP build with may factory image installed? Mayby this makes a crash on the decryption. I'm not a dev so it's just a assumption.
If you need logs i'm glad to give them to you but i know only the logcat from adb. So for more i would need guides/help.
Click to expand...
Click to collapse
No, it seems to be related to trying to load libion.so from apex images. Can you post a URL to the exact build you are using? I can test it on flame locally.