Database Info

{KERNEL-SOURCE} GoDmOdE-EVO-2.6.29 {Make Shift Kernel}[SENSORS-LIGHTS-PANEL-FIXED]

THIS SOURCE WILL WORK ON ALL CURRENT HTC EVO'S!!!
i found the board files for the EVO a while back but wanted to wait til we at least had the release RUU to release it. now the actual kernel itself isnt a EVO kernel. its actually an Incredible kernel source with the EVO board files in it. that said i had to mod the board files a little to get it to compile. anyhow link below and remember to fork as it helps github and everyone. thanx
GoDmOdE-EVO
Commit log:
Sat May 22, 2010 - First-commit-0_o = first commit
Sat Jun 19, 2010 - Fix the wimax LED, capella prox sensor. Add epson panel support for supersonic
(panel_type=0), which is present on
hardware revision 3. Implement 9bit spi. - by Joe Hansche (maejrep)
Sun Jun 20, 2010 - Add some more epson vs novatec fixes - by Joe Hansche (maejrep)
Mon Jun 21, 2010 - Fix proximity sensor and Implement wimax LED control. These commits also fixed issues with all other sensors, and enabling them to all work!!! - by Joe Hansche (maejrep)
THIS IS A UPDATE.ZIP THAT CAN BE USED WITH FRESH ROM, TO BOOT THIS KERNEL WITHOUT WIPING. PLEEEEEESE DO A NANDROID BACKUP BEFORE FLASHING THIS UPDATE.ZIP. SO U CAN JUST NANDROID RESTORE UR DEVICE BACK TO NORMAL AFTER UR DONE PLAYING . ANYHOW CAMERA IS NOT WORKING AND THERE SEEM TO BE WHATS THOUGHT TO BE VSYNC ISSUES. ANYHOW ENJOY!!!
http://link.geekfor.me/godmodefreshhh
of course dont turn this thread into a this is broke can u please fix it thread.
IF U WOULD LIKE TO HELP OUT OR BUILD UR OWN KERNEL FROM THIS SOURCE, PLEASE FORK. THIS IS ADVISED BY GITHUB AND ALSO BY ME. AS IT MAKE PULLING CHANGES TO AND FROM BRANCHES MUCH EASIER. THIS IS A GOOD THING FOR U AND ME. IF I MAKE A COMMIT U WANNA ADD U CAN EASILY SYNC UP WITH ME AND VICE VERSA. WORKS OUT GREAT FOR EVERYONE AND KEEPS US COMPLETELY OPEN, AFTER ALL WERE ALL ON THE SAME TEAM.

ToAsTcFh For MOD!!!! This is genius

Im a little too buzzed atm. What exactly is this and what does it mean for us? explain and ill understand it in the A.M.

Trying to take over the Evo forums already Toast? ha ha Good to know we are going to have good devs on this board. Still running your kernel on my Hero. That is until my Evo arrives today and I start trying to root it

chuckhriczko said:
Trying to take over the Evo forums already Toast? ha ha Good to know we are going to have good devs on this board. Still running your kernel on my Hero. That is until my Evo arrives today and I start trying to root it
Click to expand...
Click to collapse
how're you getting your evo today??

so far i know a lot of good devs coming over. im pre-ordered so as soon as it shows up at best buy ill be struggling for root again.

justinisyoung said:
how're you getting your evo today??
Click to expand...
Click to collapse
Ebay? Craglist?
ppl from the google i/o event selling them

YoungAceAtlanta said:
Ebay? Craglist?
ppl from the google i/o event selling them
Click to expand...
Click to collapse
Yep. eBay. It's a Google I/O device. Paid a HEFTY premium for it but it's worth it to get it two weeks early for me.

toastcfh said:
so far i know a lot of good devs coming over. im pre-ordered so as soon as it shows up at best buy ill be struggling for root again.
Click to expand...
Click to collapse
Awesome. Who else that you know of? I know I stopped devving for the Hero but I can't wait to start devving for this thing. This community is going to be epic!

Right on toast, this is awesome.

fantastic toast

can this kernel be loaded onto one of the google I/O event EVOs to test?

The device isn't root yet

toastcfh said:
The device isn't root yet
Click to expand...
Click to collapse
now i see the catch 22...sorry im new to all this and dont have an EVO to experiment with...
could this kernel be combined with the standard ramdisk into a boot.img, packaged into a signed update.zip and installed through the stock recovery?

joeykrim said:
now i see the catch 22...sorry im new to all this and dont have an EVO to experiment with...
could this kernel be combined with the standard ramdisk into a boot.img, packaged into a signed update.zip and installed through the stock recovery?
Click to expand...
Click to collapse
No. You can't flash anything worthwhile until the phone is rooted. Once this happens expect this forum to explode.

No we need root and the ability. To flash a custom recovery. Basically. The catch 22 is we need root before we can do anything custom

By flashing an updated NBH, doesn't that overwrite both the Kernel and the OS on the NAND? If so, couldn't we replace the Kernel with one with root, and also provide for our own (AOSP, etc.) builds of Android?
Essentially, I'm wondering what the breakdown process is for recovery. The bootloader (Power + Volume on boot) is stored on the ROM, so regardless of "bricking" your device, you should always be able to get back to the bootloader to recover, correct?
If that's the case, what stops us from simply building an NBH with the current (locked) Kernel, but with modified system files for our own ROM?

Shidell said:
By flashing an updated NBH, doesn't that overwrite both the Kernel and the OS on the NAND? If so, couldn't we replace the Kernel with one with root, and also provide for our own (AOSP, etc.) builds of Android?
Essentially, I'm wondering what the breakdown process is for recovery. The bootloader (Power + Volume on boot) is stored on the ROM, so regardless of "bricking" your device, you should always be able to get back to the bootloader to recover, correct?
If that's the case, what stops us from simply building an NBH with the current (locked) Kernel, but with modified system files for our own ROM?
Click to expand...
Click to collapse
we're thinking alike here. some of this terminology is new to me and some isnt. hopefully this makes sense. im gonna reword but ask the same question as above (at least i think same question) plus another question. im doing a lot of research and tryin to word things correctly...
this might be the same question as above, are we able to trick the supersonic RUU released here into loading our own rom.zip file (NBH)? (we were able to do this with the samsung moment)
if not, are we able to use the fastboot-bootloader mode (samsung moment doesnt have this) to install a custom recovery? if so, we are then waiting on a custom recovery to be developed?

I think we are heading down the same path.
My understanding is that flashing a new "ROM" via NBH will replace both the Kernel and the OS (Android) files on the NAND, as both live there. The only item that lives in the ROM itself is the bootloader, which should always persist. With this understanding, even if you totally destroy your Kernel and/or Android OS, you should always be able to power the device to bootloader mode (Power + Volume) to flash (and therefore replace/restore) a new Kernel/OS to your phone.
If that's the case, then root access isn't necessary. All root access will allow us to do is some fancy side operations, like running a ROM (OS) manager inside Android--and who really wants to do that? Most of us want to be able to load a single custom build of Android, optimized and designed the way we want, right?
My thought process is this:
HTC should be releasing the EVO Kernel source on developer.htc.com by the official launch. With that, we can compile the Kernel ourselves (if we can't otherwise find it compiled) and theoretically bundle that with our own OS compilation of Android into a .NBH. This .NBH could then be flashed via the bootloader, replacing both the stock OS and the Kernel with what we've bundled.
This would seem to mean we wouldn't have root access, but we wouldn't need it, as we could simply update the OS files, build an .NBH, and provide it to users to flash. This could mean that custom distros would be a single contained file--one file to flash and that's it, you're updated.
Thoughts? Is this accurate?
If this is the case, we should start looking at the Kernel and the .NBH format rather than obtaining root, because once we understand the .NBH, we can load whatever we want (including a Kernel with root access, if desired.)

Shidell said:
I think we are heading down the same path.
My understanding is that flashing a new "ROM" via NBH will replace both the Kernel and the OS (Android) files on the NAND, as both live there. The only item that lives in the ROM itself is the bootloader, which should always persist. With this understanding, even if you totally destroy your Kernel and/or Android OS, you should always be able to power the device to bootloader mode (Power + Volume) to flash (and therefore replace/restore) a new Kernel/OS to your phone.
If that's the case, then root access isn't necessary. All root access will allow us to do is some fancy side operations, like running a ROM (OS) manager inside Android--and who really wants to do that? Most of us want to be able to load a single custom build of Android, optimized and designed the way we want, right?
My thought process is this:
HTC should be releasing the EVO Kernel source on developer.htc.com by the official launch. With that, we can compile the Kernel ourselves (if we can't otherwise find it compiled) and theoretically bundle that with our own OS compilation of Android into a .NBH. This .NBH could then be flashed via the bootloader, replacing both the stock OS and the Kernel with what we've bundled.
This would seem to mean we wouldn't have root access, but we wouldn't need it, as we could simply update the OS files, build an .NBH, and provide it to users to flash. This could mean that custom distros would be a single contained file--one file to flash and that's it, you're updated.
Thoughts? Is this accurate?
If this is the case, we should start looking at the Kernel and the .NBH format rather than obtaining root, because once we understand the .NBH, we can load whatever we want (including a Kernel with root access, if desired.)
Click to expand...
Click to collapse
ok.. the bootloader isnt gonna let us flash anything that isnt for the phone that ive heard of at least. the bootloader is only gonna let us flash rom.zips signed by htc unless we have a engineering spl. if we had that we could fastboot whatever we want. but it is also my understanding that the new engineering spls will not let us flash to certain major partitions (ie rocovery, and boot) anyhow this i think was an issue for the desire that modaco rooted and he found a way around it. we need a recovery for sure. as starting a new with no backups and such would be nothing more then a pain. we should focus i think on obtaining a engineering SPL from someone nice who wants to hook us up or a exploit of some sort. we need to gain read/write access to system, boot and recovery partitions. we do that and we can do what we want with the device. were not gonna be able to just flash a kernel, boot.img, system, or update.zip thats not official without the ability to gain access to the recovery partition.
in an exploit we would have root user status and we would have write perms on system at that point we could possible add flash_image to bin, chmod it and use that to flash a new recovery. write access is all we need. if ur idea was possible all we would need to do is flash a distro with root access and then flash the recovery partition with a custom recovery. a custome recovery will give us the ability to flash, backup and restore whatever we want. so long story short we need root user status in any event so we can gain access to recovery partition.

[DEV][Closed] Trying To Port MiUi ROM To Defy (Update - 4/13/2011)

Sorry i cant work on this anymore because i lost defy. Sorry guys
Hello guys,
first of all, i am no where near a developers level, but being somehow geeky at linux and android stuff, i am trying to port MiUi ROM for motorola milestone to motorola defy. I havent succeeded till now, but i will try my best to bring MiUi goodness to Defy phone users. I worked all night last night, trying to do different stuff every time hoping it works, but everytime i do anything, all i get is the big a$$ motorola logo. I need some developer's help on doing this.
The main problem has been motorola's locked bootloader, which does not let me flash updated zip files, unless i flash the original sbf, log into motoblur, root it, install recovery, boot into recovery and finally install. And trust me, i did all of that like 10-15 times last night. Even my phone must be pissed off at me right now cuz of that If there is an easier way,please, please please let me know.
I have tried everything from replacing apps, extracting boot.img, replacing framework files, installing directly, using kitchen for htc to automatically replace and almost eveything i could think of, and still no success. I really need help from someone who can debug kernels and sneak into bytecodes.
You are really welcome to help me if you think that you could help in any ways. Please shoot me an email at zed [at] wireshock.com (i will usually reply asap), or add me in gtalk admin [at] wireshock.com so that we can talk about it. Lets all hope that we can see miui in defy some day. Wish me luck
Edit: Here is the final thing i came up with, if anyone wants to examine, here is the link -> Click Here
PLEASE NOTE THAT THIS WILL NOT WORK! IT WILL NOT BOOT! THIS IS FOR DEV'S ONLY!
March 29
Update (9:40 AM): Another night without success. I am trying my best to make it work. Few people have contacted me about this, and some have helped a lot. Thanks to them. I contacted eugene_373 about this, lets hope he replies fast.
Update (11:48 AM): @KSubediTweet My Defy no longer works... So, not much help I can give. <- Eugene's defy doesnt work, need some devs who work for defy.
Update (5:54 PM): Me and Landroid from xda worked for almost the whole day trying to make it work. No success till now, but i think we are closer than before. If anyone finds a way to run recovery without booting somehow, please let me know, that will help a lot. And be sure to say thanks to Landroid for helping me out a lot.
April 6
Update (10:53 AM): Spent the last week trying to figure out a way to run recovery without booting which would help me save 80% time. Need some more Dev's help. I have tried contacting some chinese miui developers so that they could help me on porting the rom. Waiting for reply.
April 7
Update (8:35 PM): I think i finally found something that can help! Check this out -> http://forum.xda-developers.com/showthread.php?t=1026853
April 13
Update (8:14 PM): After few days of being idle, i am back to the track. Now as i have 2nd init, pre boot menu and everything i need to work, i will try as fast as i can. And racca pointed out some stuff i didnt know before, so i am kind of positive about getting it to work this time.
P.S. All times are MST (GMT -7)

I don't have much technological knowhow to add, but good luck and its great that someones finally making the effort, so don't give up!
Sent from my HTC Vision using Tapatalk

tbman1996 said:
I don't have much technological knowhow to add, but good luck and its great that someones finally making the effort, so don't give up!
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
Thanks, ill try my best.

Eugene made some adaptations on system recovery to apply update.zip. I don't know exactly how that works but maybe help you.
link: http://forum.xda-developers.com/showthread.php?t=995131

Thanks a lot for the link, if i can get the keyfile, i think i can make an update.zip for the recovery and can open clockworkmod from default recovery. Ill try it
Edit: or i can sign the zip file so that i can flash it from default recovery.

Dexter_nbl did the port of sense for us. In his rom he used a file on sdcard to boot on recovery. Like, if the file called recovery_mode exist on sdcard execute the script to boot up on recovery....this helped a lot!

psicodelico said:
Dexter_nbl did the port of sense for us. In his rom he used a file on sdcard to boot on recovery. Like, if the file called recovery_mode exist on sdcard execute the script to boot up on recovery....this helped a lot!
Click to expand...
Click to collapse
That might have worked if the room booted at all, the problem here seems to be with some hardware driver that is preventing the phone from booting. Only if someone who knows what is preventing it from booting could help me out, i would work on fixing it somehow.

good to see a new project coming up.
got a bit quiet here in the past week, devs probably waiting for motos official froyo release.
anyways, kepp us updated on your progress and good luck!

ksubedi said:
That might have worked if the room booted at all, the problem here seems to be with some hardware driver that is preventing the phone from booting. Only if someone who knows what is preventing it from booting could help me out, i would work on fixing it somehow.
Click to expand...
Click to collapse
That ideia is for you access your system recovery to restore your system without flash a sbf, get root, install system recovery (that take a long time). This way you can try more things. Dexter call the script to verify the file on sdcard in beginning of the process of boot, i dont know how but if you want see take a look the first version of his ROM.

i dont think you can sign the update packages. maybe you should try to ask eugene how this whole cookie cutter thing works
http://twitter.com/eugene_373
http://eb-productions.proboards.com/
would be awesome to get miui on defy...
Sent from my MB525 using XDA Premium App

psicodelico said:
That ideia is for you access your system recovery to restore your system without flash a sbf, get root, install system recovery (that take a long time). This way you can try more things. Dexter call the script to verify the file on sdcard in beginning of the process of boot, i dont know how but if you want see take a look the first version of his ROM.
Click to expand...
Click to collapse
That is exactly what i have been trying to do since my first day. I have asked eugene_373 for help on this. Thanks anyways.
drsouly said:
i dont think you can sign the update packages. maybe you should try to ask eugene how this whole cookie cutter thing works
http://twitter.com/eugene_373
http://eb-productions.proboards.com/
would be awesome to get miui on defy...
Click to expand...
Click to collapse
Thanks for the link I just contacted eugene_373 about this. Ill update once i get a reply.

Keep it up!!
One closer day i will buy the defy

Thank you for your efforts. Look forward to your success

any news?!

Any news ???

I have contacted miui developers to help me out. Waiting for reply now. Lets hope that we can bring miui to defy as soon as possible. Need help from some devs.

What do you mean go to recovery without booting? Without booting to Android you cannot use any other means to write to the Filesystem, so how would you do that? You can't replace the recovery that's installed with the phone, so I don't really see how that would be possible.

Recovery without booting is possible through charge-only-mode, but no one is capable to do it for Defy. And probably it is possible in Defy Sense ROM, if you read the thread. But I did not tried.

an option would be to look for an exploit in the recovery, that allows us to make something like open recovery on the milestone... i would ask the devs from openrecovery

There is the way using the second boot used on milestone (2nd-init) and the way used by Dexter in Sense ROM;
- included ClockWorkRecovery custom edition for this rom
• - Do NOT install the apk release, or it will ruin bootup of sense.
• - activate Recovery by putting an empty file in the root of your sdcard called "recovery_mode"
• content can be anything or empty, just make sure filename is correct.
• - reboot, and it will load into recovery.
Click to expand...
Click to collapse
Sense ROM: http://forum.xda-developers.com/showthread.php?t=933710 (get the first version to see the magic)
2nd-init: http://forum.xda-developers.com/showthread.php?t=1003449

[MOD] [Update:5/5/2011] BootMenu - Recovery, 2nd Init , v0.5.1

NOTICE: Sorry Guys, As i lost my defy, i will not be able to work for defy anymore So i will not be able to maintain this thread as well. Racca is maintaining another thread with updates for this bootmenu here which can now be called the official thread.
Hello XDA,
[Notice: You might have checked my signature and already figured out that i lost my Motorola Defy So i will be no longer able to develop anything for defy. I will not be able to edit the boot menu and optimize it, but i will still post all the updates i get from Korean Developers. I am sorry to say that i will not be able to work on porting MiUi to Defy anymore. I hope some other developer will handle the work and port MiUi to Defy. Just reply to this thread if you have anything. Thank You]
This is a pre-boot menu that loads just before the android system starts, which allows you to enter recovery, start adb daemon, run 2nd init script, run 2nd boot and few more. I recently changed the format of this post so that i can easily add updates, and i hope you guys don't mind it, and if you want to check the old post, here is the link. I have also added an unofficial changelog. This MOD was developed by Korean Developers at http://cafe.naver.com/androiders, so big thanks goes to them.
Status: Beta
Latest Version: v0.5.1
Last Update: 4/16/2011
Usage:
Load second init.rc file which enables you to do a lot of things that were not possible before.
Load custom recovery before booting os, which makes it possible to restore your nandroid backup or flash a new rom even if your system is not booting.
Run ADB Daemon to debug system boot using logcat or similar tools, very useful for developers.
Change the default boot to 2nd init, so you can load the 2nd init on default boot.
And much more....
Download:
Version 0.5.1 (Latest)
Version 0.5.0
Version 0.4.5
Version 0.3.1
Version 0.2.0
XDA-Developer Forum Members, Download Latest Attached File, Non-Members, Click Here.
Upgrading:
Simply follow the installation instructions, it will overwrite the old version and install the new one.
Installation:
Download the latest zip file.
Create a folder “bootmenu” on your sd card and extract all the files inside the zip file there.
Turn on usb debugging on your phone. And use the following commands in adb:
C:/> adb shell
$ su
# cp -R /sdcard/bootmenu /data/bootmenu
# cd /data/bootmenu
# chmod 755 *
# ./install.sh
# rm -R /data/bootmenu
Click to expand...
Click to collapse
The bootmenu will be installed.
Turn off USB Debugging.
Restart your device once.
Check the Using "Pre Boot Menu" section for instructions on how to use.
Using Pre Boot Menu:
Turn your phone off.
Press the Power Button.
After 1-10 seconds, the blue led on your phone will light up for just 1.5 seconds (Still while the Motorola logo is being displayed).
Exactly when the led lights up, press the volume down button.
You will see the BootMenu, use the Volume Button to navigate up and down, and the power button to select an item.
Changelog:
Version 0.5.1
Bug Fixes
Minor Internal Script Changes
Version 0.5.0
Bug Fixes
Few Changes In UI (Background)
Updated All Scripts, Better Compatibility With Most ROMS
Changed Directory Structure
Version 0.4.5
Bug Fixes
Changed Name Of OpenRecovery To Custom Recovery
ADB Daemon Works Now
Few Minor Changes...
Version 0.3.1
Replaced Tenfar's Recovery With OpenRecovery
Added 2nd Init Script
Bug Fixes
Minor UI Enhancements
Version 0.2.0
Initial Release
Added BootMenu
Added Tenfar's Recovery
What Works:
BootMeu
ADB Daemon
2nd Init
Custom Recovery
Default Recovery
Setting 2nd Init As Default
Reboot
Normal Boot
What Doesn't Work:
2nd Boot (Can Be Done Via 2nd Init Though)
Credits:
Korean Developer "ohnholic" and Other Korean Developers for creating this
Korean Forum User "intohim" for providing me this file and helping me translate Korean things to English.
Korean Forum User "고봉현" for mailing me about the updates as soon as they are released, and also for providing some files.
XDA Developer "tenfar" for his ClockWorkMod Port To Defy.
Developer "Koushik Dutta" for ClockWorkMod.
XDA User "pedrodh" for creating an easy installer.
And everyone i forgot to mention....
Related Projects:
Easy Installer (APK) for this MOD.
Cyanogenmod 7 Port Based On 2nd Init Using This MOD (Under Developement)
MiUi Port Based On 2nd Init Using This MOD (Under Developement)
P.S. I do not take any responsibilities for the damages caused by this tool. If you brick your device, the most i can do is *help* you recover your system. So use it on your own. Works on my phone.

This will be impressive when 2nd-init works.
Thanks for everyone working in things like that!!
P.S. It's working here!

does this mean custom kernels? once it gets figured out?

mussio said:
does this mean custom kernels? once it gets figured out?
Click to expand...
Click to collapse
Well, not right now, but once the korean developers figure out a way to bypass the recovery signature verification, which is of course, not easy, we will be able to do that too. And according to what i kknow, the korean devs are working really hard on that. But this definitely means that we are one step closer.

So for now this makes flashing Roms easier? safer? sorry if i seem confused i'm not getting my Defy till Monday just want to clarify if i should flash Roms this way or follow directions dor each rom, all this sbf files and being able to downgrade is kinda confusing I never had a android phone with a locked bootloader so all this is new to me.
hope that makes sense.

mussio said:
So for now this makes flashing Roms easier? safer? sorry if i seem confused i'm not getting my Defy till Monday just want to clarify if i should flash Roms this way or follow directions dor each rom, all this sbf files and being able to downgrade is kinda confusing I never had a android phone with a locked bootloader so all this is new to me.
hope that makes sense.
Click to expand...
Click to collapse
Well, this doesnt really make flashing roms easier (its same recovery), but it definitely makes it safer as you can always restore your nandroid or flash another rom even if your phone stops booting. And i can totally understand you, the way motorola works is a bit different than HTC and other phones, sbfs and stuff like that, but dont worry, if you read the guides here -> http://forum.xda-developers.com/showthread.php?t=919334 , you will understand everything. Enjoy

That are very great news!!
Does I have to install this after every new firmware-flash or only after a bootloader up/downgrade?

wow... great news..
now we don't have to boot up the phone, and install custom recovery.
saving time

Can't wait to see custom kernels

"intohim" what a great nick... hahahahahaha!
sorry, great news & big props to the korean devs!

That sounds pretty awesome, will try later. I would have saved a lot of hours with that... anyway, I'll save them by now
Sent from my Defy running adlxmod using Tapatalk

Oh, now disabling USB debugging is not required! Bravo!

I have not disabled USB debugging and I have M boot loop. Now reflashing to try again.
For everyone - do not forget to turn off usb debugging. Now it´s working and I am going to try it some more.
Edit: Finally the true, fully working recovery. With Tenfar´s recovery, this is the best developed thing for Defy, since Defy´s release
and it´s worth the donation. About only 5 minutes to recover bricked system.
I only hope some day adb will be working too, but this is great enough for now.

How can I get root-access after starting adb via the bootmenu?
Currently, it's not working for me:
$ su
[1] Segmentation fault su
Click to expand...
Click to collapse

Does this mod mean that Cyanogen is coming to Defy???

hirano said:
Does this mod mean that Cyanogen is coming to Defy???
Click to expand...
Click to collapse
Not yet. We need the 2nd-init working to do that.

antony.ps said:
Can't wait to see custom kernels
Click to expand...
Click to collapse
not possible unless someone can crack/get the lock
it's a great improvement but no where near custom kernels
afaik, this is another "bootstrap" executed on boot except it resumes normal boot after 2 seconds or so.
if we can get 2nd-init to work with it, we might finally be close to getting what milestone already have.

peetr_ said:
I have not disabled USB debugging and I have M boot loop. Now reflashing to try again.
For everyone - do not forget to turn off usb debugging. Now it´s working and I am going to try it some more.
Edit: Finally the true, fully working recovery. With Tenfar´s recovery, this is the best developed thing for Defy, since Defy´s release
and it´s worth the donation. About only 5 minutes to recover bricked system.
I only hope some day adb will be working too, but this is great enough for now.
Click to expand...
Click to collapse
Curious, just in case anyone has already tried and can give an answer: when installed, is outer persistent after you flash a sbf? Or is it overwritten by the sbf? Does anyone know? (i mean, afaik /pds isn't restored with sbf, mess with it and you get a brick! )
Sent from my Defy running adlxmod using Tapatalk

Any news from the Koreans who develop this recovery?
Sent from my MOTO Defy

demolition23 said:
Any news from the Koreans who develop this recovery?
Sent from my MOTO Defy
Click to expand...
Click to collapse
Nope, i have just emailed "intohim" and asked him to come online, as he is the only one who can read korean, and the korean page doesnt work here for some reason. I will update as soon as i get a reply
adlx.xda said:
Curious, just in case anyone has already tried and can give an answer: when installed, is outer persistent after you flash a sbf? Or is it overwritten by the sbf? Does anyone know? (i mean, afaik /pds isn't restored with sbf, mess with it and you get a brick! )
Sent from my Defy running adlxmod using Tapatalk
Click to expand...
Click to collapse
Sorry to say, but nope, this is not hardcoded in to rom or is not replaced in place of original recovery as the bootloader is still locked. And installing a sbf update is like replacing everything on the phone with the contents from sbf. So it wont work if you reflash the sbf, unless it is included in the mod or rom you installed. Some developers have just contacted me and said that they are going to include this on their rom. So future defy roms are going to be more safe

[Q] Some Questions

stupid/sily questions:
APK related
if I try to delete a single file or apk in an android system, will it delete related files also?
Port related (ASOP/CM6/CM7/Custom ROMs/etc)
I know that the majority of XT720's kernel is 2.6.29..., anyways, why I am seeing 'Android version of 2.3.5'? and getprop value of '[ro.build.version.sdk]: [10]?..., are these valid?
I still have many questions that I would like to ask but for now, this will do.
Please enlighten me, I'm still starting to learn 'Android', any feedback is appreciated..., be it good or bad
best regards,
dabiano

Actually all the kernels are 2.6.29 because that's all Motorola has released--and because of the signature checks we can only use official Motorola kernels (except for fastbooting). That only applies to the kernel, though. Those ROMs have newer userspaces. E.g everything else (GUI etc) uses newer code. Even Motorola's 2.2.1 for Motoroi used 2.6.29.
Sent from my Milestone XT720 using xda premium

Mioze7Ae said:
Actually all the kernels are 2.6.29 because that's all Motorola has released--and because of the signature checks we can only use official Motorola kernels (except for fastbooting). That only applies to the kernel, though. Those ROMs have newer userspaces. E.g everything else (GUI etc) uses newer code. Even Motorola's 2.2.1 for Motoroi used 2.6.29.
Sent from my Milestone XT720 using xda premium
Click to expand...
Click to collapse
thanks for the reply
I'm still trying to grasp it all in my head about porting/compiling android (ASOP/CMx/etc...)
So in short, we can technically upgrade the userspace/api level of the entire android system even if the kernel stays the same?
also, you are saying that we can use another kernel if fastboot is used?, why not trick the bootloader to use a kernel that comes from a 'false' fastboot?, I may be wrong though ...

dabiano said:
thanks for the reply
I'm still trying to grasp it all in my head about porting/compiling android (ASOP/CMx/etc...)
So in short, we can technically upgrade the userspace/api level of the entire android system even if the kernel stays the same?
also, you are saying that we can use another kernel if fastboot is used?, why not trick the bootloader to use a kernel that comes from a 'false' fastboot?, I may be wrong though ...
Click to expand...
Click to collapse
That's right. I'm not certain but what I've gathered is the biggest kernel changes happened before 2.1 (which changed process management). I think it's been tweaked subsequently, but it may not be such a big deal. Additionally, there is another option--what I would call "kernel live surgery"-- skrilax_cz and nadlabak on A853 have been doing a lot of that lately--making modules that replace functions inside the kernel to replace bugs and add features.
And yes we can boot custom kernels using "fastboot boot", but I don't think anyone currently knows whether it is possible to trick fastboot to work without USB. It depends on how fastboot has been implemented. A853's seems to be the most studied bootloader, but "fastboot boot" doesn't work on A853.

Thanks for the info you shared Mioze7Ae

Returning to stock..?

Hi, I have a motorola milestone xt720.
I recently flashed dext3r's Motoblur on it and it is running fine but it has many bugs and I just want to return to froyo.. Which is my problem.
There are a few problems I am running into
-RSD Lite 4.9 doesn't recognize my phone
-Booting in recovery mode doesn't work (It shows a triangle with yellow exclamation with a phone laying down next to it)
I just can't find a guide that solves my problem, if any one could PLEASE help it would be awesome, i'm sick of the bugs on MOTOBLUR (which by the way was downloaded for XT720)

bmm1893 said:
Hi, I have a motorola milestone xt720.
I recently flashed dext3r's Motoblur on it and it is running fine but it has many bugs and I just want to return to froyo.. Which is my problem.
There are a few problems I am running into
-RSD Lite 4.9 doesn't recognize my phone
-Booting in recovery mode doesn't work (It shows a triangle with yellow exclamation with a phone laying down next to it)
I just can't find a guide that solves my problem, if any one could PLEASE help it would be awesome, i'm sick of the bugs on MOTOBLUR (which by the way was downloaded for XT720)
Click to expand...
Click to collapse
So to solve the rsdlite thing, make sure you have USB debugging on and then it should recognize your phone.
For the recovery issue, what happens after your triangle goes away? How many options do you have? If it is only 4 then you are in stock recovery and not a custom recovery like Androidiani or Mioze's. Both these and their guides are on this General forum.
Now for the "stock" ROM part. Look in the Development threads. There are plenty of options in there from CM6/7, Hellmonger's ROM,...gotta look though. When you say return to froyo, it is cryptic bc aside from Korean, there is no froyo to return too. They are all custom.

Woodrube said:
So to solve the rsdlite thing, make sure you have USB debugging on and then it should recognize your phone.
For the recovery issue, what happens after your triangle goes away? How many options do you have? If it is only 4 then you are in stock recovery and not a custom recovery like Androidiani or Mioze's. Both these and their guides are on this General forum.
Now for the "stock" ROM part. Look in the Development threads. There are plenty of options in there from CM6/7, Hellmonger's ROM,...gotta look though. When you say return to froyo, it is cryptic bc aside from Korean, there is no froyo to return too. They are all custom.
Click to expand...
Click to collapse
-Yes the phone is in debugging mode and it doesn't recognize my phone.
-The triangle doesn't go away, it stays there until i take out the battery again
-I will try those mods but knowing my luck they won't work.. I will use dext3r's froyo is what I mean to return to froyo, go through the whole process of flashing it to my phone again
Thanks for the reply

Put on Mio's CM6 RC3. Best ROM created yet for the XT720 in my opinion, really good stuff.
Definitely don't bother with Dexter's stuff at this point, what with all the amazing ROMs that have been created since Feb of 2010.

I will try that! IF I can get this to work without bricking my phone or anything :'(.
I've about given up on this phone, it has SO many problems and it's just slow in regards to processor speed and internet, 4G is out..

Don't give up on it yet. In the last 4 months we have gotten 4 really incredible ROMs. If you can boot up fully, install Mioze's recovery (I was mistaken before, it is in the Dev threads not General). The install CM6 or Hellmongers and never look back.
Most of us got this phone with a fresh 2.1. Now look what we have, thanks to some very talented people.
Good luck. Bedtime for now.
Edit: Aside from screwing with the bootloader, it is almost impossible to actually "brick" your phone. Get it to be unresponsive, yes. You can flash back to stock sbf and redo everything, but bricking is a tough thing to do.
You can overclock your CPU with Milestone Overclock from the market. Good starting point is 1000/66. Now I am going to bed.

Yeah it can boot fine, I can send messages and everything, it just has numerous bugs.

My god I figured it out....
I had to reinstall the Moto USB Driver because I completely forgot that I had to swipe my computer about a month ago and it uninstalled!
Much stress and anger lifted off of my shoulder !!!!!!!!! I can get it from here!

Woodrube said:
Edit: Aside from screwing with the bootloader, it is almost impossible to actually "brick" your phone. Get it to be unresponsive, yes. You can flash back to stock sbf and redo everything, but bricking is a tough thing to do.
Click to expand...
Click to collapse
Lol, yeah that is so true. I remember how scared I was when I first flashed dexters the very first time. New to ubuntu, new to android yipe. Its actually pretty close to impossible to brick a phone unless you tamper with bootloaders like you mentioned.