Related
which are you doing?
Definitely Staying For Now. Sounds Like P3 Wants To Root Gingerbread The Second It Drops Then I'll Upgrade.
MikeJ92YJ said:
Definitely Staying For Now. Sounds Like P3 Wants To Root Gingerbread The Second It Drops Then I'll Upgrade.
Click to expand...
Click to collapse
same here, i think
I'm having reboots every day on froyo. I don't think I have much to lose by upgrading.
Sent from my DROID X2 using XDA App
Im gonna take the update. I sbf'd last night. Im gonna try to save the update and install later. Im gonna see if the xda community can root it and I can go back to being bloat free
Sent from my DROID X2 using XDA App
Im not rommed but im rooted, but i hear lots of people talk about SBFing to stock so they can get the update, but if your just rooted doesnt it not matter?
EDIT, never owned a Droid and have always used phones with easily unlocked bootloaders so this whole SBF thing is new to me
My experience with other droids, You will get the update still but it might fail installing if you are rooted. Some custom roms remove the ota ability.
Sent from my DROID X2 using Tapatalk
Also theres a good chance the sbf will not work if you take the OTA update just ask the atrix users
No root, no upgrade. I've got my Honeycomb tablet rooted, rom'd, and OC'd faster than the phone, I can hold out until Verizon allows a full unlock if I have to.
How would the abc not work after the ota? DROID x users can sbf from .496 back to 2.3.340 .then again I understand this is a new phone .... and ATRIX users can't sbf back to 2.2? Wow.
Sent from my DROID X2 using XDA App
andrewp3481 said:
How would the abc not work after the ota? DROID x users can sbf from .496 back to 2.3.340 .then again I understand this is a new phone .... and ATRIX users can't sbf back to 2.2? Wow.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
abc? I'm assuming you mean sbf.
The x did lose their sbf ability, then they got a new one. Any time a OTA updates the bootloader, the current sbf becomes worthless. New bootloader needs a new sbf.
BTW so far this isn't 100% confirmed but it *looks* like the x2 gingerbread update contains a new bootloader, meaning it probably will hard brick your phone if you try to sbf. So if you already updated, have fun waiting for the dev team to find an exploit to root 2.3.4. You basically updated to a D3 minus the keyboard.
Sent from my DROID X2
Im gonna wait and see what happens with the updaters... Let them deal with what may come... I have downloaded the update from the link in another thread for when everything does get sorted out...
juhde said:
abc? I'm assuming you mean sbf.
The x did lose their sbf ability, then they got a new one. Any time a OTA updates the bootloader, the current sbf becomes worthless. New bootloader needs a new sbf.
BTW so far this isn't 100% confirmed but it *looks* like the x2 gingerbread update contains a new bootloader, meaning it probably will hard brick your phone if you try to sbf. So if you already updated, have fun waiting for the dev team to find an exploit to root 2.3.4. You basically updated to a D3 minus the keyboard.
Click to expand...
Click to collapse
+1 on that. I have NO plans to apply this update. I'm rooted and need to stay that way.
juhde said:
abc? I'm assuming you mean sbf.
The x did lose their sbf ability, then they got a new one. Any time a OTA updates the bootloader, the current sbf becomes worthless. New bootloader needs a new sbf.
BTW so far this isn't 100% confirmed but it *looks* like the x2 gingerbread update contains a new bootloader, meaning it probably will hard brick your phone if you try to sbf. So if you already updated, have fun waiting for the dev team to find an exploit to root 2.3.4. You basically updated to a D3 minus the keyboard.
Sent from my DROID X2
Click to expand...
Click to collapse
Yep just ask the attic users which tried to sbf from 2.3.4 they all got a hard brick
Sent from my DROID X2 using XDA Premium App
I don't plan on updating until GB is rooted.
Seems like a lot of people around the net upgraded not knowing it can't be rooted, or are disappointed in the update (for trivial reasons). I will wait to see what P3 is doing today with it via his Twitter https://twitter.com/#!/P3Droid
I am waiting. In cases like this I suspend my usual early adopter mentality. I'd like to be able to root and sbf. I bought the phone after I saw the sbf (and days before Verizon implemented tiered data) so I feel no need to cripple myself.
That said, I am envious of those playing with their "new" phones today.
Sent from my DROID X2 using XDA Premium App
well i voted i was going to stay (rooted and affinity rom), but i broke down and upgraded... havent regretted it yet
To bad this isn't 2.3.4 its 2.3.3 one reason I haven't upgraded yet I want all the new blur features or im keeping root.
Sent from my DROID X2 using XDA Premium App
I just quickly threw together one of these for the DX2 cuz i hate hot seeing my battery percentage or using a tacky 3rd party app. The battery only reads in increments of (edit:10%). You must have a custom recovery to flash this zip and you must have gingerbread also!
UPDATED 8/7 please download lastest version for working 10%increments
causes volume notification to read inaccurately when adjusting volumes(no idea why this happens)
to restore to factory settings flash the factorybatt.zip
Flashed now how do I get it to take the place of the old one?
Thanks! worked perfect...
Can it be confirmed that this does 5% increments?
(stock does 10% unless under 20%, then it does 5%)?
Don't mean to be picky, just asking from those who flashed?
Thanks and good work on this.
awesome, works great
Doesn't do 5percent
Sent from my DROID X2 using XDA Premium App
Awesome man thanks I hated the stock one I could never really tell how much I had left and I don't like having a million things in the notification bar
X2RGB
One thing I did notice is you must choose between this and crt animation you can't have both
X2RGB
oh thats why then ^
Actually now, it seems its dropping in %20 increments
Sent from my DROID X2 using Tapatalk
the framework-res.apk for x2 gingerbread has stat_sys_battery_100png, 95png, 80png, 75png etc so i swapped images for 5% increments. I dont know why its not working that way. I realize motorola reads in 10% but theres an app on the market that can read the X2 in 1%increments so i dont think that matters i dunno
Installed it on my x2, works great. My only wish is that it was accurate to 1% instead of 10, but I know that's not your fault, it's Motorola's.
Thanks.
blakestiffler said:
the framework-res.apk for x2 gingerbread has stat_sys_battery_100png, 95png, 80png, 75png etc so i swapped images for 5% increments. I dont know why its not working that way. I realize motorola reads in 10% but theres an app on the market that can read the X2 in 1%increments so i dont think that matters i dunno
Click to expand...
Click to collapse
You have to modify something else look at the atrix forum
Sent from my DROID X2 using XDA Premium App
Anybody else having a problem with battery stats or spare parts since installing this?
Sent from my DROID X2 using XDA App
I've been searching for something like this! I don't like not being able to see my volume leves and was noticing a few other hiccups with the new 10% version, so I flashed back to the one that only displays 20% increments, hopefully only temporarily though.
Boot loop
I tried to flash this mod and it sent my phone into a boot loop! I had to sbf back to 2.2 and then update again.
Im guessing this wasnt testing on the p3 rooted gingerbread?
same here.
stanleyj42 said:
I tried to flash this mod and it sent my phone into a boot loop! I had to sbf back to 2.2 and then update again.
Im guessing this wasnt testing on the p3 rooted gingerbread?
Click to expand...
Click to collapse
Works fine how else would he test it on gingerbread
Sent from my DROID X2 using XDA Premium App
Any thoughts on why this might have happened? It appears im not the only one experiecing this.
Could it have something to do with me using go launcher
P3 rooted gingerbread. Flashed from recovery and got into the red M logo loop.
Im looking for a Rom that is as similar to stock as possible with WiFi tethering available. I'm doing this for a friend and I don't know much about the droid x2. I am experienced with HTC phones though so I'm not a noob.
Sent from my Sabotaged Droid Incredible 2.
Eclipse is the most stable rom out there with some blur components (stock).
Sent from my DROID X2 using XDA App
If all that you are looking for is the wifi tethering you can simply root and install the .apk
Sent from my cyaned X2
I tried that with stock Rom and it errors out saying the kernel doesn't support it. The phone is stock 2.3.4. I just downloaded CM7.2 for it and am going to install that to the device pretty soon. I have been taking things slow to make sure I do everything correctly because this is much more difficult to do than my droid incredible 2.
Sent from my Sabotaged Droid Incredible 2.
disconnecktie said:
I tried that with stock Rom and it errors out saying the kernel doesn't support it. The phone is stock 2.3.4. I just downloaded CM7.2 for it and am going to install that to the device pretty soon. I have been taking things slow to make sure I do everything correctly because this is much more difficult to do than my droid incredible 2.
Sent from my Sabotaged Droid Incredible 2.
Click to expand...
Click to collapse
You can try that, but that is SO far left from stock ROM since there is no BLUR in it and all the apps are AOSP.
Also, HDMI doesn't work under CM7, so if you still want that, you won't have it. It's still a great ROM and it's pretty darned fast, but it does still have some issues with apps hanging once in awhile. Otherwise, it's not a bad ROM at all, especially since it was just released a few weeks ago.
I don't have much choice considering there aren't any roms that close to stock. I've had experience with CM7 roms so I know some of the issues that will rise with its use. I was trying to avoid using the 2.3.5 sbf and rerooting to use eclipse.
Sent from my Sabotaged Droid Incredible 2.
disconnecktie said:
I don't have much choice considering there aren't any roms that close to stock. I've had experience with CM7 roms so I know some of the issues that will rise with its use. I was trying to avoid using the 2.3.5 sbf and rerooting to use eclipse.
Sent from my Sabotaged Droid Incredible 2.
Click to expand...
Click to collapse
There's always the Nameless atrix port
Sent from my DROID X2 using xda premium
Is that close to stock and will it work with stock rooted 2.3.4?
Sent from my Sabotaged Droid Incredible 2.
disconnecktie said:
Is that close to stock and will it work with stock rooted 2.3.4?
Sent from my Sabotaged Droid Incredible 2.
Click to expand...
Click to collapse
It's as close to stock as you can get without being stock. It is itself a 2.3.4 rom, so if you are on rooted 2.3.4 now then download, flash, reroot and enjoy.
Sent from my DROID X2 using xda premium
I will have to reroot after I flash it? If so Im not going to be able to do that right now. I'm returning the phone today and I won't have time to take it home to my comp so I can root it again. A link to the page would be nice to if you don't mind.
Sent from my Sabotaged Droid Incredible 2.
disconnecktie said:
I will have to reroot after I flash it? If so Im not going to be able to do that right now. I'm returning the phone today and I won't have time to take it home to my comp so I can root it again. A link to the page would be nice to if you don't mind.
Sent from my Sabotaged Droid Incredible 2.
Click to expand...
Click to collapse
I think he may have meant 'reboot'
Sent from my DROID X2 using Tapatalk
Oh.... It's boot looping for some reason and I can't get into the patched bsr
Sent from my Sabotaged Droid Incredible 2.
disconnecktie said:
Oh.... It's boot looping for some reason and I can't get into the patched bsr
Sent from my Sabotaged Droid Incredible 2.
Click to expand...
Click to collapse
Try android recovery. Power off, hold down volume and power, then when it says fastboot scroll down to android recovery. Press up, then when you get the triangle hold up and down at the same time.
Sent from my DROID X2 using xda premium
Did that already. It wasn't any help. I'm going to have to use rsd lite I think.
Sent from my Sabotaged Droid Incredible 2.
disconnecktie said:
Did that already. It wasn't any help. I'm going to have to use rsd lite I think.
Sent from my Sabotaged Droid Incredible 2.
Click to expand...
Click to collapse
Did you get it working?
Hehe yea it was really easy to flash the stock 2.3.4 using rsd lite. I rerooted and reflashed cm7 without any issues thanks for the help everyone.
Sent from my Sabotaged Droid Incredible 2.
I have a possible warranty issue with the plastic lip the microphone is in coming loose. If I end up sending the phone back will they be able to see that the radio hack is on there? Its completely stock besides that. That was nerve racking doing that so the only way I know to get rid of it would be to SBF back to Froyo because sbf'ing back to 2.3.4 does not undo it.
Sent from my DROID X2 using Tapatalk
SBFing will undo any hacks you've done, regardless of which SBF version you use, so I'm not sure why it's still hanging around.
But, if SBFing to 2.3.3 does clear it out, that would be your best bet. I don't think they have any other way of detecting if you've rooted it or anything after that, but don't quote me on it! But, I think you should be safe.
I should clarify...the only way I know how to get rid of it without actually changing the numbers back with radiocomm is by sbf'ing back to Froyo
Sent from my DROID X2 using Tapatalk
tkuligowski said:
I should clarify...the only way I know how to get rid of it without actually changing the numbers back with radiocomm is by sbf'ing back to Froyo
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
I would say that's your best bet to ensure all traces are gone.
I'd say go through with the SBF. The time spent is worth it, if they end up finding out you did modify the phone they can charge you obscene amounts because it wont be covered.
iBolski said:
SBFing will undo any hacks you've done, regardless of which SBF version you use, so I'm not sure why it's still hanging around.
But, if SBFing to 2.3.3 does clear it out, that would be your best bet. I don't think they have any other way of detecting if you've rooted it or anything after that, but don't quote me on it! But, I think you should be safe.
Click to expand...
Click to collapse
The radio hack isn't based on OS from what I've read so the only way it will be overwritten is if a software upgrade is actually writing to the radio firmware and apparently sbf'ing gingerbread does not write to the radio cause after multiple ROM's and SBF's to 2.3.4 I can still use mobile hotspots without having to do the hack again.
Sent from my DROID X2 using Tapatalk
tkuligowski said:
I have a possible warranty issue with the plastic lip the microphone is in coming loose. If I end up sending the phone back will they be able to see that the radio hack is on there? Its completely stock besides that. That was nerve racking doing that so the only way I know to get rid of it would be to SBF back to Froyo because sbf'ing back to 2.3.4 does not undo it.
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
To answer your question. Yes, they can detect the radio hack, IF they so choose to. When you first did the RadioComm hack, did you backup (copy) the hex code you changed? If not, you are kind of SOL. The LIKELYHOOD that they will look into that is not very high as they will send it back to Moto to be repaired and Moto SHOULD do a full and complete firmware and software wipe and reload on it. YMMV.
Ciao!
Moon Shadow - NM said:
To answer your question. Yes, they can detect the radio hack, IF they so choose to. When you first did the RadioComm hack, did you backup (copy) the hex code you changed? If not, you are kind of SOL. The LIKELYHOOD that they will look into that is not very high as they will send it back to Moto to be repaired and Moto SHOULD do a full and complete firmware and software wipe and reload on it. YMMV.
Ciao!
Click to expand...
Click to collapse
Yes I saved a back up of the code. Can anyone confirm that a SBF to Froyo will change it back?
Sent from my DROID X2 using Tapatalk
tkuligowski said:
Yes I saved a back up of the code. Can anyone confirm that a SBF to Froyo will change it back?
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
No, the SBF file does not change/revert the RadioComm mod. You have to manually do that. The SBF file just flashes the system partitions, kind of like installing Windows on a computer. The RadioComm mod mucks with the FIRMWARE. The firmware is similar to the BIOS or CMOS of a computer. Hope that answers your question.
Ciao!
Moon Shadow - NM said:
No, the SBF file does not change/revert the RadioComm mod. You have to manually do that. The SBF file just flashes the system partitions, kind of like installing Windows on a computer. The RadioComm mod mucks with the FIRMWARE. The firmware is similar to the BIOS or CMOS of a computer. Hope that answers your question.
Ciao!
Click to expand...
Click to collapse
It does. Thanks!
Sent from my DROID X2 using Tapatalk
Ok so I think I can verify now that an SBF to froyo does in fact write to the radio firmware. I have not gone into radiocomm and verified the values, but I've done numerous SBF with gingerbread and my TBH radio hack remained intact. I did an SBF to froyo this morning and am now completely back to stock. Any attempt to use mobile hotpot takes me to Verizon website, which it should do in stock form.
Sent from my DROID X2 using Tapatalk
tkuligowski said:
Ok so I think I can verify now that an SBF to froyo does in fact write to the radio firmware. I have not gone into radiocomm and verified the values, but I've done numerous SBF with gingerbread and my TBH radio hack remained intact. I did an SBF to froyo this morning and am now completely back to stock. Any attempt to use mobile hotpot takes me to Verizon website, which it should do in stock form.
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
Wow! Thanks for the education! I was under the impression that the SBF files only did software... Well, now is as good a time to learn something new as ever!
Ciao!
Hey, I opened eclipse parts to open bootstrap recovery and once I pressed recovery mode it acted like it was going to reboot into it normally but it just hung on the red M screen and I had to do a battery pull to get my phone running again. What caused this this time? About a week ago I had to sbf to 2.3.4 and reroot 2.3.5 then I just restored a eclipse 2.2.1 backup. Since then I flashed eclipse 2.3 over it and everything has been fine. This is the first time I've tried entering recovery though, is something screwed up?
Edit: yup every time I enter recovery it freezes at the M. An no, clicking install recovery does not help even though it says install successful.
Sent from my DROID X2 using xda app-developers app
Are you running v6 supercharger?
Nope, stock Ec. 2.3
Sent from my DROID X2 using xda app-developers app
Hmm, not sure then. You are using the CM7 and not the standard BSR? If so then I'm all out of ideas. lol...all two of them.
Hmm, looks like all of this got covered in the Eclipse thread anyways. Well, I guess you are out of luck and need to SBF. It sucks, but if you have a recent nandroid then it's not the worst thing ever.
Yea when the Dev tells you to wipe... i guess you gotta wipe. Lol thanks for your input.
Did you by chance install bsr before hitting the recovery button?
Sent from my DROID X2 using Tapatalk 2
(Not being a jerk, just saying) yea I said so in my op.
Sent from my DROID X2 using xda app-developers app
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=1318083<br />
Yup I've made backups and restored numerous times. The problem isn't not.knowing how to do it, its just that my recovery is suddenly gone. Nothing I can do currently to get the phone to boot into recovery.
Sent from my DROID X2 using xda app-developers app
Sorry to hear that. Hopefully you'll get it sorted.
I had a simular issue with my droid x2 #5 (went threw 6 of them and said i had enough) but what i did was kept clicking install on the bootstrap it seemed to work i did it like 4 times. It also doesnt like to play nice with power strips sometimes. I also deleted the recovery using rootexplorer but i dont recommend that cause things can get all screwed up
Still having trouble?
This happened to me before a while ago.
I let it sit at the red M for what felt like forever and ur finally loaded BSR.
Yea, I've been told to do a wipe and start again but I just dont wanna do that so im hoping it will start working outta the blue lol. I'll try the new suggestions, thanks guys.
Sent from my DROID X2 using xda app-developers app
GoClifGo05 said:
Yea, I've been told to do a wipe and start again but I just dont wanna do that so im hoping it will start working outta the blue lol. I'll try the new suggestions, thanks guys.
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
Yea i can definitely understand that
Just be patient with it
Make sure you have good amount of battery AND make sure you are defintly plugged into the wall outlet.
Also, make sure your charger isn't malfunctioning(plug in while phone is turned on, go to settings>Battery, make sure it says "Charging(AC)" and not "Charging(USB)" , I had the OEM charger that came with my x2 basically die on me and that's what happened before it croaked, it wouldn't recognize as being plugged.into a wall charger, and if the device doesn't see AC current coming in, it won't boot into BSR)
Another thing you can try to do is press charge mode within BSR app in Eclipse settings. Then reboot the device(reboot twice for good measure ) go back into settings,.eclipse settings,.bootstrap, and press install recovery(after it says.completed press it again a couple times just to be certain lol , let it tell you competed each time before you press it again) THEN plug phone into wall without leaving app, then press reboot recovery(or recovery mode,.sry.been a while i can't remember exactly what it says lol) and then walk away, go do the dishes or something or take a shower.
Hopefully that will get you in. Good luck!
You can also try doing a cache wipe from stock Android recovery. Never know, that might help, and you won't lose any data but doing that