Related
HI people. First of XDA Forum and Dev as you guy's are doing a great job.
Secondly i have this Motorola Milestone GSM version. I am stuck on Android 2.1, as every one how fast Motorola release Android updates for their smartphones. I have gone through lot of Rooting guides but i haven't tried one yet.
As there are lot of Rooting guides and ROM for Motorola milestone on XDA as well, i am kind confuse how to do rooting and how to use a ultimate ROM on Milestone.
If you guy's can look at my Moto version as given below and can suggest me some step by step guide and Some Good ROMS as well i will be very thankful to you guys'
I know there are lot of other users who have asked same question but i want it kind simple and crisp.
Model Number
Milestone
Firmware Version
2.1-update1
Firmware Configuration Versio n
GAS_EMEA_USASHLS00RTINT_P016
Baseband Version
3GSMEPU91A_U_91.07.56I
Kernel Version
2.6.29-omap1
Build Number
SHOLS_U2_02.36.0
Click to expand...
Click to collapse
Most one-click-rooters work fine with the Milestone and it doesn't get any easier then running an app .
That's how I did my at least.
I have used universal root, but that doesn't allow APP2SD and using custom ROMS. So i want complete rooting so that i can load custom roms.
gaggid said:
I have used universal root, but that doesn't allow APP2SD and using custom ROMS. So i want complete rooting so that i can load custom roms.
Click to expand...
Click to collapse
Yes it does...
The problem is that:
-for APP2SD you must have ext2 partition which you probably didnt create and for Custom ROMS you have to load the vulnerable recovery...which you probably didnt do...as well
Just my supposing...Corect me if I'm wrong!
First, ( I think) you have to flash vulnerable recovery, then root. There is also a beta 2.2.1 beta sbf available. after achieving root, you can google GOT TEAM ANDROID and click the first link which should lead to their blog - http://www.google.ca/url?sa=t&sourc...BQ82GR7pNmLJSfPpg&sig2=Jd4iM6Nov5eYhJa2yrZLGg and there should be further instructions there. Good luck ( remember I think these are true, not 100% sure)
mohitrocks said:
First, ( I think) you have to flash vulnerable recovery, then root. There is also a beta 2.2.1 beta sbf available. after achieving root, you can google GOT TEAM ANDROID and click the first link which should lead to their blog - and there should be further instructions there. Good luck ( remember I think these are true, not 100% sure)
Click to expand...
Click to collapse
Can you guide me through on how to do
Flash Vulnerable Reovery.
How to root Milestone
What is SBF and how to use it.
What GOT TEAM ANDROID and why i need them?
If your milestone is anything like mine (I use the milestone available from telus, in canada), then your service provider may have added an un-root and return-to-factory-bootloader check on every boot.
in which case, you would need to install the OpenRecovery backup tool onto your sd card (it's an update.zip file + OpenRecovery directory), then flash a vulnerable bootloader using spf. reboot the phone (as is necessary when doing this flash), and as the system is coming up, start up into recovery (by pressing+holding the camera button, waiting for the yellow triangle w/"!", then pressing vol+ and the camera button), then execute update.zip
drop to terminal, and depending on your model, the .sh file that's un-rooting your phone may be in a different location, and simply rename the file, delete it, or make it non-executable.
Good luck!
Mystik said:
If your milestone is anything like mine (I use the milestone available from telus, in canada), then your service provider may have added an un-root and return-to-factory-bootloader check on every boot.
drop to terminal, and depending on your model, the .sh file that's un-rooting your phone may be in a different location, and simply rename the file, delete it, or make it non-executable.
!
Click to expand...
Click to collapse
I just bought the telus milestone a few days ago and am looking to bypass the update.zip when I go into recovery by permanently replacing the stock recovery with a custom recovery, would disabling this .sh file aid me in this respect?
Where could I find it?
I think i found complete guide for doing this.
Hope it will work.
Which ROM is best for Milestone ?
I am not talking about jazzy ROMs, i want a ROM with all cool features + stable functionality
i always have a hard time rooting Milestones :/
Still not able to get any strong good references on Hacking Milestone.
I know people hate these threads, but I have done as much research as I could before posting, and just want to confirm if my understanding is right...
I have a Canadian (Bell) XT860 -- don't worry, it's fine.
We now have options to restore this phone from a bricked state by flashing (using RSDlite?) either a Brazillian 2.3.5 image, the ME863 image, or a third that was mentioned but I could never find.
My understanding of this as far as development goes is that we don't have a safestrap that works yet, which prevents truly custom android f/w from being made for our phones... but as we do have an option for recovering from a bricked state, people can be more adventurous without worrying nearly as much.
Am I missing or wrong on anything here?
Yes, RSDLite is the program you would use to flash a stock SBF to your XT860.
There is the Chinese ME863 rom, and most recently the Brazilian XT860 rom. What is this 3rd one you heard of... where is it from, which carrier?
Safestrap didn't seem to work for XT860 (I think) or ME863 rom users (this one I'm sure of, as I tried it myself), but I recall when I was on my stock Bell XT860 rom, Bootstrap worked (problem was, there weren't any ROMS to play with - and I believe there still aren't any roms yet.) Hopefully this Brasil stock rom will help move things forward.
Until we get "SBF" that can bring us back to original Bell firmware, we can't really get truly "adventurous", since there is no way to bring phone back to factory state if you have to send it for service. Let's hope such recovery will be leaked/found for us soon and we can really get adventurous.
Accophox said:
My understanding of this as far as development goes is that we don't have a safestrap that works yet, which prevents truly custom android f/w from being made for our phones... but as we do have an option for recovering from a bricked state, people can be more adventurous without worrying nearly as much.
Am I missing or wrong on anything here?
Click to expand...
Click to collapse
I've been talking to Hashcode on and off on IRC for the past few weeks and we've been messing around with my bell xt860 when he's had the time. Unfortunately with his ICS port, patching safestrap (Hashcode mentioned just last night that he believes he's traced down the problem with safestrap on the xt860) etc he's extremely busy. He's mentioned a few times that he's working on a project or two for the xt860 that should get us moving along (ie patching safestrap I think), hopefully it's enough to know that devs(Hashcode) are still looking into the issues we have on the xt860.
With that being said, I have an idea or two I'm gonna try out here. I'll post results when I'm done. There are also a lot of other bright people who are giving things a shot, a few people are recompiling modules and trying to get cm7 working etc, it's ongoing but no ones had any progress to report yet unfortunately. It is ongoing though
Edit:No love, bricked for the moment. I've tried building and flashing a few roms, some I knew wouldn't work but a few had no reason not too, like a bell xt860 rom but for some reason all end with same results, sitting at the "M", not reaching the boot animation. Some difference between the verizon and our model in terms of boot.
Okay, thanks for the clarification everybody.
So - we're just missing a way to get back to Bell XT860 from Brazil/China XT860, but the workaround seems like it's just a matter of getting recovery to work and flash backups of the original software.
And - it sounds like we're fairly close to a breakthrough in getting bootstrapping enabled, which means that we're hopefully not too far off from a de-blur'd XT860.
Accophox said:
Okay, thanks for the clarification everybody.
So - we're just missing a way to get back to Bell XT860 from Brazil/China XT860, but the workaround seems like it's just a matter of getting recovery to work and flash backups of the original software.
And - it sounds like we're fairly close to a breakthrough in getting bootstrapping enabled, which means that we're hopefully not too far off from a de-blur'd XT860.
Click to expand...
Click to collapse
One of the problems we might run into is not being able to flash back to our bell kernel without an sbf from bell.
..as well as the Radio Firmware. Those can only be restored by SBF
Just to thank willis and endoroid I succesfully installed safestrap and liberty rom
the only thing its that it gives me an error when I switch to spanish language (I'm from mexico) on com.android.settings when selecting applications menu..
And also market closes.
XT860 Liberty ROM rooted and overclocked to 1200
goalando said:
Just to thank willis and endoroid I succesfully installed safestrap and liberty rom
the only thing its that it gives me an error when I switch to spanish language (I'm from mexico) on com.android.settings when selecting applications menu..
And also market closes.
XT860 Liberty ROM rooted and overclocked to 1200
Click to expand...
Click to collapse
I saw.on the liberty thread some other ppl have had market FC issues. Apparently the.solution is to just keep reflashing until it fixes. Although you may.wish to try clearing market data.first to see.if that clears it up
Sent from my XT860 using xda premium
Clearing market data doesn't help, along with force closing.
Happens when you start trying to download an app... then just cyclic FC.
It's just reflashing and praying. (I got it on the second attempt)
Well now im using steeldroid it works perfect
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?
So I've always owned samsung phones...fell in love with amoled and never looked back...and i gotta tell you, my short spurt with the one xl with having to flash kernels and rom separably and unlocking bootloaders and what not man! i really miss the simplicity of being able to root with odin and never having to look back...everything just worked as it should (the biggest inconvenience we had was having to flash an older kernel on the sg2 before flashing anything above gb) but here I am, ready and willing to embrace the atrix's sexy design but limited development...but I need some clarification that simple searches and reading through threads dont seem to explain quite as thoroughly as other devices portals.
1.) I understand the concept of a bootloader and how it needs to be unlocked in order to flash ROM's and kernels and write to specific partitions of the phone, I just want to ensure that this device has an unlockable bootloader with the latest firmware that it ships with
2.) even more important than bootloader unlocking is root...i see references to SBF's and qslite or something...is this similar to odin for samsung? do i use an SBF (perhaps the equivalent of an RUU for htc or .tar for samsung??) to flash firmwares onto the device, and will a modded version provide SU?
3.) no roms! thats unacceptable. if i can obtain root and recovery, trust me when i say that even while i cant build from source, ill put SOMETHING together, even if its only rooted/themed stock. but what are the odds of rom from other devices being ported?
4.) cheesecake. wtf.
which one of these threads should i use for the latest firmware on the atrix to root?
http://forum.xda-developers.com/showthread.php?t=1785401
http://forum.xda-developers.com/showthread.php?t=1940594
which one of these threads should i use for the latest firmware on the atrix to unlock bootloader?
http://forum.xda-developers.com/showthread.php?t=1896526
http://forum.xda-developers.com/showthread.php?t=1985031
does hash's safetrap work for backups on the ahd? i read that flashing is disabled currently, but id still like to backup
gosh so many questions! hope the trolls dont come out on sundays...........................
hapticxchaos said:
So I've always owned samsung phones...fell in love with amoled and never looked back...and i gotta tell you, my short spurt with the one xl with having to flash kernels and rom separably and unlocking bootloaders and what not man! i really miss the simplicity of being able to root with odin and never having to look back...everything just worked as it should (the biggest inconvenience we had was having to flash an older kernel on the sg2 before flashing anything above gb) but here I am, ready and willing to embrace the atrix's sexy design but limited development...but I need some clarification that simple searches and reading through threads dont seem to explain quite as thoroughly as other devices portals.
1.) I understand the concept of a bootloader and how it needs to be unlocked in order to flash ROM's and kernels and write to specific partitions of the phone, I just want to ensure that this device has an unlockable bootloader with the latest firmware that it ships with
2.) even more important than bootloader unlocking is root...i see references to SBF's and qslite or something...is this similar to odin for samsung? do i use an SBF (perhaps the equivalent of an RUU for htc or .tar for samsung??) to flash firmwares onto the device, and will a modded version provide SU?
3.) no roms! thats unacceptable. if i can obtain root and recovery, trust me when i say that even while i cant build from source, ill put SOMETHING together, even if its only rooted/themed stock. but what are the odds of rom from other devices being ported?
4.) cheesecake. wtf.
which one of these threads should i use for the latest firmware on the atrix to root?
http://forum.xda-developers.com/showthread.php?t=1785401
http://forum.xda-developers.com/showthread.php?t=1940594
which one of these threads should i use for the latest firmware on the atrix to unlock bootloader?
http://forum.xda-developers.com/showthread.php?t=1896526
http://forum.xda-developers.com/showthread.php?t=1985031
does hash's safetrap work for backups on the ahd? i read that flashing is disabled currently, but id still like to backup
gosh so many questions! hope the trolls dont come out on sundays...........................
Click to expand...
Click to collapse
Okay, your bootloader (if it is from att) is not getting unlocked. That is the best way to put it because AT&T ruins everything. Firmware flashing, there is a utility out now. It's the best way to get back to stock. Razr HD roms should be portable, we wont know for sure until we have something to test. Cheesecake is worthless now so don't even worry about it. Moto blocked us from accessing their servers. It really seems like you aren't going to like this to be completely honest. You are probably more of a nexus 4 or gs3 guy....
SirHoover2010 said:
Okay, your bootloader (if it is from att) is not getting unlocked. That is the best way to put it because AT&T ruins everything. Firmware flashing, there is a utility out now. It's the best way to get back to stock. Razr HD roms should be portable, we wont know for sure until we have something to test. Cheesecake is worthless now so don't even worry about it. Moto blocked us from accessing their servers. It really seems like you aren't going to like this to be completely honest. You are probably more of a nexus 4 or gs3 guy....
Click to expand...
Click to collapse
sincerely, ill get by with just root so to sum it all up, no bl unlock or proper recovery, but purely just root (which is fine by me ) which i can obtain by using THIS? seems your the one who made that tool kit so your clearly the man to ask i can use your utility to obtain root, and even retain root after the upgrade to the test build of jb?
your so awesome sirhoover
hapticxchaos said:
sincerely, ill get by with just root so to sum it all up, no bl unlock or proper recovery, but purely just root (which is fine by me ) which i can obtain by using THIS? seems your the one who made that tool kit so your clearly the man to ask i can use your utility to obtain root, and even retain root after the upgrade to the test build of jb?
your so awesome sirhoover
Click to expand...
Click to collapse
Yes you can use that utility to obtain root
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.