Related
Moto E 2015 LTE
I have to open a new thread, after everything went ok considering the camera for many hours, it again stopped working after restore.
What happened? I made a backup with TWRM and rebooted my phone, a message from SuperSu appeared that the binaries have to be updated, but this message disappeared as fast as it appeared. So I could not do anything. A hint was shown at the display to DOWNgrade! the google playstore. I installed a very early version of playstore 3.1 and rebooted. But the camera continued to stop working...is busy etc... I do not want the get rid of root access, all the rest of the apps are working without problems. Do we have to wait for another version of SU? A total unroot gives back the full functionality of the cam. But certainly I do not want to do this. It seems to be a problem with android 5.0.2 hxxps://play.google.com/store/apps/details?id=com.motorola.camera&hl=de or even motorola. But why does it work without SU?
Camera is working again after deleting cache, stopping the programm, wiping the dalvik (I did it but I am not really sure if it is necessary, have a try) and rebooting. So it is definitely not an hardware issue. So we have to wait for an update working with Android 5.0.2 as they have had several problems with their camera app before regarding other smartphones . Thanks Motorola
Greets
RioGrandeBlood said:
Moto E 2015 LTE
I have to open a new thread, after everything went ok considering the camera for many hours, it again stopped working after restore.
What happened? I made a backup with TWRM and rebooted my phone, a message from SuperSu appeared that the binaries have to be updated, but this message disappeared as fast as it appeared. So I could not do anything. A hint was shown at the display to DOWNgrade! the google playstore. I installed a very early version of playstore 3.1 and rebooted. But the camera continued to stop working...is busy etc... I do not want the get rid of root access, all the rest of the apps are working without problems. Do we have to wait for another version of SU? A total unroot gives back the full functionality of the cam. But certainly I do not want to do this. It seems to be a problem with android 5.0.2 hxxps://play.google.com/store/apps/details?id=com.motorola.camera&hl=de or even motorola. But why does it work without SU?
Camera is working again after deleting cache, stopping the programm, wiping the dalvik (I did it but I am not really sure if it is necessary, have a try) and rebooting. So it is definitely not an hardware issue. So we have to wait for an update working with Android 5.0.2 as they have had several problems with their camera app before regarding other smartphones . Thanks Motorola
Greets
Click to expand...
Click to collapse
this is already a known issue when you flash twrp and root. its kinda hit and miss for users.
fix-this! said:
this is already a known issue when you flash twrp and root. its kinda hit and miss for users.
Click to expand...
Click to collapse
I did not know this. Extracted the recovery img from stock rom and the camera is working.
Would you please give me a hint if any cwm working for moto g g2 and x should be working on our phone?
RioGrandeBlood said:
I did not know this. Extracted the recovery img from stock rom and the camera is working.
Would you please give me a hint if any cwm working for moto g g2 and x should be working on our phone?
Click to expand...
Click to collapse
No idea if there is a cm recovery yet. So maybe its twrp that messes up the cam.
There is no clockwork recovery, hopefully a dev can port it.
Is the camera breaking a stock camera thing, or all cameras? Like if the stock doesn't work would downloading the Google camera from the Play Store work?
bobbyphoenix said:
Is the camera breaking a stock camera thing, or all cameras? Like if the stock doesn't work would downloading the Google camera from the Play Store work?
Click to expand...
Click to collapse
Did you try? I have not, because now stock camera works, after update after rebooting. I wonder how long will it work and what happens next...
RioGrandeBlood said:
Did you try? I have not, because now stock camera works, after update after rebooting. I wonder how long will it work and what happens next...
Click to expand...
Click to collapse
Not yet. I haven't rooted yet because of this bug. That's why I asked if anyone has tried a Play Store camera while the stock one doesn't work.
Sent from my MotoE2(4G-LTE)
bobbyphoenix said:
Not yet. I haven't rooted yet because of this bug. That's why I asked if anyone has tried a Play Store camera while the stock one doesn't work.
Sent from my MotoE2(4G-LTE)
Click to expand...
Click to collapse
Thats broke to, any camera will be. To fix it download root explorer, go to system/app/supersu and rename the apk to .bak. Reboot, your not totally unrooted and the camera will work.
A perm fix will be when moto releases our kernel source and we can compile a kernel with selinux set to off or permissive.
Whatever I do, delete SuperSU or not, delete TWRP or not, after any reboot the camera starts working, then after the next reboot it stopps working, after the next reboot it is working again. Even with working and not renamed SuperSU
What the hell is this?
Renaming does not work better or less.
Could you post the output of running this after you try to use your camera and it doesn't work:
Code:
adb shell su -c dmesg | grep denied
This may help identify the cause of problems if SELinux is to blame. Tonight, I will build and post a kernel with SELinux disabled to see if that fixes anything.
Alright, I built a kernel with SELinux disabled. Apart from that, the source code is straight from the Motorola GitHub.
This is for Styx LTE (surnia) only! Flash at your own risk. I am not responsible for bricking your device, causing damage, bodily harm yada yada.
http://filebin.ca/1v4FfHSxMtX3/surnia_boot_noselinux.img
To install it, go into fastboot and run
Code:
fastboot flash boot surnia_boot_noselinux.img
This kernel is probably missing a bunch of stuff, and it breaks Bluetooth and WiFi. The camera should work though. Try it out and see if it changes the behaviour of the camera. Once you're done with it, you can return to the stock kernel by flashing the stock boot.img.
adb shell su -c dmesg | grep denied
Thanks, I will try, but time is the problem right now.
I was a bit too fast, camera seems to work after renaming SU.apk into bat.
squid2 said:
Could you post the output of running this after you try to use your camera and it doesn't work:
Code:
adb shell su -c dmesg | grep denied
This may help identify the cause of problems if SELinux is to blame. Tonight, I will build and post a kernel with SELinux disabled to see if that fixes anything.
Click to expand...
Click to collapse
Not sure you can modify the kernel since we have no source yet.
fix-this! said:
Not sure you can modify the kernel since we have no source yet.
Click to expand...
Click to collapse
We do have the source. It's on Motorola's GitHub. It was posted right when the phone was released. Yesterday, I built a kernel with SELinux disabled and posted it two posts above yours.
EDIT: Kernel source link
After renaming SU into bak I later renamed it into the original apk. version to see what will happen. And in fact nothing happens. . Camera is working for days now after several rebootings. TWRP is working great and has no issue on the camera. Thank you fix-this!
squid2 said:
Alright, I built a kernel with SELinux disabled. Apart from that, the source code is straight from the Motorola GitHub.
This is for Styx LTE (surnia) only! Flash at your own risk. I am not responsible for bricking your device, causing damage, bodily harm yada yada.
http://filebin.ca/1v4FfHSxMtX3/surnia_boot_noselinux.img
To install it, go into fastboot and run
Code:
fastboot flash boot surnia_boot_noselinux.img
This kernel is probably missing a bunch of stuff, and it breaks Bluetooth and WiFi. The camera should work though. Try it out and see if it changes the behaviour of the camera. Once you're done with it, you can return to the stock kernel by flashing the stock boot.img.
Click to expand...
Click to collapse
tried to flash on my lte model us based gsm. just kept booting back into fastboot until i flashed my stock boot.img. you may wanna talk to chainfire to see if it would be better to make it set to permissive instead of fully disabling selinux.
---------- Post added at 09:11 PM ---------- Previous post was at 09:11 PM ----------
squid2 said:
We do have the source. It's on Motorola's GitHub. It was posted right when the phone was released. Yesterday, I built a kernel with SELinux disabled and posted it two posts above yours.
EDIT: Kernel source link
Click to expand...
Click to collapse
i didn't know that.
---------- Post added at 09:13 PM ---------- Previous post was at 09:11 PM ----------
RioGrandeBlood said:
After renaming SU into bak I later renamed it into the original apk. version to see what will happen. And in fact nothing happens. . Camera is working for days now after several rebootings. TWRP is working great and has no issue on the camera. Thank you fix-this!
Click to expand...
Click to collapse
its hit or miss for me. sometimes the cam works sometimes it doesn't.
fix-this! said:
tried to flash on my lte model us based gsm. just kept booting back into fastboot until i flashed my stock boot.img. you may wanna talk to chainfire to see if it would be better to make it set to permissive instead of fully disabling selinux.
Click to expand...
Click to collapse
Thanks for trying it. I'm not surprised that it didn't work. The quick hack of a boot image I posted is missing the device tree, and it will also fail to load all kernel modules due to a version mismatch. I had tested it on the unit I had at hand, and was shocked that it was able to boot and function without a device tree image, but the hardware I used is a bit different than what you have. I've ordered a production device, and it will hopefully arrive this week. Then I will be able to test properly.
I've been working on setting up proper build infrastructure to build working kernels for surnia (complete with compatible driver modules, device tree images etc). I'm hoping to publish an initial release of my kernel for surnia over the next week or two. My initial release would probably be largely the same as the stock kernel, and then I'll start adding improvements from there.
I think you can make SELinux permissive from boot without recompiling the kernel by simply adding androidboot.selinux=permissive to the kernel command line arguments in boot.img. If anyone wants, I can make such an image using the stock kernel. I don't have a suitable device to test with at the moment though.
squid2 said:
Thanks for trying it. I'm not surprised that it didn't work. The quick hack of a boot image I posted is missing the device tree, and it will also fail to load all kernel modules due to a version mismatch. I had tested it on the unit I had at hand, and was shocked that it was able to boot and function without a device tree image, but the hardware I used is a bit different than what you have. I've ordered a production device, and it will hopefully arrive this week. Then I will be able to test properly.
I've been working on setting up proper build infrastructure to build working kernels for surnia (complete with compatible driver modules, device tree images etc). I'm hoping to publish an initial release of my kernel for surnia over the next week or two. My initial release would probably be largely the same as the stock kernel, and then I'll start adding improvements from there.
I think you can make SELinux permissive from boot without recompiling the kernel by simply adding androidboot.selinux=permissive to the kernel command line arguments in boot.img. If anyone wants, I can make such an image using the stock kernel. I don't have a suitable device to test with at the moment though.
Click to expand...
Click to collapse
Yes fix-this, my camera stopped from working again after using a root cleaner (fixed permissions here-is this the problem?) and rebooted the device. But as squid2 wrote/suggested, the problems (permissive) do not seem to be too severe and could be solved in the near future. It seems to be just a matter of time. At this point I strongly recommend the installation of TWRP. I got a functioning camera back and it helps while working on our handy, TWRP does not seem to be the problem so better install it and keep it working. It helped me a lot. Greets
squid2:adb shell su -c dmesg | grep denied
I did it, but got the message grep written wrong/not found
Root and S-Off Recommended
For S-Off look here then follow directions for permanent root in the development forum
1. Download a file explorer with root-browsing capabilities like Root Explorer or ES File Explorer from the Play Store
2. Using the file explorer you downloaded above, head over to /system/customize/ACC folder and open the default.XML file using any text editor.
3. Navigate to the following code near the bottom of the file:
<app name=”Tethering_provision”>
<item type=”integer”name=”TetheringGuard_rule”>3</item></app>
Notice the “3” above in bold. Change it to “0.” Save the edited text file and exit the app.
4. Reboot
Go into settings, enable WiFi Hotspot and it'll turn on. I did this on my At&t Desire 610, I assume other carriers can use the same method.
If Hotspot fails to initialize after being turned off, reboot your phone. I only came across this problem once.
Disclaimer/Piece of Mind: Most plans have data cap and tethering may and will consume data and possibly incure extra charges. I take no responsibility for what you do to your phone or consequences from said mod. :good:
Why is s off required? I'm trying to do this with my 510 and I hope the procedure is similar.
Bobby060 said:
Why is s off required? I'm trying to do this with my 510 and I hope the procedure is similar.
Click to expand...
Click to collapse
S-OFF is required to remove the write protection. I tried 5+ times to do this without S-off and every time it reverted back after rebooting. When you purchase S-OFF, it lets you save it permanently. $25 is a small price to pay to have tethering unlocked.
If you can make it work with S-on then I'll edit the OP. In my experience trying to write to the system will reboot the phone.
Bobby060 said:
Why is s off required? I'm trying to do this with my 510 and I hope the procedure is similar.
Click to expand...
Click to collapse
Let me know how it goes.
Isnt there a kernel that removed the write protect?
It doesn't work on my 510. I don't have soff, but I have a custom kernel with write protection removed, so the change persists across boot. Goodness, I'd hoped this would solve my problem.
godkillerz223 said:
Isnt there a kernel that removed the write protect?
Click to expand...
Click to collapse
Its never worked for me. That's why I say S-off, it makes things so much easier.
godkillerz223 said:
Isnt there a kernel that removed the write protect?
Click to expand...
Click to collapse
the Jmz kernel does remove the write protection, and if you can deal with the various bugs that come along with it, than you'll be fine. Personally, I couldn't handle the periodic freezing so I ponied up the $25.
phatmanxxl said:
If you can make it work with S-on then I'll edit the OP. In my experience trying to write to the system will reboot the phone.
Click to expand...
Click to collapse
I changed it and it didnt reboot the phone but it needs reboot to stick (i think) and it doesnt stay at "0"
Can someone with jmz kernel please give it a shot? I dont use it anymore but bugs seemed to be minimal when i was running old firmware. Thanks.
$25 for this phone is a little steep. If it meant even one good custom rom id fork it over but Im thinking the price tag makes more sense for the flagship users. However, im still looking for a good reason...
KLit75 said:
I changed it and it didnt reboot the phone but it needs reboot to stick (i think) and it doesnt stay at "0"
Can someone with jmz kernel please give it a shot? I dont use it anymore but bugs seemed to be minimal when i was running old firmware. Thanks.
$25 for this phone is a little steep. If it meant even one good custom rom id fork it over but Im thinking the price tag makes more sense for the flagship users. However, im still looking for a good reason...
Click to expand...
Click to collapse
Unless your S-off the changes won't stick during a reboot, I'm surprised the phone even let you get that far, as far as modifying the XML file. I'm working on a debloated ROM with this mod cooked in. Anybody want to test it for me? I'll upload it now to my drop box.
phatmanxxl said:
Unless your S-off the changes won't stick during a reboot, I'm surprised the phone even let you get that far, as far as modifying the XML file. I'm working on a debloated ROM with this mod cooked in. Anybody want to test it for me? I'll upload it now to my drop box.
Click to expand...
Click to collapse
Yes. It let me edit it--there might be a mod im using that allows that? But went right back to 3 after reboot.
KLit75 said:
Yes. It let me edit it--there might be a mod im using that allows that? But went right back to 3 after reboot.
Click to expand...
Click to collapse
My internet was shut off for a few days so I was desperate to find out how to use my phone as a hot spot, I knew there was a way. This was the only working solution I was able to find.
phatmanxxl said:
If you can make it work with S-on then I'll edit the OP. In my experience trying to write to the system will reboot the phone.
Click to expand...
Click to collapse
Just playing around...this does work with jmz kernel. I flashed the deodexed rom last night and its way too early but no bugs so far. Instead of kk sd fix i used twrp manager and applied the sd patch. Im also using seeder.apk (which is free right now) The rom has busybox built in so installing your own could exacerbate bugs, maybe?
Most of the bugs i experienced with the kernel were tied somehow to the audio jack. That seemed to trigger crazy behavior like auto calling, voice google searches.
Tethering is good to have but my data plan sucks. I was hoping to use it as sort of a bridge for weak wifi spots but i find the wifi on the 610 is much slower than even older devices i own.
This setup probably wont be ideal for daily use but i feel like this would be a really good phone if it had some development.
I'm running stock, rooted with Xposed. No problems here. I've read people having various issues with JMZ Kernel.
Yea this phone is slow, a good Lollipop ROM would do wonders for the 610.
AT&T HTC Desire in Venezuela
i bought this phone, and im crazy trying to get sd fix, s-off and wifi tethering enable plz somebody help me, i already unlcok the bootloader trought hctdev and fastboot, i rooted but i can do tethering and i need it to share internet on my tablet for work. there's no a zip custom rom with all the fixes we need for this model? plz help me!
victormnavaso said:
i bought this phone, and im crazy trying to get sd fix, s-off and wifi tethering enable plz somebody help me, i already unlcok the bootloader trought hctdev and fastboot, i rooted but i can do tethering and i need it to share internet on my tablet for work. there's no a zip custom rom with all the fixes we need for this model? plz help me!
Click to expand...
Click to collapse
If you get s-off from sunshine, I think it'll unlock and root, but I believe you need to be locked and unrooted first. I'm not s-off so not certain. Once you are s-off, the WiFi tethering is simple. The one stipulation is it costs $25--a lot IMO since we really have no development on this phone.
If you read my earlier post in this thread, I was able to enable WiFi tethering and write to sdcard with s-on by flashing the jmz and stock deodexed firmware and jmz kernel which removes write protection. Most people don't do that because lots of bugs have been reported. So if you're willing to pay, checkout sunshine installer.
Btw--its been about a week and my phone has been fine (no freezes and no erratic behavior when plugged into audio jack) Its not super fast but this phone wasn't really fast to start. Your results may differ. My setup procedure is a little different. Instead of kk sdcard fix I use twrp manager and set the patch. The rest was a lot of trial & error and I lost track of exactly how I arrived here, but its been working fine for me.
I can't buy Sunshine form root ninja!
The support of ninjaroot told me that i can't buy their products for ppl of Venezuela, even having amazon gift card credit. y really need to unlock this awfull at&t limits, the freedom of using tethering and can use Quickpic as a default gallery and erase pics, further can manage the sd card, install xposed and all the stuff we can do in a normal Android phone. Plz if you can help me wiht this? it's really hard for us my country to get cellphones from US due ecommerce restrictions in our credit cards. how can i sd fix via twrp as you did?
victormnavaso said:
The support of ninjaroot told me that i can't buy their products for ppl of Venezuela, even having amazon gift card credit. y really need to unlock this awfull at&t limits, the freedom of using tethering and can use Quickpic as a default gallery and erase pics, further can manage the sd card, install xposed and all the stuff we can do in a normal Android phone. Plz if you can help me wiht this? it's really hard for us my country to get cellphones from US due ecommerce restrictions in our credit cards. how can i sd fix via twrp as you did?
Click to expand...
Click to collapse
That sucks. Well the only thing I can tell you is what I used right here in this forum BUT while I know the kernel works on international version, I'm not 100% on the stock deodexed rom. Do whatever research you can. Click "downloads" in the first post then pick our phone from the list. Flash the rom (which is rooted and has busy box built in, then flash the kernel)
http://forum.xda-developers.com/desire-610/development/att-stock-rooted-odex-deodex-t2848774
KLit75 said:
That sucks. Well the only thing I can tell you is what I used right here in this forum BUT while I know the kernel works on international version, I'm not 100% on the stock deodexed rom. Do whatever research you can. Click "downloads" in the first post then pick our phone from the list. Flash the rom (which is rooted and has busy box built in, then flash the kernel)
http://forum.xda-developers.com/desire-610/development/att-stock-rooted-odex-deodex-t2848774
Click to expand...
Click to collapse
I'm willing to try that, so tell me something where i can download the patch of sdcar writing to patch via twrp?
---------- Post added at 02:21 AM ---------- Previous post was at 01:57 AM ----------
Hey guyz i just flash the jmz kernel and did the guide to unlock tether, installed xposed and now i got tethering unlocked adn can erase things from sd card, im using quickpic as my default gallery and very happy thanks for doing this possible! MANY THANKS! :laugh:
Hi guys. Im not going to lie, im a noob when it comes to rooting, so I turned here to ask for help. Now, let me explain my whole issue. Lets start with, i cant unlock my bootloader. I also cant get into flash mode on flashtool which would allow me to downgrade, and and then root my phone from there. So yeah, I cant do anything honestly. I would love it if someone would be kind enough to help me with a step by step instruction guide, or even live assistance?. I already google'd for about 2-3 hours now, and can't find anything. Any help would be greatly appreciated!
white5pirit said:
Hi guys. Im not going to lie, im a noob when it comes to rooting, so I turned here to ask for help. Now, let me explain my whole issue. Lets start with, i cant unlock my bootloader. I also cant get into flash mode on flashtool which would allow me to downgrade, and and then root my phone from there. So yeah, I cant do anything honestly. I would love it if someone would be kind enough to help me with a step by step instruction guide, or even live assistance?. I already google'd for about 2-3 hours now, and can't find anything. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Mention 'EveryThing' about your phone. You can Take a screenshot of 'About Phone' and post it here.
Thanks for the reply!
I have attached a screenshot of what the window looks like.
"prntscr DOT com/8ffqdz" Sorry for the link, but I wasnt able to post it through the img tag.
Oh I also forgot to mention, just this morning I could root my phone with Kingo Root, but reading some negative stuff about it, I would still like to root it with the standard, old method of flashing etc, and I can't do some things I could on standard root.
white5pirit said:
Thanks for the reply!
I have attached a screenshot of what the window looks like.
"prntscr DOT com/8ffqdz" Sorry for the link, but I wasnt able to post it through the img tag.
Oh I also forgot to mention, just this morning I could root my phone with Kingo Root, but reading some negative stuff about it, I would still like to root it with the standard, old method of flashing etc, and I can't do some things I could on standard root.
Click to expand...
Click to collapse
Well, it's Xperia M2.
Let me clear that,
There are two types of Rooting methods available.
1. Permanent root
(Root access is available for ever, untill you unroot manually)
2. Temporary root
(Root access is gone, when you restart phone)
So, if you have successfully rooted your phone with Kingo Root, you no need to flash rooted kernel or firmware (its same with already root access available).
After rooting, you must have seen a app SuperSU or SuperUser or anyother that manages root permissions requested by apps that needs root (you need to grant permissions to let app work). If you do not see such any app, download it from play store.
I usually suggest Xperia users to root their devices with TowelRoot app. It is smart and simple and it does not contain any preloaded app for permissions (that means you can switch with SuperSU or Superuser)
Also, what things you could not do? let me know. I'll help you out
Regards,
hitman-xda
hitman-xda said:
Well, it's Xperia M2.
Let me clear that,
There are two types of Rooting methods available.
1. Permanent root
(Root access is available for ever, untill you unroot manually)
2. Temporary root
(Root access is gone, when you restart phone)
So, if you have successfully rooted your phone with Kingo Root, you no need to flash rooted kernel or firmware (its same with already root access available).
After rooting, you must have seen a app SuperSU or SuperUser or anyother that manages root permissions requested by apps that needs root (you need to grant permissions to let app work). If you do not see such any app, download it from play store.
I usually suggest Xperia users to root their devices with TowelRoot app. It is smart and simple and it does not contain any preloaded app for permissions (that means you can switch with SuperSU or Superuser)
Also, what things you could not do? let me know. I'll help you out
Regards,
hitman-xda
Click to expand...
Click to collapse
Again, thanks for the reply. Yup, I saw the SuperUser app, and the problems I have might not be phone breaking and such, but I would like to be able to do things like, change permissions of certain folders, which i cant do with the Kingo root, as it somehow denies the access to the folder, even tho I allowed root browser/es file manager root access. Overall, i think the problem is with the permission system Kingo has. I'd also like to mention that i would love to install Cyanogenmod on my device, but I will look into that myself @edit: Also, I would prefer to have a premanent root, instead of the towelroot and such.
white5pirit said:
Again, thanks for the reply. Yup, I saw the SuperUser app, and the problems I have might not be phone breaking and such, but I would like to be able to do things like, change permissions of certain folders, which i cant do with the Kingo root, as it somehow denies the access to the folder, even tho I allowed root browser/es file manager root access. Overall, i think the problem is with the permission system Kingo has. I'd also like to mention that i would love to install Cyanogenmod on my device, but I will look into that myself @edit: Also, I would prefer to have a premanent root, instead of the towelroot and such.
Click to expand...
Click to collapse
You could just press the 'thumbs up' instead writing 'thanks' everytime.
Well, why do you want to change the permissions of the folders? You could mess-up your device if you change permissions for the root folders.
The problem looks strange. If you have rooted successfully and GRANTED permissions for ES file explorer through SuperUser, you should not get any problem changing permissions. Check in SuperUser app that you see ES file explorer.
Also try using other explorer app. I use 'Solid Explorer' and its great.
If you have temporarily rooted your device as I mentioned in above post, try using TowelRoot app for rooting your device permanently and manually download SuperSU.
If you want to use CyanogenMod (it'll be pre-rooted) you need to carry below steps;
1. Unlock your Bootloader
(Wipes everything)
2. Install recovery.
3. Take stock ROM backup.
4. Flash ROM.zip
5. Flash GApps (optional)
6. Wipe cache+dalvic+factory reset
7. Reboot
Regards,
hitman-xda
Problem is that my bootloader can't be unlocked. I guess there is literally no way in which i can unlock it then?
white5pirit said:
Problem is that my bootloader can't be unlocked. I guess there is literally no way in which i can unlock it then?
Click to expand...
Click to collapse
If your bootloader status says
'unlock bootloader allowed = NO'
Then you can't flash anything on your phone. Almost every ROM needs an unlocked bootloader. There will be some ROMs that can be flashed over locked bootloader but they will be stock based.
EDIT: You have a good Luck, you can flash recovery on Locked bootloader
http://forum.xda-developers.com/xperia-m2/development/d2303-clockworkmod-6-0-4-6-t3011821
If you flash recovery successfully, that means you can flash ROM
Check below link for ROMs Available;
http://forum.xda-developers.com/xperia-m2/development
Regards,
hitman-xda
Yup, my bootloader says it can't be unlocked. Anyways, i tried the link yo usent me, but it comes up with an error, saying "device not found". I went into recovery mode on my phone, but i assume it might be the adb driver issue? I will try to reinstall it, and get back to you.
@edit: I reinstalled the ADB drivers, and now CWM is stuck on "daemon succesfully started", but it will not do anything else. Any clue as to what could I do to fix this? @edit2: Actually, disregard what i said. It still comes up as" Device not found"
white5pirit said:
Yup, my bootloader says it can't be unlocked. Anyways, i tried the link yo usent me, but it comes up with an error, saying "device not found". I went into recovery mode on my phone, but i assume it might be the adb driver issue? I will try to reinstall it, and get back to you.
@edit: I reinstalled the ADB drivers, and now CWM is stuck on "daemon succesfully started", but it will not do anything else. Any clue as to what could I do to fix this? @edit2: Actually, disregard what i said. It still comes up as" Device not found"
Click to expand...
Click to collapse
It can be a drivers issue. Install PC companion and connect your phone, let PCC install essential drivers and after that follow the same steps for installing recovery.
If you post any screenshot, that would be better.
Mkay, it worked now after i reinstalled the device in Sony PC companion. Heres a screenshot of what the CWM cmd window looks like: "prntscr DOT com/8fth1u". I assume this is good? So, all i have to do now is just download Cyanogen Mod and flash it, right?
white5pirit said:
Mkay, it worked now after i reinstalled the device in Sony PC companion. Heres a screenshot of what the CWM cmd window looks like: "prntscr DOT com/8fth1u". I assume this is good? So, all i have to do now is just download Cyanogen Mod and flash it, right?
Click to expand...
Click to collapse
Yup! Everything looks good. Just try to enter into recovery before downloading CM.
1.Switch off your phone and wait for 10 sec
2. switch on
3. When you see LED, try pressing either of vol buttons.
Hate to rain on the parade, but CM and CM based roms don't work with locked bootloaders for that phone, despite having CWM. It should say in the title of the thread whether it'll work with locked bootloaders.
es0tericcha0s said:
Hate to rain on the parade, but CM and CM based roms don't work with locked bootloaders for that phone, despite having CWM. It should say in the title of the thread whether it'll work with locked bootloaders.
Click to expand...
Click to collapse
Yeah you are right! Purely CM doesn't work on locked bootloader. But there must be any ROM available that is based on CM or even other ROMs that has some CM features.
I went through a few threads in that forum, Omni, CM, PAC, etc and all mentioned needing unlocked bootloader. Best bet is a good stock rom and Xposed to enable other features.
es0tericcha0s said:
I went through a few threads in that forum, Omni, CM, PAC, etc and all mentioned needing unlocked bootloader. Best bet is a good stock rom and Xposed to enable other features.
Click to expand...
Click to collapse
Z4 experience looks great ;
http://forum.xda-developers.com/xperia-m2/development/rom-z4-experience-locked-unlocked-bl-t3079811
Your xposed idea is great. Plus there must be GravityBox
I've been waiting for a custom ROM, haven't quite learned to make one myself. I've tried finding a compatible Xposed with no luck. The only things I have been able to do are debloat and add Viper/Dolby sound mods that added volume boosts. Please feel free to add any trials and errors you guys have had trying to mod this phone here.
packydavis said:
I've been waiting for a custom ROM, haven't quite learned to make one myself. I've tried finding a compatible Xposed with no luck. The only things I have been able to do are debloat and add Viper/Dolby sound mods that added volume boosts. Please feel free to add any trials and errors you guys have had trying to mod this phone here.
Click to expand...
Click to collapse
There are plenty of tutorials for making your own rom and kerenel. There are plenty in xda university and an excellent one by my colleague jackeagle, if you want something device specific then it maybe better to add the phone title in your op rather than just adding a tag
Regards
Sawdoctor
LG Aristo
No ROMs, no real mods and the only progress we have towards a kernel is KyleBryant's work delivering us the kernel source itself.
JustLee said:
Dang Any tips for editing the power button on the back of the phone
Click to expand...
Click to collapse
What do you mean by editing the power button? Like how it functions or it's response upon being held down?
Substratum
Hey, just so you guys know, Substratum works once you're rooted. Just go to the Play Store and download the Substratum app along with a theme of your liking. I'll post some screenshots of my Aristo all theme translucent.
mustangtim49 said:
Hey, just so you guys know, Substratum works once you're rooted. Just go to the Play Store and download the Substratum app along with a theme of your liking. I'll post some screenshots of my Aristo all theme translucent.
Click to expand...
Click to collapse
I'd recommend against using it with certain themes.
I ended up breaking my status bar so now when I hit the settings button from the pull down, it activated gps instead.
MODS
Changed BootAnimation .zip to Cyanogenmod version
Added Viper4Divine FX + DivineEQ + Dolby Atmos
Apps Added into system:
AdAway
Camera FV-5
ES File Explorer
EvolveSMS
FlySo
GhostKik
Instagram
Kik
NovaLauncher
PowerManager
Pulsar+
Removed from system:
All LG Home Apps (FIRST replace with Launcher of your choice E.G. Nova or ADW)
Lookout
All Google but Play Store, Play Services, Play Games, Gmail, YouTube, Maps, and Drive.
All LG apps but SmartWorld (yes including Messaging)
And removed more but they were minor and cant remember...
DivineEQ is blank when loaded so far.
ES File Explorer clears its "history" every time i exit the app. But major settings stick.
I know its nothing major. If I knew Android Developing, I would create a custom rom.
https://forum.xda-developers.com/android/development/rom-ipioneer-stock-10i-v1-t3637393
xtremelora said:
https://forum.xda-developers.com/android/development/rom-ipioneer-stock-10i-v1-t3637393
Click to expand...
Click to collapse
Good look, but the is for the lv3. I've already tried and it won't work due to twrp doing a check on model version and build version sadly.
ninjasinabag said:
Good look, but the is for the lv3. I've already tried and it won't work due to twrp doing a check on model version and build version sadly.
Click to expand...
Click to collapse
As I said on the OP of that thread, check the specifications at the end.
Of course, it is for the MetroPCS version, I make it clear where it says:
Carrier: MetroPCS
And I also mention the twrp limitations and the fix.
Besides that, I am going to start building an slim version (very slim) and at the same time if anyone can provide me a T-mobile/Other Carrier Nandroid I can build slim versions of that for you guys.
xtremelora said:
As I said on the OP of that thread, check the specifications at the end.
Of course, it is for the MetroPCS version, I make it clear where it says:
Carrier: MetroPCS
And I also mention the twrp limitations and the fix.
Besides that, I am going to start building an slim version (very slim) and at the same time if anyone can provide me a T-mobile/Other Carrier Nandroid I can build slim versions of that for you guys.
Click to expand...
Click to collapse
Ooh sh#t, my bad homie.
Well now that I've made a fool of myself, I'mma back up and give this a test.
ninjasinabag said:
I'd recommend against using it with certain themes.
I ended up breaking my status bar so now when I hit the settings button from the pull down, it activated gps instead.
Click to expand...
Click to collapse
That's when you boot into recovery and flash the Substratum.rescue zip and all good, plus, you should have a good nandroid to restore also. So nobody should be afraid to use Substratum, it's perfectly safe if you know your back up plans. Anyone has questions, just reply in this thread and I'll do my best to help anyone.
mustangtim49 said:
That's when you boot into recovery and flash the Substratum.rescue zip and all good, plus, you should have a good nandroid to restore also. So nobody should be afraid to use Substratum, it's perfectly safe if you know your back up plans. Anyone has questions, just reply in this thread and I'll do my best to help anyone.
Click to expand...
Click to collapse
Yeah, I already had that panned out. My comment was a simple heads up about one of the possibilities.
snafu
starting over from scratch currently. everything was correct and working when i first rooted and progressively i messed up. i have no idea how it got so bad or why Ive put up with it for weeks now. i have several nandroid back-ups if anyone wants a headache. but i think my problem is deeper than just the ROM.
Laptop recognizes my LGMS210 as a LGMS550 when in recovery. Code 10 -broken drivers.... *re-flashed the recovery from fastboot [ADB version 1.0.32 Revision eac51f2bb6a8-android] and laptop gave me access to internal and SD but only seeing 9.95g available (6g for sys? is that right)
Google play is broke af. Nothing will install (error -504) even after cleaning data/data. data/apps .. even after dalvik/cache wipe.... even after praying. Not even apps Ive never installed before. LG smart world ie themes,fonts,whatever gives install error.
cant even install apks i have on SD (error-package seems corrupt)
Magisk wont update from ver 2.*.* to ver 16. begins to work but alas error -1 ?
I still have root tho lol
no super su present
and i have xposed framework API 26 installed but i think when using magisk and xposed modules this whole cluster nut began.
android Easter egg wont even work. its stuck with a fish selected, cant change the food offering. and NO cat has ever came.
Boot-loops 3-4 times if not shutdown properly... ie rebooter app or terminal reboot. i changed the default MPCS boot animation so i can see if its looping or chooching. gets thermo-nuclear hot and eventually boots after 4-5 minutes.
i'm gonna go ahead and re-flash stock FW.
*on a side note i keep confusing my PC software like fastboot and adb for my gf's galaxy tab A. Caught a security error brick when i accidentally used its fastboot for something like to unlock bootloader.... i have way too many devices being worked on at once. eh, never a dull moment.
₥ike_grips said:
starting over from scratch currently. everything was correct and working when i first rooted and progressively i messed up. i have no idea how it got so bad or why Ive put up with it for weeks now. i have several nandroid back-ups if anyone wants a headache. but i think my problem is deeper than just the ROM.
Laptop recognizes my LGMS210 as a LGMS550 when in recovery. Code 10 -broken drivers.... *re-flashed the recovery from fastboot [ADB version 1.0.32 Revision eac51f2bb6a8-android] and laptop gave me access to internal and SD but only seeing 9.95g available (6g for sys? is that right)
Google play is broke af. Nothing will install (error -504) even after cleaning data/data. data/apps .. even after dalvik/cache wipe.... even after praying. Not even apps Ive never installed before. LG smart world ie themes,fonts,whatever gives install error.
cant even install apks i have on SD (error-package seems corrupt)
Magisk wont update from ver 2.*.* to ver 16. begins to work but alas error -1 ?
I still have root tho lol
no super su present
and i have xposed framework API 26 installed but i think when using magisk and xposed modules this whole cluster nut began.
android Easter egg wont even work. its stuck with a fish selected, cant change the food offering. and NO cat has ever came.
Boot-loops 3-4 times if not shutdown properly... ie rebooter app or terminal reboot. i changed the default MPCS boot animation so i can see if its looping or chooching. gets thermo-nuclear hot and eventually boots after 4-5 minutes.
i'm gonna go ahead and re-flash stock FW.
*on a side note i keep confusing my PC software like fastboot and adb for my gf's galaxy tab A. Caught a security error brick when i accidentally used its fastboot for something like to unlock bootloader.... i have way too many devices being worked on at once. eh, never a dull moment.
Click to expand...
Click to collapse
You're using the wrong recovery if it's still showing the ms550.
Drivers are universal inside of company devices. (LG for LG, Samsung for Samsung) so they don't conflict.
Adb and fastboot are both universal drivers and shouldn't matter for your device. (I'm using the same fastboot I installed for my Galaxy note 4 that I am for my aristo, my V10, my htc desire 610, and my uncle's v20)
Just do what you said and start fresh.
Unlock the bootloader.
Install the proper twrp and remove encryption.
Flash the stock boot partition and wipe data (this is sneakily pertinent if you're gonna use magisk)
Do not install system mods before using magisk.
After that, use twrp's file explorer to remove and stock apps that you won't need.
Can't find a definitive answer for this anywhere.
Where do the 7.1 or newer Roms active the remote control so it can bring the box out of standy and power down?
I know there is the remote.conf file in /system/etc on the 6 Roms which I have edited sucessfully before and you supposidly edit the remote.mouse1.tab in the 7.1 Roms but that doesn't seem to work. It doesn't even let me control the box once booted never mind power up and down which maybe suggests it is activated somewhere else first??
is it written into the kernel or boot loader perhaps.??
Please don't just suggest what I have already tried above. And yes I use a wireless usb keyboard/trackpad once booted but I'm talking about bringing the unit out of standby and powering down.
Any help would be massively appreciated.
I like my 7.1 Rom but having to disconnect/reconnect the power to boot it is just plain annoying.
did you ever figure it out, my remote does not work anymore after flashing poison rom over my boxes original rom, my power button works on the remote but thats it, have to use air mouse, has to be kernel or bootloader
bluefender said:
did you ever figure it out, my remote does not work anymore after flashing poison rom over my boxes original rom, my power button works on the remote but thats it, have to use air mouse, has to be kernel or bootloader
Click to expand...
Click to collapse
Hey. No still not figured it out. I'm still on my 6.01 ROM as it works. Pretty mental how nobody seems to know a fix for this?
Diamond Geezer said:
Hey. No still not figured it out. I'm still on my 6.01 ROM as it works. Pretty mental how nobody seems to know a fix for this?
Click to expand...
Click to collapse
i read but not sure if its true, it could be the kernel or something in boot, nougat rom changed things, so now i just use an air mouse
funny thing is if i flash back with twrp the original rom, the remote works again, but do not like the original rom.
bluefender said:
i read but not sure if its true, it could be the kernel or something in boot, nougat rom changed things, so now i just use an air mouse
funny thing is if i flash back with twrp the original rom, the remote works again, but do not like the original rom.
Click to expand...
Click to collapse
Its definately got something to do with system, check out the installation method of mine and Whiteak's Poison Rom, that only modifies system partition and apparently after applying it the remote doesnt work properly
Ricky Divjakovski said:
Its definately got something to do with system, check out the installation method of mine and Whiteak's Poison Rom, that only modifies system partition and apparently after applying it the remote doesnt work properly
Click to expand...
Click to collapse
actually it's the bootloader and the remote.conf from \system\etc\ , if the bootloader will work, and if the correct remote.conf is put in system\etc\ the remote will work too for Power ON\OFF
oh, and i know how to add more remotes to a firmware (maximum in a firmware can be added 8 remotes) it's all about kernel
drakulaboy said:
actually it's the bootloader and the remote.conf from \system\etc\ , if the bootloader will work, and if the correct remote.conf is put in system\etc\ the remote will work too for Power ON\OFF
oh, and i know how to add more remotes to a firmware (maximum in a firmware can be added 8 remotes) it's all about kernel
Click to expand...
Click to collapse
Would you be able to PM me?
ive done extensive research on this and couldnt find much
Ricky Divjakovski said:
Would you be able to PM me?
ive done extensive research on this and couldnt find much
Click to expand...
Click to collapse
sure, gonna send you a PM
Is it possible I can get this information also. I have been wracking my brain trying to figure how to do this. Please and Thank you in Advance
Hi, here the same problem. Upgraded the Android 6 firmware of my CSA93 (Amlogic S912, 3GB RAM, 32GB Flash) to the Stock T95Z Android 7.1 ROM (the base for the Poison ROM) and the remote has gone. I tried to copy the original remote.conf (from Android 6) into the new /system/etc folder (and also 5 other remote.conf files from the Internet with a restart each time), but no chance. It is probably not so easy as copying a file Any suggestions are highly appreciated. It is really annoying to have to turn on the device with the power switch each time.
Me too! Any news in this?
Soldiaz said:
Me too! Any news in this?
Click to expand...
Click to collapse
It's in the recovery partition under system/etc
Is there any more info re: this issue? A good write up would really help a lot of us who cannot develop ROM but quite happy to tinker here and there.