Hello Guys,
I am in a serious problem which i am not able to solve since long time. I am facing a serious issue in my Motorola Defy+ / Mb526. I was running cm 10, then i flashed my phone once, then i tried to root it once again but i was getting "read only file system error/ No root permission error". But now even after flashing my phone my previious data is also not erased. I am not able to root it. I searched a lot but i'm not getting any answer so i started a new thread. Please help me to root my phone without which it is useless,...............emergency.........:crying::crying:
Which cm10 build do you use?
Cm10 is usually rooted
Sent from my MB526
juli9797 said:
Which cm10 build do you use?
Cm10 is usually rooted
Sent from my MB526
Click to expand...
Click to collapse
My phone was rooted at that time running JB 4.1.2. After that i flashed my phone so i lost the root permissions,then i tried to root it again and got the errors.
What did you flashed after that?
The 1204 build does nothave root permissions it is a known bug.
Sent from my MB526
Is there any solution for that
Sent from my GT-S5830 using Tapatalk 2
I think you 2 are in a misunderstanding here...
Viraj, have you flashed a stock, Motorola ROM?
Whatever is the case, you should have been more specific in the first post
Related
Hi all, I've been reading DEV section for few months by now, in order to get confident in getting CM10 on my defy+.
Yet, I haven't well understood wether my current configuration will ease the process or not.
Would someone kick in with very appreciated info?
Here's my current setup:
defy+ with stock 2.3.4
kernel 2.6.32.9
build 4.5.1-134_DFP-89
the phone has been rooted with SuperOneClick, and has 2ndInit v.2.3 installed.
I have access to bootmenu, and have already performed a "backup all".
I've heard rumors about BL5 systems not being straigtforward to be flashed with CM10.
Neither is available a FullSBF for this particular version of android for me to restore the phone as it was when I bought it (so I'm a little worried).
Thanks in advance, manuele
Try directly flashing cm10 first, wiping data and dalvik cache first. Then sometimes cm10 may reboot once without loading up fully, so just let it be. If still stuck then flash dfp 231(your region/carrier one) and repeat above steps
Sent from my MB526 using xda premium
This sounds like trial&error, tnx anyhow. I will be more specific with my question:
is it possible to operate CM10 in defy+ from a BL5 stock?
Some people have, some people couldn't. I understand your question but it is a probability at best
Sent from my MB526 using xda premium
After updating the latest KtManta kernel my nexus 10 lost its root capabilities, super user won't just work, it is just me or it is a known issue?
I've flashed the December version of the kernel afterwards and the problem prevails (ktoonsez doesn't include every kernel download link, a bad practice in my opinion)
I am on CM now and everything is working fine, I wonder if anyone has been victim to this weird issue
Sent from my Nexus 10 using Tapatalk HD
zombiegenerator said:
After updating the latest KtManta kernel my nexus 10 lost its root capabilities, super user won't just work, it is just me or it is a known issue? ...
Click to expand...
Click to collapse
I am guessing but is this a permissions issue? I've flashed KTManta a number of times including just yesterday with TWRP and never had the issue you describe. Occasionally, right after flashing a ROM or Kernel, I have seen from TWRP a "Fix Permissions" message which I always execute. Some custom ROM/Kernels flash instructions even include a "Fix Permissions" instruction.
Also sometimes after flashing then rebooting I've had to "reinstall" Superuser so it can grant root permissions to various programs. As a habit, right after a new flash, I start Superuser once just to see if it says it needs to be reinstalled. This is not a reinstall from an apk but is a dialogue message displayed when the app is started.
As I wrote this is purely a guess on my part.
I had a laugh at the thread title. (sorry) You either have a corrupt download or something else really weird going on. A kernel wont remove root from your unlocked firmware and ROM files unless the flashing script is actually programmed to remove the files needed. Which its not.
Well this is strange, because I have fixed the permission issue and wiped cache and dalvik, not once but multiple times (I set up the kernel thrice, after it was malfunctioning).
But seeing you two replying, I set up KtManta over CM today and it is not giving me a bit of trouble, strange indeed.
btw, is it true that KTManta fixed the color issue a bit?
Yes it does fix the color a little bit.
What ROM were you on that you had this problem?
EniGmA1987 said:
Yes it does fix the color a little bit.
What ROM were you on that you had this problem?
Click to expand...
Click to collapse
Stock
Sent from my Nexus 10 using Tapatalk HD
zombiegenerator said:
Stock
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
It won't cause you to lose root but it is also not really designed to use with stock either. Most if not all custom kernel users are on CM, AOKP or AOSP ROMS.
brees75 said:
It won't cause you to lose root but it is also not really designed to use with stock either. Most if not all custom kernel users are on CM, AOKP or AOSP ROMS.
Click to expand...
Click to collapse
What's the difference between AOSP and stock roms?
And yes it's now working flawlessly with CM.
Sent from my Nexus 10 using Tapatalk HD
I didn't want to post this in development... to be brief, I had a Defy during the CM7 days, then I gave it to somebody else and didn't follow the Defy threads when CM9 went out. As such, I do not know how it was possible to boot a different kernel.
Unless I got it all wrong, in CM10 Quarx is working on a modified 2.6 and a 3.0 kernel, which wasn't something deemed possible due to the locked bootloader and missing Motorola signing key. What changed?
Czehop user from milestone thread has booted last year in September a custom kernel with the old method 2ndboot but he achieved to boot with the radio. The old 2ndboot method was but without radio (phone).
Sent from my MB526 using xda app-developers app
I just tried fixing my Defy for the last couple of days before giving up, and now I'm stuck
This is what I've done so far (skip to the question in the end if you don't care):
Flashed the fixed SBF: JORDN_U3_97.21.51
SuperOneClick'd and wipe all data & cache using SndInitDefy_1.4_2
Tried flashing many other SBF's like: JRDNEM_U3_3.4.3-11_BLUR_SIGN... and JRDNEM_U3_3.4.2_179-6.1_BLUR_SIGN...
Installed CM7 and GApps
Recovery from old ClockWorkMod recovery file
So far none of the other SBF's are working,
and when I use the fixed one I get all sorts of system errors, before and after installing CM7
I've read that it is possible that I've used a Defy+ and need to use DFP-231 to fix my Defy as descrived here:
http://forum.xda-developers.com/showthread.php?t=1542956
Is it safe to use this method? Is it any good in my case?
Using the All-in-One guide I realized that the fixed SBF only works with conjunction with a Nandroid backup
I didn't use Nandroid before, and couldn't find images for download
Can you please link to a CM9 or CM10 images? (the more stable the better)
Thanks!
If you're going to use cm 9,10,10.1,10.2 then you can go ahead and use dfp231. Use framaroot apk to root and 2ndinit apk
Check development thread for each rom for latest image
Sent from my MB526 using Tapatalk 2
thekguy said:
If you're going to use cm 9,10,10.1,10.2 then you can go ahead and use dfp231. Use framaroot apk to root and 2ndinit apk
Check development thread for each rom for latest image
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Will try that and post results!
It worked!!!
But now I need the: "ICS Battery Fix" (I have the Defy- with red lens)
I tried searching online for it, but the results are not clear
Were can I get it from?
After a night of usage the battery drains quickly, and the system is laggy.
Any ideas?
Use a newer rom cm10 or cm10.1,10.2 those are better in opinion.
Sent from my MB526 using Tapatalk 2
some roms have that issue but not all of them. install the latest 10.2 from quarx. super fast and super stable.
thekguy said:
Use a newer rom cm10 or cm10.1,10.2 those are better in opinion.
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
What about the ics battery fix? Where can I get that?
And is there a way to upgrade without overriding apps and user settings?
Hi,
After installing PARANOIDANDROID following this post . The baseband isn't recognised inside PA, so i tried to flash it after the rom but no change. I read a lot about loosing the Partition where the IMEI is stored an got really scare xD After unroot and going back to stock Rom everything is fine. So PA didn't recognise either the partition or the baseband ? Am I doing anything wrong because in no faq was my problem explanded or mentioned.
Sorry for my bad english.
Regards,
Zardorac
nobody ?
You most likely did not do anything wrong, I've been seeing a lot of issues lately with the radio after people flash PA 3.99. I had an issue too last time I installed PA where my radio stopped working completely no matter what the ROM, and I wound up having to use the LG download tool to fix it.
Sent from my Nexus 4 using xda app-developers app
so best option wait for next release or is there any other option.
Regards,
Zardorac