The kexec and the recovery+boot method was ingenious, but does this mean we can boot custom kernels from the /boot partition now? I was a little worried about trying kexec, and it was holding me back, but will we be able to flash CM10 and boot normally now? Does anyone have the instructions and the files needed, or can point me to where the instructions are?
I've heard so many good things about CM rooms I'm very excited to finally try it on my recently NORMAL (referring to it bein like the ones on all the other carriers) SGS3 very soon.
Thanks
newuser134 said:
The kexec and the recovery+boot method was ingenious, but does this mean we can boot custom kernels from the /boot partition now? I was a little worried about trying kexec, and it was holding me back, but will we be able to flash CM10 and boot normally now? Does anyone have the instructions and the files needed, or can point me to where the instructions are?
I've heard so many good things about CM rooms I'm very excited to finally try it on my recently NORMAL (referring to it bein like the ones on all the other carriers) SGS3 very soon.
Thanks
Click to expand...
Click to collapse
yes, unlock bootloader and flash the non-kexec cm10 nightly!
Once the ROMs are updated for non-kexec, yes. There's a test nightly build for CM10 out now without kexec.
Yeah I would hold off until you get the go ahead from the CM team. Just my opinion though.
Sent from my SGS3 on Synergy Nightlies
Related
Have been hoping to see this happen, but appears we are stuck. I mainly want kernels to use.
rooted 1.55.531.3 with clockwork recovery and SU
Nope still working on it - we as a collective have come to a halt for the moment because the next step requires writing a kernel module that doesn't exist.
Since i'm digging through the kernel code trying to figure out how to do it, i've been also working on the other kernel projects that were either half-done or not started, and yogi2010 and I are taking steps together to write a real nice custom kernel for the doubleshot.
It's gonna take some time, HTC has written their kernel to pull what amounts to a packet-switching tactic when you try to write to the filesystem on a protected partition.
So.. evn if I am rooted and the HTC Dev unlock worked I cant flash roms? or just kernels?
Thanks..
you can flash roms normally...just when your flashing a kernel you have to do it manually
What do you mean manually? Fastboot?
Sent from my SGH-T989 using XDA App
Ya...I have no idea how but I accidentally thanked u but yea thru fastboot
So how possibly will it be now to port MIUI V4 to the infuse now that CM9 is up and running? I'd like to see it. I tried to do it myself. The ROM gets past the kernel splash and to the MIUI boot animation. The bottom buttons light up but it dosen't boot in.
phoenix2217 said:
So how possibly will it be now to port MIUI V4 to the infuse now that CM9 is up and running? I'd like to see it. I tried to do it myself. The ROM gets past the kernel splash and to the MIUI boot animation. The bottom buttons light up but it dosen't boot in.
Click to expand...
Click to collapse
Same here. I can't figure out what I'm doing wrong, and I've already pm'ed some of the other devs, they don't feel like helping. Did you use a guide, if so which one?
kirin0ichiban said:
Same here. I can't figure out what I'm doing wrong, and I've already pm'ed some of the other devs, they don't feel like helping. Did you use a guide, if so which one?
Click to expand...
Click to collapse
No guide. I've ported ROMS before, did it for the Infuse back when Mikey did his first port of MIUI GB. Kinda just know what goes where, or at least I usually do. Not sure what I'm going wrong this time. I'm kinda purposely flying solo as I don't have a full dev environment at home but if I have to I will get ADB working and get a log cat. Any chance you can get one?
Yeah, I have a pretty weak environment set up, I might be able to get you a logcat. It might be later on today or tomorrow, I've been unusually busy this week.
DO NOT FLASH IF YOU HAVE NO INTENTIONS TO CONTRIBUTE TO THE CAUSE!
IT'S BASICALLY NOT USEABLE
(TEST/ PROOF OF CONCEPT)
Here I have a copy of what I have so far. It still needs a lot of work, the touch screen seems to work in spurts and sometimes you can't get past the lock screen. I hardly have the time to continue the work because I am graduating soon and I'm getting prepared for finals. Please acknowledge this simple request, do not make a thread for this nor flash it if you have no intentions to post a log cat/diagnose its symptoms.
Instructions:
1)Flash jt1134's recovery (necessary -- at least if you don't have it)
2)Make sure you were previously on a cm9 rom
3)Wipe data/factory reset
4)Wipe dalvik cache
5)do not format "/system"
6)reboot
7)happy coding
http://db.tt/fOwDUIVE
Sent from my SGH-I997 using Tapatalk 2 Beta-5
i've tried porting it with 6 different miui v4 roms... always gets stuck on boot logo
Okay, so here is the question...
Now that the bootloader is unlocked, we should in theory be able to install any rom that required kexec without kexec, right?
I ask because I would love to reload paranoidandroid rom, but the last thing I need is a brick.
Other than that, I assume its just normal installation of a ROM similar to when I was on an unlocked HTC phone, correct?
The Rom will install fine, but the kernel has to be modified to work without kexec
Kexec roms will still run fine as long as you keep the kexec recovery. Normal roms work too. There is no need to change your recovery or wait for roms to be updated if you unlocked.
Okay thanks to both of you.
I simply do not want to install kexec, knowing that there wouldnt be a reason for it in the future once the developers out there get the roms working without it.
The risk of losing my IMEI is just too much for me, as I rely on my phone for work, and swapping phones and running in circles to get things fixed is too great a risk to take.
stevenjcampbell said:
Okay thanks to both of you.
I simply do not want to install kexec, knowing that there wouldnt be a reason for it in the future once the developers out there get the roms working without it.
The risk of losing my IMEI is just too much for me, as I rely on my phone for work, and swapping phones and running in circles to get things fixed is too great a risk to take.
Click to expand...
Click to collapse
Kexec has nothing to do with IMEI loss. Users of ATT, Tmobile, Sprint, and Verizon have lost IMEI. Verizon is the only one with kexec so clearly that isn't the problem.
con247 said:
Kexec has nothing to do with IMEI loss. Users of ATT, Tmobile, Sprint, and Verizon have lost IMEI. Verizon is the only one with kexec so clearly that isn't the problem.
Click to expand...
Click to collapse
pardon my ignorance, i am sorry.
Before I came to the S3 from a moto x2 and HTC incredible 2 I simply never heard of IMEI issues.
Well, not entirely true... i had a few iPhone's on att which became bricks after a while that had IMEI error codes, they were practically forever unfixable, and apple would just swap them.
i will have to learn about IMEI a little more before i ask further dumb questions.
what you should do is make sure the op in a thred stated that their rom is unlocked and open recovery-compatible. than you may flash without kexec. i for one use twrp to flash cm10 just as an insult to verizon lol.
Stryker1297 said:
what you should do is make sure the op in a thred stated that their rom is unlocked and open recovery-compatible. than you may flash without kexec. i for one use twrp to flash cm10 just as an insult to verizon lol.
Click to expand...
Click to collapse
So close to putting a nice dent into my data and just grabbing cm10 over 4g...
What I really want is paranoid android rom though.
Either way, seems I need to back up my IMEI regardless and can always restore if the process goes wrong.
Sent from my SCH-I535 using xda app-developers app
I saw this post by wang on 591fan
It seems like he has ported a custom kernel and is developing cm10.1 on it.
Thats a good news. We can finally have a stable version of cm
http://www.591fan.com/thread-41545-1-1.html
Looks good if it sorts out the bugs on cm10, id be more than happy !
And what he says in that? I don't understand nothing. Not even using the translator
Even i didnt get what he said.. read the comments and people are exclaiming about a new kernel.. 'sofa and front row' support from me too if its true
I am guessing kexec support has finally come to wang's cm10.1 version. That or he is using 2nd init to load it. This is not a true unlocked BL kernel... just for his cm10.1 only, you will most likely not be able to use it with other roms, unless it a cm based one, that say altered could stuff into his PA versions or something.
The real issue will be battery life and RAM usage, because with kexec and 2nd init, you load the stock kernel then unload that and load the "custom one" so there is still some ram holding some of the "old/stock kernel" all the time.
And cand somebody talk to him? Or at least tell him that we are wondering what he do
Just give it some time you will find out exactly what is going on.....
This sounds complex...so thats why cm10.1 is dead at the moment..bootloader being locked down..i thought a custom kernel wasnt possible.
Any news?
brianmoyano said:
Any news?
Click to expand...
Click to collapse
In a day or two I guess.
nishant203 said:
In a day or two I guess.
Click to expand...
Click to collapse
Its out right now. Check out http://www.591fan.com/thread-43502-1-1.html
That's is great but that does mean we have to load the kernel by kexec and use 2nd inuit like Jim mentioned correct
And will we be able to run the new kernel with Bmm and patch... Would love to try it
Bmm
1. Stock 4.0.4
2. Miui
3. PA 310 4.2.2
4. CMPA 4.1.2
amynjimmy said:
That's is great but that does mean we have to load the kernel by kexec and use 2nd inuit like Jim mentioned correct
And will we be able to run the new kernel with Bmm and patch... Would love to try it
Bmm
1. Stock 4.0.4
2. Miui
3. PA 310 4.2.2
4. CMPA 4.1.2
Click to expand...
Click to collapse
The new ROM and kernel is a single flashable zip file. Wang reminded that the ROM does not support bmm.
From what I read from the forum, some people are facing bootloop after flashing the ROM
Any brave ATT tester ??
I know it won't flash w/ patched bmm... I've Tried bout dozen times
Bmm
1. Stock 4.0.4
2. Miui
3. PA 310 4.2.2
4. CMPA 4.1.2
You can not use BMM to flash this, even with the patch.
YOU MUST use either safestrap, which can boot kexec ROMS, but most likely this will barf since wang has CWM build into his roms with 2nd init, so....
You will HAVE to flash this with bootstrap and it will be your only ROM. I have read that others are having issues getting it to boot at all right now, so my guess is that this is still not ready for prime time yet, go check out the dev thread about the cm10.1 ROM, that hankbizzo5 posted, it talks about everyone bootlooping who has tried this, so far.
jimbridgman said:
You can not use BMM to flash this, even with the patch.
YOU MUST use either safestrap, which can boot kexec ROMS, but most likely this will barf since wang has CWM build into his roms with 2nd init, so....
You will HAVE to flash this with bootstrap and it will be your only ROM. I have read that others are having issues getting it to boot at all right now, so my guess is that this is still not ready for prime time yet, go check out the dev thread about the cm10.1 ROM, that hankbizzo5 posted, it talks about everyone bootlooping who has tried this, so far.
Click to expand...
Click to collapse
it should work just fine with bmm.. of course as long as kexec files are in the right place.. download is almost completed.. will check now..
And considering how things are going, looks like you will have to get back your ATRIX 2 now ..
EDIT: As expected, kexec files are in/system/bootmenu/2nd-boot. Moved to the right place and tried with bmm.. well, once the modules are loaded and kexec executed, bmm loses where the system files are.. but then again, whirleyes says 2nd boot is WIP.. so no option as of now.. I will try editing the ramdisk tomorrow.. hope things work.. now off to installing by bootstrap..
Sent from my MB865 using Tapatalk 2
Ravikirancg said:
Sir, it should work just fine with bmm.. of course as long as kexec files are in the right place.. download is almost completed.. will check now..
And sir, considering how things are going, looks like you will have to get back your ATRIX 2 now ..
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Sorry, but this should NOT work with BMM.... BMM has its own way of handling the boot of the ROM. Wang has CWM built in with 2nd init, even using the patch with the 2nd init and kexec, this should NOT work. It is MUCH safer NOT to use BMM.
There are reasons BMM was made, and the way that CWM being embedded in the ROM with kexec, makes this much more complex, than just the standard boot with your stock kernel, no matter how kexec was implemented.
Yeah I really do not want my A2 back, sorry guys. The whole moto thing left a real bad taste in my mouth, besides working on Ubuntu phone is way more my style anyhow. I am only in here, since it looks like most have bailed. It looks like there are really only 2 devs still left, so I am kind of slowly stepping away. I am still doing some work on the back side, just do not want to do the day to day with it anymore.
Please, look into kexec and how BMM does that pass off, as well as the way that wang has it implemented into the ROM, and where he does the kernel switch off, all of those things matter. It specifically says on 591fan that bootstrap is the ONLY way to do this right now, there are several reasons behind this. BMM is mentioned but not recommended.
As always, you are responsible for your device. Use common sense and make backups
*****THIS IS A TEST BUILD, I HAVEN'T EVEN FLASHED IT MYSELF YET, DRAGONS AHEAD*****
Just a plain old CM13 build with no mods, for hiaewhl(Sprint A9)
***Builds***
07/29/16 First Test Build
Built mostly from CM13 Official hiaeul sources, pulled hiaewhl binaries
Here is the test build
md5sum 525c44e33e9efce3af32c277ba63f23a
****NOT FLASHABLE, WRONG PARTITION SIZES****
8/1/16 Second Test Build
Built mostly from CM13 Official hiaeul sources, pulled hiaewhl binaries
Here is the test build
md5sum 9cb03ec13ee374bd8498e8abb650830d
****BOOT LOOPS****
8/4/16 Third Test Build
Built mostly from CM13 Official hiaeul sources, pulled hiaewhl binaries
Here is the test build
md5sum 82143271ce5ff7a33ae0ac7a644c4bc9
****Still boot loops****
8/4/16 Fourth Test Build
Built mostly from CM13 Official hiaeul sources, pulled hiaewhl binaries
Here is the test build
md5sum 4425937bbc708b1aeeaa7850435d4172
****Hangs on HTC Screen****
***Flashing Directions***
*Must have unlocked bootloader AFAIK
Boot to recovery
Wipe everything
Flash rom zip and gapps zip
***Updating directions***
Boot to recovery
Flash newer version of this rom
Wipe Caches
***Thanks***
CyanogenMod Team
Any and all testers of my work, especially those who donate(it is always appreciated)
***Big Thanks to all those who have Donated***
@ToeJullar @Remesar @jphoff @Stealth5325 @jared-wallace @robak1965
If you feel that I forgot you please let me know
***Sources***
Added soon
If you would like me to link you recoveries, gapps or anything else here just let me know and I will be happy to put it in.
[Reserved]
Sent from my 2PQ93 using XDA-Developers mobile app
Hey man, glad to see some Sprint love finally. Cm13 doesn't require s-off to flash. It use to require others to downgrade firmware to 6.0 but as far as I know the Sprint version shipped with 6.0.1. Until I know for sure it won't bootloop right away I can't risk flashing. But once that is figured out I'll be happy to test.
agraceful said:
Hey man, glad to see some Sprint love finally. Cm13 doesn't require s-off to flash. It use to require others to downgrade firmware to 6.0 but as far as I know the Sprint version shipped with 6.0.1. Until I know for sure it won't bootloop right away I can't risk flashing. But once that is figured out I'll be happy to test.
Click to expand...
Click to collapse
Good to know thanks.
As for an update, I used the partition size from the hiaeul which is apparently different so CM wouldn't even flash lol. I am rebuilding now with the right partition sizes and should have a new build up later today. I will try to flash and report back as soon as I can.
Ok now it gets the "This build is for development purposes only..." message and boot loops there, I think I gotta do some work on the kernel. Will post another update as soon as I can, these fixes may take a little while.
Can someone with S-Off and/or super CID try the second build? The only message I can see that I think may be related in logs is telling me I don't have SuperCID, probably because I don't have S-Off. Not sure if thats really whats causing the bootloop, or if I am even looking at the right logs lol.
I have supercid and s-off
I have supercid and s-off. No flashing errors, no loops, just Hangs at the red "development build" screen... Been there at least 5 minutes and still nothing.
It started to loop after about 8 min and had to force back to twrp.... So s-off and supercid is no different...
Mrpoy13 said:
It started to loop after about 8 min and had to force back to twrp.... So s-off and supercid is no different...
Click to expand...
Click to collapse
Mine never makes it to the boot logo, it loops at the HTC screen without S-Off and/or SuperCID
Thanks for testing!
HRM, not sure where to go next, I could probably get some logs if I could make it to the CM boot animation.
So how to get S-Off when you don't have 25 bucks to spare for sunshine?
Broke down and went the sunshine route... Worked great and fast for s-off but no luck with sim unlock.
Mrpoy13 said:
Broke down and went the sunshine route... Worked great and fast for s-off but no luck with sim unlock.
Click to expand...
Click to collapse
Hey I just uploaded another test, and building another one ATM too. If you have a minute can you test them, my wife has my phone so I won't be able to test for a little while. The first out of the 2 new ones is built from source with a few changes I put in place, and the second one is hacked together using some things from the rooted deodexed stock rom thats floating around.
I think there is a good chance one of these will work, but cannot guarantee it obviously.
miked63017 said:
Hey I just uploaded another test, and building another one ATM too. If you have a minute can you test them, my wife has my phone so I won't be able to test for a little while. The first out of the 2 new ones is built from source with a few changes I put in place, and the second one is hacked together using some things from the rooted deodexed stock rom thats floating around.
I think there is a good chance one of these will work, but cannot guarantee it obviously.
Click to expand...
Click to collapse
:crying: still no joy, the one built from source still bootloops and the hacked together one just hangs at the same screen where it usually bootloops at.
I finally got some good logs though, maybe next build will boot.
No dice, huh?
Let me help you? I'm a great tester/I have knowledge on ROM building.
EVOuser94 said:
Let me help you? I'm a great tester/I have knowledge on ROM building.
Click to expand...
Click to collapse
@miked63017 follow the light!
Any movement on this yet. Really looking forward to it. I'll test if you need... I'm running 1.60.651.xxx...
I'm s-off and super CID. Ready to test anything you wanna try...
Does anyone have back up of sprint stock recovery? Would be really helpful. Thanks
xdeicidusx said:
Does anyone have back up of sprint stock recovery? Would be really helpful. Thanks
Click to expand...
Click to collapse
Just pull it yourself from firmware package.
EVOuser94 said:
Just pull it yourself from firmware package.
Click to expand...
Click to collapse
That's the problem sir, i dont have access to pc and i cant download large files from my phone as i have very limited internet access :crying: