Related
So I'm having problems installing Hard SPL (Olinex Unsigned). The phone is connected w/ Active-sync to my computer, and all of those required "steps" to check before you begin flashing were there. It takes just a few seconds for the HardSPL to install, and it says "congratulations...", so I assumed it went well. However, when it boots up, it says NOTHING about Olinex. Instead, when I'm on the boot screen, it has red letters, the lower ones stating my normal ROM build. It looks like:
R 1.00.25.5
G 1.52.29.25.12H
D 1.93 ...
I assume this is the bootloader? I held the lower volume button and hit the soft reset button to get to the bootloader, and that was the same screen it went to. However, then the ROM boots up on the phone, and it's the same intro screen as my initial ROM was. When I proceed with trying to install the HardSPL again, it tells me my current ROM is 1.93.401.2.. not Olinex.' I also tried the SSPLmanual file. No good..
Also, I realized that when I ask for it to update, Mobile Device Center loses connection w/ my phone. Maybe I am just having a problem holding a connection between the two? Activesync is turned on on my phone, and Mobile Device Center says that my phone is connected before the flash.
Has anyone had this problem before, or know how I can fix it? Thanks everyone. I've been looking around everywhere.
TAhsifter88 said:
So I'm having problems installing Hard SPL (Olinex Unsigned). The phone is connected w/ Active-sync to my computer, and all of those required "steps" to check before you begin flashing were there. It takes just a few seconds for the HardSPL to install, and it says "congratulations...", so I assumed it went well. However, when it boots up, it says NOTHING about Olinex. Instead, when I'm on the boot screen, it has red letters, the lower ones stating my normal ROM build. It looks like:
R 1.00.25.5
G 1.52.29.25.12H
D 1.93 ...
I assume this is the bootloader? I held the lower volume button and hit the soft reset button to get to the bootloader, and that was the same screen it went to. However, then the ROM boots up on the phone, and it's the same intro screen as my initial ROM was. When I proceed with trying to install the HardSPL again, it tells me my current ROM is 1.93.401.2.. not Olinex.' I also tried the SSPLmanual file. No good..
Also, I realized that when I ask for it to update, Mobile Device Center loses connection w/ my phone. Maybe I am just having a problem holding a connection between the two? Activesync is turned on on my phone, and Mobile Device Center says that my phone is connected before the flash.
Has anyone had this problem before, or know how I can fix it? Thanks everyone. I've been looking around everywhere.
Click to expand...
Click to collapse
I'm under the impression that you are not entering your bootloader screen. Please try this again (soft reset and ASAP, press the vol down button). Keep holding it until you see Red, Green, etc.(rainbow like coloured screen) .... please report back what it says on that screen before we move on.
wow.. I suppose that did the trick. AND it DOES say that it has Olinex on it, so I guess that installed w/o a problem! Thank, I really appreciate the help. Unfortunately, I've heard many different ways to get there (mainly hold vol-down THEN press soft-reset).
One last question though.. Now that I spent a good 30 minutes installing the list of those tweaks, would I really see much of an improvement jumping to a cooked ROM? I was looking at getting AZTOR or Nataly's lite (I'm not asking which one..), but I am not sure how much of an improvement I'm looking at. I'm currently running the stock ROM as 1.93 (I guess I'm running Olinex atm). Now that I've applied all of those tweaks from that one page, is it worth it to jump to a cooked ROM?
Thanks again! That makes my day seem MUCH more successful now.
TAhsifter88 said:
wow.. I suppose that did the trick. AND it DOES say that it has Olinex on it, so I guess that installed w/o a problem! Thank, I really appreciate the help. Unfortunately, I've heard many different ways to get there (mainly hold vol-down THEN press soft-reset).
One last question though.. Now that I spent a good 30 minutes installing the list of those tweaks, would I really see much of an improvement jumping to a cooked ROM? I was looking at getting AZTOR or Nataly's lite (I'm not asking which one..), but I am not sure how much of an improvement I'm looking at. I'm currently running the stock ROM as 1.93 (I guess I'm running Olinex atm). Now that I've applied all of those tweaks from that one page, is it worth it to jump to a cooked ROM?
Thanks again! That makes my day seem MUCH more successful now.
Click to expand...
Click to collapse
Hi I would not to back to a stock 1.93 rom even the stock 2.03 rom is a lot better in my option.
cobbs said:
Hi I would not to back to a stock 1.93 rom even the stock 2.03 rom is a lot better in my option.
Click to expand...
Click to collapse
haha, so you recommend I go ahead and push my luck w/ a 2.03 cooked ROM? Will I really have to worry about all of those tweaks, or will they already be optimized in the cooked roms? Again, I'm looking at 2 that are based off of performance, so I can expect they'll already be well-tweaked, but I'm new w/ all of this.
TAhsifter88 said:
haha, so you recommend I go ahead and push my luck w/ a 2.03 cooked ROM? Will I really have to worry about all of those tweaks, or will they already be optimized in the cooked roms? Again, I'm looking at 2 that are based off of performance, so I can expect they'll already be well-tweaked, but I'm new w/ all of this.
Click to expand...
Click to collapse
Hi I would but thats me. yes these roms are tweaked for performance.
make sure you have read this http://forum.xda-developers.com/showthread.php?t=416211
warning once you start to flash some roms it is hard to stop.
Hi have a look here to flash from the internal storage.
http://forum.xda-developers.com/showpost.php?p=3287426&postcount=10
Lately I keep like 4 cooked roms in folder on my internal storage and when I feel the need to try a new rom I just copy it to root, change name and install OS from bootloader (volDown, backButton, resetButton).
That is my identical process. Sometimes they never make it to the flashing stage but always a couple on standby...lol
Ok, I don't know why but with a Haret install with the same zImage and build Fat Free Froyo as the NAND install, there is no call volume or media volume at all.
I mean they're there, but don't work. Sometimes hear someone on the other end in Android, but they never hear me.
What I have used is on the main page with the devil sign (my contribution). I can't see why it would be any different.
I had a NAND install of the same kernel and build before, but NAND started to corrupt too much so went to a Haret SD install. I never had any problems apart from lack of ipv6 support, but sod it. I reflashed the phone with the WM 6.1 ROM. I can't remember the filename (or find where I grabbed it from), but the ROM details are:
R 1.27.12.11
G 22.45.88.07H
D 1.56.00.00
Note: I did have the latest HardSPL as well. Could the radio have been version-lowered to fook up Android?
Any help appreciated!!!
Your RADIO version is wrong for Android.
Try 1.65.xx.xx or 1.71.09.01
Hmm....it was 1.65....is it possible that while reflashing WM that it downgraded the radio ROM (and probably other things)? I checked in the bootloader and I still have HardSPL 3.34
KAIS130
SPL-3.34.hard
CPLD-8
shows up in the tri-colour screen.
So if that's the case, it's just a simple radio rom reflash??
xteejx said:
So if that's the case, it's just a simple radio rom reflash??
Click to expand...
Click to collapse
Yes
10char
Great! Thank you. Although if it goes wrong I will be back to haunt you lol
Seems to be working fine. Thanks again!
**haunting suspended**
im new to setcpu. got a problem, i occasionly tick set on reboot before i tested my changes in undervolting. now i get reboots every time i want to restart my device right after pincode choosing screen apears.
is there any possibility to get around this, or do i have to flash again over odin?
thx for your help
(ps: sorry posted in an other wrong thread already)
pimser said:
im new to setcpu. got a problem, i occasionly tick set on reboot before i tested my changes in undervolting. now i get reboots every time i want to restart my device right after pincode choosing screen apears.
is there any possibility to get around this, or do i have to flash again over odin?
thx for your help
(ps: sorry posted in an other wrong thread already)
Click to expand...
Click to collapse
please, anyone....?
I had almost the same problem. Mine didn't reboot, but it froze after 7-8 sec. after entering pin. I quickly uninstalled Setcpu (had 2 hurry before freezing) - and installed again. Maybe you can try the same? I believe this is caused of too heavy undervolting..??
pimser said:
im new to setcpu. got a problem, i occasionly tick set on reboot before i tested my changes in undervolting. now i get reboots every time i want to restart my device right after pincode choosing screen apears.
is there any possibility to get around this, or do i have to flash again over odin?
thx for your help
(ps: sorry posted in an other wrong thread already)
Click to expand...
Click to collapse
Easy enough to just flash via CWM but im assuming you dont have an alternative kernel on your SD. if so, just flash to speedmod or a kernel that doesnt support Setcpu so it doesnt activate.
Alternatively flash via Odin a non supportive kernel, then tick it so it doesnt activate on boot and reflash the kernel you were using.
or you could just set the safe mode flag before booting your phone and stock CPU settings will be set
make a file in the root of the SD and rename it to " setcpu_safemode", simples
example create a new .txt file and rename the file including extention to " setcpu_safemode"
"example.txt" then becomes " setcpu_safemode"
Hi,
I managed to screw up just about really bad with my Defy+ after flashing it with Waikiui which i afterwards noticed doesnt work with the Defy+ so now im in some hard packed poo here.
I have come to the conclusion that RSD Lite should do the trick if im lucky but i need to find a good SBF to flash the Defy+ with. Originally this phone rolled with a Nordic (GB?) so im looking for either that or something else that could be a good exchange for it.
Would it be possible to flash it with for an example Cyanogenmod or something?
Regards.
//FlashTec80
On the CM webpage, under the Devices - > Motorola Defy it says says there is no official support for defy+ ... on the other hand on the CM forums there are numerous posts by people claiming it runs just fine, seems like some run into a bug where the battery doesnt charge to 100% or something, you might want to stick to a ROM thats officially approved for your device or do a little bit more reading before you take the plunge. I would have posted links to forums and official page but apparently I cant since Im a noob and I need at least 8 previous posts
Tried to run CM 7 in RDS Lite, but it said that files mentioned in the XML file was missing, is that normal?
You can't flash CM7 using RSDlite. RSDlite is used for flashing of .sbf files!
To get your phone back to life, follow this steps:
1. Phone off, battery out
2. Hold Volume Up and Power Button and put the battery back in while holding the buttons - phone will boot into it's bootloader - you will see some white letters saying Bootloader Version 09.10 etc..
3. Install latest USB drivers - found here - http://developer.motorola.com/docstools/USB_Drivers/
4. Start up RSDlite on your PC (you need version 5.3.1)
5. Use this sbf - link (put the .sbf file in root C:/ and rename it to something short (e.g. defy235.sbf)
6. Select that sbf file in RSDlite and press START
7. Wait until the process reaches 100%, by that time your phone will be completely turned on > it's alive again
Can't write more, need to get going to classes, but will help you with everything else, as well. It's easy, just be patient.
P.S. Ignorance killed your defy+, not awesomeness
Cheers!
niksy+ said:
You can't flash CM7 using RSDlite. RSDlite is used for flashing of .sbf files!
To get your phone back to life, follow this steps:
1. Phone off, battery out
2. Hold Volume Up and Power Button and put the battery back in while holding the buttons - phone will boot into it's bootloader - you will see some white letters saying Bootloader Version 09.10 etc..
3. Install latest USB drivers - found here - http://developer.motorola.com/docstools/USB_Drivers/
4. Start up RSDlite on your PC (you need version 5.3.1)
5. Use this sbf - link (put the .sbf file in root C:/ and rename it to something short (e.g. defy235.sbf)
6. Select that sbf file in RSDlite and press START
7. Wait until the process reaches 100%, by that time your phone will be completely turned on > it's alive again
Can't write more, need to get going to classes, but will help you with everything else, as well. It's easy, just be patient.
P.S. Ignorance killed your defy+, not awesomeness
Cheers!
Click to expand...
Click to collapse
You are so true, my most serious side of ignorance put me here and your best side of awesomeness seems to save my ass, i hope
Noticed that the file that im downloading was namned .gz as a file ending, should i just delete that part or do i need to do something with it, decompress or something?
I cant try this before i get home from work but i will try it later, a quickie, would u suggest CM7 or MSginger do be installed over this in the ending? Or would u suggest something else
that u know works good
Hope classes going great and have a safe day
Regards.
FlashTec80 said:
You are so true, my most serious side of ignorance put me here and your best side of awesomeness seems to save my ass, i hope
Noticed that the file that im downloading was namned .gz as a file ending, should i just delete that part or do i need to do something with it, decompress or something?
I cant try this before i get home from work but i will try it later, a quickie, would u suggest CM7 or MSginger do be installed over this in the ending? Or would u suggest something else
that u know works good
Hope classes going great and have a safe day
Regards.
Click to expand...
Click to collapse
Decompress .gz
And yeah i u get stuck at the Motorola Bootanimation pull the battery and goto stock recovery and wipe data that should boot it...
Sent from my MB526 using xda premium
FlashTec80 said:
You are so true, my most serious side of ignorance put me here and your best side of awesomeness seems to save my ass, i hope
Noticed that the file that im downloading was namned .gz as a file ending, should i just delete that part or do i need to do something with it, decompress or something?
I cant try this before i get home from work but i will try it later, a quickie, would u suggest CM7 or MSginger do be installed over this in the ending? Or would u suggest something else
that u know works good
Hope classes going great and have a safe day
Regards.
Click to expand...
Click to collapse
Had a safe day Some bloody hooligans were on the bus home, though... Goddamn idiots. Anyway, on the brighter side of life...
You got your phone working again, mate? I suggest you stick with your stock ROM until tomorrow, then I'll walk you through the ROM's I've used and that'll help you make your pick and I'll help you with installing them, as well.
The fact that it's midnight here and that I get up at 6 for classes tomorrow is the reason you will have to wait for me
niksy+ said:
Had a safe day Some bloody hooligans were on the bus home, though... Goddamn idiots. Anyway, on the brighter side of life...
You got your phone working again, mate? I suggest you stick with your stock ROM until tomorrow, then I'll walk you through the ROM's I've used and that'll help you make your pick and I'll help you with installing them, as well.
The fact that it's midnight here and that I get up at 6 for classes tomorrow is the reason you will have to wait for me
Click to expand...
Click to collapse
Bloody hooligans should just go home and stay there
Yepp its working now but in a rush as i always is, its now running MS2Ginger 3.0, thought i´ll go that route till there is a proper ICS version of something out there
Thanks for all the help, with it i would for sure still be in pure panic mode
Know anything about overclocking the Defy+?
FlashTec80 said:
Know anything about overclocking the Defy+?
Click to expand...
Click to collapse
SetVsel
King_Rat said:
SetVsel
Click to expand...
Click to collapse
Ok i´ll try that, how high is it possible to go to still be stable?
FlashTec80 said:
Ok i´ll try that, how high is it possible to go to still be stable?
Click to expand...
Click to collapse
I'm glad you got to MS2G by yourself
I think the best way is to overclock in Recovery. You'll find the CPU menu when you open it and there you'll see 3 or 4 different settings. Every setting has a clock option and a vsel option. vsel sets the amount of electrical power that the CPU gets at a certain clock.
Best way to overclock would be to go step by step. Increase the highest clock setting by 50MHz, then reboot your phone and see if it works OK If it doesn't boot successfully or it hangs while you're using it - increase the vsel by 1. Then if it's stable, go on, another 50MHz+ and testing again...
Other than that, you can just set it to 1200MHz at once and increase the current vsel for that clock setting by 3-4, that would probably work as well
I have never overclocked mine, though Well, actually, the WIUI ROM come's with overclocked setting itself, it was at 1.1GHz, but it was slower than Pikachu at 1.1GHz So, overclocking doesn't help as much as a good ROM does At least that's my opinion.
P.S. CM9 (ICS) is wonderful But, you should wait for a couple more builds, while the things get even better. For me, CM9 and stock ROMs (including ms2ginger) are the best! You can always test, anyway I've come down to CM7 from CM9 and I'm truly sad
Defy+ stuck at boot amnimation
Hello everyone, my Defy+ stuck at Motorola boot animation. And I have the message below when Volume Up + Boot key :
Bootloader
09.10
Battery OK
OK to Program
Transfer Mode:
USB
My sbf is :
DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTFR004.0R_PDS03C_USAJRDNGIBRRTFR_P020_A024_M002_Service1FF.sbf
With the others it just doesn't work.
Please help me.
Well, why don't you flash that sbf to get it back to life?
FlashTec80 said:
Ok i´ll try that, how high is it possible to go to still be stable?
Click to expand...
Click to collapse
I'm on 300 - 19, 700 - 33, 1200 - 54...
just don't set your tweaks @ boot until you've fully tested them ^^ yet a cache clear would rectify being stuck in b/l
That sbf is the only one to make at least my phone stuck in the boot loop.
The others just don't show me anything, I got a black screen.
Maybe the sbf isn't the good one ?
I have done a backup of my system before I used rsd lite. How can I restore it as it's not a sbf file but a directory with .img ... files ?
Good replies every1, i dont know if im doing anything wrong here.
I first installed SetVsel app and changed the values in there, then when running stabilitytest it said i had the value i had chaged to. Uninstalled the app and tried to change value directly in 2ndinit but now when running stabilitytest it sais i only have 1000Mhz, thou in 2ndinit it clearly sais that vsel4 is set to 1200, any idea?
Cheers and have a safe day every1
Edit: "vsel sets the amount of electrical power that the CPU gets at a certain clock", so how high is it possible to push it before i see smoke coming out of my phone?
FlashTec80 said:
Good replies every1, i dont know if im doing anything wrong here.
I first installed SetVsel app and changed the values in there, then when running stabilitytest it said i had the value i had chaged to. Uninstalled the app and tried to change value directly in 2ndinit but now when running stabilitytest it sais i only have 1000Mhz, thou in 2ndinit it clearly sais that vsel4 is set to 1200, any idea?
Cheers and have a safe day every1
Edit: "vsel sets the amount of electrical power that the CPU gets at a certain clock", so how high is it possible to push it before i see smoke coming out of my phone?
Click to expand...
Click to collapse
You need to enable overclock in 2ndinit or load all modules enabled for it to take effect of your changes..
farsight73 said:
You need to enable overclock in 2ndinit or load all modules enabled for it to take effect of your changes..
Click to expand...
Click to collapse
Good post
Could someone with an non overclocked Defy+ make some runs in Quadrant Benchmark, i only made one run before i started changing things
Would also be fun to see some figures on an ordinary Defy
Just two hours left of work this week, then Top Gear Live is the thing for the evening
I did solve my problem. Thanks to anyone
godbod said:
Hello everyone, my Defy+ stuck at Motorola boot animation. And I have the message below when Volume Up + Boot key :
Bootloader
09.10
Battery OK
OK to Program
Transfer Mode:
USB
My sbf is :
DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTFR004.0R_PDS03C_USAJRDNGIBRRTFR_P020_A024_M002_Service1FF.sbf
With the others it just doesn't work.
Please help me.
Click to expand...
Click to collapse
go to recovery mode and wipe to the factory setting.
this happened because your phone is confused between the old and new firmware..
Hello folks! As the title says I have quite a strange issue with some kernels (Franco,LeanKernel and STOCK!!). I flash the kernels after flashing a rom ,doing it clean(all the wipes) and the phone is working fine for couple hours or a day,after that it just going verry sluggish even in appdrawer or when switching desktop screens. I looked at the CPU frequencies and they change as they shouldn't,I can tell that somethig isn't right with the cpu...I have this issue only with those kernels. I tried stock roms,4.2.x roms,flashed even google images to be sure it's stock,tried them with AOKP 4.2 and 4.1 ,CNA and the list could go on...
Is someone else having the same issue??
Any fix for this? I really want to try franco's kernel!!!
1. Hmmm, are you running a live wallpaper?
2. Do you face the same issue while using Trinity Kernel?
3. Are you sure you do not have any app such as SetCPU which is controlling the speed of CPU?
4. If you set the CPU speed back to normal, does this fix the issue?
5. How much space is mostly left on your sdcard?
I hope the answers of these questions will help to identify your problem much bettER
I don't have the same issue with faux's and trinity kernels . I don't have any program,i don't use a live wallpaper, how I can speed back to normal the cpu?
calinoii said:
I looked at the CPU frequencies and they change as they shouldn't
Click to expand...
Click to collapse
I thought you have checked the CPU speed/frequency using an app like "AnTuTu CPU Master".
calinoii said:
how I can speed back to normal the cpu?
Click to expand...
Click to collapse
Using AnTuTu CPU Master, check the speed set for the CPU when the phone is sluggish and if it something other than the normal 1200 MHz then modify it back to normal. This is what I meant
The frequencies changes verry verry fast,that's when the phone becomes sluggish,i have mini freezes,lots of them
calinoii said:
The frequencies changes verry verry fast,that's when the phone becomes sluggish,i have mini freezes,lots of them
Click to expand...
Click to collapse
I think some background processes are causing this so the CPU is trying to respond to them.
I suggest that you do a full wipe, install a ROM and use Franco's kernel, but do not install any other application on your phone, only default ones installed already with the ROM, maybe Gapps as well just to have a usable phone for some time, then check after a day whether it is again sluggish although there are no applications at all or it is still running fine. At least we would be able to know that maybe one of your application is not compatible well with these kernels and causing this mess.
You may want to avoid wiping so try to force stop the applications running in the background (and cached processes as well) to see if one of them is causing this problem.
Good Luck
I did wipe the data and didn't install any application and I have the same issue :-s
calinoii said:
I did wipe the data and didn't install any application and I have the same issue :-s
Click to expand...
Click to collapse
Do you use any widgets?
Nope
I am not sure I have helpful suggestions anymore except to be sure that you are using the correct Franco kernel whether you are running a 4.1 ROM or 4.2 one.
I hope other members can solve this problem for you. Maybe you will get a bettER help if you discuss this with the Franco kernel users on the Franco kernel thread.
Thanks anyway,i'll post this issue on franco's kernel thread and hope for a fix...and be sure i flashed the correct version of kernel )
Anyone? Please?
calinoii said:
I have some others with the same problem,but thisis the latest,no one could help me this far.I already did what you suggested me...I`m sure I did the clean wipes,just installed gapps and nothing else...when it was getting little hot the freezes were starting too,I think i did all I could,many people in this forums adviced me and still nothing,maybe franco's the only one who can help me with this...
Click to expand...
Click to collapse
Carrying on from here where we were in franco's thread. If you're flashing gapps then clearly you aren't using stock ROM like I told you to try. So, my suggestion to you for troubleshooting remains the same:
osm0sis said:
Well that's really peculiar. I'd try flashing stock again using fastboot. I'd fastboot oem lock, then fastboot oem unlock to wipe, then flash the entire image set as in efrant's thread just to make sure it all gets wiped. But unfortunately, like I said, if stock kernel doesn't work over a fresh fastboot flash of Google's factory image on your device there's still something very wrong, and it's likely wrong with the device itself.
Click to expand...
Click to collapse
osm0sis said:
Use the latest Google Factory Image for your device like I suggested, then you can see if you get the OTA immediately or you can flash it yourself. Do all this before you put any apps on, and don't let it put any apps on and see if you still have the issue with a completely stock setup.
Click to expand...
Click to collapse
Please report back only when you've followed that to the letter.
Tried both,the ones from the images,and the gapps on a stock flashed rom via recovery...I'm trying to resolve this for over 2 weeks now...
L.E : Ok,I will pm you when I manage to have some time for doing this again,thanks for your kindnes
I don't care how many times you think you've done it correctly before, I want you to try it AGAIN. And make sure you've completely wiped by using fastboot oem lock and unlock, then follow efrant's thread to the letter for flashing the entire image set. Factory Images ONLY, no stock-ish kitchen garbage.
I'm happy to help you but you've got to follow my instructions, since this is what I would be doing if I had this issue on my device.
Ok,I will,is there anyguide for locking and unlockingthe bootloader ? or simply "fastboot oem lock" and after "fastboot oem unlock" ?
calinoii said:
Ok,I will,is there anyguide for locking and unlockingthe bootloader ? or simply "fastboot oem lock" and after "fastboot oem unlock" ?
Click to expand...
Click to collapse
Yeah those are the commands. That's it. :good:
I think it's mentioned in efrant's post too, but no special guide necessary. Use the adb and fastboot that he attached too if you're new to fastboot.
I'm used to fastboot,I don't even need the guide to see the commands now,I think I used them like 100 times last 2 weeks )
Fair enough. Please follow the guide anyway though, and be sure to also flash userdata.img and recovery.img to be completely stock. You can fastboot boot cwm.img if you need it to flash your OTA afterwards. We just need you at 100% stock so we can try to figure this thing out. Also maybe hold off on adding your Google account so it doesn't start forcing apps onto your device. It could very well still be a rogue app issue so we need to try and keep your device as empty as possible to see if we can rule out hardware defect. :good:
Should I install any apps?
I did everything you said,now i'm waiting for it to boot up