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!
Related
Here's a recompiled version of the Browser that supports auto rotate.
Here's the download location for the Browser.apk:
http://www.koushikdutta.com/2008/12/auto-rotate-for-android-browser.html
Run the following from the command prompt to install the new Browser:
Installation Instructions:
adb remount
adb shell rm /system/app/Browser.odex
adb push Browser.apk /system/app/Browser.apk
Now start up the Browser.
You may not have a Browser.odex depending on your phone model.
The change, as I mentioned before, is really trivial. In the BrowserActivity.onCreate, I did the following:
// the next line is the original code
// setRequestedOrientation(mSettings.getOrientation());
// make it use the sensor for orientation instead.
setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_SENSOR);
To restore the original Browser, flash RC30 again.
Koush, thanks so much! I have been waiting for this!
i can't get it to install and now the browser don't work and i can't install the back up
I'm getting no space available when pushing the browser.apk
JF rc30 v1.2
kron2 said:
i can't get it to install and now the browser don't work and i can't install the back up
Click to expand...
Click to collapse
You can't get it to install? Could you be more specific?
saul972 said:
I'm getting no space available when pushing the browser.apk
JF rc30 v1.2
Click to expand...
Click to collapse
Your /system partition ran out of room. Is there something you can delete from there? I've seen this before as well on some of my company's phones; I usually end up deleting some ringtones or other junk files.
took a couple of tries but installed now...thanks!
fyi i rebooted phone to initially install the new Browser. I first got errors w/o rebooting so that may fix the problem
I had the same problems with the new browser crashing and then being told that the file couldnt be copied due to lack of space,
Easiest fix is to just reinstall rc30 or rc8 and install the patched browser again.
Worked fine after that
Koush said:
Your /system partition ran out of room. Is there something you can delete from there? I've seen this before as well on some of my company's phones; I usually end up deleting some ringtones or other junk files.
Click to expand...
Click to collapse
Not sure.
Here's the message
failed to copy 'Browser.apk' to 'system/app/Browser.apk' : no space left on device
SGTDavePwnage said:
I had the same problems with the new browser crashing and then being told that the file couldnt be copied due to lack of space,
Easiest fix is to just reinstall rc30 or rc8 and install the patched browser again.
Worked fine after that
Click to expand...
Click to collapse
Will I need to start the process again?
saul972 said:
Will I need to start the process again?
Click to expand...
Click to collapse
Its basically telling you that it cant copy the file because of lack of space withing the system partition.
As koush advises, if you know how to clear space that will fix the problem.
If you dont know how to remove things and are a bit unsure of what to do, reinstalling the modified rc30 / rc8 will reset the system partition back to its defaults.
Once your back and set to default you can try to install again if you want
I'm assuming this is for those who have root access only?
If so, it would be nice to state that when posting these mods.
Henchman said:
I'm assuming this is for those who have root access only?
If so, it would be nice to state that when posting these mods.
Click to expand...
Click to collapse
Yes this requires root access,
I can see what you are saying about perhaps specifying in the post when something requires root access, but when you look at the instructions in this case its quite obvious that this one does require root.
PS.... Cheers for the upload Koush
SGTDavePwnage said:
Yes this requires root access,
I can see what you are saying about perhaps specifying in the post when something requires root access, but when you look at the instructions in this case its quite obvious that this one does require root.
PS.... Cheers for the upload Koush
Click to expand...
Click to collapse
Obviouse to em...
But probably not to everyone.
And you know the old saying. When you Assume...
where do i put Browser.apk to install it on the sd card and if so how do i use adb to see it or do i push it from like c:\browser.apk \system\app\browser.apk
SGTDavePwnage said:
Its basically telling you that it cant copy the file because of lack of space withing the system partition.
As koush advises, if you know how to clear space that will fix the problem.
If you dont know how to remove things and are a bit unsure of what to do, reinstalling the modified rc30 / rc8 will reset the system partition back to its defaults.
Once your back and set to default you can try to install again if you want
Click to expand...
Click to collapse
Finally got it!!! Thanks for your help
kron2 said:
where do i put Browser.apk to install it on the sd card and if so how do i use adb to see it or do i push it from like c:\browser.apk \system\app\browser.apk
Click to expand...
Click to collapse
Place it in the tools folder of the SDK folder on your PC
thx joshoowa i installed it finally i did have it in the tool folder but would not install but after several tries it did i was starting to think i was installing it wrong
I've deleted most of my .ogg audio related tones in the /media/audio folder but i still get no space left. what else can i delete?
btw i'm using adb shell rm /xxx/xxx/xxx/xx.ogg to delete. is that right?
Hey Hey!!!...
Had to free up some room, but it works great..
Thanks..
http://www.4shared.com/file/WU7XiKt-/RUU_Hero_C_Sprint_2206511_sign.html
to all dev. its said the leak for sprint 2.1 .is exe file.non rooted phone can upgrade it. heard everyyhing work fine. im gsm version. im not respondsible for any damage or bricked of your phone.
the source from facebook htc hero page.
Sent from my Hero using Tapatalk
IS FOR SPRINT. NOT GSM. BE ALERT
Sent from my Hero using Tapatalk
orangeclanz said:
http://www.4shared.com/file/WU7XiKt-/RUU_Hero_C_Sprint_2206511_sign.html
to all dev. its said the leak for sprint 2.1 .is exe file.non rooted phone can upgrade it. heard everyyhing work fine. im gsm version. im not respondsible for any damage or bricked of your phone.
the source from facebook htc hero page.
Sent from my Hero using Tapatalk
Click to expand...
Click to collapse
Nice to see the CDMA Hero has it's official 2.1 fame .. but come on lazy HTC, where is 2.1 for the GSM cousin? Let's hope tomorrow is THE day..
Looks like it's working
EDIT: However, this is exactly the same as Villain 5.2 (the same leak that is).
Pretty stable
It does work well.. What an improvement from the previous version
HomerSp said:
Looks like it's working
Click to expand...
Click to collapse
But not on GSM Hero's - grrrrrrrrrrrrrrrr
Didn't the GSM hero come out before the CDMA one? How come the CDMA one came out first?
hkr said:
But not on GSM Hero's - grrrrrrrrrrrrrrrr
Click to expand...
Click to collapse
It does if you port it (I only have gsm) ;-)
HOW LEGIT IS THIS RUU THOUGH? who can co-sign it? my buddy wants to use it but doesn't want to take any chances..
someonenewhere said:
Who can co-sign it?.
Click to expand...
Click to collapse
What?
I need a Mercedes? Can someone co-sign it?
Just playing
Old news >> http://forum.xda-developers.com/showthread.php?t=661057
All of our dev's 2.1 builds are already based on this build.
FYI, when the final (non-test) build .exe comes out, flashing your phone with it may render your phone unrootable.
someonenewhere said:
HOW LEGIT IS THIS RUU THOUGH? who can co-sign it? my buddy wants to use it but doesn't want to take any chances..
Click to expand...
Click to collapse
I put it on my Hero with no problems. My guess is its very close to the RC. Or he could just wait!!
Once you have used this leaked RUU from Sprint, how do you go and flash one of the ROMs here? When I attempt to do it, I get a pic of a generic HTC phone with a red triangle and a red exclamation point. I have to do a battery pull to get it to go away.
Don't flash a ruu that doesn't have root. The exploits used to gain root are probably patched. Also this will over write your custom recovery. Leaving you with no way to flash custom roms. Wait until someone puts out a build with root.
tedya said:
Once you have used this leaked RUU from Sprint, how do you go and flash one of the ROMs here? When I attempt to do it, I get a pic of a generic HTC phone with a red triangle and a red exclamation point. I have to do a battery pull to get it to go away.
Click to expand...
Click to collapse
Sounds like you already installed the ruu I'm guessing?..lol.
You need flash a custom recovery to the phone now to be able to flash custom ROMs.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid backup your phone first thing >> Next you choose flash .zip and choose any custom ROM signed .zip on your sdcard to flash. >> After it flashes, reboot.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb remount
adb push flash_image.zip /system/bin/flash_image
danknee said:
Sounds like you already installed the ruu I'm guessing?..lol.
You need flash a custom recovery to the phone now to be able to flash custom ROMs.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid backup your phone first thing >> Next you choose flash .zip and choose any custom ROM signed .zip on your sdcard to flash. >> After it flashes, reboot.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Click to expand...
Click to collapse
Hi Dankee. I am having difficulties pushing flash_image. This is what I type/get:
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
Any ideas? Thanks so much.
tedya said:
Hi Dankee. I am having difficulties pushing flash_image. This is what I type/get:
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
Any ideas? Thanks so much.
Click to expand...
Click to collapse
you cant gain root in any other way now theres no known exploit for 2.1 yet so your basically screwed till someone finds a exploit next time gather information before you run some random program that hasnt even really been verified
Yeah, I have learned my lesson I think. I think I am going to wait around until there is an exploit for 2.1 before I end up bricking this thing. I ended up getting the flash_image pushed but now I can't reboot and use the recovery image. It goes straight to a HTC with red triangle and red exclamation point. Luckily I was able to do a battery pull and it rebooted straight to the RUU 2.1 ROM. I thought I had bricked the thing. Whew! I'll see what some of the masterminds come up with here.
I think all I am missing is being able to go into bootloader and do the v1.6.2 recovery image and then flash a custom ROM.
http://forum.androidcentral.com/htc-hero-roms-hacks/9542-how-repair-your-bootloader-a
http://forum.androidcentral.com/htc-hero-roms-hacks/9542-how-repair-your-bootloader-after-using-2-1-ruu.html
This worked for me thanks to GBhil!
Thanks SooooneR! This worked for me. I am flashing one of DamageControl's ROMs right now. Very cool.
Just like our USCC friends, I'm currently working on several mods for Cellular South's release of the Desire. I'll keep this post updated with new developments.
Linked is a custom boot.img from our stock ROM with apps2sd support. You will still need to download and flash the latest Darktremor apps2sd release and format your SD card accordingly.
How to flash?
Place the dphase-apps2sd-signed.zip file on the root of your sdcard and flash it as a zipped update.
Download Link (Cellular South, also confirmed working with Alaska Communications):
http://dphase.net/desire/dphase-apps2sd-signed.zip (2.3 MB)
MD5 checksum: 70df556ceb6891cbdcc3801d807d58af
US Cellular stock boot.img with apps2sd support
http://dphase.net/desire/dphase-USCC-apps2sd-signed.zip (2.3 MB)
MD5 checksum: e11b6f40b26811e252f0579f0ed5861c
Latest Darktremor apps2sd:
http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.1-adv-signed.zip
------------------------------------------------------------------------------------------
Zipaligned and PNG optimized system apps:
Code:
% du -sh original optimized
62M original
42M optimized
As you can see above, I've zipaligned and optimized the images in the system apps, which shaved off 20MB from total files size. This should lead to faster load times.
To install, untar the optimized archive to the directory of choice and boot to recovery. Mount the /system partition then do the following command with adb from within the directory holding the apk's (adb should be in your binary path, if not, fix that to make life easier in the future):
Code:
adb push . /system/app
You'll then see, for example:
Code:
push: ./DCSImpl.apk -> /system/app/DCSImpl.apk
push: ./HtcDialer.apk -> /system/app/HtcDialer.apk
push: ./EnhancedGoogleSearchProvider.apk -> /system/app/EnhancedGoogleSearchProvider.apk
... (etc)
Link:
http://dphase.net/desire/system_app_optimized.tar.gz (40MB compressed)
MD5 checksum:
2dc5fe2683e657006d2a8026c4ac32dc
reserved for later use
So what exactly does this accomplish? Is it basically adding apps 2 sd to the stock 2.1 rom? Any chance it will run on my US Cell desire?
Yes, adds apps2sd support to the stock rom. The latest a2sd will automagically move portions of /data over once it sees a properly formatted card.
In theory, this should work on USCC, but ymmv.
It is likely I won't get time tonight, but if I do, I'll be sure to give it a shot. I would like to get a2sd without a full reflash
con247 said:
It is likely I won't get time tonight, but if I do, I'll be sure to give it a shot. I would like to get a2sd without a full reflash
Click to expand...
Click to collapse
If it doesn't work, we'll grab your existing boot.img and I can tweak it.
Updates posted, please test and enjoy.
dphase said:
If it doesn't work, we'll grab your existing boot.img and I can tweak it.
Click to expand...
Click to collapse
That is the link to my boot.img
If you have time, if you could tweak that one, it would be great. If not, I'll give yours a shot tonight.
con247 said:
That is the link to my boot.img
If you have time, if you could tweak that one, it would be great. If not, I'll give yours a shot tonight.
Click to expand...
Click to collapse
I've modified your boot.img and placed a link in the first post.
dphase said:
I've modified your boot.img and placed a link in the first post.
Click to expand...
Click to collapse
A Big Thanks I am testing it now. I had to remember to change the MD5 information otherwise you get a fail.
Also You have to remember to run the apps2sd after the restore otherwise you will not boot!
Just booted and WOW look at all that new Space!!! Time to get more apps
seesser said:
A Big Thanks I am testing it now. I had to remember to change the MD5 information otherwise you get a fail.
Also You have to remember to run the apps2sd after the restore otherwise you will not boot!
Click to expand...
Click to collapse
Yes, I recommend installing apps2sd, formatting card, then applying new boot image.
How do you change the MD5 of the file
dphase said:
Yes, I recommend installing apps2sd, formatting card, then applying new boot image.
Click to expand...
Click to collapse
I guess I did it a little differently. I already had the sd card partitioned so I just took a backup swapped the boot.img and edited the MD5 with note++. Restored the modified backup and then ran the apps2sd.zip and rebooted.
I did it this way just in case something went wrong I could restore the backup that I didn't modify.
Going to try out that app optimize next.
Thank again.
This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte
bytethegroove said:
This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte
Click to expand...
Click to collapse
Hello and yes I was running that rom but did not like that friend Stream did not have twitter. with that rom you still had to tell the phone to move the files (a little bit of command line codding). With this boot.img and apps2sd on my stock rom backup I went from 15mb to 71mb so this one works great right out of the box.
I Explained how I did it from a backup of my stock rom up a few lines hope this helps.
I too am a little lost on this push of the app optimize. Could you explain it a little more? I have done a little adb shell programming but am lost with your directions.
Thanks,
bytethegroove said:
This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte
Click to expand...
Click to collapse
No, none of this can be flashed as a rom.
I'm not sure why anyone is changing MD5's, I included those so one could verify there was no data corruption during the download.
fixed. no worries..
con247 said:
I keep getting an MD5 mismatch after I edited the nandroid.md5 to the one in the original post
Click to expand...
Click to collapse
There is zero reason to edit that. Are you trying to use nandroid to flash the image? If so, that's the wrong answer.
con247 said:
fixed. no worries..
Click to expand...
Click to collapse
Did you restart the phone after you modified the MD5? I had that problem also until I restarted the phone and It worked after that.
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
Here is a dump of my /system/app and /system/framework that is deodexed/zipaligned. Its just the directories; its not flashable in CWM. I'll try and put together a stock zip later, but I don't have time at work. If someone else wants to do it, feel free to PM me a link and I'll host it.
For now, developers will know how to use this. In addition, if you feel brave, you can use the following steps:
Prework:
Download the zip. Extract it. Copy the deodex_app and deodex_framework directories to your external SD card.
1) Boot your phone into recovery
2) Mount /system and /sdcard from the mount menu
3) adb shell rm /system/app/*.odex
4) adb shell rm /system/framework/*.odex
5) adb shell cp /sdcard/deodex_app/* /system/app/
6) adb shell cp /sdcard/deodex_framework/* /system/framework/
7) adb shell chmod 644 /system/app/*
8) adb shell chmod 644 /system/framework/*
9) Wipe Dalvik cache from the advanced menu
10) Make sure /system, /data, and /sdcard are unmounted in the mounts menu
11) Reboot. It took about 5 minutes for my phone to boot and then it said "Upgrading Android" or something like that and went through 175 apps or so.
Download here.
ROM developers, feel free to use this to base your ROMs on. Please give credit for the base source of your ROM as always.
Edit: Clarified its also zipaligned.
Awesome!! I wish I was brave enough to try this..
So rom does this mean you'll be whippin up a kernel?? : ))))))
Sent from my SAMSUNG-SGH-I727 using xda premium
pingfl00d said:
So rom does this mean you'll be whippin up a kernel?? : ))))))
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I need the source which is not available yet. I suspect it will be shortly after this is OTA'ed. But yes, once it is, I will be updating my stock-ish
Procedure works perfectly.
At "Android is upgrading... " message now
Edit: Home button dead.
rjohnstone said:
Procedure works perfectly.
At "Android is upgrading... " message now
Edit: Home button dead.
Click to expand...
Click to collapse
My home button works fine. This seems to be a common problem if you restore with TiBu. Did you do that?
romracer said:
My home button works fine. This seems to be a common problem if you restore with TiBu. Did you do that?
Click to expand...
Click to collapse
Only user apps, no system data.
And the button worked prior to replacing files, so I'm curious what was deleted/changed that caused the button to stop working?
rjohnstone said:
Only user apps, no system data.
And the button worked prior to replacing files, so I'm curious what was deleted/changed that caused the button to stop working?
Click to expand...
Click to collapse
My guess would be something that "Android is updating..." did. I'm still not entirely sure what that is doing.
romracer said:
My guess would be something that "Android is updating..." did. I'm still not entirely sure what that is doing.
Click to expand...
Click to collapse
Most likely... no biggie.
Factory reset should take care of it.
Worst case, I have a nandroid backup.
Edit: factory reset didn't fix it... time for a restore.
I will try and add this too a zip. Thank you
EDIT:
I added this to my ROM. I am still working on ironing out all of the issues, but this helped!
http://forum.xda-developers.com/showthread.php?t=1566820
And if you want to mirror that would be amazing.
that actually worked perfectly! although you should probably add in there that people can use emmc instead of sdcard if they dont have an external card (i dont).
Thanks for this.
Sent from my SAMSUNG-SGH-I727 using xda premium
thanks
I waiting for .Zip flasheable
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Thanks romracer, always run into issues with the kitchen. I'm going to try your classpath includes in a sh script and see if it works where the kitchen hadn't.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2 Beta-4
mjwhirly said:
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Click to expand...
Click to collapse
I do most of it by hand. I'm a Linux/Windows System Administrator by day, so I'm comfortable with the command line I do use Cygwin for just about everything though rather than the Command Prompt.
promiseofcake said:
Thanks romracer, always run into issues with the kitchen. I'm going to try your classpath includes in a sh script and see if it works where the kitchen hadn't.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
The one liner I pasted in the other thread should work for both app and framework. It has more includes in the class path than are necessary for framework, but I don't think it'll break it.
It assumes the following:
You are in a directory with app, framework, deodex_app, deodex_framework and tmp subdirectories. app and framework contain the originals from the phone. The one liner should be run from this top level directory. I'd recommend doing framework first. You'll also need to Google java.awt.jar and put it in the framework directory too. Don't upload this to your phone though, its just needed for deodex'ing.
finally abit stable with these deodexed files
flash ics leak through odin
boot into android and get past the attready2go
flash cwm through odin
copy your deodexed files to sd and boot into cwm
follow your adb commands to copy and replace
reboot
only problems were superuser being a pain to flash in cwm. someone else mentioned toggle signature verification which is just before choosing your zip to install in cwm. looks good now.
mjwhirly said:
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Click to expand...
Click to collapse
i think the problem most people are having isnt related to the deodexing (anymore) but trying to flash it in CWM. it seems that flashable zips are messing up everything, as i used the same files i tried flashing in a zip this way and it works now. the zip version was unusable.
quikt said:
finally abit stable with these deodexed files
flash ics leak through odin
boot into android and get past the attready2go
flash cwm through odin
copy your deodexed files to sd and boot into cwm
follow your adb commands to copy and replace
reboot
only problems were superuser being a pain to flash in cwm. someone else mentioned toggle signature verification which is just before choosing your zip to install in cwm. looks good now.
Click to expand...
Click to collapse
That's basically exactly what I did (and my phone seems stable). Thanks for typing out the parts I left out
I've always had to flash the Superuser zip twice for some reason. I just flash it twice right on top of each other (without rebooting, exiting CWM, etc). Never have any problems in the actual OS doing it that way.
Grab the official Superuser zip from goo-inside.me/superuser