Hi all.
I have created for users a kernel installer, to take out the hassle of typing out commands yourself.
For this to work, there are some requirements that must be met.
1-you have bootloader unlocked
2-you have fastboot drivers already installed. if you dont, please install them
This was created on windows 7, and i am yet to find out if it works on anything else. So please let me know.
I currently have 2 versions. The first is just the installer itself. Where you add your kernel (the boot.img) to the folder yourself. The second, is set up to install DooMLords latest kernel (version 3).
In the future, I am hoping to also create (with the developers permission), a one click installer for custom ROM's.
To use, just extract the folder, if necessary add your boot.img, then double click "FLASH KERNEL" and plug your phone in. The installer reboots the phone into the correct mode itself and wait
Plain installer (no kernel)
http://www.4shared.com/file/pJZy6Osc/kernel_flasher.html?
DooMLords DooMKerneL auto installer
http://www.4shared.com/file/WlrTYOxa/doomkernel-version3-autoinstal.html?
Credits:
DooMLord for his amazing work on kernels and many other releases
and many others who's names i cant think of right now, but the developers should know who they are!!
you are all amazing and a great inspiration!!
EDIT:
i am currently running androhero's ROM and dooms kernel on my phone, which were both installed via this method. if all goes well and i have no issues with the ROM, and i hear back from androhero with permission, i may soon be able to roll out easy installers for custom roms
Can this work for CM7 kernel? (if there is one)
I used the XDA App to post this, what did you use?
Cat_On_Droid said:
Can this work for CM7 kernel? (if there is one)
I used the XDA App to post this, what did you use?
Click to expand...
Click to collapse
that's the kernel i was using when i built the code
just download the kernel from the cm7 thread, download the plain installer, add the boot.img to the extracted folder, and BOOM!!! cm7 kernel installer!!
No disrespect but is it so much easyer than type this few fastboot commands?
^ I also thought about that, but users with winxp will find it helpful
I used the XDA App to post this, what did you use?
IE-coRe said:
No disrespect but is it so much easyer than type this few fastboot commands?
Click to expand...
Click to collapse
some people dont feel comfortable doing it, or get it wrong. and may mess things up. this allows people to do it in a simple way.
and also, i plan to expand this into a one click type of installer to take out the hassle (and mistakes) of installing custom roms.
in essence, the less a noob has to do, the less they can get wrong and then we might have fewer people on the forum saying "i broke my phone :'(" etc. hehe.
okay thats true
Cat_On_Droid said:
^ I also thought about that, but users with winxp will find it helpful
I used the XDA App to post this, what did you use?
Click to expand...
Click to collapse
I just copy the address line in the folder window and 'cd' + paste (folder address) in the cmd window and you're good to go with issuing commands. Some .exe files also works when drag and drop into the cmd window on winxp. Pretty sure it works with fastboot.exe and i know that bunzip2/bzip2 works that way on winxp.
Then again i feel comfy doing things from a cmd window and think it's more fun that way. Well flashing from recovery is also a nice way to do things, comes in handy when out and about. Used it alot with my HTC Desire HD.
Anyway nice move @solitarymonkey i think it'll come in handy for some users that don't feel comfy in all this cmd/fastboot thingy
Regards Dousan...
solitarymonkey said:
some people dont feel comfortable doing it, or get it wrong. and may mess things up. this allows people to do it in a simple way.
and also, i plan to expand this into a one click type of installer to take out the hassle (and mistakes) of installing custom roms.
in essence, the less a noob has to do, the less they can get wrong and then we might have fewer people on the forum saying "i broke my phone :'(" etc. hehe.
Click to expand...
Click to collapse
[CONSTRUCTIVE CRITICISM]
I dont like the idea of real nooby noobs installing custom roms.
If they cant copy-paste a few commands i think it is a bad idea to have them run custom roms.
I would however like to see a stock rom + kernel installer, that wipes the cache and data(option), and relocks the bootloader(option).
[/CONSTRUCTIVE CRITICISM]
Azeazezar said:
[CONSTRUCTIVE CRITICISM]
I dont like the idea of real nooby noobs installing custom roms.
If they cant copy-paste a few commands i think it is a bad idea to have them run custom roms.
I would however like to see a stock rom + kernel installer, that wipes the cache and data(option), and relocks the bootloader(option).
[/CONSTRUCTIVE CRITICISM]
Click to expand...
Click to collapse
i understand what you are saying. but in a way, shouldnt something that's open source be available to everyone?
and when i get the chance, i'll have a look into your suggestion. although flashtool can do that if you have both the ftf of the official rom that you want, and the bootloader lock file from blagus' tutorial thread ^_^
Ok so I'm one of the n00bs that this type of program will help.
I was wondering: is it 1) possible and 2) beneficial/additive to install something like doomlord's kernel while on the stock ROM?
I would really like to my phone to run faster, have better battery life, and have the ability to overclock and I think doomlords accomplishes all that.
What do you think?
btw r800x verizon unlocked bootloader by Alejandrissimo
Dyelon said:
Ok so I'm one of the n00bs that this type of program will help.
I was wondering: is it 1) possible and 2) beneficial/additive to install something like doomlord's kernel while on the stock ROM?
I would really like to my phone to run faster, have better battery life, and have the ability to overclock and I think doomlords accomplishes all that.
What do you think?
btw r800x verizon unlocked bootloader by Alejandrissimo
Click to expand...
Click to collapse
Sorry, no dice. Doomlords's kernel won't work with the stock r800x Rom.
Sent from my R800x using xda premium
antEris said:
Sorry, no dice. Doomlords's kernel won't work with the stock r800x Rom.
Sent from my R800x using xda premium
Click to expand...
Click to collapse
Hm. well thanks anyway man....I'll probably wait until cyanogen doesn't have any profound deficiencies then
This is a nice tool you put together!
I understand where the other guys are coming from but i think this too will save me some time for sure!
DrROBschiz said:
This is a nice tool you put together!
I understand where the other guys are coming from but i think this too will save me some time for sure!
Click to expand...
Click to collapse
Indeed. For people who regularly flash different roms and need different kernels for them, it removes the tedious and repetitive task of typing the same thing again and again. And it gave me something to do and experiment with for you guys ^_^
Sent from my R800i using xda premium
Related
Presenting bmlunlock. Unlocks bml7 for writing to it via dd.
http://github.com/CyanogenMod/android_device_samsung_bmlunlock
Nice! Thanks Koush.. it's about time you did some actual work around here..
lol brandon. you know better. he pushed out 2 updates to CWM for us in less than ten minutes last night!
Yeah, I was just kidding. What really makes this useful is this bmunlock and the updated adb access via recovery. Very slick.
BHey would it be possible to use this to flash the kernel of a facinate from a mac? If so could you guys give a quick explanation of how. Us mac users are itching to get ready for roms.
If someone can do the terminal write up for the bmunlock kernel flash on windows we can probably figure out how to do it on our macs..... anyone? Please.
Well first somebody needs to cross-compile that .c source from github for android.
I don't have the tools to do that ATM, but I'll work on that.
From the README on koush's github it looks like you just run the bmunlock executable on the device, which unlocks the partition and then use dd to flash the kernel zImage contained within the tar.zip posted here: forum.xda-developers.com/showthread.php?t=787168
I'll work on this on my Fasc and post clearer instructions if I'm successful.
You rule Koush! Missing your work since i switched from the Droid to Fascinate. Thanks a lot keep it up!
I'm sorry, but what exactly is this?
If you don't know, you don't need it.
It allows devs to flash kernels directly.
adrynalyne said:
If you don't know, you don't need it.
It allows devs to flash kernels directly.
Click to expand...
Click to collapse
Well... guess I don't need it. LMFAO! ... Moving on.
The fascinate needs it.
Sent from my SCH-I500 using XDA App
keith.mcintyre26 said:
The fascinate needs it.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Redbend works as well.
Sent from my SCH-I500 using XDA App
adrynalyne said:
If you don't know, you don't need it.
It allows devs to flash kernels directly.
Click to expand...
Click to collapse
Ah. Then I don't need it. I appreciate the work Koush, but I don't know a thing about programming and I'm not a dev.
How do I compile it for the GB kernel? Do I just need to use the cross compiler?
We have an issue with the Pop Plus (GT-S5570I) flashing kernels via zip files. Sometime they do not flash at all. Others they do. It is a real pain in the butt.
Miche1asso said:
How do I compile it for the GB kernel? Do I just need to use the cross compiler?
We have an issue with the Pop Plus (GT-S5570I) flashing kernels via zip files. Sometime they do not flash at all. Others they do. It is a real pain in the butt.
Click to expand...
Click to collapse
Look at the date of the last response... 2010...
For gingerbread, you can use bmlwrite instead of redbend:
https://github.com/CyanogenMod/andr...s-common/blob/gingerbread/bmlutils/bmlwrite.c
bhundven said:
Look at the date of the last response... 2010...
For gingerbread, you can use bmlwrite instead of redbend:
https://gist.github.com/CyanogenMod...s-common/blob/gingerbread/bmlutils/bmlwrite.c
Click to expand...
Click to collapse
I know… But that is what we have in our custom ROMs and I was hoping someone could still answer, as you did.
I'll check bmlwrite. Thanks!!
This is just a link to CM9 over in the OG GS2 Developer forums:
http://forum.xda-developers.com/showthread.php?t=1410400
THIS IS NOT NOOB FRIENDLY
IF YOU HAVE TO ASK, YOU PROBABLY SHOULDN'T BE DOING THIS.
MAKE A BACKUP THROUGH CWM
Download the ODIN files from the linked thread
Copy Google Apps and Face Unlock zips to SD Card
Reboot into Download mode
Flash the ODIN files (warning::: this flashes a ICS bootloader) -- Edit, try without flashing bootloader first. It's safer.
Reboot into Recovery
Flash Gapps and Face Unlock zips
Do a factory reset (yes, AFTER installing everything)
Reboot
Set up your phone
Reboot again
PLAY AROUND FOR A WHILE
Restore backup to go back to whatever you were using before
If something confuses you, this probably isn't for you and you should wait for a i777 version of the ROM to be availible (it won't take long, please wait and save all of us from DIS ROM BRICK MAH FONE threads).
Things that don't work:
Everything listed on the CM9 Alpha page +
Home Button = Back Button & Back+Search buttons do not work
Phone does not work (and flashing the RIL in the CM9 thread will not fix this == it's a kernel problem)
This isn't my work, I'm linking and providing instructions on how to flash an ALPHA ROM. The phone DOES NOT work!
I'm not affiliated in anyway with Team Hacksung or Cyanogen.
You don't have to flash the ODIN files, just use the CWM zip he provided.
Nyk0n. said:
You don't have to flash the ODIN files, just use the CWM zip he provided.
Click to expand...
Click to collapse
Those don't flash the ICS Bootloader. It will not work.
Worked for me. No need for the ics bootloader.
Nyk0n. said:
Worked for me. No need for the ics bootloader.
Click to expand...
Click to collapse
Noted then. Thank you
I feel like it's useless without a phone lol
Sent from my SAMSUNG-SGH-I777 using xda premium
noobs have needs too
Nyk0n. said:
Worked for me. No need for the ics bootloader.
Click to expand...
Click to collapse
You must have already had an i9100 bootloader.. the install script he provides with his cwm release specifically looks for the model number.. flashing i777 roms don't so you may not have noticed up until mnow.
Just remove the first two lines in the script and it won't check.
edit: I've always been very careful and have never flashed any bootloaders on this phone. Just to clarify I didn't have to edit the script on this one though, but i have on others in the past.
Nyk0n. said:
Just remove the first two lines in the script and it won't check.
edit: I've always been very careful and have never flashed any bootloaders on this phone. Just to clarify I didn't have to edit the script on this one though, but i have on others in the past.
Click to expand...
Click to collapse
I errored out with getprop("ro.product.device ...GT 9100. To try your solution I'd edit build.prop? And I can just remove the lines, not change to i777?
Thanks
shishir95 said:
please wait and save all of us from DIS ROM BRICK MAH FONE threads)
Click to expand...
Click to collapse
Lmao!!! That line cracked me up so bad!!! thats just too funny and sadly true
jdbeitz said:
I feel like it's useless without a phone lol
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Maybe it's worth waiting until a version specifically for our phones comes out.
wesbalmer said:
You must have already had an i9100 bootloader.. the install script he provides with his cwm release specifically looks for the model number.. flashing i777 roms don't so you may not have noticed up until mnow.
Click to expand...
Click to collapse
Nyk0n. said:
Just remove the first two lines in the script and it won't check.
edit: I've always been very careful and have never flashed any bootloaders on this phone. Just to clarify I didn't have to edit the script on this one though, but i have on others in the past.
Click to expand...
Click to collapse
LimpyShox said:
I errored out with getprop("ro.product.device ...GT 9100. To try your solution I'd edit build.prop? And I can just remove the lines, not change to i777?
Thanks
Click to expand...
Click to collapse
Use the ODIN files.
LimpyShox said:
I errored out with getprop("ro.product.device ...GT 9100. To try your solution I'd edit build.prop? And I can just remove the lines, not change to i777?
Click to expand...
Click to collapse
In scripting line doesn't always mean one actual line of text it's one line of code, you need to remove everything up to the first ";"
LimpyShox said:
I errored out with getprop("ro.product.device ...GT 9100. To try your solution I'd edit build.prop? And I can just remove the lines, not change to i777?
Thanks
Click to expand...
Click to collapse
Sorry should have explained better, i was running an i9100 port at the time. That's why i didn't need to edit the build.prop. And to answer your question just remove the first two lines, you'll see once you get it up in notepad.
Pretty cool, seems to be running on my phone, cetainly just something to play with, not really too functional overall as far as any kind of Daily. Thanks for the link.
New build posted this am dated 12/26, comes with a few more fixes
Sent from my SGH-I777 using XDA App
Nyk0n. said:
Worked for me. No need for the ics bootloader.
Click to expand...
Click to collapse
There were changes to the bootloader from froyo to gingerbread on the i9000 that the rom depends on, so one can assume there to be similar bootloader changes. It's probably best to wait for Atin to give us some proper information and/or a build for the i777 after the holidays.
Sent from my SGS II.
slifer315 said:
There were changes to the bootloader from froyo to gingerbread on the i9000 that the rom depends on, so one can assume there to be similar bootloader changes. It's probably best to wait for Atin to give us some proper information and/or a build for the i777 after the holidays.
Sent from my SGS II.
Click to expand...
Click to collapse
I just flashed using the latest CWM package and it worked happily for me no problems at all. It is kind of interesting. I like ICS and can't wait until they get all the bugs sorted out when some new leaks happen.
PatriotXT92 said:
I just flashed using the latest CWM package and it worked happily for me no problems at all. It is kind of interesting. I like ICS and can't wait until they get all the bugs sorted out when some new leaks happen.
Click to expand...
Click to collapse
What do you mean by everything worked happily for you? What didn't work for you? What version did you flash? Anything else you want to share about your success?
Sent from my SGH-I777 using XDA App
the version airbus is working on seems to run a tad better than this cm9 one.
I'm planning on getting this device shortly & was wondering if the stock kernel will work with most of the roms developed here? I'm just trying to do my homework so I can be ready when I have it in hand. I'm so ready to ditch the g2x.
Sent from my LG-P999 using xda premium
TBH I haven't seen a stock kernel NOT work with a Custom ROM. The only thing is some of the features i.e. Wifi Calling may not work. So it's always best to flash the recommended to avoid boot loops or bugs.
I just looked at four of the most popular ROMs, and in less than five minutes read that only one of them said stock kernel was ok. The other three say to flash either faux's kernel, xboarder's newest kernel, or the included boot.img in the download.
But yes the stock kernel will work but like just mentioned it will have limited functionality. In my opinion, read what the dev says in their OP and throughout their thread, but a whole thread on this isn't necessary.
I don't mean to be rude, just saying it like it is. Welcome!
Sent from my HTC_Amaze_4G using XDA App
Thanks for ur replys guy's. I have always used the stock kernel with every rom on every device I've used. I'm new to flashing kernels & every time I tried flashing a kernel I've always had issues. Thanks again for ur answers.
Sent from my LG-P999 using xda premium
I wonder how this thread's topic relates to development...
Okay let me clarify the whole kernel thing.
We have three types kernels to chose from.
The stock OTA kernel. That's what your phone comes with. It is secured which means it will not allow scripts to auto-start (which means that init.d is worthless) and does not default with superuser access from adb or terminal. You can still get root access but you always need to do "su" command.
The unsecured kernel. This is the kernel that comes with your rom. This is commonly found in the zip file of the custom rom that you download. The custom rom DOES NOT (which also means DOESN'T, WON'T, WILL NOT, CAN'T and CAN NOT) update the kernel by recovery like almost all the other phones do. We believe this is because we have bootloaders with S-ON. When or IF we get s-off we may be capable of flashing a kernel by recovery.
Faux123's kernel.
Refer to [Kernel]HTC Stock[2.6.35.13](v0.0.7)OC~1.73/UV/CIFS+UTF-8[Dec-30]
Q&A
But can't we flash Faux's kernel by recovery?
Yes and no. I developed a workaround to make that work however it doesn't directly flash the kernel from the recovery. It flashes the kernel after the phone has already booted which is why a second reboot is required.
Well... why not? I don't understand.
Unfortunately since the phone MUST come to a complete boot from a kernel that initiats init.d scripts (unsecured kernel as described above), we cannot use the above method going from a pure rooted OTA rom or when going from SenseUI 3.0 to SenseUI 3.5 or ICS roms. Let me know if you're confused by this.
Alright... so can you tell me more about Faux's kernel?
Well since I'm not Faux123 I'll try to answer this.
It's a slightly modified version of the unsecured kernel (capable of executing init.d scripts) that has been tweaked to allow slight over clocking and control over the voltage going to the CPU and RAM of the phone. This can help you or hurt you. You can push your processor harder and faster to increase performance but you may lose stability and drain your battery faster. Alternatively you can reduce the voltage and preserve battery life. At this time the kernel is NOT complete due to HTC not releasing the full source of their TI drivers. It would appear that since it is not technically their drivers, they don't have to release it.
So... what's the problem making the kernel?
Faux123 tried to make the kernel from source, unfortunately without the full source attempting to do so will lose wifi and wireless tethering abilities. Again... blame HTC for that. Until they release the full source we're stuck with this limitation.
So all this talking about kernels you still haven't explain how to flash it?
This part is easy.
Use this: [Guide][Tool] Kernel Flasher 2 Step/Kernel Restore Tool||Noob Proof||V3 released || or whatever directions are included with the ROM or kernel that you're interested in flashing. If you're skilled enough you can just use the fastboot commands.
From bootloader:
fastboot flash boot c:\directorytoboot\boot.img
(replace c:\directorytoboot with actual directory)
So in conclusion... as soon as HTC releases s-off for our devices as well as the full kernel source code we can have some really kick @$$ phones! Until then... we have to [email protected]$$ everything such as fastboot flashing our half-a$$ modified kernels. It's not the rom or kernel developers fault... it's HTC's.
Felinos11 said:
I wonder how this thread's topic relates to development...
Click to expand...
Click to collapse
Yeah yeah... I'll move it.
Thank you binary for your excellent explanation. I posted it here because the people with the knowledge frequent this board & hope they would see it. I apologize if I posted this in the wrong place.
Sent from my LG-P999 using xda premium
Binary100100 said:
Yeah yeah... I'll move it.
Click to expand...
Click to collapse
so how do I go back to stock kernel binary!!!!! i kid, i kid!!!
Stock kernel works fine.
seansk said:
so how do I go back to stock kernel binary!!!!! i kid, i kid!!!
Click to expand...
Click to collapse
Go choke on some nitrous.
Binary100100 said:
Go choke on some nitrous.
Click to expand...
Click to collapse
I love nitrous oxide, we had to try in in school, you should try it sometimes, we use it on kids, and some adults unfortunately that act like kids on the dental chair
seansk said:
I love nitrous oxide, we had to try in in school, you should try it sometimes, we use it on kids, and some adults unfortunately that act like kids on the dental chair
Click to expand...
Click to collapse
I'll try it while at the range. The range masters should love that.
Binary100100 said:
I'll try it while at the range. The range masters should love that.
Click to expand...
Click to collapse
Hmm...I don't know if those two will mix well!!!
Now that we have s-off can the devs please start adding the kernel to the rom so we can flash it all in one?
I just think that it will make it easier for the average user.
Devs have become accustomed to packaging roms this way for quite some time and many users are still having issues getting S-Off.
I wouldn't be surprised if the next round of updates packaged the Kernel/Rom together.
I due time my friend.
Sent from my ADR6425LVW
Be nice if someone familiar with the process or the script could just post how to add the boot.IMG to current roms so we could add them in and flash in recovery. Think con posted templates, but assuming we would still need a script added. Otherwise, I am patient
Sent from my ADR6425LVW using xda premium
mjh68 said:
Be nice if someone familiar with the process or the script could just post how to add the boot.IMG to current roms so we could add them in and flash in recovery. Think con posted templates, but assuming we would still need a script added. Otherwise, I am patient
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
It should work if you just put the boot.img inside the kernel folder of the roms zip. I just flashed a kernel with cons template and it worked perfectly
The way I have done it to my GB ROM is to add the following code to the updater-script and remove the previous code written by con. It worked fine in GB but so far I have had no luck with ICS. I have PMed a couple of the pros for a little assistance and try and figure out what the issue could be.
This is the code used in previous ROMs:
Code:
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
The Devs already know how to do it..just a matter of implementation.
Sent from my ADR6425LVW
Marcismo55 said:
The Devs already know how to do it..just a matter of implementation.
Sent from my ADR6425LVW
Click to expand...
Click to collapse
Well I'm still waiting for them to let me in on the big secret. Con said the code should work and he would look into it if/when he gets time. Also brought it up with scott and I believe he was going to look at it as well. I do know of another way of doing it (like they do on the Xoom) but I would need some additional information.
for anyone interested the ROM with the kernel (flashes when you flash the ROM) is posted here as a test:
http://forum.xda-developers.com/showpost.php?p=25228652&postcount=78
My 3.6 ROM has both versions now. Give it a try and let me know how it works for you.
NilsP said:
My 3.6 ROM has both versions now. Give it a try and let me know how it works for you.
Click to expand...
Click to collapse
Ya i'm not doing both versions in my ROMs. I just don't see it as being necessary. If you have the kernel in place already there is no need to reflash it. All it does is make me want to blow my brains out every time I can't boot into recovery because of the damn PH98IMG. Thats just me though its good to see you supporting both. Reality is I would rather just post the kernels separate then to have the phone create the images.
zone23 said:
Ya i'm not doing both versions in my ROMs. I just don't see it as being necessary. If you have the kernel in place already there is no need to reflash it. All it does is make me want to blow my brains out every time I can't boot into recovery because of the damn PH98IMG. Thats just me though its good to see you supporting both. Reality is I would rather just post the kernels separate then to have the phone create the images.
Click to expand...
Click to collapse
Same here...
TB13 said:
Same here...
Click to expand...
Click to collapse
Glad I'm not the only one..
Due to the nature of the s-off method many people decided to forego s-off. Getting s-off was quite difficult and many people are still having issues with the timing. I don't see devs switching to adding the kernel to their .zips unless they put downloads for both s-off and s-on devices.
Sent from my ADR6425LVW using XDA
Can anyone put into layman's terms the initial process of rooting a phone? I have the OTA and there's no root method, so I'd like to manually root via TWRP. Is busy box mandatory for root? If not, should I get it or pass on it? Where do I get the package to flash? Then for supersu....where do I get the binaries/zip package for that?
I want to ruu back to actual stock and then manually root, but the only thing I cab find is the root scripts, which don't work. I'm having issues with the 1.22 rooted Rom which I believe stem from stripping out firmware and or hboot and stuff. Since I'm already updated is prefer to work from the actual stock build.
This could be a great starting point for those with phone that are already updated... Anyone care to help?
Sent from my EVO using xda app-developers app
kornface13 said:
Can anyone put into layman's terms the initial process of rooting a phone? I have the OTA and there's no root method, so I'd like to manually root via TWRP. Is busy box mandatory for root? If not, should I get it or pass on it? Where do I get the package to flash? Then for supersu....where do I get the binaries/zip package for that?
I want to ruu back to actual stock and then manually root, but the only thing I cab find is the root scripts, which don't work. I'm having issues with the 1.22 rooted Rom which I believe stem from stripping out firmware and or hboot and stuff. Since I'm already updated is prefer to work from the actual stock build.
This could be a great starting point for those with phone that are already updated... Anyone care to help?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
well chill for one second xD you dont need and cant use any of that mess if you dont have root
what you did is whats preventing you from rooting, which was updating to 1.22, as far as i understand, the current methods dont work for getting you root, sooo, maybe im wrong but i believe theres a trick where u can RUU back to the old 1.33 or whatever, but look in the original development thread
Of course its still possible. Why couldn't I ruu (to 1.22)...run HTC unlock...flash twrp...flash supersu...flash busybox? Boom, I'm rooted on a stock build. I know the current scripts can't do it, bit I can definitely do it manually if I have all the right resources....or if I knew what I was doing... Right??
Sent from my EVO using xda app-developers app
kornface13 said:
Of course its still possible. Why couldn't I ruu (to 1.22)...run HTC unlock...flash twrp...flash supersu...flash busybox? Boom, I'm rooted on a stock build. I know the current scripts can't do it, bit I can definitely do it manually if I have all the right resources....or if I knew what I was doing... Right??
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
if the htc site doesnt have it, and you know how, then you should post your method xD
otherwise idk what your saying...
If you want root and s-off use the links in my signature where it says ]ROOT] and [s-off]
Just concerned with root... It says it works up to 1.13. I've already done the OTA so I'm 1.22... Will it still work?
Sent from my EVO using xda app-developers app
Didn't you already answer your own question in the 3rd post in this thread. You seem to already have the answer.
However, I will say this is discussed in several other threads already just spend a little bit of time searching and you'll find the directions to help you. The time you'll spend searching is as much time as you've put into this thread already.
Sent from my EVO using xda premium
Rocklee99 said:
if the htc site doesnt have it, and you know how, then you should post your method xD
otherwise idk what your saying...
Click to expand...
Click to collapse
If I knew what I was doing I'd gladly post . Give me some time....I'll get there.
brandonmaze said:
Didn't you already answer your own question in the 3rd post in this thread. You seem to already have the answer.
However, I will say this is discussed in several other threads already just spend a little bit of time searching and you'll find the directions to help you. The time you'll spend searching is as much time as you've put into this thread already.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I have been searching.....I've spent HOURS and HOURS on this forum the past few days. I guess I'm just looking for confirmation that what I want to do is in fact the right thing to do... Everyone is so set on all the root scripts, but noone says what that process actually is. And that's what I want. I want the process so I can start contributing without just taking everyone else's work. I think there's a ton of people in my same situation (htc unlocked, s-on, accepted the OTA) that wants a simple way to get back root without reflashing entire roms. So I guess my three big questions are...
1.) I understand that root requires an app (superuser or supersu) as well as the binaries. I have no idea where these binaries are. Where would I get the supersu ones? Is it flashable? Where do the "binaries" actually go?
2.) Busybox...do you have to be rooted to install it? It seems like you do if this is really a set of tools not included in stock android. Maybe I'm wrong though. And more importantly....where do you get it. I'll be honest, I haven't searched around on this issue yet, so maybe the answers already out there... I just wanted to ask in case someone felt like layin down some knowledge.
3.) The flashable zip. I guess I could unzip one and see what's inside, but I'm sure someone on here can explain so it makes more sense than I'd gather by just unzipping and looking around. Like for instance, so flashable zips are entire roms...some are just radios...some are simple tweaks. This leads me to believe there's a script inside defining what to actually do. Let's say I wanted to create my own flashable zip which included TWRP, the root binaries and supersu, as well as busybox. Do I create a perl script called your_moms_a_skank and include it with all the other files? Is there a certain filename (instructions) the android operating system looks for when you flash a zip? Shoot i dunno.....I guess I'll start ripping these apart and seeing whats inside....
If you can't answer all three, that's fine. Any information is better than none... You all are awesome and I would buy you all cupcakes if I knew where you lived... Don't actually tell me where you live because the cupcakes will never come. I'll eat them long before they make it to the post office. I'm just saying....I'd consider buying you a cupcake. And it's the thought that counts...so you have to be happy about this.