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
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
Hi all,
Here I present you; all the HBOOT'S from the alpharev website all in a zip format, so you can flash it via recovery
I tested it myself and its working without any brick or something
Tested it with CWM 2.5.0.7
note: this is ONLY for GSM devices!!!
If someone could please convert the CWM2XXX scripts to CWM3XXX scripts, because i'm not able to do it.
I will add your credit to OP!! (thanks in advance)
ClockWorkMod 2XXX versions are at the bottom post, and ClockWorkMod 3XXXX verions are coming soon! since I can't convert the script and someone else has to do it!
I dont know if these zip's will work if you are S-ON! But you could try it if youre a huge tester like me ghehe, I dont know why it won't work.
Thank you for your understanding
BUT IF YOUR PHONE WILL BRICK, I AM NOT RESPONSIBLE!
How to install??
1. Put the zips on your SDCard.
2. Reboot into recovery.
3. Choose the zip to install.
4. Let it install, and it will reboot twice to install, so DONT pull the batt out.
5. Thank me and enjoy!
Have a nice day
Nice, thank you so much for this!!
wow..!
what a fantastic idea...hope it works
nice idea!!!
can u plase release the Md5 of the zips
Great idea, can anyone else confirm this works?
Pavelol said:
nice idea!!!
can u plase release the Md5 of the zips
Click to expand...
Click to collapse
lol I dont have them XD #sorry..
but i can asure you it will work
CM7R2 hboot dont work. How install Cm7 hboot on my desire? easy way pls
anetgrup said:
CM7R2 hboot dont work. How install Cm7 hboot on my desire? easy way pls
Click to expand...
Click to collapse
Why not? Wich error gives it??
Tested it with CWM 2.5.0.7
nickislauw said:
Why not? Wich error gives it??
Click to expand...
Click to collapse
He might have used ClockworkMod > 3.0 which doesn't support the amend scripting of your update scripts.
After I have read your first message, I have tried to find the edify equivalent for write_hboot_image and all I have found was that htc.install_hboot is the one, but in the CWM 4.x it requires 7 parameters. On a Hiapk forum I have found the following sample:
Code:
assert(htc.install_hboot(package_extract_file("hboot.img"),
320, 480, 16,
package_extract_file("install.565"),
package_extract_file("error.565")));
The sample contains only 6 parameters. In CWM 4.x, the seventh parameter is a string version of a SHA1 checksum (of hboot.img, I suppose). Some details in <cyanogenmod git tree>/device/htc/common/updater/recovery_updater.c. I suppose one may have to produce the 2 bitmaps, but I don't know how to use the SHA1 key in this case. If this problem is solved, then the radio flash problem is solved too.
nickislauw said:
lol I dont have them XD #sorry..
but i can asure you it will work
Click to expand...
Click to collapse
Could a corrupt download not still leave us with a brick, or is it different flashing them this way (i.e. it would detect it was corrupt and not flash)? Either way thanks for these
AlxMAX said:
He might have used ClockworkMod > 3.0 which doesn't support the amend scripting of your update scripts.
After I have read your first message, I have tried to find the edify equivalent for write_hboot_image and all I have found was that htc.install_hboot is the one, but in the CWM 4.x it requires 7 parameters. On a Hiapk forum I have found the following sample:
Code:
assert(htc.install_hboot(package_extract_file("hboot.img"),
320, 480, 16,
package_extract_file("install.565"),
package_extract_file("error.565")));
The sample contains only 6 parameters. In CWM 4.x, the seventh parameter is a string version of a SHA1 checksum (of hboot.img, I suppose). Some details in <cyanogenmod git tree>/device/htc/common/updater/recovery_updater.c. I suppose one may have to produce the 2 bitmaps, but I don't know how to use the SHA1 key in this case. If this problem is solved, then the radio flash problem is solved too.
Click to expand...
Click to collapse
well thanks for that, i will add to OP to use cwm 2xx
woahnelly said:
Could a corrupt download not still leave us with a brick, or is it different flashing them this way (i.e. it would detect it was corrupt and not flash)? Either way thanks for these
Click to expand...
Click to collapse
The ZIPs are signed packages and they contain some checksums. If you have the JDK installed, you may try jarsigner -verify <zip package> to see if the archive is corrupted.
nickislauw said:
well thanks for that, i will add to OP to use cwm 2xx
Click to expand...
Click to collapse
Or Amon RA...!
S-OFF?
Do I still need to be s-off'ed to install these hboots?
kushion said:
Do I still need to be s-off'ed to install these hboots?
Click to expand...
Click to collapse
i would assume so as there is nothing special about the way these flash
Can I use AmonRA 2.0.1, to flash this hboots.??
Sent from my HTC Desire using XDA App
?
So no s-off needed? Just rooted (obviously), flash and go? Doesn't seem right :/
You will have to be s-off already to use these.
There hboots merely work with the existing s-off hboot to alter the partition sizes, you cannot install s-off with this.
Op please add this info to the info
sent from my s-off'd desire!
AlxMAX said:
The ZIPs are signed packages and they contain some checksums. If you have the JDK installed, you may try jarsigner -verify <zip package> to see if the archive is corrupted.
Or Amon RA...!
Click to expand...
Click to collapse
Thanks for the info man - good to know
nice job dude.
Woluld be really nice to see them for cwm 3.x. Hope u`ll be able to make them soon.
Thanks to dangpzanco for the GREAT IDEA.
I finally got my Rooted GB working here. I can't provide a download link now but I'm going to do it later for sure.
Apparently there was a final signature check that was done somewhere after mounting the cache partition, preventing me from booting with a pure update.zip on top of froyo /system. Thanks to dangpzanco I could bypass it and get root.
Quick Guide (requires froyo, root and Droid2bootstrapper):
1. Download fixed SBF bellow. It's made from the CH leak containing ONLY: CG35.smg (boot) CG47.smg (recovery) CG61.smg (devtree) firmware.hmg (header) RAMDLD.smg (flash updater).
2. Download root_and_recovery.zip and copy it to SD Card.
3. Download full leaked SBF from General Forum (CH, signed) and use MotoAndroidDepacker to extract all images.
4. Copy the CG39.smg to /sdcard/
5. Boot into CWM
6. From CWM open adb shell and use this command: dd if=/sdcard/cg39.sm of=/dev/block/system
7. Still on CWM apply root_and_recovery.zip
8. Still on CWM wiped everything
9. Boot on bootloader and flash fixed SBF
10. Reboot
I actually did the same thing! I read it somewhere in one of the topics. I installed Defy BootMenu instead of CWM. Works great! Right now I've almost removed all the Chinese crap and got the GApps working (from CM7).
I also removed the Blur items for the Chinese SN's. I'll see if I can get Twitter and Facebook working with it.
2nd-init would be nice too actually. Does the method provided in the other thread work with this ROM?
Edit: the instructions were indeed from dangpzanco!
And right now I found a possible bug. My camera doesn't work. Everything is black and stays black. Photo's are take as they should however.
Can you check whether you have the same issue?
w0ndersp00n said:
And right now I found a possible bug. My camera doesn't work. Everything is black and stays black. Photo's are take as they should however.
Can you check whether you have the same issue?
Click to expand...
Click to collapse
Here it works fine. Have you tried to edit /system/build.prop?
Change device from ME722 to A953.
Yes, I changed it to A953...
Maybe I have deleted something that was necessary for the viewfinder... But what xD
Edit: Allright, nevermind. Somehow a reboot fixed it :-D On to the next step
Something bad happened when I tried to apply 2nd-init on this. The phone rebooted just after 2nd M logo not allowing me to get into CWM. Wierd, since CWM should take place before 2nd-init. Will need to raflash froyo and start over. We should find a way to root Gingerbread without CWM to make things faster.
That's odd indeed. I have to say, I think the CWM method of rooting is actually quite easy. For SuperOneClick I need to get my PC/laptop out every time and with the update.zip I can do it as I please.
I really hope you'll succeed wit 2nd-init. If you need help, just shout! Today and tomorrow I have enough time.
I'll make a nandroid of my current setup, so I can continue trying out stuff.
w0ndersp00n said:
That's odd indeed. I have to say, I think the CWM method of rooting is actually quite easy. For SuperOneClick I need to get my PC/laptop out every time and with the update.zip I can do it as I please.
I really hope you'll succeed wit 2nd-init. If you need help, just shout! Today and tomorrow I have enough time.
I'll make a nandroid of my current setup, so I can continue trying out stuff.
Click to expand...
Click to collapse
Yeps, it is easy indeed, but to do it I need to SBF froyo before installing GB again. In other words if I mess up the phone I will need to flash 2 versions instead of one. That's why it would be easier to flash just GB.
Hey there, nice I could help.
I think you could copy the /dev/block/system back after rooting and build the SBF with it.
@Milestone 2 (Finnaly on Gingerbread!)
dangpzanco said:
Hey there, nice I could help.
I think you could copy the /dev/block/system back after rooting and build the SBF with it.
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
I tried that with froyo but it didn't work.
you can try also this defy leaked gb rooted nandroid backup.
http://www.multiupload.com/SPZ8SIEC60
version 4.5.1-134 multilanguage.
use fixedsbf from new leaked milestone2 rom and milestone2patch from MS2Ginger thread.
In this rom /system/app/kpilogger.apk cause battery drain so delete it after install.
Something is seriously wrong... My backlight never shuts down. It's black, but when it's dark you'll see it's still on!
I actually can't change the brightness from settings. So I did a complete reinstall and the problem persists!
I'm using brightcontrol app now to adjust the brightness, but does anyone else has this issue? Or is it something I did?
r2beta0 can you please upload the nandroid of your system?
I try to get adb in CWM but it didn't recognize it.
julianlatasa said:
r2beta0 can you please upload the nandroid of your system?
I try to get adb in CWM but it didn't recognize it.
Click to expand...
Click to collapse
My system is messed. I still need to get 2nd-init to work. I'm having a lot of trouble trying to compile my custom version of logwrapper hijack. As I don't have experience in compiling stuff to ARM/Android it is being a pain in the a**. I'd appreciate some help here
Try setting up a QEMU environment with the GB leak kernel's zImage.
Edit: Now we can port CM7!!! Devtree.img is now signed.
@Milestone 2 (Finnaly on Gingerbread!)
dangpzanco said:
Try setting up a QEMU environment with the GB leak kernel's zImage
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
And how do I do that?
I tried some ways till this point:
- Installed CodeSourcery G++ Lite toolchain (could compile, but android didn't run)
- Installed NDK and tried some commands I could find on blog posts (no luck)
- Now I just finished setting up an ubuntu 10 VM with all the steps described on developer.android.com. I think I am now able to compile android system, but I don't want to as it will take a LOOONG time.
Do you know how do I build a specific module into android source? For example:
system/core/toolbox
I'm a developer, and have compiled stuff to run on linux/unix many times. But this ARM stuff is way complicated. Writing the code isn't the problem, but compiling is. Lots of flags I haven't seem before, and so on.
r2beta0 said:
And how do I do that?
Do you know how do I build a specific module into android source? For example:
system/core/toolbox
Click to expand...
Click to collapse
I just uncovered this answer by myself.
A 'make toolbox' on root folder seems to work just fine. Now I need a way to define new targets on android build system.
http://and-developers.com/
Has a page just for compiling the kernel from source. (I can't remember the link)
I also got stuck when trying to compile from AOSP... but I think you need to have ALL the files downloaded from source (specially the big prebuilt folder) even if you want to compile a single binary.
Well I'm not sure of anything...
Edit:Now I read what you wrote... so never mind you got it.
@Milestone 2 (Finnaly on Gingerbread!)
dangpzanco said:
http://and-developers.com/
Has a page just for compiling the kernel from source. (I can't remember the link)
I also got stuck when trying to compile from AOSP... but I think you need to have ALL the files downloaded from source (specially the big prebuilt folder) even if you want to compile a single binary.
Well I'm not sure of anything...
Edit:Now I read what you wrote... so never mind you got it.
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
Yeps I've made a full repo sync. It took 3 hours and is worth 6GB disk space
Great news! Can't wait to see a true custom ROM working
Just thought I'd share what I've learned: don't mess too much with your build.prop Somehow my modifications were the reason of my backlight not working right and making every app crash that wanted to use a sensor. But it's working again