ONLY FOR DEVELOPERS
It is possible to install open recovery using XT720 method. It did not overwrite tenfars recovery. Did not work if you use FROYO ROM. White screen with and without usb debugging
http://modmymobile.com/forums/563-m.../531599-open-recovery-v1-46-11-21-2010-a.html
I can boot into openrecovery. (can test it with 2.51 rom)
!!!!! Need fix for select key !!!!!
Maybe with openrecovery it is possible to backup / restore the bootloader. (maybe a fix for downgrade from defy 2.51 rom)
openrecovery supports ADB.
Could somebody help to modify openrecovery?
How to install:
Download attached file
1) Unpack the "OpenRecovery" folder and "OpenRecovery.zip" to the root folder of the sdcard.
2) Open adb shell or Terminal and (ensure that the phone isn't in Memory Card mode in USB connection):
Code:
Code:
su
cp /sdcard/OpenRecovery/orbootstrap/install_script.sh /tmp
chmod 755 /tmp/install_script.sh
/tmp/install_script.sh STR
Usage
1) you can reboot by typing "reboot openrecovery" to shell
2) If no error occurs, you're now in Open Recovery. If error occurs you're in Open Recovery Lite.
Walter, the Tenfar Recovery we use is based on this Open Recovery. If i remember Tenfar also uses the same.
It has already been modified to suit Defy. Correct me if I am wrong.
Good to see you back to work though
If a non-technical guy like me might suggest. We need something like this to be able to flash any sbf http://modmymobile.com/forums/564-m...112-new-sbf-flash-only-rootable-recovery.html
chaihg said:
Walter, the Tenfar Recovery we use is based on this Open Recovery. If i remember Tenfar also uses the same.
It has already been modified to suit Defy. Correct me if I am wrong.
Good to see you back to work though
Click to expand...
Click to collapse
That right, but with tenfars recovery i can`t backup bootloader.
My biggest problem is since i update to 2.51. i can`t use system dumps to build new roms. With 2.21. and 2.34. it was no problem to build a small update.zip with system dump and it boots. But since 2.51. it doesn`t work any more.
News:
Openrecovery works on Defy with 2.51 rom!!!
how can we help?
Can I install the file without destroing my phone?
I would like to help you downgrading your bootloader
Tenfar is based off ClockWork Recovery, that is not Open Recovery. Unless they are the same, which I think not .
Walter, despite the keyboard bug, any other major bug?
Ok, recovery boots.
Volup and down works but Key for select is set to camera key. How can i change it to Power buttom?
Come on Walter you can do it . So close but so far.
Powerbuttom has keymap 107 and 116 camera 212
on the openrecovery.zip you have a etc folder. It includes a keyboard file. This contaions only this here:
QWERTY
Click to expand...
Click to collapse
So US Keyboard layout is selectet by default. What about changing the layout then? I think you don't need to change the keyIDs. You need to change the names.
Sqoerk said:
on the openrecovery.zip you have a etc folder. It includes a keyboard file. This contaions only this here:
So US Keyboard layout is selectet by default. What about changing the layout then? I think you don't need to change the keyIDs. You need to change the names.
Click to expand...
Click to collapse
I will try. No luck. I think this is only for Milestone Keyboard if you use shell.
/openrecovery/keychars/QWERTY/sholesp2a-keypad.kl
OK lets see if this works. In the folder openrecovery/keychars/qwerty/sholesp2a-keypad.kl there are some numbers that walter just mentioned. Can you please modify it and see if the power button can be remapped.
EDIT: Oh damn i dint see your post before mine.
EDIT2: Can you open apk files and have a look. If yes, then tenfar recovery has the keys mapped. It should be comparable.
tenfar app is different. can't find keys
There it is:
Code:
int device_handle_key(int key_code, int visible) {
if (visible) {
switch (key_code) {
case KEY_DOWN:
case KEY_VOLUMEDOWN:
return HIGHLIGHT_DOWN;
case KEY_UP:
case KEY_VOLUMEUP:
return HIGHLIGHT_UP;
case KEY_CENTER:
case KEY_CAMERA:
case KEY_ENTER:
return SELECT_ITEM;
}
}
return NO_ACTION;
}
Code:
case KEY_POWER:
is missing
To find in: droid-openrecovery\src\bootable\open_recovery\default_recovery_ui.c
Found in the source code of the open recovery:
http://gitorious.org/droid/openrecovery/trees/master
So solve it man
Thanks,
mhm, we have to compile from source.
walter79 said:
Thanks,
mhm, we have to compile from source.
Click to expand...
Click to collapse
I'll try tomorrow
Sent from my ME525 using XDA App
apart from backing uo bootloader, does this mean free kernel loading?
I dont think so. Its a recovery system, so you can get your bricked defy back to live more easy. All without using a pc....
Sent from my ME525 using XDA App
Sqoerk said:
I dont think so. Its a recovery system, so you can get your bricked defy back to live more easy. All without using a pc....
Sent from my ME525 using XDA App
Click to expand...
Click to collapse
Not sure about that because you can't boot with a key, you need to go into a WORKING rom and then reboot to recovery
Related
thanks to skeeterslint, koush #sgs-dev , #samsung-epic , #sdx-developers
tester: me, skeeterslint, raiderep
based on koush's clockworkmod 2.5.1.0
new one click with root and recovery: http://forum.xda-developers.com/showthread.php?p=7933592#post7933592
download: http://www.sdx-downloads.com/devs/noobnl/one.click.clockworkmod2.5.1.0-flasher-fixed.zip
1. you need samsung galaxy s drivers
64-bit OS http://firon.net/xda/usb_drivers_GalaxyS_x64.zip
32-bit OS http://firon.net/xda/usb_drivers_GalaxyS_x64.zip
2. push MENU, select Applications > Development, then enable USB debugging.
3. extract and run runtryfirst.bat or runtrylast.bat
4. enjoy!
update.zip method:
1. boot into ClockworkMod Recovery
2. Apply : http://www.sdx-downloads.com/devs/noobnl/clockworkmod2.5.1.0update-fixed.zip
known issues:
adb reboot recovery quickboot boots to stock recovery
workaround:
while phone is off, hold vol down and camera button, then power on the phone
change log:
fixed in build 30: system doesn't unmount
fixes in build 31 incompatblilty with build 30 and di07 kernel
32 fixes added mount rw to the script, thanks bubby!
2.5.1.0 based on koush recovery and fixes the keys!
final fixed! forgot something to add to the scripts!
Yeah...I'm on this..thanks
Sent from my SPH-D700 using Tapatalk
Link is down.
dondadah88 said:
Link is down.
Click to expand...
Click to collapse
Awww...damn....lol. I was about to kick the wifey off the computer...lol
Sent from my SPH-D700 using Tapatalk
uploaded!..
This is something I'm looking for.
It says 0 btyes. and when you open it there's nothing there. lol.
i'm excited.
Oh and that link seems to be down.
miror: http://www.mediafire.com/?b66a2yak832uw20
thanks for the mirrir. downloaded and installed.
how do we boot into the recovery??? using quick boot goes into samsung's recovery...
while phone is off, hold vol down and camera button, then power on the phone
What functions work?
rjmjr69 said:
What functions work?
Click to expand...
Click to collapse
Well Backup works. i dont know what else?
I ran the bat file and everything but my phone still hasn't restarted yet...wtf.
What does this allow us to do? Please answer before I do this?
Backup and restore work fine for me. After the game I'll see if I can get a rom flashed but football > epic atm.
wjohnson1186 said:
What does this allow us to do? Please answer before I do this?
Click to expand...
Click to collapse
Backup everything and flash custom roms.
davidrules7778 said:
Backup everything and flash custom roms.
Click to expand...
Click to collapse
Can you explain how this is done? When I run the files does it copy what is on the phone to the computer so that I can just re-image it back onto the phone?
I maybe asking questions, but I really don't know what I am doing and want to be safe. I already have the one click flasher by noobnl, I trust him. I just want to be sure and understand what I am doing.
Thanks for all the info.
wjohnson1186 said:
Can you explain how this is done? When I run the files does it copy what is on the phone to the computer so that I can just re-image it back onto the phone?
I maybe asking questions, but I really don't know what I am doing and want to be safe. I already have the one click flasher by noobnl, I trust him. I just want to be sure and understand what I am doing.
Thanks for all the info.
Click to expand...
Click to collapse
No it saves under clockwork mod on the sd card in 3 convenient files. So when u flash a custom rom u can run restore and it will restore all your files and data.
Howdy,
Reckon it's been a while since I posted something nice up but I reckon I'll give up some goodies....
I have for yalls pleasure the DG27 to D107 update directly from Sprint, got it on my phone a few minutes ago and pulled it off.
ALSO, I pulled some of the standalone goodies out of it for yalls pleasure as well. These include the media hub apk, and the included qik.apk.
Media Hub:
http://www.droidbin.com/index.php/files/get/HRIhXjP2UZ/mediahubv102-epic4g.apk
Qik:
http://www.droidbin.com/index.php/files/get/p7oQLsoZmp/qik.apk
DG27 to D107 Update (Original non-modified-Signed):
http://www.droidbin.com/index.php/files/get/iv_p2mYBQH/cec94babb124.update-dg27-to-di07.zip
So I through together an update.zip that works on any ODEXED Stock ROM Basically it throws the needed files into system/app and then performs the checks...this is for those with ClockWork Recovery. Be aware that this method requires the stock kernel as well.
Please make sure you do a backup before using this
Update.zip (for clockwork recovery and includes all the listed apps below)
http://www.droidbin.com/index.php/files/get/CynNhuAMDp/update.zip
Firon said:
These are all the files that need to live in /system/app before the updater will work. There's also some files in /system/framework it checks for, but if you removed those, you're probably in trouble
Code:
/system/app/AccountAndSyncSettings.odex
/system/app/AlarmClock.odex
/system/app/ApplicationsProvider.odex
/system/app/BluetoothOPP.apk
/system/app/BluetoothOPP.odex
/system/app/BluetoothServices.odex
/system/app/BluetoothTestMode.odex
/system/app/Brightness.odex
/system/app/Browser.apk
/system/app/Browser.odex
/system/app/BuddiesNow.odex
/system/app/CallSetting.odex
/system/app/Camera.apk
/system/app/Camera.odex
/system/app/CameraFirmware.odex
/system/app/CertInstaller.odex
/system/app/Contacts.apk
/system/app/Contacts.odex
/system/app/ContactsProvider.apk
/system/app/ContactsProvider.odex
/system/app/DataCreate.odex
/system/app/DeviceManagement.apk
/system/app/DeviceManagement.odex
/system/app/DialerTabActivity.odex
/system/app/Divx.odex
/system/app/Dlna.apk
/system/app/Dlna.odex
/system/app/DownloadProvider.odex
/system/app/DrmProvider.odex
/system/app/DrmUA.odex
/system/app/Dun.odex
/system/app/Email.apk
/system/app/Email.odex
/system/app/EnhancedGoogleSearchProvider.apk
/system/app/FactoryTest.odex
/system/app/FlashPlugin.apk
/system/app/FlashPlugin.odex
/system/app/FlashSVGPlayer.apk
/system/app/FlashSVGPlayer.odex
/system/app/Gallery3D.apk
/system/app/Gallery3D.odex
/system/app/GlobalSearch.odex
/system/app/Gmail.apk
/system/app/GmailProvider.apk
/system/app/GoogleApps.apk
/system/app/GoogleCheckin.apk
/system/app/GoogleContactsSyncAdapter.apk
/system/app/GooglePartnerSetup.apk
/system/app/GoogleSearch.odex
/system/app/GoogleSettingsProvider.apk
/system/app/GoogleSubscribedFeedsProvider.apk
/system/app/GpsSetup.odex
/system/app/HTMLViewer.odex
/system/app/HiddenMenu.odex
/system/app/InputEventApp.odex
/system/app/JobManager.odex
/system/app/KeyBoardSlideUpCounter.odex
/system/app/Keytracer.odex
/system/app/LatinImeTutorial.apk
/system/app/Launcher.apk
/system/app/Launcher.odex
/system/app/LiveWallpapers.odex
/system/app/LiveWallpapersPicker.odex
/system/app/LogsProvider.odex
/system/app/Maps.apk
/system/app/MarketUpdater.apk
/system/app/MediaProvider.odex
/system/app/Memo.odex
/system/app/Mms.apk
/system/app/Mms.odex
/system/app/MobileAP.apk
/system/app/MobileAP.odex
/system/app/Music.apk
/system/app/Music.odex
/system/app/MyFiles.apk
/system/app/MyFiles.odex
/system/app/NetworkLocation.apk
/system/app/OtaProvisioningService.odex
/system/app/PackageInstaller.odex
/system/app/Phone.apk
/system/app/Phone.odex
/system/app/PhoneCrashNotifier.odex
/system/app/PhoneErrService.apk
/system/app/PhoneErrService.odex
/system/app/PhoneInfo.odex
/system/app/PicoTts.odex
/system/app/SamsungWidget_CalendarClock.odex
/system/app/SamsungWidget_FeedAndUpdate.odex
/system/app/SamsungWidget_ProgramMonitor.odex
/system/app/SamsungWidget_StockClock.odex
/system/app/SamsungWidget_WeatherClock.odex
/system/app/SelectiveReset.odex
/system/app/Settings.apk
/system/app/Settings.odex
/system/app/SettingsProvider.apk
/system/app/SettingsProvider.odex
/system/app/SetupWizard.apk
/system/app/SisoDrmProvider.odex
/system/app/SnsAccount.odex
/system/app/SnsProvider.odex
/system/app/SoundRecorder.odex
/system/app/SprintTV.apk
/system/app/SprintZone.apk
/system/app/Street.apk
/system/app/Swype.apk
/system/app/TATLiveWallpapersDandelion.odex
/system/app/TATLiveWallpapersLuminescence.odex
/system/app/TATLiveWallpapersOceanWave.odex
/system/app/Talk.apk
/system/app/TalkProvider.apk
/system/app/TelephonyProvider.odex
/system/app/TouchWiz30Launcher.odex
/system/app/TouchWizCalculator.odex
/system/app/TouchWizCalendar.odex
/system/app/TouchWizCalendarProvider.odex
/system/app/TtsService.odex
/system/app/UserDictionaryProvider.odex
/system/app/Vending.apk
/system/app/VideoPlayer.apk
/system/app/VideoPlayer.odex
/system/app/VoiceDialer.odex
/system/app/VoiceSearchWithKeyboard.apk
/system/app/VpnServices.odex
/system/app/WiMAXLineTest.apk
/system/app/WlanTest.odex
/system/app/amazonmp3.apk
/system/app/audioTuning.odex
/system/app/gtalkservice.apk
/system/app/lcdtest.odex
/system/app/serviceModeApp.odex
/system/app/shutdown.odex
Click to expand...
Click to collapse
Download this to get these back:
http://www.megaupload.com/?d=20HJ9004
ENJOY!
images arent loading, opening them in a new tab brings up droid bin
Your too fast
So we can flash this .zip in clockwork recovery and get the whole update?
meh I cant guarantee that will work. My bet is that you will get a signature error...If someone takes this and signs it with the test keys then it may work...depending on what kind of checks it does....
why cant you flash with the stock recovery if it is signed?
Looks like it does a system integrity check and if it fails the checks, any of them, then it wont update your phone...for instance, I tried to install the new update but it fails because I have the 3.0 TouchWhiz launcher
Stericson said:
Looks like it does a system integrity check and if it fails the checks, any of them, then it wont update your phone...for instance, I tried to install the new update but it fails because I have the 3.0 TouchWhiz launcher
Click to expand...
Click to collapse
I am pretty sure the clockwork recovery that noobnl got working has an option to bypass checks or signing but not sure if it actually works. TW 3.0? Gimme some lub here
thanks for the file- I just renamed it "update.zip", placed it on the root of the SD card and used the stock recovery.
I did this after I had gone back to the completely original stock using odin. Tested using mediahub which now loads- under build # I see D107 now
Here is the pastebin of the script....
http://pastebin.com/MVyryDTd
The actual script:
http://www.droidbin.com/index.php/files/get/rDpoTiSQD7/updater-script
jimmyz said:
thanks for the file- I just renamed it "update.zip", placed it on the root of the SD card and used the stock recovery.
I did this after I had gone back to the completely original stock using odin. Tested using mediahub which now loads- under build # I see D107 now
Click to expand...
Click to collapse
how do u get to stock recovery?
Kapow, here is an update script that runs no checks what-so-ever
http://pastebin.com/04EwkdJG
But you need to know whats different on your system because if they try to patch something on your system thats different then what they are suspecting then baaaaad things can happen.
Honestly it wouldnt be hard to make a working update for root users from this....
Stericson said:
Here is the pastebin of the script....
http://pastebin.com/MVyryDTd
The actual script:
http://www.droidbin.com/index.php/files/get/rDpoTiSQD7/updater-script
Click to expand...
Click to collapse
What do we do with this again? Or how can we apply it Stericson? Thanks.. I'm so used to HTC I am getting the hang of this new way..
plmiller0905 said:
how do u get to stock recovery?
Click to expand...
Click to collapse
assuming you dont have a custom recovery loaded just turn off the phone completely and then power on while holding down volume down and camera button.
Basically to make this work for everyone...simply have someone apply the stock update.zip, then get the patched files from their phone and make a update.zip signed with test keys to give you the patched files...
or, revert to nearly stock, meaning using all the exact files they are using and just apply this update.zip after signing it with the test keys...
jimmyz said:
assuming you dont have a custom recovery loaded just turn off the phone completely and then power on while holding down volume down and camera button.
Click to expand...
Click to collapse
Jimmyz I totaly forgot about this.. This is tech the other "official" way to update the device. As this is what ti does after the download to cache. I am liking the ease of one clicks and etc with Samsung.. This could be better than HTC's click and flash..
jimmyz said:
assuming you dont have a custom recovery loaded just turn off the phone completely and then power on while holding down volume down and camera button.
Click to expand...
Click to collapse
Thanks, which keys are used during stock recovery?
plmiller0905 said:
Thanks, which keys are used during stock recovery?
Click to expand...
Click to collapse
Hah- Im such a noob I dont know! How would I find out?
he didnt use any keys, the update.zip he used was signed by Sprint
jimmyz said:
Hah- Im such a noob I dont know! How would I find out?
Click to expand...
Click to collapse
ha...not noob by the way...but any ways...i got it figured out!
I have created the vendor files for the advnet vega based apon the cyanogen ones for the Gtab, and compiled CM6 for the vega. This is not supported by cyanogen's team yet as the vega isnt officialy supported by them yet so please take that into mind (dont ask for support on the cyanonen irc ect u probably wont get it) but feel free to ask support on this thred.
Nither me or the CyanogenMod team take no responsability for any damage caused bu this rom. by flashing it means u understand this risks and accept the risks.
What doesnt work :-
- Camera
- Rotation can be funny (if it works at all)
[UPDATE]
- Black Screen Of death can occur when rebooting (looking into this ASAP) so be prepared to restore
What works :-
- Every thing else (i think)
[INSTALL]
1) get the .zip file from the bottion of the post
2) copy it to SD card
3) reboot into recovery
4) MAKE NANDROID BACKUP
5) flash zip from recovery (you will get a boot write error thats normal)
6) reboot
7) DONE
[DOWNLOAD]
http://db.tt/UmV1dYK
[CREDITS]
CyanogenMod Team for there src
Bekit for the Gtab vendor this is based on
Anyone else i have forgotten
[MY VENDOR]
If anyone else wants to try and improve on this please feel free.
https://github.com/BuzzBumbleBee/android_device_vega/tree/froyo
(Please note at the current time the boot.img that the compile creates will not work on the vega to u will have to make one by extracting the original ramdisk from the boot.img)
thanks mate been tring with cyanogenmod for gtablet..gonna try now. THis bad boy vega need some action
got error message:
assert failed: package_extract_file("boot.img" ,"/temp/boot.img")
E:Error in /sdcard/CM-6.2.0-Vega.zip
(status 7)
Installation aborted.
edit: fixed.
I successfully installed, I put the original boot.img from vega into the zip, taking it for a spin now. Thanks Apache14.
I sold my Vega because of the screen imo wasnt great and the wi-fi issue.
Would have loved to have tried this rom though.
Good work !!!
Thanks to apache14 and everyone involved
How do we get market onto the tab. thanks in advance
Dunno about market any CM6 compatable gapps will work ..... also the adding boot.img isnt needed as there is no need to flash the boot.img (the stock advent one works pritty well for now)
Apache14 said:
Dunno about market any CM6 compatable gapps will work ..... also the adding boot.img isnt needed as there is no need to flash the boot.img (the stock advent one works pritty well for now)
Click to expand...
Click to collapse
thx mate, misread the first post
Anyone working on fixing the black screen of death on cold boot a lot of people are getting with clockwork? I know there are enough people who don't have CW installed because of this that anything that depends on it will have a more limited appeal.
arad85 said:
Anyone working on fixing the black screen of death on cold boot a lot of people are getting with clockwork? I know there are enough people who don't have CW installed because of this that anything that depends on it will have a more limited appeal.
Click to expand...
Click to collapse
I have installed clockwork a couple of times and no black screen of death. Its straight forward.
Follow the instruction paul gave on modaco.
Download the Recovery image and flash utility and extract to desktop
open terminal
adb devices to make sure your device is connected
cd to the directory of file you just extract
then type
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 4755 /data/local/flash_image
adb shell /data/local/flash_image recovery /data/local/recovery.img
thats done.
If you on mcr 6, the vega reboot recovery is already installed if not download from the market.
cheers
alphaola said:
I have installed clockwork a couple of times and no black screen of death. Its straight forward.
Click to expand...
Click to collapse
Yes, it's very straightforward. I've done it a few times too and followed the instructions. I still get the bsod as do a number of others. Without CM installed, no bsod...
Try power cycling your Vega back-to-back using the power button. I bet you'll get it to bsod reasonably quickly.
BSOD
Some people have reported black screen of death when rebooting with the power menu. so be careful and be prepared to restore (or flash stock boot,img again)
I am looking into this error now and hope to have a fix pritty soon
Apache14 said:
I am looking into this error now and hope to have a fix pritty soon
Click to expand...
Click to collapse
Brilliant - thanks
Apache14 said:
Some people have reported black screen of death when rebooting with the power menu. so be careful and be prepared to restore (or flash stock boot,img again)
I am looking into this error now and hope to have a fix pritty soon
Click to expand...
Click to collapse
arad85 said:
Brilliant - thanks
Click to expand...
Click to collapse
i fixed it. Copy boot.img,system.img and ramdisk.img from vega into the cyanogenmod zip,then flash, it also boot into recovery using rom manager.
Note: Do not unzip the cyanogengenmod, just use winrar to open it and copy those files into it then close it
alphaola said:
i fixed it. Copy boot.img,system.img and ramdisk.img from vega into the cyanogenmod zip,then flash, it also boot into recovery using rom manager.
Click to expand...
Click to collapse
Sorry, being particularly thick today. How do I get hold of the three .img files?
arad85 said:
Sorry, being particularly thick today. How do I get hold of the three .img files?
Click to expand...
Click to collapse
download the advent vega system file from advent vega website,zip it using winrar.
alphaola said:
download the advent vega system file from advent vega website,zip it using winrar.
Click to expand...
Click to collapse
<facepalm>
arad85 said:
<facepalm>
Click to expand...
Click to collapse
no stress man. Its quite smooth and fast, love the animation as well
alphaola said:
no stress man. Its quite smooth and fast, love the animation as well
Click to expand...
Click to collapse
So I did all this, and now have a device that is....
... exactly the same as before but with CWR installed (even says it's MoDaCo ROM). The flashing process took only a few seconds and no boot write error. Am I missing something here?
EDIT: hang on... just realised the zip file was wrong!!
To get the market and apps
Download http://android.d3xt3r01.tk/cyanogen/gapps/gapps-mdpi-tegra-20101020-signed.zip, then flash using rom manager. then once you reboot you should get all your apps and market. enjoy
arad85 said:
So I did all this, and now have a device that is....
... exactly the same as before but with CWR installed (even says it's MoDaCo ROM). The flashing process took only a few seconds and no boot write error. Am I missing something here?
EDIT: hang on... just realised the zip file was wrong!!
Click to expand...
Click to collapse
ahahha mate,it works.
Download button savior to make navigation easy
Hello all
Really looking forward to a stable version with an idiot proof install for folks like me.
Great work
Rgds
Lok
Defy Froyo 3.4.2 Cookie Cutter Rom​
Q. How Do I use the Update.zip?
A. Go to Market & Download Defy SD-Recovery & Install..
1. Next place the Update.zip on the /sdcard via PC
2. Turn on MoTo Phone Portal ( SD-Recovery is SD Based so you need to Turn Off USB Mass Storage )
3. ADB Debugging does not have to be Turned Off on my version
Once Booted into the Recovery apply the update.zip
wait a few minutes & it should be done...
Please Reads the notes I left in the Update.zip if you build a Custom Update.zip, this will save you trouble down the road.
What's Flashed?
A. Boot.img
B. dev_tree
C. Moto Blur 3.4.2 Rom ( Yes I know it's not the latest, built off what I had )
D. UNO & TMO-TV Removed
E. Rooted ( SU & Superuser )
F. Busybox Installed to xbin
G. Rest of Rom is stock
Once installed, remove eugene.apk from /system/app ( Old boot strap that need adb turned off before rebooting / defy sd-recovery does not have this issue)
Q. I Edited the update.zip & Now it fails verf. in recovery when trying to flash!
A. example of signapk on signing the edited update
java -Xmx1024m -jar signapk.jar -w testkey.x509.pem testkey.pk8 update1.zip update.zip
Download: Original Post
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
If we had all these Parts from 2.1 we could go back.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Hey eugene,
Glad to see you working on Defy too
I think this will be major help for developers and btw that 3.4.2 version did you used? since there are many of them.
Thanks.
um. 107 I think since it has a floating update.zip someplace & sbf.
Ill update to the latest when I start building roms
Sent from my MB525 using XDA App
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
eugene373 - great work!
racca said:
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
Click to expand...
Click to collapse
Same here, i'm pretty interested in more details, thank you
this Zip File is for what ?
Thanks
Greetings
you can not use cwm due encryption. If you dont know what an update.zip is stick to nandroid...
This is for rom builders.
Heading out, when I get home ill make it clearer.
Though, now that I think about it cwm might be fine due to the nature of how it works.
Ill test later and let everyone know
Sent from my MB525 using XDA App
So we are able to install updates via the "normal" Motorola Recovery mode? So we are able to get a "unbrickable" Defy?
Edit: got it myself. The ZIP File won't be recognized by the motorola recovery... anyway thanks for your job
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Simplestas said:
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Click to expand...
Click to collapse
Yes. I can add the string if you would like
eugene373 said:
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Click to expand...
Click to collapse
eugene373 said:
Yes. I can add the string if you would like
Click to expand...
Click to collapse
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
racca said:
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
Click to expand...
Click to collapse
Correct, you can only format with the stock recovery ( Hence the reason why I used the Stock Recovery ) any Partition with cwm recovery will cause a non-booting system..
regarding cwm I've not tested it, so Likely it will work.. Steven is still working on the cwm recovery & there is no point in me adding another cwm bootstrap recovery... Mine is just pure stock & works perfect.
I'm still weeding through the /bin /etc file's to find exactly what needs left...
but main goal was to provide an example of what is needed to make an update.zip with out breaking the system.
what exactly is the benefit of this new method?
drsouly said:
what exactly is the benefit of this new method?
Click to expand...
Click to collapse
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
eugene373 said:
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
Click to expand...
Click to collapse
ok now i got it thx
drsouly said:
ok now i got it thx
Click to expand...
Click to collapse
no problem, wasn't sure if you was being a smart-ass or honestly didn't know...
either way, sorry If I offended you.
~Eugene
I didn't understand yet . I can or not apply the update file using stock recovery?
EDIT: forget I understood now.
Sent from my MB525 using XDA App
psicodelico said:
I didn't understand yet . I can or not apply the update file using stock recovery?
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Read OP.... Download Defy SD-Recovery from Market
Yeah, I read again slowly and understood.
Sent from my MB525 using XDA App
Let's begin
1st download all the necessary files:
Motorola 5.4.0 Driver with MotoHelper http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
stock UK XT720 sbf and RSD Lite 4.9 from http://forum.xda-developers.com/showthread.php?t=953863
SuperOneClickv2.1.1 ftom http://forum.xda-developers.com/showthread.php?t=887416
OI File Manager or from Android Market
Open Recovery for XT720 from http://forum.xda-developers.com/showthread.php?t=1242259
CM6 RC3 from http://forum.xda-developers.com/showthread.php?t=1197655
Then proceed to install the windows drivers for XT720,
once that is done flash your XT720 back to factory stock,
to go into ROM flashing mode Hold Power + Volume Down + Camera buttons all at once, be patient, it will take a while and a couple of reboot.
When the phone is finally done booting up, go into Settings > Applications, and check the boxes for USB debugging + Stay awake,
now you can run SuperOneClickv2.1.1 to root your XT720, for step by step rooting instructions follow this guide http://forum.xda-developers.com/showthread.php?t=887416
Next you will want to install a File Manager to your XT720, the stock XT720 doesn't include any file manager,
open a command line (in windows run CMD),
switch to the directory ..\SuperOneClickv2.1.1-ShortFuse\ADB\
run the command line adb.exe install FileManager-1.1.6.apk
The next step is best done using a microSD card reader, then you can drag & drop all the files for your XT720 directly to the SD card from Windows Explorer
- OpenRecovery.apk,
- the unzipped files from OpenRecovery-XT720-01 folder,
- update-cm-6.3.0-RC3-MilestoneXT720-signed.zip,
- gapps-hdpi-20101114-signed.zip
Using the OI File Manager install OpenRecovery.apk (it should be at the root of your SDcard),
run Open Recovery from XT720 stock launcher's app drawer,
select Install Recovery System (allow super user),
then follow the instructions to install OpenRecovery-XT720-01 from http://forum.xda-developers.com/showthread.php?t=1242259
Once you are done proceed to install update-cm-6.3.0-RC3-MilestoneXT720-signed.zip, and gapps-hdpi-20101114-signed.zip using OpenRecovery-XT720 (for details follow http://forum.xda-developers.com/showthread.php?t=1197655),
select clear cache, dalvik, and factory reset
choose the reboot option from OpenRecovery-XT720 menu,
the first boot of CM6 will take a very long time,
when you see the launcher, let it finish loading, then reboot the phone again via power button > reboot,
after this last reboot, the phone is finally ready for normal usage.
Enjoy!
You can get the Dexter's OpenRecovery.apk here
you can use universal androot to root your phone alternatively. its super easy. just drag it onto your sd card (or download directly from your phone), install the apk, and click root. heres a link. http://www.4shared.com/file/HvHnis8C/Universal_Androot_v161.html
I actually did this to a friends xt720 yesterday and I needed to fix the APN settings, he wasn't getting data.
WARNING, about BusyBox newer than v1.17.1 and Link2SD
So i found out the hard way there's an odd bug with BusyBox 1.18.x or newer it conflicts with Link2SD, it wont mount and causes Link2SD to throw this message
Code:
Mount script error
Mount script cannot be created
mount: mounting /dev/block/vold/179:2 on /data/sdext2
failed: no such device
reverting BusyBox back to 1.17.1 fixed the problem
Help on Boot Loop
Followed all instructions here to update to the the cm 6.3.0 RC3. Everything appeared to go as stated, but after reboot i seem to be stuck in a vicious boot loop. I get the cyanogen mod droid logo but it seems to pop up every 10 seconds or so without the phone ever starting up. Any help would be greatly appreciated. It's cute as a paperweight, but not much good as a phone.
Disregard....after rebooting for nearly nine hours....the phone finally started up and appears to be working....Thanxxxx
I too now am unable to access data....i am not skilled enough to work with the APN settings. Could you please help me out on what i need to do to get my data working again...no internet access sux....
AllGamer said:
Next you will want to install a File Manager to your XT720, the stock XT720 doesn't include any file manager,
Click to expand...
Click to collapse
Awesome Instructions bud, much needed for the first timers. Just thought I would add that stock 2.1 always came with quickoffice for me and that's what I normally use at first to install Open Recovery but always end up needing a better File Manager anyway. So either way, I hate to be a stickler just might be one less step lol. Good job AllGamer dude!
Ps.. I should have just said good job dude your way is better lol.
hitech1 said:
I too now am unable to access data....i am not skilled enough to work with the APN settings. Could you please help me out on what i need to do to get my data working again...no internet access sux....
Click to expand...
Click to collapse
Install APN manager from the market and find your carrier there.
You could always just input them manually, doesn't require any skill bud, you just have to google the correct APN configuration details.
nice App
JiroPrinz8 said:
Install APN manager from the market and find your carrier there.
Click to expand...
Click to collapse
https://market.android.com/details?id=ale.android.apnmanager&feature=search_result
this is an Excellent recommendation.
I didn't even know such APP existed
it's so easy to enter APN data... pick and choose, done!
Don't think you should be flashing ROMS if you're hesistant about manually entering an APN, my 2 cents lol.
I would still rather recommend singapore rom, with the tv out and everything. Don't know of any cons with this atm.
Hi,
i installed cm6 rc 3 as described above. And it runs very smooth and stable.
Although i have one big problem: If i insert my sd-card (3gb fat + 1 gb ext4, with app folder on ext partition) in my phone, app2sd works as it should and the phone boots as usual. But when the phone shuts off the display and goes into sleep mode, i am no more able to wake it up again. When I push the power button only the leds switch on. I have to pull the battery and restart the phone.
If sdcard is not inserted, everthing works great. with no problems since three days now.
But i would like to have my sdcard back...
Perhaps some can help me.
Leotronick said:
Hi,
i installed cm6 rc 3 as described above. And it runs very smooth and stable.
Although i have one big problem: If i insert my sd-card (3gb fat + 1 gb ext4, with app folder on ext partition) in my phone, app2sd works as it should and the phone boots as usual. But when the phone shuts off the display and goes into sleep mode, i am no more able to wake it up again. When I push the power button only the leds switch on. I have to pull the battery and restart the phone.
If sdcard is not inserted, everthing works great. with no problems since three days now.
But i would like to have my sdcard back...
Perhaps some can help me.
Click to expand...
Click to collapse
I'm not certain but I think this means that Android thinks your battery has more charge than the hardware does. I would first try to redo battery calibration (there are threads in the XT720 general section about how to do this) if you can convince yourself that your battery is actually full. It can be a little tricky.
Leotronick said:
Hi,
i installed cm6 rc 3 as described above. And it runs very smooth and stable.
Although i have one big problem: If i insert my sd-card (3gb fat + 1 gb ext4, with app folder on ext partition) in my phone, app2sd works as it should and the phone boots as usual. But when the phone shuts off the display and goes into sleep mode, i am no more able to wake it up again. When I push the power button only the leds switch on. I have to pull the battery and restart the phone.
If sdcard is not inserted, everthing works great. with no problems since three days now.
But i would like to have my sdcard back...
Perhaps some can help me.
Click to expand...
Click to collapse
might be your vsel being too low. it happened to me too, and i made the vsel a little higher and it didnt happen anymore.
Hi, I have a noob question...
Can I install this recovery image (CM6) directly from stock Videotron SBF?
I do have install open Recovery based on Androidiani. Can I flash this Rom (CM6) with that recovery or I need something diffrent?
Thanks for your help!
speedmax said:
Hi, I have a noob question...
Can I install this recovery image (CM6) directly from stock Videotron SBF?
I do have install open Recovery based on Androidiani. Can I flash this Rom (CM6) with that recovery or I need something diffrent?
Thanks for your help!
Click to expand...
Click to collapse
if you are already on stock, then yes you can flash CM6
but make sure you are rooted first
and use the Open Recovery XT720 listed in the OP topic
AllGamer said:
if you are already on stock, then yes you can flash CM6
but make sure you are rooted first
and use the Open Recovery XT720 listed in the OP topic
Click to expand...
Click to collapse
Thanks, I Will proceed tomorow.
Regards,
Sent from my MB860 using xda premium
Just installed! Working nice...
Camera and camcorder are working, it was a bug with stock Rom.
Is there a Overcloking kernel for XT720 CM6 rom?
Or is there a way to overclock it with the current one?
Regards et thanks for your help!
speedmax said:
Just installed! Working nice...
Camera and camcorder are working, it was a bug with stock Rom.
Is there a Overcloking kernel for XT720 CM6 rom?
Or is there a way to overclock it with the current one?
Regards et thanks for your help!
Click to expand...
Click to collapse
yes, just download the milestone OC utility from Android market