I think I found the proper RSD lite 4.8 and motorola drivers but the problem is I cant install the drivers because the phone is bootlooped and i can't go into PC mode. When I am in bootloader and plug in the phone with RSD Lite running it attempts to load drivers, fails, and when I goto device manager and try and point it to the motorola drivers it says they are incorrect and won't install. I know this is off topic but I figure many here have bootlooped and then successfully SBFd and I'm hoping for some advice before i try and find a VZW store that can.
DroidForums.net | Android Forum & News
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
rubiX Focused 1.9.5
- Thread starter drod2169
- Start date
I think I found the proper RSD lite 4.8 and motorola drivers but the problem is I cant install the drivers because the phone is bootlooped and i can't go into PC mode. When I am in bootloader and plug in the phone with RSD Lite running it attempts to load drivers, fails, and when I goto device manager and try and point it to the motorola drivers it says they are incorrect and won't install. I know this is off topic but I figure many here have bootlooped and then successfully SBFd and I'm hoping for some advice before i try and find a VZW store that can.
thelionelking
Member
I have a recurrence of a fairly awful problem that I must be alone in experiencing. I posted a while back about my DX having a bootloader error after 1.95 and trying to nandroid backup. I went to VZW and they had no clue and didn't have the capability or intelligence to reflash the software so I received a refurb unit by mail yesterday.
The new unit was already on .340/2.2.1 so I rooted with z4root, loaded clockwork, loaded Rubix 1.95 and then restored most of my stuff via google and mybackup pro (just apks and data, no system).
Everything was fine until this morning when I went back to clockwork and re-bootstrapped recovery (I always do this before I go into clockwork recovery or ROM manager), and had clockworkmod reboot into recovery. I am now back stuck at the M logo. However, this time I can get into the normal recovery mood (Home/Power/Search etc.) In the normal recovery I tried a cache clear with a reboot - nothing; then I tried a wipe data/factory reset with a reboot - still stuck at the M logo.
I am guessing I have to SBF but I am now unsure what files to use for the SBF - I think there are .340 system only files somewhere and I am praying that will work. Does anyone know where those SBF files are and whether they might work or have any other suggestions??
Clearly there is some reproducible corruption of the bootloader (?) with the Clockworkmod recovery bootstrap that I have now unfortunately duplicated on two different DXs but I am guessing I am the only one experiencing this since nobody could even flash a theme after the ROM without going into recovery...
I think I found the proper RSD lite 4.8 and motorola drivers but the problem is I cant install the drivers because the phone is bootlooped and i can't go into PC mode. When I am in bootloader and plug in the phone with RSD Lite running it attempts to load drivers, fails, and when I goto device manager and try and point it to the motorola drivers it says they are incorrect and won't install. I know this is off topic but I figure many here have bootlooped and then successfully SBFd and I'm hoping for some advice before i try and find a VZW store that can.
Have you tried battery pull, then holding camera button, volume down and power button to power up with USB cable disconnected?
I have a recurrence of a fairly awful problem that I must be alone in experiencing. I posted a while back about my DX having a bootloader error after 1.95 and trying to nandroid backup. I went to VZW and they had no clue and didn't have the capability or intelligence to reflash the software so I received a refurb unit by mail yesterday.
The new unit was already on .340/2.2.1 so I rooted with z4root, loaded clockwork, loaded Rubix 1.95 and then restored most of my stuff via google and mybackup pro (just apks and data, no system).
Everything was fine until this morning when I went back to clockwork and re-bootstrapped recovery (I always do this before I go into clockwork recovery or ROM manager), and had clockworkmod reboot into recovery. I am now back stuck at the M logo. However, this time I can get into the normal recovery mood (Home/Power/Search etc.) In the normal recovery I tried a cache clear with a reboot - nothing; then I tried a wipe data/factory reset with a reboot - still stuck at the M logo.
I am guessing I have to SBF but I am now unsure what files to use for the SBF - I think there are .340 system only files somewhere and I am praying that will work. Does anyone know where those SBF files are and whether they might work or have any other suggestions??
Clearly there is some reproducible corruption of the bootloader (?) with the Clockworkmod recovery bootstrap that I have now unfortunately duplicated on two different DXs but I am guessing I am the only one experiencing this since nobody could even flash a theme after the ROM without going into recovery...
I think I found the proper RSD lite 4.8 and motorola drivers but the problem is I cant install the drivers because the phone is bootlooped and i can't go into PC mode. When I am in bootloader and plug in the phone with RSD Lite running it attempts to load drivers, fails, and when I goto device manager and try and point it to the motorola drivers it says they are incorrect and won't install. I know this is off topic but I figure many here have bootlooped and then successfully SBFd and I'm hoping for some advice before i try and find a VZW store that can.
Have you tried battery pull, then holding camera button, volume down and power button to power up with USB cable disconnected?
That gets me into bootloader mode just fine but RSDLite doesn't recognize my phone when the USB cable is then connected. I've tried opening RSDLite with and without the cable connected in bootloader with no success. It says driver installation unsuccessful but it seems the only way to properly install the drivers is with a working phone. I don't have that so I am trying to figure out how to get the drivers installed so RSDLite finds the phone and I can SBF.
What version of windows are you using? Are the drivers the correct drivers for your version of windows? (i.e. 64b vs 32). Did you get the drivers from Moto?
Some people reported they were not able to use RSD lite in Win7 -one was an experienced developer in the xda forums.
Others reported problems with XP 32b.
Did you try it with UAC off? And the antivirus/firewall off? -I use comodo and I had to set it to game mode, even after setting RSD as a trusted app.
If you are trying RSD from a laptop and if your problem is the driver install with a phone, you could try taking the laptop to a VZ store and ask them to lend you an X just to get the drivers in -since you said that you needed an X to get the drivers in.
I don't know if any of this would work, but those are all random things I thought of when I saw your post. I hope you can fix it. Good luck.
Some people reported they were not able to use RSD lite in Win7 -one was an experienced developer in the xda forums.
Others reported problems with XP 32b.
Did you try it with UAC off? And the antivirus/firewall off? -I use comodo and I had to set it to game mode, even after setting RSD as a trusted app.
If you are trying RSD from a laptop and if your problem is the driver install with a phone, you could try taking the laptop to a VZ store and ask them to lend you an X just to get the drivers in -since you said that you needed an X to get the drivers in.
I don't know if any of this would work, but those are all random things I thought of when I saw your post. I hope you can fix it. Good luck.
I think I found the proper RSD lite 4.8 and motorola drivers but the problem is I cant install the drivers because the phone is bootlooped and i can't go into PC mode. When I am in bootloader and plug in the phone with RSD Lite running it attempts to load drivers, fails, and when I goto device manager and try and point it to the motorola drivers it says they are incorrect and won't install. I know this is off topic but I figure many here have bootlooped and then successfully SBFd and I'm hoping for some advice before i try and find a VZW store that can.
Have you tried battery pull, then holding camera button, volume down and power button to power up with USB cable disconnected?
That gets me into bootloader mode just fine but RSDLite doesn't recognize my phone when the USB cable is then connected. I've tried opening RSDLite with and without the cable connected in bootloader with no success. It says driver installation unsuccessful but it seems the only way to properly install the drivers is with a working phone. I don't have that so I am trying to figure out how to get the drivers installed so RSDLite finds the phone and I can SBF.
thelionelking
Member
I think I found the proper RSD lite 4.8 and motorola drivers but the problem is I cant install the drivers because the phone is bootlooped and i can't go into PC mode. When I am in bootloader and plug in the phone with RSD Lite running it attempts to load drivers, fails, and when I goto device manager and try and point it to the motorola drivers it says they are incorrect and won't install. I know this is off topic but I figure many here have bootlooped and then successfully SBFd and I'm hoping for some advice before i try and find a VZW store that can.
Have you tried battery pull, then holding camera button, volume down and power button to power up with USB cable disconnected?
That gets me into bootloader mode just fine but RSDLite doesn't recognize my phone when the USB cable is then connected. I've tried opening RSDLite with and without the cable connected in bootloader with no success. It says driver installation unsuccessful but it seems the only way to properly install the drivers is with a working phone. I don't have that so I am trying to figure out how to get the drivers installed so RSDLite finds the phone and I can SBF.
Did your RSDLite install come with a manual? Check out this excerpt:
Edit: Link in the manual excerpt doesn't work. Sorry I couldn't help.
Last edited:
So, I'm trying to run the scripts in the OP, but for some reason, none of them exist... I cant restore quickoffice, ect ect. I checked, and data/rubix doesnt exist on my phone. Any idea what could have happened?
Also, the undervolt script doesnt seem to work at all...
So, I'm trying to run the scripts in the OP, but for some reason, none of them exist... I cant restore quickoffice, ect ect. I checked, and data/rubix doesnt exist on my phone. Any idea what could have happened?
Also, the undervolt script doesnt seem to work at all...
If data/rubix doesn't exist on your phone, you must of wiped data after the install. The install makes this folder for you.
To run the scripts, you must enter su before running them.
Also, Lowvolt requires the overclock module to work. It's not installed by default, since I don't have my hands on the new module yet.
A few pages back I asked about a tun.ko module for Rubix (for openvpn etc). I was able to find a working tun.ko module and wanted to share. These are raw and dirty instructions for getting tun.ko going and openvpn (at work and just don't have time to type something pretty lol). You can skip anything below that doesn't have tun.ko in the command if you just need tun.ko for another vpn client like Cisco etc.
These are for someone who has decent linux/android knowledge etc and I take no responsibility if you blow up your phone or your phone suddenly becomes alive and attacks your toaster oven or anything else you may come up with.
Assumptions:
1) Your running a working Rubix Focused 1.9.5 install on a DroidX
2) You have "OpenVPN Settings" by Friedrich Schauffelhut from the market installed (Skip OpenVPN Installer from the market, the binary it installs has an issue with ifconfig and route)
3) You have Android Terminal Emulator from market or adb shell access to your phone and know how to use them.
4) The two downloads below are are saved to the root of your SD card (aka /sdcard)
5) /system is mounted as writable (aka adb remount or via root explorer etc)
Download the following:
tun.ko:
http://sodhaxors.com/download/openvpn/tun.ko (Sorry I can't give proper credit to whom ever compiled this. I have about 12 tun.ko's that I downloaded and can't remember where the one that worked came from)
openvpn-static-2.1.1:
http://sodhaxors.com/download/openvpn/openvpn-static-2.1.1 or https://github.com/downloads/fries/android-external-openvpn/openvpn-static-2.1.1.bz2 (you will need to bzip2 -d it for the second link after downloading)
Install/Configure:
From Android Terminal or adb shell, do the following, please note assumptions 3,4, & 5 from above (also must be root, aka su first from terminal)
cp /sdcard/tun.ko /system/lib/modules/tun.ko
cp /sdcard/openvpn-static-2.1.1 /system/xbin/openvpn
chmod 644 /system/lib/modules/tun.ko
chmod 555 /system/xbin/openvpn
mkdir /system/xbin/bb
ln -s /system/xbin/ifconfig /system/xbin/bb/ifconfig
ln -s /system/xbin/route /system/xbin/bb/route
In OpenVPN Settings under Advanced:
Make sure Load tun kernel module is checked
Path to openvpn binary is set to /system/xbin/openvpn
Tun modele settings > Load module using insmod and Path to tun module /system/lib/modules.tun/ko
These are for someone who has decent linux/android knowledge etc and I take no responsibility if you blow up your phone or your phone suddenly becomes alive and attacks your toaster oven or anything else you may come up with.
Assumptions:
1) Your running a working Rubix Focused 1.9.5 install on a DroidX
2) You have "OpenVPN Settings" by Friedrich Schauffelhut from the market installed (Skip OpenVPN Installer from the market, the binary it installs has an issue with ifconfig and route)
3) You have Android Terminal Emulator from market or adb shell access to your phone and know how to use them.
4) The two downloads below are are saved to the root of your SD card (aka /sdcard)
5) /system is mounted as writable (aka adb remount or via root explorer etc)
Download the following:
tun.ko:
http://sodhaxors.com/download/openvpn/tun.ko (Sorry I can't give proper credit to whom ever compiled this. I have about 12 tun.ko's that I downloaded and can't remember where the one that worked came from)
openvpn-static-2.1.1:
http://sodhaxors.com/download/openvpn/openvpn-static-2.1.1 or https://github.com/downloads/fries/android-external-openvpn/openvpn-static-2.1.1.bz2 (you will need to bzip2 -d it for the second link after downloading)
Install/Configure:
From Android Terminal or adb shell, do the following, please note assumptions 3,4, & 5 from above (also must be root, aka su first from terminal)
cp /sdcard/tun.ko /system/lib/modules/tun.ko
cp /sdcard/openvpn-static-2.1.1 /system/xbin/openvpn
chmod 644 /system/lib/modules/tun.ko
chmod 555 /system/xbin/openvpn
mkdir /system/xbin/bb
ln -s /system/xbin/ifconfig /system/xbin/bb/ifconfig
ln -s /system/xbin/route /system/xbin/bb/route
In OpenVPN Settings under Advanced:
Make sure Load tun kernel module is checked
Path to openvpn binary is set to /system/xbin/openvpn
Tun modele settings > Load module using insmod and Path to tun module /system/lib/modules.tun/ko
plyallstar
New Member
is this a Deodexed Rom? the reason i'm asking is because i have been trying to install the fabolous revolution theme with this rom and it doesn't seem to be working. I know it says the theme is for the apex rom, but it also saying on the page that it is compatible with this rom, which i already have running. Any help?
I have a recurrence of a fairly awful problem that I must be alone in experiencing. I posted a while back about my DX having a bootloader error after 1.95 and trying to nandroid backup. I went to VZW and they had no clue and didn't have the capability or intelligence to reflash the software so I received a refurb unit by mail yesterday.
The new unit was already on .340/2.2.1 so I rooted with z4root, loaded clockwork, loaded Rubix 1.95 and then restored most of my stuff via google and mybackup pro (just apks and data, no system).
Everything was fine until this morning when I went back to clockwork and re-bootstrapped recovery (I always do this before I go into clockwork recovery or ROM manager), and had clockworkmod reboot into recovery. I am now back stuck at the M logo. However, this time I can get into the normal recovery mood (Home/Power/Search etc.) In the normal recovery I tried a cache clear with a reboot - nothing; then I tried a wipe data/factory reset with a reboot - still stuck at the M logo.
I am guessing I have to SBF but I am now unsure what files to use for the SBF - I think there are .340 system only files somewhere and I am praying that will work. Does anyone know where those SBF files are and whether they might work or have any other suggestions??
Clearly there is some reproducible corruption of the bootloader (?) with the Clockworkmod recovery bootstrap that I have now unfortunately duplicated on two different DXs but I am guessing I am the only one experiencing this since nobody could even flash a theme after the ROM without going into recovery...
First time I've heard of someone having such problems, let alone repeated... :S And I have to say, I track probably 6 different DroidX Forum sites pretty regularly...
is this a Deodexed Rom? the reason i'm asking is because i have been trying to install the fabolous revolution theme with this rom and it doesn't seem to be working. I know it says the theme is for the apex rom, but it also saying on the page that it is compatible with this rom, which i already have running. Any help?
This ROM is deodexed, but for what you're trying to do, it doesn't matter.
Some info about themes:
Themes for ROMs such as Focused/Fission — sephtin.com
The part of that post that's important to this situation:
Themes REPLACE system/framework files. If the theme was developed based on a different ROM/Framework/etc., it probably won't work properly with the ROM you're using.
In your case, you're trying to take BLUR based framework files (Fab works on BLUR ROMs/Themes), and put those BLUR files on a BLURLESS ROM.
It's NOT going to work properly. The only themes that will work properly for any ROM, are those that are specifically designed FOR that ROM (or for a ROM with similar framework)....
Hope that helps explain why you're having issues.
I have a recurrence of a fairly awful problem that I must be alone in experiencing. I posted a while back about my DX having a bootloader error after 1.95 and trying to nandroid backup. I went to VZW and they had no clue and didn't have the capability or intelligence to reflash the software so I received a refurb unit by mail yesterday.
The new unit was already on .340/2.2.1 so I rooted with z4root, loaded clockwork, loaded Rubix 1.95 and then restored most of my stuff via google and mybackup pro (just apks and data, no system).
Everything was fine until this morning when I went back to clockwork and re-bootstrapped recovery (I always do this before I go into clockwork recovery or ROM manager), and had clockworkmod reboot into recovery. I am now back stuck at the M logo. However, this time I can get into the normal recovery mood (Home/Power/Search etc.) In the normal recovery I tried a cache clear with a reboot - nothing; then I tried a wipe data/factory reset with a reboot - still stuck at the M logo.
I am guessing I have to SBF but I am now unsure what files to use for the SBF - I think there are .340 system only files somewhere and I am praying that will work. Does anyone know where those SBF files are and whether they might work or have any other suggestions??
Clearly there is some reproducible corruption of the bootloader (?) with the Clockworkmod recovery bootstrap that I have now unfortunately duplicated on two different DXs but I am guessing I am the only one experiencing this since nobody could even flash a theme after the ROM without going into recovery...
First time I've heard of someone having such problems, let alone repeated... :S And I have to say, I track probably 6 different DroidX Forum sites pretty regularly...
Check your bootloader version
if the bootloader is version 30.03 then you need 2.3.15
if it's 30.04 then you need the .340 system sbf
Johnnysyeah
Member
I am currently running Rubix 1.9.5 with Linear Theme
I turn data off at night before I go to sleep to save battery. Back when I was running 1.9.0 I would be able to do this and still be at 100% when I woke up. Now with my current setup I wake up at 90%. I know it's not too big of a deal but it does tell me my battery life is worse with current setup. I'm going to SBF, wipe data/cache/davlik/battery stats and run 1.9.5 stock to test if it's the theme.
Unless anyone has any theories as to why this is the case, I'll be back to report the results in the New Year.
I fully charged my phone last night, took it off the charger, and left it alone while I slept.
It had data sync on and auto brightness on
When I woke up, I was at 40%.
My Phone Idle takes up 40% of the battery.
Cell standby takes up 30%.
I have a really good feeling there is something wrong with my battery.
Check your bootloader version
if the bootloader is version 30.03 then you need 2.3.15
if it's 30.04 then you need the .340 system sbf
30.03 is correct -- 2.3.15.
But 30.04 could be 2.3.15, OR 2.3.320(full)/2.3.340(system)....
Depends on what came with the phone. If the phone was received very recently, or is a replacement phone, they came with 2.3.151 and bootloader 30.04... and THOSE phones will .sbf back to 2.3.15.
You can tell more reliably by the kernel version:
2.2 (2.3.15) SBF:
2.3.151 - 2.6.32.9-g23b7ba5
2.3.15 - 2.6.32.9-ga42712e
I am currently running Rubix 1.9.5 with Linear Theme
I turn data off at night before I go to sleep to save battery. Back when I was running 1.9.0 I would be able to do this and still be at 100% when I woke up. Now with my current setup I wake up at 90%. I know it's not too big of a deal but it does tell me my battery life is worse with current setup. I'm going to SBF, wipe data/cache/davlik/battery stats and run 1.9.5 stock to test if it's the theme.
Unless anyone has any theories as to why this is the case, I'll be back to report the results in the New Year.
I fully charged my phone last night, took it off the charger, and left it alone while I slept.
It had data sync on and auto brightness on
When I woke up, I was at 40%.
My Phone Idle takes up 40% of the battery.
Cell standby takes up 30%.
I have a really good feeling there is something wrong with my battery.
Something is wrong because ive been unplugged for 13 hours using my phone all day and am at 80% battery now. Of course I have the extended battery but that only accounts for maybe a 20% increase over stock.
Similar threads
- Replies
- 500
- Views
- 140K
- Replies
- 81
- Views
- 45K
- Replies
- 20
- Views
- 9K
N
- Replies
- 837
- Views
- 135K