Database Develop

[BOOTLOADER BYPASS -WIP] EternityProject Kexec method for Motorola Olympus (Atrix 4G)

Welcome to Eternity Project!
So... as most of you know I'm working on the Atrix solution from TOO MUCH time.
With the collaboration of people on #moto-atrix I've stated that FUSES on Tegra2 are really OTP, so there isn't any way to CRACK the BL, but we can still BYPASS it.
So... what is it?:
kexec is a "fastreboot" that won't pass through the Moto Bootloader, so with it it's possible to use custom kernels and, with some other development, custom Android systems like CM7 and many others.
Where's the poop?
Okay, that's it: I've successfully compiled and ran kexec on the Atrix 4G, so that kexec works, but it needs a kernel that can boot with kexec. On x86 we can build a relocatable kernel so no problems... but not on ARM and obviously not on Tegra.
The thing that is missing is exactly... _the address of the boot params_!
And now?
I'm only searching for help for completing the project and make a kernel that is bootable from my god-it-is-really-working-kexec. Any devs around?
Downloads:
- Kexec pack V0.01: DOWNLOAD
Kexec pack contains:
- ATAGS for MB860 (ATRIX_atags.tar)
- ATAGS hack module (eternity_procfs.tar)
- kexec module (eternity_kexec.tar)
- kexec tools/binaries (kexec-tools.tar)
- Kernel....that doesn't work. (eternity_kexec_kernel.tar)
So, what does work and what does not?
- ATAGS hacky hack: WORKING
- kexec module: WORKING
- kexec tools/binaries WORKING
- Kernel ToDo
How to run it:
0. FLASH AT&T 1.2.6 SBF PRIOR DOING ANYTHING
1. Extract all the archives
2. Insert the procfs_rw.ko module
3. cat atags > /proc/atags
4. Insert the kexec module
5. Run kexec for loading the kernel and jumping to it.
6. Boot! :|
P.S.: I won't release detailed how-tos because at this state I only need a DEVELOPER that can help me to build the kernel.
Thanks to:
- PAulyHoffman (special thanks!)
- unknown
- Sogarth
- the2dcour
- cranch
- eval-
- and many, many others....!

Awesome, i can verify that this kexec is working and will continue testing until we succeed.

random boot animation I made for eternity project
http://diamantephoto.com/bootanimation_red.zip
Also: 1.2.6 without losing /data, in case you were wondering exactly why I made this
http://forum.xda-developers.com/showthread.php?t=1073439

kexec pack updated. now kexec-tools is included

@kholk: Hai;
so basically this is a port of the unix kexec to run on tegra based devices?
From my understanding the android system uses a boot image that has the ramdisk and kernel combined together and they are dependent on each other... so won't overwriting the kernel at runtime give you us some issues since the core initialization of the system is ran from the ramdisk???
wouldn't be a better idea to tackle this issue too? but then again the only reason we can't flash boot images is because of the bootloader but ofcourse this is definitely a step forward for the tegra users.
now about the kernel, theoretically if we build an aosp tegra kernel from http://android.git.kernel.org/?p=kernel/tegra.git;a=summary shouldn't it work?
I can try building us a kernel if that would work
PS: people let's keep this dev ONLY if you want us to get some progress we need able to read through the thread without useless posts.
edit: also found this https://opensource.motorola.com/sf/frs/do/listReleases/projects.atrix/frs.olympus I'm sure having the source for the kernel we are currently running is also helpful

I know we should keep this dev only but please don't tell me this is for ATT only i already feel shafted enough being a Bell user and that would make it a hell of a lot worse if it was

Ratchet556 said:
I know we should keep this dev only but please don't tell me this is for ATT only i already feel shafted enough being a Bell user and that would make it a hell of a lot worse if it was
Click to expand...
Click to collapse
When a kernel that works will be deployed I'll personally port it to Bell Atrix. This will take only some seconds.

kholk, perhaps we can ask a defy developer (or any of the phones that have kexec working) to help us build the kernel.
it's too bad da_g isn't around, he did a custom kernel but wasn't able to boot it.

I'm not a developer so I am hoping someone can help me understand this process better. From my understanding kexec is used as a reboot method that skips initial bootloader and hardware loading so how will this effect if we turn our phone off or pull the battery? Will the device need to be rebooted after initial startup to reactivate the kexec? Sorry to sound like the newbie that I am, I'm just interested in learning more.

lostinbeta said:
I'm not a developer so I am hoping someone can help me understand this process better. From my understanding kexec is used as a reboot method that skips initial bootloader and hardware loading so how will this effect if we turn our phone off or pull the battery? Will the device need to be rebooted after initial startup to reactivate the kexec? Sorry to sound like the newbie that I am, I'm just interested in learning more.
Click to expand...
Click to collapse
Yeah, I'm also a little confused as to what exactly this means for all of us people who want to just flash Custom ROMs and such? In what ways is this different than just an unlocked bootloader and such?

lostinbeta said:
I'm not a developer so I am hoping someone can help me understand this process better. From my understanding kexec is used as a reboot method that skips initial bootloader and hardware loading so how will this effect if we turn our phone off or pull the battery? Will the device need to be rebooted after initial startup to reactivate the kexec? Sorry to sound like the newbie that I am, I'm just interested in learning more.
Click to expand...
Click to collapse
thebeardedchild said:
Yeah, I'm also a little confused as to what exactly this means for all of us people who want to just flash Custom ROMs and such? In what ways is this different than just an unlocked bootloader and such?
Click to expand...
Click to collapse
Assuming my understanding of kexec is correct, this would survive battery pulls. Basically, a custom rom would need to include two kernels: a Motorola kernel in addition to the custom one. The bootloader would run the Motorola kernel, which should pass any checks the bootloader would make. From there, the kernel would use kexec to load the custom kernel over itself in memory, effectively replacing itself. From there the custom kernel can continue loading the rom.
If the booloader were unlocked, the phone could directly boot the custom kernel. The downside of loading the custom one on top of the Motorola one is that the state of the phone might not be entirely known, so it would need to do more work checking what's been initialized and what hasn't. Its a little more work for the kernel/rom developer, but the end result is the same.

Jotokun said:
Assuming my understanding of kexec is correct, this would survive battery pulls. Basically, a custom rom would need to include two kernels: a Motorola kernel in addition to the custom one. The bootloader would run the Motorola kernel, which should pass any checks the bootloader would make. From there, the kernel would use kexec to load the custom kernel over itself in memory, effectively replacing itself. From there the custom kernel can continue loading the rom.
If the booloader were unlocked, the phone could directly boot the custom kernel. The downside of loading the custom one on top of the Motorola one is that the state of the phone might not be entirely known, so it would need to do more work checking what's been initialized and what hasn't. Its a little more work for the kernel/rom developer, but the end result is the same.
Click to expand...
Click to collapse
I see, thanks for the explanation! So, on the user end, would there be any noticeable differences? This kind of makes it sound like the phone will be doing a lot more work, so could we see performance decrease or perhaps startup lag or something of the sort? Or would this all pretty much function on the surface as if we had flashed a custom ROM on some phone without a locked bootloader?

thebeardedchild said:
I see, thanks for the explanation! So, on the user end, would there be any noticeable differences? This kind of makes it sound like the phone will be doing a lot more work, so could we see performance decrease or perhaps startup lag or something of the sort? Or would this all pretty much function on the surface as if we had flashed a custom ROM on some phone without a locked bootloader?
Click to expand...
Click to collapse
Boot time will be about twice as long. Other then that, everything will run about the same

Yes thank you very much for that explanation... though I do also have the question about stability. By replacing the current kernel in memory with the new modified kernel the phone state may get confused as you mentioned... could this cause instability as a whole or increase risk of kernel panics? Or once everything is loaded and complete does it stabilize with the modified kernel?
Again sorry for the questions. This topic intrigues me and I love learning how stuff works.

thebeardedchild said:
I see, thanks for the explanation! So, on the user end, would there be any noticeable differences? This kind of makes it sound like the phone will be doing a lot more work, so could we see performance decrease or perhaps startup lag or something of the sort? Or would this all pretty much function on the surface as if we had flashed a custom ROM on some phone without a locked bootloader?
Click to expand...
Click to collapse
Only difference would be that it might take slightly longer to boot up. Once the phone is finished booting, there's no difference in terms of performance because by that point the Motorola kernel isnt running, or even loaded.

thebeardedchild said:
Haha yeah I'm checking every like 2 seconds now. What exactly do we wait for then? Someone to just create the custom kernel, and then of course wait for some Custom ROMs to be created? I hope we get CM7!
Click to expand...
Click to collapse
Kexec isn't fully operational yet, still need to find boot params. Then custom kernel.

How easy will this be to install on our phones? will it just be something we need to flash through CWM or will it require some more work then that to install?

Ratchet556 said:
How easy will this be to install on our phones? will it just be something we need to flash through CWM or will it require some more work then that to install?
Click to expand...
Click to collapse
I imagine some of the preliminary stuff may need to be pushed with ADB but devs are always nice and give us very clear guides. And I'm sure either a dev or active member could easily create a batch script.
Even though I'm comfortable with ADB I always make scripts for myself because I regularly wipe me phone and whatnot. Because it's so engaging some people might want to wait until a few normal community members test this out so we can see if there are any glaring challenges with the instructions. Just remember to back things up, read instructions clearly and I'm sure we'll all be fine. We've got SBFs and all that good stuff to cover our asses too.

Would it be possible to bring fastboot off the htc to this? Then we won't have to worry about boot time at all. Even if it did double the boot time...
Sent from my MB860 using XDA App

PixoNova said:
This bypasses the bootloader
Swyped from my Motorola Atrix 4g using XDA Premium App
Click to expand...
Click to collapse
Correct this method has nothing to do with unlocking the bootloader and previous attempts at that proved it maybe impossible.

[ASK]Answers to all your questions...!

Hey guys i am starting this thread here as i find there are so many people asking questions and bricking their phones.I just want to help out people and save them from bricking their phones..
i have tried all Froyo based roms available for the captivate.i have good experience in rooting,clockworkmod and flashing roms.I would like to help out all new members here as much possible because just 2 months back i had trouble finding out things...
So what are you guys waiting for ask away....!
P.S:also i kindly request the other senior members and developers here to correct me if i am wrong anywhere and ya i dont want any donations....

Hey, I'm working on something with a similar spirit as this.
A work in progress: self help brick recovery guide
If you would want help out with this. I believe that it could help the q&a and other section of the captivate thread a lot by reducing the number of brick threads

If either of you have experience with web coding, perhaps it would be worthwhile to make up a page that has an interactive checklist of brick steps. Sort of a step-by-step troubleshooter.
For example, the first page could just be the question about whether the phone shows any signs of life at all or not, then have a page with selectable items about the Rom/kernel/modem setup, then move into more specific items.
See the attached zip for what I'm talking about.

speedy_11 said:
Hey, I'm working on something with a similar spirit as this.
A work in progress: self help brick recovery guide
If you would want help out with this. I believe that it could help the q&a and other section of the captivate thread a lot by reducing the number of brick threads
Click to expand...
Click to collapse
Same spirit here mate i am with you lets do it....!
But i will be focussing on problems of members other than bricking and also i believe prevention would be better than cure....!
jmtheiss said:
If either of you have experience with web coding, perhaps it would be worthwhile to make up a page that has an interactive checklist of brick steps. Sort of a step-by-step troubleshooter.
For example, the first page could just be the question about whether the phone shows any signs of life at all or not, then have a page with selectable items about the Rom/kernel/modem setup, then move into more specific items.
See the attached zip for what I'm talking about.
Click to expand...
Click to collapse
I saw the zip and got what you are saying i liked it. I have a decent hold over html & java so i must be able to create that....!
But i will need space to host it....!

Perhaps in lieu of hosting space, save it as an all-in-one zip file and post it on here. You wouldn't need a large amount additional space (I assume) as there probably wouldn't be a huge need for images. If that's the case, it would be all text, which should be fairly small.

jmtheiss said:
Perhaps in lieu of hosting space, save it as an all-in-one zip file and post it on here. You wouldn't need a large amount additional space (I assume) as there probably wouldn't be a huge need for images. If that's the case, it would be all text, which should be fairly small.
Click to expand...
Click to collapse
true it wont be a big zip file......!
I will create it and post it here

Wow jmtheiss you took my idea to the next level, i never though of making it interactive. But that my be the key that really will make it work.
sorry adicool I'm no good with HTML or coding i will have to leave that to you. But I have a knack for graphic design. Plus I can find and collect the images that could be use as examples (ex. like a soft brick screen)

speedy_11 said:
Wow jmtheiss you took my idea to the next level, i never though of making it interactive. But that my be the key that really will make it work.
sorry adicool I'm no good with HTML or coding i will have to leave that to you. But I have a knack for graphic design. Plus I can find and collect the images that could be use as examples (ex. like a soft brick screen)
Click to expand...
Click to collapse
i just created a test version to see if i still remember html just have a look at this attachment below....!
open the test.html first i have just created a working link for rooting others i will be doing soon,tell me what you think of it....!

adicool said:
i just created a test version to see if i still remember html just have a look at this attachment below....!
open the test.html first i have just created a working link for rooting others i will be doing soon,tell me what you think of it....!
Click to expand...
Click to collapse
Looks good to me. Clean, simple, easy to follow.

A good starting point, if you need any help feel free to ask.
Thought here: The one package is good. I'm also thing that we can have each section posted package as a separate package too (along with the whole package). So those who only need one thing like rooting the can just download that section

Hi! I'm new to the forums and need some help. I have stock I897UCKB1, sucessfully rooted and unlocked it. I would like to try out some ROMs, CM7 first. How should i start? I assume i have Eclair/Froyo bootloaders, right? I've installed ROM Manager Premium, clicked flash clockworkmod, and to reboot to recovery but it's only stock recovery. How should i proceed? Also i need some enlightment on bootloaders: if i flash the newest GB ATT bootloaders will every ROM work with it? Thanks in advance!

Go to the general section, there is a thread called "sticky roll-up" in there is a link to a thread called "e: signature verification failed" that is the work around you need for cwm (or any zip) to flash
Or you can flash a froyo kernel that has cwm baked in with odin like speedmod...
I wouldn't mess with bootloaders st this point in your flashing experience that its the only time you risk a real hard brick do leave those alone until you know for sure what you're doing.

I totally forgot about muse, so here's my on take of the guide.

bazarimajom said:
Hi! I'm new to the forums and need some help. I have stock I897UCKB1, sucessfully rooted and unlocked it. I would like to try out some ROMs, CM7 first. How should i start? I assume i have Eclair/Froyo bootloaders, right? I've installed ROM Manager Premium, clicked flash clockworkmod, and to reboot to recovery but it's only stock recovery. How should i proceed? Also i need some enlightment on bootloaders: if i flash the newest GB ATT bootloaders will every ROM work with it? Thanks in advance!
Click to expand...
Click to collapse
I would advice you to first try flashing a few froyo based roms just to gain experience in flashing after that you can move over to GB
as told by my friends here there is a thread here that fixes that cwm problem .!
If you still need help or cant find it do post here and i would be more than happy to help...!whatever you do just dont mess with bootloaders atm as they can cause your device to be bricked...
I would say start off first by flashing cognition 4.5.3....!

speedy_11 said:
A good starting point, if you need any help feel free to ask.
Thought here: The one package is good. I'm also thing that we can have each section posted package as a separate package too (along with the whole package). So those who only need one thing like rooting the can just download that section
Click to expand...
Click to collapse
Hmmm well that can be done !
i have college today i will get started with the html again once i come back....
lets finish this thing soon!
Edit:just finsihed the package for 2.2 only,have a look at the attachment,also its not complete yet but it had basic things...!

studacris said:
Go to the general section, there is a thread called "sticky roll-up" in there is a link to a thread called "e: signature verification failed" that is the work around you need for cwm (or any zip) to flash
Or you can flash a froyo kernel that has cwm baked in with odin like speedmod...
I wouldn't mess with bootloaders st this point in your flashing experience that its the only time you risk a real hard brick do leave those alone until you know for sure what you're doing.
Click to expand...
Click to collapse
adicool said:
I would advice you to first try flashing a few froyo based roms just to gain experience in flashing after that you can move over to GB
as told by my friends here there is a thread here that fixes that cwm problem .!
If you still need help or cant find it do post here and i would be more than happy to help...!whatever you do just dont mess with bootloaders atm as they can cause your device to be bricked...
I would say start off first by flashing cognition 4.5.3....!
Click to expand...
Click to collapse
Thanks, i was able to get CWM to work with speedmod kernel, so i take your advice now and try out some froyo roms!

bazarimajom said:
Thanks, i was able to get CWM to work with speedmod kernel, so i take your advice now and try out some froyo roms!
Click to expand...
Click to collapse
Cool.....!
dont forget to follow the instructions before flashing...

adicool said:
Edit:just finsihed the package for 2.2 only,have a look at the attachment,also its not complete yet but it had basic things...!
Click to expand...
Click to collapse
The information looks good, i saw that on the flash back to stock you didn't put hemdiall. Since linux and mac users cant use odin
Did you take a peak at my attempt with muse?

speedy_11 said:
The information looks good, i saw that on the flash back to stock you didn't put hemdiall. Since linux and mac users cant use odin
Did you take a peak at my attempt with muse?
Click to expand...
Click to collapse
oops i forgot that, i dont use mac so i missed it lol....!
yeah i saw your attempt it was decent enough mate,if you want to try more software try adobe dreamweaver it will help you develop web pages without html

dreamweaver would be great but my current computer wouldn't be able to handle it and i dont have the money for it. muse is free until the final product is done that why im using it.
i pm'ed you but i dont know if it sent

[Q] PDroid Assistance on CheckROMv6

I have been trying this to get PDroid to work for almost 24 hours now and I am running out of time. I'm...tired. -_-. I have searched and searched ans searched and searched and ... I'm just at a loss.
Here is my post on PDroids Thread quoted here.
CrazyOGuy said:
You know... I read that in the instructions but I didn't connect 2 & 2.
Anywho, can I patch the ROM before I Flash it or do I need to Flash it first - Get it running - than flash that same ROM again patched?
Edit: Ok... I took a leap of "Nothing Ventured...Nothing Gained". I have successfully Flashed my first ROM by my self (OMG O_O). As such I was able to patch the Zip of Version 23 (which I already have on my Note). Unfortunately I don't know where to go from here. I did try to update through ClockWorkMod...just like I did with the ROM Originally - but it seems that this doesn't work since I'm still getting the "You need a Patch" Display. I did reboot.
Edit 2: Found the problem. I missed the "output" portion of the program. Just patched it in did what is necessary. Don't think this ROM is going to work though... Ive been staring at the the title screen for a few minutes now. Might be a boot loop. I think I can fix it.
Edit 3:Fixed. Ok...The entire reason I even bothered to flash said ROM was so I could do this. Pitty. :/
Edit 4: Just tried it with CheckROMv6 Wipe. Nope. Same thing Happens. I boot it and I stare at the Boot Screen. :/
Click to expand...
Click to collapse
Based on what I have seen of CheckROMv6 ... I like it and would like to use it.
I have since then been trying to get the Android SDK to work so that I can post what is seen in the system log for errors (as mentioned in the instructions.) But to be blunt this is out of my league. I only just recently -today- have been competent enough to flash my own ROMs.
I don't even know what to ask right now (possibly due to what seems like waited effort). I need help...Can any one please take it upon themselves and please help me get through this?
If I had to guess my problem isn't in the creation of the .zip patch, but the way I'm putting it on (though both things are in the instructions and I have followed it to the letter...hence my frustration on this matter.
Edit: Oh...and before anyone mentions it (presuming any one replys >_>) I know about this thread. The DLs are no longer active.

I think I found the problem but I don't know how to solve it if what I have found is the problem. Hence Why I have bumped this.
I have something a-bit more concrete and less abstract.
I went into Clock Work Recovery...and I loaded the patched ROM. I went into Advanced and then Log where it says and I quote:
Install from sdcard complete.
Installing update...
>>>Mounting partitionsmount: failed to mount /dev/block/mmcblk0p9 at /system: Device or resource busy
Click to expand...
Click to collapse
....
(Everything else looks normal).
What does this mean? & How do I fix it?

[DEV][KERNEL] Magic sysrq to boot into bootloader (fastboot) mode

For anyone that is building their own kernels, I highly recommend grabbing this patch:
https://github.com/invisiblek/andro...mmit/f745249b52cab9feb5b7821b54d47176ae093617
Details in the commit comments.

You know what I've been hacking phones for awhile and I forgot about fastboot booting a boot.img

Haven't tried it, but sounds like nice work!
I had another idea for adding some safety - early in the boot process set the bootlloader message to tell the bootloader to boot into recovery mode (but don't actually reboot), then later when the boot is complete, reset the message. That way if the user reboots anywhere in between, they will boot into recovery.
Hope that makes sense, I brainstormed over the idea in another thread: http://forum.xda-developers.com/showpost.php?p=44030783&postcount=8
Feel free to implement any of my ideas you like - I don't have as much time for Android development as I would like.
~Troop

Trooper_Max said:
Haven't tried it, but sounds like nice work!
I had another idea for adding some safety - early in the boot process set the bootlloader message to tell the bootloader to boot into recovery mode (but don't actually reboot), then later when the boot is complete, reset the message. That way if the user reboots anywhere in between, they will boot into recovery.
Hope that makes sense, I brainstormed over the idea in another thread: http://forum.xda-developers.com/showpost.php?p=44030783&postcount=8
Feel free to implement any of my ideas you like - I don't have as much time for Android development as I would like.
~Troop
Click to expand...
Click to collapse
Yea, you could probably make the kernel write to scratch right away, in the case that it panics, dump it into recovery or bootloader, then clear it upon a full, successful boot. But that sounds like a lot more work and in the end, you really don't get anything more than this. This patch will save you from anything except a kernel panic that happens way early. (or of course blatantly flashing crap to the wrong partitions )

invisiblek said:
Yea, you could probably make the kernel write to scratch right away, in the case that it panics, dump it into recovery or bootloader, then clear it upon a full, successful boot. But that sounds like a lot more work and in the end, you really don't get anything more than this. This patch will save you from anything except a kernel panic that happens way early. (or of course blatantly flashing crap to the wrong partitions )
Click to expand...
Click to collapse
Ah, I was just thinking maybe it would be possible to write to scratch earlier than the sysrq method becomes available and thus be a little bit safer. It also wouldn't require a keyboard though that point would be a bit moot as you'd need a keyboard once you reboot into recovery. So you're right, it probably doesn't make much difference.
Have you ever done anything with kexec? That was the next thing I wanted to look into once we got something like this for booting more safely. I know people use it for multi-boot methods and someone even came up with a way to hardboot a Nexus 7 with kexec:
http://forum.xda-developers.com/showthread.php?t=2104706
Eventually, I'd like to develop something like that into a boot image that could be stored on the boot or recovery partitions and function as an extra bootloader to allow booting images stored elsewhere.
Anyway, thanks again for sharing your work, and I don't mean to hijack your thread - if you want to discuss ideas I had hoped more people would join in on brainstorming in my thread: http://forum.xda-developers.com/showthread.php?t=2380314
~Troop

Trooper_Max said:
Ah, I was just thinking maybe it would be possible to write to scratch earlier than the sysrq method becomes available and thus be a little bit safer. It also wouldn't require a keyboard though that point would be a bit moot as you'd need a keyboard once you reboot into recovery. So you're right, it probably doesn't make much difference.
Have you ever done anything with kexec? That was the next thing I wanted to look into once we got something like this for booting more safely. I know people use it for multi-boot methods and someone even came up with a way to hardboot a Nexus 7 with kexec:
http://forum.xda-developers.com/showthread.php?t=2104706
Eventually, I'd like to develop something like that into a boot image that could be stored on the boot or recovery partitions and function as an extra bootloader to allow booting images stored elsewhere.
Anyway, thanks again for sharing your work, and I don't mean to hijack your thread - if you want to discuss ideas I had hoped more people would join in on brainstorming in my thread: http://forum.xda-developers.com/showthread.php?t=2380314
~Troop
Click to expand...
Click to collapse
We used kexec on the vzw sgs3. It may be useful here but really probably isn't too necessary
Sent from my HTC6435LVW using Tapatalk 4

Unable to edit build.prop with rooted phone

Hello everybody,
I'm new to the forum and not that of a newbie concerning Android but since I've updated to Marshmallow on my Nexus 6 I cannot edit the build.prop, even if I'm root.
I already tried a lot of things, since now I used ES File Explorer to edit the file, but now when I want to save it it doesn't work that message appears "Error occurred when trying to save the file. It will not be saved.". So I say ok I'll try using a Build Prop Editor App, it requests root access, I allow it, then fails.
So after many tries I try to completely reinstall the system a second time, thinking maybe there was something I did wrong the first time I installed and rooted, I installed a root checker, it said my phone was correctly rooted, so I try again with ES File Explorer (With root explorer enabled) still the same problem.
Then I find a tutorial on how to get the build.prop via adb shell, which I try, and I have a message saying "Read only File system", so I try to remount but it still the same problem.
Just for the info, the first time I installed Marshmallow and rooted was with a guide on "theandroidsoul" (sory I can't post links since I'm new). And the second time was with the one on ibtimes.
It might not be useful but I tried two different kernels so it might give you some extra info.
Could someone please help me ? I hope I gave you enough information and sorry if I made mistakes, English is not my native language.
Thank you very much for your help.

What version SU did you flash and what kernel are you running? Why would you tell us you ran two kernels but not mention what ones... Lol, were they both stock
With Benzo M2 and supersu 2.46 I edited and saved my buildprop this morning with es file explorer. TWRP 2.8.7.1

scryan said:
What version SU did you flash and what kernel are you running? Why would you tell us you ran two kernels but not mention what ones... Lol, were they both stock
Click to expand...
Click to collapse
Sorry, I'm new and I knew I would forget info...
So I used BETA-SuperSU-v2.49 and yes the kernels I used were stock, the first one was kernel-shamu-mra58k-color-root, and the second one was ElementalX-N6-2.03.
Thank you

Francis_37 said:
Sorry, I'm new and I knew I would forget info...
So I used BETA-SuperSU-v2.49 and yes the kernels I used were stock, the first one was kernel-shamu-mra58k-color-root, and the second one was ElementalX-N6-2.03.
Thank you
Click to expand...
Click to collapse
neither of those are stock, stock is stock... Stock based maybe...
I don't know that all kernels have it sorted yet. I haven't really looked over which ones do, but it seems like it ended up taking a few extra tweaks that everyone is sorting.
Benzino was the first I head people having success with, and I want to say I have heard hells core was working too. If you just want to make it work, my best advice would be to reboot to bootloader, reflash boot.img, immediately boot to recovery (either the volume rockers, or just fastboot reboot recovery should work). then flash Benzino. I can at least tell you is should work there. Dirty flashing kernel may have issue with ramdisk modifications clashing (I don't really know much about this, but its usually recommended not to flash one kernel over another). Once things are settled in a little more, go back to your old favorite kernel?

scryan said:
neither of those are stock, stock is stock... Stock based maybe...
I don't know that all kernels have it sorted yet. I haven't really looked over which ones do, but it seems like it ended up taking a few extra tweaks that everyone is sorting.
Benzino was the first I head people having success with, and I want to say I have heard hells core was working too. If you just want to make it work, my best advice would be to reboot to bootloader, reflash boot.img, immediately boot to recovery (either the volume rockers, or just fastboot reboot recovery should work). then flash Benzino. I can at least tell you is should work there. Dirty flashing kernel may have issue with ramdisk modifications clashing (I don't really know much about this, but its usually recommended not to flash one kernel over another). Once things are settled in a little more, go back to your old favorite kernel?
Click to expand...
Click to collapse
Waou, I just tried Benzino and Super SU 2.46, it worked like a charm in no time, I even didn't have to reflash boot.img ! Should I still do it ?
Anyway, thank you very much scryan, it helped me a lot

Francis_37 said:
Waou, I just tried Benzino and Super SU 2.46, it worked like a charm in no time, I even didn't have to reflash boot.img !Should I still do it ?
Anyway, thank you very much scryan, it helped me a lot
Click to expand...
Click to collapse
Meh.
If there are no problems there are no problems
If things start going wrong... maybe look there first. I don't know too much about what can and can't happen dirty flashing kernels, so I wont say too much... I just know its not normally recommended, but I've seen plenty of people do it and not have major issues anyways. I think its the kind of thing where if one dev did things one way, and another the other... you don't clear them out and the clash.... I'd just be happy with what works

scryan said:
Meh.
If there are no problems there are no problems
If things start going wrong... maybe look there first. I don't know too much about what can and can't happen dirty flashing kernels, so I wont say too much... I just know its not normally recommended, but I've seen plenty of people do it and not have major issues anyways. I think its the kind of thing where if one dev did things one way, and another the other... you don't clear them out and the clash.... I'd just be happy with what works
Click to expand...
Click to collapse
Yes you're right And I am happy with what I have now, thanks to you
I'm glad it's been so quick !