[Discussion] replacing the bootloader - Galaxy S I9000 General

Since many of u want to have max ram available while maintaining some feature, i just have a thought if we can use grub instead. I saw that there is a boot option. So may be we can change it and when boot up we can choose which kernel to boot from. U guys think its possible or not?

Would be great and should be possible, RyanZa made an app to change kernel dierctly on the phone so it is possible.
About boot loader, we could use CW:
When the phone starts it boots on CW automaticaly (without using the combo keys...)
We choose the kernel
We boot the phone with the selected kernel.
And also an option to disable/enable automatic launch of CW.

+1 for that
Sent from my GT-I9000 using XDA App

Some sort of built in disk/partition manager might rescue 90% of the brick cases as well..

Related

Samsung Continuum Questions

Hey guys, I have a few questions that I either couldn't figure out after researching for hours (seriously) or I just need some clarification on. I apologize if these questions have already been adressed. Also, I'm new to android so try to keep it simple for me.
1. What is a kernel? Can I flash multiple kernels to the same rom? Can I flash a kernel via clockwork recovery?
2. Ive been having problems with clockwork recovery. I got it installed (meaning I can get to the clockwork recovery menu after flashing the .tar file via odin and applying the update.zip) but if I select any of the items from the clockwork recovery menu the screen immediately goes blank and I have to perform a battery pull to boot the phone up again.
3. Clockwork recovery doesnt stick. When I apply the update.zip (which contains clockwork recovery mod) from the regular recovery menu I get a "e:verification whole-file error" message thingy unless I flash the .tar file via odin every single time before hand in which case I do get to the clockwork recovery menu, but the problem from the question above occurs.
4. How to flash the latest clockwork recovery + any needed kernel + any bug fixes + latest version of needed files? Plz post a link to a place where I can download the appropriate files. I ask this even though its been asked before because im wondering if the files I used are outdated and thats why I had the problems mentioned above.
5. Is there anyway I can restore my phone back to the way i first bought it (meaning no root, no update, etc.)
Thanks in advance!
Sent from my SCH-I400 using XDA App
The only one I can answer out of those is #5 (I suck at the coding part lol, I'll let someone more knowledgable answer those)
Go to settings -> Privacy -> Factory Data Reset.
Pretty sure that's what you're looking for
You're having weird problems. My clockwork doesn't stock either but I don't think anybody's does with the continuum. I have a clean DL17 ROM, the peanutbutta jelly time kernel and I haven't had any problems
Sent from my SCH-I400 using XDA App
Ill try again later on today and ill see what happens. Maybe it was just a one time glitch. Are you supposed to select the items from the clockwork recovery menu using the camera button or the menu button?
On a separate note, about the clockwork recovery sticking, i heard about a kernel that made it stick. True or false? And if I install a kernel on my phone now, and then flash the DL17 rom, do the effects of the kernel now apply to the DL17 rom as well? does the clockwork recovery mod that i flashed before also apply to the DL17 rom as well, or do i have to reinstall clockwork recovery? what bugs does the DL17 rom have? where are the fixes?
Sent from my SCH-I400 using XDA App
Oh and whats the difference between the following kernels? and can they all be flashed using clockwork recovery? and which kernel do you use? and what bugs to each of the kernels have?
1. http://forum.xda-developers.com/showthread.php?t=1057072
2. http://forum.xda-developers.com/showthread.php?t=943833
3. http://forum.xda-developers.com/showthread.php?t=926555
Sent from my SCH-I400 using XDA App
Can someone please post a link of this thread in the continuum android development section or point this thread to a dev because I don't have permission and I really badly want these questions answered! Thanks!
I'll try and answer some of your questions as soon as I get to a computer.
Sent from my space time Continuum using the XDA App.
EDIT:
1. I'm not a dev, but here is what I understand about kernels. A kernel is part of android that contains the "drivers". You can use different kernels with the same ROM, but if you're asking if you can use 2 kernels at the same time with 1 ROM, then no, you can't. Kernels are usually flashed with clockwork, but we continuum users also use ODIN because of the difficulties with CWM not wanting to work on some phones.
2. Are uoi using the menu button to select in CWM? If you are, try clicking the lock button instead.
3. I can't help you there, sorry. :-/ My CWM always worked...
4.I'll see if I can't find a guide or 2. I'll make another video tut if needed.
5. There is a stock ODIN file that I helped make floating around here somewhere. The only thing is, the ODIN is rooted because it was needed to create the files.
I'll answer more questions later
Ok thanks a lot that helped clarify a few things. A video tutorial or a written tutorial would be great and if u could answer my other questions that would be fantastic! Thanks
Sent from my SCH-I400 using XDA App
Oh and do u flash a kernel in odin by putting the .pit file in the pit section and the kernel in the pda section?
Sent from my SCH-I400 using XDA App
Flash kernels using clockwork
Sent from my SCH-I400 using XDA Premium App
ntien said:
Oh and do u flash a kernel in odin by putting the .pit file in the pit section and the kernel in the pda section?
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
Yes, that is how you flash a kernal in odin.
I didn't have to do mine that way
Sent from my SCH-I400 using XDA Premium App
Thanks for the answers guys! Can u look at the other questions that I posted and try to answer them?
Sent from my SCH-I400 using XDA App
ntien said:
Ill try again later on today and ill see what happens. Maybe it was just a one time glitch. Are you supposed to select the items from the clockwork recovery menu using the camera button or the menu button?
On a separate note, about the clockwork recovery sticking, i heard about a kernel that made it stick. True or false? And if I install a kernel on my phone now, and then flash the DL17 rom, do the effects of the kernel now apply to the DL17 rom as well? does the clockwork recovery mod that i flashed before also apply to the DL17 rom as well, or do i have to reinstall clockwork recovery? what bugs does the DL17 rom have? where are the fixes?
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
AGH!!!! SO MANY QUESTIONS IN 1 POST >.<
ok.... Let's try and answer these *sigh*
1. If you are using the original CWM then, select is using the lock button. If you are using the new CWM the imnuts put out a few days ago, then selecting is the camera button. The latest CWM available, is the first link in the next quote.
2. ugh... I can't really comment on that, I've never had problems with CWM...
3. Yes, they do apply to the DL17 ROM.
4.CWM sticks as long as you flashed all the files correctly.
5. Which DL17 ROM? Adr's SC, or the debloated?
6. again, which one?
ntien said:
Oh and whats the difference between the following kernels? and can they all be flashed using clockwork recovery? and which kernel do you use? and what bugs to each of the kernels have?
1. http://forum.xda-developers.com/showthread.php?t=1057072
2. http://forum.xda-developers.com/showthread.php?t=943833
3. http://forum.xda-developers.com/showthread.php?t=926555
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
1. This is from what I know, just CWM. There isn't a "kernel" so to speak.
2.This is an epic kernal that I recommended trying
3. I would also recommend trying out this kernal. I'm not entirely sure what the differences between 2, and 3 are though...
ntien said:
Hey guys, I have a few questions that I either couldn't figure out after researching for hours (seriously) or I just need some clarification on. I apologize if these questions have already been adressed. Also, I'm new to android so try to keep it simple for me.
1. What is a kernel? Can I flash multiple kernels to the same rom? Can I flash a kernel via clockwork recovery?
2. Ive been having problems with clockwork recovery. I got it installed (meaning I can get to the clockwork recovery menu after flashing the .tar file via odin and applying the update.zip) but if I select any of the items from the clockwork recovery menu the screen immediately goes blank and I have to perform a battery pull to boot the phone up again.
3. Clockwork recovery doesnt stick. When I apply the update.zip (which contains clockwork recovery mod) from the regular recovery menu I get a "e:verification whole-file error" message thingy unless I flash the .tar file via odin every single time before hand in which case I do get to the clockwork recovery menu, but the problem from the question above occurs.
4. How to flash the latest clockwork recovery + any needed kernel + any bug fixes + latest version of needed files? Plz post a link to a place where I can download the appropriate files. I ask this even though its been asked before because im wondering if the files I used are outdated and thats why I had the problems mentioned above.
5. Is there anyway I can restore my phone back to the way i first bought it (meaning no root, no update, etc.)
Thanks in advance!
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
1. From wikipedia:
"In computing, the kernel is the central component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components). Usually as a basic component of an operating system, a kernel can provide the lowest-level abstraction layer for the resources (especially processors and I/O devices) that application software must control to perform its function. It typically makes these facilities available to application processes through inter-process communication mechanisms and system calls.
Operating system tasks are done differently by different kernels, depending on their design and implementation. While monolithic kernels execute all the operating system code in the same address space to increase the performance of the system, microkernels run most of the operating system services in user space as servers, aiming to improve maintainability and modularity of the operating system. A range of possibilities exists between these two extremes."
You can only run one kernel at a time.
2. dfggd's instruction vid might help: http://www.youtube.com/watch?v=USHpl0s7qhk
3. CWM does not stick (yet)
4. You'll have to do your own research on this one. Personal taste comes in to play and it is ever-changing.
5. I know there's a DJ20 dump around here somewhere....
hahahaha im sorry but i have a lot of questions lol. thanks for the help. if u can answer the other questions thatd be great, thanks. and in response to your answers:
TO DFGGED:
1. i need plain english here. whats the difference between the two clockworks? does it really matter which one i flash? if not, then i plan on using the original clockwork recovery mod so that i can flash a different kernel.
2. maybe its becuz i used the menu button to select an item so it freaked out. ill try it again as soon as i can find somebodys windows computer i can borrow to flash odin
3. and if i flash a kernel its permanent? i cant remove the kernel or flash a different kernel and overwrite it or something?
4. i definitely flashed all the files correctly and it didnt stick for me. maybe we just have different definitions of sticking. i have to flash odin every single time prior to going in to clockwork recovery. do u not have to do the same? i heard that flashing a custom kernel made it stick though so maybe thats it...
5. wait...i thought Adr's DL17 rom was the only one out for the samsung continuum. and that is the debloated/debinged/etc. isn't it?
6. if there are different roms and im just clueless, then can u post the link for both of the actual rom and fixes?
TO DFGGED(PART 2):
1. but doesnt it say flash the recovery kernel via odin? is that not a kernel?
2. what does this kernel do?
3. again, what does this kernel do?
TO WEUDEL:
1. kind of understood that lol but at least i get the basic idea
2. yup that helps to clarify a bit, thanks
3. i heard that custom kernels DOES make it stick. true or false?
4. look at my questions to dfgged above (in this post) and see if u can explain the differences to me in the kernels and original clockwork recover vs. imnuts clockwork recovery (and if imnuts clockwork recovery's recovery kernel is actually a kernel) and if there are indeed two different roms and the difference between them. and a link to a place where i can download the latest files for the fixes and actual rom. i would really appreciate it!
5. yup found it. thanks
oh and how do you flash a kernel via clockwork?
thanks so much for ur patience!!!! i owe all of u guys lol
ntien said:
oh and how do you flash a kernel via clockwork?
thanks so much for ur patience!!!! i owe all of u guys lol
Click to expand...
Click to collapse
You go to install zip file then install from sd card
Sent from my SCH-I400 using XDA Premium App
Well, since you are now over the 10 post threshold, I would suggest that you ask the specifics of these kernels within the kernel threads. That or try them all out and go with the one you like. This is a small community and the more testing everyone can do the better off we will all be.
I would but I dont have a windows computer so testing is pretty much impossible for me so...yeah anything anybody knows about the questions I just asked would be extremely helpful. Thanks again
Sent from my SCH-I400 using XDA App

Is kindle fire capable of dual booting?

Well as some of you have already seen that some phones are capable of dual booting such as ONE particular windows phone (don't remember the name of the phone) Which was able to boot into Android software while still being able to keep its stock windows Rom. Well my question is, is it possible for the kindle fire to be able to boot into another Rom like "CM7" or others as such while still keeping the stock Rom?
Sent from my Kindle Fire using xda premium
Do you mean actual dual booting, or just booting a rom within a rom? I helped a friend boot Android 2.2 on her windows phone one time and she loved it.
I dont know if you can boot one android rom within another android rom. Though I could be completely wrong.
As I do recall there is a way to boot Ubuntu Linux within an Android rom so if someone puts together a good app, it just may be possible.
A Rom within a Rom?? That's CRAZY talk lol no but In all seriousness I was thinking like when you boot up your device, it will load a screen asking you if you want to boot into the stock Rom or whichever other Rom you have installed. Such as CM9 or what have you. Or when you boot your device, it will boot into the stock Rom and from there you can choose to boot into another Rom.
Sent from my Kindle Fire using xda premium
Well in relation to what I helped a friend do with her phone and Android/Windows mobile, was that you loaded an exe from windows mobile and it rebooted her phone into android and stayed until a reboot was triggered.
But as for an option to boot to a particular OS... I suppose if someone hijacked the bootloader(which is a viable option with an unlocked bootloader such as on the fire) and then threw in a quick app that checked for bootable partitions or folders with boot files in it, listed them for you and then booted based on what you chose... then sure...
Is that possible? I think it is... although I am not the dev to do it as I have no knowledge of this type of thing.
Maybe JackpotCalvin or someone else might have some kind of better ideas.
Corey
Nothing is impossible, its just very very difficult. Unless of course you know what you're doing,then its easy. Anyways thank you for your helpful reply.you answered my question perfectly. But it IS an interesting concept towards a mobile device.
Sent from my Kindle Fire using xda premium
Glad I could be of a some help for you.
Never be affairs to ask if you need more help.
Corey
The Touchpad can dual boot. When booting, I can select which OS I want: WebOS or CM7. It's definitely possible if there's enough space, and I'm all for it since I'm a Prime member and love having access to unlimited videos.
Sent from my GT-I9100 using XDA App

[hack][2ndboot] Custom kernel (no radio)

So, currently it boots.
Phone not working.
Credits to it goes to droid-dev and of course to Quarx.
So. Like you can see in cm7 you already have 2ndboot.ko.
So, secret here.
All files here: http://fjfalcon.ru/2ndboot/
How to use it...
Code:
insmod 2ndboot.ko
mknod /dev/hbootctrl c `cat /proc/devices |grep hboot|awk '{print $1}'` 0
./hbootuser /sdcard/2ndboot/hboot.cfg
After executing last command press touchscreen... or it won't boot.
What needs to be done for phone to work.
We need to be able to boot different kernel it would help a ton with cm7 and cm9.
Sent from my XT720 using xda premium
mchlbenner said:
What needs to be done for phone to work.
Click to expand...
Click to collapse
The milestone hackers have been stuck here for ages (well, mostly it seems they surrendered a long time ago) and I feel like they're way cleverer than I am. From what I understand, the wrigley usb modem can't be reinitialized (or at least nobody knows how to and there's a severe lack of documentation available to use) and nobody's figured out how to migrate the initialized state to the new kernel. My understanding is that they've decided that kexec wants to reinitialize everything but the modem decides to panic and die instead. I don't really know what I'm talking about, though. I think it needs new eyes. I looked at the drivers a while ago and I didn't think there was a lot of wierdness going on, it registers communication channels and can destroy them, but I guess the problem is that even that basic channel dies.
So, I been working on the ksplice approach (but haven't made any progress). Kexec would be so much easier though. I also have been thinking about making a UART... did quarx make one for defy? Do you think it's the same as the milestone one? But do we really need UART if we can already boot a custom kernel (fastboot, 2ndboot)?
Sounds very hard to do? Is their a demand for this to be done.
For myself I'm a bit burnt out on hacking on this phone.
Sent from my XT720 using xda premium
fjfalcon said:
So, secret here.
All files here: http://fjfalcon.ru/2ndboot/
Click to expand...
Click to collapse
Are you running on Russian sbf? Do you just take devtree from sbf? I assume cmdline comes from /proc/cmdline I just tried on xt720mod.sbf and it started, but crashed during bootanim so probably need to update cmdline and devtree. But really cool nonetheless!
I guess touching the screen is just to cause an interupt?
So what's rhe current thinking--does quarx think atags will help fix the phone? I can work on creating a module for it. Or maybe it's easier to also read atags from a file, too. Hmm. Need to figure out if atags is passed verbatim from cdt or modified by the bootloader... we can probably just save it once from boot5 via fastboot.
Quarx thinking that atags is only bytes.. our current problem with kexec is that function not implemented error on kexec_load
Yea, cmdline and devtree from russian sbf.
Is source for your 2ndboot.ko on github or fjfalcon.ru somewhere?
I used 2ndboot dat was.. so time ago with ms1 repo.
fjfalcon said:
I used 2ndboot dat was.. so time ago with ms1 repo.
Click to expand...
Click to collapse
Ah, ok. Did it work for you? I haven't had luck with these files yet. I'm about to build uart.
Yes, it was working.. =)
Thanks! Do you remember if you used:
http://gitorious.org/droid/2ndboot
or
http://xvilka.github.com/2ndboot-ng/
Here is a idea start new thread!!!!!!!
Sent from my SGH-T759 using xda premium
fjfalcon said:
Yes, it was working.. =)
Click to expand...
Click to collapse
Ok, got it to 2ndboot your last version (i.e. the no radio version) using CBW sbf and your CyanogenMod-7.2.0-MilestoneXT720-20120916-KANG-signed.zip build. Next, I'll try to rebuild all the parts.
Edit: attached fjfalcon's 2ndboot files
Here's a WIP build based on nadlabak and skrilex_cz's latest 2ndboot source for Milestone A853. Source is at
http://github.com/CyanogenModXT720/2ndboot
With this newer 2ndboot what I notice is that ADB works and usb pluging and unplugging is detected (that didn't work for with the previous version). I don't have a SIM with me at the moment, but I assume the radio does NOT work--from what I understand there are patches to the kernel that need to be applied.
I don't think it's necessary to touch the screen to get it to boot--but I have been making sure the screen on. The boot is slower than I expect (maybe because files are being read from sdcard rather than internal, but who knows at this point). Anyway, it takes me about 3-4 minutes after running hbootuser before I see the bootanim start (your phone looks like it's crashed until bootanim starts).
I haven't been able to build a kernel that boots. It's very strange. I can build a working boot.img that works fine via fastboot, but when I take the exact same zImage and use it for 2ndboot, I can't get it to work.
I will switch phones and test this out and let you know if radio works!
i will tests your builds.
I take it you extract from zip put 2ndboot into recovery?
It could not be found in open recovery what im i doing wrong?
Sent from my SGH-T759 using xda premium
You extract the contents of the zip into /sdcard/2ndboot an the run /sdcard/2ndboot/2ndboot.sh (I do it via adb)
I haven't been able to run it from open recovery yet. I've tried, but it causes a full reboot.
Sent from my Nexus 7 using XDA Premium HD app
Mioze7Ae said:
You extract the contents of the zip into /sdcard/2ndboot an the run /sdcard/2ndboot/2ndboot.sh (I do it via adb)
I haven't been able to run it from open recovery yet. I've tried, but it causes a full reboot.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I had same issue. I tried via openrecovery and had a full reboot.
How do you do via adb (in recovery or in Android ) ? Because when I do that from android via adb it freeze.
Well, adb does freeze... you have to wait for the boot animation... and it really takes a long time. After you 2ndboot you have to think of your phone as if it were back at the (M) stage of boot, but with whatever happened to be on the screen when 2ndboot started instead of the (M).
Sent from my Nexus 7 using XDA Premium HD app
Mioze7Ae said:
Well, adb does freeze... you have to wait for the boot animation... and it really takes a long time. After you 2ndboot you have to think of your phone as if it were back at the (M) stage of boot, but with whatever happened to be on the screen when 2ndboot started instead of the (M).
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
So I haven't wait. I will try that and tell you if I have radio. But do I have to have a custom boot.img ?
Sent from my Milestone XT720 using xda-app.
EDIT : Finally I tried : after a long time I had boot animation then screen was black. I press power button (short press) then I had M logo and bootanimation and then android. Android is fully working with radio and it doesn't ask me for pincode. But I mean I had a full reboot.
Can you confirm that I have to seen M logo with 2ndboot or that I had a full reboot ?
EDIT : When screen go black : no need to press button it reboot. I think it doesn't work and make full reboot but I am not sure.
What are the exact steps to follow to make this work?
I would like to try this as well.
Thank you.
Sent from my XT720 using xda premium

Passcode-password-disable.zip

Is there anyway to get this (Passcode-password-disable.zip) to open on my phone?
I have a spare Samsung Galaxy S4 that I don't remember the security info for.
I'm trying to use my other S4 to disable my pattern on my spare...
Help!
Try fastboot
get fastboot then type in
fastboot erase userdata
fastboot erase cache
fastboot reboot
Ok. I'll give it a shot. Thanks
Just enter stock recovery and wipe data, turn phone off, hold volume up, home and power buttons at same time, when phone comes on release power button but continue to hold the other 2 and phone will boot into recovery mode, wipe data and reboot!!! Back to fresh start!!!
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Lol that's the thing though, I have stuff on there that I'd like to keep. But I do appreciate the gesture thank you!
HiHoZebra... Away!!!
Use aroma file manager
Tutorial u can find in xda
Ok I'll try that. Thanks
ramz78 said:
Use aroma file manager
Tutorial u can find in xda
Click to expand...
Click to collapse
You are my savior! Thank you so much
Sent from my HTC Glacier using XDA Free mobile app
One can also use a tool created by an xda contributor built on aroma. It is called Dr. Megan's Multitool I think. It gives u all kinds of options including flashing Rom, modem, kernel, boot loader, custom recovery, apps etc and gives u an option to disable passcode. No data loss involved.
centaur31 said:
One can also use a tool created by an xda contributor built on aroma. It is called Dr. Megan's Multitool I think. It gives u all kinds of options including flashing Rom, modem, kernel, boot loader, custom recovery, apps etc and gives u an option to disable passcode. No data loss involved.
Click to expand...
Click to collapse
Ok thank you!
Does multitool requires root ?
Sent from my GT-I8190 using XDA Premium 4 mobile app

Rom Manager for the Nexus 4?

Hello there!
Well, my phone isn't in the best of conditions. The digitizer doesn't work in select parts of the screen and my power button is completely non functional. This has made it impossible to do things in the recovery without getting stuck in there for good until the battery drains out. I really want to flash a new rom though and I've been wondering if rom manager works on the nexus 4 well. Will i have to use CWM or is TWRP fine? I basically just want to automate the whole process so i won't have to do anything in the recover. Any feedback is appreciated
If you want to use twrp, use twrp manager.
Sent from my Nexus 9 using XDA Free mobile app
MultiRom

Categories

Resources