I have looked and I may have missed it, but I was wanting to know for certain if miui or cm roms can install on stock rooted 2.2.2 frg83 droid 1/og. I have miui on my x and my husband FINALLY let me get my hands on his (my old) droid. I can not find any where that lists the system requirements. I really dont want him to see me have to sbf his phone or anything... that may make him think I killed it. it has cwm, titanium backup and rom manager pro.. any link to a list of roms I can use would be great I am sorry if I over looked this somewhere. It seems the droid 1 has been left in the dust.
Thanks in advance
For droid bionic: custom rom such as Eclipse and Liberty, are they based on the stock moto rom or based on CM7?
wow this is a premature and unneccary thread go to adroid development stickied rom/scripts/hacks etc.. it has a line up if they are 902 based 901 896 etc... click on the link it will probably bring you to rootz wiki and the rom will tell you if it is stock etc.. kinex is stock based eclipse has customized but has parts of blur still in it but is mainly aosp.
search button is your friend
Sorry, if you feel this as unnecessary thread. I did mention the question as newbie question. I did look/search & couldn't find the answer I was looking for. The reason I asked is that whichever custom rom I look, it REQUIRES some specific version from moto original rom such as 902, 901, 893 version to be compatible with that particular rom. That's why I though those custom rom are based on moto rom. I just want to understand why can't we just flash to custom rom like CM7 on bionic. If you can give me a clear answer it will be great.
Thanks in advance.
htceris123 said:
Sorry, if you feel this as unnecessary thread. I did mention the question as newbie question. I did look/search & couldn't find the answer I was looking for. The reason I asked is that whichever custom rom I look, it REQUIRES some specific version from moto original rom such as 902, 901, 893 version to be compatible with that particular rom. That's why I though those custom rom are based on moto rom. I just want to understand why can't we just flash to custom rom like CM7 on bionic. If you can give me a clear answer it will be great.
Thanks in advance.
Click to expand...
Click to collapse
The reason that you can't flash CM7 over top of stock is this:
Think of CM7 as an "update", since we are on a locked bootloader.
Now, we can't change the kernel, which is the core of the Android OS.
So, with CM7 we can't have everything that CM7 has to offer.
So devs port the CM7 code so it will work with our kernel.
This means that whatever kernel version the dev uses to write CM7 must be installed before you flash CM7. Otherwise you have a ROM with a kernel that is not compatible with it (and that is not good). It would be the same as flashing a ROM meant for an HTC phone to a Motorola phone like ours. It just wouldn't work.
Thanks, Priddyma, for explaining .....
So, basically, custom roms for bionic such as Eclipse & Liberty are built based on particular moto locked kernel, right? Is it also the case with new bionic roms with ICS features, are they built around the .902 kernel with ICS features?
Another question, when we do OTA official updates, for instant update from .893 to .902, the official updates (from Motorola) are capable of flashing to different kernel? In other words, is it possible to flash kernel (If you are Motorola dev & have the unlock code)?
What I want to know is that in the future, if Motorola is nice enough & could release the unlock code so that we can flash bootloader/kernel to whatever we want.
It's already been stated by verizon that it's them locking the bootloader, and not moto.
Sent from my DROID BIONIC using xda premium
Can i flash a stock GB rom using ROm Manager? I can't find my USB cable so i wanna do it through my phone (through recovery)
any links? thanks guys!
SS2006 said:
Can i flash a stock GB rom using ROm Manager? I can't find my USB cable so i wanna do it through my phone (through recovery)
any links? thanks guys!
Click to expand...
Click to collapse
Use your phone to download it and flash it do not use rom manager at all like today I used my phone to download cm9 and the gapps as well it tuck me 30 mints to 1 h but I got it downloaded the app called download all files get it then download the rom you need using your phone it self when you go to flash that rom it will be on your phones internal SD card and just to be safe I'm saying that what ever you do to your phone I'm not buying you a new one so I'm not responsible of what my or may not happen to your phone if all on you man
Sent from my XT862 using XDA
I see you're in ON, so I assume you're using an XT860?
Willis111 posted a CWM version of the stock Bell 2.3.6 (I believe it is rooted) - He posted it here: http://forum.xda-developers.com/showthread.php?t=1465153&highlight=bell+2+3+6
I think the download link is hosted by rapidshare so hopefully your phone will be able to download straight to the sdcard... good luck!
leersp yes I've done that before but I dont want CM9, i want stock GB, or any 100% functional GB
LazioDroid, thanks so much, I wish I had the bell version, mines actually the Verizon version?
Would that link work, or is there a verizion one?
Or CAN SOMEONE BACKUP THEIR ROM USING RECOVERY (SAFESTRAP) AND UPLOAD IT
and i can restore?
Ah... an XT862... I'm not sure if the bell cwm will work for ya.
I recommend a custom rom (Liberty). Or - others have had really good things to say about MavROM4! Both arfe available here in the Droid 3 development forum
Sent from my XT860
IMO, ROM Manager just causes more headaches than it solves and I recommend ditching it for the D3 at least. As for a stock ROM for VZW, there is a 906 debloated, optimized, etc. ROM floating around here. It was built from the leak, which is the same as the OTA.
Here it is...
http://forum.xda-developers.com/showthread.php?t=1554916
SS2006 said:
leersp yes I've done that before but I dont want CM9, i want stock GB, or any 100% functional GB
LazioDroid, thanks so much, I wish I had the bell version, mines actually the Verizon version?
Would that link work, or is there a verizion one?
Click to expand...
Click to collapse
They have the stock gb from here as will
Sent from my XT862 using XDA
I know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel
EDIT: i meant leaks, stupid typo
The kernel is based on GB because of the locked bootloader. At least that's how I am to understand it. In other words I think that the custom ROMs can be improved using the leaked ROMs but they'll still have to remain based on the GB kernel. Unless you update your stock system to ICS that is. I think the biggest thing devs should focus on right now is a way to safely upgrade to ICS where downgrading is possible in order to stay on Verizons official upgrade path.
As it stands, the OTA will look for GB 219 when upgrading so those early adopters won't be able to get future upgrades. Unless devs find a way to downgrade or trick the update that is.
Everything I've said could be wrong however this is how I have come to understand it.
Sent from my DROID4 using XDA
Given that we have the fastboot files can't we just wipe and flash that to downgrade?
Sent from my DROID4 using XDA
azrael293 said:
Given that we have the fastboot files can't we just wipe and flash that to downgrade?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
No, this results in a brick. Fastboot refuses to flash older partitions over new ones.
Sent from my XT894 using xda premium
flamefangahs said:
The kernel is based on GB because of the locked bootloader. At least that's how I am to understand it. In other words I think that the custom ROMs can be improved using the leaked ROMs but they'll still have to remain based on the GB kernel. Unless you update your stock system to ICS that is. I think the biggest thing devs should focus on right now is a way to safely upgrade to ICS where downgrading is possible in order to stay on Verizons official upgrade path.
Click to expand...
Click to collapse
This is why you need kexec - you can load the ICS kernel dynamically, without corrupting your GB install.
Sent from my DROID4 using Tapatalk
highlandsun said:
This is why you need kexec - you can load the ICS kernel dynamically, without corrupting your GB install.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Actually, upgrading to ICS leak is probably the way to go. We can now upgrade from leak 200 to 206, giving us the ability to stay on the upgrade path. Since the XDA forums are dead for the Droid 4, I suggest everyone keep up at droidforums.
Here are the instructions for upgrading from leak 200 to 206:
http://www.droidforums.net/forum/droid-4-roms/209619-get-unstuck-ics-leak-200-aka-upgrading-200-206-instructions.html
Also, I believe Hashcode is working on bringing Safestrap 2.0 to the new ICS leak based on the new kernel, and will be working on getting our ROMs on the new kernel as well.
rumgool said:
Since the XDA forums are dead for the Droid 4, I suggest everyone keep up at droidforums.
Click to expand...
Click to collapse
droidforums is about as dead for the Droid 4 as is XDA. I am really surprised how little interest people have in this phone. I guess I am one of the few that still loves physical keyboards. Only drawback on this phone is the non-removable battery. Otherwise it is rock solid. Had the original Tilt, then TP and TP2. Had the G2 on T-mobile, but reception on that phone was not good and T-mobile Network in the US sucks.
GermanGuy said:
droidforums is about as dead for the Droid 4 as is XDA.
Click to expand...
Click to collapse
This is true, I was just mentioning since most of the recent information regarding the ICS leak has been on droidforums so checking it out would fill everyone in on whats going on. Because basically development for the GB kernel is probably going to come to a halt and future development will be based on the new ICS kernel, including the existing AOSP ROMs.
wait, the 206 version keeps you on the upgrade path?
dewhashish said:
wait, the 206 version keeps you on the upgrade path?
Click to expand...
Click to collapse
No, but 206 was supposed to require 219 as 200 did and the official one will and people have found ways around it.
Sent from my XT894 using xda premium
I have Hashcode's stuff running on my kindle fire. We will all be in for a treat once he starts focusing on D4. He's done really really good work on the kindle.
dewhashish said:
I know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel
EDIT: i meant leaks, stupid typo
Click to expand...
Click to collapse
They won't be able to do so. What they will be able to do is make their builds work off/with the new kernel/radios flashed by the leak.
So Hashcode will have two builds.
1) - works on phones running the current stock GB kernel.
2) - works on phones running the leaked ICS kernel.
There is still a locked bootloader so you can't flash unsigned kernels/boot.img. For the leaked "system" files to help you need the ICS kernel. The only way to get the ICS kernel is to flash the leak.
So the leaks are great news for people wanting an AOKP or CM9 build running fully functional....on their leak installed phones. Not much help for those who do not want to flash the leak.
I'll definitely flash the leak once root has been released for 4.0.4 (in case OTA rootkeeper doesn't work) and hashcode releases safestrap 2.0 for the leak.
I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.
So far it's working great, face unlock and the camera is working perfectly and GSM/WDCMA performance is awesome, I don't seem to have the problem of under-reported GSM signal like in the stock MotoBlur leak.
(Note that I'm in Canada and using Bell Mobility, not in the US on Verizon so I can't say if LTE is functioning properly).
I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
Won't be long before Hashcode puts up an official release, but I definitely recommend trying it out if you're up for it. If Hashcode doesn't mind, I could share a .zip of the build I made if anyone out there is interested.
Sent from my XT894 using xda premium
Rick#2 said:
I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.
Click to expand...
Click to collapse
Do you think you create a guide or go into more detail how you did this? I'm not quite sure what their git is.
Sent from my XT894 using xda premium
Rick#2 said:
...
I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
...
Click to expand...
Click to collapse
This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.
Sent from my Amazon Kindle Fire using Tapatalk 2
Hashcode said:
This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire
Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?
podspi said:
If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire
Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?
Click to expand...
Click to collapse
Right now, I'm treating the front buttons like they are a special portion of the touch screen (basically any touch past 960 pixels down is considered the "button row", and then I divided the width up into 4 spots for button presses: menu, home, back and search respectively. (This is in the recovery itself as well as the splashscreen which triggers off of menu)
If that fails, Ill just use hard keys for D4's Safestrap temporarily.
Sent from my DROID4 using Tapatalk 2
..or maybe the volume buttons (I bet it requires less modification than implementing support for the digitizer)
I just put up an updated Droid4 2.00 Safestrap for use w/ the new MotoICS leaks:
http://forum.xda-developers.com/showthread.php?t=1688610
BE SURE TO MAKE AN INITIAL BACKUP OF NON-SAFE SYSTEM BEFORE YOU DO ANYTHING.
You will use the "System" backup to restore back to stock .206 to update later.
I have the D4 CM9 / AOKP builds for the MotoICS leaks almost ready and I'll post those soon.
Was anyone able to successfully get data running on international roms? Everything seems to work BESIDE data...which is important lol
I've seen 4 or 5 threads just like this and its a great questiom, although none of them have any replies.
Are we able to flash AT&T Roms also or just INTL Roms?
I'm gonna grab the TMO Kernel and start testing this a bit, I just want to clarify so I don't hard brick the radios or some crazy stuff like that.
The international roms need files replaced to get data to work any att/canadian rom will work on our device with only kernel change
allenjthomsen said:
The international roms need files replaced to get data to work any att/canadian rom will work on our device with only kernel change
Click to expand...
Click to collapse
Anybody know which files we neec to change to run International roms on the 910T?