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
Related
Hi,
I just realised that I'm going to post this, hopefully to get some help getting the frame buffer issue working. I'm not giving up on it, but it just doesnt seem fair to sit on this any longer since it works, besides the GUI glitches.
As i said before, the S7 kernel does not support framebuffering, which makes the GUI in the recovery a bitt messy. When you move up / down in the menu, it switches between selecting an item on top and an item on the bottom (you'll see 4 menus in total, but the ones on each horizontal line is a mirror).
This means that it starts by using the lower one, and it uses the top one next, then it goes back to the lower one. Boot it up and you'll probably see what I mean. This shouldnt cause any problems with the recoverys operation anyhow.
If you want to enter adb in linux you will have to get a copy of usb_modeswitch and run the following line in order to get adb to recognize the device:
sudo usb_modeswitch -W -v 12d1 -p 1031 -V 12d1 -P 1035 -M "5553424370ab71890600000080010a1106000000000000000 0000000000000" -s 20
This will switch the huawei s7 usb device into adb mode.
Also i take no responsibilites of bricks or other problems caused by using this recovery. Its truly for learning usage only.
My credit list would be to long if I where to include all forums that I've visited to get more information about this device, but if you feel like you deserve credit, let me know and i'll add you, otherwise, thanks to all people posting information about android devices, i could never have done it without you.
Ofcourse i have to thank the creators of clockwork mod, and also the people who wrote the repack-image.pl and unpack-image.pl scripts
Thanks to my wife who put up with me sitting and messing around with this for almost a week, giving her not the attention that she deserved, and thanks to all users of the S7 tablet out there.
h***://rapidshare.com/files/438781673/recovery.img.zip (not allowed to post links yet)
The shortcut key for entering recovery is menu + send, if anyone wonders.
Hope you'll enjoy it as much as I did.
Works great. Ill research a bit to see if i can help
Sent from my Ideos S7 using XDA App
Sorry for qwestion, but... How can i put it into device? Via fastboot on cmd, or somehow other?
Sent from my Ideos S7 using XDA App
I hope we can get a 2.2 rom
sorry, but it working not fully...
its have errors to open nandroid-mobile.sh
and its cant format SDcart to partitions ext2 and ext3...
or maybe i doing something wrong
GvoZdik said:
sorry, but it working not fully...
its have errors to open nandroid-mobile.sh
and its cant format SDcart to partitions ext2 and ext3...
or maybe i doing something wrong
Click to expand...
Click to collapse
You're right, I noticed now that I the wrong ramdisk in the image that was released. I have several of them for which I use to debug the framebuffer stuff, and I forgot to use my own build.
I'll upload the correct one sometime this weekend.
Sorry.
Sent from my HTC Desire using Android Tablet Forum App
thanx, thats a great work anyway...
Sent from my S7 using XDA App
thanks perivarlura for your support!
perivarlura said:
You're right, I noticed now that I the wrong ramdisk in the image that was released. I have several of them for which I use to debug the framebuffer stuff, and I forgot to use my own build.
I'll upload the correct one sometime this weekend.
Sorry.
Sent from my HTC Desire using Android Tablet Forum App
Click to expand...
Click to collapse
The ui glitches even more now that the misc partition handled and the nandroid script is running. I guess i need to get this fixed before i release it, or it will just be a mess.
***UPDATE***
I am removing this tutorial from general public view. if you read the warnings/disclaimers and are still interested you will need to read the links below and go about it yourself.
--------------------------------------------------------------------------------------
first off credit for this idea go to all the people/sites linked below. IF credit is missing where due please notify me and i will resolve. This is just a gathering of other posts and steps that worked for me.
This will wipe your device. backup anything and everything before proceeding.
If you are not willing to take it upon yourself to research any problems that arrise and fix them yourself DO NOT ATTEMPT.
If you are unwilling to wipe your stock Firmware DO NOT ATTEMPT.
If you are unwilling to start with a fresh nookie color SDcard NO NOT ATTEMPT.
If you are unable to fix your problems or want to revert to stock you can do so following the link at the bottom of the page
This is for advanced users. Make sure you read and reread everything before attempting anything! I take no responsibility and offer no promise of support if you make yourself a $250 B&N brand paperweight. keep in mind the nc is hard to brick (know from experience) but anything can happen, so be warned and proceed with caution.
if something below is not clear visit the links provided and look for your answers there. they are there and the more you read and learn the more sense this will make. if you are still unable to find help post here and i will try to get you going.
now on to the good stuff. I just wanted to gather the various posts and links that i used to gt a fully working froyo running on my nc from the internal memory (emmc) and present them in a step by step guide for others wanting to run NF from their internal memory and have no need for B&N stock. Flash is working if you install the proper apk. this is not installed out of the box. After installing to your EMMC you will be able to use any sdcard as you normally would in android. I am using a 16gb card with no problems.
***steps removed... see top of post***
helpful links:
http://forum.xda-developers.com/showpost.php?p=10254900&postcount=138
http://forum.xda-developers.com/showpost.php?p=10747294&postcount=2
nookdevs steps for creating nookie froyo sdcard:
http://nookdevs.com/Nookie_FroYo:_Burning_a_bootable_SD_card
nookie froyo thread:
http://forum.xda-developers.com/showthread.php?t=883175
nookdevs nookie froyo tips:
http://nookdevs.com/NookColor:_Nookie_Froyo_Tips
wipe nc to stock: (download the images and run the commands from an adb shell.)
http://forum.xda-developers.com/showthread.php?t=919353
Flash back to clean stock ROM (nook devs) http://nookdevs.com/Flash_back_to_clean_stock_ROM
1. first you will want a fresh NF sd card. I tried to use my seasoned nf card and ended with a brick... if you have google apps installed you will not be able to get past the android screen and will have to reimage as stated above. create your fresh nf sdcard following the steps at nookdevs here
Click to expand...
Click to collapse
As we say in french, you must call a cat a cat. Your NC wasn't bricked at all. You simply needed to touch each corner of the screen one at a time when on "touch the android" screen, starting with the top left corner, then clockwise.
Would have saved you some time
If I were you (if I may..), I'd put all the links the bottom of the post. Would make reading easier. As for my code to copy sdcard content, go on and post it directly. Opening multiple pages only makes things more complicated. No problem. As for the Volume keys and gapps, it could be ambiguous, those add-ins aren't required at all. Simple leave a link to nookie tips on nook devs for those who want it?
But of course, this is your post..
Sam
samuelhalff said:
As we say in french, you must call a cat a cat. Your NC wasn't bricked at all. You simply needed to touch each corner of the screen one at a time when on "touch the android" screen, starting with the top left corner, then clockwise.
Would have saved you some time
If I were you (if I may..), I'd put all the links the bottom of the post. Would make reading easier. As for my code to copy sdcard content, go on and post it directly. Opening multiple pages only makes things more complicated. No problem. As for the Volume keys and gapps, it could be ambiguous, those add-ins aren't required at all. Simple leave a link to nookie tips on nook devs for those who want it?
But of course, this is your post..
Sam
Click to expand...
Click to collapse
I tried the touching four corners. no go. several roms required that back when i was using a D1... I couldnt for the life of me figure it out so just scrapped and started from scratch.
thanks for your input. i planned to clean this up a bit, was just in a rush writing the original. Thanks again for your help. couldnt have gotten this far without your steps to start off.
Eager to try this out ... but will it be able to see a non-NF SD card I enter in? Will it recognize it, and let me see it as mass storage when the Nook is plugged into my PC?
Very well written, just copy and paste the code into the console for the most part ... Runs nice and fast, I have a few FC's to clean up but that is due to me not factory resetting the NC prior to doing this as I am an impatient person! I must say it is very nice not to have the B&N notification bar at the bottom of the screen.
So if this is really 2.2, does it have flash?
theyownus said:
I used 0.5.9 and replaced the vold file with the one from 0.5.8 making sure to maintain executable permissions.
Click to expand...
Click to collapse
a) What vold file? Searching for "0.5.8 vold" on this board produces no hits.
b) Executable permissions on what? This "vold" file or something else?
Don't want to be "that guy" but date should read 1/20/2011.
Thanks gonna give this a shot.
What happens to the Media partition?
Also, slightly random: Why doesn't adb ever seem to work over USB with my Nook Color? 2.1 ROM, Nookie Froyo on SD 0.5.8 or 0.5.9, it never sees a device. By contrast, it works fine on my G2.
starkruzr said:
Also, slightly random: Why doesn't adb ever seem to work over USB with my Nook Color? 2.1 ROM, Nookie Froyo on SD 0.5.8 or 0.5.9, it never sees a device. By contrast, it works fine on my G2.
Click to expand...
Click to collapse
Re-run ADB configuration. Make sure id is 0x2080.
How do we fix the SD card error. I am unable to do anything with the SD card.
samuelhalff said:
Re-run ADB configuration. Make sure id is 0x2080.
Click to expand...
Click to collapse
Wow. This is INSANELY important and this is the first time I've ever seen mention of it. Every other post simply assumes your ADB "just works." I have been endlessly frustrated by the lack of working ADB on this thing such that every time I do something with my NC I have to find a way to first install ADBWireless.
http://fineoils.blogspot.com/2010/11/pokey9000-has-got-self-booting-image.html
The instructions to get it working are in here, folks. Can these instructions be put in a sticky somewhere? This is about the least-obvious thing I can think of.
Is there any improvement in speed and reliability running this from the emmc as opposed to a class 6 uSD?
"extract them to their respective folders"
Nothin but bootloop
theyownus said:
first off credit for this idea go to samuelhalff
links:
original steps from samuelhalff http://forum.xda-developers.com/showpost.php?p=10747294&postcount=2
Click to expand...
Click to collapse
What a great idea. If only someone had talked about this weeks ago... Anyway now that it seems people are going to be trashing their nooks trying to do this, it's probably simpler for one to just boot into SD and...
[Replace the files in /system]
It would also be a good idea to clear out /data and /cache or there will likely be bootloops when froyo boots with the old data stuff still around.
That's off the top of my head and totally untested. Seriously. It probably doesn't work, and is totally unrecommended. Anyone who types "rm -rf *" in their emmc system is saying goodbye to their stock OS and will have to live with their decision. All GPL disclaimers apply.
Note also that IOMonster has a nice bootable clockwork SDcard that does all kinds of things, and automating this type of migration is only a matter of time now.
Update: Actually the steps aren't THAT different. /just sayin'.
fattire said:
What a great idea. If only someone had talked about this weeks ago... Anyway now that it seems people are going to be trashing their nooks trying to do this, it's probably simpler for one to just boot into SD and...
Somewhere in there it would be a good idea to clear out /data and /cache or there will likely be bootloops when froyo boots with the old data stuff still around.
That's off the top of my head and totally untested. Seriously. It probably doesn't work, and is totally unrecommended. Anyone who types "rm -rf *" in their emmc system is saying goodbye to their stock OS and will have to live with their decision. All GPL disclaimers apply.
Note also that IOMonster has a nice bootable clockwork SDcard that does all kinds of things, and automating this type of migration is only a matter of time now.
Update: Actually the steps aren't THAT different. /just sayin'.
Click to expand...
Click to collapse
I had the same reaction reading the post. Not only is it unfair to you, because I have read your post before attempting anything, but it's also unfair to me because it suggest that he did most of the practical work..
Anyway does it really matter? People who don't regularly read the forum often don't give a Jack of who's responsible for what. Those who do willl know you were first in line. Anyway, I understand your frustration I should have said something. I was just fed up. Sorry.
Please know that my original post recomanded doing dd's of all partition. That way reverting back to stock was easy. My post also mentionned emptying data.....
What do mean steps aren't that different?
Sent from my HTC Desire using XDA App
samuelhalff said:
I had the same reaction reading the post. Not only is it unfair to you, because I have read your post before attempting anything, but it's also unfair to me because it suggest that he did most the practical work..
Anyway does it really matter? People who don't regularly read the forum often don't give a Jack of who's responsible for what. Those who do willl know you were first in line. Anyway, I understand your frustration I should have said something. I was just fed up. Sorry.
What do mean steps aren't that different?
Click to expand...
Click to collapse
Ah, I just mean it's all the same idea-- out with the old, in with the new. Nothing particularly genius about it. In any event, it's not really a matter of credit. We all stand on the shoulders of giants. I was just amused is all... so let's just have fun, eat, drink, be merry, and dance in the rain.
It may turnout that English isn't the OP's native language. Although it isn't mine either..
Nothing really seems genius once you get to understanding it.. but as a newcomer, I still had a bit of trouble getting the sdcard to mount..
Sent from my HTC Desire using XDA App
So I've been doing this android flashing business a long time
And I've got a real mess on my hands. I'll be ****ing with this for the rest of the night! Thanks!
Why oh why can I not get anything to boot on my gosh darn incredible? I've tried everything except making it all work.
I want so badly to get something to boot, but alas it never happens. Stuck at the white screen is as far as I ever get. I don't even get the satisfaction of seeing a bootloop, at least then I'd be seeing some sort of progress. Its disheartening. I've tried all kinds of roms and system dumps to no avail.
There must be something I'm doing wrong, what?
Sent from my ADR6300 using XDA Premium App
Do wipe data and cache before flashing?
Yeah. I did manage to get a boot loop with the huashan gingersense leak. So some progress.
Sent from my ADR6300 using XDA Premium App
Give more detail, and I might be able to help. What steps are you taking to port the ROM?
You need a kernel from your device at least. You also need to change some entries in build.prop and rename the init.devicename.rc to your device's name and not the original ROM's. Then you need to replace any device specific drivers and libs with ones from your device. And then, it still might not work. There's a lot going on here.
I'm assuming that by 'porting' you mean taking an existing ROM from another device and making it work on yours. The word has a different meaning also, which is take AOSP/CM/whatever and make it work on a device that it doesn't currently work on.
gnarlyc said:
Give more detail, and I might be able to help. What steps are you taking to port the ROM?
You need a kernel from your device at least. You also need to change some entries in build.prop and rename the init.devicename.rc to your device's name and not the original ROM's. Then you need to replace any device specific drivers and libs with ones from your device. And then, it still might not work. There's a lot going on here.
I'm assuming that by 'porting' you mean taking an existing ROM from another device and making it work on yours. The word has a different meaning also, which is take AOSP/CM/whatever and make it work on a device that it doesn't currently work on.
Click to expand...
Click to collapse
Thanks I've swapped the boot.img, changed the build.prop, didn't rename the init file I instead copied over it. Copied the wifi modules, all the missing libs, the usr folder, bin folder, etc folder, and xbin.
Problem is when I change the libs it never gets past the splash, but when I change just the boot.img it'll boot loop.
And yes I mean from one device to another.
Sent from my ADR6300 using XDA Premium App
Mr. Rager said:
Thanks I've swapped the boot.img, changed the build.prop, didn't rename the init file I instead copied over it. Copied the wifi modules, all the missing libs, the usr folder, bin folder, etc folder, and xbin.
Problem is when I change the libs it never gets past the splash, but when I change just the boot.img it'll boot loop.
And yes I mean from one device to another.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
Personally, I wouldn't copy entire folders over. I also wouldn't copy the boot.img over. I'm not saying that it won't work in some cases. It might. I've always swapped the kernels inside the boot.img, and renamed the device specific init file. Then, I would compare the init files from an existing ROM for my device with the init files from the ROM that I'm trying to port and see if there are any lines that are device-specific. If the init file is trying to start up something that doesn't exist on my device, then it doesn't make sense to keep that line. On the other hand, there might be a line that changes something for that ROM that IS needed.
This same thing kind of goes with the libs and other files too. You might have one lib that relies on another lib being there. And it might need a particular build of that lib. And other files might call certain libs. This is one reason that building from source generally works better over the long run than trying to get one device's ROM to work on another.
You have device specific and ROM specific things going on at the same time, so wholesale copies tend to miss one or the other. Plus it's nice to dig in and get an idea about what's going on.
Also, if you can get adb access while it's booting, grab a logcat. It might give you an idea about what is failing.
I re-did the boot.img by replacing the kernel and renaming (in this case) init.hua_shan.rc to init.inc.rc. It gets past the "HTC Incredible" splash. So, that's a plus.
I did get a logcat, as I always do when I flash a new rom that hasn't been tried before. I use pastebin so take a 'gander' at it if you will.
From the looks of it Alsa, bouncycastle, and audio libs are having problems. Oh, and the bootanimation.zip didn't get dumped from the Huashan, but it's no big deal.
http://pastebin.com/VVxufgQL
Oh, and thank you for the help you have provided thus far.
Mr. Rager said:
I re-did the boot.img by replacing the kernel and renaming (in this case) init.hua_shan.rc to init.inc.rc. It gets past the "HTC Incredible" splash. So, that's a plus.
I did get a logcat, as I always do when I flash a new rom that hasn't been tried before. I use pastebin so take a 'gander' at it if you will.
From the looks of it Alsa, bouncycastle, and audio libs are having problems. Oh, and the bootanimation.zip didn't get dumped from the Huashan, but it's no big deal.
http://pastebin.com/VVxufgQL
Oh, and thank you for the help you have provided thus far.
Click to expand...
Click to collapse
Did you also change the ro.board.platform parameter in build.prop so that it matches the chipset name originally on your device?
Also, the next time you flash this ROM, dump the recovery log file before you reboot. This may show you errors encountered during the flash which were not shown in the normal output. A common error is porting a large ROM - such as Desire HD's - to a device with a small system partition in comparison. A workaround is to remove unneeded apps under system/app to reduce size of the ROM.
You may also want to try the Porting option in my Android Kitchen, it does the renaming, kernel and driver modifications for you.
dsixda said:
Did you also change the ro.board.platform parameter in build.prop so that it matches the chipset name originally on your device?
Also, the next time you flash this ROM, dump the recovery log file before you reboot. This may show you errors encountered during the flash which were not shown in the normal output. A common error is porting a large ROM - such as Desire HD's - to a device with a small system partition in comparison. A workaround is to remove unneeded apps under system/app to reduce size of the ROM.
You may also want to try the Porting option in my Android Kitchen, it does the renaming, kernel and driver modifications for you.
Click to expand...
Click to collapse
I've had a busy past couple of days, but I'll check into the recovery dump and see what's up. I did change the ro.board.
I was trying to abstain from your porting tools, no offense, only so I could do it manually. Just trying to gain more experience, I guess, and learn. Your kitchen is excellent. I use to set up my environment and deodex among other things. The porting tool, though greatly eases the pain and shorten the manual labor ( yes lazy America) , take the learning curve out, a bit. But I guess I could take a look at the script to see what's going on too. Lol.
EDIT#1 - So I just tried to flash my rom. However, it wouldn't, because for some reason my phone is very particular about how one copies files over to the sd card. For one, you have to have the phone booted up, MIUI GB latest in my case, and mount usb storage. If I mount it through recovery, it corrupts my sd card, too bad I wish I knew that earlier. It's a PITA really...Ubuntu...
But, as phone WAS:
Hboot - 0.92
Radio - 11.19
Ship S - OFF
I tried copying and flashing through recovery. Fail as usual. So, I was gonna boot up into MIUI and try to copy from there, and got the infamous 5-vibe and twinkle.
I tried several times to boot into MIUI, but after many battery pulls, I figured out something ODD. In the bootloader the first couple of times it skipped the scanning process, then it started scanning again. Upon further inspection:
Hboot - still 0.92
Radio - still 11.19
Ship S - ON <---NOT A TYPO
Why? I haven't a clue. I tether my phone, so I got it booted, yay, but to do it, my sd card has to be removed and my usb plugged in, then turn on. So, my next edit will be a progress update. AFTER I s-off again ( that sounds kinda dirty, lol ), and re-format my sd. Also, my phone thinks it's charging...ITS UNPLUGGED. Lol, infinite-charging batteries, it's the future...
Sent from my ADR6300 using XDA Premium App
So...Good news is I got another incredible with amoled screen
Bad news I got another incredible with nothing on it, or rooted :-( But I rooted it before I even activated it with *228
But, alas, I still have all of my work on my computer. I managed to back it up before my phone crapped out. Plus I kinda get to start from the beginning so I can be more observant, and particular.
So, back to work...will update tonight.
Edit 1 - So after some more tinkering I've managed to fix some issues, but others have popped up namely the HTC Sim card authentication, which I have no idea about, yet, bouncycastle.jar is being stubborn by not fiding its classes, and libaudioflinger.so is failing to link to libsystem_server.so which in turn fails the link to libandroid_servers.so. Same three problems as before it seems.
Here's a pastebin of the logcat.
http://pastebin.com/QYde7fuQ
I'll keep tinkering about and see what I can come up with. Hopefully I'm closer to getting this thing booted up than I think.
No, I do not have a nook tablet so I can not offer any methods to bypass myself. This is just a thread where developers can talk about gaining the ability to flash roms and recoveries.
Developers, please use this thread to collaborate so we can have everyone working in the same space.
Users, please try to not post and if you do, don't make it a completely useless post like something that just says thanks and whatnot. Just use the button for that. The less clutter = more progress
edit: Someone is donating a nook tablet to me to try and bypass the bootloader! Here's hoping it doesn't get bricked.
I've got a Nook Tablet and would be more than happy to help with this. I'm available most evenings after 9PM EDT.
I've been reading alot about kexec and 2nd init. It looks like 2nd init is the way to go, due to the fact that it's already been used multiple times.
Ideally what I'd like to do is try to reverse engineer a current 2nd init to work for the nook.
The potential issue I see is, the kernel may not be new enough to run CM7.
Am I completely off base here?
chantman said:
I've got a Nook Tablet and would be more than happy to help with this. I'm available most evenings after 9PM EDT.
I've been reading alot about kexec and 2nd init. It looks like 2nd init is the way to go, due to the fact that it's already been used multiple times.
Ideally what I'd like to do is try to reverse engineer a current 2nd init to work for the nook.
The potential issue I see is, the kernel may not be new enough to run CM7.
Am I completely off base here?
Click to expand...
Click to collapse
Kernel is good enough to run CM7 (Gingerbread), but not sufficient for CM9 (ICS). Also it is not good enough for CM8 either (although the chance we see CM8 for any device is doubtful).
We need to find a way to keep a chat between developers. Add me on g+ and ill create a huddle for every dev
Sent by breaking the sound barrier
chantman said:
I've got a Nook Tablet and would be more than happy to help with this. I'm available most evenings after 9PM EDT.
I've been reading alot about kexec and 2nd init. It looks like 2nd init is the way to go, due to the fact that it's already been used multiple times.
Ideally what I'd like to do is try to reverse engineer a current 2nd init to work for the nook.
The potential issue I see is, the kernel may not be new enough to run CM7.
Am I completely off base here?
Click to expand...
Click to collapse
your pretty spot on, but i dont see cm7 being a problem, i see cm9 being a problem. with a 2nd init rom you have to build the OS around the kernel(which it is much harder than doing it the right way) and if the kernel isnt high enough or if drivers are outdated(like the nook color graphic drivers) than you can count that OS out of your list. cm7 since it is gingerbread and since gingerbread can be booted on a froyo kernel(moto droid proved that along with the droid x/2), i think it can be booted using 2nd init, ICS on the other hand needs a ICS kernel to boot and if your not using an ICS kernel than you need a custom kernel that can get ics booting properly
now i disagree with you about 2nd init being the best way to build a rom for the nook tablet, i believe kexec is the best way to go about building a rom for the nook tablet because it will allow for a custom kernel to be booted off the original kernel. from what i have read about kexec on android is that they cant get the 3g chip to get started again(but nook tablet doesnt have a 3g chip so who cares), but wifi and all the other key functions can get started up and running, so using kexec on a nook tablet seems the best logical solution to getting around the locked bootloader(but dont quote me on this cause i havent developed anything for the nook tablet yet, nor do i even own one).
---------- Post added at 11:19 PM ---------- Previous post was at 11:18 PM ----------
Indirect said:
We need to find a way to keep a chat between developers. Add me on g+ and ill create a huddle for every dev
Sent by breaking the sound barrier
Click to expand...
Click to collapse
devs use irc to chat, its easier than any forum or chat program out there
Thats true but i cant always be on irc to keep up on info.
Sent by breaking the sound barrier
Also, ill look into getting kexec once i get my nook tab
Sent by breaking the sound barrier
Indirect said:
Thats true but i cant always be on irc to keep up on info.
Sent by breaking the sound barrier
Click to expand...
Click to collapse
There are most likely complete logs available somewhere to review, or someone could make them available for you. I don't have the link on this pc, but there is a site that keeps up-to-date logs #nookcolor available
Indirect said:
Also, ill look into getting kexec once i get my nook tab
Sent by breaking the sound barrier
Click to expand...
Click to collapse
I wouldn't spend too much time on this. Assuming that android_4430BN_defconfig from B&N's kernel sources is the defconfig used to compile the running kernel, kexec will not work as it has been disabled.
it doesn't really matter if kexec has been disabled in the kernel config. we can't really hope that they would leave a gaping hole that fricking big. honestly i'm kind of annoyed at the "omg they didn't configure their kernel specifically for us to hack the crap out of the device" posts. Seriously, even if they did this, as far as i've seen we have yet to disable OTA updates, so 3 seconds of a B&N developer time would wipe out any work depending on kexec being built into the kernel.
we can after all create modules neh? my linux kernel hacking experience is very close to non-existent, but i'll be starting by getting a module to load, followed by getting the kexec tools and a kexec module loading.
so far i'm having trouble finding any literature on kexec on ARM. it all says it's x86 only, but clearly everyone from motorola to sony communities are making use of kexec on arm. anyone know of any good points to find information on kexec for arm?
I've also seen something call splboot mentioned a few times, but am having trouble googling anything useful up. anyone familiar with that tech?
I suggest posting in the motorola dev section seeing if any of them would be interested in getting kexec up and running on the nook tab or could point us where to get information on it running with an ARM architecture device.
Indirect said:
I suggest posting in the motorola dev section seeing if any of them would be interested in getting kexec up and running on the nook tab or could point us where to get information on it running with an ARM architecture device.
Click to expand...
Click to collapse
Try Kabaldan. http://forum.xda-developers.com/member.php?u=2218140
He was a great developer when I owned a Motorola Milestone. Assuming he used 2ndInit to port CM6 and CM7
http://lists.infradead.org/pipermail/kexec/2008-February/001272.html<-- kexec on an ARM processor.
I just tried something to see where it would get me and if I could learn something new.
Using ROM Manager, I have been trying to flash different recoveries to see what results I would get or what I could break (or brick). After some research I found a device also running the OMAP 4430 processor and selected it (LG Optimus 3D). When I selected reboot into recovery, I did get some new screens I have not seen before. It made me reboot again, then another screen flashed very fast and it then rebooted and was normal from there. I think it may have replaced the recovery I flashed as it was flashing something but was very fast. I will try it again and see if I can determine what is happening. But I got it's attention and probably flashed the right thing in the wrong place, or the wrong thing in the right place.
I found a guide on a site for flashing a recovery to a device using flash_image binary, and two files were mentioned and deleted which allowed hijacking of the recovery process. Out NT has those two files as well:
/system/recovery-from-boot.p (encrypted, cannot view)
/system/etc/install-recovery.sh (can view code, and points to first file)
I wonder what the possibility is to hijack the install-recovery.sh file ? Or is there yet another file in the process? Very interesting though.
Ive actually been thinking of hijacking the install recovery script
Sent by breaking the sound barrier
To ellaborate further on my previous post, I believe this is the key to how we can get a bootloader bypass for a custom recovery as they have done for the Motorola Bionic and other Motorola phones. When a reboot occurs, the bootloader looks for a certain file in a certain place, if it exists then it reboots into recovery. If not, it boots like normal. The bootstraps for the Motorola devices mimic the logwrapper binary that the bootloader looks to and allows it to go into a custom recovery instead. A very simplified explanation.
What their bootstrap does is place the recovery indicator file in the proper place (somewhere in /data) and when the bootloader finds it, it goes to the logwrapper binary, which of course has been replaced with their hijacked version.
It appears the install-recovery.sh on our NT is looking for a "recovery" indicator, and if it exists, it is telling it to go to recovery-from-boot.p
If so, this is the very process we need to hijack to allow some type of custom recovery. It doesn't get us completely around the bootloader, but it would allow a recovery mode for flashing custom ROMs, just as the Motorola guys have done. I am probably way over simplifying this, but i have researched this quite a bit the past few days and it looks like for the short term, this is the path we need to look at.
If anyone has contact with Kousch or someone familiar with the bootstrap process, I think we could be in business to get something workable here.
Here is a link to one of the Motorola bootstraps, and the contents of the /system/etc/install-recovery.sh
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
#!/system/bin/sh
if ! applypatch -c IMG:/dev/block/platform/mmci-omap-hs.1/by-name/recovery:2048:70ef89e0497435e988819690aaabb35da6b7677f; then
log -t recovery "Installing new recovery image"
applypatch IMG:/dev/block/platform/mmci-omap-hs.1/by-name/boot:2850816:114706e7bbfa4c806323215a83d6ad4e9cd392f7 IMG:/dev/block/platform/mmci-omap-hs.1/by-name/recovery 532ad547febe82850924a52625132376514e3a8b 3203072 114706e7bbfa4c806323215a83d6ad4e9cd392f7:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Or all of this could be in place and not ever used !
---------- Post added at 02:22 PM ---------- Previous post was at 02:18 PM ----------
Indirect said:
Ive actually been thinking of hijacking the install recovery script
Sent by breaking the sound barrier
Click to expand...
Click to collapse
The Motorola bootstraps are just one .apk file ! We could probably modify the process to fit ours. But these are paid for apps on the market so we would need permission, or even better help from the developer. For testing to see if it even works I don't think it would matter, if it doesn't work or is not the fix then we move on to something else. But if it works, I don't think we can just post the fix without the developer's permission on how he wants to handle it.
Let me see what I can find out
Alright that will be great. Thanks romified.
Sent by breaking the sound barrier
FYI, I know there is a free version of the Droid 2 bootstrapper floating around somewhere (I think the developer made it available on xda). I'll see if I can find the link.
ylexot said:
FYI, I know there is a free version of the Droid 2 bootstrapper floating around somewhere (I think the developer made it available on xda). I'll see if I can find the link.
Click to expand...
Click to collapse
Yes, I have the APK and have it decompiled...just not with me. I will dig into this afternoon and see what I can determine. If I can reach Kousch (the developer) he may be interested in helping do this and making it available since the NT is fairly popular. Then we could have help with a recovery as well.
Thanks for your help though ! If you find the link that is fine, it may help others who can look into this as well.
Found the link, but I guess it's not from Kousch:
http://www.mediafire.com/?fxvlw4wl2jade0o
It's in one of the Droid X stickies over at AndroidForums.
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