Related
Credits:
- DooMLord -> his recovery sources on github, and his guidance on assisting me with setting up the build environment and for his kernel.sin unpacker.
- Sony Ericsson -> the kernel with this.
I wanted the stock kernel because of battery drain issues present in many custom kernels, mine included, because although I used the semc sources to compile my kernel, it still had worse battery drain than stock.
I have unpacked the zImage from the kernel.sin in the 4.0.2.A.0.42 and then made that and a modified ramdisk into a boot.img, which you can flash.
This is for people who want to stay with the stock kernel, but want clockworkmod recovery.
Kernel string version:
Code:
2.6.32.9-perf
[email protected] #1
Download: http://dl.dropbox.com/u/13729847/semc/kernels/stockCWM/boot.img
MD5: 1ad7e6db6258b73555f0e6ae73fe4fd6
To flash, use the command:
Code:
fastboot flash boot boot.img
If you are on linux:
Code:
./fastboot -i 0x0fce flash boot boot.img
Don't forget to say thanks if you use this!
Yo installed it the custom recovery works fine and now testing UPDATE-looks like its not starting up for me ill try a reflash UPDATE-its not working properly the system wont start man
Super interested in this since I went back to Stock rom moments ago so I can play FIFA 12. Will this work with the new HK 4.0.2.A.0.58 rom released as I have just put that on.
matknny said:
Super interested in this since I went back to Stock rom moments ago so I can play FIFA 12. Will this work with the new HK 4.0.2.A.0.58 rom released as I have just put that on.
Click to expand...
Click to collapse
wait now dat i think about it i have the same firmware as urs it doesnt work on it weird
matknny said:
Super interested in this since I went back to Stock rom moments ago so I can play FIFA 12. Will this work with the new HK 4.0.2.A.0.58 rom released as I have just put that on.
Click to expand...
Click to collapse
Yes, .42 and .58 use the same kernel.
Will this provide root? I only install Doom's for root & recovery, so if this does I'll use this instead. Thanks.
alreadyused said:
Will this provide root? I only install Doom's for root & recovery, so if this does I'll use this instead. Thanks.
Click to expand...
Click to collapse
No root, but you can flash RootXperia.zip in clockworkmod (search it on google: rootxperia.zip).
Done but having booted after installing and rebooted into recovery (which worked) then restarted to phone it wont boot. Black screen after Sony Logo.
Update: Boots after 15 minutes no battery but now android market is keep coming up unsuccessful
Update 2: It just will not boot so I had no choice but to flashtool 4.0.2.a.0.58 back to default. :-(
matknny said:
Done but having booted after installing and rebooted into recovery (which worked) then restarted to phone it wont boot. Black screen after Sony Logo.
Update: Boots after 15 minutes no battery but now android market is keep coming up unsuccessful
Update 2: It just will not boot so I had no choice but to flashtool 4.0.2.a.0.58 back to default. :-(
Click to expand...
Click to collapse
Actually had market problems myself too, it is very wierd :/
Doesn't work at all for me - fastbooted it left it for a bit
came back and got the red blinking light.
What is the trick to get a stock kernel.sin to a working boot.img ? (Spent most of this afternoon failing to get it to work). All I really want is ro.secure=0 (or ro.debuggable=1). fastbooting CWM is ok for me.
unrandomsam said:
Doesn't work at all for me - fastbooted it left it for a bit
came back and got the red blinking light.
What is the trick to get a stock kernel.sin to a working boot.img ? (Spent most of this afternoon failing to get it to work). All I really want is ro.secure=0 (or ro.debuggable=1). fastbooting CWM is ok for me.
Click to expand...
Click to collapse
Small how-to for creating insecure kernel
1) Unpack kernel.sin to get zImage and ramdisk (tools posted in my other thread)
2) unpack ramdisk
3) edit default.prop and set ro.secure=0 & ro.debuggable=1 then save file
4) repack ramdisk (cpio.gz)
5) repack into boot.img, using zimage + new packed ramdisk, using correct mkbootimg arguments
6) flash using fastboot
7) enjoy
PRO TIP:
Use ONLY LINUX FOR ALL OF THIS ELSE DEVICE WONT BOOT
Sent from my R800i using XDA App
DooMLoRD said:
Small how-to for creating insecure kernel
1) Unpack kernel.sin to get zImage and ramdisk (tools posted in my other thread)
2) unpack ramdisk
3) edit default.prop and set ro.secure=0 & ro.debuggable=1 then save file
4) repack ramdisk (cpio.gz)
5) repack into boot.img, using zimage + new packed ramdisk, using correct mkbootimg arguments
6) flash using fastboot
7) enjoy
PRO TIP:
Use ONLY LINUX FOR ALL OF THIS ELSE DEVICE WONT BOOT
Sent from my R800i using XDA App
Click to expand...
Click to collapse
Thats pretty much exactly what I did. (I did the initial split under windows though I will try again.)
I used the mkbootimg arguments from SE's building kernel blogpost.
help please
please help me somebody i have a problem i cant seem to fix , i flashed the doom kernel then flashed 4.3 icream sandwhich rom exactly like it said to do in the instructions re-booted ,It all booted up fine i played about with the rom for a few hours as you do then i went back to my backed up stock rom ,but heres where the problem happens on restoring my stock rom for some reason my camera doesnt work and playing youtube videos doesnt work and also when i try downloading from the market it just sits there for ever saying downloading but nothings happening i would be really greatfull if somebody can help me resolve this problem thanks..
are you asking this in all thread's?
flash stock rom with flashtool
help
@nickholtus where do i get the stock rom i cant find it plz help and also how do i use this flash tool thing help please somebody i need my phone working again because im going away for the week.
download flashtool
install drivers (in flashtool folder)
download stock (see development .42 .58 or .62)
flash with flashtool
DooMLoRD said:
Small how-to for creating insecure kernel
1) Unpack kernel.sin to get zImage and ramdisk (tools posted in my other thread)
2) unpack ramdisk
3) edit default.prop and set ro.secure=0 & ro.debuggable=1 then save file
4) repack ramdisk (cpio.gz)
5) repack into boot.img, using zimage + new packed ramdisk, using correct mkbootimg arguments
6) flash using fastboot
7) enjoy
PRO TIP:
Use ONLY LINUX FOR ALL OF THIS ELSE DEVICE WONT BOOT
Sent from my R800i using XDA App
Click to expand...
Click to collapse
Hey Doom, I'm trying to follow this, and I'm getting stuck
I downloaded the R800x 2.3.3 (3.0.1.E.0.88) TFT from here: http://forum.xda-developers.com/showpost.php?p=19438024&postcount=12
I unzipped it using xarchiver (installed on arch linux/available on sourceforge)
I ran unpack-kernelsin.pl, and I get two errors (that don't exit out of the perl script):
1) ramdisk written... gzip: no such file or directory
2) cpio: premature end of image
When I try to cpio-ing the ram disk, my computer just sits... How long should I wait, I have a netbook (i know, not the best for doing compiling) and the longest i've let it sit is about 10 minutes (i'm about to let it sit overnight to see if it'll work itself out)
If you could give me any pointers, that'd be outstanding
Thank you,
Pax
paxChristos said:
Hey Doom, I'm trying to follow this, and I'm getting stuck
I downloaded the R800x 2.3.3 (3.0.1.E.0.88) TFT from here: http://forum.xda-developers.com/showpost.php?p=19438024&postcount=12
I unzipped it using xarchiver (installed on arch linux/available on sourceforge)
I ran unpack-kernelsin.pl, and I get two errors (that don't exit out of the perl script):
1) ramdisk written... gzip: no such file or directory
2) cpio: premature end of image
When I try to cpio-ing the ram disk, my computer just sits... How long should I wait, I have a netbook (i know, not the best for doing compiling) and the longest i've let it sit is about 10 minutes (i'm about to let it sit overnight to see if it'll work itself out)
If you could give me any pointers, that'd be outstanding
Thank you,
Pax
Click to expand...
Click to collapse
for such things send me p.m.
Hi there guys,
I am having an issue and was wondering if someone could point me in the right direction, maybe to a tutorial or some decent info on this.
Anyways, I have been tinkering around and teaching myself about building kernels, and roms and just a short while ago finished compiling my first kernel. I have the zImage, and i have tried adding the zImage to Koush's AnyKernel updater.zip but when i try and flash it says failed but is not displaying any errors (Using TWRP recovery) Or I am doing this wrong and need to unpack and repack boot.img with the new zImage?
Any help is greatly appreciated, Thanks!:good:
(edit) I am building on Fedora 17
You answered your own question.
Unpack the boty.img and repack with new zImage
So I was in the right ball park at least.
Sent from my SGH-T989 using Tapatalk 2
Will fastboot boot boot.img work on the galaxy note for testing a kernel? In case I have a borked kernel I want to take precautions so I don't brick my device.
Sent from my SAMSUNG-SGH-T879 using Tapatalk 2
No to fastboot.
With a broken kernel you should still be able to button combo into recovery and just flash a working kernel .zip
Or..at the very least be able to boot download mode and use Odin to flash the kernel.
I have gotten the boot.IMG all packed back up and when I flash it, my phone just hangs up at the white Samsung logo screen and does not go any further. Does something in the ramdisk have to be edited?
Tapa-a-Talkit it... Galaxy Note...4.2.1
I've been working on porting CM12.1 to the Huawei P8 for the past few weeks. As it stands now, I can build everything without any issues and flash it using TWRP but I'm having issues getting it to boot properly:
The issue is with the ramdisk in the boot.img generated by the cm build. Basically, after flashing the zip file it gets stuck on the Huawei logo then boots back into the recovery. I have added some device specific files from the stock ramdisk. These are essentially "init.<device_name>.rc" files along with some other ones that are subsequently imported (for connectivity like gps and wifi). I also added a "fstab.<device_name>" from the stock ramdisk. What I noticed is that if I restore to stock room and use the boot.img generated by cm build then it goes past the Huawei logo and shows the android loading logo for like 10 seconds then boots back into recovery. Now, I don't expect the cm boot.img to work with stock system.img but the fast that it went further and got past the Huawei logo. This makes me wonder if this is a problem with my cm system.img and not the boot.img. If this is the case then I have to go back and look at the build, it doesn't fail but maybe in my device config is messed up?. Another thing I noticed is that the "init.manufacture.rc" (from stock ramdisk) causes the device to not go past the Huawei logo, removing this import makes it go through to the android loading screen (no idea why).
Another issue I have is getting logs, I only have access to the dmesg from adb shell (once the phone fails and boots into recovery) but it doesn't show much. last_kmsg and kmsg don't work. adb logcat doesn't detect any devices when the device boots.
That sums it, right now I'm just getting by through trial and error but feel like i'm blind without any logs but feel I'm very close to getting it to boot at least. If you guys have any idea where I should look and check then please let me know. I can upload the ramdisk files if someone is interested. Also I'm using the stock kernel provided by Huawei and selinux is disabled.
Thanks!
I would like to help you but i am not a dev. I own a P8 and i would love to see CM coming to our device.
I wish you good luck with this project and hope you will get some support
U got a PM
Gesendet von meinem HUAWEI GRA-L09 mit Tapatalk
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
nea102 said:
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
Click to expand...
Click to collapse
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
I had used that guide, was following that when I was getting the out of space errors.
However, I got it all sorted in the end - I just downloaded a different (older) version of the firmware and that worked.
Help for you
samlis said:
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
Click to expand...
Click to collapse
Hi good day.
I have been following your work from another page, and now in XDA.
I had not read your message, and, I changed the recovery for the stock, and, I was an idiot to close the bootloader.
What happened? Brick simple on my cell phone, did not come out (because I fixed it) of the image of erecovery (EMUI) without tabs or options, a rather rare image.
How do I solve it:
1. I did not enter fastboot, I did not correctly enter the stock recovery (I had deleted the twrp), I had closed the bootloader (my stupidity)
2. Be patient and wait for the battery to run out (wait a day for it).
3. Open cmd and place the command to open the bootloader (fastboot oem unlock) and execute.
4. Put the device in fastboot mode when connecting to the laptop (I did not work several times, the fastboot came out with error FUNC No 10 and NO 2), after numerous attempts and not to let it charge the battery too much (because it was restarted and towards brick in the EMUI logo), correctly enter the fastboot and unlock, when you enter step 3 automatically, it will be executed. I had an advance in removing the cell phone from the brick.
5. It reboots and wonderfully happened to the Rom (that had previously installed), that is to say, the erase was not executed when the bootloader had previously closed.
6. As I had little energy, it was turned off, but I connected it and entered charging mode without restarting (before I did it).
7. Wait for a load of at least 5%, and install the Catuva21 TWRP from the tutorial.
8. I put it by command to restart in fastboot, but I generate error (Error Func No 10 and No 2).
9. I turn off the cell phone and with volume up and power key
10. Enter the TWRP correctly, verify that it is installed.
11. Restart system and log in to the system. I had not deleted anything, but to avoid problems, I hope to load 55% and execute the steps to install the rom.
12. Enjoy and dry spilled tears.
Experience lived and I hope you do not do something that developers do not advise.
Grcias and happy day.
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
heindrix said:
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
Click to expand...
Click to collapse
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
yoni sofer said:
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
Click to expand...
Click to collapse
take a look here, mate.
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Hello.
I have the Huawei Mate 10 Lite phone in my hands. I wanted to change the system to some custom OS and something went wrong.
I unlocked the bootloader, uploaded TWRP and everything was OK. Problems started during Lineage install (the same with AICP). The system did not boot after installing.
At the moment only eRcovery is running but also can't install anything. I suspect this is due to the lack of original recovery. I extracted the RECOVERY.IMG and RECOVERY2.IMG files from the UPDATE.APP file.
However, I can't install them because I get this error:
-=edit=-
After many attempts to repair using information from the internet, I was able to repair the phone with this post - https://forum.xda-developers.com/showpost.php?p=76640204&postcount=79
Many thanks to @Chisetdel31260 for his great work and this post