Related
I was using Bionix-v 1.3.1 since last March, flashed over stock 2.2. I also had Rom Manager Premium V4.3.2.3 with CWM 2.5.2.1.
Recently decided to try out a GB rom. So I downloaded CM7 and MIUI 1.6.24. Tried to flash CM7, but just got a quick CWM screen with boot loop. Somehow using 3 button I could go to CWM screen and flash MIUI 1.6.24.
MIUI booted fine for me. One change I noticed is on power up I get the Samsung Vibrant screen and I new "Galaxy S Cyanogen Mod" screen. After that the MIUI boot animation starts.
Since it does not have GPS support I wanted to try Simply Honey 3.8 Revolution. But when I flashed Simply Homey it goes to Boot Loop showing Samsung Vibrant and then Galaxy S Cyanogen Mod screen. Then I tried other GB rom and got similar result. Only MIUI works and boots fine.
The CWM somehow changed to 3.X.X and it does not accept any FRYO rom having old style (with only update-script) file.
I even can not go to Download mode in any way. ( I have not tried the Jig method yet).
Please suggest any solution if you came across similar situation.
Because u were on a gb rom the way to get into download mode is different for gingerbread roms. Theres plenty of info on that on XDa, sorry dont knowit. But once u get the correct info to get into download mode the gingerbread way then odin to stock and all ur problems will be solved!
movieaddict said:
Because u were on a gb rom the way to get into download mode is different for gingerbread roms. Theres plenty of info on that on XDa, sorry dont knowit. But once u get the correct info to get into download mode the gingerbread way then odin to stock and all ur problems will be solved!
Click to expand...
Click to collapse
Thanks for your response.
I have never flashed GB rom using odin, only thing I tried is flashing CM7 using CWM. Does it automatically update the bootloader? If it does, why every other GB rom goes to boot loop?
You got a bootloop on cm7 because its a known bug, if you tried to install it again it would install just fine. You can go between miui and cm 7 easy outer roms are not comparable. I would like to know too if they install a custom bootloader, when you odin you need too install a bootloader too? That could be risky, that why i am scared to odin back.
Sent from my T959 using XDA App
hi all,
im new here and i would like to ask for a link for the most stable and fast ROM... i know many of members here already posted this kind of request and i've read some of them but still i think chose the wrong one.. i tried to install the floyo ROM on my x8 last week... on the first two days its ok... but when i tested the wifi, the browser is malfunctioning so i tried to reboot the phone... after that, the system suddenly crashed and some of the apps like launcher failed to initialize... i can't even see the menu that time and the phone always displays the "force close the application"... i thought that i will not be able to use my phone again but thanks to flash tool which i also got here...
i also want a ROM with multi touch... and please the most stable.... if there are some tips and reminders in using custom ROM's to minimize this errors that i've experience please give me a list... i still need a lot of info in modifying my x8... thanks guys!!!
Nearly all 2.2 ROMs are stable, and if you want Gingerbread, use GingerDX or MiniCM7 (I´d recommend you GingerDX).
You can also use KuyaDroid, but I did never use it and so, I don´t really know how fast and stable it is.
All those three have a fully working camera.
My tip is that you do a full wipe before installing ANY new ROM, to avoid those errors you had.
Like codfreak, I also recommend you GingerDX 010, very stable and fast.
If you are lucky to have a Cypress digitizer on your X8 you will get multiTouch.
This is my recommendation
Froyo/cm6:Froyobread because is Final
Gingerbread/cm7:GingerDX is most stable cm7 for daily use
More description Here
Froyobread most stable rom ..or u can also try floyo 0.30 ..its stable as well..atleast for me..
I think the GingerDX v.6 i currently use on my phone is very stable. I know v.10 is out there but right now im to lazy to do a full wipe and so on. The only problem i had was when i first did the installation from stock 2.1. to GingerDX v.6. I did not do a full wipe before the installation and the phone did hang at the CM logo.. I rebooted and did a full wipe. Since then the phone has been rock solid. Everything i have tried on my phone works. One minor bug is that when the battery is realy empty (as in: the phone closes itself) the X8 recovery comes up the next time the phone is started. When i do a reboot in the recovery-program a "master pin code"- question is popping up. I just click never ask for this again or something like that and after that everything is fine..
I´m very happy with the GingerDX!
tripaX8 said:
My tip is that you do a full wipe before installing ANY new ROM, to avoid those errors you had.
Like codfreak, I also recommend you GingerDX 010, very stable and fast.
If you are lucky to have a Cypress digitizer on your X8 you will get multiTouch.
Click to expand...
Click to collapse
Hi... i have a new problem... i updated my phone yesterday using pc companion to restore its original ROM because it was bricked last week... then i rooted it and installed the busybox, root folder and xRecovery.. i wanted to test this "STABLE ROM" on my x8..
http://forum.xda-developers.com/showthread.php?t=1036335
so i installed it using xRecovery.... i tested everything and it was great... i installed some app and games on it and tried to transfer the installation using app manager to save some phone memory... i also installed the launcher pro...
i reboot the phone to see if the xrecovery is working for backup if ever i encounter an error again using the ROM... and its working...
the last thing that i did was testing its wifi... its already in obtaining ip status... but its always disconnecting and after several disconnection, the phone reboot and suddenly its showed a message that "the application DSPmanager has stopped unexpectedly" (can't remember the exact message) and telling me to "force close" it... i rebooted the phone several times but it always shows that message... so i tried to access the xRecovery but it doesnt appear and i tried it many times....
is there something wrong on my installation process?? or this is just a bug of that ROM??? i've read some feedbacks on that thread but i didn't see a wifi problem on others and "the application DSPmanager has stopped unexpectedly"...
i just dont know why can't i access the xRecovery... PLease Help me T_T]
Thanks a lot for the feedbacks guys!!!
for me, the stable rom is minicm, it's standard
but i like feature on GDX/Froyobread
Hi mikel_0004 If you still can boot your phone, why don't you re-install xRecovery? and then restore a backup...
If your ROM was working BEFORE you started installing apps, then the problem should be some app you installed OR uninstalled, Did you uninstall any system app?
...tried to "transfer the installation" using app manager to save some phone memory...
Click to expand...
Click to collapse
are you talking about SystemAppRemover ? what did you "transfer" ?
About DSP manager, you can safely delete that app from /system/app with root explorer. (I read it has problems if you are using kickass module)
@mikel_0004:
If you have your ROM's backup, you can try to flash back to stock ROM, re-root and re-install xRecovery. after that, restore your backup.
Hi Guys and Girls, I hope this is the right place for my question. Sorry if I sound like a 12-year old - my english is not really the best...
I own the Motorola Defy+, and I tried to get rid of motoblur. I installed SndInit 2.0, did a reboot, did a backup, did factory reset, wiped dalvik cache and picked the miui-rom I had previously placed on my SD. The installation went pretty good, my phone told me that it finished the installation and I did another reboot.
After the reboot I get the red M (default Motorola-logo just like before I was meddling around with the phone) but just for a very short period of time and then I get a black screen with white letters (slightly out of proportion) saying:
Bootloader
09.10
Err:A5,70,00,00,23
Battery OK
OK to Program
Transfer Mode:
USB
When I remove the USB-cable the last two lines are replaced by:
Connect USB
Data Cable
Do you guys have any idea, how I could get MIUI, CM or anything else running on my phone again? I'd even be quite happy to have the stockrom running again, since a phone with ****ty motoblur is still better than no phone at all.
I'd be really grateful for any kind of help, thanks in advance.
The miui you installed was for defy or defy+? And , can you access to recovery?
Motorola Defy CM7 RC 1.5 OC 1GHz
You have forgot to do 2 things. this might be the problem .
Do:
1. Factory reset.
2. wipe data cache.
3. wipe dalvik cache.
4.install MIUI rom.
5. wipe once again data cache.
6. reboot.
If you can access recovery again . my guess you can..
Thank you guys for taking care of me!!
@LeonardoJegigzem
The MIUI is called miui-ger_DEFY_1.12.23_FULL_EN_DE.zip - it's for Defy but I've read in forums that it should run on Defy+ aswell.
@VoLtrex31
I can't access recovery (I'm assuming you're talking about the "push volume-down when blue LED turns on"-recovery?), the screen I described in OP appears right after the red-M shows up for the first time.
You are right, I didn't wipe data cache neither before, nor after the installation.
Thats not good.
Search in the forums for how to access the recovery via your computer..
This might be your only way.
Ask more forums for technical help since xda is not the best forum for asking for help.
because i am not an expert .
But don't worry i bet many people got that problem too so there is a solution .
at last you have stock recovery(i think)
to access it (on defy) ress and hold VOL DOWN and power button.
Than after(about 10 sec) you'll get an exclamation mark.
Now press VOL UP and DOWN at the same time and you can wipe data.
If phone boots up perfectly yo can reinstall 2ndinit.
If not.. i think that you have to flash the appropriate sbf via rsd lite.
buruss said:
at last you have stock recovery(i think)
to access it (on defy) ress and hold VOL DOWN and power button.
Than after(about 10 sec) you'll get an exclamation mark.
Now press VOL UP and DOWN at the same time and you can wipe data.
If phone boots up perfectly yo can reinstall 2ndinit.
If not.. i think that you have to flash the appropriate sbf via rsd lite.
Click to expand...
Click to collapse
Now that's great news - the folks at motorola seem to know that ppl want to avoid ****ty motoblur and **** up their phones so they built an easy way to rescue broken phones.
I will try that asap - right now I'm using an old sony ericsson Xperia X8 - want my Defy+ back!
Thanks buruss!
Hi guy,I know about what you talking.
1. everytime i stuck on "white letters" i recovered my defy+ with RSDLite and correct SBF file.
2. If you have 2.3.6 version of stock rom,miui or any common cm7 won't work - afaik. You must downgrade (somewhere is topic about it) or use cm7.2 or cm9
Sent from my MB526 using XDA App
mikrom.cz said:
Hi guy,I know about what you talking.
1. everytime i stuck on "white letters" i recovered my defy+ with RSDLite and correct SBF file.
2. If you have 2.3.6 version of stock rom,miui or any common cm7 won't work - afaik. You must downgrade (somewhere is topic about it) or use cm7.2 or cm9
Sent from my MB526 using XDA App
Click to expand...
Click to collapse
Yea, I 've been through the same today/yesterday, and after a lot of cursing I can tell you it is exactly like this T.T you have to re-flash the stock ROM 2.3.6 again, and then if you find a way to downgrade/install Miui-CM/basically anything than staying with the stock ROM, let me know! xD
Just relax, I'm telling you this because yesterday I could have killed a dragon with my bare hands, but a soft brick is NP, as long as RSDlite recognizes your phone you can always going back to safety, from what I've learnt hard bricking a Defy is veryveryvery hard, thanks/due to a locked boot loader
Hey Guys, first let me thank you! I'm feeling quite happy now knowing that I'm not the only one with this kinda problem and I'll try the RSDlite-rescue-mission in a few days.
Happy new year everybody!
mikrokosmonaut said:
Hey Guys, first let me thank you! I'm feeling quite happy now knowing that I'm not the only one with this kinda problem and I'll try the RSDlite-rescue-mission in a few days.
Happy new year everybody!
Click to expand...
Click to collapse
I guess it's inevitable, when you start trying this and that custom ROM, sooner or later you're going to screw it up xD but it's actually good when that happens, because you know 100% you can fix everything - you did it once, you'll do it again
Happy new year!
miui uses the 2.2 froyo as base, since all the defy plus have gingerbread miui wont boot, miui hve boot.img and davtree.img in the rom.zip, if you flashan old boot.img in to a newer defy plus with new bootloader(2.3.6) you get an error, ho to fix it, try deleting the boot.img and devtree.img from the zip and replace the 2.3.6 boot.img and devtree.img form 2.3.6 and add it to the zip( miui rom) and try to flash it again and see if it works
You guys are awesome! Phone is booting again
installed RSDlite 5.3.1
downloaded the latest .sbf for my phone and my provider
let RSDlite do its magic and now everything's working just fine.
Next thing to do - try again to get rid of motoblur!
It's not 100% true, I installed MIUI over my 2.3.4 Gingebread and it worked like a charm
Only problem is, I can't install it anymore now that I'm on 2.3.6, but 2.2 is not strictly needed, 2.3.4 worked as well
Hey, guys! I have the exact same problem. I tried to install a Galnet MIUI ROM over at galnetmiui.co.uk, and i messed it up. I didn't really know what i was doing. Perhaps i forgot to wipe cache after installation. Have the exact same error message as mikrokosmonaut.
I was running my mb 256 with android 2.3.6, as far as I know, i have to use RSD Lite to istall stock rom again. Where do I find the correct SBF? My phone was bought without a service provider subscribtion, so I have no clue where to find the right SBF. I have no objection against having blur on the phone.
Can anyone help?
hi guys!!
i've tried to install miui on my defy+ 2.3.6.. like i read on this thread i modified the .zip file changing the boot.img and devtree with the original one.
but mt defy can't boot.. stuck at motorola logo..
what can i do?? does anyone managed to install miui on a defy+ 2.3.6?
now i'm using cyanogen and it works fine, but i prefer miui
thanks!!
daede86 said:
hi guys!!
i've tried to install miui on my defy+ 2.3.6.. like i read on this thread i modified the .zip file changing the boot.img and devtree with the original one.
but mt defy can't boot.. stuck at motorola logo..
what can i do?? does anyone managed to install miui on a defy+ 2.3.6?
now i'm using cyanogen and it works fine, but i prefer miui
thanks!!
Click to expand...
Click to collapse
I don't think MIUI work on 2.3.6. you need CM7.2, or maybe some latest nightly version of MIUI
mikrom.cz said:
I don't think MIUI work on 2.3.6. you need CM7.2, or maybe some latest nightly version of MIUI
Click to expand...
Click to collapse
thanks for your reply! indeed i'm using cm 7.2.. it works pretty well, except some delays! never heard about miui nightly! i did a research on google but i couldn't find anything.. any idea??
thanks again!
hi again!
i was thinking.. you said miui shouldn't work on 2.3.6 and i guess you are right! so if i do the same thing i did (change the boot and devtree file in the latest miui.zip that is 2.3.7 if i'm not wrong) but using files from android 2.3.7?
maybe i try to explain myself better..
i make a nandroid backup of my cm 7.s2 which is 2.3.7.
then i change the files boot and devtree from cm 7.2 to the latest miui.
should it work? what do you think?
thanks again
Hi, folks! *GREAT NEWS!*
Some guys over at the devs section on the thread below have found a froyo sbf with bootloader 6 (the same as the defy 2.3.6 sbf)!!! This means we can use it to downgrade to froyo and install MIUI over it!
http://forum.xda-developers.com/showthread.php?t=1486731
I haven't tried it yet, but will flash later today or tomorrow. You should read through some of the posts and decide for yourselves if you want to try or not.
All the best!
-If I managed to help you in any way, please press the thanks button!
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 . . .
Hello, my problems started when switching from CM10.2 to try out a CM7.2 based ROM that was a stripped down version of MokeeOS. I disliked it so I then flashed the original CM7.2 and everything seemed fine, however I missed the app support of Android 4.2.2+ and decided to go back to CM10.1.
For some reason my phone switched off during the flashing of CM10.1 (Quarx's 9th of July build) and was screwed. I pulled up RSD Lite and went to flash an SBF and start again. I used this SBF [DEFYPLUS_U3_4.5.1-134_DFP-231_AU_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRANZ_P021_A030_Service1FF.sbf] Everything was fine and everything worked. I then went on to root the device so I could install CM10.1 and noticed I had trouble rooting with SuperOneClick. It always hung step #7 which said something along the lines of "cannot mount, are you root?". I hesitantly tried an APK based root called Farmaroot which surprisingly worked which then allowed me to install 2nd init recovery. Here's where it gets weird. I flashed CM10.1 and the corresponding version of GApps and rebooted and everything seemed fine. However the first thing I noticed is that it only asked me for my Google Account, not the device language or which Network I should connect to, I thought nothing of it for some reason and continued thinking everything ok. However I then noticed that the notification slider and the quick settings menu were both inoperative, no notifications or tiles could be seen. Pressing the home button did not work, nor did long pressing it to show currently open apps.
I reflashed CM10.1 using TWR and had the same problem. I then flashed CM10.2 and another version of GApps and had the same problem.
Is this a problem originating from the fact I could not root the device to begin with? I am pretty sure I also tried this SBF
[DEFYPLUS_U3_4.5.1-134_DFP-1321_AU_SIGN_SIGNED_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRANZ_P020_A026_HWp3_Service1FF.sbf]
Where should I go from here? I'm currently in exam period so I am unable to extensively search for answers or mess around. The device is currently wiped.
I'm using a Defy+ by the way.
Thanks.
Defy+ can't be rooted by SuperOneClick. And I had those issues earlier. I tried a different gapps and it worked. Search and use TJKV's minimal gapps (in the General section).
hotdog125 said:
Defy+ can't be rooted by SuperOneClick.
Click to expand...
Click to collapse
Really? It's what I used to root it every time until now.
hotdog125 said:
I tried a different gapps and it worked. Search and use TJKV's minimal gapps (in the General section).
Click to expand...
Click to collapse
Oh wow this actually worked. Thanks!
woofdog said:
Really? It's what I used to root it every time until now.
Click to expand...
Click to collapse
That's not possible:laugh:
Framaroot method doesn't affect anything. Looks like some leftover data files to me
Sent from my MB526 using Tapatalk 2