Original GT-I9305 Kernel wanted. - Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve

As the thread states im chasing the original kernel for the 9305T
Much appreciated.

Someone uploaded the XXALI8, and XXALI9 .img a few posts down in this thread:
http://forum.xda-developers.com/showthread.php?t=1932997
Can you flash these over a modified kernel i fyou want to go back to stock?
Im not sure what you do with .img files.... adb shell dd maybe?
you can get all the stock firmwares ones from here too:
http://www.sammobile.com/firmware/?page=3&model=GT-I9305&pcode=0&os=1&type=1

floopyb said:
Someone uploaded the XXALI8, and XXALI9 .img a few posts down in this thread:
http://forum.xda-developers.com/showthread.php?t=1932997
Can you flash these over a modified kernel i fyou want to go back to stock?
Im not sure what you do with .img files.... adb shell dd maybe?
you can get all the stock firmwares ones from here too:
http://www.sammobile.com/firmware/?page=3&model=GT-I9305&pcode=0&os=1&type=1
Click to expand...
Click to collapse
Cheers, i know what to do with them i just didn't have access to them.
It's for a rom im baking.

I think this is it, the boot.img from the original telstra rom

All done
Sent from my GT-I9300 using xda premium

Related

[SOLVED] Where can I get stock 2.3.3 for i9020a?

Update
Thanks to dsixda, an update.zip file is created that, on installation through clockworkmod, will return I9020a's to stock conditions:
system: 2.3.3 build GRI54
kernel: 2.6.35.7-g1d030a7 [email protected] #1
radio/baseband: I9020AUCB2
Link http://www.mediafire.com/?fey8wvmvlhh12uj
Original Link http://android.grdlock.net/index.ph... S&PHPSESSID=9dc0c107b878587d1e0b21ec1e3130ef
I9020A_GRI54_stock_update_with_radio.zip
MD5: ea6a32b590ffd4c6746d1a2caeedfe1c
If you want to install stock recovery after that
i9020a_stock_recovery.zip
MD5: 1b52b993ce58b62a71d8a38ccf0bc667
Recovery is flashed through fastboot
Thanks CraneGuy for radio img and sdixda for everything
[Original Post]
Hello,
My Nexus S I9020a is my first android, so I am new to rooting and flashing.
with the help of this awesome forum I got through with it all and I happily running cm7, so Thank you all.
However, I had a minor set-back... I didn't know about making a nandroid backup before all so I can retain it to its oem state.
If there is someone out there who can provide a link to his i9020a stock back up or there is a stock 2.3.3 out there that is for i9020a.. I would be really grateful.
my original stock info:
Build Number: GRI54
Baseband version: I9020UCKB2 -- now its NO DGSXXKB1 or I9020XXKB1 in bootloader menu
Bootloader: I9020XXKA3 -- I don't think I flashed bootloader at any step since this remains the same
CARRIER INFO: ATT
I did try installing the one in REF post in development, but build number is GRI40 and rebooting in recovery gives triangle exclamation droid.
Thank you for taking the time to read my post.
I am in the same boat. I lost my 3G too. Did you find the stock rom yet?
+1
The price we pay for being trigger happy
crypticsorr0w said:
Hello,
I did try installing the one in REF post in development, but build number is GRI40 and rebooting in recovery gives triangle exclamation droid.
Click to expand...
Click to collapse
That one is easy to fix, just go back into bootloader and fastboot flash recovery...
part 3 of http://forum.xda-developers.com/showthread.php?t=1007782
Thank you for your reply, but this is not what I am looking for as I want stock recovery not clockworkmod. I have that one in the link you provided and without it I would not have been able to install a custom ROM.
crypticsorr0w said:
Thank you for your reply, but this is not what I am looking for as I want stock recovery not clockworkmod. I have that one in the link you provided and without it I would not have been able to install a custom ROM.
Click to expand...
Click to collapse
I can provide you with a nandroid backup of the stock I9020A system.img and boot.img (untouched), but unfortunately I forgot to dump the stock recovery and radio from a shell.
Originally Posted by > dsixda
I can provide you with a nandroid backup of the stock I9020A system.img and boot.img (untouched), but unfortunately I forgot to dump the stock recovery and radio from a shell.
Click to expand...
Click to collapse
Thank you for replying. I won't be that much worried about radio as xxb1/3 somehow has better reception, I even get H most of the time now instead of 3G as when I first had the phone.
Did you obtain those files through CWM? just asking to know in future how do I go about keeping my stock images.
I appreciate your contribution to solve the issue I am facing.
Thanks
crypticsorr0w said:
Thank you for replying. I won't be that much worried about radio as xxb1/3 somehow has better reception, I even get H most of the time now instead of 3G as when I first had the phone.
Did you obtain those files through CWM? just asking to know in future how do I go about keeping my stock images.
I appreciate your contribution to solve the issue I am facing.
Thanks
Click to expand...
Click to collapse
Yes I used CWM recovery. I just flashed that immediately after unlocking bootloader. I didn't root the device beforehand, so when I made a Nandroid backup it was stock.
I can upload it later, going to bed now.
PS. For dumping recovery.img, one way is to use the "dd" command in a shell (along with other parameters specifying the mount location of the image), but you need to be rooted. There are guides online, you can find them in Google search. Haven't experimented with the Nexus S yet but I had done it successfully in the past with others.
Thanks and have a have a great night
Here's the backup, you'll find the link at this site:
http://android.grdlock.net//index.php?direction=0&order=&directory=Samsung Nexus S&
dsixda said:
Here's the backup, you'll find the link at this site:
http://android.grdlock.net//index.php?direction=0&order=&directory=Samsung Nexus S&
Click to expand...
Click to collapse
Thank you sir!
Thank you for your quick response and the files!
After downloading the zip file file i md5sum and it matched what is on the site, however when i try to restore using clockmod it says MD5 MISMATCH. I checked the files once they are on sdcard having the same md5 and it is so. I don't know what else I can do
crypticsorr0w said:
Thank you for your quick response and the files!
After downloading the zip file file i md5sum and it matched what is on the site, however when i try to restore using clockmod it says MD5 MISMATCH. I checked the files once they are on sdcard having the same md5 and it is so. I don't know what else I can do
Click to expand...
Click to collapse
just download the recovery for the i9023 and it wil work fine.....just fastboot flash it
I am using that recovery already, but thanks for chiming in
crypticsorr0w said:
Thank you for your quick response and the files!
After downloading the zip file file i md5sum and it matched what is on the site, however when i try to restore using clockmod it says MD5 MISMATCH. I checked the files once they are on sdcard having the same md5 and it is so. I don't know what else I can do
Click to expand...
Click to collapse
If required, I can make this into a flashable zip so that it can be installed as a ROM.
I solved the issue and now I have my stock GRI54 back!
Thank you!!
the issue was your recovery folder didn't have nandroid.md5 file so I created one and calculated for each file and saved.
Thanks again!
crypticsorr0w said:
I solved the issue and now I have my stock GRI54 back!
Thank you!!
the issue was your recovery folder didn't have nandroid.md5 file so I created one and calculated for each file and saved.
Thanks again!
Click to expand...
Click to collapse
That's strange, when I backed it up there was no nandroid.md5. Can you zip up the md5 and post it here? I could upload the corrected zip.
Edit: I guess I could use this method to calculate md5: http://forum.xda-developers.com/showthread.php?t=714114
just take the file out of the attached zip and put it in your recovery folder then zip and upload
dsixda said:
Or maybe you could also include the stock recovery image mentioned above and make a new md5 based on the new set of files?
Click to expand...
Click to collapse
I think he meant cwm for i9023 not stock. I can't find stock recovery anywhere anyway
crypticsorr0w said:
just take the file out of the attached zip and put it in your recovery folder then zip and upload
Click to expand...
Click to collapse
What method did you use to calculate the MD5? My device doesn't have the md5sum binary.

How do I Inject TWRP into a non-TWRP using rom?

I want to flash over to Slim ICS and try that out for a little bit but I want to continue using TWRP instead of CWM. I know I should be able to inject TWRP through the recovery bit I'm not sure how. Any help?
Sent from my Unicorn powered SGS4G
Juls317 said:
I want to flash over to Slim ICS and try that out for a little bit but I want to continue using TWRP instead of CWM. I know I should be able to inject TWRP through the recovery bit I'm not sure how. Any help?
Sent from my Unicorn powered SGS4G
Click to expand...
Click to collapse
To use the newest TWRP 2.2 you will need to pull the boot.img from aokp and make sure to pull the bcm4329.ko file to. Then using heimdall cmd flash the boot.img and then push the bcm4329.ko file.
The reason is because FB removed the inject TWRP toggle in the new versions.
eollie said:
To use the newest TWRP 2.2 you will need to pull the boot.img from aokp and make sure to pull the bcm4329.ko file to. Then using heimdall cmd flash the boot.img and then push the bcm4329.ko file.
The reason is because FB removed the inject TWRP toggle in the new versions.
Click to expand...
Click to collapse
Ah! Thanks! Where do I find the bcm4329.ko file?
Sent from my Unicorn powered SGS4G
Juls317 said:
Ah! Thanks! Where do I find the bcm4329.ko file?
Sent from my Unicorn powered SGS4G
Click to expand...
Click to collapse
/system/lib/modules
eollie said:
/system/lib/modules
Click to expand...
Click to collapse
Figured, thanks!
Sent from my Unicorn powered SGS4G
If you can't get it, I have a link to a CWM flash able zip that gives you twrp. Here's the link:
http://forum.xda-developers.com/showthread.php?t=1721489
brandonc0526 said:
If you can't get it, I have a link to a CWM flash able zip that gives you twrp. Here's the link:
http://forum.xda-developers.com/showthread.php?t=1721489
Click to expand...
Click to collapse
That is the older version of TWRP. It is a option, I just prefer the newest version it has the quirks ironed out.
I still haven't tested using the GB/CM7 twrp zip that you linked him to in ICS roms. I'll probably get around to making a twrp 2.2/ICS zip for you guys to stay on the safe side since it's easy to get the ramdisk image from an AOKP build. I just need to do it when I'm home.
brandonc0526 said:
If you can't get it, I have a link to a CWM flash able zip that gives you twrp. Here's the link:
http://forum.xda-developers.com/showthread.php?t=1721489
Click to expand...
Click to collapse
I knew that that existed but knowing it was for GB I wasn't gonna use it. Thanks though!
Sent from my Unicorn powered SGS4G
FBis251 said:
I still haven't tested using the GB/CM7 twrp zip that you linked him to in ICS roms. I'll probably get around to making a twrp 2.2/ICS zip for you guys to stay on the safe side since it's easy to get the ramdisk image from an AOKP build. I just need to do it when I'm home.
Click to expand...
Click to collapse
Actually that one works on all the ICS roms. I first tried it on CM9 then I realized it should work on all of them so I tried and it has not once failed on me. The only downside is that its a older twrp but still good.
eollie said:
To use the newest TWRP 2.2 you will need to pull the boot.img from aokp and make sure to pull the bcm4329.ko file to. Then using heimdall cmd flash the boot.img and then push the bcm4329.ko file.
The reason is because FB removed the inject TWRP toggle in the new versions.
Click to expand...
Click to collapse
how do i extract the boot.img?
Juls317 said:
how do i extract the boot.img?
Click to expand...
Click to collapse
Unzip the zip with winrar or whatever you use. Pull the boot.img over to your comp. Then flash it with heimdall.
Code:
heimdall flash --kernel boot.img
Or you could be reallllllllly nice to FB and ask him to make a CWM flashable of the new version of TWRP
hechoen said:
Unzip the zip with winrar or whatever you use. Pull the boot.img over to your comp. Then flash it with heimdall.
Code:
heimdall flash --kernel boot.img
Or you could be reallllllllly nice to FB and ask him to make a CWM flashable of the new version of TWRP
Click to expand...
Click to collapse
Haha, FB if you have time to do such a thing, I'm sure the community would appreciate it! But I'm ok with flashing through heimdall haha
Sent from my Unicorn powered SGS4G
Code:
unzip aokp_galaxys4gmtd_unofficial_milestone-6-03.zip boot.img
That will extract just the boot img, but it has to be don from cmd line. Then do what hecheon says.
eollie said:
Code:
unzip aokp_galaxys4gmtd_unofficial_milestone-6-03.zip boot.img
That will extract just the boot img, but it has to be don from cmd line. Then do what hecheon says.
Click to expand...
Click to collapse
No sh#t you can extract from a zip with heimdall! Thanks Still will most likely use winrar but good to know.
hechoen said:
No sh#t you can extract from a zip with heimdall! Thanks Still will most likely use winrar but good to know.
Click to expand...
Click to collapse
I dont think you can. Im using ubuntu so its the built in extractor.
eollie said:
I dont think you can. Im using ubuntu so its the built in extractor.
Click to expand...
Click to collapse
Damn you linux people. lol

Stock JSS15J kernel + Insecure kernel

I am far from a developer but I pulled the stock kernel for JSS15J, decompiled it and under "default.prop" edit
Code:
ro.secure=1 to ro.secure=0
and
Code:
ro.adb.secure=1 to ro.adb.secure=0
(probably super unsafe)
Recompiled and this booted just fine on my N7(2013), although size did change dramatically?
Anyway, didn't do any other wizardry, as I really don't know any. Hence, why I am attaching the stock kernel as well for actual wizards to perform on.
Stock and Insecure.zip This is hosted on Mega
Full /system /boot and /recovery: http://forum.xda-developers.com/showthread.php?t=2381438
Can you upload system.img too
Yeah, please upload the system.img, I am very curious about it Have a nice day.
nutzu4ever said:
Yeah, please upload the system.img, I am very curious about it Have a nice day.
Click to expand...
Click to collapse
Here you go
CLICK HERE
Credit to Nburnes
phuduong said:
Here you go
CLICK HERE
Credit to Nburnes
Click to expand...
Click to collapse
That's really helpful. Could you also pull the stock recovery if you still have it? The one that's floating around on xda is TWRP masquerading as stock.
dexgen said:
That's really helpful. Could you also pull the stock recovery if you still have it? The one that's floating around on xda is TWRP masquerading as stock.
Click to expand...
Click to collapse
If you tell me what to do, I'll pull the stock recovery for you.
gksmithlcw said:
If you tell me what to do, I'll pull the stock recovery for you.
Click to expand...
Click to collapse
I'm no expert but I think you'd find it here:
/dev/block/platform/msm_sdcc.1/by-name/recovery
But only if you haven't flashed any other recovery.
dexgen said:
I'm no expert but I think you'd find it here:
/dev/block/platform/msm_sdcc.1/by-name/recovery
But only if you haven't flashed any other recovery.
Click to expand...
Click to collapse
Hmm... Pulled up ADB Shell and ls'd that directory and just got an echo of the path back. Tried an ADB pull for the hell of it and got an error stating it remote object was not a file or directory.
gksmithlcw said:
Hmm... Pulled up ADB Shell and ls'd that directory and just got an echo of the path back. Tried an ADB pull for the hell of it and got an error stating it remote object was not a file or directory.
Click to expand...
Click to collapse
You can take a look at this: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Also, can you just check to see if you have /system/recovery.img on your device? It might be the fastest way.
dexgen said:
You can take a look at this: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Also, can you just check to see if you have /system/recovery.img on your device? It might be the fastest way.
Click to expand...
Click to collapse
No recovery.img in the ls of /system; I have recovery-from-boot.p. I'll check the link.
---------- Post added at 05:23 PM ---------- Previous post was at 05:20 PM ----------
dexgen said:
You can take a look at this: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Also, can you just check to see if you have /system/recovery.img on your device? It might be the fastest way.
Click to expand...
Click to collapse
It looks like I need root to do this and, of course, to gain root I have to flash a custom recovery SO I think we're out of luck until Google posts factory images.
If anyone knows how to do it without root, I'll gladly try it.
gksmithlcw said:
No recovery.img in the ls of /system; I have recovery-from-boot.p. I'll check the link.
---------- Post added at 05:23 PM ---------- Previous post was at 05:20 PM ----------
It looks like I need root to do this and, of course, to gain root I have to flash a custom recovery SO I think we're out of luck until Google posts factory images.
If anyone knows how to do it without root, I'll gladly try it.
Click to expand...
Click to collapse
Just an FYI that you can access the stock recovery after rooting. The 'file' you mentioned: "recovery-from-boot.p" causes your custom recovery to revert back to stock after a reboot. If you've rooted a Nexus you may recall that one of the first steps is to change that file to "recovery-from-boot.p.bak" (or similar) so that your system will retain the custom recovery. My point is that you can root with TWRP or CWM, reboot and you'll revert back to the stock recovery. (You don't lose root, just the custom recovery). Pull the stock recovery.img and then flash your preferred custom recovery again. The 2nd time you'll want to change the file to "recovery-from-boot.p.bak" so that you don't revert back to stock again. Make Sense?
swest6602 said:
Just an FYI that you can access the stock recovery after rooting. The 'file' you mentioned: "recovery-from-boot.p" causes your custom recovery to revert back to stock after a reboot. If you've rooted a Nexus you may recall that one of the first steps is to change that file to "recovery-from-boot.p.bak" (or similar) so that your system will retain the custom recovery. My point is that you can root with TWRP or CWM, reboot and you'll revert back to the stock recovery. (You don't lose root, just the custom recovery). Pull the stock recovery.img and then flash your preferred custom recovery again. The 2nd time you'll want to change the file to "recovery-from-boot.p.bak" so that you don't revert back to stock again. Make Sense?
Click to expand...
Click to collapse
It's been awhile since I unlocked my G-Nex and rooted it but I do recall this. I'm hoping CWM for the new N7 shows up quickly.
gksmithlcw said:
It's been awhile since I unlocked my G-Nex and rooted it but I do recall this. I'm hoping CWM for the new N7 shows up quickly.
Click to expand...
Click to collapse
TWRP is out. I haven't tried it, but there is a How To started in General and there is a download link.
Sent from my Nexus 7 using Tapatalk HD
swest6602 said:
TWRP is out. I haven't tried it, but there is a How To started in General and there is a download link.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Oh, I know. I'd rather wait for CWM Touch. Thanks for the link though.
gksmithlcw said:
Oh, I know. I'd rather wait for CWM Touch. Thanks for the link though.
Click to expand...
Click to collapse
Did you see this link: http://forum.xda-developers.com/showthread.php?t=2381544
Brenex said:
Did you see this link: http://forum.xda-developers.com/showthread.php?t=2381544
Click to expand...
Click to collapse
I did, thank you!
Brenex said:
Did you see this link: http://forum.xda-developers.com/showthread.php?t=2381544
Click to expand...
Click to collapse
Flashed CWM through fastboot working fine. I prefer CWM myself. Thanks!
You can also just BOOT into recovery w/o flashing it (fastboot boot recovery <blah.img>. I did this with TWRP and backed up the device's system/boot/recovery.
I assume that would have backed up the original recovery right?
What does insecure means for a kernel?
Sent from my Nexus 7 using Tapatalk 4 Beta
casonswag said:
What does insecure means for a kernel?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It allows ADB to run as root on the devices.
This is really a useful feature for Developers because it allows simplier access to the file system... For Example...
With an unsecure image you can do... "ADB Pulls" and pull files from the /data/ partition on the device (I forget if you can do that or not on a secure image)
But you can also do ADB push which to me is essential because I may be working on, lets say, a custom battery mod or a customer XXXXXXX. And instead of putting it in a flashable zip and flashing it each time I can use an "ADB push" command to push the file where I want it.
Unsecure may not do much for average Joe building ROMS but this is quintessential for developers.
Got it? Good!

[Q] how to reflesh stock kernel?

Ok so i flashed francos kernel trough FKU updater app and i want to go back to stock just to compare the battery life and some stuff again and to decide what to use.
How can i flash stock kernel back, do i flash all factory images or is there .zip file to flash trough recovery, or there is another way to do this? thanks for your replays.
Hi,
Stock kernel here (recovery zip file): http://forum.xda-developers.com/showthread.php?p=47269605.
You can also take a look here to fastboot the boot.img (kernel): http://forum.xda-developers.com/showthread.php?t=2513701.
Alexandar92zr said:
Ok so i flashed francos kernel trough FKU updater app and i want to go back to stock just to compare the battery life and some stuff again and to decide what to use.
How can i flash stock kernel back, do i flash all factory images or is there .zip file to flash trough recovery, or there is another way to do this? thanks for your replays.
Click to expand...
Click to collapse
boot.img is the kernel. If you have the factory images you can just fastboot flash that,
Hammer_Of_The_Gods said:
Hi,
Stock kernel here (recovery zip file): http://forum.xda-developers.com/showthread.php?p=47269605.
You can also take a look here to fastboot the boot.img (kernel): http://forum.xda-developers.com/showthread.php?t=2513701.
Click to expand...
Click to collapse
ok so i just download the zip and flash trough twrp right?
rootSU said:
boot.img is the kernel. If you have the factory images you can just fastboot flash that,
Click to expand...
Click to collapse
oh ok did not know that im quite new to this, but now i know thanks for information.
Alexandar92zr said:
ok so i just download the zip and flash trough twrp right?
Click to expand...
Click to collapse
That's right, download the right zip (4.4 or 4.4.1/4.4.2) put it "in your sdcard", reboot in recovery, flash and reboot, that's all
Hammer_Of_The_Gods said:
That's right, download the right zip (4.4 or 4.4.1/4.4.2) put it "in your sdcard", reboot in recovery, flash and reboot, that's all
Click to expand...
Click to collapse
thanks man i clicked on that thanks button
Alexandar92zr said:
thanks man i clicked on that thanks button
Click to expand...
Click to collapse
No worries, thanks
Last thing since you came from Franco kernel (the following procedure is specific):
The Gingerbread Man said:
Return to stock romz
Franco's kernel changes these system files below, so to change them back you can remove the .bak extension, or fastboot system.IMG and boot.IMG from a Google factory image which is probably easier and faster.
1 - Rename /system/lib/hw/power.msm8974.so.bak to /system/lib/hw/power.msm8974.so
2 - Rename /system/bin/thermal-engine-hh-bak to /system/bin/thermal-engine-hh
3 - Reboot to the boot loader and flash stock Kernel by downloading the Nexus images and then fastboot flash boot boot.img
...
Click to expand...
Click to collapse
So before flashing the stock kernel in recovery do the step 1 and 2 (even after if you forgot, it should be good).
Alexandar92zr said:
thanks man i clicked on that thanks button
Click to expand...
Click to collapse
May i suggest you start reading up before you get into serious rouble. Read the first 4 threads in the General section.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Hammer_Of_The_Gods said:
No worries, thanks
Last thing since you came from Franco kernel (the following procedure is specific):
So before flashing the stock kernel in recovery do the step 1 and 2 (even after if you forgot, it should be good).
Click to expand...
Click to collapse
ok lets see if i understood right.
im comeing from the stock rom just with francos kernel and now to go back to the stock i need to do step 1 and 2, how do i rename that files i connect my phone to pc or i need to download some file menager that can see that files? and about step 3 do i need to flash boot.img via fast boot or i can do it trough twrp as well?
sorry about the many questions but i do not want do do something wrong
Alexandar92zr said:
ok lets see if i understood right.
im comeing from the stock rom just with francos kernel and now to go back to the stock i need to do step 1 and 2, how do i rename that files i connect my phone to pc or i need to download some file menager that can see that files? and about step 3 do i need to flash boot.img via fast boot or i can do it trough twrp as well?
sorry about the many questions but i do not wont do do something wrong
Click to expand...
Click to collapse
With a file explorer, directly from your phone, (Root Explorer, Es File Explorer, etc...) follow the path to the files in point 1 and 2, rename the files and save. Then reboot in recovery and flash the stock kernel if you want to flash it via recovery (equal to step 3).
If you are not used with this kind of stuff (modify system files by yourself), flash the system.img and boot.img by following the link I provided above (http://forum.xda-developers.com/showthread.php?t=2513701).
Hammer_Of_The_Gods said:
With a file explorer, directly from your phone, (Root Explorer, Es File Explorer, etc...) follow the path to the files in point 1 and 2, rename the files and save. Then reboot in recovery and flash the stock kernel if you want to flash it via recovery (equal to step 3).
If you are not used with this kind of stuff (modify system files by yourself), flash the system.img and boot.img by following the link I provided above (http://forum.xda-developers.com/showthread.php?t=2513701).
Click to expand...
Click to collapse
i founded the files that i need to rename via es file explorer and now i understand it all and im not confused anymore about how to get stock kernel back.
im not used to this stuff yet because i rooted my phone yesterday and im quite new to this because last device i rooted and flashed lots of custom roms and stuff is to HD2 so i know the basic stuff but not much
and one of the topic question. why does my colors look a little diferent when i flashed the francos kernel? i know that there is something about color profiles etc. but i do not know where to start and look into that
Alexandar92zr said:
i founded the files that i need to rename via es file explorer and now i understand it all and im not confused anymore about how to get stock kernel back.
im not used to this stuff yet because i rooted my phone yesterday and im quite new to this because last device i rooted and flashed lots of custom roms and stuff is to HD2 so i know the basic stuff but not much
and one of the topic question. why does my colors look a little diferent when i flashed the francos kernel? i know that there is something about color profiles etc. but i do not know where to start and look into that
Click to expand...
Click to collapse
Okay, so all is fine to go back to stock, take your time and read all closely
About the colors, take a look here: http://forum.xda-developers.com/showpost.php?p=49561443 (links for profiles are down, for example: http://192.227.135.147/N5_ColorProfiles/Latest_Profiles/ from vomer).
Hammer_Of_The_Gods said:
Okay, so all is fine to go back to stock, take your time and read all closely
About the colors, take a look here: http://forum.xda-developers.com/showpost.php?p=49561443 (links for profiles are down, for example: http://192.227.135.147/N5_ColorProfiles/Latest_Profiles/ from vomer).
Click to expand...
Click to collapse
thanks i will look into this.
I made a stock kernel backup on Franco app and used it to restore back to stock kernel after using Franco was this process ok
Sent from my Nexus 5 using xda app-developers app

[Q] reverting from custom kernel to stock?

sorry if this doesn't quite belong here but I was curious to go back just to stock kernel, not completely stock itself. Could anyone link me to a good step by step for me to do this? Do i use adbfastboot the boot.img only? Im just a a little confused..
Sorry I am still new and learning. Thanks for any help!
Download the relevant kernel to your device from here.
Reboot to recovery
Install the zip you just downloaded
This stuff tends to be a lot simpler than you'd expect, tbh.
dallas220 said:
sorry if this doesn't quite belong here but I was curious to go back just to stock kernel, not completely stock itself. Could anyone link me to a good step by step for me to do this? Do i use adbfastboot the boot.img only? Im just a a little confused..
Sorry I am still new and learning. Thanks for any help!
Click to expand...
Click to collapse
Download the factory images from Google : https://developers.google.com/android/nexus/images#hammerheadkot49h
Extract the boot.img and flash it via fastboot.. (fastboot flash boot boot.img)
Make sure your on stock rom before you flash it..
Sent from my Nexus 5 using Tapatalk
dallas220 said:
sorry if this doesn't quite belong here but I was curious to go back just to stock kernel, not completely stock itself. Could anyone link me to a good step by step for me to do this? Do i use adbfastboot the boot.img only? Im just a a little confused..
Sorry I am still new and learning. Thanks for any help!
Click to expand...
Click to collapse
Fastboot, you flash with fastboot and yes the kernel image is boot.img. You should probably also reflash your ROM (system.img if you're on the stock ROM) as many custom kernels also modify the system partition.
BirchBarlow said:
Fastboot, you flash with fastboot and yes the kernel image is boot.img. You should probably also reflash your ROM (system.img if you're on the stock ROM) as many custom kernels also modify the system partition.
Click to expand...
Click to collapse
Thanks for all the replies guys!
I am indeed on stock rom. To flash the system.img is pretty much the same as the boot.img yes?
dallas220 said:
Thanks for all the replies guys!
I am indeed on stock rom. To flash the system.img is pretty much the same as the boot.img yes?
Click to expand...
Click to collapse
Hi,
Same way: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701.
Hammer_Of_The_Gods said:
Hi,
Same way: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701.
Click to expand...
Click to collapse
Thank you brother
And just to add to my noobness.. Returning to stock kernel and or rom doesn't wipe any files on the phone correct? Ie picture data etc....?
dallas220 said:
Thank you brother
And just to add to my noobness.. Returning to stock kernel and or rom doesn't wipe any files on the phone correct? Ie picture data etc....?
Click to expand...
Click to collapse
As long as you don't flash the userdata.img, you are fine!
If you are using the flashall script then remove the -w flag and you're good to go!
Sent from my Nexus 5 using Tapatalk
vin4yak said:
As long as you don't flash the userdata.img, you are fine!
If you are using the flashall script then remove the -w flag and you're good to go!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I plan on flashing sys and boot!
And so sorry but what do you mean the flashall srcipt?
Would that be basically flashing everything to stock?
Sorry for such dumb questions
dallas220 said:
I plan on flashing sys and boot!
And so sorry but what do you mean the flashall srcipt?
Would that be basically flashing everything to stock?
Click to expand...
Click to collapse
So no worries since you don't flash all (you use the "Method2" from the link I posted above), about the "flash-all.sh" file, when you open the factory image file, you have this script, more info here about the "-w" to delete: http://forum.xda-developers.com/showpost.php?p=51949577&postcount=4.
Hammer_Of_The_Gods said:
So no worries since you don't flash all (you use the "Method2" from the link I posted above), about the "flash-all.sh" file, when you open the factory image file, you have this script, more info here about the "-w" to delete: http://forum.xda-developers.com/showpost.php?p=51949577&postcount=4.
Click to expand...
Click to collapse
thanks for you help my brother. Just another question.. If I have a nandroidbackup on the computer that I made before I installed my custom kernel, could you somehow use that to get back to the stock kernel? Is that something...or I am just asking the most ridiculous questions?
It seems the more I read, the less I am confident with adb, flashing, backups etc.... :S
dallas220 said:
thanks for you help my brother. Just another question.. If I have a nandroidbackup on the computer that I made before I installed my custom kernel, could you somehow use that to get back to the stock kernel? Is that something...or I am just asking the most ridiculous questions?
It seems the more I read, the less I am confident with adb, flashing, backups etc.... :S
Click to expand...
Click to collapse
If want the stock kernel download the factory images from google and flash the boot.img via fastboot. That's the easiest way.
If you still want to use nandroid backup then copy the nandroid backup to the correct location... Head over to Philz Touch recovery and use the custom restore option by which you can select only the "boot" and "system" partition. But I haven't tried doing it so can't say whether it will work or not. However, technically it should work. I have no idea how to do this using TWRP though as I haven't used it much.

Categories

Resources