[Q] Rom Problem in Rooted D2G With .629 - Droid 2 Global General

Hi, Guys my problem is that i by mistake updated my Droid 2 Global to .629 by mistake and i briked my Phone but ok i found the solution and i unbriked it and as well i rooted it.. now the problem is i cant stand this Ugly Motorola Design and i hate the Stock Rom... when i try flashing into Cyanogen 7.2 Rom i always get into the Red M Bootloop no matter how many times i SBF and do it again i always get same problem.. as well when im installing the rom in the recovery from bootstrap i see that it says installing update and it finishes to fast.. is this normal? maybe is not installing the rom but installing a update from that rom and thats why i get the bootloop please help.
Thanks

Repeating for the 51th time. Because people don't ever read.
Official Cyanogenmod builds are for 2.4.x.
Only the unofficial builds exist for 4.5.x.

Gasai Yuno said:
Because people don't ever read.
Click to expand...
Click to collapse
Only three things are guaranteed in life: Death, taxes, and people's inability to learn by reading slightly older posts on a message board.

Related

[SBF-ROM]MIUI 1.5.27 English

Here is a test SBF version of MIUI latest (27/5/11) with English patch applied and including Swype and full battery percentage display too. Replaced data icons with sense ones as the green ruins the whole look!
Please do a nandroid first as i'm not sure if this even works on other peoples Defy. I tested and it works on mine.
To install:
You need to be on Nordic rom or be using it as a base for your current rom such as CM7
Install my sbf through Moto flasher. Let boot. Report.
Note: May not be full English on first boot. Go to settings and re-set English language, reboot into recovery and clear cache and dalvik cache it seemed to do the job for me.
DOWN!Download me now!
Thanks, man
Remember this is a test please don't blame me if your wife leaves you.
Ephumuris. Defy CM7 by Quarx.
sounds not good. after flashing bootloader error . restart same error after moto logo.
Good Job.
Thx
is it working?
Is there only english/chinese? Any other languages like Polish?
Sent from DEFY running Quarx's CM7
joker20 said:
sounds not good. after flashing bootloader error . restart same error after moto logo.
Click to expand...
Click to collapse
Same
Swyped by my Defy using CM-7 beta 6 with the XDA premium App
Hmm seems to not work for others... I wonder what would need to be done differently.
Removed download link for now.
Ephumuris. Defy CM7 by Quarx.
ephumuris said:
Hmm seems to not work for others... I wonder what would need to be done differently.
Removed download link for now.
Ephumuris. Defy CM7 by Quarx.
Click to expand...
Click to collapse
i think the problem is when we make a data factory reset from normal recovery which makes 2-nd init unusable. i am trying this baut for build spanish miui, and i think a method that would work is first install an original froyo->boot it completely->reboot to bootloader and flash the moded sbf. i will report back if works.
I tried it, flashed over CM7 without wiping and it worked. Then tried a full wipe with stock recovery and it sticks at the M logo.
I was on nordic 3.4.2.177 base before I flashed. After wiping had to reflash full nordic and tried again, still stuck on Motorola logo.
I made a Custom sbf with CM7 nightly build before,
http://forum.xda-developers.com/showpost.php?p=14199021&postcount=14
Came across the same problem, it seems that we should modify the dumped CG39 a bit.
I think it would be greate&enough if we would have a SBF which only contains Custom Bootmenu so it's small and flashes very fast.
After flashing that CWM can be used to flash.
m11kkaa said:
I think it would be greate&enough if we would have a SBF which only contains Custom Bootmenu so it's small and flashes very fast.
After flashing that CWM can be used to flash.
Click to expand...
Click to collapse
This is what you are looking for. http://forum.xda-developers.com/showthread.php?p=14223629#post14223629
That Thread was created 2 minutes before my post
Thank you very much
I'm sorry if it's a dumb question, I'm new to this, what's the point of a sbf? Why not just a nandroid?
It's quite useful to have a SBF. If something is going wrong, let's say you'll try to put one nandroid which is not successfully applied or you by mistake wipe your phone using stock recovery you'll have to flash fist a Froyo SBF and then you can install 2nd Init and apply the nandroid, while by having the CM7/MIUI SBF you'll have only to apply it and that's it.
So, basically , it's for the lazy ones instead of flashing nordic, root, install 2ndInit and Miui, you just flash this sbf. 5 minutes less and a chance of bricking the phone. I'm going for the long way.
We should focus on finding and reporting bugs on the basic Miui, this would really help make a better release.
wife vs modding
ephumuris said:
Remember this is a test please don't blame me if your wife leaves you.
Ephumuris. Defy CM7 by Quarx.
Click to expand...
Click to collapse
u got me there.my wife
is starting to bothered by my modding schemes on my defy.
she said im so poor of me,if i get my defy brick she will buy me iphone4..
but i say no,buy me more defys.she said how many defys u want-2 more defys.
thats 3 total ^^ then she raised her brow & silently smiles.
maybe she think im going nuts.
little offtopic fun

[Q] Downgrade to 2.2

Hi all,
I've been reading all the tutorials on how to downgrade my O3D to 2.2 but I'm having a hard time choosing what info I should follow. And everytime a find something, usualy I get the impression that its kind of a bumpy ride...
My O3D is locked to Vodafone Portugal, not rooted, everything stock and my data cable is the one that came with the phone.
I want to keep everything stock in 2.2.
Can you please point me to the safest way to do this?
Oh, and I only have Win 7 available for the process.
Thank you so much for the help!
The easiest and most comprehensive tutorial to do that is the one posted here:
http://forum.xda-developers.com/showthread.php?t=1540163 (Point 2)
If you will need additional info on the steps mentioned on the above tutorial, you can visit the two threads below:
http://forum.xda-developers.com/showthread.php?t=1287236
http://forum.xda-developers.com/showthread.php?t=1473781
Thank you.
It does appear to be the simplest I've seen.
Really hope not to ruin my phone...
Oh, and what rom do you recomend?
I can't recommend you a Froyo ROM because I used the tutorial only to flash Gingerbread ROMs. I flashed the 21D ROM almost 4 weeks ago and I got only one ghost call (that I'm aware of).
So I'm sticking with the 21D at the moment until LG releases a new ROM or until the ghost calls start occurring more often.
botson71 said:
I can't recommend you a Froyo ROM because I used the tutorial only to flash Gingerbread ROMs. I flashed the 21D ROM almost 4 weeks ago and I got only one ghost call (that I'm aware of).
So I'm sticking with the 21D at the moment until LG releases a new ROM or until the ghost calls start occurring more often.
Click to expand...
Click to collapse
Well, I have 20a on mine and it was running smoothly but then suddenly it started again with the GC. I'm kind of in the verge of trashing this peace of sh!t.
If I downgrade using this method, when (if ever) LG relleases a fix or a new rom, I will be able to update via the nromal LG process?
Yes, you can upgrade later with the normal LG process or the one you've used to downgrade to Froyo.
However, since you've only recently started experiencing ghost calls, I would suggest to make a factory reset/wipe first on your current ROM and wait few days to see if you still have issues. In my case, the factory rest helped a lot and haven't experienced ghost calls for the last 3 weeks.
botson71 said:
Yes, you can upgrade later with the normal LG process or the one you've used to downgrade to Froyo.
However, since you've only recently started experiencing ghost calls, I would suggest to make a factory reset/wipe first on your current ROM and wait few days to see if you still have issues. In my case, the factory rest helped a lot and haven't experienced ghost calls for the last 3 weeks.
Click to expand...
Click to collapse
No no, I'm experiencing GC since the update in dec 2011. I've done the factory reset with the wipes twice and it got better, but then the monster came back.
Just finished downgrading and it went like a charm.
Just had to wipe data afterwards because i've got stuck in boot loop.
And since I've installed a carrier free rom, its so much faster now... No Vodafone things loading. The boot is twice as quick as it was in 2.3.
Thank you so much for the help!
+1!
Everyting you need is on this page (http://www.acidhazardrom.com). And he also developing a great rom. Read in tools. Please thank me god luck
Sent from my LG-P920 using xda premium
Mouselik said:
Just finished downgrading and it went like a charm.
Just had to wipe data afterwards because i've got stuck in boot loop.
And since I've installed a carrier free rom, its so much faster now... No Vodafone things loading. The boot is twice as quick as it was in 2.3.
Thank you so much for the help!
+1!
Click to expand...
Click to collapse
Glad to know that everything went well without a hitch. Which version of the Froyo ROMs you installed?
botson71 said:
Glad to know that everything went well without a hitch. Which version of the Froyo ROMs you installed?
Click to expand...
Click to collapse
The v10k downloaded directly from the guide. And it made the phone faster in normal usage. The benchmarks show the same results however.
It must be the fact that it doesn't comes without all the Vodafone [email protected] on it.
Yes, Froyo could be in some cases faster than GB, for example some games. It's also more compatible with certain apps like video calling apps (Fring, Tango etc). The biggest issue however with the Froyo is the relatively higher battery consumption.
By the way, I just remembered that I saw some time ago another method to downgrade/upgrade stock ROMs which has the major advantage of being completely automatic. The post and the zip file is here and includes complete instructions.
http://forum.xda-developers.com/showpost.php?p=22189294&postcount=30
I haven't tried it myself but many other did and they said that it works very well. I know that you've downgraded successfully but I just post this for a future reference.
Mouselik said:
The v10k downloaded directly from the guide. And it made the phone faster in normal usage. The benchmarks show the same results however.
It must be the fact that it doesn't comes without all the Vodafone [email protected] on it.
Click to expand...
Click to collapse
froyo is faster after you haven't trun off your phone for days!
and
froyo can install and run "dead space" smoothly, but gingerbread can't.

CM9 can't get past welcome screen

Hello,
I appreciate everyone here is from quite a technical background. I'm quite a noob with these things but hopefully this isn't a massive issue.
I have a HTC sensation (I'm in the uk) and I have been using cm7 for many months. I've just decided to download cm9 and install and everything was going smoothly until I get to the welcome screen.
I try to change English (USA) to English (uk) but this freezes the phone and makes it reboot. I go through this motion over and over again. Any ideas please?
When I updated to cm9, I assumed my phone was already s-off (to be honest I still don't know what this means but thought I did it when I installed cm7) so all I did this time was download cm9 and gapps to the root folder of the SD card. Then I opened rom manager, flashed clockwork recovery and went into recovery mode. I then wiped the data on the phone, wiped the cache, installed cm9 and then gapps and now I'm here!
Any ideas anyone? Many thanks in advance.
Repoman123 said:
Hello,
I appreciate everyone here is from quite a technical background. I'm quite a noob with these things but hopefully this isn't a massive issue.
I have a HTC sensation (I'm in the uk) and I have been using cm7 for many months. I've just decided to download cm9 and install and everything was going smoothly until I get to the welcome screen.
I try to change English (USA) to English (uk) but this freezes the phone and makes it reboot. I go through this motion over and over again. Any ideas please?
When I updated to cm9, I assumed my phone was already s-off (to be honest I still don't know what this means but thought I did it when I installed cm7) so all I did this time was download cm9 and gapps to the root folder of the SD card. Then I opened rom manager, flashed clockwork recovery and went into recovery mode. I then wiped the data on the phone, wiped the cache, installed cm9 and then gapps and now I'm here!
Any ideas anyone? Many thanks in advance.
Click to expand...
Click to collapse
Hi,
Once you are s-off,you do not lose it,unless you manually switch it on in fastboot.
Did you update your firmware before installing the new ROM?
malybru said:
Hi,
Once you are s-off,you do not lose it,unless you manually switch it on in fastboot.
Did you update your firmware before installing the new ROM?
Click to expand...
Click to collapse
Hi, many thanks for your reply. No I didn't update the firmware, I don't think it states this in the update instructions on the CM website - I assume I was supposed to update firmware?
What should I do now, considering the phone is in this silly loop (welcome screen to off to welcome etc...)
Repoman123 said:
Hi, many thanks for your reply. No I didn't update the firmware, I don't think it states this in the update instructions on the CM website - I assume I was supposed to update firmware?
What should I do now, considering the phone is in this silly loop (welcome screen to off to welcome etc...)
Click to expand...
Click to collapse
Hi,
The best guide on firmware update is HERE
Substitute ARHD for CM9.
Repoman123 said:
Hi, many thanks for your reply. No I didn't update the firmware, I don't think it states this in the update instructions on the CM website - I assume I was supposed to update firmware?
What should I do now, considering the phone is in this silly loop (welcome screen to off to welcome etc...)
Click to expand...
Click to collapse
The post above mine links to the best guide to get CM9 booting.
But in the mean time if you don't have the time to figure all that out (it's not hard, but it can take a little while your first time because you'll be extra careful and read all the instructions 100 times before each step) you can revert back to a Gingerbread ROM. I assume that's where you started, so if you have the Gingerbread firmware you can boo any Gingerbread ROM. That will only take about 5 minutes. So if you're in a rush to get a working phone right now just do that and it'll boot right up.
haha yes i read the instructions several times, although it's quite clear, to a newbie it's still very complicated! managed to get through it though and in hindsight that thread is pure awesomeness.
managed to get cm9 working now so will spend some time messing around with it.
thank you for all of your help.
ps. yes i began using gingerbread (stock) but i didn't have a ROM to hand and I wasn't sure if I can just download and install any rom (stock or not) willy nilly without having to do several different things to my phone so i just tried to get cm9 sorted. hopefully won't have to update rom now for some time.
thanks again!!

Interesting 1st attempt

Hey guys, I'm new to the community and I just wanted to post my 1st experience with rooting etc and follow up with a few questions!
A bit of background on my device: I've had my NS for just over 3 years now and I just recently decided (when I bought my Xperia V) that I'd like to play around with it a bit. To my knowledge, my device was one of the 1st in the country and a test dummy, and I purchased it from a friend who was working and testing for Samsung at the time. It was not linked or affiliated to Vodacom (who, if I'm correct, was the only network provider to offer the NS in S. Africa) or any other carrier for that matter. So basically due to the lack of link to any carrier, I've never received any updates or notifications to update, and have been running my stock 2.3.5 for 3 years!
Anyway, my story from yesterday was a huge learning experience. I decided that I wanted to root my NS and possibly try out a new kernel before deciding whether or not I wanted to install a custom ROM. I followed this link and managed to root my NS, install CWM recovery and everything was working pretty well using UPDATE-SuperSU-v1.65.
http://forum.xda-developers.com/showthread.php?t=2034264
However I think I flashed the wrong kernel (marmite_v9.1) or for some other reason messed up, keep in mind that I was still running my stock GB which the phone came with. Either way, I was stuck on the Google boot screen for more than an hour. I fired up into fastboot and then recovery, but couldn't boot from there (I just realized that I DIDN'T make an actual backup ). To top it off I wiped the device (another great idea) and the device wouldn't boot into fastboot, giving me a "fastboot mode no boot recovery img" message. Somehow through flashing the CWM I managed to get the device into the correct fastboot mode, and eventually after digging for a few hours I managed to find this (stock?) soju GB ROM download, and managed to flash the boot and system images using fastboot, for some reason " fastboot flash userdata data.img" refused to flash. http://forum.xda-developers.com/showthread.php?t=478820
Anyway, I managed to get back to GB 2.3.5, but get this, after about half an hour on charge, I was given an update to ICS 4.0.4 which I obviously jumped at, and to top it off, I also have JB 4.1.1 available. My NS has finally seen the light of ICS and JB!!
I have a few questions for those who have used ICS and JB though. On the NS, does stock JB provide a notable difference in battery life and speed? With it's hardware, is it capable of handling ICS and JB effectively?
Also, which version of marmite would be compatible with ICS? From what I've picked up, marmite 9.1 is compatible with JB, but is it compatible with ICS too, and if not, can someone please point me in the right direction for kernel(s) which work with ICS (not just marmite).
Second, are the Oxygen and Rasbeanjelly ROMs still up to date? When searching for Oxygen for NS on the forum, the most recent version I find is this which was posted over a year ago: http://forum.xda-developers.com/showthread.php?t=1605273
And this for Rasbeanjelly (among others): http://forum.xda-developers.com/showthread.php?t=2028718
When checking out fitsnugly.euroskank, I don't see anything for the NS. . But maybe I'll consider a shot at the PA and CM ROMs and try them both in a few days
Finally, and this 1 is way over my head, but how does CWM work? If I do a wipe before flashing a ROM/kernel, won't that wipe my backups? Do I need to partition my sd before wiping, or does CWM do that for me, and if it not, does wiping not touch the backups?
Anyway, thanks in advance, and I hope I haven't asked too many questions which have been answered before. If I have, please bare with me and point me to the correct discussion(s) and I'll go bug some other people.
uwais27 said:
Hey guys, I'm new to the community and I just wanted to post my 1st experience with rooting etc and follow up with a few questions!
A bit of background on my device: I've had my NS for just over 3 years now and I just recently decided (when I bought my Xperia V) that I'd like to play around with it a bit. To my knowledge, my device was one of the 1st in the country and a test dummy, and I purchased it from a friend who was working and testing for Samsung at the time. It was not linked or affiliated to Vodacom (who, if I'm correct, was the only network provider to offer the NS in S. Africa) or any other carrier for that matter. So basically due to the lack of link to any carrier, I've never received any updates or notifications to update, and have been running my stock 2.3.5 for 3 years!
Anyway, my story from yesterday was a huge learning experience. I decided that I wanted to root my NS and possibly try out a new kernel before deciding whether or not I wanted to install a custom ROM. I followed this link and managed to root my NS, install CWM recovery and everything was working pretty well using UPDATE-SuperSU-v1.65.
http://forum.xda-developers.com/showthread.php?t=2034264
However I think I flashed the wrong kernel (marmite_v9.1) or for some other reason messed up, keep in mind that I was still running my stock GB which the phone came with. Either way, I was stuck on the Google boot screen for more than an hour. I fired up into fastboot and then recovery, but couldn't boot from there (I just realized that I DIDN'T make an actual backup ). To top it off I wiped the device (another great idea) and the device wouldn't boot into fastboot, giving me a "fastboot mode no boot recovery img" message. Somehow through flashing the CWM I managed to get the device into the correct fastboot mode, and eventually after digging for a few hours I managed to find this (stock?) soju GB ROM download, and managed to flash the boot and system images using fastboot, for some reason " fastboot flash userdata data.img" refused to flash. http://forum.xda-developers.com/showthread.php?t=478820
Anyway, I managed to get back to GB 2.3.5, but get this, after about half an hour on charge, I was given an update to ICS 4.0.4 which I obviously jumped at, and to top it off, I also have JB 4.1.1 available. My NS has finally seen the light of ICS and JB!!
I have a few questions for those who have used ICS and JB though. On the NS, does stock JB provide a notable difference in battery life and speed? With it's hardware, is it capable of handling ICS and JB effectively?
Also, which version of marmite would be compatible with ICS? From what I've picked up, marmite 9.1 is compatible with JB, but is it compatible with ICS too, and if not, can someone please point me in the right direction for kernel(s) which work with ICS (not just marmite).
Second, are the Oxygen and Rasbeanjelly ROMs still up to date? When searching for Oxygen for NS on the forum, the most recent version I find is this which was posted over a year ago: http://forum.xda-developers.com/showthread.php?t=1605273
And this for Rasbeanjelly (among others): http://forum.xda-developers.com/showthread.php?t=2028718
When checking out fitsnugly.euroskank, I don't see anything for the NS. . But maybe I'll consider a shot at the PA and CM ROMs and try them both in a few days
Finally, and this 1 is way over my head, but how does CWM work? If I do a wipe before flashing a ROM/kernel, won't that wipe my backups? Do I need to partition my sd before wiping, or does CWM do that for me, and if it not, does wiping not touch the backups?
Anyway, thanks in advance, and I hope I haven't asked too many questions which have been answered before. If I have, please bare with me and point me to the correct discussion(s) and I'll go bug some other people.
Click to expand...
Click to collapse
Follow the link in my signature for a ROM review... I've heard debates over the best versions for battery life, but JB in my opinion is far superior to ICS... Oxygen is a great ROM, but it won't get more updates and kernels/mods ect.. Are harder to obtain.. It may be a bit challenging to do, but I'd use 4.1.2 JB (follow my chart) or skip to 4.3 JB (Mokee or Slimbean)
Sent from my Nexus S using xda premium
good flashing
uwais27 said:
On the NS, does stock JB provide a notable difference in battery life and speed?
Click to expand...
Click to collapse
Speed yes. Battery life no.
uwais27 said:
With it's hardware, is it capable of handling ICS and JB effectively?
Click to expand...
Click to collapse
There are stutters here and there. You need to overclock to obtain "optimal" ICS and JB performance. JB is smoother than ICS.
uwais27 said:
Second, are the Oxygen and Rasbeanjelly ROMs still up to date?
Click to expand...
Click to collapse
No.
uwais27 said:
If I do a wipe before flashing a ROM/kernel, won't that wipe my backups?
Click to expand...
Click to collapse
No.
uwais27 said:
Do I need to partition my sd before wiping,
Click to expand...
Click to collapse
No.
uwais27 said:
....does wiping not touch the backups?
Click to expand...
Click to collapse
Normally it does not. Unless you select "wipe external sd card"

[Q] Which Cyanogen ver. for KK 4.4.2 after using AutoRec?

Hey all, need a quick hand with my T-Mo LG G2 d801- 4.4.2 stock rom.
Process so far: towelroot>supersu>autorec>twrp>...
Tried flashing CM11, but after about 20min I figured I did something wrong, lol.
What version of cyanogenmod should I be flashing, 10 or 11? From the description of what AutoRec does to deal with the bootloader, it downgrades to the last vulnerable rom to install/enable custom recovery, correct? If so, does it stay downgraded or is that just to get the custom recovery in place?
Don't want to brick my phone experimenting, so here I am. Thanks in advance!
Also should have waited till after work, as I have no more time tonight to mess with it unfortunately. Back in 8hrs! :silly:
Nevermind, I got it working.
fleshybits said:
Nevermind, I got it working.
Click to expand...
Click to collapse
Consider that while others might not have had an answer to your question, your thread could have been frequented in order to see the answer.
So, how did you resolve your issue? ?
fleshybits said:
Hey all, need a quick hand with my T-Mo LG G2 d801- 4.4.2 stock rom.
Process so far: towelroot>supersu>autorec>twrp>...
Tried flashing CM11, but after about 20min I figured I did something wrong, lol.
What version of cyanogenmod should I be flashing, 10 or 11? From the description of what AutoRec does to deal with the bootloader, it downgrades to the last vulnerable rom to install/enable custom recovery, correct? If so, does it stay downgraded or is that just to get the custom recovery in place?
Don't want to brick my phone experimenting, so here I am. Thanks in advance!
Also should have waited till after work, as I have no more time tonight to mess with it unfortunately. Back in 8hrs! :silly:
Click to expand...
Click to collapse
Autorec just flashes an older boot loader, with a stock based KK kernel that's compatible. Once up and running any stock based kernel can be flashed if running a stock ROM. It also supports running any after market ROM, however, if running a jb based ROM one needs to be on a jb modem, and if running KK a compatible modem. These are pretty much the only prerequisites.
Sorry, that was rather rude of me wasn't it? Apologies. Not fair to ask for help if I can't return the favor when I can.
Well, instead of looking around on the CM downloads page to get the most stable release, I just got the most recent snapshot of CM 11. Silly me
Turns out the right file to flash first was, of course, the last stable release for the G2 D801, which was CM 10.2.0 (at least at the time of this writing, as far as I know.) After getting the right file and trying again, I was rocking my first custom ROM. Go me! :good:
I have not yet tried the snapshot again to see if I could upgrade to CM11, as I hit another snag: I can't connect to my carrier anymore. I can see T-Mobile in the list for networks but selecting them does nothing, I get no service. Restoring the stock ROM works just fine, its like nothing happened, but running CM I can't connect. Any suggestions?

Categories

Resources