inFiniSense​
Alright, our first thread got closed just before I released this zip, so I made a new one.
This time, right off the bat, we have a flashable zip
Anyway, this is Work In Progress. Don't expect it to be done and perfect.
Ok, enough, here is..... inFiniSense!
This is a project porting the Flyer's sense (2.1/3.0) to the Nook Color, CM7 only.
We have figured out this:
We need a custom ramdisk to have custom apps. This zip flashes that ramdisk.
We need to push the apks to the Nook (No.... we need to eat them!) This zip does that. Pushes, not eats.
The apps need frameworks. So this pushes those too. (what else would we do?)
And lastly, the apps FC cause they are looking for a 3G radio. The fix.... none.
Still, flash this zip. If the apks show up, then good. As soon as we fix the FC, you will get the zip.
Also, we have found a Flyer RUU. If anyone could help us extracting the RUU (mac) into a BROWSABLE FOLDER, not a zip. Then we could be done. We are trying, but if the Nook people try too it could get done faster.
The zip isn't out yet (gimme a day. Promise. Hails to god)
Instructions to do what the zip does:
1: download the zip in the downloads section. Flash it. And reboot.
2: Make sure the zip is on the computer. Unzip it.
3: do these commands while in that folder:
Code:
adb push app/ /system/app
Then:
Code:
adb push permissions/ /system/etc/
Again:
Code:
adb push fakeserverxml/ /system/etc/
Almost done:
Code:
adb push framework/ /system/framework/
Then reboot. Hopefully, the apps will show up. They will FC.
Then do this:
Code:
adb logcat
Then launch an HTC app. post it on pastebin or somewhere. Then give me a link. This is for debugging purposes.
Hint: If every time you hit the home button you get an FC, try this:
Code:
adb shell pm disable com.htc.android.htcsetupwizard
Then launcher an HTC app. post it on pastebin or somewhere. Then give me a link. This is for debugging purposes.
Downloads:
http://www.mediafire.com/?9dp20anyjukl7mi - inFiniSense 0.1
-The working zip is almost out. Instructions to manually do this above.-
Credits:
911sniper for the Flyer dump.
xda community for all the help.
If I remember anything else, I'll tell you.
Why create a whole new post when you still have nothing? They closed your old post cause you had nothing and now you have a new one with just as much crap. What did you post? Is anything working on it? You are not explaining anything other then the fact it's still the same old crap. A non working rom is not something to post on a message board.
Anyone feel like trying this? I want to see how badly this bricks your nook color
I can't wait to examine their "zip"... install it? Ha! No f'n way.
Alright. Don't trust my zip. I flashed it. It worked.
And this isn't crap. And we have a ZIP!
Plus, if anyone could help us decompiling system.img from an RUU on Mac would really speed this ip.
do u have pics to prove that it works
Umm... Do you want one?
yeah that would shut people up
Alright. They'll be up in a sec.
Why it wont show anything like the last time. He stated nothing works right now and his uploads are completely not functional
Sent from my NookColor using XDA Premium App
Yes it will. To prove that the apps are on there. And would anybody post their logcat...?
Update: Screenies tommorow cause I have bed now.
Swyped from my 1.3 GHz Nook Color CM7.
ikingblack said:
Update: Screenies tommorow cause I have bed now.
Swyped from my 1.3 GHz Nook Color CM7.
Click to expand...
Click to collapse
OK, this is getting a little bit outta hand... cmon guys. Don't post something till you have something to post that works.
Cmon. It is a WIP. What more do you want? It isn't working. We said that. If you want something working RIGHT NOW, then move on. I'll give an update when it works.
And if you really want it to work, then we need any help decompiling that image as I said a million (3) times.
ikingblack said:
Update: Screenies tommorow cause I have bed now.
Swyped from my 1.3 GHz Nook Color CM7.
Click to expand...
Click to collapse
This isn't an excuse.
This thread should have the screenshot(s) from the start.
ikingblack said:
Update: Screenies tommorow cause I have bed now.
Swyped from my 1.3 GHz Nook Color CM7.
Click to expand...
Click to collapse
dude, reopening this tread was a really bad idea. folks get banned for such shenanigans. it'd probably be in your best interest to shut this down, sit back and, if you're serious about all this, learn from all the wonderful devs in this forum. otherwise a Mods going to shut it down, again, and i doubt they'll be so nice the second time around.
Probably not the wisest thing opening a thread after its been closed.
Redundancy..
Thread closed.
@OP, check your pm's.
Related
Well here I am again,
Not sure if I should have started a new thread for this or not. And although I feel like there are more threads than needs to be in the Development forum at the time being. I felt like the SD image might have it's own issues unrelated to the EMMC version. So I wanted to keep it seperate. If a Mod feels different, please advise so. I'll be more than happy to remove the thread and have the file posted to Divine_Madcat's original thread.
**Disclaimer: As usual, use at your own risk. Backup! And I'm not responsible for anything period**
I've just prepped an Image for Divine Madcat's latest Honeycomb Hybrid RC1. I've included rookie1's dualboot u-boot.bin and my modded CWM for SD, for the purpose of easier updates in the future for the SDcard rom.
Although there is no option to mount an SDcard in this version. I was able to mount the 4th partition as SDcard. So now you can use a file explorer of choice to browse your SDcard partition. I'm not sure if the EMMC version mounted the internal Media partition or not. Not 100% sure, but with this image you should also be able to browse your /media partition on your nook as well. And remember to thank the devs for all their time and effort into getting this to us. All I did was prep it to work as an SD image.
Directions:
1-Download the update-HC-hybrid-rc1-sd.img.7z
2-Uncompress it
3-The .img file should be able to fit on a 2gb card or larger
3-Follow directions from Nookdevs.com to burn the image
4-Pop the SDcard in your nook
5-Enjoy!
Credits:
Divine_Madcat
deeper_blue
rookie1
nemith
Edit: 5/21 - Well since the world is apparently ending today sometime. Figured I'd at least let you guys try a working .img. So here is an updated .img with the apps installing issue fixed. Everything is the same as the last .img except for the fix and I included a file manager. If it hangs at the "android_" screen on first boot. Just do a hard reboot and it should be fine. Enjoy!
Edit: 5/12 - Seems like there is an issue with installing apps where it will do a soft reboot when attempting to do so. I won't have time to take a real look at it till this weekend though.
-You could push individual apps to /data/app via adb for the time being.
Code:
$ adb push app.apk /data/app
-Or to push multiple apps. Create a folder called data. Within that folder, create a folder called app. Then place all your apks in the app folder. Now you can push the whole directory to /data/app
Code:
$ adb push /your_home_directory/data /data
-If anyone else who might want to jump ahead of me and find a fix, would very much appreciate it!
Downloads:
5/21 : update-HC-hybrid-rc1-sd-v0.2.img.7z
MD5: bba35a262821fbb7e4ef42f8bb4807d6
Click to expand...
Click to collapse
If I've helped out in some way, please say thank you in one way or another!
Thanks,
Racks
Awesome! Does this include anything new from 3.1?
Looks good. I was trying to install nook app from market but it kept rebooting. Thanks for the hard work..
Looking forward to giving this a try...
Whats the size of the image, what is the min/max size sd card required?
@Samir- nothing new. Direct image of hybrid rc1 by madcat
@Flyboy- I really didn't get a chance to test. Thanks for the info. Ill take a look when I can.
@Joenathan- sorry forgot to post img size. Its a 1.8gb image. So any card 2gb or larger should be fine. Ill update OP with size later
The more feedback the better. Can't fix things without feedback.
Thanks everyone,
Racks
Sent from my NookColor using Tapatalk
Are there quite a bit of FCs with this version? I tried the emmc one and had to revert back to CM7 because it was too unstable.
Its a bit too big for my 2GB SD card, my sd card weighs in at 1,921,024KB whereas the image is 1,927,168KB
So 2GB SD cards are out....
Thanks Racks, just what I was looking for.
Well done.
crap! I has 2gb SD card too that I use for this.
Any chance of someone making an SD version of the xboxexpert's HC build?
chisleu said:
crap! I has 2gb SD card too that I use for this.
Any chance of someone making an SD version of the xboxexpert's HC build?
Click to expand...
Click to collapse
Any reason for wanting that build? I ask, because it is out of date, and nothing more than some extra apps added by default. This version uses newer framework, and right now is advisable to use until a 3.1 build comes (especially with the SD card fix also made by Racks).
The ROM is nice, Honeycomb apps are much superior, but for me it runs too slow.
Using a class 4 generic SD. Anyone else having problems?
hirano said:
The ROM is nice, Honeycomb apps are much superior, but for me it runs too slow.
Using a class 4 generic SD. Anyone else having problems?
Click to expand...
Click to collapse
Not that the SDK is as fast as CM7, but i am willing to bet the problem is your SD card. Having used a crappy SD card myself, i know how bad they can be; invest in a cheap class 2 or 4 Sandisk card, and get blown away.
Thanks, this is exactly what I was looking for as my next NC project
Divine_Madcat said:
Not that the SDK is as fast as CM7, but i am willing to bet the problem is your SD card. Having used a crappy SD card myself, i know how bad they can be; invest in a cheap class 2 or 4 Sandisk card, and get blown away.
Click to expand...
Click to collapse
Divine,
For awhile I would see you posting around with random things in various sections and wasnt really sure if you were a troll or not, but lately youve pushed some truly amazing things like the work on dals kernel and now this update hc build and I truly am impressed with all your work. You have my complete respect. Thank you.
RileyGrant said:
Divine,
For awhile I would see you posting around with random things in various sections and wasnt really sure if you were a troll or not, but lately youve pushed some truly amazing things like the work on dals kernel and now this update hc build and I truly am impressed with all your work. You have my complete respect. Thank you.
Click to expand...
Click to collapse
Ill certainly admit, i am not the most agreeable at time; commonly, i let my daily stresses flow out on to forums. I am easily annoyed at what i see as something stupid (which sadly, it feels like has been happening more in this forum).
As it is, I am happy i could have committed something useful to the community.
Apps
Great job! Love not having to flash between CM and HC to play with the 3.0 goodness. My only question, anytime I try to install an app it reboots.....Ideas?
Fodizzle1978 said:
Great job! Love not having to flash between CM and HC to play with the 3.0 goodness. My only question, anytime I try to install an app it reboots.....Ideas?
Click to expand...
Click to collapse
You're the second person to say so. Is everyone having this issue? Is anyone having success installing any apps? From market or from a file explorer. I need more feedback so I can pinpoint the problem.
I'll have to take a look at this when I get a chance. Or if you don't mind posting a logcat? Just save a logcat to a .txt file and upload it here. I'll take a look to see where it's erroring out.
*I could be wrong, but most of the time when this happens, it seems to be a caching issue. But again, i won't know till i see the errors.
Thanks,
Racks
Here ya go
racks11479 said:
You're the second person to say so. Is everyone having this issue? Is anyone having success installing any apps? From market or from a file explorer. I need more feedback so I can pinpoint the problem.
I'll have to take a look at this when I get a chance. Or if you don't mind posting a logcat? Just save a logcat to a .txt file and upload it here. I'll take a look to see where it's erroring out.
*I could be wrong, but most of the time when this happens, it seems to be a caching issue. But again, i won't know till i see the errors.
Thanks,
Racks
Click to expand...
Click to collapse
Fodizzle1978 said:
Here ya go
Click to expand...
Click to collapse
Here's a better one....not sure I captured it the first time
I'm getting the same problem, only tried installing from market.
Sent from my PC36100 using Tapatalk
I know there are threads like this out there, but none of them fitted my questions...
Hi,
in this post, seo posted some ported sense 3.0 apps and widgets for Sense 2.1 GB roms.
I tried to install some of them and got MMS to work.
Then tried to get Rosie and widgets, but they wouldn't install directly, so i started playing around with ADB.
i think adb is fully set up, i am able to pull apks from /system/app.
problem is, i am obviously unable to push, install or uninstall system apps via
adb push
adb install
adb uninstall.
this was when i tried remounting (with remount,rw etc.) and was able to "rip off" rosie.apk (i know it worked as it wasn't there anymore later on ) but still was unable to install apps (with the effect i hadn't got a launcher at all.)
latest step was creating a signed update.zip, didn't work, recovery just restarts.
anyone help? someone got experience which may help me? i went through about 10 or 20 guides and am kind of desperate right now as things just dont work
thanks
SummonerOfDeath said:
I know there are threads like this out there, but none of them fitted my questions...
Hi,
in this post, seo posted some ported sense 3.0 apps and widgets for Sense 2.1 GB roms.
I tried to install some of them and got MMS to work.
Then tried to get Rosie and widgets, but they wouldn't install directly, so i started playing around with ADB.
i think adb is fully set up, i am able to pull apks from /system/app.
problem is, i am obviously unable to push, install or uninstall system apps via
adb push
adb install
adb uninstall.
this was when i tried remounting (with remount,rw etc.) and was able to "rip off" rosie.apk (i know it worked as it wasn't there anymore later on ) but still was unable to install apps (with the effect i hadn't got a launcher at all.)
latest step was creating a signed update.zip, didn't work, recovery just restarts.
anyone help? someone got experience which may help me? i went through about 10 or 20 guides and am kind of desperate right now as things just dont work
thanks
Click to expand...
Click to collapse
Pull me a recovery.log when you try installing the zip, and I'll have a look for you.
Sent from my HTC Hero using XDA Premium App
S.O.D. proudly presents.... recovery.log!
Here it is, i attached my own update.zip (rosie-signed.apk), maybe you could have a look at it as i don't know where the fault may be.
greets SOD
I would already be happy if you managed to solve the update.zip issue (would help me with other updates) but the main prob is adb noch really working, seems like some system part is blocking this?
my hero was originally a t-mobile google g2, created goldcard, rooted, custom recovery, new radio and custom rom.
a few details:
device HTC Hero (T-Mobile Google G2, the black one )
rom Salsasense RC2 (at the moment...)
recovery CWM 2.0.5.7 (think so, but im sure i got the latest)
sd 2gb
ooookay, tried to edit existing salsasense, resulting in non-functional rom rebooting into recovery.
JieeHD may you probably cook Rosie.apk and HtcClockWidget3d.apk in SalsaSense RC2 and upload it just for testing? much better would be to give me the keys to do it myself *still learning*
i tried it but the situation above occured^^ maybe some md5 thingy?
greets, SOD
SummonerOfDeath said:
ooookay, tried to edit existing salsasense, resulting in non-functional rom rebooting into recovery.
JieeHD may you probably cook Rosie.apk and HtcClockWidget3d.apk in SalsaSense RC2 and upload it just for testing? much better would be to give me the keys to do it myself *still learning*
i tried it but the situation above occured^^ maybe some md5 thingy?
greets, SOD
Click to expand...
Click to collapse
Fixed your update-script, new line for each command is needed
/facepalm
JieeHD said:
Fixed your update-script, new line for each command is needed
/facepalm
Click to expand...
Click to collapse
not serious no? /facepalm -.-" thanks will try that right now xD will give feedback if my device is still alive afterwards xDD
greets, S.O.D.
How's your progress going?
I messed around with the files 2 from the treat and they won't flash error 0. Tried to fix that with.different binery and gave me error 7. If you can make at least the king lockscreen with weather app working than you are the man
Sent from my HTC Hero using XDA App
stroobach said:
How's your progress going?
I messed around with the files 2 from the treat and they won't flash error 0. Tried to fix that with.different binery and gave me error 7. If you can make at least the king lockscreen with weather app working than you are the man
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
brick after flashing modified rom.
push to /system/app didnt work.
flashing restarts recovery.
jieehd's tip of single lines for every command doesnt work, same as above.
error 0 = apk is not made for your device/rom, wont install.
error 7.. dunno, think its not matching binary or parsing error.
files from my thread? as post above says one is a log and the other is defect^^
i doubt weather will work as its eating HUGE amount of resources. if u want this lockscreen, maybe try salsasense, has got a 3.0 alike lock...
holidays now, wish good luck in coding would be happy if u found a solution
greets, SOD
were can i find HTCG2/hboot/PC10IMG.zip been looking all over for it and its no were to be find
Got some questions.
1. You want WHAT? And what is the purpose?
2. In how far is this related to this topic?
3. If u give us a path to this file, why do u ask where it is? Maybe try dowloAding some random rom (probably some ruu) and do extract & search..
4. Are you really willing to contribute to this topic? I dont see the point of posting this.
5. Obey forum rules. If u have got a question, post it directly in q&a section, not in some random topic or directly explain the connection to the actual topic.
Greets, s.o.d.
agnostic900rr said:
I dunno, no idea
Click to expand...
Click to collapse
what don't you know? may we help you? whats the purpose of all these posts?
i think i'll give it a last try next time wenn i got salsa sense installed and either find a solution instantly or give it up, as noone is willing to support me and i can't do much more with my poor coding skills.
seems like we have to admit that hero's dying and i have to wait for my contract to end so i get a new phone.
greets, s.o.d.
Welcome back...
For those that havnt been following along here is the background...
Part 1 http://forum.xda-developers.com/showthread.php?t=1366627
Part 2 http://forum.xda-developers.com/showthread.php?t=1373026
Part 3 http://forum.xda-developers.com/showthread.php?t=1380605
And this is where questions/speculations etc.. should go.
http://forum.xda-developers.com/showthread.php?t=1372293
I have been real busy working on this trying to get some progress down.
There is a new alpha package for this @
http://iswarm.net/x2boot-alpha2.tgz
PLEASE DO NOT DISTRIBUTE THIS
It will be changing often and i dont want older versions floating around.
If you download your own and keep it to yourself people will always have the
newest version.
Please only mess with this if you know what you are doing.
I can and WILL NOT support it here in this thread.
Most of the action has been going down on IRC.
I have set up a new channel for this is in
#X2-AOSP on freenode
This thread is for the discussion of where to go next.. tricks, techniques to debugging a foreign ROM on our 2nd-init boot.
@ this point i have had varying success in booting cm7, still allot of bugs in logcat, and still getting a bootloop.
Please only chime in if you have any ideas or thoughts related to this.
You may be able to find support for the test package on IRC.
This thread is NOT for speculation, or questions.
This is NOT about replacing our kernel.
We really could use the help of some experienced dev's in this en-devour.
Thanks again for all the support and encouragement.
Hit the thanks button if ya like.. its free
It takes a good amount of knowledge to set up.
The more i have to help people with the basics the less time i have to work on this.
If you've got some skillz and can answer questions for folks then your help is needed and appreciated on IRC
To be honest if ya cant @ least get this setup without ALLOT of questions then you will be more of a hindrance then help in this process. Thats not to say we dont need testers.. just that the need for testers cant take all my time as then we will have no progress.
Starting to feel pretty alone in this. Are there no others out there with an x2 with some linux experience who knows their way around an adb shell, that can help?
mastafunk said:
Starting to feel pretty alone in this. Are there no others out there with an x2 with some linux experience who knows their way around an adb shell, that can help?
Click to expand...
Click to collapse
Hey I'm back in business here! You and I can start working on something
I'm cool with running commands in adb and collecting logs.
dragonzkiller said:
Hey I'm back in business here! You and I can start working on something
Click to expand...
Click to collapse
Hope you aced those exams I keep missing ya on irc will be around most of tonight.
Im comfortable with adb if someone could get me up to speed on what I'd be doing I'd be more than happy to help.
Im a bit of a Linux newb but I learn fast.
Sent from my Eclipsed and ICS themed X2.
I am considering getting rid of my x2 (1mos old) and getting something different. Do y'all think there is a pretty good chance we may see CM on the x2? This will really influence my decision whether I keep this phone. Im really dissapointed with the stock rom and available roms.
Sent from my DROID X2 using XDA App
adb/terminal
let me know what I can do
Hey, I'd like to help abit. However - I don't actually get the point - What is the problem? I can't clearly figure it out from first 10 posts of all threads linked, I don't have X2 unfortunately, and don't feel like reading 300+posts from all threads. I can only guess you're on similiar point as we are with Badadroid.
For me running custom ROM (own kernel build+platform) looks like:
- compile kernel with needed changes (or own ARMLinux port based on CodeAurora or AOSP kernel and stock released sources)
- compile AOSP or manufacturer based platform
- adjust initramfs to match device layout, loading proprietary libraries if needed, consider using AOSP init or manufacturer init binary
- put it together and boot
Correct me if you need to and tell me try to tell me where are you stuck.Try to explain current problem in one of the threads and post all logs you can get. What about UART logs? These are very, very helpful (if not mandatory, unless you're freakin development master) in early kernel/bootloader development.
I'll pay a visit to your IRC soon.
//edit:
Okay, guys on IRC explained me abit, still counting on some logs.
Can't, gotta use motos kernel.
Sent from my DROID X2 using xda premium
Hey, how are you guys!?
So there's a few roadways you guys should explore. First and foremost work on some sort of bootstrap cwm. So you guys can gain access to pseudo-roms.
Quickly as possible begin looking into kexec or 2nd init.
and for the long term look into bootloader unlocks from the test servers. me if you need help!
samcripp said:
So there's a few roadways you guys should explore. First and foremost work on some sort of bootstrap cwm. So you guys can gain access to pseudo-roms.
Quickly as possible begin looking into kexec or 2nd init.
and for the long term look into bootloader unlocks from the test servers. me if you need help!
Click to expand...
Click to collapse
We have had a bootstrap for many months and already have pseudo-roms, and they've already got a working 2nd-init.
Now they're working on getting an AOSP/CM7 ROM to boot.
Bsr's? Kexec? 2nd init?!! Guys! Why haven't we tried this?! Rofl. We could totally get some blur based roms going . We could make up some cool names like "Eclipse", or "Liberty" or something!
Sent from my DROID X2 using xda premium
Not sure if you guys heard yet, but I just got offered a job and when I start I will be getting a bit more active again.
aceoyame said:
Not sure if you guys heard yet, but I just got offered a job and when I start I will be getting a bit more active again.
Click to expand...
Click to collapse
That's awesome new ace!!! Good luck at your job!
Sent from my DROID X2
Not doing it unless there's some cool rom named something hot like molten or something.
Sent from my DROID X2 using XDA App
Is this realty a different cwr? Could it help you guys?
From my post:
Snip
I noticed after uninstalling system recovery that it still worked w/ a battery pull. I remember now where the /preinstall files must have come from: I was fooling w/ rom manager as I was going to sbf anyway and I downloaded and booted as many recoveries as I could until I crashed. I crashed on the Atrix but think it was the Dx regular (not 2nd init) that loaded.
Snip
1)paste to /preinstall: the 5 files and set perms to rwxrwxrwx but adbd: rw-rw-rw-.
2)Change charge_only_mode ( your original in system/bin) to .bak. Then paste the 2 /bin files (less the .not file) set perms to rwxrwxrwx.
3)Then .recovery_mode goes in /data perms to rw-rw-rw-. Power off. Pull battery and put it back in. Plug in. CWR!
*****
Edit: this is the regular cwr not the Tenfar's edition, it there is a difference IDNK.
*****
http://forum.xda-developers.com/showthread.php?t=1408546
skwoodwiva said:
Is this realty a different cwr? Could it help you guys?
From my post:
Snip
I noticed after uninstalling system recovery that it still worked w/ a battery pull. I remember now where the /preinstall files must have come from: I was fooling w/ rom manager as I was going to sbf anyway and I downloaded and booted as many recoveries as I could until I crashed. I crashed on the Atrix but think it was the Dx regular (not 2nd init) that loaded.
Snip
1)paste to /preinstall: the 5 files and set perms to rwxrwxrwx but adbd: rw-rw-rw-.
2)Change charge_only_mode ( your original in system/bin) to .bak. Then paste the 2 /bin files (less the .not file) set perms to rwxrwxrwx.
3)Then .recovery_mode goes in /data perms to rw-rw-rw-. Power off. Pull battery and put it back in. Plug in. CWR!
*****
Edit: this is the regular cwr not the Tenfar's edition, it there is a difference IDNK.
*****
http://forum.xda-developers.com/showthread.php?t=1408546
Click to expand...
Click to collapse
That very well could help. The eventual goal is to change USB Early Enum to boot into CWR and then normal boot (2nd init) into your rom. The current one is sorta working with it but we do not have adb in it.
aceoyame 787,756 bytes both files: "recovery" from unzipped update-recovery.zip in PI or our apk.
hey guys i know this is probably a stupid question but couldnt there be a way to port the xoom ics rom to droid x2 they basicly have the same processor dont they
As of you guys have found out there has been a few threads that have been started that throw around theories about getting CWMR to work and such and I'm here to finally give you guys the progress from the dev that's working on it.
I have been working on getting CWMR working off and on for a few months now to some avail. I have been slowly testing it and sending out alphas to people on the IRC and now I'm here to tell you where I'm at and what has been accomplished.
Part 1: Getting into CWMR
I started working with our current bootstrap recovery as a base for CWMR. It was of course in charge mode, but it was a step that had to be done first. I got a hold on a CWMR binary and after a bunch of shell commands managed to get the mangled version of CWMR that we've seen before. From there I had the idea to inject the ATRIX binary into the recovery and try it from there. It was a big success and I could use some (very few) of the functions that if offered. But I was finally in CWMR on the X2. (I posted the picture on my twitter).
Part 2: Making the Functions Work
From here the first thing I decided to do was to get the "Fix Permissions" script working. By getting this to work I know I could place my own code in there that will log to the file that I could open up and see whatever I wanted as ADB didn't work YET (more on that later). I fiddled with it a bit and got it working.
This also allowed me to access the log and find out why the unmounting and formatting wasn't working either. This was due to an issue with the mke2fs and other complementary binaries not being appropriately compiled for our phone. As I was working on CM7 at the time, i had access to the sources of these and to the recovery binary as well. I decided to build a recovery binary that was tailored to our phone and not the ATRIX and the binaries that handle formatting partitions, etc. These worked on some partitions I could wipe data and cache properly by reformatting, I could easily erase a partition at will except for one: /system.
Part 3: Getting /system Formatted (WIP)
At this point I decided to find out why /system could never be formatted. When a partition needs formatting it must be unmounted first. But I could never unmount /system. By using the logs I found out that the partition was still in use. By using the "Fix Permissions" script, I managed to find that a lot of daemons (aka services) were being ran from the /system sub directories. This meant that in order to format, I had to have them not running. Easy enough as there's a script in CWMR that allows us to kill certain processes before the new recovery starts. I decided to kill all of the services with this script but found that the display would go blank. From there I found that two services are REQUIRED to be running on the phone for drawing (making things show on the screen) to take place: servicemanager and nvrm_daemon.
The servicemanager does exactly what it's title says: it manages the currently running services. This has to be running to keep nvrm_daemon running or else things get kinda freaky.
nvrm_daemon is what is used to manage drawing commands to the screen (the nv stands for nVidia which is who made the Tegra 2). With this service running I was able to (while in charge mode still) draw to the screen and show all of the menus for CWMR.
This created a problem. As these HAD to be running /system could never unmount because they were in there. Unless we used 2nd-init. From here I created my own hijack script that allowed me to copy over the necessary daemons into /sbin (which is just a sub directory of the rootfs). Then by using a new init.rc I could start these daemons from /sbin and see if they worked for CWMR.
After a lot of coding I managed to get the daemons running from /sbin and I thought I was free from there. And while I was at it, I might as well tried to get it out of charge mode.
Part 4: Untethering the Recovery (WIP)
I figured that since I was using 2nd-init anyway that I might as well have been working on trying to get it untethered also. After a bunch of looking into why charge mode was the only way to get it working, I found that before charge mode was started the init.rc started the "pre-zygote" services. These include usbd (the usb daemon), battd (the battery daemon), etc. What was also started was nvrm_daemon (another proof that we needed this running) to draw on the screen (charge mode draws the battery indicator to show charging progress).
I decided to move to mot_boot_mode to do the hijacking. I eventually managed to get things running but it still wouldn't draw to the screen. A look at the logs showed that for whatever reason we still didn't have access to the framebuffer (the memory space aka buffer that is drawn to the screen). I was tired of rebooting over and over again to get results and by now I had SBF'd I don't know how many times, only to not be able to access the logs due to a wipe. So next thing I decided was to get ADB working at boot.
Part 5: Starting ADB at Boot (The Short Version)
I took a look through the init.rc and found that Motorola had disabled the default way to get ADB working at boot. Through a bunch of digging I found that I could re-enable the method but it started usbd also (yet another daemon I'd have to move and thus more time, etc.). But eventually I found another property (aka system variable) that i could set that would start ADB without having usbd started: persist.adb.enable_NV_DISABLED. Setting that to 1 started ADB whenever I wanted it to. This allowed me access to the system (as root actually) without having to reboot and try to get into logs and whatnot. I could see everything that was running, mount/unmount and do everything I normally could and see better why they were failing.
Part 6: Recent Discoveries (as of 1/3/12) On the /system Unmount
I decided that I was going to go back to charge mode for now. After causing too much pain with framebuffer access I decided to look into why /system STILL wouldn't unmount after moving everything out of there. With the help of mastafunk and DrPenguin I was able to get a hold of a program named strace. This allows you to debug what binaries are doing down to pretty much every comparison, file opening, memory mapping, etc. I had found that nvrm_daemon (although started from /sbin) was looking for and loading drivers found in /system/lib. This was a problem and I thought that we may never get /system unmounted. Until I found out one other thing.
The nvrm_daemon doesn't look for the drivers inside of /system/lib first. It looks for them in /vendor/lib first and then if it can't find them, goes to /system/lib. So simple enough. I thought I could just make a /vendor/lib directory, copy the libs over and have them load from there. Well it's not that simple as there is already a file in the rootfs named vendor. But the file is a symlink to /system/vendor so if it looks at /vendor/lib it really looks at /system/vendor/lib. I thought I was stuck again until I took a closer look at the /system directory. There is no ./vendor sub directory in /system. That being said, I was able to delete the symlink in the rootfs and then create a /vendor/lib directory copy over the libs to it and nvrm_daemon successfully loaded the libs from there and not from system.
Conclusion
You are now caught up on when we've basically done to try to get CWMR working on the X2. Being that we're the only Tegra 2 phone from Motorola that is locked, we're kinda stuck trying to get things working. For now I consider this progress. Albeit slow progress, but progress none the less. If you took the time to read this, I hope you now understand the frustrations I've had to deal with this. All the while trying to help masta get 2nd-init fully working for our phones.
Thank you.
Thank you very much for the detailed explanation - well written so that even a novice like myself could understand your progress and frustrations. Thank you to you and your peers also for your hard work and determination to see this through. I think I can speak for all X2 users and say this is most appreciated!
Great writeup. Very informative. Thank you for your dedication.
I thought 2nd init was done and masta was working on aosp? I mean we can log from our new init.rc so it is using it. In the meantime i've been working on my barebones so we can get new blood using 2nd init and because I want a decent daily driver in the event we cant get stuff going.
To echo what others have said, thank you very much for the information. This kind of transparency is always very much appreciated when there's some spare time to put that out there. It not only is really helpful to make it understandable, but it's nice to know that these projects are still active.
Perhaps most importantly though in the context of potential progress: having specific information is a great way for knowledgeable people reading to recognize if they might be able to help out in certain areas. You might get some fresh ideas from people who hadn't considered themselves familiar enough with the situation to be useful. Who knows.
Anyways, thank you very much again. It's very encouraging to hear progress reports in general, not to mention ones like this that involve so many successes.
Wow thanks so much for your hard work and dedication can't wait until you conquer this sounds like you are closer then ever
Sent from my DROID X2 using XDA App
I am so glad to hear the "behind the scene" drama. Thank You DK sharing. I AM sorry for what bad drama I may have started. Will you forgive me?
skwoodwiva said:
I am so glad to hear the "behind the scene" drama. Thank You DK sharing. I AM sorry for what bad drama I may have started. Will you forgive me?
Click to expand...
Click to collapse
No need to appologize man... Stuff like this should have been posted or known. To be honest, I thought Masta was finishing 2nd INIT and starting to work on getting AOSP running and CWM was out the window, thats why I jumped in to try and get progress on CWM. Thanks DK and now I know the IRC is more active, I will be on there more to try and help out.
Thank you!
Thanks a ton for all the effort you're putting in. When I got my DX2 I thought that despite the crazily over-bloated Motoblur, I would be OK due to the Tegra 2 power and wonderfully innovative developer community. I didn't count on their being such a small number of us out there for this device or the complexity that Moto would unnecessarily bake in. So, after many months of gut wrenching disappointment, I finally have hope again.
You are a true nerd hero, sir!
Its nice to have an explanation of things and why they work or dont work. A lot of us are just trying to learn so we can be useful.
Sent from my Eclipsed and ICS themed X2.
Dragonz...after reading the info about 1/3/12 I am curious...
Does this mean that you might be able to get it working and unmount system as u need it to?
Or were there still other processes using system that you will need to mess with and change around as you did with the vendor ?
Do you still need to move the servicemanager also?
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
PM me with a copy of your nightly so I can help as well please
kaliblazin707 said:
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Kali send me a pm, I have the week off and work as a mobile developer... would like to help get rid of some of those crashes. Send me a link to that irc and ill get cracking on it 2moro
Sent from my DROID X2 using xda premium
drapp said:
Kali send me a pm, I have the week off and work as a mobile developer... would like to help get rid of some of those crashes. Send me a link to that irc and ill get cracking on it 2moro
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Webchat.freenode.net
Channel #X2-AOSP
AND #DX2 for "off topic"
kaliblazin707 said:
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
I know why you have a cm7 nightly "booting" and I'm sorry to say that it's not for good cause. What is happening is that the system isn't being formatted properly (hence a point in my post) and you're just flashing a bunch of new APKs from CyanogenMod on top of BLUR. I'm sorry to say, but it's not CyanogenMod.
dragonzkiller said:
I know why you have a cm7 nightly "booting" and I'm sorry to say that it's not for good cause. What is happening is that the system isn't being formatted properly (hence a point in my post) and you're just flashing a bunch of new APKs from CyanogenMod on top of BLUR. I'm sorry to say, but it's not CyanogenMod.
Click to expand...
Click to collapse
I honestly think the way to go is to get back to that step with proper 2nd init and then replace everything blur with as much CM as possible
aceoyame said:
I honestly think the way to go is to get back to that step with proper 2nd init and then replace everything blur with as much CM as possible
Click to expand...
Click to collapse
But that's not the right way to go. All that is is basically taking the BLUR base ROM and replacing the things with CM7's stuff. That's basically taking the stock rom and turning it into another blur-based ROM with CM7 apks. That's basically like Eclipse.
dragonzkiller said:
But that's not the right way to go. All that is is basically taking the BLUR base ROM and replacing the things with CM7's stuff. That's basically taking the stock rom and turning it into another blur-based ROM with CM7 apks. That's basically like Eclipse.
Click to expand...
Click to collapse
Let me rephrase that, add CM stuff and then remove Moto stuff. So get back to that, delete moto apk's and then edit init.rc for the framework. All those FC's we are getting if when were in that state are vital clues as to whats isn't playing nice with CM's apk's and framework. The fact it can even somewhat boot in a state like that means it's fairly close to how it wants. If it didn't wipe /system/ then it sounds like you just need to properly 2nd init that ***** and then in moto's init.rc remove moto jar's and apks's. Remember if it didn't wipe then you replaced the framework with CM and it's blur running ontop of it.
ashclepdia said:
Webchat.freenode.net
Channel #X2-AOSP
AND #DX2 for "off topic"
Click to expand...
Click to collapse
Thanks ashclepdia.... helpful as always...
Sent from my DROID X2 using xda premium
Hey Kids, I figured it was getting kind of boring around here so I'm releasing a little tool I've been using for a while now. It's just what it says, an "Auto Flasher". It will flash any rom, any kernel, backup data, restore data, fix permissions, etc. With full wipe function or just a cache and delvik wipe. All from the comforts of your pc. Just plug in your evo3d with usb debugging enabled and some room on your sdcard and off you go. Oh, almost forgot. This will also Odex all your system apk's if you like. It's on the menu. Even if you have some odexed, it will skip over those.
Things to do first:
1. Run the AF4.5setup.exe. Choose a location (I like the desktop) to run it from. It will create a folder called Auto Flasher V4.5.
1.a Run the 2.08setup.exe and the 2.17setup.exe *(these are just RUU 2.08 and RUU 2.17. Download them even if you already have them. The exe will install them to the proper folder.)
2. Open the Auto Flasher V4.5\Place-Files-Here\ROM folder and copy paste your rom of choice.
3. Open the Auto Flasher V4.5\Place-Files-Here\Kernel folder and copy paste your kernel of choice (if your flashing a kernel).
4. Make sure USB debugging is on and you have about 500 mb on your sdcard.
5. If you need HTC drivers, look in the \Drivers folder. (Install them first).
6. Run the Auto_Flasher_V4.5.bat.
7. Sit back with a brew and watch the show. (It will prompt you a couple of times for some yes and no questions).
NOTES:
I had to separate the .exe's because of file size limitations on DevHost. If your not doing a firmware change then you don't need them. But I recommend you download them.
When restoring data, run your rom first for a couple of minutes. I found everything takes nicer.
When running "11. Fastboot Radio/Wimax Flasher" Please make sure you don"t interrupt this. You won't like the results. If something goes wrong, you will have to flash your radio manually because you'll be in a nasty bootloop.
This is a beta release. Many improvements on the way.
Disclaimer:
If you say I bricked your phone. I will laugh. Nothing this does can't be undone with a nand restore. So for the love of god, DO A NAND BACKUP FIRST!!!
Download: New Links
http://dev-host.org/sFH - (Version 4.5)
http://dev-host.org/u2l - (2.08 setup)
http://dev-host.org/em1 - (2.17 setup)
Old:
http://dev-host.org/btB - (Version 4)
ChangeLog:
V4.5
- Added 12th Menu ---> Hboot 1.5 Flasher
- Same as V4 just with Hboot 1.5 Support.
- Still working on V5
V4
- Added 11th Menu
- Fastboot Radio/Wimax Flasher
- Added Date and time
- Fixed some bugs
- Realigned menu
- Added a lot more arguments (for less problems)
- 32x (bit) Compatibility
- New Icon
- Suprises coming in V5!!!
V3
- Initial release
Edit: For those who have downloaded V4 before 2/27/12, don't use the Auto_Flasher_V4.exe. There's some thing wrong with it. Instead, I've attached Auto_Flasher_V4.bat (unzip it of course). Place that in the \Auto Flasher V4\Auto Flasher V4 directory were adb.exe and all the other files are. Run that instead. Other wise redownload the whole thing again. New link is up.
Special thanks go out to to my son ZxZueSxS for helping me write this and the XDA family. You guys are great.
Big Thanks to all of the people that downloaded this.
If you like this please hit thanks on my page and ZxZueSxS page.
Will this work on hboot 1.5?
jdeoxys said:
Will this work on hboot 1.5?
Click to expand...
Click to collapse
Yes. the zipped folder has TWRP 1.1.1 in it, which works the same way, if you run it manually with ADB and Fastboot. The OP has made the process a little shorter and easier for you.
Thanks gonna give this a try later, so basically this acting like a Recovery in a way...
Sent from my PG8610000 using xda premium
gunfromsako said:
Thanks gonna give this a try later, so basically this acting like a Recovery in a way...
Sent from my PG8610000 using xda premium
Click to expand...
Click to collapse
Yes, it boots a recovery img.
just wanted to say thanks, gonna try this now. i see your in valpo too, that Indiana?
Yes it is
Sent from my PG86100 using XDA App
I'm currently working on a fastboot flasher add-on for radio's and wimax. Any request to make things easier?
Redownload
Sorry guys. I didn't have all the files in the zip. Please redownload. New link is up.
Although I have not yet tried this, I did just download it and feel like a kid at Christmas. I cannot wait to try this.
I'm on 1.5 as well; I'll give this a go and let you know how it goes!
Thanks a ton!
Sent from my Etch-A-Sketch using Tapatalk.
rpenrod23 said:
Although I have not yet tried this, I did just download it and feel like a kid at Christmas. I cannot wait to try this.
I'm on 1.5 as well; I'll give this a go and let you know how it goes!
Thanks a ton!
Sent from my Etch-A-Sketch using Tapatalk.
Click to expand...
Click to collapse
Thanks. Reply's are welcomed. I'm not sure how it does with 1.5. I'm on 1.4. But if you let me know, I can alter it as needed.
Macropoutsis said:
Thanks. Reply's are welcomed. I'm not sure how it does with 1.5. I'm on 1.4. But if you let me know, I can alter it as needed.
Click to expand...
Click to collapse
I have downloaded this on 2 different PCs with both IE and Firefox and am unable to run the Auto_Flasher_V3.exe.
I receive the good ol' "Auto_Flasher_V3.exe is not a valid Win32 application" error.
Thoughts? I find it hard to believe that I have downloaded multiple bad copies.
rpenrod23 said:
I have downloaded this on 2 different PCs with both IE and Firefox and am unable to run the Auto_Flasher_V3.exe.
I receive the good ol' "Auto_Flasher_V3.exe is not a valid Win32 application" error.
Thoughts? I find it hard to believe that I have downloaded multiple bad copies.
Click to expand...
Click to collapse
That's odd. I'm not sure. What OS are you running?
rpenrod23 said:
I have downloaded this on 2 different PCs with both IE and Firefox and am unable to run the Auto_Flasher_V3.exe.
I receive the good ol' "Auto_Flasher_V3.exe is not a valid Win32 application" error.
Thoughts? I find it hard to believe that I have downloaded multiple bad copies.
Click to expand...
Click to collapse
Sorry about that. I figured it out and have made changes in V4.
Update V4
Just put up V4. Many improvements. Give it a try.
the link in the first page says THERE IS NO FILE.
please be kind to upload your latest version.
thanks very much.
New Link
For those who have downloaded V4 before 2/27/12, don't use the Auto_Flasher_V4.exe. There's some thing wrong with it. Instead, I've attached Auto_Flasher_V4.bat (unzip it of course). Place that in the \Auto Flasher V4\Auto Flasher V4 directory were adb.exe and all the other files are. Run that instead. Other wise redownload the whole thing again. New link is up.
dralibak said:
the link in the first page says THERE IS NO FILE.
please be kind to upload your latest version.
thanks very much.
Click to expand...
Click to collapse
Link is up. Had to take it down. Sorry
Hey guys, I need someone with Hboot 1.50 to test this. I'm on 1.40. I believe you need to use the HTC Unlock Hboot 1.50 method first found here http://www.htcdev.com/bootloader . Then just use the tool. Thanks.
Will HBOOT 1.5 users be able to flash new radios/wimax with this without having to run the latest ruu? Thanks