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
Related
inFiniSense​
Alright, our first thread got closed just before I released this zip, so I made a new one.
This time, right off the bat, we have a flashable zip
Anyway, this is Work In Progress. Don't expect it to be done and perfect.
Ok, enough, here is..... inFiniSense!
This is a project porting the Flyer's sense (2.1/3.0) to the Nook Color, CM7 only.
We have figured out this:
We need a custom ramdisk to have custom apps. This zip flashes that ramdisk.
We need to push the apks to the Nook (No.... we need to eat them!) This zip does that. Pushes, not eats.
The apps need frameworks. So this pushes those too. (what else would we do?)
And lastly, the apps FC cause they are looking for a 3G radio. The fix.... none.
Still, flash this zip. If the apks show up, then good. As soon as we fix the FC, you will get the zip.
Also, we have found a Flyer RUU. If anyone could help us extracting the RUU (mac) into a BROWSABLE FOLDER, not a zip. Then we could be done. We are trying, but if the Nook people try too it could get done faster.
The zip isn't out yet (gimme a day. Promise. Hails to god)
Instructions to do what the zip does:
1: download the zip in the downloads section. Flash it. And reboot.
2: Make sure the zip is on the computer. Unzip it.
3: do these commands while in that folder:
Code:
adb push app/ /system/app
Then:
Code:
adb push permissions/ /system/etc/
Again:
Code:
adb push fakeserverxml/ /system/etc/
Almost done:
Code:
adb push framework/ /system/framework/
Then reboot. Hopefully, the apps will show up. They will FC.
Then do this:
Code:
adb logcat
Then launch an HTC app. post it on pastebin or somewhere. Then give me a link. This is for debugging purposes.
Hint: If every time you hit the home button you get an FC, try this:
Code:
adb shell pm disable com.htc.android.htcsetupwizard
Then launcher an HTC app. post it on pastebin or somewhere. Then give me a link. This is for debugging purposes.
Downloads:
http://www.mediafire.com/?9dp20anyjukl7mi - inFiniSense 0.1
-The working zip is almost out. Instructions to manually do this above.-
Credits:
911sniper for the Flyer dump.
xda community for all the help.
If I remember anything else, I'll tell you.
Why create a whole new post when you still have nothing? They closed your old post cause you had nothing and now you have a new one with just as much crap. What did you post? Is anything working on it? You are not explaining anything other then the fact it's still the same old crap. A non working rom is not something to post on a message board.
Anyone feel like trying this? I want to see how badly this bricks your nook color
I can't wait to examine their "zip"... install it? Ha! No f'n way.
Alright. Don't trust my zip. I flashed it. It worked.
And this isn't crap. And we have a ZIP!
Plus, if anyone could help us decompiling system.img from an RUU on Mac would really speed this ip.
do u have pics to prove that it works
Umm... Do you want one?
yeah that would shut people up
Alright. They'll be up in a sec.
Why it wont show anything like the last time. He stated nothing works right now and his uploads are completely not functional
Sent from my NookColor using XDA Premium App
Yes it will. To prove that the apps are on there. And would anybody post their logcat...?
Update: Screenies tommorow cause I have bed now.
Swyped from my 1.3 GHz Nook Color CM7.
ikingblack said:
Update: Screenies tommorow cause I have bed now.
Swyped from my 1.3 GHz Nook Color CM7.
Click to expand...
Click to collapse
OK, this is getting a little bit outta hand... cmon guys. Don't post something till you have something to post that works.
Cmon. It is a WIP. What more do you want? It isn't working. We said that. If you want something working RIGHT NOW, then move on. I'll give an update when it works.
And if you really want it to work, then we need any help decompiling that image as I said a million (3) times.
ikingblack said:
Update: Screenies tommorow cause I have bed now.
Swyped from my 1.3 GHz Nook Color CM7.
Click to expand...
Click to collapse
This isn't an excuse.
This thread should have the screenshot(s) from the start.
ikingblack said:
Update: Screenies tommorow cause I have bed now.
Swyped from my 1.3 GHz Nook Color CM7.
Click to expand...
Click to collapse
dude, reopening this tread was a really bad idea. folks get banned for such shenanigans. it'd probably be in your best interest to shut this down, sit back and, if you're serious about all this, learn from all the wonderful devs in this forum. otherwise a Mods going to shut it down, again, and i doubt they'll be so nice the second time around.
Probably not the wisest thing opening a thread after its been closed.
Redundancy..
Thread closed.
@OP, check your pm's.
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.
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
Update 1-21-12
Ok, 1KDS ran into a small, well maybe not small, issue. The way the whole process works would require a large amount of RAM for the process to run properly. It's in the order of 6+ gigs because the scripts set up and run the operation in RAM. Since most people don't have that much RAM the project is on hold until a solution presents itself. I would like to thank 1KDS for looking into this. If anyone has ideas, feel free to post up.
Previous Info:
Ok, guys here's the deal. The dev is aware of what I'm asking and is looking into possibly doing this for us. Remember these simple requests:
1) Don't ask for ETA's. Enough said.
2) If a question is asked that needs your answers/input, please give it.
3) If he is successful, and I have to stress "IF', he will need testers. Please do, I know I definitely will.
And Finally
4) If you can, donate/support, he's doing this for YOU!
Previous Post:
Ok Here's an update. I pm'd the creator over at DXF and he has said it's pretty involved. He has said:
" It's pretty involved, it may be easier to make one myself. If you can link me the SBF file, instructions to get into the bootloader or wherever you flash from, instructions to factory reset afterward, and what root method is used for the MoPho I can work on one."
So I'm going to provide the info. My question to my fellow MoPho users is "Would you be willing to support and/or donate to him for his work on this?" If he's going to be nice enough to do this we should be nice enough to support him for his efforts. I'll update this as I find more info.
Mike
Original Post:
Have a question, how would one go about creating an automated Linux bootable CD with all the scripts and files to make it easier to SBF a MoPho?
I came from the Droid X and there was a file I downloaded that was in a word - awesome. Insert CD, boot from it, plug in phone, choose option 1, and viola!!! In a few minutes your device was flashed back to stock, no fuss no mess.
I'm a MoPho-er
I wish I could help, but IDK how to do that bub, try making a post in the Droid X Forums, ask for a dev to remake the files to boot on a CD and use this SBF file ---- use this link to download it.
See if that helps, someone may be able to make that CD.
Just thought I'd ask. It's been a few years since I dabbled with linux, Red-Hat was my last venture (10-12 years ago). I'll look at how the cd and the scripts are set up. I can probably figure it out.
I'm a MoPho-er
Let me know if you or someone can get it to work, I'd be very interested.
I think I can get it to work, just have to get the scripts right. Gonna take a fews days. I'm gonna post over at DXF and ask the person who creates them for some input.
I'm a MoPho-er
I'm linking this thread here as it has all the tools and info needed (hopefully) to create a bootable SBF CD.
http://forum.xda-developers.com/showthread.php?t=1393519
I'm a MoPho-er
Alright guys, I'll be working on a new image for the MoPho (I like that name!)
One question, anyone use the ZergRush root method on the MoPho? I have a nice script for that already as well as the Droid 3 method.
1KDS to the rescue!!!!!!!!
Thanks, your work is awesome!!!!!!
I'm a MoPho-er
I used Shabby's one click
I'm a MoPho-er
I looked at Shabby's script, looks pretty much like the Droid 3 method, I can use his script though, there may be a piece I'm not seeing that affects the MoPho. Does it work on the newest SBF/firmware?
I used it to root mine. Took it out of the box and it updated to the latest as soon as I activated it. I rooted about three days later and had success on the first try.
Edit: I don't know about the latest SBF, but (uneducated guess here) I would imagine it should.
I'm a MoPho-er
Alright guys, been busy but I'm ready to start on this new image, couple questions...
There was an SBF file posted on page 1, is that one preferred? I see there is a newer one out there.
Can someone post some clear instructions on getting into the bootloader or RSD mode and instructions for stock recovery to factory reset?
Is there a preferred bootstrap/clockwork? If one is preferred and offered free from the dev I can add a script to install it for you after rooting.
I hope I can give good info here, no one else is stepping up and I'm not fully "up to speed" on my MoPho yet. There's much I haven't tried because I'm "RSD skiddish". When I had my Droid X RSD and I just wouldn't "get along", so I'm not familiar with it. Hence the reason I loved the bootable CD.
For SBF files I think 198_6 is the latest official release. From what I understand 198_7 is out, but it's a leaked package as Sprint never released it.
As for CWM, there is one available, a thread is devoted to it. I think the version is 5.. dot something and it was made specifically for the Photon. It requires the bootloader to be unlocked as well, I believe. Thread here:
http://forum.xda-developers.com/showthread.php?t=1218417
For all the other steps there is a thread by qbking77 that has videos instructing how to root, flash, unlock, install CWM, etc. here:
http://forum.xda-developers.com/showthread.php?t=1250697
Hope this helps.
I'm a MoPho-er
Keep me posted. Can someone PM me the link to this thread when this is done, for some reason, I'm not getting updates on this thread...
Sent from my Motorola Photon 4G (MoPho) on Sprint, the Now Network using XDA Premium.
I had a couple bad downloads of the SBF file, I've got a good one now and unzipped it, the file (uncompressed) is 2.44GB! SliTaz (the Linux distro I use for these images) boots into RAM and my machine simply doesn't have enough RAM to unzip the file and stay stable, if I had more RAM I could make the iso but very few people would be able to use it as they would need 6+ gigs of RAM to run it. For now I'm putting this project on hold until I think of something else or a smaller SBF file is released. Sorry guys.
Ouch!!!!
Bummer 1KDS
Thanks for looking into it, though. I was curious why one didn't exist yet. I guess that would be a good reason why. I guess I'm just gonna have to break down and make RSD and me get along so I can do some modding to my MoPho.
I'm a MoPho-er
Question. Would a "virtual" environment work or is something like that just way to involved to work?
Edit:
Don't know if "virtual" is the right thought or not. I may have been thinking "RAM Disk" setup.
I'm a MoPho-er
Yeah, I use VirtualBox to build the images, my laptop has 4 gigs of RAM and I allocate around 2.5GB to the virtual machine so the machine stays stable and I can't even unzip it within that amount of memory. Like I said, even if I can build the image only a few people would be able to use it since it is so massive.
I am not sure if someone else has posted this already. But I couldn't find one, so here you go. (Please let me know if I'm mistaken)
I made two small edits to the boot.img of the stock (leaked) ICS rom in order to satisfy my needs:
1. ability to run init.d scripts,
2. start adb in root.
They are very simple and anyone with a little knowledge can do it himself, but it still is convenient to have someone else do it, isn't it? I, for one, searched the forum in vein.
Here's a short explanation of what it is, and how to utilize the features.
1. init.d :
You can place your own shell scripts in /etc/init.d (you have to create the directory yourself, of course) and run them at boot time. If you prefer the CM style userinit.d, you could create a script like:
Code:
#!/system/bin/sh
# call userinit.sh and/or userinit.d/* scripts if present in /data/local
if [ -e /data/local/userinit.sh ];
then
log -p i -t
userinit "Executing /data/local/userinit.sh";
logwrapper
/system/bin/sh /data/local/userinit.sh;
setprop
fi;
if [ -d /data/local/userinit.d ];
then
logwrapper busybox
run-parts /data/local/userinit.d;
fi;
and place it in init.d (credit: CM team). After that, you can place additional scripts without remounting system partition. Just don't forget to chmod appropriately.
A word of caution: Don't go wild and install all those tweaks found in other forums without checking to see their contents. I found that most of them to be either irrelevant or even harmful to the Amaze. Remeber, we've got one of the best phones on the market and wouldn't want to ruin it by running tweaks designed for our 'lessor' siblings!
2. adb root :
I was getting tired of the inability to adb push files to user restricted directories. Also, I use Droid Explorer a lot, but was tired of its inability to obtain root even though my phone is rooted. So I basically changed the default.prop and everything is fine now.
Added benefit is that 'adb remount' works now.
Well, that's it. Too simple, but until someone comes up with a nice kernel with these mods built in, we got to live with what's available.
DISCLAIMER : Should I even include a disclaimer? Why not? This is just a stock boot.img with minor modifications to its ramdisk portion, and it shouldn't harm your phone. If it doesn't work, simply reflash the stock boot.img found in the stock/leaked ICS roms. However, I don't want anyone to brick his phone, so don't flash this unless you know what you are doing. Also, I've seen some people bricking their phones merely by trying to flash innocent files like this one. Hard to believe, but anything can happen, so I will not be responsible if you brick your phone.
INSTRUCTIONS :
0. be sure you got the ICS build 4.0.3 with the stock kernel. rooted and have installed busybox (for init.d support only).
1. download the attached boot.img.
2. place the file where adb/fastboot can find it.
3. flash it using 'fastboot flash boot boot_new.img.
4. reboot.
5. try 'adb shell' and see if you get # prompt.
6. add some scripts in /etc/init.d and reboot and see if it runs.
It runs on my Amaze running the newer leaked ICS rom (unlocked bootloader, rooted, and busybox from the market). If you have any other settings, it probably won't do any good.
That's it, guys. Hope you have some fun with it (like I did).
Just flashed your modified boot.img so far everything works as described. Going to attempt my backlight script now. Just reflashed the stock RUU as certain Roms were giving me WiFi issues. Thanks
Is this why adb remount never worked?? I asked a few people and they acted like I was crazy.. I KNEW there had to be a reason it wasn't working.. I guess my only question is why was it no one thought to do this since the ICS release except you? LOL.
Edit: And I am out of thanks, this is my mental note to come back and hit thanks when I get some to give again!
Edit2: As advertised it works flawlessly, as advertised. It will be awesome to be able to push files to my phone and all the other things I couldn't do before! A simple tweak, as you said, still appreciated!
seems like were getting some more people around here that actually contribute to the amaze forums. thanks guys...carry on
Thank you very much
Now to find some scripts to run, lol.
Thank you all for the kind words! As I said in the OP, I was curious at first about the usefulness of my post. I truly believe that, if HTC had given us more power to mod this phone, this forum would have been 10 time more active with all sorts of useful stuff. Come on HTC, you give us the best phone (even better than the One series!), and why do you want to cripple us?
Double0EK said:
Just flashed your modified boot.img so far everything works as described. Going to attempt my backlight script now. Just reflashed the stock RUU as certain Roms were giving me WiFi issues. Thanks
Click to expand...
Click to collapse
As I didn't test the boot.img with any roms around, I don't know what went wrong with your wifi. That's why I only promised it would work with the NEWER stock ICS rom. Is it possible that you flashed the boot.img to a custom rom that is based on the OLDER leak?
Additionally, if the rom dev has made his/her own mods to the boot.img, it would not be compatible with the stock boot.img like mine. I didn't add, remove or move any files.
Silentbtdeadly said:
Is this why adb remount never worked?? I asked a few people and they acted like I was crazy.. I KNEW there had to be a reason it wasn't working.. I guess my only question is why was it no one thought to do this since the ICS release except you? LOL.
Edit: And I am out of thanks, this is my mental note to come back and hit thanks when I get some to give again!
Edit2: As advertised it works flawlessly, as advertised. It will be awesome to be able to push files to my phone and all the other things I couldn't do before! A simple tweak, as you said, still appreciated!
Click to expand...
Click to collapse
Hehe, yeah it is because of some security settings that phone manufacturers chose to enable in order to minimize customer support costs, I guess. Instead, they should give us all the power (and funding, too) so that we can support each other at XDA!
mrmako777 said:
seems like were getting some more people around here that actually contribute to the amaze forums. thanks guys...carry on
Click to expand...
Click to collapse
bilek06 said:
Thank you very much
Click to expand...
Click to collapse
I've used more than two dozen smart phones in the past, including ancient pda's and even iPhones (ouch!), and I think the Amaze has the best (mix of) hardware. I, too, wish there were more devs here, and wonder why some great devs around didn't see the potential in it. Well, HTC isn't doing something right...
Dark Nightmare said:
Now to find some scripts to run, lol.
Click to expand...
Click to collapse
Hard to find anything useful for the (already mighty) Amaze, isn't it?
Things I would add for myself are like:
- house keeping: delete cache, move/copy important files from internal to external sdcard, etc.
- renice phone and input method a bit. How about acore? Probably not...
- zipalign, maybe, if you're fanatic about it.
- save logs and erase oldest ones. Gosh, what am I saying? We've got so much storage space. Oh, well. If we save the logs in external sdcard, we can view them even when the phone doesn't turn on...
Hehe, I think I should search.
I never flashed your boot.img on custom roms only on the stock. I have better WiFi with stock.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
ringochan said:
Hard to find anything useful for the (already mighty) Amaze, isn't it?
Things I would add for myself are like:
- house keeping: delete cache, move/copy important files from internal to external sdcard, etc.
- renice phone and input method a bit. How about acore? Probably not...
- zipalign, maybe, if you're fanatic about it.
- save logs and erase oldest ones. Gosh, what am I saying? We've got so much storage space. Oh, well. If we save the logs in external sdcard, we can view them even when the phone doesn't turn on...
Hehe, I think I should search.
Click to expand...
Click to collapse
Lol searching, was thinking about the v6 supercharger script, still reading into it though.
I use Cache Cleaner NG to clean. Set it on Auto with new method 2 times a day.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Double0EK said:
I never flashed your boot.img on custom roms only on the stock. I have better WiFi with stock.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Click to expand...
Click to collapse
I must have misread your original post. My bad. But then, I have no idea about your wifi problem with the modified boot.img. I didn't touch anything other than 2 things that I mentioned. And my wifi is working just fine. It's spooky.
Dark Nightmare said:
Lol searching, was thinking about the v6 supercharger script, still reading into it though.
Click to expand...
Click to collapse
LOLOLOL! That guy is something! I mean the guy who created the v6 script. Yes, I think his concept is right on. I may borrow some of his tweaks like app grouping and oom/minfree. I've done similar adjustments when I was still using my G1/Dream, but with Amaze with de-bloated ICS, I am already getting (almost, if not) everything he is promising we can achieve with his script.
The only lag I have is when some background services are busy. But I don't really want to make them low priority (yet).
What do you think you like to achieve using v6? I may be able to help because I myself want to experiment some.
Double0EK said:
I use Cache Cleaner NG to clean. Set it on Auto with new method 2 times a day.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Click to expand...
Click to collapse
Hehe, you know that some script junkies won't approve of ANY apps to take over what he can do with scripts, right? I've seem many. No, I've worked with many! They refused to use GUI text editors, LOL!
ringochan said:
LOLOLOL! That guy is something! I mean the guy who created the v6 script. Yes, I think his concept is right on. I may borrow some of his tweaks like app grouping and oom/minfree. I've done similar adjustments when I was still using my G1/Dream, but with Amaze with de-bloated ICS, I am already getting (almost, if not) everything he is promising we can achieve with his script.
The only lag I have is when some background services are busy. But I don't really want to make them low priority (yet).
What do you think you like to achieve using v6? I may be able to help because I myself want to experiment some.
Click to expand...
Click to collapse
Hey, if you want to try out something cool, check this out.. http://android.mimic.ca/ it patches the services.jar file to change the OOM priority, evidently in a way more effective than the supercharger script can do it. I was going to try to include it in the latest update for my rom till I decided I wanted to work on other things.. the guy who made supercharger script helped design the patch for the file though Just thought you may be interested.
Silentbtdeadly said:
Hey, if you want to try out something cool, check this out.. http://android.mimic.ca/ it patches the services.jar file to change the OOM priority, evidently in a way more effective than the supercharger script can do it. I was going to try to include it in the latest update for my rom till I decided I wanted to work on other things.. the guy who made supercharger script helped design the patch for the file though Just thought you may be interested.
Click to expand...
Click to collapse
erm... it CAN'T be more effective than supercharging... because it IS SuperCharging
Well, 50% of it. The other 50% comes from the script when on ICS.
Why do you think that website is integrated into the latest V6 Scripts?
That needs to be done in addition to the V6 script when using ICS roms to get 100%.
Of course, non ICS roms get 100% supercharged with the script itself since there's no need to patch services.jar
zeppelinrox said:
erm... it CAN'T be more effective than supercharging... because it IS SuperCharging
Well, 50% of it. The other 50% comes from the script when on ICS.
Why do you think that website is integrated into the latest V6 Scripts?
That needs to be done in addition to the V6 script when using ICS roms to get 100%.
Of course, non ICS roms get 100% supercharged with the script itself since there's no need to patch services.jar
Click to expand...
Click to collapse
LOL. Did you search yourself? HAHA. Yes, we are talking about how awesome your scripts are..
I would be using them myself but I can't figure out a setting that really makes it awesome like it did with my old vibrant!
Edit: And thanks for the explanation, that makes more sense than whatever post that lead me to your patch.
what is a modified boot image?
what is the different between the modifed boot image and the android we can download from the developer google site/?