I did this exact procedure and everything is working fine with my phone. No issues at all. I AM NOT RESPONSIBLE FOR ANYTHING YOU CHOOSE TO DO WITH YOUR PHONE.
**Make sure adb and java are both installed on your system
1. Download and install xUltimate
2. Run Main.exe
3. Choose option 1 and wait
4. Choose option 2 and wait
5. Choose option 6 and wait
6. Choose option 3 and wait
7. Choose option 4 and wait
8. Once everything has been deodexed and the script did not come up all red with a major error then you are good. You will know the error if you see it. If you get that major error then DO NOT PROCEED.
9. Copy done_app and done_frame to your internal sdcard.
10.
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
You might get an error with the 2nd mount, and if you do just ignore and type reboot. You're device will take longer to boot the first time but after that it will be quicker. And all around will be quicker.
There is no point in doing this to your phone right now. There is no recovery or sbf for this phone at the moment.
I would advise people NOT to do this to your phone. There is no real benefit to this on a stock rom while on the phone. Your phone might actually be slower and use more memory.
You should probably post a link back to the original thread instructions as well.
Had no errors except when trying to cp so I rebooted and now stuck @ motorola logo
Rebooted into recovery and tried resetting phone with no luck. Since there is no SBF file available yet I'm assuming the phones toast until it's available? I've had the phone for past 14 days so I doubt exchanging it is going to be easy
hax0red said:
Rebooted into recovery and tried resetting phone with no luck. Since there is no SBF file available yet I'm assuming the phones toast until it's available? I've had the phone for past 14 days so I doubt exchanging it is going to be easy
Click to expand...
Click to collapse
This is exactly why I said NOT to do this.
nitroglycerine33 said:
This is exactly why I said NOT to do this.
Click to expand...
Click to collapse
Ahh but you had not posted yet when I had the page loaded reading the instructions
This phone just isn't for me, it's too locked down and slow to develop so I'm moving to a Droid Charge. Will send this back for reflash and put on ebay when it returns.
Maybe OP should also put in that there is no SBF available just to add the extra layer then the "Im not responsible bla, bla, bla,....." I love seeing any bit of development for this phone =) but we should make it bold that there is no way to fix any mistakes that occur right now. =)
hax0red said:
Rebooted into recovery and tried resetting phone with no luck. Since there is no SBF file available yet I'm assuming the phones toast until it's available? I've had the phone for past 14 days so I doubt exchanging it is going to be easy
Click to expand...
Click to collapse
If you made a backup you can go into recovery and push the backed up apks and odex back.
Sent from my DROID X2 using XDA Premium App
Interesting.. what app are you using to actually do a decent back up?
I didn't think there was one out that worked.
Thanks.
rook75 said:
Interesting.. what app are you using to actually do a decent back up?
I didn't think there was one out that worked.
Thanks.
Click to expand...
Click to collapse
Indeed, I'm curious also.
Option 6 backups your odex apks and framework
Sent from my DROID X2 using XDA Premium App
I did exactly like you said and only had trouble with the cp command so I rebooted from there rather then doing the remove (rm). I'll try pushing the files back. Can you explain further the command to push them back?
hax0red said:
I did exactly like you said and only had trouble with the cp command so I rebooted from there rather then doing the remove (rm). I'll try pushing the files back. Can you explain further the command to push them back?
Click to expand...
Click to collapse
I am mobile right now and will be home in about 30 and I will add information to the first post when I get home
Sent from my DROID X2 using XDA Premium App
nitroglycerine33 said:
There is no point in doing this to your phone right now. There is no recovery or sbf for this phone at the moment.
I would advise people NOT to do this to your phone. There is no real benefit to this on a stock rom while on the phone. Your phone might actually be slower and use more memory.
You should probably post a link back to the original thread instructions as well.
Click to expand...
Click to collapse
Yaaa I agree with this statement... until the sbf is leaked and bootloader is cracked.. I wouldn't recommend this, there's really no need unless you don't care if you don't have a phone.
Me? I need the darned thing.
Thanks for the info though.
nitroglycerine33 said:
I would advise people NOT to do this to your phone. There is no real benefit to this on a stock rom while on the phone. Your phone might actually be slower and use more memory.
Click to expand...
Click to collapse
Quadrant just pulled 2645
Sent from my DROID X2 using XDA Premium App
taylorhome11 said:
Quadrant just pulled 2645
Sent from my DROID X2 using XDA Premium App
Click to expand...
Click to collapse
I'm guessing thats an improvement for you but mine has hit 2700+ almost everytime since I got it. I've gotten a peak of either 3050 or 3150 after killing all tasks and running quadrant back to back a few times. Would be nice to have a vanilla android 2.3 running on it to really see what the hardware is worth but it seems to be a long way off for the x2.
If this backup works I'm getting a Xoom to play with instead of my phone. Never had any trouble with my HD2 like this even before nandroid was available but there was plenty of development for that phone.
Stock rooted: 2666
I just don't think the benefits outweigh the possible issues that can arise from deodexing at this time.
Taylor: I'm glad you posted this though... how did you find this out? This is awesome for the community once we (as a community) are able to develop on this phone.
Thank you.
hax0red said:
I'm guessing thats an improvement for you but mine has hit 2700+ almost everytime since I got it. I've gotten a peak of either 3050 or 3150 after killing all tasks and running quadrant back to back a few times. Would be nice to have a vanilla android 2.3 running on it to really see what the hardware is worth but it seems to be a long way off for the x2.
If this backup works I'm getting a Xoom to play with instead of my phone. Never had any trouble with my HD2 like this even before nandroid was available but there was plenty of development for that phone.
Click to expand...
Click to collapse
Yeah before this I ran it and got 2100. That was running my phone normal with adw, widgets galore, and everything else. Just opened ATK and killed all then ran again. That was one test before and then just now. Not over and over again.
hax0red said:
I did exactly like you said and only had trouble with the cp command so I rebooted from there rather then doing the remove (rm). I'll try pushing the files back. Can you explain further the command to push them back?
Click to expand...
Click to collapse
are you able to do adb devices while it is in bootloop?
rook75 said:
Stock rooted: 2666
I just don't think the benefits outweigh the possible issues that can arise from deodexing at this time.
Taylor: I'm glad you posted this though... how did you find this out? This is awesome for the community once we (as a community) are able to develop on this phone.
Thank you.
Click to expand...
Click to collapse
He probably took the instructions from here: http://forum.xda-developers.com/showthread.php?t=765270&highlight=manually+deodex
Related
In addition to enabling ADB, SuperNooter will also mount the NC /system partition and copy over Superuser.apk and the su binary. This means you do not need z4root! You should see Superuser in your Extras/App Drawer after booting from the SD card.
Tested with WinImage under Windows and dd under Ubuntu.
http://muffinworld.net/android/nookcolor/supernooter0.1.zip
Thanks for making things even easier!
-CC
Do we just write this to the sdcard like nooter? Install it like nooter? Do we need to wipe anything if we are previously rooted with nooter? Any adb commands needed?
A little more info and/or a tutorial would be really helpful
Novarider said:
Do we just write this to the sdcard like nooter? Install it like nooter? Do we need to wipe anything if we are previously rooted with nooter? Any adb commands needed?
A little more info and/or a tutorial would be really helpful
Click to expand...
Click to collapse
Yup...do exactly what you did with nooker only use this image. Same steps.
Ok but do we need to wipe anything if we already used nooter? I don't want to brick my NC. Who is going to be the first to try it out? I would but I don't know anything about programing so if I messed it up I would be screwed
You can use supernooter on top of an existing nooter to gain Superuser. I would not try it if you already have Superuser (why would anyone?).
Mistar Muffin...you are the man!!!!
Just picked up a NC today and have been prepping for the past couple days...and pleasantly surprised that the steps have diminished with this.
Thank you!!!
How safe is this? The other utility you created seems to be bricking devices. I'm not saying your a bad guy or anything I just don't want to brick my NC
Novarider said:
How safe is this? The other utility you created seems to be bricking devices. I'm not saying your a bad guy or anything I just don't want to brick my NC
Click to expand...
Click to collapse
OK. The other utility Mistar Muffin created does not "brick" devices.
(1) I've yet to see a NC truly bricked. Only people who crap their pants when things don't go perfect.
(2) The script that is having problems is not Mistar Muffin's script. It is one that someone else (rboatright) created for people who run Winblowz and it is only based on Mistar Muffin's script.
Seriously folks... You REALLY need to watch the tone here and at a minimum, get your facts straight.
<under breath>What a bunch of crybabies!</under breath>
I was actually crafting a very similar reply when I saw yours, johnopsec....thanks for setting Novarider straight!
Sent from my Droid using XDA App
johnopsec said:
OK. The other utility Mistar Muffin created does not "brick" devices.
(1) I've yet to see a NC truly bricked. Only people who crap their pants when things don't go perfect.
(2) The script that is having problems is not Mistar Muffin's script. It is one that someone else (rboatright) created for people who run Winblowz and it is only based on Mistar Muffin's script.
Seriously folks... You REALLY need to watch the tone here and at a minimum, get your facts straight.
<under breath>What a bunch of crybabies!</under breath>
Click to expand...
Click to collapse
What tone? I didn't say a single bad thing about the guy. I just dont want to brick my NC since im not a programmer and probably dont have the skill to fix it if something went wrong
Mistar Muffin said:
I was actually crafting a very similar reply when I saw yours, johnopsec....thanks for setting Novarider straight!
Sent from my Droid using XDA App
Click to expand...
Click to collapse
Setting me straight? LOL I simply asked if it is safe. I didn't need setting straight all you had to do was say yes its safe and that you didn't write the program people are having problems with. The other thread you started has people in it that are getting "bricked" devices. I didn't know you didn't write the particular program that was causing this. I was not implying you were doing anything wrong I just don't want a "bricked" device.
Novarider said:
What tone? I didn't say a single bad thing about the guy.
Click to expand...
Click to collapse
Novarider said:
Setting me straight? LOL I simply asked if it is safe. I didn't need setting straight all you had to do was say yes its safe and that you didn't write the program people are having problems with.
Click to expand...
Click to collapse
Novarider, I think that it's just the frustration of people coming on the forum and making posts with big bold red letters that say "YOU BRICKED MY NC!!!" and the like... As many others (including myself) have already stated, it's very difficult to brick a NC. I've yet to do it and I've done some VERY off-the-wall stuff with mine. My personal frustration comes from those two things.
So, sorry if you felt wrongly persecuted by my post. It wasn't directed only at you but at others who have screamed, yelled and lamented about one thing or another "bricking" their NC.
Friends?
Fair enough.
I have a question about this Utility. If I install this will I be able to gain access to the data folder so I can drop some apks into it with root explorer? I would like to be able to use a different keyboard and I was reading I need to be able to rename a keyboard and drop it there for it to work.
I had used adb to install superuser but it didn't do anything once installed so I deleted it
Novarider said:
How safe is this? The other utility you created seems to be bricking devices. I'm not saying your a bad guy or anything I just don't want to brick my NC
Click to expand...
Click to collapse
What are talking about "bricking" devices? Have yet to see anyone claim to have "bricked" a Nookcolor...
That being said, don't think it's possible to brick one with current set of tools..
-CC
Novarider said:
Fair enough.
I have a question about this Utility. If I install this will I be able to gain access to the data folder so I can drop some apks into it with root explorer? I would like to be able to use a different keyboard and I was reading I need to be able to rename a keyboard and drop it there for it to work.
I had used adb to install superuser but it didn't do anything once installed so I deleted it
Click to expand...
Click to collapse
This should do it since the script installs Superuser and Root Explorer can perform the functions mentioned (you may need to hit the button on the top of the program for R/W). As with any mod - proceed with caution or find a step by step to guide you.
norkoastal said:
This should do it since the script installs Superuser and Root Explorer can perform the functions mentioned (you may need to hit the button on the top of the program for R/W). As with any mod - proceed with caution or find a step by step to guide you.
Click to expand...
Click to collapse
I can follow the root guide on nookdevs site and just replace the program with this one right? I have root explorer now but it doesnt allow access to data since it can't be granted root access
Novarider said:
I can follow the root guide on nookdevs site and just replace the program with this one right? I have root explorer now but it doesnt allow access to data since it can't be granted root access
Click to expand...
Click to collapse
Yep. That will do it.
I got the droid-x multi-touch keyboard working a few days ago but that was several resets ago as well. Things didn't go exactly perfect for me and there were several reboots where I didn't have a keyboard at all. I can't remember the exact steps I took but, I eventually side-loaded the droid-x keyboard and it worked. I'll tinker more tonight on that. It's beer-thirty now though!
johnopsec said:
Yep. That will do it.
I got the droid-x multi-touch keyboard working a few days ago but that was several resets ago as well. Things didn't go exactly perfect for me and there were several reboots where I didn't have a keyboard at all. I can't remember the exact steps I took but, I eventually side-loaded the droid-x keyboard and it worked. I'll tinker more tonight on that. It's beer-thirty now though!
Click to expand...
Click to collapse
If you figure out an easy way to install the keyboard without having to rename files in system or anything like that please let me know. I hate the stock keyboard on the NC
Step-by-Step Needed
Does the script install Root Explorer or do we still have to use ADB to install apps? Is it possible to put APK's on an SD card and install them?
docfreed said:
Does the script install Root Explorer or do we still have to use ADB to install apps? Is it possible to put APK's on an SD card and install them?
Click to expand...
Click to collapse
It would be great if this activated it because I can't install apks from the sd card now
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
I am at a loss, i am at a point where my phone is no longer bound by the laws of logic.
I was running Passion 13.1 ICS
two days ago for some reason i woke up and my phone was asking for a password to decrypt the phone, i though this was weird being that i didnt encrypt the phone.
so i setup ODIN and flashed back to Eugene's Froyo that doesn't brick pre rooted w/re-partition checked.
it passes and reboots after reboot i get
Code:
"E:Cant mount /dev/block/mmcblkop1 (or /dev/block/mmcblk0)
(no such file or directory)
but it will reboot into android
so i booted into android setup adb and copied over the fs tools (Parted, e2fsck, mke2fs, resize2fs tune2fs, and sdparted)
i found that in /dev/block/ the partition files were missing completely so i created them using
Code:
mknod /dev/block/mmcblk0 b 179 0
mknod /dev/block/mmcblk0p1 b 179 1
mknod /dev/block/mmcblk0p2 b 179 2
i can see them there but when i try to partition them using
Code:
parted /dev/block/mmcblk0 mkfs ext2
it returns
Code:
Error: Error opening /dev/block/mmcblk0: No such device or address
so i tried a shot in the dark i tried to write zero's to it
Code:
dd if=/dev/zero of=/dev/block/mmcblk0
it returns
Code:
/dev/block/mmcblk0: cannot open for write: No such device or address
so i rebooted my phone, when it came back up i opened an adb shell and to my surprise the fs tools and the files i created in /dev/block were gone it was like it factory reset it self on reboot.
were i am at now is hardware failure unless the collective minds here can see something that i missed?
i really really REALLY want to save her she has been an awesome phone.
any help would be appreciated
Dude that sucks. You are I think the 3rd or 4th person to have this happen to. I do also believe that most of whom this happened to (at least in our forum) were running Passion (different variants though). In the Cappy threads, it was CM9 or Doc's. Seems it is totally random when it happens, but I am seriously considering going back to something else unless I get another phone.
Might want to check here for a workable solution.
Sorry for your loss.
Instead of the froyo build, you should try 2.1 jfd odin package
Woodrube said:
Dude that sucks. You are I think the 3rd or 4th person to have this happen to. I do also believe that most of whom this happened to (at least in our forum) were running Passion (different variants though). In the Cappy threads, it was CM9 or Doc's. Seems it is totally random when it happens, but I am seriously considering going back to something else unless I get another phone.
Might want to check here for a workable solution.
Sorry for your loss.
Click to expand...
Click to collapse
I was thinking about doing this, but wouldn't it make my phone incredibly slow because of the sd latency?
Dougfresh said:
Instead of the froyo build, you should try 2.1 jfd odin package
Click to expand...
Click to collapse
i tried looking for this but i cant find it do you have a link or a copy of the files?
I'm sure it will slow down but it should boot up and you can load another ROM on there. You do lose your entire internal since it is essentially swapped out for the external. Can't hurt to try with a higher class card maybe.
It seems this is happening to everyone running ICS Passion.
Ya but on the Cappy threads it is happening to people on CM9 and Doc's too.
So I am wondering if anyone on AOKP builds are getting these. I posted in the other two threads about this (the one that you were helping that guy yesterday with and the other one) to see what ROMs/kernels they were running, JIC.
Might be a problem with the port of the AOSP code since it is essentially from NS and GNex, both Sammy products though. Anyone in your NS fora reporting this problem?
Nope, nobody. And I just flashed from 2.3.6 to 4.0.4 2 days ago
I flashed GBBOOT-T959UVJFD in an effort to fix my problem, but its just stuck in a boot loop now. is there a chance that the actual physical memory is damaged?
Chances are your internal is completely locked up and without the encryption "key" you won't be able to use it. Since you know ADB, you still might be able to pull some stuff off it and mount to your PC.
Looks to be that you may need to repartition your external in the thread I posted above.
What Bootloader were you on before this all started?
The file I sent you had GB bootloaders included. So to get into recovery Vol- and Power. To get into download Vol+ and Power.
Woodrube said:
Chances are your internal is completely locked up and without the encryption "key" you won't be able to use it. Since you know ADB, you still might be able to pull some stuff off it and mount to your PC.
Looks to be that you may need to repartition your external in the thread I posted above.
What Bootloader were you on before this all started?
The file I sent you had GB bootloaders included. So to get into recovery Vol- and Power. To get into download Vol+ and Power.
Click to expand...
Click to collapse
at this point i don't even care about recovering the internal partition i would like to just format it and start over clean.
It had a GB boot loader on it.
This is what is confusing me, in my mind if a partition is locked and i forget the key or in this case it encrypts itself shouldn't i be able to just fdisk or dd the partition back to cleanliness and format it?
When I installed some of the ICS roms (Cant remember which ones, Too many out now) I remember at the very beginning of the post flash setup screens that I needed to Agree to Googles update rules.
I have read that The galaxy nexus and the Nexus S is getting 4.0.? upgrades re-pushed to their phones as the First update in December had a major battery drain bug in it and was stopped.
I have also read that some members reported that They got a "Welcome to your new Nexus....." e-mails.
Could this be caused by an update being pushed to the phone and sense it is a vibrant and not a nexus it is causing these problems??
Big Dog KMc said:
When I installed some of the ICS roms (Cant remember which ones, Too many out now) I remember at the very beginning of the post flash setup screens that I needed to Agree to Googles update rules.
I have read that The galaxy nexus and the Nexus S is getting 4.0.? upgrades re-pushed to their phones as the First update in December had a major battery drain bug in it and was stopped.
I have also read that some members reported that They got a "Welcome to your new Nexus....." e-mails.
Could this be caused by an update being pushed to the phone and sense it is a vibrant and not a nexus it is causing these problems??
Click to expand...
Click to collapse
I thought the Nexus had ICS already, so i don't think that was what happened. plus i would think it would prompt the user to apply the update or restart the device.
at this point after reading this thread, i think its hardware failure in my case. otherwise why would it clear everything after a reboot?
TheGioDoodlesII said:
Flash the original stock rom , wipe cache and do a factory reset before and after flashing
Hope i helped :beer:
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
I tried that sans the beer LOL i think i am going to need something stronger.
Anythoughts on the SGS 2? HERE
or the NEXUS HERE
i am rooted and unlocked and ran a rom well in twrp i accidentally wipe everything internal now i have to way to get zips back to flash them my backup and all is gone and i have zips on ext card but twrp wont mount it please help
I pretty much just need a way to get my zips back to internal storage
Sent from my SCH-I605 using xda app-developers app
trinitystudio said:
i am rooted and unlocked and ran a rom well in twrp i accidentally wipe everything internal now i have to way to get zips back to flash them my backup and all is gone and i have zips on ext card but twrp wont mount it please help
Click to expand...
Click to collapse
while in recovery, you can use ADB to transfer files to prime from PC via data cable. look for ADB PUSH here on forums
qery said:
while in recovery, you can use ADB to transfer files to prime from PC via data cable. look for ADB PUSH here on forums
Click to expand...
Click to collapse
thanks ill give it a try and get back with you
ok i found and did what it says it sees my prime but im getting this error now failed to write data 'protocal fault <no status>' *3%
now this
i am runnung this command - adb push pac_tf201_4.3.Build-1_20131003.zip /sdcard/ ..all i get is a protocol failure not sure what that means but i need help bad wiped internal and stuck in twrp recovery
trinitystudio said:
i am runnung this command - adb push pac_tf201_4.3.Build-1_20131003.zip /sdcard/ ..all i get is a protocol failure not sure what that means but i need help bad wiped internal and stuck in twrp recovery
Click to expand...
Click to collapse
You need to make sure sure you have all the Android files installed on your PC which I am sure you do. Also, you need to specify where the pac_tf201 build is located. This is what I did to push the version onto my TF201 in Recovery:
adb push c:/pac_tf201_4.3.Build-1_20131003.zip /sdcard/
I did the same with gapps but I made sure that both zip files (rom and gapps) were directly on my C drive and not anywhere else. Let me know if you need anymore help as I just barely did this a few days ago. Took me hours to get it but I have learned quite a bit from it. :good:
Edit: Make sure your directory is pointed to your sdk platform-tools folder as well in CMD.
alias4ever said:
You need to make sure sure you have all the Android files installed on your PC which I am sure you do. Also, you need to specify where the pac_tf201 build is located. This is what I did to push the version onto my TF201 in Recovery:
adb push c:/pac_tf201_4.3.Build-1_20131003.zip /sdcard/
I did the same with gapps but I made sure that both zip files (rom and gapps) were directly on my C drive and not anywhere else. Let me know if you need anymore help as I just barely did this a few days ago. Took me hours to get it but I have learned quite a bit from it. :good:
Edit: Make sure your directory is pointed to your sdk platform-tools folder as well in CMD.
Click to expand...
Click to collapse
i have done that all but putting it on the c:\ drive ....yes im pointed to that folder ill try c and get back to you thanks
edit: try c drive thing still a no go still getting protocol failure
Hardbricked!!!!!!!!!!!!!!
Well im hardbricked now asus wants $324 to fix so NOT!!!!!! Guess its time to go shopping lol
trinitystudio said:
Well im hardbricked now asus wants $324 to fix so NOT!!!!!! Guess its time to go shopping lol
Click to expand...
Click to collapse
Can you boot into fast boot at all? Or are you stuck at the Asus screen?
---------- Post added at 07:40 AM ---------- Previous post was at 07:39 AM ----------
alias4ever said:
Can you boot into fast boot at all? Or are you stuck at the Asus screen?
Click to expand...
Click to collapse
What would you plan on doing or what does anyone do with a hardbricked Prime as I am curious? Sorry to hear it.
It happens I have done roms for years from droid one to note2 never had a issue till now it was my own mistake so... I guess nothing to do but trash it prob going today to get Samsung note 8 or 10.1
Sent from my SCH-I605 using xda app-developers app
Do you by any chance have Asus sync running on your pc? It seems that this can interfere with adb.
Try killing all asus related programs on your pc through task manager and then try adb push again.
Sent from my SO-04E using xda app-developers app
This is what I'm curious about too. If there were photos on this SD card before you put it in the device, they will remain intact after a security wipe.
This is unclear to me based on the OP: You got the Bold as a graduation gift and would like to start using it i assume. (I also got this bold a couple days ago after my HTC One S died, bringing me to Blackberry after years of faithful service on Android. The 9900 is a great phone)
When you tried to use the phone, you were prompted to input your BBID credentials, which subsequently failed repeatedly. The phone has since been security wiped due to too many failed attempts. Upon opening the phone, the microSD that you had in there is gone.