[Q] defy slow unresponsive, cannot receive texts? cm10 build - Defy Q&A, Help & Troubleshooting

Apologies if this is in the wrong place. I have read through the guidelines beforehand.
I am a newbie so please be gentle....
I recently bought a motorola defy with cyanogenmod from ebay, the guy explained it ran faster etc and he was a computer wizz.
It has worked fantastic for the past 2 months. it was advertised as a motorola defy +.
It ran out of battery, I charged it then it got stuck in a bootloop. This has happened once before, A pull of the battery worked but not this time.
I scoured the internet and read about the power/volume button to get into android recovery, It said 'cant load cache'
I selected erase data and reboot.
I switched the phone on it came on, put my sim in and wondered why all day I had no calls or texts, no notifications. I started to play with the phone and it was very unresponsive, saying it wasnt responding. lagging touchscreen.
I pulled battery out, left it & started again.
Tried to download ebay app and it says not enough memory.
The phone comes on, looks like its working but is slow, cannot receive texts or download.
It came in original box which says motorla defy. originally on t mobile uk. I have a three sim. The sticker at back of phone under battery says MB525.
I got so confused looking online as there are many differences, red lense, green lense, defy and defy +'s i have no idea what I should do to get my phone back up and running.
The memory card in it is an 8gb.
This is the information you get when you go into 'about phone'
Model Number : MB526
Android Version : 4.1.2
Baseband Version: EPU93_U_00.60.03
Kernel Version:2.6.32.60-jellyX [email protected] #8 Thu Feb 21 00.25:47 CET 2013
CPU : ARMv7 Processor rev 2 (v7l)
Memory: 476 MB
Cyanogenmod version : 10_20130216_UNOFFICIAL-mb526
Build date: Sat Feb 16 20.56.42 CET 2013
Build number : cm_mb526-userdebug 4.1.2 JZ054K eng.frank.20130216.205551 test - keys
I have read so many posts, so many guides and watched videos on you tube, Iv downloaded some files but because of reading info such as cannot go back/downgrade im scared to do anything.
So my question to you skilled people is what do I need to do to get my phone back up and running again. what has happened is it a bug?
There doesnt appear to be any back up on the sd card? It wont let me download anything even though Iv wiped it?
Please may I have some simple, step by step instructions on what to do. I am not a whizz but am good at following instructions and basic pc.
You guys are absolute clever monkeys! I really hope someone can help.
The model number on the phone (on the sticker under battery) says mb525 and the same on the box. Is it the mod that has made it show mb526 in the about phone section under settings tab.
This is where im confused and scared about what to download or how to apply these to my phone!
There seems to be so many variants for example in the guide it talks about lens colours etc! im bamboozled!
When I press power and volume i get the android recovery. The message at the bottom says
E:can't mount CACHE : recovery/command
E:can't mount CACHE : recovery/caller
E:can't mount CACHE : recovery/log
iv wiped cache partition it says :
--- wiping cache.... Formatting CACHE .......... Cache wipe complete.............
E:Can't mount CACHE : recovery/log......
Iv wiped data it says :
Formatting DATA.................................... (lots of full stops!......)
Data wipe complete.
E:Can't mount CACHE: recovery/log
If I apply sdcard : update zip it says :
Install from sdcard..
finding sd card...
opening update package...
verifying update package...
..E..failed to open / sdcard/update.zip (No such file or directory)
E: signature verification failed
..
Installation aborted..
E:can't mount CACHE : recovery/log
So it appears I have no back up installed to save from.
Many Thanks & Kind Regards
If anyone can point me in the direction of files (that are a valid link) and a step by step of getting my phone back up and running I would be made up! I mss my defy

Can you enter custom recovery? I mean when you switch off your phone and back on, does blue led appear after about 4-5 seconds?
Sent from my MB526 using xda app-developers app

hiya thanks for reply, yes it does flash blue

Hi thanks for your reply. Yes blue led for a few seconds then straight to a red led whilst cyanogenmod loads this goes on for a while, it used to be very quick.

So download the rom you want to use, copy it to your sdcard, and flash it via recovery (press volume down when blue led comes on, select twrp recovery, install zip, wipe data and cache)
Since you are using a jelly bean rom, forget about model/green lens/red lens. Everything will work just fine
Sent from my MB526 using Tapatalk 2

thekguy said:
So download the rom you want to use, copy it to your sdcard, and flash it via recovery (press volume down when blue led comes on, select twrp recovery, install zip, wipe data and cache)
Since you are using a jelly bean rom, forget about model/green lens/red lens. Everything will work just fine
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for your reply!
Based on the build I was running which ROM do I go for? Any chance of a link pretty please?
If I follow your suggestions with sd card & ROM does that eliminate the need for the 'lite' software & gapps that I have read about?
Apologies for silly questions but Id like to be sure of what I am doing.... hehehe! Id like to come out of the bricked defy tunnel smiling
I have to say before my defy had its woopsie everything worked fast and like a dream
massive thanks again

Totally your call. You have options from 2.3 to 4.3. All links are in the development section. You will have to use lite gapps for roms after 4.1
Sent from my MB526 using Tapatalk 2

thekguy said:
Totally your call. You have options from 2.3 to 4.3. All links are in the development section. You will have to use lite gapps for roms after 4.1
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Massive update!! I have just been playing and pressed volume down when blue light on as you said and discovered a different recovery menu than the one I got a few days ago... I presume the first one was stock recovery??
So I wiped cache and then data reboot and I can now receive text messages, I can now download ebay app again (before it said not enough room)
So fingers crossed we are working. with MASSIVE thanks to you!
So my question now is.... As I am running a February 2013 build should I update to a newer or stay as I am?

Definitely update, newer builds are better
Sent from my MB526 using Tapatalk 2

thekguy said:
Definitely update, newer builds are better
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
hmmm i must say I am very impressed with all that goes on on here, i never realised what was behind the 'mod' on my new little superstar phone
So as I am a newbie I am unsure about the whole clockwork recovery etc so before I update anything how do I back up what is now eg I know it works....
In your wisdom which build should I go for? would it be a download it, put it on sd card and install from sd card as per your last instructions?
I have just put rsdlite on my laptop... So whats the gapps for & how do I put them on?
No worries if you havent the time to answer such daft questions, Im just a bit baffled when I read the pages as there is so much development I dont know what to follow... hehehe if there is clear instructions give me the link & I shall read
Massive thank you again for your time & patience I admire all the work that everyone does on here!

My last instructions should work, although you have to select clock work mod. (For twrp later on, doesn't apply to cwm) just wait for about half a minute when you enter recovery before going anything. Sometimes the recovery just crashes, so if you wait it out then you'll be on the safer side.
To backup your data: in upgrades of the same rom. Backup with titanium or others, and flash+ wipe cache. If it hangs on splash screen go back to recovery and wipe data+ cache, and restore using your application.
For different roms backup using the app and wipe data and cache after flashing and restore later.
As for the build: go for the latest of whichever rom you choose. FYI, Bluetooth headset audio doesn't work for 4.2 and above
Sent from my MB526 using Tapatalk 2

thekguy said:
My last instructions should work, although you have to select clock work mod. (For twrp later on, doesn't apply to cwm) just wait for about half a minute when you enter recovery before going anything. Sometimes the recovery just crashes, so if you wait it out then you'll be on the safer side.
To backup your data: in upgrades of the same rom. Backup with titanium or others, and flash+ wipe cache. If it hangs on splash screen go back to recovery and wipe data+ cache, and restore using your application.
For different roms backup using the app and wipe data and cache after flashing and restore later.
As for the build: go for the latest of whichever rom you choose. FYI, Bluetooth headset audio doesn't work for 4.2 and above
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Massive thanks for that I had been looking at the tiranium app... Phone is behaving at mo, sometimes a little slow but hey its working so I will take all you have said onboard & try to update to a newer version ROM.
Could you just explain what the first paragraph means in your reply.... 'select clockwork mod.. (for twrp later on, doesnt apply to cwm) please! thanks !

The remaining part of the paragraph is relevant to twrp recovery, which you will get after installing one of the recent builds
So, as of now ignore the part of the paragraph after the brackets
Sent from my MB526 using Tapatalk 2

thekguy said:
The remaining part of the paragraph is relevant to twrp recovery, which you will get after installing one of the recent builds
So, as of now ignore the part of the paragraph after the brackets
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
cool okay massive thanks I shall have a go over next few weeks thanks again. Have a top day

Related

Which miui?!?!

there's like 20 miui roms with different names. I just want the best one.
I'm going for this: http://forum.xda-developers.com/showthread.php?t=1123922
but i also dunno about it.
any support?
xriderx66 said:
there's like 20 miui roms with different names. I just want the best one.
I'm going for this: http://forum.xda-developers.com/showthread.php?t=1123922
but i also dunno about it.
any support?
Click to expand...
Click to collapse
That's the one I flashed yesterday. Follow the install instructions posted in the lithium miui thread.
No app drawer on miui, so using launcher pro. With launcher pro, the widgets are working, which weren't for some reason on the stock launcher.
Make sure you let your phone rest the full 8 and 4 mins, I don't know why but I did, and apparently it's important.
GPS also works, but I had to play with it to get it going.
SamsungVibrant said:
That's the one I flashed yesterday. Follow the install instructions posted in the lithium miui thread.
No app drawer on miui, so using launcher pro. With launcher pro, the widgets are working, which weren't for some reason on the stock launcher.
Make sure you let your phone rest the full 8 and 4 mins, I don't know why but I did, and apparently it's important.
GPS also works, but I had to play with it to get it going.
Click to expand...
Click to collapse
but thats my actual question... which one should i download? Is one better or has any advantages than the other?!
also i need to disable voodoo lagfix right? Because I just did it...
i'm going to go ahead and flash the one i linked to, it seems to look better. Thanks for the help.
edit:
am i meant to follow THESE instructions?
cashyftw said:
Lets get this out of the way first. I am not responsible if you screw up your phone, but you are probably here because you already screwed up your phone. I have now been through this several times over the last few days. Some will say this process is overkill, but there is no denying that it always works, so please refrain from stating the obvious.
If you have installed or updated CM7/MIUI and lost your baseband, IMEI, or both, this should help you. Due to the amount of people currently having this problem, I would recommend this be stickied at least temporarily until things are straightened out, so people can find it easily.
For Windows only, I do not have a Mac.
Step 1 - Read the entire post and understand everything involved before you attempt this. This is a long ride, probably 30-40 minutes from start to end. This is not for new people, and will assume you have a certain amount of knowledge because you attempted to flash CM7/MIUI.
DO NOT SKIP OR SHORTCUT ANY STEP IN THIS PROCESS, UNLESS I SPECIFICALLY STATED YOU MET THE CRITERIA TO DO SO. DO NOT EVEN THINK ABOUT TRYING THIS UNLESS YOU CAN REACH DOWNLOAD MODE AND RECOVERY USING BUTTONS WITH THE PHONE OFF!
Step 2 - Gather what you need...
1 - The AIO Vibrant Toolbox : http://forum.xda-developers.com/showthread.php?t=954509
Install according to directions in the post. Donate to this guy. He spent alot of time making this easy for you to do.
2 - The old CM7 install files : http://www.mediafire.com/?gn4qoonoe3cjyp6
Unzip to a location that is easy to get to.
3 - The new version of CM7/MIUI you want to install, from the thread of your choice. Donate to the developer you are using, they spend alot of their free time making your phone better. They don't get paid for it, and they dont charge you for it.
4 - Your phone, with a full battery.
Step 3 - Odin to JFD and install Clockwork 2.x
1 - Fire up the AIO Toolbox. Do not connect your phone yet, but power it down and pull your battery. See that sticker under it that says IMEI? Write it down! You will be referencing it a few times throughout the process. Start Odin and select your pit and pda files, they should automatically come up if you are using the toolbox. Hold down your volume up and down buttons, and insert your USB cable, then insert your battery. You should go to download mode, and see Odin connect. Hit start and let it fly. Once it reboots, unplug your phone. Go to settings/about phone and you should have a JFD baseband. Hit status, and check your IMEI. See how it matches the one you wrote down? Yay! Move on to the next item. If it does not, you have some reading to do because you really screwed something up, and it is beyond my power to help you...
2 - Mount phone and put the following files on the root of the sd card:
vibrant-efsbackup.zip (if you already have a backup/efs folder on your sd card you do not need this)
cm7-vibrant-initial-20110224.zip
The zip file of the new CM7/MIUI rom you want to flash.
3 - Download ROM Manager and install clockwork recovery 2.x (if you already have the update.zip on your sd card, which you should, you can also skip this) and power down your phone.
4 - Boot into recovery using the 3 button method (holding volume up and down and power, releasing power when the word VIbrant appears on your screen), hit reinstall packages, you may have to hit it twice to get to clockwork recovery. Choose to install zip from sd card, and select vibrant-efsbackup.zip. Let it do its thing. Then select reboot, and when it does, check your sd card for a backup/efs folder. Got it? Good. Power down the phone. (Obviously, if you already have the efs backup completed, you could have skipped this step.)
Step 4 - Install Clockwork 3.x and Old CM7
1 - Fire up the AIO Toolbox. Do not connect your phone yet, but pull your battery. Start Odin and hit the pda button, select the file cm7-vibrant-initial-kernel.tar from the CM7 package you unzipped (Remember, in a place that is easy to find). THIS IS IMPORTANT - UNCHECK AUTO REBOOT!!! Hold down your volume up and down buttons, and insert your USB cable, then insert your battery. You should enter download mode, and see Odin connect. Hit start and let it fly. Once it is finished, pull the usb cable. With the download mode screen still on your phone, boot into recovery using the 3 button method. You should now be in clockwork recovery 3.x. Move on to the next item! If you did not get in, you can try to pull your battery, replace it and boot into recovery from there. If you still can't get there, you get to go where the people who do not properly follow instructions go... back to Step 1.
2 - In clockwork 3.x, choose factory reset, and let it do it's thing. Then go to mounts and storage, and format system, data, and cache. Choose install zip from sd card and choose cm7-vibrant-initial -20110224.zip. As it is installing, one of the last things you see should be "restoring efs". Hit reboot when finished, and boot into CM7. When it boots, make sure you toggle the lockscreen a couple times so it connects to service. Check baseband and IMEI again. Baseband should have changed, but it does not matter until we get to where we are going. IMEI still the same right? Awesome! Power down the phone, move to the next step! It's not? You my friend, get to meet all your other friends back at Step 1.
Step 5 - Installing what you really want...
1 - Boot into recovery using the 3 button combo. Do a factory reset, wipe cache partition, go to advanced and wipe Dalvik cache. Choose install zip from sd card, and pick that shiny new version of CM7/MIUI you picked out. You are almost there. Flash it! Reboot, and when it comes back up, take note of what time it is and DO NOT TOUCH THE PHONE FOR 15 MINUTES. You have no idea the amount of bugs this squashes. After that, check the baseband and IMEI, even though you already know it is right anyway. If it is not, do i have to say it again? You know where you are going...
2 - Destroy the paper you wrote your IMEI on, you would not want that info in the wrong hands...
3 - Enjoy your new rom
FAQ:
Q: I did everything you said, and it did not work!
A: You either skipped a step, or did not stop at the point I told you you were screwed.
Q: No, seriously, I did everything you said!
A: Seriously, I have done this 5 times in the past 3 days, and it worked every time.
Q: I installed CM7 nightly #9,10,or 11 with this method, and I have no sound on calls. What gives?
A: These builds have known issues with in call audio. Flash CM7.1
Q: Once I am on CM7/MIUI, do I have to do this every time or can I update normally?
A: Once you are on CM7 or MIUI with the proper IMEI and a good baseband, you should be able to update via the rom posting instructions. If you decided to switch from CM7 to MIUI or vice versa, I would go back to this process to get your initial installation.
Q: I installed CM7.1 and then tried to go to MIUI, and lost everything again, what happened?
A: There are changes betweeen CM7 to 7.1 that have made this difficult due to compatability issues, which is why I recommend doing this process again if you want to switch between the two.
Q: I thought there was an easier way to do this, why so many steps?
Read the first paragraph of the post, but I guess that is also asking too much...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
xriderx66 said:
also i need to disable voodoo lagfix right? Because I just did it...
i'm going to go ahead and flash the one i linked to, it seems to look better. Thanks for the help.
Click to expand...
Click to collapse
Just install the one you linked to, the one direct from miui.us.
The other Lithium one looks like it's customized, overclock kernal, stuff like that.
I disabled vodoo lag fix. I odin back to 2.1. Then I installed stock 2.2.
Then I followed the instructions exactly. Wipe dalvic cashe, format system/data/cache, wipe factory restore, etc etc.
Not sure if I had to install 2.2 first, but I did anyway since the install instructions were for upgrading from a 2.2 rom and not a 2.1 rom.
thanks for the help. I'm on MIUI now, just gotta wait the total 12 mins for it to settle down. ;P
@xriderx66, please will you be kind enough to let me know your experience with the MIUI. i am strongly thinking of flashing same rom.
Thanks in advance.
No, that lengthy install instruction is outdated
xriderx66 said:
thanks for the help. I'm on MIUI now, just gotta wait the total 12 mins for it to settle down. ;P
Click to expand...
Click to collapse
You don't have to install via those long instructions anymore. Apparently those are outdated.
Just manually backup your /efs and keep a copy on your computer, just because everyone should have a copy of their /efs folder and nv_data.bin, otherwise if you run into trouble you can lose your IMEI.
Then follow these simple instructions as outlined by user nickmcminn60 for his Lithium MiUi rom, but it worked for the regular MiUi also:
INSTALL INSTRUCTIONS (For Lithium and SS-11 If you are on MIUI, CM-7 or a 2.2)
-Wipe Dalvik Cache
-Wipe Cache Partition
-Wipe Data/Factory Reset
-Format-System, Cache and Data (Located under "Mounts & Storage)
-Flash LE Lithium (EDIT by me samsungvibrant..OR THE STOCK VERSION OF MIUI could be flashed here)
-Fix Permissions
-Reboot and Let Settle For 8 Min
-Reboot again Let Set For 4 Min..
No need to do the longer install process you had mentioned in the prior post.
belushi7 said:
@xriderx66, please will you be kind enough to let me know your experience with the MIUI. i am strongly thinking of flashing same rom.
Thanks in advance.
Click to expand...
Click to collapse
It's a very smooth rom, it has fast animations and i love em'
The only thing bugging me right now is battery life drains way faster than what i'm used to. I'll find out more on calibrating the battery/changing kernels etc.
SamsungVibrant said:
You don't have to install via those long instructions anymore. Apparently those are outdated.
Just manually backup your /efs and keep a copy on your computer, just because everyone should have a copy of their /efs folder and nv_data.bin, otherwise if you run into trouble you can lose your IMEI.
Then follow these simple instructions as outlined by user nickmcminn60 for his Lithium MiUi rom, but it worked for the regular MiUi also:
INSTALL INSTRUCTIONS (For Lithium and SS-11 If you are on MIUI, CM-7 or a 2.2)
-Wipe Dalvik Cache
-Wipe Cache Partition
-Wipe Data/Factory Reset
-Format-System, Cache and Data (Located under "Mounts & Storage)
-Flash LE Lithium (EDIT..OR THE STOCK VERSION OF MIUI)
-Fix Permissions
-Reboot and Let Settle For 8 Min
-Reboot again Let Set For 4 Min..
No need to do the longer install process you had mentioned in the prior post.
Click to expand...
Click to collapse
Yeah, thanks, i figured that out.
Any specific kernels you're using for better battery life?
@SamsungVibrant, please how do you backup your /efs? is there a thread you can point me at so I can read it up?
how do i make my phone stop vibranting everytime i get a text message?
belushi7 said:
@SamsungVibrant, please how do you backup your /efs? is there a thread you can point me at so I can read it up?
Click to expand...
Click to collapse
With root explorer, free from market. Enable root within that app in settings. Also enable root with superuser app in tools folder. Then navigate to efs folder copy and paste it.
Sent from my GT-I9000 using XDA App
xriderx66 said:
how do i make my phone stop vibranting everytime i get a text message?
Click to expand...
Click to collapse
It is in settings, sounds.
Sent from my GT-I9000 using XDA App
I always flash MIUI still being on Voodoo and I don't notice anything.
Sent from my GT-I9000 using XDA Premium App
Is it ok to flash with gb bootloaders???
Yup but ur external SD card wont work
Sent from my GT-I9000 using XDA Premium App
From what I have seen Lithium is actually meant to be more of a development ROM for new features. The other ROM made by that developer is the SS series which is meant to be more of a daily driver (eg. more stable), and it has additional tweaks from the official MIUI release to try to achieve things like better battery life as well as a OC or UVable kernel.
SS can be found here:
http://forum.xda-developers.com/showthread.php?t=1099533
and here:
http://forums.miui.us/showthread.php?7067-ROM-SS-11.1-%281.9.30%29-**UPDATED**-10-01-11
Unrelated to the OP, but if you're using Launcher Pro you're missing out on one of the best aspects of MIUI: No App Drawer! Instead you organize your apps into folders on the Home page. It makes you wonder why there ever was an app drawer. Seems like a silly concept now that I've been using MIUI for a while.
Alanrocks15 said:
Yup but ur external SD card wont work
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
not true anymore, can be flashed with GB bootloader.
Sent from my GT-I9000 using xda premium

Gen1 to Gen2 TPT Upgrade

Sorry for the new thread, but I can't post in the dev section yet - this is really a follow up to http://forum.xda-developers.com/showthread.php?t=1258855 - maybe someone can move it?
I just used the following zip file and it worked well:
CM Nightly 257 Version (Upgrades from Gen1 to Gen2 & installs latest CyanogenMod nightly build - all in one)
Download: cm7-n257-blade-gen1-to-gen2-tpt.zip mirror
Download size: 107.8 MB
MD5: 813ba810ca0a596da4eb6ea7e47205a1
SHA1: 11030dff7b48c79463185b25fc848d488fe77768
A couple of things that weren't clear from the Instructions section (which presumably apply rather to the non all-in-one versions - haven't tried personally) were
a) Does not "reboot into ClockworkMod recovery", rather direct into CM Nightly 257, and
b) Wipes data - presumably must have done because the boot into CM was successful.
This is all very good and nicely automated; could just amend the instructions to be something like:
It should take a few seconds to flash the new Gen2 firmware (you should see some green text), then it should either reboot into ClockworkMod recovery, use that to wipe data & then install your Gen2 rom (for the custom and stock versions), or reboot into CM Nightly 257, no need to wipe or install the CM rom oneself (for the all-in-one).
All in all a great piece of work.
New here and also wish i could post on that thread as i found it extremely useful and it persuaded me to make the jump and finally upgrade my San Francisco.
It honestly feels like a new phone now, after running stock orange 2.1 since i got it about 10months back with some tweaks to launcher etc. I wish id done this a lot sooner. I also used the nightly 257 rom.
I was also (initially alarmed!) a little confused about the points a) and b) you raised above as mine also seemed to skip those steps and just launch straight into the mod. All well and good though this has now left me wondering if the step b was vital. Prior to this on a fresh start and after using Advanced Task Killer to kill all the crap id be looking at around 300mb free memory. Since the new ROM i now have 173mb free in Advanced Task Killer. Odd since i dont have a fraction of the amount of stuff on the phone considering all the stuff that came preloaded with Orange etc.
I dare say the new OS may have a larger footprint. Though my main concern is that as I somehow skipped the part where it says
"then it should reboot into ClockworkMod recovery, use that to wipe data & then install your Gen2 rom." I wonder if this means not all the old ROM has been erased and results in my limited memory.
If i check under Settings > Storage it gives me 294 Total with 203 free under internal storage. Wish id thought to check this value prior to install...
That aside it all works great and im delighted with it.
OK, what do you want free memory for? You should realise that is memory that you have paid for which isn't in use - wasted memory in other words. Android 2.3 uses more ram, when nothing else wants to use it, in order to make your phone run faster, that is a good thing. If you want to use an app which requires a lot of memory then android will free it automatically.
Don't use task killers, they harm system performance by working against Android's own memory & task management system (which is better than any task killer), reduce battery life, cause bugs & you wont get any support at all from anybody involved with Cyanogenmod if you use one.
The all in one version that includes a rom starts straight into that rom, that should be pretty obvious.
It will wipe your data, if you're updating from Android 2.1 then it'll wipe everything. Otherwise it'll miss any apps on your sd card, that's the only reason i say to wipe data - if you're coming from stock Android 2.1 then you can't have any apps on your sd card, so it makes no difference.
Stock Android 2.1 phones have 207mb internal storage ( /data) in total, you gain almost 90mb. The stock Orange bloat apps use up more room (dalvik cache) too, so you end up with much more room to install your own apps & games.
Unable to convert Gen1 -> Gen2 via TPT
Hi all,
I didn't want to start new thread, so I'll post here. In short - I'm unable to convert my Gen1 Blade to Gen2 using wbaw's TPT method.
I followed instructions carefully, tried 2 different zips (Gen1-to-Gen2-TPT-v10-custom, cm7-n257-blade-gen1-to-gen2), used 3 different microSD cards (1GB, 2GB, 8 GB class 4) and still nothing.
Image folder is on the card, all MD5s do match, I turn off the phone, wait few sec (I even took the battery out few times), press and hold menu&vol+ and then power, red power led is on, then green robot shows up, and... nothing, no green text on the screen, just few seconds later my Gen1 ROM is booting.
Any ideas?
make sure that you keep holding menu & vol+ when you press power. that's the only thing i can think of, unless your phone is already gen2. a few sd cards dont work with it, but it shouldn't be that hard to find one that does.
Thanks for the answer, wbaw.
I am holding both - menu (the one in the middle, between home and back) & Vol+ - then I press and hold power, after few seconds I let the power go but keep holding the other two. After few another seconds (while green robot is visible) a regular boot animation shows up.
My phone is definitely Gen1, as I recently installed G1 ROM (mmhmp) and previously used Mr. Pigfish, both report Gen1.
I just reformatted my stock Transcend 2GB card in CWM, put only 'image' folder with all files (MD5s are ok) and still no go. What the hell?....
Btw. I'm using 3.0.2.8 CWM. Does it make any difference? I'm running out of ideas.. what else can I check?
No idea then, sounds like you're doing everything right. The flashing should happen before the green robot shows up, if the robot comes up straight away then it's already failed to flash anything & you have to try again. It's a zte flashing program, built into one of the first bootloaders (the green robot is displayed by a later bootloader), you need to be holding vol+ & menu when you turn it on & for about a second after that, then you can let go. You should see some green text, or maybe just a black screen, then after a minute or two a big version of the green robot & clockworkmod 5.
Clockworkmod is irrelevant, it's a different zte flashing process.
Only thing I can suggest is try another sdcard. I know a few people have reported it didn't work with their sdcard, but it was only a few people & it worked with the 2nd or 3rd sdcard they tried. I got a verbatim 2gb with my phone, that works, sandisk 8gb class 2 works too & so does my new 16gb class 10 verbatim.
If everything fails & you must update to gen2, then there are some windows software phone update packages that let you update your phone using your windows pc. Those packages & instructions are in the zte blade section at modaco.com. It's a bit harder, slightly riskier, but hopefully it'll work.
I just tried another card, some noname 512MB from my old Nokia (I didn't even realized I have so many microSD cards...) and unfortunately this one is also no good. Damn....
So, TPT is built-in and should work with all Gen1 ZTE's no matter what ROM or CWM I'm using, right? Is there any possibility I accidentally removed/erased or destroyed part of it?
I didn't even flash that much, from stock Blade (well, I removed simlock), I installed CWM and went to Swedish Spring (half a year ago). Now I've decided to move forward, installed Gen1 MMHMP, but decided to give CM a try. As you can see not much of a history, therefore I'm even more surprised TPT is not working in my case...
Is there a way to tell this flasher actually works? Something other than just putting gen-to-gen converter image? Any troubleshooting you may think of?
Edit: Tried another card (that's already 5th card!!), 8GB class 4 - no go... I don't think it's a problem with microSD card anymore... it has to be something else.
It turns out TPT is not available on my Blade (some European versions lacking TPT were reported). Anyway, I have successfully converted to Gen 2 using Windows/FTM method. I didn't find it hard, it's just a bit more hassle with repeated flashing. All went good, no need to fear.
Thanks!
Hi, sorry to thread hijack the thread hijack, but I too have a question about this process and can't post in the dev forum.
I just followed the all-in-one process on my girlfriend's brand new stock Orange San Francisco, and it worked flawlessly. I'm now wanting to do the same to mine, but it isn't stock; it has ClockwordMod (3.x, I think) and a FlibbleSan ROM from Modaco installed (Gen1).
What (if any) different steps do I have to take to get everything rolling on my own device? Apologies if it's a stupid question, I was just spooked by the parts about not using it on operator upgraded 2.2 devices and wondered if the same disclaimer applied to user updated phones.
(Merry Christmas )
Never mind, I took the plunge and everything works fine.
Random Reboots after Upgrade
Can't post in Dev forum either so posting here.
I had updated my blade last year from Orange stock to JJF, still GEN1.
I followed the all-in-one process to get to GEN2 CM7 build 257 and all has worked well.
The only issue I am seeing now is random reboots every day or so.
Any ideas? Known issue or fix?
eddiem74 said:
Can't post in Dev forum either so posting here.
I had updated my blade last year from Orange stock to JJF, still GEN1.
I followed the all-in-one process to get to GEN2 CM7 build 257 and all has worked well.
The only issue I am seeing now is random reboots every day or so.
Any ideas? Known issue or fix?
Click to expand...
Click to collapse
Have you changed anything under performance tab in CM settings?
Sent from my Blade using XDA app
karthiknr said:
Have you changed anything under performance tab in CM settings?
Sent from my Blade using XDA app
Click to expand...
Click to collapse
No, just done the update?
Sent from my Nexus S using XDA App
eddiem74 said:
No, just done the update?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You did a wipe before flashing right?
Sent from my Blade using XDA app
karthiknr said:
You did a wipe before flashing right?
Sent from my Blade using XDA app
Click to expand...
Click to collapse
There was no option to wipe, it just updated from gen1 to gen2 and booted up after restart from what I can recall.
Sent from my Nexus S using XDA App
eddiem74 said:
There was no option to wipe, it just updated from gen1 to gen2 and booted up after restart from what I can recall.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Ok so I used ROM Manager and installed CyanogenMod 7 V7.1.0 as that is meant to be stable, wiped data/cache/etc via the process.
All was well until I needed to make a call, screen keeps going black and I need to remove battery to resolve?
Any ideas?
eddiem74 said:
Ok so I used ROM Manager and installed CyanogenMod 7 V7.1.0 as that is meant to be stable, wiped data/cache/etc via the process.
All was well until I needed to make a call, screen keeps going black and I need to remove battery to resolve?
Any ideas?
Click to expand...
Click to collapse
Sounds like you need to calibrate the proximity sensor. I think there should be a ZTE Blade settings app that you use to do it.
Probably better to flash one of the latest self-compiled versions of CM7. Its been a while since nightlies were made, but lots of new stuff has been added/fixed since 7.1.0 RCs/stable.
eddiem74 said:
Ok so I used ROM Manager and installed CyanogenMod 7 V7.1.0 as that is meant to be stable, wiped data/cache/etc via the process.
All was well until I needed to make a call, screen keeps going black and I need to remove battery to resolve?
Any ideas?
Click to expand...
Click to collapse
Like Amphoras says calibrate your proximity sensor in the ZTE Blade Settings app. That should do. If you still have a problem,flash the 257 nightly or any other ROM if you don't like CM.
Sent from my Blade using XDA app
this might be a bit offtopic but is there a way to tell from the packaging if the phone has amoled or tft? I suppose tft is best?

have i bricked it??

hi, i have been reading up alot today on how to root and install a rom on my xoom, i rooted it fine then i went to the ics thread and downloaded the latest build, v17... put the zip on the sd card and went into recovery mode, choose to install zip from sd and installed it, then went to reboot device and it rebooted but came to a black screen that says android across the middle, its been on that screen for 20 mins now, help please lol
sorry... sorted problem, im guessing its bcos i wasnt installing google apps from zip too, sorry again
Honestly I have run into the same issues...hold down the volume up button + power...your Xoom should reboot.
Then you see the red Motorola logo wait 3 seconds and hit volume down...you should see "Android Recovery Mode" in the upper left corner.
Hit volume up to select....your device should enter recovery mode.
From here wipe data factory reset...wipe cache partition...then go to advanced...and wipe dalvik cache.
Then go to install zip from SD card and reinstall the ROM and Gapps and you should be fine, the first boot can take up to 10 minutes so don't panic...
XOOM Running Team EOS latest ICS build v.17 OC'd @ 1.5Ghz
Sent from my DROIDX using xda premium
Haha never mind...glad you got it working...disregard my previous post ; )
Sent from my DROIDX using xda premium
Boarder277 said:
Haha never mind...glad you got it working...disregard my previous post ; )
Sent from my DROIDX using xda premium
Click to expand...
Click to collapse
No, don't be sorry. That was a great explanation.
I know you got it fixed but I will say this:
Always do a full wipe when flashing a new rom. In this case, the ICS build was a new ROM and you should have wiped.
Usually you do not need to do a full wipe if you are just flashing a new build of the same ROM (if you go to a new nightly for instance). Just need to clear cache/delvik and reinstall gapps.

[Q] Installing CM7 on Defy+

Hello dear xda community.
I own a Defy+ with 2.3.6 stock Kernel and want to switch to CM7. (Do I need another Kernel?)
Which build do you prefer, I can't decide between:
7.1.0-11
Quarks nightly
Epsylon3s nightly
maniacs nightly
Basically I'm just looking for a stable AOSP/blurfree ROM, so which one is the stablest up to now?
Which of the mentioned ROMS need/work with the battery/camera patches and are there different versions of these patches around? (here and here)
Am I right that there should be no more problems than battery and camera functionality up to now?
Thank you in advance
Edit: Another question I forgot:
In the title of the 7.1.0-11 it is written "Android 2.3.7". So does this mean even though the zip doesn't contain a Kernel it does contain 2.3.7? I couldn't find a 2.3.7 kernel for the Defy+ elsewhere.
Edit 2: I found an answer concerning whether to use 7.1.0-11:
The latest nightlys are stable, don't use 7.1.0-11
Click to expand...
Click to collapse
Though thats a tough statement whenever it comes to nightlys, I assume I will trust him here.
Like I wrote to you (by PM) before, I don't own a Defy+, but I'd say go on and try the latest Defy+ nightly which is from Quarx at this time: cm72-20120308-NIGHTLY-Defy+.zip md5 checksum: 8df5562b60ded2978a38eb9ac21bdc8e .
Make a nandroid backup of your system (custom recovery / advance / backup&restore / backup all) before installing it and then see how it goes from there...
If it really doesn't boot up, you have problems with battery not fully charging, camera or other things, you can find solutions or ask again - but at least you'll have a nand to fall back on... so no risk involved.
I haven't tried that specific March 8th Defy+ nightly yet, but I bet that it is probably at 1 or 2 small fixes close to perfection and you won't regret installing it I assure you.
Just be patient at first boot and wait a good 5-6 minutes before thinking being in a bootloop and do anything crazy..
God luck.
I tried cm72-20120308-NIGHTLY-Defy+.
Wifi is not working ..
and battery yet to check..
also camera prob..
Hi AL
i reinstalled it and now wifi is working..
But the problem now is battery..
It drains off quickly.
Also i used get atleast 50% signal at my home..
but now with this, its not catching the signal at all..
Its fine at places where full signal is there..
Let me recommend CM7 WhiteRabbit Edition 1.3! Pure awesomeness + Aroma touch based installer. This means you can customize your installation (e.g. defy+ battery fix, what apps you want installed, witch wifi driver, etc)!!
Install the PLUS edition for gingerbread kernel!
hafizca said:
Hi AL
i reinstalled it and now wifi is working..
But the problem now is battery..
It drains off quickly.
Also i used get atleast 50% signal at my home..
but now with this, its not catching the signal at all..
Its fine at places where full signal is there..
Click to expand...
Click to collapse
I was using the CM7 for Defy+ 140312 build and everything worked fine for me! Also played all sorts of games like Dead Space, Shadow Gun with ease!
you should try WUIU:http://forum.xda-developers.com/showthread.php?t=1161110
works great!!!!
The whiterabbit version problem
Hey
i did download the whiterabbitplus version as i has android 2.3.6 with kernel also 2.3.6
i rooted it as mentioned using the latest superclick
i theninstalled sndinit 2.0 and attempted to enter recovery but i got the triangle with the xclamation mark so i installed clockworkmod and it got me into recovery alright
here i format cache ,data wipe,factory reset etc and say install "zip from sd card "
auroma installer starts off fine works upto letting me select the options and everything ...just when it says "click next to start " when i do ..it just says
system/mount
error(system/mount) fail or something ...
and pretends its complete and asks for reboot
after reboot i discover no changes and it just acts like a facotry reset too place and i need to configure everything again
ive tried everything on the net ..please do help ..should i flash a lower version like froyo and try again ??
Maniacs builds are great, you should check them out.
Johnny_Queste said:
you should try WUIU:http://forum.xda-developers.com/showthread.php?t=1161110
works great!!!!
Click to expand...
Click to collapse
Sag1e said:
Maniacs builds are great, you should check them out.
Click to expand...
Click to collapse
Please, guys, stop the confusion. Both of those are Froyo only.
@athenus Have you managed to flash any ROM? From those you have mentioned...
CM7.1 - Froyo only
maniac's builds - Froyo only
Epsylon's builds - there are both Froyo and Gingerbread available
Quarx's builds - both Froyo and Gingerbread available <- this should be your choice. The latest Quarx's builds is awesome and you can find it here - http://quarx2k.ru/cm7-nightly-defy+/
P.S. Quarx is currently the only developer that actually owns a DEFY+.
If you are confused still, feel free to PM me, as I can't keep with all the threads I've posted in
hafizca said:
Hi AL
i reinstalled it and now wifi is working..
But the problem now is battery..
It drains off quickly.
Also i used get atleast 50% signal at my home..
but now with this, its not catching the signal at all..
Its fine at places where full signal is there..
Click to expand...
Click to collapse
I might be wrong, but the problems you have described having make me believe that you did not use and set the Defy Baseband Switcher app properly. Am I right/wrong?
Phone carriers around the world do not all use the same radio frequencies to receive/transmit phone signal and after any first install of cm7, you have to use that included app, give it root access, select the baseband that correspond to your location/carrier and reboot. Failing to do so causes bad signal eception, high battery drain and hot phones...
I hope that it was your problem because it will make it very simple to solve for you then.
EDIT: I believe that the baseband can now simply be changed under: Device settings/Baseband selection - no more dedicated app...
Installation failure of CM7 latest Joudan-plus
I hope someone can help me please . . .
Having rooted the phone successfully, and having followed all the relevant instructions (including installing first the various utilities - Titanium, 2ndInit, etc), to upgrade my Defy+ Build 4.5.1-134_DFP-231 with the latest CM7, I copied the CM7 zip to my Defy+ then installed it using 2ndInit - success.
Then, on the reboot, the phone just hangs at the M logo.
After doing the normal recovery, and trying to install again, these messages appear:
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Can anyone suggest what I should do next to recover the situation?
Installing CM7 on Defy+
Following my previous posting, I installed the nightly Jordan plus, from the night before - the only other one available.
That installed without any error message,
However, upon normal reboot, the phone hung at the M logo.
Any ideas please?
INSPEC said:
Following my previous posting, I installed the nightly Jordan plus, from the night before - the only other one available.
That installed without any error message,
However, upon normal reboot, the phone hung at the M logo.
Any ideas please?
Click to expand...
Click to collapse
Wipe data/cache?
Sent from my ATRIX HD using XDA Free mobile app
Installing CM7 on Defy+
Thanks for the response.
Yes, I did first wipe data and cache.
And have tried repeating the installation (including wiping).
Still hung at M logo.
INSPEC said:
Thanks for the response.
Yes, I did first wipe data and cache.
And have tried repeating the installation (including wiping).
Still hung at M logo.
Click to expand...
Click to collapse
Which recovery are you using? The normal one or the one designed for bigpart?
Sent from my ATRIX HD using XDA Free mobile app
Installing CM7 on Defy+
Thanks again for response.
I am using, from the xda posting,
2ndInit Recovery Installer v2.3 [Updated: 24-April-2012]http://forum.xda-developers.com/showthread.php?p=23465603
Installin CM on Defy+
This is an update on a previous posting of mine . . .
It read:
I hope someone can help me please . . .
​Having rooted the phone successfully, and having followed all the relevant instructions (including installing first the various utilities - Titanium, 2ndInit, etc), to upgrade my Defy+ Build 4.5.1-134_DFP-231 with the latest CM7, I copied the CM7 zip to my Defy+ then installed it using 2ndInit - success.
​Then, on the reboot, the phone just hangs at the M logo.​
​After doing the normal recovery, and trying to install again, these messages appear:
​Verifying update package
​E:failed to verify whole-file signature
​E:signature verification failed
​Installation aborted
I have subsequently performed:
Wipe data/Factory reset, then
Wipe cache.
and then trying to install three different version of CM - they are, CM 7 (both of the available Jordan Plus Nightlies), and then a CM 12 from another posting here in XDA.
All three resulted in the 'signature' problem. But the filename of all three files said they were "signed".
So can someone please explain . . . ?
---------- Post added at 02:25 AM ---------- Previous post was at 01:35 AM ----------
I have now discovered the enable/disable signature check . . .
Having disabled the signature check, and repeated all of the steps in my previous posting, and wiping the Dalvik cache, the phone still hangs at the M logo on reboot.
Any suggestions please?
Installing CM on Defy+
Following on . . .
Could this be a Bootloader problem?
I see references to similar symptoms being fixed by unlocking/relocking the Bootloader.
But my understanding, from the Cyanogen Mod website, is that CM looks after this automatically . . .

'fixed brick' - now always have to configure settings after boot

Hello,
bricked my defy a few days ago after rom flashing failed. Phone wasn't booting properly, always showing the big red 'M' letter. Fixed it via rds tool, roms are running again but they don't keep the settings.
After every reboot I have to do systems setup again (language, accout, time). It's like having a wiped phone.
What's going wrong? What can I do?!
Few odds:
- can't wipe dalvik cache in recovery. Something pops up very short, couldn't read.
- cannot install apps. Market doesn't start Download.
...
Flashed my rom+gapps again. This time market tells me there's not enough memory on my phone.
Anything's wrong with my recovery? How do I install a new one? Via sndinit again? Any alternatives?
Hi there,
I had exactly the same problem few days back when I tried to make my phone dual boot and wanted to run CM7.2 as primary ROM and CM10 as a test ROM. Experiment failed miserably and the CM7.2 was wiped out and on top of that CM10 was overwritten as primary ROM. Then the same problem as you. It was going through boot loop and every time I had to start the phone setup.
I had to flash SBF using RSDLite and root it again using superone click.
Then installed the CM7.2 again and then later flashed CM10 Nightly just on top of the CM7.2 with out wiping the data.
CM10 I used was Quarx one from Aug 25th and it works great.
I know I am not that smart but I try stuff so I can experience latest stuff.
Not sure if this helps but, let me know if you need more details.
Regards
Kalyan
Sent from my MB525 using xda app-developers app
In the meantime I found out that /data isn't and can't be mounted...
Maybe you should start again with flashing a stock sbf...
Edit: or check out this :
http://forum.xda-developers.com/showthread.php?t=1787541
Sent from my MB525 using xda app-developers app

Categories

Resources