Database Develop

Phone often freezes with froyo ....keep having to pull battery

What is happening? Pulled battery 5 times already today...what should I do and would pulling battery as often as this affect my phone or battery?
-------------------------------------
Sent via the XDA Tapatalk App

Anyone?
-------------------------------------
Sent via the XDA Tapatalk App

What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.

What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.
Click to expand...
Click to collapse
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App

rensky said:
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.

I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..

Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.
Click to expand...
Click to collapse
I did wipe prior flashing to Paul's zip with radio.
-------------------------------------
Sent via the XDA Tapatalk App

I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App

rensky said:
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3

SurfHost said:
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
Click to expand...
Click to collapse
does it work?

Im having similar issues with my 2.2 installation. I have it installed on my wife's non-rooted N1.
Not just that but the market is not even usable. Even if I clear cache.
Again, her phone is not rooted, I wipped everything from her phone then applied Froyo and its been a nightmare. Her phone isn't even stable enough to use and I cant seem to figure it out.
I need to find a way back to 2.1 without having to root her phone. She is adamant about me not doing that to her phone even though Ive rooted all the phones I've ever used with no issues.

I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.

Ive tried all that on her phone. I just wiped it again completely and re flashed just in case that was the issue. Phone still had all the issues described in this thread.
I wiped the sd card, wiped all previous system files via the stock recovery and re flashed the update zip. You cant get anymore clean than that and its still so unstable the phone its unusable. I have to either hope soft booting works or pull the battery as a last ditch.
Is there any way I could downgrade her phone to 2.1 without rooting? I tried the shipping rom in the sticky above but it seems that isn't totally legit for stock use because the phone doesn't like how its signed.
I guess I could call google/htc tomorrow but who knows where that'll get me. The only bonus iud that her phone is not rooted so she didn't really have her warranty voided.
-------------------------------------
Sent via the XDA Tapatalk App

I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.
Click to expand...
Click to collapse
I was worried if I was the only one with this problem. Phone improved today (3rd day of using) but I didn't do anything to it. Only hanged once when someone called. Hanged on calling in screen and had to pull battery.
Only once compared to 7 times yesterday!
-------------------------------------
Sent via the XDA Tapatalk App

rensky said:
does it work?
Click to expand...
Click to collapse
Yes until now it does. Sometimes the power button is reacting a little late but i havent had to pull the battery yet with the older radio.

You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.

krabman said:
You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.
Click to expand...
Click to collapse
I'll give this a shot when I get home from work. I'll report back on if it works or not. Thanks for the idea.

Interesting, not that I'm complaining, but after a few days of using 2.2 it seems more stable now....? haven't had any freezes today...yet.
Power button response also getting better.
-------------------------------------
Sent via the XDA Tapatalk App

I haven't had any issues for a few days as well. Still wondering if it had to do with the battery level.
-------------------------------------
Sent via the XDA Tapatalk App

SurfHost said:
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Older radios are not 100% compatible.

[Q] Re: Decad3nce's 1.1 ROM

Can't post in the dev forums yet, so I'll post here.
Got Decad3nce's 1.1 update ROM and it installed fine, everything was working. A few minutes later I got a screen that said that there was a problem with authorization and the Nook needs to be reset. It would then reset and roll back to a non-rooted 1.01 version.
I have tried this several times and have had it happen with Decad3nce's first ROM and the v2 ROM. Good thing I have a backup for my nootered 1.01. This one works fine. Anyone have any ideas as to why I am the only one with this problem? Thanks in advance!
I may just have to wait around for an Auto Nooter for 1.1.

sunsurfer42 said:
Can't post in the dev forums yet, so I'll post here.
Got Decad3nce's 1.1 update ROM and it installed fine, everything was working. A few minutes later I got a screen that said that there was a problem with authorization and the Nook needs to be reset. It would then reset and roll back to a non-rooted 1.01 version.
I have tried this several times and have had it happen with Decad3nce's first ROM and the v2 ROM. Good thing I have a backup for my nootered 1.01. This one works fine. Anyone have any ideas as to why I am the only one with this problem? Thanks in advance!
I may just have to wait around for an Auto Nooter for 1.1.
Click to expand...
Click to collapse
Did you reinstall any data, such as using Titanium Backup to restore from a previous install? If so, don't restore System data, ever.

Thank you Decad3nce and dalingrin!
I can't post in the developer thread either but wanted to say thanks to Decad3nce and dalingrin for their excellent contributions.
I used dalingrin's latest 1.1 GHz kernel after applying Decad3nce's v.1.1 "pre-nootered" update and all apps are working with stable operation. Quadrant scores have been averaging between 1100 to 1200.
Thanks to all the other folks in the developer forums who share their experiences. This is a fantastic community.

khaytsus said:
Did you reinstall any data, such as using Titanium Backup to restore from a previous install? If so, don't restore System data, ever.
Click to expand...
Click to collapse
Nope, didn't try and reinstall anything, just applied the 1.1 zip. It happens if I just let my Nook sit or if I start using it. I have TiBu, but just for backing up apps and app data. It's funny how I am the only one with this issue. I might uninstall all my apps and try the update without apps. Then I can reinstall one by one and see if any of them are causing the problem.

I have the same exact issue

samseh said:
I have the same exact issue
Click to expand...
Click to collapse
Sorry to hear this, but glad that I am not alone.

Sorry to hear about your troubles. My upgrade to 1.1.0 from auto-nootered 1.0.1 worked fine.

I had the exact thing happen to me. I had to go back to 1.0.1. I am going to try starting from scratch. I will update my findings after that.

So glad to know that I am not the only one. There is also someone having this problem over on Decad3nce's thread. Thanks in advance to anyone who finds a reason and/or a workaround for this.

My nook was updated Ota to 1.1. Then I don't know how I Reverted to 1.01 afterwhich I applied the pre-nooter to 1.1 againbut only had superuser installed, so I had to install applications directly with the stock browser. Finally installEd titanium backup but still can't use Market or Gmail. No application related to google is allowed to install. This is really weird.

sunsurfer42 said:
Can't post in the dev forums yet, so I'll post here.
Got Decad3nce's 1.1 update ROM and it installed fine, everything was working. A few minutes later I got a screen that said that there was a problem with authorization and the Nook needs to be reset. It would then reset and roll back to a non-rooted 1.01 version.
I have tried this several times and have had it happen with Decad3nce's first ROM and the v2 ROM. Good thing I have a backup for my nootered 1.01. This one works fine. Anyone have any ideas as to why I am the only one with this problem? Thanks in advance!
I may just have to wait around for an Auto Nooter for 1.1.
Click to expand...
Click to collapse
This may be better served in nook color q and a forum.
Sent from my LogicPD Zoom2 using Tapatalk

compuguy1088 said:
This may be better served in nook color q and a forum.
Sent from my LogicPD Zoom2 using Tapatalk
Click to expand...
Click to collapse
There's a NookColor Q and A forums? It would be in the Development forum if I could post there yet. Soon.
Still no luck getting 1.1 to stick.....

Just a quick update... Now everytime I turn on WiFi on my nootered 1.01 it seems to want to update me to 1.1 and breaks my root. Does that just mean that it is trying to push that update? I may need to block OTA updates then. Still trying to get the 1.1 root to work.

Assuming you don't use wifi 'in the wild' you can block 65.204.48.0/24 (65.204.48.0-65.204.48.254) on your router if you have that ability. This seems to block the nooks ability to get updates. This block is in use by B&N for a lot of things.
it will block the wifi's ability to test whether it's connected or not as the internet connectivity test goes to something in this subnet.

[Q] LG/VZW Update (8/4/11) for Revo

Ok, I downloaded the VZW/LG update on 8/4/11, but once downloaded it reboots into recovery.. I have Clockworkmod Recovery installed. I don't know where the downloaded file is to install it. I assume if I had stock recovery that it would have automatically installed. Can anyone help?
After reboot from CWM, the update screen comes up and says Update Failed or Incomplete.
Also just a note, the update isn't Gingerbread, it is bug fixes and a couple system app updates.
http://support.vzw.com/pdf/system_update/revolution.pdf

I downloaded the update... There is an options page where you can choose to defer or deny the update. I clicked deny.
Sent from my VS910 4G using XDA Premium App

I just deferred until 2099.
Sent from my Cubed VS910 4G.

What is the update? It kept resetting my wife's Revolution and waking us up, it hasn't hit my Revolution yet though.
It wouldn't b gingerbread, would it?
Thanks!

Nevermind, I now see the answer in another thread

drt054 said:
Ok, I downloaded the VZW/LG update on 8/4/11, but once downloaded it reboots into recovery.. I have Clockworkmod Recovery installed. I don't know where the downloaded file is to install it. I assume if I had stock recovery that it would have automatically installed. Can anyone help?
After reboot from CWM, the update screen comes up and says Update Failed or Incomplete.
Also just a note, the update isn't Gingerbread, it is bug fixes and a couple system app updates.
http://support.vzw.com/pdf/system_update/revolution.pdf
Click to expand...
Click to collapse
Anyone wondering about the OTA please read this!
If you have CWM installed, you won't be able to take the OTA.
For now, I'd suggest staying away from it until I get a chance to look it over first.
Also, if you're running my decrapified ROM, installing the OTA would bootloop your device since decrapified is deodexed and the OTA would be odexed.
In the next day or so (whenever I get access to the OTA zip file), I'll disassemble it and see what changes it contains (like if it has a new recovery, or new kernel, or changes the board configuration) I'll post back here to let y'all know.
UPDATE
It appears that the update is safe to install for those running the revo stock (not decrapified) ROM.
It makes changes to quite a lot-- new boot.img, new LTE RIL, new CDMA RIL, new LTE baseband ROM, changes to the recovery system to bring it in line with normal Android (still not very 'normal', but normal as in "now contains an installrecovery.sh that android can use"), and a bunch of new ODEX files.
Let me stress this and make it perfectly clear: this update will NOT work if you're running decrapified ROM.
In the next day or so, I'll make an updated decrapified ROM (see? I was waiting for a good reason to make an update ) that will include the OTA in it.
Until then, relax and keep hitting that "ignore" button

Hey, what does the new boot animation look like? The only other thing that interests me, is the keyboard pop up in messenging. I hate that.

markapowell said:
Hey, what does the new boot animation look like? The only other thing that interests me, is the keyboard pop up in messenging. I hate that.
Click to expand...
Click to collapse
It bothers me too! I will look into if the new Mms.apk will work with decrap 1.1, if it does I will put it in my theme page.
Sent from my VS910 4G using XDA Premium App

There are several things that I do not like about the Decrapified ROM
1. The 3 buttons on the bottom (Phone / App Drawer / Browser) sometimes vanish. Only way to fix it is to reboot
2. When you dock the phone into the car mount, the Navigation doesn't do anything. It would be nice to launch your own GPS app or the Google Navigation app. There are other activities that do nothing.
Everything is is great. Love the Google Integration and Love the missing Verizon Crapware on it (VZ Navigator, VZ Music, etc)

If ur using adw go into adw theme settings and reapply your them and the bottom buttons will deappear
wirelessrevolution said:
There are several things that I do not like about the Decrapified ROM
1. The 3 buttons on the bottom (Phone / App Drawer / Browser) sometimes vanish. Only way to fix it is to reboot
2. When you dock the phone into the car mount, the Navigation doesn't do anything. It would be nice to launch your own GPS app or the Google Navigation app. There are other activities that do nothing.
Everything is is great. Love the Google Integration and Love the missing Verizon Crapware on it (VZ Navigator, VZ Music, etc)
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App

I installed handcent as my txt app and my text feild doesn't automatically pop up until I tap in the text feild also I installed go launcher and have no problems with the phone app drawer....only issue I have is when going to this site once the page loads for some reason it wants to keep refreshing the page it doesn't matter what page it is on here it does it for all of then I have been to on the xda website

Beamer9408 said:
I installed handcent as my txt app and my text feild doesn't automatically pop up until I tap in the text feild also I installed go launcher and have no problems with the phone app drawer....only issue I have is when going to this site once the page loads for some reason it wants to keep refreshing the page it doesn't matter what page it is on here it does it for all of then I have been to on the xda website
Click to expand...
Click to collapse
The handcent thing its normal and was actually a bug in the stock mms. It should wait for you to tap the text field.
Also, have you tried the xda app? Its great!
Sent from my VS910 4G using XDA Premium App

thecubed said:
Anyone wondering about the OTA please read this!
If you have CWM installed, you won't be able to take the OTA.
For now, I'd suggest staying away from it until I get a chance to look it over first.
Also, if you're running my decrapified ROM, installing the OTA would bootloop your device since decrapified is deodexed and the OTA would be odexed.
In the next day or so (whenever I get access to the OTA zip file), I'll disassemble it and see what changes it contains (like if it has a new recovery, or new kernel, or changes the board configuration) I'll post back here to let y'all know.
UPDATE
It appears that the update is safe to install for those running the revo stock (not decrapified) ROM.
It makes changes to quite a lot-- new boot.img, new LTE RIL, new CDMA RIL, new LTE baseband ROM, changes to the recovery system to bring it in line with normal Android (still not very 'normal', but normal as in "now contains an installrecovery.sh that android can use"), and a bunch of new ODEX files.
Let me stress this and make it perfectly clear: this update will NOT work if you're running decrapified ROM.
In the next day or so, I'll make an updated decrapified ROM (see? I was waiting for a good reason to make an update ) that will include the OTA in it.
Until then, relax and keep hitting that "ignore" button
Click to expand...
Click to collapse
darnit.. I really want/need the baseband update.. anybody have the stock Recovery image? I lost mine when attempting to backup before installing CWM, not thinking I would ever need it..

drt054 said:
darnit.. I really want/need the baseband update.. anybody have the stock Recovery image? I lost mine when attempting to backup before installing CWM, not thinking I would ever need it..
Click to expand...
Click to collapse
Just flash it via revotoolkit...
The baseband image doesn't appear to change much at all, it's only a minor change it appears...

Mine wouldn't take any deferral time greater than 24 hours....and out of the blue it started about 10 hours after I deferred for 24....
Mine rebooted to Clockwork, I selected reboot, it came back up, displayed a page noting the failure, and everything appears to be working fine -- 30 minutes and counting. We'll see if it tries again...

thecubed said:
Just flash it via revotoolkit...
The baseband image doesn't appear to change much at all, it's only a minor change it appears...
Click to expand...
Click to collapse
Yeah, I PM'd you on that.. revo tool kit not working, download file only 36k, even attempted to download the .tar (via Windows7) described in the output in the program and the countdown just keeps looping. There may be something wrong with the files or the file host...
disregard.. just attempted download in Dolphin Browser on my phone and it is downloading the 6.73mb file recovery-stock.tar from 199.167.134.110/private/iomonster/files/revo-cwm/recovery-stock.tar.gz
So i should be able to follow same instructions I used to manually install cwm to install this, correct? Or I could just wait for the new decrap ROM, but I am very impatient.. lol

I am giving up!!!!!
ok.. getting really mad now. I successfully and manually flashed the stock recovery image and verified that with revo toolkit. So applied the update and it boots into stock recovery but not even half way through the arrow becomes an " ! " and reboots and says update failed or incomplete. So now I will put back CWM and wait for the next version of decrap.

drt054 said:
ok.. getting really mad now. I successfully and manually flashed the stock recovery image and verified that with revo toolkit. So applied the update and it boots into stock recovery but not even half way through the arrow becomes an " ! " and reboots and says update failed or incomplete. So now I will put back CWM and wait for the next version of decrap.
Click to expand...
Click to collapse
You can NOT apply the OTA if you're running decrap!

thecubed said:
You can NOT apply the OTA if you're running decrap!
Click to expand...
Click to collapse
I know that.. I am using stock rooted. I only meant I would wait for it because you said you were going to include the update in next version..
Sent from my VS910 4G using XDA App

thecubed said:
You can NOT apply the OTA if you're running decrap!
Click to expand...
Click to collapse
I'm running Decrap1.1 and couldn't stop the attempted upgrade, since mine wouldn't respond to any attempts to defer. So, I went poking around under the hood. Just on a hunch, I used Titatium Backup to freeze a program called Verizon Package Installer, thinking that might interupt any attempt to actually update. The update loader ran and failed, gave me a warning, and I haven't seen it again since. I also am having ZERO problems with the phone. It's like it went away and isn't coming back.
Do you think my package loader freeze might do that?

5.7.893 + Webtop without revert to stock first

Hey guys, i'm not rooted and updated using three file process to get to system version 5.7.893 only to realize that my webtop was there but not working or as they say broken. A known problem in the three fill update process. I kept reading you have to revet to stock via the method posted and then use the single update file package of 54mb to have webtop again.
I didn't want to do that because the process wipes the phone. So i downloaded the single file blur.....5.5.886.XT875 which is supposed to bring you to 5.7.893 after reverting to stock in order to have webtop. Put it on sd and booted in recovery and told it update from sd card.
It went smoothly. So now i have a software version i was really loving because my phone was running smoothly on 7.893 but now i also have webtop again. Version 1 it says.
And i confirmed i was on 5.7.893 before trying this. So i'm not sure it will work for everyone, but according to the instructions given, i didn't have to go through all of that.
If i'm going to run into problems in the future - someone alet me. If not i hope it works for other. Love my webtop.
If someone already posted this somewhere, sorry. Be easy on me

Didn't work for me. Got asert error. Are you sure you ever lost webtop?
Sent from my DROID BIONIC using xda premium

tbell6 said:
Didn't work for me. Got asert error. Are you sure you ever lost webtop?
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
yes i am very certain that i lost it. when i was sitting on ver. 5.5893 webtop was very unstable. then when i got up to 7.893 it was gone. i could not access it from the drop down menue when on the dock nothing. i am quite certain it was gone. i battery pull etc etc and nothing there was no option to run it from anywhere. i tried several times. It is curious though that i can install the one package file even with no revert and after already installing the three separate files and you can't. i ran it again last night and it installed just fine again so idk.

[ROM] CM7-GBKernel .621

I Have created a CM7 rom for rooted 621 and it should a lot easier to use now that I have tested personally and everything works as it should no need for gapps as it has vendor.apk in it and it will update to playstore.
Flashing Instructions
1:Back-up always
2:full wipe
3:install rom via CWR or bootstrap
4:Gapps arent needed but you may flash just to be comfortable
5: reboot
6: leave me feedback
7: enjoy
Downloads
Rom: http://www.4shared.com/zip/PvWul1cI/KiladarsCM7GBKERNEL.html?
Gapps: http://www.4shared.com/zip/tDblkDjI/gapps-gb-20110828-signed.html?
Known Bugs:
Settings does not open working on it right now.
let me know what you guys think.
change log:
Settings updated should work now
I Have finally fixed the settings

will this work on gb.605?
Sent from my DROID RAZR using xda premium

I believe it should. I only have my 621. Flash at your own risk.
Sent from my DROIDX using xda app-developers app

ok I'll flash later then thanks
Sent from my DROID RAZR using xda premium

BADDINOROX99 said:
ok I'll flash later then thanks
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
If your scared that your phone may brick or boot loop remember to back up and if you need me to i can find you a tutorial to unbrick your device just for comfort

Kiladar said:
If your scared that your phone may brick or boot loop remember to back up and if you need me to i can find you a tutorial to unbrick your device just for comfort
Click to expand...
Click to collapse
I can't flash it yet because my computer is in the repair shop and I never do anything risky with my phones unless my computer is nearby
Sent from my DROID RAZR using xda premium

Okay. I wonder if anyone has tried this yet.
Sent from my DROIDX using xda app-developers app

I hope so it looks promising
Sent from my DROID RAZR using xda premium

Well Im very new at modding Droid X, but I have an important question...
Is the hdmi fully working?
Or is there any rom which make it work as it should?
I mean something like a mirror.
Thanks!

Downloading Now. I just hope it's for the rooted .621 Non-Milestone hack. The Milestone hack (for root) is .604.
Sent from my DROIDX using xda premium
Update:
First I tried it without gapps. Everything booted fine, but there was no market nor would accounts/ sync let me add Google account.
So, I rebooted into recovery, which worked fine, and flashed gapps.
This time on boot, I actually got the Droid X welcome screen, was able to put in Google info, and market initiator ran and updated.
After that everything worked fine.
Tested Bluetooth, Messages, Gps and Calls. Didn't get chance to try Wifi yet, but I'm sure it works since everything-else does.
The only thing that Would be better is an updated Superuser. The 1 included will NOT update SU Binary. I think it's the old edify binary. Even by updating Superuser in the market WON'T help. Although an easy fix is to get RootUninstaller and uninstall Rom Superuser, then download new 1 from the market and install.
Keep up the hard work. Nice Rom.

Finally, does this works for any other gb kernel besides .621?
Anybody please tell us!

Nope, but maybe yes
BADDINOROX99 said:
will this work on gb.605?
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
Nope, but I may have a bad download as I forgot to check the Md5 sum before I flashed. Install was aborted. I can't try again right now because I have another phone to flash and have to go to bed early tonight.

And thank your for the review I've been waiting for a review like that I've created a couple roms and no one has have gave me so much input
Sent from my SGH-i917 using XDA Windows Phone 7 App

No prob Kiladar. I think if someone is going to comment on someones work, they should at least review it and be as informative as possible. It makes it easier
on the devs to look at potential probs/fixes too.
Oh yea, I also got to looking into your system/app folder in your zip. The vending.apk is Not in there, which i would say is why I had to flash the gapps. Just wanted you to know.
Also there is no "boot.img" (which is kernel right?) in the new dwnload.

Right, I will update OP saying to flash gapps rather then say not needed
Sent from my SGH-i917 using XDA Windows Phone 7 App

Beanerman said:
Downloading Now. I just hope it's for the rooted .621 Non-Milestone hack. The Milestone hack (for root) is .604.
Sent from my DROIDX using xda premium
Update:
First I tried it without gapps. Everything booted fine, but there was no market nor would accounts/ sync let me add Google account.
So, I rebooted into recovery, which worked fine, and flashed gapps.
This time on boot, I actually got the Droid X welcome screen, was able to put in Google info, and market initiator ran and updated.
After that everything worked fine.
Tested Bluetooth, Messages, Gps and Calls. Didn't get chance to try Wifi yet, but I'm sure it works since everything-else does.
The only thing that Would be better is an updated Superuser. The 1 included will NOT update SU Binary. I think it's the old edify binary. Even by updating Superuser in the market WON'T help. Although an easy fix is to get RootUninstaller and uninstall Rom Superuser, then download new 1 from the market and install.
Keep up the hard work. Nice Rom.
Click to expand...
Click to collapse
wifi works just fine with it, and I agree bout the updated superuser since you cant uninstall the one you have with it which means you also cant update to the new superuser because they are different volumes but over all nice ROM.:good:

thelangosta said:
Nope, but I may have a bad download as I forgot to check the Md5 sum before I flashed. Install was aborted. I can't try again right now because I have another phone to flash and have to go to bed early tonight.
Click to expand...
Click to collapse
I had it working on mine but my .605 was the .621/.605 deodexed hacked version cause I was on the .621 before I did the work around on the magic 5 route, originally I did the .604 work around but it should work on the .605 stock rooted, but then again I was also running the kernel for the .621 sooooo if the kernel is the key for running it maybe you cant.
Try another download, maybe you did get a bad DL

Other issues with phone
mbm262 said:
I had it working on mine but my .605 was the .621/.605 deodexed hacked version cause I was on the .621 before I did the work around on the magic 5 route, originally I did the .604 work around but it should work on the .605 stock rooted, but then again I was also running the kernel for the .621 sooooo if the kernel is the key for running it maybe you cant.
Try another download, maybe you did get a bad DL
Click to expand...
Click to collapse
I tried this again but, I think the real problem is with my microSD card. I have subsequently tried to flash other roms and have had other aborts as well. I know that the md5's on those checked out. I was able to flash a cm9 based rom and got it set up just fine. All this from the same card on the same phone. Sooo I am attempting to format the card just in case I have bad sectors or something.
Luckily my DX is no longer activated and just keeps me from killing my SGS3 with flashes.:silly:

thelangosta said:
I tried this again but, I think the real problem is with my microSD card. I have subsequently tried to flash other roms and have had other aborts as well. I know that the md5's on those checked out. I was able to flash a cm9 based rom and got it set up just fine. All this from the same card on the same phone. Sooo I am attempting to format the card just in case I have bad sectors or something.
Luckily my DX is no longer activated and just keeps me from killing my SGS3 with flashes.:silly:
Click to expand...
Click to collapse
I hear ya, I had the same prob with sd card so i formatted mine as well, problem was still there though. whenever i tried to install a rom from sd card via rom manager the problem was i kept getting the message saying waiting for sd cart to mount then it would say error bla bla bla sending log file to cwm ect ect ect.... i dont know exactally how i fixed that, all i know is i installed another rom, like cm7 or cm9 for instance and after that whenever i went to back up rom it worked fine ever since.... maybe something flashes over correcting the sd card problem when you install a rom... I know rom manager checks to verify the marker on sd card and thats what your problem is I believe.
Try doing this, try installing a rom cm7/cm9 without making a backup (i know you could lose everything if it fails but its the only way i know that fixed mine) after you have installed cm7/9 go to rom manager and hit the Backup Current Rom it should reboot you to cwm recovery and make an auto backup, if it does this without throwing up the waiting for sd card to mount error stuff and it runs the backup program and then reboots you it should fix your sd card problems.....

Review this rom
this is by far a ROM with the least lag by far i tried liquid ICS and plenty others don't know what it is but the lag is really minimal runs really smooth i only have this for like 3 hours but will update soon
pls hit thanks if i helped