Hey!
I don't know is there posted the insecure boot image file to make "unsecured boot.img" (JRO03C) to "insecure" so I gonna post it here if somebody needs it: (just extract it from the .zip file and flash it via Fastboot/toolkit/.. ADB?..)
So you have to flash this via "Fastboot/toolkit" (for stock JRO03C..)
If you want you can test it does it work on your Nexus if you are using Jelly Bean:
To test the insecure boot image "rooted.img" then write this to fastboot:
fastboot boot rooted.img
To Flash it to phone then just write this..:
fastboot flash boot rooted.img
I always flash image files (.IMG) via Fastboot so others who uses toolkit then it can be flashed with that too..
So the "rooted.img" does not include any kernel, it just includes the ramdisk files and I edited the default.prop to make it to insecured. All other files are stock files in this .img file, "only default.prop is edited".
Test this before you flash this! if you need I can give you the boot.img with the kernel but it is unsecured so then you can't use some commands via ADB..
When you flash this then it replaces the ramdisk files...
Flash this at your own risk if you want to flash this...
This was just what I was looking for to follow these manual root instructions. I prefer doing it this way to better understand each step of the process. Much appreciated for providing the unsecured boot image!
If you have time, would you describe how you create the unsecured boot image to begin with? Or simply link some of the resources you used to learn?
Thanks again!
Idoiocracy said:
This was just what I was looking for to follow these manual root instructions. I prefer doing it this way to better understand each step of the process. Much appreciated for providing the unsecured boot image!
If you have time, would you describe how you create the unsecured boot image to begin with? Or simply link some of the resources you used to learn?
Thanks again!
Click to expand...
Click to collapse
Sorry I didn't notice your reply before..
I followed this instruction: http://www.mydroidworld.com/topic/9778-how-to-create-an-insecure-boot-image/
My guide: http://www.jetdroid.org/forum/viewtopic.php?f=11&t=8005
Related
Hello,
I've been asked a million questions about this.
A) Use the fastboot files for 4.0.1 and do a flash-all and/or do it however you know how. You need to go back to STOCK.
B) Accept the OTA to 4.0.2
C) Let it reboot. Dont be scared. This is a nexus you wont be loosing anything.
D) Flash a 4.0.2 kernel with root enabled (http://www.box.com/s/xf6bz8f1j004bk0zc78a) Credit to Adrynalyne
E) Push the update to /cache/ as update.zip
F) Boot to stock recovery and flash the update
G) Profit
UPDATE: to fix root. Do the following after all is installed:
In order to fix su.
You can try to flash http://downloads.androidsu.com/super...ghi-signed.zip
If you get an assert failure.
You will need to unzip that. and put the su bin in place via recovery then set perm 04755 to it.
Hope this helps. Comes from chains
Hope this helps!
http://www.mediafire.com/?l1wxw3exb9195w7
when i take a pic on 4.0.4 it shows up blue then it saves with the correct colors, does anyone have this problem?
scramjones496 said:
when i take a pic on 4.0.4 it shows up blue then it saves with the correct colors, does anyone have this problem?
Click to expand...
Click to collapse
Nope. I have never seen that. are you using a rom? or real 4.0.4?
the real update 4.0.4, and how do i flash the newboot.img?
You dont need to. If you are already running 4.0.4. You can flash the unprotected boot.img from my other thread.
fastboot flash boot imgname.img
The 4.0.4 update.zip actually checks the boot so if you modify the boot sector (which is what the modified boot.img does) it won't pass the system verification without taking out the part where it verifies the boot section's SHA-1 in the updater script. The only real requirements are stock 4.0.2 radios, bootloader, and boot.
If you've unlocked you can:
- flash the 4.0.2 mysid zip file extracted from the .tgz using fastboot flash update [zip file's name]
- let it load up and reboot on its own
- go back into bootloader
- flash CWM
- choose to go into recovery mode,
- rename the 4.0.4 file to update.zip
- adb push to /data/media/
- choose flash zip from sdcard
- choose the update.zip option
It flashes fine this way. Just have to reflash CWM and flash the su zip.
Much easier 4.0.4 install HERE
Hi, sorry this is a really basic question but I can't find a proper answer.
How do I flash the modules for a kernel? I found the modules folder inside the zip but there are lots of files in it, how do I flash them to my phone?
Also the flashing tools provided with some roms never work for me, fastboot always says something like "....fastboot-windows isn't a recognised internal command..." but I have no problem flashing the boot.img manually through fastboot. Is the flasher tool needed to flash the kernel modules?
Any advice will be much appreciated, I'm trying to get CM9 Domination working but it just boot loops, I assume because I'm not flashing the kernel modules.
Thanks.
How to flash kernels.
first off, there should be two parts to the kernel that you have, first the module, that should be in a .zip format, and also a .img file that should be "kernel-11".img or boot.img or something or other. First you need to open fastboot, and in Command prompt with the ".img" file inside your adb.exe/fastboot.exe/adbwinapi.dll folder that contains these, forward CMD to this folder, , type "fastboot erase cache", then "fastboot flash boot "kernel-11.img" or whatever your .img filename is, then after this is complete you need to reboot recovery, then go to install zip from SD, of which you needed to place the module on your sd card, then simply flash the file and you should have installed your kernel!
^Remember to Hit thanks! ^^
Also, in regards to the error, i dont think your using the folder that you need to be in, What you should do is create a folder somewhere that is convenient for you that you can easily access and remember the address, then add the files fastboot.exe, adbwinapi.dll and adb.exe to, which are all located in your android-sdk/platform-tools/!
Thanks smithr179, I thought I'd have to flash through fastboot or adb, no wonder I couldn't figure it out! Recovery sounds much easier, thanks
The modules in the file I have for the stock kernel are in a normal folder (not a .zip) but they are inside a larger zip folder containing the boot.img, meta inf and system folders. Do I just flash the whole .zip file or should the modules be in a zip of their own?
I'm trying hard to get to grips with all this lol Many thanks for your help
NB. I just tried flashing the whole zip file with everything in it and it worked! Modules were flashed as well as the boot.img. Thanks for all your assistance, much appreciated
http://forum.xda-developers.com/showpost.php?p=24653473&postcount=4
Can someone please upload this file somewhere else? I can't download this file from http://d-h.st/efP
Thanks
Try my guide?
I don't really need a recovery (I'm fine with the official rom), anyway since the link is broken I will follow your guide... Thanks
Then all you need to change is:
Code:
fastboot boot RECOVERYNAME.img
Instead of "fastboot flash recovery recoveryname.img"
Either works, really...and your stock recovery will still be there as soon as you reboot.
There's a system file in place that replaces the recovery on each reboot.
I decided to install the recovery and remove the recovery restore from the rom, even if I don't need it right now it may be useful in the future...
Thanks
Ok firstly this may seem a bit confusing, I am copying this from a PM i sent to @wedgess
Hi, I am wondering if you would be able to make a bootable recovery image with TWRP as i have no idea how to do it and i can only find CWM ones which requires signature for "--update_package="
I don't want a kernel and i don't want a cwm image but i want just simple a TWRP recovery.img which is bootable like http://forum.xda-developers.com/showthread.php?t=1493996 but TWRP instead
Your kernel's work fine but i need it to boot a recovery.img then flash the new rom via "--update_package=" and then reboot device.
For more information check http://forum.xda-developers.com/showthread.php?t=2391169
I hope you can help, Thanks.
-------------------------------
TWRP works great with both the last 2 options so i need to some how create a bootable recovery img based on TWRP but i don't have a clue about kernel development... Could i maybe replace ramdisk with existing bootable recovery or something?
-------------------------------
So to put it simply, I need to switch out CWM on this recovery.img and put TWRP on it (The reasons for this are complicated to explain but i would be extremely thankful if any one could help and credit will be giviven)
So please can any one help me Thanks.
Sorry I didn't reply to your final PM as I said due to real life and limited time I cannot do it for you, But happy to help assisting you if needed. Championswimmer has a tutuorial on what to change in the device tree for TWRP. Search function is down ATM so I can't link you to the thread.
wedgess said:
Sorry I didn't reply to your final PM as I said due to real life and limited time I cannot do it for you, But happy to help assisting you if needed. Championswimmer has a tutuorial on what to change in the device tree for TWRP. Search function is down ATM so I can't link you to the thread.
Click to expand...
Click to collapse
Yeah no worries, Decided to ask any one else, As i really don't have the time to do this aswell as all the other stuff im doing. And it will take some one with experience a lot less time.
I tried switching out the /sbin folder but it didn't work and i didn't expect it to
I am hoping to find some 1 with a linux enviroment all sorted as i don't have a clue when it comes to kernels. surely there is a simple way to switch out a prebuiilt CWM Recovery with a TWRP recovery? Do you know what files TWRP and CWM use?
Thanks.
Altenatively any ideas on what needs to be changed to boot it to recovery always? if so i could modify a existing TWRP kernel (yours for example) and then force it to recovery.
EDIT
I assume you meant this guide?
PORT TO STOCK/ICS/YOU-FAVOURITE-KERNEL
A boot.img consists of the kernel image and the ramdisk (additionally and optionally RPM.bin and commandline). If you want to use TWRP for some other kernel, you have to do this
1. decompile this boot.img (for 2011 models it's a true boot.img, for 2012 models, it's actually a kernel.elf file renamed to boot.img, so you have to decompile accourdingly. you can use my kernel kitchen to do the same)
2. replace the kernel zImage with the one from the kernel you want to port to
3. replace /sbin/ramdisk.cpio with the "UNCOMPRESSED" ramdisk of the kernel you want to port this to. (usually ramdisk is compressed with gzip i.e. ramdisk.cpio.gz. you need to uncompressed ramdisk image i.e. ramdisk.cpio)
4. do not touch anyother thing
5. pack it up into a boot.img (for 2011) or kernel.elf (for 2012) and fastboot it
@wedgess ok so i got it working it now auto boots to TWRP but ADB isn't working, Any ideas?
Thanks so much i got it all working that guide helped
I am curious of what you are trying to do...
As i understand you want:
-flash (only) twrp recovery in fastboot mode
-reboot to recovery and flash rom from pc (adb sideload maybe?)
-reboot to fastboot again to flash kernel
-reboot
If i understand correctly you want to flash ROM (and kernel) from PC side, not dong it from phone?
Bakisha said:
I am curious of what you are trying to do...
As i understand you want:
-flash (only) twrp recovery in fastboot mode
-reboot to recovery and flash rom from pc (adb sideload maybe?)
-reboot to fastboot again to flash kernel
-reboot
If i understand correctly you want to flash ROM (and kernel) from PC side, not dong it from phone?
Click to expand...
Click to collapse
ok this is what happens
1. Download rom and kernel from my kitchen via helper application on windows
2. verifiy md5's
3. fastboot fllash new kernel
4. fastboot boot "recovery.img"
5. once in the new bootable recovery i created/edited, send adb command "adb shell" > recovery --update_package=ROM
6. wait for rom to install, reboot
7. DONE! new rom and kernel flashed
All done automagically and without any user interaction other than picking the rom.
Check post 1 and 2 for more info - http://forum.xda-developers.com/showthread.php?p=46111684
fma965 said:
ok this is what happens
1. Download rom and kernel from my kitchen via helper application on windows
2. verifiy md5's
3. fastboot fllash new kernel
4. fastboot boot "recovery.img"
5. once in the new bootable recovery i created/edited, send adb command "adb shell" > recovery --update_package=ROM
6. wait for rom to install, reboot
7. DONE! new rom and kernel flashed
All done automagically and without any user interaction other than picking the rom.
Check post 1 and 2 for more info - http://forum.xda-developers.com/showthread.php?p=46111684
Click to expand...
Click to collapse
One word: WOW :good:
Not just you have ideas what you can do, but knowledge to do it. You have my respect man :highfive:
i'll check that app ASAP
Bakisha said:
One word: WOW :good:
Not just you have ideas what you can do, but knowledge to do it. You have my respect man :highfive:
i'll check that app ASAP
Click to expand...
Click to collapse
Thanks current released version is quite buggy but new version coming soon
Any way since this problem is now solved, I will close the thread. if you want to discuss this then post on my kitchen thread or pm me
I have a boot.img file that i can use to root my Samsung J2 SM-J260F - if I flash this with Odin everything is Ok. Now I want to edit a file in the ramdisk of the boot.img to make the phone boot on power. However simply unpacking the Boot.img and unzipping the ramdisk then repacking fails - even when i do not edit anything in the ramdisk. When the repacked boot.img is flashed with Odin the device gets into a boot loop.
I am using the Carliv Image Kitchen for Androidv1.3 tool to do the packing and unpacking.
Is there some specific aspect of the Samsung boot.img such as a signature that is causing this to fail?
Progress update
The only unpacking tool that seemed to correctly repack the image was MTK_Extractor_V2.63 - all of the other (many) utilities I tried did not seem to repack the ramdisk correctly and caused the phone to boot into the recovery screen.
Changing the init.rc and init_samsungexynos7570.rc files as follows finally led to success.
In file init.rc
delete everything under "on charger" then add back setprop sys.powerctl reboot
Under "service lpm /system/bin/lpm"
delete class sec-charger critical and replace with trigger late-init
In file init_samsungexynos7570.rc
delete everything under "on property:ro.bootmode=charger"
AndyJN said:
I have a boot.img file that i can use to root my Samsung J2 SM-J260F - if I flash this with Odin everything is Ok. Now I want to edit a file in the ramdisk of the boot.img to make the phone boot on power. However simply unpacking the Boot.img and unzipping the ramdisk then repacking fails - even when i do not edit anything in the ramdisk. When the repacked boot.img is flashed with Odin the device gets into a boot loop.
I am using the Carliv Image Kitchen for Androidv1.3 tool to do the packing and unpacking.
Is there some specific aspect of the Samsung boot.img such as a signature that is causing this to fail?
Click to expand...
Click to collapse
Did you unlocked the bootloader?
Also i would recommend you to use a custom recovery like TWRP to flash boot.img
AndyJN said:
I have a boot.img file that i can use to root my Samsung J2 SM-J260F - if I flash this with Odin everything is Ok. Now I want to edit a file in the ramdisk of the boot.img to make the phone boot on power. However simply unpacking the Boot.img and unzipping the ramdisk then repacking fails - even when i do not edit anything in the ramdisk. When the repacked boot.img is flashed with Odin the device gets into a boot loop.
I am using the Carliv Image Kitchen for Androidv1.3 tool to do the packing and unpacking.
Is there some specific aspect of the Samsung boot.img such as a signature that is causing this to fail?
Click to expand...
Click to collapse
TBM 13 said:
Did you unlocked the bootloader?
Also i would recommend you to use a custom recovery like TWRP to flash boot.img
Click to expand...
Click to collapse
Which.... does not exist. J2 Core doesnt get the same love.
I recommend Android Image Kitchen (AIK) by Osmosis. Havent failed me once in my case.
Prove N. said:
Which.... does not exist. J2 Core doesnt get the same love.
Click to expand...
Click to collapse
I'm sorry, my bad.
has anyone tried to port the 9 pie firmware from J260A to other J260F/M/G?