23/9/2010 12:00 I've been to the Chinese Mid-Autumn Festival. Who want flashable ROM zip file will be try:http://forum.xda-developers.com/showthread.php?t=742371 or http://forum.xda-developers.com/showthread.php?t=789830, thanks to NeoPhyTe.x360 and robocik!
fastboot video:http://www.youtube.com/watch?v=fipvwzuNyEE
download url:http://www.multiupload.com/AVHZ2WJ4M4
mirror url:http://vipme.com/ROM/desireHD/, thanks to zexbig.
This is NOT a flashable zip file.
It is a file collections for ROM Dev.
09-22 15:48 update patch:fix gps FC & vold issue & Youtube HD no video issue:http://www.megaupload.com/?d=7YJ6B7UR
flash it with ROM Manager or recovery menu.
Known issue:
1.camera can not work
2.Location,CarPanel FC sometimes.
Thanks all Dev from XDA! This file pack is based on DesireHD leaked RUU/Dump.
Requirement:
1.Desire Phone
2.custom recovery(AmonRA,ClockWork)
3.parted SDCARD with ext2/ext3, ext partition size not less than 512M.
4.radio version great than 32.42.00.32U_5.09.00.08
use it with follow step:
1.unzip the ownhere.DesireHD.zip
2.reboot your desire phone to recovery mode,for example:"adb-windows.exe reboot recovery"
3.wipe data,system,sd-ext
4.adb connect to phone, for example:"adb-windows.exe shell"
Code:
mkdir /sd-ext
mount /sd-ext
mount /system
mount /sdcard
5.push ownhere.desirehd.system.tgz,ownhere.desirehd.sd-ext.tgz,ownheredesire_v2.0_acekernel.zip to /sdcard
for example:
Code:
adb-windows.exe push ownhere.desirehd.system.tgz /sdcard/
6.adb connect to phone
Code:
cd /system
rm -r *
tar zxvf /sdcard/ownhere.desirehd.system.tgz
cd /sd-ext
rm -r *
tar zxvf /sdcard/ownhere.desirehd.sd-ext.tgz
sync
lost+found may be error, ignore it.
7.flash ownheredesire_v2.0_acekernel.zip with recovery menu.
8.reboot,the first boot time is long, about 5 mins.
you got it.
removed file:
Code:
Facebook
Twitter
teeter
Metal(skin)
Black(Skin)
Wood(Skin)
Flash
Maps
Quickoffice
all of these files can be found in Market or leaked RUU.
modified file:
Code:
Vending(Market)
/system/lib/hw/
/system/lib/egl/
build.prop
and some files i forgot...
all of these files can be restore from leaked RUU(But may be crash the system)
HOWTO extract file from DesireHD leak RUU 2.15:
run RUU_Ace_HTC_WWE_1.15.405.1_Radio_12.21.60.12_26.02.00.09_M_test_148662.exe in Windows box.Then some dialog appear(which include a 'next' button), look for your windows' temp dir, search the newest dir created by RUU, then copy rom.zip(about 277M) to another dir(or RUU will delete it automaticly).
send this rom.zip to Linux box,
in Linux box, unzip rom.zip, then
Code:
mkdir system
mount -o loop,ro system.img system
all files in system dir. you can simply copy files from it.
Ouch
I was hopeing for a flashable ROM ....
Well thx a lot man, now devs will be able to develop some great HD ROM
Would love to, Except I'm not Brave Enough
Excellent Work, Well Done!
KYI
first!
WELL DONE
edit: wasn't fast enough damn
sweet dude
Wow ! Thanks !!! :d
Thanks for sharing
ash1684 said:
Ouch
I was hopeing for a flashable ROM ....
Well thx a lot man, now devs will be able to develop some great HD ROM
Click to expand...
Click to collapse
It's because he is using the Sdcard as an extended System ftom what i know at least
can someone report if it works before i try
and ownhere take your place amoungst the xda legends
LOL rapidshare is already going 150 secs for a dl... they are getting overtaxed i advise everyone to use Megaupload... only 30 sec wait
Trying this now!
any one installed this ?
apologies for having doubted about you!!!GREATE job!
How is it working?
great now I need to learn adb but thanks now I can laugh at my cousin with cs hd
2
can anyone report on whats working and whats not?
NickChaplin said:
can anyone report on whats working and whats not?
Click to expand...
Click to collapse
according to the op everything works apart from camera app, neo said he will look into fixing it tho
AndroHero said:
according to the op everything works apart from camera app, neo said he will look into fixing it tho
Click to expand...
Click to collapse
am i correct in assuming that this rom doesnt have root access?
please make flashable zip
NickChaplin said:
am i correct in assuming that this rom doesnt have root access?
Click to expand...
Click to collapse
op said it rooted with apps2sd
Related
If you are like me and you like your stock Desire rom, you rooted it using unrEVOked or some other methods, you made some custom adjustment to it and you really don't want to load a fully fledged 3rd party rom but still, you'd like to tweak it a little bit more, you'll quickly realize that you are going to need a working init.d system in order to start custom scripts on boot.
This thread will try to explain how to add init.d support to your rom, without needing to flash a new rom and wipe everything, we're just going to flash a new boot.img.
Requirements
Rooted HTC Desire
New modified boot.img, supported firmware versions: 2.10.405.2, 2.29.405.2/5, check your firmware version here: (Settings -> About Phone -> Software information -> Software number)
Download this one: View attachment boot_2.10.405.2.zip if your "Software number" is: 2.10.405.2
Download this one: View attachment boot_2.29.405.2_5.zip if your "Software number" is: 2.29.405.2 or 2.29.405.5
Make sure you download the one matching your "Software number", the wrong one will cause boot loops and weird behaviors.
ADB shell access
flash_image binary, usually provided by unrEVOked under /data/local/flash_image but if you don't have grab it here: View attachment flash_image.zip
busybox correctly installed under /system/xbin
HOW-TO
NOTE: if your Desire is not S-OFF (meaning you can't write to the /system directory), you'll need to do the whole procedure in recovery mode.
Do a nandroid backup, this in order to save your current boot.img, and also because it's never a bad idea
Make sure the nandroid backup went ok
Check your exact firmware version (Settings -> About Phone -> Software information -> Software number) and download the corresponding modified boot.img
Copy and unzip the downloaded boot.img to your sdcard or wherever you like it
Obtain adb shell access, become root (su) and wipe the existing boot image with:
Code:
cat /dev/zero > /dev/mtd/mtd2
ignore the "write: No space left on device", it's normal.
Flash the new boot image:
Code:
flash_image boot /sdcard/boot.img
where "/sdcard/boot.img" is the path where you copied the downloaded boot.img
Remount the /system partition read-write if you're not in recovery mode:
Code:
mount -o remount,rw /system
or mount it if you are in recovery mode:
Code:
mount /system
Create the init.d directory where all the custom boot scripts will be executed:
Code:
mkdir /system/etc/init.d
and set permissions:
Code:
chmod 755 /system/etc/init.d
Important: unzip and copy the View attachment 99complete.zip script to the newly created /system/etc/init.d/99complete, set permissions:
Code:
chmod 755 /system/etc/init.d/99complete
and ownership:
Code:
chown root.shell /system/etc/init.d/99complete
Failure to do so will cause a boot loops.
Cross your fingers and reboot! If anything goes wrong you can always boot into recovery and fix errors or you can restore the nandroid backup (you can just restore the boot.img if you don't want to do a full restore).
From now on, every script you put inside /system/etc/init.d will be executed at boot before almost any other initializations. Make sure you set the correct permissions to your scripts (i.e. 755).
Thanks to: teppic74 for providing stock roms with init.d support (thread) where I extracted the boot images.
Technical explanation
The provided boot.img are the original HTC provided boot.img with the init.rc script modified to stop the init process until the cm.filesystem.ready property is set to 1:
Code:
start sysinit
on property:cm.filesystem.ready=1
class_start default
where the sysinit service is the service in charge of starting all the scripts inside /etc/init.d:
Code:
# Execute files in /etc/init.d before booting
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
and the last of this script, 99completed, only sets that property to 1 so the normal system boot can continue:
Code:
#!/system/bin/sh
sync;
setprop cm.filesystem.ready 1;
of course changing init.rc is only possible by flashing a new boot.img with init.rc modified inside the ramdisk because that file, even if you can see it under / will be overwritten at every boot.
Another small modification of the new boot.img is the default.prop, in which rc.secure is set to 0 allowing to gain direct access through "adb shell"
Sounds great
Thx for your work!
So if I get that right, it's the same as if we'd flash teppic74 ROM, and nandrestoring everything except system & boot?
Just our stock ROM with init.d support?
Does that also mean we could flash the optional mods from teppic74 thread like a2sd?
Ty again!
Puenos said:
Sounds great
Does that also mean we could flash the optional mods from teppic74 thread like a2sd?
Ty again!
Click to expand...
Click to collapse
Well you could but effectively all you need is an apps2sd+ script and you can adb push it to the correct location. /system/etc/init.d
Really? I would have tried flashing either a2sd provided in teppic74's thread or even a2sd script by DT? last I would have compared to firerat's script. But if all you need to do is pushing via adb.. Is there a script out for a2sd especially for stock/sense? (like kali advised using firerat with CM?)
Thank you
Not sure to be honest, I haven't used sense for a long time. But assume if the one teppic uses on his, works - it should work for you too.
I'm just using Sense because of it's Mail-widget, haha
But I guess I'll just give it a try then, will report back, when I've managed so set everything up without having my phone exploding, hehe
But thank you very much
exactly this boot.img will just enable init.d support, no need to flash a new system.img but you just need to create the init.d directory and put the 99complete script, after that you can install any mod you like, also the ones provided in teppic74's thread.
You can also try data2whatever by melethron (that's what I'm using), just make sure you have busybox correctly installed.
hope you enjoy it and happy new year!
well I hv software number 2.11.832.3 so what I hv to do...?
r3vb07inf said:
well I hv software number 2.11.832.3 so what I hv to do...?
Click to expand...
Click to collapse
unfortunately I don't have a boot.img for that software number, you'll need to manually extract your boot.img, modify a file (init.rc) and reflash it, if you don't know how to do it I can try to do it for you but I'll need a download link for your original firmware version
You could make a universal (froyo) update zip using Koush's AnyKernel installer, then you're able to update the ramdisk only and add the init.d folder/script. Thats how i did it for CM7.
worstenbrood said:
You could make a universal (froyo) update zip using Koush's AnyKernel installer, then you're able to update the ramdisk only and add the init.d folder/script. Thats how i did it for CM7.
Click to expand...
Click to collapse
interesting, an update script that can extract the boot.img, unpack, change files, repack it and reflash it...is it safe? I may think about building an update.zip this way but I'm pretty scared by how safe it can be to automatically mess with a boot.img..
EDIT: one problem of this is that the init.rc needs to be extracted and modified, but it may be different from one firmware and another
moebius83 said:
interesting, an update script that can extract the boot.img, unpack, change files, repack it and reflash it...is it safe? I may think about building an update.zip this way but I'm pretty scared by how safe it can be to automatically mess with a boot.img..
EDIT: one problem of this is that the init.rc needs to be extracted and modified, but it may be different from one firmware and another
Click to expand...
Click to collapse
Should be the same between all froyo rom's. Check this update zip, it's for gingerbread tho, you have to replace the ramdisk-new.gz with a froyo one (with edited init.rc offcourse). It also contains /system/etc/init.d/99complete.
Edit: Don't be scared, everyone who releases custom kernels uses this method. The other way around then, keep the original ramdisk and merge it with the new kernel.
Hello there
Really appreciate all your efforts
Kindaa feeling real dumb in comparison! lol
Anyways
My Desire specs :
2.2
2.32.415.3
Baseband 32.49.00.32U_5.11.05.27
Now this has built in arabic enabled support and that is the main reason I would like to keep it
Am yet to run into a custom ROM that would provide that without having to downgrade my version
Also, had a lotta fun trying to root, just couldn't root, up untill a few days back when unrevoked came out with thier new 3.3 version
I noticed you had only two software versions from which to start...
So what about my case? could you please help this newbie along?!!
docnasef said:
Hello there
Really appreciate all your efforts
Kindaa feeling real dumb in comparison! lol
Anyways
My Desire specs :
2.2
2.32.415.3
Baseband 32.49.00.32U_5.11.05.27
Now this has built in arabic enabled support and that is the main reason I would like to keep it
Am yet to run into a custom ROM that would provide that without having to downgrade my version
Also, had a lotta fun trying to root, just couldn't root, up untill a few days back when unrevoked came out with thier new 3.3 version
I noticed you had only two software versions from which to start...
So what about my case? could you please help this newbie along?!!
Click to expand...
Click to collapse
Same thing happens to me. My spec:
2.2
2.13.707.1
32.44.00.32U
Can you help as well? Or where or how (from RUU) can I find the ramdisk-new.gz as worstenbrood's mention.
mumu_li said:
Same thing happens to me. My spec:
2.2
2.13.707.1
32.44.00.32U
Can you help as well? Or where or how (from RUU) can I find the ramdisk-new.gz as worstenbrood's mention.
Click to expand...
Click to collapse
Thanks "worstenbrood" then I can extract boot.img from stock rom. Based on the guide, I made a new boot.img. But with this new boot.img, the phone hangs at the first screen(waiting at least for 15 mins). I don't know why. I also did as worstenbrood suggest and the system boot loopless.
Can somebody help?
I attached my boot.img (original and modified) for your information.
mumu_li said:
Thanks "worstenbrood" then I can extract boot.img from stock rom. Based on the guide, I made a new boot.img. But with this new boot.img, the phone hangs at the first screen(waiting at least for 15 mins). I don't know why. I also did as worstenbrood suggest and the system boot loopless.
Can somebody help?
I attached my boot.img (original and modified) for your information.
Click to expand...
Click to collapse
did you create the /system/etc/init.d directory and the 99complete file with the correct permissions? as noted on the OP this is needed because that file will tell the boot process to continue, otherwise you'll be stuck at the boot screen
EDIT: also, do you have busybox installed under /system/xbin?
docnasef said:
Hello there
Really appreciate all your efforts
Kindaa feeling real dumb in comparison! lol
Anyways
My Desire specs :
2.2
2.32.415.3
Baseband 32.49.00.32U_5.11.05.27
Now this has built in arabic enabled support and that is the main reason I would like to keep it
Am yet to run into a custom ROM that would provide that without having to downgrade my version
Also, had a lotta fun trying to root, just couldn't root, up untill a few days back when unrevoked came out with thier new 3.3 version
I noticed you had only two software versions from which to start...
So what about my case? could you please help this newbie along?!!
Click to expand...
Click to collapse
@ moebius83
If you could help, I would really appreciate it...
Please take into consideration That I am more or less android dumb!
I attached the url for my original RUU if that helps?
http://www.mediafire.com/?ih3lbbm7yfag7d2
Would REALLY appreciate your help.
Thanks m8!
mumu_li said:
Thanks "worstenbrood" then I can extract boot.img from stock rom. Based on the guide, I made a new boot.img. But with this new boot.img, the phone hangs at the first screen(waiting at least for 15 mins). I don't know why. I also did as worstenbrood suggest and the system boot loopless.
Can somebody help?
I attached my boot.img (original and modified) for your information.
Click to expand...
Click to collapse
i created a update.zip which replaces the ramdisk only and add /system/etc/init.d/99complete. It should work for every froyo release.
worstenbrood said:
i created a update.zip which replaces the ramdisk only and add /system/etc/init.d/99complete. It should work for every froyo release.
Click to expand...
Click to collapse
great job, I was just going to make the same update.zip, you were faster, I'll link it on the OP, thanks again!
Thread closed.
I may try to help. I'm afraid I won't be able to provide you a pure stock ROM because I will need at least to root and install Droid2 Bootstrapper to get access to nandroid backups. Also my firmware is based on Brazil Retail SBF (with english language available). Is that good for you? Do you have a place where I can upload it? Also, do you need the whole nandroid backup or just the system.img?
I'm actually painfully uploading system.img from a stock-rom nandroid.
I guess you don't care about data.img and cache.img...
Boot.img is not saved in milestone2/droid2 nandroid, is it mandatory ?
Very nice man !!! ;-)
momus87 said:
I'm actually painfully uploading system.img from a stock-rom nandroid.
I guess you don't care about data.img and cache.img...
Boot.img is not saved in milestone2/droid2 nandroid, is it mandatory ?
Click to expand...
Click to collapse
I don't think so as we won't be able to change it anyway. Even so, if you need boot.img, just open adb shell, get root, and type: cat /dev/block/boot > /sdcard/boot.img
help needed?
do you need more nandroids? i'm not a pro in this field, but i would like to help you.
so, what files do you need? just the *.img, clockwork creates by using the "backup"-option?
r2beta0 said:
I don't think so as we won't be able to change it anyway. Even so, if you need boot.img, just open adb shell, get root, and type: cat /dev/block/boot > /sdcard/boot.img
Click to expand...
Click to collapse
It isn't saved because the phone has a locked /boot partition. I don't need it since I'm not going to modify the /boot partition.
Status update:
Downloading Liberty DX & D2.
Downloading AOSP 2.2 image from Android sdk
Downloading Ubuntu 10.10
next:
Install Ubuntu & Setup SDK & stuff
Comparing which files are different between DX & D2
Comparing which files are different between AOSP & D2 (I'll use D2 as base)
Replacing D2 drivers with M2 ones
Uploading for test.
Here is the link to download system.img from french sbf for milestone2 :
http://www.4shared.com/file/7az7qWj8/system.html
momus87 said:
Here is the link to download system.img from french sbf for milestone2 :
http://www.4shared.com/file/7az7qWj8/system.html
Click to expand...
Click to collapse
Thanks, but I have enough files already, I'll start working rigt away
Status update:
Done downloading, backing up ROM files for access in Ubuntu.
Installing Ubuntu & Setup SDK & stuff
Next:
Comparing which files are different between DX & D2
Comparing which files are different between AOSP & D2 (I'll use D2 as base)
Replacing D2 drivers with M2 ones
Uploading for test.
Could anybody share me a layout of the / partition? In easy words:
1. Power up your phone and connect it.
2. Open up a command prompt.
3. Type in: adb shell ls / > text.txt
4. Upload text.txt to xda-dev's
preinstall
tmp
pds
cdrom
config
cache
sdcard
acct
mnt
d
etc
system
sys
sbin
proc
init_prep_keypad.sh
init.rc
init.mapphone_umts.rc
init.mapphone_cdma.rc
init.goldfish.rc
init
default.prop
data
root
dev
hahaaha weird for some reason there's a CDMA.rc in there.... weird for a GSM handset.
smacky_wolf said:
preinstall
tmp
pds
cdrom
config
cache
sdcard
acct
mnt
d
etc
system
sys
sbin
proc
init_prep_keypad.sh
init.rc
init.mapphone_umts.rc
init.mapphone_cdma.rc
init.goldfish.rc
init
default.prop
data
root
dev
Click to expand...
Click to collapse
Thanks, could you
adb pull /init_prep_keypad.sh
adb pull /init.rc
adb pull /init.mapphone_umts.rc
adb pull /default.prop
and then zip & upload them for me?
Found some way of hijacking init.rc, making CM possible. It's hard though.
that should do it...
man, lucky i know linux mostly. i've been doing this via terminal on handset.
smacky_wolf said:
that should do it...
man, lucky i know linux mostly. i've been doing this via terminal on handset.
Click to expand...
Click to collapse
Thanks, that really helps
Great job man!
Good luck and success in this ROM !!
look forward!
Great news, I'm making awesome progress. It's just that I'm on windows right now and need some deodexed apks
Stk.apk
WeatherWidget.apk
LatinIME.apk
PhoneConfig.apk
maybe this?
actually nevermind, am pulling the proper files from xUltimate atm
here we go, these are properly deodexed.
This will be the custom recovery beta thread for Micromax a60 recovery. Split from main thread to keep it on topic.
Test Version: Note I do not have this phone and was asked to add this to my recovery lineup.
Directions:
Download this recovery and copy to root of sdcard
see post 162 for latest http://forum.xda-developers.com/showpost.php?p=14393032&postcount=162
download flash_image.zip and unzip and copy to root of sdcard
flash_image.zip
Download this and copy to root of sdcard (do not unzip)
signed_test_flash.zip
commands to flash recovery
from adb shell or terminal (requires root # prompt)
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (notice this file install-recovery.sh may not be on your device if it gives an error or file not found move on)
flash_image recovery /sdcard/recovery-a60-gnm.img (or name of recovery.img)
sync
then power off device and boot holding "HOME" key
Please test nandroid backup/restore by using the nandroid backup and restore option
Please test usb mass storage in recovery
Please test flashing of signed-test_flash.zip which if successful will place test-flash_file in /system/bin
Please test key mapping if if it is wrong use keycode debugging under other menu and send me keymapping and keycodes. IE. vol-up is keycode 000 etc
Key mapping is Vol-up & Vol-down move selection up & down. Back is backup a menu. Menu key is to select.
This is a test version I'll do full release soon after bugs (if any) are worked out.
For debugging use the move recovery-log to sd option under other and please upload it with feedback.
Appreciate the thanks guys. However, its been nearly 2 days now with no feedback. Can someone try and test to make sure everything is working as intended?
vijkap,His phone does not boot up.
I think now borax12 only having full working mobile.
He will online at above 2:30GMT.
I tested but the text on the recovery was not readable. It was only responding to volume up-down, ( as you have said now only I read the instruction ). I tried to select options with menu key, even a level down text was not readable.
I got an error "mtd: not writing bad block at 0x002c0000" one time I tried
Code:
flash_image recovery /sdcard/recovery-a60-gnm.img
The first time I tried
Code:
cat /sdcard/flash_image > /system/bin/flash_image
I got /sdcard/flash_image: No such file or directory, just added for documentation. Thanks to @drellisdee and others. Should I try once more, pls let me know.
Seems like options are working. My phone reset to default or something when I selected an option (not readable!) and my installed apps are missing
victor px5 said:
Seems like options are working. My phone reset to default or something when I selected an option (not readable!) and my installed apps are missing
Click to expand...
Click to collapse
Sounds like it. Seems you selected data wipe. Please setup adb drivers if you havent already. In recovery do this to test nandroid. Adb shell nandroid-mobile.sh --backup
Can someone verify the resolution of this device ie. Wvga, hvga etc. It need to look at resolution for the ui stuff.
When you say text isnt readable do you mean its not there or to small or jumbled to read. Try to take screen shot with adb shell ddms or adb shell ./ddms
qvga (240x320)
Its Resolution is QVGA.
Sorry for Double post.
Text is not small. Looks like the frequency is not correct, that is my guess.
I too got the same thing. It's unreadble. resolution problem may be. It should be QVGA 240x320. Thats what i think.
Installed this custom recovery through an app called "recovery flasher", which can be downloaded from the market.
Maybe the recovery screen should look like this
drellisdee, please rework on custom recovery to suit qvga. Meanwhile I'm still struggling with my phone. I'll be taking it to micromax support for a fix.
rushank2112 said:
Maybe the recovery screen should look like this
Click to expand...
Click to collapse
Yes that's similar to what its supposed to look like. Can someone give me a nandroid boot.Ingram upload and include a md5sum. If wondering if the rexocovery dump I used got corrupted in the uploading/downloading as it had no md5sum. I've never had a result like that and made 10+ recoveries.
drellisdee said:
Yes that's similar to what its supposed to look like. Can someone give me a nandroid boot.Ingram upload and include a md5sum. If wondering if the rexocovery dump I used got corrupted in the uploading/downloading as it had no md5sum. I've never had a result like that and made 10+ recoveries.
Click to expand...
Click to collapse
Does this link contains any useful stuff for Micromax A60.
http://code.google.com/p/android-roms/downloads/list
rushank2112 said:
Does this link contains any useful stuff for Micromax A60.
http://code.google.com/p/android-roms/downloads/list
Click to expand...
Click to collapse
https://github.com/packetlss/android_bootable_recovery
I think he does not ask that.
He asked boot.img and recovery.img with md5sum.
rushank2112 said:
Does this link contains any useful stuff for Micromax A60.
http://code.google.com/p/android-roms/downloads/list
Click to expand...
Click to collapse
I hope this will work? Sorry for the earlier post. Actually i'm a newbie. I thought i should help.
http://www.receptorblog.com/wordpress/nandroid-gets-working-new-recovery-image/
Sorry guys if i'm making some blunders out here, but my intention is just to help you.
drellisdee said:
Yes that's similar to what its supposed to look like. Can someone give me a nandroid boot.Ingram upload and include a md5sum. If wondering if the rexocovery dump I used got corrupted in the uploading/downloading as it had no md5sum. I've never had a result like that and made 10+ recoveries.
Click to expand...
Click to collapse
drellisdee here is the link. Hope you find it useful.
http://www.multiupload.com/VZPRKLQH3T
vijkap said:
drellisdee here is the link. Hope you find it useful.
http://www.multiupload.com/VZPRKLQH3T
Click to expand...
Click to collapse
Hey dude, the link which you have posted is the link for Stock ROM. I extracted the content of the zip and i found stock boot.img and stock recovery image. Its not a nandroid boot image or recovery image. They are stock images.
DISCLAIMER: I am not the author of this tool!
All credits goes to tommytomatoe and you can press thanks in this thread because there is no dedicated thread for DEXO @xda (at least I found none)
theking_13 said:
thiagomme said:
Why does it give better battery life? Thank you.
Click to expand...
Click to collapse
Because it splits the .apk (app package) into two parts, the .apk and a .odex file. Usually, for the phone to use an app, it has to decompile the .apk and get the parts it needs to run the app. With the odex files, which stands for "Optimized Dex" the startup time is much faster since the phone doesn't have to perform any optimizing at startup/runtime, and because of that, it also uses less CPU power, and thus makes it faster, smoother, and battery life is increased.
Click to expand...
Click to collapse
OK. So what is this tool?
This tool doesn’t deal with partially odexed ROMs. This tool is for odexing a ROM that is completely DEODEX.
The benefits? Faster boot, smaller imprint on /data/ partition, overall faster feeling
The myths? I can’t theme ODEX! WRONG! You can theme odex just fine! Just use baksmali and smali.
Click to expand...
Click to collapse
Requirements:Of the author:
adb
Linux, Mac OS X, Windows
Android device with busybox
Four minutes of your day
Added by me:
You have finally settled on a ROM that you want to use for some time without an intention to modify it further
You will need about 100 MB free space on system (my free space decreased from 160 MB to 96 MB after the completion of the process) To free some you can delete some apps from /system/app or move them to /data/app with a root file explorer (do not forget to set the correct permissions afterwards) or even better: to move your /system/lib folder to the lib partition without reflashing the ROM (see below for details)
Tested on Fallout 5.0 and Virtuous Infinity 1.35 with my Tweaked3 8.6 kernel. If you are using this it is at your own will and risk
NOT WORKING on CoolDroid and Sabsa Prime 6.5, probably because they have mixed framework from different Sense versions! Do not do on other similar ROMs only on ones with an original (even modded) framework!
Procedure:Go here and read carefully. It is basically some adb commands.
Out of respect to the author I will not mirror his link nor the instructions----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------How to free about 120 MB space on /system by moving the lib folder to its dedicated partition without reflashing the ROM
This is only for ICS Sense ROMs. AOSP ROMs have enough free space to run the script without issues. I am not sure about the GB Sense ROMs, but if I remember correct they have enough free space on /system too. (if I am wrong please PM me to add GB Sense boot.img)
Requirements:
Bootloader with /system/lib support: 2.xx or 7.xx
150 MB free space on your SDcard
adb drivers installed (link in my signature)
4EXT Recovery (or any other recovery that has a menu entry for mounting /system/lib partition)
good attention while copy/paste the commands from here. One typo will lead to a bootloop
Download Tweaked3: XI_lib_bootimg.zip
md5sum: 1bc1d645b8212cdb2e4e949c6b7b3312
Download Patched: 3089_lib_bootimg.zip
md5sum: f1ae0228eb4057b4e4c4934a1e8a0515The zips contain boot images of my Tweaked3 and Patched kernels with /system/lib support (I am not advertising them but this are the files I have ready, you can use a Stock kernel as well). There are 4 of them:
Sense4_lib_boot.img - for ALL Sense 4 ROMs (except VIrtuous Infinity)
Sense36_exp_lib_boot.img - for custom Sense 3.6 ROMs with experimental WiFi driver (Experimental kernel)
Sense36_lib_boot.img - for custom Sense 3.6 ROMs with stock WiFi driver (Stable kernel)
Virtuous_lib_boot.img - the name speaks for itself
Extract the archive in the folder where your fastboot executable is. This is not a flashable zip!orDownload 2: b2b_lib_bootimg.zip
md5sum: 4bb4d44506eae5f247b69f9c5663e3a8The zip contains boot images of my B2B kernel with /system/lib support (I am not advertising it but this are the files I have ready, you can use a Stock kernel as well). There are 2 of them:
Sense4_lib_boot.img - for ALL Sense 4 ROMs (except VIrtuous Infinity)
Sense36_lib_boot.img - for custom Sense 3.6 ROMs
Extract the archive in the folder where your fastboot executable is. This is not a flashable zip!NOTE: your ROM has to be on the same version of the kernel before the procedure, otherwise your WiFi will stop working. Or you will need to download the zip from the kernel thread and copy the modules to /system/lib/modules manually giving them right permissions (644 or -rw-r--r--)Procedure:# Connect the device to PC, open Command Prompt (cmd) and browse to the folder where are your adb and fastboot executables are (example: cd C:\android-tools)
# Reboot to Recovery (4EXT recommended)
Code:
adb reboot recovery
# Make a Nandroid backup
# Mount manually /system and /sdcard from the "mounts | storage" menu of the Recovery
# Copy the content of /system/lib to the SDcard
Code:
adb shell
mkdir /sdcard/system
cp -r /system/lib /sdcard/system
# Clean /system/lib
Code:
rm -r /system/lib
# Recreate empty /system/lib and set permissions
Code:
mkdir /system/lib
chmod 755 /system/lib
# Unmount manually /system from the "mounts | storage" menu of the Recovery
# Mount manually /system_lib from the "mounts | storage" menu of the Recovery
# Copy the lib contents to /system/lib
Code:
cp -r /sdcard/system/lib/* /system_lib
# Set permissions to /system/lib
Code:
cd /system_lib
find . -type d -exec chmod 755 {} \;
find . -type f -exec chmod 644 {} \;
[I]# Creating symlinks [COLOR=Red]Only for Virtuous Infinity![/COLOR][/I]
ln -s libhtc_ril.so librilswitch.so
cd hw
ln -s copybit.msm8660.so copybit.msm7x30.so
ln -s gralloc.msm8660.so gralloc.msm7x30.so
ln -s lights.msm8660.so lights.msm7x30.so
# Remove the SDcard /system/lib folder
Code:
rm -r /sdcard/system
exit
# Unmount manually /system_lib and /sdcard from the "mounts | storage" menu of the Recovery
# Reboot to bootloader
Code:
adb reboot bootloader
# Flash the boot.img and reboot
Code:
fastboot erase boot
fastboot flash boot XXX_lib_boot.img
fastboot reboot
Now you can use the tool above without concerns about free space
Enjoy!
amidabuddha, thanks for sharing. Have you tried this?
old.splatterhand said:
amidabuddha, thanks for sharing. Have you tried this?
Click to expand...
Click to collapse
Yes of course. Read the Requirements part
Sent from my HTC Desire S
Ok, i need help, cause i don't do this things often:
Fifth step, run it!
Click to expand...
Click to collapse
What and how?
old.splatterhand said:
Ok, i need help, cause i don't do this things often:
What and how?
Click to expand...
Click to collapse
Read further in the instructions, Theres a complete usage example with all the commands
Sent from my Desire S using xda app-developers app
Gonna try it today on CM10.
Tapatalked from Desire S running Andromadus
teadrinker said:
Read further in the instructions, Theres a complete usage example with all the commands
Click to expand...
Click to collapse
Sorry, my fault! I thought this come after the 5 steps.
if a rom is zipaligned, doesn't this mean that there's no need being odexed - kind of same thing? (same performance, battery life...)
i've read that, but i'm no expert...
toxic-hero said:
if a rom is zipaligned, doesn't this mean that there's no need being odexed - kind of same thing? (same performance, battery life...)
Click to expand...
Click to collapse
Zipaligning is about better RAM utilization. Odexing is about reducing the Dalvik VM which in theory should reduce CPU use and make the system run smoothly. You can watch the video, it is made by one of the Elite Recognized Developers of XDA so this guy probably knows what he is talking about. Moreover ALL Stock ROMs are odexed and I am sure that the companies developers are not just too lame to use it for nothing
tried the above...pasted something wrong and now phone stuck on htc screen and can't get into recovery
mackhenri said:
tried the above...pasted something wrong and now phone stuck on htc screen and can't get into recovery
Click to expand...
Click to collapse
Have you provided enough free space on your system partition? Try with a factory reset.
And once again:
If you are using this it is at your own will and risk
Click to expand...
Click to collapse
i think it was due to less space but still will try it once again after making space
Was a hard task to get enough space free.
Let's see how it works now.
old.splatterhand said:
Was a hard task to get enough space free.
Let's see how it works now.
Click to expand...
Click to collapse
Yes this may be an issue with the bigger ROMs. The easiest way is to move some app that you use rarely to /data/apps
The other way is to use the lib partition but this needs ramdisk modification and a hboot that supports it. It is not hard I may add a small how-to if more users want to use this tool
Sent from my HTC Desire S
amidabuddha said:
Yes this may be an issue with the bigger ROMs. The easiest way is to move some app that you use rarely to /data/apps
The other way is to use the lib partition but this needs ramdisk modification and a hboot that supports it. It is not hard I may add a small how-to if more users want to use this tool
Sent from my HTC Desire S
Click to expand...
Click to collapse
Get it on buddy.....I am ready to try whatever u make as you seem to give life to my phone once again and all the devs here and I am become a flashaholic...
Sent from my HTC Desire S using xda premium
amidabuddha said:
The other way is to use the lib partition but this needs ramdisk modification and a hboot that supports it. It is not hard I may add a small how-to if more users want to use this tool
Click to expand...
Click to collapse
This would b great, I did it once for Fallout with one of your kernel ramdisks, but it was not so trivial and a pain in the a** doing this all by hand. Though it worked perfectly, I don't remember every step I did, and mayb I didn't do it the elegant way, as I'm not very experienced.
As far as I remember the complicated part was unpacking kernel+ramdisk, modifing ramdisk, repacking everything and signing it. But this has to be done only once (by one idividual) for every kernel (+ramdisk). The rest ist more or less flashing and copying from /system to /system/lib partition (can be done in recovery easily). The latter mayb realised with one single script installer for every kernel (and rom) I guess. But here I also lack the experince with script installers, elsewise I would have shared the info.
I did it on Windows with bootimg-tools via Cygwin (unpacking, repacking), with SignApk on cmd (signing), in recovery (flashing, copying). For flashing I guess fastboot is more elegant (reflashed whole rom with mod boot.img). For the rest I didn't found something more convinient, but maybe soemone can enlighten me.
HOW-TO move your /system/lib folder to the dedicated partition added to the first post. Tested and verified working. Just copy the commands carefully
Enjoy!
Thx, the new guide worked like a charm for me on Fallout v5.0.0 with your kernel v8.5. I think it is more or less what I did, when it worked for me before. Also the odexing stuff worked well. What I am just wondering about, as this is odexing Rosie, will this affect the Fallout Tweaks for Rosie? And I tended to use Titanium Backup to merge updated system apps (like Facebook) into rom (essentially moving to system I guess), are there any drawbacks doing it with odexed apps?
kwisatz79 said:
Thx, the new guide worked like a charm for me on Fallout v5.0.0 with your kernel v8.5. I think it is more or less what I did, when it worked for me before. Also the odexing stuff worked well. What I am just wondering about, as this is odexing Rosie, will this affect the Fallout Tweaks for Rosie? And I tended to use Titanium Backup to merge updated system apps (like Facebook) into rom (essentially moving to system I guess), are there any drawbacks doing it with odexed apps?
Click to expand...
Click to collapse
All apps will work the same way after odexing. I can confirm all Rosie tweaks in Fallout working.
As per the Titanium stuff I have no idea try it and let us know
Sent from my HTC Desire S
when I am trying to copy /sdcard/system/lib to /system_lib it is showing not enough space....
Also in 4extrecovery - two system_lib are showing...
Any ideas?
BTW I am on Fallout 5.0...
!!!!!CAUTION: This recovery works only flawlessly on Breeze tabs with the serialnumbers containing a C! E.g. 93016Z3Cxxxxxxx!!!!!
Hi,
Finally I made it to get CWM Recovery up and running for Trekstor Surftab Breeze.
Before starting a huge thanks to my tester X-On, who tested every crappy CWM Image I made until we got a good one! Also thanks to my other tester Snackez, whose tab didn't make it as I made a silly mistake, which caused the tablet to just display a black screen.
The usual stuff:
I am not responsible for any bricks or other damages made to your tablets! But chances are minimal now.
For the reference I pasted here the contents of the recovery.fstab file:
Code:
# mount point fstype device device2
/boot emmc /dev/block/nandc
/system ext4 /dev/block/nandd
/data ext4 /dev/block/nande
/misc emmc /dev/block/nandf # here the flag to boot from the recovery partition is set. 16MB wasted for this!
/recovery ext4 /dev/block/nandg
/cache ext4 /dev/block/nandh
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/nandk
Current status:
So, after the 2nd fiasco with the 6.x.x.x CWM, I reverted back to the 5.0.X.X base, where at least the power button works. Also I found out how to break the CWM boot loop, unless you got a working adb shell:
Code:
dd if=/dev/zero of=/dev/block/nandf conv=notrunc count=20 bs=1
In my new release I've soft linked the sh binary to /system/bin, so adb should work right out of the box. Also I've added a new service calling sh, which calls postrecoveryboot.sh (containing above code snippet), so that it should definitely be executed.
Now, 02-01-2013, Backup to internal and external SD is possible without problems...see the known problems section for any other bugs.
So, here it is!
http://ul.to/fx8vsnj3
or attached.
Instructions:
1. Download the rar archive and unpack it onto your internal SD card
2. Fire up either ADB shell or download any terminal emulator from the play store and type:
Code:
$ su
# dd if=/dev/block/nandg of=/sdcard/recoverystock.img
# dd if=/sdcard/recoveryBreezeNew.img of=/dev/block/nandg
3. Turn of your tab.
4. Keep pressed the volume- key and press power until the screens lights up
5. Keep volume- pressed until you see the CWM menue
If for some reason you want to switch back to your stock recovery, you need to fire up adb shell again or your terminal emulator and type:
Code:
$ su
# dd if=/sdcard/recoverystock.img of=/dev/block/nandg
I will make a flashable CWM zip for getting the stock recovery back while being in recovery mode. Should be comfortable doing so
Known problems
1. Mounting USB Storage is not possible while getting an error message like "cannot open ums lunfile". I googled a bit it doesn't seem so easy to fix...
Regards
TheSSJ
Hi TheSSJ,
I would be interested in testing the CWM but is there a way to backup the original system since no firmware or ROM are available right now?
Keep the good working !!
Hi,
unfortunately not...I don't know why trekstor is so slow at releasing the original firmwares...
Still wanna do it?
regards
Hell Yeah!
new?
Push! Updated now with a working release! Thanks snackez and X-On for your help in testing!
good news! : Good:
thank you
have you managed to get the source code to make us a nice custom rom?
in any case, thank you for your work!
sorry for my bad english, i'm french
Hi,
no, unfortunately I'm no good ROM cooker (also there are no sources available, don't know why ). But the CWM is the first step to begin testingfor new ROMS...
Greets
If I understand, you know save / retrieve the original rom?
So this principle, it remains to find a cook to modify / improve the rom?
On the new recovery that you do, I test tonight ...
Thank you for your work, hoping that other developers are also working on
I just installed your CWN and it works great!
I did a Backup of the ROM and then removed a Hell of a lot Stock apps and added some new. The tablet got significantly faster (It feels faster).
Thanks a lot!
New update with fixed mount points. Only the mount usb storage function doesn't want to work...
Great new !
Thank you for your job !
Original Firmware
I have done your task. Works great.
But i have done a mistak.
Now i dont have a backup from the original.
Where can i found original Trekstore Firmware for breeze 7.0 ?
I have to flash my pad.
thank you for your work. no problem for installation
der-blizzard said:
I have done your task. Works great.
But i have done a mistak.
Now i dont have a backup from the original.
Where can i found original Trekstore Firmware for breeze 7.0 ?
I have to flash my pad.
Click to expand...
Click to collapse
https://www.dropbox.com/s/xtwzqq2sjmgastr/708_FW_updatepack.zip
TheSSJ said:
https://www.dropbox.com/s/xtwzqq2sjmgastr/708_FW_updatepack.zip
Click to expand...
Click to collapse
someone found some rom for this tablet?
TheSSJ said:
https://www.dropbox.com/s/xtwzqq2sjmgastr/708_FW_updatepack.zip
Click to expand...
Click to collapse
Sorry, but the link does not work.
rik81 said:
Sorry, but the link does not work.
Click to expand...
Click to collapse
Maybe because my post was from 18th January?
http://ul.to/w8vrr5oj
Regards
TheSSJ said:
Maybe because my post was from 18th January?
http://ul.to/w8vrr5oj
Regards
Click to expand...
Click to collapse
Yes of course
But i can't open the last one
Thank you
Hey guys i search for cwm for the d Serie can anybody help me ?
Send from my Samsung Galaxy S3 I9300