i was thinking since the razr ics update will have a signed kernel and it will be able to pass through the bootloader if we could use the razr ics update(since its like our roms all cross platform due to same processor,resolutions) and mod it a little so there is no 4G or webtop and change the device name to D3/solana then flash it as an update instead of a zip in recovery/fastboot like as if it was an OTA update that we sideload. we may have to return to stock to do this, or use otaroot keeper? i dont know if it will need to be re signed after changing things. but since this is an official kernel and the zip has a path motorola made it may get passed our bootloader if the unlock process is the same for all phones.
also maybe someone with a RAZR can use adb and see the commands during the update process to see if the phone spits out any lines of code when it opens the bootloader to replace the kernel?
I'm guessing it won't work as the kernel is signed only for that device and not the d3. Not to mention hw differences.
Sent from my XT862 using xda premium
the cameras are the same, they both have the same processors just razr is .2 ghz faster and running a little version different, the way they use the camcorder is the same, and the way they run flash player/hardware accelleration is the same. if we can trick the GB kernel to run the roms we have now then tricking the phone to use the razr kernel could be easy given we can get it passed the bootloader securely. once its passed the BL hashcode can get codecs to take a little easier since we will have the ability to run the DEV- ION drivers instead of getting ducati to decode and re code them for the GB kernel.
this may be worth a try instead of everyone saying "oh that wont work," then waiting god knows how long until hash gets the codecs to work, or motorola might just update up in 3-6 months. it might be a sloppy thing but it may work
double post
I doubt it'll work. The keys used to sign the Droid 3's kernel and the Razr's kernel are different. It would be just as hard (and really, afaik, impossible) to get our devices to run the Razr's kernel than it would be for us to get it to run any other kernel we can make/compile.
Sent from my XT862 using XDA
Keep brow beating Motorola, they "promised" unlock, blah, blah, blah
If we don't push though you'll never get anything.
im hoping hashcode gets the codecs working by may/june, if not then ill just go pick up a used D4/razr since they should be 100% on it by then or maybe a gnex off CL for 300 i really want to keep the d3 though.
It may work if we package the kernel into the ICS rom by hash or flash it separately. But who knows how much work it may take for that to happen. Also some DROID 3s may not be able to run that .2ghz faster so we have to tone that back. It maybe be simpler to port over razr ICS codecs
Sent from my DROID3 using XDA
saintlikesniper said:
It may work if we package the kernel into the ICS rom by hash or flash it separately. But who knows how much work it may take for that to happen. Also some DROID 3s may not be able to run that .2ghz faster so we have to tone that back. It maybe be simpler to port over razr ICS codecs
Sent from my DROID3 using XDA
Click to expand...
Click to collapse
This what will likely happen
Sent from my XT862 using xda premium
I could be mistaken here, but it is my understanding that the kernel acts as a sort of intermediate between the phone's hardware and OS. Seeing as how the RAZR lacks a physical keyboard, there could likely be some very pertinent information missing in it's kernel that is needed in order for the D3 keyboard to be usable. If this is the case, we would probably be better off attempting to utilize an ICS leak for the D4.
Sent from my DROID3 using Tapatalk
Full disclosure: I'm not a dev. My eyes glaze over the second someone mentions compiling or code.
That being said, I feel that at this point, maybe these types of off-the-wall ideas might be valuable. Even if the OP wasn't 100% on the right track, maybe that will light a fire in a more capable person's head.
mikedyk43 said:
I could be mistaken here, but it is my understanding that the kernel acts as a sort of intermediate between the phone's hardware and OS. Seeing as how the RAZR lacks a physical keyboard, there could likely be some very pertinent information missing in it's kernel that is needed in order for the D3 keyboard to be usable. If this is the case, we would probably be better off attempting to utilize an ICS leak for the D4.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
see thats the thing, our ICS roms werent programmed to utilize a hard keyboard either (sourced on the Gnex) so we can have that fixed. what im getting at is the razr, bionic, D4 and D3 run the same OMAP 4430 processor with the same efuse so it should be the same key for the bootloader. when we package the signed bootloader with either a modded RAZR rom to remove 4G and webtop and/or rename the phone id then resign it OR package the signed kernel in our ics roms then *flash as a manual update* it may get passed the bootloader. since the EFUSE looks for official firmware, the razr ics rom is signed by moto and the kernel has the efuse keys attatched (for OMAP 4430) so it may let it in. we would need root access in the rom to do changes (freeze/delete webtop) etc. we also need to wait for a reliable flashable zip of the razr rom since the only way to get it is a fatal way(cheesecake). BUT this is the deal, if we do this this will totally take you off the upgrade path if there is even one anymore, so an SBF back to 2.3.4 will need to happen in case of anything.
Tyfighter said:
Full disclosure: I'm not a dev. My eyes glaze over the second someone mentions compiling or code.
That being said, I feel that at this point, maybe these types of off-the-wall ideas might be valuable. Even if the OP wasn't 100% on the right track, maybe that will light a fire in a more capable person's head.
Click to expand...
Click to collapse
hashcode is more than capable of doing this its just a matter of if hes brave enough to try since hes tried everything else and we havent heard anything about codecs in awhile.
A few things
1). Signed. This means you can't edit it, change it, modify it or do anything with it...and it has to be signed for your device. Razr kernel will not be usable, nor will a Droid 4 when it comes out later.
2). Our D3 ICS CM9 rom is not built off the GNex ROM, it's built from source (AOSP) modified by CyanogenMod team and then further modified by Hashcode. Hashcode is modifying it to work with the D3 Gingerbread Kernel and that is why the hardware keyboard works.
3). Unless Motorola releases an ICS kernel/Rom for the D3.....OR Motorola releases an unlocker for the bootloader......the best will see is a modified source built ROM running on the stock Gingerbread kernel.
I'm not going to list someone hacking/cracking the D3 bootloader signing key, etc.... While it's entirely possible.......the Droid 2, Droid X have still not been cracked....and they've been out how long now?
We can run something like Hashcode's CM9 ICS and enjoy it and hope that Hashcode can get as much out of it as possible.......running on top of the Gingerbread kernel.....other than that it's just going to be hoping/waiting for Motorola to do something.
T
saintlikesniper said:
It may work if we package the kernel into the ICS rom by hash or flash it separately. But who knows how much work it may take for that to happen. Also some DROID 3s may not be able to run that .2ghz faster so we have to tone that back. It maybe be simpler to port over razr ICS codecs
Sent from my DROID3 using XDA
Click to expand...
Click to collapse
The problem we run into (i messed with this idea a bit) is that /boot wont allow unsigned code, the file containing the kernel needs to be flashed to /boot and is signed by motorola so it cant be tampered with and is also signed with a product code allowing it to only be flashed on that model. We cant changed the model # in the file without altering the signature so the phone wont accept the flash anyways. As for flashing it along with hashcodes rom, i think thats what theyre trying to do with kexec (this seems to be the most likely way we have to get custom kernels running on any bootloader locked phones). The problem with kexec (it's an app that loads you into an alternate kernel after the first kernel has booted, it's like a handover) is that our kernels have to have kexec support compiled into them right now by motorola for it to work(not sure theyve done this). Really, without a bootloader unlock or kernel upgrade by motorola (meaning ics and a 3.0+ kernel signed for our phones) i think we're stuck with what we're doing atm.
Perhaps we could do something like move the /boot partition to somewhere else but i imagine it's been tried and moving /boot to a partition on internal storage or something probably just causes the phone to not boot at all.
Willis111 said:
T
The problem we run into (i messed with this idea a bit) is that /boot wont allow unsigned code, the file containing the kernel needs to be flashed to /boot and is signed by motorola so it cant be tampered with and is also signed with a product code allowing it to only be flashed on that model. We cant changed the model # in the file without altering the signature so the phone wont accept the flash anyways. As for flashing it along with hashcodes rom, i think thats what theyre trying to do with kexec (this seems to be the most likely way we have to get custom kernels running on any bootloader locked phones). The problem with kexec (it's an app that loads you into an alternate kernel after the first kernel has booted, it's like a handover) is that our kernels have to have kexec support compiled into them right now by motorola for it to work(not sure theyve done this). Really, without a bootloader unlock or kernel upgrade by motorola (meaning ics and a 3.0+ kernel signed for our phones) i think we're stuck with what we're doing atm.
Perhaps we could do something like move the /boot partition to somewhere else but i imagine it's been tried and moving /boot to a partition on internal storage or something probably just causes the phone to not boot at all.
Click to expand...
Click to collapse
i dont understand why we cant completely wipe the phone of the data/rom AND bootloader and create a custom bootloader.
I think that would be eFuse and harder than it sounds entirely. Again may be easier to port razr codecs when it becomes available. Which should be soon according to speculation
Sent from my DROID3 using XDA
Willis111 said:
T
The problem we run into (i messed with this idea a bit) is that /boot wont allow unsigned code, the file containing the kernel needs to be flashed to /boot and is signed by motorola so it cant be tampered with and is also signed with a product code allowing it to only be flashed on that model. We cant changed the model # in the file without altering the signature so the phone wont accept the flash anyways. As for flashing it along with hashcodes rom, i think thats what theyre trying to do with kexec (this seems to be the most likely way we have to get custom kernels running on any bootloader locked phones). The problem with kexec (it's an app that loads you into an alternate kernel after the first kernel has booted, it's like a handover) is that our kernels have to have kexec support compiled into them right now by motorola for it to work(not sure theyve done this). Really, without a bootloader unlock or kernel upgrade by motorola (meaning ics and a 3.0+ kernel signed for our phones) i think we're stuck with what we're doing atm.
Perhaps we could do something like move the /boot partition to somewhere else but i imagine it's been tried and moving /boot to a partition on internal storage or something probably just causes the phone to not boot at all.
Click to expand...
Click to collapse
We actually don't need Motorola to have compiled kexec in (fully, at least. I think there has to be some basic support there, which there might be). As long as we can load kernel modules (which I believe we can) we could create our own and run that. The problem with kexec, though, is that it drops kernel communications with the radio for long enough for the radio to think the phone has shut down or errored or something, and it will shut itself off. So, upon loading into the new kernel, the phone will have no radio, and the only way to reinitialize it is to go through the bootloader process again, which would mean we couldn't have an unsigned kernel. It would be nice if there was a way to communicate to the radio that the kernel wasn't actually shutting off yet or if there was a way to reboot the radio after switching kernels, but sadly there isn't (as far as I know).
I say we all put our computing power together to crack Motorola's private key that they signed the kernel with, [email protected] style.
</semi-sarcasm>
Edit: Okay, actually being productive here... is the radio image signed? Because we could use kexec to load a new kernel, but modify the radio code so that it doesn't assume something horrible has happened when the kernel stops communicating with it.
ssinisterss said:
i dont understand why we cant completely wipe the phone of the data/rom AND bootloader and create a custom bootloader.
Click to expand...
Click to collapse
Because even a fully wiped phone will only accept files that are signed by motorola.
I believe the only way we can see a custom kernel is using the method some guy (i forgot who) has been able to kinda do. He's on the Razrs forums and he was able to get a custom kernel running on his phone. Unfortuantly this kernel can only use 1 out of the 2 cores, so it is not done yet. From what I remember he gets the phone to boot with the stock kernel and then has his kernel installed over it. I think the boot up process takes a little bit longer but it is a small price to pay for customization.
Flashing the Razrs ICS is futile. The only thing we can do is maybe kang some prop settings and apks. That's about it. We'd have a better chance with the Bionic, but it's still unlikley it will help anything.
Related
Anyone who has or know if tun.ko has been ported to work on the LG 2x yet?. Its because I need the tun.ko drivers to activate a VPN connection and the 4 standards provided off the shelf is not supported .
The only way I can connect is via an app from market, but said app requires the presence of tunn.ko to work.
MoDaCo has a kernel with tun included.
I would prefer it not being a custom kernel etc . Im not really that much into flashing new roms and such until at least I have seen Gingerbread on the 2x.
So at present I am hoping for a solutuon that only requires me to push it to the phone and not flash a new rom.
MeX_DK said:
I would prefer it not being a custom kernel etc . Im not really that much into flashing new roms and such until at least I have seen Gingerbread on the 2x.
So at present I am hoping for a solutuon that only requires me to push it to the phone and not flash a new rom.
Click to expand...
Click to collapse
Then either get it from the kernel image or ask Paul nicely to help you out.
Does this paul have name on this board.
You must be new here.
It's paulobrien. His 2X forum is at http://2x.modaco.com.
I just joined a few months ago, so no im not venerable yet . But does this paulk frequent these boards as well?.
The reason I ask is that I find it a bit excessive to register at yet another board for the mere reason of needing to contact him and enquire about that tun.ko file
Alright, let me put it this way; You wouldn't regret taking a minute to sign up for modaco.com, because his custom ROM's and kitchens tend to be for members there only. The MCR (MoDaCo Custom ROM) kitchens are famous for their easy way of choosing what you want to include and not in the ROM.
He's frequently here and on Twitter as paulobrien.
Yea I sent him a PM already on here . But for all the goodness of custom roms I have never really ventured into that realm and tried one. I meant to do it when I had my Desire and started to realise I might get Gingerbread for it. But then HTC says they would give it gingerbread so I stalled even more
And now I have the LG as well, and for what it is worth I am generally content in a a large extend with having a stock rom, albeit with some of the provided apps removed and a few tweeks and addons here and there, without going all the way.
But time will tell with the LG
It's definitely a good phone, and hopefully it will get even better. Let's cross our fingers for Android 2.3 or 2.4(?) soon.
In the meantime I can tell you that flashing custom ROM's is very easy. It's close to impossible to screw up the O2X because we have nvflash working and can overwrite all partitions easily. Nvflash is Nvidia's own tool for writing to the ROM. Paul has a guide for how to flash the latest stock ROM in the dev section here. Just beware that using nvflash will in most cases format (delete) everything including your external sdcard, but you can of course remove it first.
Better yet is to install the custom (ClockWorkMod) recovery, backup and flash a ROM from there, because then you don't have to reinstall apps+data. All data+sdcards will be intact, but system settings and any manually added apps in /system/app will be lost though.
If you decide to give it a go we are all friendly and helpful people, just do a little bit of homework yourself.
I had rooted and security offed my Desire which I have have now passed on .
My LG 2x is also equally rooted, I got CWM on it and flashed radio drivers . So I have already did some manner of mocking about with it . But is NVflash a "required" item on our phones. Because I considered installing it, but didn't thnk I really had a need for it at first.
But sadly rooting and doing such to your phone also means OTA software downloads are not possible as the phone is not detected as being the original phone anymore :/
MeX_DK said:
But is NVflash a "required" item on our phones. Because I considered installing it, but didn't thnk I really had a need for it at first.
Click to expand...
Click to collapse
NVFlash poses as a "last resort" if you brick your phone beyond the ability to make an adb connection. As far as I understand it, it hooks in far earlier and thus enables you to flash system partitions.
If you don't brick your phone, you probably won't need nvflash, but its a safety net to revert the phone to a stock ROM if you screw up.
Still no dice, I sent Paul a PM some days ago and not a word back :/
So is there anyone else that might be able to help, since I will assume I can't just "reuse" the version I got for my Desire
I was wondering if anyone would be able to code a bootloader like piece of software
in theory if we could make something that can start at the same level as revoery then we could have that select wich rom to start. I think then we could have mutiple roms on one device.
i was thinking it could be very good right now as devs and testers are using GB roms. THey could have a nice stable themed rom and then a dev rom and be able to switch between the to.
Is this possible or a pipedream(and why wont it work)
kedster said:
Is this possible or a pipedream(and why wont it work)
Click to expand...
Click to collapse
Bootloaders are closed source, and no one wants to re-write them right now.
Also, Q/A.
actually there was a script to dual boot the nexus S rom on our captivate a while back but it required data as system..
After reading around, I am trying to come to a conclusion about CM7 and Moto devices.
From what I read, to get CM7, you need 2nd-init to bypass the bootloader, but also read battery life suffers.
Now, if you have a unlocked bootloader, does this mean you don't need 2nd-init?
Like how does it work on HTC phones, or Samsung phones.
Just trying to understand.
Thank you
On unlocked boot loaders, the developer had the capability of changing kernels without bricking the phone. Because of this they are able to custom write kernels with compatibility for Cm7, because we don't have this luxury we have to use one kernel, the one given to us, work out any optimizations. Cm7 with 2nd init allows us to run compatibility code on top of that kernel by hi jacking the boot process
Sent from my DROID BIONIC using Tapatalk
mikeymop said:
On unlocked boot loaders, the developer had the capability of changing kernels without bricking the phone. Because of this they are able to custom write kernels with compatibility for Cm7, because we don't have this luxury we have to use one kernel, the one given to us, work out any optimizations. Cm7 with 2nd init allows us to run compatibility code on top of that kernel by hi jacking the boot process
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Okay, so if the bionic boot loader did get unlocked, we could install custom kernals? But otherwise we can't? And with unlocked boot loader, CM7 is more painless with better results?
soo my current phone right now is a Samsung stratosphere, well i have been having some big problems with it and well verizon said since i'm a long time and good customer (never ever been late on my bill) they said he will upgrade me to the droid 4 for 50$ without renewing my contract.
i am kinda new to the whole motorola stuff as i have allways had samsung android phones (i had a Motorola Backflip but i sold it 2 months later to get the Samsung captivate so i never got the chance to root it or anything) i noticed these phones have locked bootloaders and is just all pretty much on lock down compared to Samsung phones is that true?
does the droid 4 have root? and does it have custom roms? can you edit Boot animations on this phone with only root? does this phone officially have ICS?
i will be getting my Droid 4 tomorrow morning in the mail and very excited i have not done anything cool with phones since i had my Epic 4G as the stratosphere had no one working on it and only had root and that was that
First off, welcome to the D4! It really is a wonderful piece of hardware. I think you’ll enjoy it.
Now, to answer some of your questions.
1. Yes, the D4 has a locked bootloader. What does this mean? It means we are stuck with the kernel that Moto gives us. It does make it a bit more difficult of the devs but other than that, it’s really not THAT big of a deal. Of course I might not be saying that if I was the one developing ROMs for this thing.
2. The D4 does have root. The Droid 4 Utility makes it a piece of cake. Look for the “Droid 4 Utility Updated” thread in the dev section.
3. The phone does not officially have ICS. Not yet anyways. We have had 4 or 5 ICS leaks from Moto that run really really well so it can’t be far off. I am currently running the .213 ICS leak myself and it has been flawless for me.
4. We do have a few custom ROMs. There a couple of GB based ROMs that run off the stock GB kernel. Those are Eclipse and Arctic. I ran Eclipse for quite a while. Very nice. There is also CM9, AOKP, and Gummy ICS ROMs that run off the stock GB kernel. Your mileage may vary with these as they are a bit buggy from running off an older kernel. We now also have CM9 and AOKP ROMs based off the ICS kernel from the Moto ICS leaks. These are really early builds but I have been running the CM9 build for a few days now and it is surprisingly stable for how new it is.
5. I am not sure about changing boot animations. It seems I have seen somewhere, someone saying that using ROM Toolbox to change the boot animation sent them into a bootloop and they had to restore a backup. Not sure on that though. Haven’t tried it myself.
ok well from the looks of it i wanna go straight to ICS!
how would i go about doing that from Stock non root? i saw the one click root for GB and looks easy but how about ICS with root?
if i do flash the ICS leak and when the official ICS comes out will it brink my phone if i upgrade from ICS leak to ICS official?
it just seems for right now i wanna just have ICS with root and play with custom roms later when the official ICS comes out.
Since you will be going straight from stock the process will be really easy. Just download the latest ICS leak .zip file (currently .213) and stick it on your external sd card. Boot into stock recovery (hold power + volume up + volume down and select recovery), when you get to the little android guy in a box, hit volume up + volume down, then select the option to install from sd card, select the .zip file, let it do its thing and like magic, you’re on the latest Moto ICS leak. Then use the Droid 4 Utility update by jsnweitzel to root.
If you flash the ICS leak you will have to jump though a couple of hoops to get back on the OTA when it finally comes out. The OTA won’t brick your phone, it just won’t install. But there is a thoroughly tested way of jumping from leak to leak that should work to jump to the OTA and be back on the official upgrade path. This functionality is also built into jsnweitzel’s tool.
ok i went to http://www.droidforums.net/forum/dr...leak-kernel-crc-droid-4-build-6-16-213-a.html to download the .213 ICS update but it list 3 things
CRC file,Kernel,Leak
do i need to download the kernel or CRC file as well? or just the Leak file
icebear8 said:
ok i went to http://www.droidforums.net/forum/dr...leak-kernel-crc-droid-4-build-6-16-213-a.html to download the .213 ICS update but it list 3 things
CRC file,Kernel,Leak
which one do i download and put into the SD card and flash?
Click to expand...
Click to collapse
All you will need is the leak as long as you have an external sd card. The kernel is only needed for people jumping from one leak to another and I believe the crc file is for those who do not have a external sd card installed.
ok i see i got that stuff downloaded
now about the Droid 4 utility
i downloaded the tool, but under the number 2 part it says to download the GB 219 fastboot files do i need those as well? i tried downloading them but it seems both links are down
also in that droid 4 utility walkthrough it says to download the kernel for
"2. Get the matching Kernel 6.16.213 (boot.img) here: https://docs.google.com/open?id=0Byw...1J0VFBCY1NBM2M
Unzip this folder and copy the boot.img to the "files" folder of the tool. It must be named "ICSFIX" for the tool to work."
also one more thing how does motorola phones do Backups? is there a CWM to backup my phone in case of a brick?
You will need the GB .219 fastboot files eventually to jump from the leak to the OTA (unless .213 ends up BEING the OTA). But you don’t need them right now since you will already be on unmodified stock GB.
You also do not need the kernel since you are on stock GB. You only need the kernel if you are going from one leak to another.
ok sounds good,
also one more thing how does motorola phones do Backups? is there a CWM to backup my phone in case of a brick?
icebear8 said:
ok sounds good,
also one more thing how does motorola phones do Backups? is there a CWM to backup my phone in case of a brick?
Click to expand...
Click to collapse
Right now we have safestrap recovery. You should find the thread in the dev section. Since you will be on ICS you will want the 2.0 version meant for ICS. You can use this to make a backup as well as to boot into a "safe" system to install ROMs without screwing up you stock "unsafe" system.
i saw the droid razor is getting the ICS update as well, since we have pretty much the same phone are the updates suppose to come out at the same time? are the ICS leaks the same as the Maxx?
Unfortunately no. Moto has stated the D4 will get an ICS update in Q3. With the frequency and quality of the leaks I have to guess that that it will be sooner rather than later but who knows.
Sent from my XT894 using Tapatalk 2
icebear8 said:
ok well from the looks of it i wanna go straight to ICS!
how would i go about doing that from Stock non root? i saw the one click root for GB and looks easy but how about ICS with root?
if i do flash the ICS leak and when the official ICS comes out will it brink my phone if i upgrade from ICS leak to ICS official?
it just seems for right now i wanna just have ICS with root and play with custom roms later when the official ICS comes out.
Click to expand...
Click to collapse
My office just got rid of BB and handed out D4's as replacements and the first thing I did with mine was to install the 213 ICS leak and am NOW happy with the device. Have not rooted it yet, that will happen in the next day or so.
well at first the Rep was not gonna let me have the droid 4 and said that most likely his boss wont give it out because the stratosphere is a cheaper phone (the phones he was gonna give me were the LG lucid,Droid charge,Pantech breakout.
but i told the guy i need a keyboard and that was the only reason why i got the strat for, so the guy said he would try to talk down with his manger and well he comes back and tells me he had good news and his manger said yes to the droid 4 as long as i paid something for it (i said $50) and he said that was fine
but he said he would send me a new backplate along with it but no charger (i got my old one but it is really ****ty and falling apart so i gotta order a OEM from Ebay tonight)
i tried using the search but could not find my question but do we have a list of apps that can be safely debloated from this phone on ICS? i like to have my phone free from Verizons crap along with un needed stuff that just waste battery
^^Also looking for a list of things we can remove to debloat all the [email protected] from verizon (can't even use it anyway since i am in canada!)
First off, unfortunately, most of the bloatware cannot be removed without causing problems. A lot of what moto and VZ builds into these things are interdependent on each other. Plus, the OTA updates look to make sure you still have that crap on your phone before it will update. So, unless you can long press on the app in the app drawer and it gives you an option to uninstall, it's best not to. There are some apps that can safely be uninstalled like, the golf and NFL games. The rest you are better off freezing with a program like Titanium Backup. I haven't seen a list on XDA but there is a good list on DF here: http://www.droidforums.net/forum/droid-4-hacks/198081-bloatware-apps-safe-remove-droid-4-a.html that are safe to freeze. This list was started based on stock GB but most, if not all, should apply to ICS as well. I used it to freeze a bunch of stuff on the .213 ICS leak with no problems.
kwyrt said:
First off, unfortunately, most of the bloatware cannot be removed without causing problems. A lot of what moto and VZ builds into these things are interdependent on each other. Plus, the OTA updates look to make sure you still have that crap on your phone before it will update. So, unless you can long press on the app in the app drawer and it gives you an option to uninstall, it's best not to. There are some apps that can safely be uninstalled like, the golf and NFL games. The rest you are better off freezing with a program like Titanium Backup. I haven't seen a list on XDA but there is a good list on DF here: http://www.droidforums.net/forum/droid-4-hacks/198081-bloatware-apps-safe-remove-droid-4-a.html that are safe to freeze. This list was started based on stock GB but most, if not all, should apply to ICS as well. I used it to freeze a bunch of stuff on the .213 ICS leak with no problems.
Click to expand...
Click to collapse
Keep in mind that you can now "disable" applications natively in ICS. keep in mind that if you updated any of the apps the updates must be uninstalled first. Just go to apps / all apps select the app/bloat you want to disable and select, you guess it, disable.
Never mind i think it was a bad download
question i got my phone charged to 100% my last from goes by 100% to 99,98,97 etc etc but i see on this phone after about 15mins it went from 100% to 90% and then 80 over time does this phone go by 10s?
Over the next week or so I plan on making stock, deodexed roms from our fastboot system.img's. Other than Root, Busybox, init.d support, insecure adb, and being deodexed, they'll be completely stock -- nothing removed, nothing else added -- and are to be used as roms, the base rom for ports, whatever.
If you don't need insecured adb, delete /system/etc/init.d/AdbdInsecured
I include it because its a necessary feature for me.
All the roms* will be uploaded to my Goo.im page for Atrix HD
All the roms are for the locked AT&T Atrix HD running Jellybean 4.1.1.
Do not flash Gapps with the Stock Roms
Currently Done
Mexico Retail 4.1.2
AT&T 4.1.1* (not mine, see below)
To Do
Bell 4.1.2 (Jellybean)
ATT 7.7.1Q-115 (ICS)
Bell 7.7.1Q-115 (ICS)
ATT 7.7.1Q-144 (ICS)
Mods
Currently the only Mod available is the Extended Reboot Menu for stock AT&T DeOdexed, I'll make the same mod for other stock roms as I have the time.
Mexico Retail Info
Jellybean 4.1.2
Moto Blur 98.2.2 (oddly, AT&T JB 4.1.1 is Blur 98.4.20 -- this rom is higher Android Version, Lower Blur Version -- weird)
Very little bloat
WIFI didn't work until I added in the kernel modules from Stock AT&T. If you have errors, see first if it could be module related and replace the offending one.
* STOCK AT&T INFO
The stock AT&T rom is located on the Batakang FTP server and was not done by me. I assume Mattlgroff or SirHoover did that one. Someone let me know so I can give proper credits & thanks. It does not contain InsecuredAdb or init.d support. When I finish up the other stock roms on the list I'll make a Stock AT&T of my own, unless the current one's maker doesn't mind me adding init.d support and InsecuredAdb like the rest of mine on goo.im will have.
To Rom Cooks
For init.d support, I hid the init.d initialize command in /system/etc/init.qcom.bt.sh. Let me know if there's a better place to put that command or a script activated earlier in the init process we can edit.
Feel free to use my stock roms for whatever project you want. Thanks and credits are appreciated but not required.
I'm unsure if the ICS roms will even work with the Jellybean kernel & boot. I'll be finding out later on today.
Credit and Thanks
Gotta give Mattlgroff credit for the InsecuredAdb and reverse engineering Chainfire's
Thank You to whoever uploaded the Stock ATT Deodex on Batakang, I'm using its updater-script, su binary, & superuser.apk. I was lazy on the su part
I'm working on getting ICS to boot with the AT&T Jellybean kernel.
So far I'm able to get it to boot, do a complete gapps setup, but after that, it bootloops within a minute of accessing the homescreen.
Boots after that loop on the animation or will give ~30 seconds of usable display before looping.
Factory resetting allows for completing the initial setup.
If I sit on the Gapps setup page, it'll eventually start looping, but much longer than if I finished and accessed the homescreen.
I'm unable to pull any kind of logcat, ddms, etc since I can't get the PC to recognize it over usb (driver error???)
Any ideas?
I've tried replacing kernel modules with JB versions -- didn't work. By then it was after midnight so I went to sleep. That's where I'm at now. Gonna start testing out JB binaries and libs today.
Since we're able to get a working display, that makes me think that a stock ICS rom for JB users is possible. We just gotta figure out what needs to be backported from Jellybean. Maybe a new init script or an init.d script that'll fix what JB sets that ICS doesn't like.
Can someone running ICS please upload their init scripts? I'd like to compare them with JB's.
RAZRHD 4.1.2 firmware if you're still interested: http://sbf.droid-developers.org/vanquish/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml.zip
As for getting ICS to boot, I think you're spot-on about the init files. Safestrap doesn't mess with / files, but it does create symlinks for /system, etc & execute init files that are placed in /system/etc/rootfs. This might be key to your efforts.
Epinter has a CM10 rom that uses a modified ICS kernel, but it has no problem running on my JB phone with SS (minus the camera). Although I had to repair his inits to fix a boot error & insert two /bin files. Perhaps you could use his rootfs/inits as a guide on getting ICS to work with SS on JB.
My safestrap fix for Epinter: http://forum.xda-developers.com/showthread.php?t=2178123
Epinter's ICS-based CM10: http://d-h.st/ML8
Update: Just found this: http://rootzwiki.com/topic/8794-bionic-safestrap-bootstrap-recovery-12142011/page__st__20
It says that SS moves anything in /system/etc/rootfs to /, so if you can get a hold of the ICS init files, that should be all you need to fix the boot.
SS, while convenient, is a serious pain in the ass as far as the init process goes....I miss Defy's 2nd-Init in that regard. Everything was in /system/bootmenu/*. The downfall with 2nd-Init is you lose and reinstall the bootmenu with every rom install -- Accidentally wipe /system and not install a rom? -- sbf time .
I'll take a look at the RAZR HD 4.1.2 fastboot today or tomorrow. Rainy day, so maybe today. I'm just hoping that the lapdock fix isn't kernel deep.
Thanks for the links, I'm sure they'll be invaluable.
I'm guessing here, but I think ICS's biggest issue is\will be USB -- I'm unable to get anything USB to work -- phone detecting USB or the PC detecting the Phone. Working blind with no logs, no usb, and a looping boot animation really sucks. With any luck, Moto didn't fully remove USB mounting via the kernel, only SW blocks in JB. While only briefly, I know that at least the display works, bluetooth turns on and off, I think audio works (can't remember if it beeped or not with the rocker presses),
Time to search for ICS init scripts then.
Later on tonight I'm going to upload the ICS dumps. They still don't work but I figured the libraries and binaries could be useful with CM10 porting. The Bell will be flashable since it has a working display -- if only until non stop looping .
For some interesting info...there are 2 different sets of ICS camera drivers. The first is 1st AT&T\Bell and the second is the other AT&T. Means ya got two different sets of drivers to test when porting .
/I really need to update my banner below :silly:
UPDATE
They're all uploading now. Should be done in 5-7 hours. My upload speed sucks.
All are flashable, but the ICS ones don't work. Only Tested 144-att and 115-bell.
I'm also uploading 4.1.2 Bell. It's untested but should work.
Obviously, only flash these on a rom slot. I've only used and tested on slot 1.
Skeevy , i really hope you or somebody else makes Paranoid Android available for AHD ( i know it's wishful thinking ).
For me its the only ROM worth flashing with the same android base version for the AHD . Not undermining the developer's efforts , all other ROMs (with same base version 4.1) that i came across here , I can get the same functionality and ui changes from a combination of custom launcher , root apps and some minor fixes here and there . I have not yet flashed a single custom ROM on my AHD , just rooted it and debloated it for the same reason .
I used to own a defy which was officially upgraded till froyo 2.2 only and boy did i flash the **** out of it . But that was only because of worthwhile functionalities in custom ROMs(be it CM 7,CM 10 by quarx, PA by you or MIUI) that couldn't be achieved by mere root apps or custom launchers .
thanks for this rom
AnkurBedi said:
Skeevy , i really hope you or somebody else makes Paranoid Android available for AHD ( i know it's wishful thinking ).
For me its the only ROM worth flashing with the same android base version for the AHD . Not undermining the developer's efforts , all other ROMs (with same base version 4.1) that i came across here , I can get the same functionality and ui changes from a combination of custom launcher , root apps and some minor fixes here and there . I have not yet flashed a single custom ROM on my AHD , just rooted it and debloated it for the same reason .
I used to own a defy which was officially upgraded till froyo 2.2 only and boy did i flash the **** out of it . But that was only because of worthwhile functionalities in custom ROMs(be it CM 7,CM 10 by quarx, PA by you or MIUI) that couldn't be achieved by mere root apps or custom launchers .
Click to expand...
Click to collapse
I'll be straight up with you, I could make PA for us but it wouldn't be the latest version. It would be 2.5.3 just like the Defy -- AOSPA (PA 3.0+) won't be possible until we're able to get AOSP to compile from source (the SourceForge crap). It would be based on Epinter's CM10, have the same bugs as CM10...basically I'd be making PA for another device then porting that over for us . It would probably take me 6-12 hours to do all the source merging, another 2 to compile, and a day to test then upload. There is no ETA cause I haven't started on anything nor is it on my to do list yet. Times are based on how long it took me to do the Defy merging, compiling, testing.
I'm unsure on the 4.1.2 Bell rom, but the 4.1.2 Mex Retail is worth using instead of stock -- less bloat, no entitlement checks.
I partially agree on the other 4.1 custom roms -- yes, you can do it all yourself, but not everyone can. Also, not everything is compatible, so if you don't know what you're doing and flash a bad, lets say audio tweak, and it doesn't work or loops you, you could be screwed simply by lack of knowledge. That's also why I released the one custom thing I've done as a standalone mod.
Rom cooks do a lot behind the scenes -- I've been working on a rom on and off since I've had my AHD. Only mentioned in here, in a PM, and maybe publicly once or twice. I've been testing various audio tweaks, launchers, scripts, mods....I don't want to give 2-3 week eta posts cause life happens, it might not work when I get to the moment of truth, and something always happens to make any specific eta I give wrong . I've been doing tons of testing, looking for something different than the AT&T stock base or RAZR port base(see this thread :silly, tons of apk decompiling (every 4.1.2 Atrix HD apk so far), and have been adding French\Canadian English to the MR base (25 apps in). Other than that, all I know is its gonna be PlayStation Certified (already have PS Store fully working). Can't say more cause I don't know any more than that :cyclops: Point is, other cooks do tons of crap behind the scenes to ensure a good, working environment that you can't get without doing\knowing some ****. If I wasn't trying to do so much I might have had something usable by now -- I've messed with ICS, CM10 porting, SF sources, stock smali mods, my own rom, alternate stock roms.
Luckily, I still have my Defy and Bravo. Quarx is still going strong and pushing out new CM's, kernels, and everything good. One can only hope that we'll have even a quarter of the roms the Defy has. I'm so glad my first Android phone was a Defy clone. I've learned a lot because of it.
Looking forward for your custom rom skeevy :thumbup:
Sent from my MB886 using xda app-developers app
Going to test out the Bell ROM and will report results later tonight or tomorrow. Thanks so much for the upload and the work youve done so far!
I'm trying to boot into the Bell ROM and am currently stuck at a bootloop when the boot image says "Android" not sure what to do to correct this problem, I have the zip file install in ROM Slot 1 with 2GB partition size
Edit: Tried again with 1GB size also just to see if there was any difference, the error im getting has to do with the md5 of the ROM, when i enable both checks it automatically fails, however if i bypass them and continue to flash the ROM it gets stuck in a bootloop as mentioned before
Thanks a lot for your hard work,skeevy. I had a Defy green lense two years ago and sold it a year ago. Luckily,I still can enjoy modding it coz my friend still got it. It's a beast phone with all those mods by you,quarx,epsilon and maniac103. With the lack of official updates and locked bootloader,Defy can do all the impossible things. I've even seen the newest 3.x kernel with CM10.1. You guys have done a great job. Let's hope Atrix HD got the same treatment.
Sent from my MB886 using Tapatalk 2
freshlycutlawn said:
I'm trying to boot into the Bell ROM and am currently stuck at a bootloop when the boot image says "Android" not sure what to do to correct this problem, I have the zip file install in ROM Slot 1 with 2GB partition size
Click to expand...
Click to collapse
Try replacing kernel modules with the stock AT&T ones. After that I'd be guessing and would need to see a logcat if possible. That's for Bell JB, btw. Not sure what to do with any of the ICS roms at the moment.
@huatz84
If we only had Quarx, Epsylon, and Maniac103....man, AHD development would really kick off. Those 3 get **** done. I mean, they only had JB running on a Froyo kernel with Froyo\GB hybrid drivers and only 317mb of /system space to work with.
skeevy420 said:
Try replacing kernel modules with the stock AT&T ones. After that I'd be guessing and would need to see a logcat if possible. That's for Bell JB, btw. Not sure what to do with any of the ICS roms at the moment.
@huatz84
If we only had Quarx, Epsylon, and Maniac103....man, AHD development would really kick off. Those 3 get **** done. I mean, they only had JB running on a Froyo kernel with Froyo\GB hybrid drivers and only 317mb of /system space to work with.
Click to expand...
Click to collapse
I will try that tonight when I get a chance and let you know how it works. The only thing im wondering is that since my device currently with bell is only on 4.0.4 that the kernel with jellybean roms wont work because I dont have the right kernel to go with the JB rom
freshlycutlawn said:
I will try that tonight when I get a chance and let you know how it works. The only thing im wondering is that since my device currently with bell is only on 4.0.4 that the kernel with jellybean roms wont work because I dont have the right kernel to go with the JB rom
Click to expand...
Click to collapse
Did not know that...could also be an init script issue then. Ignore the first suggestion, I assumed you were an AT&T JB user, use the Bell ICS modules instead.
skeevy420 said:
@huatz84
If we only had Quarx, Epsylon, and Maniac103....man, AHD development would really kick off. Those 3 get **** done. I mean, they only had JB running on a Froyo kernel with Froyo\GB hybrid drivers and only 317mb of /system space to work with.
Click to expand...
Click to collapse
Yeah..they are amazing. With the tiny system space,they can build a stable JB rom with Froyo kernel. They've made impossible things.
Btw,I just saw that Moto includes Razr HD and Razr M to their unlocked bootloader program. Hopefully,They add Atrix HD soon.
skeevy420 said:
Did not know that...could also be an init script issue then. Ignore the first suggestion, I assumed you were an AT&T JB user, use the Bell ICS modules instead.
Click to expand...
Click to collapse
I'm going to try to flash the Bell ICS file and see how that goes and if it triggers an OTA update, if theres anything I can do to help with the development of these ROMs please let me know, I have access to a Bell Atrix HD with an unlocked bootloader so id like to do all I can
Edit: Tried the 4.0.4 Bell ROM just now and I'm getting the same error while trying to flash
--Verify md5 for /external_sd/404-115-bell.zip
-- No md5 file found!
If I uncheck the boxes to verify the md5 I can successfully flash the zip but it still gets stuck in the bootloop like the JB ROM
EDIT:
Successfully booted into the ICS ROM since I was on 4.0.4 myself and am getting the prompt to update to 4.1.2 now, it looks like when you upgrade to 4.1.2 the kernel becomes incompatable with the older ROM's and vice versa. It looks like once one is on JB there is no going back. The flash worked without me ticking the boxes which doesn't seem to be the problem, only firmware, hopefully this helps and explains why the ICS ROMS begin to instantly bootloop once you try to boot into them since im assuming youve updated at this point. Since I used a 2GB ROM slot I was getting low memory errors so I'm going to remake the slot with 1GB and am going to reflash and try the update and see if the flash for 4.1.2 directly works and if I can boot back into 4.0.4 again.
huatz84 said:
Yeah..they are amazing. With the tiny system space,they can build a stable JB rom with Froyo kernel. They've made impossible things.
Btw,I just saw that Moto includes Razr HD and Razr M to their unlocked bootloader program. Hopefully,They add Atrix HD soon.
Click to expand...
Click to collapse
Me too. Sucks we have an unlockable bootloader that we can't unlock due to Moto not supporting it. Some HD's are unlockable which is the real teaser to the rest of us.
freshlycutlawn said:
I'm going to try to flash the Bell ICS file and see how that goes and if it triggers an OTA update, if theres anything I can do to help with the development of these ROMs please let me know, I have access to a Bell Atrix HD with an unlocked bootloader so id like to do all I can
Edit: Tried the 4.0.4 Bell ROM just now and I'm getting the same error while trying to flash
--Verify md5 for /external_sd/404-115-bell.zip
-- No md5 file found!
If I uncheck the boxes to verify the md5 I can successfully flash the zip but it still gets stuck in the bootloop like the JB ROM
EDIT:
Successfully booted into the ICS ROM since I was on 4.0.4 myself and am getting the prompt to update to 4.1.2 now, it looks like when you upgrade to 4.1.2 the kernel becomes incompatable with the older ROM's and vice versa. It looks like once one is on JB there is no going back. The flash worked without me ticking the boxes which doesn't seem to be the problem, only firmware, hopefully this helps and explains why the ICS ROMS begin to instantly bootloop once you try to boot into them since im assuming youve updated at this point. Since I used a 2GB ROM slot I was getting low memory errors so I'm going to remake the slot with 1GB and am going to reflash and try the update and see if the flash for 4.1.2 directly works and if I can boot back into 4.0.4 again.
Click to expand...
Click to collapse
Good to know that. Sucks JB doesn't work for you, but at least we're both able to get to the boot animation and loop it -- we could be stuck at the boot logo. With any luck I'm hoping that we can find the right combination of files to replace to get the roms to boot with the wrong kernels. We at least know its possible since JB kernel can have a working ICS rom for about 3 minutes .
Since you have an unlockable bootloader why don't you just flash a jellybean boot.img? Unpack and repack it so its not signed and you shouldn't have any issues. You could probably start using the RAZR HD unlocked bootloader roms and recoveries and never see us again.
Holy crap... I am running ICS on my JB AHD!!! It's been 10 minutes and no boot loops so far
I restored a Safestrap ICS backup, then put some ICS init files in etc/rootfs (I attached my flashable ZIP fix).
Camera doesn't work - same for WIFI but I'm sure it's a simple driver fix.
Also attached are the full ICS init files, in case you want to compare and contrast with JB inits. I omitted qcom inits in my fix.
Well that's awesome. 10 minutes beats what I've been able to do :highfive:
Wifi didn't work with MR either -- I needed AT&T wifi modules (or probably the wifi modules of the stock kernel currently running). -- /system/lib/modules/prima/* & system/lib/modules/config.ko
From what I can tell we have 3 sets of Camera Drivers (2 are ICS drivers, 1 more for JB) -- 115-att & 115-bell are the same\1st one, 144-att is 2nd, & all JB roms are the same\3rd. I'm unsure as to what all libs are necessary for the camera with us other than the obvious /lib/camera*, lib/hw/camera*, and bin/mm-qcamera-daemon. We might need to use the JB camera app as well. Also, the 144-att camera libs have more files than the 115's -- they're similar to the JB ones (1st driver doesn't have /lib/libchromatix_ov8820_hfr_60fps.so, everyone else does).
The biggest difference of the 3 JB roms, from what I can tell, are the kernel modules; libraries and drivers are the same.
I'm being a little optimistic, but hopefully whatever works for ICS on JB kernel will work for CM10 as well; and that we can invert what we're doing to get JB working with the ICS kernel.
I know what I'm doing today.